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

Search This thread

V0latyle

Forum Moderator
Staff member
Ok but you are using MagiskHide Props Config to pass Safetynet?
Yes.

This is all I did:
  • Installed USNF (originally 2.1.1, now 2.2.1)
  • Enabled Zygisk
  • Enabled Enforce DenyList
  • Denied all components of these apps (ignore Facebook and Honeywell Home)
Screenshot_20220119-073326.png

I believe MHPC automatically installs when you enable DenyList.
I have not configured anything else. TBH I don't even know how to use the advanced options in MHPC or USNF.
 

elong7681

Senior Member
May 23, 2015
526
177
40
US
Moto X4
Google Pixel 2 XL
Yes.

This is all I did:
  • Installed USNF (originally 2.1.1, now 2.2.1)
  • Enabled Zygisk
  • Enabled Enforce DenyList
  • Denied all components of these apps (ignore Facebook and Honeywell Home)
View attachment 5512409
I believe MHPC automatically installs when you enable DenyList.
I have not configured anything else. TBH I don't even know how to use the advanced options in MHPC or USNF.
I haven't used MHPC in a long time and I also am not familiar with using the advanced features of MHPC but I did not know that USNF had advanced features. Is there a guide on GitHub or some other site for using the advanced features of USNF?
 

V0latyle

Forum Moderator
Staff member
I haven't used MHPC in a long time and I also am not familiar with using the advanced features of MHPC but I did not know that USNF had advanced features. Is there a guide on GitHub or some other site for using the advanced features of USNF?
USNF doesn't have additional instructions on its page beyond installing MHPC to spoof CTS. MHPC on the other hand has a lot of information.

Again, I didn't configure either module - just installed USNF, which I believe also installed MHPC, and blocked the apps in the screenshot. YASNAC reports SafetyNet Pass.
 
  • Like
Reactions: elong7681

Krsmqn

Senior Member
Jan 23, 2012
1,210
334
OnePlus 7 Pro
Google Pixel 5
Has anyone else gone without an automatic update as long as I have? My last update was November... With the new method for root via magisk, I want to simply wait for OTA update to happen, but I check prolly once a week with no results.
Screenshot_20220119-101608.png
 
Last edited by a moderator:

V0latyle

Forum Moderator
Staff member
Has anyone else gone without an automatic update as long as I have? My last update was November... With the new method for root via magisk, I want to simply wait for OTA update to happen, but I check prolly once a week with no results.
Please resize your photos or use a spoiler.

I haven't always had the update notification, but I monitor for new releases anyway.

If you're concerned, you can sideload the OTA or dirty flash the factory image. Instructions to do so are in the OP.
 
  • Like
Reactions: elong7681

AquilaDroid

Senior Member
Oct 11, 2012
755
728
81
Raleigh, NC
OK, over the last few days ago I tried several things to update without wiping my device. I fnally used the Android Flash Tool and flashed the V2 Beta 2 file (w/o wipe). It flashed fine, but then I discovered that I still can't flash the Magisk patched.img successfully. I then went back and bit the bullet to wipe, thinking I'd be safe since I backed everything up to Google 1/ Google Drive. After the flash tool I discovered that I'm not able to restore my data from Google 1 although it looks like it is there. I tried to install Magisk with the direct install option but it went into recovery mode so I'm still without data and Magisk.

I just downloaded the V2 Beta 2 system image (redfin-s2b2.211203.006-factory-588d1292.zip) and am debating whether to flash it or patch the boot.img with Magisk and try that again. (I have been using "fastboot boot" magisk patched image instead of flashing it.)

Also, what is "Syncios" that seems to be constantly trying to install several times on the phone? Is that the missing link between the Android Flash tool and Google 1/drive? When I search for it most of the results are their website.

Sorry to be a pain, but I'm now down to a barely usable phone and struggling more than ever! Thanks for all the help.
 

andybones

Forum Moderator
Staff member
May 18, 2010
14,906
15,231
Google Pixel 5
OK, over the last few days ago I tried several things to update without wiping my device. I fnally used the Android Flash Tool and flashed the V2 Beta 2 file (w/o wipe). It flashed fine, but then I discovered that I still can't flash the Magisk patched.img successfully. I then went back and bit the bullet to wipe, thinking I'd be safe since I backed everything up to Google 1/ Google Drive. After the flash tool I discovered that I'm not able to restore my data from Google 1 although it looks like it is there. I tried to install Magisk with the direct install option but it went into recovery mode so I'm still without data and Magisk.

I just downloaded the V2 Beta 2 system image (redfin-s2b2.211203.006-factory-588d1292.zip) and am debating whether to flash it or patch the boot.img with Magisk and try that again. (I have been using "fastboot boot" magisk patched image instead of flashing it.)

Also, what is "Syncios" that seems to be constantly trying to install several times on the phone? Is that the missing link between the Android Flash tool and Google 1/drive? When I search for it most of the results are their website.

Sorry to be a pain, but I'm now down to a barely usable phone and struggling more than ever! Thanks for all the help.
Google search shows what "syncios" is.
"All-in-one mobile manager helps you backup, transfer and manage iOS & Android phone data, sync files from computer to phone. Fully support Android 11 & iOS 15 device."

You can try it free or buy for $34.95.

Personally, I suggest Swift backup or AppDash for backing up application data.
And SMS Backup & Restore for text messages.
I also suggest making a backup of your Internal storage at least once a month to a PC.
I have lost too much from getting stuck in a bootloop and forced to factory reset, thus I'm a bit more anal about this and try to get a fresh backup at least once/twice a week.
 
  • Like
Reactions: AquilaDroid

AquilaDroid

Senior Member
Oct 11, 2012
755
728
81
Raleigh, NC
Thanks for your reply, @andybones. Yes, I did several backups in the lead up to this, including using Swift Backup, which I can't use now since I can't get root. Still don't know why I'm not able to get to the Google backups to restore everything.

I wish I hadn't been so suspicious of Syncios when it magically appeared on the phone and computer... More attempts tomorrow when my mind is (hopefully) clearer.
 
Last edited:

andybones

Forum Moderator
Staff member
May 18, 2010
14,906
15,231
Google Pixel 5
Thanks for your reply, @andybones. Yes, I did several backups in the lead up to this, including using Swift Backup, which I can't use now since I can't get root. Still don't know why I'm not able to get to the Google backups to restore everything.

I wish I hadn't been so suspicious of Syncios when it magically appeared on the phone and computer... More attempts tomorrow when my mind is (hopefully) clearer.
Very welcome. And sorry, totally forgot you need root for Swift. I believe AppDash can backup most data w/o root, but I can't say for certain.
Have you ever downlaoded Syncios before? Maybe it's re-downloading from a previous backup or something?
I feel like it is more geared towards iOS, being called Syncios, and everything makes me believe it is, but ofc does support A11+ as their site says.
I do wish I could be of some help. Best of luck my friend.
 
  • Like
Reactions: AquilaDroid

Krsmqn

Senior Member
Jan 23, 2012
1,210
334
OnePlus 7 Pro
Google Pixel 5
Please resize your photos or use a spoiler.

I haven't always had the update notification, but I monitor for new releases anyway.

If you're concerned, you can sideload the OTA or dirty flash the factory image. Instructions to do so are in the OP.
Screenshot_20220120-073301.pngI hope I did this right, but looks like after clearing storage in Google Play Services, the checking, it worked. Now, do I use the OTA update option now in Magisk?
 

V0latyle

Forum Moderator
Staff member
View attachment 5513647I hope I did this right, but looks like after clearing storage in Google Play Services, the checking, it worked. Now, do I use the OTA update option now in Magisk?
Yep, you spoiler'd properly, thank you.

So when the update prompts you to restart, before you reboot, open Magisk, tap Install, then "Install to inactive slot". THEN reboot. You should boot into the update with root.

If losing root is not acceptable, I'd recommend you wait until you're near a computer just in case something goes wrong.
 
  • Like
Reactions: andybones

V0latyle

Forum Moderator
Staff member
Strange. OTA downloaded and installed, after which I installed Magisk via OTA option, as discussed. But for some reason the update failed ...
Another user suggested restoring the boot image prior to the OTA:
  1. Open Magisk, tap Uninstall, tap Restore Images DO NOT REBOOT
  2. Manually start OTA update: Settings > System > System Update
  3. Allow OTA to download and install; DO NOT REBOOT
  4. When OTA update prompts to restart, open Magisk, tap Install, then tap Install to Inactive Slot
  5. Reboot device
More information here
 
  • Like
Reactions: elong7681

Krsmqn

Senior Member
Jan 23, 2012
1,210
334
OnePlus 7 Pro
Google Pixel 5
Another user suggested restoring the boot image prior to the OTA:
  1. Open Magisk, tap Uninstall, tap Restore Images DO NOT REBOOT
  2. Manually start OTA update: Settings > System > System Update
  3. Allow OTA to download and install; DO NOT REBOOT
  4. When OTA update prompts to restart, open Magisk, tap Install, then tap Install to Inactive Slot
  5. Reboot device
More information here
Thank you. I will give it a try when I get back to wifi.
 
  • Like
Reactions: V0latyle

Krsmqn

Senior Member
Jan 23, 2012
1,210
334
OnePlus 7 Pro
Google Pixel 5
Another user suggested restoring the boot image prior to the OTA:
  1. Open Magisk, tap Uninstall, tap Restore Images DO NOT REBOOT
  2. Manually start OTA update: Settings > System > System Update
  3. Allow OTA to download and install; DO NOT REBOOT
  4. When OTA update prompts to restart, open Magisk, tap Install, then tap Install to Inactive Slot
  5. Reboot device
More information here
Nope. Now I've lost root.
 

Attachments

  • Screenshot_20220120-172558.png
    Screenshot_20220120-172558.png
    88.3 KB · Views: 17

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    I updated to June the way I always have:
    • Patched new boot image in Magisk
    • Reboot to bootloader
    • Flash bootloader and radio
    • Reboot to bootloader
    • Dirty flash factory image (--skip-reboot --slot=all)
    • Flash patched boot image to both slots
    • Reboot; update complete.
    2
    I did what it says exactly, but I always ended up with an old version. But I was able to solve it with your "Update and Root OTA Sideload" method. After flashing the old master-root.img, I did the described steps and now I have the newest firmware with root. Thanks :)
    Don't flash an old boot image after updating. You can temporarily boot it to give Magisk root so that it can patch the new image.
    1
    No, still on the Android 12 beta which I had to install to get out of a mess that you helped me with back in January (see post #128).
    Oh, okay. You should be able to update to the latest release using the method of your choice. I would personally recommend dirty flashing the factory image.
    1
    It says SP2A.220305.012 Is there any way to boot from the other slot?
    I wouldn't try without updating again.

    Follow these instructions exactly:
    1. Follow the prompts to download and install the update, or force update via Settings > System > System Update. Do not reboot.
    2. When prompted to reboot, go into Magisk, then tap Install > Install to Inactive Slot. Magisk will prompt you to reboot; follow the prompts.
    3. Device should reboot into updated slot with root. If you get a failure message during OTA, go into Magisk, tap Uninstall, then Restore Images, before trying to update again.
    1
    I did what it says exactly, but I always ended up with an old version. But I was able to solve it with your "Update and Root OTA Sideload" method. After flashing booting the old master-root.img, I did the described steps and now I have the newest firmware with root. Thanks :)
  • 15
    If you are looking for my guide on a different Pixel, find it here:
    Update 6-20-22: Magisk 25.1 is recommended as this includes fixes for OTA updates.
    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


    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 --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!
    6
    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.
    4
    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.
    4
    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.
    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
    4
    @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).