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

Search This thread
By:
Advanced…
L

luisgerardo01

Senior Member
Mar 21, 2015
157
31
Hi, all

I bought a refurbished Google Pixel and imported to my (unsupported) country. While it arrived, I was searching for important info and found that I needed to root the device to make use of the VoLTE/VoWifi feature 😣, nothing that really mattered to me anyway as I've been rooting devices most of the time I've been using an Android phone.

I gathered the required info and even downloaded the latest device specific factory images. My only question here is: do I need to first allow the phone to do the first-time boot and wizard and even OTA update to the latest and then root or may I boot directly the device in fastboot, flash-all (script) the latest factory image and then flash the patched boot, all at once, before the first boot?

It's just to avoid downloading and erasing and then flashing everything again. BTW, I wouldn't be rooting the phone if I wouldn't need this phone feature. Also I usually root phones I want or need but after some weeks of use, so that's why I raised this short and maybe stupid doubt above.

Regards,
 
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
2,313
3,272
luisgerardo01 said:
Hi, all

I bought a refurbished Google Pixel and imported to my (unsupported) country. While it arrived, I was searching for important info and found that I needed to root the device to make use of the VoLTE/VoWifi feature 😣, nothing that really mattered to me anyway as I've been rooting devices most of the time I've been using an Android phone.

I gathered the required info and even downloaded the latest device specific factory images. My only question here is: do I need to first allow the phone to do the first-time boot and wizard and even OTA update to the latest and then root or may I boot directly the device in fastboot, flash-all (script) the latest factory image and then flash the patched boot, all at once, before the first boot?

It's just to avoid downloading and erasing and then flashing everything again. BTW, I wouldn't be rooting the phone if I wouldn't need this phone feature. Also I usually root phones I want or need but after some weeks of use, so that's why I raised this short and maybe stupid doubt above.

Regards,
Click to expand...
Click to collapse
Just go ahead and flash all, no need to waste time.
 
  • Like
Reactions: luisgerardo01
B

bdr127

New member
Dec 19, 2011
2
0
I have a Pixel 6 that I rooted and update using this great guide. (Thank you!) The phone uses Google Fi for service. I need to do the February 2023 update, and there are two -- a normal one and one for T-Mobile and T-Mobile MVNOs. Google Fi uses T-Mobile, Sprint, US Cellular, and Three (UK) networks, so I'm thinking maybe I should download the update for T-Mobile MVNOs, but I'm not sure since Google Fi uses multiple cell networks.... Anyone know for sure which update I should download?
 
tiiiit74

tiiiit74

Member
Sep 1, 2022
18
5
Hi everyone, I'm on vacation, I don't have a computer and I have a problem with Safety Net. I can no longer pay in NFC on my Pixel 6 Root when it worked a few days ago in SafetyNet-fix 2.4.0. I haven't done anything in the meantime... Tried 2.3.1 mod, doesn't work either. Can you tell me if I can unroot from Magisk without going through a computer? Thank you very much, it's urgent. See you soon I hope.
 
N

Nightf0x_007

Senior Member
Nov 5, 2012
741
84
tiiiit74 said:
Hi everyone, I'm on vacation, I don't have a computer and I have a problem with Safety Net. I can no longer pay in NFC on my Pixel 6 Root when it worked a few days ago in SafetyNet-fix 2.4.0. I haven't done anything in the meantime... Tried 2.3.1 mod, doesn't work either. Can you tell me if I can unroot from Magisk without going through a computer? Thank you very much, it's urgent. See you soon I hope.
Click to expand...
Click to collapse
Try updating to safetynet fix v2.4.0 mod 1.1 by displax
 
  • Like
Reactions: tiiiit74
Lughnasadh

Lughnasadh

Senior Member
Mar 23, 2015
5,159
6,031
Google Nexus 5
Huawei Nexus 6P
tiiiit74 said:
Hi everyone, I'm on vacation, I don't have a computer and I have a problem with Safety Net. I can no longer pay in NFC on my Pixel 6 Root when it worked a few days ago in SafetyNet-fix 2.4.0. I haven't done anything in the meantime... Tried 2.3.1 mod, doesn't work either. Can you tell me if I can unroot from Magisk without going through a computer? Thank you very much, it's urgent. See you soon I hope.
Click to expand...
Click to collapse
As for the unrooting portion of this question, you can unroot by uninstalling Magisk via the Magisk app.
 
H

Homeboy76

Recognized Contributor
Aug 24, 2012
3,872
2,310
Google Pixel XL
Google Pixel 7 Pro
D

defrag44

Member
Feb 23, 2023
7
3
luisgerardo01 said:
Hi, all

I bought a refurbished Google Pixel and imported to my (unsupported) country. While it arrived, I was searching for important info and found that I needed to root the device to make use of the VoLTE/VoWifi feature 😣, nothing that really mattered to me anyway as I've been rooting devices most of the time I've been using an Android phone.

I gathered the required info and even downloaded the latest device specific factory images. My only question here is: do I need to first allow the phone to do the first-time boot and wizard and even OTA update to the latest and then root or may I boot directly the device in fastboot, flash-all (script) the latest factory image and then flash the patched boot, all at once, before the first boot?

It's just to avoid downloading and erasing and then flashing everything again. BTW, I wouldn't be rooting the phone if I wouldn't need this phone feature. Also I usually root phones I want or need but after some weeks of use, so that's why I raised this short and maybe stupid doubt above.

Regards,
Click to expand...
Click to collapse
FYI - You do not need to root to enable VoLTE/VoWIFI, check this thread for simple solution

forum.xda-developers.com

Enable VoLTE/VoWiFi in unsupported countries without root (requires Shizuku)

Hi all, Bellow you can find some info on how to attempt to enable VoLTE in unsupported countries (tested in Romania, Digi carrier) using Shizuku and Pixel IMS app for it. This assumes that you have ADB and drivers properly setup beforehand. 1...
forum.xda-developers.com forum.xda-developers.com
 
  • Like
Reactions: Homeboy76 and luisgerardo01
H

Homeboy76

Recognized Contributor
Aug 24, 2012
3,872
2,310
Google Pixel XL
Google Pixel 7 Pro
Not another broken Magisk Canary release
Magisk Canary - app-release_981ccabb-25210.apk
breaks all modules:
github.com

25210 breaks module loading · Issue #6688 · topjohnwu/Magisk

Device: Pixel 7 Pro Android version: 13 QPR2 Magisk version name: v981ccabb Magisk version code: 25210 With the latest version, mounting all mounts fails saying No such file or directory, i.e. moun...
github.com github.com
 
  • Like
Reactions: vlucchetti and Lughnasadh
F

freonchill

Senior Member
Jul 11, 2011
266
58
Atlanta
arsradu said:
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! :)
Click to expand...
Click to collapse
FYI - if anyone is having a problem

Installed 13.0.0 (TQ1A.230205.002, Feb 2023) via pixel flasher and was running magisk canary and couldn't get magisk to properly do roof. uninstalled canary and installed debug to get root working.
 
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
119K
S.N.@.K.3
[email protected]
L
How To Guide Sim unlock tmobile pixel 6
Replies
165
Views
54K
Gerardo T.
Gerardo T.
Typhus_
Themes / Apps / Mods [MOD][MAGISK][ANDROID 12] Addon Features for Pixel Devices - Pixel 6 Thread
Replies
368
Views
57K
mobile_sensei
mobile_sensei
badabing2003
Themes / Apps / Mods 📳🔥PixelFlasher for Google Pixel 6 Support Thread.
Replies
480
Views
39K
kiwigi
kiwigi
H
How To Guide Converting Japanese Pixel 6 to Global version
Replies
146
Views
52K
kevin3688
kevin3688

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 2
    C
    choukajohn
    To @Homeboy76 and @Lughnasadh

    Thanks guys for your answers.

    First I tried to flash the other slot but it doesn't worked, corrupted device warning screen was still there.

    Then, I flashed boot.img from april update and rebooted the phone, no more corrupted device warning screen but a prompt from android because of corrupted data asked to wipe data or try again.
    I rebooted device in fastboot and flash the boot.img from may then reboot to android.

    No more corrupted device warning but again the corrupted data message. This time I choosed "try again" and android finally booted up.
    Everythings seems to work properly, root and safetynet fix.
    View
    2
    shoey63
    shoey63
    Murmel2k said:
    I today updated my phone months after I figured out that the OTA update with Magisk doesn't work. Before trying to take the next OTA update and bricking my phone again: Does taking the OTA update with Magisk (assuming to deactivate all modules, uninstalling Magisk and to install magisk into the inactive slot) now work?
    Click to expand...
    Click to collapse
    Nope.
    In fact even after restoring images it won't do an OTA update at all unless you reboot and thus lose root.
    You need a PC or laptop now.
    Pixel Flasher is the best tool for the job
    View
    1
    H
    Homeboy76
    choukajohn said:
    No error
    Fastbootd doesn't work with SDK 34.0.1

    Device is booting but now, every time I boot the phone, I have the corrupted device warning screen and I have to force boot.
    If anyone could help.
    Thanks.
    Click to expand...
    Click to collapse
    When the phone boots, back up your data and wipe the phone and set it up or try flashing the other slot.

    Flashing the other slot:

    1. If your phone is rooted, open Magisk and disable all modules then reboot.
    2. Please, verify the flash-all.bat file in the SDK Platform-tools folder has been edited:

      Edit this line in the flash-all.bat file
      fastboot -w update image-oriole-aa9a.999999.999.zip
      Remove the -w to Keep Data.
    3. Rename the attached flash-other.txt file flash-other.bat, put it in the
      SDK Platform-tools folder (the folder with fastboot.exe in it).
    4. Boot the bootloader
      connect the phone to your pc
      open a command prompt on the pc in tge SDK Platform tools folder and type flash-other
    View
    1
    Lughnasadh
    Lughnasadh
    choukajohn said:
    No error
    Fastbootd doesn't work with SDK 34.0.1

    Device is booting but now, every time I boot the phone, I have the corrupted device warning screen and I have to force boot.
    If anyone could help.
    Thanks.
    Click to expand...
    Click to collapse
    Flash the previous month's boot image (it won't boot but that's ok), then flash the boot image from your current build. That should get rid of the corrupt message.
    View
    1
    H
    Homeboy76
    SDK Platform-tools Update
    SDK Platform-tools r. 34.0.3, was released May 22, 2023.

    @badabing2003 reported a problem when using it.
    https://forum.xda-developers.com/t/...7-pro-cheetah-safetynet.4502805/post-88571575

    @Lughnasadh, suggested a fix.
    https://forum.xda-developers.com/t/...7-pro-cheetah-safetynet.4502805/post-88571601

    @badabing2003, confirmed the suggested fix works.
    https://forum.xda-developers.com/t/...7-pro-cheetah-safetynet.4502805/post-88571617

    Note: If you use Windows SDK Platform- tools r. 34.0.3. You must set the environment variable.

    I think the same is true if you use Linux SDK Platform-tools r. 34.0.3. You must set the enviroment variable.
    View
  • 26
    H
    Homeboy76
    [Guide] Root Pixel 6 with Magisk + Unlock Bootloader + Pass SafetyNet + More
    Android Security Bulletin—May 2023
    Pixel Update Bulletin—May 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

      • "...make a 100% clean install of ANY Magisk version or fork without PC or TWRP."

        Magisk General Support / Discussion

        This is the place for general support and...
        forum.xda-developers.com forum.xda-developers.com
      • Android 14 Beta are up.

        1. Builds are only available for the following Pixel devices:
          • Google Pixel 4a5(G)
          • Google Pixel 5 and 5a
          • Google Pixel 6 and 6 Pro
          • Google Pixel 6a
          • Google Pixel 7 and 7 Pro
            * * * 64-bit-only system images * * *
          • Google Pixel 4a (5G)
          • Google Pixel 5
          • Google Pixel 6
          • Google Pixel 6 Pro
        2. Android 14 GSI binaries and release
          • Pixel 4a5(G)
          • Pixel 5 and 5a
          • Pixel 6 and 6 Pro
          • Pixel 6a Pro
          • Pixel 7 and 7 Pro
      • Android 13 QPR3 beta images are up.
        Release notes - for QPR3 beta
        1. Factory Images
          Builds are only available for the following Pixel devices:

          • Google Pixel 4a and 4a (5G)
          • Google Pixel 5 and 5a
          • Google Pixel 6 and 6 Pro
          • Google Pixel 6a
          • Google Pixel 7 and 7 Pro
            * * * 64-bit-only system images * * *
          • Google Pixel 4a (5G)
          • Google Pixel 5
          • Google Pixel 6
          • Google Pixel 6 Pro
        2. OTA Images
          Builds are only available for the following Pixel devices:

          • Google Pixel 4a and 4a (5G)
          • Google Pixel 5 and 5a
          • Google Pixel 6 and 6 Pro
          • Google Pixel 6a
          • Google Pixel 7 and 7 Pro
      • Temporary fix for rooting the Google Pixel 6/6 Pro:
        https://forum.xda-developers.com/t/...der-pass-safetynet-more.4388733/post-87853193
        Note: Magisk Canary 25211
        @Lughnasadh said, "I was able to patch the Pixel 6 Pro boot image (instead of the Pixel 7 Pro boot image) on A14"...
    4. Update(s)

    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. Manually Install/Update Factory Image keep data or wipe data.

      • Important Note(s):
        1. If you haven't updated your phones Factory image in awhile. 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. If you are uncomfortable manually flashing the factory image. Try PixelFlasher by badabing2003.
        4. "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"...
        5. If you want to update to the Android 13 Factory image without wiping your phone: Do Flash Factory Image Keep Data (below).
        6. Always verify you have the latest working version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 6 - oriole.
        7. 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.
        8. 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
        9. Backup your data
        10. Download the latest Factory Image: Pixel 6 - oriole to your Computer.
        11. 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

        • Upgrading to Android 13
          * E D I T - flash-all.bat file *
          Flash to current/Active Slot.
          @Echo off
          PATH=%PATH%;"%SYSTEMROOT%\System32"
          fastboot flash bootloader bootloader-oriole-slider-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
          Note:The -w is removed to Keep Data.
          echo Press any key to exit...
          pause >nul
          exit
          Note: It is a good idea to flash the Google factory image to both slots (A & B) when Upgrading to new Android Version.
          See Flash Other Slot bat file... below, to flash to the other/inactive slot.
          * * * * E N D - Edit * * * *
        • Updating Android 13
          Flash to Other/Inactive Slot.
          Note: See Flash Other Slot bat file... below.
          * * * * Create - Flash Other Slot bat file * * * *
        • Save Flash Other Slot bat file - as flash-other.bat
          Note: To run this file type flash-other at the Command Prompt.
          ECHO OFF
          PATH=%PATH%;"%SYSTEMROOT%\System32"
          echo This is the slot you are currently on.
          fastboot getvar current-slot
          echo Press any key to continue...
          pause >nul
          fastboot --set-active=other
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          echo This is the slot you switched to.
          fastboot getvar current-slot
          echo Press any key to continue...
          pause >nul
          flash-all
          exit
          * * E N D - Creating File * *
        • 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 Data/Internal Storage.
        • Do not edit the flash-all.bat file.
        • If you need to disable Verity and Verification: See Disabling Verity and Verification below.
          Disabling Verity and Verification
          * E D I T - flash-all.bat file *
          @Echo off
          PATH=%PATH%;"%SYSTEMROOT%\System32"
          fastboot --set-active=other
          fastboot reboot-bootloader
          fastboot flash bootloader bootloader-oriole-slider-9.9-9999999.img
          fastboot reboot-bootloader
          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 - w update --disable-verity --disable-verification image-oriole-aa9a.999999.999.zip
          echo Press any key to exit...
          pause >nul
          exit
          Notes:
          1. The first time you Disable Verity and Verification it will wipe your Data/Internal Storage.
          2. When doing Subsequent updates and disabling Verity and Verification, the -w flag can be removed to Keep Data.
          3. 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.
          4. Some kernels require Disabling verity and verification
          5. To flash both slots (A & B partitions) see Flash Other Slot bat file... above.
          * * * * E N D - Edit * * * *
        • Open the folder you extracted the Factory Image to and Copy/Move these files to the Platform-tools folder:
          1. android-info.txt
          2. bootloader-oriole-....img
          3. flash-all.bat
          4. image-oriole-....zip
          5. radio-oriole-....img
        • On your phone: Boot the bootloader (fastboot mode) (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-all.bat boot/init_boot.img Flash boot/init_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/init_boot.img

        1. Flashing the boot/init_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. If your phone was previously rooted, DO NOT repeat DO NOT install another Magisk Manager app[/U]. Do this before you patch the boot/init_boot image:
          • Open the Magisk Manager app and disable all Magisk modules. 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. You can also use TB Checker to check if you have more than one Magisk Manager app installed.
        2. Extract the boot/init_boot.img file from the Factory Image.
          • 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 and extract the Image file (image-oriole-aa9a.999999.999.zip) into the folder. The, stock, boot/init_boot.img file should be in this folder.
        3. Install Magisk Canary - Download app-release.apk
          or
          Magisk Beta/Stable App
        4. Open Magisk Beta/Canary/Stable App
        5. The Update Channel should be set to Beta/Canary/Stable, depending on the version you Installed.
        6. Tap Install (next to Magisk)
        7. Tap, Select and Patch a File
        8. Select the boot.img file you extracted from the latest factory image.
        9. Tap the ✓ (Check Mark)
        10. Tap Let's Go
        11. When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.
        12. Reboot
        13. 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
        14. Boot fastboot mode
        15. Connect the phone to the Computer with USB cord.
        16. Open a Command Prompt in the folder you copied the patched boot.img to.
        17. Type fastboot flash boot "name of patched boot".img without the quote marks at the Prompt and press enter.
        18. Type fastboot reboot at the Prompt and press enter.
        19. 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.
        20. 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 Displax's safetyNet Fix
          • Open Magisk
          • Tap Modules icon
          • Tap Install from storage
          • Navigate to the Displax's SafetyNet Fix file you downloaded.
          • Tap the Displax's SafetyNet Fix file.
          • Tap the check mark (✓ at the bottom) to start the installation.
          • After it installs tap the Save icon to save the log
          • Tap Reboot.
        3. 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 Enable Biometric Authentication.
        4. Get Device Certified
          • Turn Airplane mode on
          • Open Settings
          • Tap Apps & notifications
          • Tap see all...
          • Tap three dot menu
          • Tap Show system
          • Scroll to Google Play Store
          • Tap Storage and Cache
          • Tap Clear storage
            Note: Repeat the 3 steps above for any app that needs Device Certification i.e., Google Play Services, Google Pay, Google Wallet, etc.
          • reboot
          • Turn Airplane mode off
        5. Check Device Certification
          • Open Google Play Store app
          • Tap Menu - Circle top right
          • Tap Settings
          • Tap About
          • Check Play protect certification
          • It may take 24 hours for Device Certification to be updated.
        6. Note: If after completeting Get Device Certified and Check Device Certification you've waited 24 hours your Device is not Certifed or your Device is Certified and certain Google Store apps (Google Pay, NetFliks, etc.) are not working. Use the Play Integrity API Checker app or the TB Checker - Safetynet and Root app to verify you are passing Play Integrity.
    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.
    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
    SDK Platform-tools - r33.0.3
    View
    4
    H
    Homeboy76
    Update
    Magisk Canary 23019
    View

New posts