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

Search This thread

badabing2003

Recognized Contributor
Sep 17, 2012
1,348
1,537
Going out of my mind trying to update from SQ3A.220705.003.A3 to the September one (that also means going from A12 to A13) o_O

I've followed the update A13-specific notes: Uninstall Magisk, reboot, then went to System Updates.
The update fails after a short period of time with "Installation problem". I am attaching the full logcat of "update_engine"; here are the ERROR bits:

Code:
09-18 15:19:47.954   954   954 E update_engine: [ERROR:cleanup_previous_update_action.cc(298)] Previous update has not been completed, not cleaning up
09-18 15:19:49.238   954   954 E update_engine: [ERROR:partition_writer.cc(608)] Unable to open ECC source partition boot, file /dev/block/platform/14700000.ufs/by-name/boot_b: Success (0)
09-18 15:19:49.240   954   954 E update_engine: [ERROR:delta_performer.cc(883)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
09-18 15:19:49.242   954   954 E update_engine: [ERROR:delta_performer.cc(888)] Expected:   sha256|hex = A5AB9CBD2E2604C0E98C704EC4F4FFFF20562517D38797F31A6A32F9B7146AF3
09-18 15:19:49.244   954   954 E update_engine: [ERROR:delta_performer.cc(891)] Calculated: sha256|hex = 9B7E9AFFFAE7F57E81A4B116E707E91E02C5A015F553F18E330A8F75B84A9826
09-18 15:19:49.247   954   954 E update_engine: [ERROR:delta_performer.cc(902)] Operation source (offset:size) in blocks: 0:1,5690:339,16383:1
09-18 15:19:49.249   954   954 E update_engine: [ERROR:partition_writer.cc(485)] source_fd != nullptr failed.
09-18 15:19:49.250   954   954 E update_engine: [ERROR:delta_performer.cc(957)] partition_writer_->PerformSourceBsdiffOperation( operation, error, buffer_.data(), buffer_.size()) failed.
09-18 15:19:49.252   954   954 E update_engine: [ERROR:delta_performer.cc(201)] Failed to perform BROTLI_BSDIFF operation 14, which is the operation 0 in partition "boot"
09-18 15:19:49.253   954   954 E update_engine: [ERROR:download_action.cc(222)] Error ErrorCode::kDownloadStateInitializationError (20) in DeltaPerformer's Write method when processing the received payload -- Terminating processing

My guess is my inactive slot "a" contains a different OS version? Pre-0705, I think.

I suspect this because several weeks ago *somehow* even though Automatic System Updates was disabled, the OS attempted to update itself (while still rooted). I came back to a "you've just gotten an update and a reboot" message, and lost root. I re-rooted, and all was well...so I thought.

I'm now very nervous about doing any of the following:
  1. Sideload the September update via adb (there must be a good reason for the automated update to bail, right?)
  2. Switch slots and try booting to see what's actually on there (tried this once, selecting "Turn Off" after setting "a" to active; the phone's power button would NOT power the phone on; thankfully plugging in the USB cable did; phone booted to slot "b", though)
  3. Reflashing the A12 Magisk-patched "master root" image to slot "b", for fear of bricking the phone via A12-to-A13 bootloader compatibility.
Any help on next possible steps is appreciated. I've been rooting and manually updating Android phones for years, but man does it feel like it's getting trickier and riskier :confused:
I suspect that you are still on A12?, if you are on A13, then whatever you do, do not attempt your 3rd option, ie reflash A12, you could end up bricking your device.

The reason it wouldn't update is because it felt that it was tempered with or not what it was expecting.
Code:
The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.

At this point I think the best option is to flash_all.bat factory image, with -w removed (see OP).

if you are on A13, or upgrade to A13, make absolutely certain that you flash the bootloader (not the same as boot.img) to both slots, see this thread.

Feel free to ask specific questions or anything that is not clear.
 
  • Like
Reactions: Homeboy76

Homeboy76

Senior Member
Aug 24, 2012
3,434
1,990
Google Pixel XL
Google Pixel 7 Pro
Going out of my mind trying to update from SQ3A.220705.003.A3 to the September one (that also means going from A12 to A13) o_O

I've followed the update A13-specific notes: Uninstall Magisk, reboot, then went to System Updates.
The update fails after a short period of time with "Installation problem". I am attaching the full logcat of "update_engine"; here are the ERROR bits:

Code:
09-18 15:19:47.954   954   954 E update_engine: [ERROR:cleanup_previous_update_action.cc(298)] Previous update has not been completed, not cleaning up
09-18 15:19:49.238   954   954 E update_engine: [ERROR:partition_writer.cc(608)] Unable to open ECC source partition boot, file /dev/block/platform/14700000.ufs/by-name/boot_b: Success (0)
09-18 15:19:49.240   954   954 E update_engine: [ERROR:delta_performer.cc(883)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
09-18 15:19:49.242   954   954 E update_engine: [ERROR:delta_performer.cc(888)] Expected:   sha256|hex = A5AB9CBD2E2604C0E98C704EC4F4FFFF20562517D38797F31A6A32F9B7146AF3
09-18 15:19:49.244   954   954 E update_engine: [ERROR:delta_performer.cc(891)] Calculated: sha256|hex = 9B7E9AFFFAE7F57E81A4B116E707E91E02C5A015F553F18E330A8F75B84A9826
09-18 15:19:49.247   954   954 E update_engine: [ERROR:delta_performer.cc(902)] Operation source (offset:size) in blocks: 0:1,5690:339,16383:1
09-18 15:19:49.249   954   954 E update_engine: [ERROR:partition_writer.cc(485)] source_fd != nullptr failed.
09-18 15:19:49.250   954   954 E update_engine: [ERROR:delta_performer.cc(957)] partition_writer_->PerformSourceBsdiffOperation( operation, error, buffer_.data(), buffer_.size()) failed.
09-18 15:19:49.252   954   954 E update_engine: [ERROR:delta_performer.cc(201)] Failed to perform BROTLI_BSDIFF operation 14, which is the operation 0 in partition "boot"
09-18 15:19:49.253   954   954 E update_engine: [ERROR:download_action.cc(222)] Error ErrorCode::kDownloadStateInitializationError (20) in DeltaPerformer's Write method when processing the received payload -- Terminating processing

My guess is my inactive slot "a" contains a different OS version? Pre-0705, I think.

I suspect this because several weeks ago *somehow* even though Automatic System Updates was disabled, the OS attempted to update itself (while still rooted). I came back to a "you've just gotten an update and a reboot" message, and lost root. I re-rooted, and all was well...so I thought.

I'm now very nervous about doing any of the following:
  1. Sideload the September update via adb (there must be a good reason for the automated update to bail, right?)
  2. Switch slots and try booting to see what's actually on there (tried this once, selecting "Turn Off" after setting "a" to active; the phone's power button would NOT power the phone on; thankfully plugging in the USB cable did; phone booted to slot "b", though)
  3. Reflashing the A12 Magisk-patched "master root" image to slot "b", for fear of bricking the phone via A12-to-A13 bootloader compatibility.
Any help on next possible steps is appreciated. I've been rooting and manually updating Android phones for years, but man does it feel like it's getting trickier and riskier :confused:
At the point you are at now, following @badabing2003 advice (Post 361) is the best thing you can do:
OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~..., 2. Install/Update Factory Image keep data, wipe data... Then you should read all of the Important Note(s):, before proceeding to • Flash Factory Image Keep Data.
 
Last edited:

HypromanGT

Member
Jan 8, 2011
6
6
I suspect that you are still on A12?
Yes, I am still on A12, specifically SQ3A.220705.003.A3.

At this point I think the best option is to flash_all.bat factory image, with -w removed (see OP).
OK, I'll give that a shot, thank you.

One question, though: I'm assuming I should be flashing the latest (A13, September) factory image, and not (re-)flashing the one I am currently on? (Probably a dumb question, but I've lost a fair amount of confidence at this point)

The simplist way to upgrade to Android 13 from Android 12. Would have been to follow the instructions in the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~..., 2. Install/Update Factory Image keep data, wipe data... Which includes a link to Pixel Flasher
Then you should have read all of the Important Note(s):, before proceeding to • Flash Factory Image Keep Data.

However, at the point you are at now, follow ing @badding advice is the best thing you can do.
Noted!
FWIW, I was following your post #319 regarding Steps For Installing the OTA Update which is what I was looking to do.

Thank you both for your help!
 
  • Like
Reactions: Homeboy76

badabing2003

Recognized Contributor
Sep 17, 2012
1,348
1,537
One question, though: I'm assuming I should be flashing the latest (A13, September) factory image, and not (re-)flashing the one I am currently on? (Probably a dumb question, but I've lost a fair amount of confidence at this point)
Yes you can use the latest A13, unless for whatever reasons you don't want that.
Keep in mind that once you go to A13, you can't go back to A12 (at least not without issues)
I'm personally on A13 and am happy with it.

I was following your post #319 regarding Steps For Installing the OTA Update

I personally never go the OTA route, I find factory image path more reliable and honestly faster too.
 

HypromanGT

Member
Jan 8, 2011
6
6
Yes you can use the latest A13, unless for whatever reasons you don't want that.
Keep in mind that once you go to A13, you can't go back to A12 (at least not without issues)
I'm personally on A13 and am happy with it.
Flashing latest A13 factory images (no wipe) to both slots worked. Thank you so much!! 🙇‍♂️

One small note/correction: The instructions call for adding "-- skip-reboot" to the first image flash command in flash-all.bat. It looks like the space in between the double-dash and "skip" is unintentional.

I personally never go the OTA route, I find factory image path more reliable and honestly faster too.
This was my first time trying to let the OS perform the OTA, actually. I had no issues manually sideloading them to the Pixel 2 XL in the past, but I'll definitely be using the factory images going forward 🙃
 
  • Like
Reactions: badabing2003

Homeboy76

Senior Member
Aug 24, 2012
3,434
1,990
Google Pixel XL
Google Pixel 7 Pro
Thank you for a great and comprehensive guide.

I don't understand why the guide makes you install both:
In fact, the mod by Displax is a fork of the other repository, and includes the full functionality. It works on its own. I also tested it with a Pixel 6a.
Please check the edited instruction in the OP:
~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~...
5. Root/Reroot with Magisk and Pass SafetyNet
Pass Safety Net with SafetyNet Fix
 
Last edited:

Homeboy76

Senior Member
Aug 24, 2012
3,434
1,990
Google Pixel XL
Google Pixel 7 Pro
Sorry for cuestion, what are the steps to update A13 stable to A13 beta and keep root?
I don't know what the steps are to update A13 stable to A13 beta and keep root.

The recommended way to flash Android 13 QPR1 Beta to a Pixel device is to use Android Flash Tool.

I'm guessing going from Android 13 to Android 13 QPR1 Beta will require wiping your phone.

My suggestion is to follow the linked installation instructions in the OP:
~ ~ ~ Part I - INFORMATION ~ ~ ~
4. NEW
Android 13 Beta QPR1 Program for the Google Pixels 4a5(G)/5/5a/6/6Pro/6a
1. Factory Images
Link
2. OTA Images
Link
 
Last edited:

Tone Capone

Senior Member
Dec 21, 2010
65
6
Hoping someone can help. Just bought a used Google 6. It had 13 installed. After booting into it a couple of times, I checked the current slot and it was 'a'. Using fastboot, I flashed the 13 bootloader to slot 'b'. Then I used the edited flash-all.bat file as suggested in the OP. It gave me something about a 'sparse' error at the end. I cannot boot to system. The Google logo comes up but after about 10 seconds goes back to Bootloader. I have tried changing slots and booting to system, but same result.

I checked and rechecked the hash and it matches what is on the Google Factory Images for the Pixel 6.

Please help!
 

Homeboy76

Senior Member
Aug 24, 2012
3,434
1,990
Google Pixel XL
Google Pixel 7 Pro
Hoping someone can help. Just bought a used Google 6. It had 13 installed. After booting into it a couple of times, I checked the current slot and it was 'a'. Using fastboot, I flashed the 13 bootloader to slot 'b'. Then I used the edited flash-all.bat file as suggested in the OP. It gave me something about a 'sparse' error at the end. I cannot boot to system. The Google logo comes up but after about 10 seconds goes back to Bootloader. I have tried changing slots and booting to system, but same result.

I checked and rechecked the hash and it matches what is on the Google Factory Images for the Pixel 6.

Please help!
When you go to settings => About phone what is the Build number on your phone?

I'm assuming three things:
  1. You have the latest version of SDK Platform-tools installed on your computer.
  2. You downloaded the latest, applicsble, factory image and extracted it:

    13.0.0 (TP1A.220905.004, Sep 2022) b7d576f50b9e27b753c18a9ed70669d9cbd212bb01db121de959d48cfe448e67
    or
    13.0.0 (TP1A.220905.004.A1, Sep 2022, Verizon, Verizon MVNOs) 8b8585b24193e41f7f1480cef89311a912a751d4e60b6cac97264fe8fd6dcc4b
  3. You can boot the bootloader .
If my assumptions are correct try this:
  1. Boot the bootloader
  2. Open a Command Prompt at the command prompt type: adb wait-for-device shell magisk --remove-modules
  3. Then type: fastboot Reboot
  4. Go to the OP and do ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~...,2. Install/Update Factory Image keep data,, wipe data..., • Flash Factory Image Keep Data
    Note: Don't forget to read the • Important Notes
 
  • Like
Reactions: Tone Capone

Tone Capone

Senior Member
Dec 21, 2010
65
6
When you go to settings => About phone what is the Build number on your phone?

I'm assuming three things:
  1. You have the latest version of SDK Platform-tools installed on your computer.
  2. You downloaded the latest, applicsble, factory image and extracted it:

    13.0.0 (TP1A.220905.004, Sep 2022) b7d576f50b9e27b753c18a9ed70669d9cbd212bb01db121de959d48cfe448e67
    or
    13.0.0 (TP1A.220905.004.A1, Sep 2022, Verizon, Verizon MVNOs) 8b8585b24193e41f7f1480cef89311a912a751d4e60b6cac97264fe8fd6dcc4b
  3. You can boot the bootloader .
If my assumptions are correct try this:
  1. Boot the bootloader
  2. Open a Command Prompt at the command prompt type: adb wait-for-device shell magisk --remove-modules
  3. Then type: fastboot Reboot
  4. Go to the OP and do ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~...,2. Install/Update Factory Image keep data,, wipe data..., • Flash Factory Image Keep Data
    Note: Don't forget to read the • Important Notes
When I first got the phone yesterday, I checked the build and it was the 13.0.0 TP1A.220905.004
1. Latest version of SDK tools installed
2. The non-verizon image was downloaded (verified checksum)
3. The only thing I can do is boot the bootloader currently
Previously, I had booted into the OS about 4 times without issue. I wanted to make sure both slots had the new boot loader.
The phone was not rooted and had a locked bootloader. I unlocked the boot loader and proceeded to try and flash the other slot (b) with the boot loader. Once that was done and verified, I proceeded with the Edited Flash-All as mentioned in the OP.

ADB does not currently list any devices. But fastboot commands work. ADB debugging was checked off when I started.

It will not boot into the OS...says something about the device being corrupted and may not work properly. Then it just goes back to bootloader. That's where I am stuck.

I have no idea how to fix it.
 

Lughnasadh

Senior Member
Mar 23, 2015
4,346
4,855
Google Nexus 5
Huawei Nexus 6P
When I first got the phone yesterday, I checked the build and it was the 13.0.0 TP1A.220905.004
1. Latest version of SDK tools installed
2. The non-verizon image was downloaded (verified checksum)
3. The only thing I can do is boot the bootloader currently
Previously, I had booted into the OS about 4 times without issue. I wanted to make sure both slots had the new boot loader.
The phone was not rooted and had a locked bootloader. I unlocked the boot loader and proceeded to try and flash the other slot (b) with the boot loader. Once that was done and verified, I proceeded with the Edited Flash-All as mentioned in the OP.

ADB does not currently list any devices. But fastboot commands work. ADB debugging was checked off when I started.

It will not boot into the OS...says something about the device being corrupted and may not work properly. Then it just goes back to bootloader. That's where I am stuck.

I have no idea how to fix it.
Try using Android Flash Tool since fastboot commands work.
Also, make sure you have the latest drivers installed (assuming you are using Windows) and use an A to C cable with a USB 2.0 port.
 

Tone Capone

Senior Member
Dec 21, 2010
65
6
Try using Android Flash Tool since fastboot commands work.
Also, make sure you have the latest drivers installed (assuming you are using Windows) and use an A to C cable with a USB 2.0 port.
Strangely enough, it worked. I can't say I understand what could have been different other than it did not use my downloaded image (with a verified hash).

Thanks soooooo much for the suggestion to use the flash tool...I had never used it!
 

[email protected]

Senior Member
Aug 16, 2010
71
5
Luzern CH
Hi Guys
this method can help Boot Failure as below picture, after reboot will back always to fastboot
download.jpg
 

Top Liked Posts

  • There are no posts matching your filters.
  • 24
    [Guide] Root Pixel 6 with Magisk + Unlock Bootloader + Pass SafetyNet + More
    Android Security Bulletin—November 2022
    Pixel Update Bulletin—November 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

      • @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 (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 you are uncomfortable mannually flashing the factory image. Try PixelFlasher by @badabing2003.
          Please post Comments/Discussions/Questions about the PixelFlasher on that thread.
        3. 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).
        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
          • fastboot Reboot
        7. Backup your data
        8. Download the latest Factory Image: Pixel 6 - oriole to your Computer.
        9. 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)
          * * * 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.
      • @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 (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 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 Displax/safetynet-fix-v2.3.1-MOD_2.0.zip
          • Open Magisk
          • Tap Modules icon
          • Tap Install from storage
          • Navigate to the Displax/safetynet-fix-v2.3.1-MOD_2.0.zip file you downloaded
          • Tap the Displax/safetynet-fix-v2.3.1-MOD_2.0.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.
          • 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.
        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. Alpha/Beta

          • Waiting...
        2. Official

          • Waiting...
        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