Android ADB didn't ack issue in eclipse

Question

I have spent around 5 hrs on this problem. I have read the same question on stackoverflow, but none of the solutions solved my problem... First, it gives me:

[2013-02-28 14:48:21 - adb] ADB server didn't ACK
[2013-02-28 14:48:21 - adb] * failed to start daemon *

To solve that, I kill the adb.exe in task manager, restart eclipse. Then go to DDMS, reset adb. NO LUCK...

Then, I go to command line window, type adb kill-server and adb start-server, it gives me:

adb server is out of date. killing...
ADB server didn't ACK
fail to start deamon

Now I don't know what to do. I have a project to develop on eclipse, so really need to solve this problem soon. Someone please help!!

(As many solution indicated, I killed my adb.exe thousands of times, but it showed up immediately in task manager after 2 seconds. )

Answer 1

I had the same problem, here is what actually helped me:

1. Go to platform-tools in Android SDK directory.

2. Type:

   adb nodaemon server

   Output:

   cannot bind 'tcp:5037'

3. Now I know the reason adb not responsive is because it can not bind to port 5037. Use following command to find out the process that occupies the port:

   netstat -ano | findstr 5037

   Output:

   

4. Note that process with PID 4888 is occupying port 5037.

5. Open Task Manager, click on Details tab, find the process and kill it, tfadb.exe in this case. it may vary for me it is sh.exe and port 4599 and delete all adb.exe

   

6. Retry adb kill-server and adb start-server, hopefully adb is up running fine.