• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[Guide] Root Pixel 5 Android 12 with Magisk

Search This thread

elong7681

Senior Member
May 23, 2015
373
118
40
US
Moto X4
Google Pixel 2 XL
Link: click this icon View attachment 5437537 when you're typing a message, paste the link into the URL space, and name the link whatever you want using the Text space.

To use code blocks, there are a couple ways to do it:
The simplest is to click the More icon View attachment 5437539 next to Font Size, then click Inline Code (second icon from the right, looks like View attachment 5437543 and type the code between what pops up.

The slightly harder way is to use the code blocks yourself:

[code] type code here [/code]
And in case you're curious here's the difference
This is Inline Code
Code:
This is standard code
Thank you for your help I really appreciate it!
 
  • Like
Reactions: V0latyle

badabing2003

Senior Member
Sep 17, 2012
364
98
Just so I get this right,
I'm currently on Android 11 and rooted, and I want to move to Android 12 and root it.

Is there a path even with a temporary live boot? without having to wipe? is I absolutely need to wipe?

I see this
> You are still on Android 11, you want to upgrade to Android 12 and root it.
> Flash Android 12 factory image with an edited flash-all.bat file that disables verity, disables verification, and wipes the phone: Post in thread [GUIDE] Update to and Re-Root Android 12 **READ THE NOTES**' https://forum.xda-developers.com/t/...droid-12-read-the-notes.4345627/post-85805653

Which only suggests that I need to wipe.

Can I do the following?
Remove root from my current Android
Get the OTA update for Android 12? this will assure that I keep my data
Then do the Temporary live boot a magisk patched image with `--disable-verity --disable-verification` ?

Thanks
 

elong7681

Senior Member
May 23, 2015
373
118
40
US
Moto X4
Google Pixel 2 XL
Just so I get this right,
I'm currently on Android 11 and rooted, and I want to move to Android 12 and root it.

Is there a path even with a temporary live boot? without having to wipe? is I absolutely need to wipe?

I see this
> You are still on Android 11, you want to upgrade to Android 12 and root it.
> Flash Android 12 factory image with an edited flash-all.bat file that disables verity, disables verification, and wipes the phone: Post in thread [GUIDE] Update to and Re-Root Android 12 **READ THE NOTES**' https://forum.xda-developers.com/t/...droid-12-read-the-notes.4345627/post-85805653

Which only suggests that I need to wipe.

Can I do the following?
Remove root from my current Android
Get the OTA update for Android 12? this will assure that I keep my data
Then do the Temporary live boot a magisk patched image with `--disable-verity --disable-verification` ?

Thanks
https://forum.xda-developers.com/t/...ndroid-12-keep-root-and-data-no-wipe.4350835/
 

Homeboy76

Senior Member
Aug 24, 2012
2,909
1,526
Google Pixel XL
Just so I get this right,
I'm currently on Android 11 and rooted, and I want to move to Android 12 and root it.

Is there a path even with a temporary live boot? without having to wipe? is I absolutely need to wipe?

I see this
> You are still on Android 11, you want to upgrade to Android 12 and root it.
> Flash Android 12 factory image with an edited flash-all.bat file that disables verity, disables verification, and wipes the phone: Post in thread [GUIDE] Update to and Re-Root Android 12 **READ THE NOTES**' https://forum.xda-developers.com/t/...droid-12-read-the-notes.4345627/post-85805653

Which only suggests that I need to wipe.

Can I do the following?
Remove root from my current Android
Get the OTA update for Android 12? this will assure that I keep my data
Then do the Temporary live boot a magisk patched image with `--disable-verity --disable-verification` ?

Thanks
Yes, you can do the "do the following"

Temporaily live boot a magisk_ patched.img: Post in thread '[GUIDE] Update to and Re-Root Android 12 **READ THE NOTES**' https://forum.xda-developers.com/t/...droid-12-read-the-notes.4345627/post-85811561
 

badabing2003

Senior Member
Sep 17, 2012
364
98
I'm not sure what you're trying to tell me, you just provided a link.
Are you trying to warn me not to update to 12 with OTA?
Or are you telling me how I would get to 12 rooted without wiping?

If it is the former, then Roger Roger, and thank you.
I read this part, though no explanation as to why that is bad.
> DO NOT take the OTA directly from your phone's System Upgrade settings item.

If it is the latter, then I fail to see how that would work for me.
I see this part
> This assumes you already wiped your phone once going from 11 to the 12 beta!

BB
 

badabing2003

Senior Member
Sep 17, 2012
364
98
Yes, you can do the "do the following"

Temporaily live boot a magisk_ patched.img: Post in thread '[GUIDE] Update to and Re-Root Android 12 **READ THE NOTES**' https://forum.xda-developers.com/t/...droid-12-read-the-notes.4345627/post-85811561
Thanks

So It doesn't matter how I get to 12? either flashing the 12 factory image or taking the OTA? (Is there a preferred way?)
Then it is same old same old `fastboot boot patched_boot.img` except that it would be a temporary root?
By temporary, does it mean it does not survive a reboot?
If I reboot, it would just be unrooted 12 or it would not boot anymore?

Sorry if I'm asking too many questions, just trying to be safe and not do the wrong things, wiping is really not an option for me at this stage.

Thanks
BB
 

Homeboy76

Senior Member
Aug 24, 2012
2,909
1,526
Google Pixel XL
Thanks

So It doesn't matter how I get to 12? either flashing the 12 factory image or taking the OTA? (Is there a preferred way?)
Then it is same old same old `fastboot boot patched_boot.img` except that it would be a temporary root?
By temporary, does it mean it does not survive a reboot?
If I reboot, it would just be unrooted 12 or it would not boot anymore?

Sorry if I'm asking too many questions, just trying to be safe and not do the wrong things, wiping is really not an option for me at this stage.

Thanks
BB

...preferred way?
In my opinion this is the preferred way to get Android 12 and root:
- Flash the factory image with a modified flash-all.bat file.
* Change this line:
fastboot -w update image-bramble-sp1a.210812.015.zip
* To this:
fastboot --disable-verity --disable-verification -w update image-bramble-sp1a.210812.015.zip

Yes it is a PITA because it wipes your phone and you will spend some time setting it up again.

It is worth every minute. Why?
- You may have apps that are not compatible with Android 12 and sooner or later they will cause problems.
- You could brick your phone using other methods.

...temporary root?
Means root does not survive a reboot.

So make time to backup all the data you want to keep: pictures, documents, etc.

Then make time to install Android 12 the preferred way. :)

Also, read this Guide. It list all the ways to upgrade to Android 12. Then decide how you want to upgrade. :)
 
Last edited:
  • Like
Reactions: badabing2003

V0latyle

Forum Moderator
Staff member
...preferred way?
In my opinion this is the preferred way to get Android 12 and root:
- Flash the factory image with a modified flash-all.bat file.
* Change this line:
fastboot -w update image-bramble-sp1a.210812.015.zip
* To this:
fastboot --disable-verity --disable-verification -w update image-bramble-sp1a.210812.015.zip

Yes it is a PITA because it wipes your phone and you will spend some time setting it up again.

It is worth every minute. Why?
- You may have apps that are not compatible with Android 12 and sooner or later they will cause problems.
- You could brick your phone using other methods.

...temporary root?
Means root does not survive a reboot.

So make time to backup all the data you want to keep: pictures, documents, etc.

Then make time to install Android 12 the preferred way. :)

Also, read this Guide. It list all the ways to upgrade to Android 12. Then decide how you want to upgrade. :)
I would agree that a data wipe is generally advisable when upgrading to a completely new OS version.

However, for inexperienced users, I would point them to the Android Flash Tool as it is pretty much foolproof. Bricking our phones rarely happens by accident; you have to be pretty deliberately careless, and the only case in which you'd be unable to recover your phone yourself is if you screw up the bootloader.

Speaking of, your method using ADB and/or the batch file does not update bootloader or radio. I would highly recommend that anyone updating from A11 do so.

If you can, in the OP of your guide, please link the Magisk builds you have mentioned.
 

Homeboy76

Senior Member
Aug 24, 2012
2,909
1,526
Google Pixel XL
I would agree that a data wipe is generally advisable when upgrading to a completely new OS version.

However, for inexperienced users, I would point them to the Android Flash Tool as it is pretty much foolproof. Bricking our phones rarely happens by accident; you have to be pretty deliberately careless, and the only case in which you'd be unable to recover your phone yourself is if you screw up the bootloader.

Speaking of, your method using ADB and/or the batch file does not update bootloader or radio. I would highly recommend that anyone updating from A11 do so.

If you can, in the OP of your guide, please link the Magisk builds you have mentioned.
I think it does flash the bootloader and radio:
- Flash the factory image with a modified flash-all.bat file.
* Change this line:
fastboot -w update image-bramble-sp1a.210812.015.zip
* To this:
fastboot --disable-verity --disable-verification -w update image-bramble-sp1a.210812.015.zip

I pointed them to your thread so they could decide what method of upgrading they would use. :)
- Also, read this Also, read this Guide. It list all the ways to upgrade to Android 12. Then decide how you want to upgrade.

The Magisk apps links are in the OP, 7. Root/Reroot with Magisk and Pass SafetyNet, Download files: :)
 
Last edited:
  • Like
Reactions: V0latyle

V0latyle

Forum Moderator
Staff member
I think it does flash the bootloader and radio:
- Flash the factory image with a modified flash-all.bat file.
* Change this line:
fastboot -w update image-bramble-sp1a.210812.015.zip
* To this:
fastboot --disable-verity --disable-verification -w update image-bramble-sp1a.210812.015.zip

I pointed them to your thread so they could decide what method of upgrading they would use. :)
- Also, read this Also, read this Guide. It list all the ways to upgrade to Android 12. Then decide how you want to upgrade.

The Magisk apps links are in the OP, 7. Root/Reroot with Magisk and Pass SafetyNet, Download files: :)
Oh yep, you're correct, I was thinking of it as just applying the system image, but the batch file does update bootloader and radio. My mistake.

As for the files, it can be helpful to some people to link them at the beginning of the post where listed so that users can grab everything they need at once. Just my $0.02.

Also, since Magisk 23010 uses Zygisk and DenyList, the process is a bit different; it does not require Riru or the Universal SafetyNet Fix:
So Magisk Canary was released yesterday:

Magisk 23010

Someone who is temp rooting want to patch their boot image with this and see what happens?

Also, Magisk Hide is no longer, so here's what you have to do to pass Safetynet (the check is no longer in Magisk so you'll have to use an external app)

In Magisk:
Remove Universal Safetynet Fix and Riru, if you have them installed, Reboot.
Launch Magisk again
Settings > Magisk:
Enable Zygisk
Enable Enforce Denylist
Enable for Google Play Services components: (I just enabled for all subcomponents)
com.google.android.gms
com.google.android.gms.unstable

That should be enough to pass Safetynet. Don't forget to hide other apps such as banking, GPay, DRM (Netflix, Amazon Prime Video, etc)
 
Last edited:
  • Like
Reactions: Homeboy76

Homeboy76

Senior Member
Aug 24, 2012
2,909
1,526
Google Pixel XL
Oh yep, you're correct, I was thinking of it as just applying the system image, but the batch file does update bootloader and radio. My mistake.

As for the files, it can be helpful to some people to link them at the beginning of the post where listed so that users can grab everything they need at once. Just my $0.02.

Also, since Magisk 23010 uses Zygisk and DenyList, the process is a bit different; it does not require Riru or the Universal SafetyNet Fix:

Thanks for the information. :)
 
  • Like
Reactions: V0latyle

V0latyle

Forum Moderator
Staff member
An excellent point that was brought up from a Pixel 6 user:

Data wipe is required for permanent root after upgrading to Android 12. That much we know.

But what about a device that had an original clean install of Android 12?

Who here wiped when upgrading to Android 12, and did not reflash vbmeta until AFTER you set up your device?
Basically, we need to determine if it matters when you flash vbmeta. Here's what needs to be tested:
- Factory flash Android 12 with a wipe; do NOT disable verity and verification
- Set up and use your device
- After everything is set up (download all your apps) attempt to reflash vbmeta with verity and verification disabled, as well as a patched boot image.

If this is successful, this means we shouldn't have to wipe every time we take a monthly update.
 
Last edited:

nico22320

Member
Oct 25, 2020
46
2
Basically, we need to determine if it matters when you flash vbmeta. Here's what needs to be tested:
- Factory flash Android 12 with a wipe; do NOT disable verity and verification
- Set up and use your device
- After everything is set up (download all your apps) attempt to reflash vbmeta with verity and verification disabled, as well as a patched boot image.

If this is successful, this means we shouldn't have to wipe every time we take a monthly update.

Hi, i don't see your post before my update..

I update to Android 12 with wipe and disable verity and vérification.
Reboot, set up device for long Time..
Reboot in fastboot and flash patched boot and perfect Root. No issues

I don't try the New magisk, wait for New beta update.
 
  • Like
Reactions: V0latyle

Homeboy76

Senior Member
Aug 24, 2012
2,909
1,526
Google Pixel XL
Basically, we need to determine if it matters when you flash vbmeta. Here's what needs to be tested:
- Factory flash Android 12 with a wipe; do NOT disable verity and verification
- Set up and use your device
- After everything is set up (download all your apps) attempt to reflash vbmeta with verity and verification disabled, as well as a patched boot image.

If this is successful, this means we shouldn't have to wipe every time we take a monthly update.
Just to clarify, you are saying if someone can flash the android 12 factory image to the Pixel 4a 5(G) or the Pixel 5 phones[/B] using the steps below it will confirm wiping is not necessary every time we take a monthly update.
  1. Use flash-all.bat file, no modifications, to flash Android 12 factory image.
  2. Setup (download all your apps) and use phone
  3. Attempt to reflash vbmeta with verity and verification disabled:
    fastboot --disable-verity --disable-verification flash --slot=all vbmeta vbmeta.img
  4. Flash the magisk_patched.img:
    fastboot flash boot magisk_patched.img
 
Last edited:

V0latyle

Forum Moderator
Staff member
Just to clarify, you are saying if someone can flash the android 12 factory image using the steps below it will confirm wiping is not necessary every time we take a monthly update.
  1. Use flash-all.bat file no modifications to flash Android 12 factory image.
  2. Setup (download all your apps) and use phone
  3. Attempt to reflash vbmeta with verity and verification disabled:
    fastboot --disable-verity --disable-verification flash --slot=all vbmeta vbmeta.img
  4. Flash the magisk_patched.img:
    fastboot flash boot magisk_patched.img
More or less. I was going to try to reflash vbmeta on my Pixel 5 when I got home yesterday but the tired monster got me.

It won't establish for sure whether we will have to wipe for root with the updates, because every update will have a new vbmeta.img.
 
  • Like
Reactions: Homeboy76

Mostafa_I

Member
Oct 30, 2021
7
2
Hello , i followed the instructions but it still say my device is uncertified and also the safenet failed ...even all the Magisk steps were followed ..any idea please?
 

Mostafa_I

Member
Oct 30, 2021
7
2

Attachments

  • Screenshot_20211104-103304.png
    Screenshot_20211104-103304.png
    135.5 KB · Views: 16

V0latyle

Forum Moderator
Staff member
Hello Sorry for late reply ..it is 23.0
Okay. Using 23001, I was able to get SafetyNet to pass with the following:
  • Use Magisk Hide on Google Play Services and Google Play store (all components)
  • Install Riru
  • Install Universal SafetyNet Fix 2.1.1
I also used MagiskHide on Gpay, all banking and DRM apps, and a couple others that depend on security.
 

Top Liked Posts

  • 3
    Between keep data or wipe data which option allows us to retain root when the new update comes?

    please advice
    Neither, please note the last comment of the Keep data and the Wipe data are the same:
    • Go-to Root/Reroot with Magisk and Pass SafetyNet, •Patching the boot.img - to root/reroot.

    Do Keep data to update the factory image. Then flash the magisk_patched...img, if you want to root/re-root your phone. It only takes a few seconds to flash the magisk_patched...img).
    fastboot flash boot magisk_patched...img
    2
    Update!
    Magisk Canary 23017
    2
    Thanks for your reply!

    Yes, I know that the boot command only temporarily boots the patches boot.Img.

    However,both commands (either flash or boot) does result in a boot loop.
    Did you dirty flash Android 12, removed the -w from the flash-all.bat file?

    Did you have Magisk installed with Android 11?

    Were you on the Android 11 Stock Factory image or a Custom ROM before you upgraded to Android 12?

    Did you disable/remove the Magisk Modules and unhide Magisk if you hid it before you upgraded to Android 12?

    Assuming your bootloader is unlocked and you are using the correct version of SDK Platform-tools r. 31.0.3 and Magisk Canary 23016 is, currently, installed?

    Try:
    - Boot Safe mode, when it is fully booted Reboot
    - Delete all magisk_patched.img
    - repatch the boot.img for your Factory image
    - flash the new repatched magisk_patched.img

    If it doesn't work without bootlooping. I Suggest you flash the January 2022 factory image with the -w (Wipe) and start fresh.
    2
    Ok, so I am doing this instead of the OTA update, right?
    Right
    2
    Ok, that's fine. But here is what I am struggling to understand that the guide is not clear on:
    1) When I want to simply update my phone, what is the difference between a factory update/OTA update?
    2) If I do the OTA update, can I download it directly onto the phone and run it on the phone, or does it need to be on the computer?
    3) Once the OTA update is applied, do I then proceed with patching the boot image and editing the flash-all.bat file?

    Ty
    If you do the OTA update, you can download it directly onto the phone and run it on the phone.

    Once the OTA update is applied, you then proceed with patching the boot image if you want to root your phone.

    Notes:
    - The boot.img you need to patch is in the Factory image file.
    - Use Magisk- Canary to patch it.
  • 32
    [Guide] Root Pixel 5 Android 12 with Magisk + Unlock/Lock Bootloader + More
    Android Security Bulletin—January 2022
    Pixel Update Bulletin—January 2022

    Introduction
    This Guide is for Pixel 5 owners that want to Root their phone, and enjoy the benefits of rooting it without installing a Custom ROM. However, for those that just can't live without a Custom ROM, take a look at 'Custom ROMs for Pixel 5'.

    NEW

    1. Understand 5G network...
    2. With the Magisk Canary update to 23016, there is no longer a need to wipe or --disable verity -- disable verification
    3. Magisk Alpha (vvb2060)
    4. The differences between the different variants of Magisk
    5. Magisk Modules for Magisk Alpha/Canary


    Update(s)

    1. Factory/OTA Images - 04Jan
    2. Magisk Stable - Magisk-24.0 26Jan
    3. Magisk Beta - Magisk-23.0 12May
    4. Magisk Canary - Magisk-24001 26Jan
    5. TWRP - Waiting for T.R.W.P. for Android 12
    6. SafetyNet - SafetyNetFix v2.1.3 (Riru) v2.2.1 (Zygisk) 22Dec
    7. SDK Platform-tools - r32.0.0 01Jan
    8. Custom Kernels[/INDENT]

    9. Custom ROMs
      a. ProtonAOSP[12] 01Nov


    Disclaimer

    1. I assume no responsibility for the malfunctioning/bricking of your phone.
    2. The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item.

    Prerequisites

    1. A Pixel 5 phone with an unlocked bootloader.
    2. The latest Android 12 Factory or OTA Image: "redfin" for Pixel 5

      Factory Image

      OTA Image
    3. A Computer with the latest SDK Platform-Tools: r32.0.0 installed.
    4. Important Notes:
      a. Update Platform Tools, regularly, for optimal performance.​


    My Other Guides

    Credits/Thanks/Recognitions

    1. @creezalird- Flash Android 12 factory image.
    2. Those I may have, inadvertently, forgotten.

    ~ ~ ~ INSTRUCTIONS ~ ~ ~

    Unlock Bootloader/Return Phone to Stock/Lock Bootloader

    • Unlock Bootloader

      1. This will erase all user data from the device!
      2. Backup your data
      3. Activate Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer. Tap back > System > Advanced > Developer Options. Enable OEM Unlock and, USB Debugging.
      4. Boot fastboot mode
      5. Connect the phone to the Computer with USB cord.
      6. Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
      7. You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
      8. Allow the process to complete and then type fastboot reboot at the Command Prompt and press enter.
      9. When your phone reboots disconnect your usb cable.
        Notes: After unlocking your bootloader, you'll see a warning: The bootloader is unlocked and... You will see this warning until, you relock the bootloader.
        Do not relock your bootloader until you have returned the device to Stock.
    • Return Phone to Stock

      1. Backup your data/Internal storage
      2. Settings > System > Advanced > Reset Options > Erase all data (factory reset)
      3. Log in
      4. Set up phone
    • Lock Bootloader

      1. Return the phone to Stock before locking the bootloader, failure to do so could brick your phone
      2. This will erase all user data from the device!
      3. Boot fastboot mode
      4. Open a Command Prompt and type this at the Prompt: fastboot flashing lock
      5. You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
      6. Allow the process to complete, then type this at the Command Prompt: fastboot reboot
      7. Enable Developer Options: Settings > About phone > Tap Build number 7 times or until you see 'you are a developer'.
      8. Tap Back > Developer options and toggle OEM Unlock off.

    Install/Update Factory Image keep data or wipe data

    • Important Note(s):
      1. Install Magisk Canary 23016
        Note: Tap 3 dot menu across from canary => Download, app-debug.apk
      2. Always verify you have the latest version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 5 - redfin.
      3. If you get an error: while flashing, try one of these options:
        • Change the USB port to a non charging USB port.
        • Change the USB cord.
        • Change Computers.
      4. Backup your data
      5. Download the latest Factory Image: Pixel 5 - redfin to your Computer.
      6. Extract the factory Image to a folder.
    • Flash Factory Image Keep Data

      • Open the folder you extracted the Factory Image to and Edit the flash-all.bat file with a file editor i.e., DroidEdit app.
        1. Change this line: fastboot -w update image-redfin-aa9a.999999.999.zip
        2. to this: fastboot update image-redfin-sp1a.999999.999.zip
        3. Note: If you do not remove the -w your internal storage will be wiped.
      • After, you have edited the flash-all.bat file. Copy/Move these files to the Platform-tools folder:
        1. bootloader-redfin-....img
        2. flash-all.bat
        3. image-redfin-....zip
        4. radio-redfin-....img
      • Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
      • The phone will reboot when flashing is completed.
      • Go-to Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
    • Flash Factory Image Wipe Data

      • This will wipe your phone's Internal Storage.
      • Open the folder you extracted the Factory Image to and Copy/Move these files to the Platform-tools folder:
        1. bootloader-redfin-....img
        2. flash-all.bat
        3. image-redfin-....zip
        4. radio-redfin-....img
      • Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
      • The phone will reboot when flashing is complete.
      • Setup phone
      • Enable Developer Mode and USB Debugging
        1. Setup => About phone => Tap Build number 7 times or untill you see you are a 'Devloper'.
        2. Setup => System => Developer options => Enable Developer options => enable USB Debugging
      • Go-to Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.

    Root/Reroot with Magisk and Pass SafetyNet.

    • Android 12

      • Upgrade to Android 12: OP, INSTRUCTIONS, Install/Update Factory Image keep data or wipe data, Keep data
    • Patching the boot.img - to root/reroot.

      1. Do #6 - Extract boot.img
      2. Install Magisk Canary
        Note: Tap 3 dot menu across from canary => Tap Go to file => Download, app-debug.apk
        or
        Magisk 24.0 Stable App
      3. Open Magisk Canary/Stable App
      4. Set the Update Channel Canary/Stable.
      5. Tap Install (next to Magisk)
      6. Tap, Select and Patch a File
      7. Select the boot.img file you extracted from the latest factory image.
      8. Tap the ✓ (Check Mark)
      9. Tap Let's Go
      10. When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.
      11. Reboot
      12. Copy the patched boot.img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it.
      13. Boot fastboot mode
      14. Connect the phone to the Computer with USB cord.
      15. Open a Command Prompt in the folder you copied the patched boot.img to.
      16. Type fastboot flash boot "name of patched boot".img without the quote marks at the Prompt and press enter.
      17. Type fastboot reboot at the Prompt and press enter.
      18. Important Notes: If your phone boot loops try one of the following options:
        • Flash the 'stock' boot.img to both slots: fastboot flash boot boot.img --slot all
        • Boot Safe Mode - Press Power Off button ==> Press Power Off until you see boot Safe Mode ==> Press Ok.
    • Pass Safety Net with SafetyNet Fix 2.2.1

      1. Download File(s)
      2. Install SafetyNet Fix 2.2.1
        • Open Magisk
        • Tap Modules icon
        • Tap Install from storage
        • Navigate to the SafetyNetFix file you downloaded
        • Tap the SafetyNetFix file
        • Tap the check mark (✓ at the bottom) to start the installation.
        • After it installs tap the Save icon to save the log
        • Tap Reboot.
      3. Settings for Magisk Canary
        • Open Magisk App
        • Tap the Setup icon.
        • Scroll down to App and set the Update Channel to Canary.
        • Scroll down to Check Updates and enable it.
        • Scroll down to Magisk and enable Zygisk and Enforce DenyList.
        • Tap Configure DenyList => Tap 3 Dot Menu => Check ✓ Show system apps => Check ✓ Google Play Store, Google Pay, etc.
        • Scroll down to Superuser and enable Enable Biometric Authentication.
      4. Get Device Certified Clear Google Play Services, Google Play Store, Google Pay, etc. data
        • Turn Airplane mode on
        • Open Settings
        • Tap Apps & notifications
        • Tap see all...
        • Tap three dot menu
        • Tap Show system
        • Scroll down to Google Play Store
        • Tap Storage and Cache
        • Tap Clear storage
          Note: Repeat the 3 steps above for Google Play Services, Google Pay, etc.
        • reboot
        • Turn Airplane mode off
      5. Check Device Certification
        • Open Google Play Store app
        • Tap Menu - Circle top right
        • Tap Settings
        • Tap About
        • Check Play protect certification.

    Open a Command Prompt/Boot Fastboot Mode/Boot Recovery

    • Open a Command Prompt on Computer
      1. Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type cmd and press enter.
      2. Open a Powershell Command Prompt on Computer: Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type powershell and press enter.
      3. Notes:
        • Enable USB Debugging, on your phone: Settings ==> System ==> Advanced ==> Developer options ==> Scroll down to USB debugging and enable it.
        • When using the Powershell Command Prompt Commands must be preceeded with ./: i.e, ./fastboot devices
        • If you do not want to open a Command Prompt every time you want to use the fastboot command, add the path to the Platform-tools folder to Windows environment variables.
    • Boot fastboot mode (bootloader):
      • Power off phone, press and hold the power and volume down buttons until you see Start.
    • Boot Recovery
      • Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.

    Test fastboot

    • Enable Developer Options - Tap Settings > About phone > Build number 7 times or until you should see 'you are a Developer'.
    • Enable USB Debugging - Tap Settings > System > Advanced > Developer options >
      Enable USB Debugging.
    • Open a Command Prompt on your computer in the Platform-tools folder.
    • Boot fastboot mode on your phone
    • Connect the phone to the Computer.
    • At the prompt type: fastboot devices to verify communication with phone. It should return your phone's serial number.

    ADB Sideload


    Extract/Flash boot.img

    • Extract boot.img

      1. Download the latest Factory image to your phone.
      2. Extract the Factory Image file (redfin-spa1.999999.999-factory-99a9a99a.zip) to a folder.
      3. Open the folder and, extract the Image file (image-redfin-spa1.999999.999.zip) into the folder.
      4. Copy the boot.img file to the computer's Platform-tools folder.
    • Flash boot.img

      1. Flashing the boot.img removes root.
      2. Open the folder you extracted the 'image...zip' file to and copy the boot.img file to your computer's platform-tools folder or to the folder that has fastboot.exe in it.
      3. Boot fastboot mode
      4. Connect the phone to the Computer
      5. Open a Command Prompt and type the following command at the prompt:
        fastboot flash boot --slot all boot.img
      6. Reboot

    Set Magisk App Update Channel/Update Magisk

    • Set Magisk App Update Channel

      • Open Magisk App > Tap Settings icon > Update Channel > Select Stable, Beta, Canary or Custom.
    • Update Magisk

      1. When Magisk App notifies you of an update:
      2. Tap install.
      3. Select, Direct Install (Recommended)
      4. When it finishes installing
      5. Tap, Save Log
      6. Log location: /storage/emulated/0/Download
      7. Tap, Reboot
      8. Done!

    Custom ROMs

    • Need help with a Custom ROM?
      • First, read and follow the Installation Instructions. The installation instructions are in the OP.
      • Second, if you have a problem Installing it, Search the thread of the Custom ROM you are trying to install for a solution to problem: If you don't find a solution post your request for help on the thread.
    • ROMs
      1. Alpha/Beta

        • None
      2. Official
      3. Unofficial

        • None

    Apps/Mods/Scripts/Tethering/Themes

    T.W.R.P. Backup/Restore

    • Waiting for Android 12 T.W.R.P.
    6
    :) I hope you all have a Joyful Holiday season with your family and loves ones. :)

    ~ ~ ~ Stay safe ~ ~ ~
    5
    is there a magisk boot img with modules disabled?. i have a boot loop and need a boot img with it disabled.
    You should have your stock image you can push over. I do not think replacing the boot image with another patched image would disable anything. You can also use adb to remove any modules. Regardless heres my patched boot image and the command to remove modules. Power off, connect phone enter this command, hold power button to boot phone.

    adb wait-for-device shell magisk --remove-modules

    Patched December build boot image
    here
    4
    For people who are having bootloops with patched boot.img
    Please pay attention to this step in the guide
    Section 7
    Under Patching boot.img
    4- Depending on the version of Magisk Manager installed: Set the Update Channel to Beta or Canary.

    Even if you install beta / canary magisk apk, if you don't select the matching channel, you'd get a bootloop, so don't forget that important step.
    3
    Thank you for your help I really appreciate it!
    Absolutely, helping each other is what makes this community work.