[GUIDE] Pixel 5 "redfin": Unlock Bootloader, Update, Root, Pass SafetyNet
- Thread starter V0latyle
- Start date
I ending up just updating with factory images.
My SafetyNet check continued to pass and root is working flawlessly with this method.
This process works well, just need to create a new "master boot.img" file with the updated factory files before following the instructions, this part is implied in the instructions.
But doing this I didn't lose my Google Authenticator entries.
Don't uninstall, just restore images - but this shouldn't be necessary because of the below:
No. It apparently already passed block verification. Just open Magisk, disable any modules you have installed, then tap Install > Install to Inactive Slot. Magisk will patch the boot image in the other slot then force a reboot to that slot.
Just follow the instructions and you'll be fine. Make sure you disable modules just to be safe. If for whatever reason you get a boot loop, flashing the factory boot image should get you running while you figure out the problem.
Anyone else having issue with google pay?
I just rooted with latest factory image and the wallet tile is disabled...
All I have done after root is add modules
- MagiskHide Props Config 6.1.2-v137
- Universal SafetyNet Fix 2.2.1
I pass safetynet attestation in YASNAC
And add followings in Magisk DenyList (all sub-component for each) :
- Google Play Protect Service
- Google Play Store
Google Play Service as well, but it doesnt stay after reboot (I saw on page 9 that it's normal behaviour)
Am I missing something or is it related to latest firmware update?
Edit : maybe some more details can be interesting:
- Magisk canary
- in Settings / Google / Settings for Google Apps / Google Pay : my bank card is set and seem to be operational (bank validated it and the NFC logo isnt greyed or crossed)
I just rooted with latest factory image and the wallet tile is disabled...
All I have done after root is add modules
- MagiskHide Props Config 6.1.2-v137
- Universal SafetyNet Fix 2.2.1
I pass safetynet attestation in YASNAC
And add followings in Magisk DenyList (all sub-component for each) :
- Google Play Protect Service
- Google Play Store
Google Play Service as well, but it doesnt stay after reboot (I saw on page 9 that it's normal behaviour)
Am I missing something or is it related to latest firmware update?
Edit : maybe some more details can be interesting:
- Magisk canary
- in Settings / Google / Settings for Google Apps / Google Pay : my bank card is set and seem to be operational (bank validated it and the NFC logo isnt greyed or crossed)
Last edited:
Initial Root essentially describes the process to root your device, coming from unrooted factory firmware. A patched boot image is required for root. An unpatched boot image does not have root.
Make sure you've enabled DenyList on GPay as well. There do seem to be some occasional quirks upon initial root, but generally GPay continues to work as long as everything is set up correctly. I'm able to add/remove cards and use NFC without a problem.
Can you share what's on your DenyList? I don't see any GPay while searching for it in Magisk...
Here's mine (and yes, I have a nice butt thanks to the 30 days challenge app)
And the wallet tile
Here's mine (and yes, I have a nice butt thanks to the 30 days challenge app)
And the wallet tile
Attachments
Last edited:
I don't have any "Google Pay" app in the deny list entries, but I found the sneaky bastard so now my denied apps are
- Google Play Store
- my banks apps
- this com.....wallet app
Doing a clear cache and data of Google Play service and reboot solved the problem
Thanks for your answers and digging!
Attachments
Google Pay has been superseded by GPay. The only important items on the list are Play Store and GPay, and honestly if you already have GPay installed, you don't even need to block Play Store. I simply did because of Play Protect.
I've blocked the other apps for various reasons - all payment and DRM apps (Venmo is also on the list), social media (observed odd behaviour from Facebook with unblocked root), and for some reason the smart home stuff doesn't work properly with root either
Last edited:
I haven't installed the Gpay app since it's natively included in my P5, so I don't have anything similar to yours nor "Google Pay" as suggested by eriks0n.
Only the "systemui.plugin" wallet... I guess it's related to some local specifications...
Anyway, thanks again for prompt answers - and for the OP tutorial
Only the "systemui.plugin" wallet... I guess it's related to some local specifications...
Anyway, thanks again for prompt answers - and for the OP tutorial
Hi,
In what order to do it ? As I said, last time I was afraid to lose everything
Sorry, but it's a bit confusing for me.
Thx !
If you have not unlocked your bootloader, you will be forced to wipe data when you do so. There is no way around this. Fortunately, most of your data on your device backs up to the cloud, so you won't lose everything. Keep in mind that Photos does not back up every time your system takes a snapshot, so make sure you perform a manual backup in the Photos app.Hi,
In what order to do it ? As I said, last time I was afraid to lose everything
Sorry, but it's a bit confusing for me.
Thx !
To root your device, follow the instructions under Initial Root.
Okay, so you're asking how to best update without wiping data?
Any of the methods described in the OP will allow you to do this. I personally recommend dirty flashing the factory image, but you'll need to update bootloader and radio.
Yes no wiping,
just know when exactly should I install my modified boot.img
After the flash or the flash/reboot?
After the flash, before you reboot.
This is the command I use to flash my Pixel 5:
fastboot update --skip-reboot --slot=all <update image file path>The update package reboots the device into fastboot; when the update completes, the device is still in fastboot due to the --skip-reboot option. Then, I flash the patched boot image:
fastboot flash boot --slot=all <patched boot image file path>I followed instructions for rooting my Pixel but absentmindedly forgot to disable automatic updates. Phone was rebooted after the update. On page 11 of this thread, I noticed a user (a4abbas) with a similar situation. Could you confirm that the steps to regain root are:
(I am on stock ROM with just magisk and no modules. )
download factory image for current update I am on.
extract boot.img
patch with magisk in phone
fastboot the updated file
reboot
I apologize if this question has been asked over and over.
thanks for your contributions to the forum.
(I am on stock ROM with just magisk and no modules. )
download factory image for current update I am on.
extract boot.img
patch with magisk in phone
fastboot the updated file
reboot
I apologize if this question has been asked over and over.
thanks for your contributions to the forum.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2
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.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
1
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
I wouldn't try without updating again.
Follow these instructions exactly:
- Follow the prompts to download and install the update, or force update via Settings > System > System Update. Do not reboot.
- When prompted to reboot, go into Magisk, then tap Install > Install to Inactive Slot. Magisk will prompt you to reboot; follow the prompts.
- 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.
-
15If you are looking for my guide on a different Pixel, find it here:
- Pixel 3
- Pixel 3XL
- Pixel 3a
- Pixel 3aXL
- Pixel 4
- Pixel 4XL
- Pixel 4a
- Pixel 4a (5G)
- Pixel 5a
- Pixel 6
- Pixel 6 Pro
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:
- Latest SDK Platform Tools - if Platform Tools is out of date, you WILL run into problems!
- USB Debugging enabled
- Google USB Driver installed
- I recommend using Command Prompt for these instructions; some users have difficulty with PowerShell.
Make sure the Command Prompt is running from your Platform Tools directory!
Android Source - Setting up a device for development
- Follow these instructions to enable Developer Options and USB Debugging.
- Enable OEM Unlocking. If this option is grayed out, unlocking the bootloader is not possible.
- Connect your device to your PC, and open a command window in your Platform Tools folder.
- Ensure ADB sees your device:
If you don't see a device, make sure USB Debugging is enabled, reconnect the USB cable, or try a different USB cable.Code:
adb devices
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. - Reboot to bootloader:
Code:
adb reboot bootloader - Unlock bootloader: THIS WILL WIPE YOUR DEVICE!
Select Continue on the device screen.Code:
fastboot flashing unlock
- Install Magisk on your device.
- Download the factory zip for your build.
- Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img
- Copy boot.img to your device.
- Patch boot.img with Magisk: "Install" > "Select and Patch a File"
- 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.
- Reboot your device to bootloader.
- Flash the patched image:
Code:
fastboot flash boot <drag and drop master root.img here> - Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>
- Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.
- Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
- 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.
- You should now be updated with root.
- Download the OTA.
- Reboot to recovery and sideload the OTA:
Once in recovery:Code:
adb reboot sideload
Code:adb sideload ota.zip - When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
- Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
- Reboot to bootloader.
- Boot the master root image (See note 1):
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.Code:
fastboot boot <drag and drop master root.img here> - Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
- Reboot your device. You should now be updated with root.
Please note that the factory update process expects an updated bootloader and radio. If these are not up to date, the update will fail.
- Download the factory zip and extract the contents.
- Reboot to bootloader.
-
Compare bootloader versions between phone screen and bootloader.img build numberIf bootloader is updated, reboot to bootloader.Code:
fastboot flash bootloader <drag and drop new bootloader.img here> -
Compare baseband versions between phone screen and radio.img build numberIf radio is updated, reboot to bootloader.Code:
fastboot flash radio <drag and drop radio.img here> - Apply update:
When the update completes, the device will be in fastbootd. Reboot to bootloader.Code:fastboot update --skip-reboot image-codename-buildnumber.zip - Boot the master root image (See note 1):
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.Code:
fastboot boot <drag and drop master root.img here> - Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
- Reboot your device. You should now be updated with root.
flash-allscript 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-woption so it doesn't wipe your device.
The scripted commands should look like this:
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.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>
- Follow the instructions on the Android Flash Tool to update your device. Make sure Lock Bootloader and Wipe Device are UNCHECKED.
- When the update completes, the device will be in fastbootd. Reboot to bootloader.
- Boot the master root image (See note 1):
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.Code:
fastboot boot <drag and drop master root.img here> - Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
- 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
- MagiskHide Props Config 6.1.2 (automatically installed) - MHPC GitHub and XDA Thread
- Universal SafetyNet Fix 2.2.1 - USNF GitHub and XDA 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:
- "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!6Magisk 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.4For those who are wondering, this is how I updated my Pixel 5 (and my wife's 5a):
- Download and extract the factory image
- Extract boot.img from the factory update image
- Copied boot.img to device, patched in Magisk, copied patched boot image back to update folder
- Reboot device to bootloader
- Apply update:
Code:
fastboot update device-image-buildnumber.zip - Let device boot and finish update; reboot to bootloader
- Boot patched image:
Code:
fastboot boot magisk_patched-23016_xxxxx.img - Open Magisk, tap Install, Direct Install, then reboot.
- Done.
--skip-rebootwhen 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
Confirmed working
Just applied January update like how I have always been doing on Android 11. This wouldn't be possible without Magisk version 230164@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).
