52

I could not run the android application never on my laptop. Eclipse gives same error constantly, that is "ADB server didn't Acknowledge"

I've tried everything, restart adb from ddms view, from command line (kill-server, start-server), from task manager and restart eclipse. When I manage to start adb server and re-open eclipse, as soon as I run the android application, same error comes to console; ADB server didn't ack.

Could you give an idea except restarting adb

Maveňツ
  • 9,147
  • 14
  • 53
  • 94
ydmpcn
  • 587
  • 1
  • 4
  • 10
  • you are trying to run the app on a phone or emulator? – andrei Oct 21 '14 at 08:39
  • 1
    if you are using Genymotion here is one solution http://stackoverflow.com/questions/5703550/my-eclipse-adb-server-didnt-ack-failed-to-start-daemon – LOG_TAG Nov 14 '14 at 07:50

9 Answers9

115

Killing the process adb.exe in the TASK MANAGER (to open task manager CTRL+Shift+Esc) solves it in my case. After killing it run adb start-server or adb devices and you should be fine.

enter image description here

Incase if that doesn't work

We can solve this issue so easily.

  1. Open command prompt, cd <platform-tools directory>
  2. Run command adb kill-server
  3. Open Windows Task manager and check whether adb is still running. If it is, just kill adb.exe
  4. Run command adb start-server in command prompt

enter image description here

A way bit difficult approach

Command Prompt (cmd.exe) 

netstat -aon|findstr 5037

find process id of 0.0.0.0 enter image description here

make sure it's adb.exe

tasklist|findstr 1980

enter image description here

kill this process

taskkill /f /t /im adb.exe

enter image description here

get ADB back to normal

enter image description here

for more details check it from here

Maveňツ
  • 9,147
  • 14
  • 53
  • 94
  • No, I started adb server. But in eclipse it returned its old statu again. I am confused – ydmpcn Oct 06 '14 at 13:20
  • 1
    @RyPope check my updated answer. If you have better option then please suggest – Maveňツ Oct 06 '14 at 13:38
  • I've tried but didn't work. after last command; "adb devices", I this error; adb server din't ack, deamon not running – ydmpcn Oct 06 '14 at 13:41
  • @ydmpcn 1 :open eclise open the SDK Manager ,choice i device to open or you can open the sdk dir open the SDK Manager then choice i device to open 2: close the eclipse,then open it – Maveňツ Oct 06 '14 at 13:43
  • didn't work...it is going to a loop constanty: [2014-10-06 20:31:18 - DeviceMonitor] Connection attempts: 9 ............ – ydmpcn Oct 06 '14 at 17:32
  • 1
    I tried everything for one week and nothing worked. Is there any way to develop android applications except installing adt to PCs...Any online compiler, emulator or virtual machines – ydmpcn Oct 11 '14 at 16:05
  • When I ran the netstat command, the list was so long that I couldn't scroll to the top. http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/unable-to-scroll-to-the-top-of-the-command-prompt/6f09d0d3-4d8b-490c-87a0-171e68ca8c07 This guide fixed that. However, I get several errors when I try to kill the process saying "the operation attempted is not supported" so I don't know what the hell to do now – matthew_360 Feb 26 '15 at 18:55
  • 2
    Running `adb devices` after killing adb.exe resulted in the following error: `ADB server did't ACK`. **However**, running `adb start-server` instead did the trick. – Francisco Hodge Apr 02 '15 at 17:19
  • cmd is not responding after the last cmd (adb devices). – Zin Win Htet Oct 19 '15 at 11:05
8

For Mac users, what worked for me was:

  1. Open Activity Monitor (equivalent to Windows task manager)
  2. Kill the adb task
  3. Restart adb
Reefwing
  • 2,162
  • 1
  • 20
  • 22
4

Please kill adb by command:

taskkill /f /im "adb.exe"

then, re-start it with command:

adb start-server

It work very fine for me :)

Dong Thang
  • 373
  • 5
  • 5
2

Look for typos in the ~/.android/adb_usb.ini file. This problem can be caused if that file gets messed up.

Jo Jo
  • 6,970
  • 5
  • 33
  • 47
1

In my pc, i use the command line taskkill /f /t /im wandoujia_daemon.exe (because adb.exe or bas_daemon.exe is not running in my task manager) And... the adb server is started succesfully

nam
  • 11
  • 1
0

In addition to @maveňツ solution.

Actually we have to kill the process using this address 0.0.0.0:0, that's why for most of the people killing adb.exe from task manager was working (In my case I was not able to see it even Task Manager).

Following the @maveňツ steps I find out that some other process was using this address. I went ahead to kill it, it gave me ACCESS DENIED as Error.

So using the tasklist|findstr **** i find out the name of the process and killed it from task manager.

There after it started working.

In my case bas_daemon and bas_helper were using this address both of which corresponds to MOBOROBO

DeltaCap019
  • 6,436
  • 2
  • 46
  • 69
0

in my case i use the command line taskkill /f /t /im bas_deamon.exe (because adb.exe was not started) and adb server is started successfully

beginner1417
  • 67
  • 1
  • 7
0

Kill ADB from command prompt. Kill eclipse also from command prompt. Start adb server from there using [adb start-server] And start again.

Manoj Saini
  • 11
-1

I believed you've checked the port number, and restart adb. But have you install proper android driver on your computer. Some universal android driver may not work on your computer, you'd better installed the driver provided by your mobile manufacturer, if you can't find the driver on manufacturer's website, consider download its software suit, it may include the driver.

Sean
  • 1