Resolves adb server didn ' t ACK that appears when Android development on Mac

Mac on the ADB connect not to Android phone can refer to: here

xxxdemacpro:~ xxx$ adb start-server* daemon not running. Starting it now on port 5037 *adb server didn ' t ack* failed to start daemon *

The above situation, one of the cases is that the other software occupies the port, you can directly kill the process of taking up the port, how to view Google a bit, a lot of

There is a pit, I have been looking for a long time, really a big hole

Enter in Terminal: VI. Android/adb_usb.ini Open Adb_usb.ini

# Android 3RD Party USB VENDOR ID  list# USB "ANDROID update adb ' to generate# USB VENDOR ID PER line# mx40x2a45

As the content above, it seems that there is no problem, please note that a blank line above the #MX4, yes, that is the problem of the empty line, delete is ok

Resolves adb server didn ' t ACK that appears when Android development on Mac