How to Connect to Your Phone via ADB over Wi-Fi: A Complete Guide with Commands and Tips

Debugging Android devices via ADB over Wi-Fi Saves time and eliminates the need to constantly connect a USB cable. This method is especially useful for developers, testers, and advanced users who frequently interact with their smartphone's system settings. However, not everyone knows that wireless connection requires prior configuration—and without it, the commands simply won't work.

In this article you will find step-by-step instructions taking into account the nuances of different versions Android (from 8.0 to 14), as well as solutions to typical errors such as device unauthorized or no devices/emulators foundWe'll explore which settings need to be enabled on your phone, how to check the correct drivers on your PC, and why you sometimes have to switch back to a USB connection even after successfully setting up Wi-Fi.

Spoiler: if yours Samsung Galaxy or Xiaomi Redmi refuses to connect over the air. In 90% of cases, the problem lies in an incorrectly entered IP address or disabled developer mode. And also— Starting with Android 11, Google changed the wireless ADB mechanism and now requires an additional command with a key to establish a persistent connection. pair.

What is ADB and why do you need a Wi-Fi connection?

ADB (Android Debug Bridge) - this is a tool from the package Android SDK, which allows you to control your device from a computer: install apps, retrieve logs, modify system files, and even unlock the bootloader. By default, ADB works via USB, but since 2017 (starting with Android 8.0 Oreo) official support for wireless mode appeared.

Benefits of Wi-Fi connection:

• 🔌 No cable dependency — you can debug the device at a distance of up to 10 meters (depending on the power of the router).
• ⚡ Quick response for commands - the delay is minimal with a stable 5 GHz signal.
• 📱 Convenience of testing — for example, testing geolocation functions without being tied to a table.
• 🔧 Less wear on the USB connector — relevant for old devices with a loose port.

However, the method has its limitations. Firstly, Initial setup still requires USB (except for devices with an unlocked bootloader). Secondly, if the Wi-Fi signal is weak, connection drops may occur. Thirdly, not all manufacturers (for example, Huawei on some firmware) correctly support this function.

Wi-Fi connection requirements

Before setting up, make sure your system meets the minimum requirements:

Pay special attention to the version platform-toolsOlder releases (before 28.0.0) do not support the command. adb pair, necessary for Android 11+. If you have installed Android Studio, update your tools via SDK Manager.

⚠️ Attention: On some devices Samsung (for example, series Galaxy S21 and newer) wireless ADB may be blocked by security policies KnoxIn this case, the only solution is to roll back the firmware or use alternative methods like scrcpy.

Preparing your phone: enabling USB and Wi-Fi debugging

To activate wireless mode, you first need to turn on developer mode and enable USB debugging. The instructions are universal for most devices, but on some brands (for example, Xiaomi or OnePlus) there may be additional nuances.

Enable developer mode (7 taps on the build number) | Enable USB debugging in developer settings | Connect the phone to the PC via USB and confirm trust | Check that the device is displayed in adb devices|Activate the "Wi-Fi Debugging" option (if available in the firmware)-->

Step 1: Enable Developer Mode

1. Open Settings → About phone.
2. Find the item Build number (on Samsung — Software Information → Build Number).
3. Tap it 7 times until a notification appears You have become a developer!.

Step 2: Enable USB debugging

1. Go back to the main settings menu and open System → Developer Mode (on some devices - Additional → For developers).
2. Activate the switch USB debugging.
3. Connect your phone to your PC via USB and trust the computer in the window that appears.

On Xiaomi Additionally, you may need:

• 🔓 Unblock OEM Unlock in the developer settings (if you plan to use fastboot).
• 📡 Enable USB Debugging (Security Options) in the section Additionally.

Step 3: Check the USB connection

Open a command prompt (or terminal) and run:

adb devices

If the device appears in the list (for example, 1234abcd device), you can proceed to setting up Wi-Fi. If not, check the drivers or cable.

Connecting to a Phone via ADB over Wi-Fi: Step-by-Step Instructions

Now let's move on to the process itself. The algorithm varies slightly depending on the Android version.

Method 1: For Android 11 and later (using pair)

Starting from Android 11Google has tightened its security rules. Wireless connections now require paired connection via code.

1. Connect your phone to your PC via USB and run:

   adb tcpip 5555

   This command puts the ADB daemon on the phone into network mode on the port 5555.

2. Disconnect the USB cable and find the phone's IP address:

   • 📱 On the phone: Settings → Wi-Fi → [your network] → IP address.
   • 💻 On PC (Windows): ipconfig (look for IPv4 address on the same subnet).

adb pair 192.168.1.100:5555

adb connect 192.168.1.100:5555

If everything went well, the team adb devices will show your device with a mark wireless.

Method 2: For Android 8.0–10 (simplified method)

On older versions, the process is simpler - no pair code is required:

1. Connect your phone via USB and run adb tcpip 5555.
2. Disconnect the cable and find the phone's IP address.
3. Perform:

adb connect 192.168.1.100

Port 5555 It is not necessary to specify it - it is used by default.

⚠️ Attention: On some firmware (for example, MIUI 12+ or ColorOS 11) after rebooting the phone the port 5555 reset. To avoid repeating the command adb tcpip every time, add it to the startup script or use applications like ADB WiFi from Play Market.

Solutions to common errors

Even with proper setup, glitches can still occur. Here are the most common issues and their solutions:

Error	Cause	Solution
device unauthorized	The phone does not trust the PC (no confirmation via USB).	Connect via USB, confirm trust in the dialog box and try again. adb connect.
no devices/emulators found	ADB server does not see devices.	Restart the server: adb kill-server && adb start-server.
cannot connect to [IP]:5555	The port is closed or the device is on a different network.	Check IP, restart adb tcpip and turn off the VPN.
more than one device/emulator	Multiple devices are connected.	Specify the target device explicitly: adb -s 192.168.1.100:5555 shell.

If commands are running slowly after connecting, try:

• 🔄 Reconnect to the 5 GHz network (less interference).
• 📶 Reduce the distance between your phone and the router.
• 🛠️ Disable power saving for Wi-Fi in your phone settings.
What to do if the phone is not visible in adb devices even via USB?

1. Check the cable - some "charging" cables do not transmit data.

2. Update drivers via device Manager (section "Portable devices").

3. Try a different USB port (preferably USB 2.0 on the back of the PC).

4. On Windows install Google USB Driver or a driver from the manufacturer (for example, Samsung USB Driver for Mobile Phones).

5. Restart your phone and PC.

Connection automation: scripts and third-party utilities

To avoid entering commands manually each time, you can use scripts or specialized programs.

Script for Windows (bat file)

Create a file adb_wifi.bat with the following contents:

@echo off
adb tcpip 5555
adb connect 192.168.1.100:5555
pause

Replace 192.168.1.100 to your IP address. Run the file as administrator.

Android apps

If you don't feel like working with the command line, try:

• 📱 ADB WiFi (Play Market) - automatically turns on tcpip and shows IP.
• 🔧 Bugjaeger — a full-fledged ADB client with Wi-Fi support.
• 🖥️ scrcpy - not only ADB, but also over-the-air screen mirroring.

For macOS/Linux You can create an alias in ~/.bashrc:

alias adbwifi='adb tcpip 5555 && adb connect 192.168.1.100:5555'

⚠️ Attention: Some antiviruses (for example, Kaspersky or Avast) can block adb.exe as a potentially dangerous file. Add the folder with platform-tools in exceptions or temporarily disable protection during setup.

Safety: Risks and Recommendations

Wireless debugging is convenient, but it opens up potential vulnerabilities:

• 🔓 Local access: Anyone on your network can connect to the phone if they know the IP.
• 🕵️ Traffic interception: without encryption (up to Android 11) data is transmitted in clear text.
• 📴 Unauthorized commands: An attacker can install software or change settings.

adb push local_file /sdcard/target_folder
adb pull /sdcard/file_on_the_phone local_folder