After updating the SDK, Eclipse shows this error:
ADB server didn't ACK, failed to start daemon.
When I run an Android application, it gives me the following:
Please ensure that adb is correctly located at 'D:\android-sdk-windows\platform-tools\adb.exe' and can be executed.
How can I fix this problem?
Thanks, #jowett, I have solved my same problem, doing these steps
Step 1:
CTRL+Shift+Esc to open the task manager, which has adb.exe process and end (kill) that process
Step 2:
Now, close the eclipse, which is currently running on my computer.
Step 3:
Again, restart eclipse then solved that problem.
For those using OS X
killall adb
For those using Windows
adb kill-server
should do the trick.
I met same problem, though I didn't what caused this. Whatever, i find some clues and fixed finally.
When I open SDK and AVD manager, but find the AVD version(2.3.3) is not same with android lib version(2.3). So I create a new AVD with 2.3.
I fixed it by the following steps:
1. Open windows task manager and kill adb.exe process.
2. Close eclipse and restart it. Then it works.
Hope it helps.
Command prompt (cmd.exe):
netstat -aon | findstr 5037
Find the 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:
Credit: blog post *Android ADB server didn't ACK failed to start daemon*
These symptoms occur if you are using the Genymotion emulator (on Windows or Linux) at the same time as Android Studio:
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
Genymotion includes its own copy of adb, which interferes with the one bundled in the Android SDK.
The easiest way to fix seems to be to update your Genymotion Settings so it uses the same ADB as your Android SDK:
Just check the "Use custom Android SDK tools" option and enter your desired location.
ADB will often fail if there is a newline in adb_usb.ini. Remove it, restart it, and that will often solve the problem (at least for me anyway).
If you are using a sync application for the device, it could also be because there are other apps using the same 5037 port. Shut down all services running on port 5037 and try starting ADB.
To check if any application is using port 5037, use this:
netstat -a -n -o |findstr "5037"
Get the PID of the application.
Use Process Explorer to find the Process and exit it.
Now use adb start-server or adb get-state to start/check the ADB server status.
I faced the issue when I used the Snappea / Wandoujia Sync application.
I caused this problem by entering an extra blank line at the end of ~/.android/adb_usb.ini
(Removing the extra blank line fixed the problem)
We can solve this issue so easily.
Open a command prompt, and do 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 the command prompt
I have solved my first question: Open Eclipse, open the SDK Manager, and choose the device to open.
Or you can open the SDK directory. Open the SDK Manager, and then choose the device to open
2: Close Eclipse, and then open it.
Make sure USB debugging on your phone is turned on. ADB kill-server and ADB start-server is not the problem.
C:\Documents and Settings\Administrator> adb nodaemon server
- cannot bind 'tcp:5037'
C:\Documents and Settings\Administrator> netstat -aon | findstr "5037"
- TCP 127.0.0.1:1130 127.0.0.1:5037 TIME_WAIT 0
- TCP 127.0.0.1:1269 127.0.0.1:5037 TIME_WAIT 0
- TCP 127.0.0.1:5037 0.0.0.0:0 LISTENING 3088
- TCP 127.0.0.1:5037 127.0.0.1:1128 TIME_WAIT 0
- TCP 127.0.0.1:5037 127.0.0.1:1129 TIME_WAIT 0
- TCP 127.0.0.1:5037 127.0.0.1:1270 TIME_WAIT 0
C:\Documents and Settings\Administrator>tasklist -fi "pid eq 3088"
- Image name PID session name session # memory usage
========================= ====== ================ ======== ============
- adb.exe 3088 Console 0 3,816 K
C:\Documents and Settings\Administrator>taskkill /f /pid 3088
- Success: terminate the PID for the process of 3,088.
C:\Documents and Settings\Administrator>adb start-server
- daemon not running. starting it now on port 5037 *
- daemon started successfully *
I've already up-voted another answer here to this question, but just in case anyone was wondering, you don't need to restart Eclipse to get ADB running again. Just open a shell and run the command:
adb start-server
If you haven't set the path to ADB in your system properties then you must first go to the directory in which ADB exists(in Android\android-sdk\platform-tools....I'm running Windows, I don't know how the mac people do things).
Run over to sysinternals.com and pick up TCPVIEW and PROCESS EXPLORER, if you don't have them installed already.
For some reason, the ADB daemon is terminating before the close socket exchange is complete. If you run (from the command prompt) "NETSTAT -o", you will see the socket (generally 5037) in CLOSE_WAIT state and the owning process number. Process Explorer won't show that process ID (the daemon terminated), and the process called adb.exe (which opened the socket) will be gone. (If adb.exe if found, try killing the task and see if things get cleaned up.)
Using TCPVIEW, locate the hung socket. The process name column will show the associated process can not be found. Right click, and select "Close Connection". The socket is now closed, and the adb daemon should be able to start.
I had a similar issue. Killing an existing instance of the ADB process from Task Manager did not work for me.
Just few days back, I had tried to install MIPS SDK and ADT-17 earlier and Eclipse gave me the error, and I did not fix that issue.
So, now, when I got this ADB server didn't ACK, failed to start daemon... issue, I executed 'Check for Updates' in the Eclipse Help menu item.
There were no updates available, but at least 'ADB server did not ACK' error disappeared.
I hope this might help in a few cases.
Type ./adb nodaemon server in a terminal.
If it returns Invalid content in adb_usb.ini, then there is a problem with your adb_usb.ini file in the .android folder.
Open adb_usb.ini and erase its contents. Then restart the server...it worked for me.
Check for the path of the Android directory. It should not contain spaces, etc.
Also check if the plugin has been properly configured in Eclipse → Preferences.
In my case I had everything checked multiple times, but it was still not working. I was about to reinstall everything, but I came upon an answer on this site (some other post).
Do check your antivirus. It may be blocking the ports of adb.exe or emulator programs, etc. That solved the problem in my case.
In addition to #Bastet's solution:
Actually we have to kill the process using the 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 in Task Manager).
Following the #Bastet steps, I found out that some other process was using this address. I went ahead to kill it, and it gave me ACCESS DENIED as Error.
So using the tasklist | findstr **** I found out the name of the process and killed it from Task Manager.
Thereafter it started working.
In my case bas_daemon and bas_helper were using this address both of which corresponds to MOBOROBO.
I had the same problem. But there was no process of adb on my laptop. I just log out and log in to my account, and it's resolved...
ADB could start from CMD windows after that.
The best and the most efficient way without restarting any device or software is:
Run the following:
adt-bundle-windows-x86_64\sdk\platform-tools\adb.exe
And one more thing.. ADB is a self-dependent thing. You cannot do anything until unless it wants itself to work. There is one more way which I found out: Leave the device connected for 5-6 minutes and wait. Soon the device gets connected and tries to launch.
This didn't start happening for me until I rooted my Samsung Galaxy S III phone (following the xda-developer forum guide).
It happens pretty randomly, but it's definitely occurring while running Eclipse.
Killing the adb.exe process and restarting it solves the problem.
Look at the antivirus or firewall... Does any of that block you from access... In k7 antivirus I turned off system monitor, and it does works for me...
Linux/Ubuntu users this might also be the case.... i had an android emulator running and I had to kill that. To do that do the following
lsof -i :5307
(use sudo if needed)
Note the pid in the result of above command. Then
kill -9 <pid_from_above>
then go ahead with
adb shell
I had to allow adb.exe to access my network in my firewall.
Killing Eclipse and then rebooting did not help me. I added the Android tool to the PATH variables, started Task Manager and killed adb.exe.
I restarted Eclipse, and then it worked.
Related
I have installed adt bundle eclipse. However, I can't seems to run the AVD. I have the problem of
ADB server didn't ACK
failed to start daemon
I have search on how to solve it, I've read to type adb kill-server and adb start-server. when I typed that, it says
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *"
Please follow below steps:-
Go to run
open command prompt
get into your platform-tools under android sdk.
now type command: adb kill-server
then upon success type: adb start-server
Thats'it.
Let me know if you still facing any issue..
I had this exact problem on my Vista x64 system. I solved it by doing the following:
Ctrl-Alt-Del, start Task Manager, under Processes tab, check for "shuame_helper.exe". It was there from running RootGenius. I clicked End Process, then went back to the command prompt and entered adb start-server and it worked!
Try below step from DDMS in eclipse :
So I had the same problem and failed in all the same ways as above:
adb kill-server
followed by
adb start-server
still resulted in the ADB server didn't ACK error.
The other common suggestion of using the task manager to kill the process also
failed as it seemed that something restarted adb automatically? It would disappear for a second, then there were two adb processes ,then there was one again.
Exasperated.
I restarted Windows in safe mode.
This ensured that adb wasn't started.
Shut down and restart normally. Problem solved.
Just for good measure, I also updated eclipse and android at this point, but I think that the safe mode restart fixed it.
Give it a try when all else fails.
When this happens I open Activity Monitor (on mac) or Task Manager (on windows) and look for the ADB process and force close it (sometimes there are more than one, close those to) and then press the Run button again in Android Studio or Eclipse.
1)Open task manager first
2)close any instance of adb.exe(end task it)
3)open command prompt
4) type adb start-server(you may have to execute it twice)
5) try to run now.
I had this problem using the latest ADT, SDK and Eclipse on Windows 7. I had an old ASUS TF101 and an HTC HD connected with their respective docking software. When I looked in processor tab of the Windows task manager I could see two instances of the adb.exe, one loaded and another one looking like it is trying to load.
I killed the PC connecting software (process in task manager) for the ASUS, the HTC Sync wasn't running. There is now one adb.exe running and both devices are recognised in Eclipse and in the command prompt (adb devices). You may need to restart Eclipse.
This question already has answers here:
Eclipse error "ADB server didn't ACK, failed to start daemon"
(23 answers)
Adb won't start
(21 answers)
Closed 6 years ago.
I am trying to install my project on 5 AVD's at the same time, but I constantly get this error, I am executing it on Windows 8.1
"* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon"
I have tried reading all possible posts on stackoverflow concerning this error, and all of them just mention that try to kill the adb process and restart eclipse and then all will be fine. I have tried the method mentioned in the posts and along with that I have also turned off my security and firewall, so that there is no obstruction on the port 5037. Somebody please help me as I need to execute my project and I am not able to do so :(. For your reference I can provide the output of the following command "netstat -ano | findstr "5037""
TCP 127.0.0.1:5037 0.0.0.0:0 LISTENING 7144
TCP 127.0.0.1:5037 127.0.0.1:57410 ESTABLISHED 7144
TCP 127.0.0.1:5037 127.0.0.1:57411 ESTABLISHED 7144
TCP 127.0.0.1:5037 127.0.0.1:57414 ESTABLISHED 7144
TCP 127.0.0.1:5037 127.0.0.1:57415 ESTABLISHED 7144
...
Somebody please suggest a workaround this problem, what might be the cause of this. Also you can take a look at the following image to infer what might be happening.
Try the following:
Close Eclipse.
Restart your phone.
End adb.exe process in Task Manager (Windows). In Mac, force close in Activity Monitor.
Issue kill and start command in <sdk_folder>\platform-tools\
C:\sdk\platform-tools>adb kill-server
C:\sdk\platform-tools>adb start-server
If it says something like 'started successfully', you are good.
For anyone using OSX (I'm aware OP isn't):
What worked for me in the end was removing the android settings folder in the home directory.
rm -Rf ~/.android
For me it didn't work , it was related to a path problem happened after android studio 2.0 preview 1, I needed to update genymotion and virtual box, and apparently they tried to use same port for adb.
Solution is explained here link!
Basically you just need to:
1) open genymotion settings
2) specify sdk path for the adb manually
3) adb kill-server
4) adb start-server
Similar questions are
"The connection to adb is down, and a severe error has occured."
The connection to adb is down, and a severe error has occured.You must restart adb and Eclipse.Please ensure that adb is correctly located
ECLIPSE-The connection to adb is down, and a severe error has occured
First close IDE.
In my case I killed adb via Task Manager(adb kill-server did not work)
then adb start-server
daemon not running. starting it now on port 5037 *
daemon started successfully *
If you see "started successfully" than it is solved, now start IDE.
On my Mac, I wrote this code in my Terminal:
xxx-MacBook-Pro:~ xxx$ cd
/Users/xxx/Documents/0_Software/adt20140702/sdk/platform-tools/
xxx-MacBook-Pro:platform-tools xxx$ ./adb kill-server
xxx-MacBook-Pro:platform-tools xxx$ ./adb start-server
daemon not running. starting it now on port 5037 *
daemon started successfully *
xxx-MacBook-Pro:platform-tools tuananh$
Hope this help.
if you are using any mobile suit like mobogenie or something that might also will make this issue. try killing that too from the task manager.
Note : i faced the same issue, tried the above solution. That didn't work, finally found out this solution.May useful for someone else!..
On my end, I used Resource Monitor to see which application was still listening to port 5037 after all the Eclipse and adb restart were unsuccessful for me.
Start > All Programs > Accessories > System Tools >
Resource Monitor > Network > Listening Ports
This eventually showed that java.exe was listening to port 5037, hence, preventing adb from doing so. I killed java.exe, immediately start adb (with adb start-server) and received a confirmation that adb was able to start:
android-sdks\platform-tools>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
I've got a kind of botch for the old ADB server didn't ACK * failed to start daemon * issue which might help, though i haven't seen anyone else with my problem so maybe not. Anyway...
I changed the default install location for my HTC sensation to 2 (SD card), but when trying to revert back to 0 (internal) i was getting this error. Looking in task manager showed there were 2 instances of adb.exe running, one of which kept stopping and starting and was impossible to kill, the other could be killed but then a new instance would start almost immediately.
The only way i could get adb to start successfully was to get my command ready in the command window, go to task manager to end the adb.exe, then when the window came up saying 'are you sure you want to kill adb.exe' dragged that over the command window, clicked OK then immediately pressed Enter to run the command. It seems that the short window between adb.exe being killed and restarting itself is sufficient to run a command, though if you try to do something else it won't work and you have to repeat this process each time you want to run a command.
PITA but it's the only way an uneducated numpty like myself could get round it - hopefully it'll help someone...
i have solve this problem several times using the same steps :
1- Close Eclipse.
2- Restart your phone.
3- End adb.exe process in Task Manager (Windows). In Mac, force close in Activity Monitor.
4- Issue kill and start command in \platform-tools\
C:\sdk\platform-tools>adb kill-server
C:\sdk\platform-tools>adb start-server
5- If it says something like 'started successfully', you are good.
but now it's doesn't work cause i have an anti-virus called "Baidu", this program have run "Baidu ADB server", finally i turn this process off and retry above steps it's work properly.
When I try to test my Android application with an android emulator as always I now suddenly get an error message. I'm working with Windows 8. So far I tried the following things which unfortunately could not solve the problem:
reinstalling eclipse with android adt
reinstalling java
installing "android studios" first solved the problem but after one day mysteriously also here adb, stopped working with the error message given in the title " ADB not responding ...
furthermore I unsuccessfully tried out some advice from Mr. Google:
Stopping adb.exe via task-manager and restarting eclipse / android studios
"adb kill-server" then "start-server" via command prompt
setting the path to adb.exe as an environment variable
switching off any antivirus or firewall
starting the IDEs as an administrator
updating the IDEs
The only thing I can remember doing which may have destroyed adb on my computer for all times: I connected my motorola smartphone to my laptop and installed the motorola usb drivers but as I said the adb also won't work with the emulator.
Any help would be kindly appreciated. The issue bothers me for more than an entire day now. Maybe someone had similar problems on Windows 8 ?
On OSX helped:
Close Android Studio
Kill all processess using 5037 port
sudo lsof -i |grep 5037
sudo kill PID_NUMBER
Run adb devices from console
adb devices
Meanwhile the emulator is working again. I cannot definetly say what solved the problem. What It could be a combination of two things:
Deleting the hidden ".android" folder under C:\Users...
(Probably there was some malfunctioning automatically created code)
Deleting and recreating the Path variable to the folder with adb.exe ( ...\sdk\platform-tools\;)
Finally it could be a Windows 8 issue which I don't understand.
Try this,
Open a command prompt with administration permission and type
netsh interface tcp set global autotuninglevel=disabled
This worked for me
Edit: Windows only
Kill the adb.exe with a command prompt. Open a command prompt were your adb.exe is located and type
adb kill-server
Maybe HTTP Proxy blocked the localhost 127.0.0.1:5037
If you have config the HTTP Proxy, make sure to exclude the localhost like picture below
Also, port can also be blocked by the firewall and anti-virus firewall, please notice as well.
Try this,
at the prompt try adb kill-server
Start one of your AVDs
at the prompt try adb root
The prompt should say adbd is already running as root.
That should fix it.
In case it helps anyone else, for me the problem was related with the USB hub that the tablet was plugged into on the computer (unplugging the webcam which was in use fixed it).
I got the same error. Don't worry. I have an solution. Go to Task Manager. Kill the process called adb.exe. You will find 2 or 3 processes. Kill all of them. You are done. It will work.
I have the same problems. Verify port 5037 is free and ports 5555 to 5585 are available and never used by another process.
"ADB server sets up connections to all running emulator/device instances. It locates emulator/device instances by scanning odd-numbered ports in the range 5555 to 5585"
FROM: http://developer.android.com/tools/help/adb.html
To find out which process is listening on a port on Windows yo can use:
C:> netstat -an -o
FROM: How can you find out which process is listening on a port on Windows?
I had the same problem, here is my simple fix:
-Go to task manager in windows, look for adb.exe, and kill it
-Go to command prompt, and tap adb devices ==> it will automaticaly start adb daemon
I finally just restarted the computer, and that solved the issue for me.
Uninstall HTC Sync. Or disable it somehow.
Try to open adb from command prompt from directory location as <sdk>\platform-tools,
If adb file is missing try to re-install Android SDK with latest version,
And try to run again..
I think issues will solved, by this procedure.
I saw this on a Mac OS X.
I shut down Android Studio and ran adb get-state in the terminal. When I started Android Studio back up, the warning had gone away.
BTW, I did just try restarting Android Studio without any luck. I am sure a restart of OS would have fixed it too.
The same thing with the Asus Sync utility (with the both our Transformer's 700 and 701).
I think there is a USB-port conflict between ABD driver and Sync utility.
Exit from Sync utility resolve the problem.
Looks like this could be caused by a bunch of different issues. This just happened to me because I had my android phone device plugged in for USB debugging, then after a few hours (and multiple android studio/phpstorm restarts) I had to do unplug the device manually. Things started working again after unplugging.
I have faced this problem few days ago. When I opened my task manager it showing me two adb runnig. It may be because of I am using mobogenie for connecting my android phone for debugging application. This problem is because of moboginie and adt port conflict. then I have followed following procedure to sort out this issue.
!) close eclipse
2) Go to task manager and kill all adb processes.
3) Now go to platform-tools in android sdk
4)press shift+right click mouse and select "open command window here" option
5) type
adb kill-server
adb start-server
6)if server sucessfully started then start eclipse and then connect your phone
(Remember dont connect your phone before starting eclipse)
Following works for me every time:
go to File->Invalidate Caches/Restart
select Invalidate and Restart
And, You are good to go.
I am trying to run adb. When I run : "adb start-server" it hangs during a while, and then no message.
After that the command "adb get-state" receive the answer "error: protocol fault (no status)"
If I run then "adb kill-server" the answer is "* server not running *"
I am using windows 7. An admin has elevated my rights to local admin, but it did not solve anything.
I used resources monitor to verify if any other app is using the ports of adb, but it is not the case.
on https://developers.google.com/chrome-developer-tools/docs/remote-debugging
the step 3 indicates to "Enable USB Web debugging" under Settings > Advanced > DevTools.
But on my test phone, there is no "advanced" category in the chrome settings. I couldn't find out either what is the version of chrome installed.
Somewhere on the web I saw a suggestion to change the rights of "tmp/android/" to allow read & write for all users, but in C:\Users\me\AppData\Local\Android\android-sdk\temp there is no android folder.
So I am pretty desperate now, any help would be immensely appreciated.
thanks
-olivier
EDIT 1: I could't find "Enable USB Web debugging" because it was "android browser" and not chrome (a bit ridiculous yes). I did not know that. Using another device with a proper chrome installed, I could check the option there, but adb is still crashing at startup.
EDIT 2: I did a wild guess that there was some Write issue with the platform-tools folder.
So I uninstalled everything using the sdk manager, I deleted the whole adt-bundle-windows-x86_64. Then I unzipped it elsewhere, on c:. Strange thing is, when I launch SDKManager.exe, several packages are already marked as installed :
Tools>Android SDK Tools
Tools>Android SDK Plateform-tools
Android 4.2.2>SDK Plateform
Android 4.2.2>ARM EABI v7a System Image
Extras>Android Support Library
I tried deinstall them again, delete the folder, unzip again and re-install, but still same result. It seems that somehow, it is installed wrong, but refuses to uninstall properly. Anyone knows how to force the unistallation ?
EDIT 3 :
output of adb start-server after having used set ADB_TRACE=1
C:\adt-bundle-windows-x86_64-20130219\sdk\platform-tools>adb start-server
system/core/adb/adb.c::main():Handling commandline()
system/core/adb/adb_client.c::_adb_connect():_adb_connect: host:version
system/core/adb/sysdeps_win32.c::socket_loopback_client():socket_loopback_client: port 5037 type tcp => fd 100
system/core/adb/transport.c::writex():writex: fd=100 len=4: 30303063 000c
system/core/adb/transport.c::writex():writex: fd=100 len=12: 686f73743a76657273696f6e host:version
system/core/adb/transport.c::readx():readx: fd=100 wanted=4
system/core/adb/transport.c::readx():readx: fd=100 disconnected
system/core/adb/sysdeps_win32.c::adb_close():adb_close: 100(lo-client:5037)
system/core/adb/adb_client.c::adb_connect():adb_connect: service host:start-server
This solution worked for me:
=> Check if adb is running in Task Manager, then kill it. Now Then try to restart it again via following method:
1) Shift + Right click in ...\android-sdk\platform-tools folder and select Open command window here
2) Use these commands:
adb kill-server then adb start-server
If this method didn't work and you see something like this in Command window Killing adb...
Then apply following steps:
3) Close eclipse
4) Now kill javaw.exe Java(TM) Platform SE binary in Task manager And follow step 1 & 2 again.
It will surely work. :)
Try setting the environment variable ADB_TRACE before starting the ADB server to see if it can provide any clues:
C:\Android\android-sdk\platform-tools>set ADB_TRACE=1
C:\Android\android-sdk\platform-tools>adb start-server
Please include the output in your question.
To solve problem in windows machine, try the following:
Problem
ADB stop connecting attached Android device
demon is not running and demon is running on port 5037
Solution
first list all processes which are running on port 5037
command: netstat -ano | find "5037"
Output for above command:
TCP 127.0.0.1:52935 127.0.0.1:5037 SYN_SENT 31016
TCP 127.0.0.1:52936 127.0.0.1:5037 SYN_SENT 31016
Kill processes which are running on port 5037 using the following command: taskkill /F /PID 31016
Then, restart the adb server
adb kill-server
adb start-server
Expected output:
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
Typing adb devices will give you list of devices connected to the adb server
At C:\Documents and Settings\userfoo.android there are some android-related files which uninstaller doesn't delete. Although the most of them are used by AVD, and not by ADB, I recommend you to delete it before any "new fresh" install.
Please check your user rights and privileges, and the user "system" privileges, because of in some companies, they are cutted-off to prevent from virus or automated attacks.
The output can be pinned down to transport code:
D("readx: fd=%d wanted=%d\n", fd, (int)len);
while(len > 0) {
r = adb_read(fd, p, len);
if(r > 0) {
len -= r;
p += r;
} else {
if (r < 0) {
D("readx: fd=%d error %d: %s\n", fd, errno, strerror(errno));
if (errno == EINTR)
continue;
} else {
D("readx: fd=%d disconnected\n", fd);
}
return -1;
}
this might mean adb_read() returns 0 (EOF), while transport tries to read next 4. So, looks like the transport is not being able to read anything but EOF, and simply disconnects. This maybe a USB Driver issue.
Try using Linux, or running commands with root/admin privilege.
Try this,
Open a command prompt with administration permission and type
netsh interface tcp set global autotuninglevel=disabled
This worked for me
I have the same while i was running a java application 'traccar', it works for me after killing this process
I think another process like java web server or java application like "traccar" running on your machine. It works for me after killing these process.
Uninstall Platform Tools in Android SDK Manager
Find and delete all copies of AdbWinUsbApi.dll, AdbWinApi.dll and adb.exe
Reinstall Platform Tools in Android SDK Manager
I can think of a couple of scenarios in which you would encounter this behavior.
(most likely) You're not running adb.exe as a priviledged user. Even though you're set up as a local admin, you're not running this command with elevated privileges. Since the default run->cmd is in normal user mode, this is expected. The following article explains how to run the command prompt as an admin / priviledged user. http://www.howtogeek.com/howto/windows-vista/run-a-command-as-administrator-from-the-windows-vista-run-box/
(less likely) You may need to add adb.exe to the Windows firewall rules. Go to Control Panel -> Windows Firewall, and click on "advanced settings". Then, under "inbound Rules" and "outbound rules", add a rule for adb.exe as a program.
What I did was end the adb.exe on my task manager, restarted Android Studio and then I connected my device again then everything went fine :D
adb was not responding at all for me on Windows 10. Restarting the Android device solved the problem.
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. )
I had the same problem, here is what actually helped me:
Go to platform-tools in Android SDK directory.
Type:
adb nodaemon server
Output:
cannot bind 'tcp:5037'
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:
Note that process with PID 4888 is occupying port 5037.
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
Retry adb kill-server and adb start-server, hopefully adb is up running fine.
Killing the process in the TASK MANAGER solves it in my case. After killing it run adb start-server or adb devices and you should be fine
solved the problem.
Because I have a small assistant plugin installed on my pc, it has an adb.exe running in the background all the time. So after I uninstalled the plugin, the error has gone!
I have an HTC device, whose driver software (HTC Sync) tried to run processes using adb at the same time that I was trying to run from Eclipse. If you have a program like HTC Sync for your device that might have been needed to install the driver, close this program to keep it from executing adb in parallel. So far for me, this has fixed it 100 percent.
Sometimes when we are running SnapPea, it is running a background process called "wandoujia_adb". when killing the process and running the command "adb start-server" in cmd promt, i get the following o/p text to cmd promt:
C:\Users**>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Here Is your Solution
Kill ADB process
CLose Eclipse
Remove Lock File .metadata of workspace
Ensure Only one Java Whether JDK or JRE in installed
if found remove the previous version
Use Ccleaner to remove Temp files
Clean Registry too
Restart the system
Restart Eclipse
If you have your device connected and you are trying to test through an emulator, make sure that a device sync agent isnt running in the background. This relaunches the adb even after you kill it in task manager.
I have tried many approaches I've found here, but just one worked out perfectly:
UNINSTALL AVAST ANTIVIRUS!
I had a mobogenie plugin installed on my machine which was continuously running adb. Uninstalled it and got the problem solved.
In my case I was using the mobogeine universal driver, when I end task adb.exe from task manager, It restarts again in 1-2 seconds occupying another port number.
To get rid of this problem I have to disconnect my phone & 1st kill mobogeine driver, then adb.exe does not restarts agian. Now run adb start-server . If the success message shown then everything worked perfectly.