【ADB server didn't ACK||'adb.exe start-server' failed -- run manually if necessary】问题解决办法
来源:互联网 发布:淘宝汽车装饰用品 编辑:程序博客网 时间:2024/06/03 11:55
今天在测试SQLite的时候遇到了一个问题,启动eclipse的时候说什么也连不上设备了,控制台报错如下:
[2016-4-15 7:48:27 - adb] ADB server didn't ACK[2016-4-15 7:48:27 - ddms] 'adb.exe start-server' failed -- run manually if necessary[2016-4-15 7:48:27 - adb] * failed to start daemon *、
分析原因,应该是昨天装了个360然后上面捆绑的手机助手把端口给占用了,尝试了许多方法,核心就是找占用了5037端口得进程然后杀掉。
首先执行命令;
adb nodaemon server
从报错信息得知端口为5037,然后找到都有哪些进程在使用该端口:
netstat -ano|findstr 5037
最后得到一大串内容,我把它导出到txt复制出来:
TCP 127.0.0.1:5037 0.0.0.0:0 LISTENING 4916 TCP 127.0.0.1:5037 127.0.0.1:57364 ESTABLISHED 4916 TCP 127.0.0.1:5037 127.0.0.1:57365 ESTABLISHED 4916 TCP 127.0.0.1:5037 127.0.0.1:57865 ESTABLISHED 4916 TCP 127.0.0.1:5037 127.0.0.1:58401 ESTABLISHED 4916 TCP 127.0.0.1:5037 127.0.0.1:65014 TIME_WAIT 0 TCP 127.0.0.1:5037 127.0.0.1:65020 TIME_WAIT 0 TCP 127.0.0.1:5037 127.0.0.1:65025 TIME_WAIT 0 TCP 127.0.0.1:5037 127.0.0.1:65030 TIME_WAIT 0 TCP 127.0.0.1:5037 127.0.0.1:65041 TIME_WAIT 0 TCP 127.0.0.1:5037 127.0.0.1:65046 TIME_WAIT 0 TCP 127.0.0.1:5037 127.0.0.1:65051 TIME_WAIT 0 TCP 127.0.0.1:57364 127.0.0.1:5037 ESTABLISHED 6600 TCP 127.0.0.1:57365 127.0.0.1:5037 ESTABLISHED 6600 TCP 127.0.0.1:57865 127.0.0.1:5037 ESTABLISHED 6600 TCP 127.0.0.1:58401 127.0.0.1:5037 ESTABLISHED 6600 TCP 127.0.0.1:64440 127.0.0.1:5037 TIME_WAIT 0 TCP 127.0.0.1:64445 127.0.0.1:5037 TIME_WAIT 0 TCP 127.0.0.1:64450 127.0.0.1:5037 TIME_WAIT 0 TCP 127.0.0.1:64456 127.0.0.1:5037 TIME_WAIT 0
可以看到现在占用5037的是两个进程4916和6600(当然我现在是已经修复好的了 ,所以你们出错的时候应该是其他进程,这里只是举个栗子)。
然后继续执行命令:
taskkill /pid 4916 -ftaskkill /pid 6600 -f
然后重启eclipse就可以了。当然像我这种情况,如果特别明确是那个软件的问题的话(比如360手机助手)直接去进程管理器把它杀掉也是可以的。
1 0
- 【ADB server didn't ACK||'adb.exe start-server' failed -- run manually if necessary】问题解决办法
- adb.exe,start-server' failed -- run manually if necessary
- adb.exe,start-server' failed -- run manually if necessary
- adb.exe,start-server' failed -- run manually if necessary
- adb报:adb.exe,-P,8879,start-server' failed -- run manually if necessary 端口占用
- platform-tools\adb.exe,start-server' failed -- run manually if necessary,adb启动失败,端口被占用
- ADB server didn't ACK问题解决办法
- Android ADB server didn't ACK * failed to start daemon 问题解决,杀死360MobileLoader.exe
- ADB server didn't ACK * failed to start daemon * 解决方法
- ADB server didn't ACK * failed to start daemon * 解决方案
- 解决ADB server didn't ACK * failed to start daemon *
- ADB server didn't ACK * failed to start daemon *
- ADB server didn't ACK * failed to start daemon * 解决方案
- ADB server didn't ACK * failed to start daemon * 解决方案
- ADB server didn't ACK * failed to start daemon * 解决方法
- ADB server didn't ACK * failed to start daemon * 解决方案
- ADB server didn't ACK,failed to start daemon
- ADB server didn't ACK * failed to start daemon * 解决方法
- Spark简介
- 分类与回归
- Galaxy ZOO银河星空图的识别分类
- Android Handler
- algrothm_逆序输出(charAt+for+角标)
- 【ADB server didn't ACK||'adb.exe start-server' failed -- run manually if necessary】问题解决办法
- forward与redirect的区别
- Spring MVC数据转换的总结
- algrothm_n!(循环)
- 如何远程访问MySQL server?
- Java学习-8天
- SQL*LOADER操作篇
- php实现webservice实例
- 【Qt】Variant类