Related
I've been running CM 11 for a little more than a month and have been really enjoying it. So, I have no idea why I decided to download the MythTools and revert back to stock At&t. Doing so, I messed something up on my phone.
To start, I'm using Windows 7 64bit and when selecting option 1 (install ADB-fastboot-apkTools) I get the new cmd window that states "please select install button after new window is opened press any key to continue...." when I press any key the cmd window would just close. Hoping it would help, I then chose option 6 to update my Motorola drivers. When my browser window opened I got the ADB installer window and clicked install. It seemed to have installed fine. I then updated my moto drivers. Thinking I was all set I went for option 2 to flash the stock firmware which I had put in the firmware folder. With my phone in fastboot I started the process and it failed. Reading through the cmd prompts I had noticed it said something like 'you selected 2- instal cwm.img cannot load cwm.img' . I unplugged my phone and tried to restart it and it was stuck on the bootloader screen. I then restarted into recovery and my PhilZ recovery did start up. However it displays "E: could not mount /data to setup /data/media path!" . I was still able to go through the process of a clean re-install of CM 11 but am stuck on the startup splash screen for CM.
I definitely got myself in way too deep and am clueless on how to fix this. Would someone mind instructing me on what to try next? Many thanks in advance.
I am not sure if it would make a difference in your situation but I do everything for my phone on an x86 system. I have had issues with LG and Samsung phones in the past when trying things on an x64 computer.
ifixgse said:
I've been running CM 11 for a little more than a month and have been really enjoying it. So, I have no idea why I decided to download the MythTools and revert back to stock At&t. Doing so, I messed something up on my phone.
To start, I'm using Windows 7 64bit and when selecting option 1 (install ADB-fastboot-apkTools) I get the new cmd window that states "please select install button after new window is opened press any key to continue...." when I press any key the cmd window would just close. Hoping it would help, I then chose option 6 to update my Motorola drivers. When my browser window opened I got the ADB installer window and clicked install. It seemed to have installed fine. I then updated my moto drivers. Thinking I was all set I went for option 2 to flash the stock firmware which I had put in the firmware folder. With my phone in fastboot I started the process and it failed. Reading through the cmd prompts I had noticed it said something like 'you selected 2- instal cwm.img cannot load cwm.img' . I unplugged my phone and tried to restart it and it was stuck on the bootloader screen. I then restarted into recovery and my PhilZ recovery did start up. However it displays "E: could not mount /data to setup /data/media path!" . I was still able to go through the process of a clean re-install of CM 11 but am stuck on the startup splash screen for CM.
I definitely got myself in way too deep and am clueless on how to fix this. Would someone mind instructing me on what to try next? Many thanks in advance.
Click to expand...
Click to collapse
you said you are stuck on startup splash meaning bootloop? if it is you should try again with rsd lite.
else you may lose all your data in the memory but do a format media/data and sdcard, so that it can mount /data, it worked for me. then format system mount everyting and do a fresh install of any rom you can sideload or just have it in the sdcard.
I'm pretty sure I am doing something wrong with MythTools. When I select option 2 in the tool to install stock firmware the following happens,
- asks for fimware folder example and I select "N"
- asks if firmware files are finished copying.. I press enter and continue
-then it says "the system cannot find the path specified
the system cannot find the path specified
the system cannot find the path specified
'7z' is not recognized as an internal or external command
operable program or batch file
Are you ready to flash stock fimware...
at this point i stupidly hit enter and that was it with my phone. I'm guessing the tool could not locate the firmware .xml file for extracting and I have no idea why. The compressed folder is IN the firmware folder.
One other question with Mythtools, when installing the tools what path do you want them installed in? I did them in the same file the Myth tools are in.
ifixgse said:
I'm pretty sure I am doing something wrong with MythTools. When I select option 2 in the tool to install stock firmware the following happens,
- asks for fimware folder example and I select "N"
- asks if firmware files are finished copying.. I press enter and continue
-then it says "the system cannot find the path specified
the system cannot find the path specified
the system cannot find the path specified
'7z' is not recognized as an internal or external command
operable program or batch file
Are you ready to flash stock fimware...
at this point i stupidly hit enter and that was it with my phone. I'm guessing the tool could not locate the firmware .xml file for extracting and I have no idea why. The compressed folder is IN the firmware folder.
One other question with Mythtools, when installing the tools what path do you want them installed in? I did them in the same file the Myth tools are in.
Click to expand...
Click to collapse
Disclaimer: Even though this worked for me I am not responsible if you brick your phone, I am simply sharing my experience
Okay, this is not for the faint of heart and is going to sound a little backward but it just worked for me 5mins ago. I am running Windows 8.1 Pro 64bit, so there shouldn't be a problem with your setup. I was having the same problem until I just double clicked on flashing.bat or main.bat instead of running as admin. After all I AM the admin of my PC. Then, it worked perfect...until flashing the tz.mbn file and froze up while writing the file. I thought mmm...it shouldn't take that long to write such a small file, and writing happens on the phone side (I believe) so I hit the phone's power button while leaving the Myth Tools window open, which disconnected the phone obviously. I booted back into fastboot and it continued from where it left off. (Note: I did this a few weeks ago when I lost my radios and manually flashed the modem file, which froze, but I followed the same procedure and it successfully flashed it) Then when it got to the last system.img chunk (it writes it in small chunks of 30mb and the last one is smaller, that's how I knew it was the last one) it froze again. I let it sit for about 5mins just to make sure it was written to the phone the repeated the sequence to reboot manually into fastboot and bang, once again it continued right where it left off. one or two more freezes and voila...it rebooted right back to stock. Any questions don't hesitate to ask.
If this helps you hit that thanks button!
I have a ME176CX, I upgraded the SO I got the message "it said 'Unable to detect power status' for me was weird but I keep going pressing the volume button it started but in the black screen with this message:
"FastBoot Starting...
FastBoot Starting...#1
FastBoot Starting...#2
FastBoot Starting...#3" I don't know what to do, It doesn't move from this screen.
fran1563 said:
I have a ME176CX, I upgraded the SO I got the message "it said 'Unable to detect power status' for me was weird but I keep going pressing the volume button it started but in the black screen with this message:
"FastBoot Starting...
FastBoot Starting...#1
FastBoot Starting...#2
FastBoot Starting...#3" I don't know what to do, It doesn't move from this screen.
Click to expand...
Click to collapse
Download the lollipop firmware from asus site. Copy the droidboot.img from within this file. Download newest version of tethered cwm recovery. Go to command line and cd to directory with adb.exe in it. Place droidboot.img in this folder. Within cmd, write fastboot boot droidboot.img
It should reboot rto droidboot. Now open the .bat file, type ACCEPT, and T4. You should boot into cwm recovery. Now install zip/from external sd/WW_lollipop....zip
Then reboot and you should have lollipop
I?m the worst to follow what you write, because i'm just barely know press the button ON in my tablet but upgrade what I did this time far away, I taken to a tecnician who said I erased recovery's mode and then he can't handled any way to install the oldest or newest OS, im from Venezuela where ASUS havent support to tablets yet. I'll take what you said and bring it to somebody to know about software android to help me out. By the way I bought another memo pad 7 but model me170cx dual core, actually isnt bad but I want my me176cx back.
Mis012 said:
Download the lollipop firmware from asus site. Copy the droidboot.img from within this file. Download newest version of tethered cwm recovery. Go to command line and cd to directory with adb.exe in it. Place droidboot.img in this folder. Within cmd, write fastboot boot droidboot.img
It should reboot rto droidboot. Now open the .bat file, type ACCEPT, and T4. You should boot into cwm recovery. Now install zip/from external sd/WW_lollipop....zip
Then reboot and you should have lollipop
Click to expand...
Click to collapse
I?m the worst to follow what you write, because i'm just barely know press the button ON in my tablet but upgrade what I did this time far away, I taken to a tecnician who said I erased recovery's mode and then he can't handled any way to install the oldest or newest OS, im from Venezuela where ASUS havent support to tablets yet. I'll take what you said and bring it to somebody to know about software android to help me out. By the way I bought another memo pad 7 but model me170cx dual core, actually isnt bad but I want my me176cx back.
fran1563 said:
I?m the worst to follow what you write, because i'm just barely know press the button ON in my tablet but upgrade what I did this time far away, I taken to a tecnician who said I erased recovery's mode and then he can't handled any way to install the oldest or newest OS, im from Venezuela where ASUS havent support to tablets yet. I'll take what you said and bring it to somebody to know about software android to help me out. By the way I bought another memo pad 7 but model me170cx dual core, actually isnt bad but I want my me176cx back.
Click to expand...
Click to collapse
Just say what you do not understand, I can explain
Mis012 said:
Download the lollipop firmware from asus site. Copy the droidboot.img from within this file. Download newest version of tethered cwm recovery. Go to command line and cd to directory with adb.exe in it. Place droidboot.img in this folder. Within cmd, write fastboot boot droidboot.img
It should reboot rto droidboot. Now open the .bat file, type ACCEPT, and T4. You should boot into cwm recovery. Now install zip/from external sd/WW_lollipop....zip
Then reboot and you should have lollipop
Click to expand...
Click to collapse
Mis012 said:
Just say what you do not understand, I can explain
Click to expand...
Click to collapse
Thank you mate, I'm going to try. I'll write you wherever going to happens. I aprecciate!
Mis012 said:
Download the lollipop firmware from asus site. Copy the droidboot.img from within this file. Download newest version of tethered cwm recovery. Go to command line and cd to directory with adb.exe in it. Place droidboot.img in this folder. Within cmd, write fastboot boot droidboot.img
It should reboot rto droidboot. Now open the .bat file, type ACCEPT, and T4. You should boot into cwm recovery. Now install zip/from external sd/WW_lollipop....zip
Then reboot and you should have lollipop
Click to expand...
Click to collapse
tried fastboot boot droidboot.img several times, device just reboots to fastboot and throws the same errors
Fastboot Starting....
Fastboot Starting....#1
Fastboot Starting....#2
Fastboot Starting....#3
i've searched and found different ways of flashing ME176CX but never a complete solution. With the INtel flash tool I can't find the DNX or IFWI files, with the Asus Flash Tool, cant find the raw firmware file. Can you help???
christelle868 said:
tried fastboot boot droidboot.img several times, device just reboots to fastboot and throws the same errors
Fastboot Starting....
Fastboot Starting....#1
Fastboot Starting....#2
Fastboot Starting....#3
i've searched and found different ways of flashing ME176CX but never a complete solution. With the INtel flash tool I can't find the DNX or IFWI files, with the Asus Flash Tool, cant find the raw firmware file. Can you help???
Click to expand...
Click to collapse
I can try to. Firstly, the droidboot.img has to be the one from ASUS firmware update downloaded from their site. If it doesn't work with it, well I don't know. Ask the support, take it to the store, or - if you really want to dig into it (it should be possible in your situation), then:
Firstly, buy this: (or something similar, but this is known to work well) http://www.amazon.de/gp/product/B00...qid=1440605402&ref_=sr_1_fkmr0_1&sr=8-1-fkmr0
Then, connect it to your tablet and connect usb keyboard to it. Also power it with another USB.
While starting your tablet, spam F2 key to get in UEFI setup. Then, follow some "tutorial" (search this forum for it, I saw it somewhere there) to run Windows/Ubuntu from flash disk. Run any linux distribution, and ask some kind person on lollipop to make an img with dd of entire mmcblk0 . Then use dd to copy it on your mmcblk0.
Warning! this is theoretical. It should work, but I cannot test it. CHECK MULTIPLE TIMES THAT THE img IS NOT CORRUPTED!!!
Lot of luck (even mine, luck will not help my problem anyway)
Sincerely, Mis012
Mis012 said:
I can try to. Firstly, the droidboot.img has to be the one from ASUS firmware update downloaded from their site. If it doesn't work with it, well I don't know. Ask the support, take it to the store, or - if you really want to dig into it (it should be possible in your situation), then:
Firstly, buy this: (or something similar, but this is known to work well) http://www.amazon.de/gp/product/B00...qid=1440605402&ref_=sr_1_fkmr0_1&sr=8-1-fkmr0
Then, connect it to your tablet and connect usb keyboard to it. Also power it with another USB.
While starting your tablet, spam F2 key to get in UEFI setup. Then, follow some "tutorial" (search this forum for it, I saw it somewhere there) to run Windows/Ubuntu from flash disk. Run any linux distribution, and ask some kind person on lollipop to make an img with dd of entire mmcblk0 . Then use dd to copy it on your mmcblk0.
Warning! this is theoretical. It should work, but I cannot test it. CHECK MULTIPLE TIMES THAT THE img IS NOT CORRUPTED!!!
Lot of luck (even mine, luck will not help my problem anyway)
Sincerely, Mis012
Click to expand...
Click to collapse
i think he got lost on your tutorial XD
fastboot starting
Please, Please advice ..
And I'm one of those tablets which displays a message starting fastboot 1,2,3. I tried almost everything. Well at least I think that everything is okay or if vv. Please advice how to try it changed. Thank you in advance for answers
I have my bosses Mi Note Pro here. I attempted to get it to run the Google Now
Homescreen and the phone no longer boots. I can get into fastboot and I can install TWRP but I can't access the internal storage so I can't restore from there.
I am repeatedly trying to download either of the ROMS listed on http://en.miui.com/a-234.html but it keeps falling over on the download.
Is there anywhere I can download a fastboot installable rom that has english on it?
Please help, this is desperately urgent!!!
Thanks
OK panic over - I got it back, using TWRP and an external USB thumb drive with the files I needed on it.
That was too hard - note to self - NEVER BUY A PHONE WITHOUT REMOVABLE STORAGE!!
Still cant replace the standard launcher. Still cant get google play to be the default source for software. Keyboard has still got chinese on it.......
use leo rom from xiaomi.eu
maxgreece said:
I have my bosses Mi Note Pro here. I attempted to get it to run the Google Now
Homescreen and the phone no longer boots. I can get into fastboot and I can install TWRP but I can't access the internal storage so I can't restore from there.
I am repeatedly trying to download either of the ROMS listed on http://en.miui.com/a-234.html but it keeps falling over on the download.
Is there anywhere I can download a fastboot installable rom that has english on it?
Please help, this is desperately urgent!!!
Thanks
Click to expand...
Click to collapse
Download fastboot rom from here: stable: http://update.miui.com/updates/v1/fullromdownload.php?d=leo&b=F&r=cn&n= developer: http://update.miui.com/updates/v1/fullromdownload.php?d=leo&b=X&r=cn&n=
Download, install and run Mi Flash from here: http://bigota.d.miui.com/tools/MiPhone2015731.exe
Turn off the device. Press the Volume– key and the Power button at the same time to enter Fastboot mode. Then connect the device to the Windows PC/laptop via a micro USB cable
Decompress the downloaded fastboot rom. Open the file folder for the decompressed ROM pack, and copy its path on the computer.
open MiFlash.exe and paste into the address bar the ROM file folder path copied in the last step.
Click on Refresh, and MiFlash should automatically recognize the device. Then click flash to flash the ROM file to the device.
Wait until the progress bar inside MiFlash turns fully green, which means the ROM has been successfully installed. Then your device should automatically boot to the new version.
Already done but many thanks for the input. I figured out twrp recognizes external thumb drives..... That saved me!!
Tried to download the rooms you mentioned but the downloads kept bombing out.
I am having a very similar problem but am having difficulty downloading the Fastboot ROM. I don't know whether it's because the files are hosted in China (and I am in the UK) but the download gets to about 4 or 5 MB then stops every time. I've tried a few different URLs including the one mentioned above.
Does anyone have the Mi Note (Virgo) fastboot ROM files that they would be prepared to upload for me?
Thanks in advance!
Yes, the servers of xiaomi have problems right now. It's difficult to find a working fastboot download link, that doesn't stop after a few hundred MB.
Be careful! Always check the MD5 checksum that is in every filename of xiaomi ROMs. use hashcalc for windows to check it.
Hello,
Can someone share the latest OTA (1may OR april?) of the rom file? I wanted to update flashing stock firmware unrooted and then catch the ota dont work anymore. Maybe sideload the OTA is possible.
https://drive.google.com/open?id=1NSy8XYACTHby3J-P0oNwjpemB2cVTfpI
Sideloading doesn't work. The payload_dumper works but I don't know how to proceed. Please share your solution.
I Will take a look at it. How did you get this file?
hans3103 said:
I Will take a look at it. How did you get this file?
Click to expand...
Click to collapse
connect the phone via usb
adb logcat > ota.txt
start the update checker on the phone
when it's done checking for updates, kill the adb process with ctrl-c
open ota.txt in a text editor, and find "UpdaterEngineHelper". There should be a downloadURL that looks likes this:
https:\/\/dlmgr.gtm.svcmot.com\/dl\/dlws\/1\/download\/pVVhGqfAoWboVIqb838eEonkj9%2FmlRBFuisKgbOUteZFGF0LVIr3fZGsyTBNleklN%2BvGu2j4xooz5Ky%2Fve7SfcLy%2BnAgSPiBhHVKQMS9PezFINpjNHvv0LiZfFTgkal53FtJpWmVmq9HjFdA9BLys8YW5j8U%2BumAog%2FEuma8ykNSVc6LsgTBb%2FTsECF2QrMF
remove the backslashes from the URL and paste the result in a browser. It will download a zip file.
Note that this download URL will only be available for a limited amount of time.
mijm said:
connect the phone via usb
adb logcat > ota.txt
start the update checker on the phone
when it's done checking for updates, kill the adb process with ctrl-c
open ota.txt in a text editor, and find "UpdaterEngineHelper". There should be a downloadURL that looks likes this:
https:\/\/dlmgr.gtm.svcmot.com\/dl\/dlws\/1\/download\/pVVhGqfAoWboVIqb838eEonkj9%2FmlRBFuisKgbOUteZFGF0LVIr3fZGsyTBNleklN%2BvGu2j4xooz5Ky%2Fve7SfcLy%2BnAgSPiBhHVKQMS9PezFINpjNHvv0LiZfFTgkal53FtJpWmVmq9HjFdA9BLys8YW5j8U%2BumAog%2FEuma8ykNSVc6LsgTBb%2FTsECF2QrMF
remove the backslashes from the URL and paste the result in a browser. It will download a zip file.
Note that this download URL will only be available for a limited amount of time.
Click to expand...
Click to collapse
Thanks for taking the time to offer this. Should I be able to use the download text (minus \'s) here? After removing the \'s, I get "Access to dlmgr.gtm.svcmot.com was denied." Maybe it must be done from one's phone. Is the file from your G-drive a flashable one (adb sideload)? This looked a lot like what was on my phone after I transferred the Smart Assistant app download to my phone. I didn't try to apply the "Update from SD card." I sent my phone in for repair yesterday so I can't check. I was fairly certain that if I could reflash the OPSW28.70-31-12 update (Feb, but this one may have done the job, too), my issues (mainly, no baseband after update), would be corrected. So much is different from my Google phones os and ota, but I'm trying to understand.
Hi, I managed to download the zip file from my computer. It should simply work but keep in mind that it will expire after some time. The URL I posted is just an example and it has already expired.
Sideloading the ota zip doesn't work. You can use the payload_dumper Python script to extract the images from the payload file, and then these files will have to flashed from the bootloader. I tried this a couple of times but failed.
The payload_dumper extracts these files:
.gitkeep
abl.img
bluetooth.img
boot.img
cmnlib.img
cmnlib64.img
devcfg.img
dsp.img
fsg.img
hyp.img
keymaster.img
logo.img
modem.img
oem.img
pmic.img
prov.img
rpm.img
storsec.img
system.img
tz.img
vendor.img
xbl.img
I can share those too if needed.
Thanks, again. As I don't know my way around MOTO phone world, I haven't yet unlocked the bootloader so flashing images is not available. I misunderstood about the zip file thinking it would be an installable file--like Google ota's. I appreciate the lesson on the payload extraction. I'll have to learn how to use that with the files Smart Assistant downloaded.
mijm said:
You can use the payload_dumper Python script to extract the images from the payload file, and then these files will have to flashed from the bootloader. I tried this a couple of times but failed.
.
Click to expand...
Click to collapse
It took me a couple of days (I'm NOT a programming person--71 yr old retired English teacher) to get this working (installing python, setting variables, updating pip, installing virtualenv, installing protobuf--each step requiring web search) but I was able to extract payload.bin. At least I believe I could do this, unlock my bootloader, and try installing .img files if I choose to. For certain, the modem.img is in the file set. I have no idea (I wonder if MOTO does) why the modem did not get flashed. I'll never use the "Smart" Assistant again.
You led me in the right direction which could have taken weeks otherwise. Thanks.
No problem. Please let me know how if and how you manage to flash the images. Every time I tried I got stuck in a bootloop so I must have been doing something wrong.
It sounds scary... :laugh:
Well, I have an idea of how to flash them but some of them confuse me. If you look at this post, it explains how to flash:
https://forum.xda-developers.com/z3-play/how-to/firmware-oficial-9-0-0-pie-instalacion-t3911995
But there are some extra img files in the ota which I don't know what to do with. The fact that the Z3 Play has two partition slots doesn't help.
mijm said:
Well, I have an idea of how to flash them but some of them confuse me. If you look at this post, it explains how to flash:
https://forum.xda-developers.com/z3-play/how-to/firmware-oficial-9-0-0-pie-instalacion-t3911995
But there are some extra img files in the ota which I don't know what to do with. The fact that the Z3 Play has two partition slots doesn't help.
Click to expand...
Click to collapse
Maybe you can answer my question.
I'm afraid I can't answer your question as I don't know how to create a side-loadable zip unfortunately. I would be able to convert the XML into a BAT file without problems -- I could even automate it -- but the OTA package doesn't contain any XML file so there's nothing to go on, at least for flashing the OTA file -- sorry. Meanwhile I'm still waiting for a solution on how to flash the OTA file.
mijm said:
I'm afraid I can't answer your question as I don't know how to create a side-loadable zip unfortunately. I would be able to convert the XML into a BAT file without problems -- I could even automate it -- but the OTA package doesn't contain any XML file so there's nothing to go on, at least for flashing the OTA file -- sorry. Meanwhile I'm still waiting for a solution on how to flash the OTA file.
Click to expand...
Click to collapse
Thanks for responding. I think the process I was questioning should work. The 2.2GB rom files LMSA downloads do have two xml files service and flash. I created a batch file with the service.xml file. The latest update available through the app seems to be 28.70-31-12 which is a second Feb update? This should run through fastboot on locked bootloader. The 91MB ota (May) file I downloaded does not have either of the two xml files but has the payload.bin file which the others do not have. Apparently, MOTO ota's use a delivery system that accesses payload.bin. I'm just brainstorming, but it's mostly a light show with little "BOOM." I am learning some things, though.
I also discovered that the newest (6.2.4) edition of RSD Lite may work on Windows 10--at least the device shows up. This is, supposedly, an official MOTO tool; however, Moto Agents on their forum say it isn't.
Of course, both batch creation and RSD Lite require access to the rom one wishes to flash. Hello, MOTO???? The most recent roms I've found are here.
Today I installed the latest rom that was uploaded on https://mirrors.lolinet.com/firmware/moto/beckham/official/RETAIL/
The one uploaded on 30-5-2019 has the 1 may patch inclusief. It works very good on my XT1929-8. (reteu). After that I rooted it with the latest magisk.
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://forum.xda-developers.com/t/msm-tool-guac-for-all.3934691/ and the Tool all in One, credits: mauronofrio: https://forum.xda-developers.com/t/...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://forum.xda-developers.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://forum.xda-developers.com/t/...a-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://forum.xda-developers.com/t/...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://forum.xda-developers.com/t/...a-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://forum.xda-developers.com/t/...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://forum.xda-developers.com/t/...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.