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

Question

I tried ./adb devices from ~/Android/Sdk/platform-tools directory and I got * daemon not running. starting it now on port 5037 * ADB server didn't ACK * failed to start daemon *

I expected something like this:

List of devices attached
HT9CPP809576 device

If I try ./adb kill-server and after that ./adb start-server I get

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

If I try ./adb nodaemon server I get Illegal instruction (core dumped).

I have 32bit lubuntu 15.04. I use Android studio. My Android phone(LG l50) is plugged into the computer.

How can I solve this issue ?

just save folder and try to ./adb kill-server - ./adb start-server — Tronum, Jul 09 '15 at 14:26
@Tronum I restarted the computer and try with ./adb kill-server - ./adb start-server and I got the same error. — Seba, Jul 09 '15 at 14:42
OK. Check this posts:http://stackoverflow.com/questions/23415746/how-to-resolve-the-adb-server-didnt-ack-error — Tronum, Jul 09 '15 at 14:44
this solved the problem for me: sudo apt-get install android-tools-adb — Seba, Jul 13 '15 at 06:47
That's can be. You reinstall adb so cache was cleared. It's probably solve your issue. Anyway issue was solved? Close it. — Tronum, Jul 13 '15 at 08:07
@Tronum how do you know it was installed in the first place ? — Seba, Jul 14 '15 at 10:02
you can try to use command "locate tools/hierarchyviewer" and check places with your sdk dirs. if it only one - all fine. — Tronum, Jul 14 '15 at 10:53

NickMan · Answer 1 · 2016-06-09T16:47:05.297

1

Run tasklist | findstr /i adb to see if the adb is running. If it is still running, you can kill it with taskkill /f /im adb.exe. Then restart the adb by adb start-server

edited Jun 09 '16 at 16:47

answered Jun 08 '16 at 15:05

NickMan

19
4

This should be the accepted answer, it saved me from become mad ! – Rémi P Jun 29 '16 at 08:30

score -1 · Answer 2 · answered Sep 08 '15 at 18:06

-1

this error could be due to port 5037 is getting used by other process. Try to set the adb server port to other, windows set ANDROID_ADB_SERVER_PORT = XXXX

answered Sep 08 '15 at 18:06

user2832573

1

1

Could you please add more details to the solution you provide? – abarisone Sep 08 '15 at 18:12

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

2 Answers2