Qualcomm CrashDump Mode is the black screen a Snapdragon phone drops into when its system software crashes hard enough that the phone can’t recover by itself. It isn’t a virus and it doesn’t wipe your data. To get out, hold Power + Volume Up until the phone restarts (about 10 to 15 seconds on OnePlus; Nothing says to hold Power alone for 15 seconds or more). If it keeps coming back, the cause is usually a bad update, a misbehaving app, a modified system or, less often, failing hardware.
One crash is nothing to panic about. A phone that lands on this screen every day is telling you something, and the fixes below go from the gentle ones to the last resorts.
What owners stuck on this screen ask
“My phone shut off overnight and I missed my alarm. What is this screen?”
That’s how a long Nothing Community thread on the Phone (2) began: the owner woke up to Crash Dump Mode instead of an alarm. Others in the thread saw it while idle, while taking photos, or several times a day. For many of them, forcing a restart (or just waiting for the phone to reboot itself) got them back in. One poster said Nothing customer service called a single occurrence a safety feature of the OS and advised a service centre visit if it keeps happening. That matches what the screen is for, as explained below.
“It happens again and again. Is it an app?”
Sometimes. Android Authority’s Nothing Phone 2 troubleshooting guide points at a rogue app as the likely cause of repeated crash dumps and random reboots, and suggests removing recently installed or updated apps first. Google’s own safe mode advice is the clean way to test that theory.
“It only crashes in places with bad signal”
A OnePlus 9 Pro owner on the /e/OS community forum described crashing into Crash Dump mode within minutes of unplugging in weak-coverage areas, about 30 times on one trip, while the 5G indicator kept flipping between 5G, no signal and LTE. The phone was on an old, no-longer-supported Android 11 build of /e/OS, and replies blamed that build. The takeaway: a crash that follows the modem (the radio part of the chip) often points at outdated software, so updating is the first move.
“I flashed a custom ROM and now it boots straight into CrashDump”
This one is common with modified phones. On the UBports forum, a OnePlus 6 landed in Qualcomm Crash Dump Mode after an Ubuntu Touch install went wrong. Rolling back with a stock zip didn’t help; reflashing full stock firmware with OnePlus’s MSM download tool is what other members reported as working. That route belongs to people who already modify their phones, and it erases everything.
“The service centre says it’s the motherboard. Are they right?”
Possibly. A TechEnclave thread about a OnePlus 6 with a locked bootloader and the latest update ended with a motherboard replacement, and a Nothing Phone (2) owner reported that even a fresh Nothing OS 4 flash by a repair shop only held for a short while before the phone went back into “Crashdump Mode (minidump)”. When a clean reinstall doesn’t stop it, hardware becomes the likely suspect.
What is Qualcomm CrashDump Mode, exactly?
It’s a debugging state built into phones with Qualcomm Snapdragon chips. When something critical fails, the phone stops everything and waits so engineers can copy out what was in memory at the moment of the crash.
Qualcomm’s developer documentation on RAM dumps describes it plainly: after a crash, the device reboots into RAM dump mode and waits for the dump to be collected over USB. Debug builds have this switched on by default; finished software is supposed to switch it off with a kernel setting called qcom_scm.download_mode. That’s why some phones simply reboot after a crash while others sit on the CrashDump screen.
What triggers it? Qualcomm’s post on its minidump feature lists a kernel panic, a crash in one of the chip’s subsystems, a watchdog timeout (the “watchdog bite”) or a firmware panic. The same post explains why some screens say minidump: instead of a full memory copy, which can be 12 GB or more, the phone saves only the small regions the software registered in advance.
For you as an owner, the important part is simple. The screen means “the system crashed”, not “the phone is dead”. The dump it waits for is for the manufacturer, and you don’t need to collect anything.
How to get out of Qualcomm CrashDump Mode
A forced restart gets most phones out. The exact buttons depend on the brand.
- Unplug the phone from any computer. Crash dump mode waits for a USB collection, so leave it on a wall charger or nothing at all.
- Hold the force-restart buttons for your brand (table below) and keep holding until the logo appears.
- Let it boot fully, then charge it if the battery is low and check for a system update.
- If it goes straight back to CrashDump, hold Power + Volume Down from the black screen to try reaching fastboot or the bootloader menu, choose Start or Reboot with the volume keys, and confirm with Power. Owners in the UBports thread used Volume Down + Power to get back to fastboot, and Sammy Fans suggests the same Start option for stuck Nothing Phone (2) units.
| Brand | Force restart | Source |
|---|---|---|
| Nothing Phone | Hold Power for 15 seconds or longer | Nothing Support |
| OnePlus (Nord shown) | Hold Volume Up + Power, let go when the OnePlus logo shows (10 to 15 seconds in total) | iFixit guide |
| OnePlus 9 Pro (owner report) | Power + Volume Up restarted it after each crash | /e/OS forum |
| Other Snapdragon phones | Try Power + Volume Up first, then Power alone held for 15 to 20 seconds | Check your maker’s support site |
Holding the button and getting nothing? Plug into a wall charger for 20 to 30 minutes and try again. A phone that crashed at low battery may not have enough charge to finish booting.
Why does my phone keep going into crash dump mode?
Repeated crashes usually come from software you can change. Work down this list in order, since the first items cost you nothing.
A recent system update
Fresh firmware is the classic trigger, and phone makers do pull updates for this. OnePlus, for example, paused its OxygenOS 16.0.7 and 16.0.5 rollouts after what it called “abnormal restart and boot issues” on a small number of devices, according to PhoneArena. If crashes started right after an update, check Settings > System > System update (the path varies a little by brand) for a follow-up patch, and keep an eye on your maker’s community forum. Skipping a fix update is the worst option here.
An app that crashes the system
Ordinary apps can’t usually bring down the kernel, but ones with deep access (launchers, system tweakers, VPNs, call recorders, battery “optimisers”) sometimes can. Google’s safe mode guide is the tool: start the phone in safe mode, which loads only preinstalled apps, and use it for a while. If the crashes stop, remove recently installed apps one at a time, restarting normally after each, until the problem is gone. Google suggests screenshotting your home screen first, since safe mode removes some widgets.
A rooted phone, custom kernel or custom ROM
If you’ve unlocked the bootloader and changed anything, assume that’s the cause until proven otherwise. Reflash the stock firmware for your exact model and region from the maker. This erases the phone.
A system that’s been corrupted
When safe mode doesn’t help and you’re on stock software, a factory reset is the next step. Google’s reset page is blunt: it erases all your data, you’ll need your Google account username and password to sign back in afterwards, and it can take up to an hour, so charge to at least 70% first. Back up photos and chats before you do it.
Failing hardware
If the phone crashes into CrashDump even after a reset, or can’t stay on long enough to reset, take it in. Owners in the TechEnclave and Nothing Community threads ended up with motherboard diagnoses after software fixes failed. Under warranty, that’s the manufacturer’s job, so don’t let a third-party shop open the phone first.
Is CrashDump Mode the same as EDL mode?
No, though both are Qualcomm-specific and both talk to a computer over USB. CrashDump appears after a crash and waits for a memory dump. Emergency Download mode, as Wikipedia summarises it, lives in the chip’s boot ROM and is used to reflash a bricked phone; on a PC it shows up as “Qualcomm HS-USB QD-Loader 9008”. Service centres and advanced users use EDL with tools like the MSM download tool to restore stock firmware when nothing else boots.
If your phone is fine but slow or freezing rather than crashing outright, our guide to the “Process system isn’t responding” error on Android covers the milder version of the problem. Tablet owners heading for a reset can follow how to reset an Android tablet.
Frequently asked questions
Does Qualcomm CrashDump Mode delete my data?
No. The crash screen itself doesn’t erase anything, and a forced restart keeps your files. Data is only lost if you go on to factory reset or reflash the phone.
Is Qualcomm CrashDump Mode a virus?
No. It’s a built-in debugging state on Snapdragon phones that appears after a serious system crash. Malware isn’t a typical cause; updates, apps with deep system access and modified software are far more common.
Which phones can show Qualcomm CrashDump Mode?
Any phone with a Qualcomm Snapdragon chip whose maker leaves the crash screen enabled. Most owner reports come from OnePlus and Nothing phones; brands with their own crash screens show a different message.
Why does the screen say minidump?
Minidump is a smaller crash record that saves only the memory regions the software registered in advance, instead of a full RAM copy that can reach 12 GB or more, according to Qualcomm.
Should I connect the phone to my PC while it’s in CrashDump Mode?
Only if your manufacturer’s support asks you to collect a dump. Otherwise there’s nothing for you to retrieve, so force restart it instead.
Will a repair shop fix crash dump mode?
If it’s software, a reflash usually fixes it; if it keeps returning after a clean reinstall, the board is the likely cause. Use the manufacturer’s service while the phone is under warranty.
Featured image: Dsr07 / Wikimedia Commons
