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

Search This thread
By:
Advanced…
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
2,974
1
4,764
The Free State, the Heartland of America
Google Pixel 5
Google Pixel 5a
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
 
  • Like
Reactions: sas46, malybru, belair56 and 4 others
almahix

almahix

Senior Member
Sep 19, 2011
1,320
444
Camarillo, CA USA
www.almahix.com
Google Pixel 6 Pro
I don't know if it has been previously posted but something that saved me a lot of time and made it easier to root is the following link to Magisk. Scroll down the page and you,'ll find a link to download the most recent version of Magisk Canary. Unfortunately it does name the download file with the version number.

github.com

GitHub - topjohnwu/Magisk: The Magic Mask for Android

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com github.com
 
Last edited:
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
2,974
1
4,764
The Free State, the Heartland of America
Google Pixel 5
Google Pixel 5a
almahix said:
I don't know if it has been previously posted but something that saved me a lot of time and made it easier to root is the following link to Magisk. Scroll down the page and you,'ll find a link to download the most recent version of Magisk Canary. Unfortunately it does name the download file with the version number.

github.com

GitHub - topjohnwu/Magisk: The Magic Mask for Android

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com github.com
Click to expand...
Click to collapse
Yes, this was included in the OP.
 
  • Like
Reactions: roirraW "edor" ehT
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
2,974
1
4,764
The Free State, the Heartland of America
Google Pixel 5
Google Pixel 5a
Last edited:
  • Like
Reactions: malybru, mac796, roirraW "edor" ehT and 2 others
Lughnasadh

Lughnasadh

Senior Member
Mar 23, 2015
3,332
3,304
Google Nexus 5
Huawei Nexus 6P
V0latyle said:
@topjohnwu has been busy. He doesn't get nearly enough appreciation for all his hard work.

Magisk Stable is still 23.0.
Magisk Beta is now 24.0
Canary is now 24001

Magisk 24.0 discussion thread
Click to expand...
Click to collapse
Thanks for posting the link to the new Magisk thread. This was so needed and having an active OP is just what the doctored ordered. ipdev is the perfect person to run that thread as well, imo.
 
  • Like
Reactions: V0latyle and roirraW "edor" ehT
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
2,974
1
4,764
The Free State, the Heartland of America
Google Pixel 5
Google Pixel 5a
Lughnasadh said:
Thanks for posting the link to the new Magisk thread. This was so needed and having an active OP is just what the doctored ordered. ipdev is the perfect person to run that thread as well, imo.
Click to expand...
Click to collapse
Absolutely, I also updated the OP of all my Pixel guides.
 
  • Like
Reactions: roirraW "edor" ehT, co9, Lughnasadh and 1 other person
sas46

sas46

Senior Member
Nov 26, 2013
82
9
Florence
V0latyle said:
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
Click to expand...
Click to collapse
I'm on 23016, which of the 3 update way is the safest? Patching boot.img or direct?
Considering that there's no twrp I would opt for patching boot.img but correct me if I'm wrong
 
Last edited:
  • Like
Reactions: State.of.mind
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
2,974
1
4,764
The Free State, the Heartland of America
Google Pixel 5
Google Pixel 5a
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.
 
  • Like
  • Wow
Reactions: Koss4c, sas46, KOLIOSIS and 8 others
D

Dragon Kumera

Senior Member
Mar 14, 2019
323
105
V0latyle said:
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.
Click to expand...
Click to collapse
Thanks! Ya it been a rough ride with p6p but I am so excited these updates have been made and magisk improvements.
 
  • Like
Reactions: Koss4c, jcp2, roirraW "edor" ehT and 1 other person
D

Dragon Kumera

Senior Member
Mar 14, 2019
323
105
side note.

I noticed Verizon app tried to gain root access but was denied. (If anyone knows why this happened, please let me know).
 
Nergal di Cuthah

Nergal di Cuthah

Senior Member
Sep 20, 2013
1,762
844
Google Pixel 6 Pro
Dragon Kumera said:
side note.

I noticed Verizon app tried to gain root access but was denied. (If anyone knows why this happened, please let me know).
Click to expand...
Click to collapse
If you mean "my verizon", I denied mine too. I read an article about how verizon was using the app to monitor more so i denied it. Hasn't effected the app so not sure what is wanted to do either
 
  • Like
Reactions: roirraW "edor" ehT
roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
May 8, 2010
11,610
10,139
Tralfamadore
Sprint Samsung Galaxy S III
Samsung Epic 4G Touch
Dragon Kumera said:
side note.

I noticed Verizon app tried to gain root access but was denied. (If anyone knows why this happened, please let me know).
Click to expand...
Click to collapse
A cheap way for them to find out your phone's rooted, even though there are probably other ways. It's either always or for a very long time done this. I haven't been with Verizon for five years and I remember it did back then too. Think of it as a quick-change artist. Minimum and cheap effort to fool ya into giving them what you probably shouldn't want to give them. :)

Or just looking for stats. :D

Anything that asks for root that I don't want it to know I have root, I have root denied to in Magisk's DenyList.
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
2,974
1
4,764
The Free State, the Heartland of America
Google Pixel 5
Google Pixel 5a
roirraW edor ehT said:
A cheap way for them to find out your phone's rooted, even though there are probably other ways. It's either always or for a very long time done this. I haven't been with Verizon for five years and I remember it did back then too. Think of it as a quick-change artist. Minimum and cheap effort to fool ya into giving them what you probably shouldn't want to give them. :)

Or just looking for stats. :D

Anything that asks for root that I don't want it to know I have root, I have root denied to in Magisk's DenyList.
Click to expand...
Click to collapse
Yeah, this app has always requested root for as long as I've been aware, pretty much since the beginning. Creepy af.
 
  • Like
Reactions: roirraW "edor" ehT
You must log in or register to reply here.

Similar threads

roirraW "edor" ehT
How To Guide May 2022 firmware is out - Unlocking the Pixel 6 Pro bootloader & central repository of relevant links
Replies
801
Views
97K
roirraW "edor" ehT
roirraW "edor" ehT
Freak07
Development [Kernel][03.05.2022][Android 12.1.0][Android 12.1.0 QPR Beta 2] Kirisakura 2.4.0 for Pixel 6/Pro aka "RAVIOLE"
Replies
2K
Views
151K
N
noidea24
Pekempy
How To Guide Working SafetyNet with Pixel 6 Pro Android 12
Replies
618
Views
66K
S
stoph8n24
Typhus_
Themes / Apps / Mods [MOD][MAGISK][ANDROID 12] Addon Features for Pixel Devices - Pixel 6 Pro Thread
Replies
1K
Views
93K
Aberab
Aberab
R
Question Pixel 6 Pro screen protector
Replies
581
Views
61K
L
liggerz87

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 5
    V0latyle
    V0latyle
    Lughnasadh said:
    https://twitter.com/i/web/status/1525077358893445121
    Click to expand...
    Click to collapse
    Confirmed, Canary 24310 now available

    Download
    View
    4
    roirraW "edor" ehT
    roirraW "edor" ehT
    fil3s said:
    Have you tried live booting followed by a direct install? :) This way if it fails , android will just boot the stock boot image
    Click to expand...
    Click to collapse
    That's an excellent idea for @android_dan.

    Edit/add-on:
    android_dan said:
    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
    Click to expand...
    Click to collapse
    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.
    View
    4
    V0latyle
    V0latyle
    Magisk Canary 24309 is out with support for the Pixel 6 Android 13 beta.

    Download
    View
    4
    C
    crypticc
    fil3s said:
    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.
    Click to expand...
    Click to collapse

    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
    View
    3
    M
    metomsky
    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
    View
  • 81
    V0latyle
    V0latyle
    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

    Pixel OTA Images
    Pixel Factory Images
    Magisk Stable, Magisk Canary - Magisk GitHub

    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!
    View
    9
    V0latyle
    V0latyle
    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.
    View
    8
    flar2
    flar2
    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.
    View
    7
    V0latyle
    V0latyle
    Link2811 said:
    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 ?
    Click to expand...
    Click to collapse
    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.

    niko26 said:
    Are you 100% sure?

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

    See here

    https://twitter.com/i/web/status/1303574238796808192
    Click to expand...
    Click to collapse
    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.
    View
    7
    V0latyle
    V0latyle
    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
    View

New posts