Daemon not running. Starting it now on port 5037

Question

[2014-04-16 14:01:05 - Abc] ------------------------------
[2014-04-16 14:01:05 - Abc] Android Launch!
[2014-04-16 14:01:05 - Abc] The connection to `ADB` is down, and a severe error has occurred.
[2014-04-16 14:01:05 - Abc] You must restart `ADB` and Eclipse.
[2014-04-16 14:01:05 - Abc] Please ensure that adb is correctly located at 'D:\adt-bundle-windows-x86-20131030\sdk\platform-tools\adb.exe' and can be executed.

The above error has occurred while I was trying to run a program. As a solution,

I did the following steps by opening the command prompt :

Close the Eclipse if running
Go to the Android SDK platform-tools directory in Command Prompt
type adb kill-server
then type adb start-server
No error message is thrown while starting ADB server, then adb is started successfully.
Now you can start Eclipse again.

but it is not working and in the command prompt it shows :

daemon not running .starting it now on port 5037 ADB server didn't ACK FAILED TO START DAEMON

That almost sounds like security software or something could be blocking the two "halves" of ADB from talking to each other. — Chris Stratton, Apr 16 '14 at 20:07
possible duplicate of [Adb won't start](http://stackoverflow.com/questions/2306322/adb-wont-start) — janot, Sep 19 '15 at 20:33
Solved the issue with this https://stackoverflow.com/a/70915818/5935112 — Just Shadow, Jan 23 '23 at 14:27

score 28 · Answer 1 · edited Feb 24 '15 at 20:24

28

Reference link: http://www.programering.com/a/MTNyUDMwATA.html

Steps I followed 1) Execute the command adb nodaemon server in command prompt Output at command prompt will be: The following error occurred cannot bind 'tcp:5037' The original ADB server port binding failed

2) Enter the following command query which using port 5037 netstat -ano | findstr "5037" The following information will be prompted on command prompt: TCP 127.0.0.1:5037 0.0.0.0:0 LISTENING 9288

3) View the task manager, close all adb.exe

4) Restart eclipse or other IDE

The above steps worked for me.

edited Feb 24 '15 at 20:24

Ivo Renkema

2,188
1
29
40

answered Oct 07 '14 at 07:46

Santosh Waddi

419
4
4

2

i don't know why this answer is not accepted... working awesome – Iftikhar Ali Ansari Mar 28 '15 at 10:51
1

How do I fix this for a mac? – AdamHurwitz Dec 15 '17 at 19:53
1

@AdamHurwitz -- oh that's easy. Trade the MAC for a PC. Done! -- sorry couldn't resist. – ejbytes Mar 12 '18 at 09:38
Worked for me. That's pure FM. – ejbytes Mar 12 '18 at 09:39

score 7 · Answer 2 · answered Apr 04 '16 at 11:22

7

This worked for me: Open task manager (of your OS) and kill adb.exe process. Now start adb again, now adb should start normally.

answered Apr 04 '16 at 11:22

M. Usman Khan

3,689
1
59
69

Daemon not running. Starting it now on port 5037

2 Answers2

Linked