← All guides AI Release
RU Subscribe to @ai_release1

How to Connect Android to Windows via ADB: Commands and Fixes

Updated: 19.10.2026 · AI Release · @ai_release1
How to Connect Android to Windows via ADB: Commands and Fixes

TL;DR

Requirements and setup

Illustration: Requirements and setup
Illustration: Requirements and setup

Pre-flight checklist:

The single most useful command in this whole guide is adb devices: it prints the connection state of every attached phone. Learn to read the four possible states:

StateWhat it meansFirst action
`device`Connected and authorised — you can run commandsNothing, you are done
`unauthorized`Phone has not accepted this PC's RSA key yetUnlock the phone, tap **Allow** on the dialog
`offline`Port opened but the ADB daemon on the phone is not answering`adb kill-server` then `adb devices` again
`no permissions`Linux-only message, udev rules missingAdd a udev rule — check your distribution docs

Step 1. Install ADB on Windows and unlock Developer options on the phone

Illustration: Step 1. Install ADB on Windows and unlock Developer options on the phone
Illustration: Step 1. Install ADB on Windows and unlock Developer options on the phone

What to do: Download the Platform-Tools archive from the SDK Platform-Tools section of the official Android developer site (developer.android.com), extract it, and put the folder on your PATH. On the phone, open Settings → About phone and tap Build number seven times until Android prints "You are now a developer!". Then go to Settings → System → Developer options and switch on USB debugging.

Why: adb.exe is not installed by any Windows installer — it is a portable binary, so Windows only finds it if the folder is on PATH. USB debugging is the switch that lets the phone expose its debugging interface to a host over USB; without it the phone only offers charging and file transfer.

# Extract to a stable path, e.g. C:\platform-tools
Expand-Archive -Path "$env:USERPROFILE\Downloads\platform-tools-latest-windows.zip" -DestinationPath "C:\" -Force

# Add the folder to the user PATH (current session + future sessions)
setx PATH "$env:PATH;C:\platform-tools"

Close the terminal and open a new PowerShell window — setx only affects new windows.

Example: running adb version in the new window prints something of this shape:

Android Debug Bridge version 1.0.xx
Version <build-number>
Installed as C:\platform-tools\adb.exe

The first two lines confirm the binary is on PATH; the last line confirms which copy Windows actually picked up. If Windows launches a different adb.exe (some games and emulators bundle an old one), the Installed as line will point somewhere else — delete or rename that copy.

Why this works: PATH is searched in order, so the folder you appended is visible to every new shell without touching system-wide settings.

How to check: adb version prints the three lines above, and the phone shows a new Developer options entry in Settings. On MIUI/HyperOS the extra toggle is called USB debugging (Security settings) and is required for adb install — check your vendor's documentation for the exact wording.

Step 2. Authorise the phone and read the device list

What to do: Plug the phone into the PC with the data cable, then run the ADB server and list devices. On the phone, unlock the screen and accept the "Allow USB debugging?" dialog, ticking Always allow from this computer.

Why: The first time a PC connects, the phone shows an RSA fingerprint and asks whether to trust it. Until you tap Allow, the phone appears as unauthorized and every command fails — this is a security feature, not a bug. The ADB server is the background process on port 5037 that multiplies your commands to connected devices.

adb start-server          # starts the local server if it is not running
adb kill-server           # use when state looks stale, then re-run adb devices
adb devices -l            # -l adds model, product and transport_id columns

Example: with one authorised phone attached, adb devices -l prints:

List of devices attached
R58M12ABCDE            device product:beyond1q model:SM_G973F device:beyond1q transport_id:1

The serial number (R58M12ABCDE above) is your handle when several devices are connected. Read properties directly from the phone to confirm which handset you are talking to:

adb -s R58M12ABCDE shell getprop ro.product.model
adb -s R58M12ABCDE shell getprop ro.build.version.release

Example output: SM_G973F and the Android release string (for example 13). Replace the serial with your own — it comes from the first column of adb devices.

Every command that touches one device should be prefixed with -s <serial> as soon as a second device or emulator appears. Without it ADB stops with error: more than one device/emulator.

Why this works: the server keeps one transport per serial, so -s selects the right transport instead of letting ADB guess.

How to check: adb devices lists your serial with the state device, the RSA dialog no longer appears when you replug, and adb shell getprop ro.product.model returns your model name instead of an error.

Step 3. Run commands, install an APK, and switch to ADB over Wi-Fi

Illustration: Step 3. Run commands, install an APK, and switch to ADB over Wi-Fi
Illustration: Step 3. Run commands, install an APK, and switch to ADB over Wi-Fi

What to do: Open an interactive shell on the phone, then install an APK from the PC, then move the same connection onto TCP/IP so you can unplug the cable.

Why: adb shell proves the bridge is fully working — you are executing commands inside Android's own shell. adb install is the fastest way to sideload an app without touching the phone. adb tcpip 5555 restarts the phone-side daemon in network mode on port 5555, and adb connect makes the PC talk to it over Wi-Fi.

adb shell                                  # interactive shell on the phone
# inside the shell:
getprop ro.build.version.sdk
exit

adb install -r "C:\builds\app-release.apk" # -r reinstalls, keeping app data
adb logcat -d -t 20                        # last 20 log lines, then exit

Example: a successful install prints exactly:

Performing Streamed Install
Success

A failure prints the package manager's reason instead, for example Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package com.example.app signatures do not match previously installed version; ignoring!].

Now the wireless part. Find the phone's IP in Settings → Network & internet → Wi-Fi → (your network) → IP address (for example 192.168.1.42), keep the cable plugged in, and run:

adb tcpip 5555                             # phone daemon now listens on TCP 5555
adb connect 192.168.1.42:5555              # replace with your phone's IP
adb devices
adb disconnect 192.168.1.42:5555           # when finished

Expected output: restarting in TCP mode port: 5555, then connected to 192.168.1.42:5555, and adb devices now shows both entries — the USB serial and 192.168.1.42:5555.

Two constraints that catch everyone: the PC and the phone must be on the same subnet, and adb tcpip 5555 does not survive a phone reboot — after a restart you must reconnect USB and issue it again. On Android 11 and newer there is also Wireless debugging with a pairing flow (adb pair <ip>:<port> plus a six-digit code shown on the phone); the pairing port is chosen by the phone each time, so read it from the screen.

If you want to run ADB-style commands on the phone itself without a PC at all, see Shizuku: running ADB commands on Android without a PC.

How to check: adb shell echo ok prints ok, adb install prints Success, and after unplugging the cable adb -s 192.168.1.42:5555 shell getprop ro.product.model still answers with your model. That last command is the definitive proof the wireless link is live.

Troubleshooting

Problem. The phone shows up as unauthorized and every command is refused

Problem. adb devices prints an empty list although the cable is plugged in

Problem. The Wi-Fi connection is refused

Summary and next steps

You now have a working bridge: adb devices shows your serial as device, adb shell executes on the phone, adb install returns Success, and adb connect <ip>:5555 frees you from the cable. From here, move on to scripted log capture with adb logcat or to phone-side automation, and if you would rather mirror and control the device from the desktop without ADB at all, compare the options in How to Connect Android to Windows without Microsoft Phone Link: Open Source Alternatives.

FAQ

Why does adb devices show my phone as unauthorized?

The PC's RSA key has not been accepted on the phone yet. Unlock the screen, accept the "Allow USB debugging?" dialog, or run Revoke USB debugging authorizations in Developer options and replug to trigger a fresh prompt.

Can I use ADB over Wi-Fi without a USB cable at all?

Not for the first connection on most devices: adb tcpip 5555 has to be sent over USB once. Android 11 and newer offer Wireless debugging with a pairing code that works without a cable — the pairing port is displayed on the phone each time.

Which port does ADB use?

Two different ports. The ADB server on your PC listens on 5037 for local clients, and the phone-side daemon in TCP mode listens on 5555 after adb tcpip 5555.

Do I lose ADB over Wi-Fi after rebooting the phone?

Yes. A reboot returns the phone to USB mode, so you must reconnect the cable and run adb tcpip 5555 again before adb connect <ip>:5555.

🤖 AI summary

Related guides

DeepSeek Harness Desktop: How to Install and Add Plugins on Windows and Mac

Пошаговая установка десктопного клиента DeepSeek Harness, подключение локальных и облачных моделей, настройка плагинов и

Shizuku: running ADB commands on Android without a PC

Как установить Shizuku, выдать приложениям ADB-права без root и ПК и чем это полезно для автоматизации и дебloat.

How to Use AI-Powered Search in Windows 11: Commands and Setup

Рассказываем, как находить файлы, запускать программы и управлять ПК через новый поиск Windows 11 с поддержкой Copilot.