Was rooted off of gladroot, now i flashed all the way back to factory and lost everything so i could update to the new update. That is what im running on now without a root. I just ordered a SD card from amazon. Is that the only way i can root my Atrix? I need an SD card right? or is there another way? Gladroot only seems to be for the last update. Thanks
GladRoot works just fine with the latest update as long as you are not running any mods. You will have to SBF back, gladroot, update, retain root.
WiredPirate said:
GladRoot works just fine with the latest update as long as you are not running any mods. You will have to SBF back, gladroot, update, retain root.
Click to expand...
Click to collapse
Ok ill see if there is one now, thanks again man! learning more abouto the android everyday lol.. comin from an iphone.
I feel your pain lol. I just came from an Iphone last week as well. Im pretty sure I read somewhere that you need an SD card to root though... Let me try and find that...
Okay, So specifically, if you use Gingerbreak (I can't account for anything else, all I've used so far lol), it specifically says you cannot jailbreak... gingerbreak (grr) without an sd card.
On the bright side? Best buy in my area (nationwide too?) has a microsd 8 gb for 11 dollars
Thats a good deal on the 8gb, wish there was a BB close to me.
Flash back to stock 1.26, use gladroot (just search the forum for it), update to 1.57, update to 1.83 and then run afterupdate.bat and you will be rooted on 1.83. Then just backup with titanium backup.
Sent from my MB860 using XDA App
Does anyone have the SBF for Oranges 4.1.31 retail ROM i need to unroot my Atrix to return it unfortunately.
Cheers
nope its not available, best you can do is flash olyem 2.1.1 and hope they dont notice. Although it wont have all of the orange apps, someone may have a backup of them they can send you though, saying that though i imagine you need to be rooted to restore them so maybe not a great idea.
if you used gingerbreak there is an unroot option, you could do that than factory reset?
I saw that the XDA team had rooted the new software, so I went ahead and did an upgrade via my PC instead of over the air. Now that I've started researching the root methods it looks like all of them void your warranty, so if your phone dies (and lets be honest phones do die often on their own accord), you will be stuck buying a brand new phone.
I like the new software, but there are tools I use that need root such as titanium backup, and settings profiles (for gps scripting). Will there ever be a root going forward that won't break your warranty?
vmlinuxz said:
I saw that the XDA team had rooted the new software, so I went ahead and did an upgrade via my PC instead of over the air. Now that I've started researching the root methods it looks like all of them void your warranty, so if your phone dies (and lets be honest phones do die often on their own accord), you will be stuck buying a brand new phone.
I like the new software, but there are tools I use that need root such as titanium backup, and settings profiles (for gps scripting). Will there ever be a root going forward that won't break your warranty?
Click to expand...
Click to collapse
no, the act of rooting voids your warranty not the method. How hard motorola actually tries to determine if your phone is rooted is another matter though especially if something is making your phone disfunctional.
Warranty is not a tangible item that is "broken." It is a legal agreement. By rooting your phone, you are exposing the delicate inner workings to possible breaking. However, since the manufacturer doesn't see what happens to the phone and it stops working, you can generally at least partially restore it, hiding the fact it was rooted. Is your warranty still void? Technically yes. However, the manufacturer doesnt know. Further, Although it is possible to break your phone, you will never have any trouble as long as you follow these guidelines:
- Avoid rooting phones with the OTA 2.3.4
- DO NOT FLASH SBF TO OTA 2.3.4 ATRIX. IT WILL BREAK FOR GOOD
- Read all instructions
- Make sure all mods are for YOUR specific version of the OS
- Backup with CWM before every mod.
- Lastly, insure that the phone battery is fully charged before doing any flashing. This will avoid the possibility that your phone will get bricked and then run out if battery b4 u can fix it (bricked phones do not charge).
- Aside from that, as long as u do not have OTA gingerbread 2.3.4 on your phone, don't freak out if u brick your phone. I have done it 9 times in the past month and everytime managed to restore it with RSD Lite.
Finally: IF YOU DON'T HAVE GINGERBREAD 2.3.4 OTA DO NOT UPGRADE VIA THE OTA UPDATE. USE THE FRUIT CAKE METHOD OR YOU MAY BRICK YOUR PHONE NEXT TIME THAT YOU ROOT/UNLOCK IT.
Sent from my Atrix using XDA App
Excellent replies. That makes sense, I just didn't realize it was a legal issue more than technical.
Another quick question. If I used the Motorola PC upgrade to 2.3.4 is it still considered an OTA update since I downloaded the stock from Motorola and upgraded it via PC?
Sun3vi1 said:
- Avoid rooting phones with the OTA 2.3.4
Finally: IF YOU DON'T HAVE GINGERBREAD 2.3.4 OTA DO NOT UPGRADE VIA THE OTA UPDATE. USE THE FRUIT CAKE METHOD OR YOU MAY BRICK YOUR PHONE NEXT TIME THAT YOU ROOT/UNLOCK IT.
Sent from my Atrix using XDA App
Click to expand...
Click to collapse
Huh? you can root just fine with the OTA 2.3.4 using the preinstall method. Works perfectly. If you OTA'd to 2.3.4 you don't ever want to attempt to flash back down to a previous version. You can still root and unlock the phone even with OTA 2.3.4.
The only thing that using the OTA breaks is being able to SBF to previous builds. But you can still use pudding to unlock and use other roms including froyo ones with pudding built in.
I highly doubt it is illegal to root. Where did you hear this?
Google doesn't charge to license Android, and it's their license, AFAIK individual companies cannot do what they want with this license. It remains open source software that anyone can develop for. It's based on Linux/Unix.
Does anyone here even know what rooting does? It is the act of re-enabling the Superuser. A right EVERY Linux distribution should have. Phone or not.
nexxusty said:
I highly doubt it is illegal to root. Where did you hear this?
Google doesn't charge to license Android, and it's their license, AFAIK individual companies cannot do what they want with this license. It remains open source software that anyone can develop for. It's based on Linux/Unix.
Does anyone here even know what rooting does? It is the act of re-enabling the Superuser. A right EVERY Linux distribution should have. Phone or not.
Click to expand...
Click to collapse
Sun3vi1 said "the warranty is a legal agreement". It says that if your phone breaks within a certain period of time they'll replace it, *provided* you haven't modified it in any way. Rooting may or may not be legal in your jurisdiction, but either way it voids the warranty by modifying the phone.
If you only root in a method that allows you to unroot easily enough, there's no problem. Since rooting is not a particularly invasive set of changes, unrooting should not be difficult.
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,
My phone is rooted stock on the very first original ROM (forgot the version). I asked Sprint for GSM unlock, they sent the request, but it didn't go through. The "UICC unlock" option does nothing. Could it be because I'm rooted and/or on an old ROM? I didn't tell Sprint rep about the root.
Idk probably the root it mess with the system try flashtooling back to ZV4 and then try it but dont ota to ZV6 or else you'll lose root. Alsi they code/ method may be bad. What carrier are you trying to go to?
1619415 said:
Idk probably the root it mess with the system try flashtooling back to ZV4 and then try it but dont ota to ZV6 or else you'll lose root. Alsi they code/ method may be bad. What carrier are you trying to go to?
Click to expand...
Click to collapse
Thanks for the advise. I just figured out the problem- I froze a lot of bloat with TB, and it affected UICC. unlock. I did it a while ago, and it didn't occur to me right away to defrost before attempting to unlock.
I'm thinking about traveling to South America and want to use a local SIM card while over there.
OK well have fun, glad it works
However I'm not sure how to check that the unlock actually worked. When Sprint network is available, the phone will use it regardless of the SIM. I tried to install a T-Mobile SIM from friend's phone, and my phone came up with red X SIM icon in the status bar- the same as with no SIM.
Spring does not support unlocking.
Sprint does not support domestic sim unlocking but will allow international unlocking.
If you want to use another carrier then try out cloudyg3 1.2 rom or cm11 rom. You can use any carrier with them. Or else you have to modify your build.prop file and replace the ro.carrier.target from SPR to spr using the rom toolbox app and then you get a unlocked gsmphone.