[Guide] Root Pixel 4 XL with Magisk Android 12.1

Search This thread

dogeen

New member
Jan 2, 2022
4
2
First "oh no did I brick my device?" post of the year!

I was on Android 11 with an unlocked bootloader, magisk root on the stock rom, and tried doing a clean install, without the "Magisk Restore Images" step, because Magisk hadn't backed them up, and found myself with a device that doesn't have WIFI or mobile. Luckily, I had a backup of my persist.img, but my phone doesn't appear to like that persist.img anymore.

Note: I had modified my modemst1 because my device is from US and the Turkish government wanted me to pay ~$300 to not block it, so I changed my IMEI for the Turkish line to the IMEI of an old phone that belonged to a relative, and kept my US line with the original IMEI.

Here is what I tried:
- Right when Android 12 booted for the first time, mobile was gone, but WIFI was just flaky. It listed the networks and even started downloading my backup. That was followed by a boot loop, which may have been because of a button issue. I followed the instructions for flashing boot.img with --slot all. Again, WIFI was only flaky but after a few reboots it was gone entirely.

- Reflashed the stock 12 several times, didn't help.

- Reflashed the stock 11 version I was on, didn't help.

- fastboot erase/flash persist consistently fails with "Not allowed to flash" and "Not allowed to persist" even when I have root. This is very strange.

- dd if=<persist.img path> of=/dev/block/sda2 - seems to work but doesn't fix anything. Attempting to turn on the WIFI makes the UI unresponsive.

- Installed TWERP hoping it would provide a way to flash the persist.img but didn't really help. But it showed the persist partition size to be 0 bytes, which was a very interesting finding, confirming the persist partition corruption.

3 questions:
- Am I not flashing my persist.img correctly? If so, why not? I had backed it up with dd.
- I am guessing I might have to start looking for a Pixel 4XL persist.img, but where do I look for that? I am guessing all Pixel 4XLs have the same but the stock image downloads don't come with the persist.img for some reason.
- Is there anything else I should do?
 

madmuthertrucker

Senior Member
Jan 4, 2013
202
78
Tucson, Az
Are you guys getting GPay working? I installed the Jan update and switched to magisk canary with safety net 2.2.1. I passed safety net, device is certified, banking apps all good. I denied Play store, Gpay, and Play Services. I noticed that Play services unchecks after reboot. Where am I going wrong? I'm not finding any recent info.
 

madmuthertrucker

Senior Member
Jan 4, 2013
202
78
Tucson, Az
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.
 
  • Like
Reactions: Homeboy76

pw1nce

Senior Member
Oct 12, 2013
403
36
mardan
First "oh no did I brick my device?" post of the year!

I was on Android 11 with an unlocked bootloader, magisk root on the stock rom, and tried doing a clean install, without the "Magisk Restore Images" step, because Magisk hadn't backed them up, and found myself with a device that doesn't have WIFI or mobile. Luckily, I had a backup of my persist.img, but my phone doesn't appear to like that persist.img anymore.

Note: I had modified my modemst1 because my device is from US and the Turkish government wanted me to pay ~$300 to not block it, so I changed my IMEI for the Turkish line to the IMEI of an old phone that belonged to a relative, and kept my US line with the original IMEI.

Here is what I tried:
- Right when Android 12 booted for the first time, mobile was gone, but WIFI was just flaky. It listed the networks and even started downloading my backup. That was followed by a boot loop, which may have been because of a button issue. I followed the instructions for flashing boot.img with --slot all. Again, WIFI was only flaky but after a few reboots it was gone entirely.

- Reflashed the stock 12 several times, didn't help.

- Reflashed the stock 11 version I was on, didn't help.

- fastboot erase/flash persist consistently fails with "Not allowed to flash" and "Not allowed to persist" even when I have root. This is very strange.

- dd if=<persist.img path> of=/dev/block/sda2 - seems to work but doesn't fix anything. Attempting to turn on the WIFI makes the UI unresponsive.

- Installed TWERP hoping it would provide a way to flash the persist.img but didn't really help. But it showed the persist partition size to be 0 bytes, which was a very interesting finding, confirming the persist partition corruption.

3 questions:
- Am I not flashing my persist.img correctly? If so, why not? I had backed it up with dd.
- I am guessing I might have to start looking for a Pixel 4XL persist.img, but where do I look for that? I am guessing all Pixel 4XLs have the same but the stock image downloads don't come with the persist.img for some reason.
- Is there anything else I should do?
Hi there, I understand your situation and I'm kind of in the same boat. Though I've figured out to fix the wifi and system ui crashing. I guess need some help from you though because we also have that stupid govt tax system. I'll send you a Private message and we can try to figure it out. Text me asap. Thanks
 

Lughnasadh

Senior Member
Mar 23, 2015
3,327
3,294
Google Nexus 5
Huawei Nexus 6P
Now that Magisk no longer can be installed on inactive slot, does that mean I can no longer apply OTA and maintain root? There is new OTA Android 12 QPR3 Beta 1 and I want to know if is there a way to apply it.
The option to install via inactive slot was re-introduced into Magisk with version 24.0. You should have that option again on the latest Canary, Beta and Stable versions.
 

fivefour

Senior Member
Jun 7, 2010
756
1,333
Emerald Coast
bit.ly
Could someone please share the boot image for 12 (SP2A.220305.012)?

*EDIT*
I got it from the full update zip from the OP, thank you @Homeboy76 for this thread. The OP should have far more likes...
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Thanks a lot guys. I just got the phone today and I don't think I've installed any modules. I will try the adb push method. Thank you 🙂
    2
    Hi guys, my phone is bootlooping when I am trying to root through the latest Magisk Canary app, (tried the stable magisk version and it didn't work either). If I flash the stock boot image, the phone loops into the system just fine.

    I am using the latest platform tools(33.0.1) and my active boot slot is 'b'. I am on (SP2A.220405.004, Apr 2022) build.

    Could someone post a video or detailed instructions on rooting through OTA? I have no clue how to do it?

    If there is any other method also, I'd be willing to try. Please help me!
    In addition to what others have said....It sounds like you are rooting this phone for the 1st time? But in case you are not, make sure that any Magisk modules you may have installed that need updating are disabled.

    Also, @badabing2003 makes a good point about file transferring. John Wu even recommends using the adb push method in his instructions because sometimes using the native file transfer can corrupt a boot image.
    1
    quick question maybe you guys can help me w/ - it's been a while since I rooted my pixel 4xl. When I download the platforms-tools zip file - do I use it as-is or do I need to unzip it?
    you need to unzip it, OP has instructions on what to do with it.
    1
    Ok, at least you are rooted.

    I just downloaded Magisk Canary 24308
    Note: Tap app-debug.apk -> Tap 3 dots across from 17.MB-> Tap downloadI
    That did download. It seems like stable is working though. Like you said I'm rooted. Should I unhide Magisk before updating in the future? I appreciate your help, and the guide. Even GPay is working. It's always a struggle but I guess that's what makes it fun. At least a challenge.
    1
    That did download. It seems like stable is working though. Like you said I'm rooted. Should I unhide Magisk before updating in the future? I appreciate your help, and the guide. Even GPay is working. It's always a struggle but I guess that's what makes it fun. At least a challenge.
    I think it is sensible to unhide Magisk before updating it in the future.
  • 14
    [Guide] Root Pixel 4 XL With Magisk Android 12.1
    Android Security Bulletin—May 2022
    Pixel Update Bulletin—May 2022

    Introduction
    This Guide is for Pixel 4 XL owners that want to Root their phone, and enjoy the benefits of rooting it. The Guide is divided into three parts: Information, Instructions, and Other.

    ~ ~ ~ Part I - INFORMATION ~ ~ ~
    1. 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.
    2. 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: r33.0.1 installed.
      4. Important Notes:
    3. NEW
    4. Update(s)

      1. Factory/OTA Images - 02May
      2. Magisk Alpha - 71e9c044-alpha 06May
      3. Magisk Beta - 24.3 10Mar
      4. Magisk Canary - (756d8356) (24312) 15May
      5. Magisk Stable - 24.3 10Mar
      6. TWRP - Waiting for T.R.W.P. for Android 12
      7. SafetyNet - SafetyNetFix v2.1.3 (Riru) v2.2.1 (Zygisk) 22Dec
      8. SDK Platform-tools - r33.0.1 06Apr
      9. Custom Kernels
        • Note: If you are using a Custom Kernel, please update using the method in the OP, Index, 4. Install/Update Factory Image keep data or wipe data, • Flash Factory Image Keep Data
        • Kirisakura v8.0.5 09Mar
        • ElementalX - Check ElmentalX Kernel Manager for Updates
        • CleanSlate R2.7.13/S3.9.3 03May
      10. Custom ROMs
        • [OFFICIAL] LineageOS 19.1 for the Google Pixel 4 XL 25Apr
        • [12.0] Descendant 05May
        • [12.0] PixelExperience [AOSP]
    5. My Other Guides
    6. Credits/Thanks/Recognitions

      1. bradical711 - Instructions to Pass Safety Net
      2. Those I may have, inadvertently, forgotten.
    ~ ~ ~ Part II - INSTRUCTION ~ ~ ~
    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 Android 12 (12.0.0) to Android 12.1 (12.1.0), I recommend doing a Clean Install: Do Flash Factory Image Wipe Data (below).
        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.
        • 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
        • On your phone: Boot the bootloader (Power off the phone => Press the Power and Down buttons until you see Start)
        • Connect your phone to the computer.
        • 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 #8 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
        • On your phone: Boot the bootloader (Power off the phone => Press the Power and Down buttons until you see Start)
        • Connect your phone to the computer.
        • 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 #8 to Root/Reroot.
    5. Take the OTA Update and Maintain Root

      • All the credit for this set of instructions goes to @topjohnwu for writing the instructions: Install Magisk to Inactive Slot , use Magisk Beta, Stable 24.3.
      • NOTE: If you had a Custom Kernel installed, after you Open Magisk and Restore Images. Do the following to return your phone to Stock:
        • fastboot flash dtbo dtbo.img
        • fastboot flash vendor_boot vendor_boot.img
        • There may be more .img files you need to flash. Please check the OP of the Custom Kernel thread you install for instruction to remove the Custom Kernel and return your phone to Stock. Additionally, if you installed Mods Please check the OP of the Mod thread you installed for instruction to remove the Mod and return your phone to Stock before you download the OTA.
      • If you phone bootloops
        • force Safe Mode by continually pressing volume down button during boot animation.
        • After the system boots into safe mode you can reboot your device to boot up normally (since all modules will be disabled).
        • Thanks @Typhus_ for the instructions to force Safe Mode.
    6. ADB Sideload

    7. 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/move 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
    8. 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 - Under Downloads
          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.9.3 |S2S|Gamma|KCal|AdBlock|VIB|WrGrd [3May] by tbalden
          3. [Kernel][09.03.2022][4.14.265][A12][A13] Kirisakura 8.0.5 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
          or
          Magisk 24.1 Beta/Stable App - Under Downloads
        3. Open Magisk Beta/Canary/Stable App
        4. Set the Update Channel Beta/Canary/Stable.
        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/Move the patched boot.img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it:
          • Copy it to a USB drive and transfer it to your computer.
          • Move it to your computer using adb push
        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.
    9. 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!
    10. Install/Update Magisk Modules

      • Download Modules
      • Install Modules

        1. Open Magisk
        2. Tap the Modules icon
        3. Tap Install from storage
        4. Navigate to the folder with the Module you want to install.
        5. Tap the Module to highlite it and tap Select.
        6. After it installs, tap the Disc Icon to save the install log.
        7. Tap Reboot
      • Update Modules

        1. Open Magisk
        2. Tap the Modules icon
        3. You, will see the Modules that have Updates.
        4. Tap the Module you want to update.
        5. Tap install.
        6. After it installs, tap the Disc Icon to save the install log.
        7. Tap Reboot
    ~ ~ ~ Part III - OTHER ~ ~ ~
    1. Custom ROMs

    2. Mods
    3. 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: