Develop Reference

How to restart android adb using terminal on macOS?

I keep having an issue with the Android Studio ADB not recognizing my devices. So far, the only solution I've found is to do a complete reboot of my entire computer, which isn't practical. I'd like to be able to restart the ADB from terminal, because I have seen other posts on here that claim it will fix the issue. However, I can't figure out where to use the commands "adb kill-server", because doing it at the base directory returns a "command not recognized". Can somebody help me figure out how to navigate into Android from terminal and use the command? Or, does anybody have another solution to the original problem of Android Studio not recognizing my devices?
Thanks in advance! Sorry for the wordiness.

blackbelt:~ blackbelt$ adb kill-server
blackbelt:~ blackbelt$ adb start-server
works on Linux as well as on Mac. In my machine, adb is in PATH
"command not recognized". Can somebody help me figure out how to
navigate into Android from terminal and use the command? Or, does
anybody have another solution to the original problem of Android
Studio not recognizing my devices?
In your case adb is not declared in PATH. You can either export the PATH, or specify the full qualified path to adb in the command line. E.g.
blackbelt:~ blackbelt$ /path/to/platform-tools/adb kill-server
blackbelt:~ blackbelt$ /path/to/platform-tools/adb start-server
or
blackbelt:~ blackbelt$ ./adb kill-server
blackbelt:~ blackbelt$ ./adb start-server
if you are inside platform-tools

Well instead of doing it through command line, if you find that hard you can also do the same from android studio.
Go to tools -> Android -> Android device monitor . Then it will open the separate window where you can see all the devices or emulator attached to the process. On the left hand side below the Devices tab there will be and menu bar, you need to click on the drop down arrow which will give you the option to reset the adb. Here is the image for reference
If you are using windows try to update the device driver for your device make sure the adb is correctly installed. When you connect your device to system see if it is allowed to be used at the system.

if adb kill-server not responding. Find the process id (PID) by typing top in terminal and finding PID next to adb. Then type kill <PID>
For example, for me PID for adb was 70163. Then i typed kill 70163

Simply stop adb:
adb kill-server
Then you can start it again any time:
adb start-server

Android Studio Error: Adb refused a command

I just changed my PC, and now I have a problem with Android Studio, every time i try to run or compile an app it install it correctly, but then it cannot start the main activity of the app, if you need it this is the full Android studio output:
Waiting for device.
Target device: samsung-gt_i9000-3733E37B1ACB00EC
Uploading file
local path: C:\Users\Federico\swagmasta\TurnarioConapo1.0\app\build\outputs\apk\app-debug.apk
remote path: /data/local/tmp/feddycapdev.conapo.turnario
Installing feddycapdev.conapo.turnario
DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/feddycapdev.conapo.turnario"
pkg: /data/local/tmp/feddycapdev.conapo.turnario
Launching application: feddycapdev.conapo.turnario/feddycapdev.conapo.turnario.MainActivity.
DEVICE SHELL COMMAND: am start -D -n "feddycapdev.conapo.turnario/feddycapdev.conapo.turnario.MainActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER
Error: Adb refused a command
I tried to manually run am start -D -n "feddycapdev.conapo.turnario/feddycapdev.conapo.turnario.MainActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER from the adb shell, and it work correctly, some ideas on how could i fix it?
UPDATE : I tried running as admin, rebooting PC, reconnecting cable, killing all the adb.exe processes, killing the adb server and restarting it, noone of this worked.
Maybe it's a problem of driver? I'm using a Samsung Galaxy S for debugging, at the beginning the PC didn't recognized it, so I installed samsung USB driver, so maybe that's the real problem, but if i can install app to my device via adb the driver should be working right?

Please kill and start adb server from console or terminal using following commands:
adb kill-server
adb start-server
If it does not help try to restart your computer.
If you are getting
adb command not found
error then you have to go in platform-tools directory in Android SDK.
hope it helps!

It could be blocked by some other instance of adb.
Look into your task manager if you are not running another instance of adb.

AVD NOT Showing in running android devices

As show in photo that AVD is running but not showing in Android running devices.
what is the issue?
how can i fix it ?

type in command line
adb kill-server
adb start-server
or goto ddms tab and then on left hand side select drop down and reset adb
see image

check out this
command
sudo adb kill-server && sudo adb start-server

Disconnect your USB attached real device if there is one. It can also be an API missmatch.

Must do adb kill-server and start-server everytime to recognize android device in Ubuntu

I'm developing android apps in eclipse and I upgraded recently from Ubuntu 12.10 (Quantal Quetzal) to Ubuntu 13.04 (Raring Ringtail).
In the previous Ubuntu version I had zero problems in recognizing my android device.In this new Ubuntu version I must do:
sudo adb kill-server
and
sudo adb start-server
in order to Ubuntu recognize my android device.
Everytime I restart my computer it appears question marks in eclipse when I try to debug an app, and I have to run these command lines everytime to make it work.
Anyone knows if there is a way to recognize my phone permantelly?

adb "flakiness" is a common problem, you have the right idea to start adb with root permissions.
If you have eclipse running and run it as two separate commands, there is a chance that eclipse will have tried to startup adb as a non-root user before you have run your start-server, so I recommend running in a single command line:
sudo adb kill-server && sudo adb start-server
Also you want to make sure you have only one copy of the sdk installed and that eclipse is using the same copy as is on your path at the command line.
Possibly could throw the run-as-root logic into an init script so that when you restart the computer it comes up as root - I haven't tried this though, always just "control-r, start-ser" from the command line =)

I had the same problem and solved it by
just change the owner of adb to root and restart then in future the problem won't happen again.
use this:
sudo chown root:root -R /opt/..../sdk/platform-tools/*
sudo /opt/..../sdk/platform-tools/adb kill-server
sudo /opt/..../sdk/platform-tools/adb start-server

Adb kill-server not responding?

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.

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

Task Manager -> Process -> adb.exe -> End process
That worked for me.

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.

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

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.

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.

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/

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 .

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

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.
Next:
Open Power Shell as administrator
cd C:\Users\PC01\AppData\Local\Android\Sdk\platform-tools
./adb kill-server
./adb start-server