Adb won't start

Question

Running Vista, tried starting adb from shell as admin get daemon not running starting it now

ADB server didn't ACK
* failed to start daemon *

Any help for this?

Answer 1

I had the same problem. I had improperly edited my adb_usb.ini file (I had two carriage returns at the end of the file...yes this was hard to find.)

This file is located somewhere similar to /Users/{user-name}/.android/adb_usb.ini

(replace {user-name} with your own user name)

Make sure the file reads EXTACTLY (No spaces/carriage returns/line breaks before or after):

'# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT."
'# USE 'android update adb' TO GENERATE."
'# 1 USB VENDOR ID PER LINE."

(IMPORTANT!!! There are no ' (apostrophes) in the actual file, this was the only way for me to post this without it interpreting the # for BOLD).

---

Hope that helps someone

Answer 2

If you're using Android Studio, if

• you have the "Device chooser" dialog open
• you try to run "adb devices" from your command line

it leads every single time to the following error

adb server is out of date.  killing...
cannot bind 'tcp:5037'
ADB server didn't ACK
* failed to start daemon *
error:

SOLUTION (easy and quick)

Close the "Device chooser" dialog. My guess is that it tries to take over the adb connection in a.. very intensive way.

Answer 3

1.$ apt-get remove android-tools-adb

2.$ cd $PATH_TO_SDK/platform-tools/

3.$ ./adb devices

You will see like this:

• daemon not running. starting it now on port 5037 * cannot bind 'tcp:5037' ADB server didn't ACK * failed to start daemon *

That show what errors.

Now you reset you PC, it will well.

Or

# lsof -i:5037

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME

wineserve 3609 root 268u IPv4 20118 0t0 TCP localhost:5037 (LISTEN)

# 

You will know which software use the port.

Answer 4

To avoid this simply change the following values in your host_config.xml:

<!-- Number of tests executed between reboots. A value <= 0 disables reboots. -->
<IntValue name="maxTestCount" value="10000" />
<!-- Max size [tests] for a package to be run in batch mode. -->
<IntValue name="maxTestsInBatchMode" value="100000" />

<!-- Max time [ms] between test status updates. -->
<IntValue name="testStatusTimeoutMs" value="600000" />

Answer 5

When it additionally says that adb server is out of date. killing... it kills it for you. The problem is it restarts as soon as was killed.

So you should consider finding the adb.exe wherever it could be. The simplest way to do that is opening a Task Manager, finding an adb.exe process -> RMB -> Open file location -> delete it from there. Unless it's not needed, in this case you should update it. In my case it was in C:\Windows\ and came with their Visual Studio.

Answer 6

The adb server is not running. you can open the command line window in Windows to check which process is using the 5037 port, remember the process number.

netstat -ano |findstr "5037"

Then use the Ctrl+alt+delete to open the process manager to kill the process which is possessing the 5037 port. You maybe need to try this several times until the 5037 port is free to use.