How To Guide [Guide] [January 3, 2024] Root Pixel 7 Pro Unlock Bootloader + Pass SafetyNet + Both Slots Bootable + More

[bird333]

Glad you got it working, sorry you had to wipe your phone.

When you wrote" just spent 6 hours to restore the majority of apps which still refused to be grouped in the same way on the home screen."

I don't understand why you can not place an app any where you want it on the Home Screen.
Unless, the grid was changed back to the default App grid setting when you wiped your phone.

When I have a problem with a installed Magisk manager App that is bad, I do the following:

1. Unroot by flashing the unpatched init_boot.img to both slots:
   fastboot flash init_boot --slot all init_boot.ing
2. Remove all Magisk Manager App(s):
   Settings ==> Apps ==> Show all apps
   • Find the Magisk Manager App(s) and delete.
   • If the Magisk App is hidden look for a settings app, this is normally the (default)
     name given to a hidden Magisk Manager App.
   • NOTES:
     1. https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-88230843
     2. If the hidden name of the Magisk App is settings be extremely careful removing it, you do not want to delete your Settings app.
3. Install the Magisk Manager app I want installed.
4. Patch the init_boot.img with the newly installed Magisk Manager app.
5. Flash the newly patched init_boot.img to reroot.

Question: What are the two slots you refer to?

 

[Homeboy76]

Question: What are the two slots you refer to?

The two slots I am referring to are the A and B partitions: Help understanding A/B partitions

 

[bird333]

The two slots I am referring to are the A and B partitions: Help understanding A/B partitions

Thanks for the link.

 

[Homeboy76]

SDK Platform-tools Update
SDK Platform-tools r34.0.0 and r34.0.1 are not working.

 

[Homeboy76]

Magisk Canary
These versions of Magisk Canary are all broken: 25207, 25208, 25209, and 25210.

The last working Magisk Canary 25206 - app-release.apk can be downloaded here.

 

[cmh714]

Magisk Canary
These versions of Magisk Canary are all broken: 25207, 25208, 25209, and 25210.

The last working Magisk Canary 25206 - app-release.apk can be downloaded here.

209 was working just fine for me....

 

[Homeboy76]

SDK Platform-tools
SDK Platform-tools r34.0.1 has been released.
There is a link in the OP, ~ ~ ~ Part I - INFORMATION ~ ~ ~, 2. Prerequisites, • A Computer with the latest SDK...

 

[supermansaga]

209 was working just fine for me....

That's why I am a bit hesitant to unreroot and reroot to 25206, though I am dying to enable 5g again for China telecom.

 

[badabing2003]

209 was working just fine for me....

That's why I am a bit hesitant to unreroot and reroot to 25206, though I am dying to enable 5g again for China telecom.

Depends on how you're applying.
Direct install works, but patching stock boot and applying that (ie dirty flashing) which you would do with March release (when it comes out), you lose root.
Hopefully by then 25211 will be out, otherwise I advise you to either install the stable version or 25206.

 

[gpvecchi]

I'm on the test build and Android 14 DP2, banking apps work but I don't have the certification. I cleaned Play Store and Play Services data...

 

[dd805bb]

I'm on the test build and Android 14 DP2, banking apps work but I don't have the certification. I cleaned Play Store and Play Services data...

https://xdaforums.com/t/march-8-202...-also-for-future-major-android-betas.4550933/

Go to here and check it out. Not passing cts is normal for DP 14 and 13 qpr releases. That isn't a magisk issue but DP 14 known issue.

 

[Homeboy76]

SDK Platform-tools
Several members of the XDA community have
written posts that SDK Platform-tools r34.0.1 is broken. Problem: fastbootd not working

Use SDK Platform-tools r33.0.3: https://xdaforums.com/t/guide-root-...der-pass-safetynet-more.4505353/post-88261723

 

[mochamoo]

Depends on how you're applying.
Direct install works, but patching stock boot and applying that (ie dirty flashing) which you would do with March release (when it comes out), you lose root.
Hopefully by then 25211 will be out, otherwise I advise you to either install the stable version or 25206.

Am on 25209. Dirty flashed the March update. Patched init_boot image via magisk and fastboot flashed it after flashing the update. All good here. Rooted. Adaway works. I thought I might have to go back to 25206 but 25209 is working fine so I am leaving well enough alone for now.

 

[badabing2003]

Am on 25209. Dirty flashed the March update. Patched init_boot image via magisk and fastboot flashed it after flashing the update. All good here. Rooted. Adaway works. I thought I might have to go back to 25206 but 25209 is working fine so I am leaving well enough alone for now.

Thanks,
Suspecting that the issues are device specific, but that's just a guess.

See this discussion.

 

[supermansaga]

Am on 25209. Dirty flashed the March update. Patched init_boot image via magisk and fastboot flashed it after flashing the update. All good here. Rooted. Adaway works. I thought I might have to go back to 25206 but 25209 is working fine so I am leaving well enough alone for now.

Yes. It appears 25209 is still good enough. I just followed this old video at

and updated three of my P7Ps to the March stable build. It's more straightforward now that I get more and more comfortable with the process. And the best news is that my grouped apps based on the same subject/topic on the home screen remain intact.

 

[Homeboy76]

Yes. It appears 25209 is still good enough. I just followed this old video ... and updated three of my P7Ps to the March stable build. It's more straightforward now that I get more and more comfortable with the process. And the best news is that my grouped apps based on the same subject/topic on the home screen remain intact.

People comprehend instructions differently, that is why there are several descriptions of how to do a thing on the INTERNET. I'm ok with people choosing a method of instructions that they can comprehend or that works for them.

 

[mochamoo]

People comprehend instructions differently, that is why there are several descriptions of how to do a thing on the INTERNET. I'm ok with people choosing a method of instructions that they can comprehend or that works for them.

Yeah I prefer downloading the full update file and flashing it via ADB/ fastboot method. No flash tool here. I generally will extract and patch the init_boot.img first so it is ready to go. Maybe I have been lucky but I don't disable modules first either. After the update is fully installed and the device has rebooted - I just drop back down into ADB/ fastboot and flash the patched magisk image. Done. Have been doing it this way for years and don't see a reason to change. I just have to remember to use init_boot now.

 

[synesthete]

Yeah I prefer downloading the full update file and flashing it via ADB/ fastboot method. No flash tool here. I generally will extract and patch the init_boot.img first so it is ready to go. Maybe I have been lucky but I don't disable modules first either. After the update is fully installed and the device has rebooted - I just drop back down into ADB/ fastboot and flash the patched magisk image. Done. Have been doing it this way for years and don't see a reason to change. I just have to remember to use init_boot now.

Yeah I do the same thing. It is so much easier to have the patched img ready to flash right after all of the others.

 

[anthonnyb98]

[Guide] Root Pixel 7 Pro with Magisk + Unlock Bootloader + Pass SafetyNet + More
Android Security Bulletin—March 2023
Pixel Update Bulletin—March 2023​

Introduction
This Guide is for Pixel 7 Pro owners that want to Root their phone, and enjoy the benefits of rooting it. The Guide is divided into three parts: Information, Instructions, and Other.

~ ~ ~ Part I - INFORMATION ~ ~ ~

1. Disclaimer
   
   
   

   • I assume no responsibility for the malfunctioning/bricking of your phone.
   • 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 (TQ2A.230305.008.A3, Mar 2023, WINDTRE/Canada)​

     b. 13.0.0 (TQ2A.230305.008.C1, Mar 2023)​

     d. Which one should I use?​
     
     OTA Image
     
     
     

     a. 13.0.0 (TQ2A.230305.008.A3, Mar 2023, WINDTRE/Canada)​

     b. 13.0.0 (TQ2A.230305.008.C1, Mar 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 - 13 Mar
   • Magisk Alpha - app-release_555a54ec-alpha.apk 2 Sep
   • Magisk Beta - 25.2 21Jul
   • Magisk Canary - app-release_981ccabb-25210.apk BROKEN 06Mar
   • Magisk Delta -
     app-release
   • Magisk Stable - 25.2 21Jul
   • TWRP - Waiting for T.W.R.P. for Android 13
   • SafetyNet - kdrag0n safetynet-fix-v2.4.0.zip 09Jan
     This version only supports Zygisk (Magisk 24 and newer).
   • SDK Platform-tools - r33.0.3 Aug 2022
   • Custom Kernels
     
     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 are up.
     Builds are only available for the following Pixel devices:
     
     
     

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

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

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

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

Hello, I am having this error when trying to flash the init_boot, could you help me to know why?

PS C:\Users\antho\Desktop\Pixel 7 Pro\platform-tools> fastboot flash init_boot "C:\Users\antho\Desktop\Pixel 7 Pro\platform-tools\magisk_patched-25200_4F9Ey.img"
target reported max download size of 261095424 bytes
sending 'init_boot' (8192 KB)...
OKAY [ 0.197s]
writing 'init_boot'...
FAILED (remote: partition (init_boot) not found)
finished. total time: 0.208s

 

[gpvecchi]

Put the patched init_boot in the same folder of fastboot, name it with a simple name, don't use the quotes and the path.