How to unlock bootloader

frifo

Extracting the ZIP-file delivers the folder cmdline-tools. I have placed this folder on the Desktop, opened the folder and started the terminal.

PS Directory: C:\Users[username]\Desktop\cmdline-tools> dir
bin
lib
NOTICE.txt
source.properties

PS Directory: C:\Users[username]\Desktop\cmdline-tools> cd platform-toolsadb
cd : The path "C:\Users[username]\Desktop\cmdline-tools\platform-toolsadb" cannot be found

I guess, commandlinetools-win-13114758_latest.zip is the wrong file.

frifo

On the linked page "https://community.oneplus.com/thread/64487" is written:

"5. To confirm that it is indeed working, open a command prompt window and enter the following commands:
cd Desktop/android-sdk-windows/platform-toolsadb versionIf it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are done."

But the path "platform-toosdb" isn't included in the file commandlinetools-win-13114758_latest.zip.

MrT10001

@frifo Download platform tools from here.

Extract the folder to somewhere it is easy to find, open a command prompt in that folder by right clicking in an empty space, selecting the terminal program you have installed.

Then fastboot and ADB commands will work.

frifo

The file commandlinetools-win-13114758_latest.zip from the URL "https://developer.android.com/studio?hl=en#download" doesn't work, because it is the wrong file.
It seems, that the right URL is "https://developer.android.com/tools/releases/platform-tools?hl=de" and the file "platform-tools-latest-windows.zip".

When I unpack this file, go to the folder platform-tools, open the terminal and type
adb version
I get the response:
Android Debug Bridge version 1.0.32.

phone: system - developer mode - OEM unlock enabled
Starting the phone in the fastboot (volume up + power) and after that pluging to the PC and write the command
fastboot devices -> no response
fastboot oem unlock -> < waiting for device >

MrT10001

@frifo It means your device is not in fastboot mode (i.e. at the bootloader) or is not being detected by the PC.

frifo

When I enter the fastboot mode, for about 0,5s ist written "fastboot mode"
I think, the USB-driver doesn't work.
In the Device Manager:
Other Devices - Android !
An exclamation mark ist shown.

On the webside service.oneplus.com/de/search?key=USB there is not driver for OnePlus Nord N10 5G.

I have tested the driver from developer.android.com/studio/run/win-usb -> usb_driver_r13-windows.zip, but it doesn't work.

MrT10001

@frifo Then you need to install the correct drivers on your PC. Here.

frifo

I have downloaded the file Qualcomm_USB_Driver_v1.010065.1.zip from qcomdriver.com, extracted it and started Qualcomm USB Driver v1.0.10065.1.exe.
The installation seemed to be successfull.
In the Device Manager is still an exclamation mark, when pluging in the phone while in fastboot-mode.

In Terminal "fastboot devices" brings no results.

MrT10001

@frifo So that essentially rules out the driver. Unplug the device from the PC and reboot the device and your PC.

frifo

I have rebootet PC and phone.
Than starting phone in fastboot mode, plugging USB in
Device Manager shows
Android with exclamation mark

MrT10001

@frifo Right click and choose properties, what does it say?

frifo

Phone - System - USB-configuration -> allow file transfer.

Now:
adb devices -> is found
fastboot devices -> no respond

Device Manager - right click - properties:
General
Device type: Other devices
Manufacturer: Unknown
Location: Port_#0004.Hub_00001
Device status
The drivers for this device are not installed. (Code 28)
There are no compatible drivers for this device.
To find a driver for this device, click Update Driver

Driver
Android
Driver Provider: Unknown
Driver Date: Not available
Driver Version: Not available
Digital Signer: Not digitally signed

Details
Property: Device description
Value: Android

Events
Timestamp Description
6/14/2025 ... Device configured (null)
6/28/2025 ... Device deleted
6/28/2025 ... Device configured (null)
Information
Device USB/VIC........... was configured.
Driver Name: null
Class Guid: {00000000-0000-0000-000000000000}
Driver Date:
Driver Version:
Driver Provider:
Driver Section:
Driver Rank: 0x0
Matching Device Id:
Outranked Drivers:
Device Updated: false
Parent Device: USB\ROOT_HUBxx\xxxxxxxx

MrT10001

@frifo Windows 11? Check optional updates in Windows updates.