yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] badabing2003:
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.

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.
[Google Pixel 7 Pro] Slim2none4u:
Never just reset your phone and lock the booloader! ALWAYS FLASH FACTORY IMAGE FIRST! Then relock bootloader. For future reference!
[Google Pixel 7 Pro] Elastep:
Yeah :) Thanks. It was in one of the XDA's manuals, and I first did and then thought that I've just killed it :)
[Google Pixel 7 Pro] Winstonshead:
So the head post is wrong? There is no information about flashing factory image
[Google Pixel 7 Pro] EtherealRemnant:
This is exactly why this thread and the other thread not by @roirraW "edor" ehT should be closed because they're incomplete. This one even had the wrong Magisk flashing method for weeks before it was fixed.

Note the instructions here are correct

https://xdaforums.com/t/december-5-...-pro-cheetah-safetynet.4502805/#post-87540341
[Google Pixel 7 Pro] Homeboy76:
The instructions in the OP are not wrong. They are manual instructions for

Unlocking the bootloader/Returning the Phone to Stock/Locking the bootloader

.

The instructions for (manually) flashing the Google Pixel 7 Pro Factory image are in the OP, Part II, 2?
[Google Pixel 7 Pro] Homeboy76:
First, before you post you should read the post you are replying to that would help you give an educated reply not an opinionated reply.

You never answered the members question, gave an unrequested link and gave an unrequested link.

Second, you should read the OP to verify the post you are replying to is correct. The instructions in the OP are not wrong.

Third, @roirraW "edor" ehT doesn't need you to advertise his thread. His work speaks for itself.
[Google Pixel 7 Pro] EtherealRemnant:
The link that I posted goes to the third post in that thread where the instructions are. Click the link before assuming I messed up.

From that link, scrolled past other important resources, there is a section in the same post about how to unroot:

I watched this thread for weeks with the wrong information for how to root when the phone dropped - it used the old boot image patching instead of the new init_boot patching and people were pointing it out and it wasn't being fixed. I don't understand why we need to have three different threads with basically the same info when the moderator thread is the only one that is updated quickly. It just confuses people when the info is out of sync.

I won't argue back and forth with you though, it's a waste of my time. ✌️
[Google Pixel 7 Pro] Homeboy76:
"The link that I posted goes to the third post in

that thread

..."

You are right, that links goes to @roirraW "edor" ehT thread. I apologize.

"From that link, scrolled past other important resources, there is a section in the same post about how to unroot..."

All you have to do to unroot your Pixel 7 Pro phone is flash the init_boot.img to both slots (a and b).

"I watched this thread for weeks with the wrong information for how to root when the phone dropped..."

That is not true, the information how to root is correct.

What is "phone That dropped"?

"- it used the old boot image patching instead of the new init_boot patching and people were pointing it out and it wasn't being fixed."

Not true, no where in this thread will you find instructions to root with a boot.img

"I don't understand why we need to have three different threads with basically the same info when the moderator thread is the only one that is updated quickly. It just confuses people when the info is out of sync."

You are giving your

personal opinon

.

Opinons are like noses, Everybody has one.

If you prefer using @roirraW "edor" ehT thread use it, but

don't bash other threads because of your preferences

.

@roirraW "edor" ehT isn't the only moderator that has written guides for Google Pixel phones.

"I won't argue back and forth with you though, it's a waste of my time."

"Argue"

I'm not arguing with you, I'm correcting the incorrect information you posted in this thread.
[Google Pixel 7 Pro] jake.99x3:
Finally got my T-Mobile Pixel 7 pro bootloader unlocked :p Following this guide for root and everything is going smoothly. I was able to get the OEM Unlock setting toggle-able through the support function of the app incase anybody else runs into this.
[Google Pixel 7 Pro] Winstonshead:
It's looks like complete instructions to go back for stock/locked bootloader.

I think author should correct that part to save some people from bricks
[Google Pixel 7 Pro] Homeboy76:
Are referring to this set of instructions

title

(

Unlock Bootloader

/

Return Phone to Stock

/

Lock Bootloader

)?

You have to click

CLICK TO SHOW CONTENT

to see the instructions for those three things. :)
[Google Pixel 7 Pro] Homeboy76:
"...But yeah...hopefully this helps YOU understand a bit of where the users that are getting confused by your guide are coming from as well as the users that are attempting to clarify things"

It is not

users

you are commenting for it is @EtherealRemnant comments you are trying to defend' "Even though EtherealRemnant didn't wish to clarify""

Three questions:

Did you read my edited post to EtherealRemnant before you posted this?

Did you ever write a post other than this one, identifying any errors in this thread that were not corrected?

I respect your opinion/preference for using the - w to wipe your phone. However, there is more than one wipe a phone. I prefer resetting the phone.

Do you have a problem respecting other opinions that work?

Additionally, I do have a link in this thread for the Pixel Flasher. If you prefer automated flashing.

Further, this code was corrected October 14, 2022:

fastboot flash init_boot magisk_patched...img

The error was reported October 14, 2022 (see post #3).
[Google Pixel 7 Pro] vlucchetti:
Homeboy, ignore them. I've followed your guides through multiple phones over multiple updates and you are the best out there.
[Google Pixel 7 Pro] Homeboy76:
Thanks, I'll do that.
[Google Pixel 7 Pro] badabing2003:
Folks tone it down, honestly, we can have constructive civil conversation that leads to better guides.

Stating that threads should be closed down because they contain errors is not conducive to helping the community.

We all come here seeking information we don't have answers to. Many posts contain golden information, and many other have misleading and at times wrong information.

Sifting through many (too many) such posts and extracting relevant accurate details to solve our issues or find our answers is not an easy task, we all need guides that collate and put these notes in one place in a structured format.

I personally at times have difficulty locating a piece of information that I know exists and I have seen it pass by, but can't easily find it for reference or use.

I have followed @Homeboy76 's guides for many years and used it to keep my phone updated, in fact it is one of the foundational source of information that I used to code up the automated UI tool you all know about.

I wouldn't want these guides to disappear because they contained inaccurate information at one point in time.

This is a community that is based on collaboration and synergy, we can all contribute towards making it better, or we can knock it down and destroy it, which you think would be the better path?

Writing a guide and keeping it up to date, and then trying to cover all possible permutations / branches one could / would take from a rand starting point a to an end point b is endless, and if you think you covered it all, soon you'd be asked how can I do this?

Imagine maintaining multiple guides that constantly evolve. It's not like code where you write a good function and make changes in one place and all the references would be automatically resolved.

@Homeboy76 deserves kudos not scolding, even if he makes mistakes, we all make mistakes.

In any case, we know and accept that modding our devices come with inherent risks, we still have the full responsibility to understand what we're doing, and validate the actions we're taking before acting and bricking our devices and if anything goes bad, it's on us, not the other's advice.

Sorry for my rant, hope we can all see the good in each others contributions.
[Google Pixel 7 Pro] simplepinoi177:
I agree that this, or any other guide, thread should not be closed down. There is a plethora of knowledge & experience in each and every one that everyone would benefit from. As much as it can be confusing or frustrating sifting through the various guides & threads with information all out there and maybe "out of sync", it is still beneficial and worth it and achievable if you know how to go about researching through the threads.

Also, I will say this; kudos should be given to @Homeboy76, for this guide, and for what he has put and continues to put into it. I recognize & respect that there is great value in most (if not all) of his guide and his opinions towards it; far more than anything I have ever said or done on this site.

All this being said, he did not get a "scolding" (if you can even call it that) because of his mistakes that he may have made at some point in the past on this guide, nor was it about this guide/thread being different from others or the unfortunate outcome of a few users that have used this guide. It was the attitude he gave as he got defensive and being insulted unnecessarily at the fact that personal opinions were conveyed, another thread was brought up and referenced, that at some point in the past some of the information of the guide was wrong (which is a fact that can't be escaped, but all threads must be corrected from time to time at one point or another so it shouldn't be taken so gravely), and when suggestions in attempt to contribute to the OP guide as constructive criticisms. He lashed out when the link to another guide was posted overreacting not believing it was even an xda thread, then dismissed that the post was irrelevant because it wasn't as clearly titled or marked like his OP (even though the information was there in a subsection), then "scolded" when it was disagreed on the accuracy of the OP, became defensive when it was pointed out that some corrections have taken some time to be dealt with, then again lashed out and got insulted when given ideas and suggestions to contribute to the guide and diminished them as mere opinions and even accused them as disrespectful just because they were differing opinions...

Point is that it wasn't about the guide's effectiveness & value or whatever past mistakes, it was the attitude and defensiveness at them being pointed out and aversion to constructive criticism, suggestions, & opinions that he was being "scolded" on. Anyone that runs their own thread/guide or tool has to acknowledge that an OP not being able to take constructive criticism and suggestions/contributions is detrimental to the thread/guide/tool as that would be against this being a community for all of us to contribute towards making it better.

If this is taken as a rant, my apologies for it. But I hope it is still considered constructive towards this thread as it is giving appreciation and credit as well as it makes comments to help shape its future...
[Google Pixel 7 Pro] Homeboy76:
Thank you!
[Google Pixel 7 Pro] aziz.yankee:
Hello!

I can't seem to unroot my Pixel 7 Pro, I've tried patching boot.img and init_boot.img and reflashing but root wouldn't happen.

What am I doing wrong? Can someone help please?

Firmware version: image-cheetah-tq1a.221205.012

Platform tools version: platform-tools_r33.0.3-windows

Magisk Version: 25.2 (25200)
[Google Pixel 7 Pro] Lughnasadh:
Are you trying to root or unroot? (because you said you "can't seem to unroot...", but then go on to say you are trying to root).

To unroot:

Flash the stock init_boot.img

fastboot flash init_boot init_boot.img

To root:

Patch the init_boot.img with Magisk (leave the boot.img alone), then flash the patched init_boot.img

fastboot flash init_boot <nameofpatchedinit_boot.img>
[Google Pixel 7 Pro] aziz.yankee:
Sorry, my bad, trying to ROOT.

That's what I did but it wouldn't root...what am I doing wrong?
[Google Pixel 7 Pro] Kingvtt:
I was stuck flashing the init_boot but with your command it works! Thanks
[Google Pixel 7 Pro] aziz.yankee:
Spoiler content hidden.

But then I've enabled "Beta Updates enabled" on Magisk, then re-installed Magis, re-patched init_boot.img file then reflashed. It worked. Mysterious Miracle. Thanks all!
[Google Pixel 7 Pro] 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.
[Google Pixel 7 Pro] HipKat:
Try using the Pixelflasher if you're having issues with the manual process.
[Google Pixel 7 Pro] foamerman:
Thanks. I had the magisk patch file in the wrong path.
[Google Pixel 7 Pro] badabing2003:
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

Turn off automatic install in developer options.

Disable system update notification in Google Play services.
[Google Pixel 7 Pro] 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?
[Google Pixel 7 Pro] Homeboy76:
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.
[Google Pixel 7 Pro] Fishawy:
Weird, never used Delta, but the module is automatically installed after using both Stable and Canary.
[Google Pixel 7 Pro] Homeboy76:
@Fishawy

Your assessment of the situation is correct it is "weird".

Hopefully, @badabing2003 can provide some information about the

Magisk bootloop protector

bootloop problem.
[Google Pixel 7 Pro] badabing2003:
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.
[Google Pixel 7 Pro] Fishawy:
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.
[Google Pixel 7 Pro] Homeboy76:
Did you download Magisk Beta, Canary or Stable from the links below?

The links below are the

only official

download links for downloading Magisk.

Magisk Canary (25205)

Magisk Beta 25.2 or Magisk Stable 25.2
[Google Pixel 7 Pro] Fishawy:
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.
[Google Pixel 7 Pro] badabing2003:
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.
[Google Pixel 7 Pro] Fishawy:
Thanks for that. I'll give it a go and see.
[Google Pixel 7 Pro] kevinxjen:
will it break HDR10 compliance?
[Google Pixel 7 Pro] Homeboy76:
New

The

Developer Preview QRP2 Beta

Factory/OTA image links are in the

OP, Part I, NEW

.
[Google Pixel 7 Pro] dd805bb:
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.
[Google Pixel 7 Pro] Homeboy76:
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.
[Google Pixel 7 Pro] 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
[Google Pixel 7 Pro] Homeboy76:
Disable/Turn off

Automatic system updates

: Settings => System => Developer options => Automatic system updates.
[Google Pixel 7 Pro] franco985:
in this way

and then? is present a procedure to update without losing root?
[Google Pixel 7 Pro] Homeboy76:
"is present a procedure to update without losing root?"

No, not using the instructions in this guide.

However, you may be able to

"...update without losing root?"

using

PixelFlasher

for Google Pixel 7 Pro Support Thread, that is referenced in this guide.
[Google Pixel 7 Pro] Elastep:
Settings > System > Advanced > Reset Options > Erase all data (factory reset)

THIS IS NOT GOING TO RETURN YOUR PHONE TO STOCK.... You actually need to flash a stock image to return your phone to stock.

It's a confusing manual.
[Google Pixel 7 Pro] Homeboy76:
AFAIK, when you

reset - Erase all data (factory reset)

your phone. It erases all data from your phone and flashes the current

stock

factory image to your phone.

Yes, you can also do it your way:

OP,

Part II,

2. Install/Update Factory Image keep data, wipe data...,

•

Flash Factory Image Wipe Data

.

which, erases all data from your phone and flashes the current

stock

factory image to your phone.

Note: If you

do no't wipe

your phone you

may brick it when you try to lock the bootloader

.
[Google Pixel 7 Pro] Lughnasadh:
You should be able to update with Pixel Flasher without losing root.
[Google Pixel 7 Pro] Homeboy76:
Good catch, :) I edited my post. :rolleyes:

Thanks, for the reminder.
[Google Pixel 7 Pro] dd805bb:
IDK if that needs to be done. For me it worked. Let's see if it's an issue for others first. It could be something I did mod wise. Just experience I had. I assume if more have the same issue, and that fixes it, then yes.
[Google Pixel 7 Pro] Homeboy76:
Thanks for the clarification @S8rooted&tooted.

Using Displax's safetynet-fix-v2.3.1-MOD_2.0.zip as stated in the OP works for me.
[Google Pixel 7 Pro] Elastep:
It's going to leave you with the firmware you've flashed before, not the factory stock.
[Google Pixel 7 Pro] Homeboy76:
If you are already on the

stock

factory image, why are you trying to •

Return to Stock

?

The reason that is in the OP is some XDA members flash Custom ROMS on their phones. The

only ways

, I know, an indivdual with a Custon ROM on their phone can return their phone to

stock

so they can lock the bootloader without risking

bricking their phone

are:

Reset their phone (

reset - Erase all data (factory reset)

) their phone.

Do OP, Part II, 2. Install/Update Factory Image keep data, wipe data...,

•

Flash Factory Image Wipe Data

.

fastboot -w update image...zip

Both of these methods wipe the phone. Which is required to

return a phone that is using a Custom ROM to stock

.
[Google Pixel 7 Pro] Elastep:
After reading this I was under the impression that if you do a reset of your custom ROM will magically be reverted to a factory ROM. (IDK, maybe from some hidden memory partition). And that it's safe to relock the bootloader after this. Hopefully, it's just me and no one else )
[Google Pixel 7 Pro] Homeboy76:
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.
[Google Pixel 7 Pro] badabing2003:
I would add to it that doing it to both slots assures that the inactive slot does not have anything non stock on it.
[Google Pixel 7 Pro] bethedealer:
Can I use the procedures in this thread to root QPR2 beta1?
[Google Pixel 7 Pro] Lughnasadh:
Yes, just patch the init_boot.img and flash that patched image.
[Google Pixel 7 Pro] Homeboy76:
Canary Update

Magisk (831a398b) (25206)
[Google Pixel 7 Pro] Homeboy76:
Update SafetyNet Net Fix Mod

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87198517/

Displax's SafetyNet Fix Mod: v2.3.1-MOD_2.1

• Update module.prop
[Google Pixel 7 Pro] Homeboy76:
Update SafetyNet Fix

kdrag0n SafetyNet Fix V2.4.0

This version only supports Zygisk (Magisk 24 and newer).
[Google Pixel 7 Pro] Homeboy76:
Kernel Update

[KERNEL] CleanSlate T1.4.4 |S2S|AdBlock|VIB|BatterySvr [Jan 10]
[Google Pixel 7 Pro] dd805bb:
FYI, I have been using update method install into inactive slot through Magisk for awhile now. At least the past 2 or 3 times and going from stock to beta. No issues at all for me.
[Google Pixel 7 Pro] Homeboy76:
"...stock to beta" Are you using these instructions to do that?

I wonder has anyone else been sucessful installing to the stock OTA inactive slot, manually, on their stock Pixel 7 Pro.
[Google Pixel 7 Pro] Slim2none4u:
I do my monthly updates with PF and I use the steps to install the update to the inactive slot.
[Google Pixel 7 Pro] Homeboy76:
Excellent!

I have a link to PF in this thread.

Once upon a time a member could install to the inactive slot using these instructions. I want to know has anyone been able to install to the intactive slot on their Pixel 7 Pro phone using the aforementioned instruction.
[Google Pixel 7 Pro] Lughnasadh:
I'm getting a 404 on your link. Think because it has a / at the end? Without the slash it's ok.

I've seen a handful or so of people successfully use this method over the past few months, but I've seen more who have been unsuccessful, for what it's worth.