How To Guide [Guide] [January 3, 2024] Root Pixel 6 Unlock Bootloader + Pass SafetyNet + Both Slots Bootable + More

Search This thread
By:
Advanced…
B

Binary Assault

Senior Member
May 25, 2016
524
118
OnePlus 8 Pro
OnePlus 9
Homeboy76 said:
when I asked did you patch the May 2022 boot.img with Magisk Canary 24306.

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

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

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

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

magisk --remove-modules from an adb shell should do it.
Click to expand...
Click to collapse
Thank you
 
J

Jammo2k5

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

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

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

Homeboy76

Recognized Contributor
Aug 24, 2012
4,200
2,728
Google Pixel 8 Pro
Jammo2k5 said:
Hey quick question. Is there a reason why step 16 of Root/Re-root is Flash the boot image directly and not use
Code: 
fastboot boot magisk_patched-{XXXX}.img
and then using magisk manager to install magisk directly?

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

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

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

Yes, the phones have boot looped.

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

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

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

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

Jammo2k5

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

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

Yes, the phones have boot looped.

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

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

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

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

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

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

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

Homeboy76

Recognized Contributor
Aug 24, 2012
4,200
2,728
Google Pixel 8 Pro
Jammo2k5 said:
With my recent attempts, once the device has boot looped so many times it will refuse to boot with a device corrupt message even if I flash the stock boot.img. I had to flash the entire ROM with the -flag disabled to recover the device.
Saying bricked was the wrong phrasing for that.

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

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

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

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

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

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

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

humb13

Senior Member
Nov 24, 2016
75
21
Hey guys,

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

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

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

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

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

Thanks for your help.
 
H

Homeboy76

Recognized Contributor
Aug 24, 2012
4,200
2,728
Google Pixel 8 Pro
humb13 said:
Hey guys,

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

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

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

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

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

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

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

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

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

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


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

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


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

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

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

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

mhrussell1

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

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

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

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

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

Mark
 
J

jbofc

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

mhrussell1

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

Similar threads

V0latyle
How To Guide [GUIDE] Pixel 6 "oriole": Unlock Bootloader, Update, Root, Pass SafetyNet
Replies
1K
Views
149K
V0latyle
V0latyle
L
How To Guide Sim unlock tmobile pixel 6
Replies
239
Views
88K
K
Kel Ghu
H
How To Guide Converting Japanese Pixel 6 to Global version
Replies
223
Views
86K
Y
yasinkhan1438
badabing2003
Themes / Apps / Mods 📳🔥PixelFlasher for Google Pixel 6 Support Thread.
Replies
714
Views
62K
badabing2003
badabing2003
V0latyle
  • Sticky
General PSA: Pixel 6 Bootloader Anti-Rollback
Replies
124
Views
56K
V0latyle
V0latyle

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 30
    H
    Homeboy76

    [Guide] [January 3, 2024] Root Pixel 6 Unlock Bootloader + Pass SafetyNet + Both Slots Bootable + More
    Android Security Bulletin—January 2024
    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.
      • If you choose to use a Custom Kernels, Custom ROM, etc. You should read the Installation Instructions in their thread before using this guide or attempting to install them. Additionally, 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 them
        .
    2. Prerequisites

    3. NEW

      • Android 14 Beta QPR2 are up.
        Builds (Factory/OTA) are available for the following Pixel devices:
        1. Google Pixel 5a
        2. Google Pixel 6 and 6 Pro
        3. Google Pixel 6a
        4. Google Pixel 7 and 7 Pro
        5. Google Pixel 7a
        6. Google Pixel Fold
        7. Google Pixel Tablet
        8. Pixel 8 and 8 Pro
    4. Update(s)

    5. My Other Guides
    6. Credits/Thanks/Recognitions

      • @topjohnwu - Magisk.
      • @badabing2003 - Creating Pixel Flasher, discovering how to make both slots bootable, and for his many helpful contributions to this thread.
      • @Lughnasadh - for testing badabing2003 make both slots bootable, and his many helpful contributions to this thread.
      • @Shoey - for discovering and testing patching the boot.img using the image...zip file extracted from the Google Factory image file and Magisk.
    ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~
    (The Instructions listed below are not steps, they are individual sets of instructions for the Pixel 6.)
    1. (NEW) PREVENT/FIX BOOT LOOPS

      • Prevent Boot Loops
        1. Before you patch the init_boot.img: Open the Magisk app and disable all Magisk modules.
          • If you hid the Magisk app, the default name for a hidden Magisk app is settings.
          • If you changed the hidden name to something else and have forgotten it. Use TB checker to find the name of the hidden Magisk Manager:
            1. Open the TB Checker app
            2. Tap Run Xposed check
            3. Scroll down to Magisk Random Package Name: to see Magisk's hidden name.
        2. Check for more than one installation of Magisk app: Use TB Checker
      • Fix Boot Loops
        1. Flash the 'stock' init_boot.img to both slots to remove root: fastboot flash init_boot init_boot.img --slot all
        2. Boot Safe Mode while booting to remove Magisk Modules:
          • When booting, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode.
          • Then reboot and magisk modules should be disabled. (Thanks @Lughnasadh)
        3. Use adb shell command, to remove Magisk Modules
          • Press the Power button until the phone turns off.
          • Press the Power and Volume Down to boot fastboot mode.
          • Open a Command Prompt in the Platform-tools folder or the folder that has adb.exe and fastboot.exe in it, and type adb wait-for-device shell magisk --remove-modules. When it finishes type fastboot Reboot
    2. 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.
    3. Manually Install/Update Factory Image keep data or wipe data

      • Before you start:

        1. If you haven't updated your phones Factory image in a while. It is not necessary to flash all the missed images in succession. Flash the latest Factory image.
        2. If your phone was previously rooted, open Magisk manager and disable all Magisk modules. If you hid the Magisk manager app the default name for the hidden Magisk app is settings.
        3. Always verify you have the latest working version of SDK Platform-Tools installed on your computer.
        4. If you get an errorwhile flashing, try one of these options:
          • Change the USB port to a non charging USB port.
          • Change the USB cord.
          • Change Computers.
        5. If your phone boot loops try one of the following options:
          • Flash the 'stock' init_boot.img to both slots to remove root: fastboot flash init_boot init_boot.img --slot all
          • Boot Safe Mode while booting to remove Magisk Modules
            1. When booting, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode.
            2. Then reboot and magisk modules should be disabled. (Thanks Lughnasadh)
          • Boot fastboot mode Mode By turning phone off to remove Magisk Modules
            1. Press the Power button until the phone turns off.
            2. Press the Power and Volume Down to boot fastboot mode.
            3. Open a Command Prompt in the 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
        6. Backup your data
        7. Download the latest Factory Image: Pixel 6 - oriole to your Computer.
        8. Extract files from the Factory Image

          • Extract the Factory Image file (oriole-a9a9a.999999.999-factory-99a9a99a.zip) to a folder.
          • Open the folder you extracted the Factory image to, the bootloader...img; flash-all.bat; image...zip; and radio...img files are in this folder. Extract the image-oriole-aa9a.999999.999.zip file to a folder. Open the folder you extracted the image-oriole-aa9a.999999.999.zip file to, the boot.img is in this folder. file should be in this folder.
        9. Copy/Move the bootloader...img; image...zip; and radio...img and boot.img files to your computer's Platform-tools folder, the folder that has fastboot.exe in it.
      • Flash Factory Image Keep Data

        1. Updating/Upgrading Android 14
          Note:           If you are Upgrading your Android Version, It is a good idea to flash the bootloader to both slots (A & B).
          ~ E D I T - flash-all.bat file ~

          @Echo off
          PATH=%PATH%;"%SYSTEMROOT%\System32"
          fastboot set_active other
          fastboot reboot-bootloader
          fastboot flash bootloader --slot all bootloader-oriole-aaaaaa-9.9-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot flash radio radio-oriole-a9999a-999999-999999-a-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot update image-oriole-aa9a.999999.999.zip

          echo Press any key to exit...
          pause >nul
          exit
          ~ END EDIT - flash-all.bat file ~
        2. After, you have edited the flash-all.bat file, copy/Move it to your computer's platform-tools folder.
        3. Boot fastboot mode (Power off the phone => Press the Power and Down buttons until you see Start)
        4. Connect your phone to the computer.
        5. Open a Command Prompt on your computer in the platform-tools folder and type: flash-all at the Command Prompt and press enter.
        6. The phone will reboot when flashing is completed.
        7. Go-to Part II - INSTRUCTIONS, 6. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
      • Flash Factory Image Wipe Data

        1. This will wipe your phone's Data/Internal Storage.
        2. Do not edit the flash-all.bat file,
        3. Boot fastboot mode (Power off the phone => Press the Power and Down buttons until you see Start)
        4. Connect your phone to the computer.
        5. Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
        6. The phone will reboot when flashing is completed.
        7. Go-to Part II - INSTRUCTIONS, 6. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
      • Some kernels require Disabling verity and verification

        1. If you need to disable Verity and Verification. Edit the flash-all.bat file, to disable Verity and Verification.
          ~ Edit - flash-all.bat file ~

          @Echo off
          PATH=%PATH%;"%SYSTEMROOT%\System32"
          fastboot --set-active=other
          fastboot reboot-bootloader
          fastboot flash bootloader bootloader-oriole-aaaaaa-9.9-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot flash radio radio-oriole-a99999-999999-999999-a-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot - w update --disable-verity --disable-verification image-oriole-aa9a.999999.999.a9.zip
          echo Press any key to exit...
          pause >nul
          exit
          ~ ~ ~ END EDIT ~ ~ ~
        2. Notes:
          • The first time you Disable Verity and Verification it will wipe your Data/Internal Storage.
          • When doing subsequent updates and disabling Verity and Verification, the -w flag can be removed to Keep Data.
          • Once you start Disabling Verity and Verification you should continue doing it. If you skip disabling one time. The next time you Disable Verity and Verification it will wipe your phone.
        3. Copy/Move the edited flash-all.bat file to the platform-tools folder on your computer.
        4. Boot fastboot mode (Power off the phone => Press the Power and Down buttons until you see Start)
        5. Connect your phone to the computer.
        6. Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
        7. The phone will reboot when flashing is complete.
        8. Go-to Part II - INSTRUCTIONS, 7. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
      • Setup phone

        1. Enable Developer Mode
          • Open Setup => About phone => Tap Build number 7 times or until you see you are a 'Devloper'.
        2. Enable Developer Opitions
          • Open Setup => System => Developer options => Enable Developer options
    4. Manually Install/update the OTA image keep data and root/re-root your phone

      • Before you start:

        1. If you haven't updated your phones OTA image in a while. It is not necessary to flash all the missed OTA images in succession. Flash the latest OTA image.
        2. If your phone was previously rooted, open Magisk manager and disable all Magisk modules. If you hid the Magisk manager app the default name for the hidden Magisk app is settings.
        3. Always verify you have the latest working version of SDK Platform-Tools installed on your computer.
        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 your phone boot loops try one of the following options:
          • Flash the 'stock' boot.img to both slots to remove root: fastboot flash boot boot.img --slot all
          • Boot Safe Mode while booting to remove Magisk Modules
            1. When booting, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode.
            2. Then reboot and magisk modules should be disabled. (Thanks Lughnasadh)
          • Boot fastboot mode by turning phone off to remove Magisk Modules
            1. Press the Power button until the phone turns off.
            2. Press the Power and Volume Down to boot fastboot mode.
            3. Open a Command Prompt in the 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
        6. Backup your data
        7. Download files to your phone
        8. Extract the image-oriole-aa9a.999999.999.zip file from the Factory Image.

          • Extract the Factory Image file (oriole-a9a9a.999999.999-factory-99a9a99a.zip) to a folder.
          • Open the folder you extracted the Factory image to, the image-oriole-aa9a.999999.999.zip file should be in this folder.
        9. Copy/Move the image-oriole-aa9a.999999.999.zip file and the oriole-ota-aa9a.999999.999-aaaa9999.zip to your computer's Platform-tools folder, the folder that has adb.exe in it.
      • Patch the boot.img

        1. Open Magisk (next to Magisk)
        2. Tap Install
        3. Tap Select and patch a file
        4. Navigate to the image-oriole-aa9a.999999.999.zip file
        5. Tap it then tap the check mark (✓)
        6. Tap Lets go
        7. When you see done the boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.
        8. Tap the disc icon (upper right corner) to save the log file.
        9. Reboot
        10. Copy/Move the magisk_patched_xxxxxx.img file to your computer's Platform-tools folder, the folder that has fastboot.exe in it:
          1. Copy it to a USB drive and transfer it to your computer.
          2. Move it to your computer using adb push
      • Sideload the Google OTA image file and Root it

        1. With the device powered on, booted, USB debugging enabled, and the phone connected to the computer. Type adb reboot sideload
        2. Type:
          adb sideload oriole-ota-aa9a.999999.999-aaaa9999.zip at the command prompt and press Enter.
        3. When side loading the OTA image finishes, you should see this:
          • On your computer,
            C:\platform-tools (location of folder with adb and OTA image in it)>adb sideload oriole-ota-up1a.999999.999-9a99a999.
            Total xfer: 2.00x
            C:\platform-tools>
          • On your phone, ...status 0
        4. Type adb reboot bootloader at the command prompt and press Enter.
      • Root this slot - Flash the Magisk_patched....img

        1. Type: fastboot flash boot magisk_patched-99999_aA99a.img at the command prompt and press Enter.
        2. When it finishes flashing, type fastboot reboot at the command prompt and press Enter.
        3. Disconnect the phone from the computer.
        4. Note: This slot is bootable and rooted.
    5. Make Both Slots Bootable: Manually, Flash the OTA Image to Both Slots - One bootable and rooted, the other slot bootable without root.

      • Before you start

        1. On the Phone
          • Backup your data
          • Enable Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer.
          • Enable USB Debugging: Tap Settings > System > Advanced > Developer Options. Enable USB Debugging.
          • Make sure that there is no pending OTA update, by going to Settings > About phone > System updates, which should say Your system is up to date.
          • Download files
            1. The latest Factory Image: Pixel 6 - oriole
            2. The latest OTA Image: Pixel 6 - oriole
            3. Verify the checksum of the Factory and OTA images. The last portion of the filename is the first 8 digits of its SHA-256 checksum; the full SHA-256 checksum is shown next to the download link.
          • Extract the image-oriole-aa9a.999999.999.zip file from the Factory Image.

            1. Extract the Factory Image file (oriole-a9a9a.999999.999-factory-99a9a99a.zip) to a folder.
            2. Open the folder you extracted the Factory image to, the image-oriole-aa9a.999999.999.zip file should be in this folder.
          • Copy/Move the image-oriole-aa9a.999999.999.zip file and the oriole-ota-aa9a.999999.999-aaaa9999.zip to your computer's Platform-tools folder, the folder that has adb.exe in it.
          • Patch the boot.img:

            1. Note: Before patching the boot.img disable all Magisk modules.
            2. Open the Magisk (Alpha/Beta/Canary/Delta/Stable) App and set the Update Channel to the version of Magisk app you installed.
            3. Open Magisk (next to Magisk)
            4. Tap Install
            5. Tap Select and patch a file
            6. Navigate to the image-oriole-aa9a.999999.999.zip file
            7. Tap it then tap the check mark (✓)
            8. Tap Lets go
            9. When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img), and is stored in the download folder.
            10. Tap the disc icon (upper right corner) to save the log.
            11. Tap Reboot
          • Copy/Move the magisk_patched....img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it.
          • Connect the phone to the computer.
        2. On your Computer
          • Open a Command Prompt in the Platform-tools folder.
      • (Optional): Verify your computer sees your device.

        1. With the device powered on, booted, USB debugging enabled, and the phone connected to the computer.
          Note: If you see the Allow USB Debugging prompt, on your phone, Tap Allow.
        2. Type adb devices at the command prompt and press Enter. You should see your device's serial number.
      • Sideload the Google OTA image file

        1. With the device powered on, booted, USB debugging enabled, and the phone connected to the computer.
          Note: If you see the Allow USB Debugging prompt, on your phone, Tap Allow.
        2. Type adb reboot sideload at the command prompt and press Enter.
        3. Type: adb sideload oriole-ota-aa9a.999999.999-aaaa9999.zip at the command prompt and press Enter.
        4. When side loading the OTA image finishes, you should see this:
          • On your computer,
            C:\platform-tools (location of folder with adb and OTA image in it)>adb sideload oriole-ota-up1a.999999.999-9a99a999.
            Total xfer: 2.00x
            C:\platform-tools>
          • On your phone, ...status 0
        5. Type adb reboot at the command prompt and press Enter.
        6. Note: This slot is bootable and not rooted
      • Sideload the Google OTA image file to the other slot and Root it.

        1. Type adb reboot sideload at the command prompt and press Enter
        2. Type:
          adb sideload oriole-ota-aa9a.999999.999-aaaa9999.zip at the command prompt and press Enter.
        3. When sideloading finishes, type adb reboot bootloader at the command prompt and press Enter.
          Root this slot - Flash the Magisk_patched....img
        1. Type: fastboot flash boot magisk_patched-99999_aA99a.img at the command prompt and press Enter.
        2. When it finishes flashing, type fastboot reboot at the command prompt and press Enter.
        3. Disconnect the phone from the computer.
        4. Note: This slot is bootable and rooted.
        5. Done! :)
    6. Extract files from the Factory Image

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

      • Android 14

        • Upgrade to Android 14: OP, Part II - INSTRUCTIONS, 2., 3., or 4.
      • Patching the boot.img - to root/reroot.

        1. Important Notes
          • If your phone was previously rooted, DO NOT repeat DO NOT install another Magisk Manager app. Do this before you patch the boot.img:
            1. Open the Magisk Manager app and disable all Magisk modules.
            2. If you hid the Magisk manager app the default name for the hidden Magisk app is settings. If you gave it a different name and you've forgotten the name. Use TB checker to find the name of the hidden Magisk Manager:
              • Open the TB Checker app
              • Tap Run Xposed check
              • Scroll down to Magisk Random Package Name: to see Magisk's hidden name.
                You can also use TB Checker to check if you have more than one Magisk Manager app installed.
          • If your phone boot loops try one of the following options:
            • Flash the 'stock' boot.img to both slots to remove root: fastboot flash boot boot.img --slot all
            • Remove Magisk Modules
              1. Boot Safe Mode
                • When booting, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode.
                • Then reboot and magisk modules should be disabled. (Thanks Lughnasadh)
              2. Command Prompt
                • Press the Power button until the phone turns off.
                • Press the Power and Volume Down to boot fastboot mode.
                • Open a Command Prompt in the Platform-tools folder or the folder that has adb.exe in it, and type adb wait-for-device shell magisk --remove-modules
                • fastboot Reboot.
          • If the Magisk Manager app has the Superuser and Module buttons grayed out: Read @badabing2003 post
        2. Extract the image-oriole-aa9a.999999.999.zip file from the Factory Image and Patch the boot.img file.
          • Download the latest Factory image to your phone.
          • Extract the Factory Image file (oriole-a9a9a.999999.999-factory-99a9a99a.zip) to a folder.
          • Open the folder you extracted the Factory image to, the Image file (image-oriole-aa9a.999999.999.zip) file should be in this folder.
        3. Install Magisk Manager App Beta, Canary, or Stable
        4. Open Magisk Manager App
        5. Tap the Settings icon, tap Update Channel, and set the version to the version you Installed.
        6. Tap the back arrow (<--) at the top next to Settings
        7. Tap Install, top right corner next to Magisk
        8. Tap, Select and Patch a File
        9. Select the image-oriole-aa9a.999999.999.zip file you extracted from the latest factory image.
        10. Tap the ✓ (Check Mark)
        11. Tap Let's Go
        12. When you see done the boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.
        13. Tap the disc icon (upper right corner) to save the log file.
        14. Reboot
        15. Copy/Move the magisk_patched_xxxxxx.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
        16. Boot fastboot mode
        17. Connect the phone to the Computer with USB cord.
        18. Open a Command Prompt in the Platform-tools folder.
        19. Type fastboot flash boot "magisk_patched...img" (name of patched.img file) without the quote marks at the Prompt and press enter.
        20. Type fastboot reboot at the Prompt and press enter.
      • Pass Safety Net with SafetyNet Fork

        1. Download File(s)
        2. Install osm0sis PlayIntegrityFork
          • Open Magisk
          • Tap Modules icon
          • Tap Install from storage
          • Navigate to the osm0sis PlayIntegrityFork file you downloaded.
          • Tap the osm0sis PlayIntegrityFork file.
          • When you see the confirmation screen, tap Ok.
          • After it installs tap the Disc 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.
          • (Optional) Scroll down to Superuser and Enable Biometric Authentication.
        4. Get Device Certified
          • Flash the osm0sis PlayIntegrityFork module in Magisk
          • Turn Airplane mode on
          • Open Settings
          • Tap Apps & notifications
          • Tap see all...
          • Tap three dot menu
          • Tap Show system
          • Scroll to Google Wallet/Play Store/Play Services
          • Clear Google Wallet cache (if you have it)
          • Clear Google Play Store cache and data
          • Clear Google Play Services (com.google.android.gms) cache and data (Optionally skip clearing data and wait some time, ~24h, for it to resolve on its own)
          • Turn Airplane mode Off
          • Reboot
        5. Check Device Certification
          • Note: If after completeting Get Device Certified your device is not certifed or your device is certified but certain apps (Google Pay, NetFliks, etc.) are not working. Do this to verify you are passing Play Integrity.
            1. Open Google Play Store app
            2. Tap your profile icon (top right corner)
            3. Tap Settings.
            4. Open the About menu
            5. Tap the row labeled Play Store version seven times to unlock developer mode.
            6. Tap the back arrow (upper left corner)
            7. Tap your profile icon (top right corner)
            8. Tap Settings.
            9. Open the General menu
            10. Tap Developer options
            11. Tap Check integrity
            12. If you see Basic Integrity and Device Integrity, you're passing Play integrity.
    8. 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!
    9. Install/Update Magisk Modules

    10. 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.
    11. 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.
    12. ADB Sideload

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

      • Need help with a Custom ROM?

        1. If you are trying to install a Custom ROM, read and follow the Installation Instructions in the OP of the Custom ROM thread.
        2. If you have questions, search the thread of the Custom ROM you are trying to install for answer(s)/solution(s) to your question(s)/problem(s)[/B]: 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.
        3. Try installing it with 📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones..
        4. 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 Kernel, Magisk, etc. you want to install for installation instructions, and answer(s)/solution(s) to your question(s)/problem(s) about the Custom Kernel, Magisk, etc. 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 Kernel, Magisk, etc.) thread.
      • ROMs
    2. Themes, Apps, and Mods
    3. T.W.R.P. Backup/Restore

      • Waiting for Android 14 T.W.R.P.
    View
    5
    H
    Homeboy76
    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.
    View
    5
    Lughnasadh
    Lughnasadh
    centifanto said:
    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
    Click to expand...
    Click to collapse
    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.
    View
    4
    H
    Homeboy76
    Update
    Magisk Canary 23019
    View
    4
    H
    Homeboy76
    Update
    SDK Platform-tools - r33.0.3
    View

New posts