The DROID3 has reportedly been rooted by XDA member djrbliss, one of the dedicated few that have worked non-stop on the device over the last few weeks. No photo evidence has been presented just yet, but we may have it within the next hour.
And I should point out that while this is huge news for D3 owners, this might be bigger news for potential DROID Bionic owners. Since both will likely run similar everything including Android 2.3.4, we can cross our fingers that this root method will work on it as well.
Update: Here is your photo evidence and instructions…
Update 2: The 1-click easy root has already been released here.
Instructions (via vulnfactory):
The Exploit
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/12mNext, 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.propThe
ro.sys.atvc_allow_all_adb
property 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!
Cheers Raj!
Collapse Show Comments114 Comments