How to Set Up ADB Over Wi‑Fi on Android (No Root)

Why this matters: USB debugging opens a privileged channel that ADB uses to issue commands. Without it, the PC cannot talk to the phone at all.

Step 2 – Connect the phone via USB for the first pairing

adb devices

XXXXXX    device

Step 3 – Find the phone’s IP address

Why you need it: ADB over Wi‑Fi works by opening a TCP socket on port 5555 on the phone. The PC must know the exact IP to reach that socket.

Step 4 – Enable the wireless ADB listener

adb tcpip 5555
adb connect 192.168.1.42:5555

connected to 192.168.1.42:5555

Step 5 – Verify the wireless connection

192.168.1.42:5555   device

Step 6 – Common use cases over Wi‑Fi

Once the wireless link is alive, you can use any regular ADB command. Below are a few practical examples that illustrate why many developers and power‑users keep the connection alive.

6.1 – Pull a file from the device

adb pull /sdcard/Download/example.pdf ~/Desktop/

The file is copied to your PC without ever plugging the phone in.

6.2 – Install an APK

adb install myapp.apk

Great for testing builds on a device that sits on a bench.

6.3 – Record the screen

adb shell screenrecord /sdcard/demo.mp4
# After you stop the recording (Ctrl‑C), pull the file:
adb pull /sdcard/demo.mp4 .

This works exactly as with a wired connection, but you can start the recording from your laptop while the phone stays on a stand.

6.4 – Run a shell command

adb shell dumpsys battery

Useful for quick diagnostics when you’re already at your workstation.

Step 7 – Disconnecting safely

adb usb

Troubleshooting

Wireless ADB is reliable, but a few network or device quirks can break the flow. Below are the most frequent symptoms and how to resolve them.

7.1 – adb connect … failed: timed out

• Check the Wi‑Fi network. Both PC and phone must be on the same subnet (e.g., 192.168.1.x). If you have a dual‑band router, verify that both devices are on the same band (2.4 GHz vs 5 GHz) because some routers treat them as separate networks.
• Disable AP isolation. Some guest networks block client‑to‑client traffic. Switch to a regular LAN network or disable the isolation setting in the router admin UI.
• Confirm the IP address. Android can change its IP after a Wi‑Fi toggle or a router reboot. Re‑run the “Find IP address” step.
• Firewalls. Windows Defender Firewall or third‑party security suites may block outbound traffic on port 5555. Add an outbound rule allowing adb.exe to communicate on that port.

7.2 – Device shows as offline

• Run adb kill-server then adb start-server on the PC.
• On the phone, go to Developer options and toggle USB debugging off and on again. This restarts the adbd daemon.
• If the problem persists, repeat the adb tcpip 5555 command while the phone is still connected via USB, then reconnect.

7.3 – Battery drain concerns

• After finishing your session, run adb usb to disable the TCP listener.
• On some devices (e.g., Samsung One UI) the Wi‑Fi ADB socket stays open for a few minutes even after adb usb. If you notice a noticeable drain, simply reboot the phone or toggle “USB debugging” off for a few seconds.

7.4 – “Permission denied” when pulling files

• ADB runs with the same permissions as the shell user on the device, which cannot access files in /data/data unless the device is rooted. Stick to files under /sdcard or use run-as <package_name> for debug builds you own.

Alternative methods (when the standard approach fails)

Some manufacturers ship a custom “Wireless debugging” toggle inside Developer options (e.g., Pixel devices on Android 11+). If your phone offers this option, you can skip the USB pairing entirely:

1. Open Developer options.
2. Find Wireless debugging and enable it.
3. Tap the Pair device with pairing code button. The phone will display an IP address, a port, and a 6‑digit pairing code.
4. On the PC, run:

adb pair IP:port
# Enter the 6‑digit code when prompted

After pairing, connect with adb connect IP:5555. This flow is officially supported from Android 11 onward and works on most stock Android devices.

Security considerations

• Local network only. ADB has no authentication beyond the initial USB pairing. Anyone on the same Wi‑Fi network could potentially connect to your device if the TCP listener is left open. Always disable it when you’re done.
• Use a strong router password. Prevent rogue devices from joining your network.
• Avoid public Wi‑Fi. Never enable wireless ADB on a coffee‑shop network; the risk of interception is high.

Wrap‑up

Setting up ADB over Wi‑Fi gives you the flexibility of a wired debugging session without the cable clutter. By following the steps above you’ll be able to install apps, pull logs, record the screen, and run shell commands from any workstation on the same network. Remember to re‑disable the wireless listener when you’re finished to keep battery life high and the device secure.

With this knowledge you can now integrate Android devices into your regular development workflow, automate testing on a bench of phones, or simply transfer files quickly when a USB port isn’t handy.