How To Guide [GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet

Search This thread

CPngN

Senior Member
Apr 18, 2012
169
33
Bay Area, Ca
My P6P is locking up 2 minutes after booting! I rebooted today because I thought I had lost a widget and was hoping Nova 7 was just acting up. (After rebooting I found the widget 1 page over - need to lock the destop icons down!) Just after my Calengoo app loaded and popped up my reminders for the day, everything froze. ...except the clock. After about 1 minute it reboots. During that minute I cannot do anything on the screen, nor does it respond to holding the power button down for a solid 15-20 seconds! Rinse repeat.
After it boots up, I have about 2 minutes to do things. I paused Adaway, turned off modules in Magisk and then tried to apply the update. Which went all the way through and rebooted when I tapped the button, but... never applied. Oh, I also disabled the blacklist in Magisk in case I had "gone too far" hiding things.
I'm hoping I can just reflash and get out of this.. it's very strange how far it gets before it freezes. As if there's "one last app" or service that executes and gets stuck. Anyone know how to diagnose?
 
  • Wow
Reactions: roirraW "edor" ehT

CPngN

Senior Member
Apr 18, 2012
169
33
Bay Area, Ca
My P6P is locking up 2 minutes after booting! I rebooted today because I thought I had lost a widget and was hoping Nova 7 was just acting up. (After rebooting I found the widget 1 page over - need to lock the destop icons down!) Just after my Calengoo app loaded and popped up my reminders for the day, everything froze. ...except the clock. After about 1 minute it reboots. During that minute I cannot do anything on the screen, nor does it respond to holding the power button down for a solid 15-20 seconds! Rinse repeat.
After it boots up, I have about 2 minutes to do things. I paused Adaway, turned off modules in Magisk and then tried to apply the update. Which went all the way through and rebooted when I tapped the button, but... never applied. Oh, I also disabled the blacklist in Magisk in case I had "gone too far" hiding things.
I'm hoping I can just reflash and get out of this.. it's very strange how far it gets before it freezes. As if there's "one last app" or service that executes and gets stuck. Anyone know how to diagnose?
I booted and flash booted the original boot.img. Magisk acknowledges that it can't load, no root. No change.. meaning even on stock it is rebooting. Anyone have ideas or seen this yet on their P6 ?? T.I.A.
 
  • Wow
Reactions: roirraW "edor" ehT

CPngN

Senior Member
Apr 18, 2012
169
33
Bay Area, Ca
I booted and flash booted the original boot.img. Magisk acknowledges that it can't load, no root. No change.. meaning even on stock it is rebooting. Anyone have ideas or seen this yet on their P6 ?? T.I.A.
Interesting to note:
While frozen for 60-90 seconds, I can plug it into my Mac again and issue "adb reboot bootloader" and can then flash things. So someone underneath everything, it's running enough to respond to this, and to keep the seconds ticking in the clock. But I can't imagine reflashing everything else will change much, but I suppose it won't hurt either. Going to try, as I was hoping to use the camera tonight. Grrr
 
  • Wow
Reactions: roirraW "edor" ehT

CPngN

Senior Member
Apr 18, 2012
169
33
Bay Area, Ca
Interesting to note:
While frozen for 60-90 seconds, I can plug it into my Mac again and issue "adb reboot bootloader" and can then flash things. So someone underneath everything, it's running enough to respond to this, and to keep the seconds ticking in the clock. But I can't imagine reflashing everything else will change much, but I suppose it won't hurt either. Going to try, as I was hoping to use the camera tonight. Grrr
More fun facts: If I play media before it freezes, the music or video keeps playing. I just reflashed everything (without the "-w" on last command) and rebooted. Started music. It still froze, but played music right until the quick reboot.
I'm still rebooting. It stays "frozen" (unresponsive) longer than it takes to reboot (which is like < 10 seconds).
After that, the first boot had the original colors on the G boot animation. But after that... I've noticed the faded color which I assume means it's acknoledging that it has been "altered" or rooted. Perhaps I should push to both banks, but am I just wasting time flashing the same content that's already there?
This is frustrating!
 
Last edited:
  • Wow
Reactions: roirraW "edor" ehT

Koss4c

Member
Sep 21, 2016
11
5
Yeah I didnt run any su commands like the video does....my banking app and gpay works as advertised :) so I am good there. I need to rewatch when I am less buzzed...now I need to get my google work profile working without failing its checks... :)
Super interesting how different people are getting different results :S i would have thought it was be universal. Glad ur is working "off the bat"
 

Koss4c

Member
Sep 21, 2016
11
5
Interesting to note:
While frozen for 60-90 seconds, I can plug it into my Mac again and issue "adb reboot bootloader" and can then flash things. So someone underneath everything, it's running enough to respond to this, and to keep the seconds ticking in the clock. But I can't imagine reflashing everything else will change much, but I suppose it won't hurt either. Going to try, as I was hoping to use the camera tonight. Grrr
Just confirming you have "canary" magisk -> when it downloads, it downloads as app-debug. if u dont have that it wont work (that was my issues)
 
Jan 13, 2015
12
8
More fun facts: If I play media before it freezes, the music or video keeps playing. I just reflashed everything (without the "-w" on last command) and rebooted. Started music. It still froze, but played music right until the quick reboot.
I'm still rebooting. It stays "frozen" (unresponsive) longer than it takes to reboot (which is like < 10 seconds).
After that, the first boot had the original colors on the G boot animation. But after that... I've noticed the faded color which I assume means it's acknoledging that it has been "altered" or rooted. Perhaps I should push to both banks, but am I just wasting time flashing the same content that's already there?
This is frustrating!
I would consider flashing back to stock to see if these problems continue to occur, if you still see crashing you can do a log dump and look for why the device is crashing, my first pro was experiencing phy errors when I was watching videos outside, it was really cold here, did and RMA and my new device does not crash. Currently experimenting on the original phone before I return it.
 
  • Like
Reactions: CPngN

CPngN

Senior Member
Apr 18, 2012
169
33
Bay Area, Ca
Just confirming you have "canary" magisk -> when it downloads, it downloads as app-debug. if u dont have that it wont work (that was my issues)
Yep, had that one after trying alpha and failing early. The fact that my phone boots and works perfectly fine but only for maybe 2 minutes makes me think that there's something loading that comes near the end or just takes longer than everything else, and then it crashes and boom. I've disabled Tasker, and I had recently set up Greenify again and probably should not have. So since I saw that notification icon show up late one of my reboots, just before it "soft froze", I thought that may be the culprit. Seems logical given what it can do. But I can't uninstall it until I remove it from Device Admin Apps. Which I have tried to do, but it doesn't stick! If I boot, jump in real fast and disable that setting, back out, and hold power+up -> Power Off so that things should definitely save before restarting.... it still comes back as a Device Admin.
I have a bad feeling that it may be faster to jump in and try to do a full reset and just restore everything yet again. At least I can get enough time to save my Nova setup and other configs.
Can I grab logs from an adb shell to review on the computer? I'm not sure where to look on Android 12 or what to grab with the short period of time I have under a normal boot. (Can one pull files from fastboot or recovery?) Thanks all!!!
 

CPngN

Senior Member
Apr 18, 2012
169
33
Bay Area, Ca
I would consider flashing back to stock to see if these problems continue to occur, if you still see crashing you can do a log dump and look for why the device is crashing, my first pro was experiencing phy errors when I was watching videos outside, it was really cold here, did and RMA and my new device does not crash. Currently experimenting on the original phone before I return it.
Yeah I have put stock back on. Then I switched to the other slot and repeated everything including the zip file push which takes a while. It booted and runs.... just as it has all day. I have definitely lost root; verified in 3 apps.
During a reboot in one part of that attempt, I noticed the usual faded G logo was back in full rich colors, like I had relocked the bootloader?! But since then it's been back to that faded look. Maybe that was related to the first time booting on slot_a.

So yeah, I think logs would be key before wiping everything. How can I grab the right ones? I'd say between the time I boot and can get in with adb and the time it finally reboots itself I have 4-5 minutes.
Thx guys
 

Koss4c

Member
Sep 21, 2016
11
5
You didn't read the OP. I absolutely did cover this under "Pass SafetyNet". Don't hijack my thread. I tried to keep instructions relatively simple. I am passing SafetyNet on my Pixel 5 using the modules I mentioned, and did not have to run any commands.

No

Unfortunately I can't provide any insight to that issue.

Doesn't work for anyone, and problems with unlocking the bootloader are outside the scope of this thread.
Sorry mate you did cover it.

Just wanted to give people the easy version *hands the floor back to you* its all yours
 
  • Like
Reactions: V0latyle

Lycidias

Senior Member
New magisk update 😊
Screenshot_20220123-174919_Mana.png
 

Dragon Kumera

Senior Member
Mar 14, 2019
323
105
Yeah I have put stock back on. Then I switched to the other slot and repeated everything including the zip file push which takes a while. It booted and runs.... just as it has all day. I have definitely lost root; verified in 3 apps.
During a reboot in one part of that attempt, I noticed the usual faded G logo was back in full rich colors, like I had relocked the bootloader?! But since then it's been back to that faded look. Maybe that was related to the first time booting on slot_a.

So yeah, I think logs would be key before wiping everything. How can I grab the right ones? I'd say between the time I boot and can get in with adb and the time it finally reboots itself I have 4-5 minutes.
Thx guys

Have you tried flash full factory image no modifications and try safe mode? (do not restore anything or sign into google account). Let it sit stock as bare bones as can be.
 
  • Like
Reactions: roirraW "edor" ehT

V0latyle

Forum Moderator
Staff member
just launched my magisk app and wow hey there is an update. Where would I download an offline version? (or can I save the download from magisk app itself).
Magisk Canary 23018

If you go to the main Magisk page, there's a small easy to miss button:
1642964998585.png

When you update from within the app, it does download the apk file to /storage/Downloads
 

roirraW "edor" ehT

Forum Moderator
Staff member
  • Like
Reactions: CPngN and V0latyle

V0latyle

Forum Moderator
Staff member
Just confirming you have "canary" magisk -> when it downloads, it downloads as app-debug. if u dont have that it wont work (that was my issues)
Yes, Magisk Stable has not been updated with the Canary commits. Stable is still at 23000, Canary is currently at 23018. 23010+ is Zygisk and is not compatible with some pre-Zygisk modules such as those that depended on Riru.

This is why in the OP, I advise against using Magisk Stable, especially on the Pixel 6 / 6 Pro.
 
  • Like
Reactions: roirraW "edor" ehT

Dragon Kumera

Senior Member
Mar 14, 2019
323
105

CPngN

Senior Member
Apr 18, 2012
169
33
Bay Area, Ca
Have you tried flash full factory image no modifications and try safe mode? (do not restore anything or sign into google account). Let it sit stock as bare bones as can be.
I was closing in on that decision when I decided to look up how to read logs. ("adb logcat" btw). I had to reroot and then I was able to see a couple of noisy apps in the logs, greenified being one of them as I suspected. Using su, I was able to uninstall greenify and everything has been fine since then! Today I've just been restoring all the things I disabled hoping that something would make it stable (lots of permissions to redo). Thanks all.
 

NippleSauce

Senior Member
Jun 23, 2013
369
218
ya i defiantly missed it. i tried looking on github page but only saw v23.

thx!

Also I never hide magisk app so everything went smoothly
I just noticed the update and pushed it through via the app. Leaving it hidden didn't affect the update for me. Now I just gotta find the changelog =)

*Edit* - Thank you so much @V0latyle ! Quick question, but do you know if un-hiding Magisk before updating it would only be a requirement with specific modules installed and active (and depending on the Magisk changes)?
 
Last edited:

V0latyle

Forum Moderator
Staff member
I just noticed the update and pushed it through via the app. Leaving it hidden didn't affect the update for me. Now I just gotta find the changelog =)
- [Zygisk] Show warning in app UI to indicate incompatible Zygisk modules
- [App] Allow modules to specify an update URL for in-app update + install

Commits to 23018
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Hi All,
    Up until the March update I was adding the line "-disable-verity --disable-verification vbmeta.img" to Flash-all.bat. I read that it was no longer necessary so I flashed March w/o it and had no issues. Now I'm reading it may cause issues? Should i add that line back when I flash April? Or will that wipe my phone?
    Thanks
    Disabling verity & verification was originally needed due to the fact that the phone would not boot if you had (in general) a modified boot image, e.g. magisk patched or custom kernel. This was fixed back in December with Canary Magisk 23016 and most, if not all, custom kernels now have updated the magiskboot binaries to also prevent this problem.

    However, in various situations people are still getting the "Your device is corrupt" eio message. Disabling verity & verification will likely prevent you from getting this message, but this isn't to say that you need to disable those flags. Earlier in the device's history, when you got the corrupt message the only way to get rid of it was to wipe data or clean flash. Now it appears that there are several other methods to get rid of the message without having to do a full wipe/clean flash (depending on what you were doing to cause the message to appear), although there still may be some circumstances where a wipe may be needed.

    Having the corrupt eio message does not appear to cause any harm and people have used their phones just fine with this message present, as far as I can see. It seems to be more of an annoyance.

    If you don't currently have those flags disabled and do decided to disable them again, a wipe will be required.

    So it's up to you whether or not to disable those flags. Most people today don't and have had no problems for the most part, but a few of us (myself included) still do, just to prevent getting the corrupt message in the first place and possibly having to wipe to get rid of it. As I said above, though, there now appears to be other ways besides wiping to get rid of that message if you do run into it, although there still may be some instances where a wipe may be required. But with Magisk and magiskboot binaries being updated, the original need to do this is no longer required.

    Hope that helps...
    5
    I'm not sure what I'm doing wrong, because it seems so straight forward, but this method has yet to work for me the past 3 updates. I just install the whole thing and delete "-w" now, but THIS way posted, seems easier, if it would work.View attachment 5594819
    From what I've observed over the years, that way has always been at least a little bit hit and miss, although I think it misses more often recently.

    I've always been a fan of just using the full firmware image with the -w removed, as you said, and I don't have any plans on doing it any other way.
    5
    I'd like to point out that there are two corrupt messages.

    First is the red eio message:
    boot_red1.png

    This indicates that while a valid Android system has been found, a dm-verity mismatch has occured. It is not a fatal error, and the device can continue to be used. More information here.
    What exactly causes it, as well as how to fix it is unclear at this time; I have encountered this error before, and sideloading the OTA fixed it. I personally have never encountered this when using the factory image method.

    Second, there is the Rescue Party:
    Hn-wheKMGECx5IipI9Ywa_Tcr7ZD3R69LFOCoCkCDQI.png

    This means the system has detected that core system components are stuck in a crash loop; this may be the kernel or a persistent system app. More information here
    This is a fatal error; we encountered this when we first disabled verity/verification if /data was not clean; the user could either reflash the unpatched boot image and vbmeta without the disabling options, or wipe data to continue.
    4
    Have you tried live booting followed by a direct install? :) This way if it fails , android will just boot the stock boot image
    That's an excellent idea for @android_dan.

    Edit/add-on:
    Thanks for the reply. Maybe 'm being dense but not sure how the flash tool is going to help. The problem isn't recovering from the bootloop. That's just a matter of flashing an unpatched boot image. The problem is what could be causing the patched file to bootloop the phone. I've updated this rooted phome 3 or 4 times now by flashing a patched boot file with no issues and have changed nothing on the phone
    I suggested the Official Google Android Flash Tool site because it has fixed things that manually flashing the factory image hasn't, in at least a dozen examples I've read about in this section alone in the six months the P6P has been out.

    I know that it doesn't sound necessarily rational, but it's happened often enough and almost every time it's been suggested to someone to do that instead of manually flashing the factory image zip, that the online tool fixed their issue.
  • 81
    If you are looking for my guide on a different Pixel, find it here:
    Update 5-13-22: While Magisk 24.0 has been updated for use with Android 12, many users on the Pixel 6 and 6 Pro are still experiencing issues. It is strongly recommended to use Canary 24310. This version also includes beta support for A13B2.
    Discussion thread for migration to 24.0.

    DO NOT use any version of Magisk lower than Canary 23016 as it does not yet incorporate the necessary fixes for Android 12 and your device.


    WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.

    Prerequisites:


    Android Source - Setting up a device for development


    1. Follow these instructions to enable Developer Options and USB Debugging.
    2. Enable OEM Unlocking. If this option is grayed out, unlocking the bootloader is not possible.
    3. Connect your device to your PC, and open a command window in your Platform Tools folder.
    4. Ensure ADB sees your device:
      Code:
      adb devices
      If you don't see a device, make sure USB Debugging is enabled, reconnect the USB cable, or try a different USB cable.
      If you see "unauthorized", you need to authorize the connection on your device.
      If you see the device without "unauthorized", you're good to go.
    5. Reboot to bootloader:
      Code:
      adb reboot bootloader
    6. Unlock bootloader: THIS WILL WIPE YOUR DEVICE!
      Code:
      fastboot flashing unlock
      Select Continue on the device screen.

    1. Install Magisk on your device.
    2. Download the factory zip for your build.
    3. Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img
    4. Copy boot.img to your device.
    5. Patch boot.img with Magisk: "Install" > "Select and Patch a File"
    6. Copy the patched image back to your PC. It will be named "magisk_patched-23xxx_xxxxx.img". Rename this to "master root.img" and retain it for future updates.
    7. Reboot your device to bootloader.
    8. Flash the patched image:
      Code:
      fastboot flash boot <drag and drop master root.img here>
    9. Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>

    1. Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.
    2. Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
    3. Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device.
    4. You should now be updated with root.

    1. Download the OTA.
    2. Reboot to recovery and sideload the OTA:
      Code:
      adb reboot sideload
      Once in recovery:
      Code:
      adb sideload ota.zip
    3. When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
    4. Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
    5. Reboot to bootloader.
    6. Boot the master root image (See note 1):
      Code:
      fastboot boot <drag and drop master root.img here>
      Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
    7. Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
    8. Reboot your device. You should now be updated with root.
    Note: You can use Payload Dumper to extract the contents of the OTA if you want to manually patch the new boot image. However, I will not cover that in this guide.

    Please note that the factory update process expects an updated bootloader and radio. If these are not up to date, the update will fail.
    1. Download the factory zip and extract the contents.
    2. Reboot to bootloader.
    3. Compare bootloader versions between phone screen and bootloader.img build number
      Code:
      fastboot flash bootloader <drag and drop new bootloader.img here>
      If bootloader is updated, reboot to bootloader.
    4. Compare baseband versions between phone screen and radio.img build number
      Code:
      fastboot flash radio <drag and drop radio.img here>
      If radio is updated, reboot to bootloader.
    5. Apply update:
      Code:
      fastboot update --skip-reboot image-codename-buildnumber.zip
      When the update completes, the device will be in fastbootd. Reboot to bootloader.
    6. Boot the master root image (See note 1):
      Code:
      fastboot boot <drag and drop master root.img here>
      Note: If you prefer, you can manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
    7. Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
    8. Reboot your device. You should now be updated with root.
    Note: If you prefer, you can update using the flash-all script included in the factory zip. You will have to copy the script, bootloader image, radio image, and update zip into the Platform Tools folder; you will then have to edit the script to remove the -w option so it doesn't wipe your device.
    The scripted commands should look like this:
    Code:
    fastboot update bootloader <bootloader image name>
    fastboot reboot bootloader
    ping -n 5 127.0.0.1 > nul
    fastboot update radio <radio image name>
    fastboot reboot bootloader
    ping -n 5 127.0.0.1 > nul
    fastboot update  --skip-reboot --slot=all <image-device-buildnumber.zip>
    Once this completes, you can reboot to bootloader and either boot your master patched image, or if you patched the new image, flash it at this time.

    1. Follow the instructions on the Android Flash Tool to update your device. Make sure Lock Bootloader and Wipe Device are UNCHECKED.
    2. When the update completes, the device will be in fastbootd. Reboot to bootloader.
    3. Boot the master root image (See note 1):
      Code:
      fastboot boot <drag and drop master root.img here>
      Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
    4. Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
    5. Reboot your device. You should now be updated with root.

    This is my configuration that is passing Safety Net. I will not provide instructions on how to accomplish this. Attempt at your own risk.

    Zygisk + DenyList enabled
    All subcomponents of these apps hidden under DenyList:
    • Google Play Store
    • GPay
    • Any banking/financial apps
    • Any DRM media apps
    Modules:
    To check SafetyNet status:
    I do not provide support for Magisk or modules. If you need help with Magisk, here is the Magisk General Support thread. For support specifically with Magisk v24+, see this thread.

    Points of note:
    • The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.
    • While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:
      screenshot_20211218-194517-png.5486339
    • "Installed" shows the version of patch in the boot image. If this says N/A, you do not have root access - the boot image is not patched, or you have a problem with Magisk.
    • "App" simply shows the version of the app itself.
    • If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.
    • If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.
    • Some Magisk modules, especially those that modify read only partitions like /system, may cause a boot loop after updating. As a general rule, disable these modules before updating. You are responsible for knowing what you have installed, and what modules to disable.


    Credits:
    Thanks to @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!
    9
    Magisk Stable is now at version 24.1, so I will no longer be providing any Magisk updates.

    You can use any version of Magisk now - Stable, Beta, or Canary. as long as it is 23016 or newer.

    Once again, if you want to switch versions of Maagisk, it is HIGHLY RECOMMENDED that you "Complete Uninstall" within Magisk before installing the new version. Multiple instances of Magisk can break root.

    If you simply want to update Magisk, the best way to do so is from within the app.


    Once the February update is out, I will perform some testing with installing to inactive slot, and if it works, I will update this guide.

    Given the low activity on this thread, I will probably close it if everything goes well with the next update.

    Thank you all for your testing and contributions.
    8
    My update process is to remove vbmeta.img (in addition to removing the -w flag in the flash-all script) from the factory zip before I flash it in fastboot. Seems to have worked so far, ymmv.
    7
    I just used this method, (same one described on Magisk website here https://topjohnwu.github.io/Magisk/ota.html) and it worked perfectly, both root and safetynet.
    Can someone explain to me why you see all kind of guide to update which are far more complicated than that ?
    Part of it is due to device differences - non A/B devices can't use seamless updates, so re-rooting is only possible by either patching the boot image directly, or by flashing Magisk in a custom recovery.

    Part of it is also due to user preferences. Some people, like me, prefer to update using the factory images, instead of OTA.

    And part of it is probably a bit of misinformation mixed in with anecdotes, where people who don't fully understand how the process works, but they declare that something has to be done a certain way because of what worked for them.

    I try to stick to the first two. I've spent a lot of time learning about how Android works, so I make a point of providing instructions that align with how everything is supposed to be done, while accommodating alternatives for those who want them.

    Are you 100% sure?

    Cause topjohnwu said that OTA patching from within Magisk was broken for Pixel devices.

    See here

    Notice the date of that post, 16 months ago. Magisk Canary 23017 re-incorporated the ability to install to inactive slots.

    I have been following the commits closely, so when 23017 was released, I announced it in my guides. Had you read back a couple pages, your question has been answered.

    If you don't believe me, check the commits here.
    7
    Magisk Canary updated to 23019
    Changes:
    - [Zygisk] Skip loading modules into the Magisk app to prevent conflicts
    - [MagiskBoot] Change `zopfli` to a more reasonable config so it doesn't take forever
    - [General] Several `BusyBox` changes

    Preferred method of update is from within Magisk app.


    If installing for the first time, here is the APK Download