I was following the guide to unlock the bootloader for the Xperia X8 and have gotten here:
Code:
Getting ROOT rights.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
1540 KB/s (585731 bytes in 0.731s)
error: protocol fault (no status)
Waiting...
Removing NAND MPU restrictions via SEMC backdoor. Permanent. Require ROOT rights.
66 KB/s (3087 bytes in 0.045s)
success
Waiting ...
Getting ROOT rights.
Waiting ...
It's been stuck on waiting for at least 15 minutes. There's also no USB Debugging notification, leading me to believe that the phone is disconnected. What should I do? Should I just reconnect the phone or redo the whole process?
Never mind. Just disconnected the phone and rebooted it and restarted the program and now it works.
Related
SuperOneClick v1.8.0.0
Checking drivers...
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Getting OS Version...
2.1-update1
OK
Pushing psneuter...
1078 KB/s (585731 bytes in 0.530s)
OK
chmod psneuter...
OK
Running psneuter...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running psneuter...
ROOTED
Pushing busybox...
1056 KB/s (1062992 bytes in 0.983s)
OK
chmod busybox...
OK
Getting mount path...
rootfs / rootfs ro 0 0
FAILED
tell me what is this ?? is my phone rooted ? but i think no help pls
Try the newest version of SuperOneClick at http://forum.xda-developers.com/showthread.php?t=803682
Make sure .NET Framework v2.0 or above is installed on your PC if you're on windows.
Make sure that Android drivers for your phone are properly installed.
Make sure you run SuperOneClick as administrator.
And yes use the latest version.
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
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:
==============================================
= =
= XZDualRecovery =
= Maintained by [NUT] =
= =
= For Many Sony Xperia Devices! =
= =
==============================================
1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on an unrooted (Lollipop 5.0) ROM using rootkitXperia
4. Install ADB drivers to windows
5. Open an ADB shell
6. Exit
Please choose install action.
[1,2,3,4,5,6]?1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
adb server is out of date. killing...
* daemon started successfully *
Device found!
=============================================
Getting device and ROM info
=============================================
Device model is C5502
Firmware is 10.7.A.0.222
Android version is 5.1.1
error: device unauthorized. Please check the confirmation dialog on your device.
=============================================
Step2 : Sending the recovery files.
=============================================
adb server is out of date. killing...
* daemon started successfully *
mkdir failed for /data/local/tmp/recovery, File exists
adb server is out of date. killing...
* daemon started successfully *
7 KB/s (31 bytes in 0.003s)
adb server is out of date. killing...
* daemon started successfully *
2031 KB/s (18170 bytes in 0.008s)
adb server is out of date. killing...
* daemon started successfully *
error: device unauthorized. Please check the confirmation dialog on your device.
adb server is out of date. killing...
* daemon started successfully *
329 KB/s (12812 bytes in 0.038s)
adb server is out of date. killing...
* daemon started successfully *
2100 KB/s (65965 bytes in 0.030s)
adb server is out of date. killing...
* daemon started successfully *
611 KB/s (3159 bytes in 0.005s)
adb server is out of date. killing...
* daemon started successfully *
2217 KB/s (29204 bytes in 0.012s)
adb server is out of date. killing...
* daemon started successfully *
77 KB/s (699 bytes in 0.008s)
adb server is out of date. killing...
* daemon started successfully *
error: device unauthorized. Please check the confirmation dialog on your device.
adb server is out of date. killing...
* daemon started successfully *
188 KB/s (1202 bytes in 0.006s)
adb server is out of date. killing...
* daemon started successfully *
2505 KB/s (96956 bytes in 0.037s)
adb server is out of date. killing...
* daemon started successfully *
2266 KB/s (870760 bytes in 0.375s)
adb server is out of date. killing...
* daemon started successfully *
3308 KB/s (3413045 bytes in 1.007s)
adb server is out of date. killing...
* daemon started successfully *
4471 KB/s (2313849 bytes in 0.505s)
adb server is out of date. killing...
* daemon started successfully *
1399 KB/s (14346 bytes in 0.010s)
=============================================
Step3 : Setup of dual recovery.
=============================================
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
error: device unauthorized. Please check the confirmation dialog on your device.
Look at your device and grant supersu access!
Press any key to continue AFTER granting root access.
adb server is out of date. killing...
* daemon started successfully *
tmp-mksh: /data/local/tmp/recovery/busybox: can't execute: Permission denied
Press any key to continue . . .
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
=============================================
Installation FAILED!
Please copy and paste the contents of this
window to the DevDB thread for troubleshooting!
=============================================
Press any key to continue . . .