New ((new)) | Lumia 650 Emergency Files

Finding and using "new" emergency files for the Microsoft Lumia 650 Go to product viewer dialog for this item.

(RM-1152/RM-1154) is a critical step for users trying to unbrick devices that are stuck in "Emergency Mode" or detected as QHSUSB_BULK in Device Manager. Unlike many older Lumia models, the

has historically faced issues where official Microsoft servers did not provide the necessary emergency payloads (.EDE and .EDP files) through the standard Windows Device Recovery Tool (WDRT). What are Emergency Files?

Emergency files are low-level bootloader components used when a phone's primary operating system and recovery partitions are corrupted. They consist of:

HEX/EDE Files (.ede): Programmer files that allow the flashing tool to communicate with the Qualcomm chipset.

EDP Files (.edp): Emergency descriptor payloads used to initiate the repair process. lumia 650 emergency files new

FFU Files: The full firmware image containing the OS, which is flashed after the emergency files successfully "wake up" the device. Where to Find New Emergency Files

Since Microsoft has largely discontinued support, the community has archived these files on third-party platforms.

Proto Beta Test: One of the most reliable current sources for these archives is Proto Beta Test Lumia Emergency Files, which provides a comprehensive package for various Lumia models, including those previously considered "unavailable".

LumiaFirmware: While the site LumiaFirmware remains a primary source for FFU (Full Flash Update) files, users have reported recent difficulties with downloads or required memberships for certain files.

Internet Archive: Large collections of "Retail Signed FFUs" and associated emergency files are often mirrored on the Internet Archive to ensure long-term availability. How to Use the Files to Unbrick (Summary) To repair a Finding and using "new" emergency files for the

in emergency state, you typically use a command-line tool called thor2 (included with WDRT) or WPInternals.

Identify the Device: Connect the phone to a PC. If it shows as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008, it is in emergency mode.

Download the Correct Files: Match your device's RM-1152 or RM-1154 code to the correct FFU and emergency files.

Run the Flash Command: Use a command prompt in the WDRT directory:thor2 -mode emergency -hexfile [path_to_ede] -edfile [path_to_edp]

Restore the OS: Once the emergency payload is accepted (often indicated by a red flashing screen), you can flash the full FFU image to restore the phone to working order. Note for Spec B Devices: The Remove battery, wait 30 seconds, reinsert

is a "Spec B" device. In some cases, if the specific emergency package for your product code is missing, WPInternals may require a "donor" FFU from a similar model (like the ) to facilitate the unlock or repair process. Lumia 650 DS Emergency state | Windows Central Forum

Phase 1: Device Preparation

1. Remove battery, wait 30 seconds, reinsert.
2. Connect USB cable while holding Volume Down button. If PC detects unknown QHSUSB_BULK, proceed. If not, use the capacitor short method (C3402).
3. Open Device Manager → Ports (COM & LPT). Note the COM port number (e.g., COM5).

What Are Lumia 650 Emergency Files?

Emergency files (often with extensions like .ede, .hex, or .mbn) are low-level bootloader recovery files. They allow you to force-flash the phone’s original firmware even when:

• The phone is hard-bricked (no vibration, no screen)
• The bootloader is corrupted
• Windows Device Recovery Tool (WDRT) fails to detect the device

These files bypass the normal flash mode and communicate directly with the Qualcomm emergency download (EDL) mode.

2. Composition of the New Emergency Files

The archive, labeled Lumia650_ED_Files_2024_v2.1.zip, contains the following critical components:

| File Name | Size (Bytes) | Purpose | Required For | | :--- | :--- | :--- | :--- | | MPRG8909.hex | 1,048,576 | Primary programmer (Sahara protocol loader) | All ED mode operations | | qc8650.mbn | 2,097,152 | Secondary bootloader (Firehose protocol) | Partition read/write | | RM1152_emergency_gpt0.bin | 33,554 | Main GPT (GUID Partition Table) | Rebuilding partition layout | | RM1154_emergency_gpt0.bin | 33,554 | Main GPT for dual-SIM variant | Rebuilding partition layout | | gpt_backup0.bin | 33,554 | Backup GPT (sector -34 to -1) | Recovery when main GPT corrupt | | rawprogram0.xml | 47,212 | Firehose partition scripting | Automated flashing | | patch0.xml | 12,890 | Logical sector addressing map | Offset corrections | | Lumia650_SBL1.mbn | 256,000 | Secondary bootloader stage 1 | Boot chain restoration |

Key innovation: Unlike older files, these include SHA-256 checksums embedded in the XML descriptors, allowing tools to verify integrity before writing.

Error 1: 0xFA001306: The device is not in the correct mode

• Old fix: Jump pins on the mainboard (dangerous).
• New fix: Use the emergency_boot_v2.hex file. These new files contain a reset vector that forces the CPU out of deep sleep without hardware disassembly.

Step 4: Flashing the FFU After Emergency Mode

Once emergency mode succeeds, the phone will switch to Flash mode (red screen). Do not unplug. Immediately flash the standard FFU:

thor2 -mode uefiflash -ffufile "C:\Firmware\RM1152_02177.00053.16353.55006_Retail_Prod.ffu" -do_full_nvi_update