adb cannot connect to its daemon or start the server
* daemon not running. starting it now on port 5037 *Short answer
The adb server is a background process on your computer that listens on TCP port 5037. If it is stuck or cannot start, adb commands and Android Studio fail. Stop it with adb kill-server, start it again with adb start-server, and update SDK Platform-Tools if the emulator still does not connect.
Fix it fast
1Find out which cause you have
Run any adb command in a terminal. If the server is healthy it answers with the device list. If it prints the daemon lines, watch whether the second line says it started successfully.
adb devices2Match what you see, then jump to its fix
- 1
adb devices shows the daemon-not-running lines but no device list appears, or the list stays empty although the emulator or phone is on.The adb server is stuck or hungFix - 2
Android Studio cannot connect to a freshly created emulator, while a new AVD starts but never shows up as a device.Old SDK Platform-Tools cannot talk to the emulator or deviceFix
- 1
What does the error look like?
* daemon not running. starting it now on port 5037 ** daemon started successfully *adb.exe,start-server failedAndroid Studio error: cannot connect to daemon
Cause 1 of 2
The adb server is stuck or hung
1Check
The adb client starts the server on first use. If that server is in a bad state, commands that follow do not work. Look at what adb reports now.
adb version
adb devices2Fix
Stop the server and start it again. Android Studio has the same action as the Restart ADB server button on the last page of Tools > Troubleshoot Device Connections.
adb kill-server
adb start-server3Verify
The command prints the daemon-started lines, then lists your device or emulator.
adb devicesConfirmed by developer.android.com
Cause 2 of 2
Old SDK Platform-Tools cannot talk to the emulator or device
1Check
Google's own troubleshooting asks you to start an emulator from Device Manager. If Android Studio cannot connect to it, the Platform-Tools package is the suspect.
adb version2Fix
Update Android SDK Platform-Tools in Tools > SDK Manager > SDK Tools, or download the latest standalone package, then restart the server.
sdkmanager "platform-tools"
adb kill-server
adb start-server3Verify
adb version shows the new build and the emulator is listed.
adb version
adb devicesConfirmed by developer.android.com
How do I stop it coming back?
- Keep SDK Platform-Tools updated through SDK Manager so Android Studio and your terminal use one recent adb.
- Restart the adb server first, before rebooting the machine or reinstalling the IDE.
- Let the emulator choose its own ports instead of fixing them by hand.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
Related fixes
Mobile apps
Android Studio says it cannot find adb
'adb' is not recognized as an internal or external command, operable program or batch file.
adb is shipped in the SDK Platform-Tools package, in the platform-tools folder of your Android SDK.
3 causes, each with a fixMobile apps
A phone is plugged in over USB but Android Studio and adb do not list it
adb devices prints List of devices attached with nothing below it
adb lists a phone only when four things hold: USB debugging is on, you accepted the computer's RSA key on the phone, the computer has a driver or udev rule for the device, and the cable carries data to a running adb server.
6 causes, each with a fixMobile apps
adb cannot start because something already holds its port
adb start-server failed
The adb server must bind local TCP port 5037, and every adb client talks to it there.
2 causes, each with a fixMobile apps
adb prints 'server version doesn't match this client; killing...'
adb server version doesn't match this client; killing...
adb runs a background server, and every adb command is a client.
3 causes, each with a fixMobile apps
adb tcpip 5555 fails because no device is found
adb: more than one device/emulator
adb tcpip only works while the device is attached and listed by adb, because it tells the phone to start listening on port 5555.
4 causes, each with a fixMobile apps
The Android Emulator says /dev/kvm is not found
KVM acceleration can NOT be used
The emulator wants a hypervisor and cannot find one.
4 causes, each with a fix