Connect Android With Wireless Debugging From the Browser
Pair and connect an Android 11+ phone over Wi-Fi in ADBKit with the 6-digit pairing code, no cable. Step by step, plus fixes for expired codes and changed ports.
To connect an Android 11+ phone to ADBKit over Wi-Fi with no cable, start the ADBKit agent on your computer, turn on Wireless debugging on the phone, choose Pair device with pairing code, type the 6-digit code into ADBKit, then press Connect. You pair once; afterwards ADBKit reconnects without a code.
What you need
- A phone running Android 11 or newer, on the same Wi-Fi network as your computer. Guest networks and routers with "client isolation" block it.
- Developer options enabled. If you have not done it, see how to enable USB debugging; the first steps are the same.
- Chrome or Edge on desktop, opened on the ADBKit workspace.
- The Go edition of the ADBKit agent. The Node script cannot pair, because pairing needs a cryptographic handshake and a TLS client certificate that the Node edition does not implement.
Step 1: Start the ADBKit agent
A web page cannot do mDNS discovery or TLS client certificates, so a small program on your computer does it for the tab. Install and run it:
macOS and Linux:
curl -fsSL https://adbkit.com/install.sh | shWindows (PowerShell):
irm https://adbkit.com/install.ps1 | iexLeave the window open. The script verifies a checksum, needs no administrator rights and sends no telemetry. Details, security model and alternatives are in the ADBKit agent reference.
Step 2: Turn on Wireless debugging on the phone
- Open Settings > System > Developer options (the path varies by manufacturer).
- Switch on Wireless debugging and confirm the prompt for the current network.
- Tap the Wireless debugging entry itself to open its screen.
Step 3: Open the pairing screen
On the Wireless debugging screen tap Pair device with pairing code. The phone shows a 6-digit code and an address such as 192.168.1.42:37011. Keep this dialog open: the code and its port only exist while it is visible, and it expires after a short time.
Step 4: Pair in ADBKit
- In ADBKit choose Connect over Wi-Fi and the Wireless debugging option.
- ADBKit checks that the agent is running and supports pairing, then looks for the phone on the network. With the pairing dialog open it should list your phone under pairing.
- Select it, or type the address and port shown on the phone, then enter the 6-digit code.
- When ADBKit reports that pairing succeeded, the phone lists your computer under Paired devices.
Step 5: Connect
Close the pairing dialog. Back on the main Wireless debugging screen the phone shows an IP address and port for connecting (a different port from the pairing one). ADBKit finds it automatically; choose your phone and connect. Because the agent already holds a paired key, you do not get the usual "Allow USB debugging" prompt this time. The device screen and tools open as they would over USB.
The same thing with the adb command line
If you have the Android platform tools, the equivalent is:
adb pair 192.168.1.42:37011Type the 6-digit code when asked, then connect using the other port:
adb connect 192.168.1.42:41567The first command uses the pairing port and code; the second uses the connect port from the main Wireless debugging screen. Run adb devices to confirm. See ADB over Wi-Fi for the classic cable-first method.
When something goes wrong
| Problem | Cause | Fix |
|---|---|---|
| Pairing says the code is wrong | A typo, or the dialog was reopened and the code changed | Read the current code again, type all six digits, and try once more. A new dialog means a new code |
| The code expired, or ADBKit cannot reach the pairing port | The pairing dialog closed or timed out | Tap Pair device with pairing code again, then retry quickly with the new code and port |
| The connect port changed | The port is random and changes whenever Wireless debugging is toggled or the phone reconnects | Use the address currently shown on the main Wireless debugging screen, or let ADBKit rediscover it |
| ADBKit does not find the phone | Different network, client isolation, or the agent is blocked by a firewall | Check both are on the same Wi-Fi, turn off isolation, allow the agent on private networks |
| ADBKit says this agent cannot pair | You started the Node script | Run the one-line installer to get the Go agent |
| It connects, then asks to pair again | The phone forgot the pairing, for example after you removed the computer from Paired devices | Pair again from step 3 |
| Wireless debugging turns itself off | Android disables it when you leave the Wi-Fi network, and some phones after a reboot | Turn it on again and reconnect |
More agent-specific fixes (blocked origin, Windows antivirus, macOS Gatekeeper) are in the agent troubleshooting table. To decide between this and the older method, read adb tcpip vs Wireless debugging.
Stay safe
Wireless debugging only talks to computers you have paired, but a phone with it switched on is still reachable on the network. Use it on networks you trust, never on public Wi-Fi, and turn it off when you are done. You can revoke a computer at any time under Paired devices.