Home Page » News » Tutorials » How to Set Up Wireless ADB (ADB over Wi‑Fi) on Android Without Root

Set Up Wireless ADB (ADB over Wi‑Fi) on Android Without Root

8 min read Learn how to enable ADB over Wi‑Fi on any Android device without rooting. Follow step‑by‑step instructions, see expected results, and troubleshoot common issues. September 26, 2026 17:03

Wireless ADB lets you run adb commands over the same Wi‑Fi network your computer and Android device share. It removes the need to keep a USB cable attached, which is handy for debugging apps, pulling logs, or issuing shell commands while the device is on a test bench.

Why use wireless ADB? It speeds up iterative development, lets you work on devices that are physically hard to reach (e.g., a TV box or a kiosk), and simplifies screen‑recording or UI‑automation setups that need the device to stay in place.

Before you start

Android 4.2+ (most modern devices support the feature).
A computer with Android Platform‑Tools installed.
Both the PC and the Android device must be on the same Wi‑Fi network.
Charge the device or keep it plugged in – wireless ADB can drain the battery faster than normal use.
Be aware that enabling ADB over Wi‑Fi opens a port (5555 by default) that could be accessed by anyone on the same network. Only use trusted networks and disable the feature when finished.

Step‑by‑step setup

1. Enable Developer Options

Open Settings → About phone. Scroll to Build number and tap it seven times. You’ll see a toast confirming that Developer options are now enabled.

On some manufacturers (e.g., Samsung, Xiaomi) the path may be Settings > Software information > Build number.

2. Turn on USB debugging

Return to the main Settings screen, then go to System → Developer options. Locate USB debugging and toggle it on. Confirm any security prompt that appears.

Warning: USB debugging grants a computer full access to your device. Only enable it when you trust the connected PC.

3. Connect the device via USB and authorize the computer

Plug the phone into the PC with a USB cable. On the phone, a dialog Allow USB debugging? will appear. Check Always allow from this computer and tap OK.

Open a command prompt (or terminal) on the PC and verify the connection:

adb devices

You should see a line like 0123456789ABCDEF device. If you see unauthorized, repeat the previous step.

4. Switch ADB to TCP/IP mode

With the USB connection still active, run:

adb tcpip 5555

The command tells the device’s ADB daemon to listen on port 5555 for network connections. You’ll get a confirmation like restarting in TCP mode port: 5555.

5. Find the device’s IP address

On the Android device, go to Settings → Network & internet → Wi‑Fi. Tap the connected network, then look for IP address. Note the IPv4 address (e.g., 192.168.1.42).

If you prefer a command‑line method, you can also run:

adb shell ip -f inet addr show wlan0

Look for the line containing inet – the number after it is the IP.

6. Connect ADB over Wi‑Fi

Disconnect the USB cable. In the terminal, execute:

adb connect 192.168.1.42:5555

Replace 192.168.1.42 with the IP you noted. A successful connection returns connected to 192.168.1.42:5555.

7. Verify the wireless connection

Run adb devices again. You should now see the device listed with its IP address instead of the USB serial number:

192.168.1.42:5555	device

You can now issue any usual ADB commands (e.g., adb logcat, adb install myapp.apk) without a cable.

Optional: Keep the connection alive or disable it

Automatic reconnection: Some developers prefer to leave the device in TCP mode. If you reboot the phone, you’ll need to repeat steps 4‑6 because the ADB daemon reverts to USB‑only mode.
Disable when finished: For security, run adb usb on the PC to switch the daemon back to USB mode, then unplug the cable. This closes the open port.

Troubleshooting

Common issue: "cannot connect to 192.168.1.42:5555"

Same network? Ensure both devices are on the exact same Wi‑Fi SSID. Guest networks or VLANs often isolate clients.
Firewall blocking port 5555? Some routers have client‑isolation or firewall rules. Temporarily disable them or use a different router.
IP address changed? Wi‑Fi DHCP can assign a new address after a reboot. Re‑check the IP in Settings.
ADB version mismatch? Older platform‑tools may not support adb tcpip on newer Android releases. Update to the latest Platform‑Tools package.

Issue: "device unauthorized" after wireless connect

If you see unauthorized when running adb devices, reconnect the USB cable, re‑authorize the PC, then repeat step 4.

Security considerations

Opening port 5555 effectively gives anyone on the same Wi‑Fi network the ability to control your device. To mitigate risk:

Only enable wireless ADB on trusted networks (home or lab).
Disable the feature (run adb usb or toggle USB debugging off) when not in use.
Consider using a static IP and a firewall rule on the PC to restrict connections to that address only.

When you no longer need wireless ADB, turn off USB debugging in Developer options. This closes the listening socket and restores the default security posture.

What you’ve achieved

By following this guide you now have a fully functional wireless ADB setup that works without rooting your device. You can debug apps, pull logs, install builds, or run shell commands from anywhere on your LAN, all while keeping the process secure and reversible.

User Comments (0)

Add Comment

No comments added yet.

Add Comment

Your Name: *

Comment Title: *

Your E-mail: * We'll never share your email with anyone else.

Your Comment: *

Comments will not be approved to be posted if they are SPAM, abusive, off-topic, use profanity, contain a personal attack, or promote hate of any kind.