ADB not responding. You can wait more, or kill "adb.exe" ... windows 8

Question

When I try to test my Android application with an android emulator as always I now suddenly get an error message. I'm working with Windows 8. So far I tried the following things which unfortunately could not solve the problem:

reinstalling eclipse with android adt
reinstalling java
installing "android studios" first solved the problem but after one day mysteriously also here adb, stopped working with the error message given in the title " ADB not responding ...

furthermore I unsuccessfully tried out some advice from Mr. Google:

Stopping adb.exe via task-manager and restarting eclipse / android studios
"adb kill-server" then "start-server" via command prompt
setting the path to adb.exe as an environment variable
switching off any antivirus or firewall
starting the IDEs as an administrator
updating the IDEs

The only thing I can remember doing which may have destroyed adb on my computer for all times: I connected my motorola smartphone to my laptop and installed the motorola usb drivers but as I said the adb also won't work with the emulator.

Any help would be kindly appreciated. The issue bothers me for more than an entire day now. Maybe someone had similar problems on Windows 8 ?

You could go and try to delete the motorola driver if you've got the idea that is the one messing things up — Stefan de Bruijn, Jul 25 '13 at 07:27
The only thing I found was an "ADB Interface" in the windows device manager. I deleted it. No effect. — mcExchange, Jul 25 '13 at 08:23
As I said: I already got the problem when using Eclipse with Android ADT before I installed any motorola drivers. Seems more that anyhow the IDE cannot really find the adb.exe, altough this normally works after a standard installation. But neither in "Eclipse" nor in "Android Studios" I can find any ADB settings in order to repair / change it. — mcExchange, Jul 25 '13 at 08:30

Michał Jurczuk · Answer 1 · 2015-01-04T14:09:57.270

16

On OSX helped:

Close Android Studio
Kill all processess using 5037 port

sudo lsof -i |grep 5037

sudo kill PID_NUMBER
Run adb devices from console

adb devices

edited Jan 04 '15 at 14:09

answered Sep 09 '14 at 09:40

Michał Jurczuk

3,468
4
28
53

+1. Nice. This is the only thing that worked for me. I even tried OS reset. – Chad Bingham Oct 11 '14 at 22:08
Worked for me. Just another tip: if the Android SDK is not on the PATH variable, you can find adb on /platform-tools – gibertoni Nov 10 '14 at 17:21
Help me under Windows 7 too - didn't even have to close Android Studio. I just killed the adb process and ran "adb devices". Thanks. – ElDoRado1239 Feb 08 '15 at 06:46
This worked on Mac. I was trying to run with Xamarin but was getting errors. – LearneriOS Oct 31 '16 at 20:09

score 7 · Accepted Answer · answered Jul 27 '13 at 13:17

7

Meanwhile the emulator is working again. I cannot definetly say what solved the problem. What It could be a combination of two things:

Deleting the hidden ".android" folder under C:\Users... (Probably there was some malfunctioning automatically created code)
Deleting and recreating the Path variable to the folder with adb.exe ( ...\sdk\platform-tools\;)

Finally it could be a Windows 8 issue which I don't understand.

answered Jul 27 '13 at 13:17

mcExchange

4,998
12
43
81

I found issues without making changes to both a windows 8 and windows 7 machine. Definitely something with Windows. I wonder if anyone has tried on MAC or Linux? – Shane Feb 11 '14 at 23:26
Not related to Windows, this happens in Ubuntu 13.10 as of March 2014, for my whole team... – So Many Goblins Mar 06 '14 at 11:20
I have this issue with linux – Eenvincible Mar 15 '14 at 19:34
3

Deleting de .android folder worked for me. Thank you. – Coneone May 27 '14 at 20:34

Hanju Kim · Answer 3 · 2014-08-27T12:02:01.543

5

Try this,

Open a command prompt with administration permission and type

netsh interface tcp set global autotuninglevel=disabled

This worked for me

Edit: Windows only

edited Aug 27 '14 at 12:02

answered Oct 29 '13 at 11:15

Hanju Kim

61
1
4

score 3 · Answer 4 · answered Jul 25 '13 at 07:33

3

Kill the adb.exe with a command prompt. Open a command prompt were your adb.exe is located and type adb kill-server

answered Jul 25 '13 at 07:33

Billy Korsen

524
2
6
18

4

I did that too. No effect. – mcExchange Jul 25 '13 at 08:22

fantouch · Answer 5 · 2016-04-12T09:55:44.057

2

Maybe HTTP Proxy blocked the localhost 127.0.0.1:5037
If you have config the HTTP Proxy, make sure to exclude the localhost like picture below

Also, port can also be blocked by the firewall and anti-virus firewall, please notice as well.

enter image description here

edited Apr 12 '16 at 09:55

answered Sep 29 '14 at 18:27

fantouch

1,029
12
10

score 1 · Answer 6 · edited Oct 20 '13 at 01:57

1

Try this,

at the prompt try adb kill-server
Start one of your AVDs
at the prompt try adb root

The prompt should say adbd is already running as root.

That should fix it.

edited Oct 20 '13 at 01:57

Josha Inglis

1,008
11
21

answered Oct 20 '13 at 01:31

Math-geek

11
2

Thanks, worked for me. Killing server and starting it didn't but `adb root` did the trick. – Dion Segijn Aug 30 '14 at 13:51

score 1 · Answer 7 · answered Apr 26 '14 at 15:29

1

In case it helps anyone else, for me the problem was related with the USB hub that the tablet was plugged into on the computer (unplugging the webcam which was in use fixed it).

answered Apr 26 '14 at 15:29

user3441246

33
2

score 1 · Answer 8 · answered Apr 24 '15 at 16:04

1

I got the same error. Don't worry. I have an solution. Go to Task Manager. Kill the process called adb.exe. You will find 2 or 3 processes. Kill all of them. You are done. It will work.

answered Apr 24 '15 at 16:04

Prit Ladani

11
1

score 1 · Answer 9 · edited May 23 '17 at 10:30

1

I have the same problems. Verify port 5037 is free and ports 5555 to 5585 are available and never used by another process.

"ADB server sets up connections to all running emulator/device instances. It locates emulator/device instances by scanning odd-numbered ports in the range 5555 to 5585"

FROM: http://developer.android.com/tools/help/adb.html

To find out which process is listening on a port on Windows yo can use:

C:> netstat -an -o

FROM: How can you find out which process is listening on a port on Windows?

edited May 23 '17 at 10:30

Community

1
1

answered Jul 02 '15 at 13:55

erivas

11
1
2

svchost is used port 5037. I killed so I am able to run adb devices. Thanks. – Günay Gültekin Oct 30 '16 at 18:04

score 1 · Answer 10 · answered Apr 26 '16 at 16:04

1

I had the same problem, here is my simple fix:

-Go to task manager in windows, look for adb.exe, and kill it

-Go to command prompt, and tap adb devices ==> it will automaticaly start adb daemon

answered Apr 26 '16 at 16:04

Nourdine Alouane

763
11
19

score 0 · Answer 11 · answered Apr 14 '14 at 15:32

0

I finally just restarted the computer, and that solved the issue for me.

answered Apr 14 '14 at 15:32

coder

10,172
17
67
122

score 0 · Answer 12 · answered Jun 27 '14 at 06:28

0

Uninstall HTC Sync. Or disable it somehow.

answered Jun 27 '14 at 06:28

Ozan Atmar

260
1
2
10

score 0 · Answer 13 · edited Aug 22 '14 at 17:59

0

Try to open adb from command prompt from directory location as <sdk>\platform-tools,
If adb file is missing try to re-install Android SDK with latest version, And try to run again..

I think issues will solved, by this procedure.

edited Aug 22 '14 at 17:59

Isaac G Sivaa

1,221
4
14
32

answered Aug 22 '14 at 17:48

Chai_Pot

1

score 0 · Answer 14 · answered Sep 25 '14 at 22:54

I saw this on a Mac OS X.

I shut down Android Studio and ran adb get-state in the terminal. When I started Android Studio back up, the warning had gone away.

BTW, I did just try restarting Android Studio without any luck. I am sure a restart of OS would have fixed it too.

score 0 · Answer 15 · answered Nov 20 '14 at 08:25

0

The same thing with the Asus Sync utility (with the both our Transformer's 700 and 701). I think there is a USB-port conflict between ABD driver and Sync utility.

Exit from Sync utility resolve the problem.

answered Nov 20 '14 at 08:25

A. Petrov

550
6
14

score 0 · Answer 16 · answered Feb 03 '15 at 02:10

Looks like this could be caused by a bunch of different issues. This just happened to me because I had my android phone device plugged in for USB debugging, then after a few hours (and multiple android studio/phpstorm restarts) I had to do unplug the device manually. Things started working again after unplugging.

score 0 · Answer 17 · answered Jul 03 '15 at 04:21

I have faced this problem few days ago. When I opened my task manager it showing me two adb runnig. It may be because of I am using mobogenie for connecting my android phone for debugging application. This problem is because of moboginie and adt port conflict. then I have followed following procedure to sort out this issue.

!) close eclipse 2) Go to task manager and kill all adb processes. 3) Now go to platform-tools in android sdk 4)press shift+right click mouse and select "open command window here" option 5) type

adb kill-server adb start-server

6)if server sucessfully started then start eclipse and then connect your phone (Remember dont connect your phone before starting eclipse)

score 0 · Answer 18 · answered Dec 04 '15 at 06:36

0

Following works for me every time: go to File->Invalidate Caches/Restart select Invalidate and Restart

And, You are good to go.

answered Dec 04 '15 at 06:36

Dhawan Gupta

1
1
1
2

ADB not responding. You can wait more, or kill "adb.exe" ... windows 8

18 Answers18

Linked