How to set up wireless ADB on Windows
Wireless ADB lets you debug, install APKs, and mirror your screen without a USB cable. The setup process changed significantly in Android 11 — here's how to do it the right way on every Android version.
On Android 11+: Settings → Developer Options → Wireless debugging → Pair device with pairing code. On Windows: open Terminal and run adb pair <ip>:<port>, then enter the 6-digit code shown on your phone.
Wireless ADB only works when the phone and the PC sit on the same Wi-Fi network and can reach each other directly. Two things quietly break this: a VPN active on either device, and AP/client isolation (sometimes called "guest network" or "AP isolation") on the router, which blocks devices from seeing one another. Turn both off before you begin. You'll also need ADB platform-tools on the PC, or a GUI like Andora that bundles it.
From Android 11 onward you pair once with a 6-digit code, then connect over Wi-Fi — no cable at any point:
192.168.1.42:37245).adb pair 192.168.1.42:37245
# enter the 6-digit code shown on the phone
adb connect 192.168.1.42:5555
Note the connect port differs from the pairing port — use the IP:port shown at the top of the Wireless debugging screen (not the pairing dialog) for adb connect. Andora reads both for you and pairs in one tap.
Older Android has no pairing screen, so you bootstrap wireless mode over a one-time USB connection:
adb devices lists it as device (authorize it if prompted).adb tcpip 5555.adb tcpip 5555
adb connect 192.168.1.42:5555
You'll need to repeat adb tcpip after a reboot, because the phone reverts to USB mode on restart.
If the connection keeps dying or adb devices shows the Wi-Fi device as offline, it's almost always one of these:
adb connect.For a deeper dive on the offline state itself, see our ADB device offline guide.
Andora ships a one-tap wireless setup wizard that detects your device on the LAN, prompts for the pairing code, and persists the connection across reboots — no manual adb tcpip, no hunting for IP and port. Once paired you can install APKs, mirror the screen, and browse files over Wi-Fi.
On Android 11 and newer, no — you can pair entirely over Wi-Fi using Wireless debugging → "Pair device with pairing code". On Android 10 and below you need one initial USB connection to run adb tcpip 5555, after which you can unplug and connect over Wi-Fi.
Put the phone and PC on the same network, enable Wireless debugging in Developer options, then either pair with a code (Android 11+) or run adb tcpip 5555 followed by adb connect <phone-ip>:5555. The IP and port are shown under Wireless debugging.
Wireless ADB drops when the phone sleeps, switches networks, or the router isolates clients. Disable battery optimization for the connection, keep the screen awake while debugging, turn off AP/client isolation on the router, and reconnect with adb connect. A 2.4/5 GHz band switch can also force a reconnect.
For commands and APK installs it's only marginally slower and depends on Wi-Fi quality; for screen mirroring, USB is noticeably smoother. Wireless is ideal for quick installs and logcat without a cable, while heavy mirroring or large transfers are better over USB.
The adb tcpip mode resets when the phone reboots, so you'll need to re-enable it (Android 10 and below) or re-pair. Android 11+ Wireless debugging remembers paired devices but may require toggling it back on after a restart.
Andora wraps ADB in a clean Windows GUI — drag-drop APK installer, wireless setup, screen mirroring, and one-click fixes for the errors above.
Download Andora