Wireless ADB paired but not connected? Check the right port
Separate pairing, connection and mDNS discovery, verify the current endpoint and avoid assuming every wireless debugging service uses port 5555.
“Successfully paired” does not mean an active debugging connection exists. Android wireless debugging separates pairing from connection. Check which port you are using before repeatedly trying to connect to the pairing endpoint.
This guide covers the phone's wireless-debugging pairing workflow, using documentation checked on September 16, 2026. It is not the same as a device with a preconfigured fixed TCP debugging port, nor does it imply every mirroring tool supports this workflow. No devices were operated or tested for this article.
Distinguish the endpoints
AOSP describes separate pairing and TLS connection services, discovered as _adb-tls-pairing and _adb-tls-connect. Legacy adb tcpip is a different service type. Sharing a Wi-Fi transport does not make the modes interchangeable. AOSP architecture
| Item | Purpose |
|---|---|
| Address, port and code in the pairing dialog | Pair the workstation with the phone |
| Wireless-debugging connection address and port | Establish the actual debugging connection |
| Discovery results | Locate services; they do not replace checking connection status |
Use the information currently displayed on the phone rather than treating an old port as permanent configuration.
Check the shortest path first
Android documents this wireless-debugging workflow for phones running Android 11 or later, with the workstation and phone on the same wireless network and up-to-date SDK Platform Tools. Official setup guidance
Operate only on devices you own or are authorized to debug. These commands contain placeholders that must be replaced:
adb version
adb pair PHONE_IP:PAIRING_PORT
adb devices -l
Enter the code shown by the phone when prompted. If the target is already connected normally, do not reconnect merely to finish a checklist. If pairing succeeded but the target is missing, obtain the current connection endpoint and try:
adb connect PHONE_IP:CONNECTION_PORT
adb devices -l
The command manual assigns pairing to pair, TCP/IP connection to connect, and device listing to devices -l. Omitting the port from connect defaults to 5555; that does not make 5555 the phone's wireless-debugging port. Specify the actual port. ADB command manual
This is a diagnostic sequence, not a promise that every ROM presents identical menus or behavior.
Manual connection works, but discovery does not
ADB uses mDNS for wireless automatic discovery. If an explicit connection succeeds while automatic connection fails, investigate discovery before deleting the pairing. Current Android documentation includes newer ADB diagnostics; do not apply version-specific commands or settings blindly to older tools. Wireless troubleshooting
Start with adb help for the installed tool's supported mDNS commands. Record its version, whether the connection service appears, and the manual connection result. An empty discovery result establishes only that no result was obtained at that moment. Check whether the phone is advertising, the tool configuration and the network before declaring a phone fault.
Preserve the failing stage instead of resetting everything
Change one condition at a time:
- Pairing failure: retain that error and check the current pairing dialog, not video settings.
- Connection failure after pairing: record whether you used the pairing or connection port.
- ADB connected but no picture: move on to the mirroring service; connection is only one checkpoint.
- Several desktop tools: identify their ADB versions and server configurations before changing shared components.
Do not expose debugging ports directly to the public internet for convenience. Keep pairing codes and full connection details out of public reports. System and tool versions, the failing stage and a redacted error are a much better starting point than repeated resets.