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

Search This thread

roirraW "edor" ehT

Forum Moderator
Staff member
Do you guys have a donation link?
For my part, I too help folks for free. I used to take donations, but I also needed the money more at the time. I don't even remember if I ever officially removed the way to donate to me from XDA. I haven't bothered to check for the way I had set to donate to me in XDA's settings since they changed their software the other year. I wasn't very active for several years until recently as well. I'm just always glad when I can help someone.

I have pretty low expectations these days, too. I'm happy just when there's no drama going on, especially if it's not drama coming from me! 🤣

Thanks very much for this info. I was not planning to use the Pixel 5 version unless it was known to be safe. I will wait for a Pixel 6 version to be released. I have other ways to back up apps and data but want to be able to have a system partition, etc., backup as well. Thanks for the come-back!
For what it's worth, TWRP for one phone 99.99999% of the time will not work on any other phone, but especially not different years' phones from the same manufacturer, and on top of that, the Pixel 6/Pro uses a completely different CPU than the Pixel 5 and previous. I'm sure there were exceptions, and I even have some ideas of what they were, but they were a drop of rain in the sea, relatively speaking. Besides all this, TWRP has to be gotten to work on Android 12 in general - for any phone - first. If/when that is done (could be months, could be a year, could be never), then work getting TWRP to work on the P6 & P6P could start in earnest. So it's a long road... :D

There's times I want to show people just how lucky they are I put up with them
🥂 😂
 

Az Biker

Sr. Mod / Mod & RC-RT Committees / Shred'r of MTBs
Staff member
You don't get away from me that easily :D

Holding the Vol Down button while rebooting halts at bootloader, then user can select recovery from menu
I thought the user was asking for instructions to get into the bootloader. I answered, then reread his comment and realized I misread it.

You're quick on the copy/paste, musta already been quoting the other comments and grabbed mine. Wasn't even live for 20 seconds before I deleted it (unless you used secret squirrel stuff to get it) 😛😛😛
 

Dragon Kumera

Senior Member
Mar 14, 2019
323
104
For what it's worth, TWRP for one phone 99.99999% of the time will not work on any other phone, but especially not different years' phones from the same manufacturer, and on top of that, the Pixel 6/Pro uses a completely different CPU than the Pixel 5 and previous. I'm sure there were exceptions, and I even have some ideas of what they were, but they were a drop of rain in the sea, relatively speaking. Besides all this, TWRP has to be gotten to work on Android 12 in general - for any phone - first. If/when that is done (could be months, could be a year, could be never), then work getting TWRP to work on the P6 & P6P could start in earnest. So it's a long road... :D


🥂 😂
Now I may be completely and totally wrong.

But couldnt we just do fastboot boot twrp.img and if it works it boots if not just turn phone off and reboot? As long as its not flashed we should be able to recover.
 

bleez99

Senior Member
May 1, 2011
275
196
Did you read this part?

There is only 1 way to end up with an accidentally wiped device, and that's using the flash-all script without editing it. But, since I know that's not quite what you're asking...

You simply do not need to worry about verity/verification anymore. Period. Just update your device, patch the new boot image with Magisk 23016, and chive on.


Specificity is important here - Canary 23016 incorporates the boot image header fix. Magisk Canary has been around for a long time, and anything older than 23015 won't work.


Not yet, current Canary is still 23016, but an update is well on the way - and it will support patching to inactive slots, simplifying the update for users who prefer OTA.

OTAs on rooted Pixels have always been iffy. I don't know exactly what causes them to fail, but they usually require a few tries.

Sideloading should always work, though.
My comment on Canary was completely tongue in cheek!

I just had a bad experience with my 5 before the latest canary was released with the fstab fix. Wipe was forced due to a corrupted device, I landed in recovery with try again or wipe. Of course try again didn't work, and I'd rather not have to sit for an hour or three restoring my phone.

Thanks to those that responded.
 

roirraW "edor" ehT

Forum Moderator
Staff member
Now I may be completely and totally wrong.

But couldnt we just do fastboot boot twrp.img and if it works it boots if not just turn phone off and reboot? As long as its not flashed we should be able to recover.
On paper, everything sounds great. I'm not a betting man, though. I wouldn't do this if I were you (or anyone reading this). I could be wrong but I'm given to understand that no phone that has Android 12 has a working TWRP yet.
 

Dragon Kumera

Senior Member
Mar 14, 2019
323
104
On paper, everything sounds great. I'm not a betting man, though. I wouldn't do this if I were you (or anyone reading this). I could be wrong but I'm given to understand that no phone that has Android 12 has a working TWRP yet.
Ya ofc we will need a working android 12 twrp. (But from my experience with pixel xl gen 1 that had twrp from like android 8.0 and before still worked even on android 11 kinda). Though Maybe significant changes were made in 12 to make this null and void.

I would love a way to back up everything local side like twrp did but guess I will have to be careful :).
 

V0latyle

Forum Moderator
Staff member
Now I may be completely and totally wrong.

But couldnt we just do fastboot boot twrp.img and if it works it boots if not just turn phone off and reboot? As long as its not flashed we should be able to recover.
Yep. If it doesn't work, it doesn't work. Won't hurt anything.
My comment on Canary was completely tongue in cheek!

I just had a bad experience with my 5 before the latest canary was released with the fstab fix. Wipe was forced due to a corrupted device, I landed in recovery with try again or wipe. Of course try again didn't work, and I'd rather not have to sit for an hour or three restoring my phone.

Thanks to those that responded.
Interesting. I had no such issue on my P5. I rooted the 12 Beta with 23001, then updated to 23015 when USNF was ported to Zygisk.

You're quick on the copy/paste, musta already been quoting the other comments and grabbed mine. Wasn't even live for 20 seconds before I deleted it (unless you used secret squirrel stuff to get it) 😛😛😛
I SEE EVERYTHING
Nah but for real mods have the godlike ability to see deleted posts...and they can still be replied to even in Deleted Purgatory
 

dilligaf56

Senior Member
Feb 22, 2011
165
45
SoCal, USA
Don't really see any point in backing up the "system" partition. You could simply flash the stock image. With root solutions like Magisk, it's extremely unlikely that you'd need to modify the system partition. You'd just use the mirror partition in Magisk.
And since you are likely rooted, if you need a good solution to backup apps and data, I'd recommend OAndBackupX

Yes, I'm rooted. Magisk really has come a long way since I first started using it on my rooted V20. Back then, you really needed nandroid backups in case something got b0rked on a re-flash.
Took a quick look at OAndBackupX. Once I get everything sorted and tweaked, I will install it and give it a shot. Thanks!
 
  • Like
Reactions: roirraW "edor" ehT

dilligaf56

Senior Member
Feb 22, 2011
165
45
SoCal, USA
Ya ofc we will need a working android 12 twrp. (But from my experience with pixel xl gen 1 that had twrp from like android 8.0 and before still worked even on android 11 kinda). Though Maybe significant changes were made in 12 to make this null and void.

I would love a way to back up everything local side like twrp did but guess I will have to be careful :).

Yes, I have two LG V20s - one running rooted stock Oreo (8) and the other Lineage 18 (11); the same version of TWRP works great with both OS; but of course, they were running on the same hardware. I'm finding that Android 12 and the Pixel 6/pro are horses of a completely different color. Still, I hope that TWRP does come out with a working version for us, even if the use-case is less obvious.
 
  • Like
Reactions: roirraW "edor" ehT

n3owin

New member
Jan 20, 2022
2
1
TLDR > Cant update from Nov to Jan update on my Rooted Pixel 6 Pro

Hey there! first timer here
Im trying to update my rooted Pixel 6 Pro from 12.0.0 (SD1A.210817.036, Nov 2021) to 12.0.0 (SQ1D.220105.007, Jan 2022). I can see the update when i manually search for it on the phone but when it downloads it fails and says "Couldn`t update. Installation problem" with no further explanation.
So i tried the sideload method from this thread. No luck here as well. I got the 12.0.0 (SQ1D.220105.007, Jan 2022) update from the OTA link (Not sure if thats the right one but its the only one available that says JAN 2022) and when i get to the recovery i adb sideload drag file, the file uploads and fails with the following error > error applying update 7 kinstalldeviceopenerror
From googling that error it says that im trying to upload an update meant for another phone. Im sure that im downloading the "raven" one for the pro model.

Any advice would be helpful since i have been scratching my head for the last 6 hours.

A bit more info >
im using the same PC, usb cable, usb port that i used when rooting for the first time.
I rooted the phone following this thread without disabling Android Verified Boot since it said its not needed.
I have the Canary Magisk 23016. Disabled all modules and super rights to apps before trying both methods of update.
Im using the "Tiny ADB & Fastboot" to upload the update to the phone.
Its have not done any previous updates on this phone, rooting was done on Nov update since it came with it.

Extra question > Somebody posted that they had similar problem to mine and they updated with the <Update and Root Factory Image>. (1)If i try that will the phone revert to factory settings and (2) can i use the master root.img that i saved from the first root or do i need to patch it again?

P.S. Thanks a lot for the original guide!
 
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
TLDR > Cant update from Nov to Jan update on my Rooted Pixel 6 Pro

Hey there! first timer here
Im trying to update my rooted Pixel 6 Pro from 12.0.0 (SD1A.210817.036, Nov 2021) to 12.0.0 (SQ1D.220105.007, Jan 2022). I can see the update when i manually search for it on the phone but when it downloads it fails and says "Couldn`t update. Installation problem" with no further explanation.
So i tried the sideload method from this thread. No luck here as well. I got the 12.0.0 (SQ1D.220105.007, Jan 2022) update from the OTA link (Not sure if thats the right one but its the only one available that says JAN 2022) and when i get to the recovery i adb sideload drag file, the file uploads and fails with the following error > error applying update 7 kinstalldeviceopenerror
From googling that error it says that im trying to upload an update meant for another phone. Im sure that im downloading the "raven" one for the pro model.
First, you shouldn't try to take an actual over-the-air update when you're rooted. It's rare that it would work while rooted, and at least with some phones, there's a chance trying to take the OTA while rooted will soft-brick your device (recoverable, obviously, because it's a soft-brick).

In Developer Options, you can disable the automatic OTA update check.

I recommend the other set of instructions in the OP "Spoiler: Update and Root Factory Image". I know there are folks who use the OTA file. I've always found it simpler and never had a problem in the last five years using the full factory image method.

You shouldn't use any modified/repackaged ADB/Fastboot. As the OP says, always use the (official) very Latest SDK Platform Tools. You should check for new Platform Tools every single month before you manually update your phone. Also always check to make sure you have the latest official Google USB Driver installed, at least if you're using Windows.

Extra question > Somebody posted that they had similar problem to mine and they updated with the <Update and Root Factory Image>. (1)If i try that will the phone revert to factory settings and (2) can i use the master root.img that i saved from the first root or do i need to patch it again?
If you follow the instructions in the OP, you won't factory reset your phone. The key is to remove the "-w" from the flash-all.bat (I'm assuming you're using Windows), or the same from the flash-all.sh if you're using Linux.

I can't answer your (2) because I don't do it that way and never have. I'm sure someone else who is knowledgeable about that method will chime in.
 

V0latyle

Forum Moderator
Staff member
The key is to remove the "-w" from the flash-all.bat (I'm assuming you're using Windows), or the same from the flash-all.sh if you're using Linux.
Or don't use the script at all and learn the commands...but I'm old fashioned like that
 

Carousser

Senior Member
Jan 15, 2014
80
15
TLDR > Cant update from Nov to Jan update on my Rooted Pixel 6 Pro

Hey there! first timer here
Im trying to update my rooted Pixel 6 Pro from 12.0.0 (SD1A.210817.036, Nov 2021) to 12.0.0 (SQ1D.220105.007, Jan 2022). I can see the update when i manually search for it on the phone but when it downloads it fails and says "Couldn`t update. Installation problem" with no further explanation.
So i tried the sideload method from this thread. No luck here as well. I got the 12.0.0 (SQ1D.220105.007, Jan 2022) update from the OTA link (Not sure if thats the right one but its the only one available that says JAN 2022) and when i get to the recovery i adb sideload drag file, the file uploads and fails with the following error > error applying update 7 kinstalldeviceopenerror
From googling that error it says that im trying to upload an update meant for another phone. Im sure that im downloading the "raven" one for the pro model.

Any advice would be helpful since i have been scratching my head for the last 6 hours.

A bit more info >
im using the same PC, usb cable, usb port that i used when rooting for the first time.
I rooted the phone following this thread without disabling Android Verified Boot since it said its not needed.
I have the Canary Magisk 23016. Disabled all modules and super rights to apps before trying both methods of update.
Im using the "Tiny ADB & Fastboot" to upload the update to the phone.
Its have not done any previous updates on this phone, rooting was done on Nov update since it came with it.

Extra question > Somebody posted that they had similar problem to mine and they updated with the <Update and Root Factory Image>. (1)If i try that will the phone revert to factory settings and (2) can i use the master root.img that i saved from the first root or do i need to patch it again?

P.S. Thanks a lot for the original guide!
Hope the below helps you and anyone else in a similar spot as I just was in the last hour.

I just updated from Nov 2021 patch (SD1A.210817.036) to Jan 2022 patch (SQ1D.220105.007) using factory image method. I was previously rooted on the Nov 2021 build using community/alpha magisk. Below was what I did

1. Download the factory image zip for the .007 build and extract some where on machine (for me, Win10)
2. On phone (still on .036 build), Copy over the boot.img file to phone
3. Open magisk app (I installed canary 23016 over the previous alpha/community version from Nov when root was still in flux), Magisk -> Install -> Select and Patch a File -> Select boot.img you copied over (for the SQ1D.220105.007 build) and let it patch
4. Copy over the newly patched image file to some local machine. Make a copy and call it like master-boot.img
5. Reboot into bootloader
6. Update bootloader from bootloader image in .007 directory (bootloader-raven-slider-1.0-8013568.img); reboot into bootloader
7. Update radio from radio imagein .007 directory (radio-raven-g5123b-93368-211225-b-8029609.img); reboot into bootloader
8. Update the update zip (image-raven-sq1d.220105.007.zip); it went into fastbootd immediately for me, watch terminal to know when update is done. When done, reboot to bootloader
9. Boot into the master-boot.img made from step 3/4
10. Open magisk and do Magisk -> Install -> Direct Install
11. Once done rebooting, open Magisk app
12. Disable riru; Enable Zygisk in settings and configure denylist if applicable; hide magisk app; reboot
13. Install MagiskHide Props Config (6.1.2) and safetynet-fix (2.2.1) from GH links in first post; reboot

I am updated on the SQ1D.220105.007 build from the SD1A.210817.036 build, have persistent root, pass safetynet, and did not need to wipe phone (thank god lol).
Pretty much, on your current build, patch the SQ1D.220105.007 boot.img using updated magisk app, then follow the steps for factory image/safetynet.

Btw - I am on a carrier unlocked P6P, 256GB.
 
  • Like
Reactions: roirraW "edor" ehT

Az Biker

Sr. Mod / Mod & RC-RT Committees / Shred'r of MTBs
Staff member
Or don't use the script at all and learn the commands...but I'm old fashioned like that

Meh... erase two characters VS type in a bunch of characters from memory...

I'm taking the poor memory, lazy, fewer clicks equals more chicks route!

Remove the -w, live longerer and prosperer :p
 

Top Liked Posts

  • There are no posts matching your filters.
  • 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.
    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.
    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