A typical interaction with the Nokia 3.4 using Firehose looks like this (using a tool like Qualcomm Premium Tool, QPST, or EDL Tool):
reset command -> device reboots.Example log output from a successful Firehose session:
[19:45:12] Device: Nokia 3.4 (SM4250) - COM10
[19:45:12] Sending Firehose Loader: prog_emmc_firehose_SM4250_ddr.elf
[19:45:13] Firehose handshake successful. Version: 2.3
[19:45:13] Target info: eMMC (Samsung), size: 58.24 GiB
[19:45:14] Rawprogram0.xml loaded. 56 partitions defined.
[19:45:15] Erasing userdata... DONE.
To appreciate the Firehose Loader, you must first understand the boot process of a Qualcomm device: Nokia 3.4 Firehose Loader
In a healthy device, the chain ends with Android booting. However, if the boot image is corrupted, the SBL is overwritten, or the user accidentally locks themselves out via a forgotten PIN/factory reset protection (FRP), the device enters EDL Mode.
EDL Mode is the last-resort protocol. It allows communication with the PBL over USB. The problem? EDL mode is crippled out of the box—it will only accept authenticated, signed commands from Qualcomm or the OEM (HMD Global/Nokia). A typical interaction with the Nokia 3
This is where the Firehose Loader enters.
Because HMD does not publicly distribute these files, they leak from service centers or are extracted from official Nokia care suite updates. Common sources include: Close Session: Send reset command -> device reboots
If you simply need to unbrick a Nokia 3.4, check if Ostensibly its own Nokia Care Suite supports it via normal fastboot recovery. Only fall back to Firehose if:
For security-conscious users: Enable full-disk encryption (FDE) or file-based encryption (FBE) with a strong password (not a 4-digit PIN). While Firehose can read raw data, encryption keys stored in the TrustZone cannot be exfiltrated via a standard Firehose loader unless there is a separate vulnerability in the key derivation function.
If you have obtained a legitimate Firehose file (e.g., prog_firehose_ddr_xxx.elf) for the Nokia 3.4, follow this process strictly. Disclaimer: This will void your warranty and carries the risk of total device loss.