'ADB server didn't ACK'的解决办法
16lz
2021-01-24
1:今天调试android的时候发现一个诡异的问题
[html] view plaincopy
C:\Users\xxxx>adb start-server
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
adb 不管执行 shell devices 还是logcat 都会报错
[html] view plaincopy
adb server is out of date. killing...
究其源就是adb server没启动
到stackoverflow上查了一下 经过分析整理如下:
[html] view plaincopy
C:\Users\xxxx>adb nodaemon server
cannot bind 'tcp:5037'
原来adb server 端口绑定失败
继续查看到底是哪个端口给占用了
[html] view plaincopy
C:\Users\xxxxxx>netstat -ano | findstr "5037"
TCP 127.0.0.1:5037 0.0.0.0:0 LISTENING 4236
TCP 127.0.0.1:5037 127.0.0.1:49422 ESTABLISHED 4236
TCP 127.0.0.1:49422 127.0.0.1:5037 ESTABLISHED 3840
打开任务管理器kill掉4236 这个进程。ok
至此问题解决了
-------------------------------------------------
以下是我的操作记录:
D:\TDDOWNLOAD\adt-bundle-windows-x86-20130514\sdk\platform-tools>adb kill-serve
* server not running *
D:\TDDOWNLOAD\adt-bundle-windows-x86-20130514\sdk\platform-tools>adb start-serv
r
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
D:\TDDOWNLOAD\adt-bundle-windows-x86-20130514\sdk\platform-tools>adb nodaemon s
rver
cannot bind 'tcp:5037'
D:\TDDOWNLOAD\adt-bundle-windows-x86-20130514\sdk\platform-tools>netstat -ano |
findstr "5037"
TCP 127.0.0.1:5037 0.0.0.0:0 LISTENING 2592
TCP 127.0.0.1:5037 127.0.0.1:2051 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:2052 TIME_WAIT 0
进入任务管理器杀进程
再执行确认5037进程是否存在
D:\TDDOWNLOAD\adt-bundle-windows-x86-20130514\sdk\platform-tools>netstat -ano |
findstr "5037"
更多相关文章
- Android中的系统广播集合
- Android(安卓)跨进程通信(二)
- Android(安卓)Studio 1.3.0 以上gradle proxy代理设置异常
- 锦囊篇|一文摸懂SharedPreferences和MMKV(一)
- Android(安卓)有关于* daemon not running.starting it now on p
- Android(安卓)8.0 添加一个可以让phone进程访问的hal service需
- Android(安卓)4.2.2 ScreenLock上Music远程播放控制界面的创建流
- [置顶] Android(安卓)IPC 通讯机制源码分析【中】
- 理解杀进程的实现原理