Windows does not ship with a built-in driver for OnePlus handsets. Without the correct USB driver, Device Manager shows an unknown device, ADB reports no devices attached, and Fastboot cannot flash anything. This guide walks through the full installation process, from downloading the right package to verifying the driver is loaded correctly.
On macOS and Linux, Android devices are recognized through a generic USB class driver and you typically need nothing extra beyond enabling USB debugging. Windows is different: it relies on vendor-supplied INF files that map specific USB hardware IDs to the correct WinUSB or composite driver stack.
OnePlus devices expose two or three USB interface profiles depending on the connection mode. In MTP (file transfer) mode, Windows often loads a generic MTP driver without vendor help. In ADB mode, however, the device presents a different USB interface class (0xFF, vendor-specific), which requires an Android-specific driver binding. In Fastboot (bootloader) mode the hardware ID changes again, needing yet another binding. OnePlus ships all three bindings in a single driver package, which is why you need to install it before doing any ADB or Fastboot work.
Historically, OnePlus bundled this driver with the OnePlus Switch application. The driver package can now be obtained from the support pages on OnePlus's official website (oneplus.com) under the Software section for your device model, or from Google's Windows USB Driver, which covers the ADB interface for most Android devices running stock AOSP builds.
There are two reliable sources for a OnePlus-compatible USB driver:
Option 1 — Google USB Driver via Android Studio SDK Manager: Open Android Studio, go to SDK Manager (Tools > SDK Manager), select the SDK Tools tab, check "Google USB Driver," and click Apply. The driver package is downloaded to %LOCALAPPDATA%\Android\Sdk\extras\google\usb_driver\. This driver covers ADB mode for all Android devices and Fastboot mode for Google-branded hardware. For most OnePlus tasks it works perfectly.
Option 2 — OnePlus official driver package: Visit oneplus.com, navigate to Support > Software Updates for your specific model. Look for a link labeled "OnePlus USB Driver" or "One USB Driver." The download is a self-extracting EXE or a ZIP containing a oneplus_usb_driver.inf file and one or more .cat and .sys files. If a self-extracting EXE is provided, run it to place the extracted files somewhere on disk, then proceed to the manual install steps below rather than running any included setup wizard, as the wizard sometimes fails silently on newer Windows builds.
Manual INF installation through Device Manager is the most reliable method because it bypasses installer UI quirks and directly commits the driver to the Windows driver store.
devmgmt.msc..inf file. Make sure Include subfolders is checked.Open a command prompt and run adb devices. The phone should display an authorization dialog asking whether to trust the computer. Tap Always allow from this computer, then run adb devices again. A line ending in device confirms success.
When a OnePlus phone is in Fastboot mode, it presents a different USB hardware ID. Device Manager typically shows it as Android Bootloader Interface under Other devices with a warning triangle until the WinUSB driver is applied.
To enter Fastboot mode, either run adb reboot bootloader from a working ADB connection, or power off the device and hold the Volume Up + Power buttons (on most OnePlus models) until the Fastboot screen appears. Repeat the Device Manager Update Driver steps above pointing to the same driver folder. The Google USB Driver INF contains a binding for USB\VID_05C6&PID_9008 (Qualcomm Download mode) as well as the standard Fastboot VID/PID pairs. After applying the driver, run:
fastboot devicesYou should see a serial number followed by fastboot. If the list is empty, try a different USB port (USB 2.0 ports are sometimes more reliable than USB 3.x for Fastboot on Qualcomm devices), or run fastboot devices from an elevated command prompt.
"No devices/emulators found" after installing the driver: The ADB server caches device state. Run adb kill-server, unplug the cable, replug, then run adb devices. Also check that USB Debugging is still enabled — some OnePlus models reset Developer Options after an OTA update.
Device shows as "Unknown USB Device (Device Descriptor Request Failed)": This usually points to a hardware issue (faulty cable or port) rather than a driver problem. Try a different cable, preferably one rated for data transfer rather than charging only. Cables marked "charge only" lack the data wires needed for ADB.
Driver installation fails with error 0xE0000247: This means the INF file's digital signature timestamp is outside the trusted window on heavily locked-down Windows installations. Temporarily disable driver signature enforcement by running bcdedit /set testsigning on in an elevated command prompt, rebooting, installing the driver, then re-enabling enforcement with bcdedit /set testsigning off. Note that this is only needed for unofficial or old driver packages; the current Google USB Driver is signed by a trusted authority and should not trigger this error.
Multiple "Android Device" entries in Device Manager: Each USB port stores a separate driver instance. If you plugged into several ports during troubleshooting, you may have orphaned entries. They are harmless but you can clean them up by going to Device Manager, clicking View > Show Hidden Devices, and uninstalling the ghosted entries.
Once ADB shows the device, run a quick smoke test to confirm the connection is fully functional:
adb shell getprop ro.product.modelThis should return your phone's model name, for example OP5259L1 for a OnePlus 12. If it does, ADB communication is working end to end and you can proceed with whatever task you originally needed ADB for — sideloading an APK, capturing a bug report, or setting up wireless ADB so you can disconnect the cable entirely.