How To Guide [GUIDE] Pixel 6 "oriole": Unlock Bootloader, Update, Root, Pass SafetyNet

Search This thread

gazdajezda

Senior Member
Apr 24, 2011
433
84
What happened when you tried to flash the boot image? Copy and paste the output here, or take a photo. Make sure you're using the correct firmware - "oriole" for Pixel 6.

You could also use Pixel Flasher to make this a bit easier.

Boot images were flashed ok, but after reboot it was same. Loading and black screen. I dont have a photo (only this on nonworking Pixel). Firmware is correct, at least checksum said so (i have a bakup of my phone on other disk and there was original boot.img and patched one, so I can check them with original one). Now P6 is start working, blank. So I need to setup all over again... First I will root it and then further.
About flasher: maybe next time, now it's over... phone is empty.
 

V0latyle

Forum Moderator
Staff member
Boot images were flashed ok, but after reboot it was same. Loading and black screen. I dont have a photo (only this on nonworking Pixel). Firmware is correct, at least checksum said so (i have a bakup of my phone on other disk and there was original boot.img and patched one, so I can check them with original one). Now P6 is start working, blank. So I need to setup all over again... First I will root it and then further.
About flasher: maybe next time, now it's over... phone is empty.
Okay, so you went ahead with the data wipe. Is it at least working now? If it is, I have no idea why it wouldn't have worked with the unpatched boot image. Maybe something else got screwed up.
 

r00tcracker

Member
May 8, 2013
47
14
I know this is maybe a bit out of topic, but anyone updated to December image encountered any issues?? lost root, safetynet not passing, etc??
Just want to know before I jump the gun :)
Thanks
 

V0latyle

Forum Moderator
Staff member
I know this is maybe a bit out of topic, but anyone updated to December image encountered any issues?? lost root, safetynet not passing, etc??
Just want to know before I jump the gun :)
Thanks
SafetyNet has been replaced by Play Integrity. Please see the note in the OP.

How did you update?
 
Last edited:

gazdajezda

Senior Member
Apr 24, 2011
433
84
Okay, so you went ahead with the data wipe. Is it at least working now? If it is, I have no idea why it wouldn't have worked with the unpatched boot image. Maybe something else got screwed up.

Yes, after wipe it work. I had a little mess with Swift Backup but now it's all ok. I lost my 2F seeds in Google Authenticator, but the rest seems ok.

Don't know why that happenede, i suspect an almost 4 months uptime and maybe there is some memory leak and after while strange things could happen. My opinion.
 

gazdajezda

Senior Member
Apr 24, 2011
433
84
I know this is maybe a bit out of topic, but anyone updated to December image encountered any issues?? lost root, safetynet not passing, etc??
Just want to know before I jump the gun :)
Thanks

I will stay on 12. It works ok, also all banking apps, so I do not want to try to lose that. Also, do not wanna go to non-rooted rom never again.
 

gazdajezda

Senior Member
Apr 24, 2011
433
84
I will stay on 12. It works ok, also all banking apps, so I do not want to try to lose that. Also, do not wanna go to non-rooted rom never again.

How can I prevent automatic updates? Or at least prevent those notifications to pop-up... Thank you.
 

Attachments

  • Screenshot_20221209-230050.png
    Screenshot_20221209-230050.png
    87.7 KB · Views: 25

V0latyle

Forum Moderator
Staff member

V0latyle

Forum Moderator
Staff member

r00tcracker

Member
May 8, 2013
47
14
Android 13 is rootable, and I'm using banking apps without a problem...

I'm not sure it is possible.
V0latyle, are you on the december update and with no issues with passing intregrity??

Also, if I am already on 13 (I'm on october release), do I have to flash the bootloader to both slots again, or I just can flash normally.
I'm editing the batch file.
Thanks
 

V0latyle

Forum Moderator
Staff member
V0latyle, are you on the december update and with no issues with passing intregrity??
I use a Pixel 5, but yes:
Screenshot_20221212-042325.png

Also, if I am already on 13 (I'm on october release), do I have to flash the bootloader to both slots again, or I just can flash normally.
I'm editing the batch file.
Thanks
You can flash normally. It's only necessary to update both bootloader slots when you initially update to Android 13 on the Tensor devices.
 

newkpt

Member
Dec 4, 2007
6
1
Hi!

I'm on oriole.t2b1.221118.006, and I've never rooted my phone before. I've been on the beta since the begining so I've made a few OTA updates.

I've followed the steps on the first post (unlock bootloader, patched the boot.img) and the output from "fastboot flash boot "master root.img"" is:
Code:
Sending 'boot_b' (65536 KB)                        OKAY [  1.593s]
Writing 'boot_b'                                   OKAY [  0.328s]
Finished. Total time: 1.937s

On the magisk app (v.25.2), the "installed" stays "N/A".
Code:
Installed: N/A
Zygisk: No
Ramdisk: Yes

I've sideloaded the same OTA version that I'm on, repeated the flash boot, same result.
I've sideloaded the full factory image of the same version and the result is still the same.

I've also tried to boot and boot_b having the same result.

Am I missing something? What can I try next?

ty
 
Last edited:

Lughnasadh

Senior Member
Mar 23, 2015
4,673
5,284
Google Nexus 5
Huawei Nexus 6P
Hi!

I'm on oriole.t2b1.221118.006, and I've never rooted my phone before. I've been on the beta since the begining so I've made a few OTA updates.

I've followed the steps on the first post (unlock bootloader, patched the boot.img) and the output from "fastboot flash boot "master root.img"" is:
Code:
Sending 'boot_b' (65536 KB)                        OKAY [  1.593s]
Writing 'boot_b'                                   OKAY [  0.328s]
Finished. Total time: 1.937s

On the magisk app (v.25.2), the "installed" stays "N/A".
Code:
Installed: N/A
Zygisk: No
Ramdisk: Yes

I've sideloaded the same OTA version that I'm on, repeated the flash boot, same result.
I've sideloaded the full factory image of the same version and the result is still the same.

I've also tried to boot and boot_b having the same result.

Am I missing something? What can I try next?

ty
For now, you need to patch the Pixel 7 boot image and flash that patched image on your Pixel 6 to obtain root when running QPR2 Beta 1. John Wu is looking into why patching and flashing the Pixel 6 boot image on QPR2 Beta 1 isn't working to root Pixel 6 series' devices.
 

newkpt

Member
Dec 4, 2007
6
1
For now, you need to patch the Pixel 7 boot image and flash that patched image on your Pixel 6 to obtain root when running QPR2 Beta 1. John Wu is looking into why patching and flashing the Pixel 6 boot image on QPR2 Beta 1 isn't working to root Pixel 6 series' devices.
Couldn't find that information, thanks for sharing it worked!

Any known downside using the pixel7 instead of pixel6?
 
  • Like
Reactions: Lughnasadh

gazdajezda

Senior Member
Apr 24, 2011
433
84
Nice. I figured it would fall under the system notification category. Make sure you disable automatic system updates in Developer Options.

Just week after wipe my phone get this notification. I'm sure that after install / reboot it will again go into that 'black' boot mode. Is there any way to prevent installing that updates? Automatic updates are disabled, what else I need to do to prevent updating the phone? Which apps need to be disabled? I just wanna have a rooted phone, that's all.
 

Attachments

  • Screenshot_20221215-214326_1.png
    Screenshot_20221215-214326_1.png
    70 KB · Views: 19
  • Screenshot_20221215-220928.png
    Screenshot_20221215-220928.png
    172.7 KB · Views: 19

gazdajezda

Senior Member
Apr 24, 2011
433
84
Just week after wipe my phone get this notification. I'm sure that after install / reboot it will again go into that 'black' boot mode. Is there any way to prevent installing that updates? Automatic updates are disabled, what else I need to do to prevent updating the phone? Which apps need to be disabled? I just wanna have a rooted phone, that's all.

What should I do with that? Today instalation will be done, so shall I remove Magisk so instalation will proceed without error and later root again? Also, does that update mean that A13 will be installed? I know I'm bothering with that but this is so ofensive, I have unchecked updates installation and still is bothering with that...
 

Top Liked Posts

  • 2
    Got Displax's mod working. USNF 2.4.0 is definitely broke right now unless you're using MHPC (didn't want to go that route since it's not supported anymore).

    Now... do I want to update the latest GPay that just rolled out? :ROFLMAO:
    USNF 2.4.0 works for me on my Pixel 5.
    2
    Seems to be an "intermittent" problem (within the last week) with USNF 2.4. Many people have reported that GPay/Wallet no longer works for them using USNF 2.4 and they had to revert to Displax's 2.3.1-MOD_2.1 to get it working again. On the other hand, others seem to have GPay/Wallet working just fine with 2.4.

    Definitely is definitely the wrong adverb 🙃
    1
    USNF 2.4.0 works for me on my Pixel 5.
    it works for me on p7p as well.
    @GrandAdmiral definitely is the wrong adverb in this context.
    1
    it works for me on p7p as well.
    @GrandAdmiral definitely is the wrong adverb in this context.

    Seems to be an "intermittent" problem (within the last week) with USNF 2.4. Many people have reported that GPay/Wallet no longer works for them using USNF 2.4 and they had to revert to Displax's 2.3.1-MOD_2.1 to get it working again. On the other hand, others seem to have GPay/Wallet working just fine with 2.4.

    Definitely is definitely the wrong adverb 🙃
    I got it. I got it. Lol
  • 2
    Got Displax's mod working. USNF 2.4.0 is definitely broke right now unless you're using MHPC (didn't want to go that route since it's not supported anymore).

    Now... do I want to update the latest GPay that just rolled out? :ROFLMAO:
    USNF 2.4.0 works for me on my Pixel 5.
    2
    Seems to be an "intermittent" problem (within the last week) with USNF 2.4. Many people have reported that GPay/Wallet no longer works for them using USNF 2.4 and they had to revert to Displax's 2.3.1-MOD_2.1 to get it working again. On the other hand, others seem to have GPay/Wallet working just fine with 2.4.

    Definitely is definitely the wrong adverb 🙃
    1
    Thanks!
    You are absolutely right what you are saying about learning the manual process. So I tried a couple of times, which isn't really a lot.
    At some stage after searching the error(corrupt image error in adb) on the web some solution came up that the Android adb interface driver could possibly be missing. So I tried to install it, though the pc complained that it wasn't a 64 bit driver or something along these lines. Hence I moved to PF. No complaints during that procedure.
    If Pixel Flasher worked, that's not the problem because PF uses the same ADB tools and interfaces.

    HI!
    Kind of new :)

    I've got 2 questions about this, I am using Pixel 6 - Paranoid Android ROM:
    - Ive checked my bootloader version and A&B are both "slider-1.2-9152140"
    Is this fine or should i change something?

    - Will this rooting option and safetynet work with my installed rom?
    If yes, will it clear my data (if successfull)?

    Thanks!
    Questions about Paranoid ROM should be asked in the Paranoid ROM thread.

    As for your bootloader version, I do not know off the top of my head what the Android 13 bootloader is. Since you're using a custom ROM this shouldn't be an issue.
    1
    If Pixel Flasher worked, that's not the problem because PF uses the same ADB tools and interfaces.
    Perhaps it wasn't the drivers, but rather the Android Platform Tools.
    When using PF, you select the directory where Android Platform Tools are installed and PF hard codes that full path in the generated flash_all script along with the selected device's ID, hence avoiding any potential of picking up any other Android Platform Tools in the system path.
    It's not uncommon for people to have several old versions of adb lingering in their system and some unfortunately added to their system environment.

    If it was a driver issue, you are absolutely correct, PF would have ran into the same issue.
    1
    it works for me on p7p as well.
    @GrandAdmiral definitely is the wrong adverb in this context.

    Seems to be an "intermittent" problem (within the last week) with USNF 2.4. Many people have reported that GPay/Wallet no longer works for them using USNF 2.4 and they had to revert to Displax's 2.3.1-MOD_2.1 to get it working again. On the other hand, others seem to have GPay/Wallet working just fine with 2.4.

    Definitely is definitely the wrong adverb 🙃
    I got it. I got it. Lol
  • 48
    ⚠️⚠️⚠️WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST! ⚠️⚠️⚠️

    If you are looking for my guide on a different Pixel, find it here:
    Update 6-20-22: Magisk 25.1 is recommended as this includes fixes for OTA updates, as well as support for the Android 13 beta.
    Discussion thread for migration to 24.0+.

    DO NOT use any version of Magisk lower than Canary 23016 as it does not yet incorporate the necessary fixes for Android 12 and your device.


    WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.

    Prerequisites:


    Android Source - Setting up a device for development


    1. Follow these instructions to enable Developer Options and USB Debugging.
    2. Enable OEM Unlocking. If this option is grayed out, unlocking the bootloader is not possible.
    3. Connect your device to your PC, and open a command window in your Platform Tools folder.
    4. Ensure ADB sees your device:
      Code:
      adb devices
      If you don't see a device, make sure USB Debugging is enabled, reconnect the USB cable, or try a different USB cable.
      If you see "unauthorized", you need to authorize the connection on your device.
      If you see the device without "unauthorized", you're good to go.
    5. Reboot to bootloader:
      Code:
      adb reboot bootloader
    6. Unlock bootloader: THIS WILL WIPE YOUR DEVICE!
      Code:
      fastboot flashing unlock
      Select Continue on the device screen.

    1. Install Magisk on your device.
    2. Download the factory zip for your build.
    3. Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img
    4. Copy boot.img to your device.
    5. Patch boot.img with Magisk: "Install" > "Select and Patch a File"
    6. Copy the patched image back to your PC. It will be named "magisk_patched-23xxx_xxxxx.img". Rename this to "master root.img" and retain it for future updates.
    7. Reboot your device to bootloader.
    8. Flash the patched image:
      Code:
      fastboot flash boot <drag and drop master root.img here>
    9. Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>

    1. Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.
    2. Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
    3. Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device.
    4. You should now be updated with root.

    1. Download the OTA.
    2. Reboot to recovery and sideload the OTA:
      Code:
      adb reboot sideload
      Once in recovery:
      Code:
      adb sideload ota.zip
    3. When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
    4. Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
    5. Reboot to bootloader.
    6. Boot the master root image (See note 1):
      Code:
      fastboot boot <drag and drop master root.img here>
      Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
    7. Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
    8. Reboot your device. You should now be updated with root.
    Note: You can use Payload Dumper to extract the contents of the OTA if you want to manually patch the new boot image. However, I will not cover that in this guide.

    Please note that the factory update process expects an updated bootloader and radio. If these are not up to date, the update will fail.
    1. Download the factory zip and extract the contents.
    2. Reboot to bootloader.
    3. Compare bootloader versions between phone screen and bootloader.img build number
      Code:
      fastboot flash bootloader <drag and drop new bootloader.img here>
      If bootloader is updated, reboot to bootloader.
    4. Compare baseband versions between phone screen and radio.img build number
      Code:
      fastboot flash radio <drag and drop radio.img here>
      If radio is updated, reboot to bootloader.
    5. Apply update:
      Code:
      fastboot update --skip-reboot image-codename-buildnumber.zip
      When the update completes, the device will be in fastbootd. Reboot to bootloader.
    6. Boot the master root image (See note 1):
      Code:
      fastboot boot <drag and drop master root.img here>
      Note: If you prefer, you can manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
    7. Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
    8. Reboot your device. You should now be updated with root.
    Note: If you prefer, you can update using the flash-all script included in the factory zip. You will have to copy the script, bootloader image, radio image, and update zip into the Platform Tools folder; you will then have to edit the script to remove the -w option so it doesn't wipe your device.
    The scripted commands should look like this:
    Code:
    fastboot flash bootloader <bootloader image name>
    fastboot reboot bootloader
    ping -n 5 127.0.0.1 > nul
    fastboot flash radio <radio image name>
    fastboot reboot bootloader
    ping -n 5 127.0.0.1 > nul
    fastboot update  --skip-reboot <image-device-buildnumber.zip>
    Once this completes, you can reboot to bootloader and either boot your master patched image, or if you patched the new image, flash it at this time.

    PixelFlasher by @badabing2003 is an excellent tool that streamlines the update process - it even patches the boot image for you.
    The application essentially automates the ADB interface to make updating and rooting much easier. However, it is STRONGLY recommended that you still learn the "basics" of using ADB.

    For instructions, downloads, and support, please refer to the PixelFlasher thread.

    1. Follow the instructions on the Android Flash Tool to update your device. Make sure Lock Bootloader and Wipe Device are UNCHECKED.
    2. When the update completes, the device will be in fastbootd. Reboot to bootloader.
    3. Boot the master root image (See note 1):
      Code:
      fastboot boot <drag and drop master root.img here>
      Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
    4. Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
    5. Reboot your device. You should now be updated with root.

    SafetyNet has been deprecated for the new Play Integrity API. More information here.

    In a nutshell, Play Integrity uses the same mechanisms as SafetyNet for the BASIC and DEVICE verdicts, but uses the Trusted Execution Environment to validate those verdicts. TEE does not function on an unlocked bootloader, so legacy SafetyNet solutions will fail.

    However, @Displax has modified the original Universal SafetyNet Fix by kdrag0n; his mod is able to bypass TEE, meaning that the device will pass BASIC and DEVICE integrity.

    Mod available here. Do not use MagiskHide Props Config with this mod.

    This is my configuration that is passing Safety Net. I will not provide instructions on how to accomplish this. Attempt at your own risk.

    Zygisk + DenyList enabled
    All subcomponents of these apps hidden under DenyList:
    • Google Play Store
    • GPay
    • Any banking/financial apps
    • Any DRM media apps
    Modules:
    • Universal SafetyNet Fix 2.3.1 Mod - XDA post
    To check SafetyNet status:
    To check Play Integrity status:
    I do not provide support for Magisk or modules. If you need help with Magisk, here is the Magisk General Support thread. For support specifically with Magisk v24+, see this thread.

    Points of note:
    • The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.
    • While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:
      screenshot_20211218-194517-png.5486339
    • "Installed" shows the version of patch in the boot image. If this says N/A, you do not have root access - the boot image is not patched, or you have a problem with Magisk.
    • "App" simply shows the version of the app itself.
    • If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.
    • If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.
    • Some Magisk modules, especially those that modify read only partitions like /system, may cause a boot loop after updating. As a general rule, disable these modules before updating. You are responsible for knowing what you have installed, and what modules to disable.


    Credits:
    Thanks to @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!
    7
    Magisk Canary was updated to 23016 last night. This includes a fix for the vbmeta header issue, meaning that disabling verity/verification should no longer be required, and we should be able to root as we did before. This needs testing, make sure you back up your data and photos before you do this!

    Additionally, for the Pixel 6 and 6 Pro, fstab will now load from /system/etc which should fix the root issue many of you were having.

    Q: "If verity/verification are disabled, do I need to enable them now?"
    A: No. The only thing you have to do is update to Magisk 23016.
    Q: "Will enabling verity/verification wipe my data?"
    A: No.

    I will be updating the OP to reflect this.
    5
    Magisk 24306 (release notes) is now available on the canary channel, and I can confirm that the installation to the inactive slot OTA method is working for the April update.
    5
    Interesting. How did you command the reboot?

    When I tried to update this way on my wife's 5a, it bootlooped back to the original slot.
    I always follow these steps once I know the OTA is available:

    1. Open Magisk and select 'Uninstall Magisk -> Restore Images'
    2. Open Settings and Download/Install OTA *DO NOT REBOOT*
    3. Go back to Magisk and select 'Install -> Install to Inactive Slot (After OTA)' *DO NOT REBOOT*
    4. Go back to Settings and 'Reboot' to finalize the OTA
    5
    So, if I use this tool after rooting OTA updates will work and I'll still have root?

    Edit: And can you explain more clearly the process on how to do this?

    No, the tool does nothing to maintain root. It simply allows you to take the OTA. You will still need to reboot into fastboot and flash or boot from a patched boot image.

    The steps would be:
    1. Restore boot in the Magisk app
    2. Restore vbmeta in Vbmeta Patcher
    3. Take the OTA in System Updater
    4. Patch vbmeta in Vbmeta Patcher
    5. Patch the new boot image in the Magisk app and copy it to your computer
    6. Reboot into fastboot
    7. Boot from the new patched boot image
    8. Direct Install Magisk in the Magisk App
    As I noted the quote post, this process should be considered experimental until it has been more thoroughly tested. You should consider backing up any critical data before attempting it, in case something goes wrong.

    I'm working on another tool to make it a bit easier to acquire the new boot image in step 5, but that will likely be a few days. Hopefully we'll be able to install Magisk to the inactive slot on Pixel devices again in the future, which would consolidate steps 5-8.