Develop Reference

Android ADB - failed to connect to '192.168.1.4:5037': Connection refused

When I try to connect my mobile device using adb connect 192.168.1.4:5037 i get failed to connect to '192.168.1.4:5037': Connection refused error sometimes.
How can I fix this? This issue happens intermittently. What is the reason behind this & how to fix it?
I even tried killing and restarting adb server
My steps
adb tcpip 5555
adb connect 192.168.1.4:5555
Additional Info
Device - Poco F1
Android - 10

You need to run adb tcpip 5555 with the USB cable plugged in - and then unplug.

Try following these instructions:
Open the command prompt and navigate to your sdk/platform-tools/ folder.
Type adb tcpip 5555 with your device plugged in
Type adb connect <your device ip address>:5555
At this point you unplug your device and type adb logcat
At times, such as unplugging/plugging into a USB device, the logcat will become disconnected, just redo steps 3 & 4.

ping 192.168.1.4 to see if this IP is online.
telnet 192.168.1.4 5555 to see if this port is online.

Phone should be connected over USB cable before making connection over Wi-Fi. Once you successfully connected to the device you can unplug the cable.
Just in case, try
adb kill-server
to restart the server
And make sure developer settings and USB debugging enabled, so it must be working via USB cable

Option I: This might happen when your device keeps changing IP addresses, since WiFi is sometimes switched on and off, and when you get a DHCP lease from your server/Access Point it might change. Keeping your device plugged in via USB (not necessarily to the host, but to any charger), or keeping screen on will ensure it's at the same address, and - assuming that you have the address right and you used adb tcpip (or set the adb TCP property in the shell) it should work.
Option II: You have the port number wrong. "Connection refused" means you got to the IP address, but the port isn't listening. Up there in your question you first state 5037, then 5555?

ADB: "failed to connect to '192.168.x.x:5555': Connection refused" tried both USB and Wifi

On my pixel3a phone running Android Pie, I tried to adb connect to the phone using my macbook pro and it gave me a connection refused error
"failed to connect to '192.168.xx.xxx:5555': Connection refused".
My macbook can adb connect to my other Android Pie and Oreo devices, therefore, I think the problem might be on the pixel3a phone side.
I'm guessing the debugging services is not running or somehow blocked on pixel3a which is why I keep getting connection refused.
NOTE: developer mode has been turned on and debugging over USB option has been turned on as well.
Anyone ran into similar issue? Thanks.
Btw, I tried to:
restart macbook and pixel3a.
connect through USB and Wifi.
look through to see if there is any app with the open port 5555 on the phone but none found.
see if there is anything open that looks like an adb debug using other ports than 5555 but don't see anything that looks like it.
turn off the developer/debugging mode then turn it back on again but still not working
p.s. I just got the phone and enabling the developer mode was the first thing I did. I did not install any firewall or other apps besides the network monitor apps after I see the connection refuse error.

This happens after a long period of inactivity. You need to restart the tcpip connection on port 5555.
Connect the phone to the computer via USB. Then in terminal navigate to platform-tools and insert the command...
./adb usb
expect the response restarting in USB mode
Then ..
./adb tcpip 5555
and expect the response restarting in TCP mode port: 5555
You can now check your device ip address and add it..
./adb connect 192.168.86.40:5555
ps. If you added the path to bashrc, no need to go to the platform-tools folder, just replace the ./adb with adb .

Android Studio wireless ADB error (10061)

It seems that wireless ADB has more and more issues each time I update Android Studio. Using 2.1.1, I'm now unable to connect to my tablet using the command:
adb connect <ip addr>
It results in the error:
unable to connect to <ip addr>:5555: cannot connect to <ip addr>:5555: No connection could be made because the target machine actively refused it. (10061)
This happens directly after approving the connection in the dialog box on the tablet. Before today I was forced to do an adb kill-server prior to attempting to connect to the tablet but now that doesn't even help.

Generally you can say this error is network related, check these items first:
make sure your computer and your device can see each other in network mostly this means they are connected to the same router, but in more advanced scenarios your device may be connected to a wireless router and you computer may be connected to you Local Area Network. what is important is they can see each other. you can check this by pinging you device ip address from you computer.
make sure there is no conflict with ip addresses, this might be very simple. but if you do not use DHCP server and you enter the ip addresses in you devices you could mistakenly entered same ip address in different devices
when you are sure about the network issues redo the famous steps
So when you connected by USB follow these commands:
stay connect via USB
connect to your WIFI network (computer and mobile device both)
ping DeviceIP (must be have ping to your device)
adb kill-server
adb usb
adb tcpip 5555
unplug usb cable (as per #captain_majid 's comment)
adb connect yourDeviceIP
adb devices (must be see two device names , one of them is by deviceIP)
unplug USB cable
Steps from could not connect to tcp:5037: cannot connect to 127.0.0.1:5037: No connection could be made because the target machine actively refused it. (10061)

when restart device then your port also channge so hit command below
1- adb kill-server
2- connect your phone to pc with usb cable
3- adb tcpip 5555
4- adb connect (your device ip):5555

Device and PC are connected to same network connection.
1 stay connect via USB
2 adb kill-server
3 adb usb
4 adb tcpip 5555
5 adb connect 192.168.43.1:5555
6 adb devices (must be see two device names , one of them is by deviceIP)
7 unplug USB cable

I had the same issue. These steps worked for me:
connect your device with usb
when your cmd already in AppData\Local\Android\Sdk\platform-tools>,type adb tcpip 5555
the cmd will show restarting in TCP mode port: 5555
type adb connect 192.168.43.1:5555
Hope this can solve your issue.

I recently faced the same problem.
It occurs because your device and PC are connected to different Networks.

when restart device then your port also channge so hit command below
1- adb kill-server
2- adb tcpip 5555
3- adb connect (your device ip):5555

I got this error when I had Bluestacks emulator started together with my phone attached.
When I typed in command prompt adb devices I could see two devices:
adb devices
List of devices attached
dfdcdc9c device
emulator-5554 device
Before typing adb connect I had to type -s and device ID:
adb -s dfdcdc9c tcpip 5555
adb -s dfdcdc9c connect <ip addr>

In case of me, i tried different port 5557 than again 5555,
adb tcpip 5557
adb connect device_ip_address
gives same error(10061) than again tried with,
adb tcpip 5555
adb connect device_ip_address
result: connected
that works for me(while the other thing is ok like as developer option is on and connected to same wifi)

Make sure you have to connect your phone through a USB cable for the first time.
Using Command prompt, Go to your Android SDK Directory (sdk->Platform-tools) and then
run the following commands
1- adb kill-server
2- adb tcpip 5555
3- adb connect 192.168.1.130 (Replace IP Address with your phone IP)
4- Now you can unplug it.
5- Then go to the Android studio and choose the device with IP address in
Run
Dropdown. Hope this will help it for everyone.
And then for next times just runs following command
adb connect 192.168.1.130:5555
Note: If Device is not showing in Android studio devices dropdown then
connect **USB** and run following commands
1-adb kill-server
2-adb usb
3-adb tcpip 5555
4-adb connect 192.168.1.130:5555

You must connect the mobile device via USB first, then type adb tcpip 5555 ,
and then enter your device IP adb connect <your_device_ip>

I solved the problem by enabling USB Debugging in Developer Options.

Unfortunately this issue can be caused by different reasons.
One of the reasons - make sure previous communication is disconnected.
USE:
1. adb kill-server
2. Issue command adb disconnect after restarting adb server. Do same thing after finishing job
3. run adb remount
4. adb tcpip 50555 (I usually use higher port number)
5. unplug USB cable
6. adb connect device_ip:50555
when done run adb disconnect

Following steps are standard ones to follow( mostly same as previous answers):-
adb tcpip 5555.
adb connect your_device_ip_address.
adb devices (to
see if devices got connected).
But in some cases above steps gives error like "unable to connect to device. Make sure that your computer and your device are connected to the same WiFi network." And you notice the devices are already on the same network.
In this case, install this plugin "Wifi ADB Ultimate" and follow below steps.
Connect the device once through USB.
Refresh the list to check whether its connected.
Go to About Phone > Status > IP Address and note your IP
address(e.g. 198.162.0.105).
Come back to Android Studio and fill in this IP as done in below
photo and hit the run button.

I had same issue with Android Studio 3.5.2, here is how i solved it.
First you must connect your device via USB once. (Debugging mode starts only when usb is connected)
Go to command prompt :
adb tcpip 5555
(watch for port on which adb started)
then : adb connect :
After successful connection goto Studio>Run>Select Device.

I assume you already solved the problem by now. but here is the way to avoid the problem if you are using multiple devices. I used to have the same issue so many times until I understand, how it works.
I was also trying to connect multiple devices one after another or trying to connect the same device after a while.
Always make sure to disconnect the older device before you connect the new device:
adb disconnect
after that, you will be easily able to connect new device:
adb tcpip 5555
adb connect <your_device_ip>
you can always try to ping the device using the ping command, if the ping is not getting acknowledgment then you must have connected to different wifi then your laptop or you haven't connected to wifi at all:
ping <your_device_ip>

For anyone who is Android 11+
Enable Developer Options
Enable Wireless Debugging
Allow wireless debugging on this network.
Pair Device with Pairing code
Type in adb pair [Phone_IPAddress]:[PORT] [PAIRING CODE]
After Successfully Pairing. Type adb connect [Phone_IPAddress]:[PORT]
For more info: ADB Documentation

Usually the 'target machine actively refused it' message is displayed when the target machine's 'ADB debugging' feature is not turned ON. It is turned off by default in almost all devices unless we enable 'developer options'. So whenever you land on this error, make sure you go to the settings of your target machine and trickle to the developer/development area and somewhere there should be a place to enable ADB.

After weeks of struggle and trying different approaches while everything was right and on the same network (ping {ip} was coming back positive) I figured the dumb debug bridge does not look for all network adapters to find the device! The device got connected when I manually disabled all other network adapters except the one (WiFi adapter) which was required to connect.

Step 1. Type command in terminal adb tcpip 5555
Step 2. Type command in terminal adb connect <your_phone_ip>:5555
Now check in studio device Monitor tool your phone connected without wire.
Note :- Most important your Laptop & Mobile Device Connected with same Network

I had the same issue and I thought it might be because of the network and tried many solutions but didn't work. Lastly, I checked my IP address which was updated for my device and was the root cause for this.
So please check the IP address first and use adb tcpip <port> to start listening the connection and adb connect <IP>:<PORT>

Try this way change adb to .\adb
PS C:\users\mori\appdata\local\android\sdk\platform-tools> .\adb kill-server
PS C:\users\mori\appdata\local\android\sdk\platform-tools> .\adb usb
PS C:\users\mori\appdata\local\android\sdk\platform-tools> .\adb tcpip 5555
PS C:\users\mori\appdata\local\android\sdk\platform-tools> .\adb connect 192.168.1.34:5555
connected to 192.168.1.34:5555

I had a similar problem. I found out the problem was if I had other devices/emulators connected to the adb already, the "adb connect <ip_addr>" command would give me the "No connection could be made because the target machine actively refused it" message.
The solution is to make sure all the other devices/emulators are disconnected (either physically disconnect or quit the emulator application) before running adb connect <ip_addr>. You can then reconnect your other devices (if you need them reconnected). A total pain.
Your mileage to this solution may vary depending on your problem.

I got this error when trying to establish an ADB connection to a smartwatch with WearOS 1.0 (Huawei Watch 2) via WiFi. Enabling the menu entry for fixing some WLAN issue ("Fix error via WLAN" -- my own rough translation of the German caption "Fehler über WLAN beheben") in the "Developer options" on the WearOS device solved the issue for me.

I had the same issue. It was working perfectly for a month, and then one day it stopped working. I tried all the solutions above, but to no avail. Then, I noticed that for some reason, the IP address of my phone had changed, ending with the number 1 instead of 0. So I connected to the new address with 1 as the last digit in the address and now it works again. Weird.

In my case I played with my device long enough to somehow mess up adb deamon, so port number was not set up correctly anymore.
getprop service.adb.tcp.port returned empty string.
So I solved this with following commands:
stop adbd
setprop service.adb.tcp.port 5555
start adbd
I ran all commands on rooted device in app that emulates command prompt.

So I came here because I want to adb shell into my physical Android phone over the network. Lots of useful answers are provided, but the most obvious fact is never stated. Here is the #0 fact:
The Android phone should ALWAYS be connected via USB to the laptop
And then another different laptop will do adb connect ...
This was not what I had in mind and all the above answers never mentioned it.

Go to Android Studio File - Settings
Next..
Happy Codding :)

I had a problem with my Huawei. For some reason I had wrong drivers, on Device Manager it was showed like "Android Phone". Then, I updated the drivers from Device Manager, I choose another driver and now it is showed as "Huawei" device.
From there I connected my device whitout problem (adb connect IP:5555)

For Android TV, Connect PC and TV in the same network (wi-fi),
enable developer option, and go to developer option and enable ADB debugging option.Then run the commands given below
1. ping <ur IP> (check the connection)
2. adb disconnect (to remove all the previous connections)
3. adb connect <Ur IP>
4. adb install app_name.apk

I have attempted to use many solutions above to no avail and found some pretty simple solution that works for myself.
If you are using a real device to debug like me, you may check the device official website to download the android USB driver for your development environment.
I'm using Samsung phone to debug and using windows as development environment thus I went here, download the Android USB Drivers for Windows and run it.
It resolves my ADB problem.

Unable to connect to my android device via ADB

Sorry for the nooby question, I am having trouble sorting this out using the web.
I am trying to simply connect my device to my pc via adb to debug my application.
My device is rooted. Adb debugging is enabled. I downloaded an adb running application and started ADB.
Now i am trying adb connect ip:5555. and keep on getting "unable to connect to ip:5555" ...
Same happend when i try to connect via usb.
c:\>adb connect 192.168.20.191:5555
unable to connect to 192.168.20.191:5555
Help...?
EDIT:
C:>adb devices
List of devices attached
06fecaa1 unauthorized

Launching Cordova
Open Node.js / CMD
Point to "the directory where you have located your source folder" >>> C:\Projects\RJX
Enable Wifi
Turn on Developer Option under settings
Enable / Check USB Debugging Option under settings (Google if cannot find this option)
Enable / Check the MTP Option under settings (Google if cannot find this option)
ADB Commands
adb kill-server
adb start-server
//plug off cable from mobile and plug in again if you connected your device earlier
//Uninstall the application from mobile if you already installed. (if necessary)
adb tcpip 5555
adb connect "ip" //adb connect 192.192.2.128
adb devices //to check device details
cordova run android --device
if this steps are not worked, try to close the cmd and do it again. Sometimes it needs some refresh.
**Android devices version 4.0.4 and after should be no problem if you follow these steps.

I will assume you are able to understand adb connect / ip's etc I won't bore you with that
but there are two lame "gotcha's"
THE GENYMOTION GOTCHA
genymotion WRECKS a lot of this sometimes.. I am sorry but it does.. it has a "I know what I am doing I am taking over" mentality.. sadly it doesn't know what it's doing :-P often you have to turn off genymotion for the adb->usb to work.. basically connect phone FIRST ... make sure it's there in eclipse (adb kill-server / start server if needs be ), then AND ONLY THEN then genymotion AFTER
THE OOPS [/facepalm] GOTCHA
check that your phone it isn't in Windows merely as a "Camera" - go to My Computer and look. If it looks like this pic it's that you're not running Samsung Kies(/disabled because it's annoying) the phone still goes "blub bling" when you plug it in, it may be connected via wifi so have a LAN ip but it is NOT really "connected" to ur PC. instead run/download/update this (with phone disconnected) then make sure Kies is happy AND MAKE SURE MTU is enabled

This error happened to me when PC was (accidentally) NOT in the same network as Android. When I logged on Android to the same WIFI network as PC it now works perfect and I don't have this problem.

The answer here is that it's not listening on the correct (default) port. So you need to set the TCP/IP port to 5555. Connect your device via USB and issue the following command in cmd (terminal):
adb tcpip 5555
Following this your adb connect should work fine, e.g.:
adb connect 192.168.0.n
Hope this fixes it for you.

This happened when I was previously connected with one device (e.g. apps2fire) and then tried using adb command from another machine. I rebooted the Android device and then tried again and received the prompt to allow the connection as I would have expected.

First, check your ip address in your device, then following this command.
adb kill-server
adb tcpip 5555
adb connect [your-ip-address]:5555

Connecting ADB using Wifi for non rooted device

I am trying to connect ADB using WIFI on my non rooted android devices. Currently i have 3 android devices out of which 2 are running on Android 4.0.4 and 1 on 2.3.
My device IP's are 192.168.2.122, 192.168.2.131, 192.168.2.115
I have enabled USB debugging on all of them and follow all the steps as listed here
On the command line, I did the following
adb tcpip 5555
restarting in TCP mode port:5555
adb connect 192.168.2.131
My problem is on one of my device(Android 4.0.4) ADB is getting connected with the message saying
connected to 192.168.2.122:5555
However when i try connecting other it says
unable to connect to 192.168.2.131:5555
Screenshot of the terminal page:
Image of terminal on the connected device:
Image of terminal on device which is not getting connected:
Many of the posts on Stack Over Flow says i need to root my phone for the same but the device on which ADB is getting connected is also not rooted.
May be the problem with the devices not getting connected is that their ports are not getting listened.
Any help appreciated.

I had the same problem.
I firstly connected my Android4.0.3 based device via USB and set the TCP/IP port to 5555
$ adb tcpip 5555
After that I disconnected USB connection and connected to device via WiFi IP and it worked.
$ adb kill-server
$ adb connect 192.168.2.5
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
connected to 192.168.2.5:5555

The steps are correct, with one small part different: the connect step has to be done after taking out the cable.
To reiterate follow the steps exactly as below and it will work for non-rooted devices also. I tested it with several non-rooted devices including Moto G, Nexus 1, Videocon etc.
Attach mobile via USB and type:
adb tcpip 5555
To find the mobile ip type:
adb shell ip -f inet addr show wlan0
The ip address will be shown in second line like this:
inet 192.168.1.233/24 brd 192.168.1.255 scope global wlan0
where 192.168.1.233 is the ip address of your mobile.
Remove USB cable and type:
adb connect mobile-ip:5555

After read this question I decided to create a easy to use solution to fix this problem. You can use an open source IntelliJ Plugin I've developed. Here is the code and here the plugin ready to be used.
The usage is quite simple. Here you have a gif:
Remember that old devices using an Android 2.X does not support this Android Debug Bridge feature. That's why you can't connect the device you show in the screenshots.

It works perfect with android 4.0.4. but, below that it does not works.
so, the answer to your problem is to upgrade all devices to 4.0.4.

first connect device using USB
then apply the commands....

Turn on adb over wifi on your phone
Then create file on your desktop ex. 'connect.bat'
and paste this code (you have to only change sdk, port and ip):
SET sdk=F:\Praca\sdk\platform-tools
SET port=5555
SET ip=192.168.1.101
cd /dd %sdk%
adb tcpip "%port%"
adb shell netcfg
adb connect "%ip%:%port%"
echo connected by WiFi
pause
adb -s "%ip%:%port%" usb
echo disconnected
pause
It's really fast and simply solution. Have fun!