ADB not responding. You can wait more,or kill “adb

2019-01-10 20:08发布

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?

20条回答
一纸荒年 Trace。
2楼-- · 2019-01-10 20:40

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.

查看更多
我命由我不由天
3楼-- · 2019-01-10 20:43

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.

查看更多
唯我独甜
4楼-- · 2019-01-10 20:43

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.

查看更多
beautiful°
5楼-- · 2019-01-10 20:44

This issue could be because adb incompatibility with the newest version of the platform SDK.

Try the following:

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

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

查看更多
forever°为你锁心
6楼-- · 2019-01-10 20:45

Faced this issue on Mac:

I have tried different solution, But below works for me -

  1. Uninstall "Vysor" plugin if you have installed for Chrome
  2. Under Home folder > find .Android folder and move to trash
  3. Goto, Android sdk > delete/move to trash platform-tools folder
  4. Again install/download from Android SDK Manager
  5. Open terminal -
    • adb kill-server
    • adb start-server
  6. Check adb devices, It will work and display you all connected devices.

Hope it helps !

查看更多
成全新的幸福
7楼-- · 2019-01-10 20:46

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.

查看更多
登录 后发表回答