Develop Bugs

On the Update for 30 stepers.

Question for the seniors in the area.
If I have rooted my EVO via the 30 step, non-adp / yes terminal emulator method, and have bugless beast as my rom, radio 1.39.00.05.31, can I flash the rooted update from yesterday quoted below:
Also is anything I have done been odexed / deodexed. I dont' believe it is, but maybe in the beast somthing is....again, forgive the ignorance.
Calkulin said:
Here is the OTA 1.47.651.1 update(complete ROM) rooted. It works with Toast's method but I don't know if it will work with Unrevoked
Just an FYI, zip contains odex'd system files
Also it will not break NAND access - If it does, redo Toast's part 2 root method and then rerun this update from this tread?
I am sure there are a bunch of guys in here that have a similar setup and are curious. Forgive the new guy, but I guess I'm here to progress......yes?
EVO_1.47.651.1_De-odex'd_Rooted.zip
EVO_1.47.651.1_Rooted.zip
Mirror @ SDX - EVO_1.47.651.1_Rooted.zip - Thx Joeykrim
Click to expand...
Click to collapse
Thanks for the read / reply !!!!!
-JZ

This should be posted in the general forum, imo.

Why (imho)? Put down the Gameboy and try and answer the question. Every section of my question has to do with areas specific to THIS forum. So where is the sense in posting in general? Try and contribute something to the conversation rather than, "move your post." In other words.....quit padding your stats dude. Thanks for the help though....lmao.

Considering that you will want to wipe everything (cache, dalvik cache, and system data) before installing, you can use either one. I use the standard ODEXed version myself, but it's a matter of preference.

you're good to flash this rom. it'll put on the newest sprint stock rom that was released ota but maintain your root and nand unlocked.
if you want my recommendation, wait for whomever's rom you're using to bake it into their rom, then you'll have the newest system files + your favorite custom rom
de-odex'd roms enable you to change the android themes. you can't do the same with odex'd.
odex'd also take up a little more of your internal phone space but nothing drastic.

Thread moved to Q&A.

Answered, [How-To] enclosed for Nov OTA

Go here for a much better proceedure:
http://androidforums.com/incredible...ng-nov-ota-rooted-incredible.html#post1876792

dsb9938 said:
Rooted Inc, otherwise factory ROM. S-OFF in effect.
If I flash a factory recovery, will the OTA update take?
Can I not simply reflash ClockWork after the update?
Thanks guys.
Click to expand...
Click to collapse
Im pretty sure it will take if you've got factory recovery. It doesn't seem to be as secure as the vaunted froyo update was.
And yes, you can simply reflash clockwork, but from bootloader, as a PB32IMG.zip
S-Off is wonderful.

Fretless said:
Im pretty sure it will take if you've got factory recovery. It doesn't seem to be as secure as the vaunted froyo update was.
And yes, you can simply reflash clockwork, but from bootloader, as a PB32IMG.zip
S-Off is wonderful.
Click to expand...
Click to collapse
What if I'm rooted without stock recovery?

thevoiceless said:
What if I'm rooted without stock recovery?
Click to expand...
Click to collapse
When you get the update nag, you ignore it, flash the stock recovery, which I am in process of getting now, then apply the patch, then reflash Clockwork.

Fretless said:
Im pretty sure it will take if you've got factory recovery. It doesn't seem to be as secure as the vaunted froyo update was.
And yes, you can simply reflash clockwork, but from bootloader, as a PB32IMG.zip
S-Off is wonderful.
Click to expand...
Click to collapse
Thanks, now to get the stock recovery from the RUU. Wee Haw!!!!

dsb9938 said:
When you get the update nag, you ignore it, flash the stock recovery, which I am in process of getting now, then apply the patch, then reflash Clockwork.
Click to expand...
Click to collapse
I'm still pretty new to this, how should I go about getting the stock recovery and flashing it? All I've done is use Unrevoked and Unrevoked Forever, then install ClockworkMod via Rom Manager, so pretty much everything has been done for me :/

thevoiceless said:
I'm still pretty new to this, how should I go about getting the stock recovery and flashing it? All I've done is use Unrevoked and Unrevoked Forever, then install ClockworkMod via Rom Manager, so pretty much everything has been done for me :/
Click to expand...
Click to collapse
I've asked in a couple places for the stock recovery. If/when I get it I will post a short how to.
I just don't want to lose everything on my phone to get this update.
I did a NAND backup and installed the update manually and there are several improvements I would like to have, such as significantly reduced charging time. But right now, without a custom ROM, the only way to get it is the RUU, and that wipes the phone.
Dennis

dsb9938 said:
I've asked in a couple places for the stock recovery. If/when I get it I will post a short how to.
I just don't want to lose everything on my phone to get this update.
I did a NAND backup and installed the update manually and there are several improvements I would like to have, such as significantly reduced charging time. But right now, without a custom ROM, the only way to get it is the RUU, and that wipes the phone.
Dennis
Click to expand...
Click to collapse
Awesome! Keep me updated

Please Hold.

dsb9938 said:
Please Hold.
Click to expand...
Click to collapse
What do you mean?

Go here for a much better proceedure:
http://androidforums.com/incredible...ng-nov-ota-rooted-incredible.html#post1876792

I am stuck at the bootloader not finding update.zip
any ideas?
stock 2.2 rooted s-off
I am assuming that you can't just apply the update.zip from clockwork because it fails to find the stock apps (which it is trying to update, such as AppSharing, and Flickr, etc.) that I removed.
p.s. step 7 is worded in a misleading way, although I understood what you meant. (reads like - rename the deleted file)
thanks for your help

JDubbz said:
I am stuck at the bootloader not finding update.zip
any ideas?
stock 2.2 rooted s-off
I am assuming that you can't just apply the update.zip from clockwork because it fails to find the stock apps (which it is trying to update, such as AppSharing, and Flickr, etc.) that I removed.
p.s. step 7 is worded in a misleading way, although I understood what you meant. (reads like - rename the deleted file)
thanks for your help
Click to expand...
Click to collapse
Having this issue with somebody else. I'm not sure if you can name it PB31IMG.zip or not, but you can try. Worst care, it doesn't load that way either.
I'm helping somebody else with the same issue right now, but his phone is totally hosed up, so I'm taking him back to stock 2.2 first. He has a good Titanium backup, so he won't lose anything.
If anybody else knows why the loader might ignore an update.zip please let me know.

JDubbz said:
I am stuck at the bootloader not finding update.zip
any ideas?
stock 2.2 rooted s-off
I am assuming that you can't just apply the update.zip from clockwork because it fails to find the stock apps (which it is trying to update, such as AppSharing, and Flickr, etc.) that I removed.
p.s. step 7 is worded in a misleading way, although I understood what you meant. (reads like - rename the deleted file)
thanks for your help
Click to expand...
Click to collapse
Okay, I have confirmed that you may perform "install sd/update.zip" from ROM Manager. It does work.

I'm still confused; do I have to have the stock recovery to do this?

I am not sure of these steps because I have read the threads from here and the post you put on Android forums as well and both threads are mentioning some issues.
Some posts state payload-update is unneccesary.
Some posts state that these steps are failing.
The post I am most concerned about states that "Rooted STOCK ONLY" means you can't have removed any bloatware either before doing this update. I have several apps removed, do I have to restore them before I take these steps?
Also not sure why folks are asking if they must have stock recovery. The instructions don't say anything about that.
I have noticed that the nagging has stoped on my dinc however if I go to the about update section in setup I find it states that the update has been successfully downloaded and is ready to install. Will this try to install the next time I boot the phone or is OK to boot?
Edit: Forgot to mention Some posts state that the process fails and you have to wait a few hours to continue, that's confusing and not in the instructions.
In summary
1) Do you have to re-install bloatware to make these steps work?
2) Is payload-update really necessary? What does each install in these steps do?
3) Does the process fail at some point if you don't allow the device to sit for a while, if so what step should you let it sit? It would be nice if someone understood this part also, anyone have a possible reason for this requirement?

I was asking if stock recovery is required because I've been told that OTAs won't install correctly if you don't. I was wondering if that still applied.

I got the update notification tonight and I clicked for it to install, and it counted down from ten seconds and said it was going to reboot and install updates, but it never did reboot. I'm guessing this is because I have unrevoked recovery? My gf's non rooted phone did get the update tonight as well, and hers installed without a hitch.
Sent from my HTC Incredible «•» Rooted/S-off/Froyo 2.2 «•»

Rooted, Stock 2.2, S-off, Clockwork; some bloatware removed
Install initiated through clockwork halted on vznav.apk, so I'm guessing it needs the original bloatware. I know that I should have backed it up but I guess my hatred of VZ pushiness got the better of me. Anyone have a work-around?

BrooklynAlex said:
Rooted, Stock 2.2, S-off, Clockwork; some bloatware removed
Install initiated through clockwork halted on vznav.apk, so I'm guessing it needs the original bloatware. I know that I should have backed it up but I guess my hatred of VZ pushiness got the better of me. Anyone have a work-around?
Click to expand...
Click to collapse
I guess we need someone to share the bloat apk's; I removed some of them without backing up, too :/

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

[Q] Newb M8 questions

Hi all,
Long time reader, first time poster.
Please don't kill me if my questions are somehow dumb. I promise I searched the web and xda thouroughly before posting.
1) I rooted my phone with HTCDev.com for the sole purpose of installing titanium backup. I tried to unintall some unwanted bloatware (scribble, tv, twitter, zoe, fitbit and more...) but they keep returning after boot. Why is that? Is it related to S-on? Is there a simple way to fix this?
2) My current software version is 1.54.707.7, I can update OTA to 2.22.707.3. Should I? From my experience with my previous samsung device, I'm afraid that updating blindly can cause more harm than good at some cases.
3) Can I update OTA even when I'm rooted? Will I need to replace the recovery and root again?
Thanks in advance,
Tal

talla1 said:
Hi all,
Long time reader, first time poster.
Please don't kill me if my questions are somehow dumb. I promise I searched the web and xda thouroughly before posting.
1) I rooted my phone with HTCDev.com for the sole purpose of installing titanium backup. I tried to unintall some unwanted bloatware (scribble, tv, twitter, zoe, fitbit and more...) but they keep returning after boot. Why is that? Is it related to S-on? Is there a simple way to fix this?
2) My current software version is 1.54.707.7, I can update OTA to 2.22.707.3. Should I? From my experience with my previous samsung device, I'm afraid that updating blindly can cause more harm than good at some cases.
3) Can I update OTA even when I'm rooted? Will I need to replace the recovery and root again?
Thanks in advance,
Tal
Click to expand...
Click to collapse
Hi Tal,
ok let's see if I can help you a little bit.
Regarding (1) I got a question: where and which files of the named apps did you delete?
Regarding (2) Sure you could update vis OTA as long as all system apps and stock recovery ist installed. Did you reinstall stock recovery, or are you unsing some custom recovery? As with custom recovery you can download but not install the OTA. This can then be done even if you are rooted. If you use supersu having the pro version installed you could try activating OTA survival mode and maybe root acces will still be there after performing the OTA. If not you could simply reinstall a custom recovery and using this root.
Hope this helps!?
If you could give me some answers regarding (1) I'll try to help ypu with this as well.

HTCNerdYoda said:
Hi Tal,
ok let's see if I can help you a little bit.
Regarding (1) I got a question: where and which files of the named apps did you delete?
Regarding (2) Sure you could update vis OTA as long as all system apps and stock recovery ist installed. Did you reinstall stock recovery, or are you unsing some custom recovery? As with custom recovery you can download but not install the OTA. This can then be done even if you are rooted. If you use supersu having the pro version installed you could try activating OTA survival mode and maybe root acces will still be there after performing the OTA. If not you could simply reinstall a custom recovery and using this root.
Hope this helps!?
If you could give me some answers regarding (1) I'll try to help ypu with this as well.
Click to expand...
Click to collapse
Thanks for the detailed and fast response, Yoda!
Regarding (1), I'm not sure I understand what you mean "where and which files". I backed up the mentioned apps in titanium backup, and then uninstalled them, again, with titanium backup. This method worked for me on my previous device (Samsung i9300).
Regarding (2), that's valuable information that I did not get anywhere from reading the sticky posts. I didn't know that the original recovery is needed in order to update OTA. I installed TWRP in order to install SuperSU. Is there a specific version of stock recovery that goes with the device? Or is there just one stock recovery for m8?
I had another question hidden in there, I'll make it number 3:
(3) Can someone tell me if the 2.22.707.3 version is any good? Stable enough? Or should I stick with 1.54.707.7 in the meanwhile?
Thanks allot!
Tal

talla1 said:
Thanks for the detailed and fast response, Yoda!
Regarding (1), I'm not sure I understand what you mean "where and which files". I backed up the mentioned apps in titanium backup, and then uninstalled them, again, with titanium backup. This method worked for me on my previous device (Samsung i9300).
Regarding (2), that's valuable information that I did not get anywhere from reading the sticky posts. I didn't know that the original recovery is needed in order to update OTA. I installed TWRP in order to install SuperSU. Is there a specific version of stock recovery that goes with the device? Or is there just one stock recovery for m8?
I had another question hidden in there, I'll make it number 3:
(3) Can someone tell me if the 2.22.707.3 version is any good? Stable enough? Or should I stick with 1.54.707.7 in the meanwhile?
Click to expand...
Click to collapse
(1) there are two folder /system/app and /system/priv-app. And overall there is the rw settings of the new kernel used. To be abled to unistall unwanted system apps maybe take a look at this post: http://forum.xda-developers.com/showthread.php?t=2723463, as maybe you need another kernel to accomplish it.
(2) you have to use a corresponding recovery, meaning you would have to download the 1.54.707.7 recovery (just google for it and you should find it in any forum) to work.
(3) I'm sorry that I can't be of any help here, as I performed an S-OFF debranding my phone and changin the CID to HTC__102 right from the start, setting it up to be on the WWE 2.22.401.4 since then.

3) the newest update (2.22 one) is very stable for me, no problems at all.
Sent from my One M8 using XDA Free mobile app

Thanks for this information!
Sent from my HTC One_M8 using XDA Free mobile app

HTCNerdYoda said:
Thanks for this information!
Click to expand...
Click to collapse
1) HTCDev unlocks the boot loader, it doesn't root. This can delete some default system apps, preventing an OTA. In order to have changes to system stick after reboot you need a kernel module: http://forum.xda-developers.com/showthread.php?p=51543139
2) Don't worry, HTC are much better with updates than Samsung. They work, you can trust them.
3) Once you have unlocked boot loader, you may struggle to update OTA due to the missing apps, but there are threads here explaining what to do. As mentioned, you'll need stock recovery and yes, you may need to root again, after installing your custom recovery after the update.

BenPope said:
1) HTCDev unlocks the boot loader, it doesn't root. This can delete some default system apps, preventing an OTA. In order to have changes to system stick after reboot you need a kernel module: http://forum.xda-developers.com/showthread.php?p=51543139
2) Don't worry, HTC are much better with updates than Samsung. They work, you can trust them.
3) Once you have unlocked boot loader, you may struggle to update OTA due to the missing apps, but there are threads here explaining what to do. As mentioned, you'll need stock recovery and yes, you may need to root again, after installing your custom recovery after the update.
Click to expand...
Click to collapse
Thanks for all the valuable info!!
I tried searching for the recovery, but as always, it's not that simple.. Too many sources of information and I don't know who's genuine. I haven't found a link on XDA yet (to the full stock ROM yes, not for the recovery only).
You say that OTA is a hassle when the recovery is replaced. I'm not stressed on upgrading OTA. How WOULD YOU SUGGEST to upgrade? Downloading the newest stock from XDA and using fastboot?
I created nandroid backups before but never restored one, so JUST TO BE SURE: this backup will be the full snapshot? Meaning: my old version (if the new one sucks) + apps + data? I don't need to backup ANYTHING except doing a nandroid backup?
Thanks again.
Tal
UPDATE: dug around some more and found the stock recoveries here after following the link from this post.
But before I flash anything, I just want to make sure that:
1) The nandroid I'll do in TWRP is the only backup I need to do.
2) There is no simpler option than returning to stock recovery, updating OTA, returning to TWRP recovery, rooting.
Tal

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