• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[Guide] Root Pixel 4 XL Android 12

Search This thread

bradical711

Senior Member
Aug 26, 2017
434
268
Google Pixel 4 XL
Google Pixel 6
Thanks, I don't believe this to be the issue. with stock boot.img everything works fine. Its only when I flash a patched magisk boot.img.
What device do you have.? (EDIT NVM, I seen it's a 4 XL). Anyways since your device isn't a pixel 5a 5g or newer, you don't need alpha/canary magisk to root A12. I'm using the 4 XL rn with stable magisk (23000) on A12 November security patch. Try stable magisk since you're not on a pixel 5a or newer and report back. I also did an OTA from A11 to 12 without any issue. Same modules for me etc so it might be a magisk canary/alpha issue.
 
Last edited:

docluv01

Senior Member
Nov 23, 2010
356
34
What device do you have.? (EDIT NVM, I seen it's a 4 XL). Anyways since your device isn't a pixel 5a 5g or newer, you don't need alpha/canary magisk to root A12. I'm using the 4 XL rn with stable magisk (23000) on A12 November security patch. Try stable magisk since you're not on a pixel 5a or newer and report back. I also did an OTA from A11 to 12 without any issue. Same modules for me etc so it might be a magisk canary/alpha issue.
Thanks, I just tried it, and same thing. touchscreen is not responsive.

Looks Like im the only one with this problem :(
 

loonix

Senior Member
Jun 27, 2005
167
63
I am still on September update and looking to upgrade to Android 12 via a clean install. What are some good ways to do a backup of the apps+data+settings that folks are following? I am trying to avoid anything using the cloud/paid softwares. Had used Titanium Backup when I went from Android 10 to Android 11, so that is one option but looking for some other recommendations.

Thanks.
 

73sydney

Senior Member
Jul 21, 2018
1,995
1,799
Sydney
Google Pixel 2 XL
Samsung Galaxy S20
I am still on September update and looking to upgrade to Android 12 via a clean install. What are some good ways to do a backup of the apps+data+settings that folks are following? I am trying to avoid anything using the cloud/paid softwares. Had used Titanium Backup when I went from Android 10 to Android 11, so that is one option but looking for some other recommendations.

Thanks.

Migrate - its in my signature for a reason.

Its free, it works

Here is how i use it, its worked out to be the easiest way for me, across probably 100 ROM flashes by now, from 9 to 10 to 11 to 12 :) It will warn you it hasnt been tested on 12 when you go to restore, but it works 100% fine


Note: please never mention that awful piece of crud Titanium Backup ever again in my presence :)
 
  • Like
Reactions: loonix

loonix

Senior Member
Jun 27, 2005
167
63
Migrate - its in my signature for a reason.

Its free, it works

Here is how i use it, its worked out to be the easiest way for me, across probably 100 ROM flashes by now, from 9 to 10 to 11 to 12 :) It will warn you it hasnt been tested on 12 when you go to restore, but it works 100% fine


Note: please never mention that awful piece of crud Titanium Backup ever again in my presence :)

I am glad I asked for current recommendations ! Thanks for the suggestion. I am going to follow your guide but just posting it here in case others also find the big thread linked in your signature a little daunting.


I think for us in P4XL, since we don't have TWRP we will need all the three apps -> Main, Flasher and Helper.
 

smithilberry

Senior Member
FYI, I have my Pixel 4 XL (Google Store/Unlocked version) on Nov 2021 patch without any issues
(using Magisk 23.0, passing SafteyNet, & GPay working)

All I did is the "regular method" of updating, which I define as...
1. download factory image and remove -w from flash-all
2. extract boot img from zip
3. move boot img to phone and patch with magisk manager (Magisk 23.0)
4. move magisk boot img to PC
5. flash update Code: flash-all
6. flash magisk Code: fastboot flash boot magisk_patched.img
7. reboot and enjoy

Oh, and modules I have installed for Magisk are:
Busbox 1.34.1
Riru v26.1.3
Universal SafetyNet Fix 2.1.1
 
  • Like
Reactions: ShanxRoux

loonix

Senior Member
Jun 27, 2005
167
63
FYI, I have my Pixel 4 XL (Google Store/Unlocked version) on Nov 2021 patch without any issues
(using Magisk 23.0, passing SafteyNet, & GPay working)

All I did is the "regular method" of updating, which I define as...
1. download factory image and remove -w from flash-all
2. extract boot img from zip
3. move boot img to phone and patch with magisk manager (Magisk 23.0)
4. move magisk boot img to PC
5. flash update Code: flash-all
6. flash magisk Code: fastboot flash boot magisk_patched.img
7. reboot and enjoy

Oh, and modules I have installed for Magisk are:
Busbox 1.34.1
Riru v26.1.3
Universal SafetyNet Fix 2.1.1

I have been doing the exact same steps until September update. From October I think it is now Android 12 and I just want to do a clean install(without removing -w). If you updated in October then this is exactly what I would follow too.
 

loonix

Senior Member
Jun 27, 2005
167
63
Update: I have P6 Pro coming soon so decided to go skip clean upgrade to Android 12 as I didn't want to go through too much trouble in case it arises. I did backup via the Migrate app just in case however (flash method selected during backup, not TWRP)

Ended up dirty flashing from September Android 11 update to November Android 12 upgrade. Everything appears to be running fine after an hour of use.

Also forgot to mention that while I do follow the same steps as @smithilberry , I always have added a reboot between step 5 and 6. In the past I had a bootloop one time when not doing this step and it forever changed my update method.

Essentially

1. download factory image and remove -w from flash-all
2. extract boot img from zip
3. move boot img to phone and patch with magisk manager (Magisk 23.0)
4. move magisk boot img to PC
5. flash update Code: flash-all
6. REBOOT -> Let the system update finish after you are logged in one time without root.
7. flash magisk Code(Reboot to bootloader first after 6 completes) : fastboot flash boot magisk_patched.img
8. reboot and enjoy
 

Homeboy76

Senior Member
Aug 24, 2012
2,877
1,495
Google Pixel XL
Update: I have P6 Pro coming soon so decided to go skip clean upgrade to Android 12 as I didn't want to go through too much trouble in case it arises. I did backup via the Migrate app just in case however (flash method selected during backup, not TWRP)

Ended up dirty flashing from September Android 11 update to November Android 12 upgrade. Everything appears to be running fine after an hour of use.

Also forgot to mention that while I do follow the same steps as @smithilberry , I always have added a reboot between step 5 and 6. In the past I had a bootloop one time when not doing this step and it forever changed my update method.

Essentially

1. download factory image and remove -w from flash-all
2. extract boot img from zip
3. move boot img to phone and patch with magisk manager (Magisk 23.0)
4. move magisk boot img to PC
5. flash update Code: flash-all
6. REBOOT -> Let the system update finish after you are logged in one time without root.
7. flash magisk Code(Reboot to bootloader first after 6 completes) : fastboot flash boot magisk_patched.img
8. reboot and enjoy
One, there is a Google Pixel 6 Pro | XDA forum that could benefit from your Pixel 6 Pro experiences.
Two, that factory image flashing procedure is in the OP, #4 'keep data' :)
 
Last edited:
  • Like
Reactions: loonix

loonix

Senior Member
Jun 27, 2005
167
63
One, there is a Google Pixel 6 Pro | XDA forum that could benefit from your Pixel 6 Pro experiences.
Two, that factory image flashing procedure is in the OP, #4 'keep data' :)

I understand :) Just wanted to give a datapoint where a dirty upgrade also has gone through fine (after making sure backups are in place just in case). I am very much a proponent of clean major version upgrades in the past. Your sticky has been the backbone for last couple of years of upgrades and I am very thankful. Sorry if that is not stated explicitly. It is implied, just not stated verbose.

Looking forward to retiring P4XL and hopping on the P6 Pro forum soon.
 

loonix

Senior Member
Jun 27, 2005
167
63
For those on latest Canary 23014 (Zygisk with GPay added to deny list),to pass safetynet and enable contactless payments

1) Clear data for both GPay and Google Play Services. Unfortunately this also meant adding cards back in GPay app (basically reverify already added cards in your GPay profile)

2) Apply SafetyNet fix 2.2.0 (latest).

On the bright side no longer need Riru, Riru core, LSPosed etc. etc. Just SNF 2.2.0 + Systemless hosts like old times.
 
Last edited:

crypt0kiddie

Senior Member
Jun 23, 2010
791
99
For the love of God Android 12 was painful.

I tried, I really tried. I kept having Windows Millennium Edition flashbacks the user experience was SO BAD!

Waiting for my phone to boot back into Windows 98 SE, er I mean Android 11 now.
 

madmuthertrucker

Senior Member
Jan 4, 2013
198
77
Tucson, Az
Well I just re rooted the update with Magisk 23.0, Riru, and USNF 2.1.1. I figured it's not broke maybe I shouldn't fix it. It won't work forever, I suppose, I will have to get Zygist and join the future. Next time.
 
  • Like
Reactions: Homeboy76

Top Liked Posts

  • 1
    Update!
    Magisk Canary 23017
  • 2
    :) I hope you all have a Joyful Holiday season with your family and loves ones. :)

    ~ ~ ~ Stay safe ~ ~ ~
    1
    I got GPay working! Here is how.

    Clear the cache and data for Google Play services, Google Play Store, and GPay. After which, I removed and reinstalled Google Pay and then added the payment method back in.

    I had done this originally but not the uninstall & reinstall. That's what did it.
    1
    Update!
    Magisk Canary 23017
  • 9
    [Guide] Root Pixel 4 XL Android 12 Unlock/Lock Bootloader + Systemless ROOT
    Android Security Bulletin—January 2022
    Pixel Update Bulletin—January 2022

    Introduction
    This Guide is for Pixel 4 XL owners that want to Root their phone, and enjoy the benefits of rooting it without installing a Custom ROM. However, for those that just can't live without a Custom ROM, take a look at 'Custom ROMs for Pixel 4 XL'.

    NEW
    1. The differences between the different variants of Magisk
    2. Magisk Alpha (vvb2060)
    3. Magisk Modules for Magisk Alpha/Canary

    Update(s)
    1. Factory/OTA Images - 04Jan
    2. Magisk Stable - Magisk-23.0 05Dec
    3. Magisk Beta - Magisk-23.0 05Dec
    4. Magisk Canary - Magisk-23017 20Jan
    5. TWRP - Waiting for T.R.W.P. for Android 12
    6. SafetyNet - SafetyNetFix v2.1.3 (Riru) v2.2.1 (Zygisk) 22Dec
    7. SDK Platform-tools - r31.0.3 18Aug
    8. Custom Kernels
      • Kirisakura v8.0.3 10Jan
      • ElementalX - Check ElmentalX Kernel Manager for Updates
      • CleanSlate R2.7.13/S3.8.2 08Jan
    9. Custom ROMs

    Disclaimer
    1. I assume no responsibility for the malfunctioning/bricking of your phone.
    2. The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item.

    Prerequisites
    1. A Pixel 4 XL phone with an unlocked bootloader.
    2. The latest Android 12 Factory or OTA Image: "coral" for Pixel 4 XL

      Factory Image

      OTA Image
    3. A Computer with the latest SDK Platform-Tools: r31.0.3 installed.
    4. Important Notes:

    My Other Guides

    Credits/Thanks/Recognitions
    1. bradical711 - Instructions to Pass Safety Net
    2. Those I may have, inadvertently, forgotten.

    Index
    (NOTE: Numbers 1-11 are not steps, they are individual sets of instructions).
    1. Open a Command Prompt/Boot Fastboot Mode/Boot Recovery

      • Open a Command Prompt on Computer
        1. Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type cmd and press enter.
        2. Open a Powershell Command Prompt on Computer: Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type powershell and press enter.
        3. Notes:
          • Enable USB Debugging, on your phone: Settings ==> System ==> Advanced ==> Developer options ==> Scroll down to USB debugging and enable it.
          • When using the Powershell Command Prompt Commands must be preceeded with ./: i.e, ./fastboot devices
          • If you do not want to open a Command Prompt every time you want to use the fastboot command, add the path to the Platform-tools folder to Windows environment variables.
      • Boot fastboot mode (bootloader):
        • Power off phone, press and hold the power and volume down buttons until you see Start.
      • Boot Recovery
        • Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.
    2. Test fastboot

      • Enable Developer Options - Tap Settings > About phone > Build number 7 times or until you should see 'you are a Developer'.
      • Enable USB Debugging - Tap Settings > System > Advanced > Developer options >
        Enable USB Debugging.
      • Open a Command Prompt on your computer in the Platform-tools folder.
      • Boot fastboot mode on your phone (#1)
      • Connect the phone to the Computer.
      • At the prompt type: fastboot devices to verify communication with phone. It should return your phone's serial number.
    3. Unlock Bootloader/Return Phone to Stock/Lock Bootloader

      • Unlock Bootloader

        1. This will erase all user data from the device!
        2. Backup your data
        3. Activate Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer. Tap back > System > Advanced > Developer Options. Enable OEM Unlock and, USB Debugging.
        4. Boot fastboot mode
        5. Connect the phone to the Computer with USB cord.
        6. Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
        7. You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
        8. Allow the process to complete and then type fastboot reboot at the Command Prompt and press enter.
        9. When your phone reboots disconnect your usb cable.
          Notes: After unlocking your bootloader, you'll see a warning: The bootloader is unlocked and... You will see this warning until, you relock the bootloader.
          Do not relock your bootloader until you have returned the device to Stock.
      • Return Phone to Stock

        1. Backup your data/Internal storage
        2. Settings > System > Advanced > Reset Options > Erase all data (factory reset)
        3. Log in
        4. Set up phone
      • Lock Bootloader

        1. Return the phone to Stock before locking the bootloader, failure to do so could brick your phone
        2. This will erase all user data from the device!
        3. Boot fastboot mode
        4. Open a Command Prompt and type this at the Prompt: fastboot flashing lock
        5. You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
        6. Allow the process to complete, then type this at the Command Prompt: fastboot reboot
        7. Enable Developer Options: Settings > About phone > Tap Build number 7 times or until you see 'you are a developer'.
        8. Tap Back > Developer options and toggle OEM Unlock off.
    4. Install/Update Factory Image keep data or wipe data

      • Important Note(s):
        1. When doing a major upgrade i.e., Android 11 to Android 12: I recommend doing a clean install. What is a clean install?
          • Doing a Factory reset prior to installing, major, update.
          • Using flash-all.bat file without removing the -w (#4. Wipe Data).
        2. Always verify you have the latest version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 4XL - coral.
        3. If your phone was rooted, and you want to 'Keep Data'. Do this first open Magisk ==> unhide Magisk App (if you hid it) ==> Disable/Remove all modules ==> then Uninstall Magisk - Restore images prior flashing the Factory image. Why? The changes in the New factory image may cause Magisk modules to fail. This will cause boot loops. Additionally, before Enabling/Installing the modules you Disabled/Removed check with the Dev of the module to ensure it was updated to work with the latest factory image.
        4. If you get an error while flashing, try one of these options:
          • Change the USB port to a non charging USB port.
          • Change the USB cord.
          • Change Computers.
        5. Backup your data
        6. Download the latest Factory Image: Pixel 4XL - coral to your Computer.
        7. Extract the factory Image to a folder.
      • Flash Factory Image Keep Data

        • Open the folder you extracted the Factory Image to and Edit the flash-all.bat file with a file editor i.e., Notepad. Remove the -w from this command: fastboot -w update image-coral-aa9a.999999.999.zip
          Note: If you do not remove the -w your data and internal storage will be wiped.[/B]
        • After, you have edited the flash-all.bat file. Copy/Move these files to the Platform-tools folder:
          1. bootloader-coral-....img
          2. flash-all.bat
          3. image-coral-....zip
          4. radio-coral-....img
        • Open a Command Prompt on your computer in the Platform-tools and type: flash-all at the Command Prompt and press enter.
        • System will reboot when flashing is complete.
        • Do #7 to root/reroot.
      • Flash Factory Image Wipe Data

        • This will wipe your phones Internal Storage.
        • Open the folder you extracted the Factory Image to and Copy/Move these files to the Platform-tools folder:
          1. bootloader-coral-....img
          2. flash-all.bat
          3. image-coral-....zip
          4. radio-coral-....img
        • Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
        • The phone will reboot when flashing is complete.
        • Do #7 to root/reroot.
    5. ADB Sideload

    6. Extract/Flash boot.img

      • Extract boot.img

        1. Download the latest Factory image to your phone.
        2. Extract the Factory Image file (coral-RQ1A.999999.999-factory-99a9a99a.zip) to a folder.
        3. Open the folder and, extract the Image file (image-coral-aa9a.999999.999.zip) into the folder.
      • Flash boot.img

        1. Flashing the boot.img removes root.
        2. Open the folder you extracted the 'image...zip' file to and copy the boot.img file to your computer's platform-tools folder or to the folder that has fastboot.exe in it.
        3. Boot fastboot mode
        4. Connect the phone to the Computer
        5. Open a Command Prompt and type the following command at the prompt:
          fastboot flash boot --slot all boot.img
        6. Reboot
    7. Root/Reroot with Magisk and Pass SafetyNet.

      • Important Note(s):

        1. When doing a major upgrade i.e., Android 11 to Android 12: I recommend doing a clean install. What is a clean install?
          • Doing a Factory reset prior to installing, major, update.
          • Using flash-all.bat file without removing the -w.
        2. If your phone was rooted. Do this first unhide Magisk App (if you hid it) then Uninstall Magisk - Restore Images. Why? The changes in the Factory image may cause Magisk modules to fail. This will cause boot loops.
      • Download files:

        1. Magisk App - Download to your phone
          1. Magisk Beta/Stable App
          2. Magisk Canary App
        2. Custom kernels - Download to your phone - install with Kernel Manager
          • Important Note(s): Unless otherwise directed by Kernel Devloper, Flash the Kernel after Magisk.
          1. ElementalX see EXKM for updates.
          2. [[KERNEL] CleanSlate R2.7.13/S3.8.2 |S2S|Gamma|KCal|AdBlock|VIB|WrGrd [Jan 8] by tbalden
          3. [Kernel][10.01.2022][4.14.261][A12] Kirisakura 8.0.3 for Pixel 4/XL aka FLORAL by Freak07
        3. Kernel Manager - Download to your phone
      • Patching the boot.img - to root/reroot.

        1. Do #6 - Extract boot.img
        2. Install Magisk Canary
          Note: Tap 3 dot menu across from canary => Tap Go to file => Download, app-debug.apk
        3. Open Magisk Canary App
        4. Set the Update Channel Canary.
        5. Tap Install (next to Magisk)
        6. Tap, Select and Patch a File
        7. Select the boot.img file you extracted from the latest factory image.
        8. Tap the ✓ (Check Mark)
        9. Tap Let's Go
        10. When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.
        11. Reboot
        12. Copy the patched boot.img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it.
        13. Boot fastboot mode
        14. Connect the phone to the Computer with USB cord.
        15. Open a Command Prompt in the folder you copied the patched boot.img to.
        16. Type fastboot flash boot "name of patched boot".img without the quote marks at the Prompt and press enter.
        17. Type fastboot reboot at the Prompt and press enter.
        18. Important Notes: If your phone boot loops try one of the following options:
          • Flash the 'stock' boot.img to both slots: fastboot flash boot boot.img --slot all
          • Boot Safe Mode - Press Power Off button ==> Press Power Off until you see boot Safe Mode ==> Press Ok.
      • Pass Safety Net with SafetyNet Fix 2.2.1

        1. Download File(s)
        2. Install SafetyNet Fix 2.2.1
          • Open Magisk
          • Tap Modules icon
          • Tap Install from storage
          • Navigate to the SafetyNetFix file you downloaded
          • Tap the SafetyNetFix file
          • Tap the check mark (✓ at the bottom) to start the installation.
          • After it installs tap the Save icon to save the log
          • Tap Reboot.
        3. Settings for Magisk Canary
          • Open Magisk App
          • Tap the Setup icon.
          • Scroll down to App and set the Update Channel to Canary.
          • Scroll down to Check Updates and enable it.
          • Scroll down to Magisk and enable Zygisk and Enforce DenyList.
          • Tap Configure DenyList => Tap 3 Dot Menu => Check ✓ Show system apps => Check ✓ Google Play Store, Google Pay, etc.
          • Scroll down to Superuser and enable Enable Biometric Authentication.
        4. Get Device Certified Clear Google Play Services, Google Play Store, Google Pay, etc. data
          • Turn Airplane mode on
          • Open Settings
          • Tap Apps & notifications
          • Tap see all...
          • Tap three dot menu
          • Tap Show system
          • Scroll down to Google Play Store
          • Tap Storage and Cache
          • Tap Clear storage
            Note: Repeat the 3 steps above for Google Play Services, Google Pay, etc.
          • reboot
          • Turn Airplane mode off
        5. Check Device Certification
          • Open Google Play Store app
          • Tap Menu - Circle top right
          • Tap Settings
          • Tap About
          • Check Play protect certification.
    8. Set Magisk App Update Channel/Update Magisk

      • Set Magisk App Update Channel

        • Open Magisk App > Tap Settings icon > Update Channel > Select Stable, Beta, Canary or Custom.
      • Update Magisk

        1. When Magisk App notifies you of an update:
        2. Tap install.
        3. Select, Direct Install (Recommended)
        4. When it finishes installing
        5. Tap, Save Log
        6. Log location: /storage/emulated/0/Download
        7. Tap, Reboot
        8. Done!
    9. Custom ROMs

      • Need help with a Custom ROM?

        1. Read and follow the Installation Instructions. The installation instructions are in the OP of the Custom ROM thread.
        2. If you have a problem Installing the ROM, Search the thread of the Custom ROM you are trying to install for a solution to problem: If you don't find a solution post your request for help in the thread.
      • ROMs

        1. Alpha/Beta

          • None
        2. Official
        3. Unofficial

          • None
    10. Apps/Mods/Scripts/Tethering/Themes
    11. T.W.R.P. Backup/Restore

      • Android 12 T.W.R.P.
    4
    @Homeboy76 Just wanted to give you a heads up. With the latest Magisk Beta (21.2) that came out yesterday, the patched output file is no longer named "magisk_patched.img". He added a suffix to the name so each time you patch the stock boot image a different output name will result. Thought you might want to modify #7 to address this change (y)
    3
    For those on latest Canary 23014 (Zygisk with GPay added to deny list),to pass safetynet and enable contactless payments

    1) Clear data for both GPay and Google Play Services. Unfortunately this also meant adding cards back in GPay app (basically reverify already added cards in your GPay profile)

    2) Apply SafetyNet fix 2.2.0 (latest).

    On the bright side no longer need Riru, Riru core, LSPosed etc. etc. Just SNF 2.2.0 + Systemless hosts like old times.
    3
    Is rooting Android 12 with stable magisk actually possible? or do i need the beta or canary version?
    Yes, it's fine. I've been using Stable version 23.0 since the first beta was released and am currently using it on yesterdays official release of Android 12 stable. Everything is fine for me.

    People on other Pixels, specifically the Pixel 5 (and maybe others) have reported that they have to disable dm-verity (and maybe another thing or two) before rooting or it will just land you in the bootloader when trying to boot. However, on my Pixel 4 XL I did not have to do anything. Just patched the boot image as usual and everything is fine for me.

    Of course, your mileage may vary.
    3
    So, I've been out of the flashing game for a long minute but I had to do something about all the ads I was getting. Blockada seemed to work okay but always left something to be desired. I missed Adaway, so....

    I had a hard time getting Magisk installed in Android 11 on my Pixel 4xl. I followed this well written tutorial to a tee but when I flashed magisk_patched.img to boot, then "fastboot reboot," it would kick me back to fastboot after the "G" screen and spit out the error "no valid slot to boot." Three times in a row after clean flashing the factory image too!

    I did end up getting it working. What I ended up doing was instead of "fastboot flash boot magisk_patched.img --slot all" I "fastboot flash boot magisk_patched.img" and for whatever reason that seemed to work.

    I did not take the OTA update if it matters. I had intended to wipe the device with a clean install of Android 11, then Magisk (just for ad blocker) from the get so, I'm guessing slot b wasn't used? I'm honestly not really sure how it works.

    Even then though, I had some trouble getting the order right from flashing the factory image to being rooted, so this is also what I found.

    First, unlock the bootloader of your device, then clean install Android 11 and get it set up. Download Magisk manager canary, then adb push the boot.img from your computer to your device. Use Magisk manager to patch it, then adb pull magisk_patched.img back to your computer. From there, fastboot flash boot your magisk_patched.img and you're golden. Fastboot reboot should put you back in to Android and then Magisk manager will recognize root.

    I had tried several times to use a boot.img I had already patched some days earlier but it never seemed to work. It would boot okay, once I figured out not to "--slot all," but Magisk would never recognize it was rooted unless Magisk manager patched it and I flashed that particular patched file. If I tried to flash any other patched file, Magisk manager wouldn't recognize root. Even recently patched boot.img's that were flashed to the device (not the days old one I had pre-prepped) wouldn't work. Magisk manager only seemed to recognize patched boot.img's that were made by it in that particular install. If I tried to use a boot.img from any other Magisk Manager install it wouldn't recognize it. Weird? I dunno, but, I got it up and running!

    Thanks Homeboy76 for making this tutorial. Without it I would have been lost. :good: