For anyone who's NOT on a LEAKED version of 2.1, you can still Root.
We have verified that the PB00IMG.zip goes through its checking process, and asks to update. It looks very much like the Root PB00IMG.zip IS able to be flashed over any phones that went from 1.5 to OTA 2.1.
So anyone who's holding back on going from 1.5 to OTA 2.1, for fear that they wont' be able to root, let your fears disappear.
Special thanks to ssgtob1 from AndroidForums.com who bravely tested booting up in HBOOT with the Root PB00IMG.zip on his SD card.
Thank you for your help, and anyone who DIDN'T leak, we STILL have you covered for Root. Go ahead and follow any set of normal directions for 1.5 to root, and you should be all set to Root your phone.
FOR LEAKERS: Some exploits are still being explored. I hope something comes to fruition. You will know as soon as anyone knows. I promise.
Thanks,
Paul
Peed on yet again leaking sucks. All I know is patience is a virtue I will forever remember to have after this phone. Guess im going to update to v3 leak from v1 since cannot update.
edgeupgx said:
Peed on yet again leaking sucks. All I know is patience is a virtue I will forever remember to have after this phone. Guess im going to update to v3 leak from v1 since cannot update.
Click to expand...
Click to collapse
Maybe you should continue to be patient with v1?.....
So, Ive updated to the OTA and did not have root on my 1.5 when I updated. Are you saying that even though I have done this that I can still root? If so, which tutorial/directions should I follow?
Don't worry, two things have been confirmed.
First the OTA will not work with the leaked ROMs installed.
Second, the OTA is exactly the same as the 2.1 leak v3.
This was confirmed on Android-forum by someone that took the time to compare every single file and CRC the binaries. The only difference was that the leaked ROMs use a different bootloader to install as they did and the actual OS and apps are exactly the same so if you got leak v3 you got the OTA.
The OTA won't install because you are already running it. The only down side is you still cannot root, but otherwise you have as good or better than the OTA.
.
So far, I have not come across a cooked ROM for root that does not have bugs or that functions as well as the OTA (which also has a few bugs). I'm hoping that the development will continue or even increase so we will have better ROMs soon.
xtremeskier97 said:
So, Ive updated to the OTA and did not have root on my 1.5 when I updated. Are you saying that even though I have done this that I can still root? If so, which tutorial/directions should I follow?
Click to expand...
Click to collapse
The exact directions, as if you were 1.5. You have a few options. If you have Windows, an easy way to go about it is this:\
http://forum.xda-developers.com/showthread.php?t=661413
The manual method does, literally, the EXACT same thing, it's just a teeny bit more technical, but you learn a lot about your phone in the process (that you wouldn't have learned using the Eris Master Application). If you're pretty technical (or using Mac OSX or Unix or Linux) then I would use the following tutorial (except, if you have Unix/Linux, you don't have to worry about drivers, and it's "./adb" instead of "adb" when you're running commands).
http://forum.xda-developers.com/showthread.php?t=647707
Good luck!
DigitalMD said:
So far, I have not come across a cooked ROM for root that does not have bugs or that functions as well as the OTA (which also has a few bugs). I'm hoping that the development will continue or even increase so we will have better ROMs soon.
Click to expand...
Click to collapse
I must vouch for Ivan's Eris_Official 1.0 being as bugless as the OTA, in my experience. This guy's been cooking ROMs for all kinds of phones for YEARS, and knows what he's doing. 100% clean, looks like stock, and is a lot faster.
http://forum.xda-developers.com/showthread.php?t=652044
Root after 2.1 OTA upgrade from 1.5
OK,
Let me get this straight and understand it crystal clear. Are you saying that an Eris with 1.5 without root can get the 2.1 OTA upgrade and later get root? Has anyone done this? Hoping it's true as I just got the OTA and installed it based on this thread. BTW, 2.1 .......NICE!
Bill
bczygan said:
OK,
Let me get this straight and understand it crystal clear. Are you saying that an Eris with 1.5 without root can get the 2.1 OTA upgrade and later get root? Has anyone done this?
Click to expand...
Click to collapse
Yes it is possible, and yes it has been done. I believe if you got the 2.1 OTA from a stock 1.5, the documented root method will work fine.
If you got 2.1 from any of the three leaks, you are stuck without root.
(Someone correct me if I'm wrong though! )
Add on question about rooting the OTA 2.1
I amn in the process of trying to root from the 2.1 OTA. Am I correct in thinking that following the walkthrough, that I will be replacing the OTA with another ROM which is functionally the same, but not the same exact one? Can I later redo the OTA from a file? Will this eliminate root?
Bill
bczygan said:
I amn in the process of trying to root from the 2.1 OTA. Am I correct in thinking that following the walkthrough, that I will be replacing the OTA with another ROM which is functionally the same, but not the same exact one? Can I later redo the OTA from a file? Will this eliminate root?
Bill
Click to expand...
Click to collapse
Following the walkthrough OR using the Eris Master Application (if you have Windows) will work JUST fine. (even though those things say you NEED 1.5, that's not exactly true, because OTA 2.1 works as well).
Once you Root, put a Recovery on there, then flash a nice ROM from Recovery, you will flash a ROM (like Ivan's Eris_Official_1.0) that has AT LEAST the exact same functionality as the OTA.
Later, if you want, you can follow the method documented on http://www.androidforums.com/htc-droid-eris/ in the All Things Root section, and click on AcidBath's thread, stickied at the top (then scroll about one page down) for DOWNGRADING from Root 2.1 back to Stock 1.5 (yes it is possible), then follow the tutorial for applying the MANUAL OTA update.
This will take you back from Rooted 2.1 back to OTA 2.1, if you should so choose (though I can't think of a good reason why you'd do that).
Once you have root, and you're using things like WiFi tether and so on, I'm guessing you won't go back. But the option IS available. And yes, if you go back to 1.5 then manual OTA, you will lose root, but you can GET IT BACK the same way you're getting it right now.
pkopalek - Very good info.
I'd just like to add that I manual upgraded from 1.5 to OTA 2.1 and hated it,
and found it possible to go from OTA 2.1 back down to 1.5..and I found the
process to be much easier than the manual OTA install.
I'd like to root now but after reading your instructions, (android forums site is
down right now), I'm still confused.
Root after 2.1 OTA upgrade from 1.5
I did the root last night. Took a while, but everything worked good. I now have recovery and can try other ROMS. Not quite sure yet how to access root or use su. But I love the wireless tethering. Using it right now. Used to use a wired tether program but this is better. I did lose all my apps and settings, but will rebuild it all. I don't think I'll use the OTA again. Love having root. Thanks to all who make this possible.
Bill
BlazeD OnE said:
pkopalek - Very good info.
I'd just like to add that I manual upgraded from 1.5 to OTA 2.1 and hated it,
and found it possible to go from OTA 2.1 back down to 1.5..and I found the
process to be much easier than the manual OTA install.
I'd like to root now but after reading your instructions, (android forums site is
down right now), I'm still confused.
Click to expand...
Click to collapse
Rooting, you just follow the directions for Rooting a 1.5 phone. If you're on the OTA, that's fine, if you're on 1.5, that's fine. The directions are 100% exactly the same.
The link I posted above was for DOWNGRADING from Root 2.1 to normal 1.5. Ignore that. Here's where you want to be:
The Eris Master App works GREAT if you have Windows:
http://forum.xda-developers.com/showthread.php?t=661413
Or do the normal manual Rooting method (it's exactly the same thing, just the App does the commands for you, or you do it yourself -- this is the method that I use, every time):
http://forum.xda-developers.com/showthread.php?t=647707
I suggest Ivan's Eris_Official 1.0 for a ROM, instead of 0.8t2 or whatever is suggested in that thread (that thread is kind of old).
http://forum.xda-developers.com/showthread.php?t=652044
bczygan said:
I did the root last night. Took a while, but everything worked good. I now have recovery and can try other ROMS. Not quite sure yet how to access root or use su. But I love the wireless tethering. Using it right now. Used to use a wired tether program but this is better. I did lose all my apps and settings, but will rebuild it all. I don't think I'll use the OTA again. Love having root. Thanks to all who make this possible.
Bill
Click to expand...
Click to collapse
I recommend Ivan's Eris_Official 1.0 for you too. Download and put it on your SD card.
http://forum.xda-developers.com/showthread.php?t=652044
Boot your phone into recovery, do Backup/Restore > nand backup (to back up your phone) then go back to main menu (volume down), Wipe > Wipe factory/data reset, wipe Dalvik Cache (both), back to main menu (volume down), Flash Zip from SD Card, flash Ivan's Eris_Official.
You'll be doing great.
ALSO:
anyone who's rooting and flashing these ROMs should also be flashing the latest Radio that comes with the OTA:
http://forum.xda-developers.com/showpost.php?p=6469408&postcount=113
yeah i rooted from the OTA and it worked fine it just took a bit longer than it should've because i had some trouble doing it on a mac but i figured it out eventually.
just follow the instructions and you should be fine *only if you are the 2.1 OTA or 1.5*
Hi! I'm on 2.1 OTA, and my droid Eris has never been modified in any way at a software or hardware level. I am running HBOOT 1.47.0000. Whenever I use the PB00IMG.ZIP (of which I have checked the MD5 sums) and reboot into the bootloader screen (The one with "HBOOT" and searches for images) I always get "No Image or wrong image!" and am never presented with the option of "push activate" as a result. Any tips? Yes, the PB00IMG.ZIP is in the root of the SD card. I can't really think that I'm doing anything wrong, as I've read the instructions a billion times, and checked every site with instructions, to see if there was any variation in methods.
Any input or tips (other than "don't root your phone" ) would be greatly appreciated!
It Works!!!
I gave up root for the OTA...never again. I'll 2nd (3rd, 4th, etc) if you are on the OTA you can get root. Thank God...so glad to be back. ;-)
Ok so I have what might be a very elementary question. And I apologize in advance if this is not the right thread or just generally a dumb question.
Is there any advantage or disadvantage to rooting from 2.1 OTA vs. 1.5? Also is there any real difference between my phone rooted from 1.5 and my wife's phone rooted from 2.1?
-------------------------------------
Sent via the XDA Tapatalk App
Monkeypuppet said:
Ok so I have what might be a very elementary question. And I apologize in advance if this is not the right thread or just generally a dumb question.
Is there any advantage or disadvantage to rooting from 2.1 OTA vs. 1.5? Also is there any real difference between my phone rooted from 1.5 and my wife's phone rooted from 2.1?
Click to expand...
Click to collapse
As far as I understand it, after rooting, you will have both of the phones on 2.1 rooted.
Related
Hey guys, sorry to bother everyone with another question about the update but there are a few things I could really use clarification on if it's not too much trouble.'
I'm currently on 1.57, gingerbreak rooted, gladi ROM and sbf flashed the hsupa radio. I can't really find anything about what's done in the update so i can't even tell if it'd be worth it for me to update. Will anything happen if I don't update? I didn't have any problems with my iphone when I skipped over 3 or 4 updates...just want to make sure nothing bad will happen.
Next, if I do want to update (which I don't think I will because I'm reading that a lot of people have been having problems with some things) if there a program I can use to save all of my rooted features and re-apply them after I've updated? I read about beforeupdate and afterupdate but I can't find any information about what they do and if they'll do what I'm looking for.
I'm thinking that with this update being buggy, moto will have to roll out another update pretty soon and maybe I should just wait for that one.
Here you go: Release Notes from Motorola
I accepted the update like 30 hours ago, retained root - No problems or issues here! Everything seems to be working fine.
You can use Titanium Backup to backup your user apps, I would recommend NEVER BACKUP/RESTORE SYSTEM APPS because you can get a lot of force closes and stuff.. Thats happened to me in the past.
http://goo.gl/EyexL
If you have the time and the patience, go back to 1.26 and OTA update to 1.83. The majority of the problems your reading about are from phones that are modded and have been altered and then updated. I had similar issues with my phone after the update, much like the others your reading about. Not staying up to date on official updates could leave you in the dark if a new update comes out and you find yourself stuck with a phone that cant be updated (easily). The 1.87 radio works but made my Atrix hot and chewed up battery. Im not saying its going to make a difference for you, With titanium backup and gingerbreak available now, its easy peasy to root and bring your phone back to your liking very quickly.
Beforeupdate and Afterupdate are used to retain root across upgrades. Gingerbreak is easier(click click, launch= rooted)
WiredPirate said:
I accepted the update like 30 hours ago, retained root - No problems or issues here! Everything seems to be working fine.
You can use Titanium Backup to backup your user apps, I would recommend NEVER BACKUP/RESTORE SYSTEM APPS because you can get a lot of force closes and stuff.. Thats happened to me in the past.
http://goo.gl/EyexL
Click to expand...
Click to collapse
so you're saying you updated without flashing back or anything (without changing ANY settings) and you retained everything?
spitefulcheerio said:
so you're saying you updated without flashing back or anything (without changing ANY settings) and you retained everything?
Click to expand...
Click to collapse
That is correct. I was on 1.57 rooted w/ GladRoot, NO MODS. I accepted the update, ran "afterupdate" from the GladRoot .zip. Now I'm on rooted and on 1.83.
EDIT: You cannot use this method btw since you have modded. You have to sbf first.
Dirtburgler said:
If you have the time and the patience, go back to 1.26 and OTA update to 1.83. The majority of the problems your reading about are from phones that are modded and have been altered and then updated. I had similar issues with my phone after the update, much like the others your reading about. Not staying up to date on official updates could leave you in the dark if a new update comes out and you find yourself stuck with a phone that cant be updated (easily). The 1.87 radio works but made my Atrix hot and chewed up battery. Im not saying its going to make a difference for you, With titanium backup and gingerbreak available now, its easy peasy to root and bring your phone back to your liking very quickly.
Beforeupdate and Afterupdate are used to retain root across upgrades. Gingerbreak is easier(click click, launch= rooted)
Click to expand...
Click to collapse
Yeah i know I once I'm updated, I can root again but I've downloaded tons of apps and changed so many settings to get this phone to run exactly how I want. I've spent a good amount of time changing little things here and there and I don't want to lose all of it!
Is there away to retain all of this information through some kind of backup or something? I have all my apps and user data backed up with TiBackup. If I go back to 1.26 and then update to 1.83, can i restore using TiBackup?
im not too keen on titanium backup other than how to use it for the most part lol. The static phone settings will be defaulted to shipping state if you go back to 1.26. there may be a way to do what you are trying but that's out of my league. These is a setting in Titanium to transfer phone settings across Rom's but i've never tried nor have i seen it on the Atrix Forum. (I never really looked for it, didnt need it, so there may be a thread on it.)
The fact that you have Gladiatrix Rom throws a wrench into the whole easy update thing. Check This if you havent already----- http://forum.xda-developers.com/showthread.php?t=1063618
same here i have no problem
WiredPirate said:
That is correct. I was on 1.57 rooted w/ GladRoot, NO MODS. I accepted the update, ran "afterupdate" from the GladRoot .zip. Now I'm on rooted and on 1.83.
Click to expand...
Click to collapse
Exactly what I did and everything is working fine. Ran afterupdate after the 1.83 OTA and things are working great~! everything retained
So, I am new to this site and to the android community. I apologize if I sound stupid to any of you but if you aren't going to help I'd appreciate it if you just ignored me.
Anyway, I got my Atrix a couple days ago on AT&T and started learning about rooting and such. Everything on it is still stock, last night I upgraded to Gingerbread from Froyo and I'd just like to know if there's any specific rooting program, method I can use right now for 4.5.91 Also, when I upgraded I lost my music player widget, is there I can get it back without going back to Froyo?
Follow the procedure in the second link in my signature. Since you had root before you updated go into settings manage applications clear app data for superuser.
Sent from my MB860 using XDA App
phobos512 said:
Follow the procedure in the second link in my signature. Since you had root before you updated go into settings manage applications clear app data for superuser.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
will there be any severe consequences if I screw up?
Use gingerbreak.
Sent from my MB860 using XDA App
TheToiletSpaula said:
Use gingerbreak.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I've read that gingerbreak doesn't work with this version. I'll look it up though.
phobos512 said:
follow the procedure in the second link in my signature. Since you had root before you updated go into settings manage applications clear app data for superuser.
Sent from my mb860 using xda app
Click to expand...
Click to collapse
^^^^^ only way to root gb and probably the best way if there are other methods
savier420 said:
^^^^^ only way to root gb and probably the best way if there are other methods
Click to expand...
Click to collapse
cool, just one question. Am I supposed to have the device connected to my computer the whole time? and if not between which steps should I connect/ disconnect it? also, when I put the root.img in the C: folder, do I put the zip file or just the .img inside of it?
phobos512 said:
Follow the procedure in the second link in my signature. Since you had root before you updated go into settings manage applications clear app data for superuser.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
If you are just trying to "root" your phone only, YES, this is the best method.
Thanks for posting this and providing the link in your signature. I was crapping myself reading the other post about how the new updates bricks your phone but no one said if you are just looking to root your stock OTA's you'll be fine. So, thanks again. They should sticky this under "If you are just running stock and want to root without unlocked BL/pudding use this"
PSY0NIC
PSY0NIC said:
If you are just trying to "root" your phone only, YES, this is the best method.
Thanks for posting this and providing the link in your signature. I was crapping myself reading the other post about how the new updates bricks your phone but no one said if you are just looking to root your stock OTA's you'll be fine. So, thanks again. They should sticky this under "If you are just running stock and want to root without unlocked BL/pudding use this"
PSY0NIC
Click to expand...
Click to collapse
Since this is the 1st time I've seen some one say it this way....
If you are just trying to "root" your phone only, YES, this is the best method.
Brand new phone, all stock... just want root.... use gingerbreak?
Sent from my MB860 using XDA Premium App
Hi all,
Renaissance613, can you post if you had success and if you ran into any problems? I have the same setup as you (2.3.4/4.5.91) and I'm nervous about rooting so soon after the update (I just installed it).
Also, I'm wondering if I will have to undo this root when another automatic update gets pushed down, or if it will just unroot like my gingerbreak root did. I don't have/intend to use any ROMs. I like stock phone with phone-pulled updates and rooted.
In any case, thanks for the link phobos512 - and thanks to this community of developers and users. You guys are awesome.
Hambone~
hambone123 said:
Hi all,
Renaissance613, can you post if you had success and if you ran into any problems? I have the same setup as you (2.3.4/4.5.91) and I'm nervous about rooting so soon after the update (I just installed it).
Also, I'm wondering if I will have to undo this root when another automatic update gets pushed down, or if it will just unroot like my gingerbreak root did. I don't have/intend to use any ROMs. I like stock phone with phone-pulled updates and rooted.
In any case, thanks for the link phobos512 - and thanks to this community of developers and users. You guys are awesome.
Hambone~
Click to expand...
Click to collapse
I'm about to try it but I'm still confused about a few things like when exactly to connect or disconnect my phone and what to do after I've entered all the commands on my computer, will it install by itself? This is my first time rooting a phone, and my first time even owning an android so I want to make sure I know exactly what I'm doing
I hear you man, it's nerve wracking to worry that you're going to brick your phone. I did the gingerbreak on the last release and it worked perfectly. I'm sure this method will work fine as well, as you said I just want to be sure I'm doing the right thing for my goal: stock phone/downloaded updates/rooted. Best of luck, and thanks to anyone who gives us noobs some more reassurance.
this is by far the best method to root on gingerbread, but i dont see any reason to root but to only flash custom roms, i only needed root pre-GB to allow non market apps, and the new GB OTA UPDATE allows non market apps, so im pretty happy with wat i got, before i updated to the OTA GB i had BL unlocked and rooted, just flashed back to 1.2.6 to be rid of root and unlocked BL, then just went throught the OTA updates to get to GB and im loving it, dont really care to flash any other custom roms, BUT BEWARE DOING THE OTA TO GB AND UNLOCKING THE BL THEN TRYIN TO FLASH BACK TO A STOCK ROM WILL HARD BRICK SO DO YOUR RESEARCH so if u dont want a hard bricked phone dont do the ota stick to custom roms and ignore all OTA'S
so I got through the fastboot reboot command, phone booted back up automatically, then put the phone into debug. Then typed in the adb shell code and said the specified path could not be found.
Now I was still in the command prompt that said the c:/root
What did I do wrong?
So, adb says it is a bad path?? Do this instead..it is easier and it works -- I did it this way last night!
After "moto-fastboot reboot", once your phone has completely rebooted, go to the Android Market and download and install "Terminal Emulator." Once it is instslled and you have opened it, enter the EXACT SAME commands that you were going to type into the Adb Shell..once again, type in the commands VERBATIM. After the last command, there should be a message saying (in terminal emulator) that it was successful! Congrats, you have achieved root access on the AT&T issued stock Gingerbread 2.3.4 build! I hope it works for you!
~Eric
savier420 said:
this is by far the best method to root on gingerbread, but i dont see any reason to root but to only flash custom roms, i only needed root pre-GB to allow non market apps, and the new GB OTA UPDATE allows non market apps, so im pretty happy with wat i got.
Click to expand...
Click to collapse
I'm very vanilla. I root pretty much entirely for free wireless tethering and being able to delete bloatware.
Hello everyone, I am still a little confused between what will or what will not brick my phone. I appreciate your responses.
I am still in froyo 2.2.2 (firmware 1.8.3), rooted using GladRoot method (rooted in previous firmware, then upgraded to 1.83 and used the AfterUpdate.bat.
I am afraid to do the updrade to GB because after reading a looot of threads here on this I am completely confused on what will brick my atrix and what not. If I upgrade to GB OTA, will that brick my phone? if it doesn't brick it, what does? if I upgrade to GB OTA will I able to root it? what method should I use?
thanks a lot
aroca1978 said:
Hello everyone, I am still a little confused between what will or what will not brick my phone. I appreciate your responses.
I am still in froyo 2.2.2 (firmware 1.8.3), rooted using GladRoot method (rooted in previous firmware, then upgraded to 1.83 and used the AfterUpdate.bat.
I am afraid to do the updrade to GB because after reading a looot of threads here on this I am completely confused on what will brick my atrix and what not. If I upgrade to GB OTA, will that brick my phone? if it doesn't brick it, what does? if I upgrade to GB OTA will I able to root it? what method should I use?
thanks a lot
Click to expand...
Click to collapse
Updating to GB won't brick your phone. After updating to GB you can't down grade to older OS (like the one your on right now) that would brick your phone. So as long as you don't plan on going back to a past OS version (and I don't know why anyone would) you'll have no problems at all. As for Rooting >follow this link< and follow the instructions there after you update to GB. It works perfectly, you don't have to unlock your BL or anything else like that to just have Root on GB. Hope this helps.
Thanks!!! That was the response I was looking for
Now, what method should I use if I were planning to unlock the bootloader?
Also, if something goes wrong and I need to reinstall the upgrade (or better, flash with GB again with a spf file) will that not brick by atrix either?
For Questions about BL Unlocking
aroca1978 said:
Thanks!!! That was the response I was looking for
Now, what method should I use if I were planning to unlock the bootloader?
Also, if something goes wrong and I need to reinstall the upgrade (or better, flash with GB again with a spf file) will that not brick by atrix either?
Click to expand...
Click to collapse
Click on the link below, that thread will give you the answers and files your looking for.
> Click Here <
Hey everyone, I am new to the rooting world however I have only experienced good things. I decided to root my thunderbolt using TB Autoroot+htc sync last night(had the original stock froyo, was going to installed cyanogen mod 7) and was successful. Unfortunately, I then installed the leaked 2.3.4 RUU GB which rerooted my TB before I installed the cm7(wanted to try the RUU out, bad idea lol). I was wondering if all or any of these are possible (dont care about losing data, just don't want to brick, ie avoiding command lines if possible):
1. root the phone while maintaining the leaked 2.3.4 RUU, just as was done for FROYO? Original reason for rooting was to remove the bloatware apps, but not having custom roms would be ok at this point if that is this is the only option. I know there is the revolution method to root, however will that work on the leaked 2.3.4 RUU?
2. root the tb with my current 2.3.4 RUU and install the BAMF 2.3.4/sense 3.0 GB build, or some other custom 2.3.4 rom?
A tutorial or walk through would be great! I know there are some out there, however I am looking for one specifically for those that have the leaked 2.3.4 RUU on the thunderbolt.
Also, can someone explain the difference in features of the GB builds that have been out for some time(customs) vs the RUU by verizon? I'm not talking about the physical aspects or the apps that come with, but more in terms of installing/switching between them. I know I need to root in order to install the custom roms, but assuming i can root the 2.3.4 RUU, will I be able to install any other 2.3.4 rom such as BAMF or cyanogen without problems? I have heard that you just arent allowed to go backwards, ie back to Froyo one you update to GB, but I should be able to install any 2.3.4 GB ROM once rooted via the bootloader(power+volume down) True?
Any help would be great! Thanks!
Yes you can. Just use revolutionary to root the new GB build. Here is a video tutorial for you.
Well, here comes your first less than pleasant reply...
Pretty much everything you wanted to know is posted in my thread stickied in the Q&A section. That's also where this post is going to end up. Please check my thread on basic noob questions, search before posting, and post in the correct forum.
Ota update after root
I just got this thunderbolt replacement in the mail. I noticed OTA was trying to update so I hurried and pulled the battery to intterupt the update since it was in the version I needed to be to ROOT. Ok I went ahead and ROOTED the phone then updated my RADIO (wich by the way is a big difference without it, it wont stay in 4g) ok so I think im good to go when I see the phone is trying to do a FIRMWARE update again, I dont know if this will ruin my root or phone so Im in airplane mode till I find out what to do. I dont know how to turn off automatic update and I dont want to mess up my root or phone. WHAT DO I DO PLEASE HELP!!!
Jeovanny said:
I just got this thunderbolt replacement in the mail. I noticed OTA was trying to update so I hurried and pulled the battery to intterupt the update since it was in the version I needed to be to ROOT. Ok I went ahead and ROOTED the phone then updated my RADIO (wich by the way is a big difference without it, it wont stay in 4g) ok so I think im good to go when I see the phone is trying to do a FIRMWARE update again, I dont know if this will ruin my root or phone so Im in airplane mode till I find out what to do. I dont know how to turn off automatic update and I dont want to mess up my root or phone. WHAT DO I DO PLEASE HELP!!!
Click to expand...
Click to collapse
If you are rooted, just use a program like root explorer to search for a file called otacerts.zip and rename it to otacerts.bak
When you open root explorer, make sure to put it into write mode. look at the top left side of the program and press on the mount r/w option
Cant find rom
I want to flash rom but I cant find it in my sd card through rom manager and also through recovery any suggestions its in the root of the phone highest directory
Jeovanny said:
I want to flash rom but I cant find it in my sd card through rom manager and also through recovery any suggestions its in the root of the phone highest directory
Click to expand...
Click to collapse
If you used your phone to download a rom, its in the "download" folder, move it to the root of sd card
Sent from my ADR6400L using XDA App
Root Error
I am trying to Root my Thunderbolt but keep getting the following error:
Failed to get Root!
I am using revolutionary.
I have installed, made sure their was a connection, and then removed HTC Sync.
I downloaded and installed Android USB Drivers.
I selected USB Debugging
Thunderbolt Info:
HBOOT 1.04.000
Android 2.3.4
ROM Ver 2.11.605.9
What am I missing and where can I get it? Can anyone help me out with this? Thanks in advance...
I've never rooted but I believe you need to downgrade. Revolutionary does not work with the latest OTA. There are several posts around that explain how to downgrade to the previous OTA (link below). Then you should be able to use the revolutionary method.
http://forum.xda-developers.com/showthread.php?t=1401959
Sent from my Thunderbolt using Tapatalk
Yes you need to downgrade to 2.11.605.5 then use reveloutionary
So I have a completely original Neo, still on the on the original Gingerbread (2.3.3) it had and I don't quite know how to proceed.
The only thing I do know is that if at all possible I don't want to unlock the bootloader.
Ideally I want to back everything up before I do anything but from my understanding Titanium Backup needs root to back everything up so that creates a bit of a catch 22. Similarly installing CWM so that I can access recovery is risky and could break everything so I'd want a backup first but for that I need either root or recovery so another catch 22. So what would be the safest option?
Also I want to update to ICS, I figure it's about time I get my phone current, but I don't know in what order I should do that in either...
Should I gingerbreak my Gingerbread and then update to ICS?
Should I just update to ICS and then root?
Should I upgrade using generic firmware to a version supporting the zergRush root, then root and then continue updating to current ICS?
I'm fairly confident I can get everything right first time on any method (and I know what all the methods are/am to not to lazy to research the methods myself) but I just can't figure out the safest course of action here...other than staying on Gingerbread for the duration of my phone contract.
Any help you can give me is appreciated.
Start by reading the stickies in the development section, do some reading and you'll know
look at the stickies in neo v section too
Ok so you're saying I should follow the "noob's guide" exactly and try a zergRush Root first? (Skip unlocking the bootloader since it'm not interested in cutoms roms with custom kernels) and then install CWM and make a nandroid backup?
Ok....but that still doesn't tell me whether I should update first or root first?
Also I can't seem to tell from it's thread whether the zergRush root works on the latest ICS (I don't see mention of .431 in the thread with .62 apparently being the last version that worked so that would be a no then?)?
Also my case is different because I could actually even still root with Gingerbreak if that was best/safest unlike most people trying to root (I never downgraded either so I wouldn't be exposed to the 0% issue).
ZergRush method doesn't work on fw's after .42.
There is another method, which you can find in sticky thread in general section.
First update, then root, as root is gone after flas/update.
p.s. whatever you do, just don't flash android 2.3.2 on your phone after you flash 2.3.4, but there is no really point in going to that old fw, same as there is no point in still being on 2.3.3.
Root is only gone if I don't update OTA
SCHUMI_4EVER said:
Root is only gone if I don't update OTA
Click to expand...
Click to collapse
Really? Thanks for telling me that..
I know that, I also know that you can't update from 2.3.3 to 4.0.4(which you said it's your initial goal, in your first post) via OTA. Or you can?
As far as I know I can but I admit I haven't checked yet. I don't see why once it's available for my region through the PC Suite it shouldn't also be available OTA.
Try and let us know.
It's not same if you're updating from x.x.x to x.x.y and from x.x.x to y.y.y, in first case OTA is possible, in second case I kinda doubt
I also didn't try, but if I remember correctly that's how it is.
Yeah but surely it should then just be 3 steps? So from x.x.x to x.x.y to y.y.y...that would would make sense to me anyways
Still reading up on a bit of other stuff then I'll check
http://forum.xda-developers.com/showthread.php?t=1973017
hope it helps..
Greetings,
I know the easy answer to this is going to be to flash a new rom, but if I wanted to do that I would have already. I'd rather find and repair the source of the issue and learn from it.
That being said, shortly after getting my tbolt (when they were first released) I used the revolutionary root and added in VPN software for work. Being unaware that OTA updates hadn't been blocked during the rooting, the phone took an update and went into a death-boot-loop. I found a clean updated OTA rom, flashed and unrooted the phone as the VPN software didn't work well for what I intended anyway.
Great, now the phone is all back to stock (or so I thought).. After a while, another OTA update came down, it asked to update, I allowed, and it said update failed.. Repeat ad nauseum for the next several weeks. Since I was happy with the way the phone was operating, I didn't care if it got the updates or not.
So last week, I decided that since the phone is out of warranty anyway, I might as well root and get rid of some of the bloat, and while I'm at it, get rid of the damn nag screen every tine I hook it to a computer. Searched around, found thunderbolt tool 1.0.1, downed it and tried it out, and it proceeded to say unable to lock my phone.
After a little screwing around, the "update status" on the phone itself reports ROM Version: 2.11.605.9, while the tool was getting a response of 2.11.605.5, so it was using the wrong method to get into the phone. So I edited the batch file to use the .9 method no matter what it reported back, and it proceeded to root, add the recovery, and superuser.
Ahhh, life is good, the phone is rooted again, time to start doing my own customization.
Except that after a couple reboots, everything loses the root rights.
Running titanium backup says "asking for root rights" and then "titanium has been granted superuser permissions" but it just hangs there at the "asking for root rights" screen.
Wireless tether similar story... Start the app and it says "press to start tethering" and touching the screen gets "wireless tethering has been granted superuser permissions", then hangs at "please wait while starting".
Won't do anything that requires root, unless I run the tool again and select "S-off but no root", and it will go through a procedure and root will work again for a while.
Also, as I'm typing this, I discovered that it doesn't necessarily require rebooting to lose root. I had root working last night, but when I picked up the phone to get the proper messages to type, it is not showing root again, and it hasn't been rebooted since root was working.
Thoughts on how to repair this without flashing a rom?
Have you attempted to run the "fix permissions" option in your recovery?
If that does not help, You could use something like OTA RootKeeper to protect root, if you loose it you would just click one button to get it back.
Last thing I can think of is to just reflash the same ROM you are using now on top of what you have so you loose no data and any messed up settings or files will be rewrote.
**edit**
You should really think about installing a custom ROM, because until you do, or you block OTA updates, this will be a reoccurring issue.
You could easily install a stock rooted ROM of the exact same thing you have now. nothing would change except it would be properly rooted and OTA updates would be blocked.
That is because only temp root is applied to the official 605.19 Ruu. You need to downgrade back to 605.5 after getting temp root on the 605.19 Ruu then apply the perm root zip in recovery and then flash a newer rom from recovery. If that doesn't work don't lose hope. I may be misunderstanding the situation you have but it sounds like you're only applying temp root. The tool doesn't need to be edited and you may need to flash the 605.19 stock Ruu, relock and s on and then run the tool again.
Sent from my ADR6400L using Tapatalk 2
Milimbar said:
Have you attempted to run the "fix permissions" option in your recovery?
If that does not help, You could use something like -edit- to protect root, if you loose it you would just click one button to get it back.
Last thing I can think of is to just reflash the same ROM you are using now on top of what you have so you loose no data and any messed up settings or files will be rewrote.
**edit**
You should really think about installing a custom ROM, because until you do, or you block OTA updates, this will be a reoccurring issue.
You could easily install a stock rooted ROM of the exact same thing you have now. nothing would change except it would be properly rooted and OTA updates would be blocked.
Click to expand...
Click to collapse
Haven't seen the fix permissions option anywhere I've been, care to point me in the right direction?
I'll check out the rootkeeper.
disconnecktie said:
That is because only temp root is applied to the official 605.19 Ruu. You need to downgrade back to 605.5 after getting temp root on the 605.19 Ruu then apply the perm root zip in recovery and then flash a newer rom from recovery. If that doesn't work don't lose hope. I may be misunderstanding the situation you have but it sounds like you're only applying temp root. The tool doesn't need to be edited and you may need to flash the 605.19 stock Ruu, relock and s on and then run the tool again.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Never took the .19 update, and both the tool and phone report as .05 now. (if I remember correctly the .09 reverts back to .05 to get in)
damm315er said:
Haven't seen the fix permissions option anywhere I've been, care to point me in the right direction?
Click to expand...
Click to collapse
What recovery are you using?
I only use 4ext and would recommend that.
The fix permissions will take up to 5 min and may not help your particular issue, but shouldn't hurt to try.
If 4ext - Boot into recovery, select tools then select fix permissions.
If CWM I think its in the advanced menu.
and If TWRP I think it is in the advanced menu again.
Good luck and listen to the others here, they go out of their way to help people a lot
Ok earlier I misread your post. I thought it said 605.19. Still though something you're doing is causing you to only get temp root. Reread the op of the allinone tool and make sure you meet the requirements before you start it. That away when you run it this time you are in the best possible situation for it to work. Trter is very helpful and if you post your issue in his thread he will probably assist you with anything you need.
Sent from my ADR6400L using Tapatalk 2
I remember having a similar problem about 6-7 months ago.
I would randomly loose root, though not as often as he is describing.
In my case it was a combination of an outdated root method and a flawed ROM.
If everything he is using is current, including the ROM, he shouldn't have an issue.
If it were me I would flash Santod's stock deodexed ROM and be done with it.
It is the stock ROM with nothing changed except it is prerooted.
I understand that you would like to "fix" this issue without flashing a ROM, however the ROM itself could be the problem. this solution is the simplest I can think of.
Using everything from the thunderbolt toolkit, so yes, 4ext.
Found and ran the fix permissions, ran for 15 minutes before it finished so we'll see how it goes.
I get what you're saying about the rom being screwed up, and am starting to think my only choice is to reflash it, so I'll start looking into a new rom.. That being said I'm still pursuing fixing this until I find a rom that serves my purpose.
Is there a good stable ICS for thunderbolt, pre-loaded with root and good battery life?
Yea the one in the post above yours. If you want something a that is faster and has better battery than it then head over to infectedrom.com and check out all the different options santod has made.
Sent from my ADR6400L using Tapatalk 2