I'm trying to root my phone using the method here: http://forum.xda-developers.com/showthread.php?t=1709424
without much luck... On page 33 one person mentioned getting to Daemon successfully started and having it just hang there, which is my problem, then said it was just dumb user error with never explaining what it was. Several people followed up with the same problem but no answer. Initially I started it up and it would just start up the daemon and sit, so I rebooted my phone to try again and now it doesn't even do that, it just spits out Exploit by beaups, script by designgears and sits there with a blinking cursor.
Phone is in charge only mode, USB Debugging enabled, HTC sync not running, have tried multiple USB cables and ports. I have a mac and am trying this through VirtualBox (and yes, the USB device for the phone is attached - not mounted as a disk). I can only guess this is what's causing the problem but I don't really see why it shouldn't work. Anything I can try?
Did you set the date on the phone forward a day or 2 before you tried again, like the thread says?
I didn't use this root method (rooted back on 1.73). But another person posted having similar troubles. Reinstalling the HTC drivers did the trick for that person.
redpoint73 said:
Did you set the date on the phone forward a day or 2 before you tried again, like the thread says?
I didn't use this root method (rooted back on 1.73). But another person posted having similar troubles. Reinstalling the HTC drivers did the trick for that person.
Click to expand...
Click to collapse
Date doesn't really come into play since the installer doesn't go anywhere. What HTC drivers? There's no mention of those. On a whim I installed HTC Sync and rebooted, I do get farther but don't seem to really get anywhere still. It does more stuff but seems like it keeps killing the server and a check for software updates finds nothing to update.
Exploit by beaups, script by designgears
* server not running *
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
Go to Settings, ATT Software update, check for updates.
Waiting for device to Reboot...
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
Done! Rebooting...
error: more than one device and emulator
Press any key to continue . . .
Click to expand...
Click to collapse
Well I realized that last attempt had HTC Sync running, so I killed that. Now I'm back to sitting at daemon successfully started. For fun I tried to do the non one click root, however indeed after doing the first command I get the more than one device or emulator connected error. adb devices lists my phone once initially, but after running: adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb devices lists my phone multiple times and I can go no further. I might have to try and find a real windows computer to use, maybe the vm is just doing something funky here.
chadcf said:
What HTC drivers? There's no mention of those. On a whim I installed HTC Sync and rebooted.
Click to expand...
Click to collapse
The drivers get installed with HTC Sync. So re-installing Sync would have fixed the drivers, if that was causing the issue. Sorry I can't help you anymore than the suggestions I've already made. Hopefully, somebody else can help.
chadcf said:
Well I realized that last attempt had HTC Sync running, so I killed that. Now I'm back to sitting at daemon successfully started. For fun I tried to do the non one click root, however indeed after doing the first command I get the more than one device or emulator connected error. adb devices lists my phone once initially, but after running: adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb devices lists my phone multiple times and I can go no further. I might have to try and find a real windows computer to use, maybe the vm is just doing something funky here.
Click to expand...
Click to collapse
That's a typical VM issue. You can run right from linux or mac with the manual method. Just get the right version of ADB for your O/S and add a ./ before each command that starts with "adb".
Hello
I'm trying to run a shell session but getting this error message
adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Ok, it seems obvious what the problem is but I can't find a solution
The phone is plugged, Fastboot seems to recognise the connexion as says fastboot USB
HBOOT version 1.14
Not sure what to do
Any idea?
Many thanks
EDIT Problem Solved - should launch from Recovery - Thank you
I recently received my XT1540. I was going to wait the 14 day window I have to return the device prior to unlocking bootloader. In the mean time, are there any ADB commands I can run to gain familiarity of ADB and to ensure I have the proper Motorola drivers?
'adb devices' will let you know if the device is recognized (drivers installed, etc).
Plug in to PC, turn on USB debugging on phone, run the above command. The phone should prompt for you to accept your computer's RSA key, adb should list your device as 'device'.
There is also this: http://developer.android.com/tools/help/adb.html
use the following command to print all adb commands
adb --help
So I get the following:
Code:
C:\Desktop\adb-fastboot-latest_win_linux>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
ZY333TKQ99 unauthorized
I assume this means my drivers are installed correctly and that "unauthorized" is because bootloader is not unlocked. Is this correct?
MrTooPhone said:
So I get the following:
Code:
C:\Desktop\adb-fastboot-latest_win_linux>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
ZY333TKQ99 unauthorized
I assume this means my drivers are installed correctly and that "unauthorized" is because bootloader is not unlocked. Is this correct?
Click to expand...
Click to collapse
Probably unauthorized because you need to accept RSA key request on your phone. You should see a dialog on your phone like this.
quakeaz said:
Probably unauthorized because you need to accept RSA key request on your phone. You should see a dialog on your phone like this.
Click to expand...
Click to collapse
That was it. I did not even look at the phone.
My Device : Lenovo A1000 Android 5.0 SC8830
My PC : Windows XP SP3
Start
C:\>ADB\fastboot devices
1234567890 fastboot
It is ok.
then
C:\>\ADB\adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
then try
C:\>adb shell
Windows show me this.
The procedure entry point WSAPoll could not be location in the dynamic link library WS2_32.dll
and one more question.
How to press device for oem unlock?
C:\>ADB\fastboot oem unlock
.....
I can not find a method to get twrp to the GT-I9506.
With Odin it does not work even it says all was programmen OK (still remains the old recovery)
and with adb it doesn't work too:
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
01b293754 sideload
adb usb
error: closed
error: closed
adb sideload recovery.img
error: protocol fault (no status)
error: protocol fault (no status)
What can I do (did try various usb cable) ?
Found the solution: You have to disable "Auto Reboot" in Odin !