GSMCode.PRO
Engineering Documentation
Back to All Guides

Qualcomm Emergency Download (EDL 9008) Protocol & Test Point Diagnostics

GSMCode.PRO Research & Development Group • November 2026 • 10 min read • BootROM Level
Sponsored Advertisement
Responsive In-Article Display Ad Slot (Top Article Placement)

Qualcomm Snapdragon System-on-Chip (SoC) architectures incorporate an unalterable read-only boot memory called the Primary Bootloader (PBL) or BootROM. When the device encounters severe partition corruption—or when hardware test points are shorted to ground during cold boot—the PBL halts normal secondary execution and enumerates via USB as Qualcomm HS-USB QDLoader 9008 (VID: 0x05C6, PID: 0x9008). This state provides lowest-level hardware diagnostic recovery.

1. The Sahara Protocol Handshake

Before high-level XML disk partitions can be accessed, the host utility must communicate using the binary Sahara Protocol. The PBL sends an initial SAHARA_HELLO_REQ containing the SoC hardware ID, SBL revision, and security hash:

Sahara Command Enumeration (Packet Codes) Protocol Spec v2.8
0x01: SAHARA_HELLO_REQ     // Sent by BootROM upon device enumeration
0x02: SAHARA_HELLO_RSP     // Sent by Host containing loader mode parameters
0x03: SAHARA_READ_DATA     // Target requests raw binary chunk from host
0x04: SAHARA_END_TRANSFER  // Host signals completion of Firehose ELF upload
0x05: SAHARA_DONE_REQ      // Target requests confirmation of execution transfer
0x06: SAHARA_RESET_REQ     // Host orders warm target reset

2. Firehose Programmer Execution & XML Payload

Once Sahara uploads the signed prog_firehose_xxxx.elf into device SRAM, execution transitions to the Firehose engine. Communication now switches from raw binary frames to structured XML over USB endpoints:

Sponsored Advertisement
Mid-Article Technical Documentation Banner Slot

3. Hardware Test Points (Force_USB_Boot) Mechanics

When a smartphone is completely unresponsive ("hard bricked") due to an interrupted bootloader flash, software keys cannot trigger EDL mode. In this scenario, technicians identify physical motherboard test points:

By pulling the FORCE_USB_BOOT pin to ground (GND) using fine-tipped tweezers while connecting USB power, the SoC BootROM senses a low logic level on its internal strap register and immediately diverts execution to the USB 9008 recovery handler.

Cryptographic Signature Constraints

Modern Qualcomm SoCs (such as Snapdragon 8 Gen 1/2/3 and 7-series) enforce strict secure boot via hardware Root of Trust. The Firehose ELF loader must be digitally signed with the OEM's private key matching the public key hash burned into the SoC's hardware QFPROM fuses. Using an unsigned or mismatched programmer results in immediate BootROM reset.

Previous: Samsung USB Drivers Next Guide: Samsung Knox Anti-Rollback