DroidForums.net | Android Forum & News
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
My droid bionic won't root
- Thread starter derikogreen
- Start date
derikogreen
Member
Ok I uninstalled my drivers and reinstalled them. Still not rooted... These are my drivers and my Device manager.
MotorolaDeviceManager_2.2.28.exe
USB COMPOSITE DEVICE
USB MASS STORAGE DEVICE
MOT COMPOSITE ADB INTERFACE
MOTOROLA XT875 USB DEVICE
MOTOROLA XT875 USB DEVICE
Windows 7 says they are ALL READY TO USE Does this verify my drivers are up to date and compatible.
derikogreen
Member
Not yet still trying
Try this...
- Download this file - save it to your desktop.
- Right click on the .zip on your desktop and choose "extract all" then on the next window choose "extract"
- This should create an "adb-windows" directory on your desktop with four files in it.
- Once done, make sure your phone is plugged in and usb debugging is enabled (settings > applications > development > make sure usb debugging is checked) and it's set to Charge Only - not usb mass storage
- do a shift+right-click on that adb-windows directory, and choose "open command window here"
- In the dos prompt that opens up, type "adb kill-server" (without the quotes) - it should show nothing and move to the prompt again
- Input "adb devices" (without quotes) - it should return "list of devices" and then below that a serial # and title of some sort. If it only returns "list of devices" with no serial # or anything else, then it's not connected. If it DOES show a serial # after "list of devices", then you should be good to go.
- Just to play it safe, again input "adb kill-server" (without quotes) - then leave your phone plugged in and try MotoFail again.
- And just to make sure, you want the Gingerbread version of Motofail (see here).
Last edited:
derikogreen said:
Definitely correct drivers, mark that off the list. I'm so not trying to be annoying but you DID reboot the PC somewhere in there, right? After the uninstall reinstall and before the root attempt? Are you getting the same adb outdated message?
The command line adb test is definitive. If you get a serial number yay, if not nay. If you don't get a # the first or second try switch to a different USB port. If you do happen to have an extra cable try it as well.
Last edited:
derikogreen
Member
I assumed you wanted me to press enter after I typed in adb kill-sever, and adb devices. I did exactly as you said and I received a serial number for a stated device. The first time it gave me a serial number, then as you said I played it safe and entered adb kill-server again it said server not connected and still wouldn't root thru Motofail saying the usual "adb killing sever" failed message. So i tried the Command Prompt again and after entering the final "adb kill-server" a long message appeared about THE ANDROID DEBUGG VERSION 1.0.26. as if it worked. So i ran run.bat from the Motofail folder and i didn't see the adb killing server start off message. i saw what looked to be my phone starting to root which said Waiting for device, Device found, "Deploying payload" but then the other failed messages started coming after that starting with cannot stat 'motofail':no such file directory Unable to chmod/data/local/motofail" No such file or directory. So it seems that we were close to rooting my phone because I have never seen the "Deploying payload" message and that's what I have been waiting to see because that's what I remember seeing on youtube when a phone is successfully rooted. What else could the problem be?
derikogreen
Member
Trust me your not annoying, I appreciate the help. i didn't reboot my computer after I uninstalled and reinstalled my drivers before i tried to root. I did get the same adb killing server message at that time. I will uninstall and reinstall again and then reboot before trying to root again. I did get the serial number when I tried the command prompt and it seems like i got a little bit closer to rooting yet it still failed( read my last reply to jntdroid
and you will see what I'm talking about. I didn't see the "adb killing server" message and it almost rooted, at least it seemed that way. I have a couple of other usb cords but they aren't motorola or verizon cords.derikogreen
Member
There are seven files in my motofail folder which i keep in another Folder on my desktop called Root and unroot.
Right click run.bat and select RUN, you should get "This application may be dependent on other compressed files in this folder. For the application to run properly it is recommended you first extract all files", select extract all, back to that same directory, now plug your phone in with USB debugging on and in charge only....Double click run.bat, wait for the dos screen to open and "press any key to root" or whatever it says, phone should reboot once or twice, wait a couple or five minutes and watch closely, you should be rooted.
Last edited:
linuxgator
Member
You can also kill the adb server by selecting it in windows task manager and clicking on end process. That is the best way in my opinion. Once you do that, but you should be able to root with the Motofail script. Just don't try any other commands that might invoke adb before running the script.
Sent from my DROID BIONIC using Tapatalk
Sent from my DROID BIONIC using Tapatalk
you know your drivers are good, you know your adb setup is good, you know you've unzipped the exploit injector, the only thing that could be left is settings on the phone, and I'm almost 100% sure you've got those right, you should be rooted at this point :icon_eek::blink:
derikogreen
Member
When I right click run.bat I only see run as administrator and when I select that it just starts the motofail again and of course if failed again when i pressed any key. Still unrooted