I'm getting an error whenever I try the "adb devices" command. I get the following error >>
"adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon * "
I've installed everything properly and I can clearly see my device when I open up device manager. Any help? Thanks in advance .
adb kill-server
adb devices
Sent from my HTC One X-
absolutelygrim said:
adb kill-server
adb devices
Sent from my HTC One X-
Click to expand...
Click to collapse
It didn't work. Same error
Related
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".
I'm trying to root on 2.20 and am getting stuck on the "Getting CID" step.
I've waited 10 minutes and it still says "Getting CID (waiting for device)". I've factory restored and tried the exploit again, and I'm getting stuck on the same spot every time. I redownloaded the exploit as well. Any ideas?
Root
I have the same problem....would appreciate help...
Edit:
Maybe it'll help mentioning that since I've retried it, it says that CID has already been changed
voltarian said:
I have the same problem....would appreciate help...
Edit:
Maybe it'll help mentioning that since I've retried it, it says that CID has already been changed
Click to expand...
Click to collapse
Mine says the same. I've also tried running the fastboot oem readcidecho command in a different cmd window. Nothing. Still waiting on device.
Root
This is my first time to root an android, and I honestly have only a vague idea of what I'm doing. Going to try once more and then give up for the night. If you figure out the problem do let me know.
waiting for device means.. adb did not recognize any device connected to your PC. ensure you have USB debugging enabled in your phone.. and try again
kancherlapraneeth said:
waiting for device means.. adb did not recognize any device connected to your PC. ensure you have USB debugging enabled in your phone.. and try again
Click to expand...
Click to collapse
USB debugging is enabled. I've restarted the phone, plugged the USB cable in, verified the USB debugging icon appears, select Charge Only, then do adb reboot bootloader. I then try to run fastboot oemreadcidecho with no results. fastboot devices returns nothing.
DERP
Changed USB ports...now it works. I don't even know why this mattered. The first part of the exploit was able to load using the first USB port. Oh well...thanks guys.
I'm having this same issue on a Mac. Anyone have any resolutions?
h1m said:
I'm having this same issue on a Mac. Anyone have any resolutions?
Click to expand...
Click to collapse
you have to start the adb server with root permissions (this means that before doing anything with adb you have to first type sudo)
cuyo11 said:
you have to start the adb server with root permissions (this means that before doing anything with adb you have to first type sudo)
Click to expand...
Click to collapse
Tried that. Still got the same error.
Johns-MacBook-Pro:X_Factor_Windows John$ adb wait-for-device
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Johns-MacBook-Pro:X_Factor_Windows John$ adb restore backup1.ab
Johns-MacBook-Pro:X_Factor_Windows John$ adb shell "sleep 5"
Johns-MacBook-Pro:X_Factor_Windows John$ adb shell "rm /data/data/com.android.providers.telephony/databases/a/b 2>/dev/null"
Johns-MacBook-Pro:X_Factor_Windows John$ adb shell "ln -s /dev/diag /data/data/com.android.providers.telephony/databases/a/b 2>/dev/null"
Johns-MacBook-Pro:X_Factor_Windows John$ adb restore backup2.ab
Johns-MacBook-Pro:X_Factor_Windows John$ adb shell "sleep 5"
Johns-MacBook-Pro:X_Factor_Windows John$ adb push pwn /data/local/tmp
3004 KB/s (64526 bytes in 0.020s)
Johns-MacBook-Pro:X_Factor_Windows John$ adb shell "chmod 755 /data/local/tmp/pwn"
Johns-MacBook-Pro:X_Factor_Windows John$ adb shell "/data/local/tmp/pwn"
[-] Failed.
Johns-MacBook-Pro:X_Factor_Windows John$ adb reboot bootloader
Johns-MacBook-Pro:X_Factor_Windows John$ adb kill-server
Johns-MacBook-Pro:X_Factor_Windows John$ fastboot oem readcid
...
(bootloader) cid: CWS__001
OKAY [ 0.010s]
finished. total time: 0.010s
Johns-MacBook-Pro:X_Factor_Windows John$
Possible solution
Hey I'm just registering on the forum but I've been a long time viewer...
I had the same problem till I read it was a problem on the drivers... what I did is connected the phone and plugged it with HTC sync Manager... the software will install all the drivers for your HTC.... after that just reboot and try again... it worked for me... hope it does the same for you...
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
Hi,
When i do the following command in ADB is get the below reply of both my device and an 5554-Emulator. I know that i can send the commands to my device by prefixing the command with "-d" but is there any way to delete or remove the 5554-Emulator device?
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\System32>adb devices
List of devices attached
emulator-5554 device
HT23NW100700 device
C:\Windows\System32>
"adb disconnect emulator-5554".
Cheers.
maaaaz said:
"adb disconnect emulator-5554".
Cheers.
Click to expand...
Click to collapse
Mmmm did not work..........:
C:\Windows\System32>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
emulator-5554 device
C:\Windows\System32>adb disconnect emulator-5554
No such device emulator-5554:5555
C:\Windows\System32>
Hum yes, it appears to be non working for me either.
It seems that it is just impossible to disconnect an emulator : hxxps://code.google.com/p/android/issues/detail?id=19913
Thanx for googling it for me!.........I should have done that myself. Send that the project manager didn't seem to think there is any problem with there being an emulator listed under devices.
Maybe not, I don't know if it will cause any issues or not, just never remember it being there in the past.
Sent witH desire from One X
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.