adb devices : * daemon not running. starting it now on port 5037
来源:互联网 发布:短信验证码源码 编辑:程序博客网 时间:2024/05/20 23:30
1. 执行adb kill-server和adb start-server,如何出现下面错误
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
2.查询哪个占用了5037端口
netstat -ano | findstr "5037"
出现下面信息
TCP 127.0.0.1:2568 127.0.0.1:5037 SYN_SENT 516
TCP 127.0.0.1:2569 127.0.0.1:5037 SYN_SENT 516
3. 打开任务管理器kill掉516这个进程,OK
0 0
- adb devices : * daemon not running. starting it now on port 5037
- adb start-server * daemon not running. starting it now on port 5037 * ADB ser
- 解决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 *
- * 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 *
- * 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
- * daemon not running. starting it now on port 5037 *
- * 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错误
- android ADB * daemon not running.starting it now on port 5037 *
- 安卓: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
- adb连接不上 daemon not running. starting it now on port 5037
- 开始使用Android Sutdio(二)配置Android Studio
- 调用Runtime.exec()的一些陷阱
- 【Spark】Spark应用执行机制
- 每天一个linux命令(31): /etc/group文件详解
- android一键分享功能不使用任何第三方sdk
- adb devices : * daemon not running. starting it now on port 5037
- Objective-C Associated Objects 的实现原理
- IntelliJ IDEA 快捷健与eclipse对比
- 动态寻路
- NDK 编译armebai-v7a的非4字节对齐crash Fatal signal 7 (SIGSEGV) 错误解决
- unity Json
- ubuntu安装编译 webrtc
- webview中html页面点击文本框整个页面放大
- BZOJ 3172 [Tjoi2013]单词 AC自动机(fail树)