ADB server didn't Acknowledge

AndroidEclipseAdb

Android Problem Overview


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

Android Solutions


Solution 1 - Android

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

Solution 2 - Android

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

Solution 3 - Android

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 :)

Solution 4 - Android

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

Solution 5 - Android

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

Solution 6 - Android

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

Solution 7 - Android

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

Solution 8 - Android

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

Solution 9 - Android

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.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionydmpcnView Question on Stackoverflow
Solution 1 - AndroidMaveňツView Answer on Stackoverflow
Solution 2 - AndroidReefwingView Answer on Stackoverflow
Solution 3 - AndroidDong ThangView Answer on Stackoverflow
Solution 4 - AndroidJo JoView Answer on Stackoverflow
Solution 5 - AndroidnamView Answer on Stackoverflow
Solution 6 - AndroidDeltaCap019View Answer on Stackoverflow
Solution 7 - Androidbeginner1417View Answer on Stackoverflow
Solution 8 - AndroidManoj SainiView Answer on Stackoverflow
Solution 9 - AndroidSeanView Answer on Stackoverflow