This question already has an answer here:
I am a Android newbie. I guess I might be doing something stupid here. I have started the Virtual Device and I see that adbd
daemon is running from the Terminal Emulator. When I run adb devices
I get the following error:
C:\Program Files\Android\android-sdk\tools>adb devices
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
No other process is using port 5037. What am I doing wrong? Here are the packages I have installed -
1) Android SDK Tools, revision 10
2) Android SDK Platform-Tools, revision 3
3) SDK Platform Android 2.3.3, API 10, revision 1
Seems like the security program is blocking
adb.exe
, so go to the adb file path and open adb's properties, then check theRun this program as administrator
setting.As I have tried as follow by combining omni.present's method , and finally emulator works fine. firstly I stop adb.exe process in the task manager then I stop and start eclipse
I turned off the Windows Firewall and its working like magic. I am connected to the Internet through WiFi. If you are not behind a proxy and are still unable to access the Internet through a wireless link via the emulator, go to Device Manager and disable your LAN card.
This will occur normally,if abd is not able to launch properly and didn't exit when adb kill-server is executed.
So if in Windows 1. Go to Task Manager (CTRL+ALT+DEL) 2.look for adb.exe and end the process. Now restart the emulator ,should work properly.
additionally you can close and launch the development environment also (eg: Eclipse or NetBeans).
Had the same problem, it seems that my security solution was blocking adb.exe
I found there was a process call "Tadb.exe" in Windows Task Manager. I guess Tadb.exe is a similiar adb application of Tencent. Because I got an alert of "android device detected by QQ" after I install the last version of Tencent QQ2013 Beta5 (6970) yesterday.
After I killed the Tadb.exe, the original adb.exe of Android SDK works again.
You can see the detailed proecss to solve this problem here: adb cannot run, adb server is out of date