Related
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.
Hey guys. I was on CM7, but I started getting some major issues so I successfully SBF'd to get back to 2.3.4, then applied to the 2.3.5 (412) bla bla, yea, you know. So after that flashed, I attempted to root with zergRush and it wouldn't work. It would show error, then something like "pushing busybox successful" then more errors, but all the pushes were successful. My phone didn't reboot or anything even after 10 minutes of waiting. So I did a battery pull, rebooted, busybox app said I didn't have root, THEN, I rebooted normally, and the busybox app said I didn't have root either nor did I have the superuser app that I am supposed to after a successful attempt. Any ideas as to why this isn't working? Any advice? Thanks!
I can never get ZR to work on my laptop w/W7. Go to my signature link and in the middle of post 3 I have more on VooDoo Root Keeper.
I'm assuming I have to downgrade to 2.3.4, root, then install the voodoo thing to protect root then go back to 2.3.5?
Right sbf . Pete's etc.
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
so I am very excited for my Jellybean update.
I am running an original Droid Razr Maxx with the (until now) latest ICS release from Motorola and Verizon. The phone is rooted but I have never loaded any other ROMS (I don't even know how).
So can I update with the OTA Jellybean update while I am rooted? If I need to unroot my phone how can I do that? I used the "DroidRazrRoot404" tool but I cannot seem to use it to unroot my razr maxx.
Any advice is greatly appreciated.
So you have the OTA? Or this is in anticipation of the OTA?
~SU!C!D3~ on Tapatalk
You should be able to update with root, however you should have all official bloat installed or frozen because the OTA will check for it.
However, you will lose root after update....
??? Where did you get that JB OTA update? I am very exited as well, but most probably, it won't come out until next year...
Will OTA occur when the bloatware is frozen? Obviously not a big issue since I can unfreeze but just curious. Also, if I have a ROM on Slot 1 in SS for example, would I just go back to stock ROM and use the OTA when it comes out? Or are there any ROM/SS issues I need to consider or simply delete. And the OTA Rootkeeper app should solve my problems about losing root too right?
for those that want the download and more info about it
http://www.droid-life.com/2012/12/2...-331mb-update-as-build-98-72-8/#disqus_thread
ACEstrom said:
so I am very excited for my Jellybean update.
I am running an original Droid Razr Maxx with the (until now) latest ICS release from Motorola and Verizon. The phone is rooted but I have never loaded any other ROMS (I don't even know how).
So can I update with the OTA Jellybean update while I am rooted? If I need to unroot my phone how can I do that? I used the "DroidRazrRoot404" tool but I cannot seem to use it to unroot my razr maxx.
Any advice is greatly appreciated.
Click to expand...
Click to collapse
Using the download already provided, I had to do a few things to get mine to work.
1. Make sure you are on .211 Stock (if on .214 or .215 SBF back to .211)
2. Remove Safestrap or Bootstrap
3. Make sure all apps are thawed (if they were frozen)
4. Download the OTA update file DO NOT UNZIP IT
5. Place it in the root of your SD card
6. Boot into Stock Recovery holding down Power, Vol+, and Vol- and the same time.
7. Select down to Recovery and press up.
8. When you see the android laying on its back PRESS Vol+ and Vol- simultaneously.
9. Select wipe cache (this will not delete any data)
10. Select install update from External SD and select the zip file.
11. Let it run and update, should work.
I encountered an error so I had to SBF back to .211 and start over fresh, but honestly a fresh restart may not be a bad idea for performances sake.
The only issue that I see is my Razr didn't keep root. I am not sure that this is possible to keep root with this upgrade.
Used voodoo OTA rootkeeper. Protected root, temp unroot. Install, restored and used @matt's root restore fix. Works like a charm.
~SU!C!D3~ on Tapatalk
R1pTheJacka said:
Will OTA occur when the bloatware is frozen? Obviously not a big issue since I can unfreeze but just curious. Also, if I have a ROM on Slot 1 in SS for example, would I just go back to stock ROM and use the OTA when it comes out? Or are there any ROM/SS issues I need to consider or simply delete. And the OTA Rootkeeper app should solve my problems about losing root too right?
Click to expand...
Click to collapse
Hey, I've been looking at the posts about the update, and it seems that If you have safestrap/bootmenu/bootstrap, you will not be able to upgrade.... If you want the upgrade, you should go back to stock .211...
If you just have some frozen apps, you will be able to update correctly
Follow the instructions that chadgauth posted...
lost root
Stock 211 rooted. Voodoo root keeper backed up protect root, temp unroot.
Installed 4.1.2 update all good. Failed to get root back thru vodoo.
FYI cannot go back to 211 after flash 4.1.2 so now stuck
Without root till some dev comes out with a root method for us
Restore with voodoo rootkeeper then use Matt's rootfixer forum.xda-developers.com/showthread.php?t=2064074&page=19 post#187
Make sure you have USB debugging enabled in development
Enable "Unknown Sources" in privacy
Go to settings/storage menu soft key
Computer connect - select MTP
~SU!C!D3~ on Tapatalk
Tried that. For some reason it did not save the such file with vodoo so root fixer says cannot be found. Prolly some mistake I made or uncommon glitch
queberican351 said:
Restore with voodoo rootkeeper then use Matt's rootfixer forum.xda-developers.com/showthread.php?t=2064074&page=19 post#187
Make sure you have USB debugging enabled in development
Enable "Unknown Sources" in privacy
Go to settings/storage menu soft key
Computer connect - select MTP
~SU!C!D3~ on Tapatalk
Click to expand...
Click to collapse
As I was installing through recovery I got an error because it was checking my preinstalled apps for ForestWallpaper.apk which I'm assuming I deleted ages ago, in addition to
e:error in /tmp/sideload/package.zip
(status 7)
Installation aborted.
..but according to this I'm screwed? http://forum.xda-developers.com/showpost.php?p=19468147&postcount=15
R1pTheJacka, You can SBF back to .211.
Also, all of you guys that are using OTA Rootkeeper, why are you temp unrooting after protecting root? On my Droid X upgrade to ICS a while back and on this OTA to JB today on the RAZR Maxx, I just protected with OTA Rootkeeper but left it rooted. Didn't temp unroot. Then upgraded and then simply restored root. No need for an extra step of fixing it after trying to restore root.
85gallon said:
You can SBF back to .211.
Also, all of you guys that are using OTA Rootkeeper, why are you temp unrooting after protecting root? On my Droid X upgrade to ICS a while back and on this OTA to JB today on the RAZR Maxx, I just protected with OTA Rootkeeper but left it rooted. Didn't temp unroot. Then upgraded and then simply restored root. No need for an extra step of fixing it after trying to restore root.
Click to expand...
Click to collapse
As far as sbf back to 211 you can't it just throws you into a black screen boot loop then you have to play with the power and volume buttons yo get into recovery to reflash the job update
sttierney said:
As far as sbf back to 211 you can't it just throws you into a black screen boot loop then you have to play with the power and volume buttons yo get into recovery to reflash the job update
Click to expand...
Click to collapse
It didn't for me. And even the directions that everyone is following from droidrzr.com tells you not to "temp unroot". It is kind of buried in the instructions, but it says not to temp unroot.
85gallon said:
It didn't for me. And even the directions that everyone is following from droidrzr.com tells you not to "temp unroot". It is kind of buried in the instructions, but it says not to temp unroot.
Click to expand...
Click to collapse
Once your on jb I tried sfb back to 211 and it was a nightmare to get recovery to come back up got the eye then black screen. And of course I updated before the instructions came out so that's how I ended up being where I am with no root
sttierney said:
Once your on jb I tried sfb back to 211 and it was a nightmare to get recovery to come back up got the eye then black screen. And of course I updated before the instructions came out so that's how I ended up being where I am with no root
Click to expand...
Click to collapse
I went up and edited my post to clarify that I was responding to R1pTheJacka. He never made it to JB. He errored out trying to upgrade. Never made it to JB. You are correct, if you make it to JB you can't go back from the posts I am seeing.
unable to root ota using voodo
I have successfully flashed jelly bean but was unable to restore root using voodoo root keeper. If you guys have any luck please let me know... Missing my tethering. :/
Chadwick108 said:
I have successfully flashed jelly bean but was unable to restore root using voodoo root keeper. If you guys have any luck please let me know... Missing my tethering. :/
Click to expand...
Click to collapse
You can use this to get root back if you used voodoo root keeper.
http://forum.xda-developers.com/showthread.php?p=35863089
Sent from my JellyBeaned Droid RAZR Maxx
error unable to use restore root
klabit87 said:
You can use this to get root back if you used voodoo root keeper.
http://forum.xda-developers.com/showthread.php?p=35863089
Sent from my JellyBeaned Droid RAZR Maxx
Click to expand...
Click to collapse
root keeper will not work superuser app is installed is checked and /system supports root protection but will not allow restore root.
also tried matts restore root.zip but get error message of system/bin/sh su not found....