How To Guide [GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
- Thread starter V0latyle
- Start date
If you're asking if you need to use a patched Pixel Pro 7 boot image to root on QPR2 Beta 2.1, then yes.
Thank you for 1) clarifying my question and 2) answering my question. If I can hit like twice I would lol.
I guess I'll also download the P7P image and patch its boot for my P6P.
This is one of the best threads on XDA. Mostly because the people here are helpful, patient, and knowledgeable. I appreciate it.
Hi all, I installed the Bliss 16.3 yesterday, it is rooted with Magisk. Now I have an update available in System -Updater and wanted to install it with root. I am on Magisk Uninstall-Restore Image. Then I installed the update since it hasn't restarted yet, went to Magisk and click Install on inactive slot and click Let's go in the top right and the device reboots. When it starts, it doesn't install anything and where it has restarted, there is still a new update available under System Updater Bliss 16.3 from 01/14/2023. I've tried it 3 times today but the update is always there. What am I doing wrong? somehow the update doesn't seem to grab it.
This thread is for the stock firmware, we do not provide support for custom ROMs
Can you show a screen shot of the command you are using? Are you using the recent version of adb that came out this week?
It would be helpful to let others know what you did to fix your initial problem.
For certification, you can try this.
Right i have the safetynet fix installed but im still failing cts profile and google play store play protect certification is not certified
If you're having issues with the Universal SafetyNet Fix module, please ask your questions in that thread:
forum.xda-developers.com
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
it only let me download the kdragon fix not the modded version that you have?
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Link for safetynet-fix-v2.4.0-MOD_1.0.zip
(Hope it os ok to post the link)
Releases · Displax/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - Displax/safetynet-fix
github.com
my issue is fixed sorry about thatIf you're having issues with the Universal SafetyNet Fix module, please ask your questions in that thread:
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
Yasnac is for depricated safety net you should check pi with something like integrity checker https://github.com/1nikolas/play-integrity-checker-app
Similar threads
Top Liked Posts
-
1
Good to know - I've always used the original C to C cable without issues. Guess it depends on the pc (my is fairly recent)1
I had the same exact problem, on delta and using PixelFlasher. After some trial and error I figured out how to get it back to where it was. It's actually really simple. Just uninstall any instance of the Magisk app you have installed, including any hidden magisk app you may have forgotten to unhide (uninstall them just like any other app by long pressing on the app and dragging it to the top where it says uninstall). Once you have all instances of the Magisk app uninstalled, just use PixelFlasher like you normally do. Download the March update, process and patch it, flash it and let PixelFlasher do it's thing. Thats it, you're back to where you were before you lost root except now you're on the March release. All your modules will still be there and enabled (just remember to keep data when flashing). Let me know how it goes.For me update on latest march update is not going to sucess with Root unfortunately
Till now I was using Magisk Delta and used Pixelflasher - worked everytime like a charm.
Now after march update I lost root and am not able to regain it. I patched boot image with Delta Magisk but when booting (live or flash), root is not present.
When selecting Canary Build from Magisk, Pixelflasher is telling
WARNING! Problematic Magisk Manager Version: 981ccabb:25210 is installed. Advised not to use this version.
Anyone facing similar issues and is able to help to regain Root?
Edit:
There seems to be an issue between latest Magisk and March update...
I had to downgrade from 25210 to 25206 which works now flawlessly as usual.1
It really does seem like there are more issues than normal this month. The changelog is posted around here somewhere but I can't remember where I seen it. I highly recommend using PixelFlasher to update your device, it's a very well put together program that Badabing2003 created. I can't say enough good things about it, really well done. It literally takes me 224 seconds every month to update, except this month do to an error on my part. Give it a go, if you have any questions or run into any issues PM me and I'll help you out. -
3
Are you using the correct factory image for your device? It should have "raven" in the file name.
Also, Platform Tools 34.0.0 is known to have problems. Use 33.0.33FYI, Platform Tools 34.0.1 still has the fastbootd problems as well so don't update to that.1
Yeah, I definitely know what I'm doing. Installing 33.0.3 has completely resolved the problem. Thank you for help, you're the MVP.1
To what release-candidate issue are you referring? I was on QPR beta, and just flashed the March (release) update on P6P. Did my usual thing, patch the boot, flash-all, flash the patched boot, got root, no issues. I'm on Magisk 25210.
I have my own unrelated issue that I've seen in the past few months--after flash-all and flash patched boot, restart takes me to an corrupted image. To fix it, I simply re-flash again and everything works.
Add me to the list of those who DID NOT have the issue @ermintrude had.1
This is the first time I've ever run into issues updating the monthly on my P6P, Part my fault because I forgot to unhide Magisk (although I didn't think this would cause issues as it hasn't in the past) but somehow I lost root. Not all that big of a deal as I uninstalled Magisk and patched the new update and that fixed the issue but for some strange unknown reason I'm now showing Magisk Delta (which is what I installed), but I'm also showing the icon for the hidden Magisk app which I uninstalled prior to re-rooting. I'm guessing that one of the files must have been left behind. Strangely, everything is working perfectly, Passes root check and integrity, all my modules are there and working as well. Seeing everything is working as it should and I'm not having any issues I'm just going to leave it as is. I think if I try to uninstall the old Magisk app it might take a file with it that shouldn't be uninstalled and I don't feel like doing a full wipe if I don't need to. Anyone else have an issue similar to this please let me know. -
97
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
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:
- 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 bypass TEE, 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 @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!9Magisk 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.7Magisk 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
New posts
-
Paranoid Android Topaz 1 - Poco F1- Latest: first_damned
-
