Develop Bugs

OTA Update on a rooted M8

hello, i need to verify something with you guys.
Currently i'm using an HTC One M8 rooted and running on a stock rom, and TWRP as a recovery, can i still have OTA updates in my phone even if I'm on root and TWRP as a recovery. also one thing how can go remove TWRP recovery or revert to HTC recovery
many thanks

I also am curious about this topic

snap213 said:
hello, i need to verify something with you guys.
Currently i'm using an HTC One M8 rooted and running on a stock rom, and TWRP as a recovery, can i still have OTA updates in my phone even if I'm on root and TWRP as a recovery. also one thing how can go remove TWRP recovery or revert to HTC recovery
many thanks
Click to expand...
Click to collapse
1. Download the stock recovery for your device from the recovery thread
2. Flash it through fastboot (as you did TWRP)
3. Apply the OTA
4. Reflash TWRP
5. Re-root the phone

guess i'm stuck with my rooted phone then, i rooted my phone using Hansoon2000 All-In-One-Kit
and i can't find my stock rom, my software number is 1.54.707.7

snap213 said:
guess i'm stuck with my rooted phone then, i rooted my phone using Hansoon2000 All-In-One-Kit
and i can't find my stock rom, my software number is 1.54.707.7
Click to expand...
Click to collapse
Not stock rom...stock recovery

Look at the bottom of the first post of mr_hofs thread in the general section here: http://forum.xda-developers.com/showthread.php?t=2701376
You'll find your stock recovery there ?
Hope that helps.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
---------- Post added at 02:48 PM ---------- Previous post was at 02:46 PM ----------
spikeydoo2006 said:
Look at the bottom of the first post of mr_hofs thread in the general section here: http://forum.xda-developers.com/showthread.php?t=2701376 (under the nandroid backups section)
You'll find your stock recovery there ?
Hope that helps.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my HTC One_M8 using XDA Premium 4 mobile app

Remember (as said a million times already in multiple threads) - to flash an OTA you CANNOT have changed anything in the original system (fonts, Xposed mods, removing system apps, ANYTHING) otherwise the OTA WILL FAIL

i've browse mr.hofs thread and i've seen lots of stock recoveries. I don't know which stock recovery will I use.
I tried to match it using my software number 1.54.707.7 but there is none. or should i just try the closer to that version?
also another question? can i flash my stock recovery using Hasoon2000's AIO Toolkit? i see here on the left box it's says your own recovery.
thanks.

snap213 said:
i've browse mr.hofs thread and i've seen lots of stock recoveries. I don't know which stock recovery will I use.
I tried to match it using my software number 1.54.707.7 but there is none. or should i just try the closer to that version?
also another question? can i flash my stock recovery using Hasoon2000's AIO Toolkit? i see here on the left box it's says your own recovery.
thanks.
Click to expand...
Click to collapse
here is my recovery backup from 1.54.707.7. https://www.dropbox.com/s/p2ht9dxns3ggcyk/recovery.img
Can you backup your radio.img for me? I forgot to backup when i convert my phone to GPE.

to any Hasoons2000's users out there?
also another question? can i flash my stock recovery using Hasoon2000's AIO Toolkit? i see here on the left box it's says your own recovery.
---
or can anyone give me a much more detailed or step by step instructions, i know i' cant post in HTC development forum.

snap213 said:
to any Hasoons2000's users out there?
also another question? can i flash my stock recovery using Hasoon2000's AIO Toolkit? i see here on the left box it's says your own recovery.
---
or can anyone give me a much more detailed or step by step instructions, i know i' cant post in HTC development forum.
Click to expand...
Click to collapse
Yes, you can! I did it exactly that way - and after OTA update reflashed TWRP and rerouted that way. Its a 4 minute job.

snap213 said:
to any Hasoons2000's users out there?
also another question? can i flash my stock recovery using Hasoon2000's AIO Toolkit? i see here on the left box it's says your own recovery.
---
or can anyone give me a much more detailed or step by step instructions, i know i' cant post in HTC development forum.
Click to expand...
Click to collapse
Learn to do it yourself, relying on toolkits is a false economy as if anything goes wrong you'll have no idea how to fix it...

EddyOS said:
Remember (as said a million times already in multiple threads) - to flash an OTA you CANNOT have changed anything in the original system (fonts, Xposed mods, removing system apps, ANYTHING) otherwise the OTA WILL FAIL
Click to expand...
Click to collapse
Yes, that has been mentioned quite a few times in various threads..However one question that pops up now is:
Lets says I did make changes to the system files by removing a system app or using xposed mods (but not flashing any custom roms). But these changes were made AFTER taking a backup of (unchanged) stock recovery. Will OTA still fail if i now flash stock recovery and then ota update? I am guessing it should work as i am bringing the phone back to stock status.
Also what if i do not flash any custom recovery, I just boot into it to take a backup and remain in stock rom. In that case, for an OTA update, do i still need to first flash stock recovery if I have not made changes to sys files?
Finally when you say OTA fail, does that mean there is a chance I will brick/soft brick my phone?or is it just an error message. I ask because in case i make changes to sys and then forget about it or do not realise its consequence for an OTA update, its better I know now what I am getting into.

anjaan said:
Yes, that has been mentioned quite a few times in various threads..However one question that pops up now is:
Lets says I did make changes to the system files by removing a system app or using xposed mods (but not flashing any custom roms). But these changes were made AFTER taking a backup of (unchanged) stock recovery. Will OTA still fail if i now flash stock recovery and then ota update? I am guessing it should work as i am bringing the phone back to stock status.
Also what if i do not flash any custom recovery, I just boot into it to take a backup and remain in stock rom. In that case, for an OTA update, do i still need to first flash stock recovery if I have not made changes to sys files?
Finally when you say OTA fail, does that mean there is a chance I will brick/soft brick my phone?or is it just an error message. I ask because in case i make changes to sys and then forget about it or do not realise its consequence for an OTA update, its better I know now what I am getting into.
Click to expand...
Click to collapse
The OTA requires a 100% stock running Android build, so if you have removed any system apps it will just fail and reboot to the ROM you're running at the moment (so you should be safe). Basically, if the /system partition on the phone is ANY way different from how it was when you first bought it the OTA will fail
For example, other than S-OFF my phone is exactly how I received it, therefore the new OTA update installed successfully. If I had removed one system app (e.g. Hangouts), it would fail as it's looking for it and if it can't find it it'll just reboot

i still have my S-OFF here in my HTC, and i haven't removed any system apps. i'll try this later this week.
i just needed my root because of setCPU nothing else.
--- anyway, since we're all learning here.
we'll for example, OTA has been updated and all goes well. now that i have to reflash my recovery to TWRP.
big question again, how do i save my stock recovery using TWRP?

snap213 said:
i still have my S-OFF here in my HTC, and i haven't removed any system apps. i'll try this later this week.
i just needed my root because of setCPU nothing else.
--- anyway, since we're all learning here.
we'll for example, OTA has been updated and all goes well. now that i have to reflash my recovery to TWRP.
big question again, how do i save my stock recovery using TWRP?
Click to expand...
Click to collapse
If you're now on 1.54.401.10, you can manually extract it from the firmware package I uploaded HERE

I installed the OTA yesterday and had a different experience. I am with the stock rooted ROM, but I installed Xposed with some modules and the swipe to sleep and no write protection kernel modules. Also, unlocking the bootloader also ate my calculator and torch apps, and I reinstalled them as user apps instead of system apps.
Well, after flashing the stock recovery, the OTA worked like a charm. I applied it manually from the stock recovery, but I don't think this makes a difference. I had to re-root afterwards, but all the rest was preserved.
I am S-OFF though. Is that the reason why it bypassed some security checks?

Black Antitoon said:
I installed the OTA yesterday and had a different experience. I am with the stock rooted ROM, but I installed Xposed with some modules and the swipe to sleep and no write protection kernel modules. Also, unlocking the bootloader also ate my calculator and torch apps, and I reinstalled them as user apps instead of system apps.
Well, after flashing the stock recovery, the OTA worked like a charm. I applied it manually from the stock recovery, but I don't think this makes a difference. I had to re-root afterwards, but all the rest was preserved.
I am S-OFF though. Is that the reason why it bypassed some security checks?
Click to expand...
Click to collapse
I can see the apps that were removed during unlocking still working if installed as user apps as they're still on the /data partition. If they weren't there at all then it'd probably fail. Surprised that it worked with Xposed installed, but that's also a user app so it could very well work - logically it makes sense.
As a rule of thumb I'd only apply an OTA on a 100% stock system, that way you know it'll all be fine

[Q] Rooted phone and want to install OTA update

The OTA 4.4.3 update is now available for my phone, but I've rooted it, and I've read the horror stories so I'm not going to blunder blindly into this
My rooting experience went a little poorly - I thought I was doing the right thing by backing everything up on the phone first, using Helium. Unfortunately Helium simply did the backup onto the internal storage itself, so it all got wiped during the process anyway.
Anyway, I got over that, but now I want to install the OTA 4.4.3 update. So here's the things I've done which I think are relevant:
1. Installed TWRP recovery, as required for rooting
2. Have flashed the SuperSU program for root
3. AFAIK I'm still on "stock" - I haven't gone out to find any special roms etc
4. Had to reinstall the calc and flashlight apps as they were missing after the whole exercise (so many I'm not on stock, or they would be there?)
5. I have installed Xposed Framework and the Sense 6 tweaks and GravityBox apps.
6. I tried to uninstall some system apps (Facebook, Twitter, things I don't use) with a root uninstaller program, but every time the phone reboots they re-appear, so I think I need s-off to do that properly?
7. I've 'Disabled' the weibo app through the standard app info button
I understand I have to go back to the "stock recovery" in order to do the OTA update, but is there anything else in the above list that I need to do anything about?
Will going back to the stock recovery mean I lose all of the content on my device again, and have to restore it from a backup? If I use the HTC backup app to back up all my phone data on the rooted 4.4.2 I'm running, can this then be restored onto the 4.4.3 version?
Also is the problem I mention in #6 solved by going s-off?

Lanthanide said:
The OTA 4.4.3 update is now available for my phone, but I've rooted it, and I've read the horror stories so I'm not going to blunder blindly into this
My rooting experience went a little poorly - I thought I was doing the right thing by backing everything up on the phone first, using Helium. Unfortunately Helium simply did the backup onto the internal storage itself, so it all got wiped during the process anyway.
Anyway, I got over that, but now I want to install the OTA 4.4.3 update. So here's the things I've done which I think are relevant:
1. Installed TWRP recovery, as required for rooting
2. Have flashed the SuperSU program for root
3. AFAIK I'm still on "stock" - I haven't gone out to find any special roms etc
4. Had to reinstall the calc and flashlight apps as they were missing after the whole exercise (so many I'm not on stock, or they would be there?)
5. I have installed Xposed Framework and the Sense 6 tweaks and GravityBox apps.
6. I tried to uninstall some system apps (Facebook, Twitter, things I don't use) with a root uninstaller program, but every time the phone reboots they re-appear, so I think I need s-off to do that properly?
7. I've 'Disabled' the weibo app through the standard app info button
I understand I have to go back to the "stock recovery" in order to do the OTA update, but is there anything else in the above list that I need to do anything about?
Will going back to the stock recovery mean I lose all of the content on my device again, and have to restore it from a backup? If I use the HTC backup app to back up all my phone data on the rooted 4.4.2 I'm running, can this then be restored onto the 4.4.3 version?
Also is the problem I mention in #6 solved by going s-off?
Click to expand...
Click to collapse
Flashing back stock recovery you won't loose anything. This just happens during the unlock process if done with HTCDev.
Good that you are not S-Off and FB, Twitter and so on are still installed, as otherwise you wouldn't be abled to perform the OTA. An OTA is only going to run if the whole system is unchanged.
Only thing that's quite likely going to happen, is that you root is lost after the OTA. Tthus you would have to flash TWRP and the SuperSu again, after the OTA.

HTCNerdYoda said:
Flashing back stock recovery you won't loose anything. This just happens during the unlock process if done with HTCDev.
Good that you are not S-Off and FB, Twitter and so on are still installed, as otherwise you wouldn't be abled to perform the OTA. An OTA is only going to run if the whole system is unchanged.
Only thing that's quite likely going to happen, is that you root is lost after the OTA. Tthus you would have to flash TWRP and the SuperSu again, after the OTA.
Click to expand...
Click to collapse
I thought it didn't matter if you were s/off or not, so long as recovery and OS were stock and CID matched (or were SuperCID).

bruce7373 said:
I thought it didn't matter if you were s/off or not, so long as recovery and OS were stock and CID matched (or were SuperCID).
Click to expand...
Click to collapse
It doesn't matter in general. But it matters in case that you used S-Off to uninstall system APPs Thus an OTA wouldn't succeed.
That's what I wanted to say in my post above
Sent from my HTC One_M8 using XDA Free mobile app

Wow found my answer already. Just to confirm. I'm in the same situation. Rooted. Installed twrp and su. Went to s-off with firewater but got the whelp message.
Got the OTA update in this morning. Tried installing it, went to my recovery so I tried to install it. It failed of course. Phone is still ok.
I'm just making sure I'll do this ok. Gotta go back to original recovery then install it or am I just better off going to a custom rom?
On my vivid, I used paranoid when it was available, used pacman for a bit. Also used the CyanogenMod. I know recommendation shouldn't be made but i know on my vivid there were lots of issues since there wasn't a specific team rolling out the roms but someone porting them from the specific team. Is there a team dedicated to this phone? If so are their roms leaps ahead of the ones ported over? Just looking at the downloads you can tell which one is the most popular, that doesn't always mean they are the best.
Thanks for any advice.

Yuskow said:
Wow found my answer already. Just to confirm. I'm in the same situation. Rooted. Installed twrp and su. Went to s-off with firewater but got the whelp message.
Got the OTA update in this morning. Tried installing it, went to my recovery so I tried to install it. It failed of course. Phone is still ok.
I'm just making sure I'll do this ok. Gotta go back to original recovery then install it or am I just better off going to a custom rom?
Click to expand...
Click to collapse
I would revert to stock recovery and get me this OTA. And you need a 2.22.xxx FW for some of the custom ROMs currently available.
It's the fastest way to update your firmware anyway
Alternatively you could try to perform an S-Off using SunShine and paying 25$ for it, as I did to flash the newest FW.

HTCNerdYoda said:
I would revert to stock recovery and get me this OTA. And you need a 2.22.xxx FW for some of the custom ROMs currently available.
It's the fastest way to update your firmware anyway
Alternatively you could try to perform an S-Off using SunShine and paying 25$ for it, as I did to flash the newest FW.
Click to expand...
Click to collapse
Got my cid as bm 001
so i got the nandroid backup here http://forum.xda-developers.com/showthread.php?t=2701376
now i just do a restore under twrp?
is the s-off really worth it?

Yuskow said:
Got my cid as bm 001
so i got the nandroid backup here http://forum.xda-developers.com/showthread.php?t=2701376
now i just do a restore under twrp?
Click to expand...
Click to collapse
As long as the ROM you are using is stock and you only routetd, you just need to flash stock recovery for the OTA to succeed.
Yuskow said:
is the s-off really worth it?
Click to expand...
Click to collapse
Well from my point of view: yes it is. Needed S-Off to debrand my One M8 and change CID to a WWE one. Well and additionally you can do a lot more if the security flag is on off (never without propper reading before doing it of course).

Yuskow said:
Wow found my answer already. Just to confirm. I'm in the same situation. Rooted. Installed twrp and su. Went to s-off with firewater but got the whelp message.
Got the OTA update in this morning. Tried installing it, went to my recovery so I tried to install it. It failed of course. Phone is still ok.
I'm just making sure I'll do this ok. Gotta go back to original recovery then install it or am I just better off going to a custom rom?
On my vivid, I used paranoid when it was available, used pacman for a bit. Also used the CyanogenMod. I know recommendation shouldn't be made but i know on my vivid there were lots of issues since there wasn't a specific team rolling out the roms but someone porting them from the specific team. Is there a team dedicated to this phone? If so are their roms leaps ahead of the ones ported over? Just looking at the downloads you can tell which one is the most popular, that doesn't always mean they are the best.
Thanks for any advice.
Click to expand...
Click to collapse
I had the Vivid as well and ended up with a 4.4.2 ROM which seemed to be the most current that was available at the time, but can't remember the name or the dev.
As for the M8, I've been on ARHD almost exclusively and think it's one of the best ROMs out there. I've tried Viper, MaximusHD, Renovate also, but always come back to ARHD.
http://forum.xda-developers.com/showthread.php?t=2694917
---------- Post added at 07:40 AM ---------- Previous post was at 07:33 AM ----------
HTCNerdYoda said:
As long as the ROM you are using is stock and you only routetd, you just need to flash stock recovery for the OTA to succeed.
Well from my point of view: yes it is. Needed S-Off to debrand my One M8 and change CID to a WWE one. Well and additionally you can do a lot more if the security flag is on off (never without propper reading before doing it of course).
Click to expand...
Click to collapse
I have the WWE edition and am currently with ATT. I'm considering their new update mainly to see if the new firmware/radio will give me better LTE speeds. The fw is 2.23 based. Will that be a problem if or when I return to ARHD which is on 2.22?

bruce7373 said:
I have the WWE edition and am currently with ATT. I'm considering their new update mainly to see if the new firmware/radio will give me better LTE speeds. The fw is 2.23 based. Will that be a problem if or when I return to ARHD which is on 2.22?
Click to expand...
Click to collapse
That's a really good question. Regarding ViperOne I could tell that running 1.8.0 (which was on 1.54.xx base) with 2.22.xxx FW worked flawlessly. So I would guess this should work just fine.
At least it's worth a try. Maybe better ask in the ROM thread.

Used arhd on my vivid for a bit. Must say it was an ok rom but lots of issues in general with all new roms on the vivid. Hardware too outdated. Maybe I'll give it a shot. Really leaning to a de-senced one.

HTCNerdYoda said:
Flashing back stock recovery you won't loose anything. This just happens during the unlock process if done with HTCDev.
Good that you are not S-Off and FB, Twitter and so on are still installed, as otherwise you wouldn't be abled to perform the OTA. An OTA is only going to run if the whole system is unchanged.
Only thing that's quite likely going to happen, is that you root is lost after the OTA. Tthus you would have to flash TWRP and the SuperSu again, after the OTA.
Click to expand...
Click to collapse
Ok, that's encouraging.
My CID is HTC__621 although I don't think I need that for just flashing back to stock recovery. My version is 1.54.709.12, so I downloaded the matching recovery from here http://forum.xda-developers.com/showthread.php?t=2701376 and flashed it. I confirmed that the stock recovery was installed by booting to it and getting the red triangle etc.
Then I downloaded the OTA upgrade and told it to install. I didn't watch the installation progress, but eventually it went to the red triangle screen and finally rebooted. But I'm still on 1.54.709.12, so I take that to mean the OTA failed. When I go to system update, it checks and finds one available and offers to download it again, which I haven't done.
I'm wondering if 'disabling' the weibo program could have caused the update to fail? Or possibly I *did* actually uninstall a stock program or two that I mentioned at #6 and that's what's preventing the update?
Anyway, I made a complete nandroid backup on the external SD card before I flashed the recovery. It seems like the easiest approach now would be to flash a stock ROM for HTC__621 then do the OTA upgrade. After that, I could restore my HTC sync (the app) backup from the cloud, but if I wasn't happy with that I could recover the data portion of my nandroid backup?

Lanthanide said:
Ok, that's encouraging.
Anyway, I made a complete nandroid backup on the external SD card before I flashed the recovery. It seems like the easiest approach now would be to flash a stock ROM for HTC__621 then do the OTA upgrade. After that, I could restore my HTC sync (the app) backup from the cloud, but if I wasn't happy with that I could recover the data portion of my nandroid backup?
Click to expand...
Click to collapse
In fact you are right. The OTA fails as something on the system has been changed that's critical to the OTA.
So I would back up the data on the phone I need, download a stock nandroid backup for your CID, install with twrp, re-flash stock recovery and perform the OTA again.

HTCNerdYoda said:
In fact you are right. The OTA fails as something on the system has been changed that's critical to the OTA.
So I would back up the data on the phone I need, download a stock nandroid backup for your CID, install with twrp, re-flash stock recovery and perform the OTA again.
Click to expand...
Click to collapse
Ok, so I put on a stock nadroid backup for HTC__621, changed to stock recovery, but the OTA update is still failing at around the 30% mark.
Actually I've just noticed that the stock ROM I put on doesn't have the calc or flashlight apps, but when I originally bought the phone they were on there. I had subsequently installed them using the apps on this thread here: http://forum.xda-developers.com/showthread.php?t=2699906
But maybe that is what is preventing me from doing the OTA now?
Edit: Right, so doing some more reading, it seems that HTC included these 'stock' apps in the /data directory instead of /system, so when doing the HTCDev install, they get wiped. But there was a note in that thread saying that for the One M7, they would actually do a hash of those apps too and if they weren't there the update would fail.
Someone linked to this thread http://forum.xda-developers.com/showthread.php?t=2703759 which says the APKs in the first one were from the M7, and these are from M8, and it also included another one called Seven Digital (yet another bloatware app I don't care about, hence why I didn't notice it was gone). Anyway I installed those 3 apps, but the OTA update still fails at around the 30% mark. I notice that the thread says preload APKs for 1.54.401.5, but my phone is running 1.54.709.12, so if they really are doing hashing for all of these apps, the update might be expectly a slightly different version and therefore fail the hash check?

Resolved!
Right, posting as new post because I solved it!
I searched through the collection thread and luckily found someone else who has HTC__621 who wanted to do the 4.4.3 upgrade as well. ckpv5 stepped in to lend a hand with this post: http://forum.xda-developers.com/showpost.php?p=54598052&postcount=1514
The TWRP stock ROM he posted there includes the flashlight and calculator app, as well as another one that looks like it was missing - WeChat. So now the OTA update has applied as expected. :highfive
I'll suggest Mr Hofs remove the existing nandroid backup for HTC__621 that he has there because it isn't complete.

Weirdly after all that was done, now that I have 4.4.3, the calc and flashlight apps are again missing; no sign of WeChat either. So I'll probably have to go through this whole performance again next time I want to OTA update?
Edit: More findings. In installing Xposed Framework on my phone, it can't do the 'classical' install because of S-on, instead it flashes it through recovery. So I suspect this could have been preventing the OTA update as well.

Lanthanide said:
Weirdly after all that was done, now that I have 4.4.3, the calc and flashlight apps are again missing; no sign of WeChat either. So I'll probably have to go through this whole performance again next time I want to OTA update?
Click to expand...
Click to collapse
Because you relocked bootloader when you did the OTA update. So those files were deleted when you re-unlocked bootloader after OTA done.
There's a TWRP backup for the latest here : http://forum.xda-developers.com/showpost.php?p=55097943&postcount=1744
Just a note : there is no need to relock bootloader to do OTA update.

ckpv5 said:
Because you relocked bootloader when you did the OTA update. So those files were deleted when you re-unlocked bootloader after OTA done.
There's a TWRP backup for the latest here : http://forum.xda-developers.com/showpost.php?p=55097943&postcount=1744
Just a note : there is no need to relock bootloader to do OTA update.
Click to expand...
Click to collapse
Ok, at least there's an explanation for what happened, but I didn't at any point explicitly lock the bootloader. All I did was:
1. Flash TWRP recovery
2. Flash the ROM you provided
3. Boot the phone, going through the setup stuff to configure wifi etc
4. Booted to fastboot and flashed to stock recovery
5. Rebooted phone, downloaded and installed OTA update
6. Booted to fastboot and re-flashed TWRP, ran nandroid backup and then installed superSU when offered
At what point would the locking of the bootloader have occurred?

Lanthanide said:
At what point would the locking of the bootloader have occurred?
Click to expand...
Click to collapse
Re-unlocking bootloader is one scenario that may happen that remove the preload folder.
Restoring an old backup which doesn't have the preload folder is another scenario.
Anyway that is easily can be fix by pushing the preload folder from OTA zip to /data
then make a new backup for future OTA

ckpv5 said:
Re-unlocking bootloader is one scenario that may happen that remove the preload folder.
Restoring an old backup which doesn't have the preload folder is another scenario.
Anyway that is easily can be fix by pushing the preload folder from OTA zip to /data
then make a new backup for future OTA
Click to expand...
Click to collapse
Ok, well like I said, I didn't explicitly choose the lock the bootloader at any point, and the nandroid backup that you created *did* have the extra apps in there (I confirmed their presence at step 3 in my sequence).
Note that I'm not trying to be argumentative, just explaining my experience in case this might help others in the future.

[Q] How to proceed to S-Off,boot loader unlock,sim unlock from stock?

Hello friends, I just got a new refurbished rogers(canada) HTC M8 GSM phone.Its totally stock at this moment and would like to do sim unlock,s-off and boot loader unlock. But before i would like to get full back up of my stock.Few questions:
1.How can i do full complete backup of my stock phone in case in future i need to revert back?
2. what are the steps to do s-off,sim unlock and bootloader unlock?
Right now phone says:
Android version 4.4.3
HTC sence version 6.0
software number 2.23.631.2
HTC SDK API level 6.25
kernel version
3.4.0--g523xxxxxx
baseband version
1.19.2133xxxxxxxx
build number
2.23.631.xxxxxxxrelease-keys
Thanks in advance...

Go to HTCDev.com to unlock the bootloader. The process is self-explanatory (just follow the website instructions). There is a writeup on the following guide, if you need help. But honestly, if you can follow instruction, the process is self-explanatory as I mentioned: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
Then, to backup the stock ROM and recovery, follow the instructions listed on the following thread under "How do i backup the stock HTC recovery?" : http://forum.xda-developers.com/showthread.php?t=2701376
This process will boot custom recovery without actually flashing recovery it to the phone, allowing you to backup stock recovery as well as the stock ROM (if you flash custom recovery before doing this, stock recovery is over-written and therefore can't be backed up). Note that your version's stock ROM and recovery may already be uploaded to the above thread by another XDA user.
Then achieve root by your preferred method (flash custom recovery and flash SU/SuperSU, or use weaksauce, towelroot, etc.). Then use sunshine to achieve s-off (firewater s-off will likely not work, as it was patched some time ago): http://theroot.ninja/
Then after s-off, you can unlock SIM: http://forum.xda-developers.com/showthread.php?t=2708572

Thanks a lot redpont73 for your directions!!!Will follow your steps and let you know how things went..Thanks

Ok i unlocked my bootloader with htcdev.com and it says unlocked now.
Now how to backup my stock at this point? I tried this thread you showed me: http://forum.xda-developers.com/show....php?t=2701376 but didn't understand fully. but it says :fastboot boot recovery_filename.img (this does not work on the latest 3.xx firmwares !!! we need to get the stock recoveries from the OTA files)"
I am little confused at this point.How can i back up at this point without installing any recovery software like twrp?please guide me.thanks

ninja_zx11 said:
Now how to backup my stock at this point? I tried this thread you showed me: http://forum.xda-developers.com/show....php?t=2701376 but didn't understand fully. but it says :fastboot boot recovery_filename.img (this does not work on the latest 3.xx firmwares !!! we need to get the stock recoveries from the OTA files)"
I am little confused at this point.How can i back up at this point without installing any recovery software like twrp?
Click to expand...
Click to collapse
By placing the custom recovery image in your fastboot folder, you can then boot recovery without actually flashing it to the phone, using the command you quoted. Think of it as remotely running the TWRP software that is still located on your PC (at least I think that is how it works).
Once you are booted into TWRP, you can backup system (stock ROM) and recovery(stock recovery).

redpoint73 said:
By placing the custom recovery image in your fastboot folder, you can then boot recovery without actually flashing it to the phone, using the command you quoted. Think of it as remotely running the TWRP software that is still located on your PC (at least I think that is how it works).
Once you are booted into TWRP, you can backup system (stock ROM) and recovery(stock recovery).
Click to expand...
Click to collapse
Could you please help me to find the custom recovery image that i can put in my fast boot folder and please step by step if you don't mind please.Just trying to learn and don't want to brick my phone with any wrong move.thanks

i found this thread.
http://forum.xda-developers.com/showpost.php?p=53770286&postcount=4
Will that help?thanks

ninja_zx11 said:
i found this thread.
http://forum.xda-developers.com/showpost.php?p=53770286&postcount=4
Will that help?thanks
Click to expand...
Click to collapse
Yes, that is another method.
---------- Post added at 11:11 AM ---------- Previous post was at 11:05 AM ----------
ninja_zx11 said:
Could you please help me to find the custom recovery image that i can put in my fast boot folder and please step by step if you don't mind please.
Click to expand...
Click to collapse
Go to the General forum section for the M8, and look at the Index thread (sticky at the top of that forum) to find link to recoveries and other resources, including guides and how-tos. Read up and learn.
Taking the time to familiarize yourself with the basic concepts and processes is much more valuable than someone walking your though step-by-step. I won't walk you through step-by-step, as you will learn very little that way.
The process is not that difficult, anyway. You already used fastboot to unlock the bootloader. Other fastboot commands are not any different in execution. If you can't handle taking it from here, modding the phone probably isn't for you.
With S-on, you aren't going to brick the phone by backing up or flashing recovery. Even with s-off, as long as you only flash things intended for the M8 (and only for the GSM version - not CDMA - to be safe), you will not brick. You can only brick the phone if you damage hboot, radio, or partition tables.

redpoint73 said:
Yes, that is another method.
---------- Post added at 11:11 AM ---------- Previous post was at 11:05 AM ----------
Go to the General forum section for the M8, and look at the Index thread (sticky at the top of that forum) to find link to recoveries and other resources, including guides and how-tos. Read up and learn.
Taking the time to familiarize yourself with the basic concepts and processes is much more valuable than someone walking your though step-by-step. I won't walk you through step-by-step, as you will learn very little that way.
The process is not that difficult, anyway. You already used fastboot to unlock the bootloader. Other fastboot commands are not any different in execution. If you can't handle taking it from here, modding the phone probably isn't for you.
With S-on, you aren't going to brick the phone by backing up or flashing recovery. Even with s-off, as long as you only flash things intended for the M8 (and only for the GSM version - not CDMA - to be safe), you will not brick. You can only brick the phone if you damage hboot, radio, or partition tables.
Click to expand...
Click to collapse
Yes you are right...I will read more and i want to learn and will try to do it myself.If i will have some confusion, i will ask here.Looks like i need more reading.
Now what i am planning to do is:
1. Install twrp
2.Take a full nandroid backup.(will it be enough to save me in future if i would like to go back to stock after S-OFF?)
3.root and s-off.
Does it make sense?

ninja_zx11 said:
Now what i am planning to do is:
1. Install twrp
2.Take a full nandroid backup.(will it be enough to save me in future if i would like to go back to stock after S-OFF?)
3.root and s-off.
Does it make sense?
Click to expand...
Click to collapse
The process to backup stock recovery is easy, by either method we already discussed. If you want to be thorough, backup stock recovery.
Backing up stock recovery and stock ROM is sufficient to return (mostly) to stock. There isn't much else you can do

redpoint73 said:
The process to backup stock recovery is easy, by either method we already discussed. If you want to be thorough, backup stock recovery.
Backing up stock recovery and stock ROM is sufficient to return (mostly) to stock. There isn't much else you can do
Click to expand...
Click to collapse
UPDATE:
I downloaded latest twrp and i booted into twrp .then took full backup. i also took back up using philz touch same way by just booting into philztouch.
Then i tried to root using supersu by same booting into twrp and tried to root.it created a supersu icon on the spring board and then i tried to install it from play store but it errored out and phone rebooted.After that i tried to remove the supersu icon from the phone but just couldnt. Then i thought of restoring stock backup using twrp and it restored it to stock stage.Atleast now i know that my stock backup worked.!!!
Now my question is why did supersu not root my phone?Should i try another method?please advice.thanks

ninja_zx11 said:
UPDATE:
I downloaded latest twrp and i booted into twrp .then took full backup. i also took back up using philz touch same way by just booting into philztouch.
Then i tried to root using supersu by same booting into twrp and tried to root.it created a supersu icon on the spring board and then i tried to install it from play store but it errored out and phone rebooted.After that i tried to remove the supersu icon from the phone but just couldnt. Then i thought of restoring stock backup using twrp and it restored it to stock stage.Atleast now i know that my stock backup worked.!!!
Now my question is why did supersu not root my phone?Should i try another method?please advice.thanks
Click to expand...
Click to collapse
huh? Did you flash it and then tried to install it from the play store after it was already "installed" by being flashed in custom recovery? If not, what exactly are you talking about here?
I've never bothered with the play store, just boot the custom recovery and flash the latest SuperSU. That's it... :silly:

BerndM14 said:
huh? Did you flash it and then tried to install it from the play store after it was already "installed" by being flashed in custom recovery? If not, what exactly are you talking about here?
I've never bothered with the play store, just boot the custom recovery and flash the latest SuperSU. That's it... :silly:
Click to expand...
Click to collapse
thanks BerndM14, i just copied supersu zip to internal storage as you said and installed it by booting into twrp from pc. and its done... thanks..

ninja_zx11 said:
UPDATE:
I downloaded latest twrp and i booted into twrp .then took full backup. i also took back up using philz touch same way by just booting into philztouch.
Then i tried to root using supersu by same booting into twrp and tried to root.it created a supersu icon on the spring board and then i tried to install it from play store but it errored out and phone rebooted.After that i tried to remove the supersu icon from the phone but just couldnt. Then i thought of restoring stock backup using twrp and it restored it to stock stage.Atleast now i know that my stock backup worked.!!!
Now my question is why did supersu not root my phone?Should i try another method?please advice.thanks
Click to expand...
Click to collapse
Sounds like a brick in the making.
Make sure that you read and understand what you are about to do before you do it.
A nandroid won't always help you.
If I may make a suggestion, don't go S-Off.

I am abandoning the idea of doing S-off after the suggestion from xunholyx above and after reading this http://android-revolution-hd.blogspot.ca/2013/06/do-we-really-need-s-off.html.

ninja_zx11 said:
I am abandoning the idea of doing S-off after the suggestion from xunholyx above and after reading this http://android-revolution-hd.blogspot.ca/2013/06/do-we-really-need-s-off.html.
Click to expand...
Click to collapse
I see you are learning. I will never understand why folks seek to get s-off, without even understanding what it means. You should not be attempting any mods, unless you fully understand what the purpose is (such as s-off).

redpoint73 said:
I see you are learning. I will never understand why folks seek to get s-off, without even understanding what it means. You should not be attempting any mods, unless you fully understand what the purpose is (such as s-off).
Click to expand...
Click to collapse
thanks redpoint73 for giving me helping hand!! without your help i wouldn't have done it.....

Return completely to stock (VM)

I'm trying to get a completely stock experience on my phone. I want to update it to the latest version but cannot because it is rooted, bootloader is unlocked, and a custom recovery is installed. I tried installing a stock rom then flashing a stock recovery and then relocking the bootloader to run the RUU on HTC's website. I am stuck on hboot version 3.18.xxx. Any help would be greatly appreciated.

The_Greatest_Juan said:
I'm trying to get a completely stock experience on my phone. I want to update it to the latest version but cannot because it is rooted, bootloader is unlocked, and a custom recovery is installed. I tried installing a stock rom then flashing a stock recovery and then relocking the bootloader to run the RUU on HTC's website. I am stuck on hboot version 3.18.xxx. Any help would be greatly appreciated.
Click to expand...
Click to collapse
You need to nandroid restore back to pure stock WITH root added and no apps removed.
Then you need to remove root from the settings in the SuperSU app.
Then go to the bootloader, flash the stock recovery.
Then back to the bootloader and relock it.
Now factory restore from bootloader or settings while you have the stock recovery, relocked bootloader and root removed.
Now you can update via HTC or system update.
Sent from my 710C using XDA Free mobile app

jaysoblitzed said:
You need to nandroid restore back to pure stock WITH root added and no apps removed.
Then you need to remove root from the settings in the SuperSU app.
Then go to the bootloader, flash the stock recovery.
Then back to the bootloader and relock it.
Now factory restore from bootloader or settings while you have the stock recovery, relocked bootloader and root removed.
Now you can update via HTC or system update.
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
Ok. So i did everything you said except whenever I try to factory reset, it flashes a screen that says entering recovery but then immediately goes back into bootloader. Is this because I have the incorrect recovery or a different problem.

Everything has been done as your guide, however on update process, the screen was displayed is dark blank.
What's something wrong guy...

Does anyone have the RUU.exe for virgin mobile. Tried to use the one I had last nite didn't work. Downloaded it 3times,says Install Script Shield has stopped working. Anyone.

ajones23 said:
Does anyone have the RUU.exe for virgin mobile. Tried to use the one I had last nite didn't work. Downloaded it 3times,says Install Script Shield has stopped working. Anyone.
Click to expand...
Click to collapse
Tried it last night..worked the second time..did stop working for me once as well

ajones23 said:
Does anyone have the RUU.exe for virgin mobile. Tried to use the one I had last nite didn't work. Downloaded it 3times,says Install Script Shield has stopped working. Anyone.
Click to expand...
Click to collapse
THIS is the only one, as it is the official one from HTC.

FoxyDrew said:
THIS is the only one, as it is the official one from HTC.
Click to expand...
Click to collapse
Already flashed back to stock. Used it method put Rom zip on sdcard,rebooted and put sdcard in. Success. Thanks.

Stock recovery for OS version 3.41.651.41 needed

I bought the phone (HTC One M9) yesterday and I realized I couldn't install the OTA updates I received because TWRP custom recovery was installed. I've looked through all the threads here but I never found the file I need. Any help would be highly appreciated. By the way,the bootloader is locked and the phone is unrooted, but S-OFF

S-off makes no difference. Unlocked bootloader makes no difference. If you flash a stock recovery over twrp you'll instantly kill the phone.
You need the full proper stock firmware of the exact same version you have on it now in .zip format and flash it from the external sd in download mode. You can use the ruu (.exe) too if it'll flash. Then you can take the ota's.
If the phone has been touched and not flashed back to stock you will need to flash to stock to get ota's. You cannot just "undo" what you've done to it. It must be properly reflashed to get the stock hash and keys.

shivadow said:
If you flash a stock recovery over twrp you'll instantly kill the phone.
Click to expand...
Click to collapse
Why should flashing the stock recovery via twrp kill the phone? If that was the case you wouldn't be able to get back to stock via twrp backups.
Edit @OP: If you have a RUU for the mentioned firmware version then you can use the RUU decryption tool that is linked in the ReadMe thread. The tool will extract the stock recovery from the RUU.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Why should flashing the stock recovery via twrp kill the phone? If that was the case you wouldn't be able to get back to stock via twrp backups.
Edit @OP: If you have a RUU for the mentioned firmware version then you can use the RUU decryption tool that is linked in the ReadMe thread. The tool will extract the stock recovery from the RUU.
Click to expand...
Click to collapse
Unrooted. Twrp will require root. If I remember correctly you flash twrp which roots the phone and then you flash supersu?.
If it is unrooted with twrp on it then it is in an "unknown state" (to me) and not worth risking going any further unless it is a full stock firmware flash. If he flashes a stock recovery over twrp he still wont have system "untouched" which I believe stock recovery requires?.. At least to get the ota's he will need an untouched partition.
Or would he be better off rerooting via twrp and go from there?.

No, twrp doesn't require root nor does flashing twrp root the phone. Twrp is a custom recovery that supports (unlike the stock recovery) flashing files that aren't signed by HTC. SuperSU and magisk are the ones that enable root. For using a metaphora (that might not fit exactly but that should suffice for making things clear): You don't consider your phone to be rooted, either, just because you installed Odin on your PC.
Root can (more or less) be compared with admin permissions on a Windows PC. It has nothing to do with twrp being "installed" or not. There are even methods for rooting phones without the use of twrp (e.g. kingroot - which is adware, btw).
If you flash twrp but don't root your phone then it's simply not-rooted. Keeping the phone in such a state doesn't make much sense since it isn't completely stock, either. However, it's not risky at all.
As long as the system image didn't get modified (e.g. by mounting it via twrp) and you didn't tinker with your phone aside from flashing twrp, re-flashing the stock recovery is absolutely sufficent for getting back to a completely stock state.
The thing is that most people that flash twrp to modify their system partition in one way or another. As you wrote (and due to Android updates being block-based since Android 5), ota's will fail as soon as they notice that the system got modified.
The stock recovery on the other hand doesn't "care" whether your phone is modified or not.
The only problem that might arise is that people tend to re-lock their bootloader since they learned (while using older htc devices) that it would be necessary for flashing certain stock files (e.g. RUUs) or installing OTA's. The m9 won't boot if you re-lock the bootloader and the phone isn't completely stock. There are security checks which don't differentiate between wanted user customizations and critical software failures. Therefore, they will try to save the hardware from damages caused by the "failed" software (by preventing the phone from booting).
In addition, google's frp makes it impossible to re-un-lock the bootloader in such situations if "OEM unlock" isn't activated in the developer settings of the used rom.
That's why the readme thread discourages the average Joe and the average Jane from re-locking this phone.
Sent from my Moto X Style using XDA Labs

Thanks, but I went ahead and flashed a zip RUU for that firmware version, then flashed the nougat one afterwards