Engineering
Reading a Qualcomm EDL handshake, step by step
7 min read
Emergency Download Mode (EDL) is built into the Qualcomm boot ROM itself, below the bootloader and below Android entirely. It exists so a device can still be recovered when nothing else on it will run — which is exactly why UnlockLab checks the USB device list for it when a device is in a state ADB and Fastboot can't reach.
The handshake happens in two stages. First, the device speaks Sahara: a small, fixed protocol whose only job is to identify the chip and receive a signed "programmer" image — a piece of code Qualcomm's boot ROM will only execute if it's signed correctly for that specific chip. UnlockLab does not take part in this handshake.
Once the programmer loads and the boot ROM hands off execution to it, the device switches to Firehose — a command-response protocol for reading (and, if you choose to, writing) flash storage directly. This is where partition tables actually become readable. UnlockLab does not speak Sahara or Firehose. It only notices that a device in this mode is present, from the USB listing: Qualcomm's vendor ID 05C6 with product ID 9008.
Why the signed-programmer requirement matters: it's the actual security boundary. A device with a locked bootloader can still be read in EDL, but only through a programmer the chip's boot ROM trusts — which is precisely why EDL access alone doesn't imply unrestricted device access. UnlockLab stays outside that boundary entirely: it reports that a device is in EDL, and sends nothing to it.