Quick Note: I am in the Android SDK "platform-tools" directory.
My problem seems to be a bit of a weird one - Whenever I start ADB with adb start-server
, I get the following:
* deamon not running. starting it now on port 5037 *
* daemon started successfully *
Well, Great. It started successfully. Now I try using adb shell
:
* deamon not running. starting it now on port 5037 *
What??? I thought it already started...ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
Well, Crap. So I open Task Manager and kill adb.exe. Then I run adb shell
(without running adb start-server
first).
This time I get:
* deamon not running. starting it now on 5037 *
* deamon started successfully *
** deamon still not running **
error: cannot connect to deamon
So, As a brief summary - here is what I have tried:
adb shell
adb start-server
and then executing adb shell
adb shell
adb start-server
and then executing adb shell
Am I missing something obvious? Help me please :P
EDIT: Solution on another question: https://stackoverflow.com/a/29524143/2872279
Check that you have the correct USB drivers for your Android device installed (they should either include or be downloaded with an ADB driver).
If you haven't installed platform-tools
, you need to do so. You can get a copy from the Android Developer's website: https://developer.android.com/studio/releases/platform-tools
If this was already working for you and it has recently stopped, on Windows - try reinstalling the driver and/or checking that the device is actually recognised. You can do so by running devmgmt.msc
with + R or from command prompt.
It might be worth just checking that your USB cable is not damaged - ideally try connecting your phone to another computer or with another USB cable. This has been an issue more times than I would care to admit.