Can't boot Magisk 21 and Android 11

[nontheoretical]

Updated to Android 11 (clean install) and can't get Magisk patched image to boot.
I'm using manager 8.0.2(307) and the latest Magisk is 21.0
I patched the boot image from the website, flash successfully, but it reboots to the bootloader saying "no valid slot to boot"

Is anyone else having this issue?
I know the unpatched boot image is ok because when I flash it back it boots up fine.
Am I missing anything?

Edit:
Was able to boot without issue with the latest Magisk Canary 04995881 (21002).

Apparently, it's related to these issues:
https://github.com/topjohnwu/Magisk/issues/3277
https://github.com/topjohnwu/Magisk/issues/3271

I'm willing to help anyone else suffering from this issue get their phones booting back up.

 

[dcarvil]

Updated to Android 11 (clean install) and can't get Magisk patched image to boot.
I'm using manager 8.0.2(307) and latest Magisk is 21.0
I patched the boot image from the website, flash successfully, but it reboots to the bootloader saying "no valid slot to boot"

Is anyone else having this issue?
I know the unpatched boot image is ok because when I flash it back it boots up fine.
Am I missing anything?

Thanks in advance.

Did you disable or remove all modules? See https://github.com/topjohnwu/Magisk/issues/3292#issuecomment-705764812

I have no modules installed, and had no problems with the Sept. update. I have not yet tried October.

 

[nontheoretical]

Did you disable or remove all modules? See https://github.com/topjohnwu/Magisk/issues/3292#issuecomment-705764812

I have no modules installed, and had no problems with the Sept. update. I have not yet tried October.

I'm on the Oct update and I don't have any modules installed.
It's a clean install so I haven't even had the chance to install modules yet.

I might downgrade to Sept update if I can't root soon.

Apparently it's related to these issues:
https://github.com/topjohnwu/Magisk/issues/3277
https://github.com/topjohnwu/Magisk/issues/3271

 

[Bubbler4343]

I am also having the "no valid slot to boot" error. I updated ota google play system update and then got an error to factory reset or try again. I have been trying to flash-all without -w to september and october factory images but still keep getting the error and cannot boot into system.

Can anyone help me fix this issue? I'm unable to use the adb magisk remove-module script.

 

[dcarvil]

I am also having the "no valid slot to boot" error. I updated ota google play system update and then got an error to factory reset or try again. I have been trying to flash-all without -w to september and october factory images but still keep getting the error and cannot boot into system.

Can anyone help me fix this issue? I'm unable to use the adb magisk remove-module script.

There are some recent comments on running the remove-module script in the github link in post 2. Hopefully something there will help.

 

[nontheoretical]

I am also having the "no valid slot to boot" error. I updated ota google play system update and then got an error to factory reset or try again. I have been trying to flash-all without -w to september and october factory images but still keep getting the error and cannot boot into system.

Can anyone help me fix this issue? I'm unable to use the adb magisk remove-module script.

Not sure about the removing of the modules (maybe try the safe mode trigger built into the new Magisk?)

I was able to successfully boot by flashing the stock boot image, the updating to the latest Magisk Canary 04995881 (21002)

Looks like this was updated recently due to the two issues I listed earlier.
I'm gonna keep my magisk_patched.img for this build of Magisk and try with the latest beta and stable releases as they come out.

I'm happy to help anyone else get their build to boot, provide checksums for sanity checks, etc.

 

[EndlessBliss]

I can confirm that flashing the 11 image in its stock form first, letting Android upgrade your user data, then flashing the image with the patched boot.img file works!

Directly flashing an image over Android 10 with boot.img patched throws it into fastboot

 

[nontheoretical]

I can confirm that flashing the 11 image in its stock form first, letting Android upgrade your user data, then flashing the image with the patched boot.img file works!

Directly flashing an image over Android 10 with boot.img patched throws it into fastboot

Are you using Canary or Stable?
I had to switch to Canary to get it to boot.

I was coming from a clean install so I had no user data to upgrade.

 

[EndlessBliss]

I'm coming from a very unclean install and it worked perfectly with this method. Switched to Beta in Magisk Manager and running 21.0 (21000) on a Pixel 4 XL

 

[nontheoretical]

I'm coming from a very unclean install and it worked perfectly with this method. Switched to Beta in Magisk Manager and running 21.0 (21000) on a Pixel 4 XL

It looks like this was only reported by users on pixel 3a and older models.