[Guide] [December 6, 2023] Root Pixel 5 Unlock Bootloader + Pass SafetyNet + Both Slots Bootable + More

Search This thread
By:
Advanced…
franck811

franck811

Member
Oct 13, 2012
45
9
Corsica
For me I had everything uninstalled and even made a clean installation for the update and since I can not root I am in bootloop constantly
 
H

Homeboy76

Recognized Contributor
Aug 24, 2012
4,200
2,728
Google Pixel 8 Pro
franck811 said:
For me I had everything uninstalled and even made a clean installation for the update and since I can not root I am in bootloop constantly
Click to expand...
Click to collapse
What?
You're rooted, the phone is booting, but you're getting constant boot loops?
Was the magisk Update Channel set to the same version of Magisk i.e., Beta/Canary/Stable before you patched the boot.img?
 
Last edited:
franck811

franck811

Member
Oct 13, 2012
45
9
Corsica
I am not rooted clean install ..... identical update channel before flash and I get bootloop even by flashing fastboot flash boot --slot all boot.img I do not get out I have to flash the entire ROM to go out
 
A

aznriceballman

Senior Member
Jun 27, 2014
145
13
Homeboy76 said:
Just Curious
Is the SDK Platform-tools on your computer r31.0.0?
Did you remove all the Modules before you patched the boot.img?
Did flashing the stock boot.img fastboot flash boot --slot all boot.img remove the boot loop?
Try booting Safe Mode then reboot and try fastboot flash boot magisk_patched_oLhvB.img.
Click to expand...
Click to collapse
I most definitely did not remove all the modules.... Is booting into safe mode then flashing a good enough way to do this?
 
H

Homeboy76

Recognized Contributor
Aug 24, 2012
4,200
2,728
Google Pixel 8 Pro
jackowy said:
so I either could flash the whole factory image again with -w or just wait till May? Any downsides I may run into? Thanks for your reply’s :)
Click to expand...
Click to collapse
Using the -w will wipe your internal Storage. It is the same as doing a Factory reset: Settings => System => Advanced => Reset options => Erase all data (factory reset)
So, if it ain't broke don't fix it
 
Last edited:
G

Gibsonflyingv

Senior Member
Jul 28, 2011
378
62
Homeboy76 said:
Just Curious
Is the SDK Platform-tools on your computer r31.0.0?
Did you remove all the Modules before you patched the boot.img?
Did flashing the stock boot.img fastboot flash boot --slot all boot.img remove the boot loop?
Try booting Safe Mode then reboot and try fastboot flash boot magisk_patched_oLhvB.img.
Click to expand...
Click to collapse
I'm able to use the factory fastboot flash boot boot.img --slot all to at least get past the boot loop. I tried uninstalling magisk, doing safemode, rebooting and then flashing my patched boot.img but that resulted in another bootloop. :(

Is the only way out of this to do a clean install? Really didn't want to do that right now.
 
franck811

franck811

Member
Oct 13, 2012
45
9
Corsica
Gibsonflyingv said:
I'm able to use the factory fastboot flash boot boot.img --slot all to at least get past the boot loop. I tried uninstalling magisk, doing safemode, rebooting and then flashing my patched boot.img but that resulted in another bootloop. :(

Is the only way out of this to do a clean install? Really didn't want to do that right now.
Click to expand...
Click to collapse
clean install was for me the only issue I do not understand because the root has always worked for updates but the one impossible to root ..... I give up for the moment
 
sidhaarthm

sidhaarthm

Senior Member
Mar 1, 2009
444
144
London, U.K.
Reading some of the recent posts, I'd just like to say that I had no issues rooting my Pixel 5 after the latest April update tonight.

Here are the steps I followed:
- Disabled (not removed) any UI or other Magisk mods that I felt could have interfered with the update
- Extracted the boot.img from the factory April ROM and patched it using Magisk app on my Pixel 5, while I was still on the March update (with root)
- Unhide Magisk v22 app
- Flashed factory April ROM (without wipe)
- Flashed magisk_patched.img boot image - root successfully acquired
- Flashed latest EX Kernel and re-instated any Magisk mods that I had previously disabled.

I have root and everything works as expected, AdAway, GPay, ViperFX etc.

I know its' strictly not recommended, but here is the link to my Magisk v22 patched boot.img for April update, in case it helps anyone who is currently stuck without root.
 
  • Like
Reactions: franck811
H

Homeboy76

Recognized Contributor
Aug 24, 2012
4,200
2,728
Google Pixel 8 Pro
sidhaarthm said:
Reading some of the recent posts, I'd just like to say that I had no issues rooting my Pixel 5 after the latest April update tonight.

Here are the steps I followed:
- Disabled (not removed) any UI or other Magisk mods that I felt could have interfered with the update
- Extracted the boot.img from the factory April ROM and patched it using Magisk app on my Pixel 5, while I was still on the March update (with root)
- Unhide Magisk v22 app
- Flashed factory April ROM (without wipe)
- Flashed magisk_patched.img boot image - root successfully acquired
- Flashed latest EX Kernel and re-instated any Magisk mods that I had previously disabled.

I have root and everything works as expected, AdAway, GPay, ViperFX etc.

I know its' strictly not recommended, but here is the link to my Magisk v22 patched boot.img for April update, in case it helps anyone who is currently stuck without root.
Click to expand...
Click to collapse
Just One Problem with Your Method
"- Disabled (not removed) any UI or other Magisk mods that I felt could have interfered with the update"

There are some people (noobs) who are not technically knowledgeable enough about UI or Magisk mods to choose which UI or mods to disable.

If they guess wrong boot loops, that is why I recommend uninstalling Magisk - Restore Images.

You are correct it is not encouraged/recommended to use a magisk_patched.img that was not patched on your phone.
 
Last edited:
  • Like
Reactions: sidhaarthm
G

Gibsonflyingv

Senior Member
Jul 28, 2011
378
62
So is there no way to recover from not uninstalling/unhiding magisk? I'm assuming I'll have to format, re-unlock, everything?
 
H

Homeboy76

Recognized Contributor
Aug 24, 2012
4,200
2,728
Google Pixel 8 Pro
Gibsonflyingv said:
So is there no way to recover from not uninstalling/unhiding magisk? I'm assuming I'll have to format, re-unlock, everything?
Click to expand...
Click to collapse
@Gibsonflyingv, you do not have to relock the bootloader.
Just do #4 'Wipe data', then #7 to Reroot - Patching the boot.img.

Notes:
  1. Backup any files yo want to keep (Photos, SMS, etc.) before doing #4 'Wipe data' because it will wipe your Internal Storage.
  2. Before repatching the boot.img, make sure the Magisk Update Channel is set to the same version of Magisk you are using to repatch the boot.img: Beta/Canary/Stable
 
Last edited:
You must log in or register to reply here.

Similar threads

V0latyle
[GUIDE] Pixel 5 "redfin": Unlock Bootloader, Update, Root, Pass SafetyNet
Replies
472
Views
57K
R
Regys
R
[Tutorial] Unlock Bootloader, get root and valid Safetynet
Replies
307
Views
63K
supaneko
supaneko
M
[Guide] Flash Magisk on Android 12
Replies
370
Views
88K
K
kartikeya98
S
[Video][Tutorial] How to enable 5G for Unlisted Countries on Pixel 4a(5G) and Pixel 5 using QPST.
Replies
109
Views
34K
S
swangjang
Az Biker
UPDATING Pixel 5 Factory Image & Re-Rooting
Replies
47
Views
18K
{davros}
{davros}

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 1
    badabing2003
    badabing2003
    HippoMan said:
    I was going to try KernelSU on my Pixel 5 running A11 a while ago, but I got sidetracked and never got to it. I now want to try either KernelSU or APatch on this device.

    Does anyone have any successful experience getting either KernelSU or APatch to work on the Pixel 5 running A11?

    I want to stick with A11 if possble, because there's a working TWRP version for the Pixel 5 running that OS version, and I do not want to lose nandroid backup/restore capabilities.

    Thank you in advance for any thoughts.
    Click to expand...
    Click to collapse
    KernelSU requires a GKI, which I'm sure your A11 is not.
    My A14 Pixel 5 is not.
    That leaves you with APatch
    Last I check it didn't work on my P5
    The readme says: CONFIG_KALLSYMS_ALL=n: Early support
    View
  • 55
    H
    Homeboy76
    [Guide][November 6, 2023] Root Pixel 5 Unlock Bootloader + Pass SafetyNet + Both Slots Bootable + More
    Android Security Bulletin—November 2023
    Pixel Update Bulletin—November 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

      • ...
    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.
    ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~
    (The Instructions listed below are not steps, they are individual sets of instructions for the Pixel 5.)
    1. (NEW) PREVENT/FIX BOOT LOOPS

      • Prevent Boot Loops
        1. Before you patch the init_boot.img: Open the Magisk app and disable all Magisk modules.
          • If you hid the Magisk app, the default name for a hidden Magisk app is settings.
          • If you changed the hidden name to something else and have forgotten it. Use TB checker to find the name of the hidden Magisk Manager:
            1. Open the TB Checker app
            2. Tap Run Xposed check
            3. Scroll down to Magisk Random Package Name: to see Magisk's hidden name.
        2. Check for more than one installation of Magisk app: Use TB Checker
      • Fix Boot Loops
        1. Flash the 'stock' init_boot.img to both slots to remove root: fastboot flash init_boot init_boot.img --slot all
        2. Boot Safe Mode while booting to remove Magisk Modules:
          • 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)
        3. Use adb shell command, to remove Magisk Modules
          • 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 and fastboot.exe in it, and type adb wait-for-device shell magisk --remove-modules. When it finishes type fastboot Reboot
    2. 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.
    3. Manually Install/Update Factory Image keep data or wipe data

      • Before you start:

        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' init_boot.img to both slots to remove root: fastboot flash init_boot init_boot.img --slot all
          • 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 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 Factory Image: Pixel 5 - redfin to your Computer.
        8. Extract files from the Factory Image

          • 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 bootloader...img; flash-all.bat; image...zip; and radio...img files are in this folder. Extract the image-redfin-aa9a.999999.999.zip file to a folder. Open the folder you extracted the image-redfin-aa9a.999999.999.zip file to, the boot.img is in this folder. file should be in this folder.
        9. Copy/Move the bootloader...img; image...zip; and radio...img and boot.img files to your computer's Platform-tools folder, the folder that has fastboot.exe in it.
      • Flash Factory Image Keep Data

        1. Updating/Upgrading Android 14
          Note: If you are Upgrading your Android Version, It is a good idea to flash the bootloader to both slots (A & B).
          ~ E D I T - flash-all.bat file ~

          @Echo off
          PATH=%PATH%;"%SYSTEMROOT%\System32"
          fastboot set_active other
          fastboot reboot-bootloader
          fastboot flash bootloader --slot all bootloader-redfin-aaaaaa-9.9-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot flash radio radio-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

          echo Press any key to exit...
          pause >nul
          exit
          ~ END EDIT - flash-all.bat file ~
        2. After, you have edited the flash-all.bat file, copy/Move it to your computer's platform-tools folder.
        3. Boot fastboot mode (Power off the phone => Press the Power and Down buttons until you see Start)
        4. Connect your phone to the computer.
        5. Open a Command Prompt on your computer in the platform-tools folder and type: flash-all at the Command Prompt and press enter.
        6. The phone will reboot when flashing is completed.
        7. 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

        1. This will wipe your phone's Data/Internal Storage.
        2. Do not edit the flash-all.bat file,
        3. Boot fastboot mode (Power off the phone => Press the Power and Down buttons until you see Start)
        4. Connect your phone to the computer.
        5. Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
        6. The phone will reboot when flashing is completed.
        7. Go-to Part II - INSTRUCTIONS, 7. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
      • Some kernels require Disabling verity and verification

        1. If you need to disable Verity and Verification. Edit the flash-all.bat file, to disable Verity and Verification.
          ~ Edit - 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-aa9a.999999.999.a9.zip
          echo Press any key to exit...
          pause >nul
          exit
          ~ ~ ~ END EDIT ~ ~ ~
        2. Notes:
          • The first time you Disable Verity and Verification it will wipe your Data/Internal Storage.
          • When doing subsequent updates and disabling Verity and Verification, the -w flag can be removed to Keep Data.
          • 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.
        3. Copy/Move the edited flash-all.bat file to the platform-tools folder on your computer.
        4. Boot fastboot mode (Power off the phone => Press the Power and Down buttons until you see Start)
        5. Connect your phone to the computer.
        6. Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
        7. The phone will reboot when flashing is complete.
        8. Go-to Part II - INSTRUCTIONS, 6. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
      • Setup phone

        1. Enable Developer Mode
          • Open Setup => About phone => Tap Build number 7 times or until you see you are a 'Devloper'.
        2. Enable Developer Opitions
          • Open Setup => System => Developer options => Enable Developer options
    4. Manually Install/update the OTA image keep data and root/re-root your phone

      • Before you start:

        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:
          • Flash the 'stock' boot.img to both slots to remove root: fastboot flash boot boot.img --slot all
          • 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 files to your phone
        8. Extract the image-redfin-aa9a.999999.999.zip file from the Factory Image.

          • 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-redfin-aa9a.999999.999.zip file should be in this folder.
        9. Copy/Move the image-redfin-aa9a.999999.999.zip file and the redfin-ota-aa9a.999999.999-aaaa9999.zip to your computer's Platform-tools folder, the folder that has adb.exe in it.
      • Patch the boot.img

        1. Open Magisk (next to Magisk)
        2. Tap Install
        3. Tap Select and patch a file
        4. Navigate to the image-redfin-aa9a.999999.999.zip file
        5. Tap it then tap the check mark (✓)
        6. Tap Lets go
        7. When you see done the 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
        10. 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 side loading the OTA image finishes, you should see this:
          • On your computer,
            C:\platform-tools (location of folder with adb and OTA image in it)>adb sideload redfin-ota-up1a.999999.999-9a99a999.
            Total xfer: 2.00x
            C:\platform-tools>
          • On your phone, ...status 0
        4. 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. 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
          • 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.
          • 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 files
            1. The latest Factory Image: Pixel 5 - redfin
            2. The latest OTA Image: Pixel 5 - redfin
            3. Verify the checksum of the Factory and OTA images. 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.
          • Extract the image-redfin-aa9a.999999.999.zip file from the Factory Image.

            1. Extract the Factory Image file (redfin-a9a9a.999999.999-factory-99a9a99a.zip) to a folder.
            2. Open the folder you extracted the Factory image to, the image-redfin-aa9a.999999.999.zip file should be in this folder.
          • Copy/Move the image-redfin-aa9a.999999.999.zip file and the redfin-ota-aa9a.999999.999-aaaa9999.zip to your computer's Platform-tools folder, the folder that has adb.exe in it.
          • 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 image-redfin-aa9a.999999.999.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
          • Copy/Move the magisk_patched....img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it.
          • Connect the phone to the computer.
        2. On your Computer
          • 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, on your phone, 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, on your phone, 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 side loading the OTA image finishes, you should see this:
          • On your computer,
            C:\platform-tools (location of folder with adb and OTA image in it)>adb sideload redfin-ota-up1a.999999.999-9a99a999.
            Total xfer: 2.00x
            C:\platform-tools>
          • On your phone, ...status 0
        5. Type adb reboot at the command prompt and press Enter.
        6. Note: This slot is bootable and not rooted
      • Sideload the Google OTA image file to the other slot and Root it.

        1. Type adb reboot sideload at the command prompt and press Enter
        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! :)
    6. 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.
    7. Root/Reroot with Magisk and Pass SafetyNet.

      • Android 14

        • Upgrade to Android 14: 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 Fork

        1. Download File(s)
        2. Install osm0sis PlayIntegrityFork
          • Open Magisk
          • Tap Modules icon
          • Tap Install from storage
          • Navigate to the osm0sis PlayIntegrityFork file you downloaded.
          • Tap the osm0sis PlayIntegrityFork file.
          • When you see the confirmation screen, tap Ok.
          • After it installs tap the Disc 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
          • Flash the osm0sis PlayIntegrityFork module in Magisk
          • Turn Airplane mode on
          • Open Settings
          • Tap Apps & notifications
          • Tap see all...
          • Tap three dot menu
          • Tap Show system
          • Scroll to Google Wallet/Play Store/Play Services
          • Clear Google Wallet cache (if you have it)
          • Clear Google Play Store cache and data
          • Clear Google Play Services (com.google.android.gms) cache and data (Optionally skip clearing data and wait some time, ~24h, for it to resolve on its own)
          • Turn Airplane mode Off
          • Reboot
        5. Check Device Certification
          • Note: If after completeting Get Device Certified your device is not certifed or your device is certified but certain apps (Google Pay, NetFliks, etc.) are not working. Do this to verify you are passing Play Integrity.
            1. Open Google Play Store app
            2. Tap your profile icon (top right corner)
            3. Tap Settings.
            4. Open the About menu
            5. Tap the row labeled Play Store version seven times to unlock developer mode.
            6. Tap the back arrow (upper left corner)
            7. Tap your profile icon (top right corner)
            8. Tap Settings.
            9. Open the General menu
            10. Tap Developer options
            11. Tap Check integrity
            12. If you see Basic Integrity and Device Integrity, you're passing Play integrity.
    8. 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!
    9. Install/Update Magisk Modules

    10. 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.
    11. 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.
    12. ADB Sideload

    ~ ~ ~ Part III - OTHER ~ ~ ~
    1. Custom ROMs

      • Need help with a Custom ROM?

        1. If you are trying to install a Custom ROM, read and follow the Installation Instructions in the OP of the Custom ROM thread.
        2. If you have questions, search the thread of the Custom ROM you are trying to install for answer(s)/solution(s) to your question(s)/problem(s)[/B]: 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.
        3. Try installing it with 📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones..
        4. 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 Kernel, Magisk, etc. you want to install for installation instructions, and answer(s)/solution(s) to your question(s)/problem(s) about the Custom Kernel, Magisk, etc. 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 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.
    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://xdaforums.com/t/platform-to...7-pro-cheetah-safetynet.4502805/post-88571575

    @Lughnasadh, suggested a fix.
    https://xdaforums.com/t/platform-to...7-pro-cheetah-safetynet.4502805/post-88571601

    @badabing2003, confirmed the suggested fix works.
    https://xdaforums.com/t/platform-to...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