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

Search This thread
Some people can not read:

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.
geez man....damn....thanks for calling me out on missing TWO WORDS "from Google" as it was rather late...guess it means i must never read every single word of every single post and I guess it means i'm just one of those "some people just can not read" all the time...was just trying to help...
 
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
This isn't a chat room! Stay on topic!
 
geez man....damn....thanks for calling me out on missing TWO WORDS "from Google" as it was rather late...guess it means i must never read every single word of every single post and I guess it means i'm just one of those "some people just can not read" all the time...was just trying to help...
People should be called out when they don't read. What "help" can you offer if you don't read? The help needed was already given.
 
Considering the post is on bootloader unlocking, I am seeing if anybody else has dealt with this issue... I'm also sure there are some members with the T-Mobile pixel who may be interested in this if it works out...
No your post is about maybe getting an unlocked bootloader from a sim unlock. This is a guide not a development forum on tmobile locked bootloader. Now grow up and stop arguing nonsense.
 
  • Like
Reactions: Homeboy76
People should be called out when they don't read. What "help" can you offer if you don't read? The help needed was already given.
It wasn't about not reading...it was a simple mistake of mis-reading due to it being late and simply overlooking two words. I guess you never make any simple mistakes like that.

And some help was already given; I was attempting to give supplementary help in terms of the benefits of running the Verizon image vs. the global one which wasn't discussed. Also, I was just making sure the person knew the difference between the two variants -- in case he might want to stop or reverse the transaction to switch to the variant from Google; albeit this is a simple mistake for bringing up on my part for missing the two words "from google".
I would hope that it would have been productive and just as helpful to point out if that was the case (if not to that person, then to any other user that might be reading here just to learn)....
 
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
I have a new Google unlocked phone, in order to Enable OEM Unlocking you need to have a connection to the internet or cell, otherwise it will remained greyed out.... GL!
 

Homeboy76

Senior Member
Aug 24, 2012
3,530
2,071
Google Pixel XL
Google Pixel 7 Pro
It wasn't about not reading...it was a simple mistake of mis-reading due to it being late and simply overlooking two words. I guess you never make any simple mistakes like that.

And some help was already given; I was attempting to give supplementary help in terms of the benefits of running the Verizon image vs. the global one which wasn't discussed. Also, I was just making sure the person knew the difference between the two variants -- in case he might want to stop or reverse the transaction to switch to the variant from Google; albeit this is a simple mistake for bringing up on my part for missing the two words "from google".
I would hope that it would have been productive and just as helpful to point out if that was the case (if not to that person, then to any other user that might be reading here just to learn)....
I may have called you out for your mis-reading but I also thanked you for your contribution to the question.

All is forgiven: Your mis-reading, my reacting to it. Let's move on, or we all will be making the OT mistake. :ROFLMAO::ROFLMAO::ROFLMAO:
 
Last edited:
  • Like
Reactions: simplepinoi177

jake.99x3

Senior Member
Jul 7, 2013
371
86
Richmond
No your post is about maybe getting an unlocked bootloader from a sim unlock. This is a guide not a development forum on tmobile locked bootloader. Now grow up and stop arguing nonsense.
Yes and in order to follow the guide and unlock the bootloader you need to be SIM unlocked correct? Ironic you desire to reduce clutter from this thread yet you fill it with these nonsensical replies. Somebody woke up on the wrong side of the bed
 

Homeboy76

Senior Member
Aug 24, 2012
3,530
2,071
Google Pixel XL
Google Pixel 7 Pro
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
Sims unlocking means you can change sim card/carriers. It does not mean you can unlock the bootloader OEM unlock your phone.
 
Considering the post is on bootloader unlocking, I am seeing if anybody else has dealt with this issue... I'm also sure there are some members with the T-Mobile pixel who may be interested in this if it works out...

Sims unlocking means you can change sim card/carriers. It does not mean you can unlock the bootloader OEM unlock your phone.
I think in certain cases getting sim unlocked also means being able to unlock the bootloader as well...
I think there might be some misattributing going on here...jake.99x3 might be getting what is capable with AT&T mixed up with T-Mobile (and/or might be mistaken in thinking that AT&T policy applies to T-Mo...)

According to Superguy in the quoted post below...AT&T can have its bootloader unlocked once it is SIM unlocked...it may(probably) isn't that case for T-Mo...
Some more than others. AT&T is unlockable once it's SIM unlocked. T-Mo's requires as server side unlock. On Verizon you're just screwed.

The factory unlocked will be the least hassle if use their financing or are willing to pay up front. Otherwise, you'll have to find other means to unlock AT&T or T-Mo versions.
In any case, according to Superguy, jake.99x3 would have to somehow get T-Mo to unlock it on their "server side"...not simply SIM unlock it...
 
  • Like
Reactions: Homeboy76

Homeboy76

Senior Member
Aug 24, 2012
3,530
2,071
Google Pixel XL
Google Pixel 7 Pro
I think in certain cases getting sim unlocked also means being able to unlock the bootloader as well...
I think there might be some misattributing going on here...jake.99x3 might be getting what is capable with AT&T mixed up with T-Mobile (and/or might be mistaken in thinking that AT&T policy applies to T-Mo...)

According to Superguy in the quoted post below...AT&T can have its bootloader unlocked once it is SIM unlocked...it may(probably) isn't that case for T-Mo...

In any case, according to Superguy, jake.99x3 would have to somehow get T-Mo to unlock it on their "server side"...not simply SIM unlock it...
@Superguy @jake.99x3
One of the Prerequisites of using this Guide is: A Pixel 7 Pro phone with an unlockable bootloader. See OP, ~ ~ ~ Part I - INFORMATION ~ ~ ~ 2. Prerequisites

If you do not have a Pixel 7 Pro with an unlockable bootloader the instructions, in this Guide, to root your Pixel 7 Pro will not work.

So, as @Slim2none4u stated, trying to use this Guide to get your bootloader unlocked is OT.

If you purchased you Pixel 7 Pro from these wireless carriers: AT&T or T-Mobile

The links below explain their policy to get your device/phone unlocked.
Note: Your device/phone must have an unlocked bootloader to root it.
  1. AT&TUnlock your device Requirements
  2. T-Mobile device unlock
 
Last edited:
  • Like
Reactions: Slim2none4u
I just got mine delivered via FedEx from Spectrum and it came already on Android 13, it just updated to the most recent Security Update after setup.
Just wondering if unlock & root is still possible and which of all these steps I would need to follow?
 

Attachments

  • Screenshot_20221130-193739.png
    Screenshot_20221130-193739.png
    140.6 KB · Views: 43
  • Screenshot_20221130-194713.png
    Screenshot_20221130-194713.png
    258.7 KB · Views: 43

Homeboy76

Senior Member
Aug 24, 2012
3,530
2,071
Google Pixel XL
Google Pixel 7 Pro
I just got mine delivered via FedEx from Spectrum and it came already on Android 13, it just updated to the most recent Security Update after setup.
Just wondering if unlock & root is still possible and which of all these steps I would need to follow?
It looks like OEM unlock is greyed out.
That usually means your bootloader is not unlockable. If your bootloader is not unlockable, you cannot root your phone.
 

Homeboy76

Senior Member
Aug 24, 2012
3,530
2,071
Google Pixel XL
Google Pixel 7 Pro
Ya, it's locked until I pay it off then, I guess, they give me an unlock code.
It's a nice, long 2 year contract but thx for the answers, I was hoping it'd still be an option
Before you pay it off, I would call the Carrier that you brought your phone from (Spectrum/Verizon) and ask them will they unlock the bootloader if you pay off the phone.

Why?
First, most (not all) carriers only do a Sim Card unlock. You can check their Unlock Policy via the links below.

Second, if you want to root your phone the bootloader must be Unlocked.
  1. Spectrum Mobile Device Unlocking Policies
  2. Verizon Device Unlocking Policies
 
  • Like
Reactions: Slim2none4u

Gruber008

Senior Member
Jul 17, 2011
326
126
Split
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!
 

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