[Guide] Root Pixel 5 with Magisk + Unlock Bootloader + Pass SafetyNet + More

Search This thread

Prattham

Senior Member
Sep 6, 2013
4,129
1,223
New Delhi
is there any way we can install magisk on Android 13 over a custom from? everytime I flash magisk in twrp it takes me to bootloader
 

Homeboy76

Recognized Contributor
Aug 24, 2012
3,872
2,310
Google Pixel XL
Google Pixel 7 Pro
is there any way we can install magisk on Android 13 over a custom from? everytime I flash magisk in twrp it takes me to bootloader
It depends on the Custom ROM you are trying to install. That is why I wrote this in the OP: OP, ~ ~ ~ Part III - OTHER ~ ~ ~ 1. Custom ROMs, • Need help with a Custom ROM?,
3. If you are trying to install a Addon(s) {Custom Kernel, Magisk, etc.} to the Custom ROM you installed: Search the thread of the Custom ROM you installed or the thread of the Addon you want to add to your Custom ROM for answer(s)/solution(s) to your question(s)/problem(s). If you don't find an answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM or Addon (Custom Kernel, Magisk, etc.) thread.
 

Prattham

Senior Member
Sep 6, 2013
4,129
1,223
New Delhi
It depends on the Custom ROM you are trying to install. That is why I wrote this in the OP: OP, ~ ~ ~ Part III - OTHER ~ ~ ~ 1. Custom ROMs, • Need help with a Custom ROM?,
3. If you are trying to install a Addon(s) {Custom Kernel, Magisk, etc.} to the Custom ROM you installed: Search the thread of the Custom ROM you installed or the thread of the Addon you want to add to your Custom ROM for answer(s)/solution(s) to your question(s)/problem(s). If you don't find an answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM or Addon (Custom Kernel, Magisk, etc.) thread.
Yup done that, did not find much help so i thought I'll expand my area of seeking support
 

HippoMan

Senior Member
May 5, 2009
2,161
942
Hippoland
Unless I've done something incorrectly, I have noticed that the Contacts app under Android 11 on my rooted Pixel 5 phone (rooted via the instructions here) no longer allows any access to device-only contacts. The contacts have to be shared from a Google account. And it also seems to be the case that it is impossible in Settings to turn off network access for the Contacts app.

And if I freeze the Contacts Storage app, then all my SMS and phone apps only see phone numbers and no user names.

Am I missing something? If not, does anyone know of a way to get the Contacts app or some alternative to access device-only contacts in a way that these contacts are indeed available to SMS and phone apps?

Thank you in advance.
 
Last edited:

omartins

Senior Member
Jan 31, 2011
245
71
SDK Platform-tools
Several members of the XDA community have
written posts that SDK Platform-tools r34.0.1 broken. Problem: fastbootd not working

SDK Platform-tools r33.0.3 is attached : OP post #769
Always on the edge 😅 (thank you)

Nevertheless, why not add this same alert to OP or / and attach r33.0.3 to the same post?
 
  • Like
Reactions: Homeboy76

FritzM

Senior Member
Sep 6, 2018
65
13
Verizon Samsung Galaxy Note 4
just 3 or 4 posts before yours, @Homeboy76 clearly stated the r

just 3 or 4 posts before yours, @Homeboy76 clearly stated the reason, it applies to 34.0.0 and 34.0.1
I actually had to go back to page 38 around Feb 21/22 to see 34.0.0 specifically mentioned as having a problem, and it was one person in a bootloop state. I followed the procedure here using 34.0.0 and it is working flawlessly, except when the Pixel 5 was booted in fastbootd, the Windows 10 PC would not recognize the device, but I loaded another driver so it was recognized at https://www.droidwin.com/how-to-install-fastboot-drivers-in-windows-11/

Note: Please use the official Google link provided below by badabing2003, not my link as it is from unofficial source.
 
Last edited:

badabing2003

Recognized Contributor
Sep 17, 2012
2,325
3,320
I actually had to go back to page 38 around Feb 21/22 to see 34.0.0 specifically mentioned as having a problem, and it was one person in a bootloop state. I followed the procedure here using 34.0.0 and it is working flawlessly, except when the Pixel 5 was booted in fastbootd, the Windows 10 PC would not recognize the device, but I loaded another driver so it was recognized at https://www.droidwin.com/how-to-install-fastboot-drivers-in-windows-11/
Are you saying that it worked after you installed a driver from that post?
I personally would not dare trust that.
1- Source is not from the official Google.
2- Unisgned, yet it says Google?
 

FritzM

Senior Member
Sep 6, 2018
65
13
Verizon Samsung Galaxy Note 4
Are you saying that it worked after you installed a driver from that post?
I personally would not dare trust that.
1- Source is not from the official Google.
2- Unisgned, yet it says Google?
Now that I think about it, I don't know why I did not get it from Google! Thanks for raising that mistake. I checked all the SHA256 hashes for the files and they all match with the files from your Google link. Also, the device manager shows the driver as signed by Google and did not prompt during the driver installation saying anything about not signed. Below is a screenshot from the Device Manager on PC.
driver.jpg
.

I updated the driver to the version from your Google link and the content in above screenshot did not change.
I guess I was lucky this time, but I will remember this! Thanks again.
 
  • Like
Reactions: badabing2003

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    SDK Platform-tools Update
    SDK Platform-tools r. 34.0.3, was released May 22, 2023.

    @badabing2003 reported a problem when using it.
    https://forum.xda-developers.com/t/...7-pro-cheetah-safetynet.4502805/post-88571575

    @Lughnasadh, suggested a fix.
    https://forum.xda-developers.com/t/...7-pro-cheetah-safetynet.4502805/post-88571601

    @badabing2003, confirmed the suggested fix works.
    https://forum.xda-developers.com/t/...7-pro-cheetah-safetynet.4502805/post-88571617

    Note: If you use Windows SDK Platform- tools r. 34.0.3. You must set the environment variable.

    I think the same is true if you use Linux SDK Platform-tools r. 34.0.3. You must set the enviroment variable.
    2
    now im attempting to flash a ROM but i get this message

    C:\platform-tools>adb devices
    adb server version (32) doesn't match this client (41); killing...
    * daemon started successfully
    List of devices attached
    -end of output-
    The error is telling your what your problem is.
    You're using old version 32 platform tools, switch to 33.0.3
    2
    @Homeboy76 not sure if you were aware, but Play Protect is not the same as Play Integrity.

    While I do believe that the Play Store's Play Protect ceritication corresponds with MEETS_DEVICE_INTEGRITY, I'm not 100% sure.

    What I AM sure about is Play Store will not tell you your device is failing. You can be failing BASIC_INTEGRITY and DEVICE_INTEGRITY, and Play Store will still show "Device is certified". This does not seem to change until all Play Store data is cleared.

    Why this is a problem: You could be passing pre update, then failing post update, and Play Store will still report your device as certified.

    Solution: Either use Play Store Developer Options to confirm Play Integrity is passing BASIC and DEVICE labels, or use a 3rd party app such as Integrity Checker or TB Checker. I personally prefer to use Integrity Checker because the responses are instantly apparent, no need to read the JSON output from Play Store
    1
    just picked up a pixel 5 and it updated to android 13. OEM unlocking is enabled, USB debugging as well and the toggle for developer options is also on. I did a fresh install of platform-tools and the device is shown when adb devices is typed into the CMD Im able to reboot using fastboot and seems everything is working except when i enter fastboot flashing unlock its only pulls up the help section for adb. Any help on what I may have done wrong would be appreciated, thanks
    Are you using SDK Platform-tools r. 34.0.1?
    If yes, try SDK platform-tools r. 33.0.3
  • 52
    [Guide] Root Pixel 5 with Magisk + Unlock Bootloader + Pass SafetyNet + More
    Android Security Bulletin—May 2023
    Pixel Update Bulletin—May 2023

    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

      • I assume no responsibility for the malfunctioning/bricking of your phone.
      • If you choose to use a Custom Kernels, Custom ROM, etc. You should read the Installation Instructions in their thread before using this guide or attempting to install them. Additionally, 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 them.
        .
    2. Prerequisites

    3. NEW

      • "...make a 100% clean install of ANY Magisk version or fork without PC or TWRP."
      • Android 14 Beta are up.

        1. Builds are only available for the following Pixel devices:
          • Google Pixel 4a5(G)
          • Google Pixel 5 and 5a
          • Google Pixel 6 and 6 Pro
          • Google Pixel 6a
          • Google Pixel 7 and 7 Pro
            * * * 64-bit-only system images * * *
          • Google Pixel 4a (5G)
          • Google Pixel 5
          • Google Pixel 6
          • Google Pixel 6 Pro
        2. Android 14 GSI binaries and release
          • Pixel 4a5(G)
          • Pixel 5 and 5a
          • Pixel 6 and 6 Pro
          • Pixel 6a Pro
          • Pixel 7 and 7 Pro
      • Android 13 QPR3 beta images are up.
        Release notes - for QPR3 beta
        1. Factory Images
          Builds are only available for the following Pixel devices:

          • Google Pixel 4a and 4a (5G)
          • Google Pixel 5 and 5a
          • Google Pixel 6 and 6 Pro
          • Google Pixel 6a
          • Google Pixel 7 and 7 Pro
            * * * 64-bit-only system images * * *
          • Google Pixel 4a (5G)
          • Google Pixel 5
          • Google Pixel 6
          • Google Pixel 6 Pro
        2. OTA Images
          Builds are only available for the following Pixel devices:

          • Google Pixel 4a and 4a (5G)
          • Google Pixel 5 and 5a
          • Google Pixel 6 and 6 Pro
          • Google Pixel 6a
          • Google Pixel 7 and 7 Pro
    4. Update(s)

      1. Factory/OTA Images - 01 May
      2. Android 14 DP
        1. Factory images and OTA images
        2. Android 14 GSI binaries and release
      3. Magisk Alpha - app-release_709f25f6-26101.apk 12 Apr
      4. Magisk Beta - Magisk v26.1.apk 11 Apr
      5. Magisk Canary - app-release_47d2d4e3-26102.apk 24 May
      6. Magisk Cygisk - Click Pages 5 for installation Instructions.
      7. Magisk Delta - app-release
      8. Magisk Stable - Magisk v26.1.apk 11 Apr
      9. TWRP - 370_11-0... 04Oct - Waiting for T.R.W.P. for Android 13
      10. SafetyNet - Displax's SafetyNet Fix, v2.4.0-MOD_1.2 14Feb
      11. SDK Platform-tools - r34.0.3 May 22 2023
      12. Custom Kernels
    5. My Other Guides
    6. Credits/Thanks/Recognitions

      • Those I may have, inadvertently, forgotten.
    ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~
    (The Instructions listed below are not steps, they are individual sets of 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. Use the Android flash tool:
          select Wipe => Force Flash Partitions => Lock Bootloader.
      • Lock Bootloader

        1. If your phone is not 100 percent stock do Return Phone to Stock. If you don't you may 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. Manually Install/Update Factory Image keep data or wipe data

      • Important Note(s):

        1. If you haven't updated your phones Factory image in awhile. It is not necessary to flash all the missed images in succession. Flash the latest Factory image.
        2. If you are uncomfortable manually flashing the factory image. Try PixelFlasher by badabing2003.
        3. If your phone was previously rooted, open Magisk manager and disable all Magisk modules. If you hid the Magisk manager app the default name for the hidden Magisk app is settings.
        4. If you want to Upgrade to a new Android Version or update the Factory Image without wiping your phone: Do Flash Factory Image Keep Data (below).
        5. Always verify you have the latest working version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 5 - redfin.
        6. 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.
        7. 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
          • Remove Modules

            1. Press the Power button until the phone turns off.
            2. Press the Power and Volume Down to boot the bootloader.
            3. Open a Command Prompt in the SDK-Platform-tools folder or the folder that has adb.exe in it, and type adb wait-for-device shell magisk --remove-modules
              then type
            4. fastboot Reboot
        8. Backup your data
        9. Download the latest Factory Image: Pixel 5 - redfin to your Computer.
        10. 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

        • Installing/Upgrading Android Version/
          * E D I T - flash-all.bat file *
          Flash to current/Active Slot.
          * * * S T A R T - E D I T * * *
          @Echo off
          PATH=%PATH%;"%SYSTEMROOT%\System32"
          fastboot flash bootloader bootloader-redfin-a9-9.9-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot flash radio radio-redfin-a9999-99999-999999-b-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot update image-redfin-aa9a.999999.999.zip
          Note:The -w is removed to Keep Data.
          echo Press any key to exit...
          pause >nul
          exit
          * * * * E N D - E D I T * * * *
          Note: It is a good idea to flash the Google factory image to both slots (A & B) when updating or upgrading to new Android version.
          See Flash Other Slot bat file... below.
        • Flash Other Slot bat file - Save as flash-other.bat
          Note: To run this file type flash-other at the Command Prompt.

          ECHO OFF
          PATH=%PATH%;"%SYSTEMROOT%\System32"
          echo This is the slot you are currently on.
          fastboot getvar current-slot
          echo Press any key to continue...
          pause >nul
          fastboot --set-active=other
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          echo This is the slot you switched to.
          fastboot getvar current-slot
          echo Press any key to continue...
          pause >nul
          flash-all
          exit
          * * * * E N D File * * * *
        • 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 Data/Internal Storage.
        • Do not edit the flash-all.bat file,unless you need to disable Verity and Verification to use a custom kernel.
          * E D I T - flash-all.bat file *
          @Echo off
          PATH=%PATH%;"%SYSTEMROOT%\System32"
          fastboot --set-active=other
          fastboot reboot-bootloader
          fastboot flash bootloader bootloader-redfin-a9-9.9-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot flash radio radio-redfin-a9999-99999-999999-b-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot -w update --disable-verity --disable-verification image-redfin-aa9a.999999.999.zip
          echo Press any key to exit...
          pause >nul
          exit
          Notes:
          1. The first time you Disable Verity and Verification it will wipe your Data/Internal Storage.
          2. When doing Subsequent updates and disabling Verity and Verification, the -w flag can be removed to Keep Data.
          3. Once you start Disabling Verity and Verification you should continue doing it. If you skip disabling them one time. The next time you Disable Verity and Verification it will wipe your phone.
          4. To flash both slots (A & B partitions) see Flash Other Slot bat file... above.
          * * * * E N D - Edit * * * *
        • 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

      • This set of instructions was written by @topjohnwu: Install Magisk to Inactive Slot , use Magisk Canary, Beta or Stable.
      • NOTE: After you Open Magisk and Restore Images. If you had a Custom Kernel installed, Please check the OP of the Custom Kernel thread you install for the 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
        • Press the Power button until the phone turns off.
        • Press the Power and Volume Down to boot the bootloader.
        • Open a Command Prompt in the SDK-Platform-tools folder or the folder that has adb.exe in it, and type adb wait-for-device shell magisk --remove-modules
        • fastboot Reboot
    4. Extract Files from Factory Image flash-all.bat boot/init_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/init_boot.img file should be in this folder.
      • Flash boot/init_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 13

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

        1. If your phone was previously rooted, DO NOT repeat DO NOT install another Magisk Manager app. Do this before you patch the boot/init_boot image:
          • Open the Magisk Manager app and disable all Magisk modules. If you hid the Magisk manager app the default name for the hidden Magisk app is settings.
            If you gave it a different name and you've forgotten the name. Use TB checker to find the name of the hidden Magisk Manager. You can also use TB Checker to check if you have more than one Magisk Manager app installed.
        2. Extract the boot/init_boot.img file from the Factory Image.
          • Download the latest Factory image to your phone.
          • Extract the Factory Image file (redfin-a9a9a.999999.999-factory-99a9a99a.zip) to a folder.
          • Open the folder you extracted the Factory image to and extract the Image file (image-redfin-aa9a.999999.999.zip) into the folder. The, stock, boot/init_boot.img file should be in this folder.
        3. Install Magisk Canary - Download app-release.apk
          or
          Magisk Beta/Stable App
        4. Open Magisk Beta/Canary/Stable App
        5. The Update Channel should be set to Beta/Canary/Stable, depending on the version you Installed.
        6. Tap Install (next to Magisk)
        7. Tap, Select and Patch a File
        8. Select the boot.img file you extracted from the latest factory image.
        9. Tap the ✓ (Check Mark)
        10. Tap Let's Go
        11. When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.
        12. Reboot
        13. 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
        14. Boot fastboot mode
        15. Connect the phone to the Computer with USB cord.
        16. Open a Command Prompt in the folder you copied the patched boot.img to.
        17. Type fastboot flash boot "name of patched boot".img without the quote marks at the Prompt and press enter.
        18. Type fastboot reboot at the Prompt and press enter.
        19. Important, 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
          • Remove Modules
            1. Press the Power button until the phone turns off.
            2. Press the Power and Volume Down to boot the bootloader.
            3. Open a Command Prompt in the SDK-Platform-tools folder or the folder that has adb.exe in it, and type adb wait-for-device shell magisk --remove-modules
            4. fastboot Reboot.
        20. Important, if the Magisk Manager app has the Superuser and Module buttons greyed out:
      • Pass Safety Net with SafetyNet Fix

        1. Download File(s)
        2. Install Displax's safetyNet Fix
          • Open Magisk
          • Tap Modules icon
          • Tap Install from storage
          • Navigate to the Displax's SafetyNet Fix file you downloaded.
          • Tap the Displax's SafetyNet Fix 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.
          • Enable Denylist
          • Tap Configure DenyList => Tap 3 Dot Menu => Check ✓ Show system apps => Check ✓ Google Play Store, Google Pay, Google Wallet etc.
          • (Optional) Scroll down to Superuser and enable Enable Biometric Authentication.
        4. Get Device Certified
          • Turn Airplane mode on
          • Open Settings
          • Tap Apps & notifications
          • Tap see all...
          • Tap three dot menu
          • Tap Show system
          • Scroll to Google Play Store
          • Tap Storage and Cache
          • Tap Clear storage
            Note: Repeat the 3 steps above for any app that needs Device Certification i.e., Google Play Services, Google Pay, Google Wallet, 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
          • It may take 24 hours for Device Certification to be updated.
        6. Note: If after completeting Get Device Certified and Check Device Certification you've waited 24 hours your Device is not Certifed or your Device is Certified and certain Google Store apps (Google Pay, NetFliks, etc.) are not working. Use the Play Integrity API Checker app or the TB Checker - Safetynet and Root app to verify you are passing Play Integrity.
    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 from Storage

        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
      • Install Modules from Fox2Code/Fox Magisk Module Manager

        1. Open Fox2Code/Fox Magisk Module Manager
        2. Tap the Modules icon
        3. Locate the Module you want to install
        4. Tap Install
        5. After it installs, tap the Disc Icon to save the install log.
        6. Tap Reboot
      • Update Modules

        1. Open Fox2Code/Fox Magisk Module Manager
        2. You, will see the Modules that have Updates.
        3. Tap the Module you want to update.
        4. Tap install.
        5. After it installs, tap the Disc Icon to save the install log.
        6. 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?
        1. If you are you are trying to install or have installed a Custom ROM, read and follow the Installation Instructions in the OP of the Custom ROM thread.
        2. Search the thread of the Custom ROM you are trying to install or have installed for answer(s)/solution(s) to your question(s)/problem(s): If you don't find a answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM thread you are trying to install or have installed.
        3. If you are trying to install a Addon(s) {Custom Kernel, Magisk, etc.} to the Custom ROM you installed: Search the thread of the Custom ROM you installed or the thread of the Addon you want to add to your Custom ROMfor answer(s)/solution(s) to your question(s)/problem(s). If you don't find an answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM or Addon (Custom Kernel, Magisk, etc.) thread.
      • ROMs
        1. Google Pixel 5 ROMs, Kernels, Recoveries, & Other
        2. Other Custom ROMs
    2. Themes, Apps, and Mods
    3. T.W.R.P. Backup/Restore

      • Waiting for Android 13 T.W.R.P.
    7
    SDK Platform-tools Update
    SDK Platform-tools r. 34.0.3, was released May 22, 2023.

    @badabing2003 reported a problem when using it.
    https://forum.xda-developers.com/t/...7-pro-cheetah-safetynet.4502805/post-88571575

    @Lughnasadh, suggested a fix.
    https://forum.xda-developers.com/t/...7-pro-cheetah-safetynet.4502805/post-88571601

    @badabing2003, confirmed the suggested fix works.
    https://forum.xda-developers.com/t/...7-pro-cheetah-safetynet.4502805/post-88571617

    Note: If you use Windows SDK Platform- tools r. 34.0.3. You must set the environment variable.

    I think the same is true if you use Linux SDK Platform-tools r. 34.0.3. You must set the enviroment variable.
    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.