ADB device not found on Windows

What "device not found" actually means

When adb devices shows an empty list under "List of devices attached" — or a tool reports "no adb connection found" or "device not connected in ADB mode" — the ADB server on your PC can't see the phone at all. That's different from "unauthorized" (ADB sees it but you haven't approved this computer) or "offline" (it's connected but the daemon stopped responding). An empty list almost always comes down to four things, in order of how often they're the culprit:

1. A charge-only USB cable — by far the most common cause.
2. USB debugging is off, or the authorization was never granted.
3. The wrong USB connection mode (charging instead of File transfer).
4. A missing or wrong USB driver on Windows.

Work through the fixes below in that order — most people are sorted by Step 2.

Step 1 — Turn on USB debugging

On the phone, open Settings → About phone and tap Build number seven times to unlock Developer options. Then go to Settings → System → Developer options and switch on USB debugging. While you're there, pull down the USB notification when connected and set the mode to File transfer (MTP) — charging-only mode hides the device from ADB.

Step 2 — Rule out the cable and port

Charge-only cables look identical to data cables but carry only power. Test yours by copying a file over MTP — if files won't transfer, the cable can't carry ADB either, so swap it for a known-good one. Plug directly into a rear USB 2.0 port on a desktop rather than a front-panel port or hub, which are often flaky for ADB.

Step 3 — Install the OEM USB driver

Windows ships generic ADB drivers but some OEMs (Samsung, Xiaomi, OnePlus) require their own. Andora ships with the standard ADB Windows USB drivers (AdbWinApi, AdbWinUsbApi, libusb) so most modern devices are detected without extra setup. If your device still doesn't show up, search '[brand] USB driver' and install the OEM driver from the manufacturer.

Step 4 — Restart the ADB server and authorize

Force a clean reconnect with adb kill-server then adb start-server, reconnect the phone, and accept the "Allow USB debugging?" prompt (tick "Always allow from this computer"). Then confirm it's listed:

C:\platform-tools> adb devices
List of devices attached
ABC123XYZ    device

Once your phone shows as device you're back in business — you can install an APK from your PC or mirror the screen straight away.

Still not showing up? Advanced checks

• Two ADB installs fighting — run where adb and remove any older copy that isn't your current platform-tools; mismatched versions can return an empty list.
• Unknown device in Device Manager — open Windows Device Manager; if the phone shows with a yellow warning under "Other devices", right-click → Update driver → pick "Android ADB Interface".
• Revoke and re-grant authorizations — in Developer options tap Revoke USB debugging authorizations, then reconnect to force a fresh prompt.
• Reboot both ends — a phone reboot clears a stuck device-side daemon; restarting the PC clears a stuck driver.

Frequently asked questions