android – adb cannot bind 'tcp:5037'-ThrowExceptions

Exception or error:

It used to work fine, but today after I connected my Android phone to my machine, and run adb devices, I got the following error:

* daemon not running. starting it now on port 5037 *
cannot bind 'tcp:5037': Address already in use
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon: Operation timed out

How to solve this problem? (I am using a MacBook)

How to solve:

Try with following commands

Find port details by List Open Files lsof command.

sudo lsof -i :5037 and find PID and kill it.

kill -9 <pid here>

Example: kill -9 4363

Then start adb server. adb devices command.

###

Kill the Adb server and restart.

adb kill-server
adb start-server

enter image description here

###

I managed to solve this problem on MacBook by first running the following command to list the process which is using port 5037

lsof -n -i4TCP:5037 | grep LISTEN

Then, I kill it:

kill -9 <PID>

Then, adb devices works!

###

it is clear that Address already in use. busybox netstat -antp to check who is using the port.

###

I’ve fixed the problem by updating the Android SDK.

android update sdk --no-ui  

Additionally, I’ve updated the Platform Tools to the newest version.


If this doesn’t work, redownload android sdk.

  • wget http://dl.google.com/android/android-sdk_r24.2-linux.tgz

  • tar -xvf android-sdk_r24.2-linux.tgz cd android-sdk-linux/tools

  • install all sdk packages

  • ./android update sdk --no-ui

###

  1. Android Studio Terminal

$ adb devices

List of devices attached
adb server is out of date.  killing...
cannot bind 'tcp:5037': Address already in use
ADB server didn't ACK
* failed to start daemon *
error: 
error: 
  1. OS Terminal

$ adb devices

List of devices attached
adb server is out of date.  killing...
* daemon started successfully *
  1. Finally test again at the IDE terminal

$ adb devices

GL

###

I ran adb kill command and then it started working fine

adb kill-server
adb start-server

Leave a Reply

Your email address will not be published. Required fields are marked *