How To Guide [GUIDE] Pixel 6 "oriole": Unlock Bootloader, Update, Root, Pass SafetyNet
- Thread starter V0latyle
- Start date
GrandAdmiral
Senior Member
Yeah, only use one module of a type at a time. You can use USNF 2.4.0 with MHPC, although the latter is no longer being developed to my knowledge
GrandAdmiral
Senior Member
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?
Now... do I want to update the latest GPay that just rolled out?
Last edited:
USNF 2.4.0 works for me on my Pixel 5.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?
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
Definitely is definitely the wrong adverb
I think Wallet randomly stopped working for me but I had changed something in Magisk, so after enabling DenyList on all subprocesses of Wallet/GPay and clearing data on Wallet, it works fine.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
GrandAdmiral
Senior Member
I got it. I got it. LolSeems 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
phaino00
Senior Member
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 can say the lastest gpay update caused gpay not to work with USNF 2.4, at least for me. Reverted to Dispax's MOD 2.1 and cleared data of gpay app and gpay is working again.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 installed feb update yday but USNF 2.4.0 wasn't passing integrity anymore but there is 2.3.1 mod 3.0 fix already out which is working
Who what? Huh?! I wasn't there that day, you can't prove anything....Oh.
Nah. The assumption should always be that things are working as they should, and whoever is reading the thread can take note of the last few posts at the end.
Completely unrelated: Magisk 25.2 works on the 14 Developer Preview...but Zygisk doesn't work for some reason
Pretty common for OTAs to not work while rooted. Either use the factory method or sideload OTA
I have not rooted an Android device in years so I apologize for the inexperience.
I have an unlocked Pixel 6
Android 13 Nov 2022 software release.
I have unlocked the boot loader, installed Magisk, patched the proper boot file, transferred it back to my pc and then ran `fastboot boot <imgname>.img`
my device loads and reboots on its own.
Once it reboots I go to Magisk and it is stil N/A so not rooted.
I am not sure what I might be missing I have checked a couple of guides and all have the same process.
Thank you for the help
I have an unlocked Pixel 6
Android 13 Nov 2022 software release.
I have unlocked the boot loader, installed Magisk, patched the proper boot file, transferred it back to my pc and then ran `fastboot boot <imgname>.img`
my device loads and reboots on its own.
Once it reboots I go to Magisk and it is stil N/A so not rooted.
I am not sure what I might be missing I have checked a couple of guides and all have the same process.
Thank you for the help
Attachments
Something about the root patch seems to interfere with normal automatic OTAs. This happens to a lot of people. For some reason the system doesn't check for and download the update.
The update methods that work are described in the OP.
What version of Magisk are you using?
Try flashing the patched image to /boot.
I am using the latest version of Magisk downloaded today.
I can try the boot dir
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2
With Pixel Flasher you can. To do it manually you'll need to flash one slot, set the active slot to the other slot and then flash again.1
Canary 25207, 25208, 25209 and 25210 have issues. You can use 25206 or the stable version.1
34.0.1 is not working. It does not switch to fastbootd to flash product.img and other images. Had to downgrade to 33.0.3 to install March build.1magisk-files/app-release.apk at 5b2934603f979d7133e67bbc30c6ce3fa0d8e31e · topjohnwu/magisk-files
Magisk File Host. Contribute to...
github.com
1 -
50
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:
- Pixel 3
- Pixel 3XL
- Pixel 3a
- Pixel 3aXL
- Pixel 4
- Pixel 4XL
- Pixel 4a
- Pixel 4a (5G)
- Pixel 5
- Pixel 5a
- Pixel 6 Pro
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:
- Latest SDK Platform Tools - if Platform Tools is out of date, you WILL run into problems!
- USB Debugging enabled
- Google USB Driver installed
- I recommend using Command Prompt for these instructions; some users have difficulty with PowerShell.
Make sure the Command Prompt is running from your Platform Tools directory!
Android Source - Setting up a device for development
- Follow these instructions to enable Developer Options and USB Debugging.
- Enable OEM Unlocking. If this option is grayed out, unlocking the bootloader is not possible.
- Connect your device to your PC, and open a command window in your Platform Tools folder.
- Ensure ADB sees your device:
If you don't see a device, make sure USB Debugging is enabled, reconnect the USB cable, or try a different USB cable.Code:
adb devices
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. - Reboot to bootloader:
Code:
adb reboot bootloader - Unlock bootloader: THIS WILL WIPE YOUR DEVICE!
Select Continue on the device screen.Code:
fastboot flashing unlock
- Install Magisk on your device.
- Download the factory zip for your build.
- Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img
- Copy boot.img to your device.
- Patch boot.img with Magisk: "Install" > "Select and Patch a File"
- 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.
- Reboot your device to bootloader.
- Flash the patched image:
Code:
fastboot flash boot <drag and drop master root.img here> - Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>
- Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.
- Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
- 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.
- You should now be updated with root.
- Download the OTA.
- Reboot to recovery and sideload the OTA:
Once in recovery:Code:
adb reboot sideload
Code:adb sideload ota.zip - When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
- Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
- Reboot to bootloader.
- Boot the master root image (See note 1):
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.Code:
fastboot boot <drag and drop master root.img here> - Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
- Reboot your device. You should now be updated with root.
Please note that the factory update process expects an updated bootloader and radio. If these are not up to date, the update will fail.
- Download the factory zip and extract the contents.
- Reboot to bootloader.
-
Compare bootloader versions between phone screen and bootloader.img build numberIf bootloader is updated, reboot to bootloader.Code:
fastboot flash bootloader <drag and drop new bootloader.img here> -
Compare baseband versions between phone screen and radio.img build numberIf radio is updated, reboot to bootloader.Code:
fastboot flash radio <drag and drop radio.img here> - Apply update:
When the update completes, the device will be in fastbootd. Reboot to bootloader.Code:fastboot update --skip-reboot image-codename-buildnumber.zip - Boot the master root image (See note 1):
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.Code:
fastboot boot <drag and drop master root.img here> - Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
- Reboot your device. You should now be updated with root.
flash-allscript 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-woption so it doesn't wipe your device.
The scripted commands should look like this:
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.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>
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.
- Follow the instructions on the Android Flash Tool to update your device. Make sure Lock Bootloader and Wipe Device are UNCHECKED.
- When the update completes, the device will be in fastbootd. Reboot to bootloader.
- Boot the master root image (See note 1):
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.Code:
fastboot boot <drag and drop master root.img here> - Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
- 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 force basic attestation instead of hardware, 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
- Universal SafetyNet Fix 2.3.1 Mod - XDA post
To check Play Integrity status:
- Play Integrity Checker - NOTE:
MEETS_STRONG_INTEGRITYwill ALWAYS fail on an unlocked bootloader.
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:
- "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!7Magisk 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.5Magisk 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
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 OTA5
No, the tool does nothing to maintain root. It simply allows you to take the OTA. You will still need to reboot intofastbootand flash or boot from a patchedbootimage.
The steps would be:
- Restore
bootin the Magisk app - Restore
vbmetain Vbmeta Patcher - Take the OTA in System Updater
- Patch
vbmetain Vbmeta Patcher - Patch the new
bootimage in the Magisk app and copy it to your computer - Reboot into
fastboot - Boot from the new patched
bootimage - Direct Install Magisk in the Magisk App
I'm working on another tool to make it a bit easier to acquire the newbootimage 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.
