Develop Bugs

[Solved] How do I restore to stock(recovery and rom no root) with an OTA Update?

So I was wondering how I can return my HTC Desire (CDMA) to stock. I have an OTA update that I got from my friend's desire I also have a nandroid backup of the original sense.
Is there any way to convert the OTA update so it is a flashable zip I can use on CWM?
The other thing is can anyone help me if I post the update?

d-shade said:
So I was wondering how I can return my HTC Desire (CDMA) to stock. I have an OTA update that I got from my friend's desire I also have a nandroid backup of the original sense.
Is there any way to convert the OTA update so it is a flashable zip I can use on CWM?
The other thing is can anyone help me if I post the update?
Click to expand...
Click to collapse
Flash the downgrader from Alpharev (if necessary), then either use the appropriate RUU or restore your nandroid backup from recovery.

Pipusz said:
Flash the downgrader from Alpharev (if necessary), then either use the appropriate RUU or restore your nandroid backup from recovery.
Click to expand...
Click to collapse
If I had an RUU that would make it simple but all I have is an OTA update. And I saw somewhere that I can't really flash an OTA update with CWM. Also restoring the nandroid from recovery would look stock but it will still have root. I am just trying to get it back to factory stock rom and recovery with no root.
Looking at the files in the OTA there is a firmware.zip that has a new hboot, recovery and radio. But I am just not sure and where to start for creating a flashable zip with the OTA.
I uploaded the OTA I have if anyone can help me create a flashable zip or just tell me what to do. http://www.4shared.com/file/0b8ls5sf/OTA_Bravo_C_S_UTSTARCOM_WWE-Ge.html

Before you do that... ask yourself what could possibly be the most important question before you take the chance of breaking your phone: "What's the point?"

d-shade said:
...return my HTC Desire (CDMA) to stock...
Is there any way to convert the OTA update so it is a flashable zip I can use on CWM?
Click to expand...
Click to collapse
The request makes no sense..Flashing a rooted OTA doesnt return it to stock.

Droidzone said:
The request makes no sense..Flashing a rooted OTA doesnt return it to stock.
Click to expand...
Click to collapse
I don't want to flash a rooted OTA I have an OTA that my carrier pushed out for 2.2 update. I want to create a flashable zip with the OTA that I can use in CWM to remove root and restore the phone to stock and possibly the recovery as well.
bortak said:
Before you do that... ask yourself what could possibly be the most important question before you take the chance of breaking your phone: "What's the point?"
Click to expand...
Click to collapse
I am getting a new phone so I wanted to restore it back to stock.

d-shade said:
I don't want to flash a rooted OTA I have an OTA that my carrier pushed out for 2.2 update. I want to create a flashable zip with the OTA that I can use in CWM to remove root and restore the phone to stock and possibly the recovery as well.
I am getting a new phone so I wanted to restore it back to stock.
Click to expand...
Click to collapse
Then that is not the way to procede..You cant flash non-rooted OTAs on CWM..Well, you can, but it will just bungle up the whole setup.. What you can do is to flash an RUU and revert it to stock, then flash the OTA with the stock recovery to get it update

Droidzone said:
Then that is not the way to procede..You cant flash non-rooted OTAs on CWM..Well, you can, but it will just bungle up the whole setup.. What you can do is to flash an RUU and revert it to stock, then flash the OTA with the stock recovery to get it update
Click to expand...
Click to collapse
My carrier never distributed the RUU, which was why I was asking if there was any way to do it with the OTA. I can get my hands on a phone with a stock recovery, if there is any way to extract it from the phone using ADB

d-shade said:
My carrier never distributed the RUU, which was why I was asking if there was any way to do it with the OTA. I can get my hands on a phone with a stock recovery, if there is any way to extract it from the phone using ADB
Click to expand...
Click to collapse
No. That's impossible.. Well there was a way, if you'd thought about it earlier...to create a backup after a revolutionary S-off, then do whatever you want with the phone..and then finally when you wanted to restore, you could have restored the unrooted backup, then stock recovery and then finally Stock Hboot in that order... But now, there will no way other than to use an RUU of another carrier.

Droidzone said:
No. That's impossible.. Well there was a way, if you'd thought about it earlier...to create a backup after a revolutionary S-off, then do whatever you want with the phone..and then finally when you wanted to restore, you could have restored the unrooted backup, then stock recovery and then finally Stock Hboot in that order... But now, there will no way other than to use an RUU of another carrier.
Click to expand...
Click to collapse
Well I do have a unrooted backup but the only recovery that I have is the one in the OTA. Would it be possible to install that recovery and still be able to do an update using the OTA file?

Best course of action would be to restore your backup, followed by the following in order:
Prerequisites: S-off, Goldcard, An RUU confirmed to work with your device (Any region/WWE).
Steps:
Restore your backup with CWM. Ensure that it boots.
Extract recovery.img from the stock RUU (which should be working on your device normally)
In fastboot mode, and after going to the dir containing fastboot.exe (from sdk):
Code:
fastboot flash recovery recovery.img
fastboot reboot-recovery
Ensure that recovery works.
Then, using the hboot.img from the RUU,
Code:
fastboot flash hboot hboot.img
(the hboot extension may not be .img in the zip. Probably it's .nb0. Rename it)
Dont use OTA files at any point. You can update with it after successfully returning to stock with your backup.
Flashing hboot should be the last thing you do..Once the stock hboot makes you S-on, fastboot commands become inaccessible to you.

Thanks for the info, I think I am finally on track now. I was able to restore back to stock sense and was finally able to fix my mms issues(ro.cid problems after using unrevoked). Now I just need to figure out which ruu to take the recovery and hboot from.
I did find the alltel bravo_c ruu on shipped-roms.com hopfully that will work. Is there any sure way to know if the recovery will work or not on my phone?
I am with GCI its a local carrier in Alaska. I remember from my hero that alltel and my carrier had some similarities, along with cellsouth
Edit:
I just finished downloading the Alltel RUU and the HBOOT looks to be the same version. Also the Radio listed in the file name is the same as I currently have.
So I guess it is pretty safe to say that this recovery and hboot will work with my phone right?

The only sure way is to flash it. However make sure that the RUU is relatively new and has a version number greater than 1.2 and that you flash GSM one if you're on GSM, and CDMA if it's a CDMA phone.
bravoc=CDMA
bravo=GSM
Dont mix these...otherwise you'll end up with a black screen and a panic attack
There's another method to find if RUU is compatible, which is to open the zip and read the text file inside..See my Desire Unbricking guide and Goldcard FAQ link

Well I got it all back to stock, I still have s-off but everything else is stock and the latest FW my carrier pushed out.
I was having a problem using fastboot to flash the recovery so I just made a PB99IMG.zip to flash the recovery then everything else(hboot radio) everything is working fine thanks for all the help!

[Solved] Installing OTA with S-Off and Root

Update: Well, I took the plunge on my own, and everything worked fine. Flashed firmware.zip, went to stock recovery and flashed OTA, and voila, all good.
So I've bought an HTC device for the first time. I did S-Off and unlocked bootloader and rooted as well. Now, there's an OTA available (I have the Asia_India variant), and I wanted to ask just how would I go about updating.
Here's what I've surmised till now:
1. Revert changes to system partition or it will fail to update (I moved some system APKs, but I saved them for such a scenario.)
2. Flash Firmware.zip to get stock recovery back.
3. Install OTA normally from the notification.
However, I'm still not sure what else I'd need to do (unroot, using the option in SuperSU?), so was wondering if someone could help me out. I've made backups in Philz and TWRP recovery both just to be sure.
P.S.: I extracted the firmware.zip file from the OTA, and tried to open it, but it doesn't open in apps like WinRAR. Is that normal, with the file only flashable via fastboot?

Personally, I'd say remove root just incase it stops the OTA but others will say it doesn't matter so long as the rest of the system is 100% stock as HTC intended it

For OTA updates after having a custom recovery, just flash your ROM stock recovery (search XDA all are available) then run OTA as you normally would and then flash your custom recovery again (if you like to get root again). However personally I would not do this with S-ON device, probably it's better if you're S-OFF while doing this to avoid any problem.

I am also interested in this. What would be the risk if I do this with S-ON? Assume I flash the wrong stock recovery or do some other mistake, won't I still be able to flash my custom recovery back from fastboot and get everything back up and running?
Thanks to whom will answer. :good:

Black Antitoon said:
I am also interested in this. What would be the risk if I do this with S-ON? Assume I flash the wrong stock recovery or do some other mistake, won't I still be able to flash my custom recovery back from fastboot and get everything back up and running?
Thanks to whom will answer. :good:
Click to expand...
Click to collapse
So long as the phone still boots to fastboot, yes (although unlocking the boot loader will delete any backups so make sure you backup the backup to your PC before doing anything else!)

Thank you for your answer. As far as you know, being S-ON, is there really any kind of mistake one can do to brick the phone so that it doesn't even boot to fastboot?
Also, if my bootloader is already unlocked, no data wipe is going to happen again flashing a firmware/OTA in any predictable case, right?
Once again, thank you or anybody else who knows the answer.
By the way, are there any FAQs answering these questions? There are some FAQs here and there, but none seems to be very clear on these matters.

Black Antitoon said:
Thank you for your answer. As far as you know, being S-ON, is there really any kind of mistake one can do to brick the phone so that it doesn't even boot to fastboot?
Also, if my bootloader is already unlocked, no data wipe is going to happen again flashing a firmware/OTA in any predictable case, right?
Once again, thank you or anybody else who knows the answer.
By the way, are there any FAQs answering these questions? There are some FAQs here and there, but none seems to be very clear on these matters.
Click to expand...
Click to collapse
If you're S-ON there's not a lot you can do to brick the phone. You could wipe the ROM and have it not boot but you should always be able to get back to fastboot. This is where S-OFF is only handy to have if RUUs are about (it's the ONLY reason I am S-OFF, it's purely for a 'going back to stock' standpoint)
Yes, if the bootloader is already unlocked then you're good to go

[Q] Root without custom recovery?

I would like to root my HTC One M9 without installing TWRP or another custom recovery so that I can easily unroot and then take OTA updates. I have a developer M9 so my bootloader is already unlocked. I will eventually flash custom ROMs but at the moment, the stock firmware with Sense 7 is more than sufficient for me. Can anyone shed some light? I did find this http://www.how-to-root.club/2015/03/htc-one-m9-6891.html but I'm not sure how reliable it is since there's only a few comments.

theloneranger08 said:
I would like to root my HTC One M9 without installing TWRP or another custom recovery so that I can easily unroot and then take OTA updates. I have a developer M9 so my bootloader is already unlocked. I will eventually flash custom ROMs but at the moment, the stock firmware with Sense 7 is more than sufficient for me. Can anyone shed some light? I did find this http://www.how-to-root.club/2015/03/htc-one-m9-6891.html but I'm not sure how reliable it is since there's only a few comments.
Click to expand...
Click to collapse
"I could be wrong here and let me know if I am" it doesn't work that way with the m9. That site is bogus anyways, could you not tell by the video? Anyhow, even if you where to root it, there is no way to "simply" unroot it and take ota. There is new security on the m9 dealing with updates. Ota will not work if your software is or has been modified in any way, or if you have super cid. The common way for people to get OTA with the m9 is flash twrp, make a backup BEFORE rooting, flash newest supersu beta inside twrp, profit. When ota comes, go back to twrp, restore non rooted backup, flash stock recovery, take ota. IMO this is all a waste of time with an htc, just bite the bullet and spend $25 on soff and you don't have to worry about ota, you can flash firmware all day long before htc even releases it. Just flash a stock rooted rom like maximus if you don't want a lot of tweaks.
Your boot loader will say modified after flashing twrp, and will still say modified after restoring back to your stock backup. The "modified" boot loader does not affect ota, but if it annoys you like it does me, the only way to get rid of it at this time is to have soff and flash stock RUU in exe or sdcard mode. fastboot oem rebootRUU will not remove boot loader modified
edit.. there is now a way to remove modified status without flashing rom

an0ther said:
"I could be wrong here and let me know if I am" it doesn't work that way with the m9. That site is bogus anyways, could you not tell by the video? Anyhow, even if you where to root it, there is no way to "simply" unroot it and take ota. There is new security on the m9 dealing with updates. Ota will not work if your software is or has been modified in any way, or if you have super cid. The common way for people to get OTA with the m9 is flash twrp, make a backup BEFORE rooting, flash newest supersu beta inside twrp, profit. When ota comes, go back to twrp, restore non rooted backup, flash stock recovery, take ota. IMO this is all a waste of time with an htc, just bite the bullet and spend $25 on soff and you don't have to worry about ota, you can flash firmware all day long before htc even releases it. Just flash a stock rooted rom like maximus if you don't want a lot of tweaks.
Your boot loader will say modified after flashing twrp, and will still say modified after restoring back to your stock backup. The "modified" boot loader does not affect ota, but if it annoys you like it does me, the only way to get rid of it at this time is to have soff and flash stock RUU in exe or sdcard mode. fastboot oem rebootRUU will not remove boot loader modified
edit.. there is now a way to remove modified status without flashing rom
Click to expand...
Click to collapse
Thanks for all of the info. I wish simply rooting your phone wasn't such a pain. I guess I'll just flash TWRP, make a backup of my phone, and then root it and then if I need to do an OTA I can just restore the backup and flash the stock recovery. I found this download site for the recovery. I'm assuming I'd pick developer and then recovery. Do I use the signed one? What happens if I flash the wrong recovery? https://www.androidfilehost.com/?w=files&flid=28830

Also, if I S OFF you said I can install OTA updates? So I can install them even if I have a custom recovery and root access?

theloneranger08 said:
Also, if I S OFF you said I can install OTA updates? So I can install them even if I have a custom recovery and root access?
Click to expand...
Click to collapse
Not ota, but you can flash firmware without doing anything. So you run a stockish rom like maximus and he releases his own OTA's, then you can flash official firmware to keep up with it, and if you get tired of that method, you can always ruu and go back to completely stock.

an0ther said:
Not ota, but you can flash firmware without doing anything. So you run a stockish rom like maximus and he releases his own OTA's, then you can flash official firmware to keep up with it, and if you get tired of that method, you can always ruu and go back to completely stock.
Click to expand...
Click to collapse
So I bit the bullet and installed TWRP, did a Nandroid backup, and then rooted my phone. Now I'm trying to determine whether I want to S-Off my phone. I know that I'd need to RUU and return to stock to flash firmware if I'm S-On, but if I flash a rom that is continually updated, then will I miss any of the features of new firmware released by HTC? I guess my question is, if a dev. updates a rom to reflect the newest firmware from HTC, how does that actually work because from what I've read, it doesn't actually touch the firmware of the phone? So would there be things that HTC can improve that the rom cannot?

theloneranger08 said:
So I bit the bullet and installed TWRP, did a Nandroid backup, and then rooted my phone. Now I'm trying to determine whether I want to S-Off my phone. I know that I'd need to RUU and return to stock to flash firmware if I'm S-On, but if I flash a rom that is continually updated, then will I miss any of the features of new firmware released by HTC? I guess my question is, if a dev. updates a rom to reflect the newest firmware from HTC, how does that actually work because from what I've read, it doesn't actually touch the firmware of the phone? So would there be things that HTC can improve that the rom cannot?
Click to expand...
Click to collapse
Correct. Roms do not upgrade firmware. In the future you will need to upgrade firmware when wifi/camera/touchscreen/etc improvements are implemented into firmware. Having soff, you can simply flash just the firmware and not worry about software. Without soff, you have to revert back to stock and take ota or use new firmware RUU. Soff is a must on HTC and is honestly the only reason I didn't buy an s6. Ive had the m7/m8/m9 and the flexibility of rooting and firmware etc is unlike any other.

an0ther said:
Correct. Roms do not upgrade firmware. In the future you will need to upgrade firmware when wifi/camera/touchscreen/etc improvements are implemented into firmware. Having soff, you can simply flash just the firmware and not worry about software. Without soff, you have to revert back to stock and take ota or use new firmware RUU. Soff is a must on HTC and is honestly the only reason I didn't buy an s6. Ive had the m7/m8/m9 and the flexibility of rooting and firmware etc is unlike any other.
Click to expand...
Click to collapse
Ok great and I can flash firmware regardless of what rom I'm running?

theloneranger08 said:
Ok great and I can flash firmware regardless of what rom I'm running?
Click to expand...
Click to collapse
Correct. It doesn't have to be a perfect match, just in the same base. Right now your current firmware is fine, but most people swap to the newest developer with no red text. If you are new to htc and flashing firmware read instructions carefully or ask me. You need super cid or matching cid to flash firmware that isn't supported by your carrier variant. Everyone has to learn and these phones are near impossible to hard brick as long as you can read. Never flash cdma firmware on gsm phone, never run ruu for your phone if MID doesn't match, never turn s-on back on, but if you have to make sure you are NOT super cid or have unsigned firmware "no red text firmware" Never ever ever unzip a signed firmware file and edit it and zip it back up to flash unless you decrypt it and know what you are doing. Get an 32 gig or less sd card. Feel free to ask me any questions.

an0ther said:
Correct. It doesn't have to be a perfect match, just in the same base. Right now your current firmware is fine, but most people swap to the newest developer with no red text. If you are new to htc and flashing firmware read instructions carefully or ask me. You need super cid or matching cid to flash firmware that isn't supported by your carrier variant. Everyone has to learn and these phones are near impossible to hard brick as long as you can read. Never flash cdma firmware on gsm phone, never run ruu for your phone if MID doesn't match, never turn s-on back on, but if you have to make sure you are NOT super cid or have unsigned firmware "no red text firmware" Never ever ever unzip a signed firmware file and edit it and zip it back up to flash unless you decrypt it and know what you are doing. Get an 32 gig or less sd card. Feel free to ask me any questions.
Click to expand...
Click to collapse
Awesome, thanks I really appreciate it. I'll definitely let you know if I have any questions.

theloneranger08 said:
So I bit the bullet and installed TWRP, did a Nandroid backup, and then rooted my phone. Now I'm trying to determine whether I want to S-Off my phone. I know that I'd need to RUU and return to stock to flash firmware if I'm S-On, but if I flash a rom that is continually updated, then will I miss any of the features of new firmware released by HTC? I guess my question is, if a dev. updates a rom to reflect the newest firmware from HTC, how does that actually work because from what I've read, it doesn't actually touch the firmware of the phone? So would there be things that HTC can improve that the rom cannot?
Click to expand...
Click to collapse
Check it out this http://www.bestandroidrootedapps.com/how-to-root-htc-one-m9-and-also-have-custom-recovery-installed-on-it/

[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

Unroot Euro (EE) HTC M9 for OTA update?

Hi all,
I'm really out of touch with the scene so please go easy on me.
I rooted my European M9 a while ago and have TWRP recovery installed, S-On, Software version is 2.10.61.6, Baseband is 01.01_U11440601_83.06.50709G_F
The other day I got the Android 6.0 OTA update which I was not expecting as I was under the impression that since rooting (as has been the case with all my other Androids) OTAs would be disabled.
Just to see what would happen I accepted it, the device rebooted and of course loaded TWRP. So that's a no go.
Could someone please tell me what the best way of updating without having to lose all my data is?

S-off is the best and only way to save your data. Otherwise you need to go through the complex process of getting it back to official status.
Sent from my HTC One M9 using Tapatalk

OK, what's the best way to get S-off? I see there's a $25 app some people are using, is there an alternative to that?

No alternative. Sunshine works great but be sure to read twice and press the button once..
Sent from my HTC One M9 using Tapatalk

OK, thanks for the advice. So if I get S-OFF via Sunshine, what's next?

I have a full backup of my system before I rooted, can I not just flash back the stock recovery and then proceed with the OTA?
If not and I need to be S-OFF still then fine, just trying to understand why that is.
Thanks!

S-off just makes life easier for being able to run unsigned code. Like, unsigned roms will install.
If you flash the stock backup you still need to obtain official status to take the ota. This is known to bugger your phone if you get it wrong. S-off solves the buggered phones issue..
Sent from my HTC One M9 using Tapatalk

OK, thanks for clarifying the info.
I'm now rooted, unlocked and s-off.
The backup of my recovery partition is "recovery.emmc.win", what's the process to flash that back to the phone and continue from there so I can accept the OTA?
Another thing - It's possible that I accepted another OTA since making that backup as I'm now on 2.10.61.6. I can't find a stock recovery for that version so does this affect the process?

Bump! Can anyone help me out here with the correct guide to follow please? Really don't want to mess this up!

Hi JonnyG1980, I am happy to help you but don't suppose you could upload your backup as I have been looking for it for ages?
Sent from my HTC One M9 using Tapatalk

AirwolfUK said:
Hi JonnyG1980, I am happy to help you but don't suppose you could upload your backup as I have been looking for it for ages?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
My stock recovery backup? I'm not sure which version that is taken from as I'm pretty sure I accepted an OTA to get to the version I am on now.

Download the orange RUU.zip from here and place on your sdcard rename to 0PJAIMG.zip boot into download mode and it'll prompt you to flash make sure you backup all your data etc beforehand as this will wipe your device

liam_davenport said:
Download the orange RUU.zip from here and place on your sdcard rename to 0PJAIMG.zip boot into download mode and it'll prompt you to flash make sure you backup all your data etc beforehand as this will wipe your device
Click to expand...
Click to collapse
I'm trying to update WITHOUT wiping my device. Hence going S-OFF.

liam_davenport said:
Download the orange RUU.zip from here and place on your sdcard rename to 0PJAIMG.zip boot into download mode and it'll prompt you to flash make sure you backup all your data etc beforehand as this will wipe your device
Click to expand...
Click to collapse
Hi Liam, where / what RUU?
I am trying to get back to some release of stock to get the mm ota.
I think I have three choices?
1. Restore my 1.32.16.x backup and take the 2.10.61.x again then on to MM but I need stock 1.32.61.x recovery
2. Restore someone else's 2.10.61.x backup?
3. S-off
So if anyone has either 1 or 2 I would be very grateful.
Thanks -
Sent from my HTC One M9 using Tapatalk

try to follow this guide:
http://forum.xda-developers.com/one-m9/help/htc-one-m9-3-35-401-12-ruu-installer-t3318517

xyqtt said:
try to follow this guide:
http://forum.xda-developers.com/one-m9/help/htc-one-m9-3-35-401-12-ruu-installer-t3318517
Click to expand...
Click to collapse
Yes but I need the specific RUU first!
Sent from my HTC One M9 using Tapatalk

Sorry if I'm repeating myself, but could anyone explain the benefits of S=Off again to me?
I've tried various RUU to update my phone and all have rejected the CID (ORANG001) so I've had no option than to use one with a matching base (x.x.61.x) to my existing rom. I was under the impression that the CID was made irrelevant or could be changed, but I can find no reference on how to go about this.
As I couldn't find my current RUU, or the latest MM release I had to go with 1.32.61.15, has this downgrade been permitted by being S-Off?

If you didn't change your CID then being s-off enabled you to downgrade.
As a reference, I am still s-on and cannot downgrade to 1.32.x from 2.10.x
Sent from my HTC One M9 using Tapatalk

AirwolfUK said:
If you didn't change your CID then being s-off enabled you to downgrade.
As a reference, I am still s-on and cannot downgrade to 1.32.x from 2.10.x
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Thanks, I think I get it now. Now just the question of whether to re-root or not remains.

Hi johnny did you achieve s-off? If so, how? Also, did you get to download and install the ota?