I believed you've checked the port number, and restart adb. But have you install proper android driver on your computer. Some universal android driver may not work on your computer, you'd better installed the driver provided by your mobile manufacturer, if you can't find the driver on manufacturer's website, consider download its software suit, it may include the driver.

In addition to @maveňツ solution.

Actually we have to kill the process using this address 0.0.0.0:0, that's why for most of the people killing adb.exe from task manager was working (In my case I was not able to see it even Task Manager).

Following the @maveňツ steps I find out that some other process was using this address. I went ahead to kill it, it gave me ACCESS DENIED as Error.

So using the tasklist|findstr **** i find out the name of the process and killed it from task manager.

There after it started working.

In my case bas_daemon and bas_helper were using this address both of which corresponds to MOBOROBO

in my case i use the command line taskkill /f /t /im bas_deamon.exe (because adb.exe was not started) and adb server is started successfully

Kill ADB from command prompt. Kill eclipse also from command prompt. Start adb server from there using [adb start-server] And start again.

In my pc, i use the command line taskkill /f /t /im wandoujia_daemon.exe (because adb.exe or bas_daemon.exe is not running in my task manager) And... the adb server is started succesfully

Look for typos in the ~/.android/adb_usb.ini file. This problem can be caused if that file gets messed up.

Please kill adb by command:

taskkill /f /im "adb.exe"

then, re-start it with command:

adb start-server

It work very fine for me :)

For Mac users, what worked for me was:

1. Open Activity Monitor (equivalent to Windows task manager)
2. Kill the adb task
3. Restart adb

Killing the process adb.exe in the TASK MANAGER (to open task manager CTRL+Shift+Esc) solves it in my case. After killing it run adb start-server or adb devices and you should be fine.

Incase if that doesn't work

We can solve this issue so easily.

1. Open command prompt, cd <platform-tools directory>
2. Run command adb kill-server
3. Open Windows Task manager and check whether adb is still running. If it is, just kill adb.exe
4. Run command adb start-server in command prompt

A way bit difficult approach

Command Prompt (cmd.exe)

netstat -aon|findstr 5037

find process id of 0.0.0.0

make sure it's adb.exe

tasklist|findstr 1980

kill this process

taskkill /f /t /im adb.exe

get ADB back to normal

for more details check it from here