Develop Bugs

Ota when.rooted

Hi I have a htc one.m8 rooted with htc dev and.twrp and I have a over.the air.update and no way of installing it at the moment. How does one go about doing.this update when.rooted or do I have to unroot to do the update? Thanks
Sent from my HTC One_M8 using Tapatalk

MAhtc said:
Hi I have a htc one.m8 rooted with htc dev and.twrp and I have a over.the air.update and no way of installing it at the moment. How does one go about doing.this update when.rooted or do I have to unroot to do the update? Thanks
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I assume, that a HTC-Stock ROM is installed on your htc one m8. NO Custom ROM and NO Custom HBoot! <- IMPORTANT
Root doesn't matter for an OTA Update.
But you have to flash the Stock Recovery that matches with your ROM Base and Relock the Bootloader.
First you must Backup your device including Internal Storage, because of the Factory Reset that happen when you Unlock the Bootloader again!
You can find here a collection of Stock Recovery
COLLECTION of Stock backup's by Mr Hofs
And you shut use this Toolkit to Relock the Bootloader and to Unlock it again after the OTA.
All-In-One Toolkit V2.0 by Hasoon2000
Menu -> Commands->Relock Bootloader. You have to be in fastboot USB Mode first, to do that.
After that you can receive and install a OTA for HTC.
READ EVERYTHING VERY CAREFULLY IN EVERY THREAD!
Since your device is Unlocked and S-OFF you can brick it with a wrong move!
You can find almost everything on this Forum, try to use Search next time.
Regards, Toni
---------- Post added at 08:03 AM ---------- Previous post was at 07:59 AM ----------
I've forgotten to mention that you must be on the right CID!

Or supercid 11111111

exad said:
Or supercid 11111111
Click to expand...
Click to collapse
As far as I know, you can't receive a OTA Update with Super CID 111111.
It won't flash, because of the "android-info" in the OTA Update File.
The "android-Info" contains the CID that can receive the OTA, otherwise it won't flash. to avoid that the device receives a wrong OTA.
You must set it to the original Provider CID that matches with your Stock ROM.
In your case, I think:
modelid: 0P6B16000
cidnum: TELUS001

just install a custom rom...

Toni10 said:
As far as I know, you can't receive a OTA Update with Super CID 111111.
It won't flash, because of the "android-info" in the OTA Update File.
The "android-Info" contains the CID that can receive the OTA, otherwise it won't flash. to avoid that the device receives a wrong OTA.
You must set it to the original Provider CID that matches with your Stock ROM.
In your case, I think:
modelid: 0P6B16000
cidnum: TELUS001
Click to expand...
Click to collapse
Incorrect, SuperCID bypasses all CID checks. I was pretty sure already as this was the case on my OneXL, but for the sake of giving the correct information, I just restored a Rogers TWRP backup, flashed rogers stock recovery extracted from the rogers OTA, changed my CID to 11111111 and ran the OTA from stock recovery. As per my sig, I am not even using a rogers phone.
Ran just fine.

Does rooting and s-off affect performance at all on the m8?
Sent from my HTC One_M8 using xda app-developers app

No. Just gives you the opportunity to tweak it more to your needs.

Toni10 said:
I assume, that a HTC-Stock ROM is installed on your htc one m8. NO Custom ROM and NO Custom HBoot! <- IMPORTANT
Root doesn't matter for an OTA Update.
But you have to flash the Stock Recovery that matches with your ROM Base and Relock the Bootloader.
First you must Backup your device including Internal Storage, because of the Factory Reset that happen when you Unlock the Bootloader again!
You can find here a collection of Stock Recovery
[url] COLLECTION of Stock backup's by Mr Hofs[/URL]
And you shut use this Toolkit to Relock the Bootloader and to Unlock it again after the OTA.
All-In-One Toolkit V2.0 by Hasoon2000
Menu -> Commands->Relock Bootloader. You have to be in fastboot USB Mode first, to do that.
After that you can receive and install a OTA for HTC.
READ EVERYTHING VERY CAREFULLY IN EVERY THREAD!
Since your device is Unlocked and S-OFF you can brick it with a wrong move!
You can find almost everything on this Forum, try to use Search next time.
Regards, Toni
---------- Post added at 08:03 AM ---------- Previous post was at 07:59 AM ----------
I've forgotten to mention that you must be on the right CID!
Click to expand...
Click to collapse
the link for stock recovery doesn't work

Toni10 said:
As far as I know, you can't receive a OTA Update with Super CID 111111.
It won't flash, because of the "android-info" in the OTA Update File.
The "android-Info" contains the CID that can receive the OTA, otherwise it won't flash. to avoid that the device receives a wrong OTA.
You must set it to the original Provider CID that matches with your Stock ROM.
In your case, I think:
modelid: 0P6B16000
cidnum: TELUS001
Click to expand...
Click to collapse
I have a SaskTel htc one m8

MAhtc said:
Hi I have a htc one.m8 rooted with htc dev and.twrp and I have a over.the air.update and no way of installing it at the moment. How does one go about doing.this update when.rooted or do I have to unroot to do the update? Thanks
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
on another note I am new to this whole root thing and was wondering about going back to stock or at least a step by step way to get the ota update on my rooted m8. I can't seem to find it on the forum, I very well could be blind lol so I apologize
thank you

What you need to do an OTA:
Stock Recovery
Stock Rom
Stock CID or SuperCID
Can I keep root!?!? Yes, you can!
As it stands there is no RUU (Rom Update Utility) to easily return to stock SO If one does not have the stock rom installed, one must restore a stock nandroid and manually flash stock recovery/
Stock Rom Nandroid backups and Recoveries courtesy of Mr Hofs
This collection assumes you know your CID. If you don't know it, check it! Boot to fastboot then use the command: fastboot oem readcid
What can you do if you don't have your nandroid and it isn't listed there? You can request someone from the same carrier with a stock nandroid upload theirs within that thread.
Once you have the nandroid, it's simply a matter of putting the nandroid in the appropriate folder for your custom recovery, booting to said recovery and restoring the nandroid.
Where nandroids should be placed:
TWRP: \sdcard\TWRP\backups\
Philz Touch: \sdcard\clockworkmod\backups\
Once you have the nandroid restored, you will need to flash stock recovery. If you know the stock recovery version you should be using, you can download them on that same thread. It is also possible to extract the recovery from the OTA zip file should you have access to it. (You can use the stock rom you restored to download the OTA then extract it and the firmware.zip file within and then flash the recovery.img)
fastboot flash recovery recovery.img
Then you can boot to stock recovery and flash the OTA.zip
Boot to bootloader
Select Recovery
You'll get a picture on your screen
Press and hold volume up and then press power
You will be presented with a menu
Select apply update from internal storage and then select the OTA Zip file in the downloads folder.
All done.

exad said:
Incorrect, SuperCID bypasses all CID checks. I was pretty sure already as this was the case on my OneXL, but for the sake of giving the correct information, I just restored a Rogers TWRP backup, flashed rogers stock recovery extracted from the rogers OTA, changed my CID to 11111111 and ran the OTA from stock recovery. As per my sig, I am not even using a rogers phone.
Ran just fine.
Click to expand...
Click to collapse
I never tried it with Super CID, to install an OTA.
In the most Tutorials that I've found it was recommended to set the original CID.
But good to Know that it works.
At least it's safer to set the original CID, in that case.
MAhtc said:
the link for stock recovery doesn't work
Click to expand...
Click to collapse
Sorry, the Link is working now.
That is a HTC CID List at xda.
http://forum.xda-developers.com/showthread.php?t=2445289

EDIT: Nevermind, I followed the guide here http://forum.xda-developers.com/showthread.php?t=2708581 to change my MID to the European one,
reflahed the OTA.zip in stock recovery and all good now!
******************************************************************************************************************
I am on SuperCID and flashed everything to 1.54.401.5.
Everything stock.
I tried flashing the OTA.zip from stock recovery but I get an error
"assert failed: check_mid("full", "0P6B100000" == "t".
I have the Asia 2.5GHZ version and the MID is "0P6B11000" but wanted to run full EU WWE and get the updates there.
Does the stock recovery check for ModelID as well?
Is there something I can do, like change my model ID? Can you please point me to a link on how to do it? Thanks.
exad said:
What you need to do an OTA:
Stock Recovery
Stock Rom
Stock CID or SuperCID
Can I keep root!?!? Yes, you can!
As it stands there is no RUU (Rom Update Utility) to easily return to stock SO If one does not have the stock rom installed, one must restore a stock nandroid and manually flash stock recovery/
Stock Rom Nandroid backups and Recoveries courtesy of Mr Hofs
This collection assumes you know your CID. If you don't know it, check it! Boot to fastboot then use the command: fastboot oem readcid
What can you do if you don't have your nandroid and it isn't listed there? You can request someone from the same carrier with a stock nandroid upload theirs within that thread.
Once you have the nandroid, it's simply a matter of putting the nandroid in the appropriate folder for your custom recovery, booting to said recovery and restoring the nandroid.
Where nandroids should be placed:
TWRP: \sdcard\TWRP\backups\
Philz Touch: \sdcard\clockworkmod\backups\
Once you have the nandroid restored, you will need to flash stock recovery. If you know the stock recovery version you should be using, you can download them on that same thread. It is also possible to extract the recovery from the OTA zip file should you have access to it. (You can use the stock rom you restored to download the OTA then extract it and the firmware.zip file within and then flash the recovery.img)
fastboot flash recovery recovery.img
Then you can boot to stock recovery and flash the OTA.zip
Boot to bootloader
Select Recovery
You'll get a picture on your screen
Press and hold volume up and then press power
You will be presented with a menu
Select apply update from internal storage and then select the OTA Zip file in the downloads folder.
All done.
Click to expand...
Click to collapse

Firstly you don't need to relock the bootloder to flash an ota.
From what I can see from looking at the updater script in the ota it checks CID and MID. The CID and MID for various models seem to be listed in the updater script. If yours isn't there then it it will fail.
From what I can see it doesnt seem like a particular CID or MID is required, just one listed in the updater script.
Not sure if you can modify an updater script in a signed ota and it still work or not.

Toni10 said:
As far as I know, you can't receive a OTA Update with Super CID 111111.
It won't flash, because of the "android-info" in the OTA Update File.
The "android-Info" contains the CID that can receive the OTA, otherwise it won't flash. to avoid that the device receives a wrong OTA.
You must set it to the original Provider CID that matches with your Stock ROM.
In your case, I think:
modelid: 0P6B16000
cidnum: TELUS001
Click to expand...
Click to collapse
I left mine on Super CID and was able to flash the OTA. I've also read reports of others who have been able to flash the OTA after only going back to the stock recovery, however I went through the process of relocking my bootloader and insuring all "bloat" apps were restored (this was on an AT&T variant though).

Well tired doing this again but it fails, umm says cid unknown in the recovery screen when try I to flash the ota, tired changing my cid to original and to supercid, still same.thing, don't know what I am doing wrong

I also tried going back to stock and running the update but says it Won't install since it thinks the phone is rooted

exad said:
What you need to do an OTA:
Stock Recovery
Stock Rom
Stock CID or SuperCID
Can I keep root!?!? Yes, you can!
As it stands there is no RUU (Rom Update Utility) to easily return to stock SO If one does not have the stock rom installed, one must restore a stock nandroid and manually flash stock recovery/
Stock Rom Nandroid backups and Recoveries courtesy of Mr Hofs
This collection assumes you know your CID. If you don't know it, check it! Boot to fastboot then use the command: fastboot oem readcid
What can you do if you don't have your nandroid and it isn't listed there? You can request someone from the same carrier with a stock nandroid upload theirs within that thread.
Once you have the nandroid, it's simply a matter of putting the nandroid in the appropriate folder for your custom recovery, booting to said recovery and restoring the nandroid.
Where nandroids should be placed:
TWRP: \sdcard\TWRP\backups\
Philz Touch: \sdcard\clockworkmod\backups\
Once you have the nandroid restored, you will need to flash stock recovery. If you know the stock recovery version you should be using, you can download them on that same thread. It is also possible to extract the recovery from the OTA zip file should you have access to it. (You can use the stock rom you restored to download the OTA then extract it and the firmware.zip file within and then flash the recovery.img)
fastboot flash recovery recovery.img
Then you can boot to stock recovery and flash the OTA.zip
Boot to bootloader
Select Recovery
You'll get a picture on your screen
Press and hold volume up and then press power
You will be presented with a menu
Select apply update from internal storage and then select the OTA Zip file in the downloads folder.
All done.
Click to expand...
Click to collapse
So I cannot flash ota, lost s-off and would like to go back to stock for now, and tried flashing several ways to get stock software back but nothing is working

exad said:
Incorrect, SuperCID bypasses all CID checks. I was pretty sure already as this was the case on my OneXL, but for the sake of giving the correct information, I just restored a Rogers TWRP backup, flashed rogers stock recovery extracted from the rogers OTA, changed my CID to 11111111 and ran the OTA from stock recovery. As per my sig, I am not even using a rogers phone.
Ran just fine.
Click to expand...
Click to collapse
Really? This is terrific info. Not that I care to do any type of OTA, (why bother? It'll be on XDA in a couple of minutes lol) but it is something to remember. I didn't realize the Super CID was that expansive. I did realize that it allowed you to use your phone on any carrier though, so I probably should have picked up on that.

[Q] how to update to least lollipop

hi all
my friend tried to update his phone, and all he's got is:
the phone can't boot into recovery. stuck on "entering recovery"
insert coin rom (v 3.0.8) works fine, except the play store!
i tried to flash a new recovery with no success. finally i flash a twrp by captain throwback version 2.8.0.6, and wow it works!
now, i'm wanna to update his M8 to least android version.
fastboot getvar all:
m8_ul
s-on
CID: HTC__K18
MID: 0P6B10000
HBOOT: 3.16.0.0000
version main: empty
settings >> about >> software information:
android version 4.4.2
sense 6.0
InsertCoin version 3.0.8
build number 1.54.401.10
can i simply flash 4.16.401.10 firmware.zip, least TWRP version, ARHD 34.0 (don't worry i don't forget the boot.img )
or
it's better to return to stock and perform software updates?
by the way,
the build number in settings, is the current firmware.zip that installed? or the firmware that the rom based on??
thank's

i read somewhere that its safer to flash firmwares in row, start at 1.54.401.10 then the others in the x.xx.401.xx line
you can also try simply to flash the latest RUU. maybe you get some wifi errors.
i was on 3.xx.401 firmware and installed the 4.x DEV RUU without any errors
yeah the build number in settings shows the rom base.

ok, thanks
erislav said:
yeah the build number in settings shows the rom base.
Click to expand...
Click to collapse
so, i cannot know the exact firmware he has..
i'm asked that because the safest way to update is going back to stock. i found only 1.54.401.5 NAND Backups.
i'm afraid to flash the wrong nand backup..
how can i know which firmware he has?

http://forum.xda-developers.com/showthread.php?t=2701376
If you want to go the save way Try the 1.54.401.x RUU.exe from the thread. Then you should be fine to apply the otas
Dont be to afraid from flashing wrong files in most cases your phone wont get bricked it just dont boot up

erislav said:
http://forum.xda-developers.com/showthread.php?t=2701376
If you want to go the save way Try the 1.54.401.x RUU.exe from the thread. Then you should be fine to apply the otas
Dont be to afraid from flashing wrong files in most cases your phone wont get bricked it just dont boot up
Click to expand...
Click to collapse
sorry about all of my questions but, i found there only 1.54.1540.10 RUU EXE
not 401 ..

TUR_G7 said:
hi all
my friend tried to update his phone, and all he's got is:
the phone can't boot into recovery. stuck on "entering recovery"
insert coin rom (v 3.0.8) works fine, except the play store!
i tried to flash a new recovery with no success. finally i flash a twrp by captain throwback version 2.8.0.6, and wow it works!
now, i'm wanna to update his M8 to least android version.
fastboot getvar all:
m8_ul
s-on
CID: HTC__K18
MID: 0P6B10000
HBOOT: 3.16.0.0000
version main: empty
settings >> about >> software information:
android version 4.4.2
sense 6.0
InsertCoin version 3.0.8
build number 1.54.401.10
can i simply flash 4.16.401.10 firmware.zip, least TWRP version, ARHD 34.0 (don't worry i don't forget the boot.img )
or
it's better to return to stock and perform software updates?
by the way,
the build number in settings, is the current firmware.zip that installed? or the firmware that the rom based on??
thank's
Click to expand...
Click to collapse
Version main is empty because of the older recovery. Try to flash TWRP 2.8.4.0 again.
You can't flash the firmware zip without being S-Off. Sunshine is the only way to do it now, and it costs $25 (totally worth it). Or you could return to stock and take the OTAs. (stock ROM and recovery plus unmodified system partition)
The build number in settings is in fact the ROM base, and not the current firmware version.

xunholyx said:
Version main is empty because of the older recovery. Try to flash TWRP 2.8.4.0 again.
You can't flash the firmware zip without being S-Off. Sunshine is the only way to do it now, and it costs $25 (totally worth it). Or you could return to stock and take the OTAs. (stock ROM and recovery plus unmodified system partition)
The build number in settings is in fact the ROM base, and not the current firmware version.
Click to expand...
Click to collapse
first thanks for your help!
i will try this tomorrow .
on my m8 I bought sunshine (totally worth it) agree
but before i have s-off i'm flashed new firmware.zip (you have to relock your bootloader)
s-off lets you to flash firmware.zip without Signature and without relock
look at this http://forum.xda-developers.com/showthread.php?t=2696282

TUR_G7 said:
first thanks for your help!
i will try this tomorrow .
on my m8 I bought sunshine (totally worth it) agree
but before i have s-off i'm flashed new firmware.zip (you have to relock your bootloader)
s-off lets you to flash firmware.zip without Signature and without relock
look at this http://forum.xda-developers.com/showthread.php?t=2696282
Click to expand...
Click to collapse
Another part of the problem is that HTC updates incrementally. You can't just leap frog from 4.4.2 to 5.0.1.
Once you get S-Off, you can flash a firmware zip from this thread. @Sneakyghost makes his firmware packages so that you don't have to flash each update one at a time. You can just jump to the newest.
But.....from the readout on the earlier post, it is WWE and there is an RUU for that. It is signed, so it should work. It will only get you to 4.4.4. (3.28.401.9 is the newest on this thread). You could try to flash the Lolly firmware after you have updated to this.

[Q] 2.10.401.1 RUU.exe or how to get back to full Stock ROM

Hi Folks,
Well, I'm S-OFF and running ViperROM with 2.10.401.1 firmware (from sneakyghost thread) and TWRP Recovery on an international device with unlocked bootloader and SuperCID.
Now I want to play again with a full fresh and clean stock experience. How to accomplish this?
The easiest way would be to run a 2.10.401.1 RUU exe, but I couldn't find one. I guess it's not available and maybe never will be.
So, after reading threads I would assume the way I have to go is to run an 1.32 RUU exe and then I should get the 2.10 OTA
Is that right or do I have to relock the bootloader to get stock OTAs ? (Cos of S-OFF)
Hope you could help me out on that one and point me in the right direction.
Thx

You have to be 100% stock to get OTAs successfully. Since you're s-off, just running an earlier RUU exe should do it, but you may need to relock.
Under no circumstances should you go back to s-on.

DroidShift79 said:
Hi Folks,
Well, I'm S-OFF and running ViperROM with 2.10.401.1 firmware (from sneakyghost thread) and TWRP Recovery on an international device with unlocked bootloader and SuperCID.
Now I want to play again with a full fresh and clean stock experience. How to accomplish this?
The easiest way would be to run a 2.10.401.1 RUU exe, but I couldn't find one. I guess it's not available and maybe never will be.
So, after reading threads I would assume the way I have to go is to run an 1.32 RUU exe and then I should get the 2.10 OTA
Is that right or do I have to relock the bootloader to get stock OTAs ? (Cos of S-OFF)
Hope you could help me out on that one and point me in the right direction.
Thx
Click to expand...
Click to collapse
Hi
Did you check this thread...
http://forum.xda-developers.com/one-m9/development/firmware-t3068243

MAX 404 said:
Hi
Did you check this thread...
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
Click to expand...
Click to collapse
Yes, did that. But the full ZIP that is there doesn't touch the /system partition, so it's not the clean way I want to go.
THX anyway.

DroidShift79 said:
Yes, did that. But the full ZIP that is there doesn't touch the /system partition, so it's not the clean way I want to go.
THX anyway.
Click to expand...
Click to collapse
Hi
I see....guess the only way for now is as you point out earlier RUU and upgrade from there.
good luck

MAX 404 said:
Hi
I see....guess the only way for now is as you point out earlier RUU and upgrade from there.
good luck
Click to expand...
Click to collapse
Thought of this,
just not sure if I need to relock bootloader to get official otas

DroidShift79 said:
Thought of this,
just not sure if I need to relock bootloader to get official otas
Click to expand...
Click to collapse
If you're S-OFF you don't need to relock to get OTAs. I converted my carrier handset to unbranded and received OTA updates after flashing a RUU without relocking.
Sent from my HTC One M9 using Tapatalk

THX kingvortex. I just do it and report back.
Thanks all of you.

DroidShift79 said:
Thought of this,
just not sure if I need to relock bootloader to get official otas
Click to expand...
Click to collapse
kingvortex said:
If you're S-OFF you don't need to relock to get OTAs. I converted my carrier handset to unbranded and received OTA updates after flashing a RUU without relocking.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
hi mates
I do not think S-OFF , S-ON or locked bootloaders are much of an issue to get OTA, check points 8, 9 and 10 from this thread
EDIT : kingvortex you are right oem locked is necessary with s-on
http://forum.xda-developers.com/one...ery-twrp-touch-recovery-t3066720/post59745198
8. How do I restore stock system so that I can accept an OTA?
Check the "Mount system as read-only" box in the Mount menu.
Restore stock "System Image" backup (This will only work if you've made a System Image backup prior to making any modifications to /system like root it). As of the official 2.8.6.1 version, it is no longer necessary to fastboot flash the stock system image.
NOTE: If you made a stock system backup with one of the Beta TWRP versions, you will have to rename the backup file in the backup folder manually from "system.emmc.win" to "system_image.emmc.win" for the new official TWRP to see it as a "System Image" backup rather than a "System" backup. Otherwise, you'll get an error that the backup can't be restored because system is read-only.
Fastboot flash stock recovery (fastboot flash recovery recovery_signed.img)
NOTE: It is also possible to restore stock recovery via the TWRP GUI. Rename the stock recovery file to "recovery.emmc.win" and place in the backup folder with the stock system image. Recovery will then show as a restore option. MAKE SURE YOU REALLY WANT TO DO THIS, AS TWRP WILL BE GONE WHEN YOU REBOOT OUT OF RECOVERY!!
Reboot to system, install OTA.
9. What if I have an RUU? Do I need to worry about all this OTA nonsense?
Not if you don't care about losing all your data. If you're S-ON and have an RUU available for your exact variant (model ID and CID must match) and software number (main version must be the same or newer), then you can get back to a fully stock state by relocking (fastboot oem lock) and flashing an RUU. However, if you'd prefer to take an OTA to keep your data intact, the method stated above is how to do so. Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software (though you'll still have to find a way to update your firmware if you're not S-OFF)
10. After I go through all this and successfully apply an OTA, how do I make sure I have a clean starting point again?
After the OTA is applied and TWRP is flashed, it will once again detect an untouched system, which will mount system read-only and allow you to make a fully stock backup and start the process over again, this time with the new base.

Well, what I did so far, was to use the 1.32.401.17 ruu.exe
Flash went fine, but no OTA did show up.
So I wanted to flash the 1.32.401.8 ruu zip.
But putting it on sdcard or using fastboot flash zip failed.
Wonder why!?
Later on I'll try Max 404 find.
MAX 404 said:
hi mates
I do not think S-OFF , S-ON or locked bootloaders are much of an issue to get OTA, check points 8, 9 and 10 from this thread
EDIT : kingvortex you are right oem locked is necessary with s-on
http://forum.xda-developers.com/one...ery-twrp-touch-recovery-t3066720/post59745198
8. How do I restore stock system so that I can accept an OTA?
Check the "Mount system as read-only" box in the Mount menu.
Restore stock "System Image" backup (This will only work if you've made a System Image backup prior to making any modifications to /system like root it). As of the official 2.8.6.1 version, it is no longer necessary to fastboot flash the stock system image.
NOTE: If you made a stock system backup with one of the Beta TWRP versions, you will have to rename the backup file in the backup folder manually from "system.emmc.win" to "system_image.emmc.win" for the new official TWRP to see it as a "System Image" backup rather than a "System" backup. Otherwise, you'll get an error that the backup can't be restored because system is read-only.
Fastboot flash stock recovery (fastboot flash recovery recovery_signed.img)
NOTE: It is also possible to restore stock recovery via the TWRP GUI. Rename the stock recovery file to "recovery.emmc.win" and place in the backup folder with the stock system image. Recovery will then show as a restore option. MAKE SURE YOU REALLY WANT TO DO THIS, AS TWRP WILL BE GONE WHEN YOU REBOOT OUT OF RECOVERY!!
Reboot to system, install OTA.
9. What if I have an RUU? Do I need to worry about all this OTA nonsense?
Not if you don't care about losing all your data. If you're S-ON and have an RUU available for your exact variant (model ID and CID must match) and software number (main version must be the same or newer), then you can get back to a fully stock state by relocking (fastboot oem lock) and flashing an RUU. However, if you'd prefer to take an OTA to keep your data intact, the method stated above is how to do so. Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software (though you'll still have to find a way to update your firmware if you're not S-OFF)
10. After I go through all this and successfully apply an OTA, how do I make sure I have a clean starting point again?
After the OTA is applied and TWRP is flashed, it will once again detect an untouched system, which will mount system read-only and allow you to make a fully stock backup and start the process over again, this time with the new base.
Click to expand...
Click to collapse

RUU Error 155 despite relocked bootloader

Phone specs:
Code:
RELOCKED
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.23.213311491.05G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.20.531.4 (1.54.401.5)
eMMC-boot 2048MB
So I'm trying to update my One M8, and I think I messed up pretty bad. I tried running the RUU updater for my T-Mobile variant (found on HTC's ROM Download page), but got the infamous "error 155." However, my bootloader is re-locked. Therefore, according to all the forum posts I could find, I shouldn't be getting that error. I've run a few commands since then, including fastboot oem writecid 11111111 and fastboot erase cache. Somehow, I've managed to get to the point where my phone won't even boot into recovery, it just gets stuck at the "Entering recovery..." screen. However, while stuck on this screen, the phone does respond to ADB commands. I can get root shell access, but I'm not sure what to do with it.
I've tried flashing TWRP 3.0.0.0 to no avail. I've tried running fastboot boot <twrp filename here>, also to no avail. I'm pretty much stuck with a phone that only boots into fastboot, and a weird purgatory-recovery where I can achieve shell access. The RUU file fails to update no matter what I do.
Is there a way I can fix this, or have I completely bricked my phone?
Thank you for your time.

RalphORama said:
Phone specs:
Code:
RELOCKED
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.23.213311491.05G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.20.531.4 (1.54.401.5)
eMMC-boot 2048MB
So I'm trying to update my One M8, and I think I messed up pretty bad. I tried running the RUU updater for my T-Mobile variant (found on HTC's ROM Download page), but got the infamous "error 155." However, my bootloader is re-locked. Therefore, according to all the forum posts I could find, I shouldn't be getting that error. I've run a few commands since then, including fastboot oem writecid 11111111 and fastboot erase cache. Somehow, I've managed to get to the point where my phone won't even boot into recovery, it just gets stuck at the "Entering recovery..." screen. However, while stuck on this screen, the phone does respond to ADB commands. I can get root shell access, but I'm not sure what to do with it.
I've tried flashing TWRP 3.0.0.0 to no avail. I've tried running fastboot boot <twrp filename here>, also to no avail. I'm pretty much stuck with a phone that only boots into fastboot, and a weird purgatory-recovery where I can achieve shell access. The RUU file fails to update no matter what I do.
Is there a way I can fix this, or have I completely bricked my phone?
Thank you for your time.
Click to expand...
Click to collapse
Have you flashed both stock recovery for the RUU in particular youre flashing and re-locked BL, and are you installing a version number that is equal to or higher than the one you already have installed.
Completely stock phone should flash RUU, as long as its not a version down from whats installed, ie, trying to flash LP when MM is already flashed on phone, UNLESS of course youre s-off and supercid, because with supercid you should be able to flash any RUU .
But i had similar issues, im s-on, so i had to revert to stock LP completely, then flashed HTC__001 Stock MM for my phone, failing all that there is always the option of copying a nandroid on here to ur sd card, boot into twrp and restore the Nandroid just to get it up and running again.
I would run the RUU, let it sit at first screen, goto start button and type in %temp%, find the folder inside temp that ruu just created, (sort by date), pull the rom.zip from that to ur desktop, Unzip it and get the files recovery and boot.img, flash them both to ur phone via fastboot, if it still works, then restart ur phone and it should load up, you could then try to install the RUU from windows again, failing that after flashing recovery and boot, goto ur stock recovery and wipe and reset then reboot phone.
It doesnt sound like hard brick, just soft brick, it should be ok.

If you try to flash a Android MM ruu i suggest to flash a lower ruu first. Usually the big jump from the 3.16 boot loader to a 3.19 boot loader is too much.
Or flash the standalone firmware first and then the full ruu.
The high version of TWRP doesn't work because your bootloader is too low (3.16) if you want a working TWRP then use a 2.7 version.
If you can get to the bootloader then it's just a softbrick. A hardbrick is only when the bootloader is not accessible anymore or when the phone doesn't boot up in any way anymore.
Cheers

Mr Hofs said:
Or flash the standalone firmware first and then the full ruu.
Click to expand...
Click to collapse
This is most likely the solution. In particular, if OP is trying to install MM RUU, there is a new peculiarity (requirement?) with all MM RUUs, where you need to have MM firmware in order to run the RUU, or else you will have Error 155.
Find the firmware.zip that matches the version number of the RUU, flash it; then try the RUU again.
---------- Post added at 09:42 AM ---------- Previous post was at 09:35 AM ----------
gazza35 said:
Have you flashed both stock recovery for the RUU
Click to expand...
Click to collapse
You don't need stock recovery to RUU. Folks keep saying this, and its not true.
You need stock recovery to OTA, but you do not need it for RUU. OTA and RUU are two very different things.
gazza35 said:
because with supercid you should be able to flash any RUU .
Click to expand...
Click to collapse
This is also not true. You need to match MID and CID (or SuperCID) in order to flash an RUU. SuperCID bypasses the CID check, but you still need to pass the MID check.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
gazza35 said:
But i had similar issues, im s-on, so i had to revert to stock LP
Click to expand...
Click to collapse
Same peculiarity with the MM RUU I mentioned above (need to flash the MM firmware if coming from LP) also applies if you try to downgrade back to LP. Meaning, you need to flash the LP firmware, then LP RUU.

Mr Hofs said:
If you try to flash a Android MM ruu i suggest to flash a lower ruu first. Usually the big jump from the 3.16 boot loader to a 3.19 boot loader is too much.
Or flash the standalone firmware first and then the full ruu.
The high version of TWRP doesn't work because your bootloader is too low (3.16) if you want a working TWRP then use a 2.7 version.
If you can get to the bootloader then it's just a softbrick. A hardbrick is only when the bootloader is not accessible anymore or when the phone doesn't boot up in any way anymore.
Cheers
Click to expand...
Click to collapse
Thank you (and everyone else) for your replies! Out of curiosity, where can I find a lower RUU? I can only find the most recent one from HTC's website.
EDIT: I flashed TWRP 2.7 and I was able to boot into recovery! I love progress.

RalphORama said:
Out of curiosity, where can I find a lower RUU? I can only find the most recent one from HTC's website.
Click to expand...
Click to collapse
You can find the links for older T-Mob RUUs here: http://forum.xda-developers.com/showthread.php?t=2714456

HTC M8(TMOB101) Revert to Stock Issue

Sorry..if it's an already solved issue.
I'm using an unlocked HTC M8 which I rooted, unlocked bootloader and installed the latest Lineage OS (Android 7.1.2).
I got a good offer for the device and would like to sell it. So I want to revert it back to stock.
The device information are :
version-main: 6.12.111.4
version-misc: PVT SHIP S-ON
modelid: 0P6B10000
cidnum: T-MOB101
I could only find a Lollipop firmware for my CID which I copied into my SD card as OP6BIMG.zip
But the bootloader gives error as "Large Image Update Failed..Press power to reboot"
This goes on until I remove my SD card.
The RUU I used is "0P6BIMG_M8_UL_L50_SENSE60_MR_TMO_DE_4.19.111.3_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_449335_combined_signed.zip"
Is this because I'm trying to downgrade Android version?
Also should I try after re-locking the bootloader (which is something I'm a bit worried to do because I think I will end up in an even worse condition if it doesn't work...because in my experience with an M9 it never unlocks again after relocking in a custom rom.)
Please help.

If you can't find 6.12.111.4, restore fully stock backup
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You don't need to relock bootloader to restore nandroid
Edit : here is RUU.zip - https://www.androidfilehost.com/?fid=24399965296001026
You need to relock bootloader to install RUU

ckpv5 said:
If you can't find 6.12.111.4, restore fully stock backup
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You don't need to relock bootloader to restore nandroid
Edit : here is RUU.zip - https://www.androidfilehost.com/?fid=24399965296001026
You need to relock bootloader to install RUU
Click to expand...
Click to collapse
OK..will try the RUU zip after relocking bootloader.
Hope it works.
Will update about the same after.

Downloading...

So I relocked my bootloader.. downloaded the RUU zip.. renamed it to 0P6BIMG and put in my SD card.
Booted into bootloader and voila.. it flashed right away and now am back to pure stock.
Thank you..ckpv5 for all the help.
You saved my day.

[email protected] said:
I'm using an unlocked HTC M8 which I rooted, unlocked bootloader and installed the latest Lineage OS (Android 7.1.2).
I got a good offer for the device and would like to sell it. So I want to revert it back to stock.
Click to expand...
Click to collapse
Just good practice: Always make a TWRP backup before flashing a custom ROM, root, etc.
I personally never start messing with these phones, without beforehand having some strategy to get back to stock.
[email protected] said:
The device information are :
version-main: 6.12.111.4
I could only find a Lollipop firmware for my CID which I copied into my SD card as OP6BIMG.zip
But the bootloader gives error as "Large Image Update Failed..Press power to reboot"
This goes on until I remove my SD card.
The RUU I used is "0P6BIMG_M8_UL_L50_SENSE60_MR_TMO_DE_4.19.111.3_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_449335_combined_signed.zip"
Is this because I'm trying to downgrade Android version?
Click to expand...
Click to collapse
Correct. You cannot "downgrade" by RUU with s-on.
[email protected] said:
Also should I try after re-locking the bootloader (which is something I'm a bit worried to do because I think I will end up in an even worse condition if it doesn't work...because in my experience with an M9 it never unlocks again after relocking in a custom rom.)
Click to expand...
Click to collapse
Typically, no problem unlocking the bootloader on the M8 again, after relocking it.
Locked or Relocked bootloader is required to RUU with s-on.

redpoint73 said:
Just good practice: Always make a TWRP backup before flashing a custom ROM, root, etc.
I personally never start messing with these phones, without beforehand having some strategy to get back to stock.
Correct. You cannot "downgrade" by RUU with s-on.
Typically, no problem unlocking the bootloader on the M8 again, after relocking it.
Locked or Relocked bootloader is required to RUU with s-on.
Click to expand...
Click to collapse
Thanks for all the information.
Will definitely keep these in mind the next time I try to mess with software;

Hello a quick question, instead of reverting to stock by RUU, can I flash a Sense-based rom via TWRP? I am presently on Lineage 15.1 with latest TWRP and S on. Thank you.

Babakkardan said:
Hello a quick question, instead of reverting to stock by RUU, can I flash a Sense-based rom via TWRP? I am presently on Lineage 15.1 with latest TWRP and S on. Thank you.
Click to expand...
Click to collapse
If you are looking to go back to stock..you can use Stock RUU zip of your model to flash via recovery.

[email protected] said:
If you are looking to go back to stock..you can use Stock RUU zip of your model to flash via recovery.
Click to expand...
Click to collapse
You can't flash RUU.zip with recovery. It will fail if you try to do so. You need to flash RUU.zip with htc_fastboot in RUUmode. Otherwise use the SD card method (auto install in bootloader). Another alternative is to flash the RUU executable (.exe).

redpoint73 said:
You can't flash RUU.zip with recovery. It will fail if you try to do so. You need to flash RUU.zip with htc_fastboot in RUUmode. Otherwise use the SD card method (auto install in bootloader).
Click to expand...
Click to collapse
Oops my bad...I actually meant the sd card method renaming the rom to OP6BIMG.
:angel:
(Thanks for correcting)