This question already has answers here:
Adb won't start
(21 answers)
Closed 6 years ago.
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
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.
Incase if that doesn't work
We can solve this issue so easily.
Open command prompt, cd <platform-tools directory>
Run command adb kill-server
Open Windows Task manager and check whether adb is still running. If it is, just kill adb.exe
Run command adb start-server in command prompt
A way bit difficult approach
Command Prompt (cmd.exe)
netstat -aon|findstr 5037
find process id of 0.0.0.0
make sure it's adb.exe
tasklist|findstr 1980
kill this process
taskkill /f /t /im adb.exe
get ADB back to normal
for more details check it from here
For Mac users, what worked for me was:
Open Activity Monitor (equivalent to Windows task manager)
Kill the adb task
Restart adb
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 :)
Look for typos in the ~/.android/adb_usb.ini file. This problem can be caused if that file gets messed up.
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
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
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
Kill ADB from command prompt.
Kill eclipse also from command prompt.
Start adb server from there using [adb start-server]
And start again.
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.
I am trying to follow this link ddms: 'adb.exe,start-server' failed -- run manually if necessary, Android Studio and it works for me.
you can also try this process
adb kill-server
then
adb start-server
then
adb nodaemon server
output cannot bind 'tcp:5037'
then #Parth Anjaria comment from how to restart ADB manually from Android Studio this link.
This problem's solution varies.
when i run adb devices
adb server is out of date. killing...
cannot bind 'tcp:5037'
ADB server didn't ACK
* failed to start daemon *
error:
its the same as this error here
. some of the comments say that try to adb kill-server then start adb again but it does not work in my ubuntu machine.
I have also tried killall -9 adb which is the correct answer of this question. It is also stated in the correct answer is the best solution is to change genymotion settings and point to sdk but in my case i already did it.
can someone help me get rid of this error.
any way in case if someone will see this post i want to point how really simple the solution by closing all the genymotion devices then running the command
killall adb. By killing all the adb does kill it all then i did start-server maybe i have another adb running some times before and i forgot about it.
This is my first post here, so first of all, hello everybody!
I am not sure if it is bug or a feature:) but I have noticed that when you will run adb install with no device connected, it firstly starts adb daemon (if was not currently running), and then wait for the device. After that, when you open new window and run adb kill-server, adb install command will not stop, but shows protocol fault and then restart adb daemon again.
There is no other way of stopping this, than killing the process (for example using ctrl+c).
Screenshot
I have also noticed that other commands like adb shell, adb devices, adb wait-for-device doesn't act like adb install - stop when adb kill-server will be lunched.
My version of ADB is 1.0.31
I have tested this issue on Linux and Windows, and both works the same.
Please let me know, what do you think about it.
Best Regards,
Pawel
I am getting this exception when i trying to run my application
[2013-09-10 12:09:21 - EffectiveNavigation] The connection to adb is down, and a severe error has occured.
[2013-09-10 12:09:21 - EffectiveNavigation] You must restart adb and Eclipse.
[2013-09-10 12:09:21 - EffectiveNavigation] Please ensure that adb is correctly located at 'E:\Configured-Eclipse\adt-bundle-windows-x86-20130522\sdk\platform-tools\adb.exe' and can be executed.
When i tried to reset adb from eclipse it is showing this error
[2013-09-10 12:18:20 - adb] Attempting to restart adb, but version check failed!
I have tried this also from the command prompt.
1.adb kill-server //kill all active server
2.adb start-server //start adb server
Restarted the eclipse also but still the same error .Help me to resolve the issue.
Finally this was the issue
turned off COMODO Defense+ module and all worked....
If you install some application manage your phone, kill the application.
First of all, make sure you can run adb.exe itself without any errors. run it in "Administrator Mode" in cmd.exe and also, "adb.exe devices" should output list of connected and recognized USB devices.
Check update for eclipse adt first.
============== For most adb-down situations this may work. ========
Exit eclipse and kill the process adb.exe from Task Manager.
run adb kill-server and adb start-server. then retry.
If an error occurred when 'adb start-server'
Use netstat -abn to finger out if there is a process which is listening on port 5037 (default adb port), and kill it. Then run 'adb start-server' or just 'adb devices'