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

Search This thread

Dragon Kumera

Senior Member
Mar 14, 2019
379
133
So has anyone else had google pay just stop working one day? I havent been able to use it since a month now. Did everything I could think of. Did google change something?

Updated what I did the next post down.
 
Last edited:

Dragon Kumera

Senior Member
Mar 14, 2019
379
133
That provides us with zero information. Please tell us what you've done
Very sorry. I meant to add that in the post but forgot. I will update soon. (if it helps December update for p6p worked fine but I updated to the February one and updated magisk and thats when the problem began).

I have saftey net fix 2.4 installed.
clear storage for google play services and google play store to get that check to pass after updating and re rooting. Google play is certified but it seems play services check is not passing.

I do have developer options enabled and debugging off so my banking app works.
I did the integrity api check and it reports the top and bottom as fails.
meets device integrity = fail
meet basic integrity = pass
meet strong integrity = fail

The other security check app said cts profile fail or something like that. Weird thing is on first boot of the app after a phone reboot it passes but then relaunching the app says it fails.
 
Last edited:

StanWiz

Senior Member
Oct 27, 2014
88
30
Very sorry. I meant to add that in the post but forgot. I will update soon. (if it helps December update for p6p worked fine but I updated to the February one and updated magisk and thats when the problem began).

I have saftey net fix 2.4 installed.
clear storage for google play services and google play store to get that check to pass after updating and re rooting. Google play is certified but it seems play services check is not passing.

I do have developer options enabled and debugging off so my banking app works.
I did the integrity api check and it reports the top and bottom as fails.
meets device integrity = fail
meet basic integrity = pass
meet strong integrity = fail

The other security check app said cts profile fail or something like that. Weird thing is on first boot of the app after a phone reboot it passes but then relaunching the app says it fails.
There is a new saftey netfix( 2.4.0mod _1.2 I believe) - that should fix your problem.
 

dilligaf56

Senior Member
Feb 22, 2011
187
58
SoCal, USA
There is a new saftey netfix( 2.4.0mod _1.2 I believe) - that should fix your problem.
This seems to work for me; I had the same problem after updating to the February firmware. After installing this module, it passes the needed two out of three Play Integrity checks. Still have to see if Google Pay works. Unfortunately Lookout still finds Magisk, even though it's "hidden"...I just ignore the warning, but it didn't find it before last month.

Here is the link to the updated module:
 

darkness4every1

Senior Member
Feb 13, 2013
150
64
Google Pixel 6 Pro
So has anyone else had google pay just stop working one day? I havent been able to use it since a month now. Did everything I could think of. Did google change something?

Updated what I did the next post down.
Mine stopped working as well, can't make any contactless payments, can't add cards on my watch anymore.
I'm on latest Universal SafetyNet Fix 2.4.0 Mod 1.2, tried clearing cache/ data for play services, play store, wallet, wear os. Wallet is hidden in magisk.
Everything was fine before FEB update.
 

Dragon Kumera

Senior Member
Mar 14, 2019
379
133
Mine stopped working as well, can't make any contactless payments, can't add cards on my watch anymore.
I'm on latest Universal SafetyNet Fix 2.4.0 Mod 1.2, tried clearing cache/ data for play services, play store, wallet, wear os. Wallet is hidden in magisk.
Everything was fine before FEB update.
I just updated to the mod v1.2 was released recently and was able to finally setup google pay again. Will test it monday to see if it works. (pm me so we dont clutter chat here). I can help you fix it or attempt to after I test to make sure it does work.
 

V0latyle

Forum Moderator
Staff member
Mine stopped working as well, can't make any contactless payments, can't add cards on my watch anymore.
I'm on latest Universal SafetyNet Fix 2.4.0 Mod 1.2, tried clearing cache/ data for play services, play store, wallet, wear os. Wallet is hidden in magisk.
Everything was fine before FEB update.
Any other mods?

I haven't had to use DenyList on any Google apps.

Stock fingerprint, USNF 2.4.0 Mod 1.2, DenyList only on non-Google apps. No issues on my Pixel 5
 

darkness4every1

Senior Member
Feb 13, 2013
150
64
Google Pixel 6 Pro
Any other mods?

I haven't had to use DenyList on any Google apps.

Stock fingerprint, USNF 2.4.0 Mod 1.2, DenyList only on non-Google apps. No issues on my Pixel 5
A lot of mods. After clearing cache/data I can add cards and stuff for a few minutes but then I get the "Something went wrong, try again later" error.

Before updating to 1.2 I'd get an error when trying to pay contactless, after 1.2 I'm getting no error (or something went wrong) but payment is being declined
 

V0latyle

Forum Moderator
Staff member
A lot of mods. After clearing cache/data I can add cards and stuff for a few minutes but then I get the "Something went wrong, try again later" error.

Before updating to 1.2 I'd get an error when trying to pay contactless, after 1.2 I'm getting no error (or something went wrong) but payment is being declined
What other mods? Have you altered device fingerprint/profile in any way?

Please continue these questions here as this thread is only intended for issues with software updates
 

darkness4every1

Senior Member
Feb 13, 2013
150
64
Google Pixel 6 Pro

Attachments

  • Screenshot_20230224-201240.png
    Screenshot_20230224-201240.png
    302.8 KB · Views: 33
  • Screenshot_20230224-201234.png
    Screenshot_20230224-201234.png
    304.7 KB · Views: 34
  • Screenshot_20230224-201223.png
    Screenshot_20230224-201223.png
    329.7 KB · Views: 33

Dragon Kumera

Senior Member
Mar 14, 2019
379
133
Mine stopped working as well, can't make any contactless payments, can't add cards on my watch anymore.
I'm on latest Universal SafetyNet Fix 2.4.0 Mod 1.2, tried clearing cache/ data for play services, play store, wallet, wear os. Wallet is hidden in magisk.
Everything was fine before FEB update.
Tested google pay Monday and it worked fantastic. I am running stock though no other modules besides the ones required to get it working.
 

triggerhappy_

Member
Jan 16, 2022
34
24
Hey all! Tryna do the Feb update by following the steps "Update and Root Factory Image" but can't!

archive does not contain 'vendor_other.img'
Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)
fastboot: error: Command failed

I've done this tons of times. What's wrong and what should I do?

p.s. platform tools and all drivers are up to date.
 

V0latyle

Forum Moderator
Staff member
Hey all! Tryna do the Feb update by following the steps "Update and Root Factory Image" but can't!

archive does not contain 'vendor_other.img'
Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)
fastboot: error: Command failed

I've done this tons of times. What's wrong and what should I do?

p.s. platform tools and all drivers are up to date.
Are you using the correct factory image for your device? It should have "raven" in the file name.

Also, Platform Tools 34.0.0 is known to have problems. Use 33.0.3
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Ok so i been on Android 13 for ever now i never rooted when on Android 12 i a confused what i all need to exactly do for root. Do i need to download my current firmware and then adload the boot.img to all slots? I guess i have been confused since i got this phone exactly what to do and its holding me back on root.
    Let me give you a little advice, when I rooted my Pixel 6 Pro, it was the first device I had rooted since my Nexus 6p. I came across the PixelFlasher program developed by Badabing2003 and haven't gone back to the old school way of doing things. once you learn how to use it, it's so easy! it literally takes me about 4 minutes to update my device every month when the update releases. The first thing you want to do is read the OP from the beginning and follow the instructions. If for some reason you can't figure something out and can't find what you're looking for, just ask your question in the thread and someone will get back to you pretty quick. if you need to you can always message me and I'll try to help you out.
    1
    I feel like this is a really dumb question but I am reading sort of multiple answers, so am curious what latest "best practice" is -- I have a Pixel 6 Pro, bought unlocked from Google, with a Verizon SIM. (i.e., it wasn't a Verizon model) Should I flash the regular/World image or the specific Verizon image? is it just a difference of tweaks for Verizon's service?) I don't want it to make any changes to the phone that would lock it to Verizon... I usually flash before a Verizon variant pops up but I'm late this month... (I haven't had any issues with the phone either way)

    It sounds like it's generally preferable to use the carrier version but just wanted to make sure that's still the case and I wasn't going to mess anything up.
    I would flash the regular world version as its a GSM Unlocked model from Google (the same one I have). The Verizon SIM will work just fine in it just like any other carrier. If it was the specific Verizon model, I would have said flash the Verizon update as it probably has something that works with their specific device because it has a different chip and also works on the millimeter wave band.
    1
    I feel like this is a really dumb question but I am reading sort of multiple answers, so am curious what latest "best practice" is -- I have a Pixel 6 Pro, bought unlocked from Google, with a Verizon SIM. (i.e., it wasn't a Verizon model) Should I flash the regular/World image or the specific Verizon image? is it just a difference of tweaks for Verizon's service?) I don't want it to make any changes to the phone that would lock it to Verizon... I usually flash before a Verizon variant pops up but I'm late this month... (I haven't had any issues with the phone either way)

    It sounds like it's generally preferable to use the carrier version but just wanted to make sure that's still the case and I wasn't going to mess anything up.
    Because it's verizon and mnvo carriers, i use the vz one on my unlocked google phone on Verizon's network. I imagine a signal tweak but don't know if i see an actual better signal.
    I also use the global before the verizon comes out and it works just as well, so either.
  • 98
    ⚠️⚠️⚠️ 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


    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!
    9
    Magisk Stable is now at version 24.1, so I will no longer be providing any Magisk updates.

    You can use any version of Magisk now - Stable, Beta, or Canary. as long as it is 23016 or newer.

    Once again, if you want to switch versions of Maagisk, it is HIGHLY RECOMMENDED that you "Complete Uninstall" within Magisk before installing the new version. Multiple instances of Magisk can break root.

    If you simply want to update Magisk, the best way to do so is from within the app.


    Once the February update is out, I will perform some testing with installing to inactive slot, and if it works, I will update this guide.

    Given the low activity on this thread, I will probably close it if everything goes well with the next update.

    Thank you all for your testing and contributions.
    8
    My update process is to remove vbmeta.img (in addition to removing the -w flag in the flash-all script) from the factory zip before I flash it in fastboot. Seems to have worked so far, ymmv.
    7
    Now THIS is a useful thread! Thanks 👍

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

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

    "6. Reflash vbmeta to disable boot verification"
    7
    Magisk Canary updated to 23019
    Changes:
    - [Zygisk] Skip loading modules into the Magisk app to prevent conflicts
    - [MagiskBoot] Change `zopfli` to a more reasonable config so it doesn't take forever
    - [General] Several `BusyBox` changes

    Preferred method of update is from within Magisk app.


    If installing for the first time, here is the APK Download