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

Search This thread

Lughnasadh

Senior Member
Mar 23, 2015
3,526
3,611
Google Nexus 5
Huawei Nexus 6P
Yes, I just downloaded the latest set before beginning the process today.

Also, just to make sure I have my head around this, conceptually; I m not actually "flashing" the patched boot image, just using it as a placeholder to kickstart my device, right? Otherwise booting would just fail and not fall back to the non-patched boot image. Please don't be offended, it seems like I'm learning this all over again and want to make sure I get it right.
Well, you can temporarily root by using
Code:
fastboot boot <nameofpatchedbootimage>
and then do a direct install after you boot or you can flash it using
Code:
fastboot flash boot <nameofpatchedbootimage>
 

HolGORE

Member
Oct 28, 2008
32
6
Google Pixel 6 Pro
Short question:

  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.
What means modify the system here? Don't all modules modify the system? I have basic call recorder, disable ipv6 and safetynet fix modules. Do they modify the system?

Thanks
 

roirraW "edor" ehT

Forum Moderator
Staff member
Short question:

  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.
What means modify the system here? Don't all modules modify the system? I have basic call recorder, disable ipv6 and safetynet fix modules. Do they modify the system?

Thanks
For what it's worth, you don't have to uninstall the Magisk Modules. Just disable them. It's good practice just to disable all Magisk Modules before you flash an update, and be prepared that after you re-enable them, the phone might boot loop if one of the modules needs updating to work with the latest OTA.

If the phone does boot loop, then use Safe Mode which will disable all Magisk Modules, then you can boot normally.

Practically speaking, it doesn't sound like you have any modules that would likely cause you a problem, but famous last words, so disable them all.
 
Well, you can temporarily root by using
Code:
fastboot boot <nameofpatchedbootimage>
and then do a direct install after you boot or you can flash it using
Code:
fastboot flash boot <nameofpatchedbootimage>

Best advice that I have incorporated in my monthly update discipline. Manually flash the bootloader and radio and then flash rom.zip. This leaves you in the fastbootd screen. Boot back to bootloader and boot with patched .img and direct install from magisk.
 

punishermoose

Member
Nov 12, 2013
17
2
LG V20
Essential Phone
Best advice that I have incorporated in my monthly update discipline. Manually flash the bootloader and radio and then flash rom.zip. This leaves you in the fastbootd screen. Boot back to bootloader and boot with patched .img and direct install from magisk.
I will try that and report what happens. Thanks for the advice, all.
 
  • Like
Reactions: roirraW "edor" ehT

Cubox.

Member
Aug 14, 2018
13
4
Hi,

Are you guys getting L1 Widevine? Would the L1 Widevine stay if you stock flash and lock the bootloader back?

Thanks
 

State.of.mind

Senior Member
Sep 2, 2011
449
74
Google Pixel 6 Pro
Curious question. When it comes to updating the device, how do you know what Factory image to select? Do you select the factory image based on your current provider? For example, i am using an unlocked P6P (purchased through google), but I am a Verizon customer. Would I select the Factory Update that is compatible with Verizon ie (SQ3A.220705.003.A1, Jul 2022, Verizon, Verizon MVNOs)??
 
Curious question. When it comes to updating the device, how do you know what Factory image to select? Do you select the factory image based on your current provider? For example, i am using an unlocked P6P (purchased through google), but I am a Verizon customer. Would I select the Factory Update that is compatible with Verizon ie (SQ3A.220705.003.A1, Jul 2022, Verizon, Verizon MVNOs)??
Hear! Hear!

You can use any of them as they are all the same, but if there is a carrier specific version available, irrespective of whether you have purchased it from Google or the carrier, it makes more sense to go with the carrier specific version.
 
  • Like
Reactions: State.of.mind

Nergal di Cuthah

Senior Member
Sep 20, 2013
1,793
870
Google Pixel 6 Pro
Curious question. When it comes to updating the device, how do you know what Factory image to select? Do you select the factory image based on your current provider? For example, i am using an unlocked P6P (purchased through google), but I am a Verizon customer. Would I select the Factory Update that is compatible with Verizon ie (SQ3A.220705.003.A1, Jul 2022, Verizon, Verizon MVNOs)??
That
Curious question. When it comes to updating the device, how do you know what Factory image to select? Do you select the factory image based on your current provider? For example, i am using an unlocked P6P (purchased through google), but I am a Verizon customer. Would I select the Factory Update that is compatible with Verizon ie (SQ3A.220705.003.A1, Jul 2022, Verizon, Verizon MVNOs)??
I'm on factory unlocked on vzw and, when there is one, use the vzw build
 
  • Like
Reactions: State.of.mind

V0latyle

Forum Moderator
Staff member
Curious question. When it comes to updating the device, how do you know what Factory image to select? Do you select the factory image based on your current provider? For example, i am using an unlocked P6P (purchased through google), but I am a Verizon customer. Would I select the Factory Update that is compatible with Verizon ie (SQ3A.220705.003.A1, Jul 2022, Verizon, Verizon MVNOs)??
Generally, the carrier named variants contain various fixes/improvements in the baseband image for that specific network, based on the carrier's infrastructure and channel scheme. AFAIK only the baseband is different; everything else is the same as the ROW firmware.

The best way to know for sure would be to compare the various images with a hash checker.
 

HolGORE

Member
Oct 28, 2008
32
6
Google Pixel 6 Pro
For what it's worth, you don't have to uninstall the Magisk Modules. Just disable them. It's good practice just to disable all Magisk Modules before you flash an update, and be prepared that after you re-enable them, the phone might boot loop if one of the modules needs updating to work with the latest OTA.

If the phone does boot loop, then use Safe Mode which will disable all Magisk Modules, then you can boot normally.

Practically speaking, it doesn't sound like you have any modules that would likely cause you a problem, but famous last words, so disable them all.

so i disabled all modules.
rebooted the device
removed magisk, installed the new july update and installed magisk at the inactive slot, like described in the tutorial on first page.
im using magisk 25.1

now i'm stuck at the Google Logo.

any idea what i did wrong?
 

roirraW "edor" ehT

Forum Moderator
Staff member
so i disabled all modules.
rebooted the device
removed magisk, installed the update and installed magisk at the inactive slot, like described in the tutorial on first page.
now i'm stuck at the Google Logo.

any idea what i did wrong?
I can't advise as to the OTA method, because I always flash the full factory image, which is what I would suggest (very important - follow the directions in this guide Spoiler: Update and Root Factory Image, and remove the "-w" from the flash-all.bat or flash-all.sh, depending on whether you're using Windows or Linux).

Alternatively, and often enough it's saved users' bacon when all else fails, use the Spoiler: Update and Root using the Android Flash Tool method.
 

HolGORE

Member
Oct 28, 2008
32
6
Google Pixel 6 Pro
I can't advise as to the OTA method, because I always flash the full factory image, which is what I would suggest (very important - follow the directions in this guide Spoiler: Update and Root Factory Image, and remove the "-w" from the flash-all.bat or flash-all.sh, depending on whether you're using Windows or Linux).

Alternatively, and often enough it's saved users' bacon when all else fails, use the Spoiler: Update and Root using the Android Flash Tool method.
looks like it was the USB cable, that was connected. it was connected to a usb charger, not even to a pc.
after unpluging it the phone started, wtf...
 
  • Like
Reactions: roirraW "edor" ehT

V0latyle

Forum Moderator
Staff member
EijEfV6XkAAlNXl.jpg


How'd you do that?!

@HolGORE I got a bootloop as well when I tried to use the inactive slot method on my wife's 5a. I'm not sure what's wrong with it. Until the problem is discovered, I'd recommend updating using the method of your choice, then manually patching and flashing the new boot image.
 
  • Haha
Reactions: roirraW "edor" ehT

HolGORE

Member
Oct 28, 2008
32
6
Google Pixel 6 Pro
EijEfV6XkAAlNXl.jpg


How'd you do that?!

@HolGORE I got a bootloop as well when I tried to use the inactive slot method on my wife's 5a. I'm not sure what's wrong with it. Until the problem is discovered, I'd recommend updating using the method of your choice, then manually patching and flashing the new boot image.
my phone is starting again, but looks like root is gone.
 
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
This doesn't work with every webpage, but for pages that it does work on like this thread, in Chrome (I'm sure in other Chromium-based, and other browsers as well), just highlight the text you want to create a link to, right-click on top of the highlighted text and choose "Copy link to highlight".

1657223850414.png
 
  • Like
Reactions: HolGORE

V0latyle

Forum Moderator
Staff member
my phone is starting again, but looks like root is gone.
Check your current system version, you can see it at the bottom of the notification windowshade. My guess is that when the system bootlooped, it reverted to the old slot. You will need to re-root by manually patching the boot image. Since you want to update, I suggest doing so using the factory image method. Looks like you already did that. Double check to make sure you are indeed on the newest update, since the system may have reverted to the old slot after bootlooping.

This doesn't work with every webpage, but for pages that it does work on like this thread, in Chrome (I'm sure in other Chromium-based, and other browsers as well), just highlight the text you want to create a link to, right-click on top of the highlighted text and choose "Copy link to highlight".

View attachment 5654571
Neat trick!
 

HolGORE

Member
Oct 28, 2008
32
6
Google Pixel 6 Pro
Check your current system version, you can see it at the bottom of the notification windowshade. My guess is that when the system bootlooped, it reverted to the old slot. You will need to re-root by manually patching the boot image. Since you want to update, I suggest doing so using the factory image method. Looks like you already did that. Double check to make sure you are indeed on the newest update, since the system may have reverted to the old slot after bootlooping.


Neat trick!
Just realized it reverted lol. I guess I try it with the factory method
 

almahix

Senior Member
I don't know how I did it or how to restore the Pixel 6 pro 12 recovery. I can boot into recovery but pressing the buttons doesn't bring up the menu so I can side load. There is just no response. In deparationi used the Android tools to fresh install the new factory image, but it didn't restore the recovery. HELP!
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Folks, I'm going to ask that for further discussion of GPay/Wallet vs Magisk, please take it to this thread. The issues you are having are not isolated to the Pixel 6 / 6 Pro; many other users are having the same problems.

    Let's keep this thread on topic, please.
    4
    My bad. The articles I have seen the past couple of days stated that Google pay was being replaced by Google wallet every where except the US and I think Singapore. I presumed that the US was not getting wallet. I stand corrected. :)
    I believe some Wallet functions are limited in the US, such as being able to upload your driver's license. But, for payment, mine seems to work fine.
    3
    Google wallet is not available in the USA.
    Not true. Works fine for me, and I'm about as American as you can get
    3
    I did not find an A13 root specific thread, so posting here. For an already rooted phone on A12, Magisk 25101, I read that the process to flash A13 is the same. I even read that disabling verity ("flash vbmeta --disable-verity....) may no longer needed. I read something similar in John Wu's thread about disabling verity being a part of Magisk now.

    Is all of the above true?
    Is there any harm in manually disabling verity before first boot anyway?
    Along with SafetyNetFix 2.3.1, are there any new root issues on A13?

    Many thanks.
    Root process is the same for A13 as it is on A12.

    Disabling verity and/or verification is not required, but can be of help when unexpected things arise. I've had both disabled since I got the phone with no problems. If you are disabling them for the first time you will have to wipe (except if you just disable verity alone, then it's likely you won't have to wipe). If you want to keep them disabled you will have to disable with each monthly update. You won't have to wipe when updating unless you boot with them enabled and then want to disable. So disable before booting when doing monthly updates.

    Magisk does not disable verity and verification and no longer strips the avb key from fstab entries as it did before.
    3
    Thanks for your reply and information. This is what caused me to assume that Magisk somehow disabled verity

    That just refers to a specific bug that cropped up on A13B2, Canary 24309, if I remember correctly, where it was required that verity and verification be disabled in order to avoid a bootloop. It was fixed in the next Canary.
  • 87
    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 --slot=all <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. Please note that root access is required to patch.
    1. Download PixelFlasher and the factory image. You do not need to extract the factory image.
    2. Open PixelFlasher. Point the Android Platform Tools directory (browse for your Platform Tools folder)
    3. Point the Factory Image directory to the factory image package you just downloaded.
    4. Connect your device via USB. Ensure it shows up under ADB Connected Devices.
    5. Click the button to the right of the factory image Browse button (looks like a meat grinder). This will extract the boot image from the factory package.
    6. When the boot image appears in the list, click on it and click Patch. A root request should pop up on your device; this is PixelFlasher requesting shell root access through ADB. Make sure you approve it.
    7. PixelFlasher will automatically copy the boot image to your device, patch it in Magisk, then copy it back to your PC. The patched image should now appear in the boot image list.
    8. Select the patched boot image, the desired flash mode (Keep Data), and click Flash Pixel Phone.
    9. Pixel Flasher will automatically update bootloader, radio, system, then finally flash the patched boot image.
    10. When your device boots, you should be updated with root.

    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.

    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:
    To check SafetyNet 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
    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
    7
    I just used this method, (same one described on Magisk website here https://topjohnwu.github.io/Magisk/ota.html) and it worked perfectly, both root and safetynet.
    Can someone explain to me why you see all kind of guide to update which are far more complicated than that ?
    Part of it is due to device differences - non A/B devices can't use seamless updates, so re-rooting is only possible by either patching the boot image directly, or by flashing Magisk in a custom recovery.

    Part of it is also due to user preferences. Some people, like me, prefer to update using the factory images, instead of OTA.

    And part of it is probably a bit of misinformation mixed in with anecdotes, where people who don't fully understand how the process works, but they declare that something has to be done a certain way because of what worked for them.

    I try to stick to the first two. I've spent a lot of time learning about how Android works, so I make a point of providing instructions that align with how everything is supposed to be done, while accommodating alternatives for those who want them.

    Are you 100% sure?

    Cause topjohnwu said that OTA patching from within Magisk was broken for Pixel devices.

    See here

    Notice the date of that post, 16 months ago. Magisk Canary 23017 re-incorporated the ability to install to inactive slots.

    I have been following the commits closely, so when 23017 was released, I announced it in my guides. Had you read back a couple pages, your question has been answered.

    If you don't believe me, check the commits here.