• We are moving to xdaforums.com!

    Posts made between now and when the migration is complete will not be carried over.
    You will be automatically redirected once the migration is complete.

How To Guide [Guide] Root Pixel 7 Pro with Magisk + Unlock Bootloader + Pass SafetyNet + More

Search This thread

badabing2003

Recognized Contributor
Sep 17, 2012
3,053
4,725
Hello, comprehensive guide. thanks.

i get a pixel 7 in a few days, so started to gain informations.
i'm flashing/brinking android devices for a few years now, but not pixels. just be curious and for understandings:
- if i want root immediately after a update-stockrom or customrom via fastboot method: why not just go into recovery afterwards and just sideload magisk.zip to root?
- is it possible to replace init_boot.img in a image zip (stock or custom rom) with the magisk patched version just to immediately get root after fastboot flashing something? (of course: using the init_boot from that zip before to patch with magisk)

thank you all
First part no, there is no recovery or twrp for Pixel.
Second part, yes.
 
  • Like
Reactions: ChillDuder

badabing2003

Recognized Contributor
Sep 17, 2012
3,053
4,725
thank you.
i thought there is a 'install update via adb' option in stock recovery, because i saw a screenshot of a pixel recovery on random internet search ;)
if your bootloader is unlocked you can dirty flash factory image and flash patched init_boot.
If your bootloader is not unlocked, the only thing you could do is sideload OTA and get updated.
 
  • Like
Reactions: ChillDuder

ChillDuder

Senior Member
Nov 23, 2015
55
16
Xiaomi Mi 8
OnePlus 8T
i had to do --disable-verity --disable-verification along with wipe data -w at least once with stock rom flashing to get disabled verification, for e.g. custom kernels. ok.
and if i wish to stay disabled verification i had to continue to do so.

but do had this to do also with every custom rom flashes?
thanks in advance
 

Homeboy76

Recognized Contributor
Aug 24, 2012
4,141
2,525
Google Pixel 7 Pro
i had to do --disable-verity --disable-verification along with wipe data -w at least once with stock rom flashing to get disabled verification, for e.g. custom kernels. ok.
and if i wish to stay disabled verification i had to continue to do so.

but do had this to do also with every custom rom flashes?
thanks in advance
Yes, you have to --disable-verity --disable-verification every time you update the factory image. If you want to use a Custom kernel. If you skip doing it once the next time you do it you will have to wipe your phone.
 
Last edited:

Homeboy76

Recognized Contributor
Aug 24, 2012
4,141
2,525
Google Pixel 7 Pro
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.
 
Last edited:

Homeboy76

Recognized Contributor
Aug 24, 2012
4,141
2,525
Google Pixel 7 Pro
Sorry;
Does most of this work for the pixel 7? Some of the custom os section says panther/cheetah in the titles. Hoping they are similar
I think you are asking about the Operating System (OS), but you want to know if the firmware/software is interchangable.

Why?

You wrote, "Some of the custom os section says panther/cheetah in the titles. Hoping they are similar"

The OS on all Google phones is Android.
The Google Pixel 7/7Pro are on Android 13. Yea, I know they are beta testing Android 13 and 14.

AFAIK, Google makes firmware/software for the Google Pixel 7/7 Pro, and several other Google phones. Every phone they make has its own unique firmware/software they are not interchangeable i.e.,

cheetah" for Pixel 7 Pro
13.0.0 (TQ2A.230505.002, May 2023) Flash Link fe44ced0de116faaabf4928ee3db7f382d034d54fe5da7dab7575ba4febd9a89

panther" for Pixel 7
13.0.0 (TQ2A.230505.002, May 2023) Flash Link 3271ae5c4d3288e4a067ad161728ae40a6fc62f8acafd0e426442c9e04c71a05

Everything looks the same but the SHA256 verification.

Why? The files are not the same.

The firmware/software for the Google Pixel 7 is not made to work on the Google Pixel 7 Pro and vice versa.

You can use this guide for Google Pixel 7/7 Pro, but you must use the correct firmware/software for your phone version.
 
Last edited:

simplepinoi177

Forum Moderator
Staff member
Sorry;
Does most of this work for the pixel 7? Some of the custom os section says panther/cheetah in the titles. Hoping they are similar
What @Homeboy76 states in Post #456 is true and answers most of your inquiry, as supplemental information -- adb & fastboot commands, drivers, sometimes custom ROMs & kernels, apps, work for both panther/cheetah (Pixel 7/Pixel 7 Pro).
 

Homeboy76

Recognized Contributor
Aug 24, 2012
4,141
2,525
Google Pixel 7 Pro
What @Homeboy76 states in Post #456 is true and answers most of your inquiry, as supplemental information -- adb & fastboot commands, drivers, sometimes custom ROMs & kernels, apps, work for both panther/cheetah (Pixel 7/Pixel 7 Pro).

Most of this works for the pixel 7 not pro? Custom os section says panther/cheetah
True, however @andrew2432 original post (See above) stated "Custom os section says panther/cheetah" I assumed andrew2432 was referring to a section in this thread: OP, ~ ~ ~ Part III - OTHER ~ ~ ~, 1. Custom ROMs, • Need help with a Custom ROM.

My assumption was wrong. :ROFLMAO:

My thanks to Staff Member @simplepinoi177 for the "assist". :) 👍
 
Last edited:

andrew2432

Senior Member
Yeah sorry, I don't have a pro. I meant do I take the same actions/run the same commands but with pixel 7 files. Coming from a pixel 5; so new boot stuff to pay attention to and a few more odd things here and there. It looks like had I read first I could see pixel 7 users are using this guide with success.
 
  • Like
Reactions: Homeboy76

wangdaning

Senior Member
Sep 17, 2012
1,527
650
Wuxi
Yeah, method is the same, just files are different.
Yeah sorry, I don't have a pro. I meant do I take the same actions/run the same commands but with pixel 7 files. Coming from a pixel 5; so new boot stuff to pay attention to and a few more odd things here and there. It looks like had I read first I could see pixel 7 users are using this guide with success.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    Just as a reminder, the "2 slot approach" is not really meant to allow you to switch to your unrooted slot and then have apps work properly because that slot is unrooted. The problem here is that in most instances with an unlocked bootloader you won't be able to pass Play Integrity API checks without doing more, such as rooting and then using Displax's USNF mod or Chiteroman's Play Integrity Fix mod. Thus, even on a slot that is unrooted, you will still fail the Play Integrity API checks because your bootloader is unlocked and "most" apps in question (e.g. apps that check the security of your device such as checking if you are rooted) need to pass this in order to work properly. There are, however, some apps that check if you are rooted, but don't check if you are passing Play Integrity or if your bootloader is unlocked. In these limited circumstances the "2 slot approach" would be helpful.

    Also, with the "2 slot approach", you would be able to switch from the rooted slot to the unrooted slot without a computer, but not vice versa. To switch from the unrooted slot back to the rooted slot you would need a computer.

    But in general, It's more of a fail safe in case something goes wrong with one slot you know the other slot is bootable because this method makes both slots bootable.

    And both slots share /data partition, so you will have the same apps and app data on both slots.
    5
    Is it possible to switch slot within the phone? I mean, without connecting it to a pc.
    If you are on a rooted slot you can switch using the app below. As stated above, if you are on an unrooted slot you need to use a PC since this app requires root.

    4
    The "Your device is corrupt. It can't be trusted and may not work properly." message is not part of the unlocked bootloader message. It is the RED eio corrupt message.

    The system is just noticing the expected and calculated hash on the boot partition doesn't match. The bootloader is looking for an updated OS. Flashing an old boot image and then a new/current boot image often gets rid of it. The bootloader notices an updated boot image and switches back to restart mode instead of eio mode.

    I have not seen anyone report any ill effects from having this message. You can likely leave it as is if you want, do the old/new boot image maneuver or wait until the next update which "should" get rid of the message as well.
    3
    many thanks. One more dumb question. How can I quickly check if both of my current 2 slots are even bootable? Obviously one is already bootable. But I have no idea about the other. I forgot if I had flash both the last time.
    You can use the app I mentioned above. Or if you sideloaded the OTA onto your current slot then just sideload it again and both slots will be bootable.
  • 43
    [Guide] Root Pixel 7 Pro with Magisk + Unlock Bootloader + Pass SafetyNet + More
    Android Security Bulletin—October 2023
    Pixel Update Bulletin—October 2023

    Introduction
    This Guide is for Pixel 7 Pro 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 init_boot.img using the Google OTA image file and Magisk
        @Shoey discovered and tested the procedure (see - OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 3., or 4.).
      • Android 14 Beta QPR1 are up.
        Builds (Factory/GSI/OTA) are available for the following Pixel devices:
        1. Google Pixel 5a
        2. Google Pixel 6 and 6 Pro
        3. Google Pixel 6a
        4. Google Pixel 7 and 7 Pro
        5. Google Pixel 7a
        6. Google Pixel Fold
        7. Google Pixel Tablet
    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 on his Pixels 7 pro and 6 Pro, and his many helpful contributions to this thread.
      • @Shoey - for discovering and testing patching the init_boot.img using the full Google OTA image file and Magisk (see - OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 3. or 4.)
      • 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 error while 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' init_boot.img to both slots to remove root: fastboot flash init_boot boot.img --slot all
          • Boot Safe Mode to 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 to 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 7 Pro - cheetah to your Computer.
        8. Go to Part II - INSTRUCTIONS => 4. Extract the flash-all.bat and the init_boot.img 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-cheetah-aaaaaa-9.9-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot flash radio radio-cheetah-a9999a-999999-999999-a-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot update image-cheetah-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-cheetah-....img
          2. flash-all.bat
          3. image-cheetah-....zip
          4. radio-cheetah-....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 init_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-cheetah-aaaaaa-9.9-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot flash radio radio-cheetah-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-cheetah-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-cheetah-....img
          2. flash-all.bat
          3. image-cheetah-....zip
          4. radio-cheetah-....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 init_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 error while 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:
          • Boot Safe Mode while booting to 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 off to 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 7 Pro - cheetah to your Computer.
      • Patch the init_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 init_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 cheetah-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 init_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 init_boot.img:
            1. Note: Before patching the init_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 init_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 cheetah-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 cheetah-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 init_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, stock, init_boot.img file should be in this folder.
    6. Root/Reroot with Magisk and Pass SafetyNet.

      • Android 14

        • Upgrade to Android 14: OP, Part II - INSTRUCTIONS, 2., 3, or 4.
      • Patching the init_boot.img - to root/reroot.

        1. Important Notes
          • If your phone was previously rooted, DO NOT repeat DO NOT install another Magisk Manager app. Do this before you patch the init_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' init_boot.img to both slots to remove root: fastboot flash init_boot init_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. Patch the init_boot.img file
          • Factory Image - Extract and Patch the init_boot.img file

            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.
            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, stock, init_boot.img file should be in this folder.
            4. Install Magisk Manager App Beta, Canary, or Stable
            5. Open Magisk Manager App
            6. Tap the Settings icon, tap Update Channel, and set the version to the version you Installed.
            7. Tap the back arrow (<--) at the top next to Settings
            8. Tap Install, top right corner next to Magisk
            9. Tap, Select and Patch a File
            10. Select the init_boot.img file you extracted from the latest factory image.
            11. Tap the ✓ (Check Mark)
            12. Tap Let's Go
            13. When you see done the init_boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.
            14. Tap the disc icon (upper right) to save the log file.
            15. Reboot
          • OTA Image - Patch the init_boot.img file

            1. Open Magisk Manager App
            2. Tap Install, top right corner next to Magisk
            3. Tap Select and patch a file
            4. Navigate to the Google OTA.zip file
            5. Tap it then tap the check mark (✓)
            6. Tap Lets go
            7. When you see done the init_boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.
            8. Tap the disc icon (upper right corner) to save the log file.
            9. Reboot
        3. 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
        4. Boot fastboot mode
        5. Connect the phone to the Computer with USB cord.
        6. Open a Command Prompt in the Platform-tools folder.
        7. Type fastboot flash init_boot "magisk_patched...img" (name of patched.img file) without the quote marks at the Prompt and press enter.
        8. 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
          • 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

      • 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 Androidacy Module Manager

        1. Open Androidacy 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 Androidacy 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
    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
    2. Themes, Apps, and Mods
    3. T.W.R.P. Backup/Restore

      • Waiting for Android 14 T.W.R.P.
    9
    << Edited >>
    Update Displax/safetynet-fix Mod forked from kdrag0n/safetynet-fix
    Changelog: v2.4.0-MOD_2.0
    • Fix KernelSU support. You still need "ZygiskOnKernelSU".
    • Fix WiFi calling on some devices (and maybe other related issues) by moving changing ro.product.first_api_level from global namespace to GMS only.
    • Pass MEETS_STRONG_INTEGRITY[. By default you need device that launched with Android 13+ or custom ROM that manipulate with ro.product.first_api_level (>= 33 / or null / or not present).
      If you want to play with it more complex - use separate "-STRONG" build. NOTE: Various system issues are possible on "-STRONG" build!
      (Fixed by Google)
    Use Displax's v2.4.0-MOD_1.3....
    8
    Update
    I tested SDK Platform-tools r. 34.0.1 it is not fixed. There are still problems with fastbootd. Use SDK Platform-tools r. 33.0.3
    7
    @Homeboy76
    I'm sure everybody would join in on my congratulations on becoming a Recognized Contributor! You certainly work diligently enough on this thread and on all your others to deserve the title!
    6
    Reported as bug.

    It's been confirmed and fix is being done on GitHub. FYI everyone. Open source rules.