[GUIDE] Pixel 5 "redfin": Unlock Bootloader, Update, Root, Pass SafetyNet

Search This thread
By:
Advanced…
X

xsR1zU

New member
Jun 14, 2010
4
4
V0latyle said:
Interesting that you were able to successfully update and root using the OTA. Others are experiencing boot loops.
Click to expand...
Click to collapse
I suspect my success was because I didn't bypass using the reboot button that is presented when the system update is ready to reboot, and I didn't flash the patched boot image until after rebooting into the newly updated version for the first time.

The process I used was similar to that of unrooting, taking the OTA, and then rooting again, except that I don't have to download a factory image in order to regain root -- I just use the boot image that is installed as part of the update.
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
10,299
5
18,205
The Heartland of America
Google Pixel 5
Google Pixel 5a
xsR1zU said:
I suspect my success was because I didn't bypass using the reboot button that is presented when the system update is ready to reboot, and I didn't flash the patched boot image until after rebooting into the newly updated version for the first time.

The process I used was similar to that of unrooting, taking the OTA, and then rooting again, except that I don't have to download a factory image in order to regain root -- I just use the boot image that is installed as part of the update.
Click to expand...
Click to collapse
Oh okay. So you basically did a normal OTA without using Magisk to patch the "new" slot until AFTER the update was complete. Makes sense.
 
Y

yickhcr

Member
Jun 15, 2018
19
9
Markham
i can confirm dirty flashing from A12 to A13 works without data loss, kept root; took the same steps as i would've with any other monthly update.

One thing i did notice is that google wallet now says "phone doesn't meet security requirements" when i check "tap to pay setup", HOWEVER previously stored credit cards seems to load fine and still available? i havent had a chance to test making an actual payment yet so cant say if tap to pay is really fked or not
Screenshot_20220817-100225.pngScreenshot_20220817-100213.pngScreenshot_20220817-100418.png
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
10,299
5
18,205
The Heartland of America
Google Pixel 5
Google Pixel 5a
yickhcr said:
i can confirm dirty flashing from A12 to A13 works without data loss, kept root; took the same steps as i would've with any other monthly update.

One thing i did notice is that google wallet now says "phone doesn't meet security requirements" when i check "tap to pay setup", HOWEVER previously stored credit cards seems to load fine and still available? i havent had a chance to test making an actual payment yet so cant say if tap to pay is really fked or not
View attachment 5688329View attachment 5688327View attachment 5688331
Click to expand...
Click to collapse
Are you using the @Displax modded Universal SafetyNet Fix module?
 
Y

yickhcr

Member
Jun 15, 2018
19
9
Markham
V0latyle said:
I don't use Wallet personally but GPay is working fine.

Installed Wallet and it seems fine too.

View attachment 5688383
Click to expand...
Click to collapse
didnt google wallet replaced google pay?
anyway, i dont know why it says it doesnt meet the requirements but i can add a new payment card
i *suspect* if i clear storage&cache for wallet/play service/play store it will work... but i dont want to re add all the cards if i dont have to... will try making an actual payment and see if it works
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
10,299
5
18,205
The Heartland of America
Google Pixel 5
Google Pixel 5a
yickhcr said:
didnt google wallet replaced google pay?
Click to expand...
Click to collapse
No...at least not yet

There's actually 3 apps:
  • Embedded GPay - system app in Pixel devices and some others, cannot be replaced by Wallet
  • Play Store GPay - standalone app, which as I understand it is going to be updated to
  • Play Store Wallet - standalone app, which as I understand it is going to replace GPay
yickhcr said:
anyway, i dont know why it says it doesnt meet the requirements but i can add a new payment card
i *suspect* if i clear storage&cache for wallet/play service/play store it will work... but i dont want to re add all the cards if i dont have to... will try making an actual payment and see if it works
Click to expand...
Click to collapse
Your cards are saved to your Google account (if synced) so even if you clear storage for the app it should re-sync everything.

Clearing cache doesn't remove any configuration from the app.
 
You must log in or register to reply here.

Similar threads

H
[Guide] [December 6, 2023] Root Pixel 5 Unlock Bootloader + Pass SafetyNet + Both Slots Bootable + More
Replies
941
Views
182K
HippoMan
HippoMan
R
[Tutorial] Unlock Bootloader, get root and valid Safetynet
Replies
307
Views
63K
supaneko
supaneko
M
[Guide] Flash Magisk on Android 12
Replies
370
Views
88K
K
kartikeya98
G
[Guide] Enable automatic call recording in stock dialer app (root needed)
Replies
123
Views
44K
TanzimXDA
TanzimXDA
S
[Video][Tutorial] How to enable 5G for Unlisted Countries on Pixel 4a(5G) and Pixel 5 using QPST.
Replies
109
Views
34K
S
swangjang

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 17
    V0latyle
    V0latyle
    Official updates for this device ended February 2024.

    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.

    Before asking any questions, please read this post.
    For help passing Play Integrity verdicts, see this thread.

    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
    6
    V0latyle
    V0latyle
    Magisk Canary was updated to 23016 last night. This includes a fix for the vbmeta header issue, meaning that disabling verity/verification should no longer be required, and we should be able to root as we did before. This needs testing, make sure you back up your data and photos before you try this!

    Q: "If verity/verification are disabled, do I need to enable them now?"
    A: No. The only thing you have to do is update to Magisk 23016.
    Q: "Will enabling verity/verification wipe my data?"
    A: No.

    I will be updating the OP to reflect this.
    View
    4
    V0latyle
    V0latyle
    For those who are wondering, this is how I updated my Pixel 5 (and my wife's 5a):
    1. Download and extract the factory image
    2. Extract boot.img from the factory update image
    3. Copied boot.img to device, patched in Magisk, copied patched boot image back to update folder
    4. Reboot device to bootloader
    5. Apply update:
      Code: 
      fastboot update device-image-buildnumber.zip
    6. Let device boot and finish update; reboot to bootloader
    7. Boot patched image:
      Code: 
      fastboot boot magisk_patched-23016_xxxxx.img
    8. Open Magisk, tap Install, Direct Install, then reboot.
    9. Done.
    You can potentially save a couple steps by using --skip-reboot when applying the update, then simply rebooting to bootloader and flashing the patched boot image.

    Note: I manually patched the boot image because I didn't have a 23016 boot image handy.
    View
    4
    X
    Xx-Ness-xX
    V0latyle said:
    For those who are wondering, this is how I updated my Pixel 5 (and my wife's 5a):
    1. Download and extract the factory image
    2. Extract boot.img from the factory update image
    3. Copied boot.img to device, patched in Magisk, copied patched boot image back to update folder
    4. Reboot device to bootloader
    5. Apply update:
      Code: 
      fastboot update device-image-buildnumber.zip
    6. Let device boot and finish update; reboot to bootloader
    7. Boot patched image:
      Code: 
      fastboot boot magisk_patched-23016_xxxxx.img
    8. Open Magisk, tap Install, Direct Install, then reboot.
    9. Done.
    You can potentially save a couple steps by using --skip-reboot when applying the update, then simply rebooting to bootloader and flashing the patched boot image.

    Note: I manually patched the boot image because I didn't have a 23016 boot image handy.
    Click to expand...
    Click to collapse
    Confirmed working

    Just applied January update like how I have always been doing on Android 11. This wouldn't be possible without Magisk version 23016
    View
    4
    Didgeridoohan
    Didgeridoohan
    @TKruzze @V0latyle If you're using USNF it doesn't matter if you add the necessary gms components to the Deny listh. The module will always remove them since keeping them on the list will actually keep USNF from doing it's thing.

    For simple SafetyNet pass Universal SafetyNet Fix is all you need (and possibly MagiskHide Props Config if you need to spoof a device fingerprint).
    View

New posts