ADB Not Responding - Wait More or Kill adb or Rest

Question

This question already has an answer here:

• How to make Android's aapt and adb work on 64-bit Ubuntu without ia32-libs (works for versions 12, 13 and 14) 5 answers

I did serious searching both on Google and SO before asking this question - mainly because none of the suggestions out there didn't fix my problem!

After unsuccessfully attempting to make my new Intellij and Android SDK to work on my newly installed Ubuntu 13.10, I am coming to you for help. I know there are thousands of suggestions out there already but none of them worked for me.

Here is what I have tried:

• adb kill-server
• adb start-server
• adb devices

That last command listed my device - and that meant that it was able to detect it without any issues.

• I have added all the necessary rules like 51-android.rules and those should be fine.
• Started and restarted the IDE several times without any success.
• I have installed libraries to fix any 64-bit issues
• I even deleted the adb key in the .android folder since it gets generated automatically each time anyway.
• I have no other older versions of IntelliJ or SDKs;
• This was a clean installation of Ubuntu; I totally removed my Windows 8 (yeah, am done with Windows) and installed Ubuntu 13.

I don't know what else to try and do because I have spent hours online trying suggestions from others to no avail.

Any help would be really appreciated because I can't wait to get back to my Android App Development! Thank you.

EDIT - SOLUTION

I solved this problem and then documented it here for others who are having this issue; ADB not responding - the solution

I hope this helps.

Answer 1

Make sure adb is in your user's $PATH variable.

or

You can try to locate it with whereis and run it with ./adb

Go to the path Android/Sdk/platform-tools/ and run this command from terminal

./adb start-server

Answer 2

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

Answer 3

If it is a case of missing dependency, you can solve the problem by installing ia32-libs, lib32ncurses5-dev, and lib32stdc++6 packages using apt-get utility. This is required in order to run 32 bit apps on 64 bit machine. If the problem persists, then it may also be a case that another client-server programs like lampp is running... It is because android debug bridge is also a client-server program... In this case, what you can do is, stop the program and restart android studio. You can even try restarting your system...

Answer 4

I did following

chmod u+x /path/to/adb

and restarted android studio

Answer 5

I had the same problem. I'll try to help you explaining my problem. I was trying to run a Selenium test on my HTC and so have to install an Android Debug Bridge just like you. I believe you don't have problems with installing the bridge. When you connect your device in USB port, try to script "adb devices" and you can see if your device is connected or not. Then I'm not so sure but I think you have to install a server as it was in Selenium Android to stream your data to your phone.

Answer 6

I got the same error. After starting a virtual device I tried to run the app I'm creating, again the error appeared but with a tip added: Install the SDK Platform-tools. Opened the SDK Manager and realize that the "Android SDK Platform-tools" Rev. 19.0.2 was not installed. Installed it and ADB started to work without errors.

(I am running Android Studio 6.0 in Ubuntu 14.04 and don't remember removing the Platform-tools)