Develop Reference

ADB not responding in android studio

The dialog has 3 options: Wait more, Restart and Cancel. But all of them gives me the same result, i.e. a message Waiting for ADB appears and I can't do anything with Android Studio.
I have to kill the program using windows task manager! I'm using windows 7.
I tried some steps like rebuild project and clean project but it didn't work correctly....I also try kill the adb.exe in Task manager ..but it not show in the Task manager sometimes.
Can anyone help me on this?
the main problem is adb.exe not found in Task manager..

Open command prompt and type in the below command
adb kill-server
then start server using the below command
adb start-server
This could remove any potential "waiting for adb" message if your adb server is not started correctly
Note: you may want to have adb in path variable

ADB not responding. If you'd like to retry, then please manually kill "adb.exe" and click 'Restart'

I am a newbie and want to learn android. However, I face difficulties during installation of android studio.
I have installed android studio correctly but when I want to run a Hello World in my android device, it shows
ADB not responding. If you'd like to retry, then please manually kill
"adb.exe" and click 'Restart'
I have searched it from the Internet but it still cannot solve the problem, what can I do to solve it?

I've found the answer to this. This had been plaguing me for days, but so happy to have this fixed.
When I go to task manager the process adb.exe was constantly restarting itself. This is what was causing the issue (for me).
Go to Tools -> Android -> Enable ADB entegration. Untick this. Make sure its status appears as unticked. Now go to task manager and killed the process adb.exe, it will not restart itself this time. Now click run, hey presto, ADB runs. Whoop de doo.

Here is what worked for me on Ubuntu:
I simply removed the file /tmp/adb.log
sudo rm /tmp/adb.log
Hope it helped.
Cheers.

You should first try stopping adb and then restarting it.
Use this command:
adb kill-server
followed by:
adb start-server
On Mac OSX: If the adb process needs to be killed, you can use ps to show all processes with the following command, (pipe through grep to find it easier)
ps aux | grep adb
You can kill it with the following command, using the process id of adb from the previous ps command.
kill -9 <process id>

you need platform-tools_r23.0.1-linux.zip . Url for it from google's repository is:
https://dl-ssl.google.com/android/repository/platform-tools_r23.0.1-linux.zip
Go into your android-sdk-linux directory, I deleted the platform-tools directory (but I think that's unnecessary) and unzip'ed the platform-tools zip there. The SDK updater correctly shows 23.0.1 is installed at this point.
all will work properly
one can find detailed discussion about this issue here

I had the problem because the project was not built and showed an error as follows
Error:Error: Cannot run program "/path/to/Android/Sdk/build-tools/21.1.2/aapt": error=2, No such file or directory
I solved the problem by running those commands
sudo apt-get install lib32stdc++6
sudo apt-get install lib32z1
Ubuntu can't run the aapt on 64 bit before installing this packages
Thanks to https://stackoverflow.com/a/27734148/2119981

I solve the problem.Open cmd and input netstat -aon|findstr 5037 .if there is a process uses the port.You should kill it.You can get the pid and find the process in Task Manager.

I Battled with this problem for a couple of days (nearly drove me nuts) and every solution I found failed to help me. Till I tried this:
(On Mac)
I uninstalled Android Studio (moved it from Applications to Trash).
Restarted my Mac.
Reinstalled Android Studio (moved it back from Trash to Applications).
And everything was back to normal.

I didn't find adb.exe in the task manager so i did the following and it worked fine after that
I closed the emulator and removed my phone.
restart the windows.
connect the usb device and then i run the application.

Go to Tools -> Android -> Enable ADB entegration
untick it and press run ( you will get an error) now re-tick it and press run and it will works.

Open "Android Monitor" window at the bottom of Android Studio, there will be some error info of the problem.
And my problem hint is "no permission to access /tmp/adb.1001.log".
Just remove the file, the problem will been resolved.

ADB server can't start android

I have installed adt bundle eclipse. However, I can't seems to run the AVD. I have the problem of
ADB server didn't ACK
failed to start daemon
I have search on how to solve it, I've read to type adb kill-server and adb start-server. when I typed that, it says
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *"

Please follow below steps:-
Go to run
open command prompt
get into your platform-tools under android sdk.
now type command: adb kill-server
then upon success type: adb start-server
Thats'it.
Let me know if you still facing any issue..

I had this exact problem on my Vista x64 system. I solved it by doing the following:
Ctrl-Alt-Del, start Task Manager, under Processes tab, check for "shuame_helper.exe". It was there from running RootGenius. I clicked End Process, then went back to the command prompt and entered adb start-server and it worked!

Try below step from DDMS in eclipse :

So I had the same problem and failed in all the same ways as above:
adb kill-server
followed by
adb start-server
still resulted in the ADB server didn't ACK error.
The other common suggestion of using the task manager to kill the process also
failed as it seemed that something restarted adb automatically? It would disappear for a second, then there were two adb processes ,then there was one again.
Exasperated.
I restarted Windows in safe mode.
This ensured that adb wasn't started.
Shut down and restart normally. Problem solved.
Just for good measure, I also updated eclipse and android at this point, but I think that the safe mode restart fixed it.
Give it a try when all else fails.

When this happens I open Activity Monitor (on mac) or Task Manager (on windows) and look for the ADB process and force close it (sometimes there are more than one, close those to) and then press the Run button again in Android Studio or Eclipse.

1)Open task manager first
2)close any instance of adb.exe(end task it)
3)open command prompt
4) type adb start-server(you may have to execute it twice)
5) try to run now.

I had this problem using the latest ADT, SDK and Eclipse on Windows 7. I had an old ASUS TF101 and an HTC HD connected with their respective docking software. When I looked in processor tab of the Windows task manager I could see two instances of the adb.exe, one loaded and another one looking like it is trying to load.
I killed the PC connecting software (process in task manager) for the ASUS, the HTC Sync wasn't running. There is now one adb.exe running and both devices are recognised in Eclipse and in the command prompt (adb devices). You may need to restart Eclipse.

The connection to adb is down, and a severe error has occured while running Android Project

[2014-04-02 12:30:28 - EsrtDummyproject1] The connection to adb is down, and a severe error has occured.
[2014-04-02 12:30:28 - EsrtDummyproject1] You must restart adb and Eclipse.
[2014-04-02 12:30:28 - EsrtDummyproject1] Please ensure that adb is correctly located at 'C:\Tulika\SOFTWARES\adt-bundle-windows-x86-20130522\sdk\platform-tools\adb.
I tried all the ways to solve it.
I have killed the adb.exe process from Task manager.
Restarted eclipse.
But still facing with the same issue.
Can anyone help resolving it ?

Try below steps:
Close the Eclipse if running
Go to the Android SDK platform-tools directory in Command Prompt
type adb kill-server
then type adb start-server
No error message is thrown while starting ADB server, then adb is started successfully.
Now you can start Eclipse again.
it worked for me this way, Eclipse should be closed before issuing these commands.
Restart your phone as well!

It happens sometimes if you use more than one instances of eclipse
To repair logging do:
1. Unplug the device
2. Close all Eclipse windows
3. Restart adb in command line: adb kill-server and than adb start-server
4. Run again Eclipse and connect device
Sometimes this also helps, Go to Eclipse Window > Perspective > DDMS and than from Device sub-window choose Reset adb

ADB not responding. You can wait more,or kill "adb.exe" process manually and click 'Restart'

I have installed Android Studio.
Then I have updated the Android SDK.
Now when I start Android Studio, this message pops up:
ADB not responding. You can wait more,or kill "adb.exe" process manually and click 'Restart'
The dialog has 3 options: Wait more, Restart and Cancel.
But all of them
gives me the same result, i.e. a message Waiting for ADB appears and I can't do anything with Android Studio.
I have to kill the program using windows task manager! I'm using windows 7.
Can anyone help me on this?

Go to
Tools > Android > (Uncheck) Enable ADB Integration
(if studio hangs/gets stuck end adb process manually)
then,
Tools > Android > (Check) Enable ADB Integration

On my macbook pro, i was occasionally getting this in Android Studio. The following resolved it for me:
Open up a Terminal and, instead of using 'adb kill-server', use this:
$ killall adb
wait a minute and it looks like Android Studio automatically restarts adb on it's own.

From the command prompt run the command adb kill-server. This will shutdown ADB and android studio or Eclipse if you were to use that, would show Waiting for ADB as you said.
Once ADB has shutdown down run adb start-server or run adb devices which will automatically start the adb service and show that your android emulator or development devices has successfully connected.

If you are suffering from "ADB not responding. If you’d like to retry, then please manually kill ‘adb’ and click ‘Restart’ or terminal appear Syntax error: “)” unexpected"
then perhaps you are using 32bit OS and platform-tools has updated up 23.1.
The solution is to go back to the platform-tools 23.0.1.
You can download the platform-tools 23.0.1 for Linux here , for windowns here and Mac here
After the download, go to your sdk location > platform-tools folder to delete old platform-tools in sdk and paste down into the downloaded one.
Woohooo ... it should work.
This is a bug with latest ADT.

For me, on Windows 7, killing the ADB server and restarting it via command line did not help. It would not start up successfully.
>adb kill-server
>adb start-server
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
So killing the adb.exe process via Task Manager was actually the easiest solution that case.

Check if any service is listening on port 5037, and kill it. You can use lsof for this:
$ lsof -i :5037
$ kill <PID Process>
Then try
$ adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
This solved my problem.

I ran into this problem and tried a number of solutions on my Mac without any success. I finally got to work with the commands below:
$ rm -rf ~/.android
$ killall adb
$ adb devices
Note that rm -rf ~/.android will remove any AVDs that you have configured, so don't take this step lightly. Personally I had to though and I'm not sure why. Hopefully this helps someone.

This issue could be because adb incompatibility with the newest version of the platform SDK.
Try the following:
If you are using Genymotion, manually set the Android SDK within Genymotion settings to your sdk path. Go to Genymotion -> settings -> ADB -> Use custom SDK Tools -> Browse and ender your local SDK path.
If you haverecently updated your platform-tools plugin version, revert back to 23.0.1.
Its a bug within ADB, one of the above must most likely be your solution.

I run netstat -nao | findstr 5037 in cmd.
As you see there is a process with id 3888. I kill it with taskkill /f /pid 3888
if you have more than one, kill all.
after that run adb with adb start-server, my adb run sucessfully.

1.if your phone system is over 4.2.2 , there will be
2.disconnect the USB and try again or restart your phone
3.After after all try , it didn't work. It may be a shortage power supply so try other usb interface on your computer.
I solved the problem doing the first step . anyway have try.

If you need to kill all adb processes on windows with one command, you can do it as follows:
taskkill /F /IM adb*

I had this problem and solved it by this way...
I had a app in my pc that used adb...
I tried to disable it but still my android studio's adb had problem
after unistall that application and problem solved.

I had the same problem. I have restarted ADB in any possible way, I have killed the process and restarted the PC with no results.
Then I found this plugin. Just download and install it in your Android Studio IDE. Under Tools -> Android you have a menu ADB Idea. Here you can kill, start, restart, clean ADB.

None of the above helped me completely. Although Oventoaster made me think. I had a couple of adb on my system. Removed them almost all.
I am running android studio on ubuntu 14.04 64 bit.
So I checked manually /home/xxxxx/Android/Sdk/platform-tools/adb
where xxxxx was my linux username
this gave
/home/xxxxx/Android/Sdk/platform-tools/adb: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
https://stackoverflow.com/a/27415749/4453157
solved it for me.

If the above CMD command option is not working and you cannot make it work in any other way then follow this below.
Click on below link
http://adbshell.com/downloads
and download the first link with name ADB Kits ( contains adb.exe and necessary .dll files).
After downloading replace these files with the ones in the path
Android/Sdk/platform-tools/
Now click on adb.exe and it will open cmd and will start the adb server.
Now it will detect the device and no problem. OOOOOllllaaaaa.....
If the Problem persists again then do the same... save the folder
somewhere.... just replace files... it will detect the device
automatically then

I had this problem on Windows 8, but I solved the problem by updating all of Android Studio's plugins with the SDK Manager, then restarting the computer.

An another one: you might want to avoid running Eclipse and Android Studio together, it helped me.

I had this problem on Windows 7. My situation is this through SDK Manager. I only download API 19 but I had not downloaded related Android SDK build-tools. So it occur this problem.
I went through SDK Manager download build-tools 19 to fix it. Hope to give you help.

Faced this issue on Mac:
I have tried different solution, But below works for me -
Uninstall "Vysor" plugin if you have installed for Chrome
Under Home folder > find .Android folder and move to trash
Goto, Android sdk > delete/move to trash platform-tools folder
Again install/download from Android SDK Manager
Open terminal -
adb kill-server
adb start-server
Check adb devices, It will work and display you all connected devices.
Hope it helps !

there seems to be about a million reasons this bug happens, but for me (running on ubuntu), it was openvpn running in the background that caused it.
I killed the openvpn service and no more issues.