For those of you new to Droid Bionic rooting, here’s a root guide you can follow:
- First, you will want to root your Droid Bionic, please see How to Root Droid Bionic.
- After rooting, I highly recommend you to install Safestrap recovery, which is much safer when installing new ROMs.
- To install new ROMs, here’s a tutorial you can follow, see How to Install ROM using Safestrap recovery.
- Before installing new ROM, make sure you backup all your apps using Titanium Backup app so you can restore your apps after installing a new ROM. (Installing a new ROM will erase all your personal settings, apps, etc…etc…)
- Once you’ve done everything, you can try out new ROMs, see our Droid Bionic ROMs category.
- If you need to get your Droid Bionic completely back to stock, please see our Droid Bionic Unroot category.
Subscribe via RSS
Pingback: How to Root Droid Bionic! [NEW][5.5.893] | Droid Bionic Root
Just got the 5.9.902 update, had to unroot to get it.
Is there a new one click root, so i can reroot.
Thanks for the help
Jack
Jack,
Any luck getting your Bionic rooted?
Im with Jack on this one. The 5.9.902 killed my root, Any updates on what we can do?
I did the motofail root and it works on the bionic with 5.9.902 software on your system.
I just got the Bionic and I am trying to root it. I have system version 5.9.902.
After running the runme.bat I get the following error.
“failed to copy ‘files superuser.apk’ to ‘/system/app/./superuser.apk’ read-only file system”
How can I resolve this?
—————————————————————
Easy rooting toolkit (v2.0)
created by DooMLoRD
Modified by Frasertag
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
—————————————————————
[*] This script will:
(1) root ur device using latest zergRush exploit (10 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable “USB DEBUGGING”
from (Menu\Settings\Applications\Development)
(3) enable “UNKNOWN SOURCES”
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip “PC Companion Software” prompt on device
—————————————————————
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
— STARTING —-
— WAITING FOR DEVICE
adb server is out of date. killing…
* daemon started successfully *
— cleaning
rm failed for *, No such file or directory
— pushing zergRush”
711 KB/s (22776 bytes in 0.031s)
— correcting permissions
— executing zergRush
[**] 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 ! 0×00016118
[*] Scooting …
[*] Sending 149 zerglings …
[*] Sending 189 zerglings …
[-] Hellions with BLUE flames !
[1] Segmentation fault ./data/local/zer…
— WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle “USB DEBUGGING” (first disable it then enable it)
— DEVICE FOUND
— pushing busybox
1343 KB/s (1075144 bytes in 0.781s)
— correcting permissions
— remounting /system
mount: permission denied (are you root?)
— copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
— correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
— correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
— installing busybox
/system/xbin/busybox: not found
— pushing SU binary
failed to copy ‘files\su’ to ‘/system/bin/su’: Read-only file system
— correcting ownership
Unable to chmod /system/bin/su: No such file or directory
— correcting permissions
Unable to chmod /system/bin/su: No such file or directory
— correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
— pushing Superuser app
failed to copy ‘files\Superuser.apk’ to ‘/system/app/./Superuser.apk’: Read-only
file system
— cleaning
— rebooting
I’m also getting no where… I get the following messages from busybox:
busybox: /system/xbin/acpid: Read-only file system
busybox: /system/xbin/addgroup: Read-only file system
busybox: /system/xbin/adduser: Read-only file system
busybox: /system/xbin/adjtimex: Read-only file system
busybox: /system/xbin/arp: Read-only file system
busybox: /system/xbin/arping: Read-only file system
busybox: /system/xbin/ash: Read-only file system
busybox: /system/xbin/awk: Read-only file system
busybox: /system/xbin/basename: Read-only file system
busybox: /system/xbin/beep: Read-only file system
busybox: /system/xbin/blkid: Read-only file system
….
In the end, no root permission. System version 5.9.902.XT875. Any updates?
Hey how do i unroot my bionic with the motofail already on it?
I am trying to root my bionic but when i do it, it only restarts my phone once and not three times as the guide says. What am i doing wrong?
If I am running an older ROM am I able to install the latest bionic update without reverting to the factory ROM first?