How To Guide [Guide] Root Pixel 6 with Magisk + Unlock Bootloader + Pass SafetyNet + More

Search This thread

badabing2003

Recognized Contributor
Sep 17, 2012
1,586
1,868
Process of elimination.
We can try few things.

1- Live boot to the patched image, let's see if that works see the guides in OP, basically you remove the word flash from your command.
This will tell us if your root.img is good or not.

2- Switch slots and try on the inactive slot, but first factory flash that slot like you did this one and then try to flash the boot.img
If that works, then something about the boot partition on the current slot could be the issue.
 

V0latyle

Forum Moderator
Staff member
That's good, there shouldn't be a problem with that version, as long as you did download it from the link you gave.
Process of elimination.
We can try few things.

1- Live boot to the patched image, let's see if that works see the guides in OP, basically you remove the word flash from your command.
This will tell us if your root.img is good or not.

2- Switch slots and try on the inactive slot, but first factory flash that slot like you did this one and then try to flash the boot.img
If that works, then something about the boot partition on the current slot could be the issue.
I might have missed it, did he already try flashing the stock boot image? Maybe one of our gurus @pndwal or @ipdev might have some input.
 

manjaroid

Senior Member
Jun 25, 2019
276
119
first I suggest that you are not using a remote drive like OneDrive.
Second, keep the path short, in theory it all should work in Windows or DOS, but I witnessed too much strange behavior with long filepaths.
I've been wondering about the path too and keep coming back to OneDrive. @takeshishen - Since c:\something made no difference maybe try logging in as a different user with a local account... just to eliminate OneDrive as a possibility once and for all.
 

V0latyle

Forum Moderator
Staff member
I've been wondering about the path too and keep coming back to OneDrive. @takeshishen - Since c:\something made no difference maybe try logging in as a different user with a local account... just to eliminate OneDrive as a possibility once and for all.
OneDrive by default only covers user files - %USER%/Documents, /Pictures, /Videos. To include anything else it must be specially configured, and it cannot AFAIK back up the root of an OS drive.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,586
1,868
@V0latyle,@badabing2003 Thank you for your help. I just had time to try again. The same path, and cable. Using PixelFlasher is a success.
Great, thanks for reporting.
This suggests that somewhere along the lines, you did something differently.
You should check the PixelFlasher logs, it shows you everything it did,
see if you can spot a step where you did it differently.
 
  • Like
Reactions: ipdev

Homeboy76

Senior Member
Aug 24, 2012
3,552
2,082
Google Pixel XL
Google Pixel 7 Pro
@V0latyle,@badabing2003 Thank you for your help. I just had time to try again. The same path, and cable. Using PixelFlasher is a success.
This thread does have a link to PixelFlasher for XDA members that are uncomfortable with manually flashing the factory image.

Brief Comments/Discussions/Questions about the PixelFlasher will are ok.

Long Comments/Discussions/Questions about the PixelFlasher that border on Hijacking the thread are NOT ok.

These long Comments/Discussions/Questions about the PixelFlasher must/should be posted on the PixelFlasher thread for the developer @badabing2003, or other knowledgeable experts @V0latyle to Comment on/Discuss/Answer Questions.
 
Last edited:

V0latyle

Forum Moderator
Staff member
This thread does have a link to PixelFlasher for XDA members that are uncomfortable with manually flashing the factory image.

Brief Comments/Discussions/Questions about the PixelFlasher will are ok.

Long Comments/Discussions/Questions about the PixelFlasher that border on Hijacking the thread are NOT ok.

These long Comments/Discussions/Questions about the PixelFlasher must/should be posted on the PixelFlasher thread for the developer @badabing2003, or other knowledgeable experts @V0latyle to Comment on/Discuss/Answer Questions.
Me? An expert? Hardly! Lol

Since @takeshishen had asked for help here, I didn't want to divert his questions to another thread, especially not mine, because I didn't want to give the impression that I'm trying to promote myself
 

Homeboy76

Senior Member
Aug 24, 2012
3,552
2,082
Google Pixel XL
Google Pixel 7 Pro
Me? An expert? Hardly! Lol

Since @takeshishen had asked for help here, I didn't want to divert his questions to another thread, especially not mine, because I didn't want to give the impression that I'm trying to promote myself
I understand you not wanting to divert @takeshishen to your thread. However, the questions were about the PixelFlasher tool and should have been diverted to that thread.
 
Last edited:

badabing2003

Recognized Contributor
Sep 17, 2012
1,586
1,868
This thread does have a link to PixelFlasher for XDA members that are uncomfortable with manually flashing the factory image.

Brief Comments/Discussions/Questions about the PixelFlasher will are ok.

Long Comments/Discussions/Questions about the PixelFlasher that border on Hijacking the thread are NOT ok.

These long Comments/Discussions/Questions about the PixelFlasher must/should be posted on the PixelFlasher thread for the developer @badabing2003, or other knowledgeable experts @V0latyle to Comment on/Discuss/Answer Questions.
To be clear,
I agree 100% , I didn't want to hijack the thread, hence I did one suggestion to try with PF to eliminate potential user error, for that I provided my response in PF thread.
All other back and forth posts here evolved around the manual steps @takeshishen had taken or should take to troubleshoot the error, nothing was PF related.
 
  • Like
Reactions: V0latyle

takeshishen

Member
Jan 2, 2021
12
4
I understand you not wanting to divert @takeshishento your thread. However, the questions were about the PixelFlasher and should have been diverted to that thread.
Sorry, I don't understand the rules of this forum. I don't want to offend it. My question also involves ADB, SDK and Magisk Where should I classify my problems and other people's help? The author mentioned PixelFlasher in the tutorial. Can't I use this software in this topic? I just have confused questions.ADB, SDK, MAGISK, file path, and the cable for brushing. Do they need to be classified one by one?
 

Homeboy76

Senior Member
Aug 24, 2012
3,552
2,082
Google Pixel XL
Google Pixel 7 Pro
To be clear,
I agree 100% , I didn't want to hijack the thread, hence I did one suggestion to try with PF to eliminate potential user error, for that I provided my response in PF thread.
All other back and forth posts here evolved around the manual steps @takeshishen had taken or should take to troubleshoot the error, nothing was PF related.
Not mad at ya! :ROFLMAO:
I too have suggested PixelFlasher, that is why there is a link to it on my thread. :cool:
Your comment on this thread have been helpful.
 
Last edited:

Homeboy76

Senior Member
Aug 24, 2012
3,552
2,082
Google Pixel XL
Google Pixel 7 Pro
Sorry, I don't understand the rules of this forum. I don't want to offend it. My question also involves ADB, SDK and Magisk Where should I classify my problems and other people's help? The author mentioned PixelFlasher in the tutorial. Can't I use this software in this topic? I just have confused questions.ADB, SDK, MAGISK, file path, and the cable for brushing. Do they need to be classified one by one?
No, you should not classify your problems. Yes, you can use Pixel flasher. Brief questions about ADB, SDK, MAGISK and file path are welcome. Long discussions about them are NOT welcome and should be posted on their respective threads or Google searched.

I don't know what cable for brushing is. o_O
 
Last edited:
  • Like
Reactions: Slim2none4u

takeshishen

Member
Jan 2, 2021
12
4
No. Yes you can use Pixel flasher. Brief questions about ADB, SDK, MAGISK and file path are welcome. Long discussions about them are NOT welcome and should be posted on their respective threads or Google searched.

I don't know what cable brushing is. o_O
I'm glad to have solved the problem here and met so many enthusiastic people. This is enough. Have a nice day for all of you. I don't want to continue this topic. Thanks for all your replies!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Anyone know if the boot image is fixed on the new beta? Or do we still need to use the image from the Pixel 7.

    I'm on holiday with no laptop, and don't want to update it it's going to go wrong.
    It looks like it is not.
    1
    Update SafetyNet Fix
    kdrag0n SafetyNet Fix V2.4.0
    This version only supports Zygisk (Magisk 24 and newer).
    1
    It looks like it is not.
    I'm not sure what's happening with the latest Android 13 Beta on the Pixel 6, but your comment to patch and flash the Pixel 7 boot image did the trick for me. I thought I was missing something. But nope, looks like the problem was somewhere else entirely.

    Many thanks! :)
  • 24

    [Guide] Root Pixel 6 with Magisk + Unlock Bootloader + Pass SafetyNet + More
    Android Security Bulletin—January 2023
    Pixel Update Bulletin—January 2023

    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. Use the Android flash tool:
          select Wipe => Force Flash Partitions => Lock Bootloader.
      • Lock Bootloader

        1. If your phone is not 100 percent stock do Return Phone to Stock. If you don't you may 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 (the link to it is in the Important Note(s) 2.) below.

      • 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 the previous factory image was rooted (you used Magisk to patch the boot.img of the previous factory image). Open Magisk manager and disable all Magisk modules.
        3. If you want to update to the Android 13 Factory image without wiping your phone: Do Flash Factory Image Keep Data (below).
        4. Always verify you have the latest version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 6 - oriole.
        5. 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.
        6. 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
            then type
          • fastboot Reboot
        7. If you are uncomfortable manually flashing the factory image. Try PixelFlasher by badabing2003.
          Please post Comments/Discussions/Questions about PixelFlasher on that thread.
        8. Backup your data
        9. Download the latest Factory Image: Pixel 6 - oriole to your Computer.
        10. 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

        • If you are Updating/Upgrading to Android 13. 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)
          * * * S T A R T - E D I T * * *
          @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-aa9a.999999.999.zip
          echo Press any key to exit...
          pause >nul
          exit
          * * * * E N D - Edit * * * *

          Update Android 13
          * * * S T A R T - E D I T * * *
          @Echo off

          PATH=%PATH%;"%SYSTEMROOT%\System32"
          echo Change active slot
          fastboot getvar current-slot
          fastboot --set-active=other
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot getvar current-slot

          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)
          * * * S T A R T - E D I T * * *
          @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 - E D I T * * *
        • After, you have edited the flash-all bat file. 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

      • 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 (oriole-a9a9a.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-oriole-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, 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.
        19. Important, if the Magisk Manager app has the Superuser and Module buttons greyed out:
      • Pass Safety Net with SafetyNet Fix

        1. Download File(s)
        2. Install kdrag0n safetynet-fix-v2.4.0.zip/Displax's safetynet-fix v2.3.1-MOD_2.1.zip
          • Open Magisk
          • Tap Modules icon
          • Tap Install from storage
          • Navigate to the kdrag0n safetynet-fix-v2.4.0.zip/Displax's safetynet-fix v2.3.1-MOD_2.1.zip file you downloaded.
          • Tap the kdrag0n safetynet-fix-v2.4.0.zip/ Displax's safetynet-fix v2.3.1-MOD_2.1.zip 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.
        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.
          • 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.
        4. 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
        5. 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. Google Pixel 6 ROMs, Kernels, Recoveries, & Other
        2. Other Custom Rom
    2. Themes, Apps, and 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