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

Search This thread

Oberbergler

Senior Member
May 26, 2015
210
47
I tried sideloading the OTA (downloaded from: https://developers.google.com/android/ota), and that failed as well!! I got an error like this:

"Error applying update: 7 (ErrorCode::kInstallDeviceOpenError) E:Error in /sideload/package.zip (status 1)"

I don't know what's wrong! Please help!
Same problem. Followed the installation process from the description. It's exactly the same how I did it on my Pixel 3 the past 3 years.

Have you found a solution? I absolutely cannot install the update. Tried Nov, Dec and Jan OTA via ADB and system OTA update.
 
can someone point me to the easiest way to update to jan. update without losign my data or my root setup TIA
I disable all magisk modules.
Reboot to bootloader.
fastboot flash-all (with -w removed)
Reboot phone
Transfer boot.img to phone.
Patch with magisk
Transfer patched.img to PC
fastboot flash boot --slot all magiskpatched.img
reboot
re-enable mods one at a time with reboots in between.
Thats my method.
YMMV
 

SMMmmm

Member
Dec 5, 2014
46
6
Same problem. Followed the installation process from the description. It's exactly the same how I did it on my Pixel 3 the past 3 years.

Have you found a solution? I absolutely cannot install the update. Tried Nov, Dec and Jan OTA via ADB and system OTA update.
Yes, I could finally update it to the Jan release.

Follow the 'Update and Root Factory Image' in the OP. That worked for me, follow that exactly and that method doesn't wipe data.
 
  • Like
Reactions: Oberbergler

V0latyle

Forum Moderator
Staff member
But you had to wipe all data, right?
Why would using the Flash Tool require wiping data? Who started that rumor?
can someone point me to the easiest way to update to jan. update without losign my data or my root setup TIA
There are several ways in the OP. Read it.
I disable all magisk modules.
Reboot to bootloader.
fastboot flash-all (with -w removed)
Reboot phone
Transfer boot.img to phone.
Patch with magisk
Transfer patched.img to PC
fastboot flash boot --slot all magiskpatched.img
reboot
re-enable mods one at a time with reboots in between.
Thats my method.
YMMV
Disabling modules or removing Magisk is not necessary.
Yes, I could finally update it to the Jan release.

Follow the 'Update and Root Factory Image' in the OP. That worked for me, follow that exactly and that method doesn't wipe data.
Exactly. It's rather frustrating to see the same question asked repeatedly: "Will the factory method wipe my data?"

No. Just follow the directions exactly as I wrote them.

I am not a fan of having to restore after a data wipe, and I'm not a fan of anyone else having to wipe data. I don't have any tricks up my sleeve that I'm not sharing.

The bottom line, for everyone who keeps wondering if your data will be wiped:

If you read the OP, and did not see any mention of a data wipe being required, then why are you asking?
 

Nightf0x_007

Senior Member
Nov 5, 2012
673
72
while in bootloader executing flash-all it fails to update and says boot partition not found and just updates the radio and the bootloader only
 

Nightf0x_007

Senior Member
Nov 5, 2012
673
72
Now my device when reboots i get your device is corrupted before the bootloader unlocked warning is this new in jan update or ials sowmthing screwed on my phons
 

V0latyle

Forum Moderator
Staff member
while in bootloader executing flash-all it fails to update and says boot partition not found and just updates the radio and the bootloader only
Your Platform Tools are probably out of date. Go back and read the OP.

after flashing magisk patched boot img i get boot failure cant boot system up
Reflash the stock boot image.

Now my device when reboots i get your device is corrupted before the bootloader unlocked warning is this new in jan update or ials sowmthing screwed on my phons
You didn't disable verity/verification, did you?

Also, please post only ONCE. If necessary, edit your post to contain more information, but multiple posts is unnecessary.
 

Nightf0x_007

Senior Member
Nov 5, 2012
673
72
Your Platform Tools are probably out of date. Go back and read the OP.


Reflash the stock boot image.


You didn't disable verity/verification, did you?

Also, please post only ONCE. If necessary, edit your post to contain more information, but multiple posts is unnecessary.
Already disabled dm verity/verification when i eas updating from nov. To dec.

Now my phone is working and updated to jan., I would like to reflashed it again as i feel the phone is not on a stable ground and at any moment it will bootloop
 

V0latyle

Forum Moderator
Staff member
I have magisk 23016 already and i disabled them when i 1st got the phone and updated it from nov. To dec.
I think you misunderstand. Magisk 23016 precludes the need to disable verity/verification; disabling only happens when the /vbmeta partition is flashed. If it is reflashed at any point without the disable options, they are enabled by default. So, if you did not disable verity/verification when you updated to January, they are now enabled. It doesn't matter anyway.

Do this::
  1. Download factory image and extract its contents
  2. Extract boot.img from image-oriole-buildnumber.zip
  3. Manually patch boot image in Magisk, copy patched image to PC
  4. Reboot device to bootloader
  5. Apply update:
    Code:
    fastboot update <drag and drop image-oriole-buildnumber.zip here> --skip-reboot
  6. When update finishes, reboot to bootloader
  7. Flash new patched image:
    Code:
    fastboot flash boot <drag and drop magisk_23016-patched_xxxxx.img here>
  8. Reboot to system.
 

thaitan

New member
Mar 26, 2010
1
0
Is there somewhere a video tutorial...i cant update my rooted pixel 6 to the january update..need some help pls
 

mailistman

Senior Member
Dec 7, 2012
189
25
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 !
Screenshot_20220119-232943.png
 

V0latyle

Forum Moderator
Staff member
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 !
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.
 

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
    Yes, I read about bootloops here after normal (classic) root process (flash factory image without -w and patched boot.img). That works now?

    So, if I disable Magisk modules (have only Systemless hosts and USNF, i can actually do OTA update (restore org image, patch inactive...) and system will reboot normally? Last 2 times i do it, phone won't boot normally.
    I am using those two modules and have never disabled them. The modules that should be disabled are those that modify /system.

    You should in theory be able to use the automatic OTA method. I personally haven't bothered, because my Pixel 5 never gets the notifications and doesn't download the update, so I just use the factory image.
    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.
  • 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<<<