ADB server did not confirm

Question

I could never run the Android application ever on my laptop. Eclipse constantly gives the same error that "ADB server did not confirm"

I tried everything, restarted adb from the ddms view, from the command line (kill-server, start-server), from the task manager and restarted eclipse. When I manage to start the adb server and re-open eclipse, as soon as I launch the Android application, the same error will come to the console; ADB server did not respond.

Could you give an idea other than restarting adb

Answer 1

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

---

Enable if this does not work

We can solve this problem so easily.

• Open a command prompt, cd <platform-tools directory>
• Adb start command adb kill-server
• Open Windows Task Manager and check if adb working. If so, just kill adb.exe
• Run adb start-server command at command prompt

---

Hard beat bit approach

Command line (cmd.exe)

 netstat -aon|findstr 5037 

find process id 0.0.0.0

make sure adb.exe

 tasklist|findstr 1980 

kill this process

 taskkill /f /t /im adb.exe 

return ADB to normal operation

See here for more details.

Answer 2

For Mac users, what worked for me was:

• Open Activity Monitor (equivalent to Windows Task Manager)
• Kill adb task
• Restart adb

Answer 3

Kill the adb command with the command:

 taskkill /f /im "adb.exe" 

then re-run it with the command:

 adb start-server 

This works great for me :)

Answer 4

Look for typos in the file ~ / .android / adb_usb.ini. This problem may be caused if this file is confused.

Answer 5

On my computer, I use the command line taskkill / f / t / im wandoujia_daemon.exe (because adb.exe or bas_daemon.exe does not work in my task manager) And ... the adb server starts successfully

Answer 6

In addition to the @ maveň ň solution .

In fact, we need to kill the process using this address 0.0.0.0:0 , so for most people killing adb.exe from the task manager, it worked (in my case, I could not even see it in the task manager).

Following the steps of @ mave ツ , I will find out that some other process used this address. I went to kill him, he gave me ACCESS DENIED as Error .

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

After that, he began to work.

In my case, bas_daemon and bas_helper used this address, both of which correspond to MOBOROBO

Answer 7

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

Answer 8

Kill ADB from the command line. Kill eclipse also from the command line. Start the adb server from here using [ adb start-server ] and start again.

Answer 9

I figured you checked the port number and restarted adb. But you have your own Android driver on your computer. Some universal Android driver may not work on your computer, you better install the driver provided by the manufacturer of your mobile phone, if you cannot find the driver on the manufacturer’s website, think about downloading its software, it may include a driver .