Related
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.
Back when the 2.1 leak was out I decided to update my wife's Eris to 2.1. I installed the 2.1 rooted leak, and that is what is currently on there. It has some issues that she would like resolved, so I figured I would go ahead and actually update to the latest ROM.
However, it's been so long since I have even checked into the process I can't remember if there are any issues going from the leaked and rooted 2.1 to the 2.1 release. I remember some issues with a baseband version not allowing updating to the legit 2.1, if anyone could offer advice as the next step to take that would be awesome.
Current baseband on the phone is 2.40.00.01.22
I hate even asking, but my head is so full of everything else right now I just want to get it to a more usable state for her.
Thanks!
The baseband version you report is consistent with installing the "Root PB00IMG.zip" file (with HBOOT).
That 2.1 ROM was incredibly buggy. Moreover, it never received any OTA updates, so it is still as buggy as they day it was leaked.
I suppose that since you still have that ROM on the phone, you never installed the Amon_RA (custom) recovery boot. You are going to need to learn how to do that; but first, read on.
Here's the deal - the "Root" PB00IMG.zip ROM used the Engineering (S-OFF) bootloader, which had a version of 1.49.2000; whereas, the "leak" ROMs that came out after that (leak-V2 and leak-V3) used the 1.49.0000 bootloader.
That means that you can not simply apply the Leak-V3 ROM or the "Official" (MR3?) RUU, without first applying the (jcase) "Flash Any RUU" method. The simplest way to do this involves using Amon_RA recovery ... which (I guess) you don't have on your phone yet.
Here's the good news, though: The (jcase) "One Click" root will install the Amon_RA recovery for you - in a way which is tremendously easier than the old-fashioned way of doing it. I am pretty sure that it works with the Root-2.1-Leak ROM.
So, there you go - "root" your already rooted phone using the "One Click" method from jcase, and then from there learn how to install custom ROMs. You can either do that (choose a stock-like custom ROM such as xtrSense), or you can install the "FlashBack15 v1" ROM, which will unroot your phone and return it to the most recent stock version of 2.1 via OTA. From there you can re-root the phone using ANY method.
Note that I did not give you a complete step-by-step, but an outline instead. Step-by-steps are available in each of the respective threads. A useful guide to using Amon_RA (with pictures) is available here on AF
bftb0
So i had rooted my amaze earlier and every thing was great removed my bloat and went along my way, since the 12th my phone kept telling me it had the update to do so i clicked install but since clockwork was my recovery the phone did not want to do the update so. i decided to unroot my phone and try to restore but nothing seemed to be the same can some one help me out i cannot get su-2.3.6.3-ef-signed.zip to run right to root. All i know about this stuff is how to follow directions so
Ok, I know there are a lot of posts already on updating to 2.3.6 and root, but there appears to be a lot of different situations and limited information that is causing me some confusion.
So, what I want to do is get some clear details about probably the second most common situation: A Motorola Atrix 4G running the stock ROM with root access and an unlocked bootloader.
With regards to updating, aside from the obvious actions (i.e. TiBu, maybe a Nandroid), is there anything else that needs to be done to perform the update?
Additionally, I would like to keep root/unlocked even with the update, but I am willing to re-do root after the update. I can't find clear information on what methods work to keep root or to restore root after updating.
That is pretty much all that I am trying to do. I can not afford to brick my phone, so I want to make sure that I understand everything before I update.
P.S. Curse Motorola and it's stupid locked bootloaders!
I'm in the same shoes and looking to do the same thing...I want to keep root, not brick my phone...Apply the 141 update. I don't mind a little work (re-root, re-modify some files)
I'm running an unlocked bootloader, AT&T Atrix with 4.5.91 which is rooted with some custom changes (tethering, 2g/3g toggle, unlock APNs, agps)
Seems it could be possible to rebuild Blur_Version_91.4.5.141.MB860ATT.en.US available from Motorola and exclude the bootloader portions to keep the phone from bricking?
psychephylax said:
I'm in the same shoes and looking to do the same thing...I want to keep root, not brick my phone...Apply the 141 update. I don't mind a little work (re-root, re-modify some files)
I'm running an unlocked bootloader, AT&T Atrix with 4.5.91 which is rooted with some custom changes (tethering, 2g/3g toggle, unlock APNs, agps)
Click to expand...
Click to collapse
Yeah, I used the script that applied the tethering/hotspot tweak. That's about it. I haven't had to use any agps or anything, it's got amazing gps as it is.
Glad I'm not the only one though
If you have a stock rom unlocked bootloader with root don't do the ota update.I just soft bricked my phone.
Sadly, I did just that. I just wasn't paying attention.
Update: resorted to a factory reset. Now I have 2.3.6 running. Just going to take some time to restore my apps and settings.
Looks like I'm in the same boat. What's the best way to recover from a soft-brick in this situation?
thatguy193 said:
If you have a stock rom unlocked bootloader with root don't do the ota update.I just soft bricked my phone.
Click to expand...
Click to collapse
Yeah, this is exactly why I have asked. I read at least one post somewhere where someone tried both the SD Card and the OTA update and the SD didn't work, but the 2nd OTA try did. I don't know if they said they had unlocked or not.
Johnston212 said:
Yeah, this is exactly why I have asked. I read at least one post somewhere where someone tried both the SD Card and the OTA update and the SD didn't work, but the 2nd OTA try did. I don't know if they said they had unlocked or not.
Click to expand...
Click to collapse
Well I found this threadhttp://forum.xda-developers.com/showthread.php?t=1498856 was trying the auto updater as suggested but my phone wont stay on long enough for it to work.It does the auto shutdown and tries re-installing the OTA update which gives me the android triangle guy.
I recently made an update of my Atrix 4G's System from 2.3.4 to 2.3.6.
My 2.3.4 version was unlocked and rooted. It is on ATT.
Initially I received a notification in my phone about the new System update available. I tried three times OTA, but each time the process failed. When it was booting up always gave me the Android Icon with an Exclamation mark inside of a triangle. But nothing else happens. My phone continued working but with the 2.3.4 version.
Then I went to this page:
Because I haven't less than 8 post in this site I can't post any URL.
But, go for the "Motorola software update" in the Motorola's web page or Google it and get it.
And installed the "Motorola Software update" application. I had to restart my PC in order to make the software to recognize and connect to my Atrix 4G. When the Atrix was connected, by USB port, I had to select the "Windows media Sync" in the USB connection options list to make the connection to work.
Then, all that I had to do was wait until the process got completed.
I hadn't see nothing different with the new update.
I conserved my "unlocked" condition but I lost my "Rooted" condition. But that is not a big issue, there are several thread in the web that help you to get rooted again.
Hope this can help, It works for me.
cjfermin said:
I conserved my "unlocked" condition but I lost my "Rooted" condition. But that is not a big issue, there are several thread in the web that help you to get rooted again.
Hope this can help, It works for me.
Click to expand...
Click to collapse
You have an unlocked bootloader? Or sim-unlocked phone?
I'm in the same situation of @cjfermin and the 2.3.6 was flashed without any problem.
Of course I've lost ROOT, but I've followed simple instructions on the web (using Fasboot) and I've re-rooted the Atrix in 3 minutes.
PS: my Atrix was/is sim-unlocked and with unlocked bootloader.
emandt said:
I'm in the same situation of @cjfermin and the 2.3.6 was flashed without any problem.
Of course I've lost ROOT, but I've followed simple instructions on the web (using Fasboot) and I've re-rooted the Atrix in 3 minutes.
PS: my Atrix was/is sim-unlocked and with unlocked bootloader.
Click to expand...
Click to collapse
Thanks, that is exactly what I was needing to find out. I've heard yes and no's on different re-rooting methods. Could you link the one that you used? I was thinking about using Gingerbreak or OneClickRoot
I was trying to apply the OTA 4.5.141, on my rooted AT&T Motorola Atrix stock rom 2.3.4 and after the first reboot, following the instructions from the update, I am getting the message “failed to boot 2 starting rds mode” and just sit there. After removing the battery and booting up again, the phone seems to booting up normally and then when the phone finishes loading most of the widgets, I get a message saying “turning off” and the same cycle keeps repeating.
This is my primary phone and I am really desperate right now and I do not know what to do.
Please I need some help,
Johnston212 said:
Could you link the one that you used?
Click to expand...
Click to collapse
Here: http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/
Hope that helps you!
Alverik said:
I was trying to apply the OTA 4.5.141, on my rooted AT&T Motorola Atrix stock rom 2.3.4 and after the first reboot, following the instructions from the update, I am getting the message “failed to boot 2 starting rds mode” and just sit there. After removing the battery and booting up again, the phone seems to booting up normally and then when the phone finishes loading most of the widgets, I get a message saying “turning off” and the same cycle keeps repeating.
This is my primary phone and I am really desperate right now and I do not know what to do.
Please I need some help,
Click to expand...
Click to collapse
Ok, is your bootloader unlocked as well? I googled the "failed to boot 2 starting RSD mode" that you mentioned and there are a number of posts on it from over the years. It seems that you may need to flash a SBF file, but I don't know enough about your situation to competently tell you more than that.
Johnston212 said:
Ok, is your bootloader unlocked as well? I googled the "failed to boot 2 starting RSD mode" that you mentioned and there are a number of posts on it from over the years. It seems that you may need to flash a SBF file, but I don't know enough about your situation to competently tell you more than that.
Click to expand...
Click to collapse
I am on stock rom 2.3.4 and have only rooted my phone nothing else. It seems that because it was a rooted phone the update could not finish the process.
Now I don’t know what to do.
Should I try to flash to 2.3.4 using RDS lite and then update using OTA 4.5.141 or flash using 4.5.141 (I don’t know where to find it)?
Help please, this is my only phone.
Alverik said:
I am on stock rom 2.3.4 and have only rooted my phone nothing else. It seems that because it was a rooted phone the update could not finish the process.
Now I don’t know what to do.
Should I try to flash to 2.3.4 using RDS lite and then update using OTA 4.5.141 or flash using 4.5.141 (I don’t know where to find it)?
Help please, this is my only phone.
Click to expand...
Click to collapse
If the only thing you've ever done to the phone is root then flashing the official 2.3.4 (not fruitcake) with RSDlite and then applying the 141 OTA update should be ok. Things to note:
1) Make sure the phone is fully charged
2) Apply the 141 OTA update from sd card. Go to motorola's website . I've had mixed results when applying previous updates when downloading over wifi.
3) Be VERY sure you've done nothing else to your phone other than root, i.e. unlock, mess with the bootloader and/or recovery (unlock, ROMs).
gnahc79 said:
If the only thing you've ever done to the phone is root then flashing the official 2.3.4 (not fruitcake) with RSDlite and then applying the 141 OTA update should be ok. Things to note:
1) Make sure the phone is fully charged
2) Apply the 141 OTA update from sd card. Go to motorola's website . I've had mixed results when applying previous updates when downloading over wifi.
3) Be VERY sure you've done nothing else to your phone other than root, i.e. unlock, mess with the bootloader and/or recovery (unlock, ROMs).
Click to expand...
Click to collapse
The only thing that I have done other than rooting my phone it’s unlocking the sim card.
I don't have a SIM unlocked phone, so I can't with 100% certainty say you will be ok. You should be fine though. Maybe others with SIM unlocked phones will chime in.
gnahc79 said:
I don't have a SIM unlocked phone, so I can't with 100% certainty say you will be ok. You should be fine though. Maybe others with SIM unlocked phones will chime in.
Click to expand...
Click to collapse
I am not able to copy the update file to the SD card because I get a message saying “turning off” a little bit after the phone loads the sd card and then I get the "failed to boot 2 starting RSD mode" and after that the only way to take it out of that mode, it’s by removing the battery.
What options do I have now?
Thank you,
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