10-01-2012 10:23 AM
71 123
tools
  1. kbp08tls's Avatar
    Seasoned vets know by now to never accept OTA's on a rooted phone. Those new to the rooted world, take note.

    If you are rooted, but haven't unlocked or installed a custom recovery, HOLD TIGHT. DO NOT take the OTA unless you want to lose root for an undetermined amount of time (days, weeks, ???). There are currently no root methods that I know of yet for the new update.

    If you are thinking about using a root keeper, DON'T RISK IT. Sometimes it works, sometimes it doesn't.

    If you're rooted, unlocked, and have custom recovery, but still running the stock ROM, flash the updated rooted stock ROM here: http://forums.androidcentral.com/htc...ml#post1953211

    If you have a custom ROM flashed, hold tight and follow your particular ROM developer's instructions for the update.

    I know this should be in the Rooting Roms and Hacks subforum, but there's very little traffic there and I don't want anyone to bork their phone because they didn't know better.


    It's becoming clear that the update in the bootloader has closed the s-off exploit, and splashes and radios are no longer flashable in recovery.
    It's also clear that the update "fixes" current root exploits. Zedomax and regaw (root fails, HTC unlock works) are confirmed not working after OTA.
    Rootkeepers are flaky. Don't trust them. Period.
    Tical, MERCDROID, TonyC and 3 others like this.
    07-11-2012 09:39 AM
  2. Tical's Avatar
    Seasoned vets know by now to never accept OTA's on a rooted phone. Those new to the rooted world, take note....
    I just replied as much in another thread. I think part of the problem has been the ease of rooting and the proliferation of 'one click' solutions. These are VERY convenient. But I wonder if that convenience comes at the cost of most users having little to no understanding of what they are doing. People will throw out 'just root it' off the cuff, not explaining that it effectively takes you off of the official channels for updates/fixes. For the more knowledgeable, that's the entire point... But for others, I'm not convinced, it might be doing more harm than good that it's been made so easy and suggested so nonchalantly... </random thoughts>

    Great idea to set up the PSA though. Good Karma.
    MERCDROID and kbp08tls like this.
    07-11-2012 09:56 AM
  3. DougB541#CB's Avatar
    Good tip, its actually the main reason I haven't rooted yet, i was waiting on the first update or so.
    07-11-2012 10:10 AM
  4. digmys's Avatar
    It won't "bork" your phone. It just won't flash. No one that doesn't know better will hurt their phone trying.
    07-11-2012 10:15 AM
  5. KMyers's Avatar
    We need to separate the differences between rooted and custom recovery. They are 2 different things.

    You CAN root and have a stock recovery. In my case this is how I have it setup. I did apply the OTA and it simply breaks root.

    If you are rooted and have a custom recovery, then wait for an update .zip file to be leaked.
    kbp08tls and crxssi like this.
    07-11-2012 10:20 AM
  6. bpdamas's Avatar
    We need to separate the differences between rooted and custom recovery. They are 2 different things.

    You CAN root and have a stock recovery. In my case this is how I have it setup. I did apply the OTA and it simply breaks root.

    If you are rooted and have a custom recovery, then wait for an update .zip file to be leaked.
    So, since you accepted the OTA and it breaks root, if you were s-off in theory, all you would have to do is after you accept the OTA is the following:

    1. Flash a custom recovery through the hboot with fastboot usb
    2. Flash the superuser app again

    The only reason I say this because this is exactly what I did every time an update came out on my EVO 3D with revolutionary s-off. Either way I might try and accept the OTA update and see if s-off retains. If it does, the above method should work no problem. Anyone have any thoughts?

    Here is a link to show how to accept OTA updates.

    http://forums.androidcentral.com/htc...heres-how.html
    07-11-2012 10:36 AM
  7. bpdamas's Avatar
    It won't "bork" your phone. It just won't flash. No one that doesn't know better will hurt their phone trying.
    It can and will flash with a stock recovery.

    To get a stock recovery, see here:

    http://forum.xda-developers.com/show....php?t=1228648
    07-11-2012 10:37 AM
  8. mazzmoney95's Avatar
    After spending a year with a non rooted EVO 3D, I totally forgot and did the update. Nothing happened because it would just bring me to recovery.
    07-11-2012 10:44 AM
  9. kbp08tls's Avatar
    Thanks all for the clarifications. I'm personally going to hold off until I see a fair number of reports on all of the different combinations of root, recovery, locked/unlocked, s-on/s-off before I make a final judgment on taking the OTA. Or until a known safe rooted update.zip is posted.

    It still stands that UNLESS YOU KNOW WHAT YOU ARE DOING, you should not take an OTA on a rooted phone before it is judged safe to do so.
    Tical likes this.
    07-11-2012 10:48 AM
  10. bpdamas's Avatar
    It still stands that UNLESS YOU KNOW WHAT YOU ARE DOING, you should not take an OTA on a rooted phone before it is judged safe to do so.
    Agreed. I think that is definitely something to go by.
    07-11-2012 10:53 AM
  11. kronosqq's Avatar
    Just tried the OTA on mine, root, lazy panda s-off, and CWM recovery. It just doesn't flash the update.

    Sent from my EVO using Android Central Forums
    07-11-2012 11:47 AM
  12. chud's Avatar
    Being rooted and being unlocked with a custom recovery are two wildly different things.

    If you are rooted but not unlocked, go ahead and take the OTA and just reroot. It's not like you can just flash anything anyway if you only have root access.

    If you are unlocked and rooted then wait for a flashable .zip of the update or wait for your favorite ROM to be updated.
    kbp08tls and eerongal like this.
    07-11-2012 11:48 AM
  13. bpdamas's Avatar
    Just tried the OTA on mine, root, lazy panda s-off, and CWM recovery. It just doesn't flash the update.

    Sent from my EVO using Android Central Forums
    I more than likely fails only because you are running a custom recovery. See the following link to create your own stock recovery, flash the stock recovery through fastboot, and then try to apply the update if you really want to. However, I wouldn't recommend it since you could lose root and s-off.

    [GUIDE] Get Stock Recovery/Install OTA Updates without losing data. - xda-developers
    07-11-2012 11:54 AM
  14. kronosqq's Avatar
    I more than likely fails only because you are running a custom recovery. See the following link to create your own stock recovery, flash the stock recovery through fastboot, and then try to apply the update if you really want to. However, I wouldn't recommend it since you could lose root and s-off.

    [GUIDE] Get Stock Recovery/Install OTA Updates without losing data. - xda-developers
    Yeah, I'm probably going to hold off. Google wallet for me would be cool but is by no means a necessity.

    Sent from my EVO using Android Central Forums
    07-11-2012 12:21 PM
  15. bpdamas's Avatar
    Yeah, I'm probably going to hold off. Google wallet for me would be cool but is by no means a necessity.

    Sent from my EVO using Android Central Forums
    Probably a good idea. I haven't decided if I want to install it or not. I have it downloaded and have it waiting in my download bar.
    07-11-2012 12:33 PM
  16. blckz28's Avatar
    I'm rooted with stock rom and stock recovery. The update fails for me. After the phone reboots the update starts to load and then comes to the ! icon. Holding down the power button gets you back up as if nothing happened. Might have to unroot to get this update?
    07-11-2012 12:47 PM
  17. ReproOne's Avatar
    If you are just rooted to use wifi tether, for example, can you apply the OTA update and use RootKeeper to get it back?
    07-11-2012 12:56 PM
  18. bpdamas's Avatar
    I'm rooted with stock rom and stock recovery. The update fails for me. After the phone reboots the update starts to load and then comes to the ! icon. Holding down the power button gets you back up as if nothing happened. Might have to unroot to get this update?
    Hmmmm ... that seems somewhat strange especially with a stock recovery. Are you s-off? Did you ever flash a custom recovery or ROM?
    07-11-2012 12:59 PM
  19. blckz28's Avatar
    Hmmmm ... that seems somewhat strange especially with a stock recovery. Are you s-off? Did you ever flash a custom recovery or ROM?
    Nope, S-On and have never flashed another recovery or rom. I did just unroot it and my update still fails.
    07-11-2012 01:16 PM
  20. ReproOne's Avatar
    Wonder if you could use RootKeeper, temp unroot, apply update, and then restore root?
    07-11-2012 01:19 PM
  21. bpdamas's Avatar
    Nope, S-On and have never flashed another recovery or rom. I did just unroot it and my update still fails.
    What method did you use to gain root? To unroot?
    07-11-2012 01:19 PM
  22. blckz28's Avatar
    What method did you use to gain root? To unroot?
    I used the One-Click Root ToolKit to root and then in the SuperSU app I went into settings and used the option to full unroot.
    07-11-2012 02:57 PM
  23. gmtom1's Avatar
    Same here - I'm rooted only, using the original one-click method & just tried the OTA update and got the red triangle ! error. Rebooted and it doesn't seem that the update was applied. Going to try unroot now and update again.
    07-11-2012 03:17 PM
  24. gmtom1's Avatar
    Same here - I'm rooted only, using the original one-click method & just tried the OTA update and got the red triangle ! error. Rebooted and it doesn't seem that the update was applied. Going to try unroot now and update again.
    Ok, still no luck applying the OTA with unroot. It must be checking against the tampered warning. Looks like I'll need to do a full RUU or wait until someone smarter than me figures out how to get the OTA applied. Anyone know if I use the RUU method to return to stock, will that break my Wallet secure element?
    07-11-2012 03:35 PM
  25. kbp08tls's Avatar
    Here's some sage advice from EarlyMon, a mod over at Android Forums. Quoted directly, with his permission, from this thread, because he says it so much better than I ever could.

    I would personally advise against any OTA updates, regardless of method.

    If this OTA does mess with the bootloader, then I think that many will rue the day they avoided this warning.

    Once upon a time it was an inviolate rule of rooting - never, never, never accept an OTA. The "accept OTA/re-root/try-to-preserve root" school is one I'll never accept - look at the 1.5 year history of people doing it and right after declaring victory, crying that they're stuck until new exploits can be found.

    The s-off unlocking of the bootloader expects a specific exploit - will it remain? The Regaw one-click goes through HTC anonymously selecting "other supported device" - with that still work with this bootloader?

    Your mileage may vary, do as you all think best.

    No one has ever been jammed up following the "just wait, don't accept the OTA advice" - ever. Plenty of those who went the other way lived to regret it.

    ...

    PS from the OTA Rootkeeper page -


    The application doesn't support original Superuser and not SuperSU for a very simple reason. The same feature OTA protection feature is already present in SuperSU.
    All of us here are already using SuperSU, so - what's the point of playing with that?

    Second PS - No one has ever once regretting following my rooting advice in over two years. I feel like a dork for putting it that way, but I really want to stress the importance of giving this a day or two to sort out.

    Confirmed with a big tip of the topper to Sgt. Slaughter (AF member, XDA mod and a friend to all) -


    new hboot 1.15.000 inside
    We're all on 1.12.xxxx now (1.12.2222 for those staying current).
    crxssi likes this.
    07-11-2012 03:40 PM
71 123
LINK TO POST COPIED TO CLIPBOARD