Adb won't start

Question

Running Vista, tried starting adb from shell as admin get daemon not running starting it now

ADB server didn't ACK
* failed to start daemon *

Any help for this?

Answer 1

There is yet another possibility. If you have installed any permission managers, like Advanced android permission manager , the adb may fail.It was my case. Uninstalled the app and then no issues.

Answer 2

I was unable to use adb. I got the following error, both on the command line and in eclipse.

* daemon not running. starting it now on port 5037 *
ADB server didn't ACK<br>
* failed to start daemon *

That is, adb start-server failed even after rebooting. To diagnose the problem, I found that you can run adb with the following arguments:

adb nodaemon server

And it will print out the reason that it cannot run. In my case, it was a blank line in the adb_usb.ini file.

Answer 3

You may have a stuck copy of the adb daemon in memory. Try removing it with Task Manager, or reboot, and see if that helps.

Answer 4

The top answer is Windows-specific but this has a decent amount of Google visibility, so if you're running a *nix-like machine (I'm on a Mac), the steps are similar:

$ killall adb
$ cd <PATH_TO_SDK>/platform-tools/
$ adb kill-server
$ adb start-server

Or, if you're like me and just want to access adb no matter your current directory, add

export PATH=${PATH}:<PATH_TO_SDK>/platform-tools/

to your ~/.bash_profile.

Answer 5

This problem has annoyed me for a long time. In addition to the above answer, use these tips:

• Create a bat file with the following and run it. This bat file will solve most of your adb problems.

tskill adb

cd \tools\

adb kill-server

adb start-server

ddms

• Use the command netstat to monitor the state of connections (adb uses 5037)

• If the bat file doesn't work try: disconnect-reboot phone-connect. (hint: use `adb reboot' if adb is responding at all, if not do it the old fashioned way)

• Sometimes Windows can be funny. Reboot the machine.

• Turn on USB Debugging Mode

  • Download the Android SDK and unzip
  • Uninstall all "Android *" from Device Manager
  • Do an "Add Hardware" from Control Panel, choosing "Install the hardware... (Advanced)"
  • Select "Android USB Devices" and click "Next"
  • Click "Have Disk" and enter the path where the SDK was unzipped

• Still not working ? Factory reset the phone.

• MTP detection delays ADB. Sometimes you if need boot time logs you may have to disable the MTP driver in Device Manager (Windows)

---

This is a brilliant patch for adb when you get the error :

Adb connection Error:An existing connection was forcibly closed by the remote "

Answer 6

It seem are the same, but sometime, the command adb kill-server have no effect (at least is in my case). So, i have tried other way.

You can check this way: https://stackoverflow.com/a/34627522/5597864