Android ADB server didn't ACK
2013-08-20 22:54
363 查看
运行android工程,出现错误,adb没有启动,在命令行中输入adb start-server,报错。
解决办法如下:
命令行中输入 adb nodaemon server 查看是不是adb服务器端口有冲突
![](http://img.blog.csdn.net/20130820224249734?watermark/2/text/aHR0cDovL2Jsb2cuY3Nkbi5uZXQvZnJlZXRhbmd4aWFveWluZw==/font/5a6L5L2T/fontsize/400/fill/I0JBQkFCMA==/dissolve/70/gravity/SouthEast)
命令行中输入 netstat -ano|findstr "5037" 即可显示相应的PID号
![](http://img.blog.csdn.net/20130820225233250?watermark/2/text/aHR0cDovL2Jsb2cuY3Nkbi5uZXQvZnJlZXRhbmd4aWFveWluZw==/font/5a6L5L2T/fontsize/400/fill/I0JBQkFCMA==/dissolve/70/gravity/SouthEast)
打开任务管理器,选中“服务”,查看相应PID号对应的名称,然后选中“进程”,找到对应的名称,结束进程,如图
![](http://img.blog.csdn.net/20130820225255593?watermark/2/text/aHR0cDovL2Jsb2cuY3Nkbi5uZXQvZnJlZXRhbmd4aWFveWluZw==/font/5a6L5L2T/fontsize/400/fill/I0JBQkFCMA==/dissolve/70/gravity/SouthEast)
重启eclipse,即可。
解决办法如下:
命令行中输入 adb nodaemon server 查看是不是adb服务器端口有冲突
命令行中输入 netstat -ano|findstr "5037" 即可显示相应的PID号
打开任务管理器,选中“服务”,查看相应PID号对应的名称,然后选中“进程”,找到对应的名称,结束进程,如图
重启eclipse,即可。
相关文章推荐
- 当android调试遇到ADB server didn't ACK以及顽固的sjk_daemon进程
- Android 解决ADB server didn't ACK问题
- 当android调试遇到ADB server didn't ACK以及顽固的sjk_daemon进程 .
- Android EclipseADT 报错: ADB server didn't ACK的解决方法
- Android 程序无法运行ADB server didn't ACK问题
- 90%的android开发者都会遇到的问题,当sjk_daemon遇见ADB server didn't ACK
- android最近老出现这样的问题: ADB server didn't ACK
- Android ADB server didn't ACK 解决方法
- android搭建环境错误 daemon not running. starting it now on port 5037 ADB server didn't ACK
- Android 程序无法运行ADB server didn't ACK问题
- Eclipse下ADB报错:Android ADB server didn't ACK,解决办法
- 当android调试遇到ADB server didn't ACK以及顽固的sjk_daemon进程
- 当android调试遇到ADB server didn't ACK以及顽固的sjk_daemon进程
- Android ADB server didn't ACK 解决方法(一张图让你解决问题)
- android搭建环境错误 daemon not running. starting it now on port 5037 ADB server didn't ACK
- android ADB server didn't ACK
- android adb被占用解决办法 ADB server didn't ACK
- 当android调试遇到ADB server didn't ACK以及顽固的sjk_daemon进程
- android搭建环境错误 daemon not running. starting it now on port 5037 ADB server didn't ACK
- Android-ADB server didn't ACK