How to connect ADB over Wi-Fi: A complete guide with commands and tips

Debugging Android devices via ADB over Wi-Fi — is a convenient alternative to a wired connection that saves time and eliminates the need to constantly reconnect a cable. This is especially relevant for developers, testers, or simply advanced users who frequently work with Android Debug BridgeBut how do you set up such a connection correctly, what commands should you use, and what pitfalls might arise?

Many people mistakenly believe that wireless ADB debugging It only works on newer versions of Android or requires root access. In reality, this functionality is available on almost all devices starting from Android 11, and there are workarounds for older versions. In this article, we'll cover all connection methods, including Google's official method and alternative solutions for older smartphones.

If you've never used ADB before, don't worry—we'll explain every step in detail. Experienced users will also find some rare tips on troubleshooting common errors like "device unauthorized" or "cannot connect to port."

What is ADB and why do I need Wi-Fi debugging?

ADB (Android Debug Bridge) is a command-line tool that allows you to manage your Android device from your computer. It allows you to install apps, retrieve logs, change system settings, and even unlock certain features not available through the standard interface.

Traditionally ADB works through USB-cable, but starting from Android 11 Google has added official support for wireless connectivity. This means that after the initial setup, you can control the device without a physical connection—just ensure your smartphone and computer are on the same Wi-Fi network.

Advantages of wireless ADB:

• 🔌 No need for cable - convenient for frequent connection/disconnection.
• 📱 Less wear on the USB connector on the device.
• 🚀 Quick testing applications without a permanent connection.
• 🔄 Ability to work with multiple devices simultaneously.

However, the method also has its limitations. For example, The first connection still requires a USB cable to authorize the device. (The exception is some custom firmware.) Wireless ADB can also be less stable than wired, especially on congested networks.

Preparation: What you need to connect ADB over Wi-Fi

Before you begin setting up, make sure you have everything you need:

1. Computer with installed ADB and Fastboot (Part Android SDK Platform Tools).
2. Android device with OS version not lower Android 5.0 (for older versions additional steps will be required).
3. USB cable (for first connection only).
4. Shared Wi-Fi network — the computer and smartphone must be connected to the same router.

If ADB Not installed yet, download Platform Tools Download the archive from Google's official website and unzip it to a convenient folder. For Windows, you may also need to install drivers for your device (they are usually installed automatically the first time you connect via USB).

Install Android SDK Platform Tools|Enable developer mode on your smartphone|Connect the device via USB and authorize debugging|Make sure your computer and smartphone are on the same Wi-Fi network-->

You need to enable it on your device developer mode And USB debuggingTo do this:

1. Go to Settings → About phone.
2. Find the item Build number and click on it 7 times until the notification "You are now a developer" appears.
3. Go back to the main settings and open the new section For developers.
4. Activate the option USB debugging.

⚠️ Attention: On some devices (eg. Xiaomi, Huawei) additionally required to be enabled USB debugging (security settings) in the developer section and confirm permission to connect when you first connect to the computer.

Official Method: Connecting ADB over Wi-Fi on Android 11 and Later

Starting from Android 11Google has simplified the process of connecting to ADB over Wi-Fi by integrating it into the default settings. Here are the step-by-step instructions:

1. Connect the device via USB and authorize debugging (a permission request will appear on the smartphone screen - confirm it).
2. Open a terminal (or command prompt) on your computer and run the following command to ensure the device is detected:

   adb devices

   The response should contain a line containing the serial number of your device.

3. Set ADB to TCP/IP mode (replace 5555 to any free port if 5555 is busy):

   adb tcpip 5555

4. Disconnect the USB cable and connect via Wi-Fi (replace IP_ADDRESS to the real IP of your device):

   adb connect IP_ADDRESS:5555

To find the IP address of your Android device, go to Settings → Wi-Fi, click on the name of your network and look at the "IP address" section (usually it's something like 192.168.x.x).

If the connection is successful, the command adb devices Now it will show your device with a mark IP_ADDRESS: 5555Now you can use all standard ADB commands, for example:

adb shell
adb install app.apk
adb logcat

⚠️ Attention: On some devices (eg. Samsung With One UI) after rebooting the port 5555 reset. In this case, you will have to re-execute the command adb tcpip 5555 via USB.

Alternative Method: ADB over Wi-Fi on Android 10 and Later

For devices on Android 10 There's no official wireless ADB support in older versions, but you can use a local network workaround. Here's how:

1. Connect the device via USB and run:

   adb devices

   Make sure it is detected.

2. Switch to TCP/IP mode on a random port (eg. 5555):

   adb tcpip 5555

3. Find out the IP address of the device (as described above) and connect:

   adb connect IP_ADDRESS:5555

The main difference from the new method is that After rebooting the device, port 5555 will close, and you will have to repeat the procedure via USBTo avoid this, you can use applications like ADB WiFi or WiFi ADB from Google Play that automatically restart the ADB server after a reboot.

Also on some firmware (for example, LineageOS or Pixel Experience) there is a built-in option ADB over network in the developer settings. In this case, simply enable it and connect via IP.

Troubleshooting Common ADB Wi-Fi Connection Errors

Even with proper setup, problems sometimes arise. Here are the most common errors and how to fix them:

• 🔴 "device unauthorized" — The device is not authorized. Solution: Connect via USB, confirm the debugging request on the smartphone, and repeat the command. adb connect.
• 🔴 "cannot connect to IP_ADDRESS:5555" — the port is busy or the device is not responding. Solution: Check that the IP address is correct and try a different port (e.g. 5556).
• 🔴 "no devices/emulators found" — ADB doesn't see the device. Solution: Restart the ADB server with the command adb kill-server, then adb start-server.
• 🔴 "connection reset" — Unstable network connection. Solution: Reconnect to Wi-Fi or use a cable.

If the device connects but commands are executed slowly, try:

• Go to Wi-Fi channel 5 GHz (if the router supports it).
• Disconnect other devices from the network to reduce the load.
• Use port 5555 for one device only (for the second one, select 5556 etc.).

Security: Risks of Wireless ADB Debugging

While ADB over Wi-Fi is convenient, it opens up potential vulnerabilities. If an attacker connects to the same network, they could theoretically access your device through an open port. 5555To minimize risks:

• 🔒 Use ADB over Wi-Fi only on trusted networks (home or work Wi-Fi).
• 🔒 Turn off debugging after completing the work with the command:

  adb disconnect IP_ADDRESS:5555

• 🔒 Do not leave your device unattended with ADB enabled. in public places.
• 🔒 Update regularly Platform Toolsto avoid vulnerabilities in older versions of ADB.

@echo off
adb connect 192.168.1.100:5555
adb install app.apk
adb shell am start -n com.example.app/com.example.app.MainActivity
pause

adb -s IP1:5555 install app1.apk
adb -s IP2:5556 install app2.apk

adb connect localhost:5554