Troubleshooting Your Lumia 650 : What to Do When "Emergency Files" Are Missing or Full

If you’ve tried to recover a bricked Lumia 650 using the Windows Device Recovery Tool, you might have run into a frustrating wall: an error stating that emergency files are full or simply unavailable. This usually happens when the device is in a "Qualcomm HS-USB QDLoader 9008" mode (hard-bricked) and the standard recovery software can't find the necessary handshake files to start the flash process.

Here is how to navigate this situation and get your Windows phone back to life. 1. Understanding the "Emergency Files"

Emergency files (specifically .ede and .edp files) are specialized payloads used to jumpstart a phone that won't boot into its normal recovery mode.

The Issue: Microsoft often didn't officially release or host the specific emergency files for the Lumia 650/DS on their public servers, leading to the "not available" error in standard tools.

The "Full" Error: This often indicates a communication mismatch or a corrupted bootloader that refuses to accept the emergency payload being sent by the recovery tool. 2. Manual Recovery with Thor2

When the automated tool fails, the best approach is to use the Thor2 command-line utility, which is included with the Windows Device Recovery Tool installation.

Locate Thor2: Navigate to the installation folder (usually C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool).

Source the Files: Since they aren't on Microsoft's servers, you may need to find them from community sources like Proto Beta Test or LumiaFirmware.

Run the Command: Open Command Prompt as an administrator and use the following syntax:thor2 -mode emergency -hexfile [path_to_ede] -edfile [path_to_edp] -ffufile [path_to_ffu]. 3. Alternative: WPInternals

If Thor2 doesn't do the trick, the community-developed Windows Phone Internals tool is your next best bet.

guides/WIP-NewGuide.md at master · WOA-Project ... - GitHub

It sounds like you're dealing with a "storage full" error on an older Microsoft Lumia 650

, specifically involving "emergency files" or system-critical data that's preventing the phone from functioning. Windows 10 Mobile

(a platform Microsoft no longer supports), managing storage can be a bit tricky. Here is a write-up on why this happens and how to clear it out. The Problem: "Emergency Files Full" This error usually refers to the System & Reserved storage or Temporary Files

reaching capacity. Because the Lumia 650 only has 16GB of internal storage, it doesn't take much—OS updates, error logs, or app cache—to choke the system. Step-by-Step Solutions 1. Clear Temporary Files (The Quickest Fix)

Windows 10 Mobile has a built-in tool to purge "emergency" or junk files. This Device (Internal Storage). Scroll down to Temporary Files Check the boxes for Temporary files Downloads folder Telemetry/Error logs Remove files 2. Move Apps to an SD Card

The Lumia 650 supports microSD cards up to 200GB. Moving your apps off the internal "Emergency" space is the best long-term fix. Insert a high-quality microSD card. Change the setting "New apps will save to:" to To move existing apps: Tap This Device Apps & games , select an app, and hit 3. Reset the Camera Upload & WhatsApp Cache

Apps like WhatsApp and OneDrive often store "emergency" backup files or large media caches internally.

Go into WhatsApp settings and clear your chat history or delete large videos.

Check the "Upload Center" to see if stuck uploads are creating massive temporary cache files. 4. The "Soft Reset"

If the phone is lagging or the storage error won't disappear after deleting files, a soft reset clears the RAM and temporary system state without deleting your data. Press and hold the Volume Down

buttons simultaneously for 10–15 seconds until the phone vibrates and restarts. 5. The Final Option: Hard Reset

If the "System" category is taking up 10GB+ and won't go down, it's likely a corrupted update file. This wipes the phone. Reset your phone Summary for the Write-up

The Lumia 650 "Emergency Files Full" issue is typically caused by telemetry logs failed Windows Update fragments

occupying the limited 16GB internal flash memory. By shifting the default save location to an and manually purging the Temporary Files

When your Microsoft Lumia 650 reports that "emergency files" are full, it generally refers to one of two scenarios: either the phone's temporary/system storage is clogged with cached data, or you are a developer/modder attempting to use recovery tools like Windows Device Recovery Tool (WDRT) or WPInternals and the required firmware files are missing or taking up too much space. Managing Storage and Temporary Files

If you are seeing a general "Storage Full" message caused by system or temporary files, follow these steps to clear them: Use Built-in Storage Settings: Go to Settings > System > Storage. Tap on This Device and select Temporary files.

Tap Remove files to clear app caches, downloads, and telemetry.

Perform a Hard Reset:If the storage remains full due to phantom "system" files, a factory reset is the most effective solution.

Settings Method: Go to Settings > System > About > Reset your phone.

Button Combo Method: Power off the phone. Hold Power + Volume Down until an exclamation mark (!) appears. Then press in order: Volume Up -> Volume Down -> Power -> Volume Down. Understanding Emergency Files for Recovery

For users trying to "unbrick" or flash a Lumia 650, "emergency files" refer to specific .EDE (hex) and .EDP (mbn) files required when the phone is stuck in Emergency Download Mode (QHSUSB_DLOAD).

I understand you're looking for "emergency files" for the Lumia 650 — likely referring to FFU (Full Flash Update) images, emergency flash files (like .hex or .ede), or recovery firmware for unbricking or repairing the device.

Here’s the essential information you need:

Additional Critical File (Not always included)

Some rare bricks require MPRG_8992_fh.elf or similar "Programmer" file, but for the Lumia 650’s Snapdragon 212 (MSM8909), the Hex file acts as the programmer.

Checksum Warning: Always verify the SHA-1 hash of your files against known community databases (like LumiaFirmware). Corrupt hex files are the #1 cause of hard bricks during EDL flashing.

Official & Reliable Sources

  1. Microsoft Device Recovery Tool (official tool) – Automatically downloads the correct emergency files when you recover a Lumia 650. This is the safest option.

  2. Lumia Firmware Archives (community-hosted):

    • LumiaFirmware.com – Search for Lumia 650 (RM-1152, RM-1154, RM-1156 depending on variant)
    • Windows Device Recovery Tool offline cache – Look for RM-1152_*.ffu

  3. Required file types for full emergency recovery:

    • FFU image (main OS + firmware)
    • Emergency files: .ede (Emergency Download Engine) + .hex (bootloader)

9. Post-Recovery: Installing the FFU

Emergency files only resurrect the bootloader. Your Lumia 650 now has no operating system. You must flash a valid FFU.

  1. In WP Internals, go to the Flash tab.
  2. Click Flash FFU and select a stock ROM (e.g., RM-1152_021R001_FFU.bin).
  3. Ensure the phone is still in Flash Mode (red screen).
  4. Click Flash. This takes 5-10 minutes.
  5. After completion, the phone will reboot into Windows 10 Mobile setup.

Alternative: Use Microsoft's thor2 command line if WP Internals fails.

thor2 -mode emergency -hexfile RM1152.hex -mbnfile RM1152.mbn -orig_gpt
thor2 -mode flash -ffufile RM1152.ffu -do_full_nand_update

Background and Technical Context


    

  • Lumia 650 hardware: 1 GB RAM, 16 GB internal storage (user-accessible ~11 GB), microSD support.
    • 

  • Windows 10 Mobile emergency features potentially involved:

      

    • Emergency Contacts / ICE (In Case of Emergency) card.
      • 

    • SOS/power-button emergency call features.
      • 

    • System diagnostic logs, crash dumps, and telemetry snapshots stored for troubleshooting.
      • 

    • Apps that manage or export emergency information.
      • 

    

    • 

  • Storage partitioning and quotas: system-reserved areas may limit space for logs; corruption or runaway logging can exhaust allocated space.
    • 



Solution 1: The Built-in Storage Sense Tool


The quickest way to clear space is using the native cleaner.


    

  1. Go to Settings (the gear icon).
    2. 

  2. Select System > Storage.
    3. 

  3. Tap on This Device to see a breakdown of what is using your space.
    4. 

  4. Look for the category labeled "Temporary Files".
    5. 

  5. Tap it to open the cleanup tool.

      

    • Ensure Temporary files and Internet Explorer/Edge history are checked.
      • 

    • Note: You may also see a "Previous version of Windows" option. Check this if you are sure you don't want to roll back an update.
      • 

    

    6. 

  6. Tap Delete.
    7. 



Hard reset via buttons (Lumia 650):


    

  1. Power off the phone.
    2. 

  2. Press and hold Volume Down + Power until it vibrates.
    3. 

  3. Release Power but keep holding Volume Down until you see a large exclamation mark.
    4. 

  4. Press keys in this sequence: Volume Up → Volume Down → Power → Volume Down.
    5. 

  5. The phone should reset.
    6. 





Solution 2: Clear the "Other" Storage


Lumia users often find that a mysterious category called "Other" takes up gigabytes of space. This includes app data, maps, and cached images.


    

  1. Go to Settings > System > Storage.
    2. 

  2. Select This Device.
    3. 

  3. Locate "Other" in the list.
    4. 

  4. Tap it to see what apps are holding data.
    5. 

  5. If you see apps you no longer use, tap the app and select Uninstall.
    6. 

  6. Pro Tip: Offline maps are a major storage hog. If you have downloaded maps for navigation, go to Settings > Apps > Offline Maps and delete any you aren't currently using.
    7. 



2. Why You Need the Full Set


Many users fail because they only download a partial package. You cannot simply find an emergency.img or a single hex file. The Lumia 650 emergency files full package consists of three distinct components, each with a critical role:


| File Type | Naming Convention (Example) | Function |
| :--- | :--- | :--- |
| EDL Loader (Hex) | RM-1152_emergency_hex.hex | Initializes the Qualcomm processor’s RAM. Allows the PC to talk to the dead CPU. |
| Emergency MBN | RM-1152_emergency_BOOT.mbn | Signed bootloader replacement. Contains device security certificates. |
| Partition Map | RM-1152_gpt_main0.bin | Maps the eMMC storage sectors. Prevents writing data to incorrect addresses. |


Without any one of these three, the flash operation will fail with a "Sahara Fail" or "Firehose error." The "Full" package is non-negotiable.