For a Microsoft Lumia 650 Go to product viewer dialog for this item.
to work with emergency files (often used for unbricking or bootloader unlocking), you typically need the specific .ede and .edp files for its RM model (e.g., RM-1152). These files are used in conjunction with tools like WPInternals or THOR2 to recover a phone stuck in a boot loop or a "dead" state (Qualcomm 9008 mode). Key Steps to Make Emergency Files Work
Obtain Correct Files: You need the FFU (Flash File Update) for your specific RM version and the matching Emergency Packages (.ede and .edp files).
Since official Microsoft servers for the Windows Device Recovery Tool (WDRT) are often unreliable or missing specific files for the
, many users find them on community-run archives like ProtoBetaTest or LumiaFirmware.
Use WPInternals for Automation: The WPInternals tool is the most user-friendly way to use these files. It can often automatically search for and download the necessary emergency files if you connect your device in "Normal Mode" or "Flash Mode".
Manual Flashing with THOR2: If WPInternals fails, you can use the THOR2 command-line utility (included with WDRT). A typical emergency flash command looks like this:
thor2 -mode emergency -hexfile [path_to_.ede] -edfile [path_to_.edp]
Note: Some users report that if the 650-specific files fail, files for related models like the RM-1085 (Lumia 950 XL) Go to product viewer dialog for this item. are sometimes used as "donor" files during the process. Important Considerations
Battery Charge: Ensure the phone has enough battery; if it is completely drained, the emergency flash may fail midway.
Driver Check: In your PC's Device Manager, the phone should ideally show up as "QHSUSB_BULK" or "Qualcomm HS-USB QDLoader 9008" for the emergency mode to trigger correctly.
Risk: Emergency flashing is a deep-level recovery. If interrupted, it can permanently brick the device. What is the current state of your (e.g., stuck on a logo, black screen, or "sad face" error)?
To recover or unlock a Go to product viewer dialog for this item.
using emergency files, you need specific system files—typically .ede (emergency download executable) and .edp (emergency download payload)—to interface with the device while it is in an unresponsive or "Emergency" state. Where to Find Emergency Files
Because Microsoft has shut down many of its original Lumia support servers, these files must now be sourced from community repositories:
Proto Beta Test: A reliable community source that hosts a dedicated Lumia Emergency Files directory.
LumiaDB: A newer alternative to the older lumiafirmware.com that offers FFU and emergency files without account requirements.
LumiaFW (GitHub): Another community-maintained firmware database frequently used by Windows Phone enthusiasts. How to Use the Files lumia 650 emergency files work
Once you have the correct files for your specific RM number (e.g., RM-1152 for the Lumia 650), use the following tools to flash them:
WPInternals: This is the primary tool for unlocking the bootloader. You select your device's FFU (Flashable Firmware Unit), the emergency folder containing the .ede/.edp files, and the SBL3 file to initiate the process.
Thor2 (via Command Prompt): Part of the Windows Device Recovery Tool (WDRT) directory, this manual tool can force an emergency flash:
thor2 -mode emergency -hexfile [path to .ede] -edfile [path to .edp]
Windows Device Recovery Tool (WDRT): While the official servers are often down, the tool itself can sometimes still recognize a device in "Qualcomm HS-USB QDLoader 9008" mode if local emergency files are provided. Known Issues with Lumia 650
Availability: Some users have reported that specific emergency files for the Lumia 650 Dual SIM (DS) were historically harder to find compared to models like the 950.
Emergency State: If your device appears in Device Manager as Qualcomm HS-USB QDLoader 9008, it is in a "hard bricked" emergency state and requires these files to communicate with flashing software.
The "emergency files" for the Microsoft Lumia 650 Go to product viewer dialog for this item.
generally refer to specific firmware components (.EDE and .EDP files) required to recover the device when it is in a "hard bricked" state or "emergency mode". 🛠️ Recovery & Emergency Files
is stuck on a black screen or shows up as "Qualcomm HS-USB QDLoader 9008" in Device Manager, the standard Windows Device Recovery Tool (WDRT) may fail.
Availability: Officially, emergency files for the 650 were often unavailable on Microsoft servers.
Third-Party Sources: You may need to source them from community repositories like Lumia Emergency Files at Proto Beta Test or Internet Archive.
Tools: Specialized tools like WPInternals or manual command-line flashing via thor2 are typically used with these files to unbrick the device. Microsoft Lumia 650 Review was marketed as a sleek, business-oriented budget phone.
guides/WIP-NewGuide.md at master · WOA-Project ... - GitHub
Microsoft Lumia 650 enters "Emergency Mode" (often detected by a PC as QHSUSB_BULK Qualcomm HS-USB QDLoader 9008
), it typically indicates a corrupted bootloader or a deep system crash. Recovering the device requires specific Emergency Files Full Flash Update ) firmware file. postmarketOS Wiki Recovery Prerequisites Windows Device Recovery Tool (WDRT):
Even if the tool itself cannot automatically fix the phone, you need it installed to get the necessary drivers and the Emergency Files: You need a Hex file ( ) and an Emergency Descriptor file ( For a Microsoft Lumia 650 Go to product
). Note that for some Lumia 650 variants, these files are notoriously difficult to find on official servers; you may need to source them from third-party archives like LumiaFirmware Proto Beta Test Firmware (FFU):
The original firmware file for your specific model (e.g., RM-1152). Step-by-Step Unbricking Guide Check Device Connection Connect your to your PC via USB. Device Manager . It should appear under "Universal Serial Bus devices" as QHSUSB_BULK
. If it shows as "Qualcomm HS-USB QDloader 9008," you must update the driver to the "Care Suite Emergency Connectivity" driver via the Windows Device Recovery Tool Locate Thor2 Utility Open a Command Prompt (CMD) as an administrator. Navigate to the WDRT directory: 64-bit Windows:
cd "C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool" 32-bit Windows:
cd "C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool" Flash Emergency Payload
Run the following command, replacing the bracketed paths with your actual file locations:
thor2 -mode emergency -hexfile [path_to_ede_file] -edfile [path_to_edp_file] Wait for the process to finish. If you see a FFU_PARSING_ERROR
, it often means the emergency payload was successfully flashed, and the phone should now show a red screen. Flash the Firmware (FFU)
Once the phone is in the red "Flash Mode" screen, run this command:
thor2 -mode uefiflash -ffufile [path_to_ffu_file] -do_full_nvi_update -do_factory_reset
This will write the full operating system back to the device. Do disconnect the cable during this 10–15 minute process. Reboot to Normal Mode After the flash is complete, use this command to restart: thor2 -mode rnd -bootnormalmode postmarketOS Wiki
guides/WIP-NewGuide.md at master · WOA-Project ... - GitHub 19 May 2022 —
Emergency Files and Recovery "emergency files" are specialized firmware components used to repair a "hard-bricked" device that cannot be recovered through standard software
. These files allow the computer to communicate with the phone's hardware when its primary operating system and bootloader are corrupted or missing. 1. Purpose of Emergency Files Unbricking : They are essential when a device is stuck in Qualcomm HS-USB QDLoader 9008
mode (also known as EDL or Emergency Download mode), where the screen remains black and the phone only shows up in a computer's Device Manager. Bootloader Repair
: They re-write critical low-level details and the bootloader to restore the device to a state where it can accept a standard Full Flash Update (FFU). Bootloader Unlocking : Tools like WPInternals
often require these files to temporarily modify the bootloader for root access or installing custom operating systems like Windows on ARM. 2. Key File Types File Format:
Emergency recovery typically requires three specific files tailored to the Lumia 650's hardware (Product Type RM-1150, RM-1152, or RM-1154): HEX File (
: An Emergency Download Executable used to initialize the phone's processor. EDP File (
: An Emergency Download Program file containing the payload for the bootloader repair.
: The main firmware image that contains the complete operating system. 3. Recovery Process Overview
is in an emergency state, the general recovery workflow involves: Driver Installation
: Ensuring the PC recognizes the device as "Care Suite Emergency Connectivity" or "Qualcomm HS-USB QDLoader 9008". Tool Setup : Using the utility, which is part of the Windows Device Recovery Tool (WDRT) installation. Command Execution
: Running a command similar to the following in an administrator Command Prompt:
thor2 -mode emergency -hexfile [path_to_ede] -edfile [path_to_edp] FFU Flashing
: Once the emergency files restore the bootloader (often indicated by a red screen), the standard FFU firmware is flashed to restore the OS. 4. Availability and Challenges Lumia 650 DS Emergency state | Windows Central Forum
The "files" are not a separate set of rescue tools but rather the full Flashable Firmware Update (FFU) images. The device uses these files to overwrite the corrupted OS or Boot partitions.
.ffu (Full Flash Update)The Lumia 650, while a sleek Windows 10 Mobile device, is not immune to software corruption. When a standard flash fails or the device enters a hard brick state (black screen, no vibration, unrecognized by the Windows Device Recovery Tool), standard recovery becomes impossible. This is where Emergency Files come into play.
Once the emergency work is done, your phone will be in "Flash Mode" (red screen or detected as "Nokia Boot Manager"). Now, flash the actual OS:
thor2 -mode uefiflash -ffufile "C:\path\to\RM1152.ffu" -do_full_nvi_update -do_factory_reset
This will take 5-10 minutes. Do not unplug the device until you see "Operation completed successfully."
Because Microsoft has shut down the official Lumia firmware servers, the "emergency files" are now sourced from community archives.
.ffu file for the specific model (RM-1152 vs RM-1153).WinUSB Drivers (compat drivers for Qualcomm).This article explains the Lumia 650’s emergency files (emergency info) feature: what it is, what data you can include, how to set it up on Windows 10 Mobile, how emergency responders can access it, limitations specific to the Lumia 650, troubleshooting, privacy considerations, and alternatives.
Follow this sequence meticulously. Any deviation can result in a deeper brick.