Today I flashed the newest OOS 10.0.3. After I had flashed it+TWRP through Magisk and rebooted, Vanced Youtube was not able to be installed correctly. I have fixed this earlier by uninstalling the Youtube app through a root-uninstaller app. Then flash Vanced in Magisk, and reboot.
After doing this, my phone would only bootloop into TWRP/Fastboot. So I tried to boot into TWRP, flash OOS 10.0.3, TWRP then Magisk, in TWRP, but no success. The phone would just bootloop. So I tried my final attempt without having to wipe the whole phone - Flash an old backup (I think it was from October, probably OOS 10.0.1). After doing a full recovery in TWRP with the old backup, my phone boots into Qualcomm CrashDump Mode with a message displaying
dm-verity device corrupted Force Dump
Kernel_restart
Click to expand...
Click to collapse
By holding power+volume up for 10 seconds, my phone reboots displaying the warning message about my phone's bootloader being unlocked, then shows the quoted message above.
Could anyone please help me fix this?
---
Update:
So after trying to reboot for 15+ times, my phone somehow booted into TWRP. What would be the best step now?
Wipe all, flash OOS 10.0.3, Flash TWRP and Flash Magisk?
Which specific model do you have, region? Which twrp was used?
Werchio said:
Today I flashed the newest OOS 10.0.3. After I had flashed it+TWRP through Magisk and rebooted, Vanced Youtube was not able to be installed correctly. I have fixed this earlier by uninstalling the Youtube app through a root-uninstaller app. Then flash Vanced in Magisk, and reboot.
After doing this, my phone would only bootloop into TWRP/Fastboot. So I tried to boot into TWRP, flash OOS 10.0.3, TWRP then Magisk, in TWRP, but no success. The phone would just bootloop. So I tried my final attempt without having to wipe the whole phone - Flash an old backup (I think it was from October, probably OOS 10.0.1). After doing a full recovery in TWRP with the old backup, my phone boots into Qualcomm CrashDump Mode with a message displaying
By holding power+volume up for 10 seconds, my phone reboots displaying the warning message about my phone's bootloader being unlocked, then shows the quoted message above.
Could anyone please help me fix this?
---
Update:
So after trying to reboot for 15+ times, my phone somehow booted into TWRP. What would be the best step now?
Wipe all, flash OOS 10.0.3, Flash TWRP and Flash Magisk?
Click to expand...
Click to collapse
TWRP?! There are no working twrps for 7T series.
gpz1100 said:
Which specific model do you have, region? Which twrp was used?
Click to expand...
Click to collapse
Oneplus 7, EU region (guacamoleb). TWRP that I have managed to boot into is 3.3.1-70.
Aswin08 said:
TWRP?! There are no working twrps for 7T series.
Click to expand...
Click to collapse
My bad. It is a Oneplus 7 Guacamoleb, TWRP version is 3.3.1-70
Oneplus 7T Qualcomm CrashDump Mode
Hi Everyone,
My OnePlus 7T got stuck in QUALCOMM CRASHDUMP MODE.
First, i wanted to know the reason why this crash is happening as i can see many users reporting the same in many forums.
Note : It is my brand new phone purchased 2 days back.
Thanks !!
Restor your firmware with the msmtool
Here are the drivers that are installed on my PC ( I enabled hidden devices, in order to see them ) These were recognizing prior to " qualcomm crash dump" .
Now ADB,Fastbootd and Windows 10 / Mac OSx do not see my device, let alone recognize
It's possible that your phone is corrupted. Double freezer bag phone, express all excess air out from bag, zip both bags tightly, stick phone in freezer for 1 hr to deplete battery, then try buttons and msmtool
Related
I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Did you buy the phone second hand or did you try to flash TWRP yourself? It shouldn't have TWRP installed by default.
Regardless, you can use TWRP to flash the latest update.
Given that you have TWRP, I'm assuming that you have an unlocked bootloader. Did you notice a warning pop up everytime you reboot your phone before? It should say something along the lines of "your device has been unlocked and can't be trusted". If not, you'll have to unlock it (it wipes your phone in the process).
If the bootloader is unlocked, you can simply download and flash the latest zip for OOS 4.0.3 in TWRP. This will update you phone and replace TWRP with the stock recovery (so you don't run into this problem again in the future when installing an OTA). If you don't intend to modify your phone in any way, then this is all you need to do, your phone should be functional.
There are plenty of threads with detailed guides on how to do all of this.
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
sndr1384 said:
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
Click to expand...
Click to collapse
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
This is issue of using a faulty twrp so for that when ur phone us booting up go to fastboot and flash twrp 3.0.4-1 and everything will work
emuandco said:
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
Click to expand...
Click to collapse
Similar Problem here:
just wanted to flash latest OOS 4.0.3, so I flashed back stock recovery with flashify and rebooted into recovery mode to flash the already downloaded OOS 4.0.3. zip. That's when it began to go poop! After rebooting it just went dark with no Chance to power it on again! No dice with power button, Volume up/down + power button, nothing! Not even the LED's are blinking when plugged in. So this one seems to be basically dead!
I got it once booting again after randomly pushing the buttons (after x minutes!?), but everytime I reboot the phone it just shuts off without beeing able to power it on again. At the Moment it's dead!
Any ideas what might happened? If I get it on again, should I immediately reset it to factory Settings?
I am kinda lost here! Any help/ideas would be much appreciated!
Flashify? Never used it and never trusted apps which flash stuff on a running system. Use fastboot and reflash the recovery partition. Link to recovery is in my former post.
fastboot flash recovery PATHTOIMGFILE
Thank you for your advice! Still a lot to learn! Got it up again, will try as you suggested!
It appeared that my stock recovery file was corrupted , but all is fine again! Thank you very much!
Mannycolon85 said:
I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Click to expand...
Click to collapse
I may have been the person you traded with to get the OnePlus 3, but I took the phone back and after 5 hours I got it up and running.
The phone would boot to TWRP, but even after wiping the entire system and dragging a ROM zip to the internal storage, reinstalling did nothing. It just kept booting back to recovery.
The solution entailed the following.
Download stock recovery IMG. Flashed through TWRP. Rebooted recovery and now was back to stock recovery.
Download the official OxygenOS ROM zip from the OnePlus website and changed the name to update.zip
Next I downloaded Android studio for access to ADB. I had never used ADB before, but I knew this was needed to push a file to the phone.
Needless to say, ADB kept freezing my computer when I would type in the commands to side load.
I deleted Android studio and installed a minimal ADB/Fastboot I found online. I opened my command prompt, typed the command for sideloading, and immediately got my installation starting. It took about 10 minutes to fully install. When it was finished, I rebooted and had a fully functioning OnePlus 3
Sent from my ONEPLUS A3000 using Tapatalk
Few months ago I flashed some stuff on my phone which I shouldn't have, I guess. In the meantime I got a new one but now I'm trying to recover my OP3. I tried all sorts of MSM tools, (from Marshmallow to latest Pie that OP support provided me with) and in best case I could get it to bootloop and then throw me a dm verity warning screen after that (screenshot below) After that it only can throw me in a generic chinese OP recovery which fails to do anything. MSM runs fine, loads up as HS 9008 Qualcomm device and gets it's job done in 5-6 mins. I can't do anything in fastboot since bootloader is locked after MSM. Is there any help because it seems to not be completely dead?
Thanks
Screen after bootloop:
https://imgur.com/a/R1lJTjX
AnnoyingZlatan said:
Few months ago I flashed some stuff on my phone which I shouldn't have, I guess. In the meantime I got a new one but now I'm trying to recover my OP3. I tried all sorts of MSM tools, (from Marshmallow to latest Pie that OP support provided me with) and in best case I could get it to bootloop and then throw me a dm verity warning screen after that (screenshot below) After that it only can throw me in a generic chinese OP recovery which fails to do anything. MSM runs fine, loads up as HS 9008 Qualcomm device and gets it's job done in 5-6 mins. I can't do anything in fastboot since bootloader is locked after MSM. Is there any help because it seems to not be completely dead?
Thanks
Screen after bootloop:
https://imgur.com/a/R1lJTjX
Click to expand...
Click to collapse
If you can get to bootloader, download and flash OOS 5.0.6. If not, try one of the MSM Tools on XDA. There are quite a few of them, search. Please also note that the Tool is different for 3 and 3T.
I had used one of the oldest Tools here on XDA a couple of times without any hiccups.
Did you get a solution to this? I am struggling with the same issue.
Another OP3 user here with the same problem as you guys.
I tried all of the MSM tools posted here, with no success and varying responses from the phone.
One of them does let me actually boot to recovery, but it's the generic one that only has install from adb (and sideloading always fails at 47% - haven't found a solution around that yet either). From inside recovery, attempting to wipe cache or wipe system gets about 3/4 of the way then the device reboots on its own.
I was also on occasion able to boot to the decrypt password entry screen, but no password is valid and attempting to issue a reset from there (from Forgot password) doesn't seem to do anything.
No issues getting to fastboot or qs9008 serial mode, but bootloader is locked also so kind of stuck.
In my case, phone was working fine, but the OTA update caused a brick so I've been trying to recover it since then.
Maybe somebody else has an idea here..
myserver57 said:
Another OP3 user here with the same problem as you guys.
I tried all of the MSM tools posted here, with no success and varying responses from the phone.
One of them does let me actually boot to recovery, but it's the generic one that only has install from adb (and sideloading always fails at 47% - haven't found a solution around that yet either). From inside recovery, attempting to wipe cache or wipe system gets about 3/4 of the way then the device reboots on its own.
I was also on occasion able to boot to the decrypt password entry screen, but no password is valid and attempting to issue a reset from there (from Forgot password) doesn't seem to do anything.
No issues getting to fastboot or qs9008 serial mode, but bootloader is locked also so kind of stuck.
In my case, phone was working fine, but the OTA update caused a brick so I've been trying to recover it since then.
Maybe somebody else has an idea here..
Click to expand...
Click to collapse
Did you try to sideload OOS using adb? Try the various versions of OOS.
TNSMANI said:
Did you try to sideload OOS using adb? Try the various versions of OOS.
Click to expand...
Click to collapse
Thanks, yes I did. Stalls at 47%.
Also tried every version of OOS that I could find (5.04, 5.05, 5.06, etc from https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722)
Also tried the versions from https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
(this one is the one that sometimes lets me get to recovery, the others don't).
myserver57 said:
Thanks, yes I did. Stalls at 47%.
Also tried every version of OOS that I could find (5.04, 5.05, 5.06, etc from https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722)
Also tried the versions from https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
(this one is the one that sometimes lets me get to recovery, the others don't).
Click to expand...
Click to collapse
If you are able to use fastboot, try flashing TWRP or atleast boot TWRP and then from TWRP flash OOS or one of the custom ROMs.
If this also fails, I am at a loss for ideas. May be you have a hardware fault.
TNSMANI said:
If you are able to use fastboot, try flashing TWRP or atleast boot TWRP and then from TWRP flash OOS or one of the custom ROMs.
If this also fails, I am at a loss for ideas. May be you have a hardware fault.
Click to expand...
Click to collapse
Thanks again for trying to help.
Sadly, bootloader is locked so flashing TWRP or even booting to TWRP is a no-go.
I don't think it's a hardware fault since it was working fine before the OTA update, but I guess you never know. Damn, if only sideloading would work, darn thing...
I have a weird situation going on with my phone
My phone is Chinese Pack and I had Xiaomi Eu MIUI 12 previously
I tried flashing MIUI 11 Stable China rom on it using TWRP
when I installed the rom, TWRP didn't get deleted and my phone started to bootloop, so I flashed magisk and the bootloop was gone and I could boot my device after flashing magisk.
Now I want to sell my phone and I'm trying to flash everything back to normal, get rid off TWRP and Magisk and lock the bootloader as well using MiFlash
the phone is running on V11.0.5.0.PCACNXM and I'm trying to flash the same rom using MiFlash and lock bootloader, but at first, it says device mismatch
and when I delete the first 2 lines of flash_all_lock.bat which causes this problem, something else happen
check the attached image
when I press the flash button, this screen comes up and nothing changes except the timer that goes up, and when I remove the phone cable, the phone boots normally without any problem, practically, MiFlash doesn't change a thing
any solution that can help me unlock Bootloader, remove Twrp and Magisk?
Already tried different versions of MiFlash and an app called XiaomiADBFastbootTools.jar, nothing again
P.S: while flashing with XiaomiADBFastbootTools.jar, I get the same message but after removing the cable, the error changes to "current device anti-rollback version is greater than this package", which is nonsense because I have the same ROM on phone already.
I got the notification for the 11.F.17 update on my rooted and unlocked OP9 Pro.
I uninstalled Magisk and restored the images so i could do the OTA update since it failed if i didn't.
When it was done I reinstalled Magisk to the 2nd slot and hit reboot.
Now I am greeted with the Qualcom Crashdump Mode and the dm-verity device corrupted verity_ctr error.
I am getting ready to use the MSM tool AGAIN!
Is there any way of getting to my personal data before i wipe everything?
I am able to get into fastboot mode and my pc (linux) does show the phone but i can't seem to get ADB to find it.
Edit: Well somehow I got it to boot normally. I plugged it into the warp charger and held up + power and now it works.
Edi t#2: It booted back into the old android and not the update i installed. Well at least i can get my files now.
How should I go about updating to 11.F.17?
pdrift said:
I got the notification for the 11.F.17 update on my rooted and unlocked OP9 Pro.
I uninstalled Magisk and restored the images so i could do the OTA update since it failed if i didn't.
When it was done I reinstalled Magisk to the 2nd slot and hit reboot.
Now I am greeted with the Qualcom Crashdump Mode and the dm-verity device corrupted verity_ctr error.
I am getting ready to use the MSM tool AGAIN!
Is there any way of getting to my personal data before i wipe everything?
I am able to get into fastboot mode and my pc (linux) does show the phone but i can't seem to get ADB to find it.
Click to expand...
Click to collapse
You might try flashing a stock boot image of f.17 into both boot_a and boot_b
Or f.16 if you have reason to believe the update didn't take
Or trying to boot to your other slot
Appreciative said:
You might try flashing a stock boot image of f.17 into both boot_a and boot_b
Or f.16 if you have reason to believe the update didn't take
Or trying to boot to your other slot
Click to expand...
Click to collapse
I got it to boot normally by plugging into the warp charger and holding up + power.
I just realised that it booted back into the old version of android not the update.
Try downloading the file with the oxygen updater apk on google play store. Then installing per instruction on apk.
2125 AA model OPO9
So my phone has been nagging me to upgrade to A13 for awhile now and I decided to finally bite the bullet and do it, so I backed up everything before I did it.
Now previously, to keep Magisk, I was following the guide to restore the image, do the upgrade, then flash magisk in the inactive slot. But from reading it sounded like after I upgraded to A13, I needed to go into fastboot and boot off the magisk'ed boot image. So I restored the image in magisk and then upgraded to A17 and rebooted, then to A18 (as I had the A18 boot images) and rebooted. Everything came up fine. However, as soon as I boot into the bootloader, I see if for a split second and then it immediately crashes into the Qualcomm crash dump screen. I can still reboot into the OS but I'd really like to have Magisk back if possible.
Edit (More info): When I reboot, I do get a new notice on the pre-boot screen that the device is unlocked that I didn't see before when I was on A12. In addition, in the OS, the OEM unlock is greyed out (with bootloader unlocked) and will not let me lock it again.
My current state is a working phone on A17/F18 with no root but would like to get root back (and a working bootloader for peace of mind).
So I guess my questions are:
1) Is there still a way I can get Magisk in my current state. Without the bootloader I'm assuming I'm SOL...
2) Would a factory reset from within the OS fix the bootloader?
2) If I need to use the MSM tool, where can I find the qualcomm drivers? I found one link but it was a CAB file and I could not get anything working out of that.
jbradshw said:
2125 AA model OPO9
So my phone has been nagging me to upgrade to A13 for awhile now and I decided to finally bite the bullet and do it, so I backed up everything before I did it.
Now previously, to keep Magisk, I was following the guide to restore the image, do the upgrade, then flash magisk in the inactive slot. But from reading it sounded like after I upgraded to A13, I needed to go into fastboot and boot off the magisk'ed boot image. So I restored the image in magisk and then upgraded to A17 and rebooted, then to A18 (as I had the A18 boot images) and rebooted. Everything came up fine. However, as soon as I boot into the bootloader, I see if for a split second and then it immediately crashes into the Qualcomm crash dump screen. I can still reboot into the OS but I'd really like to have Magisk back if possible.
Edit (More info): When I reboot, I do get a new notice on the pre-boot screen that the device is unlocked that I didn't see before when I was on A12. In addition, in the OS, the OEM unlock is greyed out (with bootloader unlocked) and will not let me lock it again.
My current state is a working phone on A17/F18 with no root but would like to get root back (and a working bootloader for peace of mind).
So I guess my questions are:
1) Is there still a way I can get Magisk in my current state. Without the bootloader I'm assuming I'm SOL...
2) Would a factory reset from within the OS fix the bootloader?
2) If I need to use the MSM tool, where can I find the qualcomm drivers? I found one link but it was a CAB file and I could not get anything working out of that.
Click to expand...
Click to collapse
Google for latest Qualcomm 9008 USB drivers
TheGhost1951 said:
Google for latest Qualcomm 9008 USB drivers
Click to expand...
Click to collapse
Is MSM my only option here then?
jbradshw said:
Is MSM my only option here then?
Click to expand...
Click to collapse
If you want a fresh start and try all over again with less hassle!