I'm trying to root a new Droid 4 for a friend. I rooted one a month or so ago using Motofail without any trouble. But it's not working for me this time.
I'm running Windows 7 x64.
I installed the latest Motorola drivers.
I connected the phone to USB cable and let it install all the drivers with USB Debugging enabled and with it disabled. I did both in Charge only and Mass Storage.
One thing that is unusual in this situation is that the phone hasn't been activated with Verizon. I'm doing this so my friend can keep using his old phone until I have this one set up. I've done this in the past with several Droid Razrs but the other Droid 4 I rooted was already activated. If you think this is causing the trouble, let me know.
Model Number: DROID4
System Version: 6.13.215.XT894
Android Version: 2.3.6
Build Number: 6.5.1_167_DR4-1_M-215
I get the following in command prompt when attempting to root:
[*]
[*] Motofail: Universal Motorola Android Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on Droid 3, Droid Bionic, Droid RAZR, and Droid 4
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] Device found.
[*] Deploying payload...
682 KB/s (501292 bytes in 0.717s)
[*] Owning phone...
[*] Motofail: Universal Motorola Android Root Exploit
[*] Copyright (c) 2012 Dan Rosenberg (@djrbliss)
[*] Exploit complete.
[*] Rebooting device...
[*] Waiting for phone to reboot.
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
[*] Attemping persistence...
adb server is out of date. killing...
* daemon started successfully *
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
[*] Cleaning up...
error: device not found
error: device not found
[*] Rebooting...
error: device not found
error: protocol fault (no status)
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
Can anyone help me? I know you can...
Sounds like your Motorola USB drivers are nonexistent or outdated. I would download the latest USB drivers and try it again. You cannot just go by the drivers Windows 7 downloads, you need to download them from the Motorola website.
---------- Post added at 09:45 PM ---------- Previous post was at 09:43 PM ----------
Here's that link:
http://www.motorola.com/Support/US-EN/Support-Homepage/Software_and_Drivers/USB-and-PC-Charging-Drivers
Thanks for the reply. I downloaded the latest drivers and restarted the computer and now I get this...
[*]
[*] Motofail: Universal Motorola Android Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on Droid 3, Droid Bionic, Droid RAZR, and Droid 4
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
adb server is out of date. killing...
* daemon started successfully *
[*] Device found.
[*] Deploying payload...
550 KB/s (501292 bytes in 0.889s)
[*] Owning phone...
adb server is out of date. killing...
* daemon started successfully *
[*] Motofail: Universal Motorola Android Root Exploit
[*] Copyright (c) 2012 Dan Rosenberg (@djrbliss)
[*] Exploit complete.
[*] Rebooting device...
adb server is out of date. killing...
* daemon started successfully *
[*] Waiting for phone to reboot.
adb server is out of date. killing...
* daemon started successfully *
error: protocol fault (no status)
[*] Attemping persistence...
adb server is out of date. killing...
* daemon started successfully *
error: device not found
failed to copy 'su' to '/system/bin/su': Read-only file system
adb server is out of date. killing...
* daemon started successfully *
Unable to chmod /system/bin/su: No such file or directory
adb server is out of date. killing...
* daemon started successfully *
link failed Read-only file system
* daemon not running. starting it now *
* daemon started successfully *
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
adb server is out of date. killing...
* daemon started successfully *
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
[*] Cleaning up...
adb server is out of date. killing...
* daemon started successfully *
[*] Motofail: Universal Motorola Android Root Exploit
[*] Copyright (c) 2012 Dan Rosenberg (@djrbliss)
[*] Exploit complete.
[*] Rebooting...
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
error: protocol fault (no status)
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
It seems to me to go okay until the phone reboots... at that point the phone trys to activate and I wonder if that's messing up the system. Unless someone has a better solution, I'm going to activate the phone and then try it to see if it will make a difference.
Are you giving the program admin rights?
Sent from my DROID4 using Tapatalk 2
I give admin rights by right-clicking on run.bat and selecting Run as administrator? If yes, I've tried that. The problem isn't specific to Droid 4 as I just now tried rooting a Razr with the same results. It's telling me my "adb server is out of date" and then "device not found".
Can any of you guys tell me how to figure out where the problem is and fix it? It's weird because I've rooted 8 Razrs and 1 D4 before without a problem...
Unroot and reroot.
Sent from my DROID4 using Tapatalk 2
I was never rooted so how can I unroot?
Also make sure your phone is in charge only mode, and the screen is unlocked and on when the process begins.
Yes my phone was in Charge only with screen unlocked.
Thanks to all who are responding!
Try using the Droid 4 utility instead of just Motofail.
Then, like papi was saying, try running the unroot process to get rid of any trace of the exploit. You may want to boot into fastboot and run a data/cache wipe at this point. Then, run the root option again.
I got it guys!!! I copied five files from the Motofail folder: busybox, motofail, run.bat, su and Superuser.apk to my Android-sdk\platform-tools\ folder. I then ran run.bat as an Adminstrator and everything went off without a hitch. Yay!!!
But please, can someone tell me why it worked. I would really like to use this as a learning experience because I just spent a frustrating 8 hours or so fussing with this.
Thanks guys!
mrbuilder
It could have been that somehow the program couldnt find those files in the previous directory
Sent from my DROID4 using Tapatalk 2
Related
I will try to briefly describe the steps I took to get to where I currently to give you an idea of what I tried.
stock
root + 4ever root (R3l3AS3DRoot_Windows_V2.1)
"restore bionic only" option - to upgrade, losing root
OTA Upgrade to .893
root + 4ever root - FAILED
"restore bionic only" option
root + 4ever root - FAILED
pete's moto tools - ROOT FAILED (PetesMotorolaRootTools_v1.07)
pete's moto tools - UNROOT FAILED, cant 'su' of course, trying anything at this point.
What should I do from here?? I want to run .893, rooted. Any other methods I should try?
Code:
********************************************************************************
* *
* dhacker29 and DroidTh3ory Presents: R3L3AS3DRoot for the BIONIC *
* An easier way to Root or Restore your BIONIC on any system Revision *
* This script will give you the option to restore to stock 886 system, *
* root your phone using zergRush, and/or apply 43V3R root *
* *
* A special thanks for the info and files to: *
* http://BriefMobile.com/droid-bionic-recieves-fastboot-recovery-files *
* revolutionary for zergRush https://github.com/revolutionary *
* P3Droid for the 43V3R Root method http://http://www.mydroidworld.com *
* And HUGE thanks to SoulShadow for the procedure!! *
********************************************************************************
*
* PRESS the appropriate number to make your slection and continue
*
* 1. Restore, Root and 43V3R Root a Bionic
* -restores /system to 886 and wipes data and cache
* -roots your phone and installs the 43V3R Root hack
* If you are bootlooping or softbricked you need this option
*
* 2. Root and 43V3RRoot a non-rooted Bionic
* -roots your phone and installs the 43V3R Root hack
* This works with all Bionics (886 and 893 rev).
*
* 3. 43V3RRoot a Rooted Bionic
* This takes a 'rooted' Bionic and installs the 43V3R Root hack
* This works with all Bionics (886 and 893 rev).
*
* 4. Restore Bionic ONLY - No root
* -restores /system, wipes data and cache
* -does NOT root or install 43V3R Root hack
* This works with all Bionics (886 and 893 rev).
* Note that you will still have the same kernel and radio, either .886 or .893
* but your /system partion will be stock .886
*
* 5. Install CheesecakeV2.apk to get the OTA updates
*
* 6. Help - I need more information!
*
* 7. Quit
*
* Type 1, 2, 3, 4, 5, 6, or 7 and then press ENTER: 2
********************************************************************************
* *
* DROID BIONIC R3L3AS3D Root and 43V3R Root *
* *
********************************************************************************
*
* and set USB Mode to Charge Only
*
* READY TO ROOT YOUR DROID BIONIC WHEN YOU ARE!
Press any key to continue . . .
"* Running zergRush exploit..."
1406 KB/s (23052 bytes in 0.016s)
[**] 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 ! 0x00016118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[+] Zerglings found a way to enter ! 0x18
[+] Overseer found a path ! 0x000161e0
[*] Sending 189 zerglings ...
[+] Zerglings caused crash (good news): 0x40122c5c 0x0074
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd25ac9 0xafd39877
[*] Sending 185 zerglings ...
[-] Bad luck, our rush did not succeed :(
* Wait about 30 seconds for the adb server to restart as root
Press any key to continue . . .
* Installing busybox, su, and SuperUser apk...
remount failed: Operation not permitted
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
failed to copy 'su' to '/system/xbin/su': Read-only file system
1415 KB/s (754980 bytes in 0.521s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
link failed Read-only file system
Unable to chmod /data: Operation not permitted
* Installing 43V3R Root...
failed to copy 'mount_ext3.sh' to '/system/bin/mount_ext3.sh': Read-only file system
Unable to chmod /system/bin/mount_ext3.sh: Read-only file system
* All done! Your phone should now be 43V3R rooted!
* Why don't you check out Shift[3]R? You're ready to flash it now
********************************************************************************
Press any key to continue . . .
This fixed me this morning.
Look up Bionic Path Saver 1-Click Method
Then look up the runmebbb script and files to pair with the 1 click method or you probably wont retain root.
Thanks, I'll give it a try and see what happens. For anyone else looking for this, I found it at mydroidworld but more specifically on this multiupload dl.
let me know if you have any problems. after about 12 hours of working on mine last night i finally got my bionic back to booting regularly. im not pro but i think i should be able to lend ya a hang.
Find rota893.zip
When on 55893.. root it.. them update to 901 if you want.
BBB
Sleeping is under rated.
I actually ended up following instructions from droid forums for a variation of the 'bionic path saver'. I got up to step 6 or so, but the kin3xt zip I downloaded just wouldn't flash from recovery.
This was when I realized that I needed clockwork mod installed to do this . I've been a little out of the loop on ROM dev here lately, and didn't realize that ability was even possible yet. I found it on the FAQ page, and am now happily rooted and romed up
Thanks for getting me back on my feet !
Hi all, i was update my droid 3 up to .906. Now i want root my device (never root before), can i use old method like one_click_root?
do a search for motofail. That is the only known method that works for the .906 update.
Failing to Root
I too am attempting to root my Droid 3 for the first time. I tried both motofail from Dan Rosenberg and MotorolaOneClickRoot from Pete Souza. Below is a screen capture of my attempt.
Phone specifics:
Motorola Droid 3 on Verizon Android version 2.3.4 System version 5.7.906.XT862
[*]
[*] Motofail: Universal Motorola Android Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on Droid 3, Droid Bionic, Droid RAZR, and Droid 4
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] Device found.
[*] Deploying payload...
cannot stat 'motofail': No such file or directory
Unable to chmod /data/local/motofail: No such file or directory
[*] Owning phone...
/data/local/motofail: not found
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Attemping persistence...
remount failed: Operation not permitted
failed to copy 'su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
link failed Read-only file system
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
[*] Cleaning up...
/data/local/motofail: not found
rm failed for /data/local/motofail, No such file or directory
[*] Rebooting...
"[*] Exploit complete!"
"[*] Press any key to exit."
Press any key to continue . . .
Thanks in advance,
Bonsai144
Make sure that USB Debugging is selected (under menu->Applications->Development), and also make sure that you select Charge Only mode when you connect to your computer via USB.
For good measure, turn on "Never sleep while charging" or something along those lines. It should be near where you turn of USB Debugging.
linuxgator said:
Make sure that USB Debugging is selected (under menu->Applications->Development), and also make sure that you select Charge Only mode when you connect to your computer via USB.
Click to expand...
Click to collapse
+1
---------- Post added at 04:59 AM ---------- Previous post was at 04:57 AM ----------
LFerryT said:
Hi all, i was update my droid 3 up to .906. Now i want root my device (never root before), can i use old method like one_click_root?
Click to expand...
Click to collapse
you can find the sbf,motofail and .906 update all in my thread...link in my sig
You may also be missing drivers for it...
You can download the Moto Device Manager here
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
and this should be able to install the latest, proper drivers. These may not be needed, but it's just one more step in troubleshooting.
Hello ill post the log here
process requires standard 2.x android firmware.
Press any key to continue . . .
Getting ROOT rights.
* daemon not running. starting it now *
* daemon started successfully *
error: protocol fault (no status)
* daemon not running. starting it now *
* daemon started successfully *
695 KB/s (585731 bytes in 0.823s)
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
error: protocol fault (no status)
Waiting ...
error: protocol fault (no status)
Removing NAND MPU restrictions via SEMC backdoor. Permanent. Require ROOT righ
.
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Waiting ...
adb server is out of date. killing...
* daemon started successfully *
Jeasus please help me somebody via tv i cant do this **** it wont go 807 286 319 pass is 123456 ILL KEEP IT ON
nikolai4os said:
Jeasus please help me somebody via tv i cant do this **** it wont go 807 286 319 pass is 123456 ILL KEEP IT ON
Click to expand...
Click to collapse
check your antivirus
nikolai4os said:
Jeasus please help me somebody via tv i cant do this **** it wont go 807 286 319 pass is 123456 ILL KEEP IT ON
Click to expand...
Click to collapse
Open Task Manager on PC. Just Ctrl+Alt+Del and END process “ADB.exe”; if its running.
As CnC-ROCK said as above..Turn of all kind of Antivirus. Anything. Even a malware checker should be turned off..
These can help..step by step tutorial
http://ijustutter.com/guide-flashing-naa-kernel-custom-rom-x8-w8-x10-mini-pro
http://ijustutter.com/step-by-step-guide-to-unlock-bootloader-of-x8-w8-x10-mini-x10-mini-pro
CnC-ROCK said:
check your antivirus
Click to expand...
Click to collapse
I dont use any.
Try to get new versions of ADB
Do it thought flashtool
Install drivers
Go to plugin/unlock/then the program it will ask you to connect your device(disabled) in flash mode with pressed back button in usb port/then will ask you to switch on your device/then when the Sony Ericsson logo appears connect again your device one more time in usb to complete the unlock(THIS IS IMPORTANT) method
This method always work even with antivirus on
Tip:
If you have issues with SHOW flashmode drivers install also and the Gordons gate
Hello all,
I had unlocked my bootloader. flashed some roms (AOSP), used and thought of returning back to Stock as I wanted to test if the backed up TA can be restored successfully.
So I flashed .434 ftf, relocked the bootloader and tried to use the rooting toolkit to root.. But it is getting stuck in between as not getting any ahead further.. What should I do?
This is what all I can see:
Press any key to continue . . .
### beginüI ###
waiting for device
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
transfer files to your phone part1
adb server is out of date. killing...
* daemon started successfully *
27 KB/s (442 bytes in 0.015s)
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
10 KB/s (170 bytes in 0.015s)
adb server is out of date. killing...
* daemon started successfully *
----------------------------------------------------------------------
[*] description:
1. press the button to restore the data in your phone operation.
adb server is out of date. killing...
* daemon started successfully *
Now unlock your device and confirm the restore operation.
if Restoring data is complete,
Press any key to continue . . .
----------------------------------------------------------------------
[*] description:
1. Dial *#*#7378423#*#* and select "Service tests" in your phone o
2. select "Display" in your phone operation.
* Screen is white until completion of restart
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
executing /data/local/tmp/onload.sh ...
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
----------------------------------------------------------------------
[*] description:
1. push power button, so turn off the screen
2. push power button, so turn on the screen
* Repeat steps 1 and 2
----------------------------------------------------------------------
adb server is out of date. killing...
* daemon started successfully *
mandarjoshiin said:
Hello all,
I had unlocked my bootloader. flashed some roms (AOSP), used and thought of returning back to Stock as I wanted to test if the backed up TA can be restored successfully.
So I flashed .434 ftf, relocked the bootloader and tried to use the rooting toolkit to root.. But it is getting stuck in between as not getting any ahead further.. What should I do?
This is what all I can see:
Press any key to continue . . .
### beginüI ###
waiting for device
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
transfer files to your phone part1
adb server is out of date. killing...
* daemon started successfully *
27 KB/s (442 bytes in 0.015s)
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
10 KB/s (170 bytes in 0.015s)
adb server is out of date. killing...
* daemon started successfully *
----------------------------------------------------------------------
[*] description:
1. press the button to restore the data in your phone operation.
adb server is out of date. killing...
* daemon started successfully *
Now unlock your device and confirm the restore operation.
if Restoring data is complete,
Press any key to continue . . .
----------------------------------------------------------------------
[*] description:
1. Dial *#*#7378423#*#* and select "Service tests" in your phone o
2. select "Display" in your phone operation.
* Screen is white until completion of restart
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
executing /data/local/tmp/onload.sh ...
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
----------------------------------------------------------------------
[*] description:
1. push power button, so turn off the screen
2. push power button, so turn on the screen
* Repeat steps 1 and 2
----------------------------------------------------------------------
adb server is out of date. killing...
* daemon started successfully *
Click to expand...
Click to collapse
Have you usb debugging checked along with unknown sources ?
mileyxperia said:
Have you usb debugging checked along with unknown sources ?
Click to expand...
Click to collapse
Yes bro.. it has already been checked... :crying:
I can tell you it can not be related to your TA restore.
mandarjoshiin said:
Yes bro.. it has already been checked... :crying:
Click to expand...
Click to collapse
Flash again via flashtool full wipe root it with flashtool or binarys tool ?? Try to reinstall drivers ? Reboot pc ?
I reinstalled the drivers and now it has worked fine.. Now I can go ahead and try n see if restore TA works.. :fingers-crossed:
mandarjoshiin said:
I reinstalled the drivers and now it has worked fine.. Now I can go ahead and try n see if restore TA works.. :fingers-crossed:
Click to expand...
Click to collapse
Good luck flashing ta is risky could brick device :laugh:
I tried this one. But it says it only works for 5.0.1 (extreme noob)
http://forum.xda-developers.com/amazon-fire/general/psa-information-regarding-firmware-t3264224
Or in short, not yet
Yes you can.
http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362
http://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
pappasmurfsharem said:
Yes you can.
http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362
http://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
Click to expand...
Click to collapse
I just tried the supertool method on 5.1.1 and it doesn't appear to work. Drivers work fine, batch file boots to fastboot, but when the device restarts, the normal lock screen appears, and the batch file is unable to find the device. I opened another shell window and ADB DEVICES lists the device.
Anyone had any luck on 5.1.1?
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
--------------------------------------------------------------------------------
[*] Big thanks to k4y0z from XDA
[*] Make sure USB Debugging is enabled on your tablet
[*] this tool will boot you into fastboot and root your device.
[*] device will reboot a couple times during this process.
--------------------------------------------------------------------------------
press a key to reboot the device in fastboot mode
< waiting for device >
...
(bootloader) APPEND KERNEL CMDLINE
OKAY [ 0.007s]
finished. total time: 0.008s
resuming boot...
OKAY [ 0.003s]
finished. total time: 0.004s
--------------------------------------------------------------------------------
[*] your device is rebooting and will inject root files.
--------------------------------------------------------------------------------
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
error:
adb server is out of date. killing...
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
4703 KB/s (5904943 bytes in 1.226s)
adb server is out of date. killing...
* daemon started successfully *
error: device offline
adb server is out of date. killing...
* daemon started successfully *
error: device offline
adb server is out of date. killing...
* daemon started successfully *
error: device offline
< waiting for device >
mistermick said:
I just tried the supertool method on 5.1.1 and it doesn't appear to work. Drivers work fine, batch file boots to fastboot, but when the device restarts, the normal lock screen appears, and the batch file is unable to find the device. I opened another shell window and ADB DEVICES lists the device.
Anyone had any luck on 5.1.1?
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
--------------------------------------------------------------------------------
[*] Big thanks to k4y0z from XDA
[*] Make sure USB Debugging is enabled on your tablet
[*] this tool will boot you into fastboot and root your device.
[*] device will reboot a couple times during this process.
--------------------------------------------------------------------------------
press a key to reboot the device in fastboot mode
< waiting for device >
...
(bootloader) APPEND KERNEL CMDLINE
OKAY [ 0.007s]
finished. total time: 0.008s
resuming boot...
OKAY [ 0.003s]
finished. total time: 0.004s
--------------------------------------------------------------------------------
[*] your device is rebooting and will inject root files.
--------------------------------------------------------------------------------
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
error:
adb server is out of date. killing...
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
4703 KB/s (5904943 bytes in 1.226s)
adb server is out of date. killing...
* daemon started successfully *
error: device offline
adb server is out of date. killing...
* daemon started successfully *
error: device offline
adb server is out of date. killing...
* daemon started successfully *
error: device offline
< waiting for device >
Click to expand...
Click to collapse
I got root and xposed working on 5.1.1
http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362/page5
mistermick said:
I just tried the supertool method on 5.1.1 and it doesn't appear to work. Drivers work fine, batch file boots to fastboot, but when the device restarts, the normal lock screen appears, and the batch file is unable to find the device. I opened another shell window and ADB DEVICES lists the device.
Anyone had any luck on 5.1.1?
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
--------------------------------------------------------------------------------
[*] Big thanks to k4y0z from XDA
[*] Make sure USB Debugging is enabled on your tablet
[*] this tool will boot you into fastboot and root your device.
[*] device will reboot a couple times during this process.
--------------------------------------------------------------------------------
press a key to reboot the device in fastboot mode
< waiting for device >
...
(bootloader) APPEND KERNEL CMDLINE
OKAY [ 0.007s]
finished. total time: 0.008s
resuming boot...
OKAY [ 0.003s]
finished. total time: 0.004s
--------------------------------------------------------------------------------
[*] your device is rebooting and will inject root files.
--------------------------------------------------------------------------------
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
error:
adb server is out of date. killing...
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
4703 KB/s (5904943 bytes in 1.226s)
adb server is out of date. killing...
* daemon started successfully *
error: device offline
adb server is out of date. killing...
* daemon started successfully *
error: device offline
adb server is out of date. killing...
* daemon started successfully *
error: device offline
< waiting for device >
Click to expand...
Click to collapse
Almost looks like a loose USB
Same problem here. no luck with 5.1.1. Supertool doesn't work.
ongogo said:
Same problem here. no luck with 5.1.1. Supertool doesn't work.
Click to expand...
Click to collapse
Works perfectly fine.
post in that thread if you need support.
mistermick said:
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] your device is rebooting and will inject root files.
--------------------------------------------------------------------------------
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
error:
Click to expand...
Click to collapse
This indicates you've got some out of date adb drivers installed. Make sure nothing else that uses adb is running (emulator, sync software?) Try taskkill adb in task manager. If that doesn't work you'll need to track down the old drivers and uninstall.
DoLooper said:
This indicates you've got some out of date adb drivers installed. Make sure nothing else that uses adb is running (emulator, sync software?) Try taskkill adb in task manager. If that doesn't work you'll need to track down the old drivers and uninstall.
Click to expand...
Click to collapse
I like how the thing that it said to me 8 or 9 times was the one thing I didn't pay attention to. I'm pretty sure I already had adb installed from when I rooted my TF101. That's probably the issue. I'll give it a shot when I get home.
*Edit: I uninstalled all of the HTC crap I had, whatever old version of minimal adb and fastboot was running, and reinstalled the platform-tools from the sdk, and the supertool finally was able to complete successfully. Now I have a $35 android tablet that is actually usable!