11

我在这个问题上花了大约 5 个小时。我在stackoverflow上阅读了同样的问题，但没有一个解决方案解决了我的问题...... 首先，它给了我： 

[2013-02-28 14:48:21 - adb] ADB server didn't ACK
[2013-02-28 14:48:21 - adb] * failed to start daemon *

为了解决这个问题，我在任务管理器中杀死了 adb.exe，重新启动 eclipse。然后去DDMS，重置adb。没运气...

然后，我转到命令行窗口，输入adb kill-serverand adb start-server，它给了我：

adb server is out of date. killing...
ADB server didn't ACK
fail to start deamon

现在我不知道该怎么办。我有一个项目要在eclipse上开发，所以真的需要尽快解决这个问题。有人请帮忙！！

（正如许多解决方案所示，我杀死了我的 adb.exe 数千次，但它在 2 秒后立即出现在任务管理器中。）

4

10 回答 10

16

I had the same problem, here is what actually helped me:

  1. Go to platform-tools in Android SDK directory.

  2. Type:

    adb nodaemon server

    Output:

    cannot bind 'tcp:5037'

  3. Now I know the reason adb not responsive is because it can not bind to port 5037. Use following command to find out the process that occupies the port:

    netstat -ano | findstr 5037

    Output:

    Find port binding

  4. Note that process with PID 4888 is occupying port 5037.

  5. Open Task Manager, click on Details tab, find the process and kill it, tfadb.exe in this case. it may vary for me it is sh.exe and port 4599 and delete all adb.exe

    Processes

  6. Retry adb kill-server and adb start-server, hopefully adb is up running fine.

    Fine

于 2014-03-08T02:00:09.973 回答
14

在我的情况下，终止 TASK MANAGER 中的进程可以解决它。杀死它后运行adb start-server或adb devices你应该没问题

于 2013-06-10T12:07:11.853 回答
2

解决了这个问题。因为我的电脑上安装了一个小助手插件，所以它的后台一直运行着一个adb.exe。所以在我卸载插件后，错误就消失了！

于 2013-02-28T15:15:34.217 回答
2

我有一台 HTC 设备，它的驱动程序软件 (HTC Sync) 试图在我试图从 Eclipse 运行的同时使用 adb 运行进程。如果您的设备有可能需要安装驱动程序的程序（如 HTC Sync），请关闭此程序以防止它并行执行 adb。到目前为止，对我来说，这已经修复了 100%。

于 2013-05-24T01:59:03.930 回答
1

Sometimes when we are running SnapPea, it is running a background process called "wandoujia_adb". when killing the process and running the command "adb start-server" in cmd promt, i get the following o/p text to cmd promt:

C:\Users**>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

于 2013-07-12T07:30:09.497 回答
0

Here Is your Solution

  1. Kill ADB process
  2. CLose Eclipse
  3. Remove Lock File .metadata of workspace
  4. Ensure Only one Java Whether JDK or JRE in installed if found remove the previous version
  5. Use Ccleaner to remove Temp files
  6. Clean Registry too
  7. Restart the system
  8. Restart Eclipse
于 2013-08-08T03:52:47.833 回答
0

If you have your device connected and you are trying to test through an emulator, make sure that a device sync agent isnt running in the background. This relaunches the adb even after you kill it in task manager.

于 2013-12-08T15:34:17.503 回答
0

I have tried many approaches I've found here, but just one worked out perfectly:

UNINSTALL AVAST ANTIVIRUS!

于 2014-04-12T21:31:55.273 回答
0

I had a mobogenie plugin installed on my machine which was continuously running adb. Uninstalled it and got the problem solved.

于 2015-02-23T13:23:10.117 回答
-1

In my case I was using the mobogeine universal driver, when I end task adb.exe from task manager, It restarts again in 1-2 seconds occupying another port number.

To get rid of this problem I have to disconnect my phone & 1st kill mobogeine driver, then adb.exe does not restarts agian. Now run adb start-server . If the success message shown then everything worked perfectly.

于 2015-06-02T04:56:43.847 回答