The Droid 3 is the most powerful Droid to date -- its 1Ghz dual-core OMAP processor and Android 2.3.4 make it a speedy and capable device. As with most devices, D3 owners wanted root access in order to take full advantage of all that it had to offer. That day has finally arrived, as the D3 has been rooted by developer drjbliss from the XDA forums.
The rooting process seems to be rather easy, granted you have ADB set up and know how to use it. The vulnerability was found in some proprietary Motorola code that allows specific files to be edited and manipulated into achieving root access.
Here's how to make it happen:
Log in to the device using “adb shell” and type the following commands:mv /data/local/12m /data/local/12m.bak ln -s /data /data/local/12m
Next, physically reboot the device by pressing the power button. When it wakes up, log in using “adb shell” again, and type the following:rm /data/local/12m mv /data/local/12m.bak /data/local/12m mv /data/local.prop /data/local.prop.bak echo "ro.sys.atvc_allow_netmon_usb=0" > /data/local.prop echo "ro.sys.atvc_allow_netmon_ih=0" >> /data/local.prop echo "ro.sys.atvc_allow_res_core=0" >> /data/local.prop echo "ro.sys.atvc_allow_res_panic=0" >> /data/local.prop echo "ro.sys.atvc_allow_all_adb=1" >> /data/local.prop echo "ro.sys.atvc_allow_all_core=0" >> /data/local.prop echo "ro.sys.atvc_allow_efem=0" >> /data/local.prop echo "ro.sys.atvc_allow_bp_log=0" >> /data/local.prop echo "ro.sys.atvc_allow_ap_mot_log=0" >> /data/local.prop echo "ro.sys.atvc_allow_gki_log=0" >> /data/local.prop
ro.sys.atvc_allow_all_adbproperty is a Motorola-specific configuration that prevents ADB from dropping its root privileges. Reboot the device one final time, and on logging in with “adb shell”, you should be presented with a root prompt. Enjoy!
For more information, hit the source links below.