Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

adb pair or adb connect fails with error 10061 over Wi-Fi

Erroradb reports error 10061 (connection refused) when connecting to the phone over Wi-Fi on Windows

Short 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.

  • Applies to Android Studio current stable, Android SDK Platform-Tools 37 and newer, Android 11 and newer phone, Windows 11
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 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-status
  2. 2Match what you see, then jump to its fix

    1. 1The 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. 2The connection is refused although Wireless debugging is on.The device was never paired, or you used the wrong addressFix
    3. 3adb server-status shows an old version, or a connection that worked yesterday is refused today.The adb server is old or stuckFix
    4. 4The phone never appears by itself; the mDNS service list is empty.The network blocks mDNS, so auto discovery never finds the phoneFix

What does the error look like?

  • adb reports error 10061 (connection refused) when connecting to the phone over Wi-Fi on Windows
  • Wireless 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 -l

2Fix

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

3Verify

After pairing in the next step, the phone shows in adb devices.

adb devices -l

Confirmed by developer.android.com

Did this fix it?

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:37099

2Fix

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:37099

3Verify

The device is listed with the state device.

adb devices

Confirmed by developer.android.com

Did this fix it?

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 version

2Fix

Update Android SDK Platform-Tools in SDK Manager, then restart the adb server.

adb kill-server
adb start-server

3Verify

Pair or connect again.

adb devices

Confirmed by developer.android.com

Did this fix it?

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

2Fix

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

3Verify

The output now contains a tls service with the phone's IP address and port.

adb devices -l

Confirmed by developer.android.com

Did this fix it?

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 fix

Mobile 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 fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.