ADB server didn't ACK on macOS

adb server didn't ack ubuntu
adb server kill
adb server is out of date
could not read ok from adb server
update adb server version
daemon not running android studio
adb stop-server
adb server can not be started

I am getting this error since two days ago when I updated my Android Studio to the latest stable version 2.3; the full error message I am getting from Gradle Console is:

07:59:59 E/adb: error: could not install *smartsocket* listener: Address already in use
07:59:59 E/adb: ADB server didn't ACK
07:59:59 E/adb: * failed to start daemon *
07:59:59 E/adb: error: cannot connect to daemon
07:59:59 E/ddms: '/Users/USER_NAME/Library/Android/sdk/platform-tools/adb start
server' failed -- run manually if necessary

My attempts to solve the issue:

  • kill all adb processes and make sure no process is holding port 5037, adb kill-server (says * server not running * even in cases when adb is running), close Android Studio, delete ~/.android directory, run adb start-server (says * daemon not running. starting it now at tcp:5037 *; * daemon started successfully *, start Android Studio and run application, MAC throws error adb quit unexpectedly and gradle console shows same the error I posted above.

  • uninstalled and deleted all Android Studio stuff (except for projects directory), restarted MAC, installed fresh and latest android studio.

  • increased gradle vm ram org.gradle.jvmargs=-Xmx1536M in project

  • uninstalled antivirus and restarted the mac


  • OS: MacOS Sierra 10.12.3
  • Android Studio: 2.3
  • buildToolsVersion: '25.0.0'
  • Android Debug Bridge version: 1.0.39

Address already in use means you have another instance of adb running. Check your system variable $PATH and $ANDROID_HOME and file (of your project) and your .bash_profile . Make sure that all of these has same android sdk path. Then try restarting the adb server. adb kill-server and adb start-server.

ADB server didn't Acknowledge, 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  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 corre

I read that you killed the adb, but as this answer says How to resolve the "ADB server didn't ACK" error? did you do that from the platform-tools folder? If your answer is yes, update the Android SDK to the lastest version via the SDK manager and update the $ANDROID_HOME

I hope it helps!

adb server didn't ACK || Daemon not running, After entering any adb command if you're getting an error like : * daemon not running. starting it Duration: 3:18 Posted: 26 Dec 2015 To fix the "adb server is out of date" bug, please follow these steps: Connect your device to the USB port Download and run ADBFix. Specify the location of your Android SDK.

I usually find this issue occurring when I have two instances of ADB working, i.e when I have my Eclipse and Android studio running at the same time AND when they point to different SDK Manager(platform-tools folder) on the system. Try to search for what other IDE is using ADB, kill it in the Activity Monitor and run only one instance. Or my work around was to have only one SDK Manager and point both my IDEs to one platform-tools folder.

Hope that helps.

[Solved, kind of] ADB not working, "ADB server didn't ACK , not install *smartsocket* listener: Address already in use ADB server didn't ACK * failed to start daemon * error: cannot connect to daemon. After entering any adb command if you're getting an error like : * daemon not running. starting it now * ADB server didn't ACK * failed to start daemon * err

In my case, I had an old version of adb installed using brew cask. And while I updated my Android Studio to the latest, the adb was still pointing to the brew installed older version.

So after updating that version, using:

brew cask install android-platform-tools

And making sure that the adb itself was pointing to the new version, the errors went away.

ADB server didn't ACK * failed to start deamon*, 5. 6. 7. Windows Command Prompt. c:androidsdkplatform-tools>adb devices. adb server is out of date . killing ADB server didn't ACK. * failed to start daemon *. Yes, that was indeed where my ADB was located. However, I gave that AUR package a shot, and voilà – after uninstalling android-tools, installing android-sdk-platform-tools, and changing the path i bashrc it seems to work again.

Just write down platform-tools path (/Users/USER_NAME/Library/Android/sdk/platform-tools) In the .bash_profile file, located at (/Users/USER_NAME/.bash_profile), like this :

export PATH="$PATH:/Users/USER_NAME/Library/Android/sdk/platform-tools"

"adb server didn't ack * failed to star…, *Daemon not running, starting it now on port 5037*(this does successfully start the adb.exe process) ADB server didn't ACK * failed to start  ADB server didn't ACK Full server startup log: /tmp/adb.1000.log Server had pid: 30319 --- adb starting (pid 30319) --- adb I 09-28 01:13:58 30319 30319 main.cpp:57] Android Debug Bridge version 1.0.39 adb I 09-28 01:13:58 30319 30319 main.cpp:57] Version 1:8.1.0+r23-5~18.04 adb I 09-28 01:13:58 30319 30319 main.cpp:57] Installed as /usr/lib

adb server problem + ADB server didn't ACK + thread spawning + , adb server problem + ADB server didn't ACK + thread spawning + failed to start daemon : All of that with one command >flutter run #37869. ADB and Fastboot tools store your smartphone or tablet’s ADB_VENDOR_KEY in one of these files and for some reason, it can’t access it. So go ahead and delete both of these files. Restart your computer, and start up the ADB server again with the “adb devices” command.

How do I fix adb "failed to start daemon" error?, daemon not running; starting now at tcp:5037 ADB server didn't ACK Full server startup long: /tmp/adb.1000.log Server had pid: 2036 --- adb  Do check your antivirus. It may be blocking the ports of adb.exeor emulator programs, etc. That solved the problem in my case. 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) I had a similar issue.

ADB is server is out of date, killing … - Bilal Bayasut, adb devices adb server is out of date. killing… cannot bind 'tcp:5037' ADB server didn't ACK * failed to start daemon * error: I've searched the  c:\Program Files\Expo XDE\resources\app ode_modules\xdl\binaries\windows\adb\adb.exe into that same location. I killed adb with: adb kill-server which caused a restart of the adb server automatically due to having my Genymotion device already running. I hit the “Restart” button inside of the Expo XDE and it immediately began working.

  • Try reinstalling (i.e. uninstalling and installing again) platform-tools from within Android Studio SDK Manager. You might run adb command in shell between those actions to make sure ADB wasn't duplicate-installed in your system.
  • Hi @Onik, I uninstalled platform-tool then ran adb on terminal. It says the command not found. So I think there's noduplicates
  • Thanks JIthin, I always saw one instance of adb in Activity Monitor. Then I created a new user on my MAC and installed Android Studio and it worked. I figured it out it is has to do with $PATH and digged into .bash_profile .bashrc .profile .zshrc .zlogin and cleaned up duplicates and it works. Thanks again.
  • Hi @Jaco, the first link doesn't resolve the issue on my MAC; see the log. As for the second link, SDK path is already set, and I created and exported a custom path, installed the tools, and changed it in Android Studio, but still no luck
  • Please elaborate your answer to help others arriving at this question.