Welcome to the forums!
Creative user name, I must say.
Creative user name, I must say.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Root after OTA?
- Thread starter eazy401
- Start date
-
- Tags
- htc evo 4g
evomattnc
Android Expert
if you are that person that has enough time, skill, and dumb luck to find an exploit to allow us in
, otherwise we wait...
actually the latest but smaller update htc/sprint put out is software number is 4.24.651.1 it is basically the netflix and other fixes. not that it changes the ability to root yet.
evomattnc
Android Expert
yeah i was just quoting the post from 2 posts up for humorous effect, it was apparently lost on you
The software version has nothing to do with it either...
yeah i was just quoting the post from 2 posts up for humorous effect, it was apparently lost on you
The software version has nothing to do with it either...
lol, i'm so lost
joehornback
Well-Known Member
If we accept this new maintenance release, will that further delay our ability to root once an exploit is found? Does this release update the HBOOT again?
here is the latest maintenance ota rooted stock rom:
[ROM][STOCK] 4.24.651.1 - Odexed & De-Odexed - xda-developers
i would not risk accepting it. just flash this rom and you are good to go.
joehornback
Well-Known Member
I'm sorry, but I might have left out a little info, I am not rooted at all, never have been, I am stock unrooted waiting for the new exploit to be found so I can root my GB 2.3.3 EVO. And my questions is, since I already took the original update now I'm stuck waiting for a new exploit, I don't want to take another update if it's going to further delay my ability to root when the exploit is found.
ahhh i see,
should not be an issue. i do not think that the recent maintenance update came with a new hboot. so you should be good to go with accepting it. i think the only change they did was to the software.
Just shamelessly bumping this thread so that hopefully someone will update it as soon as an exploit has been discovered for the latest OTA. Couldn't find a thread on xda dedicated to this exact topic, so I'm going to subscribe to this one.
I was all excited to finally root my phone before I realized we're still waiting on an exploit for GB...
I was all excited to finally root my phone before I realized we're still waiting on an exploit for GB...
evomattnc
Android Expert
I'm sure it will be up everywhere. what it comes down to is if you have hboot 2.16 there is no exploit yet. Every other hboot its rootable with the exception of some foreign evos. Any how point is its not about gb or froyo or eclair, its about radios and security...
yeah, there is no need to bump the thread because as soon as there is an exploit, believe me you will know about it here. there will be a sticky on the how to's. and i know that there will be a million threads and posts asking how to do this. so you will know. just stay tuned to this forum.
This might not be the right thread for this question, but here goes anyway.
I have been rooted with unrevoked since soon after the initial EVO release last June. I am also s-off. I haven't flashed any dev ROMs, as all I'm primarily interested in is wireless tether, and a couple other root apps.
So, my "strategy" has always been to:
1) re-install the stock recovery
2) take the OTA
3) re-install su
4) have a new, root stock ROM.
5) just for good measure, install ROM manager to make nandroids easy, just in case I ever want to try a dev ROM.
So, this worked flawlessly, throughout the Froyo OTA update cycle (two or three updates, if I recall).
And it worked perfect to accept the GB1 update.
However, in trying to do this with the latest GB2 update, I tried to flash the stock recovery (using the stock recovery extracted from the GB1 OTA zip file that I saved from the phone). When I flash the PC36IMG.zip file I created (via VolumeDown-PowerButton boot), it indicates the flash was taken. But, after deleting the PC36IMG file, and trying to re-boot into the stock recovery, it hangs at a RedTriangle-Exclamation screen. I must battery pull. I can re-boot the phone, no problem, but no recovery is possible to get into. Note the phone is still rooted (su runs and shows my su apps). I can re-flash ClockWorkMod, and get back into that recovery, but simply cannot get the stock recovery flashed successfully.
Unrevoked "recommends" going back to stock recovery to accept any OTA. So I've always done that, with no issues until now. Not sure I need to do that, but I have not tried simply accepting the GB2 OTA with CWM recovery installed.
Any thoughts on why a stock recovery cannot be flashed now that I am on GB1 when I've never had an issue with this previously?
Thanks in advance.
I have been rooted with unrevoked since soon after the initial EVO release last June. I am also s-off. I haven't flashed any dev ROMs, as all I'm primarily interested in is wireless tether, and a couple other root apps.
So, my "strategy" has always been to:
1) re-install the stock recovery
2) take the OTA
3) re-install su
4) have a new, root stock ROM.
5) just for good measure, install ROM manager to make nandroids easy, just in case I ever want to try a dev ROM.
So, this worked flawlessly, throughout the Froyo OTA update cycle (two or three updates, if I recall).
And it worked perfect to accept the GB1 update.
However, in trying to do this with the latest GB2 update, I tried to flash the stock recovery (using the stock recovery extracted from the GB1 OTA zip file that I saved from the phone). When I flash the PC36IMG.zip file I created (via VolumeDown-PowerButton boot), it indicates the flash was taken. But, after deleting the PC36IMG file, and trying to re-boot into the stock recovery, it hangs at a RedTriangle-Exclamation screen. I must battery pull. I can re-boot the phone, no problem, but no recovery is possible to get into. Note the phone is still rooted (su runs and shows my su apps). I can re-flash ClockWorkMod, and get back into that recovery, but simply cannot get the stock recovery flashed successfully.
Unrevoked "recommends" going back to stock recovery to accept any OTA. So I've always done that, with no issues until now. Not sure I need to do that, but I have not tried simply accepting the GB2 OTA with CWM recovery installed.
Any thoughts on why a stock recovery cannot be flashed now that I am on GB1 when I've never had an issue with this previously?
Thanks in advance.
interesting way of doing it. but i think that the best way is to just flash the rooted stock rom for the ota. there is a stock version of the second (maintenance) ota. you get it here:[ROM][STOCK] 4.24.651.1 - Odexed & De-Odexed - xda-developers
on that note the red triangle you are getting is because you cant access the stock recovery only custom recoveries can you get access to.
Yes, if I flash a stock recovery, and try to get into it, it just hangs. A battery pull is required. But, if I then flash a CWM recovery, I can get into with no problems
I'm more interested in why this might be happening now, than actually getting the GB2 update.
it hangs because it is a stock recovery which nobody has access to. custom ones are different.
"nobody has access to"... Not sure I understand this statement.
As I stated in the first post, I "always had access to" the stock recovery and could flash it, or a custom recovery, when Froyo was the present.
I got to GB1 by re-flashing the stock recovery, then taking the GB OTA update. s-off with unrevoked allows this, and recommends this method.
well recoveries you would normally have options to like flash a rom or kernel. in a stock recovery you do not. when checking if you have a stock recovery you will always get a the red triangle. it is most likely installed. anyways this is a moot point as all you really need to do is wait for the devs to cook up the ota rooted rom. much easier and safer way to update it that way.
OK, I'm hoping this is finally the right place to ask this question, and get an answer. Here goes....
I have been rooted with unrevoked since soon after the initial EVO release last June. I am also s-off via unrevoked forever. I haven't flashed any dev ROMs, as all I'm primarily interested in is wireless tether, and a couple other root apps.
So, my "strategy" with OTA updates has always been to:
1) re-install the stock recovery
2) take the OTA
3) re-install ClockWorkMod recovery
3) re-install su
4) have a new, root stock ROM.
5) just for good measure, install ROM manager to make nandroids easy, just in case I ever want to try a dev ROM.
The above process is recommended by unrevoked and has worked flawlessly, throughout the Froyo OTA update cycle (two or three updates, if I recall).
And it worked perfect to accept the GB1 update. I did that process, took the OTA and am still rooted, but now on hboot 2.16, still with s-off.
However, in trying to do this same process again, with the latest GB2 update, I tried to flash the stock recovery (using the stock recovery extracted from the GB1 OTA zip file that I saved from the phone). When I flash the PC36IMG.zip file I created (via VolumeDown-PowerButton boot), it indicates the flash was taken. But, after deleting the PC36IMG file, and trying to re-boot into the stock recovery, it hangs at a RedTriangle-Exclamation screen. I must battery pull. I can re-boot the phone, no problem, but no recovery is possible to get into. Note the phone is still rooted (su runs and shows my su apps). I can re-flash ClockWorkMod, and get back into that recovery, but simply cannot get the stock recovery flashed successfully.
Unrevoked "recommends" going back to stock recovery to accept any OTA. So I've always done that, with no issues until now. I cannot take the OTA GB2 update with ClockWorkMod. It gives the following:
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
Any thoughts on why a stock recovery cannot be flashed now that I am on GB1 when I've never had an issue with this previously? Does it have something to do with now being on hboot 2.16? If so, since I'm unrevoked s-off, can i just go back to hboot 2.10. That image is available on XDA.
Is anyone else here (like me) currently at hboot 2.16, with s-off, and full access into CWM recovery and root?
Thanks in advance.
I have been rooted with unrevoked since soon after the initial EVO release last June. I am also s-off via unrevoked forever. I haven't flashed any dev ROMs, as all I'm primarily interested in is wireless tether, and a couple other root apps.
So, my "strategy" with OTA updates has always been to:
1) re-install the stock recovery
2) take the OTA
3) re-install ClockWorkMod recovery
3) re-install su
4) have a new, root stock ROM.
5) just for good measure, install ROM manager to make nandroids easy, just in case I ever want to try a dev ROM.
The above process is recommended by unrevoked and has worked flawlessly, throughout the Froyo OTA update cycle (two or three updates, if I recall).
And it worked perfect to accept the GB1 update. I did that process, took the OTA and am still rooted, but now on hboot 2.16, still with s-off.
However, in trying to do this same process again, with the latest GB2 update, I tried to flash the stock recovery (using the stock recovery extracted from the GB1 OTA zip file that I saved from the phone). When I flash the PC36IMG.zip file I created (via VolumeDown-PowerButton boot), it indicates the flash was taken. But, after deleting the PC36IMG file, and trying to re-boot into the stock recovery, it hangs at a RedTriangle-Exclamation screen. I must battery pull. I can re-boot the phone, no problem, but no recovery is possible to get into. Note the phone is still rooted (su runs and shows my su apps). I can re-flash ClockWorkMod, and get back into that recovery, but simply cannot get the stock recovery flashed successfully.
Unrevoked "recommends" going back to stock recovery to accept any OTA. So I've always done that, with no issues until now. I cannot take the OTA GB2 update with ClockWorkMod. It gives the following:
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
Any thoughts on why a stock recovery cannot be flashed now that I am on GB1 when I've never had an issue with this previously? Does it have something to do with now being on hboot 2.16? If so, since I'm unrevoked s-off, can i just go back to hboot 2.10. That image is available on XDA.
Is anyone else here (like me) currently at hboot 2.16, with s-off, and full access into CWM recovery and root?
Thanks in advance.
aburgthing
Well-Known Member
I know you say the Unrevoked says to do this convoluted method but it is the strangest thing I've ever heard and I've been flashing ROMs on this thing since it came out. You are dancing extremely close to the line of losing root; actually I'm surprised you haven't.
Why would you want to get back to a "stock recovery" when a custom recovery gives you everything you need PLUS so much more? Within hours every OTA has been rooted and made available to the masses for download. I would be surprised, very surprised if you find an answer to your question because it is a cardinal rule to NEVER accept an OTA under any circumstances. Too much can go wrong if you are running a rooted ROM even if it isn't a custom one that's had changes to it's framework. If you can get into CWM and want to flash the latest OTA, you've got to learn how to flash ROMs from the "custom" recovery. Sorry I can't help with your specific inquiry but I hope you take this sound advise before you end up unrooted or worse with an expensive paperweight.
Why would you want to get back to a "stock recovery" when a custom recovery gives you everything you need PLUS so much more? Within hours every OTA has been rooted and made available to the masses for download. I would be surprised, very surprised if you find an answer to your question because it is a cardinal rule to NEVER accept an OTA under any circumstances. Too much can go wrong if you are running a rooted ROM even if it isn't a custom one that's had changes to it's framework. If you can get into CWM and want to flash the latest OTA, you've got to learn how to flash ROMs from the "custom" recovery. Sorry I can't help with your specific inquiry but I hope you take this sound advise before you end up unrooted or worse with an expensive paperweight.
you can try and install this: PC36IMG_SuperSonic_S_Sprint_WWE_3.70.651.1_Radi..zip
this will give you 2.2 stock rom and recovery. after flash then try and run unrevoked to get you fully rooted.
avalanche420
Lurker
all you have to do is run the 3.70 RUU. it will say booting into bootloader, then it will time out and give you an error. at this time all you have to do is unplug the cord from the phone, and close the RUU and reopen and rerun it again and it will work flawlessly. ive done it a couple times already. this is how you root evo on stock 2.3.3 ota. you have to downgrade to 2.2. dont flash that pc36img file. most people have bad luck with this. the easiest way to be able to root after 2.3.3 ota is the RUU