Adb server not responding

Question

I am new to Android. I think I could do something stupid here. I started a virtual device and I see that the adbd daemon is starting from the terminal emulator. When I search for adb devices, I get the following error:

C:\Program Files\Android\android-sdk\tools>adb devices * daemon not running. starting it now on port 5037 * ADB server didn't ACK * failed to start daemon * error: cannot connect to daemon 

No other process uses port 5037. What am I doing wrong? Here are the packages I installed -

 1) Android SDK Tools, revision 10 2) Android SDK Platform-Tools, revision 3 3) SDK Platform Android 2.3.3, API 10, revision 1 

Answer 1

I turned off the Windows firewall and its work like magic. I am connected to the Internet via WiFi. If you are not behind a proxy server and still cannot access the Internet wirelessly through an emulator, go to the device manager and disconnect your LAN card.

Answer 2

This will happen in normal mode if abd fails to start normally and fails when kill-server adb is running.

So, if on Windows 1. Go to the task manager (CTRL + ALT + DEL) 2. View the adb.exe file and complete the process. Now restart the emulator, it should work correctly.

In addition, you can close and start the development environment (for example: Eclipse or NetBeans).

Answer 3

I suspect that the problem is related to many instances of adb (on Windows), I usually encounter this problem, so I do not turn off my system, so the adb process may not finish properly.

So, having opened the task manager, select the "Process" tab, just find adb.exe, right-click on it and select End Process Tree , and not just "End Process"

Answer 4

If the same problem, it looks like my security solution blocked adb.exe

Answer 5

this is not the right folder for adb: lately adb has moved from / tools to / platform-tools to the sdk folder.

Answer 6

It seems like the security program is blocking adb.exe , so go to the adb file path and open the adb properties, then check the Run this program as administrator parameter.

Answer 7

In my case, the adb.exe process starts when I connect the phone, and then when I have adb devices, I have your problem, and killing the process does not help it to resurrect like a stubborn zombie if the phone is connected. so I decided to disconnect the phone and then kill the adb.exe process and then start it using adb devices and connect the phone After that, when I manage adb devices, I get the same message about adb destruction being outdated, but this time on the second line * daemon started successfully *

win xp htc sensation is the new eclipse adt sdk bundle from google, so I assume this is relevant.

Answer 8

I found that the Tadb.exe process was called in the Windows Task Manager. I assume Tadb.exe is a similar adb Tencent application. Because I received a warning about the “Android device detected by QQ” after I installed the latest version of Tencent QQ2013 Beta5 (6970) yesterday.

After I killed Tadb.exe, the original adb.exe Android SDK file works again.

You can see a detailed request to solve this problem: adb cannot work, adb server is out of date

Answer 9

根本 原因 是 因为 你 的 机器 上 5037 端口 被 某个 进程 占用 了, 此时 不但 android 设备 无法 使用 ADB 连接, iOS 设备 也不 能用 Itunes 连接.

可以 查询 到 占用 5037 端口 的 进程 并 关闭 它, netstat / a / o也许 可以 帮助 你.

要 windows7 上, LogsAndAlerts 服务 会 占用 5037 端口.

---

The main reason is that port 5037 on your computer, busy with the process, not only Android devices cannot use the ios device to connect adb without using iTunes.

You can request a process and close it, netstat / a / o can help you deal with up to 5037 ports.

On Windows7, the LogsAndAlerts service will take port 5037.

Answer 10

As I tried following the omni.present union, and finally the emulator is working fine. firstly i stop the adb.exe process in task manager then i stop and start eclipse