ADB and Fastboot are the two most important command-line tools in Android repair — used for everything from unlocking bootloaders to flashing partitions and debugging. But they only work if Windows detects the phone through the right USB driver. This guide covers installing the ADB/Fastboot driver and platform-tools for 2026.

What Are ADB and Fastboot?

ADB (Android Debug Bridge) talks to a booted Android phone for commands, file transfer, and debugging. Fastboot talks to the phone's bootloader for flashing partitions, unlocking, and recovery. Both need a matching USB driver so Windows can open the connection.

Together they power tasks like bootloader unlocking, sideloading, and single-partition flashing.

What You Will Need

  • A Windows PC
  • Android SDK Platform-Tools (the official ADB/Fastboot package)
  • The ADB/Fastboot USB driver (Google USB driver or the OEM driver)
  • USB debugging enabled on the phone (for ADB)
  • A good data cable

Step 1: Install Platform-Tools

Download the official Android SDK Platform-Tools and extract it to a simple path like C:\platform-tools\. This folder contains adb.exe and fastboot.exe — the actual tools you'll run from a command window.

Step 2: Enable USB Debugging (for ADB)

On the phone: 1. Go to Settings → About phone and tap Build number seven times to unlock Developer Options. 2. Open Developer Options and turn on USB debugging. 3. Connect the phone and authorize the PC when prompted.

Fastboot doesn't need USB debugging — it works from the bootloader.

Step 3: Install the USB Driver

Install the ADB/Fastboot driver (the Google USB driver works for many devices; some brands need their OEM driver):

  • Automatic: run the driver installer.
  • Manual: in Device Manager, right-click the device → Update driver → Browse → point to the driver folder.

For Fastboot mode specifically, Windows must show the phone as an Android Bootloader Interface.

Step 4: Verify ADB and Fastboot

Open a command window in your platform-tools folder:

  • Run adb devices — your phone's serial should appear (authorize on the phone if asked).
  • Reboot to bootloader and run fastboot devices — the serial should list.

If both list the device, your driver and tools are working.

Common Problems and Fixes

adb devices shows nothing. USB debugging off or not authorized, or the driver is missing.

fastboot devices empty. The Android Bootloader Interface driver isn't installed — install it via Device Manager.

"unauthorized" in adb. Accept the debugging prompt on the phone.

Device not detected in fastboot. Bad cable or missing driver — use a data cable on USB 2.0 and reinstall.

Pro Tips From the Workbench

The most common ADB/Fastboot trip-up is the driver difference between modes: a phone can be perfectly detected in ADB (booted) but invisible in Fastboot (bootloader) because Fastboot needs the Android Bootloader Interface driver specifically. If adb devices works but fastboot devices doesn't, that's almost always the cause — install the bootloader driver via Device Manager.

Keep platform-tools in a simple path and add it to your system PATH so you can run adb/fastboot from any command window. And always authorize the PC on the phone the first time — an unauthorized device shows in the list but rejects commands. A data cable on USB 2.0 rounds out a reliable setup.

Quick Reference Checklist

For ADB & Fastboot setup:

  • Platform-tools extracted to a simple path (add to PATH).
  • USB debugging enabled + PC authorized (for ADB).
  • USB driver installed (Google/OEM).
  • Android Bootloader Interface driver for Fastboot mode.
  • Verify: adb devices and fastboot devices list the serial.
  • Data cable on USB 2.0.

If ADB works but Fastboot doesn't, it's almost always the missing Android Bootloader Interface driver — install it via Device Manager in Fastboot mode.

One more habit worth forming: after any Windows update, quickly run adb devices and fastboot devices on a test phone to confirm the drivers still bind correctly. Windows occasionally swaps a working driver for a generic one, and catching that on a test device is far better than discovering it mid-job. Keeping platform-tools updated alongside your drivers ensures the newest phones and commands work without surprises.

Frequently Asked Questions

Do I need USB debugging for Fastboot? No. Fastboot works from the bootloader without USB debugging. ADB needs it.

Why does adb devices show "unauthorized"? You haven't accepted the debugging prompt on the phone. Reconnect and tap Allow.

Fastboot doesn't detect my phone — why? The Android Bootloader Interface driver isn't installed. Add it via Device Manager while in Fastboot mode.

Which driver works for ADB/Fastboot? The Google USB driver covers many devices; some brands need their OEM driver.

Where do I get ADB and Fastboot? From the official Android SDK Platform-Tools package.

Do ADB and Fastboot use the same driver? Related but not identical — Fastboot mode specifically needs the Android Bootloader Interface driver, which is why one can work without the other.

Can I run adb from any folder? Yes, if you add platform-tools to your system PATH; otherwise run it from inside the platform-tools folder.

Do all phones use the same Fastboot driver? Many use the generic Android bootloader driver, but some brands need their OEM driver for Fastboot. Install the OEM one if the generic fails.

Why does adb keep asking for authorization? Enable "Always allow from this computer" on the prompt, and the phone will stop re-asking on that PC.

A Note on Safe Downloads

Get platform-tools from the official Android source and drivers from trusted sites like our USB drivers page. Avoid random "ADB installer" downloads that bundle extras.

Conclusion

Setting up ADB and Fastboot comes down to three things: install platform-tools, install the correct USB driver (including the Android Bootloader Interface for Fastboot), and enable USB debugging for ADB. Verify with adb devices and fastboot devices, and you're ready for unlocking, flashing, and debugging. For more, see our how-to guides.