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?

Unable to connect to device with Marshmallow for wireless debugging. Getting (10061) error

I am trying to connect to an Android device with Marshmallow for wireless debugging.
C:\...\sdk\platform-tools>adb connect 192.168.1.103:5555
unable to connect to 192.168.1.103:5555: cannot connect to 192.168.1.103:5555:
No connection could be made because the target machine actively refused it. (10061)
I also tried adb connect "192.168.1.103:5556" and "adb connect 192.168.1.103" but ended up with same result.
The first command above used to work fine on my OnePlus Two before the Marshmallow update.
Any help on how to do wireless debugging on Marshmallow?

I am also using the One Plus two and updated to marshmallow 2 weeks ago . i have the same issue
try to kill your adb sever then try again .
adb kill-server
you should use 5556 port number not 5555 anymore
if its not working connect your phone via usb cable then restart the adb into wireless mode
adb tcpip 5556
then try to connect your phone with the port no 5556 (eg ip:5556) after connected you can remove your usb cable
it worked for me

Connect the Android device with the computer using your USB cable.
Restart adb in tcpip mode
adb tcpip 5556
Now try to reconnect the android device.

at first ping your Android Device IP from pc and ping your PC IP from Android Terminal Emulator make shore got replay (it means wireless connecting is stable and no firewall problem)
connect USB chek "adb devices" in command line
in this level you must have device name (esle must use other command likd eadb kill-server & adb start-server or chek device driver)
make your Device conncet first and work truly (many reason like your device driver and other thing must cheked in this case)
after that try "adb connect 192.168.1.3:5555" (your device IP And always POST is 5555 and some time 5556)
if got error like (10061) test this "adb tcpip 5555"
after that tray again "adb connect 192.168.1.3:5555"
if this doset work unplug usb connection and connect again and tray one more time
after connecting to device you device ip display in devices list in ADT now you must unplug USB if lost connection , dont wory just try "adb connect 192.168.1.3:5555" one more time but whitout USB cable (it just for first time wireless connecting need usb)

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

adb device offline with ADB wireless

For some reasons, my phone does not work anymore with cable.
I saw on the Internet that it is possible to connect adb to the via Wifi, however I tried it and I get this:
adb devices
List of devices attached
192.168.1.2:5555 offline
I search this on Google and it seems that it is related to Android 4.2.2.
And indeed, my device is running Android 4.2.2.
I didn't find any answers on Google for my problem since it is always with a cable, mine is on Wifi...
Any idea how to solve this?

For me the complete steps that worked were :
Settings -> Developer options -> Revoke USB debugging authorizations (clear the list of authorized PCs).
Set USB Debugging OFF.
In Terminal write : adb kill-server
Then : adb start-server
Then : adb connect xx.xx.xx.xx:5555 (the devices ip), it should say unable to connect.
Now turn ON USB debugging again and type the adb connect xx.xx.xx.xx:5555 again.
It should now ask for authorization and you are back online without
needing to connect cable to USB, only wifi used.

run adb kill-server, then try to connect wirelessly again. It worked for me.

I could not find exact solution for this problem too.
Best way worked for me was disconnecting device from wifi, then try to connect while device is not connected to Wifi like:
adb connect 192.168.55.3:5555
this causes adb waiting for connection. immediately connect device to wifi and adb will detect device and connect again.
hope this helps.

Disconnect adb over wifi, connect your phone with a USB-cable to your pc. It will ask you on your phone is you want to allow the connection. Tick always allow. You will only get this when you connect with USB and have to do this only once, you can use over wifi afterwards.
Don't get the pop-up? Try the answers on google over a cable, since you need to do this first.

It seems you want authenticate adb over wifi.If you had your device rooted,you can try this way.
Copy ~/.android/adb_key.pub to your android device,and rename it to adb_keys
Move it to your /data/misc/adb/
Reboot your android,then reconnect over wifi.

For the first time in debug mode, you need to Authorize your phone with the PC, and that requires the USB cable. After that you can use Debug over WIFI.
If you want to force your phone to show the Authorization message box, simply delete the below file.
/data/misc/adb/adb_key

In android studio go to Preferences->Plugins
Download and install this plugin
ADB WIFI Connect
, restart Android Studio
Connect phone via USB
In android terminal use command: adb devicesyou should get visible device connected via USB:
List of devices attached
988a57334e57365058 device
Click on plugin icon in android studio AndroidWiFiADB
If phone get connected properly via WiFI, you see in event log:
12:41 Android WiFi ADB: Device 'ModelOfYourPhone' connected.
In android terminal use command: adb devices use should get
List of devices attached
988a57334e57365058 device
192.168.60.101:5555 device
Disconnect USB cable and re-check again adb devices, should remain only device connected via wifi:
List of devices attached
192.168.60.101:5555 device

Try disconnecting your device with:
abd disconnect <IP/TCP>:<port>
Then restart the WiFi connection of your device, and reconnect your device with:
abd connect <IP/TCP>:<port>
That may fix it; it worked for me.

For me, the important part turned out to be the following line adb tcpip 5555 together with using the port in the IP of my phone like so: adb connect 192.168.1.87:5555 (only using one of them, did not work, i.e: writing the second alone didn't work, writing the first and then excluding the port in the IP also didn't work). The adb tcpip 5555 line is not mentioned anywhere here. So, for me, the PORT needed to be both manually set and used in the connect line!
These are the events of my command line in Windows PowerShell Admin to demonstrate (Wifi on and debug mode on and confirmed permission when the popup came):
notice that the connection first failed, then it said it was connected which is weird behavior to begin with (no matter what, it always failed once and "succeeded" once), and in both instances, the device showed as offline. The disconnect commands also confirm that its 110% offline
PS C:\WINDOWS\system32> adb kill-server
PS C:\WINDOWS\system32> adb start-server
error: protocol fault (couldn't read status): Connection reset by peer
PS C:\WINDOWS\system32> adb start-server
* daemon not running; starting now at tcp:5037
* daemon started successfully
PS C:\WINDOWS\system32> adb connect 192.168.1.87:5555
failed to connect to 192.168.1.87:5555
PS C:\WINDOWS\system32> adb devices
List of devices attached
220947272e047ece device
192.168.1.87:5555 offline
PS C:\WINDOWS\system32> adb connect 192.168.1.87:5555
already connected to 192.168.1.87:5555
PS C:\WINDOWS\system32> adb devices
List of devices attached
220947272e047ece device
192.168.1.87:5555 offline
PS C:\WINDOWS\system32> adb disconnect 192.168.1.87:5555
error: no such device '192.168.1.87:5555'
PS C:\WINDOWS\system32> adb disconnect 192.168.1.87:5555
error: no such device '192.168.1.87:5555'
PS C:\WINDOWS\system32> adb tcpip 5555
restarting in TCP mode port: 5555
PS C:\WINDOWS\system32> adb disconnect 192.168.1.87:5555
error: no such device '192.168.1.87:5555'
PS C:\WINDOWS\system32> adb connect 192.168.1.87:5555
connected to 192.168.1.87:5555
PS C:\WINDOWS\system32> adb devices
List of devices attached
220947272e047ece device
192.168.1.87:5555 device
As soon as I added the adb tcpip 5555 command and it restarted in TCP mode port: 5555 the adb connect 192.168.1.87:5555 command worked!

Make sure that pc is authorized in the device by going to Developer options -> Revoke USB debugging authorisations and then trying to connect via USB. After accepting the PC, disconnect the cable and connect through wifi.
adb kill-server
adb run-server
adb connect IP:5555
Although in my case, when I tried to connect it failed at first and second try it said already connected.
I disconnected from the device and connected again and it solved.
adb disconnect ip:5555
adb connect ip:5555

I solve this problem for huawei P10.
its about phone's developer settings => find usb developer settings, and under usb developer setting there is a "adb debugging in charging mode..." enable it. My problem solved with this way. Hope yours too....

My solution steps:
Turn Off WiFi and Turn it back On again.
Settings -> Developer options -> Revoke USB debugging authorizations.
Settings -> Developer options -> Turn Off ADB over network and turn it back On again.
adb kill-server
adb start-server
adb connect xx.xx.xx.xx:5555
Note: Step 3 was the key for me. don't forget it.

In simple cases it will start after Enabling USB debugging
For complexities you need to delete the
adbkey
file from
C/.android and then running following commands in command prompt
adb kill-server
adb start-server
adb devices

Note that wireless adb connectivity in Android 6.0.0 is broken. Updating to 6.0.1 fixes the issue.
https://stackoverflow.com/a/34530543/1123355

In Windows, if you are using system-wide proxy software like Proxifier, you need to add adb.exe to the ingore list or direct-mode list. In my case, using Proxifier will make adb able to connect to any IP address even when the phone is not connected to the WiFi, and this leads to device offline.

I know its late to answer but I believe this is the exact answer:
go to WIFI setting on your device and "set a new IP" in your network IP range an reconnect.

Conflicting ADB connections can cause this issue as well:
Windows Host with Docker to Hyper-V Android x86 emulator
I didn't see this answer here yet so for those attempting something similar, the issue I had was that the local Windows Host ADB process had already acquired the adb connection during start up (adb server start).
By simply running: adb disconnect <Device/Android x86 Hyper-V ip>:5555
on host machine
Running adb connect <Device/Android x86 Hyper-V ip>:5555 on the Docker container was able to successfully acquire the remote device (aka Android x86 Hyper-V)
IMPORTANT!!! Until you disconnect Docker (or whatever), your host machine (or any others) will not be able to connect, apparently only one ADB connection at a time is allowed.
I didn't need to do anything else listed above. Hope this helps others.

Just turn off your Proxifier or something else like this.
Socks5 works fine

Watever! I'm always using these steps to connect ADB Wifi with android studio
STEP-1:
1. Go to Android studio->Settings-> Plugins -> Search ADB WIFI
2. Install the pluging and restart android studio
STEP-2:
1. Find the location of SDK Manager For ex for my computer
Copy the whole location
Now open Terminal in Android studio itself( This will show in right bottom corner).
type cd YOUR_SDK_LOCATION
type cd platform-tools
Now type adb tcpip 5555
FOR NEXT STEP YOU MUST CONNECT YOUR MOBILE AND LAPTOP WITH SAME WIFI
type adb connect 192.168.6.100:5555 in terminal (Here 192.168.6.100 is your mobile IP Address)
now the message will show like this 'connected to 192.
168.6.100:5555'
STEP -3 :
1.Go to Android studio->Tools->ADB WIFI-> ADB Restart
1.Go to Android studio->Tools->ADB WIFI-> ADB USB to WIFI
Like below
That's it .

In My case my wifi network is not same thats why i am not getting connected with the device.
There is very easy and helpful plugin for this purpose Android Wifi ADB
How to Connect using plugin:
connect device using cable
click on Android wifi adb icon
disconnect your USB connection now your device is connected over wifi.
Enjoy Happy debugging.

adb reconnect offline
adb connect [ip]:[port] (for exemple adb connect 192.168.8.100:44

While all tips with killing ADB server helped me many times, now I got the message:
cannot connect to <IP>:<port>: No connection could be made because the target machine actively refused it. (10061)
It was possible to attach the device only while it was connected with USB, and after disconnecting cable it appeared as offline at the attached devices list.
I have just solved my problem by changing the USB configuration:
Developer options > Select USB Configuration: MTP (Media Transfer Protocol)
PTP (Picture Transfer Protocol) works as well.
Screenshot
I hope it will help.

I have this problem just now. Note that my case is special, the usb has been disabled for security concerns. Reboot not working. This is not ip problem since ping is working and nmap shows 5555 port is open. Also since I will not able to connect if port is wrong, so nothing to do with port.
There are 4 reasons:
Because another pc in the local network already connected, so the other guy have to adb disconnect first, then I can do adb disconnect and adb connect <ip>, since only one person can connect at the same time.
A hotspot ssid name might consists of multiple bssids in (especially you're in office) local network, so you need to ensure your pc try all the hotspot bssids which match the android connected hotspot bssid. Note that I noticed it's not always the case (Now I tried different bssids still success), but it did solved before.
Ensure the port 5555 is open correctly. Even though there are many ways, but you can download this app to open port 5555.
And I just encounter a weird case, client A connect just fine. But then client B turn on wifi and attempt to connect but failed. Then this failure causes original client A no longer able to connect. Reboot device/adb disconnect/adb kill-server doesn't help, and confirmed the ip is same(tested by turn off/on device and observe the ping). I make a joke about client B wifi still turn on may interfere the device wifi. Then I realized Client B disconnect/kill-server is not enough, client B also need turn off wifi to make client A connect. And it did.

Try,
adb disconnect <your_ip_address>:port_number or adb disconnect
eg.
adb disconnect 192.168.1.2:5555
Or
adb disconnect
The difference is that first one will disconnect only the required device, the second one will disconnect all the devices.
The benefit of using this command is that you don't have to kill and restart the server. Killing and restarting the server requires your device to be plugged in to your computer which is most irritating process.

For me the reason is GLOBAL PROXY (A country without international internet). Adb try to connect my device through proxy server.

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!