ADB server didn't ack * failed to start daemon * Solution

A few days ago, I took a leave of absence. After I returned to my company, I turned on my computer and plugged in my cell phone. Eclipse reported the ADB server didn 'Tack * failed to start daemon * error. The previous problems were:

1. Shut down the task manager, shut down the adb.exe process, or re-plug the phone and restart eclipse;

2. Alternatively, there is a downward arrow in the upper right corner of the devices range in ddms in Eclipse:

Click it and select reset ADB;

3. You can restart eclipse and restart your computer.

However, this time, it is useless. This time, ADB started, but it was immediately killed. It may be that 360 has added a blocked list. This is easy to do, just cancel it. If it is not blocked, check whether your pods have been enabled, turn off the pods, and re-plug the pods with your phone, if the pod is enabled, the pod will also enable ADB, which will cause eclipse to fail to enable ADB.

In fact, the pea pod is only used to install the driver. You can debug it in eclipse without it.ProgramWe recommend that you enable the function when you cancel the mobile phone connection in the pod settings.