Home Page » News » Tutorials » How to Pair ADB Over Wi‑Fi Using QR Code on Android 11+ (No Root)

Pair ADB Over Wi‑Fi Using QR Code on Android 11+

13 min read Learn to connect Android 11+ devices to ADB over Wi‑Fi using the built‑in QR‑code pairing feature—no USB cable, no root required. October 03, 2026 12:00

Why use QR‑code pairing for wireless ADB?

Traditional wireless ADB requires a one‑time USB connection to authorize the PC. Android 11 introduced Wireless debugging with pairing via QR code or PIN. This method eliminates the need for a cable, reduces wear on the USB port, and works on the same network without prior trust. It’s especially handy when you have a tablet or a device that’s difficult to connect physically.

Before you start

Android version: Android 11 (API 30) or newer. The QR‑code feature is not available on older releases.
PC requirements: A recent adb binary (version 30.0.5 or later). Older ADB versions cannot handle the new pairing protocol.
Network: Both PC and Android device must be on the same Wi‑Fi network (same subnet). Wi‑Fi isolation on routers can block the connection.
Battery: Keep the device charged or plugged in; wireless debugging can drain battery faster.
Security note: Wireless ADB opens a remote shell. Only pair on trusted networks and disconnect when finished.

Step 1 – Install or update ADB on your computer

Download the Android SDK Platform‑Tools zip for your OS.
Extract the folder to a convenient location (e.g., C:\adb on Windows or ~/adb on macOS/Linux).
Add the folder to your system PATH so you can run adb from any terminal.
- Windows: setx PATH "%PATH%;C:\adb"
- macOS/Linux: add export PATH=$PATH:~/adb to ~/.bash_profile or ~/.zshrc.
Open a terminal and verify the version:
```
adb version
```
You should see Android Debug Bridge version 1.0.41 or higher (the numeric part after the dot reflects the platform‑tools version, e.g., 30.0.5).

If the version is older than 30.0.5, delete the old folder and repeat the download.

Step 2 – Enable Developer options and Wireless debugging on the Android device

Open Settings → About phone (or About tablet).
- Scroll to Build number and tap it seven times. You’ll see a toast saying “You are now a developer!”.
Return to the main Settings screen. A new entry Developer options appears.
- Tap Developer options → enable the toggle at the top.
- Scroll down to Wireless debugging and turn it on.
  - On some OEM skins (e.g., Samsung One UI) the option may be under Advanced or Debugging.
When you enable Wireless debugging for the first time, Android will display a dialog asking to confirm the action. Tap OK.

At this point the device is ready to accept a pairing request, but you still need to exchange credentials.

Step 3 – Pair the device using the QR code

On the Android device, stay in Developer options → Wireless debugging. Tap the Pair device with pairing code button (icon looks like a QR code).
A pop‑up appears showing a QR code and a six‑digit PIN. Keep this screen visible.
On the PC, run the following command (replace adb with the full path if it’s not in PATH):
```
adb pair
```
The terminal will prompt:
```
Enter pairing code:
```
Point your phone’s camera at the QR code displayed on the PC screen, or simply type the six‑digit PIN shown on the phone into the terminal and press Enter.
- If you use the QR code, Android automatically copies the pairing information to the clipboard on the phone, and adb reads it via the camera.
- If you type the PIN, the pairing will succeed as long as the device and PC are on the same network.
After a successful exchange you’ll see:
```
Successfully paired to :
```
The terminal also stores a temporary pairing key in ~/.android/adbkey (or %USERPROFILE%\.android\adbkey on Windows).

Now the PC knows how to authenticate to the device without a USB cable.

Step 4 – Connect to the device over Wi‑Fi

Still in the Wireless debugging screen on the phone, tap Connect device. It will show the device’s IP address and port (usually 5555).
Back on the PC, run:
```
adb connect :5555
```
Replace with the address shown on the phone.
If the connection succeeds you’ll see:
```
connected to :5555
```
Verify the device is listed:
```
adb devices
```
The output should contain a line like:
```
:5555   device
```

At this point you can run any ADB command—install APKs, pull logs, capture screenshots—exactly as you would over USB.

Step 5 – Typical workflow examples

Installing an APK without a cable

adb install path/to/app.apk

Pulling a log file from the device

adb pull /sdcard/Download/log.txt ./log.txt

Running a shell command

adb -s :5555 shell dumpsys battery

Notice the -s flag can be omitted if only one device is connected.

Step 6 – Disconnecting safely

When you’re done, run:
```
adb disconnect :5555
```
On the phone, toggle Wireless debugging off. This revokes the temporary key and prevents stray connections.

Turning the feature off also saves battery because the device stops broadcasting its debugging service.

Troubleshooting

Device does not appear in `adb devices`

Check network isolation: Some guest Wi‑Fi networks block peer‑to‑peer traffic. Switch to the main SSID or disable client isolation in the router settings.
Verify IP address: The IP shown in the Wireless debugging UI may change after a router reboot. Refresh the screen and copy the new address.
Firewall rules: Ensure your PC’s firewall allows inbound connections on port 5555. On Windows, add an inbound rule for adb.exe.

Pairing fails with “Pairing code invalid”

Make sure you are using ADB version 30.0.5 or newer. Older versions cannot interpret the QR‑code payload.
If you typed the PIN, double‑check each digit. The PIN expires after 2 minutes.
Restart the pairing UI on the phone (tap the three‑dot menu → Reset pairing code) and try again.

Connection drops after a few minutes

Android may power‑save the Wi‑Fi radio when the screen is off. Keep the screen on, or enable Stay awake while charging in Developer options.
Some OEMs (e.g., Xiaomi) have aggressive background restrictions. Add adb to the device’s battery optimization whitelist.

Security considerations

Wireless debugging is essentially an open remote shell. Treat it like any other remote access tool:

Only enable it on trusted networks (home or lab). Avoid public Wi‑Fi.
Disable the feature immediately after you finish debugging.
If you suspect the device was left paired, you can revoke the key by tapping Forget all devices in the Wireless debugging screen.

Alternative methods if QR‑code pairing is unavailable

PIN pairing: Same UI offers a six‑digit PIN instead of a QR code. Use adb pair and type the PIN.
USB‑first method: Connect the device via USB, run adb tcpip 5555, then disconnect and adb connect over Wi‑Fi. This works on Android 9 and later but requires a cable once.

QR‑code pairing is the most convenient because it eliminates the initial cable entirely.

Wrap‑up

By following the steps above you can set up a fully wireless ADB connection using Android’s built‑in QR‑code pairing. The workflow saves time, reduces wear on ports, and works on any Android 11+ device without rooting. Remember to keep the feature disabled when not in use and to verify that both devices stay on the same trusted network.

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.