Rebooted system from TWRP, and got a Qualcomm CrashDump Mode image. - OnePlus 7T Pro 5G McLaren Questions & Answers

Hello everyone. Had TWRP up attempting to install Lineage when I realized Lineage does not support Oneplus 7T Pro McLaren. I was planning on either trying to reinstall Oxygen, or maybe the unofficial Lineage. I am pretty sure I was able to reboot the phone a few times holding power & volume down. I ran into some sort of sideloading issue, rebooted using power & volume down, and tried again, and it seemed to resolve it. I was attempting to sideload one of the images, and I was getting a bad zip format message. I tried to reboot the phone holding the buttons, and it wasn't working. I selected the reboot button within TWRP, and chose system.
It rebooted, and I got the Qualcomm CrashDump Mode image.
I can reboot the phone into fastboot mode holding volume up, & volume down, & power. I don't know where to go from here.

Flash your phone with official firmware

AzimBahar said:
Flash your phone with official firmware
Click to expand...
Click to collapse
Thank you. Downloading stock firmware, and looking for instructions now.

AzimBahar said:
Flash your phone with official firmware
Click to expand...
Click to collapse
Could you please tell me.. Is it possible to use a Windows emulator to use MsmDownloadTool V4.0.exe? I use Linux and have no access to a Windows machine.

Related

TWRP and Root gone for me on Z1 Compact and my USB port is broken. Please help

Hi, I see a lot of posts everywhere, here and on reddit talking about how the latest PA wipes TWRP and root. I've never flashed a rom that did that. I'm not a newbie and would have been able to fix it, but my USB port is broken. I've been charging via the magnetic port. I don't like that people aren't being taken seriously with this request because in most cases, sure you could use flashboot, but in my case I'm locked out of my device.
I would use something like Rashr, but I don't have root. The only way I can think of to get root is to use one of those sketchy apps like KingoRoot and then install Rashr but I have a feeling that would probably brick my device and since it's "usable" (but I can't get into recovery or root it) I should probably cut my losses and sell it.
I think this release should be pulled if it's causing this many problems. If the release is updated with a working TWRP, would I be able to fix it through the PA updater, or is that only system files and no recovery?
We haven't shipped with root in a LOOOOONG time.
I've never seen a ROM flash remove recovery. The ROM itself has nothing to do with recovery, and doesn't actively remove it.
I tried Paranoid Android on my Xperia Z3 Tablet Compact, I liked it a lot, but P.A. breaks TWRP so I'd be forced to reinstall the rom from scratch with every rom update so I can't use P.A.
thommcn said:
I tried Paranoid Android on my Xperia Z3 Tablet Compact, I liked it a lot, but P.A. breaks TWRP so I'd be forced to reinstall the rom from scratch with every rom update so I can't use P.A.
Click to expand...
Click to collapse
Not required . It is very easy to get twrp after flashing PA. It is a problem with sony devices. Follow my guide on how to get twrp, but download the twrp for your device and not for z3 compact
http://forum.xda-developers.com/z3-compact/general/twrp-z3-compact-unlocked-bootloader-t3476868
---------- Post added at 07:11 AM ---------- Previous post was at 07:07 AM ----------
bananabytes said:
Hi, I see a lot of posts everywhere, here and on reddit talking about how the latest PA wipes TWRP and root. I've never flashed a rom that did that. I'm not a newbie and would have been able to fix it, but my USB port is broken. I've been charging via the magnetic port. I don't like that people aren't being taken seriously with this request because in most cases, sure you could use flashboot, but in my case I'm locked out of my device.
I would use something like Rashr, but I don't have root. The only way I can think of to get root is to use one of those sketchy apps like KingoRoot and then install Rashr but I have a feeling that would probably brick my device and since it's "usable" (but I can't get into recovery or root it) I should probably cut my losses and sell it.
I think this release should be pulled if it's causing this many problems. If the release is updated with a working TWRP, would I be able to fix it through the PA updater, or is that only system files and no recovery?
Click to expand...
Click to collapse
Im not a 100% sure this will work, it mostly wont work, but try using kingroot to get root on the device, then use flashfire to flash recovery to boot/FOTA/Recovery partition depending on your device. Then try getting into recovery. But how did you get recovery in the first place if you had a broken USB? Why would you take chances?
Hi panzerox123, Thanks for link to guide but no go - I followed that guide five times and failed five times. It fails at 'To enter recovery mode, power off your phone, and press and hold Vol-down and Power button together until you see the sony logo.', it boots stock android instead. I tried flashing to Recovery and to the FOTAKernel - both failed. Recovery doesn't work with stock or Paranoid Android on this Z3TC but does with CM12 and FreeXperia.
thommcn said:
Hi panzerox123, Thanks for link to guide but no go - I followed that guide five times and failed five times. It fails at 'To enter recovery mode, power off your phone, and press and hold Vol-down and Power button together until you see the sony logo.', it boots stock android instead. I tried flashing to Recovery and to the FOTAKernel - both failed. Recovery doesn't work with stock or Paranoid Android on this Z3TC but does with CM12 and FreeXperia.
Click to expand...
Click to collapse
Really? This is how I got recovery back when I flashed pa. Are you sure fastvoot is working in your device? When you hold vol- and power button for around 10 seconds, you shoyuld see Sony logo, and then screen flashes and enters recovery.
Another question, did you download the correct twrp for your device? The link in the thread is for z3 compact phone
My tablet is the SGP611 'scorpion_windy'. Firmware: SGP611_23.5.A.1.291_UK.ftf TWRP: twrp-3.0.2-0-scorpion_windy.img (https://dl.twrp.me/scorpion_windy/twrp-3.0.2-0-scorpion_windy.img)
Vol- and power buttons are pressed until I get the Sony logo but it doesn't enter recovery - instead the tablet boots. Unlike with CM12, I don't get to see the violet led either.
thommcn said:
My tablet is the SGP611 'scorpion_windy'. Firmware: SGP611_23.5.A.1.291_UK.ftf TWRP: twrp-3.0.2-0-scorpion_windy.img (https://dl.twrp.me/scorpion_windy/twrp-3.0.2-0-scorpion_windy.img)
Vol- and power buttons are pressed until I get the Sony logo but it doesn't enter recovery - instead the tablet boots. Unlike with CM12, I don't get to see the violet led either.
Click to expand...
Click to collapse
Hmmmm very weird... are you on stock or pa?
Wait... Flash the latest firmware available for your device using flashtool. It updates bootloader so you can enter recovery using the above.
If all else fails, there is another method to update pa without starting from scratch every time. Can't explain it right now, I'm on Mt phone, when I get to lapptop , I'll explain
23.5.A.1.291 is the latest firmware that I downloaded with XperiFirm http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
Either stock or P.A. won't enter recovery.
thommcn said:
23.5.A.1.291 is the latest firmware that I downloaded with XperiFirm http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
Click to expand...
Click to collapse
Weird... I'll get back alright... Don't know why there are problems
The only method that will work for stock on this tablet to get recovery right now is this one: http://forum.xda-developers.com/z3-...torial-stock-android-marshmallow-6-0-t3409486 using RecRoot.
As for P.A. - attempting to enter recovery results in continuous bootloops until reset.
thommcn said:
The only method that will work for stock on this tablet to get recovery right now is this one: http://forum.xda-developers.com/z3-...torial-stock-android-marshmallow-6-0-t3409486 using RecRoot.
As for P.A. - attempting to enter recovery results in continuous bootloops until reset.
Click to expand...
Click to collapse
That only happens when the wrong recovery is flashed...
RecRoot is only used with stock because it was designed for the Z3 phone so obviously that is no good for our purposes as would still have to flash the correct version of twrp.
So I either flash the base.img from CM12 (lollipop) scorpion_windy or FreeXperia 6.0.1 (marshmallow) scorpion_windy, then flash TWRP scorpion_windy. Then get into recovery, then wipe dalvik, system, data, cache, then install paranoid android, then wipe dalvik + cache and finally reboot. Well it boots fine but booting in to recovery just ends in bootloops.
thommcn said:
RecRoot is only used with stock because it was designed for the Z3 phone so obviously that is no good for our purposes as would still have to flash the correct version of twrp.
So I either flash the base.img from CM12 (lollipop) scorpion_windy or FreeXperia 6.0.1 (marshmallow) scorpion_windy, then flash TWRP scorpion_windy. Then get into recovery, then wipe dalvik, system, data, cache, then install paranoid android, then wipe dalvik + cache and finally reboot. Well it boots fine but booting in to recovery just ends in bootloops.
Click to expand...
Click to collapse
Same here.
Entering Recovery from ADB or standard hard buttons (USB + Vol-Up several time at boot) caused the boot loops.
The only way I found to enter the Recovery mode is: Unplug USB, Vol-down + Power press at the same time until the sony logo comes up.
igiona said:
Same here.
Entering Recovery from ADB or standard hard buttons (USB + Vol-Up several time at boot) caused the boot loops.
The only way I found to enter the Recovery mode is: Unplug USB, Vol-down + Power press at the same time until the sony logo comes up.
Click to expand...
Click to collapse
That is not how you enter recovery, that is how you enter fastboot mode... To enter recovery, you need to have a recovery installed on the recovery partition. To enter it, press vol-down+power button until you see sony logo and then leave the buttons
panzerox123 said:
That is not how you enter recovery, that is how you enter fastboot mode... To enter recovery, you need to have a recovery installed on the recovery partition. To enter it, press vol-down+power button until you see sony logo and then leave the buttons
Click to expand...
Click to collapse
When the device is normally powered up, the status led turns purple/pink. There if the Volum-up (down as well?) is pressed a couple of time, the LED changes color and the device enters the Recovery mode.
Of course you need a recovery image to be flashed in the recovery partition.
The problem here is that with some ROMs (i.e. AOSPA) is not possible to enter the recovery mode via "purple/pink led" procedure. The device will enter a reboots loop.
This procedure works properly with CM12.1 and CM13.
from "theandroidsoul" (I cannot post outside link yet, sorry).
How to boot into recovery
Switch off your Xperia Z first
Switch it back on and the time when you see your phone’s LED notification light turn purple or pink — start pressing either the Volume UP or Volume Down key a couple of times and your phone will reboot into recovery
Click to expand...
Click to collapse
igiona said:
When the device is normally powered up, the status led turns purple/pink. There if the Volum-up (down as well?) is pressed a couple of time, the LED changes color and the device enters the Recovery mode.
Of course you need a recovery image to be flashed in the recovery partition.
The problem here is that with some ROMs (i.e. AOSPA) is not possible to enter the recovery mode via "purple/pink led" procedure. The device will enter a reboots loop.
This procedure works properly with CM12.1 and CM13.
from "theandroidsoul" (I cannot post outside link yet, sorry).
Click to expand...
Click to collapse
That is when your recovery is embedded with the kernel. If you have the latest marshmallow build for Sony, it allows to to boot into recovery partiton .

Oh ****! Now I have screwed up! Wiped out my system

Hi.
I was trying to root my P8 and followed a guide to install twrp recovery and other stuff. I installed the wrong version of what I think was SuperSu and after that I got stuck at the logo when I started the phone. I went into twrp recovery mode and tried a few things there, which didn't work. Then I wiped out the system. That was dumb as ****. Now I can't do anything. When I start the phone, I only see the Huawei logo and "powered by android" at the bottom. I've been googling a little but can't find a solution.
Is there any way to fix this or am I screwed? I can't buy a new phone at the moment. :/
NedNegel said:
Hi.
I was trying to root my P8 and followed a guide to install twrp recovery and other stuff. I installed the wrong version of what I think was SuperSu and after that I got stuck at the logo when I started the phone. I went into twrp recovery mode and tried a few things there, which didn't work. Then I wiped out the system. That was dumb as ****. Now I can't do anything. When I start the phone, I only see the Huawei logo and "powered by android" at the bottom. I've been googling a little but can't find a solution.
Is there any way to fix this or am I screwed? I can't buy a new phone at the moment. :/
Click to expand...
Click to collapse
Install stock recovery with fastboot and then reinstall your firmware using the dload method.
How do I do that when nothing works?
Did you install twrp
Sent from my GRACE using Tapatalk
I did, but it seems I can't go into twrp mode anymore. I restarted my phone after I was stupid enough to wipe the system. I just got to the Huawei eRecovery EMUI thing, but when i try to download new version and recovery it fails to get package info from network.
NedNegel said:
I did, but it seems I can't go into twrp mode anymore. I restarted my phone after I was stupid enough to wipe the system. I just got to the Huawei eRecovery EMUI thing, but when i try to download new version and recovery it fails to get package info from network.
Click to expand...
Click to collapse
Enter bootloader mode (power + volume down)
Connect to pc
Use adb/fastboot (follow one of the thousands guides on Internet) and flash the twrp recovery.
Then with adb copy a rom into the phone and flash it via twrp
wfonz said:
Enter bootloader mode (power + volume down)
Connect to pc
Use adb/fastboot (follow one of the thousands guides on Internet) and flash the twrp recovery.
Then with adb copy a rom into the phone and flash it via twrp
Click to expand...
Click to collapse
I finally made it.
Most of those thousands of guides I found just said about the same thing as erayrafet: "Install stock recovery with fastboot and then reinstall your firmware using the dload method."
I tried that, I pressed power + volume down and all the other things people said, but nothing happened. . It did not work, and could not reach bootloader mode. Have been trying to make it work since yesterday, and now I finally succeeded. I sat for about 15 minutes and just pressed power + volume down. The phone just restarted over and over, somtimes I got to the Huawei eRecovery EMUI thing, but after about 15 minutes I finally got into bootloader mode.
So it's solved now after I found another guide.
Thanks for trying to help. :good:

Install of LOS, hit snag at TWRP update

Hey everyone,
I was running through the process of installing LOS 15.1 official when I hit a snag. I unlocked the bootloader, installed the Universal O bootloader, and was in the process of updating my version of TWRP. After flashing the image to recovery, I noticed that the TWRP version hadn't updated to the new one. I tried rebooting and that's when the problem started. Now, when I hit power + volume up, I get the ZTE powered by android screen, then 3 flashes of the notification light, and then it powers off. If I hit the power button, it sits on that same ZTE splash screen for what seems like indefinitely. I can't figure out how to get back into TWRP.
Any help is greatly appreciated
You can try flashing twrp via the twrp app
Hey!
Try to reboot the phone, press volume button to get the selection menu and reboot to fastboot.
connect the phone to your PC and using the a7toolkit flash the recovery again.
I think I did exactly the same thing as you and I fixed it this way
daaper said:
I unlocked the bootloader, installed the Universal O bootloader, and was in the process of updating my version of TWRP.
Click to expand...
Click to collapse
I assume you are coming from stock because you're unlocking your bootloader. I have a question about this process, did you install an older twrp first before flashing the O bootloader?
Chris axon 7 said:
You can try flashing twrp via the twrp app
Click to expand...
Click to collapse
I'm not sure how to do this if my phone won't boot.
rzarectha said:
Hey!
Try to reboot the phone, press volume button to get the selection menu and reboot to fastboot.
connect the phone to your PC and using the a7toolkit flash the recovery again.
I think I did exactly the same thing as you and I fixed it this way
Click to expand...
Click to collapse
When I connect my phone to my computer, none of the toolkits I've tried can see it. It comes up as "Handset Diagnostic Interface (DFU) (Com4)". When I attempt to enter EDL mode with volume +, volume -, and power I don't get a flashing LED, just a solid one. As near as I can tell, this means my phone is hardbricked. I've got an EDL cable on order to hopefully fix this, but it's going to take almost a month to get here :crying:
tprfd said:
I assume you are coming from stock because you're unlocking your bootloader. I have a question about this process, did you install an older twrp first before flashing the O bootloader?
Click to expand...
Click to collapse
Yes, the toolkit I used (Axon7RootToolV4) first unlocked the bootloader and then had a step to flash TWRP. When I was attempting to update TWRP, per the LOS instructions, it wasn't updating like it has in the past on other phones. I now know that restarting was the worst thing to do at that point. If the version of TWRP doesn't also match the bootstack and ROM, you're going to have a bad day if you restart.

Fastboot mode doesnt work

Hello,
My issue is really weird. I was using No Limits rom with oos 4.5.1
Later, i've reverted back to stock rom and my actual version is Pie with OOS 9.0.7 . Also my recovery is stock at the moment.
The issue is, i can not enter to fastboot mode. İ am selecting that and pressing power button to start fb mode but my device reboots back to desktop without entering to mode. Device is up and running, no stuck at bootloop or etc.
Now i can not load any recovery, root etc. Tried all combinations to enter but doesnt work at all.
İs there any solution to solve this ?
Kaanb93 said:
Hello,
My issue is really weird. I was using No Limits rom with oos 4.5.1
Later, i've reverted back to stock rom and my actual version is Pie with OOS 9.0.7 . Also my recovery is stock at the moment.
The issue is, i can not enter to fastboot mode. İ am selecting that and pressing power button to start fb mode but my device reboots back to desktop without entering to mode. Device is up and running, no stuck at bootloop or etc.
Now i can not load any recovery, root etc. Tried all combinations to enter but doesnt work at all.
İs there any solution to solve this ?
Click to expand...
Click to collapse
Instead of trying to enter fastboot mode from android did you tried to enter bootloader by holding power + volume up while powering the device on.
Also if you have enabled USB debugging you should be able to enter fastboot mode by connecting to a pc and using platform tools: adb reboot bootloader
strongst said:
Instead of trying to enter fastboot mode from android did you tried to enter bootloader by holding power + volume up while powering the device on.
Also if you have enabled USB debugging you should be able to enter fastboot mode by connecting to a pc and using platform tools: adb reboot bootloader
Click to expand...
Click to collapse
Hello, tried that ways too, and it reboots to the desktop anyway. On pc, when i wrote that command, it reboots again.
İ guess something happened to the bootloader firmware if it exists..
Kaanb93 said:
Hello, tried that ways too, and it reboots to the desktop anyway. On pc, when i wrote that command, it reboots again.
İ guess something happened to the bootloader firmware if it exists..
Click to expand...
Click to collapse
Then I recommend to flashing everything from scratch with https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706

Bootloop after Viper4Android

So I just rooted and got everything to work just fine (.33). Thought i'd smash in Viper4Android aswell.
The phone is now stuck on the logo with the red and two white dots.
I can get it to reboot with Vol+ and power, but the power-button does not let me go into recovery mode at all. It's like its disconnected.
Is there anything you can do to get into recovery/fastboot from here?
Also tried every single vol+powercombination with 0 results..
Thanks in advance.
What viper4android version did you install? And what Android version are you on?
If using Magisk 21> you should be able to hold down power button to boot into safe mode.
Hold power button and volume down and up at the same time, this should boot you into bootloader.
If you're on Android 10:
Boot into TWRP and remove module folder from data/adb/modules
Android 11 (or 10)
[Recovery][Stock OOS]Oxygen OS Stock recovery with ADB enabled
While waiting for a working TWRP for all those needful of the possibility to access their file system from recovery, e.g. for removing an offensive magisk extension preventing boot I repackaged the Stock OOS recovery but with ADB enabled...
forum.xda-developers.com
Lossyx said:
What viper4android version did you install? And what Android version are you on?
If using Magisk 21> you should be able to hold down power button to boot into safe mode.
Hold power button and volume down and up at the same time, this should boot you into bootloader.
Click to expand...
Click to collapse
Thanks for the reply.
I seem to have solved it (for now..).
I could not get any key to answer to my commands when i rebooted the phone (hence why i couldnt get into recovery etc.), it only went back to the loop after displaying the usual message about the bootloader being unlocked.
Holding down both volume-buttons and using the msm-tool i managed to get it back to OEM (with everything locked. Again. Lmao) so now i just gotta watch out when I install Viper again (if i do..).
Running Oxygen 11.0.3.3.IN11BA with the latest Magisk (I just patched it today)
Edit: I just used the Viper4Android that i found inside Magisk if that makes any sense.
I'll try your links and see if i have to re-flash again..
Cheers

Categories

Resources