Hey, there seems to be a few of us(or maybe it's just me) confused about how we can root after the new update.
I just wanted to know if there was a confirmed safe way to restore root.
Thanks
Update:
Thanks to superkev. Manual way works. I can also confirm it also.
Also remember to keep your phone awake (ie. not in the locked screen)
superkev said:
I tried the manual instructions from here: http://briefmobile.com/motorola-atrix-4g-root
Step 6 failed for me, possibly because I had used this method to root 2.3.4. The rest of it went perfectly. I think the 2.3.6 update changed the permissions of the su binary, so these instructions just reset that to what they're supposed to be. I am rooted again!
Click to expand...
Click to collapse
I can't seem to find any root information on bell atrix 2.3.6 either.
saw some unconfirmed reports that superoneclick worked, but it doesn't work for me just sits at "Failed to set prot mask"
and then "WaitforDevice" forever...
if anyone has legit root info for the bell atrix 2.3.6 posting it would be greatly appreciated.
All I want is to install it! But im in usa so I need someone to make a fruitcake of it for me. Oh and I have also read super one click is supposedly working for some.
Sent from my MB860 using Tapatalk
I've got super one click working but superuser keeps denying all my root permissions without giving me a prompt.
DANGER!
So I tried SuperOneClick 2.3.1 and got my Bell Atrix 2.3.6 rooted.... all seemed good and Root Checker told me I was rooted. Light Flow got Super User permission and I thought I was gold!
Then my phone started freezing up and rebooting. Now I can't use the phone because it is crashing every 30 seconds. I would say avoid SuperOneClick (at least this version) for now!!
Oh, and SuperOneClick won't unroot my device so I'm kind of stuck. I would rather not reset my device and have to reinstall all my apps (which are backed up with Titanium Back-up, but which of course needs root to work...).
I'm just trying GingerBreak to unroot so we'll see how that goes.....
---------- Post added at 02:51 AM ---------- Previous post was at 02:44 AM ----------
... OK... so GingerBreak unrooted my phone but it is still completely hooped and the crashing woes continue... anyone with a solution on which system files I might be able to replace to fix this?!?!?
Aaaarrrg!
I tried wit Pete's first and it failed but super one click worked right from the first attempt. Before doing that though, I did a factory reset and started from scratch. Then I restored my apps only with TB. All is OK except that in market my apps list is empty with a message saying that my purchased apps will appear here. I have read that it is a known problem, but not necessarily with this update or because of rooting. In my experience super one click has otherwise been OK. Hope that helps. Don't have a solution for you except maybe trying to do a factory reset first if you are able to and then try again.
Sent from my MB860 using xda premium
Hey thanks. Yes, I ended up having to do a reset from the boot menu (power+vol down) and do an 'Android Recovery' which apparently wipes the system files and reinstalls the OS. My TB backups are still sitting on the internal SD but I am hesitant to re-root so I can reinstall TB and restore... what build of SuperOneClick did you use?
I tried with SuperOneClick 2.3.1.0 (latest). It says that it worked, but even after rebooting, my apps are being denied root access.
UPDATE:
I tried the manual instructions from here: http://briefmobile.com/motorola-atrix-4g-root
Step 6 failed for me, possibly because I had used this method to root 2.3.4. The rest of it went perfectly. I think the 2.3.6 update changed the permissions of the su binary, so these instructions just reset that to what they're supposed to be. I am rooted again!
I just updated to 2.3.6 and used the Briefmobile method to root and can also confirm that it is working. I had previously used this method to do 2.3.4 and had no issues on 2.3.6. Cheers
I might caution those who are not on AT&T about using the "manual" root method from BriefMobile. It was built with AT&T 2.3.4 files. Flashing the root.img in fastboot flashes those files to your /preinstall folder possibly hosing your Bell specific files. This has in the past, and possibly could in the future cause issues when trying to install future updates.
For those of you who have done it, can you look in /preinstall/md5 and see if you have att files?
Sent via 2.3.4 Rooted/Unlocked Moto Atrix using Tapatalk
superoneclick 2.3.1.0
this works flawlessly and on first attempt. so easy!
gingerbreak 1.2 didn't work this time, but it was useful to me for unrooting.
just make sure you do that before installing the update, and follow the superoneclick instructions.
too early to comment on battery life, and other than the keyboard I don't notice any aesthetic changes.
bell atrix
Remember to flash back the original preinstall image to avoid update issues.
Cheers!
das8nt said:
For those of you who have done it, can you look in /preinstall/md5 and see if you have att files?
Click to expand...
Click to collapse
That directory does contain some ATT and Cingular files. However, I used this method to root 2.3.4 and it didn't prevent me from installing the 2.3.6 update. I'm hoping I won't have any trouble going to ICS (fingers crossed that such a thing will even happen!)
superkev said:
That directory does contain some ATT and Cingular files. However, I used this method to root 2.3.4 and it didn't prevent me from installing the 2.3.6 update. I'm hoping I won't have any trouble going to ICS (fingers crossed that such a thing will even happen!)
Click to expand...
Click to collapse
Good deal. I had to help a few revert that folder when updating from 2.2.2 to 2.3.4 due to missing the gameloft stuff, but if it didn't effect your update that's good news.
Just in case, here's the 2.3.6 Bell stock preinstall.img to flash via moto-fastboot (thanks to NFHimself's new Gobstopper): http://www.megaupload.com/?d=C098P9IV
Sent via 2.3.4 Rooted/Unlocked Moto Atrix using Tapatalk
I used the manual way to root with the 2.3.6 update but TB is saying it can't can't gain root access and su keeps fc'ing on me. Anyone have any ideas what could be causing this? I also tried the superone click method but during the exe install on my pc it keeps stopping saying i don't have an internet connection????
j7logan said:
I also tried the superone click method but during the exe install on my pc it keeps stopping saying i don't have an internet connection????
Click to expand...
Click to collapse
that's weird. you definitely don't need internet access to perform the root (i was offline), provided you have superoneclick and phone drivers installed i'd say. does the driver check feature complain about it too?
Yeah, i thought it was strange too. It doesn't give me that error with the driver check, only when it is going through the install process of the exe.
Sometimes you need to treat your phone like a computer when it starts acting weird, save yourself some hassle and just do a format/factory reset and start fresh.
i used Doomlord's Rooting Toolkit: http://forum.xda-developers.com/show....php?t=1319653 it worked in 30 sec
Link to the exact Superoneclick you used? I tried the Doomloader link but it's broken.
I checked and saw an OTA update for my Atrix (4.5.141) [mine currently 4.5.91 ; 2.3.4]
I downloaded and install but it appeared a < ! > in process then it restart itself and says update failed.
I think this problem caused by Root.(Is there any way to unroot my phone ?)
Be sure to undo anything you did that requires root access (defrost apps, etc)
For unrooting, it depends how you rooted your phone.
1) if you used the one click method, there's an unroot button
2) if you used the fastboot preinstall method, delete the su related files:
http://androidforums.com/atrix-4g-all-things-root/423259-best-way-unroot.html
It may be as simple as only removing su from /system/bin and uninstalling superuser.apk, but doing a full unroot is the safest way IMO.
I just updated today. ATT 2.3.4 with locked Bootloader, rooted with the one click method. When I went to use the one click method to unroot I received an error message saying that I didn't have the proper back up files.
After much searching on-line, I installed OTA RootKeeper and ran it to make my Atrix look like it hadn't been rooted. After the update I ran OTA RootKeeper again to restore root.
I've restarted my phone 3 or 4 times in the last 4 hours and so far all is well!
walker63 said:
I just updated today. ATT 2.3.4 with locked Bootloader, rooted with the one click method. When I went to use the one click method to unroot I received an error message saying that I didn't have the proper back up files.
After much searching on-line, I installed OTA RootKeeper and ran it to make my Atrix look like it hadn't been rooted. After the update I ran OTA RootKeeper again to restore root.
I've restarted my phone 3 or 4 times in the last 4 hours and so far all is well!
Click to expand...
Click to collapse
OTA Rootkeeper is good only if you used a root method that uses the zergrush exploit. Most of the one click methods use it. I however, used a method that edited build.prop. I used OTA Rootkeeper, updated, and it failed to properly restore root. Others that used a root tool that uses zergrush had no problem restoring with OTA Rootkeeper.
OKAY, so I was getting my phone ready to flash CM9 when it's released. I used my .iso disk to SBF just fine. Wiped date and cache and got ready to ROOT. I use Pete's Motorola Root tools to do so. Done this a few times, so I know what I'm doing here. It tells me it's "Running Exploit 1 of 3..." Done, reboots. Running Exploit 2 of 3 done. Again, reboots. "Running Exploit 3 of 3......." and it just hung up on that for quite a while. It ended up telling me ROOT access was successful but was unable to push superuser.apk.
So without using the UnRoot my Phone option first, I just decided to hit ROOT again. This time it went through all the stages just fine and superuser is on my phone. I just tested this with ROM toolbox pro and it does grant it SU permissions. I am only wondering if this could have messed up some files somewhere on my phone, somehow. This is the first time ever Pete's 1 click root tool ever gave me an issue. Just curious if I should play it safe and SBF again and try once more to root without issue or if my phone should just be fine as is........ Thanks
RoyJ said:
OKAY, so I was getting my phone ready to flash CM9 when it's released. I used my .iso disk to SBF just fine. Wiped date and cache and got ready to ROOT. I use Pete's Motorola Root tools to do so. Done this a few times, so I know what I'm doing here. It tells me it's "Running Exploit 1 of 3..." Done, reboots. Running Exploit 2 of 3 done. Again, reboots. "Running Exploit 3 of 3......." and it just hung up on that for quite a while. It ended up telling me ROOT access was successful but was unable to push superuser.apk.
So without using the UnRoot my Phone option first, I just decided to hit ROOT again. This time it went through all the stages just fine and superuser is on my phone. I just tested this with ROM toolbox pro and it does grant it SU permissions. I am only wondering if this could have messed up some files somewhere on my phone, somehow. This is the first time ever Pete's 1 click root tool ever gave me an issue. Just curious if I should play it safe and SBF again and try once more to root without issue or if my phone should just be fine as is........ Thanks
Click to expand...
Click to collapse
The EXACT same thing happened to me a few hours ago...it was the first time I had to restart rooting with Pete's and I use it all the time. I checked with Root Checker and TiBU and so far everything has been fine.
Sent from my DROID X2 using Tapatalk 2
Yeah, everything seems fine. I was just wondering if it could have left some broken files on my phone that would cause bugs or glitches after the flash
did you install system recovery/ bootstrap
can you boot into clockwork/ BSR , if you can you should be good
sd_shadow said:
did you install system recovery/ bootstrap
can you boot into clockwork/ BSR , if you can you should be good
Click to expand...
Click to collapse
Yes, that was never a problem. However upon trying to flash CM9 it just hung on installing for over 30 minutes. I just SBF'ed again and rooted with NO issues this time. About to try to flash again. Wish me luck!
Edit: So after I rooted without any problems I tried installing it again and it worked!
Awesome! Enjoy I wonder if it helps is people formatted their system as well before going to cm9? On the dinc2 when going between ginger bread and ics you must wipe system also.
This root method was unsuccessful for me. I came from stock rooted 181 to ICS 211. Phone is now showing SU as a system app. Busybox says "your phone is rooted". But all permissions denied. Obviously not rooted. Script seems to self destruct before second reboot. Cannot uninstall SU apk. Any ideas?
JoJoLanny said:
This root method was unsuccessful for me. I came from stock rooted 181 to ICS 211. Phone is now showing SU as a system app. Busybox says "your phone is rooted". But all permissions denied. Obviously not rooted. Script seems to self destruct before second reboot. Cannot uninstall SU apk. Any ideas?
Click to expand...
Click to collapse
Well, you may be up a creek. A few things.
First, you're on .211 which (unconfirmed) may be the version they're pushing for the soak test. That would be a good thing because you'd already be updated. Second, when you flash to versions higher than .79 (I think) it actually changes the signature on your bootloader, making it impossible to revert back to GB and try again. There are ways, but I'm not going to go into detail, you'll have to look that up on your own.
I was able to flash GB 173, root GB, preserve root with Voodoo and then install the .75 ICS leak (one of the more stable ones, IMO) and restore root.
My advice to anyone running a leak is to try and flash back to GB and then just sit on it. The soak test emails are coming out so the official release can't be far away. I honestly don't see the point of flashing a leak at this point as it will probably be fully deployed in the next week or so.
Can you give me any additional information, like what utility you used to flash and what you used to preserve root when going from GB -> ICS?
The root method you used is wrong.
Run tibu to fix permissions
Sent from my XT910 using xda premium
I have problems with rooting or unrooting my Maxxed Droid Razr.
I had leak ICS rooted. I downgraded to GB(rooted) and sideloaded official .211. Tried to restore root with OTA RootKeeper. My phone showed SU icon and asked permission to run OTA Rootkeeper I did allow the permission everything looked good. I tried to check the root root checker but it does not show that my phone is rooted.
I tried DroidRazrUtility 1.6 to root it again but it fails all the time saying that files already exists. Then I tried to unroot but it said that my phone does not have root.
I tried to get back to GB but it did not work. Just stuck on boot loop. Sideloaded the ICS .211 and SU icon was gone and no root at all. I did couple master resets with deleting all the internal and sd storage. Still no luck.
Now I can not root my phone. Any ideas how to get the root back.
Appreciation "Thank you" will be given to anyone who tries to help.
droidxrooting said:
I have problems with rooting or unrooting my Maxxed Droid Razr.
I had leak ICS rooted. I downgraded to GB(rooted) and sideloaded official .211. Tried to restore root with OTA RootKeeper. My phone showed SU icon and asked permission to run OTA Rootkeeper I did allow the permission everything looked good. I tried to check the root root checker but it does not show that my phone is rooted.
I tried DroidRazrUtility 1.6 to root it again but it fails all the time saying that files already exists. Then I tried to unroot but it said that my phone does not have root.
I tried to get back to GB but it did not work. Just stuck on boot loop. Sideloaded the ICS .211 and SU icon was gone and no root at all. I did couple master resets with deleting all the internal and sd storage. Still no luck.
Now I can not root my phone. Any ideas how to get the root back.
Appreciation "Thank you" will be given to anyone who tries to help.
Click to expand...
Click to collapse
Download unstuck ics 211. Flash the .85 kernel then root using matts utility 1.6 then use unstuck again to flash the .211 kernel back to the phone. There's a tutorial for it online in better detail
Sent from my DROID RAZR using xda app-developers app
Found the guide. Doing it right now. I will report if that fixes it.
Moved to Q&A
Cheers
thank you
it is fixed here are the steps I took. http://www.droidrzr.com/index.php/topic/2693-ics-616211-morning-of-6152012-not-fastbootable/