Develop Bugs

Does the OTA Simple Root unlock NAND

I can't seem to find the answer
Should I do anything after I do the OTA Simple Root. I was thinking of flashing the original RUU and going through the 3 step simple root, assuming this method doesn't unlock NAND.
I am using the White HTC Evo if that matter

It seems like I am also having issues with Wireless Tether with this root method, maybe I should just RUU and start over

michaelvibe said:
It seems like I am also having issues with Wireless Tether with this root method, maybe I should just RUU and start over
Click to expand...
Click to collapse
All simpleroot does is downgrade you from 1.47 to 1.17. You have to update to the stock rooted rom(guide below). You'll still have root/nand access with superuser permissions to allow wifi tether/titanium backup etc etc.
Guide - http://forum.xda-developers.com/showthread.php?t=715915
When it says to rename to PC36IMG.zip leave the .zip off. It won't read it with the .zip but leave the other file alone...don't rename it.

churchwin88 said:
All simpleroot does is downgrade you from 1.47 to 1.17. You have to update to the stock rooted rom(guide below). You'll still have root/nand access with superuser permissions to allow wifi tether/titanium backup etc etc.
Guide - http://forum.xda-developers.com/showthread.php?t=715915
When it says to rename to PC36IMG.zip leave the .zip off. It won't read it with the .zip but leave the other file alone...don't rename it.
Click to expand...
Click to collapse
Ugh that is over my head...guess that I am not as savvy as I thought. I ended up just flashing the stock RUU and am going to run the 3 step simple root.

michaelvibe said:
Ugh that is over my head...guess that I am not as savvy as I thought. I ended up just flashing the stock RUU and am going to run the 3 step simple root.
Click to expand...
Click to collapse
Which RUU did you flash? The 3 step simple root won't work with the latest RUU. You need the Simple root OTA.
EDIT: Which software version do you have as of now?

churchwin88 said:
Which RUU did you flash? The 3 step simple root won't work with the latest RUU. You need the Simple root OTA.
EDIT: Which software version do you have as of now?
Click to expand...
Click to collapse
I ran the original RUU, which sent my software version back to 1.32.651.1
On another note, I get an unhandled exception error when running simple root step 2, saying file not found.
sorry, original being RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe

michaelvibe said:
I ran the original RUU, which sent my software version back to 1.32.651.1
On another note, I get an unhandled exception error when running simple root step 2, saying file not found.
Click to expand...
Click to collapse
Okay, I'm kind of confused about something. Did you previously have root/nand access?
As for the simple root error, I have no clue. I haven't used that program. You'll have to post in that thread and ask someone.

churchwin88 said:
Okay, I'm kind of confused about something. Did you previously have root/nand access?
As for the simple root error, I have no clue. I haven't used that program. You'll have to post in that thread and ask someone.
Click to expand...
Click to collapse
I am not sure, I ran OTA simple root, but it somewhat confused me. Afterwards I installed Wireless Tether and it failed because of SU permissions. At that point I ran the RUU and was just going to start fresh. Everything is working fine, I just need to unlock NAND now.

michaelvibe said:
I am not sure, I ran OTA simple root, but it somewhat confused me. Afterwards I installed Wireless Tether and it failed because of SU permissions. At that point I ran the RUU and was just going to start fresh. Everything is working fine, I just need to unlock NAND now.
Click to expand...
Click to collapse
Haha, you went forward then backward and now are moving to the same spot you was in earlier.
Where exactly are you right now as far as rooting? What have you done since flashing the RUU?

churchwin88 said:
Haha, you went forward then backward and now are moving to the same spot you was in earlier.
Where exactly are you right now as far as rooting? What have you done since flashing the RUU?
Click to expand...
Click to collapse
Well I ran the RUU of course, and now I am almost through the 3 step simple root lol

michaelvibe said:
Well I ran the RUU of course, and now I am almost through the 3 step simple root lol
Click to expand...
Click to collapse
If simple root won't work follow these two guides.
Guide 1 - **you can skip the part with the evorecovery for now** - http://forum.xda-developers.com/showthread.php?t=690762
After that do this guide(part 2) - gives you unlocked nand - http://forum.xda-developers.com/showthread.php?t=701835

michaelvibe said:
Well I ran the RUU of course, and now I am almost through the 3 step simple root lol
Click to expand...
Click to collapse
Hah you guys were right, I am now back at 1.17.651.1. What a waste of my time...
Total noobie, at least I didn't brick the phone in the process

michaelvibe said:
Hah you guys were right, I am now back at 1.17.651.1. What a waste of my time...
Total noobie, at least I didn't brick the phone in the process
Click to expand...
Click to collapse
Hey, you live and learn.
Now, since that worked. You need the latest stock root rom(1.47). Go back to post #3 I made and follow my word of advice and the guide.

churchwin88 said:
Hey, you live and learn.
Now, since that worked. You need the latest stock root rom(1.47). Go back to post #3 I made and follow my word of advice and the guide.
Click to expand...
Click to collapse
So at this point I can flash custom roms correct? I don't absolutely have to run the newest stock?

michaelvibe said:
So at this point I can flash custom roms correct? I don't absolutely have to run the newest stock?
Click to expand...
Click to collapse
Yeah, you can go to a custom rom if you want. If you do the stock route first you have the option to do a nandroid backup which saves everything to that point so if you run into trouble later on you can just restore everything back to that point(meaning no doing rooting then unrooting then rooting again lol)
IMO, I would do the stock rom first and wait a couple days as the devs are cooking up the latest roms for a release here soon. Then I would get a custom rom but that is me.
EDIT: I only mention the nandroid backup because I don't believe you have a recovery flashed yet. If you do have a recovery I would highly suggest making a backup of both nand and google propiertory(however you spell it).

churchwin88 said:
Yeah, you can go to a custom rom if you want. If you do the stock route first you have the option to do a nandroid backup which saves everything to that point so if you run into trouble later on you can just restore everything back to that point(meaning no doing rooting then unrooting then rooting again lol)
IMO, I would do the stock rom first and wait a couple days as the devs are cooking up the latest roms for a release here soon. Then I would get a custom rom but that is me.
EDIT: I only mention the nandroid backup because I don't believe you have a recovery flashed yet. If you do have a recovery I would highly suggest making a backup of both nand and google propiertory(however you spell it).
Click to expand...
Click to collapse
After I flashed that rom that you provided me with in link three, the recovery changed. I assume that is normal. The option for nandroid backup was gone, but I did find NAND backup with I assume is the same thing. The NAND backup is in case anything ever goes wrong when I am flashing correct?
Thanks for the help.

[ROM] Official Gingerbread update available via OTA from Verizon!

Anyone in the US who woke up this morning and immediately tried Settings -> Software update -> Check new was greeted with a surprise from Verizon: Gingerbread available via OTA! It's a big update, so be sure you have a nice, strong, reliable 3G connection before attempting the upgrade.
My selfish question for the experts is: Now that I've performed the dance of joy at achieving S-OFF and root thanks to Alpharev, will I lose my happiness (S-OFF and/or root) if I allow Verizon to update my Android OS OTA? Are there any special precautions I should follow before, during or after the update? I already have a post-S-OFF Nandroid backup. Is that enough of a safety net?
Thanks all!
- Dave

ViperGeek said:
Anyone in the US who woke up this morning and immediately tried Settings -> Software update -> Check new was greeted with a surprise from Verizon: Gingerbread available via OTA! It's a big update, so be sure you have a nice, strong, reliable 3G connection before attempting the upgrade.
My selfish question for the experts is: Now that I've performed the dance of joy at achieving S-OFF and root thanks to Alpharev, will I lose my happiness (S-OFF and/or root) if I allow Verizon to update my Android OS OTA? Are there any special precautions I should follow before, during or after the update? I already have a post-S-OFF Nandroid backup. Is that enough of a safety net?
Thanks all!
- Dave
Click to expand...
Click to collapse
There is a sticky thread in this forum about the GB RUU/OTA and also some threads in the General section (which is where this post should have been made). You may be putting your AlphaRevX S-OFF at risk by trying to install the OTA. In addition, before you can even attempt to install the OTA, you must remove ClockworkMod and install the original recovery.img from the Froyo ROM, so you would lose your 'safety net' backup, too.
There is already a fully rooted and de-bloated version of the ROM that you can safely flash using CWM and retain both root and S-OFF.

tpbklake said:
There is a sticky thread in this forum about the GB RUU/OTA and also some threads in the General section (which is where this post should have been made).
Click to expand...
Click to collapse
Sorry for the misplaced thread. I attempted to place this announcement in the same place as the same announcement for China Telecom:
[ROM] Offical Gingerbread 2.3.4 ROM is out via OTA by ChinaTelcom
You may be putting your AlphaRevX S-OFF at risk by trying to install the OTA. In addition, before you can even attempt to install the OTA, you must remove ClockworkMod and install the original recovery.img from the Froyo ROM, so you would lose your 'safety net' backup, too.
Click to expand...
Click to collapse
Thanks for the good advice and feedback.
There is already a fully rooted and de-bloated version of the ROM that you can safely flash using CWM and retain both root and S-OFF.
Click to expand...
Click to collapse
FTW, the ROM/thread in question is here:
http://forum.xda-developers.com/showthread.php?t=1161411
- Dave

recovery from the froyo ROM. GB 2.18.605.3 RUU leak whatever. just get back to stock recovery any of those from HTC will work. but you MAY lose root. and you MAY not be able to get it back other than XTC clip. Cheers.

tpbklake said:
There is a sticky thread in this forum about the GB RUU/OTA and also some threads in the General section (which is where this post should have been made). You may be putting your AlphaRevX S-OFF at risk by trying to install the OTA. In addition, before you can even attempt to install the OTA, you must remove ClockworkMod and install the original recovery.img from the Froyo ROM, so you would lose your 'safety net' backup, too.
There is already a fully rooted and de-bloated version of the ROM that you can safely flash using CWM and retain both root and S-OFF.
Click to expand...
Click to collapse
Some of this is incorrect,
It is possible you may lose root but you will not lose your s-off. It's a higher version of the bootloader so it should not be overwritten. I just learned that the OTA won't even install without the stock recovery.
However I'm with tpbklake, I would personally just install a ROM that's based off of the new OTA update. No difference (minus the bloat of course) plus you'll still have root.

HELP
Where does the OTA update download to? I had it downloaded but flashed to the rmk ROm but now it keeps rebooting and I assume wanting to apply the official OTA as it is sitting on my phone - dumb move by me somehow but how can I kill this boot loop issue can I remove something from the sdcard?
Thanks in advance.

chrismoo said:
Where does the OTA update download to? I had it downloaded but flashed to the rmk ROm but now it keeps rebooting and I assume wanting to apply the official OTA as it is sitting on my phone - dumb move by me somehow but how can I kill this boot loop issue can I remove something from the sdcard?
Thanks in advance.
Click to expand...
Click to collapse
all your base are belong to verizon!
well, you could try booting into recovery and starting all over again via clockwork.
if it's stuck in a loop, pull the battery, put it back in and hold down VOLUME DOWN + POWER to go into recovery

If you've rooted or plan to root, do not accept or bother with the OTA whatsoever.
The hard work has already been done, just install the ROM I put together.

I know I did something stupid at some point I have a backup so will restore that and try again - just thought there might have been a shortcut - like removing a file.
Live and learn!

chrismoo said:
Where does the OTA update download to? I had it downloaded but flashed to the rmk ROm but now it keeps rebooting and I assume wanting to apply the official OTA as it is sitting on my phone - dumb move by me somehow but how can I kill this boot loop issue can I remove something from the sdcard?
Thanks in advance.
Click to expand...
Click to collapse
the OTA will not install without the stock recovery. Sounds like you have CWM recovery on your phone.
pull the battery out
pop everything back in, hold vol down and then power. It'll load to the bootloader, once there it'll check for a P32IMG file name after that you'll have the option to select recovery.
you might want to wipe data, cache, and dalvik cache within recovery before installing the new rmk rom again.
Which ROM did you come from?

I came from CM7 back to stock (where it downloaded the OTA) and then I tried to RMK. I have Nandroid backups so will just try a complete wipe and then try RMK again.

so lets say you crack you're screen or something and need to get a new phone via insurance. couldn't you download this ota and then lose s-off and root so they would have no idea you did it in the first place?

applejacks108 said:
so lets say you crack you're screen or something and need to get a new phone via insurance. couldn't you download this ota and then lose s-off and root so they would have no idea you did it in the first place?
Click to expand...
Click to collapse
Replies earlier in this thread suggest that you'd first have to restore the original Recovery image, replacing, CWM, before you could load the updated OTA update. At that point, you'd be running GB, unrooted, but /may/ still have S-OFF.
- Dave
Sent from my Transformer TF101 using Tapatalk

That is correct. If anyone remembers the DInc1 we had to flash stock radio, s-on file, stock RUU. As of now we have NO s-on file to flash.
NoClue....

SuperSU and Stock Recovery

is there away to install SuperSU when you have stock recovery? I'm thinking that we have to have either CWM/TWRP to install the zip. or am I having a brain fart on this.....
Thanks for whomever can clear my cobwebs..

You need a custom recovery (TWRP or CWM).

bkeaver said:
is there away to install SuperSU when you have stock recovery? I'm thinking that we have to have either CWM/TWRP to install the zip. or am I having a brain fart on this.....
Thanks for whomever can clear my cobwebs..
Click to expand...
Click to collapse
You can install it if you have the bootloader unlocked.
Use boot command instead of flash to boot into custom recovery and install su.
e.g
Fastboot boot twrp.img

uronfire said:
You can install it if you have the bootloader unlocked.
Use boot command instead of flash to boot into custom recovery and install su.
e.g
Fastboot boot twrp.img
Click to expand...
Click to collapse
Yes, this.
However, why bother keeping stock recovery at all? Stock recovery is effectively neutered once rooted, as you can no longer install an OTA.

uronfire said:
You can install it if you have the bootloader unlocked.
Use boot command instead of flash to boot into custom recovery and install su.
e.g
Fastboot boot twrp.img
Click to expand...
Click to collapse
Thanks this worked :good:

so when I go into recovery now I get a image of a htc one with a red triangle and exclamation mark inside of it?? since I have never went into recovery on this phone before isn't it supposed to look like any other stock recovery??? and if this isn't right I have tried flashing the recovery already and still get the same result... can someone expand on this for me pls

bkeaver said:
so when I go into recovery now I get a image of a htc one with a red triangle and exclamation mark inside of it?? since I have never went into recovery on this phone before isn't it supposed to look like any other stock recovery??? and if this isn't right I have tried flashing the recovery already and still get the same result... can someone expand on this for me pls
Click to expand...
Click to collapse
You have stock recovery.

BenPope said:
You have stock recovery.
Click to expand...
Click to collapse
so it doesn't give you flash update and wipe and all that anymore.. sorry like I said I have never went into recovery on this phone.. just making sure...

bkeaver said:
so it doesn't give you flash update and wipe and all that anymore.. sorry like I said I have never went into recovery on this phone.. just making sure...
Click to expand...
Click to collapse
I think you have to hold volume up and hit power or something.

ok I am good.. thank you... I'm putting everything back to stock because someone bought my phone and I just want to make sure everything is correct on it now.. thanks!!

redpoint73 said:
Yes, this.
However, why bother keeping stock recovery at all? Stock recovery is effectively neutered once rooted, as you can no longer install an OTA.
Click to expand...
Click to collapse
i sold the phone and this is what they requested. I know the OTA wont work and I never keep stock recoveries on my phones but.... I guess they will find out for themselves

and btw thanks everyone for the help. I hit my thanks button but on my browser it it isn't showing it just to let you know....

bkeaver said:
i sold the phone and this is what they requested. I know the OTA wont work and I never keep stock recoveries on my phones but.... I guess they will find out for themselves
Click to expand...
Click to collapse
Sounds like somebody that is a bit ill-informed. They want root, but they probably also want OTA (the 2 don't go together, IMO) and heard that you need stock recovery for OTA. I suppose they can change everything back that they modified with root, and unroot or hide root to install the OTA. But it just seems they are making life more complicated than it needs to be.
Also sounds like its a person that wants root, but not willing to do it themselves. But I suppose that's not really your problem!

Option to root and have ota is very easy :
Stock rom (unmodified but rooted)
Stock recovery
And you can ota. The ota will probably delete superuser but that's about it. The ota will not fail because its rooted as long as the stock rom/apps are unmodified

Mr Hofs said:
Option to root and have ota is very easy :
Stock rom (unmodified but rooted)
Stock recovery
And you can ota. The ota will probably delete superuser but that's about it. The ota will not fail because its rooted as long as the stock rom/apps are unmodified
Click to expand...
Click to collapse
yeah this is what I did for them so who knows.. I've never tried it that way but i guess it would work like that

redpoint73 said:
Yes, this.
However, why bother keeping stock recovery at all? Stock recovery is effectively neutered once rooted, as you can no longer install an OTA.
Click to expand...
Click to collapse
Rooting doesn't affect ota's, at least not in my experience.

ashyx said:
Rooting doesn't affect ota's, at least not in my experience.
Click to expand...
Click to collapse
Only if absolutely nothing was changed with the stock ROM.
Its more my point there is little point to installing OTAs on a rooted device.

redpoint73 said:
Only if absolutely nothing was changed with the stock ROM.
Its more my point there is little point to installing OTAs on a rooted device.
Click to expand...
Click to collapse
I don't understand that statement. I still run stock sense, but with a few additions that don't affect ota's. So I still get updates while having things configured the way I want. I can also run things that require root such as titanium backup and a few others.

ashyx said:
I don't understand that statement. I still run stock sense, but with a few additions that don't affect ota's. So I still get updates while having things configured the way I want. I can also run things that require root such as titanium backup and a few others.
Click to expand...
Click to collapse
Because once you accept an OTA, you will be unrooted. You will have to root again, either by installing custom recovery (than back to stock recovery so you can OTA) or the trick of booting custom recovery via adb to flash SU (as described here). Its just a lot of jumping through hoops with little added value.
On the other hand, if you have custom recovery installed, you can flash any of the array of stock rooted or awesome custom ROMs posted here. This includes stock rooted ROMs taken from OTA updates from lots of versions (often posted within days of the OTA starting to roll out), not just your carrier, so you can possibly get an update much faster than waiting for the OTA to roll out from your carrier (although that depends on what carrier version you have). You also don't have to constantly be worried "well, if I change this I won't get OTAs". You can do whatever the heck you want, and isn't that really the whole point of root?
Its just my opinion. And a lot of this may stem from the fact that I'm on AT&T, who are not only agonizingly slow about rolling out OTAs (sometimes 3-4 months or even later than other carriers on my past HTC device) and have even went to the effort to close exploits and prevent unlocking of bootloaders when rolling out new OTAs (on the One X EVITA). In fact there was even a bug (I assume it was a bug - others may accuse that it was intentional) where installing the Jellybean OTA with SuperCID and S-on bricked the phone.
As I said, its just an opinion. But there are many others on XDA that will agree that OTAs have no place on rooted Android devices.
And to be fair, I did cover myself and stated "there is little point" instead of "there is no point"

[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.

Updating via OTA with modified system

I'm sure there's a guide somewhere but I couldn't find one clear enough. I recently got my HTC 10 to replace my Galaxy S4 GPE and have a question. This is my first update after rooting my phone, and I received an OTA message today. With my s4, all i needed to do to update was use ODIN. I know it's different with the HTC 10, but want to be 100% sure I'm doing this right. From what I've read I need to:
1. Mount system as read only via twrp and restore my original system-image (which I did make)
2. Flash stock recovery
3. Boot into Android and take the OTA.
4. Flash TWRP and make a backup in read only mode of system-image (for the sake of convenience with future OTAs)
5. Flash supersu.
Is this right? I read some where that having an unlocked bootloader would make an error occur when taking the OTA. Is this right? How do you guys update? Does flashfire work with HTC 10 and how do I use it? I'm s-on, does that matter? I have the factory unlocked version of the HTC 10. I'm terrified of something going wrong during the update process. Any help is greatly appreciated.

Kryztof said:
I'm sure there's a guide somewhere but I couldn't find one clear enough. I recently got my HTC 10 to replace my Galaxy S4 GPE and have a question. This is my first update after rooting my phone, and I received an OTA message today. With my s4, all i needed to do to update was use ODIN. I know it's different with the HTC 10, but want to be 100% sure I'm doing this right. From what I've read I need to:
1. Mount system as read only via twrp and restore my original system-image (which I did make)
2. Flash stock recovery
3. Boot into Android and take the OTA.
4. Flash TWRP and make a backup in read only mode of system-image (for the sake of convenience with future OTAs)
5. Flash supersu.
Is this right? I read some where that having an unlocked bootloader would make an error occur when taking the OTA. Is this right? How do you guys update? Does flashfire work with HTC 10 and how do I use it? I'm s-on, does that matter? I have the factory unlocked version of the HTC 10. I'm terrified of something going wrong during the update process. Any help is greatly appreciated.
Click to expand...
Click to collapse
That's exactly right.
Never relock your bootloader. It's completely unnecessary and can only cause problems if you don't know exactly what you're doing. And again, it's completely unnecessary. People love to throw that idea out as a troubleshooting suggestion. Don't do it.
That's exactly how I update.
Used flashify to root my Samsung tablet once. I've never used it once on any of my HTC devices, so I can't offer any advice on that. I don't really see why it would be necessary though.
S-on/off does not matter for this process.
I hope this answers all of your questions. Good luck.

jollywhitefoot said:
That's exactly right.
Never relock your bootloader. It's completely unnecessary and can only cause problems if you don't know exactly what you're doing. And again, it's completely unnecessary. People love to throw that idea out as a troubleshooting suggestion. Don't do it.
That's exactly how I update.
Used flashify to root my Samsung tablet once. I've never used it once on any of my HTC devices, so I can't offer any advice on that. I don't really see why it would be necessary though.
S-on/off does not matter for this process.
I hope this answers all of your questions. Good luck.
Click to expand...
Click to collapse
Unfortunately the error I read about mentioning a modified file system showed up. I followed this guide and got errors and managed to recover from a bootloop. I think I will just wait a while and use a RUU to restore and update.
EDIT: and now I get the same error with my old backup. I think I messed up the "mount system as read only" part because I do remember flashing System over but if it was read only it should have given me an error?

Kryztof said:
Unfortunately the error I read about mentioning a modified file system showed up. I followed this guide and got errors and managed to recover from a bootloop. I think I will just wait a while and use a RUU to restore and update.
Click to expand...
Click to collapse
Well I wrote that guide, so if you want to post what you did over in that thread I'll be happy to help you out. If you're US Unlocked that method should work 100%. I've never heard of anyone getting a bootloop from it.

U probably flashed a wrong stock recovery or something.
Would the steps described in the first post work for international HTC 10 (Europe) ?

CroCop18 said:
U probably flashed a wrong stock recovery or something.
Would the steps described in the first post work for international HTC 10 (Europe) ?
Click to expand...
Click to collapse
You're talking about in this guide?
http://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187
If you're interested in testing something, post over there. Short answer is no, the instructions in the OP have not worked on International devices. But @Captain_Throwback just posted an idea that might work.

jollywhitefoot said:
You're talking about in this guide?
http://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187
Short answer is no, the instructions in the OP have not worked on International devices.
Click to expand...
Click to collapse
Then how to revert an int. HTC 10 (1.90.401.5.) back to stock ? I have my system image backup and original recovery for my version...
Why does this have to be so complicated -.-

CroCop18 said:
Then how to revert an int. HTC 10 (1.90.401.5.) back to stock ? I have my system image backup and original recovery for my version...
Why does this have to be so complicated -.-
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-10/how-to/htc-10-stock-rom-ruu-t3378240/page5

Mr Hofs said:
http://forum.xda-developers.com/htc-10/how-to/htc-10-stock-rom-ruu-t3378240/page5
Click to expand...
Click to collapse
So flashing a RUU.zip is the only way for int. HTC 10 ?

CroCop18 said:
Then how to revert an int. HTC 10 (1.90.401.5.) back to stock ? I have my system image backup and original recovery for my version...
Why does this have to be so complicated -.-
Click to expand...
Click to collapse
It's not that complicated. Are you getting the System Corrupt error when you try to download the OTA?
If so, you have a few options for updating.
1) try the experimental option I'm working on in this thread (http://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187)
2) RUU (the 1.90 ruu is available now I think, but if not, just use 1.80 then OTA
3) flash signed firmware to update your firmware and then use someone's system backup to update the system files

jollywhitefoot said:
It's not that complicated. Are you getting the System Corrupt error when you try to download the OTA?
If so, you have a few options for updating.
1) try the experimental option I'm working on in this thread (http://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187)
2) RUU (the 1.90 ruu is available now I think, but if not, just use 1.80 then OTA
3) flash signed firmware to update your firmware and then use someone's system backup to update the system files
Click to expand...
Click to collapse
Im not getting any error, I`m just checking on how to revert back to stock and not screw up something in the process lol.
I thought you can only flash an RUU which main version is the same as your phone or newer (capt. throwback wrote that in his twrp topic).
Anyway, looks like flashing an RUU is the safest way.

CroCop18 said:
Im not getting any error, I`m just checking on how to revert back to stock and not screw up something in the process lol.
I thought you can only flash an RUU which main version is the same as your phone or newer (capt. throwback wrote that in his twrp topic).
Anyway, looks like flashing an RUU is the safest way.
Click to expand...
Click to collapse
That's correct about the RUU needing to be same or newer. What are you currently on? I assumed since you're wwe and trying to OTA then you were on 1.80.401.3.
RUU is definitely the safest way.