Modern Nokia Android phones are made by HMD Global and run Android One or close-to-stock Android. This means USB driver setup is simpler than heavily customized devices like MIUI phones — there are no proprietary software layers to navigate. However, Windows still needs the correct USB driver to recognize Nokia handsets for ADB and Fastboot. This guide covers the driver options and how to verify a working connection.
This guide applies exclusively to Nokia Android phones (HMD Global, 2017 onward: Nokia 3, 5, 6, 7, 8, X20, G50, C30, and related models). If you have an older Nokia Symbian or Asha device, the Nokia PC Suite and Nokia Suite drivers for those phones are entirely different products and this guide does not apply.
HMD Global Nokia Android phones use standard Android USB hardware IDs, which means the Google USB Driver works on all of them. HMD does not publish a proprietary USB driver package the way Motorola or Sony do. The recommended approach is to use the Google USB Driver directly.
The Google USB Driver supports all Android devices for ADB and Fastboot use, including Nokia HMD phones. It is the most reliable and up-to-date option for Nokia devices on Windows.
There are two ways to install it:
Option A: Through Android Studio
%APPDATA%\Android\Sdk\extras\google\usb_driver\ (or your custom SDK path).Option B: Standalone download
C:\GoogleUSBDriver.devmgmt.msc).After installation, the device should appear under Android Device or ADB Interface in Device Manager without a warning icon.
Nokia Android phones run Android One with minimal customization, making Developer Options easier to access than on most other brands:
Connect the Nokia phone via USB. Select File Transfer in the USB preference popup. Open a terminal and run:
adb devices
An authorization dialog appears on the Nokia screen: "Allow USB debugging?" Tap Always allow from this computer and then tap Allow. Run adb devices again. The device serial number should appear with status device.
Nokia Android phones support Fastboot mode through the standard hardware key method. The key combination varies slightly by model:
adb reboot bootloaderConfirm the connection in Fastboot mode:
fastboot devices
Nokia's bootloader unlock policy varies by region and carrier. Most global HMD Nokia phones (not carrier-locked variants) support bootloader unlocking. In Developer Options, enable OEM Unlocking first. Then in Fastboot mode:
fastboot flashing unlock
Confirm the wipe prompt on-device. Note that some Nokia models display a message stating the device does not support official unlock — in those cases, HMD has not enabled the unlock pathway for that specific SKU.
Nokia's use of Android One means software updates come directly from Google rather than through a customized OEM layer. This has a practical benefit for USB connectivity: Nokia phones respond to standard ADB commands exactly as Google's documentation describes, without MIUI-style security restrictions, custom permission prompts, or brand-specific daemon services. Commands like adb shell, adb install, and adb backup work as expected once USB Debugging is enabled and authorized.
Nokia phones also tend to receive Android security patches promptly because HMD is committed to the Android One program, which requires timely updates. This means the ADB daemon version on the device is usually current, reducing compatibility issues with newer platform-tools versions.
Device recognized as "Portable Device" (MTP) but not as an ADB device: The USB Debugging toggle is off or the USB mode on the phone is set to Charging Only. In the notification shade, tap the USB connection notification and change it to File Transfer. Ensure USB Debugging is enabled in Developer Options. After making changes, disconnect and reconnect the cable.
"No permissions" error on Linux: Linux requires a udev rule for the Android ADB interface. Create or edit /etc/udev/rules.d/51-android.rules and add a line for HMD's USB vendor ID. HMD Nokia phones use the standard Android ADB vendor ID 0x2d9d. Add the line:
SUBSYSTEM=="usb", ATTR{idVendor}=="2d9d", MODE="0666", GROUP="plugdev"Then run sudo udevadm control --reload-rules and reconnect the phone.
Google USB Driver installation rejected with "The best driver for your device is already installed": Windows is satisfied with an existing generic driver and will not replace it via the normal update path. Open Device Manager, right-click the device entry under Other Devices or Portable Devices, choose Uninstall Device, tick the box to delete the driver software, then reconnect the phone. Windows will attempt to reinstall; during this process, manually point to the Google USB Driver folder.
Device shows in fastboot devices but flash commands fail with permission errors on macOS: Run the fastboot command with sudo on macOS, or fix the USB device permissions. Alternatively, use an Android Studio-managed platform-tools installation which sets up the correct permissions automatically.