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

Search This thread

JJT211

Senior Member
Mar 13, 2012
213
28
You should update your instrcutions with the correct command for flashing boot image


Code:
fastboot flash init_boot magisk_patched-25200_Wt9vl.img
 
  • Like
Reactions: Homeboy76

T.A.R.D.I.S.

Senior Member
May 3, 2014
159
81
Google Pixel 7 Pro
Hello
I have a fail on the magisk_patched.img flash :
FAILED (remote: partition (init_boot) not found)

I take the last platform tool (r33.0.3), usb drivers on Android studio, flashing factory firmware as it said on tuto (november one).
So, what am i forgetting please?
 
Hello
I have a fail on the magisk_patched.img flash :
FAILED (remote: partition (init_boot) not found)

I take the last platform tool (r33.0.3), usb drivers on Android studio, flashing factory firmware as it said on tuto (november one).
So, what am i forgetting please?
You need to extract the init_boot.img not the boot.img.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,563
1,841
That's what i try since yesterday, and i don't know why, but i can't change slot with adb or PixelFlasher. I can't flash factory image on the second slot too. That why i try the init_boot_b command.
With init_boot_b command, it the first time it passed.
Your device is in bootloader mode?
What do you get when you issue this command"
Code:
fastboot getvar current-slot

What happens when you do

Code:
fastboot --set-active=other
fastboot reboot bootloader
fastboot getvar current-slot
 

T.A.R.D.I.S.

Senior Member
May 3, 2014
159
81
Google Pixel 7 Pro
My wish is rooting, and i was blocked. With my edit, i find the solution but i think it's not a normal command.
I just write my command to help others members in the same situation 😉
Sorry for my bad english!
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,563
1,841
My wish is rooting, and i was blocked. With my edit, i find the solution but i think it's not a normal command.
I just write my command to help others members in the same situation 😉
Sorry for my bad english!
Thank you for posting your solution.
I'm still curious in learning why / how you were blocked, as that should not have happened.
 

renzgy

Member
Feb 26, 2014
15
6
Google Pixel 7 Pro
Hello, i tried this step patching init_bot.img through magisk app but during patch in magisk its give me error patching failed. Im updated in November build which is 13.0.0 (TD1A.221105.001, Nov 2022).
anyone here who root the device with pixel 7 pro which November update?

UPDATE: @Homeboy76 It's working with magisk canary because of these steps I managed to changed my SKU of my Japan version using the instructions of @HarryShan in converting device.
 
Last edited:
  • Like
Reactions: Homeboy76

foamerman

Senior Member
Sep 1, 2010
414
86
B-town
Hey Guys I've got a question? I'll be getting my 7pro tomorrow from Google I'm hoping it will have the Global version on it. I have a OnePlus 10 pro now that's enough of that. I'm on Verizon I'll be unlocking the bootloader before I put my sim in also. My question is I noticed in the op under Google Pixel Updates there was one for the Global and also one for Verizon. Now I know wants I put my sim in Verizon will fill my phone up what all kinds of crap. OK so do I want to stay with the Global ver. or go with Verizon? O thanks for your help also. This phone will be a new experiences for me. I've been with OnePlus for a long time.

 

Homeboy76

Senior Member
Aug 24, 2012
3,530
2,071
Google Pixel XL
Google Pixel 7 Pro
Hey Guys I've got a question? I'll be getting my 7pro tomorrow from Google I'm hoping it will have the Global version on it. I have a OnePlus 10 pro now that's enough of that. I'm on Verizon I'll be unlocking the bootloader before I put my sim in also. My question is I noticed in the op under Google Pixel Updates there was one for the Global and also one for Verizon. Now I know wants I put my sim in Verizon will fill my phone up what all kinds of crap. OK so do I want to stay with the Global ver. or go with Verizon? O thanks for your help also. This phone will be a new experiences for me. I've been with OnePlus for a long time.

Your carrier is Verizon so use the Verizon factory/ota image if it is available. If it is not available use the Global factory/ota image.
 
Hey Guys I've got a question? I'll be getting my 7pro tomorrow from Google I'm hoping it will have the Global version on it. I have a OnePlus 10 pro now that's enough of that. I'm on Verizon I'll be unlocking the bootloader before I put my sim in also. My question is I noticed in the op under Google Pixel Updates there was one for the Global and also one for Verizon. Now I know wants I put my sim in Verizon will fill my phone up what all kinds of crap. OK so do I want to stay with the Global ver. or go with Verizon? O thanks for your help also. This phone will be a new experiences for me. I've been with OnePlus for a long time.

I understand you are putting your phone on the Verizon network, but did you purchase your phone from Verizon? Or did you purchase it from Google, Amazon, Swappa, or any other third-party site -- anything outside of any carriers? Because if you did purchase it through Verizon (or any carrier), it won't matter whether you put the sim before or after unlocking the bootloader, most likely you will not be able to unlock the bootloader because the OEM unlock toggle will be greyed out and unable to switch -- without the switch you would not be able to unlock the bootloader successfully...

Your carrier is Verizon so use the Verizon factory/ota image if it is available. If it is not available use the Global factory/ota image.
If you are on Verizon's cell line, it would be best to use their factory/ota image as it has certain "tweaks" for the Pixel 7 Pro & their network; if not, using the Global factory/ota image works just as well -- even if you did load Verizon's factory/ota image on a device that isn't on their line, the images are comparable and either would be safe to use; it's just as matter of having one that would have said "tweaks" applied for Verizon's line or not...
 

Homeboy76

Senior Member
Aug 24, 2012
3,530
2,071
Google Pixel XL
Google Pixel 7 Pro
I understand you are putting your phone on the Verizon network, but did you purchase your phone from Verizon? Or did you purchase it from Google, Amazon, Swappa, or any other third-party site -- anything outside of any carriers? Because if you did purchase it through Verizon (or any carrier), it won't matter whether you put the sim before or after unlocking the bootloader, most likely you will not be able to unlock the bootloader because the OEM unlock toggle will be greyed out and unable to switch -- without the switch you would not be able to unlock the bootloader successfully...


If you are on Verizon's cell line, it would be best to use their factory/ota image as it has certain "tweaks" for the Pixel 7 Pro & their network; if not, using the Global factory/ota image works just as well -- even if you did load Verizon's factory/ota image on a device that isn't on their line, the images are comparable and either would be safe to use; it's just as matter of having one that would have said "tweaks" applied for Verizon's line or not...
Please read the post before you reply:
foamerman said:
...I'll be getting my 7pro tomorrow from Google I'm hoping it will have the Global version on it...

Homeboy76 said
"Your carrier is Verizon so use the Verizon factory/ota image if it is available. If it is not available use the Global factory/ota image."

Sometime, there is no Verizon monthly factory/ota image posted or it is posted after the Global factory/ota image is posted.

Thank you for explaining the reason one should use the Verizon factory/ota image if their carrier is Verizon.
 
Last edited:
  • Haha
Reactions: Slim2none4u

Homeboy76

Senior Member
Aug 24, 2012
3,530
2,071
Google Pixel XL
Google Pixel 7 Pro
I have a Google phone on Verizon and I have never put the Verizon update on it. I'm afraid that it will come with all their crapware.
Some other people feel the same way. :)

The bottom line, it's your phone you decide which factory/ota image you want to use.

My point in post #35 and #37 was you can use the Global or Verizon factory/ota image if your carrier is Verizon.

You have confirmed my point.
 
  • Like
Reactions: madmuthertrucker

jake.99x3

Senior Member
Jul 7, 2013
371
86
Richmond
Requested a temporary SIM unlock from T-Mobile; explained that I was traveling out of country and that past pixels had come unlocked ;p . My request was granted and I was given a 30 day SIM unlock for my Pixel 7 pro. System -> Developer Options -> OEM unlocking is greyed out with the message "Connect to the internet or contact your carrier". I did a little more searching and other users mentioned this going away 3 days after connecting to mobile data/wifi; Hopefully this is the case for my pixel haha
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    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?
    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.

    3
    I fixed the links, thanks.

    Yeah, that's why that particular set of instructions has a strick through more people are unsuccecessful using this method to install to the Inactive Slot.
    Only thing I do differently is 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.
    It worked on stock, then I went to android beta, it worked. That was December I jumped back on beta. Then January update did the same way to update.
    2
    Ah, ok. There have been a few people (that I have seen) on the Pixel 7 series who have been successful using that method, but most have not. There are 2 Github issues opened related to this issue. The devs couldn't find any problems with the script and no one has provided a log so they can look into it more. Until logs are provided, they can't work on a fix or figure out why some are successful while most are not.


    Ok thanks, so I wasn't going crazy lol
    2
    Updated OP
    ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~
    3. Take the OTA Update and Maintain Root
  • 21
    [Guide] Root Pixel 7 Pro with Magisk + Unlock Bootloader + Pass SafetyNet + More
    Android Security Bulletin—January 2023
    Pixel Update Bulletin—January 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.
      • 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 an item.
    2. Prerequisites

    3. Update(s)

      • Factory/OTA Images - 3 Jan
      • Magisk Alpha - app-release_555a54ec-alpha.apk 2 Sep
      • Magisk Beta - 25.2 21Jul
      • Magisk Canary - app-release_831a398b -25206.apk 26Dec
      • 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 11Aug
      • Custom Kernels
        Note: If you are using a Custom Kernel, please update using the method in the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, Install/Update Factory Image keep data or wipe data, • Flash Factory Image Keep Data
    4. NEW

      • The QRP2 Beta Factory/OTA images are up for:

        1. Pixel 4a and 4a (5G)
        2. Pixel 5 and 5a
        3. Pixel 6 and 6 Pro
        4. Pixel 6a
        5. Pixel 7 and 7 Pro

        There are also 64-bit QRP2 Beta Factory images:

        1. Pixel 4a (5G)
        2. Pixel 5
        3. Pixel 6
        4. Pixel 6 Pro
    5. My Other Guides
    6. Credits/Thanks/Recognitions

      • @topjohnwu - Magisk.
      • @Lughnasadh - for his many contributions to this thread
      • vvb2060 - Magisk alpha.
      • 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 files from the FactoryImage/Flash the init_boot.img or edit the flash-all.bat file.
      • Flash Factory Image Keep Data

        • If you are Upgrading to Android 13 or Updating Android 13. Open the folder you extracted the Factory Image to and edit the flash-all.bat file with a text editor i.e., DroidEdit app (See Bold items below).

          Upgrade To Android 13 (First Time Install) Note: This installs the Factory image to both slots
          * * * S T A R T - E D I T * * *
          @Echo off
          PATH=%PATH%;"%SYSTEMROOT%\System32"
          fastboot flash bootloader bootloader-cheetah-aaaaaa-9.9-9999999.img --slot all
          fastboot reboot-bootloader
          timeout /t 5 >nul
          fastboot flash radio radio-cheetah-a9999a-999999-999999-a-9999999.img --slot all
          fastboot reboot-bootloader
          timeout /t 5 >nul
          fastboot -- skip-reboot update image-cheetah-aa9a.999999.999.zip
          Note: I replaced the -w with -- skip-reboot to Keep Data.
          fastboot reboot-bootloader
          timeout /t 5 >nul
          fastboot --set-active=other
          timeout /t 10 >nul
          fastboot reboot-bootloader
          timeout /t 5 >nul

          fastboot update image-cheetah-aa9a.999999.999.zip
          echo Press any key to exit...
          pause >nul
          exit
          * * * * E N D - Edit * * * *
          Update Android 13 Note: This installs the Factory image to the other slot
          * * * S T A R T - E D I T * * *
          @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
          timeout /t 5 >nul
          fastboot flash radio radio-cheetah-a99999-999999-999999-a-9999999.img
          fastboot reboot-bootloader
          timeout /t 5 >nul
          fastboot update image-cheetah-aa9a.999999.999.zip
          Note: I removed the -w to Keep Data.
          echo Press any key to exit...
          pause >nul
          exit
          * * * * * * E N D * * * * * *
        • 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 Internal Storage.
        • Do not edit the flash-all.bat file.
        • 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 files from the FactoryImage/Flash init_boot.img or edit flash-all.bat file.

      • Extract Files from Factory Image

        1. Extract flash-all.bat and init_boot.img files
        2. Download the latest Factory image to your phone.
        3. 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.
        4. 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.
      • Flash init_boot.img

        1. Flashing the init_boot.img removes root.
        2. Open the folder you extracted the 'image...zip' file to and copy the init_boot.img file to your computer's platform-tools folder or to the folder that has fastboot.exe in it.
        3. Boot fastboot mode
        4. Connect the phone to the Computer
        5. Open a Command Prompt and type the following command at the prompt:
          fastboot flash boot --slot all init_boot.img
        6. Reboot
    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 boot init_boot.img --slot all
          • 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 safetynet-fix-v2.4.0.zip
          • Open Magisk
          • Tap Modules icon
          • Tap Install from storage
          • Navigate to the kdrag0n safetynet-fix-v2.4.0.zip file you downloaded.
          • Tap the kdrag0n safetynet-fix-v2.4.0.zip file.
          • Tap the check mark (✓ at the bottom) to start the installation.
          • Note: You do not have to disable/remove SafetyNet Fix.
          • 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.
    6
    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?
    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.
    5
    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?
    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.

    4
    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.
    I would add to it that doing it to both slots assures that the inactive slot does not have anything non stock on it.
    4
    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