[Guide] Root Pixel 5 with Magisk Android 12.1

Search This thread

soCram

Senior Member
Nov 25, 2007
103
19
I found a solution for my issue.

For the others out there suffering the same issue with a non-wiped phone:

I obviously did have some modules activated which still caused the phone to bootloop even with patched boot.img and Magisk 23016. This is problematic because even flashing the current patched boot.img does not help here (even if you uninstall the magisk manager first). Magisk is still loading the modules which are causing a bootloop here.

You have to do the following in this case: flash the patched boot.img and start in safe mode. The, run adb shell and enter "magisk --remove-modules". This will remove the modules and reboot your phone. The phone will then boot flawlessly.

Edit: Just saw your post @Homeboy76: Thanks.

Maybe it makes sense to give this hint on the first page to people which updated to Android 12 some time ago and didn't get root after the update and are now using the opporunity to root with the new Magisk version?
 

elong7681

Senior Member
May 23, 2015
499
168
40
US
Moto X4
Google Pixel 2 XL
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.
You said January 2022? But you meant December 2021 correct?
 

elong7681

Senior Member
May 23, 2015
499
168
40
US
Moto X4
Google Pixel 2 XL
I found a solution for my issue.

For the others out there suffering the same issue with a non-wiped phone:

I obviously did have some modules activated which still caused the phone to bootloop even with patched boot.img and Magisk 23016. This is problematic because even flashing the current patched boot.img does not help here (even if you uninstall the magisk manager first). Magisk is still loading the modules which are causing a bootloop here.

You have to do the following in this case: flash the patched boot.img and start in safe mode. The, run adb shell and enter "magisk --remove-modules". This will remove the modules and reboot your phone. The phone will then boot flawlessly.

Edit: Just saw your post @Homeboy76: Thanks.

Maybe it makes sense to give this hint on the first page to people which updated to Android 12 some time ago and didn't get root after the update and are now using the opporunity to root with the new Magisk version?
You should be able to remove all the Magisk modules through the app without issue you just have to reboot your phone once you remove the modules and then un-hide Magisk and reboot and then remove Magisk and reboot and do it all from within the Magisk app.
 
  • Like
Reactions: Homeboy76

soCram

Senior Member
Nov 25, 2007
103
19
You should be able to remove all the Magisk modules through the app without issue you just have to reboot your phone once you remove the modules and then un-hide Magisk and reboot and then remove Magisk and reboot and do it all from within the Magisk app.
I tried that but it didn't show me any modules there.
 
After typing in the command "fastboot flash boot --slot all boot.img" it's stuck on <waiting for lot>
The "waiting for lot" error occurred because you typed a single hyphen (-) in the slot all command instead of a dash/double hyphen (--) before the slot all. Thus the command should be written "fastboot flash boot –slot all boot.img" and not "fastboot flash boot -slot all boot.img" I could not find this error addressed elsewhere on XDA.
 
  • Like
Reactions: Homeboy76

a4abbas

Senior Member
Jan 29, 2013
69
2
Between keep data or wipe data which option allows us to retain root when the new update comes?

please advice
 

Homeboy76

Senior Member
Aug 24, 2012
3,160
1,722
Google Pixel XL
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
 
Last edited:

mattstermh

Senior Member
Dec 9, 2015
79
9
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 then flash the magisk_patched...img. It only takes a few seconds to flash the magisk_patched...img).
fastboot flash boot magisk_patched...img
Not sure I am following. If I just want to update when the next android update is available, a re-root is needed?
 
  • Like
Reactions: a4abbas

Homeboy76

Senior Member
Aug 24, 2012
3,160
1,722
Google Pixel XL
Not sure I am following. If I just want to update when the next android update is available, a re-root is needed?
If you just want to update, your device, you have two options:
- Take the OTA
- Do Install/Update Factory Image Keep data or wipe data: To update the factory image.

Both options will remove root.

If you want root, yes you have to root/re-root.
 
Last edited:
  • Like
Reactions: a4abbas

mattstermh

Senior Member
Dec 9, 2015
79
9
If you just want to update, your device, you have two options:
- Take the OTA
- Do Install/Update Factory Image Keep data or wipe data: To update the factory image.
I've read the original post but I'm still confused. If I take the OTA I do not lose root, right? And which is the method I use to download it?
 

Xx-Ness-xX

Senior Member
Nov 15, 2010
133
34
Chicago
HTC One (m7)
i9100
I've read the original post but I'm still confused. If I take the OTA I do not lose root, right? And which is the method I use to download it?
He clearly stated Neither
In other words, you will lose root
Quote for reference:
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
 
  • Like
Reactions: Homeboy76

V0latyle

Forum Moderator
Staff member
He clearly stated Neither
In other words, you will lose root
Quote for reference:
Updating will always "lose" root, because the boot image is overwritten with the (new) unpatched boot image.

Fortunately, it's extremely simple to regain root: just perform the update however you want to do it, then patch the new boot image with Magisk Canary 23016 or later.

For the sake of clarity, we no longer have to worry about losing the ability to root. Magisk 23016 fixed this.
 
  • Like
Reactions: Pixel86

li0rli0r

Member
May 22, 2009
47
2
Google Pixel 5
Hello, i have a small issue after i rooted the phone (January update) , but google play security is still on October security update, when i try to update it to December it updates and restart the phone, but after he up again, after a few seconds he does again reset to phone and the security update of google play is back to October...

Does anyone know how to fix it?

thanks
 

Homeboy76

Senior Member
Aug 24, 2012
3,160
1,722
Google Pixel XL
Hello, i have a small issue after i rooted the phone (January update) , but google play security is still on October security update, when i try to update it to December it updates and restart the phone, but after he up again, after a few seconds he does again reset to phone and the security update of google play is back to October...

Does anyone know how to fix it?

thanks
Try Settings Apps => See all => Google play store => Storage & cache => Clear cache and Clear storage => Reboot.
 
  • Like
Reactions: stanis64

mattstermh

Senior Member
Dec 9, 2015
79
9
He clearly stated Neither
In other words, you will lose root
Quote for reference:
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
 

Homeboy76

Senior Member
Aug 24, 2012
3,160
1,722
Google Pixel XL
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.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    That's not necessary. Why? There is a link to lineageOS (OP Part I - Information, 3. Update(s). :)
    Because I think we have our wires crossed.

    I saw lineage 19 upgrade, so I decided to upgrade and noticed I lost root. I begun my search on how to root, starting with the Lineage thread and didn't find detailed instructions (in fact there wasn't really, but I did search on the lineage thread) like this thread. I went ahead and followed the instructions even look at other android 12 root thread but this one was clearer.

    I simply came across your thread and used it successfully to root.

    I mentioned the custom rom because if someone comes across your thread using a non stock android rom, it could possibly avoid them asking questions... when I was just helping by mentioning my rom version.

    Anyway thank you again. It worked for me.
    1
    Thank you for the guide, can confirm it worked for me on Lineage 18 root, upgraded to Lineage 19 and now rooted.
    Data is intact no wipe required for me. 🎉🥳
    :oops: You sure you posted this on the correct thread? This is not a lineage thread.
    1
    💯 I sure did as I used the guide on this thread to root in general, but for my rom which happens to be a custom rom, Lineage.

    There wasn't any instructions as per say on the lineage thread, so I guess reporting back will help someone if they needed.
    1
    Thank you for your reply!
    No, I was previously with root before the upgrade and then lost it.
    I managed to fix it. It turns out it were the modules that were preventing my phone to start. I removed them with adb and it started.

    I'm not sure if I can upgrade as on my previous attempts, the magisk manager would just not open.
    Did you have Magisk Manager hidden before the upgrade?
    It's advisable that you unhide it before an update.
  • 42
    [Guide] Root Pixel 5 with Magisk Android 12.1
    Android Security Bulletin—May 2022
    Pixel Update Bulletin—May 2022

    Introduction
    This Guide is for Pixel 5 owners that want to Root their phone, and enjoy the benefits of rooting it. The Guide is divided into three parts: Information, Instructions, and Other.

    ~ ~ ~ Part I - INFORMATION ~ ~ ~
    1. 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.
    2. 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: r33.0.1 installed.
      4. Important Notes:
        a. Update Platform Tools, regularly, for optimal performance.​
    3. Update(s)

      1. Factory/OTA Images - 02May
      2. Magisk Alpha - 71e9c044-alpha 06May
      3. Magisk Beta - 24.3 10Mar
      4. Magisk Canary - (756d8356) (24312) 15May
      5. Magisk Stable - 24.3 10Mar
      6. TWRP - Waiting for T.R.W.P. for Android 12
      7. SafetyNet - SafetyNetFix v2.1.3 (Riru) v2.2.1 (Zygisk) 22Dec
      8. SDK Platform-tools - r33.0.1 06Apr
      9. Custom Kernels
        Note: If you are using a Custom Kernel, please update using this method in the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, Install/Update Factory Image keep data or wipe data, • Flash Factory Image Keep Data
      10. Custom ROMs
        a. ProtonAOSP[12]
        c. [Rom][GrapheneOS]Android 12][AOSP][UNOFFICIAL]
    4. NEW

    5. My Other Guides
    6. Credits/Thanks/Recognitions

      1. @creezalird- Flash Android 12 factory image.
      2. Those I may have, inadvertently, forgotten.
    ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~
    1. 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.
    2. Install/Update Factory Image keep data or wipe data

      • Important Note(s):
        1. When doing a Major Upgrade Android 12 (12.0.0) to Android 12.1 (12.1.0), I recommend doing a Clean Install: Do Flash Factory Image Wipe Data (below).
        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. If you phone bootloops
          • force Safe Mode by continually pressing volume down button during boot animation.
          • After the system boots into safe mode you can reboot your device to boot up normally (since all modules will be disabled).
          • Thanks @Typhus_ for the instructions to force Safe Mode.
        5. Backup your data
        6. Download the latest Factory Image: Pixel 5 - redfin to your Computer.
        7. Go to Part II - INSTRUCTIONS => 4. Extract Files from the FactoryImage/Flash boot.img and extract the flash-all.bat file.
      • 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
        • On your phone: Boot the bootloader (Power off the phone => Press the Power and Down buttons until you see Start)
        • Connect your phone to the computer.
        • 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 Part II - INSTRUCTIONS => 5. 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
        • On your phone: Boot the bootloader (Power off the phone => Press the Power and Down buttons until you see Start)
        • Connect your phone to the computer.
        • 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 Part II - INSTRUCTIONS => 5. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
    3. Take the OTA Update and Maintain Root

      • All the credit for this set of instructions goes to @topjohnwu for writing the instructions: Install Magisk to Inactive Slot , use Magisk Beta, Stable 24.3.
      • NOTE: If you had a Custom Kernel installed, after you Open Magisk and Restore Images. Do the following to return your phone to Stock:
        • fastboot flash dtbo dtbo.img
        • fastboot flash vendor_boot vendor_boot.img
        • There may be more .img files you need to flash. Please check the OP of the Custom Kernel thread you install for instruction to remove the Custom Kernel and return your phone to Stock. Additionally, if you installed Mods Please check the OP of the Mod thread you installed for instruction to remove the Mod and return your phone to Stock before you download the OTA.
      • If you phone bootloops
        • force Safe Mode by continually pressing volume down button during boot animation.
        • After the system boots into safe mode you can reboot your device to boot up normally (since all modules will be disabled).
        • Thanks @Typhus_ for the instructions to force Safe Mode.
    4. Extract Files from Factory Image/Flash boot.img

      • Extract Files from Factory Image

        1. Extract flash-all.bat and boot.img file
        2. Download the latest Factory image to your phone.
        3. Extract the Factory Image file (bramble-r2d1a.999999.999-factory-99a9a99a.zip) to a folder. The, stock, flash-all.bat file should be in this folder.
        4. Open the folder you extracted the Factory image to and, extract the Image file (image-bramble-aa9a.999999.999.zip) into the folder. The, stock, boot.img file should be in this 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
    5. Root/Reroot with Magisk and Pass SafetyNet.

      • Android 12

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

        1. Go to Part II - INSTRUCTIONS => 4. Extract Files from the FactoryImage/Flash boot.img and extract the boot.img file.
        2. Install Magisk Canary
          Note: Tap 3 dot menu across from canary => Tap Go to file => Download, app-debug.apk
          or
          Magisk 24.1 Beta/Stable App - Under Downloads
        3. Open Magisk Beta/Canary/Stable App
        4. Set the Update Channel Beta/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/Move the patched boot.img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it:
          • Copy it to a USB drive and transfer it to your computer.
          • Move it to your computer using adb push
        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.
    6. 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!
    7. Install/Update Magisk Modules

      • Download Modules
      • Install Modules

        1. Open Magisk
        2. Tap the Modules icon
        3. Tap Install from storage
        4. Navigate to the folder with the Module you want to install.
        5. Tap the Module to highlite it and tap Select.
        6. After it installs, tap the Disc Icon to save the install log.
        7. Tap Reboot
      • Update Modules

        1. Open Magisk
        2. Tap the Modules icon
        3. You, will see the Modules that have Updates.
        4. Tap the Module you want to update.
        5. Tap install.
        6. After it installs, tap the Disc Icon to save the install log.
        7. Tap Reboot
    8. 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.
    9. 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.
    10. ADB Sideload

    ~ ~ ~ Part III - OTHER ~ ~ ~
    1. 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
    2. Mods
    3. 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.