ADB is not starting (no error message)
Try setting the environment variable ADB_TRACE before starting the ADB server to see if it can provide any clues:
C:\Android\android-sdk\platform-tools>set ADB_TRACE=1
C:\Android\android-sdk\platform-tools>adb start-server
Please include the output in your question.
At C:\Documents and Settings\userfoo.android there are some android-related files which uninstaller doesn't delete. Although the most of them are used by AVD, and not by ADB, I recommend you to delete it before any "new fresh" install.
Please check your user rights and privileges, and the user "system" privileges, because of in some companies, they are cutted-off to prevent from virus or automated attacks.
To solve problem in windows machine, try the following:
Problem
ADB stop connecting attached Android device
demon is not running and demon is running on port 5037
Solution
first list all processes which are running on port 5037
command: netstat -ano | find "5037"
Output for above command:
TCP 127.0.0.1:52935 127.0.0.1:5037 SYN_SENT 31016
TCP 127.0.0.1:52936 127.0.0.1:5037 SYN_SENT 31016
Kill processes which are running on port 5037 using the following command: taskkill /F /PID 31016
Then, restart the adb server adb kill-server adb start-server
Expected output:
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
Typing adb devices will give you list of devices connected to the adb server
This solution worked for me:
=> Check if adb is running in Task Manager, then kill it. Now Then try to restart it again via following method:
1) Shift + Right click in ...\android-sdk\platform-tools folder and select Open command window here
2) Use these commands:
adb kill-server then adb start-server
If this method didn't work and you see something like this in Command window Killing adb...
Then apply following steps:
3) Close eclipse
4) Now kill javaw.exe Java(TM) Platform SE binary in Task manager And follow step 1 & 2 again.
It will surely work. :)