So you’ve got an Android device and want to dive deep into the world of modding? Be it rooting or installing a custom ROM like LineageOS, most of the aftermarket modding requires you to connect your Android smartphone to a computer using a USB cable so you can use tools like the Android Debug Bridge (ADB) and Fastboot to interact with the device. For an Android power user, you may also want to reinstall the factory firmware on your phone, which means you have to deal with the OEM-specific flashing utilities.
However, none of these tinkering jobs are possible if your PC can’t see the target device in the first place. As in the case of Windows, the operating system may require an additional piece of software known as the “driver” in order to properly recognize all the different connection modes exposed by the Android device. Below you can find a list of official OEM-provided Android USB driver packages and a generic driver installation guide. If you don’t see the maker of your device listed or you see a misplaced link, send a message to Skanda Hazarika (SkandaH on the forums) with the device details.
Table of Contents:
Purpose of Android USB drivers
The USB interface of an Android device is a pretty complex object. Depending on the configuration, it may expose the standard Android USB debugging interface, the fastboot interface, and various other SoC-specific diagnostic interfaces to the computer. Simultaneously maintaining more than one interface is supported as well, e.g. you can interact with your device with ADB while configuring the internal modem parameters.
Keep in mind the aforementioned scenarios are a bit different from connecting the device through the plain old Media Transfer Protocol (MTP) or Picture Transfer Protocol (PTP) mode. MTP enables the end-user to browse the internal memory on the device from a PC as if it’s an external storage drive. Microsoft ships a generic MTP/PTP driver with every edition of Windows since Windows XP, so you don’t need an external driver for that.
Download Android USB drivers for popular OEMs
Most Android OEMs offer official driver packages for their devices. Besides the ADB and Fastboot interfaces, these drivers also support proprietary flashing protocols designed by the corresponding device maker. For example, if you want to flash a Samsung Galaxy device, you must install the Samsung USB driver package beforehand.
Note that Microsoft has been shipping a generic ADB driver with Windows for a while, so installing the OEM driver just for the sake of USB debugging might not sound worthwhile anymore. Windows can also check and install the missing drivers on the fly through Windows Update. However, Microsoft-recommended drivers are not always the best choice for complex USB interfaces, so do check out the official driver pack whenever possible.
Get the appropriate driver for your device from the index below:
How to install Android USB drivers
Now that you’ve downloaded the suitable driver package for your device, it’s time for you to install it. Some OEMs offer standard installer executables, which means you can easily install the whole driver suite by double-clicking on the setup file and following the wizard.
However, Google and a few other vendors prefer to stick with the bare INF and associated binary files which are packed inside a zip or rar archive. Such packages need to be installed using Device Manager, but you have to extract the contents of the archive beforehand.
- Right-click on the Start button and select the Device Manager entry. You can also call the Microsoft Management Console snap-in named
devmgmt.mscdirectly from Run to open Device Manager.
- Connect the Android device to your PC. Depending on the selected configuration, you may see one or more unknown devices popping up.
- (Optional) Right-click on the unknown device entry, select Properties, move to the Details tab, and finally select Hardware Ids from the dropdown menu. Now open your favorite search engine, paste the hardware identifier in the search box, and go through the search results. This is a crude way to determine the probable interface your device is currently exposing.
- Right-click on the unknown device entry and select Update drivers. Now select Browse my computer for drivers/driver software and point the wizard to the folder where you extracted the driver package.
- If everything goes right, you should see a confirmation page like the following.
Manually install the driver for an unsupported device
On some occasions, the OEM drivers aren’t enough. Perhaps you’ve stumbled upon a no-name generic tablet, or the flash mode interface of your shiny new phone has yet to get an official driver from its maker. In that case, you can forcibly install an existing driver package for a similar USB interface through Device Manager.
- Open Device Manager and locate the unknown device entry.
- Right-click on it and select Update drivers. Select Browse my computer for driver software and then choose the option named Let me pick from a list of available drivers on my computer.
- Now select Show All Devices and click Next. On the next screen, click on the Have Disk… button.
- At this point, you need to browse to the location where the extracted driver for a similar device is located. Pick the INF file from the list of files and select Open.
- Now carefully choose the driver model. For example, if you’re trying to install the Fastboot mode driver for a device, select the Android Bootloader Interface from Google’s driver set. Windows might show a warning related to compatibility, but you can ignore it and continue the installation process anyway.
- That’s it!
This method lets you force-install a signed driver without breaking its digital signature, so you don’t need to turn off driver signature enforcement on a 64-bit Windows instance.
You’ve now got the correct USB driver installed on your computer and your Android device is ready to receive instructions. Now it’s time to put it all together and run your first ADB command!