Develop Bugs

red triangle while trying to update OTA lollipop while on TWRP...

Hey guys, I was rooted but on my stock 4.4.2 Sense Rom. I wanted to flash the OTA lollipop update. I had TWRP so i could not update the OTA. So i found a video on youtube that said i had to...
1 - Replace custom recovery with stock recovery
2 - Process OTA Update
3 - Replace stock recovery with custom recovery
I was at step 2 and my htc one m8 is tmobile US and was T-MOB010 so i downloaded "stock+recovery+1.12.531.19+recovery" there was two different ones for me to choose from. There was that one and then "2.22.531.5" however i could not find that DL link. I then flashed the stock recovery thru ADB and rebooted my phone, and it started to update but then i got a red triangle. I saw a comment on the youtube video that said i needed to find the OTA update and transfer to my PC and find the "recovery.img" file and then extract that and flash that to my phone. I looked thru the entire zip file however there is a folder i could not access, the last one named "firmware" I try to extract but i get an error message saying "cannot open, file is invalid" The OTA update i found in my internal storage in download folder and it is named "OTA_M8_UL_L50_SENSE60_MR_TMOUS_4.20.531.4-3.32.531.2_release_420432xio08y7xuups2gkl" that's got to be it because that's the only thing that could be the update any help??
youtube video: https://www.youtube.com/watch?v=PPPT5J8xG6w
Thread i was going off: http://forum.xda-developers.com/show....php?t=2701376

jfreshh330 said:
Hey guys, I was rooted but on my stock 4.4.2 Sense Rom. I wanted to flash the OTA lollipop update. I had TWRP so i could not update the OTA. So i found a video on youtube that said i had to...
1 - Replace custom recovery with stock recovery
2 - Process OTA Update
3 - Replace stock recovery with custom recovery
I was at step 2 and my htc one m8 is tmobile US and was T-MOB010 so i downloaded "stock+recovery+1.12.531.19+recovery" there was two different ones for me to choose from. There was that one and then "2.22.531.5" however i could not find that DL link. I then flashed the stock recovery thru ADB and rebooted my phone, and it started to update but then i got a red triangle. I saw a comment on the youtube video that said i needed to find the OTA update and transfer to my PC and find the "recovery.img" file and then extract that and flash that to my phone. I looked thru the entire zip file however there is a folder i could not access, the last one named "firmware" I try to extract but i get an error message saying "cannot open, file is invalid" The OTA update i found in my internal storage in download folder and it is named "OTA_M8_UL_L50_SENSE60_MR_TMOUS_4.20.531.4-3.32.531.2_release_420432xio08y7xuups2gkl" that's got to be it because that's the only thing that could be the update any help??
youtube video: https://www.youtube.com/watch?v=PPPT5J8xG6w
Thread i was going off: http://forum.xda-developers.com/show....php?t=2701376
Click to expand...
Click to collapse
It sounds like the stock recovery that you loaded wasn't a new enough version. To update to lollipop you need to install a lollipop or a 4.4.X stock recovery. If you install anything that was released prior to that you will get the red triangle deal.
So try and find one thats a little newer. Perhaps see if someone has posted the lollipop one for your carrier. You can use that one. Should be easy to find as it's the latest. Then the OTA should take just fine. Perhaps the other stock one you mentioned would work. You just need to find it. I'm on Rogers in Canada so I'm not too familiar with the T-Mobile files. As mentioned though, just make sure the stock recovery is from Android 4.4.X or 5.X.X and you will be fine.

flexfulton said:
It sounds like the stock recovery that you loaded wasn't a new enough version. To update to lollipop you need to install a lollipop or a 4.4.X stock recovery. If you install anything that was released prior to that you will get the red triange deal.
So try and find one that a little newer. Perhaps see if someone has posted the lollipop one for your carrier. You can use that one. Should be easy to find as it's the latest. Then the OTA should take just fine. Perhaps the other stock one you mentioned would work. You just need to find it. I'm on Rogers in Canada so I'm not too familiar with the AT&T files. As mentioned though, just make sure the stock recovery in from Android 4.4.X or 5.X.X and you will be fine.
Click to expand...
Click to collapse
Thank you for the reply! Is there a chance of bricking by trying to change out the stock recovery? Or would the worst that would happen is I get the red triangle. I mean obviously I'm not going to be flashing stock recoverys from different devices but u know.

jfreshh330 said:
Thank you for the reply! Is there a chance of bricking by trying to change out the stock recovery? Or would the worst that would happen is I get the red triangle. I mean obviously I'm not going to be flashing stock recoverys from different devices but u know.
Click to expand...
Click to collapse
You mentioned stripping out the recovery.img from the OTA update. This shouldn't be a problem. Not sure why it wouldn't let you access it. Perhaps you have a bad download?
Look around XDA a little more. You should be able to find the OTA you are looking for.
As for flashing a wrong branded stock recovery, I don't really want to say cause I'm not sure what would happen. Just to be safe I'd stick to your carrier's files but perhaps someone else can speak on that.
---------- Post added at 08:00 AM ---------- Previous post was at 07:51 AM ----------
http://forum.xda-developers.com/showthread.php?t=2714456
That link will be of great help to you. Has the recovery you require (3.32.531.2 - I just downloaded it myself with no issues) and much discussion on the subject of OTA Lollipop updates etc for T-Mobile.
Let me know if you need anything else. If you still can't get it to work, those would be the guys to consult.
Happy flashing!

flexfulton said:
You mentioned stripping out the recovery.img from the OTA update. This shouldn't be a problem. Not sure why it wouldn't let you access it. Perhaps you have a bad download?
Look around XDA a little more. You should be able to find the OTA you are looking for.
As for flashing a wrong branded stock recovery, I don't really want to say cause I'm not sure what would happen. Just to be safe I'd stick to your carrier's files but perhaps someone else can speak on that.
Click to expand...
Click to collapse
So I was going to try and download the official Rom off the HTC website. I've found the download link for the Rom. 4.16.1540.8 do you really think of I just use the recovery. IMG file it will work?

flexfulton said:
You mentioned stripping out the recovery.img from the OTA update. This shouldn't be a problem. Not sure why it wouldn't let you access it. Perhaps you have a bad download?
Look around XDA a little more. You should be able to find the OTA you are looking for.
As for flashing a wrong branded stock recovery, I don't really want to say cause I'm not sure what would happen. Just to be safe I'd stick to your carrier's files but perhaps someone else can speak on that.
---------- Post added at 08:00 AM ---------- Previous post was at 07:51 AM ----------
http://forum.xda-developers.com/showthread.php?t=2714456
That link will be of great help to you. Has the recovery you require (3.32.531.2 - I just downloaded it myself with no issues) and much discussion on the subject of OTA Lollipop updates etc for T-Mobile.
Let me know if you need anything else. If you still can't get it to work, those would be the guys to consult.
Happy flashing!
Click to expand...
Click to collapse
Awesome thanks so much!

jfreshh330 said:
So I was going to try and download the official Rom off the HTC website. I've found the download link for the Rom. 4.16.1540.8 do you really think of I just use the recovery. IMG file it will work?
Click to expand...
Click to collapse
Sideload the latest recovery as found in the thread I linked to above. Reboot and the OTA should take no problems. It was downloading and everything fine for you before but was unable to flash because of an outdated recovery you installed.
So my recommened method to update OTA, is to follow the first route you were taking but with the newest recovery.img file in place of what you used in step 1.
If you already have the OTA downloaded on your phone, you shouldn't have to download it again either. It should see that it's already downloaded ready to be installed.
---------- Post added at 08:15 AM ---------- Previous post was at 08:13 AM ----------
jfreshh330 said:
Awesome thanks so much!
Click to expand...
Click to collapse
No problem. Let me know how it turns out for you.

If you don't mind wiping your personal data (you can of course back it up first,and restore later by a variety of methods) and setting up the phone again; it would be much easier to just update by RUU. Relocking the bootloader required if s-on.
The method of returning to stock ROM and recovery will work to update OTA. But its just a lot more potential pitfalls, as you have found (finding the right stock recovery, stock ROM, and even then there is no guarantee your data will be retained, although it should).

redpoint73 said:
If you don't mind wiping your personal data (you can of course back it up first,and restore later by a variety of methods) and setting up the phone again; it would be much easier to just update by RUU. Relocking the bootloader required if s-on.
The method of returning to stock ROM and recovery will work to update OTA. But its just a lot more potential pitfalls, as you have found (finding the right stock recovery, stock ROM, and even then there is no guarantee your data will be retained, although it should).
Click to expand...
Click to collapse
If you flash the stock recovery and let the OS do the OTA update there will be no issues. Relocking bootloaders etc sounds like a lot more work to me.
He is already on stock ROM and has the instructions to do the stock recovery OTA update so I think that's the best route. I provided him with the correct recovery so there should be no problems now.
Also I don't see how in any case doing an OTA would cause you to lose your data. People would have a S$%t fit if they lost data on OTA updates.

flexfulton said:
If you flash the stock recovery and let the OS do the OTA update there will be no issues. Relocking bootloaders etc sounds like a lot more work to me.
He is already on stock ROM and has the instructions to do the stock recovery OTA update so I think that's the best route. I provided him with the correct recovery so there should be no problems now.
Click to expand...
Click to collapse
Its a matter of opinion which approach is easier or "best". I just gave it as another option.
Relocking the bootloader is a single fastboot command. Yes, the OP would then need to unlock the bootloader again after the RUU.
On the other hand, the OTA approach requires flashing stock recovery, then installing 3 OTA updates in order to get up to Lollipop (opposed to just a single RUU that would take the OP up to LP).
flexfulton said:
Also I don't see how in any case doing an OTA would cause you to lose your data. People would have a S$%t fit if they lost data on OTA updates.
Click to expand...
Click to collapse
Its not "supposed" to happen. But I have seen it happen to folks, on more than a few occasions. And yes, those folk have a S$%t fit when it happens.
In any case, everyone should backup their data and be prepared to have to restore it (and its all that much easier on a phone that is already rooted). No data is immune from loss, even from day-to-day use, and all the more for a major system change like an OS update.

redpoint73 said:
Its a matter of opinion which approach is easier or "best". I just gave it as another option.
Relocking the bootloader is a single fastboot command. Yes, the OP would then need to unlock the bootloader again after the RUU.
On the other hand, the OTA approach requires flashing stock recovery, then installing 3 OTA updates in order to get up to Lollipop (opposed to just a single RUU that would take the OP up to LP).
Its not "supposed" to happen. But I have seen it happen to folks, on more than a few occasions. And yes, those folk have a S$%t fit when it happens.
In any case, everyone should backup their data and be prepared to have to restore it (and its all that much easier on a phone that is already rooted). No data is immune from loss, even from day-to-day use, and all the more for a major system change like an OS update.
Click to expand...
Click to collapse
Agreed backups are good.
Why 3 OTA updates? Is that a T-Mobile thing? I only had 1 when I made the jump on the Rogers network.

flexfulton said:
That link will be of great help to you. Has the recovery you require (3.32.531.2 - I just downloaded it myself with no issues) and much discussion on the subject of OTA Lollipop updates etc for T-Mobile.
Click to expand...
Click to collapse
The OP is presently on Android 4.4.2, which is software number 1.xx. He will need a recovery corresponding to 1.xx software, as he seems to have already figured out, but its not working.
---------- Post added at 09:53 AM ---------- Previous post was at 09:50 AM ----------
flexfulton said:
Agreed backups are good.
Why 3 OTA updates? Is that a T-Mobile thing? I only had 1 when I made the jump on the Rogers network.
Click to expand...
Click to collapse
Not just a T-Mob thing.
He is on Android 4.4.2 (software 1.x). Unless T-Mob skipped a software version (and I don't think they did) he needs to update in sequence to software 2.x, then 3.x, then finally up to the current 4.x.
OTAs need to be installed in sequence; opposed to RUUs which are complete factory images, so you can skip software numbers.
Not sure about Rogers. But my guess is that you only had to update from 4.4.4 to 5.0; or something to that effect.

redpoint73 said:
The OP is presently on Android 4.4.2, which is software number 1.xx. He will need a recovery corresponding to 1.xx software, as he seems to have already figured out, but its not working.
---------- Post added at 09:53 AM ---------- Previous post was at 09:50 AM ----------
Not just a T-Mob thing.
He is on Android 4.4.2 (software 1.x). Unless T-Mob skipped a software version (and I don't think they did) he needs to update in sequence to software 2.x, then 3.x, then finally up to the current 4.x.
OTAs need to be installed in sequence; opposed to RUUs which are complete factory images, so you can skip software numbers.
Not sure about Rogers. But my guess is that you only had to update from 4.4.4 to 5.0; or something to that effect.
Click to expand...
Click to collapse
Makes sense. I only had to go up one level. I figured that the carriers would package all of the older updates in with new one but apparently I'm wrong. I appologize.
I was trying to help out as I had the same issue when I went to update. I installed a recovery that was too old, determined that I needed to flash a recovery from either 4.4.X or lollipop and my OTA update was fine after that. Point being, I could go ahead and flash a newer recovery to get the OTA to download.
Anyway I applogize if I was in error in my help. No one else was helping and based on my own experiences it sounded like the same issue.

flexfulton said:
Makes sense. I only had to go up one level. I figured that the carriers would package all of the older updates in with new one but apparently I'm wrong. I appologize.
Click to expand...
Click to collapse
OTAs will normally only allow you to install from the immediate previous version (you cannot skip a version). Sometimes they are complete packages; but often they are not. Sometimes the OTA just contains what has been changed; basically a "patch". And for that reason, the updates need to be installed sequentially. In fact, I've seen folks brick due to unwittingly installing partial firmware packages from OTAs (with s-off, which bypasses such safety checks).
flexfulton said:
Anyway I applogize if I was in error in my help.
Click to expand...
Click to collapse
There's no need to apologize. As you are well aware, this is a self-supporting community that flourishes due to the contributions of its members. Your answers may not have been 100% correct. But it was well intended; and you answered to the best of your knowledge. At least you learned something and can pass it along now. I'm just a member who passes along what I've learned here also (don't have any specialized developer knowledge or anything); and I'm certainly not right all the time.

So the recovery 3.32.5312 will not work? And i apologize i am on 4.4.4 not 4.4.2

HELP!! Potentially bricked my m9

Hi Guys,
Not sure if much can be done, so before I flashed a rom for 5.1.1, I decided to flash the required, firmware 2.9.710.x, but before flashing that, I re-locked my bootloader, as I have s-on. Before that, I was trying to get the OTA to work but it didn't as I had mounted system as r/w. So I had stock recovery, s-on and relocked bootloader. After I flashed the firmware, I could not unlock the bootloader as there is some new developer setting that I am required to enable. BUT the I am still on old 5.0 ROM that will not boot anymore and is stuck on the splash screen - I've tried wipe cache and factory reset. I have an RUU for 1.32 which I cannot use because now I have 2.9.710.x firmware. I've also tried to sideload the OTA but that will not work because system was mounted r/w
Is there anything I can do to get it to work? I feel like I've tried all avenues, but if there is something you guys think I can do to make it work again, I'd be over the moon!

anshuashmeet said:
Hi Guys,
Not sure if much can be done, so before I flashed a rom for 5.1.1, I decided to flash the required, firmware 2.9.710.x, but before flashing that, I re-locked my bootloader, as I have s-on. Before that, I was trying to get the OTA to work but it didn't as I had mounted system as r/w. So I had stock recovery, s-on and relocked bootloader. After I flashed the firmware, I could not unlock the bootloader as there is some new developer setting that I am required to enable. BUT the I am still on old 5.0 ROM that will not boot anymore and is stuck on the splash screen - I've tried wipe cache and factory reset. I have an RUU for 1.32 which I cannot use because now I have 2.9.710.x firmware. I've also tried to sideload the OTA but that will not work because system was mounted r/w
Is there anything I can do to get it to work? I feel like I've tried all avenues, but if there is something you guys think I can do to make it work again, I'd be over the moon!
Click to expand...
Click to collapse
Never relock if your phone is not 100 % stock. Otherwise it won't boot. Besides there are already numerous post written by people that made the same mistake as you did. Even if your phone could boot you wouldn't be able to enable the OEM Unlock option since it's not implemented in the 1.XX roms and by flashing the firmware you do not update your rom.
I guess the only possibility to recover your phone is using this RUU service.
Just because I'm curious: Why didn't you use one of the backups that are provided here?

Flippy498 said:
Never relock if your phone is not 100 % stock. Otherwise it won't boot. Besides there are already numerous post written by people that made the same mistake as you did. Even if your phone could boot you wouldn't be able to enable the OEM Unlock option since it's not implemented in the 1.XX roms and by flashing the firmware you do not update your rom.
I guess the only possibility to recover your phone is using this RUU service.
Just because I'm curious: Why didn't you use one of the backups that are provided here?
Click to expand...
Click to collapse
Thanks for your reply!
I've submitted an enquiry form to them. Didn't know that service existed. Hopefully they have the RUU file that I need.
I did download the stock backup file from that link but I thought before I give it a go, I'll try and get an OTA and get an official update. That failed so I decided to flash the firmware before going to the latest rom. Forgetting I just locked my bootloader with stock recovery, completely unaware of this 5.1 developer option issue. My fault for not doing research, but I didn't know such issue could exist as for the last few years, I haven't had an issue like this. Normally issues occur if I flash a newer ROM without firmware so was trying to avoid that.

Note 4 on Page Plus - how to safely acquire official OTA updates?

I've searched and looked at a couple of guides, etc. but am still unsure: How can I get my Verizon Note 4 up to date with latest Marshmallow? I have seen some guides that say that flashing the official rom will lock the bootloader - I'm assuming this isn't a problem for Page Plus?
My phone is from ebay, but unmodified as far as I can tell.

hrab said:
I've searched and looked at a couple of guides, etc. but am still unsure: How can I get my Verizon Note 4 up to date with latest Marshmallow? I have seen some guides that say that flashing the official rom will lock the bootloader - I'm assuming this isn't a problem for Page Plus?
My phone is from ebay, but unmodified as far as I can tell.
Click to expand...
Click to collapse
Since you're not going to get an OTA the way I would do it is to drop this file (Thanks, hsbadr!) on your SD card, boot into recovery and flash the update.zip. You can do the same with this file (thanks again, hsbadr!) to bring yourself up to date. The second file is the monthly Android security update. That will leave you with a locked Marshmallow bootloader. If it is your intention to unlock a Marshmallow bootloader, that is not how I would do it.
This is how I would do it. Follow the directions closely.

douger1957 said:
Since you're not going to get an OTA the way I would do it is to drop this file (Thanks, hsbadr!) on your SD card, boot into recovery and flash the update.zip. You can do the same with this file (thanks again, hsbadr!) to bring yourself up to date. The second file is the monthly Android security update. That will leave you with a locked bootloader. If it is your intention to unlock a Marshmallow bootloader, that is not how I would do it.
This is how I would do it. Follow the directions closely.
Click to expand...
Click to collapse
Thanks for being so helpful. I have flashed custom roms, rooted, etc with other phones, but I don't have plans for this one just yet. I suppose it's best to have the option in the future. I saw a thread with links to the OTA upgrade files - can they be downloaded and upgraded manually?

hrab said:
Thanks for being so helpful. I have flashed custom roms, rooted, etc with other phones, but I don't have plans for this one just yet. I suppose it's best to have the option in the future. I saw a thread with links to the OTA upgrade files - can they be downloaded and upgraded manually?
Click to expand...
Click to collapse
Use the first two links I gave you, drop the files one at a time starting with the first one, boot into recovery and chose the option that says something about update. Then drop the second file on the sd card and do the same thing.
If you decide to unlock the bootloader, you'll need to downgrade to 5.1.1 in ODIN. If you want an unlocked Marshmallow bootloader, you'll have to do the unlock process twice.

douger1957 said:
Use the first two links I gave you, drop the files one at a time starting with the first one, boot into recovery and chose the option that says something about update. Then drop the second file on the sd card and do the same thing.
If you decide to unlock the bootloader, you'll need to downgrade to 5.1.1 in ODIN. If you want an unlocked Marshmallow bootloader, you'll have to do the unlock process twice.
Click to expand...
Click to collapse
Awesome, thanks. I'm assuming the process you describe will [should] keep my apps/data intact?

hrab said:
Awesome, thanks. I'm assuming the process you describe will [should] keep my apps/data intact?
Click to expand...
Click to collapse
It should. They're Verizon updates.

douger1957 said:
It should. They're Verizon updates.
Click to expand...
Click to collapse
When I boot into recovery, the android logo has chinese text below it. Is this a concern?

Bootloader upgrade questions

Hi,
I was reading the threads about upgrading / unlocking the bootloaders.
After spending almost half day rooting and rerooting, I have a few questions.
Right now I am on BPA1, rooted, stock. In order to install an Marshmallow ROM, it looks like I have to upgrade the bootloader, to minimum CPD1. Here it gets confusing. I already changed the CID to developer and the bootloader is unlocked. If I try to upgrade:
1. Can I flash just the bootloader (and eventually the modem) and not the entire stock firmware?
2. Will I lose root? If yes, I have to reroot, but the rooting tools are kind on unreliable, spent a lot of time already, no guarantee they will work again...In order to push the files for bootloader unlock, root is required. Is there a way to keep root? Flashing the stock firmware seems to lock the bootloader and eliminate root, so every time something needs to be upgraded, we have to go through the same process?
3. At this point, it looks that there are so many updates: CPD, CPF, CPG, CPJ, that I need a CPR if I have to repeat the process 4 times! Some roms don't require the latest update, but if it installed, will it work? E.g. the rom requires CPF and I upgrade to CPJ, what happens?
Thanks!

razvu said:
Hi,
I was reading the threads about upgrading / unlocking the bootloaders.
After spending almost half day rooting and rerooting, I have a few questions.
Right now I am on BPA1, rooted, stock. In order to install an Marshmallow ROM, it looks like I have to upgrade the bootloader, to minimum CPD1. Here it gets confusing. I already changed the CID to developer and the bootloader is unlocked. If I try to upgrade:
1. Can I flash just the bootloader (and eventually the modem) and not the entire stock firmware?
2. Will I lose root? If yes, I have to reroot, but the rooting tools are kind on unreliable, spent a lot of time already, no guarantee they will work again...In order to push the files for bootloader unlock, root is required. Is there a way to keep root? Flashing the stock firmware seems to lock the bootloader and eliminate root, so every time something needs to be upgraded, we have to go through the same process?
3. At this point, it looks that there are so many updates: CPD, CPF, CPG, CPJ, that I need a CPR if I have to repeat the process 4 times! Some roms don't require the latest update, but if it installed, will it work? E.g. the rom requires CPF and I upgrade to CPJ, what happens?
Thanks!
Click to expand...
Click to collapse
Yeah it definitely gets a little confusing, but I might be able to clear up a few of your questions. The bootloader you want to upgrade to is the cpd1 version, after that the only things that change when you upgrade to pf3, pg2, and pj1 are the kernels and modems. Right now I'm using the latest pj1 firmware and my bootloader has never changed from cpd1 and flashed between the different versions several times and for unlocking the bootloader on 6.0 you do have to repeat the process you did for lp, unfortunately.

kevintm78 said:
Yeah it definitely gets a little confusing, but I might be able to clear up a few of your questions. The bootloader you want to upgrade to is the cpd1 version, after that the only things that change when you upgrade to pf3, pg2, and pj1 are the kernels and modems. Right now I'm using the latest pj1 firmware and my bootloader has never changed from cpd1 and flashed between the different versions several times and for unlocking the bootloader on 6.0 you do have to repeat the process you did for lp, unfortunately.
Click to expand...
Click to collapse
OK, so what file do I need to download and flash? I have to unloack the CPD1 bootloader and reroot? Which app? Kingroot or Kingoroot?
Once this is updated, how can I upgrade the modems and kernels, can I flash them individually?
Thanks!

razvu said:
OK, so what file do I need to download and flash? I have to unloack the CPD1 bootloader and reroot? Which app? Kingroot or Kingoroot?
Once this is updated, how can I upgrade the modems and kernels, can I flash them individually?
Thanks!
Click to expand...
Click to collapse
These are excellent questions that I'm sure a lot of members are thinking, but just haven't formally asked.
I have a Developer Device that I got directly from a Samsung 2 years ago. When hsbadr put out CM 14.1, I was still on Android 5.1.1. It seemed like a daunting task to do all that was required to get to CM 14.1, but I went ahead with it. I decided that it just made more sense to have my device CID changed to the one that everyone else was on, so I went through all the motions. Yes, the root thing was very touchy. But it really wasn't all that bad.
I'm now on bootloader CPD1, and just today upgraded the baseband by odin flashing the partial firmware for CPJ2 baseband.
Can't wait for hsbadr's next build!!!!

Ok, so in conclusion, which file needs to be flashed to upgrade to CPD1? Is it a stock tar, or the bootloader can be flashed just by itself? After flashing I'm gonna lose root again and have to start over before changing the CID?
You mentioned that you have a developer edition. I have one developer and one retail. My developer is still on an older Jasmine, but it needs to sent for repair. I'm trying to get the retail one done, so I can use it in the meantime. Then, the plan is to get the same thing done on the developer edition. I was hoping that would be easier, as the bootloader is unlocked, but apparently that's not the case.
Sent from my SM-N910V using XDA Free mobile app

Nobody can recommend the right file to flash?
Sent from my SM-N910V using XDA Free mobile app

I am also looking for advice on how to upgrade the bootloader. I am on BPA1 currently but everything I find keeps upgrading everything but the bootloader.
Thanks in advance for any help you can provide.

Unlocked VZW update

So I have an unlocked HTC 10. a while back I managed to do all the good stuff to make it work with Verizon. I don't remember all of the things I did, but safe to say the needed things for it work on Verizon through the #*#*4636*#*# menu. Fast forward a year later, I'm still on 6.0.1 and I would like to know how I can go to the latest and greatest update from Android while being able to connect to the Verizon signal. I haven't kept up with anything from here so pardon my lack of knowledge.

Xeazlouro said:
So I have an unlocked HTC 10. a while back I managed to do all the good stuff to make it work with Verizon. I don't remember all of the things I did, but safe to say the needed things for it work on Verizon through the #*#*4636*#*# menu. Fast forward a year later, I'm still on 6.0.1 and I would like to know how I can go to the latest and greatest update from Android while being able to connect to the Verizon signal. I haven't kept up with anything from here so pardon my lack of knowledge.
Click to expand...
Click to collapse
So you must be s-off in that case and you simply flashed the Verizon radios, right?
You can probably update your unlocked 10 to the latest software, and then redo the steps you originally did to get it to work on verizon.
To update:
If you were never rooted and didn't ever modify your system partition, make sure you have stock recovery and take the OTA update.
If you are rooted, but have an untouched system backup on hand, restore it as well as stock recovery and then take the OTA.
If you are rooted with no backup, or if the above options fail, the easiest and cleanest way is to backup your phone contents and run the latest Nougat ruu which will bring you to fully stock and updated.
Other option, since you're s-off, is to flash the OTA "manually" with twrp and through fastboot. Look for instructions in the twrp thread faq.

Tarima said:
So you must be s-off in that case and you simply flashed the Verizon radios, right?
If you are rooted with no backup, or if the above options fail, the easiest and cleanest way is to backup your phone contents and run the latest Nougat ruu which will bring you to fully stock and updated.
Other option, since you're s-off, is to flash the OTA "manually" with twrp and through fastboot. Look for instructions in the twrp thread faq.
Click to expand...
Click to collapse
No. To convert US Unlocked to VZW we had to manually set the CID and then run the Verizon RUU. If we flash the latest N RUU, I don't think that'll work on VZW. Last I checked (which was last fall TBH) VZW was on a different and older branch than the Unlocked latest head codeline. We should be able to run the latest VZQ RUU assuming someone has made one. I'm also looking for this. I'll update this post if I find it.

drumz0rz said:
No. To convert US Unlocked to VZW we had to manually set the CID and then run the Verizon RUU. If we flash the latest N RUU, I don't think that'll work on VZW. Last I checked (which was last fall TBH) VZW was on a different and older branch than the Unlocked latest head codeline. We should be able to run the latest VZQ RUU assuming someone has made one. I'm also looking for this. I'll update this post if I find it.
Click to expand...
Click to collapse
Where does the OP say he converted to VZW variant?
There are two ways to get unlocked to work on VZW, one is to flash just the modem and the other is a full Vzw conversion. Based on the fact he states he had to go into the secret menu, my guess is that it was the former which is why I asked....
FYI latest vzw ruu can be found on the Verizon HTC 10 forums.
https://forum.xda-developers.com/verizon-htc-10/how-to/verizon-official-ruu-1-19-605-9-t3377586

Interesting, didn't know you could get VZW to work without the full conversion. That was the route I went, and despite it, my phone still shows up on Verzion as a 'Non Verizon Device' (Everything works though). Thanks for the link to the RUU though!