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

Search This thread
By:
Advanced…
S

skankerveen

New member
Sep 24, 2011
2
0
I hard bricked my device today (doesn't even turn on - can't even get into fastboot recovery). I'll explain what happened so perhaps others can avoid my mistakes in the future.

I was using:
Platform-tools Version 34.0.1-9680074
Factory image raven-t3b2.230316.005-factory-3923dd64
Magisk v26.1
Magisk patched my boot image, named: magisk_patched-26100_Xq7GU

I followed this guide to the letter (I think😅), however, I did not read any of the thread past the OP before starting.
I encountered a boot loop after Step 8 of Initial Root / Create Master Root Image, and doing a fastboot reboot. I did not specify a boot area
fastboot flash boot[_a or _b] <drag and drop master root.img here>.
After encountering the boot loop, I tried to flash the original boot.img from the factory image, reflashing the magisk patched, but none of it was able to recover from the boot loop.
I then made the mistake which led to a hard brick, which was to flash the original boot.img to boot_b (fastboot flash boot_b boot.img) and use fastboot --set-active=b to force the bootloader to use that (I am not an expert, I did not know the consequences, and I take full responsibility for taking these matters into my own hands instead of asking for help). My device began to bootloop for several minutes, although the bootloop was extremely quick compared to before so I thought it was a positive sign. However, I then decided to hold the power button to force it off and boot into fastboot/recovery. Once powered off, it no longer powers on and it is hard bricked.

This was a few hours of frustration condensed, so perhaps I've overlooked some things, but felt worthwhile to post here in case anybody is interested.
 
Nergal di Cuthah

Nergal di Cuthah

Senior Member
Sep 20, 2013
2,177
1,240
Google Pixel 6 Pro
Switch to platform tools before 34.x. it is bugged, and does what you describe in your post, i think. The fix is in march or april so readback a few pages, both for the fix and the previous working platform tools (i think it was discussed after/during the roll out of march update (which i believe is the end of march)).
 
Nergal di Cuthah

Nergal di Cuthah

Senior Member
Sep 20, 2013
2,177
1,240
Google Pixel 6 Pro
skankerveen said:
I hard bricked my device today (doesn't even turn on - can't even get into fastboot recovery). I'll explain what happened so perhaps others can avoid my mistakes in the future.

I was using:
Platform-tools Version 34.0.1-9680074
Factory image raven-t3b2.230316.005-factory-3923dd64
Magisk v26.1
Magisk patched my boot image, named: magisk_patched-26100_Xq7GU

I followed this guide to the letter (I think😅), however, I did not read any of the thread past the OP before starting.
I encountered a boot loop after Step 8 of Initial Root / Create Master Root Image, and doing a fastboot reboot. I did not specify a boot area
fastboot flash boot[_a or _b] <drag and drop master root.img here>.
After encountering the boot loop, I tried to flash the original boot.img from the factory image, reflashing the magisk patched, but none of it was able to recover from the boot loop.
I then made the mistake which led to a hard brick, which was to flash the original boot.img to boot_b (fastboot flash boot_b boot.img) and use fastboot --set-active=b to force the bootloader to use that (I am not an expert, I did not know the consequences, and I take full responsibility for taking these matters into my own hands instead of asking for help). My device began to bootloop for several minutes, although the bootloop was extremely quick compared to before so I thought it was a positive sign. However, I then decided to hold the power button to force it off and boot into fastboot/recovery. Once powered off, it no longer powers on and it is hard bricked.

This was a few hours of frustration condensed, so perhaps I've overlooked some things, but felt worthwhile to post here in case anybody is interested.
Click to expand...
Click to collapse
Here's the link for old platform tool
forum.xda-developers.com

September 18, 2023 TQ3A.230901.001 Global | .C2 Verizon - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet

Pixel 7 Pro [Cheetah] Updated July 13, 2023 Note that multiple users in several threads have said that 34.0.4 did not work correctly for them. I recommend sticking with 33.0.3 (below): Anyone that updated their platform tools and needs to...
forum.xda-developers.com forum.xda-developers.com
 
S

skankerveen

New member
Sep 24, 2011
2
0
Doesn't really matter as my device is hard-bricked. Left on the charger all night just to make sure, but it still won't even turn on.
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
8,335
4
13,715
The Heartland of America
Google Pixel 5
Google Pixel 5a
skankerveen said:
Doesn't really matter as my device is hard-bricked. Left on the charger all night just to make sure, but it still won't even turn on.
Click to expand...
Click to collapse
Sorry to hear that. Unfortunately your only option is to have it repaired by replacing the mainboard (most repair centers do not perform low level flashing). If you're still under warranty this should be free, just tell them it stopped working completely.
 
R

Remanifest

Senior Member
Feb 22, 2010
102
13
San Antonio, TX
Interesting to see the comments RE adb causing a bootloop. I'm using adb version 1.0.41 on Linux, and I didn't encounter any problems with the update using the factory image. Maybe I just got lucky, or maybe the bug is platform-specific?
 
S

Sand_23

Member
Feb 10, 2023
10
1
Google Pixel 6 Pro
I got a question about rooting. I updated my p6p to TQ2A.230305.008.E1. I deinstalled magisk before and all Modules. But i cant find the factory Image to extract and create a new boot Image to Patch. I stored my old master root boot image but can i use it again? Is there any alternative? Thx in advance
 
Nergal di Cuthah

Nergal di Cuthah

Senior Member
Sep 20, 2013
2,177
1,240
Google Pixel 6 Pro
Sand_23 said:
I got a question about rooting. I updated my p6p to TQ2A.230305.008.E1. I deinstalled magisk before and all Modules. But i cant find the factory Image to extract and create a new boot Image to Patch. I stored my old master root boot image but can i use it again? Is there any alternative? Thx in advance
Click to expand...
Click to collapse
forum.xda-developers.com

September 18, 2023 TQ3A.230901.001 Global | .C1 T-Mobile | .C2 Verizon - Root Pixel 6 Pro [Raven]

Pixel 6 Pro [Raven] Updated July 13, 2023 Note that multiple users in several threads have said that 34.0.4 did not work correctly for them. I recommend sticking with 33.0.3 (below): Anyone that updated their platform tools and needs to...
forum.xda-developers.com forum.xda-developers.com
First post april 10th entry
 
S

Sand_23

Member
Feb 10, 2023
10
1
Google Pixel 6 Pro
Nergal di Cuthah said:
forum.xda-developers.com

September 18, 2023 TQ3A.230901.001 Global | .C1 T-Mobile | .C2 Verizon - Root Pixel 6 Pro [Raven]

Pixel 6 Pro [Raven] Updated July 13, 2023 Note that multiple users in several threads have said that 34.0.4 did not work correctly for them. I recommend sticking with 33.0.3 (below): Anyone that updated their platform tools and needs to...
forum.xda-developers.com forum.xda-developers.com
First post april 10th entry
Click to expand...
Click to collapse
But this is an other Version, see the numbers. Sorry, iam confused
 
Nergal di Cuthah

Nergal di Cuthah

Senior Member
Sep 20, 2013
2,177
1,240
Google Pixel 6 Pro
Sand_23 said:
Phone update all by itself and in month steps
Click to expand...
Click to collapse
Since your rooted you must be bootloader unlocked. you could flash updates with the "flash" link in update table.
Won't have to do anything to remove root after. Just need to flash patched boot like your already doing.

Tl:dr stepped out

Step one: download factory image from "link" link. Extract boot.img as per usual. Copy it to the download folder of your phone.

Step two: connect your phone to computer and press the table's "flash" link

Step three: progress through flash website the link takes you to. When it's done reboot your phone and let it boot up. There's a silent notification "android is updating", or some such. it'll take about 2-5 minutes.

Step four: After it's done open Magisk. Root the file in your downloads folder. Copy the patched file to your computer (preferably in the platform tools folder)

Step five: Fastboot flash the patched boot. Like you normally do.
 
  • Like
Reactions: Sand_23
dilligaf56

dilligaf56

Senior Member
Feb 22, 2011
187
58
SoCal, USA
I'm currently on Magisk 25206 (after rolling back from previous buggy upgrade). I'm now being told that there is a new update (26101). Is this new version OK? I don't want to have to downgrade again. Thanks!
 
You must log in or register to reply here.

Similar threads

roirraW "edor" ehT
How To Guide September 18, 2023 TQ3A.230901.001 Global | .C1 T-Mobile | .C2 Verizon - Root Pixel 6 Pro [Raven]
Replies
2K
Views
324K
Strephon Alkhalikoi
Strephon Alkhalikoi
Freak07
Development [Kernel][24.09.2023][Android 13.0.0]Kirisakura 1.1.5_Raviantah for Pixel 6/Pro aka "RAVIOLE"
Replies
3K
Views
440K
F
falsehhhhh
Pekempy
How To Guide Working SafetyNet with Pixel 6 Pro Android 12
Replies
636
Views
95K
NakamotoShigetoki
NakamotoShigetoki
Typhus_
Themes / Apps / Mods [MOD][MAGISK][ANDROID 12] Addon Features for Pixel Devices - Pixel 6 Pro Thread
Replies
1K
Views
145K
Thebear j koss
Thebear j koss
Az Biker
How To Guide [Pixel 6 Pro] Easy STEP BY STEP Unlock-Root-Update
Replies
373
Views
74K
Nergal di Cuthah
Nergal di Cuthah

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 1
    V0latyle
    V0latyle
    Nicolas.... said:
    I try, but Magisk only propose the installation by patching a file. Do you know if I can use an old magisk_patch.img created from another release factory image?

    View attachment 6012115
    View attachment 6012117
    Click to expand...
    Click to collapse
    Again, you need to live boot the previous patched image:
    fastboot boot magisk_patched-*****.img

    This commands the phone to immediately boot the image instead of flashing it. This should be sufficient to give you temproary root so you can perform Direct Install.

    Did you happen to have the Magisk app hidden/disguised before you tried all this?
    View
  • 101
    V0latyle
    V0latyle
    ⚠️⚠️⚠️ 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:
    For best results, use the latest stable Magisk release.
    Discussion thread for migration to 24.0+.
    Note: Magisk prior to Canary 23016 does not incorporate the necessary fixes for Android 12+.

    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 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 force basic attestation instead of hardware, 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_20230323-072859-3-png.5870161
    • "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 @badabing2003 , @pndwal , @Displax , @Az Biker , @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
    G
    Ghisy
    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"
    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