[HOWTO] Root the Atrix 2(Updated for 2.3.6 FINALLY)

Search This thread

dk-v1

Senior Member
Dec 28, 2011
143
13
Baton Rouge
There should be no reason. Obtaining root should have nothing to do to with how fast your phone runs.

That's kinda what I was thinking.

Pre-root score was above 5200, now I'm barely getting 4300. Lost about 100mb of ram as well.

Haven't changed anything else either.

What other info would be helpful in finding an answer?

Sent from my MB865 using XDA App
 
Last edited:

JRW 28

Senior Member
Aug 19, 2011
1,065
663
FL
I've gone through the 1-step process a few times including right after doing a factory reset. I've checked for the root via root check and ROM Manager and no bueno.

Below is what each process spits out ... looks like my guts are set to Read Only. How do I get around this or am I just way off and is it something else?

Thank for your time!!!

PS 2.3.6

[*] Motorola universal root script by P3Droid
[*]
[*] This should work on most motorola phones
[*]
[*] Press any key to get this phone rooted !
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] Motorola Phone Connected...
[*] Starting the Root Process, Do Not Disconnect Phone...
3177 KB/s (22776 bytes in 0.007s)

[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.

[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.

[+] Found a GingerBread ! 0x00016118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
[1] Segmentation fault /data/local/zerg
[*] Waiting for phone to reboot.
* daemon not running. starting it now *
* daemon started successfully *
[*] Installing Root Packages ...
remount failed: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
link failed Read-only file system
failed to copy 'busybox' to '/system/bin/busybox': Read-only file system
Unable to chmod /system/bin/busybox: No such file or directory
/system/bin/busybox: not found
2459 KB/s (785801 bytes in 0.312s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
cannot create /data/local.prop: permission denied
[*] Rebooting...
* daemon not running. starting it now *
* daemon started successfully *
[*] Your Phone is Rooted !
[*] Press any key to exit.
Press any key to continue . . .

Go to the beginners thread and perform the steps for rooting 2.3.6 instead of 2.3.5. And while you're there read the rest and it should help you with anything else.
 

Obievil

Senior Member
May 12, 2011
79
4
Oui! What a mess. I need to post this here for future people.

My wife's Atrix 2 was on 2.3.5. She installed the 2.3.6 OTA. The problem with this is that it effectively soft bricked the device. it still worked, but Root was gone, but not only gone, we could not uninstall Superuser.apk. I spent at least an hour trying to resolve this through shell and ADB.

We ended up doing a manual back up. using the guide to revert the device to 2.3.5 stock, Then doing the OTA push and then re-rooting the device.

For the love of all that is holy. DO NOT do the Stock OTA when rooted.
 

shabbypenguin

Inactive Recognized Developer
May 30, 2010
4,896
5,365
35
I see what you are saying, but to call that out when cogeary was the one right here, who helped that person out and made it easier for that person to perform the hack, not Dan who created the "original" hack, is not very cool.

So what you are telling me is that those of us that do have to re-engineer things for THIS phone, and get donations should not accept them because the original hack was performed by someone else for another phone, and never really "meant" for this phone... And that our time is worthless.

Wow you must really not like those hacks and scripts to make YOUR life easier on THIS phone, that have been reversed engineered from other phones and brought to this one.

As long as people give credit where credit is due, as it STATES in the XDA rules, that is perfectly acceptable. I saw no where, that cogeary took credit for the "orginal" hack, and only stated that it was his script that used the hack.

hey, not to knock anyone as thats not my intention, but what exactly had to be "re-engineered" for the A2?

http://pastebin.com/ukqyyyvu

http://pastebin.com/qvw2MCaZ

as far as i can see just the heading of it was changed. on which i dont blame cogeary one bit, ive renamed my zergrush scripts plenty of times so that noobs dont go "ZOMG I DONT HAVE X PHONE!?!?!?!!?" but i guess i dont understand your stance on how it needed to be rengineered etc. the script from bliss woulda worked just fine, just as would any one of the zergrush scripts or superone click would have worked on 2.3.5

again please dont take it the wrong way, im not trying to discredit anyone...
 

floridaboy69

Member
Jan 6, 2012
20
3
Orlando
Oui! What a mess. I need to post this here for future people.

My wife's Atrix 2 was on 2.3.5. She installed the 2.3.6 OTA. The problem with this is that it effectively soft bricked the device. it still worked, but Root was gone, but not only gone, we could not uninstall Superuser.apk. I spent at least an hour trying to resolve this through shell and ADB.

We ended up doing a manual back up. using the guide to revert the device to 2.3.5 stock, Then doing the OTA push and then re-rooting the device.

For the love of all that is holy. DO NOT do the Stock OTA when rooted.

Hey I've been having the same exact problem, becuase I was unaware of the OTA update and now its unrooted, and super user just denies everything, how do I fix this?
 

rob219

Senior Member
Jul 11, 2010
709
123
here and there
Hey I've been having the same exact problem, becuase I was unaware of the OTA update and now its unrooted, and super user just denies everything, how do I fix this?

did you try the 2.3.6 root zip in the first post? You should download it and try running the root command. If that doesnt fix it run the unroot command and after it reboots run the root command again and you should be good.
 

floridaboy69

Member
Jan 6, 2012
20
3
Orlando
did you try the 2.3.6 root zip in the first post? You should download it and try running the root command. If that doesnt fix it run the unroot command and after it reboots run the root command again and you should be good.
Ive tried thats, its just starts the .bat and reboots and goes through as it normally should but absolutely nothing changes, updated all the drivers and watched a video of a guy rooting it on 2.3.6. Nothing has worked and super user just denies everything because the system will not root!

---------- Post added at 11:42 AM ---------- Previous post was at 11:06 AM ----------

Connect your device to begin...
Device connected.
[*] Deleting files...
Permission denied
Permission denied
[*] Completed! Rebooting...
[*] Done. If all went well your device should be unrooted.
Press any key to continue . . .

And.....

Connect device to begin!
Device connected.

[*] Performing exploit... (thanks Dan Rosenberg!)

2646 KB/s (501292 bytes in 0.185s)
[*] Motofail: Universal Motorola Android Root Exploit
[*] Copyright (c) 2012 Dan Rosenberg (@djrbliss)
[*] Exploit complete.

[*] Done. Rebooting device...
[*] Done. Pushing su and Superuser to device...
943 KB/s (22228 bytes in 0.023s)
link failed File exists
2792 KB/s (843503 bytes in 0.295s)
[*] Done. Cleaning up exploit...

[*] Motofail: Universal Motorola Android Root Exploit
[*] Copyright (c) 2012 Dan Rosenberg (@djrbliss)
[*] Exploit complete.

[*] Done. Rebooting device...
[*] Done.

If all went well well your Atrix 2 should be rooted!
Thanks for using, and enjoy root!

Press any key to exit.

These are my results and no matter what I do (I even factory reset it!). This is maddening, its like superuser gets locked in the programs and just starts denying any program the needs to use it!
 

SeekerLoki

Senior Member
Jan 12, 2012
51
16
I believe the exploit was successful, but you have a file in the way that causes su not to be setup correctly. (I'm guessing based on your log and the way the original exploit works). Try Something like this:

1. Open "ADB shell" to phone (from the exploit directory)
2. type in the ADB shell "/system/xbin/su" (prompt should now end in # instead of $)
(only continue if the prompt changed)
3. type in the ADB shell "rm /system/bin/su"
4. "ln -s /system/xbin/su /system/bin/su"

This will use the setup of the new exploit. I believe you could replace setup 3 and 4 with "chmod 6755 /system/bin/su" and that would work as well. Give it a shot and let me know if it works.
 

floridaboy69

Member
Jan 6, 2012
20
3
Orlando
I believe the exploit was successful, but you have a file in the way that causes su not to be setup correctly. (I'm guessing based on your log and the way the original exploit works). Try Something like this:

1. Open "ADB shell" to phone (from the exploit directory)
2. type in the ADB shell "/system/xbin/su" (prompt should now end in # instead of $)
(only continue if the prompt changed)
3. type in the ADB shell "rm /system/bin/su"
4. "ln -s /system/xbin/su /system/bin/su"

This will use the setup of the new exploit. I believe you could replace setup 3 and 4 with "chmod 6755 /system/bin/su" and that would work as well. Give it a shot and let me know if it works.
Thanks, I'm pretty bad with command prompt, could you write out the commands that I enter in order?
 

SeekerLoki

Senior Member
Jan 12, 2012
51
16
Thanks, I'm pretty bad with command prompt, could you write out the commands that I enter in order?

I'll try... You will need to know the directory path to either the exploit directory or the android SDK with platform-tools installed. adb.exe is part of the SDK platform-tools and was also included in the exploit zip file. Replace **Directory where adb.exe lives** with the correct path and you should be set.

1. cd **Directory where adb.exe lives**
2. adb shell
3. /system/xbin/su
4. rm /system/bin/su
5. ln -s /system/xbin/su /system/bin/su

Good luck!
 
  • Like
Reactions: floridaboy69

SeekerLoki

Senior Member
Jan 12, 2012
51
16
Sorry about that... I forgot an important step. After step 3 type:
mount -o rw,remount /dev/null /system

This will remount the /system partition read / write.
 

NaffyG

Member
Oct 30, 2009
7
0
<quote> Originally Posted by Asmodae View Post

Ah yes, tape drives, those were fun (/sarc). Peek and poke to get basic stuff done, like load a program! I too learned programming on a TRS machine. TRS-80 Coco II. You guys are reaching back a ways there.

program cartridges half the size of an 8track.After Jim and I got on this subject I called my Dad to see whatever happened to it. He STILL has it! Its on the shelf in his storage shed. </quote>

<Off Topic> YES I Still have 2 TRS-80 CoCo 3 machines! (128k baby!) I have one from the late 80's, and one that I recently picked up at a yard sale for $5, complete with spare tape drive, floppy drive, and a few game cartridges. For $5 I couldn't resist!
 

fadetoblack2104

Senior Member
Sep 29, 2010
183
15
Jefferson City
I have tried both methods several times each tonight and cannot seem to gain root access. I have even tried a factory reset on the phone. I have verified that unknown sources and usb debugging are both on and the phone is in charge only. The error I am getting using the manual mode is shown in the image attached.
 

Attachments

  • Untitled.jpg
    Untitled.jpg
    43.4 KB · Views: 455

Top Liked Posts

  • There are no posts matching your filters.
  • 54
    First: I'd like to make it clear I am not claiming this process as my own. This method was created by p3droid over at the MyDroidWorld Forums. I am not a dev, just someone compiling information.




    Second: This root method is originally intended for the Droid Bionic and I take no responsibility if this bricks your phone.

    Third: This root was discovered by JRW 28 So give him some love with that thanks button.

    If you are on 2.3.6:
    Install the OTA and upgrade your phone to 2.3.6
    Download the 2.3.6 root zip from HERE
    Make sure you have the right drivers installed then connect your phone to your PC.
    Unzip the file and then double-click "Click-To-Root.bat".
    Refer to the trouble shooting step bleow the 2.3.5 method if you are unable to attain root!

    If you are on 2.3.5:

    Root:
    I used the Lazy One Click and it worked perfectly, others have had success with the full manual method.
    I am a manual man, I don't use 1 clicks so I will post this the only way I know how...

    Download the follow file: it contains the exploit, su, Superuser

    Download exploit ---> Exploit.zip

    1) Unzip contents of folder to your Desktop

    2) open a command terminal and navigate to the folder (cd Desktop/Exploit)

    3) type the following commands
    ---> adb push zerg /data/local
    ---> adb push su /data/local
    ---> adb push Superuser.apk /data/local
    ---> adb shell
    ---> cd /data/local
    ---> chmod 777 zerg
    ---> ./zerg

    4) Wait for the root to be gained

    5) type the following commands
    ---> adb shell (only type this if you are no longer in [email protected])
    ---> mount -o rw,remount /dev/null /system
    ---> cat /data/local/su > /system/bin/su
    ---> cat /data/local/Superuser.apk > /system/app/Superuser.apk
    ---> chmod 4755 /system/bin/su
    ---> chmod 4755 /system/app/Superuser.apk
    ---> reboot



    ********************************

    Windows Version
    For the lazy I made you a 1-click ---> 1-click-exploit.zip
    Original Thread on MyDroidWorld: http://www.mydroidworld.com/forums/...-your-phone-back-upgrade-path.html#post106072

    Important for those using Oneclick:
    1.Extract the files from 1-click_exploit.zip.
    2.Enable USB debugging. Do so by going into your settings, then to applications, then to development.
    3.Set your connection type to charge only. You can change your connection type through the notification bar once your are connected.
    4.Make sure you go to Settings, Applications, and check Unknown sources if you haven't done so already.
    5.Click runme.bat while your phone is connected. Be patient and let the program do it's thing. YOUR PHONE WILL REBOOT! Do not be alarmed as this is normal. Your phone should now be rooted.
    Cheers!


    If runme.bat hangs after daemeon starts:

    1.First make sure you have USB Debugging, Unknown Sources, and Charge only connection enabled
    2.If none of these options work, uninstall your drivers and download and install one of these:
    Driver-wise:
    Try this if on 32-bit:http://www.mediafire.com/?71c12qc4a1svqza
    And this for 64-bit:http://www.mediafire.com/?ysphmaz131d3an9

    Proof of Root:
    attachment.php
    This is a terminal screen showing the Atrix 2 (Codenamed Edison, look it up if you must) accessing root.
    6
    well here is root for 2.3.6 thx goes to Dan Rosenberg... i just tested it and my atrix 2 2.3.6 is rooted...

    he is asking for donations for the red cross, please donate if you can...
    wepay.com/donations/droid-4-root-bounty

    this is only for windows, but i guess you can get the instructions from the .bat file and do the same in any console

    by the way it is supposed to be a universal motorola root method...
    5
    where do i say he is taking donations... people should learn to read... and jim, sorry to bring cogeary down from the pedestal where u had him... but yeah he did not help Dan do anything... the batch file and everything was provided by Dan... and his original files did the job quite good, so dunno where u got your info... so lets get this stuff straight... no i didnt say he was taking donations, and yes i did say taking donations based on others work when you did nothing... is a big no no

    vulnfactory.org/blog/2012/02/11/rooting-the-droid-4-a-failed-bounty-experiment/ so that you educate yourself jim

    Edit: anyhow this is my last post about this, cause i might "scare off" some developers

    your attitude and outlook plain sucks.why don't you make that your last post in the a2 forum entirely.
    4
    Thanks for taking the plunge for all of us. :) Let us know how it goes!

    It works great! Successfully rooted an unrooted 2.3.6.

    Here are my personal root/unroot scripts that will be used in the Megatool (when it eventually is released): View attachment 2.3.6Root.zip

    Thank you chan32167 for testing this for Dan Rosenberg and posting it here!
    3
    Hi Jim, thanks for your directions, I really appreciate it..unfortunately I still can't root after trying your method..I've attached screenshots again of what I am seeing...any other suggestions?? Thanks in advance..


    Ok, you are going to have to try it the hard way..... I used this last night on my replacement phone and it worked like a charm, but it is not the easiest for a windows user....

    First remove anything you copied into /data/local with

    Code:

    adb shell
    cd /data/local
    rm ./tmp/*
    rm ./*
    exit
    exit

    End code:

    Now for the root stuff in detail.

    Download the follow file: it contains the exploit, su, Superuser

    Download exploit ---> http://forum.xda-developers.com/attachment.php?attachmentid=767802&stc=1&d=1320119485

    1) Unzip contents of folder to your Desktop

    2) open a command terminal and navigate to the folder (cd Desktop/Exploit)

    3) Run the following commands:

    Code:
    adb push zerg /data/local
    adb push su /data/local
    adb push Superuser.apk /data/local
    adb shell
    cd /data/local
    chmod 755 zerg
    ./zerg

    End code

    4) Wait for the root to be gained, you will be disconnected.

    5) Run the following commands:

    Code:

    adb shell

    (only type the rest of this if you are no longer in [email protected], and your prompt is a "#")

    mount -o rw,remount /dev/null /system
    cat /data/local/su > /system/bin/su
    cat /data/local/Superuser.apk > /system/app/Superuser.apk
    chmod 4755 /system/bin/su
    chmod 4755 /system/app/Superuser.apk
    reboot

    End code