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

Search This thread

Nimueh

Recognized Contributor
May 19, 2012
3,182
2,627
OnePlus 3
Samsung Galaxy Tab A series
Even what you do seems complicated to me.
I download the factory image, patch the boot image with magisk, flash all needed stuff with 0riole-Flasher in one single step, done.

No disabling modules, no sideloading, booting images and whatever.

Works all fine here.
Yea I don't like that flasher, I prefer the manual way - and if you'd ever had a bootloop due to the system having updated while you were using a substratum overlay you'd know why I disable all modules, just in case :LOL:
 
  • Like
Reactions: Lughnasadh

Homeboy76

Senior Member
Aug 24, 2012
3,160
1,722
Google Pixel XL
I have no idea why all those guides have such complicated ways of updating ... when I updated from rooted December to 007 it was basically 3 steps:

Patch boot.img with Magisk, disable all modules
Reboot to recovery, sideload the OTA zip
Reboot to bootloader, boot patched img and then once booted direct install in Magisk

That worked fine for me, without all those bells + whistles. There might be instances where the "complicated" way is needed but I have no idea when or why 🤷‍♀️
Maybe, the reason some members choose to flash the factory image is you have to download the latest factory image to get the latest boot.img.

So they just flash it instead of downloading the factory image and the OTA image.
 
  • Like
Reactions: Lughnasadh

Lughnasadh

Senior Member
Mar 23, 2015
3,323
3,288
Google Nexus 5
Huawei Nexus 6P
Since my Nexus days I've always just removed the -w from the flash-all.bat file and flash-all'd away, always disabling any mods that modify the SystemUI, Android framework, etc. first. Many mods often need updating to that specific monthly update or you'll get thrown into a bootloop, as Nimueh said.

I then patch the boot image and flash it.

But really, the "best" way to update is whatever way the person feels most comfortable with. Many trails to get to the same destination.
 

bobbarker2

Senior Member
Aug 30, 2013
1,571
569
Google Pixel 6 Pro
Google Pixel 6
Erm ... while TiBu might not be maintained it still works. But try Migrate instead, I've been using it across 3 devices (incl. this Pixel) and it works great :)

OT but..
Migrate requires TWRP. Which isn't available. There's a Migrate Flasher “Alternative to TWRP flashing for Migrate apps" that's in early access and was last updated in 2020.

Titanium doesn't work on 12 or if it does it's dicey at best. Tried using it, it freezes or restores corrupt apps. There's plenty of store reviews that say the same. And it hasn't been updated since 2019.. so yeah..
 

gazdajezda

Senior Member
Apr 24, 2011
394
79
Agree, Tibu not working ok on 12, Swift is better. Yesterday i update and root my PIX6 and today i get a message that system update is available and is downloading... Will that cancel root and brick my phone? I set system updating to off in developer settings, why it does that anyway?
 

DNAblue2112

Member
Oct 14, 2015
42
18
OnePlus 5T
Google Pixel 6
Agree, Tibu not working ok on 12, Swift is better. Yesterday i update and root my PIX6 and today i get a message that system update is available and is downloading... Will that cancel root and brick my phone? I set system updating to off in developer settings, why it does that anyway?
It won't brick the phone. If the OTA update works it will simply remove root and update. You can then reapply root after the update. I believe you can also use magisks a/b updating thing for applying it to the OTA update before rebooting. But it shouldn't be able to brick your device unless something goes horrifically wrong
 

Nimueh

Recognized Contributor
May 19, 2012
3,182
2,627
OnePlus 3
Samsung Galaxy Tab A series
OT but..
Migrate requires TWRP. Which isn't available. There's a Migrate Flasher “Alternative to TWRP flashing for Migrate apps" that's in early access and was last updated in 2020.

Flashing through Migrate Flasher works fine though, no matter when it was updated. It restores everything just fine, so who cares about updates since it does what it's supposed to :cool:
 

gazdajezda

Senior Member
Apr 24, 2011
394
79
Ah, so then it will install update after it download it? Asking this because i lived happily for a month with rooted phone (36) until 4 days ago after reboot it booted to some strange mode where only have 3 options (relock, shutdown, reboot i think it was) were available. So i flash an november update (37) and root it & disable system updates. So here are we again 😀 I'm perfectly fine with current version and don't wannt such forced updates of my phone. Eh google... custom rom will be solution?

It won't brick the phone. If the OTA update works it will simply remove root and update. You can then reapply root after the update. I believe you can also use magisks a/b updating thing for applying it to the OTA update before rebooting. But it shouldn't be able to brick your device unless something goes horrifically wrong
 

BrianRC

Member
May 22, 2014
43
26
Sacramento
Help @Homeboy76 !! I am stuck in bootloop.

After unlocking bootloader, I must have made a mistake in step "Install/Update Factory Image keep data or wipe data" OS would not start so I selected factory reset. Now I am stuck in bootloop. Any help would be much appreciated.
 

Homeboy76

Senior Member
Aug 24, 2012
3,160
1,722
Google Pixel XL
Help @Homeboy76 !! I am stuck in bootloop.

After unlocking bootloader, I must have made a mistake in step "Install/Update Factory Image keep data or wipe data" OS would not start so I selected factory reset. Now I am stuck in bootloop. Any help would be much appreciated.
Just keep Pressing the volume down button during boot animation.

It should boot into safe mode.
When it finishes booting into safe mode reboot.
 
Last edited:

BrianRC

Member
May 22, 2014
43
26
Sacramento
Thanks @Homeboy76 . Holding volume down button gets me to Fastboot Mode. From there I can get to Recovery Mode. In Recovery Mode I can select Wipe data/factory reset and see the following:

-- Wiping data --
E: Open failed: /metadata/ota: No such file or directory
Formatting /data...
Formatting /metadata...
Wiping Titan M...
Wiping keys...
E:gto_esehal SecureElement:t1_recv_window_append free = 261

E:gto_esehal SecureElement:t1_recv_window_append free = 261

E:gto_esehal SecureElement:t1_recv_window_append free = 261

E:gto_esehal SecureElement:t1_recv_window_append free = 261

Data wipe complete

Then reboot but problem remains. I get the "bootloader is unlocked" error message for a moment followed by the initial Google splash screen, then black, then back to "bootloader is unlocked" error message.
 

Homeboy76

Senior Member
Aug 24, 2012
3,160
1,722
Google Pixel XL
Thanks @Homeboy76 . Holding volume down button gets me to Fastboot Mode. From there I can get to Recovery Mode. In Recovery Mode I can select Wipe data/factory reset and see the following:

-- Wiping data --
E: Open failed: /metadata/ota: No such file or directory
Formatting /data...
Formatting /metadata...
Wiping Titan M...
Wiping keys...
E:gto_esehal SecureElement:t1_recv_window_append free = 261

E:gto_esehal SecureElement:t1_recv_window_append free = 261

E:gto_esehal SecureElement:t1_recv_window_append free = 261

E:gto_esehal SecureElement:t1_recv_window_append free = 261

Data wipe complete

Then reboot but problem remains. I get the "bootloader is unlocked" error message for a moment followed by the initial Google splash screen, then black, then back to "bootloader is unlocked" error message.
Why are you going to recovery to reset your phone?

Are you trying to install Custom ROM?
If yes, read the instructions in the Custom ROM thread you are trying to install.

If you are not trying to install a Custom ROM:
  1. On your phone
    - Boot the bootloader:
    - Power off the phone => Press the Power and Down buttons until you see Start
  2. Connect your phone to the computer
  3. Read the instruction in the OP, ~ ~ ~ Instructions ~ ~ ~, Install/Update Factory Image keep data or wipe data, • Flash Factory Image Wipe Data.
    Note: Make sure the flash-all.bat file has this line: fastboot -w update image-oriole-aa9a.999999.999.zip
  4. Then do OP, ~ ~ ~ Instructions ~ ~ ~, Install/Update Factory Image keep data or wipe data, • Flash Factory Image Wipe Data.
 
Last edited:

BrianRC

Member
May 22, 2014
43
26
Sacramento
Why are you going to recovery to reset your phone?

Are you trying to install Custom ROM?
If yes, read the instructions in the Custom ROM thread you are trying to install.

If you are not trying to install a Custom ROM:
  1. On your phone
    • Boot the bootloader on your phone:
      Power off the phone => Press the Power and Down buttons until you see Start
  2. Connect your phone to the computer
  3. Read the instruction in the OP, Instructions, Install/Update Factory Image keep data or wipe data, • Flash Factory Image Wipe Data.
    Note: Make sure the flash-all.bat file has this line: fastboot -w update image-oriole-aa9a.999999.999.zip
  4. Then do OP, Instructions, Install/Update Factory Image keep data or wipe data, • Flash Factory Image Wipe Data.

Why are you going to recovery to reset your phone?

Are you trying to install Custom ROM?
If yes, read the instructions in the Custom ROM thread you are trying to install.

If you are not trying to install a Custom ROM:
  1. On your phone
    - Boot the bootloader:
    - Power off the phone => Press the Power and Down buttons until you see Start
  2. Connect your phone to the computer
  3. Read the instruction in the OP, ~ ~ ~ Instructions ~ ~ ~, Install/Update Factory Image keep data or wipe data, • Flash Factory Image Wipe Data.
    Note: Make sure the flash-all.bat file has this line: fastboot -w update image-oriole-aa9a.999999.999.zip
  4. Then do OP, ~ ~ ~ Instructions ~ ~ ~, Install/Update Factory Image keep data or wipe data, • Flash Factory Image Wipe Data.
OMG @Homeboy76, you fixed it! Editing back in the -w and running Flash-All in the bootloader worked. Thank you!

This is where I got hung up with your instructions in the first place.

Under Flash factory image Keep Data, after editing out -w and running “Flash-All” at the command prompt, it returned <waiting for any device> and nothing happened. I did some research on that and tried swapping cables and updating USB drivers to no avail.

Now this time you had me run the batch file while logged in to the bootloader. Should have I run the batch file in bootloader while trying to Keep Data? Previously I was trying to run inside the OS.

Cheers,

Brian
 

Homeboy76

Senior Member
Aug 24, 2012
3,160
1,722
Google Pixel XL
OMG @Homeboy76, you fixed it! Editing back in the -w and running Flash-All in the bootloader worked. Thank you!

This is where I got hung up with your instructions in the first place.

Under Flash factory image Keep Data, after editing out -w and running “Flash-All” at the command prompt, it returned <waiting for any device> and nothing happened. I did some research on that and tried swapping cables and updating USB drivers to no avail.

Now this time you had me run the batch file while logged in to the bootloader. Should have I run the batch file in bootloader while trying to Keep Data? Previously I was trying to run inside the OS.

Cheers,

Brian
Yes.
Take a look at the, modified, instructions. :)
 

BrianRC

Member
May 22, 2014
43
26
Sacramento
Hello @Homeboy76,

Things are not going well.

Under instructions for "Patching the boot.img - to root/reroot" steps 16 and 17 I see the following:

C:\platform-tools>fastboot flash boot magisk_patched-24101_aK2f8.img
Sending 'boot_a' (65536 KB) OKAY [ 1.823s]
Writing 'boot_a' OKAY [ 0.100s]
Finished. Total time: 1.949s

C:\platform-tools>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.003s

Then the phone boot loops, so I tried "Flash the 'stock' boot.img to both slots:"

C:\platform-tools>fastboot flash boot boot.img --slot all
Sending 'boot_a' (65536 KB) OKAY [ 1.832s]
Writing 'boot_a' OKAY [ 0.101s]
Sending 'boot_b' (65536 KB) OKAY [ 1.831s]
Writing 'boot_b' OKAY [ 0.100s]
Finished. Total time: 3.906s

When I reboot, I get an error message "Your device is corrupt. It can't be trusted and may not work properly."
Press power button to continue.

When I continue booting the phone, it gets permanently stuck on the initial Google logo.

I really appreciate your help with this.
 

Homeboy76

Senior Member
Aug 24, 2012
3,160
1,722
Google Pixel XL
Hello @Homeboy76,

Things are not going well.

Under instructions for "Patching the boot.img - to root/reroot" steps 16 and 17 I see the following:

C:\platform-tools>fastboot flash boot magisk_patched-24101_aK2f8.img
Sending 'boot_a' (65536 KB) OKAY [ 1.823s]
Writing 'boot_a' OKAY [ 0.100s]
Finished. Total time: 1.949s

C:\platform-tools>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.003s

Then the phone boot loops, so I tried "Flash the 'stock' boot.img to both slots:"

C:\platform-tools>fastboot flash boot boot.img --slot all
Sending 'boot_a' (65536 KB) OKAY [ 1.832s]
Writing 'boot_a' OKAY [ 0.101s]
Sending 'boot_b' (65536 KB) OKAY [ 1.831s]
Writing 'boot_b' OKAY [ 0.100s]
Finished. Total time: 3.906s

When I reboot, I get an error message "Your device is corrupt. It can't be trusted and may not work properly."
Press power button to continue.

When I continue booting the phone, it gets permanently stuck on the initial Google logo.

I really appreciate your help with this.

Did you do wipe data before flashing the magisk_patched.img?
- Boot Safe mode then reboot:
- re-patch the boot.img with Magisk- canary_24001
- flash repatched boot.img
fastboot flash boot magisk_patched.. Img
 

BrianRC

Member
May 22, 2014
43
26
Sacramento
Did you do wipe data before flashing the magisk_patched.img?
- Boot Safe mode then reboot:
- re-patch the boot.img with Magisk- canary_24001
- flash repatched boot.img
fastboot flash boot magisk_patched.. Img
When you say, did I wipe data, last night i did "Flash Factory Image Wipe Data" as you directed. Then I set up phone again so I could use it. Then I followed instructions this morning under Patching the boot.img - to root/reroot.

And your instructions for booting in to safe mode... Press Power Off button ==> Press Power Off until you see boot Safe Mode ==> Press Ok. Are not working for me.

Your saying now I should wipe data again before flashing magisk_patched.img? Isn't that the same as "Flash Factory Image Wipe Data" ?
 

Homeboy76

Senior Member
Aug 24, 2012
3,160
1,722
Google Pixel XL
When you say, did I wipe data, last night i did "Flash Factory Image Wipe Data" as you directed. Then I set up phone again so I could use it. Then I followed instructions this morning under Patching the boot.img - to root/reroot.

And your instructions for booting in to safe mode... Press Power Off button ==> Press Power Off until you see boot Safe Mode ==> Press Ok. Are not working for me.

Your saying now I should wipe data again before flashing magisk_patched.img? Isn't that the same as "Flash Factory Image Wipe Data" ?
No, just confirming you Wiped data.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Update
    Magisk Canary (c11ccbae) (24310)
    3
    Update
    Magisk Canary (756d8356) (24312)
    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!
    Try booting 'Safe mode' then reboot and flash the magisk patched boot.img
    fastboot flash boot magisk_patched_boot.img

    ...rooting through OTA...
    OP, Part II - Instructions, 3. Take the OTA...
    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!
    This is probably because the magisk_pacthed.img is not good, which could be due to how you transferred it to the phone, I have seen many reports that transfer through file manager is not always very reliable.

    In addition to what @Homeboy76 suggested, you can also try transferring the boot.img through adb.
    Test it first before flashing to see if it boots to root ok (without the flash option)
    Code:
    fastboot boot magisk_patched_boot.img

    One last thing, make sure when using Magisk canary (recommended) you set the channel to canary.
    2
    Hey folks. I'm a bit confused about the procedure to take an OTA and keep root, and would really appreciate some pointers.

    I have patched my boot.img as per the initial instructions (extracted boot.img from factory image, patched with magisk, and flashed it with fastboot).

    It's my understanding that to take the May OTA (I'm on the April one) I have to:
    • Go to magisk, uninstall, remove images
    • Install the OTA (both steps, DO NOT REBOT)
    • Go to magisk again, install to inactive slot
    • Reboot the device
    Is that it?

    What's confusing me is that the instructions for this on the OP (which link to the official instructions) says that "install to inactive slot" has been removed because Google changed how OTAs are taken, and that magisk does not quite have support for that. However, I'm using magisk 24.3, and the option is there. So, I'm bit unsure if it's safe to do this procedure or not.

    Some pointers in the right direction would be really appreciated.

    P.S. I disabled automatic system updates in the developer settings, but I opened the system updates screen in the settings, and now it says that the update will resume when the device is inactive. Is the update going to be automatically installed during the night? I hope not, until I figure out the right procedure to keep root.
    That note you are referring to in the instructions is old and there is currently a Pull Request to remove it, so you can ignore it as Magisk has been updated to support "Install to Inactive Slot" on Pixels. You may want to use Canary 24307 though. This method did not work with Stable 24.3 on the April build but was fixed with Canary 24306/7.

    However, this method is really hit and miss, to be honest.
  • 17
    [Guide] Root Pixel 6 with Magisk, Android 12.1
    Android Security Bulletin—May 2022
    Pixel Update Bulletin—May 2022

    Introduction
    This Guide is for Pixel 6 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

      • 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

    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 error while 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
          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.
          • 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.
    3
    That screen doesn't have a "device corrupt" message on it though, so I assumed he wasn't talking about that.
    Twice in one day, you're gooooood! :)
    3
    Update
    Magisk Canary (756d8356) (24312)