• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Possible to root after ota update

D

donzi23

Newbie
My wife just got back with her new Thunderbolt and took the latest update before she got home. Is it possible for me to root her phone after the ota.
 
I have the same question...
I just bought the thunderbolt yesterday and I immediately got the OTA update.

I see a lot of rooting options available. Which options are still available to me? I don't want to end up bricking this thing.
 
XDA should update the manual root thread if it is still working. It may still work fine but you never know, at this point I wouldn't advise trying to root your phone.
 
Yeahha said:
XDA should update the manual root thread if it is still working. It may still work fine but you never know, at this point I wouldn't advise trying to root your phone.
Click to expand...

jcase mentioned on twitter that he was out of town,it may be a couple days before he gets a chance to update it. it did say on android police( [Exclusive Download] Leaked 1.70.605.0 Update For The HTC Thunderbolt (No, It's Not Gingerbread) ) that if you were rooted and had to have it,the existing method should still work.

this update is still 2.2.1,and the changes to the firmware are minimal. i imagine the exploits and downgrade will remain the same,and that the only real downside will be that at the end of the process,youll be running rooted mr1 instead of rooted update. if you want to use it before the thread is updated,just make sure you flash a new rom right away thats 1.70.605.0 or newer.

droidi said:
GPS doesn't work? Worked fine on my dinc...
Click to expand...
:confused:

works fine for me on the custom roms,and on the update.
 
Yeah I figured the method would still work but I can't be certain and I don't want to tell some to go for it and the end up with a brick
 
Yeahha said:
Yeah I figured the method would still work but I can't be certain and I don't want to tell some to go for it and the end up with a brick
Click to expand...

i agree completely... you can never be too careful what you reccomend as safe for people.im not criticising what you said,i was just adding what i know about the subject :)

i should have put alittle more emphasis,actually,on making sure that if a person DOES use this before the guide is updated,on the importance of flashing a new rom right away. as long as youre on rooted mr1,your phone is going to want to update. there was a user just a few days ago that used an outdated guide,and ended up on rooted 1.12.605.6 firmware,and when his phone asked him to update,he tried to let it :eek: it sent him into a bootloop and caused a moment of panic for sure. thats why i always point people to the xda guide.

being on older firmeware in itself doesnt harm you,but trying to take an OTA while rooted can. other clockwork recoverys on other devices will let the update harmlessly fail if you try to acept it,but thast proving itself to not be the case here. the guy a few days ago was able to get to recovery and flash a rom,so had a happy ending,but i do remember seeing on another forum where someone supposedly was not able to recover from an OTA that they werent even asked if they wanted to install! :eek: i took it with a grain of salt,but you never know.

so if you want to use the guide before its updated,youve been warned. :)
 
scotty85 said:
i agree completely... you can never be too careful what you reccomend as safe for people.im not criticising what you said,i was just adding what i know about the subject :)

i should have put alittle more emphasis,actually,on making sure that if a person DOES use this before the guide is updated,on the importance of flashing a new rom right away. as long as youre on rooted mr1,your phone is going to want to update. there was a user just a few days ago that used an outdated guide,and ended up on rooted 1.12.605.6 firmware,and when his phone asked him to update,he tried to let it :eek: it sent him into a bootloop and caused a moment of panic for sure. thats why i always point people to the xda guide.

being on older firmeware in itself doesnt harm you,but trying to take an OTA while rooted can. other clockwork recoverys on other devices will let the update harmlessly fail if you try to acept it,but thast proving itself to not be the case here. the guy a few days ago was able to get to recovery and flash a rom,so had a happy ending,but i do remember seeing on another forum where someone supposedly was not able to recover from an OTA that they werent even asked if they wanted to install! :eek: i took it with a grain of salt,but you never know.

so if you want to use the guide before its updated,youve been warned. :)
Click to expand...


I knew what you were saying an the method probably still works but I don't know enough to confirm it will.

Usually custom roms are built to not notice any OTA update, if you were just stock rooted your phone would see an OTA
 
scotty85 said:
jcase mentioned on twitter that he was out of town,it may be a couple days before he gets a chance to update it. it did say on android police( [Exclusive Download] Leaked 1.70.605.0 Update For The HTC Thunderbolt (No, It's Not Gingerbread) ) that if you were rooted and had to have it,the existing method should still work.

this update is still 2.2.1,and the changes to the firmware are minimal. i imagine the exploits and downgrade will remain the same,and that the only real downside will be that at the end of the process,youll be running rooted mr1 instead of rooted update. if you want to use it before the thread is updated,just make sure you flash a new rom right away thats 1.70.605.0 or newer.


:confused:

works fine for me on the custom roms,and on the update.
Click to expand...

I had mentioned this in another thread and someone said it would not allow you to downgrade your software when flashing the upgrade ROM since it would be an older version.

I didn't know for sure, so I didn't argue, but I don't think there would be an issue.

To be safe I agree and would wait until the root thread is updated however.
 
Ibrick said:
I had mentioned this in another thread and someone said it would not allow you to downgrade your software when flashing the upgrade ROM since it would be an older version.
Click to expand...

if im understanding this correctly,it wont be an issue. steps 2 and 3 take care of it so that you can downgrade from whatever firmware youre running to the 1.03.605.10 firmware in order to use the exploits that allow permanent root,unlock the mmc,and write the s-off bootloader.

remember when youre flashing the "upgrade PG05IMG" youre not flashing over the most current firmware,your flashing over 1.03.605.10 downfrade firmware. so pretty much anything that you use is going to be newer,including shipping firmware 1.12.605.6. the only prollem being that you dont want the "upgrade PG05IMG" rooted rom to be older than current firmware,because of the aforementioned potential OTA prollems.
 
scotty85 said:
if im understanding this correctly,it wont be an issue. steps 2 and 3 take care of it so that you can downgrade from whatever firmware youre running to the 1.03.605.10 firmware in order to use the exploits that allow permanent root,unlock the mmc,and write the s-off bootloader.

remember when youre flashing the "upgrade PG05IMG" youre not flashing over the most current firmware,your flashing over 1.03.605.10 downfrade firmware. so pretty much anything that you use is going to be newer,including shipping firmware 1.12.605.6. the only prollem being that you dont want the "upgrade PG05IMG" rooted rom to be older than current firmware,because of the aforementioned potential OTA prollems.
Click to expand...

I spose I should have mentioned this was for an unrooted phone, which doesn't really have anything to do with this thread, and changes things completely, but I'll hijack for a minute cause I'm curious :p.. Basically attempting to flash the OTA MR1 RUU over the OTA MR2 RUU, in case the newer one didn't jive with the phone.

I don't think I've had an Android phone for more than a week without rooting it so I've never attempted it. I would think it would still work though. Essentially you're just flashing an older image of a phone over a newer image of a phone.

Would the upgrade prevent going backwards?
 
Ibrick said:
I spose I should have mentioned this was for an unrooted phone, which doesn't really have anything to do with this thread, and changes things completely, but I'll hijack for a minute cause I'm curious :p.. Basically attempting to flash the OTA MR1 RUU over the OTA MR2 RUU, in case the newer one didn't jive with the phone.

I don't think I've had an Android phone for more than a week without rooting it so I've never attempted it. I would think it would still work though. Essentially you're just flashing an older image of a phone over a newer image of a phone.

Would the upgrade prevent going backwards?
Click to expand...

aaaaaahhh yes that does change things considerably,lol. assuming a non rooted s-on phone, you are correct. the s-on bootloader wont let you backpedal on the firmware versions,it will only let you reflash whatever it is,or something hihger than it. attempting to flash older firmware will stop the downgrade in its tracks with a "main version higher" error.

if by slim chance the phone was a legitimate s-off test phone,you could flash whatever firmware you wanted,tho doing so would overwrite the s-off bootloader so you couldnt do it again :eek: youd need to remove the bootloader from firmware youre flashing in order to preserve s-off.

in order to go back in firmware versions on a stock phone,youll need temp root so you can re-write the misc. image. you can then flash older firware with no "main version higher" error. follow jcases directions here: [HOWTO] Restore to stock for root users and non-root users UPDATED 5/17/2011 - xda-developers just substitute the mr1 file for the 1.12.605.6 firmware file.

not that it matters,really... trying to stay on stock mr1 will result in constant pestering from the phone to update. :eek:
 
just an fyi...

my replacement phone updated itself while i was starting to root it :eek:

the current method worked just fine on the 1.70.605.0 firmware. i didnt even sign in on the mr1 "upgrade". i skipped past the setup,put it in disc drive so i could transfer some stuff to the SD and immediately boot to recovery and flash my rom and the 627 radios.

not tryin to talk anyone who wants to wait for an updated guide not to... just reporting it worked fine for me,for what its worth :)
 
You must log in or register to reply here.
Back
Top Bottom