I did the forever root and updated to .893 no problem. i decided however to flash back to stock so i could flash the new Liberty RC1 rom. When using oneclick fastboot restore my phone was restored back to .886 however i am unable to acheive root now. i noticed during the fastboot restore it failed to flash boot.img. and now petes motorola root tools fails on step 3 every time. im guessing this is because of the mod in the data file that prevented the .893 update from breaking root. trying to restore using RSDlite with the full FXZ restore file but i fails immediately every time. this is nothing urgent since my phone is working just fine, i just want my root access back!!!! any advice or solutions would be greatly appreciated and be careful with the forever root. before flashing anything after doing it go back and change the file to modified back to its original or you will most likely lose any permission to the boot.img or whatever the hell boot file it is.
this is the same problem im having.. it sucks i cant acheive anything now .. anyone know how to get root back?
Just found this last night....I was in the same boat, fixed mine.
rootzwiki.com/topic/7801-root-r3l3as3d-wfor3v3r-root-v10-linuxwindows-get-root-after-893-ota-oops/#post189877
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,
Okay..just rooted today by downgrading to .15 version of the firmware and using viperboy's root tool...tried to reboot into recovery using the vol down etc method and no dice...all I get is the android dude layed out with his guts all over the place...lol
I went ahead an flashed CWM, figured it might be TWRP related and still no dice...any help would be much appreciated.
*I also tried booting into recovery via terminal "reboot recovery.." -- no luck.
You need to unlock your tablet. When you're rebooting and you don't see a message on the top left saying something 'unlock', you're unlocked.
Rooting will not let you install CWM. Unlocking using Asus's tool will allow you to install a CWM, TWRP, or etc.
ShyTownFantasy said:
You need to unlock your tablet. When you're rebooting and you don't see a message on the top left saying something 'unlock', you're unlocked.
Rooting will not let you install CWM. Unlocking using Asus's tool will allow you to install a CWM, TWRP, or etc.
Click to expand...
Click to collapse
Thanks for the response...So what exactly is the point of rooting without unlocking if you can't boot into recovery and install custom ROMS?
Just a quick suggestion if you want to unlock and install CWM. You should un-root yourself and do a reset to factory first. I'm not sure if it's a must but it wouldn't hurt since you want to install a custom rom anyways. You'll lose everything when you install a custom rom. If it doesn't unlock the first time don't keep trying. Just wait until the next day. The unlock tool has to get a code from Asus to unlock and Asus's server seem to be miss firing A LOT.
A few people including myself are having problems with unlocking the prime.
PS - Rooting will let you run certain apps.
Hi guys,
first of all I want to salut everybody here as I am completely new to the Android world and that's indeed the best resource online. Thanks for that.
Now my big problem. As from the title, I downgrade my Fire HD 6 (4th gen) to 4.5.3 with adb sideload to root it with kingroot and everything went fine. I have then installed TWRP and everything went fine. I have then used TWRP to go back to 5.3.1 and I lost root and recovery. I managed to gain my root privileges back but as for the recovery not a chance. I tried to install TWRP again with dd from adb shell (as I can su) but once again nothing. Checking with fastback getval all, I do have a locked bootload:
Is this the reason why TWRP doesn't run anymore?
If yes, how can I unlock it back?
Is this what's meant with boot loader loop?
Thank you all in advance!
Edit 1:
maybe cuber.py may help but I can't find this file.
Edit 2:
ok found the tools here https://forum.xda-developers.com/kindle-fire-hdx/development/tools-create-unlock-img-fix-boot-img-t3050689
Edit 3:
I tried with cuber.py but the tool can't sign the img because it's not ANDROID. That's what it says. Now I am really stuck. Help please!
LM
I was in the exact same situation, so maybe I can offer some insight. I also have an HD 6 running 5.3.1 that I have downgraded to get root then upgraded a few times. Let me say that I am still learning too, and am by no means an expert but I can try to help.
As far as losing root, i'm not sure as that never happened to me. Did you flash the most up-to date SuperSu with TWRP or did you just answer yes when TWRP prompted you if you wanted root privileges? Flashing a SuperSu through TWRP will give you the SuperSu icon on your home screen once you upgrade back to 5.3.1, whereas just letting TWRP grant root access won't. You will still have root, but without the icon there's no direct control over it (at least not that I could find) so it's still there, just hidden.
My TWRP also replaced by the stock recovery upon updating back to 5.3.1. As far as I know, this is unavoidable. I believe it's as you suspect and is due to the 5.3.1 bootloader being locked. This would also explain why the process for rooting 5.3.1 is so involved as opposed to just using something like Kingroot. I also don't think there's anyone still doing active development on the HD 6 / HD 7.
If you really want to have both root and TWRP, you could try downgrading to an older OS that still has the feel of 5.3.1. I'm not sure about any other versions, but 5.1.1 is rootable via Kingroot (which should mean that it has an unlocked bootloader) and has the same exact UI as 5.3.1. So if you're feeling adventurous try downgrading to 4.5.3, installing TWRP, and upgrading to 5.1.1 instead of 5.3.1 (just be sure to block automatic updates!) and see if TWRP is still active. If so, root with Kingroot and you're good. If you still don't have TWRP, at least you're no worse off than you were.
If you do try this, please post your results here. I might try this myself. I am currently running stock. As I said, I went through the process a few times. For some reason SuperSu was causing erratic behavior in some of my apps and when I tried to switch my SU app to kingroot I lost root completely. I really didn't care about root enough to repeat the whole process again, but if I could keep TWRP it might be worth it. Anyway, good luck.
P.S. You may need to try rooting with Kingroot several times for it to work. I know for a fact that it can root 5.1.1 since I've done it on my own HD 6 when I was running 5.1.1. I'm not sure why it fails, but keep trying and eventually it will get root access. You may have to try 6 or 7 times but eventually it will work.
I went back and re-read this thread more carefully:https://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 and it turns out that TWRP doesn't play well with any 5.X.X bootloaders. Oh well, I was kind of hoping my idea would work. It turns out that you can use TWRP on your current rooted 5.3.1, but only on a temporary basis. Refer to the above thread post #2 for instructions. Basically, you put the correct 5.3.1 bootloader on your device then run AutoTWRP which will flash 4.5.3 bootloaders and TWRP for you. Reboot into recovery and you have your TWRP. You can then do whatever you want. The downside is that since you are running a 4.5.3 bootloader you can't get back into your OS, only TWRP. And once you flash your 5.3.1 bootloader to get back into your OS, TWRP no longer works. I know it's a pain in the arse having to connect to a PC and run a batch file every time you need to use TWRP, but at least it's a sort of workaround.
I used Wugfresh' root installer before and it worked like a charm. You can't get any OTA's with it though. Since I wanted Android 7, I wanted to unroot, install the OTA and reroot using Wugfresh' client. I already did this before when I wanted to upgrade to Android 6. Then everything went well and I was done in an hour.
This time however, I'm stuck. When it needed to reboot after succesfully installing Android 7.1.1, I got set to the No Command screen. After some googling I found out that you had to go to the bootloader first, and then go to Recovery. I got that far, but now I have no clue on what to do.
Rebooting from there doesn't work (obviously). It seems logical to me that I have to install TWRP, but the zip file is not there anymore to install it. Is there a way to still get this zip file on my phone while in recovery mode, and is this the solution to my problem? I also found the format option in TWRP. Does that get rid of all the TWRP stuff and bring me back to complete stock, so I can go back to rooting everything again? I'd be happy to do so, since right now I'm sitting with nothing but a dead Android.
Thank you so much for your help in advance!