How to Fix "ADB Device Not Found" Error on Windows (2026)

You plug in your Android phone, open a terminal, type adb devices, and get nothing useful back. It is one of the most common frustrations in Android development, and it has multiple distinct causes — each requiring a different fix. This guide walks through every realistic root cause and gives you a concrete resolution for each one.

Before diving into individual fixes, run this command to see exactly what ADB knows about your connected devices:

adb devices

If you see an empty list or only the header line List of devices attached, work through the causes below in order. Most people find their fix by cause 1 or 2.

Cause 1: USB Debugging Is Disabled

This is the most common cause by far. ADB only works when USB Debugging is turned on in Developer Options. If the option is not visible to you, see our guide on USB Debugging not showing in Developer Options.

To enable USB Debugging:

1. Open Settings on your Android device.
2. Go to About Phone and tap Build Number seven times until you see "You are now a developer!"
3. Go back to Settings > System > Developer Options (or Settings > Developer Options on some devices).
4. Toggle USB Debugging to ON.
5. Reconnect the USB cable and run adb devices again.

When you reconnect, your phone should display a dialog asking "Allow USB debugging?" with a fingerprint of the host computer's RSA key. Tap Allow. If you want to avoid this prompt in the future, check "Always allow from this computer" before tapping Allow.

Cause 2: Wrong USB Connection Mode

When you connect an Android device via USB, it can operate in several modes: Charging only, File Transfer (MTP), PTP, RNDIS (USB Tethering), and others. ADB only functions reliably in File Transfer (MTP) or PTP mode. If your device is set to "Charging only" (which is the default on many modern Android phones for security reasons), ADB cannot enumerate the device properly.

To change the USB mode:

1. Pull down the notification shade on your Android device after connecting the cable.
2. Tap the notification that says "Charging this device via USB" or "USB connected".
3. Select File Transfer or MTP from the list of options.
4. Run adb devices again.

Some devices remember this setting per cable or per host. If it keeps reverting to charging-only, you may need to set it each time or look for a "Default USB configuration" option inside Developer Options on your device.

Cause 3: Missing or Incorrect USB Drivers

Windows needs a USB driver to communicate with your Android device at the ADB level. Without the correct driver, the device either does not appear in Device Manager at all, or appears with a yellow warning icon under "Other Devices" as an unknown device.

There are two types of drivers to consider:

• Google USB Driver — works for Pixel devices and many others. Install via Android SDK Manager or download directly from developer.android.com.
• Manufacturer driver — required for Samsung (install via Samsung Smart Switch or Odin), OnePlus, Xiaomi, Huawei, and others. Search for "[your brand] USB driver Windows" to find the official download.

After installing the driver:

1. Open Device Manager (right-click Start > Device Manager).
2. Look for your phone under Android Device, Portable Devices, or Other Devices.
3. It should now show without a warning icon. If it still shows a warning, right-click > Update Driver > Browse my computer and point it at the downloaded driver folder.
4. Disconnect and reconnect the cable, then run adb devices.

Cause 4: Unauthorized Device

If your adb devices output shows a device serial number followed by unauthorized rather than being empty, the issue is slightly different — the device is detected but has not granted permission to this computer. See our dedicated guide on fixing the ADB Unauthorized error for full resolution steps.

The quick fix: look at your phone's screen while ADB is connected. There should be a dialog asking "Allow USB debugging?" — tap Allow. If no dialog appeared, go to Developer Options and tap "Revoke USB debugging authorizations", then disconnect and reconnect the cable.

Cause 5: Faulty Cable or USB Port

Not all USB cables support data transfer. Many cheap USB-C cables are charge-only and have no data lines wired. This is especially common with cables bundled with cheap accessories or power banks.

To rule out a cable or port issue:

• Try a different USB cable — ideally the one that came in your phone's box.
• Try a different USB port on your PC, preferably a USB 3.0 port (blue) directly on the motherboard rather than a hub or front panel port.
• Avoid USB hubs — they can cause enumeration failures with ADB.

A quick sanity check: if your device charges when connected but your PC does not play the device connect sound, the cable almost certainly lacks data lines.

Cause 6: Stale ADB Server

The ADB server is a background process that manages communication between the adb client and connected devices. It can get into a broken state, especially after an ADB version upgrade, after connecting/disconnecting many devices, or after a system sleep/wake cycle.

Restarting the ADB server is always a safe thing to try and often resolves strange detection failures:

adb kill-server
adb start-server

Or in a single line:

adb kill-server && adb start-server

After the server restarts, reconnect your device and run adb devices. You should see the RSA authorization prompt appear on your phone if the server was the problem.

If multiple ADB binaries are installed on your system (for example, one from Android Studio, one from a standalone SDK, one from a third-party tool), they can conflict — each trying to start its own server on port 5037. To check what is listening on that port:

netstat -ano | findstr :5037

If you see multiple entries, identify and remove duplicate ADB installations, keeping only one version on your PATH.

Full Diagnostic Checklist

If you have worked through all six causes and ADB still cannot find your device, run through this checklist systematically:

1. USB Debugging is enabled (confirmed in Developer Options, toggle is blue/on).
2. USB mode is set to File Transfer, not Charging Only.
3. The RSA authorization dialog appeared and you tapped Allow.
4. Your phone appears in Device Manager without a yellow warning icon.
5. You are using a data-capable USB cable, not a charge-only cable.
6. You have run adb kill-server && adb start-server.
7. You have only one version of ADB installed on your system.
8. You have tried a different USB port, bypassing any hub.

For the vast majority of users, one of the first three items on this list is the root cause.

Testing Your Fix

Once ADB detects your device, confirm everything is working with a few test commands:

adb devices
# Expected output:
# List of devices attached
# R3CX90BXXXX    device

adb shell getprop ro.product.model
# Should print your device model name

adb shell echo "ADB is working"
# Should print: ADB is working

If all three commands succeed, your ADB setup is healthy and you can proceed with your workflow.

Conclusion

The "ADB device not found" error almost always comes down to one of six things: USB Debugging being off, the wrong USB mode selected, a missing driver, an unauthorized device, a bad cable, or a stale ADB server process. Work through each cause in order and you will resolve it in a few minutes.

If you find yourself repeatedly dealing with ADB setup issues — especially on Windows where driver management can be tedious — consider using Andora, which bundles ADB and handles device detection automatically so you can focus on what you actually want to do with your device.