How To Guide [Guide] Root Pixel 7 Pro 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
supermansaga said:
Safe to update this one? Do we have good release notes on what changed? Thanks
Click to expand...
Click to collapse
notes.md file for Magisk 206102...

@topjohnwu
topjohnwu Update Canary Channel: Upstream to 47d2d4e3
1 contributor
20 lines (17 sloc) 972 Bytes
Magisk (47d2d4e3) (26102)
  • Implement all logging code in the project with Rust
  • [MagiskBoot] Support extracting boot image from payload.bin
  • [Daemon] Make daemon socket a fixed path in MAGISKTMP
  • [resetprop] Support printing property context
  • [resetprop] Support only printing persistent properties from storage
  • [resetprop] Properly support setting persistent properties bypassing property_service
  • [MagiskSU] Support -g and -G options
  • [MagiskSU] Support switching mount namespace to PID with -t
Diffs to v26.1
  • [MagiskBoot] Support extracting boot image from payload.bin
  • [Daemon] Make daemon socket a fixed path in MAGISKTMP
  • [resetprop] Support printing property context
  • [resetprop] Support only printing persistent properties from storage
  • [resetprop] Properly support setting persistent properties bypassing property_service
  • [MagiskSU] Support -g and -G options
  • [MagiskSU] Support switching mount namespace to PID with -t
 
  • Like
Reactions: supermansaga
P

purgy

Senior Member
Aug 29, 2013
183
62
Sydney
Google Pixel 7a
Would I need to disable dm verity etc to install bootloop protector into the boot image? Is this even possible on the 7 series, what with root living in init_boot?

I'm on 7a (lynx) but this seems to be the default "pixel 7 series root" thread.

I assume disabling dm verity etc will involve a data wipe?
 
H

Homeboy76

Recognized Contributor
Aug 24, 2012
4,130
2,510
Google Pixel 7 Pro
purgy said:
Would I need to disable dm verity etc to install bootloop protector into the boot image? Is this even possible on the 7 series, what with root living in init_boot?

I'm on 7a (lynx) but this seems to be the default "pixel 7 series root" thread.

I assume disabling dm verity etc will involve a data wipe?
Click to expand...
Click to collapse
<<Edited>>
AFAIK, you would not have to disable verity to install the Magisk BootloopSaver module created by @huskydg the creater of the Magisk delta fork. Just follow these instructions to install the Magisk BootloopSaver module: OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~..., 7. Install/Update Magisk Modules)

This is a Pixel 7 Pro (cheetah) guide, but Pixel 7 (panther) owners can use it. Pixel 7 owners must download the Factory/OTA images for their phone. Pixel 7a (lynx) owners can also use this guide, just download the Pixel 7a Factory/OTA images.

AFAIK, A first time disabling verity does require a wipe.
 
Last edited:
  • Like
Reactions: andrew2432 and Slim2none4u
sawdoctor

sawdoctor

Senior Member
Sep 11, 2016
462
277
Homeboy76 said:
This is a Pixel 7 Pro guide, but Google Pixel 7 owner can use it. Pixel 7 users must download the Pixel 7 software for their phone. I assume Pixel 7a owners can do the same.

What is "lynx"? Did you mean your PC has a Linux Operating System? What is the bootloop protector that you want to install in the the boot.img?

AFAIK, A first time disabling verity does require a wipe.
Click to expand...
Click to collapse
Lynx is Google's codename for the pixel 7a
 
  • Like
Reactions: Homeboy76
P

purgy

Senior Member
Aug 29, 2013
183
62
Sydney
Google Pixel 7a
Homeboy76 said:
This is a Pixel 7 Pro guide, but Google Pixel 7 owner can use it. Pixel 7 users must download the Pixel 7 software for their phone. I assume Pixel 7a owners can do the same.

What is "lynx"? Did you mean your PC has a Linux Operating System? What is the bootloop protector that you want to install in the the boot.img?

AFAIK, A first time disabling verity does require a wipe.
Click to expand...
Click to collapse
Lynx is Google's codename for the phone, like panther and cheetah for the other p7 series phones.

The module I'm referring to is this one https://github.com/gibcheesepuffs/Magisk_BootloopSaver

While it can run as just a script, it also offers to install itself into the boot image.

As we patch init_boot.img instead of boot.img on these phones, I'm wondering if that will even work, or (rather ironically) cause a bootloop.
 
H

Homeboy76

Recognized Contributor
Aug 24, 2012
4,130
2,510
Google Pixel 7 Pro
purgy said:
Lynx is Google's codename for the phone, like panther and cheetah for the other p7 series phones.

The module I'm referring to is this one https://github.com/gibcheesepuffs/Magisk_BootloopSaver

While it can run as just a script, it also offers to install itself into the boot image.

As we patch init_boot.img instead of boot.img on these phones, I'm wondering if that will even work, or (rather ironically) cause a bootloop.
Click to expand...
Click to collapse

Got it, thanks.

purgy said:
Would I need to disable dm verity etc to install bootloop protector into the boot image? Is this even possible on the 7 series, what with root living in init_boot?

I'm on 7a (lynx) but this seems to be the default "pixel 7 series root" thread.

I assume disabling dm verity etc will involve a data wipe?
Click to expand...
Click to collapse
<<Edited>>
AFAIK, you would not have to disable verity to install the Magisk BootloopSaver module created by @huskydg the creater of the Magisk delta fork. Just follow these instructions to install the Magisk BootloopSaver module: OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~..., 7. Install/Update Magisk Modules)

This is a Pixel 7 Pro (cheetah) guide, but Pixel 7 (panther) owners can use it. Pixel 7 owners must download the Factory/OTA images for their phone. Pixel 7a (lynx) owners can also use this guide, just download the Pixel 7a Factory/OTA images.

AFAIK, A first time disabling verity does require a wipe.
 
Last edited:
  • Like
Reactions: purgy
S

supermansaga

Senior Member
Mar 12, 2011
324
68
Does anyone have this issue after updating to June? An endless attempt to update a 0kb Cross-Device Services? Thanks. Pls see the screenshot
 

Attachments

  • Screenshot_20230616-183554.png
    Screenshot_20230616-183554.png
    51.8 KB · Views: 48
M

mochamoo

Senior Member
Oct 16, 2010
560
151
Google Pixel 7 Pro
Updated a rooted phone with no trouble. Am trying to update a non rooted phone with the OTA image. Adb devices shows it. It doesn't show any more so adb sideload doesn't work. USB debugging is on. Any ideas?
 
You must log in or register to reply here.

Similar threads

roirraW "edor" ehT
How To Guide September 18, 2023 TQ3A.230901.001 Global | .C2 Verizon - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Replies
3K
Views
278K
schmeggy929
schmeggy929
Freak07
  • Poll
Development [Kernel][23.09.2023][Android 13.0.0 Stable]Kirisakura_Raviantah 1.1.5 for Pixel 7/Pro aka "Pantah"
Replies
2K
Views
197K
Samuel Holland
Samuel Holland
badabing2003
Themes / Apps / Mods 📳🔥PixelFlasher for Google Pixel 7 Pro Support Thread.
Replies
1K
Views
79K
badabing2003
badabing2003
N
Development [ROM][UNOFFICIAL][cheetah/panther] LineageOS 20.0 for the Pixel 7 Pro/7
Replies
352
Views
58K
Shihabus Sakib Rad
Shihabus Sakib Rad
roirraW "edor" ehT
General September 20 2023 - Android 14 QPR1 Beta 1 U1B1.230908.003 - "Upside Down Cake" - Pixel 7 Pro [Cheetah]
Replies
869
Views
85K
Aks
Aks

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 3
    Lughnasadh
    Lughnasadh
    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.
    View
    2
    M
    moichman
    Homeboy76 said:
    I'm curious to read your answer to @simplepinoi177 question. What version of magic are you using to patch the init_boot.img?

    Then try the following on your phone:
    1. Pull down quick settings tap the power icon, tap and hold Power off until you see Boot Safe Mode tap ok. Let Safe mode boot fully, then reboot.
    2. Then use TB checker to check for duplicate Magisk Manager app installed:
      • Open the TB Checker app
      • Tap Run Xposed check
      • Scroll down to Magisk Random Package Name: to see a Magisk's Manager app name. Delete that Magisk Manager app.
    Then do this on your computer
    1. Flash the 'stock' init_boot.img to both slots to remove root: ./fastboot flash init_boot boot.img --slot all
    2. Then flash the Magisk patched image.
      ./fastboot flash init_boot magisk_patched_[random].img
      Check if you have root.
    Click to expand...
    Click to collapse

    yay! profit!
    i downloaded a fresh copy of the factory image and copied init_boot.img to platform tools. since there was a slight difference from what was supposed to be in the tb checker results, i am going to detail it all.
    i did the first step 1 and 2, and noticed something odd when i ran tb checker. after the xposed check, all references regarding magisk failed. also, the magisk random package name was enpty, even though the magisk app was installed. that cinched what the problem was, in my mind. i went ahead and deleted magisk as you suggested.
    i did part 2 step 1 and flashed init_boot.img, as you suggested. i then installed the magisk app and pushed the init_boot.img to the pixel, and patched it. after pulling the patched image and flashing it as you suggested in part 2 step 2 and rebooted it now says the device is rooted and apps recognize it.
    thank you, @Homeboy76 and @simplepinoi177 for taking the time to analyze and respond, and offering succinct advice!
    View
    2
    H
    Homeboy76
    Magisk Canary Update

    Magisk (96e559fb) (26203)
    • [General] Update BusyBox to 1.36.1
    • [General] Fix compiling toolchain that produces broken arm32 executables
    Diffs to v26.2
    • [General] Fix device information detection script
    • [General] Update BusyBox to 1.36.1
    • [General] Fix compiling toolchain that produces broken arm32 executables

      magisk-files/notes.md at canary · topjohnwu/magisk-files · GitHub

    Download

    1. Tap app-release.apk
    2. Tap the three dot menu across from Code Blame
    3. Tap Download
    View
    2
    H
    Homeboy76
    Google's September 2023 factory and OTA are up!
    View
    2
    H
    Homeboy76
    moichman said:
    if i may ask what may be a stupid question. in the instructions on the first page, i certainly appreciate the detailed instructions and covering the varied situations and outcomes. i am comfortable with, and have done on my old phone, running the flash-all.
    my question is this: if one is simply doing a monthly update on an already rooted phone, is there a reason to go through the process of extracting the flash-all and editing, etc? is it better than flashing the stock image, doing the OTA through settings, then flashing the patched init_boot.img back...or will this miss something that using flash-all won't?
    similar questions apply to upgrading to 14, when it's released. can i flash the stock image, do the upgrade, then flash the patched init_boot.img, or is it better to flash-all, etc?
    thanks!
    Click to expand...
    Click to collapse
    If you just use the flash-all.bat file without editing it, it will wipe your phone.

    If you take the automatic OTA it will unroot your phone and you have to flash Magisk to the inactive slot or flash the new patched init_boot. img that you extracted from the latest factory image.

    There are some post that state the latest Magisk Alpha/Canary can extract the init_boot.img from the OTA.zip file. At this point in time I am not familiar with that process.
    I'm hoping @shoey63 who has extracted the init_boot.img from the OTA.zip will share the process he used to do it.
    View
  • 43
    H
    Homeboy76
    [Guide] Root Pixel 7 Pro with Magisk + Unlock Bootloader + Pass SafetyNet + More
    Android Security Bulletin—September 2023
    Pixel Update Bulletin—September 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 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 13

        • Upgrade to Android 13: OP, Part II - INSTRUCTIONS, 2. Install/Update Factory Image keep data or wipe data, Keep data
      • 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. Extract the init_boot.img file from the Factory Image.
          • Download the latest Factory image to your phone.
          • Extract the Factory Image file (cheetah-a9a9a.999999.999-factory-99a9a99a.zip) to a folder.
          • 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.
        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 init_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 init_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 init_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
          • 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 13 T.W.R.P.
    View
    9
    H
    Homeboy76
    << 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....
    View
    8
    H
    Homeboy76
    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
    View
    7
    simplepinoi177
    simplepinoi177
    @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!
    View
    6
    D
    dd805bb
    Reported as bug.

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

New posts