adb pair or adb connect fails with error 10061 over Wi-Fi
adb reports error 10061 (connection refused) when connecting to the phone over Wi-Fi on WindowsShort answer
Error 10061 means the phone's address refused the TCP connection. For adb wireless debugging that usually means Wireless debugging is off or the phone is on another network, the pairing step was skipped or used the wrong address, or the adb server is old or stale. Check the prerequisites, pair once with adb pair, then check adb devices.
Fix it fast
1Find out which cause you have
Ask adb about its own state. The output shows the adb version and whether device discovery over the network (mDNS) is on.
adb server-status2Match what you see, then jump to its fix
- 1
The connect attempt is refused at once, and Wireless debugging on the phone is off or shows a different Wi-Fi network.Wireless debugging is off, or the phone and computer are on different networksFix - 2
The connection is refused although Wireless debugging is on.The device was never paired, or you used the wrong addressFix - 3
adb server-status shows an old version, or a connection that worked yesterday is refused today.The adb server is old or stuckFix - 4
The phone never appears by itself; the mDNS service list is empty.The network blocks mDNS, so auto discovery never finds the phoneFix
- 1
What does the error look like?
adb reports error 10061 (connection refused) when connecting to the phone over Wi-Fi on WindowsWireless debugging device not listed by adb devices
Cause 1 of 4
Wireless debugging is off, or the phone and computer are on different networks
1Check
Wireless debugging needs a phone with Android 11 (API 30) or higher on the same wireless network as the workstation. A guest or isolated Wi-Fi often blocks device-to-device traffic.
adb devices -l2Fix
Join both devices to the same ordinary Wi-Fi network, then switch Wireless debugging on in Developer options.
# on the phone: Settings > Developer options > Wireless debugging > On
adb devices -l3Verify
After pairing in the next step, the phone shows in adb devices.
adb devices -lConfirmed by developer.android.com
Cause 2 of 4
The device was never paired, or you used the wrong address
1Check
A device must be paired once with a pairing code. The IP address, port and code come from the Pair device with pairing code screen, and they change each time you open it.
adb pair 192.168.1.20:370992Fix
On the phone choose Pair using pairing code, run adb pair with the address and port shown there and type the pairing code when prompted. In Android Studio you can instead use the Pair devices over Wi-Fi dialog and scan the QR code.
adb pair 192.168.1.20:370993Verify
The device is listed with the state device.
adb devicesConfirmed by developer.android.com
Cause 3 of 4
The adb server is old or stuck
1Check
The documentation asks you to check that adb server-status shows a current version, and to update SDK Platform-Tools if it does not.
adb version2Fix
Update Android SDK Platform-Tools in SDK Manager, then restart the adb server.
adb kill-server
adb start-server3Verify
Pair or connect again.
adb devicesConfirmed by developer.android.com
Cause 4 of 4
The network blocks mDNS, so auto discovery never finds the phone
1Check
adb relies on mDNS to discover paired devices automatically. Run the command with Wireless debugging on and look for a tls service with the phone's IP address and port. The Android documentation says an empty output means the network does not support mDNS.
adb mdns track-services --proto-text2Fix
Use a network that allows mDNS, such as a different Wi-Fi network or a phone hotspot, then pair again.
adb mdns track-services --proto-text3Verify
The output now contains a tls service with the phone's IP address and port.
adb devices -lConfirmed by developer.android.com
How do I stop it coming back?
- Keep Platform-Tools current, as the Android documentation advises for wireless debugging.
- Use one trusted home or office network for the phone and the computer.
- Pair once; the Android documentation says the device stays paired until you forget it, so do not repeat the pairing step.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
Related fixes
Mobile apps
A phone is plugged in over USB but Android Studio and adb do not list it
adb devices prints List of devices attached with nothing below it
adb lists a phone only when four things hold: USB debugging is on, you accepted the computer's RSA key on the phone, the computer has a driver or udev rule for the device, and the cable carries data to a running adb server.
6 causes, each with a fixMobile apps
adb cannot start because something already holds its port
adb start-server failed
The adb server must bind local TCP port 5037, and every adb client talks to it there.
2 causes, each with a fixMobile apps
The phone shows as unauthorized and Android Studio will not run the app
adb devices lists the phone but Android Studio cannot deploy to it
An unauthorized phone means it has not trusted this computer's RSA key.
3 causes, each with a fixMobile apps
Android Studio cannot pair the phone over Wi-Fi
The Pair devices over Wi-Fi dialog lists no device
Wireless pairing needs the phone on Android 11 or higher and on the same Wi-Fi network as the computer, with current Platform-Tools.
4 causes, each with a fixMobile apps
adb cannot connect to its daemon or start the server
* daemon started successfully *
The adb server is a background process on your computer that listens on TCP port 5037.
2 causes, each with a fixMobile apps
adb prints 'server version doesn't match this client; killing...'
adb server version doesn't match this client; killing...
adb runs a background server, and every adb command is a client.
3 causes, each with a fix