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

Search This thread

Homeboy76

Senior Member
Aug 24, 2012
3,375
1,907
Google Pixel XL
I am about to get the pixel 6a next week.
I just want to know if i unlock the bootloader and not root (can't root untill zips/ota available), will my banking apps fail like Google pay (India), PhonePe, PayTm, etc.
Don't care about safety net just want my banking apps to work untill we get the zip to patch the boot image.
¯\_( ͡❛ ͜ʖ ͡❛)_/¯
This is a Google Pixel 6 thread. I think you want the Google Pixel 6a Forum.
 
Last edited:

tom1807

Senior Member
Let me rephrase can i use unlocked pixel 6 for all banking apps without flashing magisk+safety net fix
No, bootloader unlocked without Magisk installed, Google flags your phone as insecure and so the banking apps.
The day 6a is officially shipped, the OTA/Images will be available.

Edit, this is still the Pixel 6 topic (no a), your questions belong to the Pixel 6a thread, like we have a Pixel 6 Pro thread.

Cheers
 

mad_tunes

Senior Member
May 25, 2007
96
3
Sorry if the answers somewhere in this thread, but I've not been able to find it..

This guide worked a treat for me up until about a week ago.
I went to pay for someting with google pay, I got two beeps instead of one and it refused to work, Didnt get a screenshot or note the message though, as I was at the counter in a shop.

I've tried to re-do everything from the 'Pass Safety Net with SafetyNet Fix' section a few times now, and get to the point of being able to open the google pay/wallet app and adding a card.
Once I enter the three digits from the back of my card, it says its contacting my bank and then 'This phone can't be set up for contactless payments'
I've updated both magisk and safetynetfix since (both were only one version behind to begin with), but still get the same

The play store says its certified.
YASNAC & SafetyNet Fix both say everything passes

It's ony a guess, but it might have started as google pay changed to wallet... I hadn't noticed any mention of wallet prior to the problem, at least.

I've searched here, googled, and tried various things but havent been able to re-add my card.

If I could make an old-style nandroid backup of the phone I would already have tried resetting it. I'd reset if needed, but would really like to avoid doing that and ending up in the same situation if pos.

What could/should I do to get it going again?

Thanks in advance
 
Last edited:

rrusek

Senior Member
Mar 3, 2006
194
38
Razer Phone 2
Google Pixel 6
Magisk Updates
Magisk Beta - 25.2 21Jul
Magisk Canary - app-release_9b61bdfc-25201.apk 21Jul
Magisk Stable - 25.2 21Jul
Can any please confirm or deny if the follow module work under Magisk Stable - 25.2 21Jul:

  1. Busybox for Android NDK 1.34.1
  2. Dolby Atmos Magic Revision 1.1
  3. GoogleDialerMod-Magisk 1.03
  4. Systemless Hosts 1.0
  5. Universal SafetyNet Fix 2.2.1
  6. Zygisk - LSPosed 1.8.2
Much appreciate it.

Thank you,
RJR
 

Homeboy76

Senior Member
Aug 24, 2012
3,375
1,907
Google Pixel XL
Can any please confirm or deny if the follow module work under Magisk Stable - 25.2 21Jul:

  1. Busybox for Android NDK 1.34.1
  2. Dolby Atmos Magic Revision 1.1
  3. GoogleDialerMod-Magisk 1.03
  4. Systemless Hosts 1.0
  5. Universal SafetyNet Fix 2.2.1
  6. Zygisk - LSPosed 1.8.2
Much appreciate it.

Thank you,
RJR
I can't confirm all of the modules, but these should work with no problem:
- Busybox for Android NDK 1.34.1
- Systemless Hosts 1.0 (The latest version)
- Universal SafetyNet Fix 2.2.1
- Zygisk - LSPosed 1.8.2 (The latest version)
 
  • Like
Reactions: Slim2none4u

mad_tunes

Senior Member
May 25, 2007
96
3
I got mine working again by using magisk props to spoof the phone fingerprint with the pixel 6 fingerprint they provide plus installing gpay sqlite fix. I tried so much other stuff as well but those two were the last two I did before it started working again
I'd already tried gpay sqlite fix, which hadn't done the trick on its own.
Just set a pixel 6 fingerprint using MagiskHidePropsConf as well, and I'm back in business.
Thanks a lot @DNAblue2112

Installed MagiskHidePropsConf Magisk module
Restarted
Installed a terminal app from play store
Changed props to pixel 6. I had to run 'su props' then 'props' at the terminal and follow the menu, 1>f>7>29.
Restarted

Not sure if its needed but I hadnt cleared any data since wallet last refused to add the card, so:
Enabled flight mode
Cleared data for play services, play store & wallet (remember to untick updates for youtube if you use yast)
Restarted
Flight mode off

Still saw Pay icon & splash screen not Wallet
Opened Pay and got 'google play is updating at the moment, so you wont be able to access the app'
Restarted
Still pay not wallet
Waited a few minutes & restarted again
Icon changed to wallet, can get into the app OK now
Checked with SafetyNet Test & YASNAC - still passes in both
(Re-)Added card.... and got to 'your card is ready for contactless'!
App looks ready to go
 
Last edited:

mad_tunes

Senior Member
May 25, 2007
96
3
Can any please confirm or deny if the follow module work under Magisk Stable - 25.2 21Jul:

  1. Busybox for Android NDK 1.34.1
  2. Dolby Atmos Magic Revision 1.1
  3. GoogleDialerMod-Magisk 1.03
  4. Systemless Hosts 1.0
  5. Universal SafetyNet Fix 2.2.1
  6. Zygisk - LSPosed 1.8.2
Much appreciate it.

Thank you,
RJR
I've used these OK with 25.2:
  • GoogleDialerMod-Magisk 1.03
  • Systemless Hosts 1.0
  • Universal SafetyNet Fix 2.3.1
 

Homeboy76

Senior Member
Aug 24, 2012
3,375
1,907
Google Pixel XL
Pixel 6a, Pixel 6, and Pixel 6 Pro

* * * * * Regular Users * * * * *

* * * * * No Downgrading * * * * *

* * * * * This is why there is No Downgrading * * * * *
 
Last edited:
  • Haha
Reactions: Slim2none4u

Absoluttalent

New member
May 27, 2015
4
0
I am having issues taking any OTA updates. This is the 4th time when I followed directions and same result. I disabled modules and removed them, restarted, uninstalled magisk, take update, reinstall magisk and reboot. Then I'm met with the red text "your device is corrupted" and stays frozen on the boot screen with "Google" on it.


Holding power + vol up gets me back in, but I lose root and didn't get the OTA applied. So I need to update and redo the root process all over.


Any ideas what is the reason for this is? The only modules I used was systemless hosts file and safety net fix, and outside of YT vanced and AdAway (root version) , everything else on the phone is official apps from play store. It's a pain to do this every month for the update


Forgot to mention, this was with whatever the latest versions of magisk was. Back in March 24.13 or whatever it was at the time, June was the 25.1, and recently I was on 25.2
 
I am having issues taking any OTA updates. This is the 4th time when I followed directions and same result. I disabled modules and removed them, restarted, uninstalled magisk, take update, reinstall magisk and reboot. Then I'm met with the red text "your device is corrupted" and stays frozen on the boot screen with "Google" on it.


Holding power + vol up gets me back in, but I lose root and didn't get the OTA applied. So I need to update and redo the root process all over.


Any ideas what is the reason for this is? The only modules I used was systemless hosts file and safety net fix, and outside of YT vanced and AdAway (root version) , everything else on the phone is official apps from play store. It's a pain to do this every month for the update


Forgot to mention, this was with whatever the latest versions of magisk was. Back in March 24.13 or whatever it was at the time, June was the 25.1, and recently I was on 25.2
I would advice using this tool.
I believe your issue is that you are not disabling Verity and Verification. This tool makes the process quick and painless.
 

Homeboy76

Senior Member
Aug 24, 2012
3,375
1,907
Google Pixel XL
I am having issues taking any OTA updates. This is the 4th time when I followed directions and same result. I disabled modules and removed them, restarted, uninstalled magisk, take update, reinstall magisk and reboot. Then I'm met with the red text "your device is corrupted" and stays frozen on the boot screen with "Google" on it.


Holding power + vol up gets me back in, but I lose root and didn't get the OTA applied. So I need to update and redo the root process all over.


Any ideas what is the reason for this is? The only modules I used was systemless hosts file and safety net fix, and outside of YT vanced and AdAway (root version) , everything else on the phone is official apps from play store. It's a pain to do this every month for the update


Forgot to mention, this was with whatever the latest versions of magisk was. Back in March 24.13 or whatever it was at the time, June was the 25.1, and recently I was on 25.2
If you are referring to the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 3. Take the OTA Update and Maintain Root instructions. You rebooted to soon. Additionally, an upgrade for the Google Pixel 6/Pro/6a to Android 13 requires flashing the bootloader to the a and b slot to avoid bricking your phone.
Further, the instructions in the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 2. Install/Update Factory Image keep data, wipe data, or use @badabing2003 PixelFlasher are the instructions most people should use to upgrade to Android 13.
 
Last edited:
  • Like
Reactions: Slim2none4u

Homeboy76

Senior Member
Aug 24, 2012
3,375
1,907
Google Pixel XL
I would advice using this tool.
I believe your issue is that you are not disabling Verity and Verification. This tool makes the process quick and painless.
First, AFAIK disabling Verity and Verification are no longer required.
Second, there is ,now, a link to the PixelFlasher in the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 2. Install/Update Factory Image keep data, wipe data, or use @badabing2003 PixelFlasher. Thanks for the reminder. :)
 
Last edited:
  • Like
Reactions: Slim2none4u

Absoluttalent

New member
May 27, 2015
4
0
I would advice using this tool.
I believe your issue is that you are not disabling Verity and Verification. This tool makes the process quick and painless.
I will have to try that tool then. I would've liked to do this without involving the computer. But guess that might be my option


If you are referring to the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 3. Take the OTA Update and Maintain Root instructions. You rebooted to soon. Additionally, an upgrade for the Google Pixel 6/Pro/6a to Android 13 requires flashing the bootloader to the a and b slot to avoid bricking your phone.
Further, the instructions in the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 2. Install/Update Factory Image keep data, wipe data, or use @badabing2003 PixelFlasher are the instructions most people should use to upgrade to Android 13.
Rebooting too early? I followed the directions and waited until after I get the reboot button from update and from magisk install to slot screen. I gotta wait longer after the process is completed to reboot?

And I was not doing the Android 13 update, just the monthly patches

But later when I get home, I will give the pixelflasher a shot
 

Homeboy76

Senior Member
Aug 24, 2012
3,375
1,907
Google Pixel XL
I will have to try that tool then. I would've liked to do this without involving the computer. But guess that might be my option

Rebooting too early? I followed the directions and waited until after I get the reboot button from update and from magisk install to slot screen. I gotta wait longer after the process is completed to reboot?

And I was not doing the Android 13 update, just the monthly patches

But later when I get home, I will give the pixelflasher a shot
@Absoluttalent

If you were you trying to install the ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 3. Take the OTA Update and Maintain Root. You would be installing the August 2022 OTA (Android 13).

If were you just trying to install the OTA update you would be installing the August 2022 update (Android 13).

Please read the Updating Pixel 6, Pixel 6 Pro, and Pixel 6a devices to Android 13 for the first time section of the Factory Images for Nexus and Pixel Devices web site.

The steps for installing the OTA update are:
- uninstall Magisk (remove root)
- reboot
- take the OTA update

Root Phone
- Download the Factory image for August 2022
- Extract the boot.img and the bootloader-oriole-slider-1.2-8739948.img
- install Magisk manager
- Patch the August 2022 boot.img
- Put the Magisk_patched...img and the bootloader-oriole-slider-1.2-8739948.img on your computer, in the SDK Platform-tools folder (the folder with fastboot.exe and adb.exe in it).
- boot the bootloader
- adb reboot bootloader
- flash the magisk_patched...img
- fastboot flash boot magisk_patched...img

Install bootloader to a and b slots
- This prevents bricking your Google Pixel 6 phone.
-fastboot flash bootloader bootloader-oriole-slider-1.2-8739948.img --slot all
-fastboot reboot-bootloader
-fastboot reboot
- Done!
 
Last edited:

Absoluttalent

New member
May 27, 2015
4
0
If you were you trying to install the ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 3. Take the OTA Update and Maintain Root. You would be installing the August 2022 OTA (Android 13).

If were you just trying to install the OTA update you would be installing the August 2022 update (Android 13).

The steps for installing the OTA update are:
- uninstall Magisk (remove root)
- reboot
- take the OTA update

Root Phone
- Download the Factory image for August 2022
- Extract the boot.img and the bootloader-oriole-slider-1.2-8739948.img
- install Magisk manager
- Patch the August 2022 boot.img
- Put the Magisk_patched...img and the bootloader-oriole-slider-1.2-8739948.img on your computer, in the SDK Platform-tools folder (the folder with fastboot.exe and adb.exe in it).
- boot the bootloader
- adb reboot bootloader
- flash the magisk_patched...img
- fastboot flash boot magisk_patched...img

Install bootloader to a and b slots
- This prevents bricking your Google Pixel 6 phone.
fastboot flash bootloader bootloader-oriole-slider-1.2-8739948.img --slot all
-fastboot reboot-bootloader
-reboot
- Done!
I had no idea the august update was with Android 13, it was only 1.45mb.

Thanks for the instructions on this though. Might have to go through it on my next days off.
 

Top Liked Posts

  • 2
    :oops: Are you asking a question?
    That person seems to be posting similar posts in a bunch of different threads, Thinking maybe they're trying to get their post count up to 10 🙄

    @AarohiAngel , please don't spam threads like this.
  • 5
    Thank you both @Lughnasadh and @capntrips!

    What's odd is I did reflash my boot image thinking that would fix but it didn't, had to reflash anew from sideload.

    Thanks again for the info
    Yeah, sometimes flashing an old boot image (it will fail to boot) and then flashing a new boot image works. Sometimes sideloading an OTA works. Sometimes just waiting for the next monthly OTA works. It's a crazy thing with this Pixel 6 series and the changes that have come with it.
    4
    Yeah, sometimes flashing an old boot image (it will fail to boot) and then flashing a new boot image works. Sometimes sideloading an OTA works. Sometimes just waiting for the next monthly OTA works. It's a crazy thing with this Pixel 6 series and the changes that have come with it.
    Very good info, thank you. Yeah maybe if I had flashed my stock boot, and then reflashed my patched it would have worked, but either way sideloading the OTA fixed it. Very odd. Thanks again
    4
    Thanks for the reply. What hash is Android looking at to trip this message? I performed the same steps to root after flashing back to stock and I don't get that message anymore. Just curious 🙂
    See here for more info. The entire Verified Boot implementation is complex and error prone. It trips for a ton of things (and sometimes seemingly erroneously). Reflashing the boot partition (or even just a fastboot boot) is frequently enough to fix it.
    2
    :oops: Are you asking a question?
    That person seems to be posting similar posts in a bunch of different threads, Thinking maybe they're trying to get their post count up to 10 🙄

    @AarohiAngel , please don't spam threads like this.
    2
    People have come across this corruption message doing a variety of things, from flashing patched boot images, to flashing kernels to updating monthly security builds in various ways. Here's a better explanation...


    Thank you both @Lughnasadh and @capntrips!

    What's odd is I did reflash my boot image thinking that would fix but it didn't, had to reflash anew from sideload.

    Thanks again for the info
  • 23

    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

      • @topjohnwu - Magisk.
      • vvb2060 - Magisk alpha.
      • Those I may have, inadvertently, forgotten.
    ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~
    (The Instructions listed below are not steps, they are individual sets of 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, wipe data, or use @badabing2003 PixelFlasher

      • Important Note(s):
        1. "Updating Pixel 6, Pixel 6 Pro, and Pixel 6a devices to Android 13 for the first time

          Warning: The Android 13 update for Pixel 6, Pixel 6 Pro, and the Pixel 6a contains a bootloader update that increments the anti-roll back version for the bootloader. This prevents the device from rolling back to previous vulnerable versions of the bootloader. After flashing an Android 13 build on these devices you will not be able to flash and boot older Android 12 builds. For developers who need to develop and test against an Android 12 environment, a special Developer Support Build that contains the bootloader update should be used.

          After taking an Android 13 update and successfully booting the device post update, an Android 12 build resides in the inactive slot (seamless updates for more information on slots) of the device. The inactive slot contains an older bootloader whose anti-rollback version has not been incremented. If the active slot is then flashed with a build that fails to boot, the fallback mechanism of seamless updates kicks in and the device tries to boot from the inactive slot. Since the inactive slot contains the older bootloader, the device enters an unbootable state.

          To avoid hitting this state, if you are flashing a Pixel 6, Pixel 6a, or Pixel 6 Pro device with an Android 13 build for the first time, please flash the bootloader partition to the inactive slot"...
        2. If you want to update to the Android 13 Factory/OTA image without wiping your phone and your phone is rooted. Open Magisk and delete all the modules or uninstall Magisk. Do Flash Factory Image Keep Data (below).
        3. Always verify you have the latest version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 6 - oriole.
        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. If you phone bootloops
          • Press the Power button until the phone turns off.
          • Press the Power and Volume Down to boot the bootloader.
          • Open a Command Prompt in the SDK-Platform-tools folder or the folder that has adb.exe in it, and type adb wait-for-device shell magisk --remove-modules
          • fastboot Reboot
        6. Backup your data
        7. Download the latest Factory Image: Pixel 6 - oriole to your Computer.
        8. 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 to Upgrade to Android 13 or Update Android 13 with a text editor i.e., DroidEdit app (See Bold items below).

          * * * * * * * * * * * * * * * * *
          Upgrade To Android 13 (First Time Installing Android 13)
          * * * * * * * * * * * * * * * * *
          @Echo off
          PATH=%PATH%;"%SYSTEMROOT%\System32"
          fastboot flash bootloader bootloader-oriole-slider-9.9-9999999.img --slot all
          fastboot reboot-bootloader
          timeout /t 5 >nul
          fastboot flash radio radio-oriole-a9999a-999999-999999-a-9999999.img --slot all
          fastboot reboot-bootloader
          timeout /t 5 >nul
          fastboot -- skip-reboot update image-oriole-aa9a.999999.999.zip
          Note: I replaced the -w with -- skip-reboot to Keep Data.
          fastboot reboot-bootloader
          timeout /t 5 >nul
          fastboot --set-active=other
          timeout /t 10 >nul
          fastboot reboot-bootloader
          timeout /t 5 >nul
          fastboot update image-oriole-tp1a.220624.021.zip
          echo Press any key to exit...
          pause >nul
          exit
          * * * * * * E N D * * * * * *

          * * * * * * * * * * * * * * *
          Update Android 13
          * * * * * * * * * * * * * * *
          @Echo off
          PATH=%PATH%;"%SYSTEMROOT%\System32"
          fastboot --set-active=other
          fastboot reboot-bootloader
          fastboot flash bootloader bootloader-oriole-slider-9.9-9999999.img
          fastboot reboot-bootloader
          timeout /t 5 >nul
          fastboot flash radio radio-oriole-a99999-999999-999999-a-9999999.img
          fastboot reboot-bootloader
          timeout /t 5 >nul
          fastboot update image-oriole-aa9a.999999.999.zip
          Note: I removed the -w to Keep Data.
          echo Press any key to exit...
          pause >nul
          exit
          * * * * * * E N D * * * * * *
        • 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 edit the flash-all.bat file with a text editor i.e., DroidEdit app (See Bold items below).

          * * * * * * * * * * * * * * * * *
          Upgrade To Android 13 (First Time Installing Android 13)
          * * * * * * * * * * * * * * * * *
          @Echo off
          PATH=%PATH%;"%SYSTEMROOT%\System32"
          fastboot flash bootloader bootloader-oriole-slider-9.9-9999999.img --slot all
          fastboot reboot-bootloader
          timeout /t 5 >nul
          fastboot flash radio radio-oriole-a9999a-999999-999999-a-9999999.img --slot all
          fastboot reboot-bootloader
          timeout /t 5 >nul
          fastboot -w update image-oriole-aa9a.999999.999.zip
          echo Press any key to exit...
          pause >nul
          exit
          * * * * * * E N D * * * * * *
        • 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.
      • @badabing2003 Google Pixel 6 PixelFlasher Support thread
    3. Take the OTA Update and Maintain Root

      • This set of instructions was written by @topjohnwu: Install Magisk to Inactive Slot , use the latest Magisk Canary, Beta, or Stable.
      • NOTE: After you Open Magisk and Restore Images. If you had a Custom Kernel installed, 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 Mod 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
        • Press the Power button until the phone turns off.
        • Press the Power and Volume Down to boot the bootloader.
        • Open a Command Prompt in the SDK-Platform-tools folder or the folder that has adb.exe in it, and type adb wait-for-device shell magisk --remove-modules
        • fastboot Reboot
    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 13

        • Upgrade to Android 13: 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/Stable 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
          • Remove Modules
            1. Press the Power button until the phone turns off.
            2. Press the Power and Volume Down to boot the bootloader.
            3. Open a Command Prompt in the SDK-Platform-tools folder or the folder that has adb.exe in it, and type adb wait-for-device shell magisk --remove-modules
            4. fastboot Reboot.
      • 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. Install Displax/safetynet-fix Mod, v2.3.1-MOD
          • Open Magisk
          • Tap Modules icon
          • Tap Install from storage
          • Navigate to the Displax/safetynet-fix Mod, v2.3.1-MOD file you downloaded
          • Tap the Displax/safetynet-fix Mod, v2.3.1-MOD file
          • Tap the check mark (✓ at the bottom) to start the installation.
          • Note: You do not have to disable/remove SafetyNet Fix.
          • After it installs tap the Save icon to save the log
          • Tap Reboot.
        4. 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.
          • Do not enable Denylist
          • Tap Configure DenyList => Tap 3 Dot Menu => Check ✓ Show system apps => Check ✓ Google Play Store, Google Pay, Google Wallet etc.
          • Scroll down to Superuser and enable Enable Biometric Authentication.
        5. Get Device Certified Clear Google Play Store, Google Play Services, Google Pay, Google Wallet, etc. data[/B]
          • 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 & Cache
          • Tap Clear storage
            Note: Repeat the 3 steps above for Google Play Services, Google Pay, Google Wallet, etc.
          • reboot
          • Turn Airplane mode off
        6. Check Device Certification, I may take 24 hours for 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 from Storage

        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
      • Install Modules from Fox2Code/Fox Magisk Module Manager

        1. Open Fox2Code/Fox Magisk Module Manager
        2. Tap the Modules icon
        3. Locate the Module you want to install
        4. Tap Install
        5. After it installs, tap the Disc Icon to save the install log.
        6. Tap Reboot
      • Update Modules

        1. Open Fox2Code/Fox Magisk Module Manager
        2. You, will see the Modules that have Updates.
        3. Tap the Module you want to update.
        4. Tap install.
        5. After it installs, tap the Disc Icon to save the install log.
        6. 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?
        1. If you are you are trying to install or have installed a Custom ROM, read and follow the Installation Instructions in the OP of the Custom ROM thread.
        2. Search the thread of the Custom ROM you are trying to install or have installed for answer(s)/solution(s) to your question(s)/problem(s): If you don't find a answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM thread you are trying to install or have installed.
        3. If you are trying to install a Addon(s) {Custom Kernel, Magisk, etc.} to the Custom ROM you installed: Search the thread of the Custom ROM you installed or the thread of the Addon you want to add to your Custom ROMfor answer(s)/solution(s) to your question(s)/problem(s). If you don't find an answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM or Addon (Custom Kernel, Magisk, etc.) thread.
      • ROMs
        1. Alpha/Beta

          • None
        2. Official

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

      • Waiting for Android 13 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.
    5
    Thank you both @Lughnasadh and @capntrips!

    What's odd is I did reflash my boot image thinking that would fix but it didn't, had to reflash anew from sideload.

    Thanks again for the info
    Yeah, sometimes flashing an old boot image (it will fail to boot) and then flashing a new boot image works. Sometimes sideloading an OTA works. Sometimes just waiting for the next monthly OTA works. It's a crazy thing with this Pixel 6 series and the changes that have come with it.
    4
    Update
    SDK Platform-tools - r33.0.3