How to Enable ADB Over Wi‑Fi on Android (No USB Cable Required)

Why ADB Over Wi‑Fi?

Android Debug Bridge (ADB) is the standard tool developers and power users use to communicate with a device from a computer. By default it works over a USB cable, which is reliable but can become cumbersome when you need to test an app repeatedly, install many builds, or run shell commands while the phone is charging on a desk. Enabling ADB over Wi‑Fi removes the cable, lets you keep the device in a natural position, and speeds up the iterative workflow.

From a security perspective, ADB over Wi‑Fi is not a permanent configuration. It opens a network port that any device on the same subnet could try to access. The tutorial therefore emphasizes how to enable it safely, verify the connection, and disable it when you are done.

Before You Start

• Computer: Windows, macOS, or Linux with the Android SDK platform‑tools installed. If you don’t have them, download the platform-tools zip from the official Android developers site and add the folder to your system PATH.
• Android device: Running Android 5.0 (Lollipop) or newer. The steps are identical on most manufacturers, though menu wording may differ slightly.
• Network: Both the computer and the phone must be connected to the same Wi‑Fi network (same subnet). Avoid guest networks that isolate clients.
• Battery: Keep the phone plugged in or ensure at least 50 % charge. Enabling ADB over Wi‑Fi does not consume much power, but a sudden shutdown could leave the device in an unexpected state.
• Backup: No data will be altered by this process, but it is good practice to have a recent backup in case you later decide to reset developer options.

Step‑by‑Step Procedure

Verifying the Connection

Run a harmless command to confirm you have full control, for example:

adb -s 192.168.1.42:5555 shell getprop ro.product.model

The output should be the model name of your phone (e.g., Pixel 6). If you get an error like “device offline” or “no such device”, double‑check the IP address and ensure the phone is still on the same Wi‑Fi network.

Alternative: Native Wireless Debugging (Android 11+)

Starting with Android 11, Google introduced a built‑in “Wireless debugging” option that avoids the temporary USB step. The workflow is slightly different but offers a QR‑code pairing method.

Keeping the Connection Alive Across Reboots

By default, the TCP/IP listener stops when the device reboots or when you manually turn off USB debugging. If you need a persistent Wi‑Fi ADB session (e.g., for a development workstation that stays on), consider one of the following approaches:

• Automation app (Tasker/Automate): Create a profile that runs the shell command setprop service.adb.tcp.port 5555; stop adbd; start adbd on boot. This requires the “Run Shell” action with root or the “Grant permission” option via ADB.
• Permanent ADB over Wi‑Fi apps: Some Play Store apps (e.g., “ADB Wireless”) use the same adb tcpip command internally and can be set to auto‑start. They still need the initial USB pairing.
• Wireless debugging (Android 11+): The pairing persists until you toggle the option off, even after a reboot.

Remember that leaving the port open permanently exposes your device to anyone on the same network. Only use these tricks on trusted home or office Wi‑Fi.

Troubleshooting Common Issues

1. “device offline” or “cannot connect to 192.168.x.x:5555”

• IP mismatch: Phones often switch between 2.4 GHz and 5 GHz bands, which may be on different subnets. Verify the IP after each reconnection.
• Firewall blocking port 5555: Some routers or Windows Defender firewalls block inbound connections on uncommon ports. Add an exception for adb.exe or open port 5555 in the router’s settings.
• ADB version mismatch: Ensure the adb binary on your PC is from the same SDK version as the device’s Android version (usually not a problem, but older platform‑tools can misbehave).

2. “cannot bind to port” when running adb tcpip

This occurs if another process is already listening on the chosen port. Choose a different port, e.g., adb tcpip 5556, and use the same port for the adb connect command.

3. Device disappears after Wi‑Fi sleep

Many phones turn off Wi‑Fi during deep sleep to save battery. Disable the “Wi‑Fi optimization” or “Turn off Wi‑Fi during sleep” option in the Wi‑Fi settings, or keep the screen on while debugging.

4. RSA key prompt reappears after each connection

If you repeatedly see the “Allow USB debugging?” dialog, the device’s stored ADB keys have been cleared (common after a factory reset). Accept the prompt once and the key will be stored until you manually revoke it under Developer options > Revoke USB debugging authorizations.

Security Considerations

Enabling ADB over Wi‑Fi is convenient, but it also widens the attack surface:

• Network exposure: Anyone on the same subnet can attempt to connect. Always disable the feature when you are done (adb disconnect and toggle USB debugging off).
• Authentication: ADB uses RSA keys for authentication. The first connection requires you to approve the fingerprint on the phone. Do not approve unknown requests.
• Port forwarding: If you use a VPN that routes traffic through the same subnet, the ADB port could be reachable from remote locations. Keep Wi‑Fi debugging off when using public or untrusted networks.

For the highest security, use the native “Wireless debugging” feature on Android 11+; it generates a temporary pairing code and does not keep a persistent open port.

Cleaning Up – Turning Off ADB Over Wi‑Fi

1. On the computer, run adb disconnect 192.168.1.42:5555 (replace with your IP).
2. On the phone, go back to Developer options and toggle USB debugging off, or simply turn off Wireless debugging if you used the Android 11 method.
3. If you used adb tcpip, you can also revert to USB‑only mode by running adb usb while the phone is still connected via USB.

These steps close the network port and prevent accidental remote access.

Putting It All Together – A Real‑World Example

Imagine you are developing a UI‑intensive app on a Pixel 6 running Android 13. You need to test layout changes dozens of times per day. Instead of plugging and unplugging the device, you follow the tutorial above:

1. Enable Developer options and USB debugging once.
2. Connect via USB, run adb tcpip 5555.
3. Find the phone’s IP (192.168.0.101) and run adb connect 192.168.0.101:5555.
4. Leave the phone on the desk, keep the Wi‑Fi on, and continue issuing adb install, adb logcat, and adb push commands without ever touching the cable.
5. When the workday ends, run adb disconnect 192.168.0.101:5555 and turn off USB debugging.

The workflow saves you minutes per build, reduces wear on the USB port, and keeps your desk tidy.

Final Checklist

• Enable Developer options and USB debugging.
• Connect once via USB and run adb tcpip 5555.
• Note the device’s Wi‑Fi IP address.
• Connect from PC with adb connect <IP>:5555.
• Verify with a simple adb shell getprop command.
• Disable the feature after you finish (adb disconnect + toggle off).

Following these steps gives you a reliable, cable‑free ADB experience while keeping your device secure.