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

Search This thread
By:
Advanced…
A

ankutsa

Member
Oct 27, 2016
24
3
Hello,

On a Pixel 5 I have succesfully run all the steps until the OTA update step (I prefer Android 11 and don't need to update).
Then I enabled Zygisk and deny list for all sub components of "google play".
Also installed the safety-net fix module.

In the YASNAC app my phone passes both safetynet checks.
...but I still cannot see Revolut banking app in the Play store. If I go to the app page from the "not installed" menu it says that the Revolut app is unavailable for my device :(
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
6,640
2
10,798
The Heartland of America
Google Pixel 5
Google Pixel 5a
ankutsa said:
Hello,

On a Pixel 5 I have succesfully run all the steps until the OTA update step (I prefer Android 11 and don't need to update).
Then I enabled Zygisk and deny list for all sub components of "google play".
Also installed the safety-net fix module.

In the YASNAC app my phone passes both safetynet checks.
...but I still cannot see Revolut banking app in the Play store. If I go to the app page from the "not installed" menu it says that the Revolut app is unavailable for my device :(
Click to expand...
Click to collapse
Did you read the SafetyNet/Play Integrity section in the OP?

Refer to this thread, specifically:
V0latyle said:
My device passes SafetyNet but I can't use Google Pay/other apps.
Don't rely on SafetyNet as a good assessment of your device's compatibility and security. It is possible to pass SafetyNet, but fail Play Integrity.
Click to expand...
Click to collapse
If you go to Play Store > Settings > About > Play Protect certification, does it show "certified"?
 
A

ankutsa

Member
Oct 27, 2016
24
3
No, it says that it's not certified :(
But it's weird that I can see/install other banking apps, like Wise, or even Google Wallet.
So there is no way around this? I have to unroot if I want to use Revolut?

ps: I also installed the Integrity api checker app, and fails device & strong integrity.
And run YASNAC again and now it only passes first safetynet check, and I swear it passed both checks before. The only thing I did between these 2 runs was a reboot

ps2: did some more testing, and apparently both "device" and "basic" checks pass after restart, but some time after that, "device" check starts to fail

ps3: not sure if it's related, but after android starts i see a notification with "x google enrollment is running in the background" for like 3 seconds
 
Last edited:
A

ankutsa

Member
Oct 27, 2016
24
3
If I install OTA, can I downgrade to Android 11 later if I don't like it or it is not possible anymore?
 
A

ankutsa

Member
Oct 27, 2016
24
3
An update- I installed this mod https://github.com/Displax/safetynet-fix/releases
instead of the "official" 2.4 and now both safety checks pass all the time in YASNAC, and both device & basic check pass in the other app all the time.

..but g play still shows that the device is not certified, and still can not see Revolut in play store when I search for it.

Anyone managed to get Revolut in play store on rooted Pixel 5 ? Could it be that Revolut requires the 3rd type of check to pass, the one that is hardware-backed?
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
6,640
2
10,798
The Heartland of America
Google Pixel 5
Google Pixel 5a
ankutsa said:
If I install OTA, can I downgrade to Android 11 later if I don't like it or it is not possible anymore?
Click to expand...
Click to collapse
AFAIK there is nothing preventing rollback on the Pixel 5. However I doubt your issue with Play Store certification has anything to do with Android version.
ankutsa said:
An update- I installed this mod https://github.com/Displax/safetynet-fix/releases
instead of the "official" 2.4 and now both safety checks pass all the time in YASNAC, and both device & basic check pass in the other app all the time.

..but g play still shows that the device is not certified, and still can not see Revolut in play store when I search for it.

Anyone managed to get Revolut in play store on rooted Pixel 5 ? Could it be that Revolut requires the 3rd type of check to pass, the one that is hardware-backed?
Click to expand...
Click to collapse
Wipe data for Play Store and restart.

For further support regarding Play Integrity please ask your questions in this thread. Be sure to specify what other mods you're using, if any
 
  • Like
Reactions: ankutsa
A

ankutsa

Member
Oct 27, 2016
24
3
Thanks, that kind of worked, Google play shows as "certified" now.

But Revolut still unavailable. I guess this confirms that Revolut is the only app in the world using the hardware-backed check :)
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
6,640
2
10,798
The Heartland of America
Google Pixel 5
Google Pixel 5a
ankutsa said:
Thanks, that kind of worked, Google play shows as "certified" now.

But Revolut still unavailable. I guess this confirms that Revolut is the only app in the world using the hardware-backed check :)
Click to expand...
Click to collapse
No. Play Store does not require specific integrity labels for apps. I suspect something else is wrong.

When did the app last work? It might be because you're still on Android 11. It's available for me...
Screenshot_20230317-201043~2.png
 
A

ankutsa

Member
Oct 27, 2016
24
3
Today I did a Revolut search again on it again and now it shows up! very weird..
I did not use it on this phone before. I have another Pixel 5, non-rooted, that I use daily and has Revolut installed on it.
The rooted phone I got as a back-up phone after the other one dies. I like Pixel 5 because its the only small phone not made of glass and has enough memory and good feature.
 
D

Durchmesser

Member
Oct 14, 2015
44
2
for the record:
I solved my Problem installing magisk on my Pixel 5.
After Installing Lineageos or any new Update (I still stick on 19.1)
  1. OTA Update Lineageos
  2. I have to reboot to lineageos recovery
  3. Activate adb sideload
  4. download Magisk APK to desktop (If I not already have a copy)
  5. rename it from .APK to .ZIP
  6. Code: 
    adb sideload 'PathTo/Magisk.zip'
  7. reboot phone
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
6,640
2
10,798
The Heartland of America
Google Pixel 5
Google Pixel 5a
Durchmesser said:
for the record:
I solved my Problem installing magisk on my Pixel 5.
After Installing Lineageos or any new Update (I still stick on 19.1)
  1. OTA Update Lineageos
  2. I have to reboot to lineageos recovery
  3. Activate adb sideload
  4. download Magisk APK to desktop (If I not already have a copy)
  5. rename it from .APK to .ZIP
  6. Code: 
    adb sideload 'PathTo/Magisk.zip'
  7. reboot phone
Click to expand...
Click to collapse
This thread has nothing to do with LineageOS.
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
6,640
2
10,798
The Heartland of America
Google Pixel 5
Google Pixel 5a
Durchmesser said:
Sorry, I was not aware that we should not mention this OS in this thread. But I'm not good enough in this subject to be able to say that this behavior to getting root works on all kind of Android OS.
Click to expand...
Click to collapse
It doesn't. You can only flash Magisk in custom recoveries such as TWRP or LOS Recovery. It won't work with the stock recovery, and all of us who are using the stock OS are just patching the boot image.
 
  • Like
Reactions: Durchmesser
You must log in or register to reply here.

Similar threads

H
[Guide] Root Pixel 5 with Magisk + Unlock Bootloader + Pass SafetyNet + More
Replies
827
Views
150K
H
Homeboy76
R
[Tutorial] Unlock Bootloader, get root and valid Safetynet
Replies
305
Views
57K
V0latyle
V0latyle
M
[Guide] Flash Magisk on Android 12
Replies
370
Views
81K
K
kartikeya98
G
[Guide] Enable automatic call recording in stock dialer app (root needed)
Replies
123
Views
37K
TanzimXDA
TanzimXDA
V0latyle
  • Locked
[Closed] Android 12 Update and Root ***Obsolete***
Replies
424
Views
38K
V0latyle
V0latyle

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 16
    V0latyle
    V0latyle
    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
    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