adbl连接不上 daemon not running. starting it now on port 5037 ADB server didn't ACK
2018-03-20 11:02
1486 查看
在开发的过程中adb经常断开不能连接到设备,但是重启又可以连接上,严重影响开发效率,发现是端口被占用导致,如下的方法可以解决:
1 首先要检查驱动是否有问题,可以在设备管理器中查看adb的驱动是否安装成功,确保驱动正常安装;
2 从cmd进入dos界面,执行adb kill-server和adb start-server,如何还连接不上,出现
启动adb start-server出现下面错误* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *3、执行下面命令
adb nodaemon server
出现下面错误
cannot bind 'tcp:5037'
原来adb server 端口绑定失败
3、输入下面的命令查询哪个占用了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
4、找到原因,原来是360手机助手占用了这个端口,打开任务管理器kill掉516这个进程,重新连接手机,正常
1 首先要检查驱动是否有问题,可以在设备管理器中查看adb的驱动是否安装成功,确保驱动正常安装;
2 从cmd进入dos界面,执行adb kill-server和adb start-server,如何还连接不上,出现
启动adb start-server出现下面错误* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *3、执行下面命令
adb nodaemon server
出现下面错误
cannot bind 'tcp:5037'
原来adb server 端口绑定失败
3、输入下面的命令查询哪个占用了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
4、找到原因,原来是360手机助手占用了这个端口,打开任务管理器kill掉516这个进程,重新连接手机,正常
相关文章推荐
- adbl连接不上 daemon not running. starting it now on port 5037 ADB server didn't ACK
- adbl连接不上 daemon not running. starting it now on port 5037 ADB server didn't ACK
- adbl连接不上 daemon not running. starting it now on port 5037 ADB server didn't ACK
- adbl连接不上 daemon not running. starting it now on port 5037 ADB server didn't ACK
- adbl连接不上 daemon not running. starting it now on port 5037 ADB server didn't ACK
- adbl连接不上 daemon not running. starting it now on port 5037 ADB server didn't ACK
- adbl连接不上 daemon not running. starting it now on port 5037 ADB server didn't ACK
- adb -连接不上- daemon not running. starting it now on port 5037 ADB server didn't ACK
- * daemon not running. starting it now on port 5037 *&&ADB server didn't ACK
- 安卓: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 server didn't ACK .
- daemon not running. starting it now on port 5037 ADB server didn't ACK 解决5037端口被其他进程所占用
- android搭建环境错误 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 server didn't ACK
- android搭建环境错误 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 server didn't ACK
- adb连接不上 daemon not running. starting it now on port 5037
- adb start-server * daemon not running. starting it now on port 5037 * ADB ser
- android ADB * daemon not running.starting it now on port 5037 *
- adb devices : * daemon not running. starting it now on port 5037