Home / Guides / Drivers

ADB driver on Windows - make your Android device show up

To talk to an Android phone over ADB, Windows needs an ADB interface driver for that phone - and this is the step where most setups fail: the phone charges, files may even transfer, but "adb devices" stays empty. The driver is free and official; the trick is getting the right one installed against the right device entry.

Quick answer

On the phone: Settings, About phone, tap Build number 7 times, then enable USB debugging in Developer options. Reconnect the cable and watch the phone screen - accept the "Allow USB debugging" prompt. If adb devices still shows nothing, install the USB driver from your phone maker (or Google's USB driver) through Device Manager - method 3 below.

Symptoms - how this problem looks

adb devices returns an empty list
The device shows as "unauthorized" in adb
Device Manager shows the phone model or "Android" with a yellow triangle
File transfer works, but ADB and fastboot do not
A "universal ADB installer" tool ran but changed nothing
The device disappears in fastboot mode

Why it happens

USB debugging is off

Without USB debugging enabled in Developer options - and the RSA prompt accepted on the phone screen - no driver will make adb work.

No ADB interface driver

Windows knows the phone as a media device but has no driver for its ADB interface - the debug channel simply is not installed.

Wrong USB mode or cable

Charge-only mode and charge-only cables never expose the data interfaces. The USB mode notification on the phone decides what Windows sees.

Junk "driver installer" tools

Random universal ADB installers bundle unwanted software and often install a mismatched driver that then blocks the right one.

The fixes, in order

1. Prepare the phone first

  1. Settings, About phone, tap Build number 7 times to unlock Developer options.
  2. In Developer options enable USB debugging.
  3. Connect the cable, pull down the notification shade and set USB mode to File transfer.
  4. Watch for the "Allow USB debugging?" prompt on the phone and tap Allow (tick "Always allow from this computer").

2. Let Windows fetch the driver

  1. Settings, Windows Update, Advanced options, Optional updates, Driver updates - install anything mentioning your phone brand or Android.
  2. Reconnect the phone and run adb devices again.

3. Install the maker's USB driver through Device Manager

  1. Download the USB driver from your phone maker's support site (Samsung, Xiaomi, Motorola and others publish one), or Google's USB Driver for Pixel devices from the official Android developer site.
  2. Right-click Start, open Device Manager - the phone sits under Other devices or Portable Devices, often with a yellow mark.
  3. Right-click it, Update driver, Browse my computer for drivers, and point to the downloaded driver folder.
  4. If nothing matches, choose "Let me pick from a list", select Android Device, then Android ADB Interface.

Stay safe: Skip "universal ADB driver" download sites. The official maker packages are free, signed, and do not bundle extras.

4. Verify and fix "unauthorized"

  1. Run adb kill-server, then adb devices - a fresh authorization prompt appears on the phone.
  2. "Unauthorized" means the prompt was dismissed: check the phone screen and accept it.
  3. Still empty? Revoke USB debugging authorizations in Developer options and reconnect - the prompt returns.

The automatic option

If you do not know the exact model, several devices need attention at once, or the manual route did not find a match - Outbyte Driver Updater identifies your installed hardware automatically and updates the drivers from official sources, with a backup before every change. The scan and diagnosis are free.

Download Driver Updater Downloads Outbyte Driver Updater for Windows 11, 10, 8 and 7. Free 2-day trial, no credit card required.

Full features and details →

Frequently asked questions

Do I need Android Studio for the ADB driver?

No. The platform-tools package (adb itself) and the USB driver are separate small downloads. The driver comes from your phone maker or Google's USB driver page; adb comes with platform-tools.

Fastboot does not see the device even though adb works. Why?

Fastboot mode presents a different USB interface that needs its own driver entry. Boot the phone into fastboot, open Device Manager, and install the same maker driver against the new "Android" entry that appears (method 3).

adb worked before and stopped after a Windows update. What now?

The update likely replaced the phone's driver with a generic one. Reinstall the maker's USB driver through Device Manager (method 3) - authorization on the phone survives, so it is usually back in one step.