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

Search This thread

StanWiz

Senior Member
Oct 27, 2014
62
15
I'm on my first pixel phone - way down there on the learning curve. I rooted my phone using instructions in this thread . Everything was fine until I received an ota notification, ended up updating using instructions from this thread . End result was the corrupt data problem which I fixed with adb.
Unfortunately when I try to reinstall magysk I end up with data corruption. Is there any way out of this with wiping data?
Thanks
 

westhaking

Senior Member
Jan 18, 2009
235
103
Google Pixel 2
Google Pixel 6 Pro
I'm on my first pixel phone - way down there on the learning curve. I rooted my phone using instructions in this thread . Everything was fine until I received an ota notification, ended up updating using instructions from this thread . End result was the corrupt data problem which I fixed with adb.
Unfortunately when I try to reinstall magysk I end up with data corruption. Is there any way out of this with wiping data?
Thanks
When you get to the step of flashing the magisk image run
Code:
fastboot boot magisk_patched-xxxx.img
and NOT
Code:
fastboot flash boot magisk_patched-xxxx.img

Once it boots, go into your magisk app and install magisk using the Direct Install (Recommended) method. Reboot and hopefully you're good to go.
 
Last edited:
  • Like
Reactions: StanWiz

StanWiz

Senior Member
Oct 27, 2014
62
15
@westhaking - better but not quite there yet. After fastboot boot it tries to reboot twice and gives a possible corrupt message. Retry boots - no error message but magysk is not installed.
(previously retry did not work)
 
Last edited:

V0latyle

Forum Moderator
Staff member
So I have a general question about adb. Is it similar to the Cisco IOS cli? Where you can for example tell it "do sh (sh= show) run | incl vlan. 1" basically can you do a direct grep or does it require a pipe ?
What???

Android Debug Bridge is just that. You can use adb shell to run shell commands, but the purpose is to interface with Android and the device.
 

roirraW "edor" ehT

Forum Moderator
Staff member
So I have a general question about adb. Is it similar to the Cisco IOS cli? Where you can for example tell it "do sh (sh= show) run | incl vlan. 1" basically can you do a direct grep or does it require a pipe ?
Here's a list of adb shell commands and there's at least one example of grep. There are probably other and official sources of this information, but this was one of the first Google search results.

 

StanWiz

Senior Member
Oct 27, 2014
62
15
@westhaking Fyi - I downloaded the latest factory zip,patched the boot.img and flashed the patched image and everything is back to normal. The corrupt message is just a bad memory. I won't try to understand why lol
Thanks
 
  • Love
Reactions: roirraW "edor" ehT

V0latyle

Forum Moderator
Staff member
Yeah there's been multiple reports of people taking the OTA with magisk installed and it giving them the corrupt data message and no boot. Best to always update directly with the factory image.
The OTA shouldn't do this and is considered the "safest" way to update. I suspect the majority of issues have to do with Magisk or other modifications.
 
When you get to the step of flashing the magisk image run
Code:
fastboot boot magisk_patched-xxxx.img
and NOT
Code:
fastboot flash boot magisk_patched-xxxx.img

Once it boots, go into your magisk app and install magisk using the Direct Install (Recommended) method. Reboot and hopefully you're good to go.
I got the your device is corrupt. I think it was bc I accidentally did: fastboot flash boot magisk_patched-xxxx.img[/CODE] instead of fastboot boot magisk_patched-xxxx.img[/CODE]
 

V0latyle

Forum Moderator
Staff member
I got the your device is corrupt. I think it was bc I accidentally did: fastboot flash boot magisk_patched-xxxx.img[/CODE] instead of fastboot boot magisk_patched-xxxx.img[/CODE]
Shouldn't make any difference. What version of Magisk did you use to patch the boot image?
 
  • Like
Reactions: roirraW "edor" ehT

pontozero

Member
Sep 9, 2020
12
1
I would like to know what influences if I install only flash radio.img? will interfere with the cell phone's SIM network?! Or just wifi and bluetooth?
 

V0latyle

Forum Moderator
Staff member
I would like to know what influences if I install only flash radio.img? will interfere with the cell phone's SIM network?! Or just wifi and bluetooth?
The radio modem handles all wireless connectivity, so the radio image contains firmware for all wireless functions. It shouldn't "interfere" with anything - flashing the radio won't change your carrier provisioning, WiFi or Bluetooth settings.
 

pontozero

Member
Sep 9, 2020
12
1
The radio modem handles all wireless connectivity, so the radio image contains firmware for all wireless functions. It shouldn't "interfere" with anything - flashing the radio won't change your carrier provisioning, WiFi or Bluetooth settings.


It's ok! i asked the question because my phone corrupted my EID number i cant add e-sim anymore, thats why i thought it would solve this problem
 

V0latyle

Forum Moderator
Staff member
It's ok! i asked the question because my phone corrupted my EID number i cant add e-sim anymore, thats why i thought it would solve this problem
No, the firmware does not contain IMEI/EID information - that is hard coded into the phone, and if corrupted requires specialty repair.
 
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
What the hell! I searched and tried to repair it by software but I couldn't, because it seems that the service is not starting so it can't add the e-sim again
Maybe the conversation here can help ->
 
  • Like
Reactions: V0latyle

Nawor81

Member
Feb 8, 2017
34
3
I'm at a loss, I have botted to the nov update so therefore any OTA's don't get installed. Now I keep losing root access and don't understand how to keep it
 
I'm at a loss, I have botted to the nov update so therefore any OTA's don't get installed. Now I keep losing root access and don't understand how to keep it
Download and use the Pixel Flasher program. Take your time and read the instructions. It's not a difficult program to use, it's actually quite easy once you use it for the first time. It was a life saver for me, I tried to update my Pixel 6 Pro using a method I found on YouTube and ended up losing root also. Once I installed Pixel Flasher on my PC I ran the program, it was fully automated, it installs the November update including the latest version of magisk which automatically patches the boot img and installs without wiping data. Great program badabing created.
 
  • Like
Reactions: V0latyle

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    This is one of the best threads on XDA. Mostly because the people here are helpful, patient, and knowledgeable. I appreciate it.
    2
    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.
    1
    Does the January QPR patch still have the boot issues like December?
    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.
    1
    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
  • 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:
    Update 6-20-22: Magisk 25.1 is recommended as this includes fixes for OTA updates, as well as support for the Android 13 beta.
    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 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.

    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
    Modules:
    • Universal SafetyNet Fix 2.3.1 Mod - XDA post
    To check SafetyNet status:
    To check Play Integrity 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!
    9
    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.
    8
    My update process is to remove vbmeta.img (in addition to removing the -w flag in the flash-all script) from the factory zip before I flash it in fastboot. Seems to have worked so far, ymmv.
    7
    Now THIS is a useful thread! Thanks 👍

    I might try to root my P6P this week-end.

    If I already took the OTA from Google, can I just go to #6? (there's no data on my phone yet, just BL unlocked)

    "6. Reflash vbmeta to disable boot verification"
    7
    Magisk 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