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

Search This thread

V0latyle

Forum Moderator
Staff member
93618068_3705919662816648_5328266307781525504_n.png


Magisk Canary has been updated to 23017. Installing to inactive slot now supported.

Download it here or update through the Magisk app.

Note: If you have the Magisk app hidden, MAKE SURE you only update through the app! Multiple instances of Magisk will break root.
 

Attachments

  • 1642686868752.jpeg
    1642686868752.jpeg
    9.1 KB · Views: 32
Last edited:
  • Like
Reactions: bush911

mailistman

Senior Member
Dec 7, 2012
187
25
Please resize your screenshot or put it in a spoiler.

Did you have the Magisk app hidden before you updated?

You should still be able to manually patch and flash the new boot image.

The boot image is not device specific; if someone wants to post a patched Oriole boot image, any Pixel 6 can use it.
thanks for replying. sorry about attachment. on november build, i had magisk visible on app drawer as i run root explorer & few modules. hopefully someone will post copy of patched boot img on january build.
dumb question : can i use patched boot img from november build to flash in fastboot to get root on this january build ? or i will get bootloop ?

thank you.
 

V0latyle

Forum Moderator
Staff member
thanks for replying. sorry about attachment. on november build, i had magisk visible on app drawer as i run root explorer & few modules. hopefully someone will post copy of patched boot img on january build.
dumb question : can i use patched boot img from november build to flash in fastboot to get root on this january build ? or i will get bootloop ?

thank you.
You can temporarily boot an older boot image for root. Don't flash it. Instead, when you boot the older patched image, open Magisk, tap Install, then Direct Install to patch the new boot image.

Alternatively, if you're using the factory image update method, you can just extract and manually patch the new boot image.
 

airtower

Senior Member
Sep 9, 2010
1,100
359
Arlington, TX
Google Pixel 6
hello ..
thanks to OP for the instructions. i don't mean to derail this topic but i believe my issue is much related here. i am using P6 oriole. i was able to root on november build .037 and still have copy of my patched boot img on november build. i updated to january build .007 following guide here using update & root factory img method. update was success, but i lost root. i might have made mistake at some point.
now in no rooted state, when i tried to patch my boot.img using magisk 23016, i can't go to the next step because "Let's go" button greyed out. see attached. i tried to google it before i come here but same issue(s) were from different phone model & different magisk version, and worse, no resolutions either.

1. has anyone here experience the same issue ? and how did you overcome it ?
2. can someone please upload their P6 oriole patch boot .img from january build for me to try to flash on mine so i can get root ? or is the patch file specific for each phone ?

thank you !

Are you being prompted to select a file? "Let's Go" remains greyed out unless a file is selected.
 
  • Like
Reactions: V0latyle

mailistman

Senior Member
Dec 7, 2012
187
25
Are you being prompted to select a file? "Let's Go" remains greyed out unless a file is selected.
yes sir. boot.img has been selected (my post #281, see the radio button where you ticked option is highlighted), but "let's go" button remains greyed out.

Please read the Initial Root / Create Master Root Image section in the OP.
this where i hit the wall sir :
5. Patch boot.img with Magisk: "Install" > "and Patch a File"

thank you.
 

mailistman

Senior Member
Dec 7, 2012
187
25
Sounds like an issue with your magisk install. Have you cleared data or un and reinstalled?
i did un & reinstalled canary 23016 few times but getting same issue. later i will try with the new 23017.
if issue remains with 23017, i am thinking to downgrade back to november build. but it sounds too much work just to get the magisk do the magic 🙈.
wondering so far nobody posts january boot.img patched for me to try. should i open a new thread ?
 

V0latyle

Forum Moderator
Staff member
i did un & reinstalled canary 23016 few times but getting same issue. later i will try with the new 23017.
if issue remains with 23017, i am thinking to downgrade back to november build. but it sounds too much work just to get the magisk do the magic 🙈.
wondering so far nobody posts january boot.img patched for me to try. should i open a new thread ?
I don't think it's a problem with your firmware. Downgrading most likely won't help.

Try this:
  1. In Magisk, tap Uninstall > Complete Uninstall. Let Magisk reboot your device. You will reboot without root.
  2. Install Magisk Canary 23017
  3. Copy the January boot image to your device's root storage folder (make sure there's no others)
  4. In Magisk, tap Install > Select and Patch a File; select the boot image you just copied, then Let's Go
  5. Copy patched boot image back to your PC; rename it something easy like "patched January.img"
  6. Reboot to bootloader and flash the patched image:
    Code:
    fastboot flash boot <drag and drop patched image here>
  7. Select Start on your device, you should boot with root; confirm in Magisk (Installed should not say N/A)
 

mailistman

Senior Member
Dec 7, 2012
187
25
I don't think it's a problem with your firmware. Downgrading most likely won't help.

Try this:
  1. In Magisk, tap Uninstall > Complete Uninstall. Let Magisk reboot your device. You will reboot without root.
  2. Install Magisk Canary 23017
  3. Copy the January boot image to your device's root storage folder (make sure there's no others)
  4. In Magisk, tap Install > Select and Patch a File; select the boot image you just copied, then Let's Go
followed your advice with 23017 till point 4 but still no go.
FYI, on my 23016 i didn't have the restart button nor uninstall option on magisk app, so i removed it from Apps setting.
attached screenshots.
what else can i possibly try ? thank you.
 

Attachments

  • 20220120_140754.png
    20220120_140754.png
    121.6 KB · Views: 33
  • 20220120_140910.png
    20220120_140910.png
    53.2 KB · Views: 33

V0latyle

Forum Moderator
Staff member
followed your advice with 23017 till point 4 but still no go.
FYI, on my 23016 i didn't have the restart button nor uninstall option on magisk app, so i removed it from Apps setting.
attached screenshots.
what else can i possibly try ? thank you.
I think you're assuming the "Let's Go" button is inactive simply because it is gray. Tap on it after selecting the boot image. It looks exactly the same on my device. It should work.

You won't see the Restart option if Magisk doesn't have root access, as is shown in your first screenshot: Installed: N/A
 

mailistman

Senior Member
Dec 7, 2012
187
25
You won't see the Restart option if Magisk doesn't have root access, as is shown in your first screenshot: Installed: N/A
true.. i wasn't rooted


I think you're assuming the "Let's Go" button is inactive simply because it is gray. Tap on it after selecting the boot image. It looks exactly the same on my device. It should work.
update : solved my own problem about the greyed out "Lets Go" button : i toggled OFF System > Developer options > Don't keep activities.
you can try to toggle it on or off followed by reboot and see for yourself when you try to select & patch a file.

thank you for all your help over here !
 
Last edited:
  • Like
Reactions: V0latyle

V0latyle

Forum Moderator
Staff member
Magisk Canary 23018 is out.
Changes:
  • [Zygisk] Show warning in app UI to indicate incompatible Zygisk modules
  • [App] Allow modules to specify an update URL for in-app update + install
Update from within Magisk to prevent problems like breaking root.

If you do not already have Magisk installed, Download it here
 
Last edited:

V0latyle

Forum Moderator
Staff member
Magisk Canary updated to 23019
Changes:
- [Zygisk] Skip loading modules into the Magisk app to prevent conflicts
- [MagiskBoot] Change `zopfli` to a more reasonable config so it doesn't take forever
- [General] Several `BusyBox` changes

Preferred method of update is from within Magisk app.

If installing for the first time, here is the APK Download
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    Canary 24310 has been released; this incorporates fixes for an AVB issue that was causing bootloops on the Pixel 6 / 6 Pro.
    4
    Magisk Canary 24309 is out with support for the Pixel 6 Android 13 beta.

    Download
    3
    Hi all, so i have a REALLY STUPID question. I first rooted after april's patch. I have the modded boot image for that particular OTA. What the instructions for this month don't make clear are whether I have to download the ota for may and patch that boot image before doing the automatic phone system update?

    I understand i have to uninstall magisk, disable addons etc before doing it, its just that boot image thing i'm not certain about.

    Because if i've got this right in my head, as it stands while i've got root access, i could install to 2nd slot now, then uninstall magisk etc and then do ota with current patched boot image in slot 2?
    When installing the automatic OTA, you don't download the boot image. When you install Magisk to the inactive slot after taking the OTA, it patches the newly installed boot image in the inactive slot. You perform a Restore Images before the OTA so update_engine finds the stock image before update; otherwise, it will fail. You don't lose root unless you reboot after Restore Images. Do not reboot when System Update prompts you.

    Be sure you're on Magisk 24307 before starting the process.

    Edit: or the newly released 24308, though I haven't seen any reports using that version.
    3
    24307 starts to open and won't get past the screen of the Magisk logo with the mask. It just sits there indefinitely.

    I haven't unlocked the bootloader yet

    See here. For now, you'll have to initially root with 24306 then upgrade to 24307, though I bet it won't be long before 24308, due to this bug.
    2
    I've been doing this for so many years, and never once had any issues flashing factory image to update my phone.
    Granted I don't do OTA, but all I read is how people are having issues with OTA.
    With the exception of one, and only one benefit that I see OTA presents, which is being able to update without needing a computer, I honestly don't see any other value in it.
    If I'm wrong about it, I'm open to learning from my mistakes.
    I'm with you. I always use the factory image. I don't modify system or use a custom kernel, either. In fact I flash to both slots when I update.

    At some point someone is going to have to be willing to take a day or two to experiment and find out exactly what situations cause what problems. As @Lughnasadh pointed out in the 6 Pro thread, OTAs will fail if any read only partitions are modified, or if a custom kernel is used.
  • 41
    If you are looking for my guide on a different Pixel, find it here:
    Update 5-13-22: While Magisk 24.0 has been updated for use with Android 12, many users on the Pixel 6 and 6 Pro are still experiencing issues. It is strongly recommended to use Canary 24310. This version also includes beta support for A13B2.
    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 update bootloader <bootloader image name>
    fastboot reboot bootloader
    ping -n 5 127.0.0.1 > nul
    fastboot update radio <radio image name>
    fastboot reboot bootloader
    ping -n 5 127.0.0.1 > nul
    fastboot update  --skip-reboot --slot=all <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.

    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.

    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:
    To check SafetyNet 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
    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.
    4
    I tinkered a bit and made some wrapped updater script for Windows. Makes the update process of the Pixel 6 a bit more convenient ... I made it just for fun. It's pretty self explanatory, but there's a how-to included anyway.



    EDIT: Updater outdated, will update 0riole_Flasher soon

    >>>UPDATES<<<