android搭建環境錯誤 daemon not running. starting it now on port 5037 ADB server didn't ACK

本文轉載自查看原文 2013-11-01 09:28 23801 Android

1、輸入cmd進入dos界面，進入android-sdk-windows\platform-tools目錄，執行下面命令
啟動adb start-server
出現下面錯誤
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *

2、執行下面命令
adb nodaemon server
出現下面錯誤
cannot bind 'tcp:5037'
原來adb server 端口綁定失敗

3、輸入下面的命令查詢哪個占用了5037端口
netstat -ano | findstr "5037"
出現下面信息
TCP 127.0.0.1:5037 0.0.0.0:0 LISTENING 1616

4、打開任務管理器kill掉1616這個進程，到此解決

5、再次運行下面命令，為空則可以
netstat -ano | findstr "5037"

免責聲明！

本站轉載的文章為個人學習借鑒使用，本站對版權不負任何法律責任。如果侵犯了您的隱私權益，請聯系本站郵箱yoyou2525@163.com刪除。

猜您在找 android adb命令* daemon not running.starting it now on port 5037 * 問題解決 * daemon not running; starting now at tcp:5037 android adb啟動失敗問題 adb server is out of date. killing... ADB server didn't ACK * failed to start daemon * ADB server didn't ACK完美解決 Android 解決adb server is out of date. killing... ADB server didn't ACK * failed to star 'ADB server didn't ACK'的解決辦法 adb server is out of date. killing... ADB server didn't ACK解決方法【雜症】一個豌豆莢引發的血案——關於ADB server didn't ACK的問題 appium---[ADB] Killing adb server on port 5037報錯 zookeeper錯誤Error contacting service. It is probably not running.