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

Search This thread
By:
Advanced…
O

Oberbergler

Senior Member
May 26, 2015
211
48
SMMmmm said:
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!
Click to expand...
Click to collapse
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.
 
Slim2none4u

Slim2none4u

Senior Member
Oct 28, 2011
1,092
801
50
Livermore Falls
www.youtube.com
Verizon Droid Incredible 2
Sprint HTC EVO 4G LTE
Nightf0x_007 said:
can someone point me to the easiest way to update to jan. update without losign my data or my root setup TIA
Click to expand...
Click to collapse
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
 
S

SMMmmm

Member
Dec 5, 2014
49
11
Oberbergler said:
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.
Click to expand...
Click to collapse
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

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
10,299
5
18,207
The Heartland of America
Google Pixel 5
Google Pixel 5a
Oberbergler said:
But you had to wipe all data, right?
Click to expand...
Click to collapse
Why would using the Flash Tool require wiping data? Who started that rumor?
Nightf0x_007 said:
can someone point me to the easiest way to update to jan. update without losign my data or my root setup TIA
Click to expand...
Click to collapse
There are several ways in the OP. Read it.
rhewins2268 said:
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
Click to expand...
Click to collapse
Disabling modules or removing Magisk is not necessary.
SMMmmm said:
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.
Click to expand...
Click to collapse
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?
 
  • Like
  • Haha
Reactions: co9, Oberbergler and Slim2none4u
N

Nightf0x_007

Senior Member
Nov 5, 2012
818
90
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
 
N

Nightf0x_007

Senior Member
Nov 5, 2012
818
90
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

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
10,299
5
18,207
The Heartland of America
Google Pixel 5
Google Pixel 5a
Nightf0x_007 said:
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
Click to expand...
Click to collapse
Your Platform Tools are probably out of date. Go back and read the OP.

Nightf0x_007 said:
after flashing magisk patched boot img i get boot failure cant boot system up
Click to expand...
Click to collapse
Reflash the stock boot image.

Nightf0x_007 said:
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
Click to expand...
Click to collapse
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.
 
N

Nightf0x_007

Senior Member
Nov 5, 2012
818
90
V0latyle said:
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.
Click to expand...
Click to collapse
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

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
10,299
5
18,207
The Heartland of America
Google Pixel 5
Google Pixel 5a
Nightf0x_007 said:
I have magisk 23016 already and i disabled them when i 1st got the phone and updated it from nov. To dec.
Click to expand...
Click to collapse
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.
 
T

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
 
M

mailistman

Senior Member
Dec 7, 2012
195
27
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

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
10,299
5
18,207
The Heartland of America
Google Pixel 5
Google Pixel 5a
mailistman said:
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 !
Click to expand...
Click to collapse
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.
 
You must log in or register to reply here.

Similar threads

H
How To Guide [Guide] [January 3, 2024] Root Pixel 6 Unlock Bootloader + Pass SafetyNet + Both Slots Bootable + More
Replies
757
Views
154K
R
RimWulf
L
How To Guide Sim unlock tmobile pixel 6
Replies
239
Views
89K
K
Kel Ghu
V0latyle
  • Sticky
General PSA: Pixel 6 Bootloader Anti-Rollback
Replies
124
Views
56K
V0latyle
V0latyle
H
How To Guide Converting Japanese Pixel 6 to Global version
Replies
223
Views
87K
Y
yasinkhan1438
badabing2003
Themes / Apps / Mods 📳🔥PixelFlasher for Google Pixel 6 Support Thread.
Replies
714
Views
62K
badabing2003
badabing2003

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 53
    V0latyle
    V0latyle
    ⚠️⚠️⚠️WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST! ⚠️⚠️⚠️

    Official updates for this device will end October 2024.

    If you are looking for my guide on a different Pixel, find it here:
    For best results, use the latest stable Magisk release.
    Discussion thread for migration to 24.0+.
    Note: Magisk prior to Canary 23016 does not incorporate the necessary fixes for Android 12+.

    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

    Pixel OTA Images
    Pixel Factory Images
    Magisk Stable, Magisk Canary - Magisk GitHub

    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.

    Before asking any questions, please read this post.
    For help passing Play Integrity verdicts, see this thread.

    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_20230323-072859-3-png.5870161
    • "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 @badabing2003 , @pndwal , @Displax , @Az Biker , @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!
    View
    7
    V0latyle
    V0latyle
    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.
    View
    5
    capntrips
    capntrips
    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.
    View
    5
    soodz
    soodz
    V0latyle said:
    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.
    Click to expand...
    Click to collapse
    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
    View
    5
    capntrips
    capntrips
    KedarWolf said:
    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?
    Click to expand...
    Click to collapse

    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.
    View

New posts