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

Search This thread
By:
Advanced…
H

Homeboy76

Senior Member
Aug 24, 2012
3,692
2,175
Google Pixel XL
Google Pixel 7 Pro
Gruber008 said:
Is it alright if I use stable Magisk on my 7 Pro?
I mean, everything is working so I'm confused why's everyone suggesting to use canary version of Magisk.
If it's necessary to use canary, what's the easiest way to switch from stable to canary, do I need to re-flash init_boot?

Thanks in advance!
Click to expand...
Click to collapse
Yes, it is alright if you use the stable version of the Magisk app.

Usually, when people write about changing their Magisk app version. They explain why they are changing it. If the explanation they provide is not something you need to do.

"If it ain't broke don't fix it"

The instructions in the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~..., 6. Set Magisk App Update Channel/Update Magisk, • Set Magisk App Update Channel is the easiest way to change versions of the Magisk app.

If you lose root after changing the Magisk app version: Patch the init_boot.img with the new magisk app and flash it.
fastboot flash init_boot magisk_patched...img
 
  • Like
Reactions: Gruber008
Elastep

Elastep

Senior Member
Feb 7, 2010
244
68
Ashburn
Samsung Galaxy Note 20 Ultra
Google Pixel 7 Pro
Guys, I've reset my phone to stock and relocked the bootloader. Now getting this.. How do I reset everything back? Or am I fully bricked now?
IMG_5410.jpeg
 
Elastep

Elastep

Senior Member
Feb 7, 2010
244
68
Ashburn
Samsung Galaxy Note 20 Ultra
Google Pixel 7 Pro
EtherealRemnant said:
fastboot getvar current-slot

fastboot --set-active=a or b (whichever isn't currently active)

It is unlikely to work though. You clearly had something modified that shouldn't have been.
Click to expand...
Click to collapse
FAILED (remote: 'command (set_active:) is not allowed when locked')
No luck :)
Google said that the fix is going to be free.. Will try some local Asurion guys first, but I doubt. Then probably will have to send it to google...
 
EtherealRemnant

EtherealRemnant

Senior Member
Sep 15, 2007
5,033
2,183
38
Denver, CO
OnePlus 9
Samsung Galaxy Watch 4
Elastep said:
FAILED (remote: 'command (set_active:) is not allowed when locked')
No luck :)
Google said that the fix is going to be free.. Will try some local Asurion guys first, but I doubt. Then probably will have to send it to google...
Click to expand...
Click to collapse
Well it's good that Google is going to take care of you. You must have bought it directly from the Google Store. I've heard nothing but problems for people trying to get warranty service that bought it anywhere else (which means it's a good thing that I only keep my phone for a year as I bought it from Best Buy).
 
Elastep

Elastep

Senior Member
Feb 7, 2010
244
68
Ashburn
Samsung Galaxy Note 20 Ultra
Google Pixel 7 Pro
EtherealRemnant said:
Well it's good that Google is going to take care of you. You must have bought it directly from the Google Store. I've heard nothing but problems for people trying to get warranty service that bought it anywhere else (which means it's a good thing that I only keep my phone for a year as I bought it from Best Buy).
Click to expand...
Click to collapse
Yes, bought it from Google Store directly...
Never had a phone before (and I had a lot of phones) that I could not somehow reset to factory. settings...
This is clearly some underthought.
 
EtherealRemnant

EtherealRemnant

Senior Member
Sep 15, 2007
5,033
2,183
38
Denver, CO
OnePlus 9
Samsung Galaxy Watch 4
Elastep said:
Yes, bought it from Google Store directly...
Never had a phone before (and I had a lot of phones) that I could not somehow reset to factory. settings...
This is clearly some underthought.
Click to expand...
Click to collapse
You needed to use the Android Flash Tool. Android Verified Boot 2 will brick if you have made any modifications to system partitions and re-lock the bootloader. This goes for any phone, just some have low level tools like MSM and Odin that will allow you to recover from the brick. AFT would have restored full stock software and re-locked it for you. Your mistake is re-locking the bootloader manually. Nobody should ever be doing this if they don't want to risk a brick.
 
Last edited:
Elastep

Elastep

Senior Member
Feb 7, 2010
244
68
Ashburn
Samsung Galaxy Note 20 Ultra
Google Pixel 7 Pro
EtherealRemnant said:
You needed to use the Android Flash Tool. Android Verified Boot 2 will brick if you have made any modifications to system partitions and re-lock the bootloader. This goes for any phone, just some have low level tools like MSM and Odin that will allow you to recover from the brick. AFT would have restored full stock software and re-locked it for you. Your mistake is re-locking the bootloader manually. Nobody should ever be doing this if they don't want to risk a brick.
Click to expand...
Click to collapse
Yes, it’s clear now.. I was under the impression that I can always use some tool like Odin as you’ve mentioned.. I wonder if Google has some secret low level tool as well…
 
You must log in or register to reply here.

Similar threads

roirraW "edor" ehT
How To Guide March 13, 2023 TQ2A.230305.008.C1 Global | .A3 WINDTRE/Canada - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Replies
2K
Views
151K
bluegrass55
bluegrass55
Freak07
Development [Kernel][23.03.2023][Android 13.0.0 Stable]Kirisakura_Raviantah 1.0.1 for Pixel 7/Pro aka "Pantah"
Replies
1K
Views
107K
terlynn4
terlynn4
N
Development [ROM][UNOFFICIAL][cheetah/panther] LineageOS 20.0 for the Pixel 7 Pro/7
Replies
289
Views
38K
i42o
i42o
badabing2003
Themes / Apps / Mods 📳🔥PixelFlasher for Google Pixel 7 Pro Support Thread.
Replies
641
Views
40K
badabing2003
badabing2003
roirraW "edor" ehT
General March 15, 2023 QPR3 Beta 1 T3B1.230224.005 - Pixel 7 Pro [Cheetah] - [thread also for future Android QPR Betas]
Replies
418
Views
48K
D
dd805bb

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 4
    badabing2003
    badabing2003
    cmh714 said:
    209 was working just fine for me....
    Click to expand...
    Click to collapse

    supermansaga said:
    That's why I am a bit hesitant to unreroot and reroot to 25206, though I am dying to enable 5g again for China telecom.
    Click to expand...
    Click to collapse
    Depends on how you're applying.
    Direct install works, but patching stock boot and applying that (ie dirty flashing) which you would do with March release (when it comes out), you lose root.
    Hopefully by then 25211 will be out, otherwise I advise you to either install the stable version or 25206.
    View
    3
    H
    Homeboy76
    gpvecchi said:
    I suggest to add the guide to disable verify and verification in the first post, I didn't do this, and now I need another full wipe to install a custom kernel.
    Click to expand...
    Click to collapse
    You must be a mind reader, I was in the process of adding Disabling Verity and Verification to the OP. :)

    It has been added to the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~..., 2. Install/Update Factory Image keep data, wipe data...

    However, flashing the stock factory image does not require Disabling Verity and Verification. Therefore, I also edited the Disclaimer. :)
    View
    3
    D
    dd805bb
    KernelSU is also another way to root our phones now, FYI.. They have a manager now and module support. You can run modules like magisk but is buggy. Just another way. Zygisk for KernelSU allows you to install Zygisk modules like safetynet fix and lsposed. Systemless hosts module it is lacking.

    GitHub - tiann/KernelSU: A Kernel based root solution for Android

    A Kernel based root solution for Android...
    github.com github.com

    Just another way to root or use both Magisk/KernelSU.
    View
    3
    H
    Homeboy76
    SDK Platform-tools
    Several members of the XDA community have
    written posts that SDK Platform-tools r34.0.1 is broken. Problem: fastbootd not working

    Use SDK Platform-tools r33.0.3: https://forum.xda-developers.com/t/...der-pass-safetynet-more.4505353/post-88261723
    View
    3
    H
    Homeboy76
    Magisk Canary
    These versions of Magisk Canary are all broken: 25207, 25208, 25209, and 25210.

    The last working Magisk Canary 25206 - app-release.apk can be downloaded here.
    View
  • 28
    H
    Homeboy76
    [Guide] Root Pixel 7 Pro with Magisk + Unlock Bootloader + Pass SafetyNet + More
    Android Security Bulletin—March 2023
    Pixel Update Bulletin—March 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. Update(s)

      • Factory/OTA Images - 13 Mar
      • Magisk Alpha - app-release_555a54ec-alpha.apk 2 Sep
      • Magisk Beta - 25.2 21Jul
      • Magisk Canary
        Note: Magisk Canary 25207, 25208, 25209 (some devices), and 25210 are broken.
        - Use Magisk Canary 25206
        - Tap the 3 dot menu across from 5b2934603f => Tap Go to file =>
        Tap app-release.apk => Tap the 3 dot menu across from 10.9 MB => Tap Download
      • Magisk Cygisk - Click Pages 5 for installation Instructions.
      • Magisk Delta -
        app-release
      • Magisk Stable - 25.2 21Jul
      • TWRP - Waiting for T.W.R.P. for Android 13
      • SafetyNet - kdrag0n safetynet-fix-v2.4.0.zip 09Jan
        This version only supports Zygisk (Magisk 24 and newer).
      • SDK Platform-tools - r33.0.3 Aug 2022
      • Custom Kernels
    4. NEW

      • "...make a 100% clean install of ANY Magisk version or fork without PC or TWRP."

        Magisk General Support / Discussion

        This is the place for general support and...
        forum.xda-developers.com forum.xda-developers.com
      • Android 14 Beta are up.
        Builds are only available for the following Pixel devices:

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

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

          • Google Pixel 4a and 4a (5G)
          • Google Pixel 5 and 5a
          • Google Pixel 6 and 6 Pro
          • Google Pixel 6a
          • Google Pixel 7 and 7 Pro
    5. My Other Guides
    6. Credits/Thanks/Recognitions

      • @topjohnwu - Magisk.
      • @Lughnasadh - for his many helpful contributions to this thread.
      • @badabing2003 - for Pixel Flasher and for his many helpful contributions to this thread.
      • 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. Install/Update Factory Image keep data, wipe data, or use @badabing2003 PixelFlashers

      • Important Note(s):
        1. If the previous factory image was rooted (you used Magisk to patch the init_boot.img of the previous factory image). Open Magisk manager and disable all Magisk modules.
        2. Always verify you have the latest version of SDK Platform-Tools installed on your computer.
        3. 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.
        4. If you phone bootloops
          • Press the Power button until the phone turns off.
          • Press the Power and Volume Down to boot the bootloader.
          • Open a Command Prompt in the SDK-Platform-tools folder or the folder that has adb.exe in it, and type adb wait-for-device shell magisk --remove-modules
          • fastboot Reboot
        5. Backup your data
        6. Download the latest Factory Image: Pixel 7 Pro - cheetah to your Computer.
        7. 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 to 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 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 both slots (A & B partitions) see Flash Other Slot bat file... above.
          * * * * E N D - Edit * * * *
        • Open the folder you extracted the Factory Image to and Copy/Move these files to the Platform-tools folder:
          1. bootloader-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 => 5. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
      • Use PixelFlasher by @badabing2003
    3. Take the OTA Update and Maintain Root

      • XDA member @S8rooted&tooted does this to Take the OTA Update and Maintain Root

        ...I don't untick auto updates and restart it on the update screen.
        Steps I do
        I see the update notification
        I uninstall Magisk, just restore images
        Go to update screen and let it fully update
        Once the restart button is there on update screen,
        I head over to magisk install to inactive slot,
        After that is done go back to update screen and restart it there via bottom restart button...
    4. Extract the flash-all.bat and the init_boot.img 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.
    5. Root/Reroot with Magisk and Pass SafetyNet.

      • Android 13

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

        1. Go to Part II - INSTRUCTIONS => 4. Extract files from the FactoryImage/Flash init_boot.img or edit flash-all.bat file.
        2. Install Magisk Canary - Download app-release.apk
          or
          Magisk Beta/Stable App
        3. Open Magisk Beta/Canary/Stable App
        4. The Update Channel should be set to Beta/Canary/Stable, depending on the version you Installed.
        5. Tap Install (next to Magisk)
        6. Tap, Select and Patch a File
        7. Select the init_boot.img file you extracted from the latest factory image.
        8. Tap the ✓ (Check Mark)
        9. Tap Let's Go
        10. When you see done, the init_boot.img has been patched (magisk_patched_xxxxxx.img), and is stored in the download folder.
        11. 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:
          • Copy it to a USB drive and transfer it to your computer.
          • Move it to your computer using adb push
        13. Boot fastboot mode
        14. Connect the phone to the Computer with USB cord.
        15. Open a Command Prompt in the folder you copied the patched boot.img to.
        16. Type fastboot flash init_boot magic_patched....img at the Prompt and press enter.
        17. Type fastboot reboot at the Prompt and press enter.
        18. Important, if your phone boot loops try one of the following options:
          • Flash the 'stock' init_boot.img to both slots: fastboot flash init_boot --slot all init_boot.img
          • Remove Modules
            1. Press the Power button until the phone turns off.
            2. Press the Power and Volume Down to boot the bootloader.
            3. Open a Command Prompt in the SDK-Platform-tools folder or the folder that has adb.exe in it, and type adb wait-for-device shell magisk --remove-modules
            4. fastboot Reboot.
        19. Important, if the Magisk Manager app has the Superuser and Module buttons greyed out:
      • Pass Safety Net with SafetyNet Fix

        1. Download File(s)
        2. Install kdrag0n or Displax's safetyNet Fix
          • Open Magisk
          • Tap Modules icon
          • Tap Install from storage
          • Navigate to the kdrag0n SafetyNet Fix or Displax's SafetyNet Fix file you downloaded.
          • Tap the kdrag0n SafetyNet Fix or 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.
          • Scroll down to Superuser and enable Enable Biometric Authentication.
        4. Get Device Certified Clear Google Play Store, Google Play Services, Google Pay, Google Wallet, etc. data[/B]
          • Turn Airplane mode on
          • Open Settings
          • Tap Apps & notifications
          • Tap see all...
          • Tap three dot menu
          • Tap Show system
          • Scroll down to Google Play Store
          • Tap Storage & Cache
          • Tap Clear storage
            Note: Repeat the 3 steps above for Google Play Services, Google Pay, Google Wallet, etc.
          • reboot
          • Turn Airplane mode off
        5. Check Device Certification, It may take 24 hours for Device Certification
          • Open Google Play Store app
          • Tap Menu - Circle top right
          • Tap Settings
          • Tap About
          • Check Play protect certification.
    6. Set Magisk App Update Channel/Update Magisk

      • Set Magisk App Update Channel

        • Open Magisk App > Tap Settings icon > Update Channel > Select Stable, Beta, Canary or Custom.
      • Update Magisk

        1. When Magisk App notifies you of an update:
        2. Tap install.
        3. Select, Direct Install (Recommended)
        4. When it finishes installing
        5. Tap, Save Log
        6. Log location: /storage/emulated/0/Download
        7. Tap, Reboot
        8. Done!
    7. Install/Update Magisk Modules

      • Download Modules
      • Install Modules from Storage

        1. Open Magisk
        2. Tap the Modules icon
        3. Tap Install from storage
        4. Navigate to the folder with the Module you want to install.
        5. Tap the Module to highlite it and tap Select.
        6. After it installs, tap the Disc Icon to save the install log.
        7. Tap Reboot
      • Install Modules from Fox2Code/Fox Magisk Module Manager

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

        1. Open Fox2Code/Fox Magisk Module Manager
        2. You, will see the Modules that have Updates.
        3. Tap the Module you want to update.
        4. Tap install.
        5. After it installs, tap the Disc Icon to save the install log.
        6. Tap Reboot
    8. Open a Command Prompt/Boot Fastboot Mode/Boot Recovery

      • Open a Command Prompt on Computer
        1. Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type cmd and press enter.
        2. Open a Powershell Command Prompt on Computer: Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type powershell and press enter.
        3. Notes:
          • Enable USB Debugging, on your phone: Settings ==> System ==> Advanced ==> Developer options ==> Scroll down to USB debugging and enable it.
          • When using the Powershell Command Prompt Commands must be preceeded with ./: i.e, ./fastboot devices
          • If you do not want to open a Command Prompt every time you want to use the fastboot command, add the path to the Platform-tools folder to Windows environment variables.
      • Boot fastboot mode (bootloader):
        • Power off phone, press and hold the power and volume down buttons until you see Start.
      • Boot Recovery
        • Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.
    9. Test fastboot

      • Enable Developer Options - Tap Settings > About phone > Build number 7 times or until you should see 'you are a Developer'.
      • Enable USB Debugging - Tap Settings > System > Advanced > Developer options >
        Enable USB Debugging.
      • Open a Command Prompt on your computer in the Platform-tools folder.
      • Boot fastboot mode on your phone
      • Connect the phone to the Computer.
      • At the prompt type: fastboot devices to verify communication with phone. It should return your phone's serial number.
    10. ADB Sideload

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

      • Need help with a Custom ROM?

        1. If you are you are trying to install or have installed a Custom ROM, read and follow the Installation Instructions in the OP of the Custom ROM thread.
        2. Search the thread of the Custom ROM you are trying to install or have installed for answer(s)/solution(s) to your question(s)/problem(s): If you don't find a answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM thread you are trying to install or have installed.
        3. If you are trying to install a Addon(s) {Custom Kernel, Magisk, etc.} to the Custom ROM you installed: Search the thread of the Custom ROM you installed or the thread of the Addon you want to add to your Custom ROMfor answer(s)/solution(s) to your question(s)/problem(s). If you don't find an answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM or Addon (Custom Kernel, Magisk, etc.) thread.
      • ROMs
    2. Themes, Apps, and Mods
    3. T.W.R.P. Backup/Restore

      • Waiting for Android 13 T.W.R.P.
    View
    6
    badabing2003
    badabing2003
    foamerman said:
    OK The sdk files that I downloaded are from AUG 2022 version 33.0.3
    adb and fastboot are in Windows C: \Platform-Tools
    Here are the directory contents
    Ok for some reason I can't post the contents of the dir. so adb fastboot files and magisk_patched-25200_OKTza.img are in the Platform-Tools directory. Is that what your asking?
    Click to expand...
    Click to collapse
    I know what your problem is, I'm trying to be helpful here, but I find it that you are either unwilling or unable to provide the information you're being asked.
    If it is the former, then I don't want to waste my time, if it is the latter, perhaps modding is not for you.
    I'm not asking those for my benefit, I'm asking them so that I provide you precise commands and instructions to get this to work.
    Just because you downloaded a specific version of the SDK does not make it that it is being used.
    How many times I have to ask you the provide the output of the where commands
    You say everything is in C:\Platform-Tools directory, yet your screenshot shows that you are not operating in C:\Platform-Tools directory.
    1670157147221.png


    If your need my further assistance, please find a way to supply the information asked of you in this post.
    Apologies if this sounds a bit harsh, put yourself in my shoes.
    View
    5
    Lughnasadh
    Lughnasadh
    schmeggy929 said:
    Ya'll are confusing the heck out of me. Wouldn't 100% be unsuccessful using that link method? As Magisk wants to patch the boot.img and not init_boot.img the Pixel 7 needs?
    Click to expand...
    Click to collapse
    I assume you are talking about updating the Magisk version within the Magisk app (via direct install)? If so, Magisk does have the ability to find and patch the init_boot.img. Support for that was added back in March of last year.

    Add init_boot parition · topjohnwu/[email protected]

    The Magic Mask for Android. Contribute to...
    github.com github.com
    View
    4
    badabing2003
    badabing2003
    Homeboy76 said:
    Ok, can we agree using this method may be the safest method to Return phone to stock:
    Use the Android flash tool: select Wipe => Force Flash Partitions => Lock Bootloader.
    Click to expand...
    Click to collapse
    I would add to it that doing it to both slots assures that the inactive slot does not have anything non stock on it.
    View
    4
    H
    Homeboy76
    Update SafetyNet Net Fix Mod
    https://forum.xda-developers.com/t/...al-safetynet-fix-2-3-1.4217823/post-87198517/

    Displax's SafetyNet Fix Mod: v2.3.1-MOD_2.1
    • Update module.prop
    View

New posts