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

[State.of.mind]

Does anyone know why i'm getting this error after I try to root after December update? "FAILED (remote: partition (init_boot) not found)"

I patched the init_boot img file, and I am on Magisk Canary. Not sure what's going on here.

 

[HipKat]

Guys got a question. I've been at this for a few days now. I'm having trouble getting root.
1 Bootloader is unlocked
2 SDK is updated
3 Used 2-3 usb cables changed usb slots
But I'm still getting error cannot load magisk_patched-25200_OKTza.img also getting FAILED: (remote partition (init_boot) not found)
What the h#ll am I doing wrong?

Try using the Pixelflasher if you're having issues with the manual process.

 

[foamerman]

Try using the Pixelflasher if you're having issues with the manual process.

Thanks. I had the magisk patch file in the wrong path.

 

[dantevn]

If I understand this correctly, rooting my phone disables OTA?

 

[badabing2003]

If I understand this correctly, rooting my phone disables OTA?

No, OTA check still happens, and downloading of the update can happen too and you'd get notifications about it, however installing it would fail.
I suggest you

1. Turn off automatic install in developer options.
2. Disable system update notification in Google Play services.

 

[Fishawy]

Need help rooting my first-ever Pixel, coming from years of OnePlus.

Phone: Pixel 7 Pro 512GB (Australia, network unlocked).
Status: bootloader unlocked (OEM unlocking enabled), and USB debugging also enabled.
Build number: TQ1A.221205.011 (so I downloaded cheetah-tq1a.221205.011-factory-b144b426.zip).
Magisk Version: Both Stable 25.2 (25200) and Canary (25205).
Tools used: Both adb/fastboot commands from OP, and PixelFlasher tool to flash the full firmware with rooting.
Result: Flashing the magisk_patched init_boot is always successful, zero errors.
Problem: Right after booting to system, phone stays on for 20-30 seconds, then automatically reboots to system, and repeats endlessly.

Tried that more than 20 times now, no success. Only thing I can do with the next reboot is quickly open the Magisk app and uninstall Magisk --> Restore image.

What am I doing wrong? I tried falshing to both slots, no difference. I tried placing the magisk_patched file in C:\platform-tools, and also putting the firmware and the platform tools at the same path. I've also read something about a "wrong path" but not sure what the right one is.

Any help is truly appreciated.

EDIT: Finally figured it out. Not sure how or why, but the "Magisk Bootloop Protector" module was automatically being installed after flashing the patched init_boot, and it looped indefinitely. Removing it stops the bootloop. Is this a known issue with P7P and this module? Do I need to do anything?

 

[Homeboy76]

Need help rooting my first-ever Pixel, coming from years of OnePlus.

Phone: Pixel 7 Pro 512GB (Australia, network unlocked).
Status: bootloader unlocked (OEM unlocking enabled), and USB debugging also enabled.
Build number: TQ1A.221205.011 (so I downloaded cheetah-tq1a.221205.011-factory-b144b426.zip).
Magisk Version: Both Stable 25.2 (25200) and Canary (25205).
Tools used: Both adb/fastboot commands from OP, and PixelFlasher tool to flash the full firmware with rooting.
Result: Flashing the magisk_patched init_boot is always successful, zero errors.
Problem: Right after booting to system, phone stays on for 20-30 seconds, then automatically reboots to system, and repeats endlessly.

Tried that more than 20 times now, no success. Only thing I can do with the next reboot is quickly open the Magisk app and uninstall Magisk --> Restore image.

What am I doing wrong? I tried falshing to both slots, no difference. I tried placing the magisk_patched file in C:\platform-tools, and also putting the firmware and the platform tools at the same path. I've also read something about a "wrong path" but not sure what the right one is.

Any help is truly appreciated.

EDIT: Finally figured it out. Not sure how or why, but the "Magisk Bootloop Protector" module was automatically being installed after flashing the patched init_boot, and it looped indefinitely. Removing it stops the bootloop. Is this a known issue with P7P and this module? Do I need to do anything?

Did you use Magisk Delta to patch the init_boot.img?

Why?

AFAIK Magisk Delta is the only version ot Magisk that has Magisk Bootloop Protector "in it".

I've used both Magisk Version: Stable 25.2 and Canary (25205) to patch the init_boot.img.

There are no preinstalled modules in either of them.

 

[Fishawy]

Did you use Magisk Delta to patch the init_boot.img?

Why?

AFAIK Magisk Delta is the only version ot Magisk that has Magisk Bootloop Protector "in it".

I've used both Magisk Version: Stable 25.2 and Canary (25205) to patch the init_boot.img.

There are no preinstalled modules in either of them.

Weird, never used Delta, but the module is automatically installed after using both Stable and Canary.

 

[Homeboy76]

Weird, never used Delta, but the module is automatically installed after using both Stable and Canary.

@Fishawy
Your assessment of the situation is correct it is "weird".
Hopefully, @badabing2003 can provide some information about the Magisk bootloop protector bootloop problem.

 

[badabing2003]

@Fishawy
Your assessment of the situation is correct it is "weird".
Hopefully, @badabing2003 can provide some information about the Magisk bootloop protector bootloop problem.

If @Fishawy provides a support.zip file I can see what is going on.
PF does not install any modules.
But I wouldn't be able to tell what else manually is performed outside of PF.

 

[Fishawy]

If @Fishawy provides a support.zip file I can see what is going on.
PF does not install any modules.
But I wouldn't be able to tell what else manually is performed outside of PF.

You are correct. It happened with adb/fastboot as well, so it's not directly PF-related.

I panicked because it's my first Pixel ever and I thought I was doing something wrong. I've removed the module for now, and will be resorting to manually booting to safe mode in case of a bootloop.

 

[Homeboy76]

You are correct. It happened with adb/fastboot as well, so it's not directly PF-related.

I panicked because it's my first Pixel ever and I thought I was doing something wrong. I've removed the module for now, and will be resorting to manually booting to safe mode in case of a bootloop.

Did you download Magisk Beta, Canary or Stable from the links below?

The links below are the only official download links for downloading Magisk.

1. Magisk Canary (25205)
2. Magisk Beta 25.2 or Magisk Stable 25.2

 

[Fishawy]

Did you download Magisk Beta, Canary or Stable from the links below?

The links below are the only official download links for downloading Magisk.

1. Magisk Canary (25205)
2. Magisk Beta 25.2 or Magisk Stable 25.2

Yes, always those links.

I saw another post on the forum today having the same issue I had, so guess I'm not alone in this.

 

[badabing2003]

Yes, always those links.

I saw another post on the forum today having the same issue I had, so guess I'm not alone in this.

I think you're talking about this.
We don't know yet if it is the same issue (the user has not responded), similar symptoms does not mean the same issue.
Magisk stable has not been updated since July, same with the beta
And Magisk canary I've been using 25205 ever since it came out, and I would have noticed, and even if I didn't many others use it too.

You want to confirm that this is the case, uninstall Magisk, make sure the suspect module is not there, and then install Magisk from PF, choose stable or Canary and see if bootloop protector magically shows up.
PF installs Magisk from the official source.
Any other source should not be trusted.

 

[Fishawy]

I think you're talking about this.
We don't know yet if it is the same issue (the user has not responded), similar symptoms does not mean the same issue.
Magisk stable has not been updated since July, same with the beta
And Magisk canary I've been using 25205 ever since it came out, and I would have noticed, and even if I didn't many others use it too.

You want to confirm that this is the case, uninstall Magisk, make sure the suspect module is not there, and then install Magisk from PF, choose stable or Canary and see if bootloop protector magically shows up.
PF installs Magisk from the official source.
Any other source should not be trusted.

Thanks for that. I'll give it a go and see.

 

[kevinxjen]

will it break HDR10 compliance?

 

[Homeboy76]

New
The Developer Preview QRP2 Beta Factory/OTA image links are in the OP, Part I, NEW.

 

[dd805bb]

New
The Developer Preview QRP2 Beta Factory/OTA image links are in the OP, Part I, NEW.

I wasn't passing safetynet on DP beta, CTS failed, basic integrity passing. I was using the safetynet fix on here. I uninstalled it and tried kdragon OG one. It worked, both CTS and basic integrity passing now. Weird that it's that way. Thought I would share. May just be my phone or whatever.

 

[Homeboy76]

I wasn't passing safetynet on DP beta, CTS failed, basic integrity passing. I was using the safetynet fix on here. I uninstalled it and tried kdragon OG one. It worked, both CTS and basic integrity passing now. Weird that it's that way. Thought I would share. May just be my phone or whatever.

Thanks, that is good news.
I just want to confirm I read your post correctly that the only SafetyNet Fix needed for Developer Preview QPR2 Beta is kdrag0n's SafetyNet Fix v2.3.1 (Zygisk).

Displax's safetynet-fix-v2.3.1-MOD_2.0.zip is not needed to pass SafetyNet.

 

[franco985]

One question: once I am on a rooted p7p and I have OTA notification, how to keep root installing OTA? thank you in advance