How To Guide [Guide] Root Pixel 6 with Magisk, Android 12.1

Search This thread

Binary Assault

Senior Member
May 25, 2016
466
109
OnePlus 8 Pro
Google Pixel 6
when I asked did you patch the May 2022 boot.img with Magisk Canary 24306.

I meant did you download the Magisk Canary 240306 App, Install it and patch the stock bootimg from the May 2022 factory image.

If you did that it is not possible for magisk to be installing with modules.

My guess is you flashed the May 2022 OTA image without disabling/removing the Magisk modules and uninstalling Magisk.

Suggestion
After, you've remove the modules, backup your data, dirty flash the May 2022 factory image, and patch the stock boot.img with Magisk Canary 24306 and flash it to root.
I'll give it a whirl. Thanks
From the FAQ:

magisk --remove-modules from an adb shell should do it.
Thank you
 

Jammo2k5

Member
Mar 24, 2016
13
1
Hey quick question. Is there a reason why step 16 of Root/Re-root is Flash the boot image directly and not use
Code:
fastboot boot magisk_patched-{XXXX}.img
and then using magisk manager to install magisk directly?

The benefits i see with this method are:
1. If the boot.img is bad it will fail to boot without flashing and wont brick the device.
2. the stock images are backed up by magisk using this install method which allows for restoring and OTA updates using the device only without any extra steps.

This is the method I used to re-root after the may update because I flashed the boot image directly when I rooted last month.
 

Homeboy76

Senior Member
Aug 24, 2012
3,224
1,773
Google Pixel XL
Hey quick question. Is there a reason why step 16 of Root/Re-root is Flash the boot image directly and not use
Code:
fastboot boot magisk_patched-{XXXX}.img
and then using magisk manager to install magisk directly?

The benefits i see with this method are:
1. If the boot.img is bad it will fail to boot without flashing and wont brick the device.
2. the stock images are backed up by magisk using this install method which allows for restoring and OTA updates using the device only without any extra steps.

This is the method I used to re-root after the may update because I flashed the boot image directly when I rooted last month.
The step 16 you are referring to in the OP actually starts in the OP , ~~~ Part II Instructions ~~~, 2. Install/Update Factory Image keep data or wipe data,
Flash Factory Image Keep Data or Flash Factory Image Wipe Data, • Go-to Part II - INSTRUCTIONS => 5. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.

I've never read of one instant of a Google Pixel phone that was bricked because they used fastboot flash boot magisk_patched-....img.

Yes, the phones have boot looped.

Why did the phone boot loop instead of booting to the OS?
The main reason the phones were boot looping instead of booting the OS is the Magisk modules were not disabled/removed before pataching the boot.img.

One way to stop the boot looping is flashing the stock boot.img to both slots.

"2. the stock images are backed up by magisk using this install method which allows for restoring and OTA updates using the d
evice only without any extra steps."

Are you saying flashing the patched Magisk boot.img with fastboot flash boot magisk_patched-....img will not back up the stock boot.img so it can be restored?
 
  • Like
Reactions: Slim2none4u

Jammo2k5

Member
Mar 24, 2016
13
1
The step 16 you are referring to in the OP actually starts in the OP , ~~~ Part II Instructions ~~~, 2. Install/Update Factory Image keep data or wipe data,
Flash Factory Image Keep Data or Flash Factory Image Wipe Data, • Go-to Part II - INSTRUCTIONS => 5. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.

I've never read of one instant of a Google Pixel phone that was bricked because they used fastboot flash boot magisk_patched-....img.

Yes, the phones have boot looped.

Why did the phone boot loop instead of booting to the OS?
The main reason the phones were boot looping instead of booting the OS is the Magisk modules were not disabled/removed before pataching the boot.img.

One way to stop the boot looping is flashing the stock boot.img to both slots.

"2. the stock images are backed up by magisk using this install method which allows for restoring and OTA updates using the d
evice only without any extra steps."

Are you saying flashing the patched Magisk boot.img with fastboot flash boot magisk_patched-....img will not back up the stock boot.img so it can be restored?
With my recent attempts, once the device has boot looped so many times it will refuse to boot with a device corrupt message even if I flash the stock boot.img. I had to flash the entire ROM with the -flag disabled to recover the device.
Saying bricked was the wrong phrasing for that.

Secondly yes flashing the magisk boot image using fastboot will not allow magisk to backup the image as it has no access to it and it won't backup when you patch an image to regular storage.

However if you boot with the patched image using the fastboot boot command and then patch directly using the recommended option it will backup the images for restoration and will allow the ota method of restore, update, re magisk without reboot method to work.

Im asking if there is a reason why that shouldn't be done because I don't want to **** up my device because something happens in the background I am not seeing.
 

Homeboy76

Senior Member
Aug 24, 2012
3,224
1,773
Google Pixel XL
With my recent attempts, once the device has boot looped so many times it will refuse to boot with a device corrupt message even if I flash the stock boot.img. I had to flash the entire ROM with the -flag disabled to recover the device.
Saying bricked was the wrong phrasing for that.

Secondly yes flashing the magisk boot image using fastboot will not allow magisk to backup the image as it has no access to it and it won't backup when you patch an image to regular storage.

However if you boot with the patched image using the fastboot boot command and then patch directly using the recommended option it will backup the images for restoration and will allow the ota method of restore, update, re magisk without reboot method to work.

Im asking if there is a reason why that shouldn't be done because I don't want to **** up my device because something happens in the background I am not seeing.
First, my reply to your original post was not meant to dismiss your view of temporarily booting a Magisk_patched...img: fastboot boot magisk_patched....img.

I was explaining why step 16 is fastboot flash boot magisk_patched....img.

Second, I wanted to understand what you meant when you wrote:

"2. the stock images are backed up by magisk using this install method which allows for restoring and OTA updates using the device only without any extra steps."

The only reference to OTA in this Guide is in the OP ~~~ Part II - Instructions, 3. Take the OTA Update and Maintain Root
 
  • Like
Reactions: Slim2none4u

humb13

Member
Nov 24, 2016
36
5
Hey guys,

Currently I have a Oneplus 8. Unfortunately the battery is swollen and about to go. I believe it might be a better idea to upgrade the phone instead of spending money to replace the battery. I'm looking into a Google Pixel 6 and reading Homeboy76's root instructions. They're not all that different from the Oneplus with the following differences I'd like to inquire about:

It's says to extract the kernel (boot.img) and a flash-all.bat file. I'm not seeing anything explaining what to do with the batch file after extracting it.

Homeboy76 recommends a clean flash in order to perform a major upgrade (e.g. 12.00 to 12.1). What's the best way to back up your data (apps & media) before performing the upgrade? To my knowledge a clean flash wipes everything. Speaking of upgrades, Oneplus performs them OTA. We flash the stock boot.img file to unroot, perform the OTA upgrade, download and patch the new boot.img with Magisk and reflash. You can't do this with Pixel 6?

The final step is the Universal SafetyNet Fix. Oneplus root instructions didn't include this at all. Is this mandatory? Or is it that the Pixel 6 requires this because it's more "googly" than the Oneplus?

Also: Many Oneplus users continue to use Magisk 23001. This is the last version that includes a root hider. This version won't work on the Pixel 6, or more correctly Android 12 or higher?

Thanks for your help.
 

Homeboy76

Senior Member
Aug 24, 2012
3,224
1,773
Google Pixel XL
Hey guys,

Currently I have a Oneplus 8. Unfortunately the battery is swollen and about to go. I believe it might be a better idea to upgrade the phone instead of spending money to replace the battery. I'm looking into a Google Pixel 6 and reading Homeboy76's root instructions. They're not all that different from the Oneplus with the following differences I'd like to inquire about:

It's says to extract the kernel (boot.img) and a flash-all.bat file. I'm not seeing anything explaining what to do with the batch file after extracting it.

Homeboy76 recommends a clean flash in order to perform a major upgrade (e.g. 12.00 to 12.1). What's the best way to back up your data (apps & media) before performing the upgrade? To my knowledge a clean flash wipes everything. Speaking of upgrades, Oneplus performs them OTA. We flash the stock boot.img file to unroot, perform the OTA upgrade, download and patch the new boot.img with Magisk and reflash. You can't do this with Pixel 6?

The final step is the Universal SafetyNet Fix. Oneplus root instructions didn't include this at all. Is this mandatory? Or is it that the Pixel 6 requires this because it's more "googly" than the Oneplus?

Also: Many Oneplus users continue to use Magisk 23001. This is the last version that includes a root hider. This version won't work on the Pixel 6, or more correctly Android 12 or higher?

Thanks for your help.
...It's says to extract the kernel (boot.img) and a flash-all.bat file...

I'm assuming you are referring to OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 4. Extract Files from Factory Image

- Read the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 2. Install/Update Factory Image keep data or wipe data
It explains what to do with the flash-all.bat file after you have extracted it.

- Read the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 5. Root/Reroot with Magisk and Pass SafetyNet., • Patching the boot.img - to root/reroot.
It explains what to do with the boot.img file after you have extracted it.

One of the other uses for the extracted boot.img file is removing root: OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 4. Extract Files from Factory Image


...What's the best way to back up your data (apps & media) before performing the upgrade? To my knowledge a clean flash wipes everything. Speaking of upgrades, Oneplus performs them OTA. We flash the stock boot.img file to unroot, perform the OTA upgrade, download and patch the new boot.img with Magisk and reflash. You can't do this with Pixel 6?...

- Search the OnePlus threads for backing up data (apps & media) for your phone.
- A clean flash does wipe everything.
- We flash the stock boot.img file to unroot, perform the OTA upgrade, download and patch the new boot.img with Magisk and reflash. We do too.


The final step is the Universal SafetyNet Fix. Oneplus root instructions didn't include this at all. Is this mandatory? Or is it that the Pixel 6 requires this because it's more "googly" than the Oneplus?...
- It is mandatory if you want to pass SafetyNet.

Also: Many Oneplus users continue to use Magisk 23001. This is the last version that includes a root hider. This version won't work on the Pixel 6, or more correctly Android 12 or higher?
- If you are purchasing a Google Pixel 6 phone with an unlockable bootloader so you can root it.
- You should use Magisk Beta/Stable 24.x or Magisk Canary app-release_2431x.

- Read the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 5. Root/Reroot with Magisk and Pass SafetyNet., • Pass Safety Net with SafetyNet Fix 2.2.1, 3. Settings for Magisk Canary

It explains how to hide your apps.
 
Last edited:
  • Like
Reactions: Slim2none4u

Homeboy76

Senior Member
Aug 24, 2012
3,224
1,773
Google Pixel XL
Magisk Canary Update
app-release (2106751e) (24315)

Zygisk
[MagiskSU] [Zygisk] Proper package management and detection
[Zygisk] Fix Zygisk's self code unloading implementation...
 
  • Like
Reactions: Slim2none4u

mhrussell1

Senior Member
Oct 28, 2011
74
10
Anaheim
LG Nexus 5X
Google Pixel 3
- Read the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 5. Root/Reroot with Magisk and Pass SafetyNet., • Pass Safety Net with SafetyNet Fix 2.2.1, 3. Settings for Magisk Canary

It explains how to hide your apps.
While waiting for my new phone, I used your steps for this section to get my P3 to show device certified and I was able to get GPay to work again which it had not for the last few months, so thanks for that!

My question is your steps say to check the services in the Configure Deny List: "Google Play Store, Google Pay, etc."

Then while in Airplane mode you say to clear storage on that same list.

I added at least one more service, Google Play Protect Service along with my one of my banking apps. Is there a definitive list for the deny list that allow GPay to work? What do you mean by etc.?

Mark
 

jbofc

Member
Jun 6, 2014
5
0
So can I re-lock the bootloader and retain root? I just wanted to use BCR with the google phone app... It's installed now but as I understand if I re-lock bootloader then this may brick my phone? I haven't rooted for ages...can I just take ota updates now or do I have to re-patch each update?
 

mhrussell1

Senior Member
Oct 28, 2011
74
10
Anaheim
LG Nexus 5X
Google Pixel 3
So can I re-lock the bootloader and retain root? I just wanted to use BCR with the google phone app... It's installed now but as I understand if I re-lock bootloader then this may brick my phone? I haven't rooted for ages...can I just take ota updates now or do I have to re-patch each update?
The OP Part II Instructions in the last part of step 1. states that you should NOT lock the bootloader before you return to a stock image. There is a method to do OTA updates when you are unlocked but I have never used it. I prefer the full image flash with the -w flag removed to keep my data and root.
 
Last edited:

Top Liked Posts

  • 2
    Thanks for the update.
    By the way, section 5 the link to SNF still says 2.2.1
    Perhaps you can change that to:
    Latest SafetyNetFix without specifying a version and link with this URI
    This way it will always be accurate and no need for maintenance.
    I removed 2.2.1.
    :oops: I thought you read "section 5, the link to the SafetyNet releases has always been in the OP; ~~~ Part II - Instructions ~~~ ; Root/Reboot with Magisk Pass SafetyNet; • Pass SafetyNet with SafetyNet Fix; 1. Download file(s)
  • 4
    Magisk Updates
    - Magisk Beta 25.0
    - Magisk Canary (cacf8736) (25001)
    2
    So can I re-lock the bootloader and retain root? I just wanted to use BCR with the google phone app... It's installed now but as I understand if I re-lock bootloader then this may brick my phone? I haven't rooted for ages...can I just take ota updates now or do I have to re-patch each update?
    The OP Part II Instructions in the last part of step 1. states that you should NOT lock the bootloader before you return to a stock image. There is a method to do OTA updates when you are unlocked but I have never used it. I prefer the full image flash with the -w flag removed to keep my data and root.
    2
    SafetyNetFix Update
    v2.3.1 - 27Jun
    This version only supports Zygisk (Magisk 24 and newer).
    2
    Thanks for the update.
    By the way, section 5 the link to SNF still says 2.2.1
    Perhaps you can change that to:
    Latest SafetyNetFix without specifying a version and link with this URI
    This way it will always be accurate and no need for maintenance.
    I removed 2.2.1.
    :oops: I thought you read "section 5, the link to the SafetyNet releases has always been in the OP; ~~~ Part II - Instructions ~~~ ; Root/Reboot with Magisk Pass SafetyNet; • Pass SafetyNet with SafetyNet Fix; 1. Download file(s)
    1
    Hey guys,

    Currently I have a Oneplus 8. Unfortunately the battery is swollen and about to go. I believe it might be a better idea to upgrade the phone instead of spending money to replace the battery. I'm looking into a Google Pixel 6 and reading Homeboy76's root instructions. They're not all that different from the Oneplus with the following differences I'd like to inquire about:

    It's says to extract the kernel (boot.img) and a flash-all.bat file. I'm not seeing anything explaining what to do with the batch file after extracting it.

    Homeboy76 recommends a clean flash in order to perform a major upgrade (e.g. 12.00 to 12.1). What's the best way to back up your data (apps & media) before performing the upgrade? To my knowledge a clean flash wipes everything. Speaking of upgrades, Oneplus performs them OTA. We flash the stock boot.img file to unroot, perform the OTA upgrade, download and patch the new boot.img with Magisk and reflash. You can't do this with Pixel 6?

    The final step is the Universal SafetyNet Fix. Oneplus root instructions didn't include this at all. Is this mandatory? Or is it that the Pixel 6 requires this because it's more "googly" than the Oneplus?

    Also: Many Oneplus users continue to use Magisk 23001. This is the last version that includes a root hider. This version won't work on the Pixel 6, or more correctly Android 12 or higher?

    Thanks for your help.
    ...It's says to extract the kernel (boot.img) and a flash-all.bat file...

    I'm assuming you are referring to OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 4. Extract Files from Factory Image

    - Read the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 2. Install/Update Factory Image keep data or wipe data
    It explains what to do with the flash-all.bat file after you have extracted it.

    - Read the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 5. Root/Reroot with Magisk and Pass SafetyNet., • Patching the boot.img - to root/reroot.
    It explains what to do with the boot.img file after you have extracted it.

    One of the other uses for the extracted boot.img file is removing root: OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 4. Extract Files from Factory Image


    ...What's the best way to back up your data (apps & media) before performing the upgrade? To my knowledge a clean flash wipes everything. Speaking of upgrades, Oneplus performs them OTA. We flash the stock boot.img file to unroot, perform the OTA upgrade, download and patch the new boot.img with Magisk and reflash. You can't do this with Pixel 6?...

    - Search the OnePlus threads for backing up data (apps & media) for your phone.
    - A clean flash does wipe everything.
    - We flash the stock boot.img file to unroot, perform the OTA upgrade, download and patch the new boot.img with Magisk and reflash. We do too.


    The final step is the Universal SafetyNet Fix. Oneplus root instructions didn't include this at all. Is this mandatory? Or is it that the Pixel 6 requires this because it's more "googly" than the Oneplus?...
    - It is mandatory if you want to pass SafetyNet.

    Also: Many Oneplus users continue to use Magisk 23001. This is the last version that includes a root hider. This version won't work on the Pixel 6, or more correctly Android 12 or higher?
    - If you are purchasing a Google Pixel 6 phone with an unlockable bootloader so you can root it.
    - You should use Magisk Beta/Stable 24.x or Magisk Canary app-release_2431x.

    - Read the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 5. Root/Reroot with Magisk and Pass SafetyNet., • Pass Safety Net with SafetyNet Fix 2.2.1, 3. Settings for Magisk Canary

    It explains how to hide your apps.
  • 19
    [Guide] Root Pixel 6 with Magisk, Android 12.1
    Android Security Bulletin—June 2022
    Pixel Update Bulletin—June 2022

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

    ~ ~ ~ Part I - INFORMATION ~ ~ ~
    1. Disclaimer

      • I assume no responsibility for the malfunctioning/bricking of your phone.
      • 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

    3. Update(s)

    4. NEW

      • SafetyNet Fix 2.3.1 - 27Jun
    5. My Other Guides
    6. Credits/Thanks/Recognitions

      • Google - Android 12 factory/OTA images.
      • @topjohnwu - Magisk.
      • vvb2060 - Magisk alpha.
      • Those I may have, inadvertently, forgotten.
    ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~
    1. 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.
    2. 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 6 - oriole.
        3. If you get an errorwhile flashing, try one of these options:
          • Change the USB port to a non charging USB port.
          • Change the USB cord.
          • Change Computers.
        4. 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.
        5. Backup your data
        6. Download the latest Factory Image: Pixel 6 - oriole to your Computer.
        7. Go to Part II - INSTRUCTIONS => 4. Extract Files from the FactoryImage/Flash boot.img and extract the flash-all.bat file.
      • 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., DroidEdit app.
          1. Change this line: fastboot -w update image-oriole-sq9d.999999.999.zip
          2. to this: fastboot update image-oriole-sq1d.999999.999.zip
          3. Note: If you do not remove the -w your 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-oriole-....img
          2. flash-all.bat
          3. image-oriole-....zip
          4. radio-oriole-....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 completed.
        • Go-to Part II - INSTRUCTIONS => 5. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
      • Flash Factory Image Wipe Data

        • This will wipe your phone's Internal Storage.
        • Open the folder you extracted the Factory Image to and Copy/Move these files to the Platform-tools folder:
          1. bootloader-oriole-....img
          2. flash-all.bat
          3. image-oriole-....zip
          4. radio-oriole-....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.
        • Setup phone
        • Enable Developer Mode and USB Debugging
          1. Setup => About phone => Tap Build number 7 times or untill you see you are a 'Devloper'.
          2. Setup => System => Developer options => Enable Developer options => enable USB Debugging
        • Go-to Part II - INSTRUCTIONS => 5. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
    3. 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
        • fastboot flash vendor_dlkm vendor_dlkm.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.
    4. Extract Files from Factory Image/Flash boot.img

      • Extract Files from Factory Image

        1. Extract flash-all.bat and boot.img file
        2. Download the latest Factory image to your phone.
        3. Extract the Factory Image file (bramble-r2d1a.999999.999-factory-99a9a99a.zip) to a folder. The, stock, flash-all.bat file should be in this folder.
        4. Open the folder you extracted the Factory image to and, extract the Image file (image-bramble-aa9a.999999.999.zip) into the folder. The, stock, boot.img file should be in this 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
    5. Root/Reroot with Magisk and Pass SafetyNet.

      • Android 12

        • Upgrade to Android 12: OP, Part II - INSTRUCTIONS, 2. Install/Update Factory Image keep data or wipe data, Keep data
      • Patching the boot.img - to root/reroot.

        1. Go to Part II - INSTRUCTIONS => 4. Extract Files from the FactoryImage/Flash boot.img and extract the boot.img file.
        2. Install Magisk Canary - Download app-release.apk
          or
          Magisk Beta 25.0/Stable 24.3 App
        3. Open Magisk Beta/Canary/Stable App
        4. The Update Channel should be set to Beta/Canary/Stable, depending on the version you Installed.
        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

        1. Download File(s)
        2. Install SafetyNet Fix
          • Open Magisk
          • Tap Modules icon
          • Tap Install from storage
          • Navigate to the SafetyNet Fix file you downloaded
          • Tap the SafetyNet Fix 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.
          • Optional 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.
    6. 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!
    7. 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
    8. 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.
    9. 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
      • 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.
    10. ADB Sideload

    ~ ~ ~ Part III - OTHER ~ ~ ~
    1. Custom ROMs

      • Need help with a Custom ROM?
        • First, read and follow the Installation Instructions. The installation instructions are in the OP.
        • Second, if you have a problem Installing it, 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 on the thread.
      • ROMs
        1. Alpha/Beta

          • None
        2. Official

          • None
        3. Unofficial
    2. Mods
    3. T.W.R.P. Backup/Restore

      • Waiting for Android 12 T.W.R.P.
    5
    I have modified the OP to make it easier to use. It has been divided into three parts: Information, Instructions, and Other.
    Tip: Read the, entire, Information Part first, then the Instructions for the operation you want to preform i.e., Install Factory image: Read Install/Update Factory Image keep data or wipe data, etc.
    4
    Magisk Updates
    - Magisk Beta 25.0
    - Magisk Canary (cacf8736) (25001)