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

[badabing2003]

One more question. I still have November firmware on my phone but want to update it to the newest one from January. Can I flash it to both slots or should I stick to only one?

You can if you want to.
I alternate slots each month, but that's just me.

 

[Homeboy76]

One more question. I still have November firmware on my phone but want to update it to the newest one from January. Can I flash it to both slots or should I stick to only one?

@innit, you can but, my recommendation is you wait for the Feburary Factory image to drop. It should drop in a few days, if not today. While you are waiting for it to drop.

1. If you want to flash it manually
   • Start by getting acquainted with the procedure to flash it to one slot by reading:
     ~ ~ ~ Part II - INFORMATION, 8, 4, and 5.
   • Then flash it to one slot.
2. If you want to flash it using Pixel Flasher
   • Start by getting acquainted with the procedure to flash it using Pixel Flasher by, throughly, reading: The Pixel Flasher OP.

Notes:

1. Flashing to the alternate/other slot each month and flashing to both slots are both good ideas.
2. Edit the flash-all.bat file:
   Updating or Upgrading To Android 13
   * * E D I T - flash-all.bat file * *
   Flash to Other/Inactive Slot....
3. Flash to Inactive/Other slot: Run the edited flash-all.bat file.
4. Flash to Active-Inactive/Both slots: Run the edited flash-all.bat file twice.

 

[Lughnasadh]

One more question. I still have November firmware on my phone but want to update it to the newest one from January. Can I flash it to both slots or should I stick to only one?

Just to add to what @badabing2003 and @Homeboy76 said....

If you have never flashed the firmware to your current inactive slot (i.e. you've always manually flashed to the same slot or have never taken an OTA to update), then you should probably flash to both slots or at least the inactive slot. When your phone is shipped the full firmware/OS is only installed on one slot (slot A, lets assume). Thus, if you have never flashed the firmware to slot B it will not be bootable without doing so. It's a good precaution in case slot A becomes unbootable for some reason.

(For the discussion above I'm assuming it is standard for Google to ship with the firmware/active slot only on slot A. None of my Pixels have ever come with the full firmware/OS installed on slot B to start).

The February security update should be released on February 6 (always the 1st Monday of the month unless there is a holiday, then usually the day (sometimes 2) after the holiday).

 

[badabing2003]

@Lughnasadh
Although I follow that practice, I know on my newer device I won't be able to boot to the other slot no matter what.
See this, but I still do it out of habit.
If we manage to switch slots and pass AVB, then I can modify PF to flash without system_other or receover the original system after booting successfully.

 

[Lughnasadh]

@Lughnasadh
Although I follow that practice, I know on my newer device I won't be able to boot to the other slot no matter what.
See this, but I still do it out of habit.
If we manage to switch slots and pass AVB, then I can modify PF to flash without system_other or receover the original system after booting successfully.

Right. You'd have to flash the firmware to the other slot first before being able to boot that slot, as you mentioned in an earlier, very informative post. But as I understand it, if you got into a bootloop and the device tries to revert to the inactive slot, it would be able to boot into that slot because the firmware had been previously flashed to that slot? Or is this incorrect? Seems I remember (at least I think I do in my old age, lol) some people mentioning that after a bootloop (it has to bootloop 3 times in a row to do this if I remember correctly?) the device reverted to the other slot and was able to boot into that other slot (they noticed they were on an older firmware version afterwards). Maybe when the device does this it does something (AVB related or writes the system_other image?) to make it able to boot to that other slot under these circumstances?

 

[badabing2003]

Right. You'd have to flash the firmware to the other slot first before being able to boot that slot, as you mentioned in an earlier, very informative post. But as I understand it, if you got into a bootloop and the device tries to revert to the inactive slot, it would be able to boot into that slot because the firmware had been previously flashed to that slot? Or is this incorrect? Seems I remember (at least I think I do in my old age, lol) some people mentioning that after a bootloop (it has to bootloop 3 times in a row to do this if I remember correctly?) the device reverted to the other slot and was able to boot into that other slot (they noticed they were on an older firmware version afterwards). Maybe when the device does this it does something (AVB related or writes the system_other image?) to make it able to boot to that other slot under these circumstances?

Just to be clear,
Let's say I'm on A and A is bootable
I flash factory to B
B is bootable and now active.
I never tested forcing B to become unbootable and checking if the system switches to A and boots fine.

My guess is that it won't work for sure, because A's system is overwritten by that fact that I flashed to B.
So I did two different tests
1- Restore a backup of system to A, and switch slot to A (making sure that bootctl reported slot usable), A was still not bootable, the system would try 3 times and eventually mark it unbootable and revert to B
2- I deleted system_other from the factory image before flashing B, B was bootable, and I switched to A, this time A's system was untouched, so I expected it to boot, but it still failed because of AVB (on newer devices) but passed on older Pixel XL

 

[innit]

You can if you want to.
I alternate slots each month, but that's just me.

@badabing2003 @Homeboy76 @Lughnasadh Thanks again for your help. Flashing to both slots with Pixel Flasher went smoothly. Normally I just do a clean install & set up everything from scratch every month but that always takes a lot of time. Now thanks to PF you only need few minutes

 

[15xda]

I'm using the February T-mobile pixel 7 pro image, with magisk 25.2 and universal-safetynet-fix 2.4.0. What I find is that if I just reboot my phone, I pass safetynet. However, after a while I start failing again and have reboot my phone. Has anyone else seen something like this, or does anyone have suggestions? Kind of awkward because payment will suddenly stop working...

 

[crypt0kiddie]

I'm using the February T-mobile pixel 7 pro image, with magisk 25.2 and universal-safetynet-fix 2.4.0. What I find is that if I just reboot my phone, I pass safetynet. However, after a while I start failing again and have reboot my phone. Has anyone else seen something like this, or does anyone have suggestions? Kind of awkward because payment will suddenly stop working...

I'm having a lot of issues with Tap to Pay.

Sometimes when I open "Wallet" it says, "Device doesn't meet security requirements".

If I close wallet and try again, no message and sometimes Tap to Pay will work after that but other times even though no message, it fails to work when I try to pay.

Yesterday Tap to Pay worked fine, today its not working again.

Sometimes rebooting helps, other times not.

Did this on the December update but its WAY WORSE on February.

Somethings broken.

I need to buy a Play Store credit, cant do that either now.

*Update*

Just ran YASNAC, failed Safetynet for sure. CTS profile mismatch..

 

[crypt0kiddie]

I got it working.... The trick was safetynet-fix-v2.4.0-MOD_1.1.zip

MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0

Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...

forum.xda-developers.com

 

[Pbsipher1]

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...

issuing the command adb shell pm disable-user com.qualcomm.qti.uim has worked on OnePlus phones to ungrey oem toggle and root without unlock .bin or sim unlock(not 100% sure about unlock bin it's been a while since I've had a new 1+ to flash can't remember) for sure that I know of from op6 through op9 and nords could a similar one do the same for this device.

 

[supermansaga]

I have a device that has passed the check w/ SEP Mobile, intune company portal, and all that, except as I signed into the Outlook / Edge under company work profile by microsoft, the sign-in process is an endless loop without success. On one screen, there is a red asterisk in front of "Device is healthy." But it won't elaborate. Instead, that screen quickly vanishes. Any clues? Thanks.

 

[simplepinoi177]

I have a device that has passed the check w/ SEP Mobile, intune company portal, and all that, except as I signed into the Outlook / Edge under company work profile by microsoft, the sign-in process is an endless loop without success. On one screen, there is a red asterisk in front of "Device is healthy." But it won't elaborate. Instead, that screen quickly vanishes. Any clues? Thanks.

It is most likely detecting root access. You most likely have to put Outlook, Edge, anything Microsoft, and maybe even some other hidden additional app/setting in the Zygisk DenyList (making sure every sub-entry is ticked in every/all applicable apps/settings) or employ Shamiko. There are other root hiding methods, but they vary with their successes and can particularly work in one way but not others. In the end, there are some apps that just are seemingly impossible to hide root from and they seem to detect even just an unlocked bootloader and will restrict itself. Thems the unfortunate reality and compromise/consequence of having root or custom beyond stock (kernel, ROM, etc.)...

 

[supermansaga]

It is most likely detecting root access. You most likely have to put Outlook, Edge, anything Microsoft, and maybe even some other hidden additional app/setting in the Zygisk DenyList (making sure every sub-entry is ticked in every/all applicable apps/settings) or employ Shamiko. There are other root hiding methods, but they vary with their successes and can particularly work in one way but not others. In the end, there are some apps that just are seemingly impossible to hide root from and they seem to detect even just an unlocked bootloader and will restrict itself. Thems the unfortunate reality and compromise/consequence of having root or custom beyond stock (kernel, ROM, etc.)...

Shamiko has come to the rescue. Many thanks. My final question is now that we have rooted, is there any way to hide apps on P7P? I know the other Android phones have this innate ability, but just not P7P.

 

[mcwups1]

I'm sure it's here somewhere, but when I use "search this thread" it's not specific.

I have T-Mobile (Sprint) as a carrier, but I bought the phone from Google unlocked, not T-Mobile. Do I still use the T-Mobile Factory Image, or Global?

 

[Homeboy76]

I'm sure it's here somewhere, but when I use "search this thread" it's not specific.

I have T-Mobile (Sprint) as a carrier, but I bought the phone from Google unlocked, not T-Mobile. Do I still use the T-Mobile Factory Image, or Global?

T-Mobile

 

[Homeboy76]

SDK Platform-tools r. 33.0.3.

📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.

DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...

forum.xda-developers.com

 

[schmeggy929]

I'm sure it's here somewhere, but when I use "search this thread" it's not specific.

I have T-Mobile (Sprint) as a carrier, but I bought the phone from Google unlocked, not T-Mobile. Do I still use the T-Mobile Factory Image, or Global?

I use the Global version, Carrier firmware is always way behind.

 

[Pbsipher1]

[Guide] Root Pixel 7 Pro with Magisk + Unlock Bootloader + Pass SafetyNet + More
Android Security Bulletin—Febuary 2023
Pixel Update Bulletin—Febuary 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
   
   
   

   • A Pixel 7 Pro phone with an unlockable bootloader.
   • The latest Android 13 Factory or OTA Image: "cheetah" for Pixel 7 Pro
     Factory Image
     
     
     

     a. 13.0.0 (TQ1A.230205.001.A2, Feb 2023, Telstra)​

     b. 13.0.0 (TQ1A.230205.001.D2, Feb 2023, T-Mobile, T-Mobile MVNOs)​

     c. 13.0.0 (TQ1A.230105.002, Jan 2023)​

     d. Which one should I use?​
     
     OTA Image
     
     
     

     a. 13.0.0 (TQ1A.230205.001.A2, Feb 2023, Telstra)​

     b. 13.0.0 (TQ1A.230205.001.D2, Feb 2023, T-Mobile, T-Mobile MVNOs)​

     c. 13.0.0 (TQ1A.230105.002, Jan 2023)​

     d. Which one should I use?​
   • A Computer with the latest SDK Platform-Tools: r33.0.3 installed.
   • Important Notes:
     
     a. Update Platform Tools, regularly, for optimal performance.​
     b. Need Google's USB Drivers for your Pixel Phone?​
3. Update(s)
   
   
   

   • Factory/OTA Images - 6 Feb
   • 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​
     a. Google Pixel 7 Pro ROMs, Kernels, Recoveries, & Other​
     b. ElementalX Kernel Manager​
4. NEW
   
   
   

   • Android 14 Beta for:
     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
   • 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
   
   
   

   • Pixel 6
   • Pixel 5
   • Pixel 4a (5G)
   • Pixel 4 XL
   • Pixel 3 XL
   • Pixel 1 XL
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 errorwhile 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
     
     
     

     • Updating or 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
       timeout /t 5 >nul
       fastboot flash radio radio-cheetah-a9999a-999999-999999-a-9999999.img
       fastboot reboot-bootloader
       timeout /t 5 >nul
       fastboot update image-cheetah-aa9a.999999.999.zip
       Note:The -w to Keep Data.
       echo Press any key to exit...
       pause >nul
       exit
       * * * * E N D - Edit * * * *
     • Updating or Upgrading To Android 13
       * * E D I T - flash-all.bat file * *
       Flash to Other/Inactive Slot.
       @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 - Edit * * * *
     • 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
     
     
     

     • PixelFlasher for Google Pixel 7 Pro Support Thread
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:
         • Read @badabing2003 post
   • Pass Safety Net with SafetyNet Fix
     
     
     

     1. Download File(s)
        • kdrag0n latest SafetyNet Fix
          This version only supports Zygisk (Magisk 24 and newer). If you are having problems passing SafetyNet with kdrag0n Mod[/U], use Displax's latest SafetyNet Fix, a "fork" of kdrag0n safetynet-fix.
        • https://github.com/Fox2Code/Fox Magisk Module Manager
          (This is the new Magisk Module repository.)
     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
     
     
     

     1. Fox Magisk Module Manager Releases
     2. LSposed Releases
     3. Shamiko Releases
   • 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
    
    
    

    • Stock Recovery
      
      
      

      • Full OTA Images for Nexus and Pixel Devices - Updating instructions
    • Custom Recovery TWRP
      
      
      

      • Waiting for Android 13 (R) T.W.R.P

~ ~ ~ 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
     
     
     

     1. Google Pixel 7 Pro ROMs, Kernels, Recoveries, & Other
     2. Other Custom ROMs
        
        GrapheneOS​
2. Themes, Apps, and Mods
   
   
   

   • Google Pixel 7 Pro Themes, Apps, and Mods
3. T.W.R.P. Backup/Restore
   
   
   

   • Waiting for Android 13 T.W.R.P.

hey homeboy76 I have the spectrum variant of the 7 pro on the Verizon network. the phone is not paid off and ive only been on their network less than 30 days came from metro PCs of 16 years. this is my first pixel. I've rooted almost all my phones since 2017 and up until recently have never had to network unlock in order to oem unlock. actually only phones that I needed to do that on ever was one+ devices but had a work around to bypass with a adb shell command. I'm sure there has to be a cmd line shell that can be called just no luck in finding it ..........yet. I did come across a dialer code. *#*#0702#*#* which brings up a menu for ims sim1 sim2 provisioning and policy, esim provisioning and more all of which are editable. kinda like a build.prop editor ui. could there possibly be something in this menu that would allow us to change the ability to unlock oem without carrier unlock. I have attached some screen shots but it's not even close...... to all the options available I can take more screenshots if somehow I found something no one can access but doubt it. I only consider myself a noob, is self taught and only reason I have the knowledge I do have has all been picked from geniuses such as yourself here on XDA. Let me know pls if there could be hope in this device after all . my window to return is coming quick only 7 days thanks buddy

 

[psymsi]

1. 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...

I had a security update required before taking the Feb 2023 OTA update so YMMV, but this did not work for me.

I selected "restore images" from Magisk, then once the update had downloaded, I had to select "Restart" to start the install - no other option. Once installed, it rebooted so couldn't install to inactive slot and lost root.