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

Search This thread

V0latyle

Forum Moderator
Staff member
Just wanted to say thanks for your time and effort on this @V0latyle - Very Cash Money
boss-glasses-meme-vector-illustration-thug-life-design-vector-id1323446628
 
  • Like
Reactions: roirraW "edor" ehT

Kris Chen

Senior Member
Jan 10, 2013
720
304
Taoyuan
Google Pixel 6 Pro
I want to ask about OTA: Whether can I update OTA but won't lose Magisk root ?

I have another phone - Oneplus8pro. I can OTA and won't lose the magisk root.

1. Donwload full OTA file and flash it ... BUT DON'T REBOOT phone after
finishing it;
2. Open Magisk manager to install Magisk to another inactive slot;
3. Then rebooting phone...

Whether it works at Pixel6 pro OTA ?
 

V0latyle

Forum Moderator
Staff member
I want to ask about OTA: Whether can I update OTA but won't lose Magisk root ?

I have another phone - Oneplus8pro. I can OTA and won't lose the magisk root.

1. Donwload full OTA file and flash it ... BUT DON'T REBOOT phone after
finishing it;
2. Open Magisk manager to install Magisk to another inactive slot;
3. Then rebooting phone...

Whether it works at Pixel6 pro OTA ?
Magisk 23017 is supposed to work that way, not sure if it's working for the P6 though. Until we know it's working for sure, the best way to update is by dirty flashing the factory image.
 

Koss4c

Member
Sep 21, 2016
11
5
Edit : If your having google pay issues or other random google issues/ bank app issues follow this:

Just wanted to throw in, as V0latyle did'nt cover it: the google services: Zygist, Magisk Hide Props Config Module, Universal Safetynet Fix module
A Brilliant video going through installation:

Maybe you could pin this so people can easily follow :)
 
Last edited:
Just wanted to throw in, as V0latyle did'nt cover it: the google services: Zygist, Magisk Hide Props Config Module, Universal Safetynet Fix module
A Brilliant video going through installation:

Maybe you could pin this so people can easily follow :)
I didnt deal with all that and everything is working....curious if others had to do this....
 

roirraW "edor" ehT

Forum Moderator
Staff member
Just wanted to throw in, as V0latyle did'nt cover it: the google services: Zygist, Magisk Hide Props Config Module, Universal Safetynet Fix module
A Brilliant video going through installation:

Maybe you could pin this so people can easily follow :)

I didnt deal with all that and everything is working....curious if others had to do this....
Those things aren't necessary for root proper. They're only necessary for Google Pay, some banking apps, and probably a very few non-banking apps. It's also covered at a high-level in the OP. Just click on the "Spoiler: Pass SafetyNet" in the first post.

I never fooled with those steps before a few months ago but they work perfectly for me to get working Google Pay and a few bankings apps I use.

If you need more detail than @V0latyle gives in the OP, at the top of the list of Pixel 6 Pro threads, click the How To Guide filter:
1642819727041.png

Then look for (or Control-F to search/find for) the thread by @Pekempy called "Working SafetyNet with Pixel 6 Pro Android 12". That first post will give you the detail you need. Please ask any questions if necessary in that thread.
 
Last edited:
  • Like
Reactions: V0latyle
Those things aren't necessary for root proper. They're only necessary for Google Pay, some banking apps, and probably a very few non-banking apps. It's also covered at a high-level in the OP. Just click on the "Spoiler: Pass SafetyNet" in the first post.

I never fooled with those steps before a few months ago but they work perfectly for me to get working Google Pay and a few bankings apps I use.

If you need more detail than @V0latyle gives in the OP, at the top of the list of Pixel 6 Pro threads, click the How To Guide filter:
View attachment 5514969
Then look for (or Control-F to search/find for) the thread by @Pekempy called "Working SafetyNet with Pixel 6 Pro Android 12". That first post will give you the detail you need. Please ask any questions if necessary in that thread.
Yeah I didnt run any su commands like the video does....my banking app and gpay works as advertised :) so I am good there. I need to rewatch when I am less buzzed...now I need to get my google work profile working without failing its checks... :)
 

dilligaf56

Senior Member
Feb 22, 2011
165
45
SoCal, USA
Just curious -
I recently rooted my new unlocked Pixel 6 Pro using the January update, Magisk 23016, Zygisk, etc. Everything worked fine until I tried to activate it with the eSIM on Verizon. There was no second IMEI number available, and I was unable to activate it through the usual routine of scanning the eSIM QR code provided by Verizon. Their level 2 tech worked with me for a couple of hours off and on, then punted and contacted Google tech support without any luck. Does rooting by flashing the factory image kill the eSIM capability? Just curious.

I finally got it activated by using a physical SIM and all is working well - but I would like to have the capability to use it if possible.
 

V0latyle

Forum Moderator
Staff member
Edit : If your having google pay issues or other random google issues/ bank app issues follow this:

Just wanted to throw in, as V0latyle did'nt cover it: the google services: Zygist, Magisk Hide Props Config Module, Universal Safetynet Fix module
A Brilliant video going through installation:

Maybe you could pin this so people can easily follow :)
You didn't read the OP. I absolutely did cover this under "Pass SafetyNet". Don't hijack my thread. I tried to keep instructions relatively simple. I am passing SafetyNet on my Pixel 5 using the modules I mentioned, and did not have to run any commands.
Just curious -
I recently rooted my new unlocked Pixel 6 Pro using the January update, Magisk 23016, Zygisk, etc. Everything worked fine until I tried to activate it with the eSIM on Verizon. There was no second IMEI number available, and I was unable to activate it through the usual routine of scanning the eSIM QR code provided by Verizon. Their level 2 tech worked with me for a couple of hours off and on, then punted and contacted Google tech support without any luck. Does rooting by flashing the factory image kill the eSIM capability? Just curious.
No
I finally got it activated by using a physical SIM and all is working well - but I would like to have the capability to use it if possible.
Unfortunately I can't provide any insight to that issue.
We must connect to Internet first then the OEM Unlocking will come available. (except carrier devices)
Doesn't work for anyone, and problems with unlocking the bootloader are outside the scope of this thread.
 

analyst783

Member
Sep 14, 2010
25
4
Greenville, SC
Google Pixel 6
I tried to apply the Jan update using the android flash tool. There was no 'skip reboot' option (yes, I looked at the 'advanced' options) but I proceeded anyway (prob a very bad decision). Now I cannot boot successfully with a magisk-patched boot image. (Phone evetually winds up in recovery with a 'try again' choice) Did the vbmeta flag get re-enabled? Do I have to wipe to get root back? Finally... how did others use the flash tool? Was 'skip reboot' missing for others?

UPDATE: in the meantime, will try w/flashing the update via fastboot

UPDATE2: back in business w/root. Booting immediately after the flash tool update didn't do any lasting damage (data is intact and readable). I tried the fastboot update as well. The key to getting root back was re-creating my 'master magisk patched' boot image using the latest boot image from the Jan factory image.

I reallllllly thought a 'recent' patched boot image (from Dec in this case) would be sufficient. I still plan to go back and retry the flash tool update (despite the missing 'skip reboot') and see if the updated patched boot image allows root after that.
 
Last edited:

V0latyle

Forum Moderator
Staff member
I tried to apply the Jan update using the android flash tool. There was no 'skip reboot' option (yes, I looked at the 'advanced' options) but I proceeded anyway (prob a very bad decision). Now I cannot boot successfully with a magisk-patched boot image. (Phone evetually winds up in recovery with a 'try again' choice) Did the vbmeta flag get re-enabled?
This has been confusing for a lot of people.

There is no "manual" enabling of verity/verification. They are enabled by default when /vbmeta is flashed. They can only be manually disabled. The point is moot, as disabling verity/verification is not necessary as of Magisk 23016.
Do I have to wipe to get root back?
No. If this happens again, you can always reflash the unpatched boot image to get back to system. You won't have root. But, you can get temporary root by live booting the patched image:
Code:
fastboot boot <patched boot image>

Finally... how did others use the flash tool? Was 'skip reboot' missing for others?
It's been a little while since I used it; the skip reboot option is not available with the Android Flash Tool. My mistake. After the device boots, just reboot to bootloader and flash the patched image.
UPDATE2: back in business w/root. Booting immediately after the flash tool update didn't do any lasting damage (data is intact and readable). I tried the fastboot update as well. The key to getting root back was re-creating my 'master magisk patched' boot image using the latest boot image from the Jan factory image.
Glad you got it straightened out. There's been some weird things going on back and forth with the December and January updates on the P6/P6Pro.

Regardless, if you're having trouble booting the "old" patched image, just download the factory zip and patch the new boot image.
I reallllllly thought a 'recent' patched boot image (from Dec in this case) would be sufficient. I still plan to go back and retry the flash tool update (despite the missing 'skip reboot') and see if the updated patched boot image allows root after that.
It should.
 
  • Like
Reactions: roirraW "edor" ehT

Dragon Kumera

Senior Member
Mar 14, 2019
323
105
Edit : If your having google pay issues or other random google issues/ bank app issues follow this:

Just wanted to throw in, as V0latyle did'nt cover it: the google services: Zygist, Magisk Hide Props Config Module, Universal Safetynet Fix module
A Brilliant video going through installation:

Maybe you could pin this so people can easily follow :)
that a lot of tinkering when it is not needed. But maybe they just had bad luck or are on an older magisk version.

Google pay worked fine on me once google play said certified.
 
  • Like
Reactions: roirraW "edor" ehT
Yeah it was the first I read about anything like that IIRC, it said something about the phone needing to be alive for a week....so if you set the date back further than that you should get OEM Unlock to be un-greyed.....wish I could find that again to link but havent yet :) Again IIRC when I did this it took an hour or two while on the wrong date, but it did un-grey for me....
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    Have you tried live booting followed by a direct install? :) This way if it fails , android will just boot the stock boot image
    That's an excellent idea for @android_dan.

    Edit/add-on:
    Thanks for the reply. Maybe 'm being dense but not sure how the flash tool is going to help. The problem isn't recovering from the bootloop. That's just a matter of flashing an unpatched boot image. The problem is what could be causing the patched file to bootloop the phone. I've updated this rooted phome 3 or 4 times now by flashing a patched boot file with no issues and have changed nothing on the phone
    I suggested the Official Google Android Flash Tool site because it has fixed things that manually flashing the factory image hasn't, in at least a dozen examples I've read about in this section alone in the six months the P6P has been out.

    I know that it doesn't sound necessarily rational, but it's happened often enough and almost every time it's been suggested to someone to do that instead of manually flashing the factory image zip, that the online tool fixed their issue.
    4
    Magisk Canary 24309 is out with support for the Pixel 6 Android 13 beta.

    Download
    4
    No idea.. this was the 1st time it's happened to me on A12. Do you think I should use canary? Mind you, I should note the 'direct install' option was still available, but when I tried it it failed , can't remember the error.

    See post above and I think there's a note a page or two back too. 24.3 doesn't work for the later April FW
    3
    Android Flash Tool got me back into the OS. I patched the May boot.img then flashed it. I'm good and rooted.
    thank you very much for the help
  • 81
    If you are looking for my guide on a different Pixel, find it here:
    Update 5-13-22: While Magisk 24.0 has been updated for use with Android 12, many users on the Pixel 6 and 6 Pro are still experiencing issues. It is strongly recommended to use Canary 24310. This version also includes beta support for A13B2.
    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 update bootloader <bootloader image name>
    fastboot reboot bootloader
    ping -n 5 127.0.0.1 > nul
    fastboot update 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.

    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
    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.
    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