Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

adb kill-server not responding?

Tags:

android

adb

In ADB, I am facing an error when I am trying to print the version with

padmakumar@padmakumar-desktop:~$ adb version
Android Debug Bridge version 1.0.29

but its showing below error

padmakumar@padmakumar-desktop:~$ adb devices
error: protocol fault (no status)

NOTE: adb kill-server is not working i.e it's not responding.

and in my Eclipse console I am getting this error:

Android Launch!
[2012-01-09 20:31:28 - Shopping List] The connection to adb is down, and a severe error has occured.
[2012-01-09 20:31:28 - Shopping List] You must restart adb and Eclipse.
[2012-01-09 20:31:28 - Shopping List] Please ensure that adb is correctly located at '/home/padmakumar/android-sdk/platform-tools/adb' and can be executed.
like image 753
Padma Kumar Avatar asked Jan 09 '12 15:01

Padma Kumar


People also ask

Do adb kill-server?

It kills the running adb server on your Mac. To use it, open the Terminal and move to the location where adb is located by using the cd command. Once you are inside the correct directory, type the command adb kill-server to kill a server if it is running.

How do I shut down adb server?

To stop the adb server, use the adb kill-server command. You can then restart the server by issuing any other adb command.

Why adb shell not working?

Make sure USB debugging is enabled and USB is physically plugged in. Make sure everything is ok with the ADB drivers, double-check the device manager. Check if the device appears in "adb devices", make sure its authorized on the device. Try actual adb shell and other relevant adb stuff.


2 Answers

I also came across the same error when I was trying to install one app in emulator. You need not restart PC to overcome this. Just kill the server. if 'adb kill-server' is also not working, kill the process (adb.exe) through task manager. There you go!!

like image 142
hashcoder Avatar answered Nov 15 '22 19:11

hashcoder


If zombie adb process is not the issue i.e. there's no adb.exe in the task-manager list, the problem is usually adb ports e.g. 5555, 5554, 5037 etc., being taken by other applications.

Solutions:

  1. On all Windows: find the process taking one of those ports using netstat -bn and kill it from task-manager Ctrl+Shift+Esc is the shortcut.

  2. On Windows 7 and 8: there's this new tool called Resource Monitor. It'll also allow you to find out the blocked port and blocking process under the network tab.

  3. On Linux: the similar is done with netstat -pn. Feel free to use your grep foo as needed and kill the blocking process with kill or pkill.

  4. Change Default ADB Port: Apparently default ADB port can be changed as described here by setting up an environmental variable before launching ADB. Give it shot. It'll allow more flexibility if you don't want to kill the blocking processes.

like image 32
gsbabil Avatar answered Nov 15 '22 18:11

gsbabil