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

Search This thread
By:
Advanced…
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
10,299
5
18,207
The Heartland of America
Google Pixel 5
Google Pixel 5a
Magisk Stable is now at version 24.1, so I will no longer be providing any Magisk updates.

You can use any version of Magisk now - Stable, Beta, or Canary. as long as it is 23016 or newer.

Once again, if you want to switch versions of Maagisk, it is HIGHLY RECOMMENDED that you "Complete Uninstall" within Magisk before installing the new version. Multiple instances of Magisk can break root.

If you simply want to update Magisk, the best way to do so is from within the app.

Once the February update is out, I will perform some testing with installing to inactive slot, and if it works, I will update this guide.

Given the low activity on this thread, I will probably close it if everything goes well with the next update.

Thank you all for your testing and contributions.
 
  • Like
Reactions: MattP410, co9, Nezorflame and 1 other person
A

awesomeo3000

Member
Dec 29, 2011
38
12
I followed the instructions, but I am unable to take OTA updates. It just says "installation problem." Then when I tried repeating the steps for SQ1D.220105.007 factory image, it gets stuck on the "G" screen at boot, so I had to revert back to the patched SD1A.210817.036.A8 boot.img. I also tried reflashing the original unpatched SD1A.210817.036.A8 boot.img to take the OTA, and that still says "installation problem."
 
A

awesomeo3000

Member
Dec 29, 2011
38
12
V0latyle said:
  1. Follow the instructions on the Android Flash Tool to update your device. Check the "Skip reboot" box.
  2. When the update completes, the device will be in fastbootd. Reboot to bootloader.
Click to expand...
Click to collapse
I was about to try the Android Flash Tool, but I noticed that it says it will lock the bootloader as part of the process, and there's no option to uncheck that. I also don't see anything that looks like a "Skip reboot" box. I thought that if we lock the bootloader while the phone is rooted, it gets bricked? Here's a screenshot of what I see in the AFT.
Screen Shot 2022-01-28 at 8.03.19 PM.png
 
capntrips

capntrips

Senior Member
Aug 29, 2020
367
839
OnePlus 6T
Google Pixel 6
awesomeo3000 said:
I was about to try the Android Flash Tool, but I noticed that it says it will lock the bootloader as part of the process, and there's no option to uncheck that. I also don't see anything that looks like a "Skip reboot" box. I thought that if we lock the bootloader while the phone is rooted, it gets bricked? Here's a screenshot of what I see in the AFT.View attachment 5521939
Click to expand...
Click to collapse

Before clicking "Install Build", click the pencil icon to see the flashing options.

Screenshot_20220128-202306~2.png

Screenshot_20220128-202424.png
 
  • Like
Reactions: catseyenu and V0latyle
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
10,299
5
18,207
The Heartland of America
Google Pixel 5
Google Pixel 5a
awesomeo3000 said:
I followed the instructions, but I am unable to take OTA updates. It just says "installation problem." Then when I tried repeating the steps for SQ1D.220105.007 factory image, it gets stuck on the "G" screen at boot, so I had to revert back to the patched SD1A.210817.036.A8 boot.img. I also tried reflashing the original unpatched SD1A.210817.036.A8 boot.img to take the OTA, and that still says "installation problem."
Click to expand...
Click to collapse
If you try the factory update method, extract and patch the new boot image. You are using Magisk 24.0, correct?
awesomeo3000 said:
I was about to try the Android Flash Tool, but I noticed that it says it will lock the bootloader as part of the process, and there's no option to uncheck that. I also don't see anything that looks like a "Skip reboot" box. I thought that if we lock the bootloader while the phone is rooted, it gets bricked? Here's a screenshot of what I see in the AFT.
Click to expand...
Click to collapse
You missed a step. There's a little pencil icon you have to click when you're selecting the build. That opens the options menu where you can select "Lock bootloader", "Wipe data", "Force flash all partitions", etc. There is no skip reboot option; to do that you have to manually flash via ADB.
 
A

awesomeo3000

Member
Dec 29, 2011
38
12
V0latyle said:
If you try the factory update method, extract and patch the new boot image. You are using Magisk 24.0, correct?

You missed a step. There's a little pencil icon you have to click when you're selecting the build. That opens the options menu where you can select "Lock bootloader", "Wipe data", "Force flash all partitions", etc. There is no skip reboot option; to do that you have to manually flash via ADB.
Click to expand...
Click to collapse
I am using Magisk 24.1. I got it to work by downloading the latest OTA and using your OTA sideload instructions, then recreated the master root image and reflashed. All this got my root back and I started with a fresh wipe.

Any ideas why the regular OTA download wasn't working? If it worked as expected, I wouldn't have to wipe the phone every time, right? If I'm able to just download the OTA from Settings, Updates, and then boot the master root image, all apps and configs on the phone stays preserved?

And good call on the AFT. If I uncheck the wipe data and lock bootloader, will that mess anything up for the updates? I really don't want to wipe every time.
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
10,299
5
18,207
The Heartland of America
Google Pixel 5
Google Pixel 5a
awesomeo3000 said:
I am using Magisk 24.1. I got it to work by downloading the latest OTA and using your OTA sideload instructions, then recreated the master root image and reflashed. All this got my root back and I started with a fresh wipe.

Any ideas why the regular OTA download wasn't working? If it worked as expected, I wouldn't have to wipe the phone every time, right? If I'm able to just download the OTA from Settings, Updates, and then boot the master root image, all apps and configs on the phone stays preserved?
Click to expand...
Click to collapse
You should never have to wipe your phone. Automatic OTA is iffy with a patched boot image. You can try "Restore Boot Image" in Magisk, then download OTA, then select "Install to inactive slot" before rebooting.

Or, you can sideload the OTA, let it boot, reboot to bootloader, temp boot a previously patched image, and perform Direct Install in Magisk.
awesomeo3000 said:
And good call on the AFT. If I uncheck the wipe data and lock bootloader, will that mess anything up for the updates? I really don't want to wipe every time.
Click to expand...
Click to collapse
Nope.

The way I prefer to update is by flashing the factory zip. We will see what happens with the February update to see if OTA root really is fixed in Magisk.
 
capntrips

capntrips

Senior Member
Aug 29, 2020
367
839
OnePlus 6T
Google Pixel 6
awesomeo3000 said:
Any ideas why the regular OTA download wasn't working?
Click to expand...
Click to collapse

The OTA from System Update is a delta OTA, so it compares the hashes of the partitions in your active slot to those expected of a completely stock system. If you are rooted, you'll first need to restore your boot partition. If you're on older builds of Android and Magisk, you may need to restore your vbmeta partition. One person claimed their bootloader and radio partitions being out of sync prevented them from taking the OTA.

You can filter your logcat for update_engine to see what partition is preventing you from updating, but if you're going to plug into a computer to check that, you may as well just flash the build manually.

For more detail on taking an OTA, see Magisk's OTA upgrade guide for devices with A/B partitions:

OTA Upgrade Guides

The Magic Mask for Android
topjohnwu.github.io

The note and linked tweet at the top of that page are now out of date, as of build 23017.
 
  • Like
Reactions: V0latyle
A

awesomeo3000

Member
Dec 29, 2011
38
12
V0latyle said:
You should never have to wipe your phone. Automatic OTA is iffy with a patched boot image. You can try "Restore Boot Image" in Magisk, then download OTA, then select "Install to inactive slot" before rebooting.

Or, you can sideload the OTA, let it boot, reboot to bootloader, temp boot a previously patched image, and perform Direct Install in Magisk.

Nope.

The way I prefer to update is by flashing the factory zip. We will see what happens with the February update to see if OTA root really is fixed in Magisk.
Click to expand...
Click to collapse
I considered flashing the factory zip, but didn't want to mess with the bootloader and radio since that's in the brick zone.
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
10,299
5
18,207
The Heartland of America
Google Pixel 5
Google Pixel 5a
awesomeo3000 said:
I considered flashing the factory zip, but didn't want to mess with the bootloader and radio since that's in the brick zone.
Click to expand...
Click to collapse
Simply follow the directions exactly as written and you won't have any problems.
gazdajezda said:
Is this method succesfully tested with Android 12? The most simplest one.
Click to expand...
Click to collapse
I'm not sure, but per @capntrips post above, it makes sense. More detailed instructions:
  1. Prior to downloading OTA, open Magisk, tap Uninstall, tap Restore Boot Images. Do not reboot.
  2. Manually start the OTA download: Settings > System > System update > Check for update or Download and install
  3. When prompted to reboot to complete the update, do not reboot. Open Magisk, tap Install in the Magisk section, select "Install to Inactive Slot (After OTA)", tap Let's Go. Allow it to reboot your device when prompted.
  4. You should reboot into updated system with root.
 
G

gazdajezda

Senior Member
Apr 24, 2011
457
98
Ok, i guess we will know for sure soon. I started it, now downloading update... If i not came back in an half an hour, it was a failure 😁
 
G

gazdajezda

Senior Member
Apr 24, 2011
457
98
I type this from computer :( It finished and after that i install Magisk to other (inactive) slot and reboot. It's been stuck on rainbow G with line sponning form left to right for some 15 minutes now. I think it won't boot. What can i do now?
 
G

gazdajezda

Senior Member
Apr 24, 2011
457
98
I managed to boot it, aparently from other slot with old unpatched boot image so update to latest version was not succesfull. I will root it back now, but i'm afraid that it will again start downloading / installing it. I have disabled this option "Developer options / Automatic system updates" IS disabled. But it already show that updates are ready and i think it will start downloadaing it / installing after as soon i will turn on Wifi. Ahhh...

I used Magisk 24101, is that version ok?
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
10,299
5
18,207
The Heartland of America
Google Pixel 5
Google Pixel 5a
manjaroid said:
To update from Canary 24101 to Stable 24.1 it's not clear to me if just switching channels is enough. Uninstall first?
Click to expand...
Click to collapse
Yes - but do it from within the app. Select Complete Uninstall. Magisk will restore your boot image, remove itself, then reboot your device. After it does so, install Magisk Stable. From here, you can either manually re-patch the factory boot image with Stable, or you can live boot a previously patched boot image (it won't matter if it was patched with Canary) for temporary root, then perform Direct Install within Magisk.
 
  • Like
Reactions: manjaroid
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