[CAUTION!] Make sure you know what your doing before you ROOT your phone. It is your own fault if you kill your phone.
This is a sample log from SuperOneClick
It's that easy!
By following this Guide you Agree with all of the above and consequences that follow
Here are some preparation before we start:
Get Motorola phone drivers for Windows from http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
Get SuperOneclick from http://xdaforums.com/showthread.php?t=803682
Get Motorola phone drivers for Windows from http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
Get SuperOneclick from http://xdaforums.com/showthread.php?t=803682
- Install the Motorola drivers
- in the phone go to Settings > Applications > Development
- select USB Debugging
- connect USB cable
- set USB mode to "Portal & Tools" a.k.a. "PC mode"
- run SuperOneClick
- click Root
- Done!
This is a sample log from SuperOneClick
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
585 KB/s (5392 bytes in 0.009s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
ROOTED
Getting mount path...
/dev/block/mtdblock7
OK
Remounting system with read-write access...
OK
Pushing su...
512 KB/s (26264 bytes in 0.050s)
OK
chmod su...
OK
Pushing Superuser.apk...
571 KB/s (196521 bytes in 0.336s)
OK
Remounting system with read-only access...
OK
Running a SU test...
It's that easy!
Last edited: