Your OnePlus 7 Pro shows Qualcomm CrashDump Mode, and Android will not start. Start with a hardware restart that does not intentionally erase your data, then use the phone’s response to choose the next step. If the screen keeps returning, get a diagnosis before attempting anything that wipes the phone.
Try a force restart first
A startup failure does not reveal its cause through the CrashDump screen alone, so begin with the OnePlus 7 Pro’s non-erasing hardware restart.
Hold Power and Volume Up together for 10 seconds.
If the phone switches off instead of restarting, press Power to turn it on.
Back up your data immediately if Android starts. Resetting or reflashing risks destroying the files you want to recover.
If Android still will not start, check recovery access
Stock recovery lets you check whether the phone responds outside normal startup. Entering it alone neither repairs the phone nor erases your data.
With the phone powered off, hold Power and Volume Down together to enter recovery.
Menu labels depend on the installed OxygenOS version, and custom recovery interfaces differ. Do not substitute a data wipe for a missing cache-only option. Reaching recovery does not establish that a reset will fix the problem.
If recovery will not open, or the phone keeps returning to CrashDump Mode, request OnePlus diagnosis using the repair steps below.
Remove a suspect app once Android is accessible
If trouble followed a recent app installation and Android now starts, test the suspected app; this method is unavailable before Android starts and does not establish a cure for persistent CrashDump Mode.
- 1.Open Google Play Store and tap your profile icon.
- 2.Select Manage apps & devices, then Manage.
- 3.Select the suspected app and tap Uninstall.
- 4.Restart the phone and test it before removing another app.
Get persistent startup failures diagnosed
Diagnosis addresses persistent startup failures without assuming a particular motherboard component has failed.
Open the OnePlus US repair page, or your regional OnePlus service page outside the US.
On the US page, select Request Repair.
Describe the CrashDump screen in your application, including whether a restart restored Android and whether recovery opened.
Expect the repair to erase the phone. OnePlus states that your data will be erased during the repair process, and asks you to back up all personal data and to remove the SIM card and security lock before shipping.
Ask OnePlus to confirm OnePlus 7 Pro service eligibility and parts availability before sending the phone.
Submit your repair application.
Follow the shipping instructions supplied for your accepted repair request.
Use My Service Requests to track the case.
Disable Magisk modules on an already-rooted phone
This method applies to an already-rooted phone using Magisk when a module causes the boot failure. Magisk documents the shortcut, but OnePlus does not endorse it, and it cannot resolve failures occurring before Magisk executes.
During startup, begin holding Volume Down several seconds before the boot animation.
Release Volume Down when the animation appears to trigger Magisk’s module-disabling mode. Timing matters: continuing to hold the button through startup can also activate Android Safe Mode.
Back up immediately if the phone reaches Android.
Use ADB only with an existing authorized connection
This Magisk alternative requires an already-rooted phone, previously enabled USB debugging, a previously authorized computer, and a functioning Android ADB shell; a CrashDump-only or Qualcomm download-mode USB connection is insufficient.
- 1.If the computer needs ADB, download the Windows, Mac, or Linux package from Google’s Android SDK Platform-Tools page. Installing these tools alone does not repair the phone.
- 2.Connect the phone to the previously authorized computer.
- 3.Run
adb devicesand check for an authorized Android connection. Stop if that connection is unavailable. - 4.Run
adb shellto open the Android shell. - 5.Run
magisk --remove-modules. Magisk removes the modules and restarts the device.
Keep older reset and flashing advice in perspective
Older instructions cover stock-recovery wipes, factory resets through the original Settings interface, the original updater, and an OxygenOS 12-to-11 rollback. Those procedures apply to particular interfaces and builds. Resets and rollbacks erase data, so confirm compatibility with OnePlus before considering them.
Check the OnePlus software-download page for official package availability before considering firmware.
Ask OnePlus to confirm that any proposed package matches your exact model, region, and carrier. Firmware and instructions are not interchangeable across variants.
MSM Download Tool and EDL reflashing, firmware flashing over Fastboot, boot-slot switching, and recovery cache wiping have no established current OnePlus-supported consumer procedure covering the relevant OnePlus 7 Pro builds.
Bootloader unlocking is the exception. OnePlus still publishes an official unlock procedure that names the OnePlus 7 Pro among its applicable models. It is not a CrashDump repair: it requires a phone that still boots far enough to enable OEM unlocking under Settings > System > Developer options, and OnePlus warns that unlocking can leave the user data partition inaccessible and ends official software upgrades.
If OnePlus cannot confirm a compatible software recovery route, request a repair assessment and clarify data-erasure requirements before authorizing work.
Frequently Asked Questions
Will remotely erasing the phone repair CrashDump Mode?
Remote erasure is not firmware repair. Do not use it as a CrashDump troubleshooting step.
Should I try heating or freezing the phone?
Heating, freezing, pressing chips, and DIY reflow or reballing are not documented OnePlus consumer fixes. Arrange a repair assessment for persistent startup failure.
Was OxygenOS 12 MP3 the final OnePlus 7 Pro release?
OnePlus published an OxygenOS 12 H.41 announcement after the earlier MP3 announcement called MP3 the last release. That history does not establish one latest build for every region, carrier, or variant.