Question Dm-verity device corrupted

[AutruiP]

Hi,

I've tried to flash a new magisk-boot img, following this guide, after downloading the signed flashable zip LE2113_11_F.75.

I've patched the boot.img with my magisk app, and after flashing it,my OnePlus 9 doesn't boot anymore.

I've got this error : QUALCOMM CrashDump Mode. dm-verity device corrupted. verity-ctr

I can't boot to TWRP, I tried a fastboot boot and a fastboot flash recovery, but I always get a Qualcomm dump error.

Can someone help me to fix this issue ?

Thanks !

 

[Creepergames360]

this refrence might help-

Help needed! Qualcomm Crash dump after trying to reinstall magisk upon upgrade to Android 11

Hi, Lost root access after updating my OnePlus 6T to Android 11 a few days back, hence decided to flash magisk_patched image that I had created around 2 months back. Phone didn't like it ofcourse and gave me a QualComm Crash Dump error. After...

forum.xda-developers.com

"The update to [Insert Version Here] does not agree with Magisk which causes it to either fail to complete the update or to die at early boot depending on how bad things were messed up. You can reapply root once the update to [Insert Version Here] is finished though, so you can still have root.

In your case manually upgrading to [Insert Version Here], letting it finish the upgrade, and then installing Magisk again is your best bet, in which case you would either have to find something that understands the update format or manually extract the updated partitions from the payload, iirc"

 

[AutruiP]

Hi, thanks for your answer.

I've managed to gain access back to my phone, using the payload.bin from the signed flashable zip, and the fastboot enhance tool.

I've had to flash it on the a slot, as I have errors when trying to flash it on the b slot.

I've managed to boot on TWRP using this one for the encryption support.

I still got the dm-verify error when booting on the b slot, can't flash the payload.bin on it, can't backup it... I'm not sure if it's normal neither how to fix it, as even trying to fastboot flash boot crashes.

I've tried to flash the signed flashable zip in TWRP, and got this :

Flashing A/B zip to inactive slot : B
Step 1/2
Error applying update: 23 (ErrorCode:: kDownloadManifestParseError)
Updater process ended with ERROR: 1

 

[TheNewHEROBRINE]

Hi, thanks for your answer.

I've managed to gain access back to my phone, using the payload.bin from the signed flashable zip, and the fastboot enhance tool.

I've had to flash it on the a slot, as I have errors when trying to flash it on the b slot.

I've managed to boot on TWRP using this one for the encryption support.

I still got the dm-verify error when booting on the b slot, can't flash the payload.bin on it, can't backup it... I'm not sure if it's normal neither how to fix it, as even trying to fastboot flash boot crashes.

I've tried to flash the signed flashable zip in TWRP, and got this :

It's not a problem if one slot is broken, it will probably fix itself on the next update.

 

[AutruiP]

Hi, thanks for your answer.

The fact that you talked about the next update made me try to locally install the update with the signed flashable zip, using the system updater. It worked and fixed everything !

Thanks