• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROOT] tehRoot v1.1.1 (5.5.866 to 5.7.893) [1700+ downloads]

Ok, I've been trying to get this working, but so far all it's done is add to my frustration.

My Device:
Motorola Droid bionic on Verizon.

system version (Settings>About Phone) is 5.5.893.XT875.Verizon.en.US

Steps I've taken:
Before connecting the phone, i enabled USB debugging via ticking the check-box found at: Settings>Applications>Development>USB Debugging

I connect the phone, and it is immediately recognized by my computer, as I already have the drivers for the phone installed.

I downloaded and ran "tehroot" three or four times, each time getting the same message stating that "ADB" couldn't be found. I deleted the unzipped directory of files, deleted the Zip, rebooted my computer and phone, redownloaded the zip file, confirmed the settings on the phone where were they should be, as listed above and again, the result can be viewed in the screenshots below. Note, I attempted to use the Motorola drivers bundled with Tehroot, but they could not be found either:

Downloaded zip file on my desktop:
screenshot1.jpg


Next, The files in the Directory (NOT the zip file) after extraction (you can see on the left in the explorer window that the zip archive is not what is selected):
screenshot2.jpg


Next, after running the batch file, selecting "1" for "root & 43v3r root", then selecting "2" for the 64 bit version of the drivers:
screenshot3.jpg


Then finally, after I click "ok", it automatically goe into the screen where I would assume it would give me the play by play on how the rooting was going. Instead, it tells me twenty or so times that it can't find the 'adb' file that is clearly in the same directory as it is, and then lies to me about my phone being rooted lol:
screenshot4.jpg


So... yeah.... any advice?
 
Upvote 0
Solved!! sorry if I wasted your time looking into it... I'm so used to right clicking things and running as administrator...

I tried without running as admin and it works fine

FYI, if you want this to work DO NOT run as administrator!

Thank you, that is all.

Don't worry about it.

This is probably a "start directory" problem. The program expects to be run and given it's own path to start in. But if you run as admin, it most likely changes that to a different path. It's like how when you open up the command prompt, you start in a certain directory, except in this case that start area needs to be the folder.

Unfortunately there really isn't a way to fix this unless I make some sort of packaged exe that forces a certain directory, but that's annoying to setup.

Anyhow, I'm glad it's all working!
 
Upvote 0
Hey, i tried the tehroot for .893 you posted. After using it i can use safestrap, it force closes after install when I try to open it. I looked on the web and they say something along the line it cant get su permission and they suggested re rooting. when i did i got the follow errors...

[*] 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 files...
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
2340 KB/s (843503 bytes in 0.352s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
+
+ 43V3R Rooting.
failed to copy 'mount_ext3.sh' to '/system/bin/mount_ext3.sh': Read-only file sy
stem
Unable to chmod /system/bin/mount_ext3.sh: Read-only file system
+ Congratulations! Your Droid Bionic is now rooted and 43V3R Rooted.

Any help would be great and thanks in advance.
 
Upvote 0
Hey, i tried the tehroot for .893 you posted. After using it i can use safestrap, it force closes after install when I try to open it. I looked on the web and they say something along the line it cant get su permission and they suggested re rooting. when i did i got the follow errors...

[*] 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 files...
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
2340 KB/s (843503 bytes in 0.352s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
+
+ 43V3R Rooting.
failed to copy 'mount_ext3.sh' to '/system/bin/mount_ext3.sh': Read-only file sy
stem
Unable to chmod /system/bin/mount_ext3.sh: Read-only file system
+ Congratulations! Your Droid Bionic is now rooted and 43V3R Rooted.

Any help would be great and thanks in advance.

Ah yes, the blue flames.

What version of the system software are you running?
 
Upvote 0
root and 43V3RRoot. put the 901zip on the sd, went to recovery mode, applied the update. when it was successful i rebooted. Appeared to work.

That's very strange. If you 43V3RRooted, it should have stuck.

In fact, I double checked the code from the Pathsaver to make sure that everything checked out.

The only option now is to use the Pathsaver to get root and 901 together.

Check the sticky for that link.
 
  • Like
Reactions: Trampi
Upvote 0
Worked for me on the first try coming from .893
Thanks a bunch! I just did root only btw. FREEDOM!

You should build an unroot option into this as well, would be sweet!

Why would anyone ever want to unroot? :D

I'd have to learn what the proper method for that is, if there is one. No other root tool for the bionic other than pete's old one have that.

There's always the OTA Root Keeper app that hides root.
 
  • Like
Reactions: SNeitzel
Upvote 0
It didn't work.

I have Windows XP SP3. The Motorola drivers v.5.40 32bit Drivers are installed.
USB debugging is on.
USB set to Charge Only.

I ran the .bat file from a CMD prompt; not from the Windows folder.

Ran with option 1 for Root and 43V3R Root. It seem to run OK up until it got to:

[+] Rush did it ! It's a CG, man !
[+] Killing ADB and restarting as root... enjoy!


Then I got:

error: device not found even though the Bionic was still plugged in.
+ Waiting for phone to reboot (it never did)
* daemon not running. starting it now *
* daemon started successfully


At this point the Droid froze. I had to pull the battery to restart it. The script didn't move.
After it rebooted I plugged the USB cable back in and the script began again with:

+ Installing files...
remount failed: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
Unable to chmod /system/xbin/su: Read-only file system
link failed File exists
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: Read-only file system
2108 KB/s (0 bytes in 843503.000s)
pkg: /data/local/temp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
+
+ 43V3R Rooting.
failed to copy 'mount_ext3.sh' to '/system/bin/mount_ext3.sh': Read-only file system
Unable to chmod /system/xbin/mount_ext3.sh: Read-only file system
+ Congratulations! Your Droid Bionic is now rooted and 43V3R Rooted.
+
+ Press ENTER to return to the main menu
Press any key to continue...

I tried Option #2 but got basically the same thing.What am I doing wrong? BTW I am a total newbie, so please speak "English". :)
 
Upvote 0
It didn't work.

I have Windows XP SP3. The Motorola drivers v.5.40 32bit Drivers are installed.
USB debugging is on.
USB set to Charge Only.

I ran the .bat file from a CMD prompt; not from the Windows folder.

Ran with option 1 for Root and 43V3R Root. It seem to run OK up until it got to:

[+] Rush did it ! It's a CG, man !
[+] Killing ADB and restarting as root... enjoy!


Then I got:

error: device not found even though the Bionic was still plugged in.
+ Waiting for phone to reboot (it never did)
* daemon not running. starting it now *
* daemon started successfully


At this point the Droid froze. I had to pull the battery to restart it. The script didn't move.
After it rebooted I plugged the USB cable back in and the script began again with:

+ Installing files...
remount failed: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
Unable to chmod /system/xbin/su: Read-only file system
link failed File exists
filed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: Read-only file system
2108 KB/s (0 bytes in 843503.000s)
pkg: /data/local/temp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
+
+ 43V3R Rooting.
failed to copy 'mount_ext3.sh' to '/system/bin/mount_ext3.sh': Read-only file system
Unable to chmod /system/xbin/mount_ext3.sh: Read-only file system
+ Congratulations! Your Droid Bionic is now rooted and 43V3R Rooted.
+
+ Press ENTER to return to the main menu
Press any key to continue...

I tried Option #2 but got basically the same thing.What am I doing wrong? BTW I am a total newbie, so please speak "English". :)

Run it from Explorer, not as an Administrator. If that doesn't work, then we'll have to figure this one out. I'm a full time student, so I can't always give quick support as I have higher priorities... :eek:
 
Upvote 0
I have been reading different forums most of the afternoon and I my brain feels like mush. I only have one question for now. If I use tehRoot v1.1 to root my Bionic how do I unroot it if necessary? I'm really sorry if this has been covered and I missed it.

Thanks for the help.

I've never tested these methods myself, but just some information for you to look over.

DROID Bionic Root/Unroot Tool Also Available Now – Droid Life

How to Unroot Droid Bionic! - YouTube
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones