20421 results in Bootloops/Qualcomm CrashDump Mode

[androidacy-user]

I can run 20420 fine, no problem.

20421 results in always rebooting to Qualcomm CrashDump Mode when trying to boot system, every time. Reverting to 20420 resolved this.

OnePlus 7 pro, OxygenOS Open Beta 17 (Android 10).

No logcat, pstore, anything because it never gets far enough in the boot process.

[palmbeach05]

I have a similar experience with my g7 power, it bootloops, and i am unable to pull any logs. Revert back to 20420 and everything is fine

[xerta555]

Same issue for me too, where can i found the 20420 zip installer ?

[palmbeach05]

Same issue for me too, where can i found the 20420 zip installer ?

https://github.com/topjohnwu/magisk_files/blob/51e925d88c07d9fab2017d57c723e28c18a0d996/magisk-debug.zip

[xerta555]

topjohnwu/magisk_files@51e925d/magisk-debug.zip

Effectivly it works for me too, so back on 20420. So just wait that John fix it.

[Terminator-J]

\

I can run 20420 fine, no problem.

20421 results in always rebooting to Qualcomm CrashDump Mode when trying to boot system, every time. Reverting to 20420 resolved this.

OnePlus 7 pro, OxygenOS Open Beta 17 (Android 10).

No logcat, pstore, anything because it never gets far enough in the boot process.

Same here, OnePlus 6 (crDroid 6.9 for enchilada over OOS 10.3.5)

[DeltaOn3X]

Same problem on my Note 10+, Android 10. It just bootloops until it starts without root.

Is there a way how i can flash 20420 again without twrp ? with the stock recovery i get a signature verification failed error.

[palmbeach05]

Same problem on my Note 10+, Android 10. It just bootloops until it starts without root.

Is there a way how i can flash 20420 again without twrp ? with the stock recovery i get a signature verification failed error.

Stock recovery = useless for what you want to do

[xerta555]

Is there a way how i can flash 20420 again without twrp ? with the stock recovery i get a signature verification failed error.

Stock recovery is useless for this type of action. Install again twrp and flash the zip directly.

[KaMyKaSii]

My Zenfone 4 (Android 9) is stuck on the ASUS logo, I don't know if it's the same problem. The device does not generate /proc/last_kmsg or /sys/fs/pstore/console-ramoops, I will attach the backup of the asdf partition which may have some relevant log asdf.ext4.win.tar.gz

[Nemisor]

On Pixel 2XL with DP3, easiest recovery is to simply re-flash it using the android flash tool. Should probably work with any other pixel too.

[KaMyKaSii]

Same problem on my Note 10+, Android 10. It just bootloops until it starts without root.

Is there a way how i can flash 20420 again without twrp ? with the stock recovery i get a signature verification failed error.

1. Go to fastboot, flash stock boot.img/ramdisk.img and reboot to Android
2. Open Magisk Manager settings and set the below custom channel, it's just a edit pointing to 20420 files https://github.com/KaMyKaSii/Unlock-SSH-on-Xiaomi-and-Redmi-WiFi-6-routers/raw/master/debug.json
3. Patch your stock boot.img/ramdisk.img and flash it using fastboot again

[DeltaOn3X]

Same problem on my Note 10+, Android 10. It just bootloops until it starts without root. Is there a way how i can flash 20420 again without twrp ? with the stock recovery i get a signature verification failed error.

1. Go to fastboot, flash stock boot.img/ramdisk.img and reboot to Android
2. Open Magisk Manager settings and set the below custom channel, it's just a edit pointing to 20420 files https://filebin.net/kqnvfqmpe955x366/debug.json?t=dcwdrfj2
3. Patch your stock boot.img/ramdisk.img and flash it using fastboot again

Thank you, ill try this out EDIT: Ok this is not an option as my device is not A/B :/

[People-11]

same, on my Pixel 2, backing into 20420

[KaMyKaSii]

Same problem on my Note 10+, Android 10. It just bootloops until it starts without root. Is there a way how i can flash 20420 again without twrp ? with the stock recovery i get a signature verification failed error.

1. Go to fastboot, flash stock boot.img/ramdisk.img and reboot to Android
2. Open Magisk Manager settings and set the below custom channel, it's just a edit pointing to 20420 files https://filebin.net/kqnvfqmpe955x366/debug.json?t=dcwdrfj2
3. Patch your stock boot.img/ramdisk.img and flash it using fastboot again

Thank you, ill try this out EDIT: Ok this is not an option as my device is not A/B :/

Mine isn't either. What's the problem? You just need to restore and then patch the same partition you did when you installed Magisk. By the way, I updated the custom channel link

[blackbox87]

After updating to 20421 my Pocophone F1 running LineageOS 16 kept booting to fastboot. I fixed it by booting to TWRP and reverting to 20420.

[DeltaOn3X]

Same problem on my Note 10+, Android 10. It just bootloops until it starts without root. Is there a way how i can flash 20420 again without twrp ? with the stock recovery i get a signature verification failed error.

1. Go to fastboot, flash stock boot.img/ramdisk.img and reboot to Android
2. Open Magisk Manager settings and set the below custom channel, it's just a edit pointing to 20420 files https://filebin.net/kqnvfqmpe955x366/debug.json?t=dcwdrfj2
3. Patch your stock boot.img/ramdisk.img and flash it using fastboot again

Thank you, ill try this out EDIT: Ok this is not an option as my device is not A/B :/

Mine isn't either. What's the problem? You just need to restore and then patch the same partition you did when you installed Magisk. By the way, I updated the custom channel link

For System as root devices you cant restore on of the 3 patched partitions. Rooting my Note 10+ is not only patching the boot.img but the whole Firmware (AP one)

[mu198]

@DeltaOn3X, Have you tried to extract the boot from the AP and then repackage it as .tar

[DeltaOn3X]

@DeltaOn3X, Have you tried to extract the boot from the AP and then repackage it as .tar

I made a backup Extracted boot, recovery and vbmeta, packed it in a tar file. Patched the tar file with magisk 20420 (thank you for the custom link!) Rebooted to download mode and flashed the patched tar with Odin (obviously ap tab) (auto-reboot on) Now its workin again. Sideloading the patched imgs seperatly with abd gives me the same error again with "verification failed"

[mu198]

@DeltaOn3X, Have you tried to extract the boot from the AP and then repackage it as .tar

I made a backup Extracted boot, recovery and vbmeta, packed it in a tar file. Patched the tar file with magisk 20420 (thank you for the custom link!) Rebooted to download mode and flashed the patched tar with Odin (obviously ap tab) (auto-reboot on) Now its workin again. Sideloading the patched imgs seperatly with abd gives me the same error again with "verification failed"

What do you flash about adb sideload ??? And why?

[DeltaOn3X]

@DeltaOn3X, Have you tried to extract the boot from the AP and then repackage it as .tar

I made a backup Extracted boot, recovery and vbmeta, packed it in a tar file. Patched the tar file with magisk 20420 (thank you for the custom link!) Rebooted to download mode and flashed the patched tar with Odin (obviously ap tab) (auto-reboot on) Now its workin again. Sideloading the patched imgs seperatly with abd gives me the same error again with "verification failed"

What do you flash about adb sideload ??? And why?

Look at @katmykasii reply

[mu198]

Yes, there is nothing about the adb sideload, as the Odin mode replaces the fastboot mode at Samsung

[jx-it]

For me neither magisk uninstaller.zip nor flashing 20420 worked. I'm still stuck in bootloop on Mi 9 SE. Any ideas?

[androidacy-user]

For me neither magisk uninstaller.zip nor flashing 20420 worked. I'm still stuck in bootloop on Mi 9 SE. Any ideas?

Weird, flashing 20420 immediately solved for me. Maybe dirty flash your ROM?

[jx-it]

Weird, flashing 20420 immediately solved for me. Maybe dirty flash your ROM?

I also tried this, but it's still stuck.

[zgfg]

Same on Xiaomi Mi 9T, MIUI 12, Android 10

Tried patching boot.img with Magisk 20421 from Manager 296 and 297, same bootloop. patching-Magisk-20421.log bootloop-patched-Magisk-20421.log magisk_patched-20421.zip

For comparison, working boot image patched by previous Magisk 20420: magisk_patched_working-20420.zip

[nabakolu]

Also had bootloop on Xperia XA2. Using the Magisk installer zip i luckily still had on my sd card worked to resolve the problem. (even for a second time to check if it really was a Magisk problem)

[EvoXCX]

Same Oneplus 6 LineageOS 17.1

[topjohnwu]

61599059d5dd76d3994a33edaf8e2e77c5455bac

[androidacy-user]

6159905

All this trouble over a simple mixup lol

beenthere