ADB server didn't ACK * failed to start daemon *
来源:互联网 发布:英国普利茅斯大学 知乎 编辑:程序博客网 时间:2024/06/05 06:00
android adb启动失败问题 adb server is out of date. killing… ADB server didn’t ACK * failed to start daemon *
错误如下–》
adb server is out of date. killing…
ADB server didn’t ACK
* failed to start daemon *
原因是adb的端口号被占用了。
解决办法:
1.定位到jdk bin目录下,输入命令adb nodaemon server
很显然,我们的adb端口号是5037,但是绑定失败,肯定是别的进程占用他的端口号了,此时我们需要做的就是找到那个进程病kill it。
2.输入命令netstat -ano | findstr “5037”
喔,看到127.0.0.1:5037我们就高兴了,原来5037这个端口号还真是被占用了,当然,我们会发现,是被PID为9056的进程所占用的,接下来我们就是消灭这个进程的时候了。
3.打开”任务管理器“,接下来一步步点击 进程–>查看–>选择列 看到PID(进程标识符)把它前面的对号勾上。点击“确定”按钮返回“任务管理器”主界面
4.此时我们根据PID区查找之前的9056进程,点击右键然后“结束进程”就ok了,再启动adb你会看到此时就ok了。
最后一步:重启eclipse/studio
阅读全文
0 0
- 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 * 解决方法
- 关于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 * 解决方案
- Android ADB server didn't ACK * failed to start daemon
- ADB server didn't ACK, failed to start daemon
- Android ADB server didn't ACK * failed to start daemon *
- 文章标题
- 从概念到案例:初学者须知的十大机器学习算法
- 解密ln( )函数
- sqlite C++ 的sqlite3_get_table函数使用
- 网易2017秋招编程题:计算糖果 [python]
- ADB server didn't ACK * failed to start daemon *
- 自总结Linux命令
- qduoj 196 李院长发红包
- 3.3 决策树DecisionTrees
- shell script 实现累加计算
- Windows、linux系统使用命令提示符功能(cmd,command,又称命令行)详细图文教程和手册下载
- 7-4 求幂级数展开的部分和(20 分)
- mongodb对于时间的存储问题
- Python的基础知识2