Sam Mearns Sam Mearns - 13 days ago 6
Android Question

Android ADB - Daemon still not running

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:


  • Rebooting my PC

  • Rebooting my Phone

  • Executing
    adb shell

  • Executing
    adb start-server
    and then executing
    adb shell

  • Killing ADB and Executing
    adb shell

  • Killing ADB and Executing
    adb start-server
    and then executing
    adb shell

  • Reinstalling my phone's USB Drivers

  • Checking port 5037, It is not in use by any other application, and only becomes used by adb.exe when I start the daemon.



Am I missing something obvious? Help me please :P

EDIT: Solution on another question: http://stackoverflow.com/a/29524143/2872279

Answer

In the end, I downgraded from Windows 10 to Windows 7 and ADB worked perfectly. You probably wouldn't have to do that, but I would recommend trying:

  1. Uninstall ADB and Reinstall [If you didn't get it standalone, uninstall and reinstall that part of the SDK, then try reinstalling the SDK]
  2. If that doesn't work, try making a second user account and seeing if it works. If that works its a problem with your user account.
  3. If that doesn't work try your Android phone in another computer, if it works its a problem with your PC. [My PC was recognising the phone but ADB wasn't working]
  4. Try reinstalling your OS
  5. If all else fails, try downgrading your OS, if you recently installed a new OS, it may not be compatible with ADB. When I was using Windows 10, I was using a pretty unstable insider build.
Comments