Do you mean you went into a bootloop when you updated Magisk to 24304 or when you tried to install this kernel after updating Magisk?
Crazy this worked for me too lol but question does this mean we can flash custom kernel with latest canary magisk or should we use stable magisk for now to root/flash a custom kernel with a12L/a13? Thanks iVery happy it worked! Tried everything to get rid of the corrupt message (excluding resetting my phone - that was NOT something I was willing to do). FIgured there must be something that tells Android that it has been updated (and therefore to get rid of the corrupt message) and decided to simply try seeing if the boot.img file was the trigger for it. Very happy I was right!
I think the corruption issue is more related to vbmeta/verity. I have verity and verification disabled and have had no corruption issues throughout. Currently on Canary 24304.
yeah I was more worried about phone not booting as thats what happened to me
Like i said earlier. Something is borked unfortunately if the device is corrupted scenario happens.
Yes, those scenarios should be treated as separate issues as one exists for a long time now. As things usually go everything gets mixed up and there's a lot of chaos now.
There´s no kernel source yet for stable march 12.1.0, which dropped a few hours ago. They probably push it during night in my timezone. Not going to bother waiting.
Hey, how do you downgrade from canary to stable Magisk? I just switched back to the stable channel in the Magisk app but I'm sure there's more to do, right?Since I´m a bit impatient, I downgraded to stable magisk 24300 and was able to boot the A12L builds from the linked post on march stable update. So far no issues. Make sure you´re not on canary 24303 or later!
If you feel comfortable and don´t want to miss out on any features (sweep to sleep is in my muscle memory), at least it´s booting fine
I uninstalled magisk app, reinstalled older magisk app, repatched boot.img, flashed repatched boot.img via fastboot. (if you're running a custom kernel you need to reflash completely to stock, by following the guide from the FAQ, before flashing "only" stock boot.img)