Originally Posted by nicbennett
*Daemon not running, starting it now on port 5037*(this does successfully start the adb.exe process)
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon*
Click to expand...
Click to collapse
Originally Posted by snovvman
W7/64.
ADB worked for me for months. I used it regularly. The last thing I did was *trying* to use Wireless ADB Widget and issueing ADB TCPIP command. I have made no changes to the system.
The error occurs when no device device connected. Same error when device IS connected.
-Downloaded ADB/SDK again to a different directory, same error
-Updated USB driver and SDK components, same error
-Disabled all firewall/anti-malware/anti-virus, same error
-Rebooted multiple times, same error off boot
-Port 5037 is not bound by any app or process
-ADB, upon failed load, is not listed in Taskmgr, nothing to kill
-Deleted temp files
-Issued at prompt: ADB Disconnect, ADB USB, ADB devices: All return same error as above
-Issued at prompt: ADB kill-server, only prompt returns
Read lots of posts on the web, nothing helps.
I am really interested in a solution and would like to understand what is causing the problem. If in fact it is a configuration issue, where is the ADB config file?
Thanks.
Edit: I am running the command prompt as an administrator.
Click to expand...
Click to collapse
I originally added my post to this thread in the Nook forum. I don't think there is enough expertise in that forum to help with this problem.
The bottom line is that ADB no longer works and I can't figure out why (see quoted text above). I would imagine that someone here would have an answer for this. Please help!
Thanks.
Only thing I would try it open Task Manager and go to processes and close anything that is adb or adb.exe.
DGreen1 said:
Only thing I would try it open Task Manager and go to processes and close anything that is adb or adb.exe.
Click to expand...
Click to collapse
In this case, ADB never starts. It does not work even after a fresh reboot. It is not found in Taskmgr nor Process Explorer.
snovvman said:
In this case, ADB never starts. It does not work even after a fresh reboot. It is not found in Taskmgr nor Process Explorer.
Click to expand...
Click to collapse
Is what he meant was to kill any process that is using adb. This is not only a process that is Android related etc. My buddy had your exact same problem because he had his external hd connected to his computer before trying to run adb. Restarting and killing processes that were using adb on his computer did the trick. Hope this helps!
My problem was Windows
snovvman said:
The error occurs when no device device connected. Same error when device IS connected.
. . .
I am really interested in a solution and would like to understand what is causing the problem.
Click to expand...
Click to collapse
In my case, the problem was Windows Vista. From day one, Windows refused to successfully install the USB drivers for the EVO (with the very helpful diagnostic message: "Windows encountered an error installing..."). I have never been able to use adb, and this meant that all the rooting (and update/upgrade) guides that required adb had to be adapted to getting the file(s) onto the SD card, and then using Terminal Emulator (or similar app) to get the job done.
I've just completed a disk-wipe-and-reinstall of Windows on my laptop, and hope to find the time next week to install all the SDK goodies and make sure that the USB subsystem recognizes my EVO. I'm fed up with not being able to use adb, and that, along with Windows Update failing to install over a dozen security patches, finally pushed me over the edge into a re-install. Auuugh! The pain!
Yellowcard8992 said:
Is what he meant was to kill any process that is using adb. This is not only a process that is Android related etc. My buddy had your exact same problem because he had his external hd connected to his computer before trying to run adb. Restarting and killing processes that were using adb on his computer did the trick. Hope this helps!
Click to expand...
Click to collapse
Interesting, but I haven't been able to find any other service that is bound to adb and I have no other USB devices connected. Thanks for chiming in though.
tgi007 said:
In my case, the problem was Windows Vista. From day one, Windows refused to successfully install the USB drivers for the EVO (with the very helpful diagnostic message: "Windows encountered an error installing..."). I have never been able to use adb, and this meant that all the rooting (and update/upgrade) guides that required adb had to be adapted to getting the file(s) onto the SD card, and then using Terminal Emulator (or similar app) to get the job done.
I've just completed a disk-wipe-and-reinstall of Windows on my laptop, and hope to find the time next week to install all the SDK goodies and make sure that the USB subsystem recognizes my EVO. I'm fed up with not being able to use adb, and that, along with Windows Update failing to install over a dozen security patches, finally pushed me over the edge into a re-install. Auuugh! The pain!
Click to expand...
Click to collapse
For me, I have been able to get two Vista and one Windows 7 computer to work with ADB and HTC drivers the first time. I also have an Epic, and the Samsung drivers installed fine as well (even though they are known to have issues).
Unfortunately, ADB just "broke" one day.
I keep thinking that the Evo community has enough brains and knowledge to sort this out quickly...
Have you updated the sdk recently?
The updated sdk moves the adb files from the tools folder to another folder called platform-tools.
I have adb working properly on both my vista machine and my ubuntu machine hosted on my vista machine.
If you have installed htc sync before uninstall it and the htc driver installer.
Redownload htc sync and the adb files (adb.exe and adbwinapi.dll is all you need). Since adb was working correctly before I'm assuming your java is installed correctly as well.
Reinstall htc sync. When that finishes I suggest a reboot. When you've rebooted uninstall htc sync but leave the htc driver installer. Reboot again.
When you've rebooted again enable usb debugging on your device and connect it to your pc choosing charge only.
This should hopefully reinstall the usb drivers correctly. On vista it installs as adb device or something along those lines.
If the drivers install correctly you should be able to run adb from the directory your two files are in (desktop for example).
If you want, send me a pm with your gtalk username and I can help you troubleshoot it.
lovethyEVO said:
Have you updated the sdk recently?
The updated sdk moves the adb files from the tools folder to another folder called platform-tools.
I have adb working properly on both my vista machine and my ubuntu machine hosted on my vista machine.
If you have installed htc sync before uninstall it and the htc driver installer.
Redownload htc sync and the adb files (adb.exe and adbwinapi.dll is all you need). Since adb was working correctly before I'm assuming your java is installed correctly as well.
Reinstall htc sync. When that finishes I suggest a reboot. When you've rebooted uninstall htc sync but leave the htc driver installer. Reboot again.
When you've rebooted again enable usb debugging on your device and connect it to your pc choosing charge only.
This should hopefully reinstall the usb drivers correctly. On vista it installs as adb device or something along those lines.
If the drivers install correctly you should be able to run adb from the directory your two files are in (desktop for example).
If you want, send me a pm with your gtalk username and I can help you troubleshoot it.
Click to expand...
Click to collapse
Thanks for replying. I had already updated ADB (in platform-tools) before started having this problem. I had also uninstalled HTC sync (reboot, launch ADB w/o HTC sync, same problem) and reinstalled HTC sync, same problem. I updated Java JVM, no change. I then re-downloaded the SDK to a different directory, no dice.
I usually open a command prompt "as Administrator" and run ADB from the directory. Even with a device disconnected, I get the same error. I test this way because if I issued "ADB devices" and it returns nothing, I know it's working. It appears that ADB doesn't even start to the point to poll for devices.
I have, just for laughs, connected my device (USB debugging/charge only), but no joy.
I won't have much time to poke around more until the weekend. If I don't come up with anything, I will take you up on the gtalk. Thanks again.
Windows Vista just makes it all that much harder to fix things...
lovethyEVO said:
If you have installed htc sync before uninstall it and the htc driver installer.
. . .
Reinstall htc sync. When that finishes I suggest a reboot. When you've rebooted uninstall htc sync but leave the htc driver installer. Reboot again.
. . .
This should hopefully reinstall the usb drivers correctly. On vista it installs as adb device or something along those lines.
Click to expand...
Click to collapse
In my case, I tried all these things and many more (lived with this problem since first getting my EVO on release date in June). No dice, as Windows Vista, once it installs a device driver, doesn't give the user the option to uninstall it (by Microsoft's expressly-stated intent -- a design decision I vehemently disagree with). At least the user could repair such problems in prior versions of Windows by simply uninstalling a device, choosing "yes" to the "remove driver files from the disk" question, and (after the obligatory and ubiquitous Windows reboot) re-connect the USB device. That would start fresh with that device's driver.
I never invested the time to learn how the USB subsystem registers devices and their drivers (in Windows Vista) in order to determine how to manually remove a driver from the Windows Registry adequately that it would treat the device as "new hardware detected" upon the next connection.
Once Windows Vista has scrambled some internals in the database/registry controlling the USB subsystem's driver knowledge, you're toast. Nothing I could find in Microsoft's Knowledge Base nor MSDN shed any light on how to tackle the removal-and-recreation-from-scratch of the USB system configuration.
Microsoft's stock answer was invariably "re-install Windows". Yeah, thanks for that. Windows, even more than 26 years later, is still not a real operating system, and still has bugs dating back to Windows 3.1.
Sigh.
Check Windows Firewall service.
In my case I just turned off the Windows Firewall and it started working.
regards
Gaurav
i had this problem.
disable any program like Proxifier and firewall
I accidently figured it out
so i was trying to find my cid number because i was flashing ICS firmware and stuff, and the adb deal in the prompt kept giving me the exact same error, and thus would'nt work. after trying everything (such as: installing drivers, killing the process, restarting my comp, reinstalling adb, etc.) for about an hour and a half, i just stumbled upon a page that was linked to in the ICS flash guide, that had a different adb folder download. this download has an entirely different effect on the command prompt and worked so i could get my cid number and rewrite superCid. here it is:
http://forum.xda-developers.com/attachment.php?attachmentid=872134&d=1327512033
Download it, click "start here", then treat it like normal
ADB server din't ACK
Please help....I was trying installing Hellkat 4.4.2 on my kindle fire by following http://forum.xda-developers.com/showthread.php?t=2570078
Downloaded all the files and flashed through TWRP and was successful. But after flashing, when it is rebooting it is getting stuck on the hellkat logo and not booting.
If I try to install TWRP again, i am getting error ADB server din't ACK *failed to start daemon*. and ADB status online and boot status unknown.
Please help......
orangeipod1gb said:
ADB server din't ACK
Please help....I was trying installing Hellkat 4.4.2 on my kindle fire by following http://forum.xda-developers.com/showthread.php?t=2570078
Downloaded all the files and flashed through TWRP and was successful. But after flashing, when it is rebooting it is getting stuck on the hellkat logo and not booting.
If I try to install TWRP again, i am getting error ADB server din't ACK *failed to start daemon*. and ADB status online and boot status unknown.
Please help......
Click to expand...
Click to collapse
your solution is
netsh advfirewall set currentprofile firewallpolicy allowinbound,allowoutbound
I have an HTC Incredible 4G LTE. I underwent the process detailed here to unlock the bootloader.
When i got the HTCDev website, i ran a fastboot command and it just says <waiting for device>. I tried to detect the device with adb devices, and fastboot devices, but with no success. the THC Sync manager is not installed. HTC drivers should be installed. I am plugged into a USB 2.0 port, the same one used through out the process (i even tried the other one).
I am at a loss as to what is happening. I do know that the device manager sees my phone, and shows the drivers as the latest version. It does give this message:
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
The device manager is listing the driver as version 2.0.7.3.
EDIT: Was able to get driver updated to 2.0.7.18
Also, when connected to the computer normally an orange light shows near the speaker. I wasn't concerned at first as I know the Android OS is not actually up and running on the phone, but do wonder if it doesn't indicated a problem.
Another note, I am running Windows 8.
EDIT 2: More research has yielded the following "Android Bootloader Interface". Every reference installing this from the usb_driver in the ../extra/google/usb_driver folder. When I attempt to do so from the device manager Have Disk ui I receive the following error
The folder you specified doesn't contain a compatible software driver for your
device. If the folder contains a driver, make sure it is designer to work with
Windows for x64-based systems.
Click to expand...
Click to collapse
EDIT 3: Removed entire android sdk, redownloaded and installed. Removed all HTC software and drivers. Booted phone into fastboot, and windows detected an "Android 1.0" device, installed the Android Bootloader Interface driver from the google usb_driver successfully. However, fastboot devices still does not detect the phone, and device manager still shows code 10.
As of now:
No HTC Sync, or HTC Driver
phone booted into fastboot, phone displays "FASTBOOT USB"
phone is set to usb debug
phone is connected to pc with good cable to a usb 2.0 port
I have:
rebooted pc, re-installed drivers, changed usb cords, changed usb ports, even tried a usb 3.0 port, i have tried some generic fixes for code 10 errors, and completely run out of ideas
EDIT 4: After using a different computer running Windows 7 I was able to complete the process, however, i would very much like toresolve the issue with my own PC, as the Win7 laptop is not mine. I utilized the adb/fastboot/winapi files from my Win8 machine. Win7 automatically found HTC drivers (2.0.7.18) and everything seemed to work just fine. Any ideas?
hello guys, just bought that amazing watch today i have an issue. How can i connect it to my pc ? I plug in the usb, while sm3 is off. Win7 start to install and at the end it fails because of the drivers. So my pc doesn't recognise it. I can only see the "empty" E:/ Disk. Any suggestion ?
edit: unistalled the "watch" and then plugged in again and drivers get istalled. Now i have a "sony file-cd usb gadget" . help me pls
edit: wrong section :/ sorry
I have exactly the same problem.
i installed the Google USB Driver from theAndroid SDK Manager and also installed the Sony PC Companion. But the Smartwatch 3 still shows in the device manager under "other devices" without installed driver.
The only way i could connect to it is using ADB over Bluetooth which is really slow.
Anyone any idea?
i used these adb drivers http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi
after installation, i went to device manager, update drivers, search pc for drivers, choose from a list of...., and then i selscted adb testing interface version 3.12.0.0
i had to skip the warnin popup, but adb is working fine
Thank you a lot.
i could not find any "adb testing interface" so i installed "Google Nexus 7 ADB Interface" from the list and so far it seems to work with that too.
Not sure why you have such a testing interface driver.
Did this HERE and no driver problem for me.
Drivers can be found in this folder : Program Files (x86)/Sony/Sony PC Companion/Drivers/
The Driver used in the bootloader is a different one. I have no issue there.
But it seems there is no actual ADB Driver used when the device is in normal operation mode for debugging apps or pushing apps directly over ADB on to the device.
I am new to android, HTC One VX being my first phone ((Got it like Last year as a gift iirc)).
Using Stock rom and my os is 8.1 pro x64
I am trying to unlock the bootloader.. I went to HTCdev, followed the directions for unlocking the bootlader.
1. Got the Android SDK and installed
2. Got the HTC SYnc Manager for the drivers.
3. Got Fastboot and moved it to where the ADB .dll file is.
I get my phone into bootloader after making sure USB Debugging is enabled, then I plug it into my computer. After a few moments, Windows pops up with USB Device is not recognized. I check Device Manager, it shows "My HTC" under unknown devices. I manually point the thing to where the W8 x64 driver is , and it says the driver is up to date. Bring up the Property info of the device, this is what is showing int he text box,
Code:
A request for USB BOS descriptor failed
Just to make sure, I navigate back to the ADB folder, bring up CMD there and type in
Code:
adb devices
. No device was listed despite my phone being connected to my computer. Tried it with 3 different cords, front and back of my computer. ((USB 3.0 ports.))
I put it in one of my USB 2.0 ports and the issue persists, the device status shows
Code:
A device which does not exist was specified
.
Is there anyway to fix this, its quiet annoying, Apparently doing clean reinstalls of everything isn't going to fix it for me.
I have a Oneplus 3, and after I updated my laptop's Windows 10 to the new Anniversary Update (I'm not sure what's the reason, so I mentioned this, just in case), it fails to recognize the MTP option when I connect the phone to my laptop. Although, it is able to recognize the phone in P2P (Photo Transfer) mode and wholly recognizable on my Ubuntu on the same laptop and other Windows laptops/PCs apart from mine.
I tried updating the driver software from the Device Manager but it shows the following error:
Code:
Windows found driver software for your device but encountered an error while attempting
to install it.
[MTP Device Symbol]
A service installation section in this INF is invalid.
Thank You
When clicking on the "Driver update" find Android device, and MTP. There should be 2 options. Select an option, and if it isn't working, select the other. Hope i helped