[OnePlus 7 Pro Guides, News, & Discussion] A.Noob:
Before you start, make sure to put all of the files that you need in the same folder as your adb.exe and fastboot.exe because it will make things easier when you have to fastboot files to your phone. Make sure to follow the directions from the original developers of the tools below. Also, in the windows file explorer, right click on the "Name" tab, in the pop up click "More," select "Path," and also select "Folder Path," then click "Okay." This will make it easier to find the file path name if you need it when you are flashing a specific file to your phone using ADB.

Once you navigate to your android fastboot/adb folder, at the top of your file explorer, click in the address bar, this will highlight the text blue in the address bar, delete the text in the address bar, type CMD and then press enter. The adb/fastboot command window will pop up and be ready for you to use. You may as well leave that command window, the MSM tool, credits: Lucifer6: https://xdaforums.com/t/msm-tool-guac-for-all.3934691/ and the Tool all in One, credits: mauronofrio: https://xdaforums.com/t/rom-stock-f...boot-roms-for-oneplus-7-pro-7-pro-5g.3931424/ , https://toolaio.tk/ open in case one of these tools decides to bite you in the brain so hard your phone melts into booting itself properly.

You'll be needing this Twrp.img from this post if you're on android 11 like I am, credits: Nebrassy:

https://xdaforums.com/t/recovery-11-unofficial-teamwin-recovery-project.4289455/

And Magisk, credit: topjohnwu, which can be downloaded from Step 1 in this article https://www.xda-developers.com/how-to-install-magisk/

Credit: Sumukh for the article (code word the instructions in this article are for a different breed of TWRP then the one needed for rooting android 11 OnePlus 7 Pro, so please after booting into TWRP go to "Advanced," then in the list click "Flash Current TWRP," then reboot straight back to TWRP, flash Magisk, then reboot straight back to TWRP, then flash Magisk again, and then reboot the system ((if possible at this time)) or you'll have boot loops for breakfast), credits: topjohnwu for Magisk

And the android 11 stock rom of your oneplus 7 pro which can be found here, credit OPTeam: https://xdaforums.com/t/oneplus-7-pro-5g-rom-ota-oxygen-os-repo-of-oxygen-os-builds.3930585/

I wasn't able to use MSM Tool by Lucifer6 because my phone didn't want to be recognized by my computer and I am not sure the files exist for android 11 to work with the MSM Tool, but if they do exist or there is a way to use the android 11 zip with the MSM Tool, please someone post it with detailed instructions so that everyone can find it.

I couldn't get the Tool All in One to work because I don't know, however, there are important files in mauronofrio's zip file in this post: https://xdaforums.com/t/rom-stock-f...boot-roms-for-oneplus-7-pro-7-pro-5g.3931424/ Grab the zip file from the link next to "All Roms on AFH." This can help get your phone back from the nightmare of the qualcomm crashdump scenario. If you are on android 11, do not flash the images in this zip folder because the zips in this post are for android 10 and I don't think you can downgrade. There are more directions about this in number 3 of this post.

If at any point you are able to boot your phone into the system, DO NOT put a password, fingerprints, facelock, swipe pattern, nudey collage on your phone to lock it up until AFTER you are sure you are completely done using TWRP, because Nebrassy's TWRP, as far as I know, is not supposed to be able to decrypt the phone once it has a nudey papier-mâché password on it. So, once you put a password on your phone, you may not be able to use TWRP again unless you like pain.

And yes, I did try, in the past week to clean install my rom, made sure to not create a password, flash TWRP and magisk, make a password for the phone, realized I needed to do something else in TWRP, deleted my papier-mâché password and the fingerprints to go along with and then try to get back into TWRP. It's really a hit or miss. You may get back in, you may end up flashing something only for it to get stuck in a TWRP booting boot loop like I did.

It's risky. Take off your password to your phone, then TWRP it up, say your goodbyes to TWRP and then finish setting up your phone with a password. Also, you may have to try plugging the OEM charging cable into different USB ports on your computer at specifically any time.

There are three different recipes that I tried to get my phone to work again after crash dumping. Any one of these could help. For me, it took doing all three, trial and error and error and error for my phone to get booted and rooted after the crash dump so you can try doing the easiest looking ones first, which are number 1 and number 2, see if that works, and then move on to the harder one.

Read all three recipes first before you try anything because some things from number two you can use in one or three. You're in for a real one right now so relax and get comfy. Take your time and make sure you follow the directions in the original posts by the developers because it will waste less of your time if you make sure you extract everything and other scientific ratchet. And you'll make less of a mess of your phone than it already is.

It's bricked, not dead. Hopefully. Hopefully, it's not dead. And I'm not much for hope nor am I much for being blamed if your phone slips into an endless hell pit, it contacts a plane's black box and directs said plane to land onto your roof, or some other maniacal nonsense backwater dribble okay let's get started.

1.) Easy: I used a combination of movements buttons including power off and volume down, only volume up and volume down which did other things, and power off and volume up. At first, none of these movements buttons would take me to fastboot mode. It would just keep rebooting to qualcomm crashdump mode no matter what.

Flustered, red, breathing hard because I don't walk enough, I tried these movements buttons again and again and again and again and not always in the order I wrote them down. I kept trying until I saw some Chinese writing.

Choose the first option even if you can't read the text. Guess where the "Okay" (bottom right) is and click it. The text--the first option--is highlighted in blue, which I should have said in the first place. Hopefully after twitching that phone for a good 30-45 minutes or more depending on how long you like crying, it will finally boot into fastboot mode. Plug the phone to the windows, fastboot boot the twrp.img from Nebrassy in the CMD window. If you are still trying to root, grab a usb or an external hard drive that has the rom zip and the latest magisk.apk that you need for your phone (directions below). If you are not trying to root, grab a usb or an external hard drive that has the rom zip and just flash the rom and that's it (directions below).

Plug the USB storage into your phone. On twrp go to "Mount," click the checkbox next to "USB Storage," click "Select Storage," then in the pop up click the circle next to your USB or external hard drive or whatever you're using. Go to "Install," select the zip of the rom on your USB Storage, click "Install."

You can then flash twrp afterwards by going back in the past and selecting to have TWRP flashed automatically after a rom installation; it's in the options. Or by going to "Advanced," then click "Flash Current TWRP" (mind you this is for the Oneplus 7 Pro using the TWRP 3.5.2_11-Nebrassy image in October of 2021, so if you're reading this and have a different phone or you're from the future, please, don't laugh at me if the current way of flashing TWRP is outdated by the time you read this).

Then you must flash magisk, reboot to TWRP recovery, and then flash magisk again or else the phone won't boot. After flashing magisk that second time, you may reboot the system. Once you get past those sussy terms and voluntary agreements, magisk will look like an android 1 icon. Click it.

The phone will ask you for your hand in marriage by asking if you are truly ready to jump off the deep end by allowing magisk to install unknown apps. Click I do, and magisk will install. Then, magisk will ask you to install the other half of itself, and again, make that app yo baby momma by saying yes, yes, yes. And now you have a new phone with none of your old life to spy on you and tell you how good you weren't in the past or whatever.

3.) Not so easy, but manageable. Caution, read slowly: Another thing I did try was to flash all of the images in the stock rom zip. You can download the correct rom for your phone in this post, credit OPTeam: https://xdaforums.com/t/oneplus-7-pro-5g-rom-ota-oxygen-os-repo-of-oxygen-os-builds.3930585/ ,search the googles, or use the OEM website. Then, use the payload dumper method from here: credits to djsubterrain

https://xdaforums.com/t/how-to-extr...ot-image-and-apply-root-to-the-phone.4263811/

After I djsubterrained my payload, all of this sounding unnecessarily dirty, I put it in this other thing that I tried (directions below): credits to mauronofrio

https://xdaforums.com/t/rom-stock-f...boot-roms-for-oneplus-7-pro-7-pro-5g.3931424/

I downloaded the zip file from the above post in the link next to "All roms on AFH." Extract it. Once I did the dump on my payload, I took all of the extracted images from the "payload_output" folder, put them in a new folder inside of mauronofrio's extracted zip folder, named that new folder "images," and just renamed the original "images" folder that was in the zip file to something else.

In mauronofrio's extracted zip folder, I copied the file named "flash-all-partitions-fastboot.bat" from the "Others_flashall" folder and pasted it into my new "images" folder. I double clicked on the "flash-all-partitions-fastboot.bat" file. An alluring window opened and I typed "Y" for yasss and then clicked "Enter."

And then that flashed most of the images to the phone. Not all of the images flashed. Some of them said "failed," but the important ones like the system.img and boot.img, among others, flashed successfully. I have no idea if using that specific ".bat" file was the right one for my situation because I wasn't sure if I was wearing comfy enough pants to be seen by the oracle.

After that, I did the the whole fastboot boot to TWRP and flashed the zip rom over again using my USB storage because it was easier for me to do that than to figure out how to adb sideload when the adb sideload button in TWRP wasn't working and while I was crash dumping for qualcomm, my phone refused to be recognized by the Tool All In One and the MSM Tool. Then I flashed TWRP, then I flashed magisk, rebooted to recovery, flashed magisk again, and then I tried to reboot to the system. But my phone booted back to twrp, a lot, a lot of times before the end of this story.

2.) Also easy: I think from TRWP (or you can use the power and volume buttons mantra from number one) I clicked on reboot the bootloader from fastboot mode. I used the up and down volume buttons to select "Bootloader" or "Start" (do both until the "Boot Reason" screen shows up for you).

For whatever reason I clicked "Boot Reason" and the reason was something made up like fs_mgr_mount_all. I clicked "Next" at the bottom of the screen and it asked me to wipe everything like music and photos which I already thought were long gone. But I have a backup of my music and my photos so no big deal.

I clicked on "wipe all data," and my phone finally booted back up into the OS. I went through the completely voluntary terms and conditions and voluntarily, completely voluntarily, and no one else is here with me, agreed to the voluntary terms and conditions. And then I clicked on the android 1 icon for magisk and...

At some point in time I formatted the system using TWRP after flashing the zips and the stuffs and now even though my phone says encrypted, the first time I booted back to twrp after finishing setting up my phone and putting a password on it, TWRP said that it decrypted USER 0 after putting my password into TWRP. I have no idea how it happened.

Nebrassy's TWRP is not supposed to be able to do that for android 11 as far as I know. About 30 mins later I booted back to TWRP just to see what would happen, and sure enough it took my password and decrypted my phone. Even though I am on android 11, rooted with a TWRP that is not supposed to be able to decrypt USER 0. I don't know how. Maybe I'll try to upload a log file so that can be figured out, or maybe by now it has already been figured out. Don't know.

So, that was fun, I hope you were able to get out of the crashdump by any of the means used here or not here. If you were able to get out of the qualcomm crashdump some other way or have advice on how any of the recipes could have been cooked better please post it in a forum or in this thread or sector B.92-80 of space so that no one ever comes close to using the very last tears their body has to offer.

I'm sorry if I forgot to give credit to anyone but at this point you'll have to flash me into recovery to get it. Or just say "I belong in here too," and post a link to your something helpful.