Can't boot to system with Magisk v21 installed

[s3tupw1zard]

Hello,
I tried Magisk v21 with Atom OS v2.8 Android 11 ROM, but it reboots to Fastboot mode. Please fix this.

If you need any logs or kind of, please tell me where to get them.

regards

[s3tupw1zard]

P.S. my device is Redmi Note 8 ginkgo

[Ad1tyaS1ngh]

@topjohnwu I have a Realme 2 Pro. Same thing happens when flash Magisk v21 on my device. I can only use Magisk v21 on my device by first flashing a modded Magisk Canary File and then flashing v21 on top of it. It might have something to do with patching the boot image.

[Pipodi]

I can confirm the same issue too. Flashing RevengeOS (Oneplus 7 Pro) with a patched Magisk version works, when I flash v21 it goes into fastboot mode.

I tried what @Ad1tyaS1ngh said, but no luck.

[Ad1tyaS1ngh]

@Pipodi maybe this method only works for some devices. But it worked fine for one of my friends who has a OnePlus 7 pro.

[s3tupw1zard]

So you mean patching the Boot Image with magisk Manager Not glashing the magisk ZIP File?

[Ad1tyaS1ngh]

@s3tupw1zard I meant that in our device group someone sent a modded zip file for Magisk which worked and booted fine. It was just an assumption that v21 didn't patch the boot image correctly.

[s3tupw1zard]

Ah okay

[Pipodi]

@Ad1tyaS1ngh I first did this:

• Flashed the patched version
• Opened Magisk Manager
• Updated to v21 from there (direct installation)
• Reboot

It got me in fastboot mode. After that I've uninstalled Magisk from TWRP with the uninstaller and I tried your method, flashing the patched version first, and then the v21 immediately after. Still in fastboot mode.

[s3tupw1zard]

The Problem is the Official Magisk Version. only use the patched magisk version.

[s3tupw1zard]

on my side it booted with patched. But i got a notification that dtbo image was patched. After this when booting, it shows redmi logo and then my phone is turning off. i think dtbo patching is the problem

[s3tupw1zard]

Requesting root isnt working too

[s3tupw1zard]

here are my logs:
https://pastebin.com/c8Ps9b0y

[Ad1tyaS1ngh]

@Pipodi Follow these steps:

1. Flash Modded Magisk
2. Uninstall the modded Magisk manager (don't uninstall magisk, uninstall only the apk file)
3. Flash v21 from recovery.
   Done

[Pipodi]

@Ad1tyaS1ngh Nope, doesn't work for me. Maybe we are running two different versions of patched Magisk? Mine is Magisk 6159905(20422).

[Ad1tyaS1ngh]

@Pipodi let me ask my friend how he managed to install v21. I will get back to you as soon as he replies.

[Ad1tyaS1ngh]

@Pipodi He flashed the canary build, booted, rebooted into recovery, flashed v21 booted.

[Pipodi]

@Ad1tyaS1ngh I tried everything, even flashing the latest canary, but no luck. I'll wait for a more accurate and maybe official solution! Thanks anyway! :)

[Ad1tyaS1ngh]

@Pipodi no problem man. We all are here for the official solution 😄

[topjohnwu]

@Ad1tyaS1ngh @Pipodi where do you get the modified Magisk? And please tell the source to contribute back as Magisk is GPL licensed

[Pipodi]

@topjohnwu I've found it in the Telegram Group of the RevengeOS for OnePlus 7 Pro. There's a topic on XDA too, but I think the modified version provided there is outdated compared to the one on the Telegram group.

[Ad1tyaS1ngh]

@topjohnwu I found it in redmi note 7 group on telegram. The modded Magisk version doesn't work but the only way we can flash v21 is by first flashing it otherwise it gets into fastboot mode. In order to not use the modded one, I have switched back to Android 10 and using v20.4.

[Ad1tyaS1ngh]

@Pipodi Sorry man I just confirmed that v21 never worked with OnePlus 7 pro.

[KurashikiAzusa]

@topjohnwu The MagiskCU seems to be from an old version of Magisk Canary, version 20422. I cannot verify it because the magisk_files canary branch's older commits was wiped. I did however, source the 20422 files from various sources from googling.

MagiskCU.zip , Magisk-(61599059)-(20422).zip
SHA-1: EA218657D2F2C50FFEA99DF6E464183DA21D458F

[guchito9]

Hi, it's fixed for me in the latest canary

[topjohnwu]

Please try again on the latest canary build. If the issue persists, please open a new issue, following the new instructions in the issue template.

[Snaxeko]

@topjohnwu I have a Realme 2 Pro. Same thing happens when flash Magisk v21 on my device. I can only use Magisk v21 on my device by first flashing a modded Magisk Canary File and then flashing v21 on top of it. It might have something to do with patching the boot image.

Did you disable AVB2.0 to make Magisk works on your Realme ? Personally I experience a boot issue like here

Edit: found how to fix it