You know this happened to me on 12. Phone would randomly go into a bootloop. I don't know what the screen is called but it's the one when you first boot the phone and you get the option to pause the booting process. The only ways I found I could stop it was to plug the charger to it then hold the power button as it was bootlooping and that made it stop. Don't know what causes it.
[GUIDE] Pixel 5 "redfin": Unlock Bootloader, Update, Root, Pass SafetyNet
- Thread starter V0latyle
- Start date
I would suggest reflashing the boot image. Try unpatched first to see if it corrects the issue. If it only happens with a patched image, you are probably using the wrong version of Magisk.
Thank you. I am still rocking magisk 23001, which may well be the culprit. It hasn't happened again after I removed a couple of patches I didn't use, but will definitely try the latest magisk on June's update and see.
You cannot use a lower version of Magisk than 23016 on Android 12. But yes, Stable 24.3 should work fine. Not sure if it works for delta OTAs though. I personally use the latest Canary.
Hello all! Sorry if this question has already been answered but I was wondering if anyone has tried to root lineage 19.1 on pixel 5 (redfin)
Thank you so much,
DroidRommer
Thank you so much,
DroidRommer
Yes!
[ROM][OFFICIAL][redfin] LineageOS 19: OP, Instructions "to install".
Install LineageOS on redfin: Scroll down and read Installing LineageOS from recovery, 6. (Optionally):... These are the instructions for sideloading magisk alpha/beta/canary/stable.zip to root.
Last edited:
This thread is for rooting and updating the stock ROM and kernel, so the methods here may not work on custom ROMs.
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.
Any things I need to be aware of flashing this over January Android 12 Beta 2 build? Thanks for your continued support!
Do you mean Android 13 Beta? 12 has been official release since September of last year. If you're downgrading from 13 I would strongly recommend a clean install.
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.
Hi there,
first of all, thanks for your work! I tried updating OTA with your suggestion, updated magisk first to v. 25101 and then followed your steps. After rebooting it seems that I lost root now. Do you have any advice on how to fix it? I still have the old, flashed boot.img available, if that helps.
Did you reboot through Magisk, or did you select Reboot now after installing the OTA update?
You should be able to temporarily boot an older patched boot image:
fastboot boot <Magisk patched boot image>Then perform Direct Install in Magisk.
Did you patch inactive slot in Magisk before you rebooted?Thanks for ypur quick answer.
I rebooted using Magisk. Rebooting using fastboot worked and I could install root with Magisk and reboot. Zygisk was not installed and the phone now wants to have the OTA update again, hm.
Check your current firmware (swipe notifications all the way down, it'll be right under the quick settings). Current is SQ3A.220605.009.A1. It's possible that the device rebooted to the "old" slot.
Similar threads
Top Liked Posts
-
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
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.
1 -
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).
