Develop Bugs

Troubleshooting Guide & FAQ: Updating stock ROM

Hi guys,
I saw many threads popping up in the Q & A section about applying updates on a stock rooted ROM. So i though it would be helpul if i shared my experiences and also clear some misconceptions.
This Thread mainly applies for those looking to upgrade from 2.09 to the recent 2.22/2.24 ! It may or may not work for any previous updates.
Q) My phone is rooted, Bootloader unlocked and CWM installed. How do i update to 2.22?
Ans.)
1) Backup your root using Voodoo OTA Rootkeeper.
2) Flash the stock recovery for your area using the All in one kit (or you can use the command line if you're familiar).
3) Download the update, click install, sit back and enjoy !
ITS that simple.
Q) What do i do if i cant find stock recovery for my latest version?
Ans) The recovery does not seem to have changed from version 1.56 to 2.09. You can flash the older recovery provided, you've checked your region is correct.
Q) Do i need to re-lock my bootloader for the update to take place?
Ans) NO! You don't need to re-lock anything. It updates perfectly fine with unlocked bootloader. Just flash Stock recovery !
Q) Do i lose my apps/settings/cache?
Ans) Since its an OTA from HTC, you retain everyhting!
Q) Will i lose my root if i update?
Ans) You will! Thats exactly why you're advised to backup your root.
Q) My updates fails with a red triangle and exclamation mark, what did i do wrong?
Ans) You need to understand that during the update, several stock apps are patched. If any of these STOCK APPS ( the ones that came with ya new phone) are uninstalled/frozen/meddled with, an error will pop up.
Q) How do i identify the cause of the error?
Ans) When the red triangle pops up, press the Volume UP, Volume DOWN and LOCK keys at the same time for a second and release. You should see the cause of your error. Try to restore/unfreeze the app thats causing the error. If that is not possible, try posting your error here to see if experts here can help.
All the stock recoveries can be found on this forum. If however u've a doubt, i'd be happy to help.
This guide is not perfect and may contain errors ( i've tried to make it complete to the best of my knowledge). I'm open to suggestions and questions

shubhamsizzles said:
Hi guys,
I saw many threads popping up in the Q & A section about applying updates on a stock rooted ROM. So i though it would be helpul if i shared my experiences and also clear some misconceptions.
This Thread mainly applies for those looking to upgrade from 2.09 to the recent 2.22/2.24 ! It may or may not work for any previous updates.
Q) My phone is rooted, Bootloader unlocked and CWM installed. How do i update to 2.22?
Ans.)
1) Backup your root using Voodoo OTA Rootkeeper.
2) Flash the stock recovery for your area using the All in one kit (or you can use the command line if you're familiar).
3) Download the update, click install, sit back and enjoy !
ITS that simple.
Q) What do i do if i cant find stock recovery for my latest version?
Ans) The recovery does not seem to have changed from version 1.56 to 2.09. You can flash the older recovery provided, you've checked your region is correct.
Q) Do i need to re-lock my bootloader for the update to take place?
Ans) NO! You don't need to re-lock anything. It updates perfectly fine with unlocked bootloader. Just flash Stock recovery !
Q) Do i lose my apps/settings/cache?
Ans) Since its an OTA from HTC, you retain everyhting!
Q) Will i lose my root if i update?
Ans) You will! Thats exactly why you're advised to backup your root.
Q) My updates fails with a red triangle and exclamation mark, what did i do wrong?
Ans) You need to understand that during the update, several stock apps are patched. If any of these STOCK APPS ( the ones that came with ya new phone) are uninstalled/frozen/meddled with, an error will pop up.
Q) How do i identify the cause of the error?
Ans) When the red triangle pops up, press the Volume UP, Volume DOWN and LOCK keys at the same time for a second and release. You should see the cause of your error. Try to restore/unfreeze the app thats causing the error. If that is not possible, try posting your error here to see if experts here can help.
All the stock recoveries can be found on this forum. If however u've a doubt, i'd be happy to help.
This guide is not perfect and may contain errors ( i've tried to make it complete to the best of my knowledge). I'm open to suggestions and questions
Click to expand...
Click to collapse
Hi, thanks for the super explanations - last two really helped me - at least I found the reason why my phone does not want to Updates.
I send thanks to your instructions displayed mistake - I phone from T-Mobile Czech and the application of course I deleted it - it is useless.
Do you know if this can be downloaded somewhere, possibly where I got all this ROM mentioned in the error? I deleted more applications, so it probably will want to install these
I watched a lot of the internet, but I found none.
Sorry for my English ...

Well, if you made a backup if the current Rom/apps, then just extract and install the apps. Or else, I think you can extract the app from ruu if your version. You'll have to do it for each of the apps you uninstalled. That's gonna be a hell of a job, if u ask me.
I think its better you stick to the current software, or of you really wanna update, reset your phone via ruu. And then update.
Sent from my HTC One V using xda app-developers app

Rooted M8 + Stock recovery

Ok, I rooted and S-offed my phone to install adaway and to remove some google blotware from my stock ROM. Then i put back stock recovery to have option of OTA update.
Question is, how can I know that OTA is working? When I had custom recovery I have tried search for updates to see is there any difference noticable. It searched for updates, the same it is searching now with stock. But, there is no any updates atm.
So, once when they actually come, how will I know is my phone seeing them?

cyberlord86 said:
Ok, I rooted and S-offed my phone to install adaway and to remove some google blotware from my stock ROM. Then i put back stock recovery to have option of OTA update.
Question is, how can I know that OTA is working? When I had custom recovery I have tried search for updates to see is there any difference noticable. It searched for updates, the same it is searching now with stock. But, there is no any updates atm.
So, once when they actually come, how will I know is my phone seeing them?
Click to expand...
Click to collapse
Good question and I've been wondering the same myself. I welcome corrections on this but from my understanding, your bootloader must be relocked (tampered flag is OK AFAIK), and I don't think S-Off or On will matter (but likely will be returned to S-ON after OTA), and the recovery must be flashed to stock. Additionally, your Software/OS number should match the most recent update provided by your carrier which can be found on their support page (unable to link because <10 posts hehe).
Being rooted itself shouldn't be a problem as well from what I understand.
After doing something like the Dev bootloader unlock, the calculator and flashlight apps are removed - I wonder if the removal of those apps will cause OTA update issues or if it's just any alterations to the \system folder that is cause for concern?

Damn, you brought even more questions to the table. Bootloader relocked? I found on forums that only that stock recovery is important. Plus, now when you said, I checked fir calculator and flaslight. Both gone...
Plus, I had one small 2-3 sec long photo of my carrier during boot. It is gone to.
You said about OS number... it should match cause my ROM is stock.
And I have to update my phone asap when available cuz my carrier is having this well known bug with my phone: data connection is dcing with download arrow next to H letter that stops to light.

You don't need to relock bootloader to get OTA. Stock recovery and all the system apps should be present and you shouldn't be rooted.

uronfire said:
You don't need to relock bootloader to get OTA. Stock recovery and all the system apps should be present and you shouldn't be rooted.
Click to expand...
Click to collapse
Even if those system apps are: google kiosk, for example?
And, will I see those OTAs when they come without being able to install OR i will not be able to see them at all?

If you have a stock ROM and haven't messed with the CID or MID, you will get the notification.
To install the OTA, you need an unmodified ROM and stock boot loader.

BenPope said:
If you have a stock ROM and haven't messed with the CID or MID, you will get the notification.
To install the OTA, you need an unmodified ROM and stock boot loader.
Click to expand...
Click to collapse
Woops, I guess I was mostly wrong! Good to know. This means I also need to replace the flashlight and calculator apps as well?

Ok, prerequisites for OTA on rooted stock rom
1, it is fine to be rooted
2, it is fine to be s off
3, you must have stock recovery
4, you must have stock firmware
5, you must have completely stock rom (see above its fine to still be rooted) i.e no system apps removed, the rom must be as it was out of the box with all bloatware etc.
if you meet the above conditions, you should be able to get OTAs:good:
Only issue maybe that the ota breaks root i beleive, but once that's installed, you can reflash custom recovery and su binaries

exocetdj said:
Ok, prerequisites for OTA on rooted stock rom
1, it is fine to be rooted
2, it is fine to be s off
3, you must have stock recovery
4, you must have stock firmware
5, you must have completely stock rom (see above its fine to still be rooted) i.e no system apps removed, the rom must be as it was out of the box with all bloatware etc.
if you meet the above conditions, you should be able to get OTAs:good:
Only issue maybe that the ota breaks root i beleive, but once that's installed, you can reflash custom recovery and su binaries
Click to expand...
Click to collapse
Few aps like calculator and flashlight gone away with the root, I was not the one who deleted them. I did not even know they will be deleted so I didn't backup them.
My only question is, since all other conditions are met, will my phone at least "see" that OTA update? And when that happens, I can do Factory reset in stock recovery (which i have) and with some luck deleted aps will be installed again.

cyberlord86 said:
Few aps like calculator and flashlight gone away with the root, I was not the one who deleted them. I did not even know they will be deleted so I didn't backup them.
My only question is, since all other conditions are met, will my phone at least "see" that OTA update? And when that happens, I can do Factory reset in stock recovery (which i have) and with some luck deleted aps will be installed again.
Click to expand...
Click to collapse
do you have a stock backup??
if so just retsore that with a CUSTOM recovery, then flash your stock recovery and that should be all you need if the other conditions are satisfied. By restoring a stock backup you will have these missing apps. if you don't have a backup, check HERE
you will need the matching backup to your firmware (in fastboot type "fastboot getvar mainver" and it will let you know if you are unsure of your firmware number.
Oh and thank @Mr Hofs for his lovely backup collection

Possible Brick HTC M8

Hello All,
I think I may have possibly bricked my m8.
I was using cyanogen 11, when I decided to try and flash the GPE rom that is available.
However I did not flash the latest firmware. I am not able to get into fast boot. When I press Power + Volume Down, it takes me too bootloader but no options are available other then press power to reboot.
When it reboots I do get into the rom however, wifi, and service are unavailable for obvious reasons. My Stupidity may have costed me this phone :/ I wasn't able to get s-off with my t mobile variant. It is unlocked, and had TWRP installed.
Any help would be greatly appreciated!

Bricked? But you can get into ROM? Do you even know what a "brick" means?
Just restore your device to Stock and do an OTA to get latest firmware in order to have a working custom ROM on latest firmware. You are T-Mobile, US? Do an RUU, or head over to the Collection thread in General section and download a nandroid backup for your device and restore it from within TWRP(Instructions is also available in the first 2 posts of the Collection Thread).
If you can get it into bootloader/fastboot it ain't "bricked", it's recoverable.

BerndM14 said:
Bricked? But you can get into ROM? Do you even know what a "brick" means?
Just restore your device to Stock and do an OTA to get latest firmware in order to have a working custom ROM on latest firmware. You are T-Mobile, US? Do an RUU, or head over to the Collection thread in General section and download a nandroid backup for your device and restore it from within TWRP(Instructions is also available in the first 2 posts of the Collection Thread).
If you can get it into bootloader/fastboot it ain't "bricked", it's recoverable.
Click to expand...
Click to collapse
Okay maybe not bricked but I messed it up quite badly, Im not able to get it into the recovery or have it be detected via fastboot. I did try and do a ruu to have it be put back to stock but Im not sure how to go about doing that since ruu cannot see it since it isnt in fastboot... :/

Did you Make sure you update you SDK. Only the latest fastboot and adb will work with lollipop

subarudroid said:
Did you Make sure you update you SDK. Only the latest fastboot and adb will work with lollipop
Click to expand...
Click to collapse
I did get the latest one from the official site, I was able to use it perfectly fine last night. Now however when I try adb shows the device offline, even if I kill and start the server, and disable and renable the debugging, try different ports etc. I can get it to show the device name, but it says offline next to it, I get no prompt on the device. I was reading the gpe doesnt use fastboot, ( I may be wrong) But that would explain why I dont see anything at the bootloader screen, other then press power to reboot the device.

Good news everyone! I was able to fix it in the most impractical way ever.
So why nothing else worked, I did still have access to the rom which of course had no wifi or service. So what I did was install the terminal emulator via browsers onto my phone, from there I was able to type reboot recovery and restore my backup that I had! and wala, whatya know, now it works, and I dont have a useless phone anymore

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.

Can't get past hands free activation on any rom

Decided to go back to my S-oFF Sprint htc one m8 from over a year ago.
First thing I did was update my firmware only, no recovery no boot, firmware only. I upgraded firmware to 6.20.651.3 using this link: http://forum.xda-developers.com/showthread.php?t=2729173
I then updated my twrp from 2.8.50 to 3.0.2-0.
after I try any rom, even sprint roms, I can't get passed the hands free activation and prl update screen. It will reboot before the phone boots up. I have tried a few gpe roms and it wont get past the boot screen.
I tried loading up a nandroid i made over a year ago and its a lollipop rom that works, but still wants to go through handsfree activation. I am able to turn it off there, but want to get back to marshmallow and newer roms. I called sprint support and they said it shows as fully activated on their end.
What else should I try? Should i upgrade firmware, recovery and boot?

I hate bumping, but im out of options here. Any advice?

memekmek said:
I hate bumping, but im out of options here. Any advice?
Click to expand...
Click to collapse
I've gone through countless threads like these: http://forum.xda-developers.com/showthread.php?t=2716834
my situation seams to be unique, where my phone will actually reboot right after hands free activation, thus rendering it useless. I've been able to mount the system in twrp and delete the htc service apk, but on the marshmallow roms, i can't get LTE to work.
Im stumped. :crying:

So I've managed to read through threads and turn off hands free activation by:
1. Using wifi at initial setup (this helps get passed the initial hands free activation)
2. Mounting system in twrp, then deleting htcservice apk in twrp (this helps getting past the initial setup if its a problem)
3. freezing vdm client in titanium backup to avoid having the hands free activation keep popping up.
However, even though I made sure to upgrade my firmware in steps I am not sure if i properly have the latest firmware installed correctly. Is there a way to check? I have LTE on 5.0 roms, but cannot get LTE to work on 6.0 roms. Even 3g data toggles on and off on 6.0 roms.
Any help on the LTE and firmware issues would be very much appreciated!

memekmek said:
However, even though I made sure to upgrade my firmware in steps I am not sure if i properly have the latest firmware installed correctly. Is there a way to check? I have LTE on 5.0 roms, but cannot get LTE to work on 6.0 roms. Even 3g data toggles on and off on 6.0 roms.
Click to expand...
Click to collapse
On the bootloader screen, the OS number indicates the firmware version. Alternately, if you do fastboot getvar all, the firmware number is shown as "version-main". So you will want to see 6.20.651.3 there for Marshmallow firmware (6.20.654.3 for HK Edition).
Additionally, if the OS number is red on the bootloader screen, or a 2nd number is shown in parenthesis (usually in red) it means there is an issue with the firmware not properly installed (partially installed).

redpoint73 said:
On the bootloader screen, the OS number indicates the firmware version. Alternately, if you do fastboot getvar all, the firmware number is shown as "version-main". So you will want to see 6.20.651.3 there for Marshmallow firmware (6.20.654.3 for HK Edition).
Additionally, if the OS number is red on the bootloader screen, or a 2nd number is shown in parenthesis (usually in red) it means there is an issue with the firmware not properly installed (partially installed).
Click to expand...
Click to collapse
Then I appear to be stuck as to why data does not work on my 6.0 roms. I am a Sprint user, tested the stock rooted rom from OMJ's thread, tried insert coin rom, viper rom. None of the 6.0 roms have data working properly.

memekmek said:
Then I appear to be stuck as to why data does not work on my 6.0 roms. I am a Sprint user, tested the stock rooted rom from OMJ's thread, tried insert coin rom, viper rom. None of the 6.0 roms have data working properly.
Click to expand...
Click to collapse
Only thing I can think of, is do full RUU (will wipe the phone) instead of just the firmware, and see if that helps.

redpoint73 said:
Only thing I can think of, is do full RUU (will wipe the phone) instead of just the firmware, and see if that helps.
Click to expand...
Click to collapse
Does the bootloader need to be relocked? if not, can i rename the ruu as 0P6BIMG.zip and update through fastbook in the bootloader?

memekmek said:
Does the bootloader need to be relocked? if not, can i rename the ruu as 0P6BIMG.zip and update through fastbook in the bootloader?
Click to expand...
Click to collapse
Since you are s-off, you do not need to relock the bootloader to RUU.
Yes, you can use the SD card method (rename RUU to 0P6BIMG.zip, put on SD card, and reboot into bootloader).

redpoint73 said:
Since you are s-off, you do not need to relock the bootloader to RUU.
Yes, you can use the SD card method (rename RUU to 0P6BIMG.zip, put on SD card, and reboot into bootloader).
Click to expand...
Click to collapse
Welp, did the RUU last night. It changed nothing, and did nothing for me other than making it a pain to reinstall twrp and get my nandroid back up. booo
lte and data is still spotty on 6.0 roms. The only other possible reason i think this could be happening is because i tried to carrier unlock this phone a few months ago, but i downloaded sim card info app, and it all appears to be ok.