Reputation: 202
When I run ADB and type in "adb start-server" it says
*daemon not running. starting it now on port 5037 *
could not read ok from ADB Server, error = 109
*failed to start daemon *
error: cannot connect to daemon
what should I do? I've tried killing the server and restarting the pc but nothing seems to work. my pc recognizes the phone and the adb process only appears briefly when i try to start the server. also, it gets stuck on wating for device when i type "fastboot oem unlock"
Upvotes: 10
Views: 26751
Reputation: 3904
This happened to me because I had Oculus Developer Hub open.
Even if you're not using its adb features, it will constantly try to start its own version of adb and kill the one you're trying to launch.
Upvotes: 0
Reputation: 445
In my case the issue was in IntelliJ IDEA plugin - Aladdin Logcat. Turned it off and everything works now.
Upvotes: 0
Reputation: 1554
Looks like windows is messing up the ports (reserving them). I have the same issue with docker containers and this worked for me:
Run this in the command line (as administrator)
net stop winnat
adb.exe start-server
net start winnat
Upvotes: 32
Reputation: 68
Happened to me today.
I realized it happened when I started Android Studio after having my Genymotion emulator running, so I fixed it by closing everything (even check task manager for a running instance of adb). After closing everything, I opened Android Studio first and then the emulator and everything was ok.
Upvotes: 4
Reputation: 644
Happened with me as well. Just check there might be an existing adb process running in your task manager. Just kill the process and run the 'adb start-server' command. Hope it helps
Upvotes: 13