* daemon not running.starting it now on port 5037 * 问题解决
2015-04-04 20:10
357 查看
今天，又出现了adb连接不上的问题了。
现象，adb shell 时出现以下信息：
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
显然，原因是ADB SERVER的端口被占用。
解决方法：
请参考：
adb server is out of date. killing完美解决：
地址： /article/1496393.html
内容来自用户分享和网络整理，不保证内容的准确性，如有侵权内容，可联系管理员处理 
相关文章推荐
- * daemon not running.starting it now on port 5037 * 问题解决
- mac下* daemon not running.starting it now on port 5037 * 问题解决
- 解决daemon not running. starting it now on port 5037
- daemon not running. starting it now on port 5037 ADB server didn't ACK 解决5037端口被其他进程所占用
- 关于老问题 * daemon not running. starting it now on port 5037 * ADB server didn't ACK * failed to st
- adb devices : * daemon not running. starting it now on port 5037
- android搭建环境错误 daemon not running. starting it now on port 5037 ADB server didn't ACK
- 有关于* daemon not running.starting it now on port 5037 *ADB
- adbl连接不上 daemon not running. starting it now on port 5037 ADB server didn't ACK
- adbl连接不上 daemon not running. starting it now on port 5037 ADB server didn't ACK
- Android adb shell:daemon not running. starting it now on port 5037错误
- adbl连接不上 daemon not running. starting it now on port 5037 ADB server didn't ACK
- android搭建环境错误 daemon not running. starting it now on port 5037 ADB server didn't ACK
- adbl连接不上 daemon not running. starting it now on port 5037 ADB server didn't ACK
- android搭建环境错误 daemon not running. starting it now on port 5037 ADB server didn't ACK
- 安卓：daemon not running. starting it now on port 5037 ADB server didn't ACK
- android搭建环境错误 daemon not running. starting it now on port 5037 ADB server didn't ACK
- android搭建环境错误 daemon not running. starting it now on port 5037 ADB server didn't ACK
- daemon not running.starting it now on port 5037 *
- android搭建环境错误 daemon not running. starting it now on port 5037 ADB server didn't ACK