Develop Reference

Daemon not started in Android Studio

Please don't mark this as a duplicate question.
When i m trying to run app in emulator or in real device everytime it throws an exception
Unable to connect to adb. Verify that your localhost entry is pointing to ip4 or ip6 respectively Android
For getting solution i dig google and tried the solution using
adb tcpip 5555
adb connect 127.0.0.1:5555
But every time it catch the same exception.
daemon not running; starting now at tcp:5037
adb F 05-03 12:32:21 9776 7156 main.cpp:45] cannot open C:\Users\admin\AppData\Local\Temp\adb.log: Permission denied
This application has requested the Runtime to terminate it in an unusual way.
Advanced help would be appreciated!

Open command Prompt use following commands
adb kill-server
adb start-server
adb devices // it will shows the device id if its connect success
if not showing the device restart android studio and mobile then execute the command again it will work

Finally i found an answer.
There was my silly mistake. While i was set JAVA_HOME path by
C:\Program Files (x86)\Java\jre1.8.0_211\bin
So just i needed to remove \bin. The correct path is
C:\Program Files (x86)\Java\jre1.8.0_211
Further i started Android Studio as Run as Administrator.

First, try running adb.exe in at the sdk/platform-tools. If it's not working then probably your adb.exe is broken. Then you need to download the sdk again or you can replace the platform-tools folder from some another pc. I also face that problem with Android Studio 3.4.

adb cannot start daemon, CreateProcess failure, error 2

I an unable to run adb root or any adb command. I get the following error. I set ADB_TRACE=1:
C:\WINDOWS\system32>adb root
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: could not connect
to tcp:5037
system/core/adb/adb_client.c::adb_connect():adb_connect: service root:
* daemon not running. starting it now on port 5037 *
CreateProcess failure, error 2
* failed to start daemon *
error: cannot connect to daemon
I am using Windows 7.
From netstat -a I don't see anything else using port 5037. When I run adb, I observe that adb momentarily is displayed on Task Manager, but then it goes away. Windows Firewall is turned off. I get the same results if I run cmd as administrator.

You need to make sure that all your development tools use the same version of adb.
One easy way to do that is to open the Command Prompt window as Administrator and run these 2 commands to delete all copies:
taskkill /f /im adb.exe
for %a in ("%systemroot%" "%userprofile%" "%path:;=";"%") do #del /q /f /s "%~a\adb.exe" "%~a\adbwinapi.dll" "%~a\adbwinusbapi.dll" 2>nul
Then reinstall the latest version of the platform-tools package from the SDK Manager or manually by downloading and unzipping the package file (check adb info page for the link) into the %ANDROID_SDK_HOME% folder.
Also make sure that %ANDROID_SDK_HOME%\platform-tools folder is included in your %PATH%.

I solved this problem long ago, but did not update this question.
I was having this issue because I was running the incorrect adb executable. I had one executable in C:\Windows\system32 and another in a different directory. The version in C:\Windows\system32 had did not have all the files needed by adb whereas the version in the other directory did. I'm not sure what those files were, but the adb executable was the same version in both directories. Since C:Windows\system32 was in the PATH first, that version was executed first. I removed adb from the Windows directory, and the problem went away.

I just solved this issue by going to Task Manager and killing all the adb' then it works like a charm.

I faced the same issue, to solve it, I have uninstalled the package Platform-tools on the SDK manager -> SDK tools and re-installed it.
Now, It's working correctly.

I solved this by going to the actual platform-tools directory.
Default path is C:\Users[youruser]\AppData\Local\Android\sdk\platform-tools
Apparently it won't start unless you change to that directory.

You can try this solution: Move the adb.exe and adbwinapi.dll to X:\Windows\system
It worked for me

I got the same problem, BTW I am using win7 64bit.
solved it like this:
Move the adb.exe and adbwinapi.dll to X:\Windows\SysWOW64
hope useful

ADB not responding. You can wait more, or kill "adb.exe" ... windows 8

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.

ADB is not starting (no error message)

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.

Eclipse error "ADB server didn't ACK, failed to start daemon"

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.