qhsusb_bulk: what it is and how to turn it into the 9008 driver
4 min read
qhsusb_bulk is not a special extra phone mode. It is the name Windows gives a Qualcomm device in EDL before the proper driver is installed. In the correct state the same phone appears as Qualcomm HS-USB QDLoader 9008 under Ports (COM and LPT). While Device Manager still shows qhsusb_bulk, an unknown device, or a yellow mark with Code 10, UnlockTool, DFT Pro, Cheetah and similar tools usually cannot open the port.
What “right” and “wrong” look like
- Right: Ports (COM and LPT) → Qualcomm HS-USB QDLoader 9008 (COMx), no yellow mark.
- Driver not installed yet: Other devices or Universal Serial Bus controllers → QHSUSB_BULK / qhsusb_bulk, often with a yellow mark.
- Code 10: the device is visible, but Windows could not start it. The port is missing in the tool, or it flickers.
Entering and leaving EDL is covered in EDL mode: how to enter and exit. This page is about something else: how to make Windows see a phone that is already in 9008.
How to install the driver
- Unplug the phone and close service tools, Mi Flash, QPST and any other utility that might hold the port.
- In Device Manager, uninstall qhsusb_bulk or the unknown device. If you see a checkbox to remove the driver, tick it.
- Install a signed Qualcomm USB driver from your service tool package or from a Qualcomm pack. Do not download the first archive that appears for “qhsusb_bulk driver”.
- Connect the phone in EDL to a rear USB 2.0 port, with no hub, on a known-good data cable.
- Refresh the device list: a QDLoader 9008 row with a COM number should appear. Remember that port — the program should show the same one.
If Windows 11 blocks the driver because of a signature, start with Windows 11 driver signature for flashing. If the installer fails or Windows rolls the driver back, see Qualcomm 9008 driver will not install.
Code 10 and the yellow mark
Code 10 in Device Manager means “the device failed to start”. Common causes: several driver versions mixed together, an unsigned pack, a charge-only cable, an unstable USB 3 port in EDL, or a phone that holds the mode for only a fraction of a second. A practical order:
- Remove the device and the driver, then reboot the PC.
- Install one current signed driver, not three packs “just in case”.
- Use a short cable, a rear USB 2.0 port, and no docking station.
- Enter EDL again and watch whether the device vanishes after a couple of seconds. A port that appears and disappears is often the cable, the socket or power — not “a bad program”.
If the port flashes and the protocol drops, read Sahara errors. If 9008 is stable and the tool already asks for a Xiaomi signature, you have reached the next stage: EDL authentication failed.
How not to break the USB stack
Do not install WinUSB/Zadig “for experiments” and the standard Qualcomm serial driver at the same time unless you know which interface your tool actually needs. Changing the driver class without a reason is a common way to end up with a 9008 port that no utility can open. Then you have to remove the device, clean out old packages, and reinstall a single signed driver.
Once the 9008 port is stable, you can move on to UnlockTool, DFT Pro Tool or Cheetah Tool Pro — after you check the model. A working driver alone does not mean a method exists for that phone.
FAQ
What is qhsusb_bulk?
It is the name Windows uses for a Qualcomm phone in EDL until the correct driver is installed. After a proper install, the same device usually appears as Qualcomm HS-USB QDLoader 9008 under Ports (COM and LPT).
Are qhsusb_bulk and 9008 different phone modes?
No. The phone is already in EDL. Only the Windows driver changes. While the entry stays qhsusb_bulk or shows a yellow mark, a service tool usually cannot open the port.
What does Code 10 mean on a 9008 device?
In Device Manager, Code 10 means the device failed to start. Typical causes are an incomplete or wrong driver, a signature conflict on Windows 11, a poor cable, or an unstable port. Remove the device and its driver, then reinstall on a USB 2.0 port.
Should I search for a separate “qhsusb_bulk driver”?
No. You need a signed Qualcomm USB / QDLoader 9008 driver, not a random archive named qhsusb_bulk. Unknown driver packs are a common source of Code 10 and a broken USB stack.
Topics: Drivers & modes
Recommended offers
Read next
Qualcomm 9008 driver not installing: QHSUSB_BULK and other errors
Why the Qualcomm 9008 driver fails and the phone shows up as QHSUSB_BULK in EDL: installation, signature, cable, port and common errors.
November 4, 2026 · 4 min readDriversWindows 11 driver signature: preparing a PC for flashing
Why Qualcomm/MediaTek/Samsung drivers fail to install on Windows 11 because of signature policy, and how to prepare the PC safely.
November 4, 2026 · 4 min readGuideEDL mode: what it is, how to enter and how to exit
What EDL mode (Qualcomm 9008) is, how to enter EDL via adb, buttons, cable or test point, how to exit EDL, and why the screen stays black while in it.
November 10, 2026 · 3 min readDriversQualcomm Sahara error in EDL 9008: what causes it and how to fix it
Sahara protocol error, Sahara fail or failed to receive hello packet in EDL 9008: timeouts, drivers, cables, firehose and EDL auth, with a step-by-step fix.
November 4, 2026 · 4 min readGuideXiaomi EDL authentication failed: what it means and what to check
Why Xiaomi in EDL reports Authentication failed or asks for authorization in Mi Flash, DFT Pro and other tools. What to check and which lawful paths exist.
November 10, 2026 · 4 min readGuidesAll guidesHow-tos, error fixes and tool comparisons.Open the guides

