提示ADB server didn’t ACK 占用端口 解决 (纯图,PID)
2013-01-31 23:27
495 查看
如果出现adb端口被占用,可以通过netstat -ano|findstr "5037"查看端口的使用情况(我这里adb的使用端口为5037),
结果如图,最后1列是PID
我这里是5352,被占用的情况下去任务管理器中杀掉这个进程即可)
ps:显示PID的方法如下
按照PID排序,结束对应的进程
最后,重启Eclipse(软件内重启 file / restart),CMD输入adb start-server
,成功。
相关文章推荐
- 提示ADB server didn’t ACK 占用端口 解决 (纯图,PID)
- daemon not running. starting it now on port 5037 ADB server didn't ACK 解决5037端口被其他进程所占用
- [积累]ADB server didn't ACK 解决方法/端口占用查看
- 解决Adb Server ACK error的问题(端口占用)
- ADB server didn't ACK 默认的ADB端口被占用之解决办法
- 解决编译器“The connection to adb is down, and a severe error has occured.ADB server didn't ACK”提示错误方法
- Eclipse下调试 提示ADB server didn’t ACK解决
- ADB server didn't ACK 进程占用adb '5073' 端口
- 提示ADB server didn't ACK错误的解决方法
- 输入指令adb remount出现ADB server didn't ACK提示的解决方式
- Eclipse下调试 提示ADB server didn’t ACK解决
- 解决Adb Server ACK error的问题(端口占用)
- 【Android】解决 adb server didn't ACK问题
- 如何解决adb命令报错 "ADB server didn't ACK"问题
- android 之'ADB server didn't ACK'的解决办法
- ADB server didn’t ACK解决办法
- ADB server didn't ACK 解决方法
- Android Eclipse 重启adb and Eclipse ADB server didn't ACK问题解决方案
- 解决提示ADB server didn't ACK的错误,无法启动ADB服务
- Android--'ADB server didn't ACK'的解决办法