yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] simplepinoi177:
I understand you are putting your phone on the Verizon network, but did you purchase your phone from Verizon? Or did you purchase it from Google, Amazon, Swappa, or any other third-party site -- anything outside of any carriers? Because if you did purchase it through Verizon (or any carrier), it won't matter whether you put the sim before or after unlocking the bootloader, most likely you will not be able to unlock the bootloader because the OEM unlock toggle will be greyed out and unable to switch -- without the switch you would not be able to unlock the bootloader successfully...

If you are on Verizon's cell line, it would be best to use their factory/ota image as it has certain "tweaks" for the Pixel 7 Pro & their network; if not, using the Global factory/ota image works just as well -- even if you did load Verizon's factory/ota image on a device that isn't on their line, the images are comparable and either would be safe to use; it's just as matter of having one that would have said "tweaks" applied for Verizon's line or not...
[Google Pixel 7 Pro] Homeboy76:
Please read the post before you reply:

foamerman said:

...I'll be getting my 7pro tomorrow from Google I'm hoping it will have the Global version on it...

Homeboy76 said

"Your carrier is Verizon so use the Verizon factory/ota image if it is available. If it is

not

available use the Global factory/ota image."

Sometime, there is no Verizon monthly factory/ota image posted or it is posted after the Global factory/ota image is posted.

Thank you for explaining the reason one should use the Verizon factory/ota image if their carrier is Verizon.
[Google Pixel 7 Pro] madmuthertrucker:
I have a Google phone on Verizon and I have never put the Verizon update on it. I'm afraid that it will come with all their crapware.
[Google Pixel 7 Pro] Homeboy76:
Some other people feel the same way. :)

The bottom line, it's your phone you decide which factory/ota image you want to use.

My point in post #35 and #37 was you can use the Global or Verizon factory/ota image if your carrier is Verizon.

You have confirmed my point.
[Google Pixel 7 Pro] jake.99x3:
Requested a temporary SIM unlock from T-Mobile; explained that I was traveling out of country and that past pixels had come unlocked ;p . My request was granted and I was given a 30 day SIM unlock for my Pixel 7 pro. System -> Developer Options -> OEM unlocking is greyed out with the message "Connect to the internet or contact your carrier". I did a little more searching and other users mentioned this going away 3 days after connecting to mobile data/wifi; Hopefully this is the case for my pixel haha
[Google Pixel 7 Pro] schmeggy929:
Try again.
[Google Pixel 7 Pro] schmeggy929:
Well he is the developer of Pixel Flasher sooooooo I'm gonna go with Pixel Flasher. Lol
[Google Pixel 7 Pro] badabing2003:
Android Flash tool is solid, but it doesn't have all the features of PF, if you want to flash and keep root, you can't do it in Android Flash Tool, you still would need to do that manually or through a tool like PF.
[Google Pixel 7 Pro] Homeboy76:
Good questions, I've updated the guide with the answer to these two questions: OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 2. Manually Install/Update Factory Image keep data, wipe data, or use @badabing2003 PixelFlashers, Important Note(s): 1 and 2.

This guide has always referred XDA members that are uncomfortable

manually flashing

the factory image to use @badabing2003 PixelFlasher.
[Google Pixel 7 Pro] inpowers:
Thanks Homeboy & badabing

Much appreciated.
[Google Pixel 7 Pro] supermansaga:
Are we comfortable with Magisk Canary 26101 yet?
[Google Pixel 7 Pro] inpowers:
All working on my end after updating firmware this morning. No issues with wallet
[Google Pixel 7 Pro] supermansaga:
It appears Homeboy hasn't endorsed it at the top? It's really hard for us newbies to understand what each Canary version has changed. Thx
[Google Pixel 7 Pro] Homeboy76:
...endorsed it at the top?

What does that mean? It is not a question.
[Google Pixel 7 Pro] simplepinoi177:
I can't be sure...but I'm guessing he means it not being stated in the OP ("at the top" of the thread?) -- like "officially" where it seems to be "endorsed" or confident enough to be posted in the OP official steps...

Although why he thinks you need to be listing and updating all the changelogs of the canary versions is confounding me...you're not a Magisk Canary repo or even a dedicated thread to it...
[Google Pixel 7 Pro] Homeboy76:
All version of the

official versions of

Magisk and the Magisk

forks

that I am aware of are listed in the OP: ~ ~ ~ Part I - INFORMATION ~ ~ ~,

Update(s)

The

offical versions

are listed in the OP again in ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~; 5. Root/Reroot with Magisk and Pass SafetyNet; • Patching the init_boot.img - to root/reroot.; 2, 3, and 4.
[Google Pixel 7 Pro] supermansaga:
I am seeing the below instead of 26101. Thanks. Not a big deal

Magisk Canary - app-release_e2545e57-26001.apk 05 Apr
[Google Pixel 7 Pro] Homeboy76:
https://xdaforums.com/t/guide-root-...der-pass-safetynet-more.4505353/post-88400427
[Google Pixel 7 Pro] supermansaga:
Thanks. See your update in #1 Part 1 No. 4 too
[Google Pixel 7 Pro] redwoodie:
I'm new to this thread and ready to order a P7 Pro. Is there a list of variants/vendors somewhere that identifies which Pixels have unlockable bootloaders? I am on VZW but would never buy from them...am I assured of getting an unlockable BL from Google Store? And, oh yeah...will it support VZW bands? I see Staff Member Simplepinoi177 lists a Verizon Pixel 7 Pro that's rooted...didn't think that possible on a VZW sold/branded phone?

Thanks!
[Google Pixel 7 Pro] Homeboy76:
@redwoodie

Yes, if you buy a Google Pixel 7 Pro from the Google Store or Google Fi you will get a Google Pixel 7 Pro with an unlockable bootloader. Yes, it will work on the Verizon network - VZW bands.

Note: The model that supports the Verizon (5G mmWave + Sub 6GHz20) is GE2AE, look at this thread (Pixel 7 Pro) under Network to see all the bands.

When you order your phone from the Google Store or Google Fi, they will ask what carrier you are using. I'm assuming they ask that question so they know which model to ship.
[Google Pixel 7 Pro] redwoodie:
Thanks!
[Google Pixel 7 Pro] simplepinoi177:
@redwoodie, just be sure you get the global unlocked variant,

even in the Google Store

-- as you can

still

purchase the Verizon variant in Google Store (if by accident); and would then be restricted from unlocking the bootloader & custom ROM/kernel/rooting...
[Google Pixel 7 Pro] redwoodie:
So, if I get GE2AE, I'm good with unlockable BL? If I tell them Verizon are they likely to steer me to the VZW locked variant?

Man, it is such a minefield with variants! I learned my lesson years ago when I bought a Sony Xperia Z2 tablet from the bastards. It only got 1 OS update and locked BL. At least there was a root exploit though.
[Google Pixel 7 Pro] cmh714:
Yes. I have the GE2AE from Google and have it on VZW. It is unlocked and rooted.
[Google Pixel 7 Pro] Phantisy:
Anyone have an issue with Google Play Services unchecking after a reboot in the Magisk DenyList? I'm on the stock rom TQ2A.230405.003.E1 with a Magisk Canary 26101.
[Google Pixel 7 Pro] Lughnasadh:
If you are using a USNF mod, that's normal. It automatically unchecks it and "denies" it in the background because it won't work properly if it is checked.
[Google Pixel 7 Pro] Phantisy:
I'm not sure what that means. Can I correct that? My phone won't pass SafetyNet
[Google Pixel 7 Pro] Lughnasadh:
Are you using a USNF mod? If so, which one? You should be using this one.
[Google Pixel 7 Pro] Phantisy:
I'm not sure which one I had. I uninstalled it and installed the one you linked.
[Google Pixel 7 Pro] DroXc:
I'm having an odd issue with my Pixel 7 Pro - I had everything working fine with root and it passed all safety checks, suddenly the other morning it seemed to be working fine and I went to use google pay on my phone and suddenly it's giving me a security error and safety checks are failing. I tried Magisk and it's giving errors but there is a pending software update but it hasn't went through yet. I cant't seem to find a way to fix this without fully wiping and starting fresh, anyone have any ideas on what I can do? I re-installed Magisk but it doesnt give me any options to install new modules.
[Google Pixel 7 Pro] cmh714:
So lets see...I would try reflashing your patched init_boot.img assuming you are using the same version of Magisk.

Otherwise, I think I would start with the latest version of magisk you like, patch init_boot with this version, then flash that and see where you are.
[Google Pixel 7 Pro] madmuthertrucker:
I had this happen to me until I installed USNF 2.4.0_1.2 by kdrag0n, modded by Displax
[Google Pixel 7 Pro] supermansaga:
I would recommend this video

to flash April update OR you could try the pixel flasher. I can only speak to the former as I have actually done it myself a few times now.
[Google Pixel 7 Pro] badabing2003:
The user already said:

Which means it has nothing to do with update and keeping root, regardless of how it's done, and it has more to do with passing Play Integrity.

There are dedicated lengthy threads about it, but the gist of it is making sure to use displax's safetynet-fix-v2.4.0-MOD_1.2.zip.
[Google Pixel 7 Pro] jhjhjhjhjhjh:
Ok hello pixel world. First time pixel 7 pro owner.

Coming from Motorola's devices.

One really can't unlock the bootloader unless the phone is Sim network Unlocked?

Say it isn't so..

Bought my pixel from spectrum.

Any root solutions for us Spectrum users?.
[Google Pixel 7 Pro] Homeboy76:
Verizon own Spectrum, and Verizon policy is never unlock the bootloader.

However, some people say if you pay off the Spectrum phone you can request the phone be

sims unlocked

. After, the phone is sim unlocked you can unlock the bootloader. I'm waiting for someone to confirm it.
[Google Pixel 7 Pro] jhjhjhjhjhjh:
Yeah I figured that upon my research hoping there was a workaround by now ..:)

Anywho loving this phone so far.. Coming from a rooted world this phone doesn't make me want to root actually.. The experience so far is similar to me using pixel experience gsi 13 rom .So I'll wait...Not rushing to root at all...

Thanks mate...
[Google Pixel 7 Pro] simplepinoi177:
You might be pleasantly surprised how many users come to feel the same way; that rooting is unneeded for them as they seem to get & enjoy everything they wish enough from the stock ROM...much can still be customized without root access...
[Google Pixel 7 Pro] reg66:
Quick question for you seasoned Pixelers, does Google Pixel 7 Pro have anything like the old Samsung knox (iirc) , whereby they (manufacturer under warranty for example) can tell that I was once unlocked?

Basically I need to temporarily root my device and then relock bl, but it's not that essential that I'm prepared to lose warranty for sure (although I appreciate if something goes drastically wrong during root, they'll know)
[Google Pixel 7 Pro] simplepinoi177:
Google Pixels don't have anything like Samsung KNOX (which, reportedly/supposedly causes a physical mark/change on the system board when bootloader is unlocked; I'm sure there might be ways for Google to be able to tell if the bootloader has been unlocked, but they don't care and/or overlook it) whereas Google honors devices even if it's bootloader has been unlocked -- you can send them a warranty repair/replacement/trade-in with a device with an unlocked bootloader and they will still honor it.

Be very careful relocking the BL...countless (and i mean countless) users going back all the way from the Pixel 1 has hard-bricked their device doing it wrongly. Either way, you will not lose warranty. And, like 98% of the time anything "drastically" goes "wrong during root", it's easy enough to correct -- it mainly depends on getting back into the bootloader; which attempting to root usually can't wreck it so badly you can't get to the bootloader/fastboot mode...

If/When you relock the bootloader; the safest way and the best bet going about it is using Google's official Android Flash Tool -- it's made with checks and protocols that make it the safest and full way of relocking the bootloader.

Hope this helps...
[Google Pixel 7 Pro] badabing2003:
Curious if you know if Android flash tool allows you to flash to both slots?

I'm asking because hypothetically if it only flashes one slot, you can have a bad inactive slot.

If I were to relock a bootloader, I would flash full image to both slots with wipe and then lock it.

Not that I would relock :)
[Google Pixel 7 Pro] simplepinoi177:
I imagine Google/main Android devs have it figured out to take put the least amount of risk where, I imagine, they flash both; just to be safe. I know the hard bricking is most at risk when having different bootloader versions to the installed OS (or something like that), but I'm sure there has to be some risk/connection with that also being the case in the inactive slot as well...so I'm willing to be they take care of that; even if not really necessary, to mitigate he risk anyways...

But after looking at @xtcislove's screenshot, it doesn't look like it's optional (if done at all), but I went ahead to check it out myself because I was curious if flashing both slots fell under "force flash all partitions", but it doesn't; it states about flashing bootloader or modem, even if it isn't necessary (same version as being installed) and/or unnecessary to reset the device.

But I coulda sworn (the only 2 times I did it back in Nov) that there was the option for it...
[Google Pixel 7 Pro] Lughnasadh:
"Force Flash All Partitions" does not flash the OS to both slots. This was tested by a member using a Pixel 6 series device when they updated from Android 12 to Android 13. Force flash partitions was selected but when checking the bootloader versions afterwards to make sure the A13 bootloader was on both slots it was found that the A12 bootloader was still on the inactive slot.
[Google Pixel 7 Pro] xtcislove:
Do i get something wrong here?

I understand it like this:

Without "Force Flash all Partitions" ticked, the tool skips partitions that are already on the same version.

"Force Flash all Partitions" is ticked by default.

If "Skip Secondary" is ticked, the tool will NOT flash the secondary slot.

"Skip Secondary" is deactivated by default.

Am i wrong here or do in understand you guys wrong?
[Google Pixel 7 Pro] Lughnasadh:
Since "Skip Secondary" is disabled by default, that would mean when using the default settings the tool would flash to both slots, but this doesn't seem to be the case. I'm pretty certain the user I mentioned above did not have "Skip Secondary" checked and therefore when they flashed it should have flashed to both slots if this were the case, which it didn't.

Having said that, I can't be completely sure exactly what Google means when they use the term "secondary partitions". I have not found any other context where Google refers to "secondary partitions" as meaning partitions on the inactive/other slot. Possibly they mean partitions other than boot, system, vendor & radio???
[Google Pixel 7 Pro] supermansaga:
May update is here https://developers.google.com/android/images

Happy flashing
[Google Pixel 7 Pro] Homeboy76:
OP Changes

I added additional notes to the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~,

5. Root/Reroot with Magisk and Pass SafetyNet.,

• Patching the boot/init_boot.img - to root/reroot.,

1 & 2.
[Google Pixel 7 Pro] missionman:
Sorry everyone Im new to this and having a hard time on something likely easy for the rest of you.

Im in fastboot mode on my pixel 7 pro.

I already have adb drivers and just installed the hard to figure out google bootloader drivers from my usb_driver folder. its showing up on device manager as Android Bootloader Interface

my platform-tools folder is on my desktop with fastboot.exe and al that.

when i open Command Prompt i get nowhere.

heres the text i copied from CMD window.

"Microsoft Windows [Version 10.0.19044.2673]

(c) Microsoft Corporation. All rights reserved.

C:\Users\PWNing YOU softly>fastboot --version

'fastboot' is not recognized as an internal or external command,

operable program or batch file."

I cannot get anywhere.

What do i do?
[Google Pixel 7 Pro] gpvecchi:
You're in the wrong directory
[Google Pixel 7 Pro] missionman:
I just figured it out. thank you! i placd the command exe into the folder and it worked. bootloader is unlocked. now to root it.
[Google Pixel 7 Pro] wrkadung:
You can now use the PixelFlasher tool to root your phone within minutes. Here is the tutorial for beginners on how to use PixelFlasher to root your Pixel phone.
[Google Pixel 7 Pro] Homeboy76:
Update

SDK Platform Tools r. 34.0.1

fixed
[Google Pixel 7 Pro] madmuthertrucker:
Are we sure about the fixed part? I'm skittish.
[Google Pixel 7 Pro] Homeboy76:
The, major, problem with r 34.0.1 was fastbootd wasn't working. Several, members have reported using r. 34.0.1 and stated fastbootd is working.
[Google Pixel 7 Pro] Homeboy76:
Update

I tested SDK Platform-tools r. 34.0.1 it is

not fixed

. There are still problems with fastbootd. Use SDK Platform-tools r. 33.0.3
[Google Pixel 7 Pro] sillyshyme:
Can you make a guide for Pixel 7 users?
[Google Pixel 7 Pro] xtcislove:
its the same. You simply download and use panther(Pixel7) and not cheetah(Pixel7Pro) firmware
[Google Pixel 7 Pro] sillyshyme:
what if I am on beta 14 of Android do I have unenroll prior then wait for 13 to reinstall and follow directions or can I use beta 14?
[Google Pixel 7 Pro] sillyshyme:
Just read few things US Verizon won't let me do this unlock bootloader :( so is it worth trying or not since Verizon will not allow it says fellow XDA users.
[Google Pixel 7 Pro] Homeboy76:
@sillyshyme,

If you join the Android 14 Beta with an

unlockable bootloader

you cannot return to Android 13. You will remain there until Android 14 is released: See

"it is not worth it" - Post #439 below

.
[Google Pixel 7 Pro] xtcislove:
Since you are a senior member i expect you to to a little bit of search on your own. Everything you are asking can be found by a quick search.

For example in google: "Verizon Gopogle pixel 7 pro bootloader unlock"

The first page you find gives you the answer at a glance.
[Google Pixel 7 Pro] Homeboy76:
It is not worth it
[Google Pixel 7 Pro] ChillDuder:
Hello, comprehensive guide. thanks.

i get a pixel 7 in a few days, so started to gain informations.

i'm flashing/bricking android devices for a few years now, but not pixels. just be curious and for understandings:

- if i want root immediately after a update-stockrom or customrom via fastboot method: why not just go into recovery afterwards and just sideload magisk.zip to root?

- is it possible to replace init_boot.img in a image zip (stock or custom rom) with the magisk patched version just to immediately get root after fastboot flashing something? (of course: using the init_boot from that zip before to patch with magisk)

thank you all
[Google Pixel 7 Pro] badabing2003:
First part no, there is no recovery or twrp for Pixel.

Second part, yes.
[Google Pixel 7 Pro] ChillDuder:
thank you.

i thought there is a 'install update via adb' option in stock recovery, because i saw a screenshot of a pixel recovery on random internet search ;)
[Google Pixel 7 Pro] badabing2003:
if your bootloader is unlocked you can dirty flash factory image and flash patched init_boot.

If your bootloader is not unlocked, the only thing you could do is sideload OTA and get updated.
[Google Pixel 7 Pro] ChillDuder:
i had to do --disable-verity --disable-verification along with wipe data -w at least once with stock rom flashing to get disabled verification, for e.g. custom kernels. ok.

and if i wish to stay disabled verification i had to continue to do so.

but do had this to do also with every custom rom flashes?

thanks in advance
[Google Pixel 7 Pro] Homeboy76:
Yes, you have to --disable-verity --disable-verification every time you update the factory image. If you want to use a Custom kernel. If you skip doing it once the next time you do it you will have to wipe your phone.
[Google Pixel 7 Pro] Homeboy76:
Magisk Canary Update

app-release_47d2d4e3-26102.apk

Notes:

Tap app-release.apk

Tap 3 dots (...) across from 10.x MB

Tap Download
[Google Pixel 7 Pro] Homeboy76:
SDK Platform-tools Update

SDK Platform-tools r. 34.0.3, was released May 22, 2023.

@badabing2003 reported a problem when using it.

https://xdaforums.com/t/platform-to...7-pro-cheetah-safetynet.4502805/post-88571575

@Lughnasadh, suggested a fix.

https://xdaforums.com/t/platform-to...7-pro-cheetah-safetynet.4502805/post-88571601

@badabing2003, confirmed the suggested fix works.

https://xdaforums.com/t/platform-to...7-pro-cheetah-safetynet.4502805/post-88571617

If you use Linux or Windows SDK Platform- tools r. 34.0.3. You must set the environment variable:

Linux

Windows

Note:

If you have any problems with SDK Platform-tools 34.0.3

. You can get SDK Platform-tools 33.0.3 here.
[Google Pixel 7 Pro] Lughnasadh:
Good morning. I think that should be 34.0.3 and not 34.0.4, unless Google released a newer version while I was asleep.
[Google Pixel 7 Pro] Homeboy76:
:rolleyes: fixed, thanks.
[Google Pixel 7 Pro] missionman:
Thanks I got rooted and now im all good!
[Google Pixel 7 Pro] Homeboy76:
Update

XDA members are reporting more issues with SDK Platform-tools 34.0.3

Use SDK Platform-tools 33.0.3
[Google Pixel 7 Pro] andrew2432:
Most of this works for the pixel 7 not pro? Custom os section says panther/cheetah
[Google Pixel 7 Pro] wangdaning:
34.0.3, after adding the android_out thing to path, still failed to wipe device with stock flash-all.bat. It remembered my screen unlock. Google ain't gonna fix anything, they just break it.
[Google Pixel 7 Pro] Homeboy76:
Where does custom os section say panther/cheetah? Most of what work for pixel 7 not pro?
[Google Pixel 7 Pro] andrew2432:
Sorry;

Does most of this work for the pixel 7? Some of the custom os section says panther/cheetah in the titles. Hoping they are similar
[Google Pixel 7 Pro] Homeboy76:
I think you are asking about the Operating System (OS), but you want to know if the firmware/software is interchangable.

Why?

You wrote, "Some of the custom os section says panther/cheetah in the titles. Hoping they are similar"

The OS on all Google phones is Android.

The Google Pixel 7/7Pro are on Android 13. Yea, I know they are

beta

testing Android 13 and 14.

AFAIK, Google makes firmware/software for the Google Pixel 7/7 Pro, and several other Google phones. Every phone they make has its own

unique firmware/software

they are not

interchangeable

i.e.,

cheetah" for Pixel 7 Pro

13.0.0 (TQ2A.230505.002, May 2023)	Flash	Link

fe44ced0de116faaabf4928ee3db7f382d034d54fe5da7dab7575ba4febd9a89

panther" for Pixel 7

13.0.0 (TQ2A.230505.002, May 2023)	Flash	Link

3271ae5c4d3288e4a067ad161728ae40a6fc62f8acafd0e426442c9e04c71a05

Everything looks the same but the SHA256 verification.

Why?

The files are not the same

.

The firmware/software for the Google Pixel 7 is not made to work on the Google Pixel 7 Pro and vice versa.

You can use this guide for Google Pixel 7/7 Pro, but you must use the correct firmware/software for your phone version.
[Google Pixel 7 Pro] simplepinoi177:
What @Homeboy76 states in Post #456 is true and answers most of your inquiry, as supplemental information -- adb & fastboot commands, drivers,

sometimes

custom ROMs & kernels, apps, work for both panther/cheetah (Pixel 7/Pixel 7 Pro).
[Google Pixel 7 Pro] Homeboy76:
True, however @andrew2432 original

post

(See above) stated "

Custom os section

says panther/cheetah" I assumed andrew2432 was referring to a

section

in this thread: OP, ~ ~ ~ Part III - OTHER ~ ~ ~, 1. Custom ROMs, • Need help with a Custom ROM.

My assumption was wrong. :ROFLMAO:

My thanks to Staff Member @simplepinoi177 for the "assist". :) 👍