Adb kill-server not responding?

Question

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.

This question is similar as of http://stackoverflow.com/questions/4072706/the-connection-to-adb-is-down-and-a-severe-error-has-occured — Sharda Singh, Apr 03 '13 at 18:06

score 16 · Accepted Answer · answered Jun 01 '12 at 09:01

16

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!!

answered Jun 01 '12 at 09:01

hashcoder

498
7
19

4

restarting ur PC is a bad option. – Sharda Singh Apr 03 '13 at 18:06
What is adb restarts again ? Then restart solves problem – Vivek Warde Nov 15 '15 at 09:12
2

after investigating for a long time, finally i found out that adb daemon keep restarting. and it is because my chrome have enabled android debugger. In chrome address bar, open: chrome://inspect#devices, then uncheck "Discover usb devices" – James Tan Jul 19 '21 at 13:30

score 7 · Answer 2 · edited May 23 '17 at 11:58

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:

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.
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.
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.
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.

android studio adb wifi plugin that I installed was using the port, thus making the adb kill-server non responsive, exit android studio and then did kill server worked on linux — Ismail Iqbal, Jun 09 '18 at 05:23
thanks. this resolved the issue. For me, the port 5037 was used up by java. adb commands worked for me once java.exe was terminated from task manager — Arun Thomas, Jan 22 '19 at 08:09

score 6 · Answer 3 · edited Sep 29 '12 at 12:06

6

Task Manager -> Process -> adb.exe -> End process

That worked for me.

edited Sep 29 '12 at 12:06

Tiago Almeida

14,081
3
67
82

answered Sep 12 '12 at 04:24

JK_S

145
1
5

Thanks for your answer. but I am using Linux not Windows Pc – Padma Kumar Sep 12 '12 at 08:16
Hi, true the answer is for Windows, I think for Linux you can find the process id of adb and use kill command...hope it helps – JK_S Sep 13 '12 at 04:10
it wont work.. as when u are connected with the device it will automatically restarts the adb server again. so it is useless – Sharda Singh Apr 03 '13 at 18:07
If you are using ubuntu you can go to System Monitor and kill ADB Process – scienticious Oct 19 '20 at 04:41

score 2 · Answer 4 · answered Feb 25 '14 at 04:25

2

navigate to adb.exe folder
shift + right click inside the folder
start commandline from here
unplug any android device connected to your PC
type "adb.exe wait-for-device"; press Enter
connect your device; wait for commandline to finish
done

answered Feb 25 '14 at 04:25

apen

672
4
14

score 2 · Answer 5 · edited Apr 12 '19 at 10:03

2

adb kill-server did not work on my Linux computer

First, I used ps -ef | grep adb and killed all adb deamonswhich did not solve the problem. Then I usedps -ef | grep javaand saw a process that was blocking theadb`.

Upon killing that process, adb worked perfectly. Maybe this process can be helpful for someone.

edited Apr 12 '19 at 10:03

Sanip

1,772
1
14
29

answered Apr 12 '19 at 08:55

Isuru Kariyawasam

126
2

This does not provide an answer to the question. You can [search for similar questions](https://stackoverflow.com/search), or refer to the related and linked questions on the right-hand side of the page to find an answer. If you have a related but different question, [ask a new question](https://stackoverflow.com/questions/ask), and include a link to this one to help provide context. See: [Ask questions, get answers, no distractions](https://stackoverflow.com/tour) – Shanteshwar Inde Apr 12 '19 at 09:18

neel · Answer 6 · 2014-04-01T00:23:30.313

1

On trying to kill multiple adb.exe processes from windows Task Mgr it said "Access is denied". On Windows 7, Resource Monitor allows those adb.exe processes to be killed.

edited Apr 01 '14 at 00:23

answered Mar 31 '14 at 11:03

neel

184
5

score 1 · Answer 7 · answered Nov 05 '14 at 04:54

1

install following packages

sudo apt-get install lib32z1 lib32z1-dev lib32stdc++6

if you are using Genymotion then set path of Android SDK in its settings.

ref :http://www.intellicode.in/adb-not-responding-wait-more-or-kill-adb-or-restart/

answered Nov 05 '14 at 04:54

Kirtan

1,782
1
13
35

score 1 · Answer 8 · answered Mar 18 '19 at 04:05

Install again ADB.EXE in your SDK path like Steps :

1)Close Your Android Studio

2)Fine path in Your Computer->[drive][your SDK path]\Sdk\platform-tools

3)Replace this path at adb.exe File or Download again if not updated adb.exe File.

4)Click on adb.exe if the command prompt is open and details see and then close automatically then its work. OR if any error occurred or not start adb-server again replace this file .

5)Now successfully run your adb-server open android studio and connect your device after Developer Option ON .

score 0 · Answer 9 · answered Apr 30 '13 at 14:06

If using the "kill-server" parameter doesn't work you will have to kill the process itself.

In case you use GNU/Linux you have to use the command "ps aux|grep adb" to find the pid of the adb proccess, or directly with "pidof adb" and then "kill PID" where PID is the pid number of the adb process. This should also work with Macintosh and other Unixes (although the parameters of the "ps" command may be different)

In Windows just open the task manager to and kill the adb entry in the proccesses table

score 0 · Answer 10 · answered Dec 29 '22 at 07:41

From James Tan's answer:

After investigating for a long time, finally i found out that adb daemon keep restarting. and it is because my chrome have enabled android debugger. In chrome address bar, open: chrome://inspect#devices, then uncheck Discover usb devices.

Open Power Shell as administrator
cd C:\Users\PC01\AppData\Local\Android\Sdk\platform-tools
./adb kill-server
./adb start-server

Adb kill-server not responding?

10 Answers10

Linked