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

Search This thread
By:
Advanced…
H

Homeboy76

Recognized Contributor
Aug 24, 2012
4,130
2,510
Google Pixel 7 Pro
Magisk Canary Update
app-release_69529ac5-25211.apk
Notes:
  1. Tap app-release.apk
  2. Tap 3 dots (...) across from 10.9 MB, Tap Download
  3. ...[General] Bump minimum supported Android version to Android 6.0
  4. Google Android 14 Codename is 'Android U' or 'Upside Down Cake'
    1. ...[MagiskPolicy] Update rules to support Android U...
    2. ...This fixes boot image patching issues on Android U preview...
 
H

Homeboy76

Recognized Contributor
Aug 24, 2012
4,130
2,510
Google Pixel 7 Pro
:oops: Not another broken Magisk Canary
Notes:
  1. Magisk Canary 25207, 25208, 25209 (some devices), 25210 and 25211 are broken.
  2. Magisk 25211: Some, are reporting Systemless host is still not working in this thread:
    Magisk General Support / Discussion - starting at Post #55137
  3. Use Magisk Canary 25206
    • Tap the 3 dot menu across from 5b2934603f
    • Tap Go to file
    • Tap app-release.apk
    • Tap the 3 dot menu across from 10.9 MB
    • Tap Download
<<Edit>> Fix for Module loading, System less Host is still broken.

Waiting for Magisk 26001.
 
Last edited:
  • Like
Reactions: HippoMan
HippoMan

HippoMan

Senior Member
May 5, 2009
2,362
1,107
Hippoland
Homeboy76 said:
:oops: Not another broken Magisk Canary
Notes:
  1. Magisk Canary 25207, 25208, 25209 (some devices), 25210 and 25211 are broken.
  2. Magisk 25211: Some, are reporting Systemless host is still not working in this thread:
    Magisk General Support / Discussion - starting at Post #55137
  3. Use Magisk Canary 25206
    • Tap the 3 dot menu across from 5b2934603f
    • Tap Go to file
    • Tap app-release.apk
    • Tap the 3 dot menu across from 10.9 MB
    • Tap Download
Click to expand...
Click to collapse
The canary in the coal mine is doing its job well! :)
 
M

mangojain

Senior Member
Jul 24, 2010
230
26
{davros} said:
received a pixel 5 the other day. so correct me if I'm wrong, grey out OEM unlocking is in no way bypass able. I'm guessing this is a refurbed Verizon phone that is carrier unlocked some how.
Click to expand...
Click to collapse
I'm in the same boat ☹️
Do post an update if you come across any solution or the oem unlocking option becomes available on its own.
 
D

Dawudd

New member
Mar 27, 2012
3
1
Is anyone else having an issue with Magisk not being detected? I've installed Magisk many times before, but I've never had this issue before.

I uninstalled Magisk in order to update my phone. I updated it manually (used a factory image without wiping data), as I never get OTA updates and I hadn't updated my phone in a few months. Then I went through all the standard steps: patch boot.img and flash the new version. But it's not being detected at all. Magisk just says "N/A".

I've tried this with the latest Magisk (26.1), with the most recent Canary build, and with 25.2. I should note that I didn't disable any modules before uninstalling Magisk. I'm on the latest redfin build (TQ2A.230405.003 – not the T-Mobile or Telus build).

Any idea what it could be?
 
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,036
4,691
Dawudd said:
Is anyone else having an issue with Magisk not being detected? I've installed Magisk many times before, but I've never had this issue before.

I uninstalled Magisk in order to update my phone. I updated it manually (used a factory image without wiping data), as I never get OTA updates and I hadn't updated my phone in a few months. Then I went through all the standard steps: patch boot.img and flash the new version. But it's not being detected at all. Magisk just says "N/A".

I've tried this with the latest Magisk (26.1), with the most recent Canary build, and with 25.2. I should note that I didn't disable any modules before uninstalling Magisk. I'm on the latest redfin build (TQ2A.230405.003 – not the T-Mobile or Telus build).

Any idea what it could be?
Click to expand...
Click to collapse
You probably have multiple Magisks (known issue) possibly a hidden one is still lingering around.
Uninstall it and reboot, you should be fine.
 
  • Like
Reactions: Dawudd
H

Homeboy76

Recognized Contributor
Aug 24, 2012
4,130
2,510
Google Pixel 7 Pro
OP Changes
I added additional notes to the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~,
5. Root/Reroot with Magisk and Pass SafetyNet.,
• Patching the boot/init_boot.img - to root/reroot.,
1 & 2.
 
S

sintoo

Senior Member
Nov 26, 2009
189
15
Hello. Quick question. The instructions of Unlock bootloader with the command "fastboot flashing unlock" have a warning: THIS WILL WIPE YOUR DEVICE!
- Coming from Stock May2005 update Pixel5, does "Wipe your device" means ALL apps (including .apk installed apps not on PlayStore) will be gone?
If yes: SO SAD because I would hate to re-install them all, relogin, set various settings (Can't remember them all for each specific app). Note: these .apk apps settings are not backup.


- Also, I'm just wondering if there is a newly discovery that allows for Relocking of the Bootloader (so no warning message) WHILE Magisk (patched boot.img) is still doing its job (allow specific apps root-permission)?
- Thank you so much. :) I want to root to improve battery life (I tried everything, restricting background run, killapps.
- But my battery of Pixel5 is getting only 4-6hr with moderate alternating between Google-Maps, Google Chat, Google Camera, back to Google-Maps, Camera again, and so on so forth).
 
Last edited:
H

Homeboy76

Recognized Contributor
Aug 24, 2012
4,130
2,510
Google Pixel 7 Pro
sintoo said:
- Hello. I'm just wondering if there is a newly discovery that allows for Relocking of the Bootloader (so no warning message) WHILE Magisk (patched boot.img) is still doing its job (allow specific apps root-permission)?
- Thank you so much. :) I want to root to improve battery life (I tried everything, restricting background run, killapps.
- But my battery of Pixel5 is getting only 4-6hr with moderate alternating between Google-Maps, Google Chat, Google Camera, back to Google-Maps, Camera again, and so on so forth).
Click to expand...
Click to collapse
If you try to lock your bootloader with Magisk installed you will brick your phone. Your phone must be 100 % stock prior to locking the bootloader.
(OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~...,
1. UnlockBootloader/Return Phone to Stock/Lock Bootloader,
• Return Phone to Stock)
 
Last edited:
S

sintoo

Senior Member
Nov 26, 2009
189
15
Homeboy76 said:
If you try to lock your bootloader with Magisk installed you will brick your phone. Your phone must be 100 % stock prior to locking the bootloader.
Click to expand...
Click to collapse
I just edited/added my question. Thank you for this response. Could you also advise/comment on my question about "Will Wipe your device".
 
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,036
4,691
sintoo said:
- But my battery of Pixel5 is getting only 4-6hr with moderate alternating between Google-Maps, Google Chat, Google Camera, back to Google-Maps, Camera again, and so on so forth).
Click to expand...
Click to collapse
I'm not sure how much of an battery improvement you are expecting.
Google maps, with GPS on, and Camera are battery drainer apps, and if they are your primary apps, I'd say 6 hours is good.
 
You must log in or register to reply here.

Similar threads

V0latyle
[GUIDE] Pixel 5 "redfin": Unlock Bootloader, Update, Root, Pass SafetyNet
Replies
435
Views
48K
V0latyle
V0latyle
M
[Guide] Flash Magisk on Android 12
Replies
370
Views
84K
K
kartikeya98
R
[Tutorial] Unlock Bootloader, get root and valid Safetynet
Replies
305
Views
60K
V0latyle
V0latyle
S
[Video][Tutorial] How to enable 5G for Unlisted Countries on Pixel 4a(5G) and Pixel 5 using QPST.
Replies
101
Views
28K
S
swangjang
Az Biker
UPDATING Pixel 5 Factory Image & Re-Rooting
Replies
47
Views
17K
{davros}
{davros}

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 1
    H
    Homeboy76
    Magisk Beta/Stable Update
    Magisk Beta/Stable v26.3

    • [General] Fix device information detection script
    • [General] Update BusyBox to 1.36.1
    • [General] Update toolchain that produces broken arm32 executables
    • [App] Fix root service unable to bind on OnePlus devices

    Magisk Canary Update
    Magisk (d4e552d0) (26301).

    • Upstream to latest release
    Diffs to v26.3
    • N/A

    Download Magisk Canary

    1. Tap app-release.apk
    2. Tap the three dot menu across from Code Blame
    3. Tap Download
    View
    1
    H
    Homeboy76
    Google's September 2023 factory and OTA are up!
    View
    1
    thaimaduc
    thaimaduc
    Homeboy76 said:
    Flash OTA zip file, then reboot and check if your phone is rooted. If it is you're done.

    If it is not rooted, see 3. If below.

    I don't think your phone will be rooted.

    Why?

    1. When you flash the September OTA it will install to the other slot ( if you boot fastboot mode and the active slot is a it will install on slot b or vice versa) and unroot it.
      This means Slot b is now the active slot or vice versa.
    2. The inactive slot is slot a it has the rooted August OTA on it.
    3. If your phone is not rooted:
      • adb reboot bootloader
      • fastboot flash boot magisk-patched...img
      • fastboot reboot

    Thank God the phone is not a Google Pixel 6 that has anti-roll back bootloaders.

    Updating Pixel 6, Pixel 6 Pro, and Pixel 6a devices to Android 13 for the first time
    Warning: The Android 13 update for Pixel 6, Pixel 6 Pro, and the Pixel 6a contains a bootloader update that increments the anti-roll back version for the bootloader. This prevents the device from rolling back to previous vulnerable versions of the bootloader. After flashing an Android 13 build on these devices you will not be able to flash and boot older Android 12 builds. For developers who need to develop and test against an Android 12 environment, a special Developer Support Build that contains the bootloader update should be used.

    After taking an Android 13 update and successfully booting the device post update, an Android 12 build resides in the inactive slot (seamless updates for more information on slots) of the device. The inactive slot contains an older bootloader whose anti-rollback version has not been incremented. If the active slot is then flashed with a build that fails to boot, the fallback mechanism of seamless updates kicks in and the device tries to boot from the inactive slot. Since the inactive slot contains the older bootloader, the device enters an unbootable state.

    To avoid hitting this state, if you are flashing a Pixel 6, Pixel 6a, or Pixel 6 Pro device with an Android 13 build for the first time, please flash the bootloader partition to the inactive slot after successfully updating and booting into Android 13 at least once. This can be done by following these steps:

    Option 1 (recommended): After a successful boot into Android 13 for the first time, sideload the full OTA image corresponding to that build and reboot the device to ensure that both slots have a bootable image.

    Option 2 (using factory images): If you flashed your device with the factory image after unlocking the bootloader, after a successful boot into Android 13 for the first time
    1. Extract the contents of the factory ROM .zip file, identify the bootloader image in the extracted files, and follow the sequence of events as listed below to flash the bootloader to both the slots. Substitute the name of the bootloader image with that of your device for the Pixel 6 and Pixel 6a.
    2. Start the device in fastboot mode with one of the following methods:
      • Using the adb tool: With the device powered on, execute:
        adb reboot bootloader​
      • Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device.
    3. Flash the Android 13 bootloader to the inactive slot. The following command is specific to a particular build of a Pixel 6 Pro device. Substitute the name of the bootloader image determined in the first step above, if different, for the image file name argument.
      fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img​
      If the flash was successful this command will print OKAY [ ... ]. Do not proceed unless this command completes successfully.
    4. After flashing the inactive slot bootloader to an Android 13 bootloader, reboot to that slot to ensure that the bootloader will be marked as bootable. Important: Please run the exact sequence of commands as listed below. Don't forget to enter the full line fastboot reboot bootloader when rebooting. Failure to do so may leave your device in an unbootable state.
      fastboot set_active other​
      fastboot reboot bootloader​
      fastboot set_active other​
      fastboot reboot bootloader​
    5. Reboot into the current OS. Either press the power button to boot or use the following fastboot command:
      fastboot reboot​
    Click to expand...
    Click to collapse
    Thank you so much, your answer is helpful and detailed as always. I want to confirm my understanding that:
    1. If my phone is on the latest OTA, and NOT rooted, all I have to do is flash the patched boot img
    2. If my phone is NOT on the latest OTA, and rooted, I have to flash the latest OTA zip, and then flash the new patched boot img of the latest OTA
    View
  • 52
    H
    Homeboy76
    [Guide] Root Pixel 5 with Magisk + Unlock Bootloader + Pass SafetyNet + More
    Android Security Bulletin—September 2023
    Pixel Update Bulletin—September 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

      • Patching the boot.img using the image...zip file extracted from the Google Factory image file and Magisk. (see - OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 2., 3., or 4.)
    4. Update(s)

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

      • @topjohnwu - Magisk.
      • @badabing2003 - Creating Pixel Flasher, discovering how to make both slots bootable, and for his many helpful contributions to this thread.
      • @Lughnasadh - for testing badabing2003 make both slots bootable, and his many helpful contributions to this thread.
      • @Shoey - for discovering and testing patching the boot.img using the image...zip file extracted from the Google Factory image file and Magisk.
      • 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 a while. It is not necessary to flash all the missed images in succession. Flash the latest Factory image.
        2. 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.
        3. Always verify you have the latest working version of SDK Platform-Tools installed on your computer.
        4. If you get an errorwhile flashing, try one of these options:
          • Change the USB port to a non charging USB port.
          • Change the USB cord.
          • Change Computers.
        5. If your phone boot loops try one of the following options:
          • Flash the 'stock' boot.img to both slots to remove root: fastboot flash boot boot.img --slot all
          • Boot Safe Mode while bootingto remove Magisk Modules
            1. When booting, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode.
            2. Then reboot and magisk modules should be disabled. (Thanks Lughnasadh)
          • Boot fastboot mode by turning phone offto remove Magisk Modules
            1. Press the Power button until the phone turns off.
            2. Press the Power and Volume Down to boot fastboot mode.
            3. Open a Command Prompt in the 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
        6. Backup your data
        7. Download the latest Factory Image: Pixel 5 - redfin to your Computer.
        8. Go to Part II - INSTRUCTIONS => 5. Extract files from the Factory Image.
      • Flash Factory Image Keep Data

        • Upgrading Android 13
          * E D I T - flash-all.bat file *
          Flash to current/Active Slot.
          @Echo off
          PATH=%PATH%;"%SYSTEMROOT%\System32"
          fastboot flash bootloader bootloader-redfin redfin-aaaaaa-9.9-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot flash radio radio-redfin redfin-a9999a-999999-999999-a-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
          Note: It is a good idea to flash the Google factory image to both slots (A & B) when Upgrading to a new Android Version.
          See Flash Other Slot bat file... below, to flash to the other/inactive slot.
          * * * * E N D - Edit * * * *
        • Updating Android 13
          Flash to Other/Inactive Slot.
          Note: See Flash Other Slot bat file... below.
          * * * * * E N D * * * * *
        • 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 - Creating 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 => 6. 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.
        • If you need to disable Verity and Verification: See Disabling Verity and Verification below.
          Disabling Verity and Verification
          * 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-aaaaaa-9.9-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot flash radio radio-redfin-a99999-999999-999999-a-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot - w update --disable-verity --disable-verification image-redfin-AA1A.999999.999.A9.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 one time. The next time you Disable Verity and Verification it will wipe your phone.
          4. Some kernels require Disabling verity and verification
          5. To flash the Factory image to both slots (A & B) 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 until you see you are a 'Devloper'.
          2. Setup => System => Developer options => Enable Developer options => enable USB Debugging
        • Go-to Part II - INSTRUCTIONS => 6. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
      • If you are uncomfortable manually flashing the factory image, use PixelFlasher by @badabing2003
    3. (NEW) Manually Install/update the OTA image keep data and root/re-root your phone

      • Important Note(s):
        1. If you haven't updated your phones OTA image in a while. It is not necessary to flash all the missed OTA images in succession. Flash the latest OTA image.
        2. 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.
        3. Always verify you have the latest working version of SDK Platform-Tools installed on your computer.
        4. If you get an errorwhile flashing, try one of these options:
          • Change the USB port to a non charging USB port.
          • Change the USB cord.
          • Change Computers.
        5. If your phone boot loops try one of the following options:
          • Flash the 'stock' boot.img to both slots to remove root: fastboot flash boot boot.img --slot all
          • Boot Safe Mode while bootingto remove Magisk Modules
            1. When booting, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode.
            2. Then reboot and magisk modules should be disabled. (Thanks Lughnasadh)
          • Boot fastboot mode by turning phone offto remove Magisk Modules
            1. Press the Power button until the phone turns off.
            2. Press the Power and Volume Down to boot fastboot mode.
            3. Open a Command Prompt in the 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
        6. Backup your data
        7. Download the latest OTA Image: Pixel 6 - redfin to your Computer.
      • Patch the boot.img

        • Open Magisk (next to Magisk)
        • Tap Install
        • Tap Select and patch a file
        • Navigate to the Google OTA.zip file
        • Tap it then tap the check mark (✓)
        • Tap Lets go
        • When you see done the boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.
        • Tap the disc icon (upper right corner) to save the log file.
        • Reboot
        • Copy/Move the magisk_patched_xxxxxx.img file to your computer's Platform-tools folder, the folder that has fastboot.exe in it:
          1. Copy it to a USB drive and transfer it to your computer.
          2. Move it to your computer using adb push
      • Sideload the Google OTA image file and Root it

        1. With the device powered on, booted, USB debugging enabled, and the phone connected to the computer. Type adb reboot sideload
        2. Type:
          adb sideload redfin-ota-aa9a.999999.999-aaaa9999.zip at the command prompt and press Enter.
        3. When sideloading finishes, type adb reboot bootloader at the command prompt and press Enter.
      • Root this slot - Flash the Magisk_patched....img

        1. Type: fastboot flash boot magisk_patched-99999_aA99a.img at the command prompt and press Enter.
        2. When it finishes flashing, type fastboot reboot at the command prompt and press Enter.
        3. Disconnect the phone from the computer.
        4. Note: This slot is bootable and rooted.
    4. (NEW) Make Both Slots Bootable: Manually, Flash the OTA Image to Both Slots - One bootable and rooted, the other slot bootable without root.

      • Before you start

        1. On the Phone
          • Backup your data
          • Make sure that there is no pending OTA update, by going to Settings > About phone > System updates, which should say Your system is up to date.
          • Download the latest OTA image for your device.
          • Verify the checksum of the OTA image. The last portion of the filename is the first 8 digits of its SHA-256 checksum; the full SHA-256 checksum is shown next to the download link.
          • Patch the boot.img:
            1. Note: Before patching the boot.img disable all Magisk modules.
            2. Open the Magisk (Alpha/Beta/Canary/Delta/Stable) App and set the Update Channel to the version of Magisk app you installed.
            3. Open Magisk (next to Magisk)
            4. Tap Install
            5. Tap Select and patch a file
            6. Navigate to the Google OTA.zip file
            7. Tap it then tap the check mark (✓)
            8. Tap Lets go
            9. When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img), and is stored in the download folder.
            10. Tap the disc icon (upper right corner) to save the log.
            11. Tap Reboot
            12. Copy/Move the magisk_patched....img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it.
            13. Connect the phone to the computer.
        2. On your Computer
          • Enable Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer.
          • Enable USB Debugging: Tap Settings > System > Advanced > Developer Options. Enable USB Debugging.
          • Open a Command Prompt in the Platform-tools folder.
      • (Optional): Verify your computer sees your device.

        1. With the device powered on, booted, USB debugging enabled, and the phone connected to the computer.
          Note: If you see the Allow USB Debugging prompt when you connect the phone to the computer, Tap Allow.
        2. Type adb devices at the command prompt and press Enter. You should see your device's serial number.
      • Sideload the Google OTA image file

        1. With the device powered on, booted, USB debugging enabled, and the phone connected to the computer.
          Note: If you see the Allow USB Debugging prompt when you connect the phone to the computer, Tap Allow.
        2. Type adb reboot sideload at the command prompt and press Enter.
        3. Type: adb sideload redfin-ota-aa9a.999999.999-aaaa9999.zip at the command prompt and press Enter.
        4. When sideloading finishes, type adb reboot at the command prompt and press Enter.
        5. Note: This slot is bootable and not rooted
      • Sideload the Google OTA image file to the other slot and Root it.

        1. With the device powered on, booted, USB debugging enabled, and the phone connected to the computer. Type adb reboot sideload
        2. Type:
          adb sideload redfin-ota-aa9a.999999.999-aaaa9999.zip at the command prompt and press Enter.
        3. When sideloading finishes, type adb reboot bootloader at the command prompt and press Enter.
          Root this slot - Flash the Magisk_patched....img
        1. Type: fastboot flash boot magisk_patched-99999_aA99a.img at the command prompt and press Enter.
        2. When it finishes flashing, type fastboot reboot at the command prompt and press Enter.
        3. Disconnect the phone from the computer.
        4. Note: This slot is bootable and rooted.
        5. Done! :)
    5. Extract files from the Factory Image

      1. Download the latest Factory image to your phone.
      2. Extract the Factory Image file (cheetah-a9a9a.999999.999-factory-99a9a99a.zip) to a folder. The, stock, flash-all.bat file should be in this folder.
      3. Open the folder you extracted the Factory image to and extract the Image file (image-cheetah-aa9a.999999.999.zip) into the folder. The flash-all bat and, the stock boot.img file should be in this folder.
    6. 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. Important Notes
          • If your phone was previously rooted, DO NOT repeat DO NOT installanother Magisk Manager app. Do this before you patch the boot.img:
            1. Open the Magisk Manager app and disable all Magisk modules.
            2. 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:
              • Open the TB Checker app
              • Tap Run Xposed check
              • Scroll down to Magisk Random Package Name: to see Magisk's hidden name.
                You can also use TB Checker to check if you have more than one Magisk Manager app installed.
          • If your phone boot loops try one of the following options:
            • Flash the 'stock' boot.img to both slots to remove root: fastboot flash boot boot.img --slot all
            • Remove Magisk Modules
              1. Boot Safe Mode
                • When booting, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode.
                • Then reboot and magisk modules should be disabled. (Thanks Lughnasadh)
              2. Command Prompt
                • Press the Power button until the phone turns off.
                • Press the Power and Volume Down to boot fastboot mode.
                • Open a Command Prompt in the Platform-tools folder or the folder that has adb.exe in it, and type adb wait-for-device shell magisk --remove-modules
                • fastboot Reboot.
          • If the Magisk Manager app has the Superuser and Module buttons grayed out: Read @badabing2003 post
        2. Extract the image-redfin-aa9a.999999.999.zip 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, the Image file (image-redfin-aa9a.999999.999.zip) file should be in this folder[/U].
        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 image-redfin-aa9a.999999.999.zip 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. Tap the disc icon (upper right) to save the log file.
        13. Reboot
        14. Copy/Move the magisk_patched_xxxxxx.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
        15. Boot fastboot mode
        16. Connect the phone to the Computer with USB cord.
        17. Open a Command Prompt in the Platform-tools folder.
        18. Type fastboot flash boot "magisk_patched...img" (name of patched.img file) without the quote marks at the Prompt and press enter.
        19. Type fastboot reboot at the Prompt and press enter.
      • 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.
    7. 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!
    8. Install/Update Magisk Modules

    9. 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.
    10. 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.
    11. 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.
    View
    7
    H
    Homeboy76
    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

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

    Windows

    Note: If you have any problems with SDK Platform-tools 34.0.3. You can get SDK Platform-tools 33.0.3 here.
    View
    6
    H
    Homeboy76
    :) I hope you all have a Joyful Holiday season with your family and loves ones. :)

    ~ ~ ~ Stay safe ~ ~ ~​
    View
    5
    Ducter
    Ducter
    prgopala said:
    is there a magisk boot img with modules disabled?. i have a boot loop and need a boot img with it disabled.
    Click to expand...
    Click to collapse
    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
    View
    4
    badabing2003
    badabing2003
    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.
    View

New posts