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

[Homeboy76]

So the head post is wrong? There is no information about flashing factory image

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?

 

[Homeboy76]

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

January 3, 2022 (TQ1A.230105.002 - Global / .A1 Telstra) - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet

https://developers.google.com/android/images#cheetah 13.0.0 (TQ1A.230105.002, Jan 2023) Flash Link 34d676ff4d260f02d9ada1f16f24fd7995c9b9ca832410099950d9c510db8793 13.0.0 (TQ1A.230105.002.A1, Jan 2023, Telstra) Flash Link...

forum.xda-developers.com

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.

 

[EtherealRemnant]

First, before you should read the post
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, you didn't post any instructions, you posted a link to the Dec 2022 Factory image.
That link is in the OP under Prerequisites.
Fourth, make sure your facts are correct before you try to correct someone.

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:

How to unroot
One of these two options:

1. Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you do not have to manually unlock the bootloader - their site will do that on its own).
   Select the options to:
   • Wipe
   • Force flash all partitions
   • Re-lock bootloader

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.

 

[Homeboy76]

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.

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

 

[jake.99x3]

Finally got my T-Mobile Pixel 7 pro bootloader unlocked 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.

 

[Winstonshead]

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?

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

 

[Homeboy76]

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

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.

 

[simplepinoi177]

So the head post is wrong? There is no information about flashing factory image

"The link that I posted goes to the third post in that thread..."
What are you writing about, what third post??
Those links do not go to an XDA thread or XDA post.


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

There is no section in those links on 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. 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.

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.

Again, you are giving your personal opinon.
Opinons are like noses, Everybody has one.

"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 wrong information you posted in this thread.

Your last two post # 100 and # 103 are opinionated, and full of incorrect information.

@EtherealRemnant isn't wrong. His link does go to the third post of THIS thread; which clearly is a "XDA thread" & "XDA post".
Even though EtherealRemnant didn't wish to clarify with you because English may not be your first language, I am willing...
"when the phone dropped" or "phone that dropped" is American English slang for when the phone (Pixel 7 Pro) first released (back in October 13).
He is correct again in pointing to that section of the thread/post because although the section isn't titled to re-lock the bootloader directly, the steps do include how to re-lock it as one of the "options" using the Official Google Android Flash Tool (option 1 if i recall correctly).
He is also correct in saying how you were incorrect at first when you didn't update your information for the Pixel 7; specifically that we need to patch the init_boot instead of the boot partition (it was apparent you were copying your guide from other devices [most likely Pixel 6] and it was incorrect for this device). It did take you a little while to correct that information. And also for weeks on updating via OTA "and maintain root" (which applies because it would fall under "wrong information on how to root") as you were insisting that using the Magisk "Install to Inactive Slot (after OTA)" was still applicable for our Pixel 7 devices...I know because I was pointing other users to that section of your post who were interested in attempting to do the "usual" applying OTA to inactive slot to retain root for weeks before you all of a sudden finally updated that it doesn't work and it's up to topjohnwu to update the method. I know you must remember that as it was a major shake-up on your guide that you modified as well as you must be aware how long it took you to update that information after initially creating this thread/guide -- as that method had never worked so it would be easy to measure how much time had past between the creation of this thread and when you modified that step.

It is getting kinda confusing that there are a number of rooting guides on here. I follow both of these in attempt to assist users on both and try and consolidate knowledge & experience from both when applicable in hopes to correct any of the "out of sync" info being passed around...

You should also consider adding supplemental info and implement steps to include using the Official Google Android Flash Tool as an option to re-lock the bootloader as that definitely and surely has more success and less-of-a-chance-of-bricking-the-device than attempting to manually run the fastboot commands (as the tool also flashes the factory image instead of merely resetting the phone) as well as it being from Google knows more what it's doing than many novice users -- it's hard to mess up when it's mostly automated and code is specifically written for the specific device and objective.
In my personal opinion, I figure applying a Full Factory Image with the "-w" command intact might be better than merely resetting the device; maybe something is kept (which is bad as for the same reason why the phone needs to be completely stock in order to be successful) by merely resetting it that bricks the phone when re-locking and/or going through the set-up process somehow does NOT keep it in "pure" stock form for the re-lock of the bootloader to be successful -- your steps state to "set up phone" at the end of "return phone to stock" (which you state to do in Step #1 in your Lock Bootloader section) when maybe that's a bad idea when re-locking the bootloader. Again, just my opinion and something you may want to consider...

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

 

[Homeboy76]

...Even though EtherealRemnant didn't wish to clarify with you because English may not be your first language, I am willing...

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

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

1. Did you read my edited post to EtherealRemnant before you posted this?
2. Did you ever write a post other than this one, identifying any errors in this thread that were not corrected?
3. 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).

 

[vlucchetti]

Homeboy, ignore them. I've followed your guides through multiple phones over multiple updates and you are the best out there.

 

[simplepinoi177]

Do you have a problem respecting other opinions that work?

dude calm down, where do you get me having "a problem respecting other opinions"?! Having a different opinion does not mean not having "a problem respecting other opinions"...it's simply a different opinion! Even you said "Opinions are like noses, Everybody has one.". Geez...
I literally said "Again, just my opinion and something you may want to consider...", I don't see how that was disrespectful to your opinion nor was it anything but just a mere suggestion...‍

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

It shows that English may not be your first language and/or you have trouble reading... I did not write my post for "users [ I ] am commenting for", it is obviously for YOU in hopes it helps you understand WHERE users are coming from, not FOR them. Because there are users that have been confused by you guide and there is need for some clarification -- either on your part or theirs -- and you would be deluded believing otherwise and that there is no need for clarification. I don't wish to, but please don't make me quote all the posts here of users that got confused by your guide. Winstonshead & Post #106 being just one of them.
And, also again, you misunderstand that I was helping you try to understand EtherealRemnant's English slang; which he "didn't wish to clarify", but I was attempting so -- again, either misunderstanding English and/or you having trouble reading things.

Three questions:

1. Did you read my edited post to EtherealRemnant before you posted this?
2. Did you ever write a post other than this one, identifying any errors in this thread that were not corrected?
3. 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.

1. Dude, you seriously had like 5 "edited posts" to EtherealRemnant, how the hell am I supposed to know which one you're referring to?!?! Or are you referring to the post where you were wrong and incorrectly & mistakenly stated EtherealRemnant did not link to a XDA thread/post? Or the one where you did not understand what it meant when the Pixel first dropped...?
2. Why did I need to write a post identifying any errors in this thread that weren't corrected for you to have errors for a long time regardless? I'm not responsible for the information on the OP. Who said we had to identify and correct your errors in order to point them out? While it might've been convenient or nice for me to have, it doesn't absolve that there were errors for a long time nevertheless. Me and EtherealRemnant were merely pointing that out, not taking responsibility for it nor coming out like we weren't nice enough to point it out.
3. You say you respect my different opinion but claim I'm not respecting other opinions just because it's different than mine? Under your logic, you're not respecting my opinion that works because it's different than yours that works...
   In any case, maybe this will put it to rest; I DO respect most of your guide and your opinions on what you include in it.

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

Yes, you do, and it is a fine program. I only suggest the Official Google Android Flash Tool because it is, in fact, "official" and therefore safer; Even badabing2003 has a disclaimer stating that there are risks involved with his tool -- especially considering this whole thing was triggered by re-locking bootloader and bricking the device -- because it is mostly developed and kept up with just him while Google has a whole team dedicated to their official one as well as they have the most intimate and complete knowledge in terms of flashing and locking/unlocking bootloaders on its devices.

Further, this code was corrected October 13, 2022:
fastboot flash init_boot magisk_patched...img
The error was reported October 13, 2022 (see post #3).

post #3 is shown as posted on October 14; possibly a whole 24 hours after you created the thread. That's 24 hours of potential ramifications for users who would have followed and gotten into a bootloop because of it. This again speaks to the "out of sync" experience having these multiple guides.
Also, while that mistake was rectified within a day, the mistake in the section of updating by OTA and retaining root went on for far longer than that (weeks by my recollection).
All this was simply pointed out by @EtherealRemnant that there have been some delays in correct information on this guide before...

I sincerely hope this post helps you understand (or at least better understand) some things and I hope you aren't so defensive of the help of clarifying things for you; as taking offense can severely affect objectivity and reception to help and improvement...

 

[Homeboy76]

Homeboy, ignore them. I've followed your guides through multiple phones over multiple updates and you are the best out there.

Thanks, I'll do that.

 

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

 

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

 

[Homeboy76]

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

Thank you!

 

[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)

 

[Lughnasadh]

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)

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>

 

[aziz.yankee]

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

Sorry, my bad, trying to ROOT.

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>

That's what I did but it wouldn't root...what am I doing wrong?

 

[Kingvtt]

That was done.
testing this : fastboot flash init_boot_b magisk_patched-25200_T9evv.img
And that's pass!!

I was stuck flashing the init_boot but with your command it works! Thanks

 

[aziz.yankee]

This is the error message I get:

C:\platform-tools> fastboot flash init_boot magisk_patched-25200_fcyG0.img Warning: skip copying init_boot_a image avb footer (init_boot_a partition size: 8388608, init_boot_a image size: 67108864). Sending 'init_boot_a' (65536 KB) OKAY [ 3.405s] Writing 'init_boot_a' FAILED (remote: 'failed to flash partition (init_boot_a)') fastboot: error: Command failed C:\platform-tools> fastboot flash init_boot_b magisk_patched-25200_fcyG0.img Warning: skip copying init_boot_b image avb footer (init_boot_b partition size: 8388608, init_boot_b image size: 67108864). Sending 'init_boot_b' (65536 KB) OKAY [ 3.431s] Writing 'init_boot_b' FAILED (remote: 'failed to flash partition (init_boot_b)') fastboot: error: Command failed

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!