ADB Over Wi-Fi: Connect an Android Device Without a Cable

To use ADB over Wi-Fi, connect the phone by USB once, run adb tcpip 5555, unplug the cable, then run adb connect <phone-ip>:5555. Your computer and phone must be on the same network. Android 11 and newer also offer a built-in Wireless debugging mode that uses a pairing code and needs no cable at all.

Before you start

• USB debugging must be enabled on the phone. See how to enable USB debugging if you have not done that.
• The computer and the phone must be on the same local network. Guest networks and some public Wi-Fi block device-to-device traffic.
• You need the Android platform tools (adb) on your computer for the command-line method.

Method 1: The classic method (adb tcpip)

This works on any Android version with USB debugging.

1. Connect the phone with a USB cable and confirm it is authorized:

adb devices

1. Switch the device's ADB daemon to TCP/IP mode on port 5555:

adb tcpip 5555

You should see restarting in TCP mode port: 5555.

1. Find the phone's IP address (see the next section).
2. Unplug the cable and connect over the network:

adb connect 192.168.1.42:5555

Replace the address with your phone's. A successful run prints connected to 192.168.1.42:5555.

1. Check it:

adb devices

The device now appears as 192.168.1.42:5555. All the usual commands work as if it were plugged in.

To disconnect, run adb disconnect 192.168.1.42:5555. TCP mode is not permanent: it resets when the phone reboots.

Finding your phone's IP address

• On stock Android: Settings > About phone > Status information (or Status) and look for IP address. Alternatively open the connected Wi-Fi network's details in Settings > Network & internet > Internet.
• From the computer, while the phone is connected by USB:

adb shell ip route

The address after src on the wlan0 line is the phone's IP.

Menu names vary between manufacturers, but the IP address is always shown somewhere under the Wi-Fi network details or the phone's status page.

Method 2: Wireless debugging (Android 11 and newer)

Android 11 added a pairing-based mode that needs no cable.

1. Open Settings > System > Developer options and enable Wireless debugging (the phone must be on Wi-Fi).
2. Tap Wireless debugging, then Pair device with pairing code. The phone shows an IP address, a port and a six-digit code.
3. On the computer, pair using that pairing port:

adb pair 192.168.1.42:37123

Type the six-digit code when asked.

1. Back on the main Wireless debugging screen, note the IP address and port shown there (this is a different port from the pairing one) and connect:

adb connect 192.168.1.42:41567

The port changes, so you may need to check it each time the setting is toggled.

Security: read this before leaving it on

Warning: An open ADB-over-TCP port can be reached by anyone on the same network, and an attacker who reaches it can attempt to talk to your phone. Use it only on trusted networks such as your home or office, never on public Wi-Fi.

Android still asks for RSA key authorization the first time a computer connects, which is a safeguard, but you should not rely on it alone. When you are done:

adb usb

This switches the device back to USB mode. Rebooting the phone also resets classic TCP mode, and you can turn off Wireless debugging in Developer options.

Using ADB over Wi-Fi in ADBKit

A web browser cannot open raw TCP connections, so it cannot reach port 5555 on its own. ADBKit solves this with a small helper that runs on your computer and relays the traffic. It needs Node.js. The full setup, options and troubleshooting are in the ADBKit Wi-Fi helper reference.

1. Download the helper, adbkit-bridge.mjs, and start it from the folder where you saved it:

node adbkit-bridge.mjs

1. Connect the phone by USB in the ADBKit workspace and open the Wi-Fi dialog.
2. Press Turn on Wi-Fi debugging. ADBKit runs adb tcpip 5555 for you and shows the phone's address.
3. Connect by typing the IP address (port 5555), or use Scan network to find devices.

The helper listens on 127.0.0.1 only, answers only ADBKit pages and only connects to private network addresses, so it is not a general-purpose open proxy.

Note: ADBKit currently supports the classic adb tcpip 5555 method. The Android 11+ Wireless debugging pairing-code flow (adb pair) is not supported yet. If your phone only offers Wireless debugging, use the USB step above to enable TCP/IP mode first.

Troubleshooting

• failed to connect or timeout. Confirm both devices are on the same network and the IP address is current; routers can change it. Some networks isolate clients from each other.
• unauthorized after connecting. Unlock the phone and accept the debugging prompt. If it still fails, revoke authorizations in Developer options and try again.
• Connection drops. Wi-Fi sleep settings and weak signals interrupt sessions. Reconnect with adb connect.
• The device is busy. Only one program can use a connection at a time. See fixing ADB device busy or unauthorized errors.

If you want to understand why browsers need a helper for TCP while USB works directly, read what WebADB is.