Magisk Canary + Pixel 4 XL + Android 11 = stuck at boot

[delanvital]

I hope this is the right place to ask, pardon me if not:

Issue: After upgrading to Android 11, the patched boot image causes bootloop, when patched using Magisk Canary

Phone/setup: Pixel 4 XL, updated today to Android 11 using OTA, which strangely enough worked just fine. Previously used the usual Magisk build, but grabbed Canary for this stuff. I'm flashing using latest ADB tools via download straight from Google + using original Pixel cable which so far has worked great with fastboot. Fastboot devices -l reports the phone.

Approach:
Flash-all.bat without -w, boots fine, all in order = boots fine, all in order
Extract boot.img, move to phone
Download latest Canary build straight from github front page, moditfy boot.img, transfer image to pc
ADB reboot bootloader, fastboot flash boot modified-image
Outcome: Stuck in boot - makes it to the "G" logo with the spinning line below. Left like that for 20 minutes, no change.

Approach two:
Flash-all.bat without -w, boots fine, all in order = boots fine, all in order
Extract boot.img, move to phone
Moditfy boot.img, transfer image to pc
ADB reboot bootloader, fastboot flash boot_a modified-image, fastboot flash boot_b modified-image
Outcome: Stuck in boot - makes it to the "G" logo with the spinning line below. Left like that for 20 minutes, no change.

Any idea what I'm doing wrong?

EDIT: Solution here! https://forum.xda-developers.com/showpost.php?p=83499831&postcount=23

 

[ReservedName]

I hope this is the right place to ask, pardon me if not:

Issue: After upgrading to Android 11, the patched boot image causes bootloop, when patched using Magisk Canary

Phone/setup: Pixel 4 XL, updated today to Android 11 using OTA, which strangely enough worked just fine. Previously used the usual Magisk build, but grabbed Canary for this stuff. I'm flashing using latest ADB tools via download straight from Google + using original Pixel cable which so far has worked great with fastboot. Fastboot devices -l reports the phone.

Approach:
Flash-all.bat without -w, boots fine, all in order = boots fine, all in order
Extract boot.img, move to phone
Download latest Canary build straight from github front page, moditfy boot.img, transfer image to pc
ADB reboot bootloader, fastboot flash boot modified-image
Outcome: Stuck in boot - makes it to the "G" logo with the spinning line below. Left like that for 20 minutes, no change.

Approach two:
Flash-all.bat without -w, boots fine, all in order = boots fine, all in order
Extract boot.img, move to phone
Moditfy boot.img, transfer image to pc
ADB reboot bootloader, fastboot flash boot_a modified-image, fastboot flash boot_b modified-image
Outcome: Stuck in boot - makes it to the "G" logo with the spinning line below. Left like that for 20 minutes, no change.

Any idea what I'm doing wrong?

Pixel 4a here, just tried to follow OTA instructions and ended up bootlooped until I paused it. After resuming it rebooted but the update didn't take and magisk was uninstalled. I did have the safetynet fingerprint module installed so probably this caused an issue? Not sure it relates exactly to your problem but thought I'd chime in with a similar problem and model.

EDIT:
After this reboot where I lost magisk I retried the OTA and it succeeded. I then tried to flash the patched boot.img in fastboot but it failed now I'm endlessly bootlooping.

EDIT 2:
tried a couple things but couldn't get 11 to boot so I flashed back to 10 but wiped my userdata so I'm done messing around for awhile I think 11 just is a no go for now.

 

[delanvital]

Pixel 4a here, just tried to follow OTA instructions and ended up bootlooped until I paused it. After resuming it rebooted but the update didn't take and magisk was uninstalled. I did have the safetynet fingerprint module installed so probably this caused an issue? Not sure it relates exactly to your problem but thought I'd chime in with a similar problem and model.

On Android 10, when booting Magisk in the core only mode, I would still fail the ctsProfile. I would never complete safetynet 100%. I am not sure what should be possible, but it seems some ppl can make it pass safetynet on Android 10 by running Magisk in core only mode. When upgrading to Android 11, and before flashing any boot.img, but after installing Canary build, I would still fail the ctsProfile part of the satefy net. I wonder if that somehow impacts.

If wonder if the issue is linked to the fingerprint. I also have the fingerprint module (where it allows apps to believe it's using a fingerprint, but in fact it's my face). I will try and remove all the modules, then uninstall Magisk, then reinstall Canary build. Cheers mate.

 

[cgo72123]

I hope this is the right place to ask, pardon me if not:

Issue: After upgrading to Android 11, the patched boot image causes bootloop, when patched using Magisk Canary

Phone/setup: Pixel 4 XL, updated today to Android 11 using OTA, which strangely enough worked just fine. Previously used the usual Magisk build, but grabbed Canary for this stuff. I'm flashing using latest ADB tools via download straight from Google + using original Pixel cable which so far has worked great with fastboot. Fastboot devices -l reports the phone.

Approach:
Flash-all.bat without -w, boots fine, all in order = boots fine, all in order
Extract boot.img, move to phone
Download latest Canary build straight from github front page, moditfy boot.img, transfer image to pc
ADB reboot bootloader, fastboot flash boot modified-image
Outcome: Stuck in boot - makes it to the "G" logo with the spinning line below. Left like that for 20 minutes, no change.

Approach two:
Flash-all.bat without -w, boots fine, all in order = boots fine, all in order
Extract boot.img, move to phone
Moditfy boot.img, transfer image to pc
ADB reboot bootloader, fastboot flash boot_a modified-image, fastboot flash boot_b modified-image
Outcome: Stuck in boot - makes it to the "G" logo with the spinning line below. Left like that for 20 minutes, no change.

Any idea what I'm doing wrong?

Same here, and after the Glogo, if I restart I get ""no valid slot to boot". Flashing unpatched boot.img gets me back in, but there doesn't seem to be a way to root 11 release build?

 

[badhabit_wb]

Works fine on my Pixel 4 xl. I'm using a patched boot img. Make sure you use the correct boot img

 

[MichRT]

...if I restart I get ""no valid slot to boot". Flashing unpatched boot.img gets me back in...

Google Store Pixel 4a here. I have the exact same experience. Tried:

2. Uninstall Magisk -> Install OTA -> Install Inactive Slot -> bootloops 3 times and settles on previous boot slot, Android 10, no Magisk

3. Patch Boot.img -> flash-all.bat -> fastboot flash boot magisk_patched.img -> fastboot bootloop with the message "no valid slot to boot"

Can confirm re-flashing stock boot.img or running the full update script successfully boots Android 11, no root of course

 

[ChocoboX]

Pixel 4 XL user here. I updated to Android 11 last night. Same thing happened to me. Waiting for an update to Magisk for Android 11

 

[delanvital]

Pixel 4 XL user here. I updated to Android 11 last night. Same thing happened to me. Waiting for an update to Magisk for Android 11

I noticed a new buildof Magisk available in the manager. New modified boot image has a slightly different filesize. Tried fastboot boot magisk_patched.img but still stuck on G and the moving line below. I wonder what is different compared to the 4xl users who has no problems...

 

[Didgeridoohan]

Just want to point out that a common cause for issues when updating from one Android version to another is incompatible mods.

Make sure that no Magisk modules are installed that could be causing issues. Uninstalling the modules before updating, uninstalling Magisk, manually deleting the module directories in /data/adb/modules (or the whole modules directory) or wiping /data would all be ways of accomplishing this...

This might not be true for everyone, but it's quite likely.

Edit: Oh yeah... And don't install TWRP. Only booting it seems to be fine though.

 

[ChocoboX]

I got it to work !!! Pixel 4 XL user. Might work on other Pixel phones / non-Pixel phones as well.
You need to download Magisk Canary apk first.
Try this post https://www.xda-developers.com/latest-magisk-canary-release-adds-support-for-android-11/
Here is the trick, you need to set the update channel in the settings to Canary Debug. Just Canary won't work and won't show any updates!
Then you will see immediately that a new version is available for manager and Magisk. Update the manager first. Then install Magisk to boot.img. Flash and there you go. I even got modules working and GPay works and even the CTS profile works! previously that failed on me (despite trying the settings recommended and Terminus commands with Busybox)

 

[chaim]

does not work

I got it to work !!! Pixel 4 XL user. Might work on other Pixel phones / non-Pixel phones as well.
You need to download Magisk Canary apk first.
Try this post https://www.xda-developers.com/latest-magisk-canary-release-adds-support-for-android-11/
Here is the trick, you need to set the update channel in the settings to Canary Debug. Just Canary won't work and won't show any updates!
Then you will see immediately that a new version is available for manager and Magisk. Update the manager first. Then install Magisk to boot.img. Flash and there you go. I even got modules working and GPay works and even the CTS profile works! previously that failed on me (despite trying the settings recommended and Terminus commands with Busybox)

i have the same versions but do not see the Canary Debug.
currently it is not working

 

[Didgeridoohan]

There's only been one Canary channel for some time (and it's the debug release, even though it doesn't say so in the Manager). If anyone is using a Manager that has both a "Canary" and a "Canary Debug" channel they're using an old build of the Manager. And on such a build, the regular "Canary" channel won't work since it no longer exists.

 

[ChocoboX]

i have the same versions but do not see the Canary Debug.
currently it is not working

Ok, I found the correct link to download Magisk Canary apk
https://forum.xda-developers.com/pixel-4-xl/how-to/android-11-beta-1-jun-2020-t4113249

It's an older version but once you switch to Canary Debug it should show correct updates. For there things worked for me.
Also, I'm attaching a link to download the Magisk boot image for Android 11 directly, in case you want to skip this whole process. Just flash it with Fast Boot
https://1drv.ms/u/s!Ark6wHh1kVRCg9NyWPCCeqtpfT4XUA?e=oRse0J

 

[rester555]

Does Soli work or do you need to download that module too?

 

[ChocoboX]

Does Soli work or do you need to download that module too?

What is Soli? Sorry for the dumb question. I can try and see.

 

[rester555]

It's the RF based motion sensor in the front of the phone that turns on active display and swipes in front of the display to control the phone.

 

[ChocoboX]

It's the RF based motion sensor in the front of the phone that turns on active display and swipes in front of the display to control the phone.

I'm in the US already so it works without a problem for me. I also tried to install Enable Soli from GitHub and it installed and phone booted. Not sure how to test it further for you.

 

[Didgeridoohan]

Just so that there's no confusion...

The correct (and only) place to get the Magisk installation zips and Manager apks is always going to be on John's GitHub.

Here's the (current) link to the up-to-date Canary Manager:
https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk

But, if in doubt, always go to the above linked GitHub to get the latest downloads.

Downloading from anywhere else might mean that you are installing an altered (possibly maliciously) root Manager. Don't take the risk...

 

[chaim]

magisk_patched.img

what command do you use to flash it
i use:
./fastboot flash boot magisk_patched.img

and i gets stuck in bootloop

 

[Badger50]

can anyone upload the magisk_patched.img for pixel 4xl

While I don't mind sharing my patched.img, just remember that TJW always recommends that users should patch their own boot.img so as to avoid any potential problems. Having said that, here you go :good:

https://drive.google.com/file/d/15fWU492AQ3eBJCgMGWe2wgc5J2b4MSPu/view?usp=drivesdk