yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] lunacies:
I notice on the first page it mentioned Verizon bootloader's cannot be unlocked, does that mean if I have a Verizon p7p I will never be able to unlock and root it? I don't want to wipe my phone and go through setting everything up again but there are always a couple apps I would like that require root and rooting on newer devices seems so much more involved than when I used to do it. I am just wondering if it's even possible with Verizon or if I am wasting my time by even looking into it.
[Google Pixel 7 Pro] roirraW "edor" ehT:
That is correct.

Not possible with Verizon on any phone. The chances are about as slim as winning a huge lottery that Verizon or Google might goof up and some

temporary

exploit will be found by some talented developer. Might happen, but not very probable.

You can use a Google Factory unlocked model with Verizon, and then you'd be able to unlock that bootloader - but any Verizon variant of device will not be able to be bootloader unlocked, so won't be able to be rooted.
[Google Pixel 7 Pro] lunacies:
Well that's a bummer, guess I won't even waste my time researching how to do it then. I would have gotten one from Google but Verizon had too good of a trade in deals to pass up...700$ for my pixel 1 xl that doesn't even turn on anymore ...oh well. Guess I'll keep an eye out if anything changes.
[Google Pixel 7 Pro] wr3cckl3ss1:
Will be working on trying to enable OEM toggle after removing that package sometime today....also reached out to VZW themselves to inquire about carrier unlocking the phone. They said they will put a request in for me and notify me in 2 business days.(did this with s22 ultra to carrier unlock it before and way before the 60 day mark) But going forward. I'll run a steady logcat on the pixel 7 pro to maybe catch the functions they push to "carrier unlock" it. I'm really interested in how the process all works as i know it's all server based. If i can find something worthy and can enable that toggle. Trust me, i would be more than happy to share to fellow VZW P7P owners here. I'd say we're in a tight window as new updates are coming soon, so any temp exploits or any ways to uncover a way in....grow very slim as the day comes closer for the monthly updates. But I'll try I'm best. Lol
[Google Pixel 7 Pro] roirraW "edor" ehT:
That's understandable. Someone - might have been Google, or someone else - was offering some trade-in value for the P1 when pre-ordering the P7, but it definitely wasn't as much as that. Yours is a very hard deal to beat.

Good luck again!
[Google Pixel 7 Pro] Superguy:
Hopefully whatever you do will work on AT&T is well.

I'm liking their deal, but I need it unlocked as well.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Either way, you should be able to eventually with an AT&T variant:
[Google Pixel 7 Pro] wr3cckl3ss1:
Knowing all this I'll keep everything in mind. But I know it's a long shot and I know that whatever I uncover could possibly bring some sort of light to the situation or can maybe be a dead end but above all I just started with all this unlocking stuff and I like to say that I came a long way from a few months ago to now so like I said if a phone like the s22 ultra US Version can be sort of breached then I can only imagine how much easier it should be to unlock or at least breach the mechanism that does keep the security at bay. I also have a good team of guys to help me in this in the situation and so far it's been pretty good as we've all discovered the breach that is the s22 ultra. No I'm not the one that showboat or showcase what I have or how I came to breach that phone because I don't want widespread attention and I don't want widespread amount of users to come flood the threats asking a million in one questions but until I'm for certain that I'm actually fully in side the s22 ultra then I'll keep my Intel and knowledge to myself and those who know about it. I wasn't the one to go this route using the exploits but I figured there shouldn't be any harm as the majority of XDA is for unlocking...root and some sort of modification to the phone and or the operating system. But I'll leave you with this there is a certain exploit that should be coming very soon that I believe should open a lot of doors to let's say phone that are maybe 8 years old and current. As far as I know it affects kernels 5.10.xxx. I'm hoping this pixel 7 Pro falls under that umbrella so that the door could be open for root and then you know any possible development could continue on maybe opening up the bootloader but that's a long shot in itself.
[Google Pixel 7 Pro] wr3cckl3ss1:
And just to add lastly I would never ask for money, i would never want anyone to give me money. Just being able to get the Intel, being able to get the knowledge acquired is sufficient enough for me.
[Google Pixel 7 Pro] i5lee8bit:
So update on my lil' problem I had a while back @roirraW "edor" ehT and @NepoRood... It came back on my replacement device today! So that was 2 whole days before the same exact symptoms started presenting again. Ugh. On that note, I have also been verity and verification disabled and on Kirisakura since the day I got it. I was actually hoping that would somehow help but 🤷‍♂️

Other weird note - on my first P7Pro, as I was waiting for my replacement to arrive, I noticed after being turned on for a while (about 24-48 hours), Chrome would prompt me the normal way to agree to sync. Tips & support would open again, GPay fully load, etc. My phone would work 100% normally... until a reboot. Then back to square one, but again about 24-48 hours later, seems to "fix" itself (that is, prompt me to set up sync, with my existing account showing, by tapping "I'm In", instead of only offering to add account and reject me because that account is very obviously already on the device). Ugh, this is such an annoying issue to explain each time, lol!! But it would continue doing this over the past few days as well since I switched to the replacement.

So yeah, I'm still glad I did the replacement because I can completely rule out it was the device itself. Also being able to use the $200 preorder credit for preordering the P7 Pro on a Pixel 7 Pro itself was kinda awesome!! 😁😁

My conclusion is to just accept defeat and assume something about this device and the current software / current versions of Google services just simply don't agree with my particular Google account for some odd reason. It does seem like it's something that will eventually settle on its own, seeing as how it kind of does already, though in a very annoying way (the waiting 24+ random hours for it to start working again). I'm hoping a future firmware update will eventually clear it up entirely.

But I also wanted to mention, since I believe no one has yet, that I was able to successfully install the Google Play System Update a few minutes ago. It oddly required an update/reboot that was literally only a few kB large, and then again at either 83 or 93 MB (exact numbers from memory, I forget which). After that 2nd time it says October 1, 2022 finally, instead of July. And this was with my phone in it's broken state. One weird thing was during the 2nd install, the notification jittered like it was having a seizure. Not sure if that's normal or again had to do with my phone being weird, but it was all fine in the end apparently. The jittering notification seemed to only happen as it was downloading, but was fine during installation, fyi, in case anyone else experiences the same thing. Just leave it alone.

Also unfortunately, it didn't fix my "special/unique" problem haha.

And last thing to mention, I noticed people mentioned the Huawei 6P thing - this happened to me too during one of my many factory resets, but I have no idea which one and just figured it had to do with my phone bugging out, so I didn't mention it. I probably didn't wait long enough to see if it changed back to P7Pro, but I can only say that my replacement has always reported correctly.
[Google Pixel 7 Pro] roirraW "edor" ehT:
@i5lee8bit, Thanks for updating again. I do hope your issue goes away sooner rather than later. I haven't had any reoccurrence of Chrome sync issues ever since 2-3 days or so after I got mine when it stopped having the issue.

I just now manually checked for the Play System Update. Previously, it had looked as if I had the update available, but I don't recall it giving a size, just said it was installed and had me reboot, but afterward, it still said July, so it was probably the common issue where it was telling people there was an update but many couldn't successfully install it.

Just now when I checked, I was still on the July, and it said there was a 62 MB update. I performed the update, rebooted, and successfully updated it to October. I haven't followed all the news on this too closely - I think I've seen the news that others had been recently successful, but I usually don't bother manually checking for any kind of updates unless there's a problem - which I very, very rarely have, luckily.

Screenshots for anyone below:

​
[Google Pixel 7 Pro] i5lee8bit:
Yup me neither, I usually just wait for notifications or automatic. But I figured on a long shot I could check to see if the update installs now (honestly, since I saw that update "bug" being a thing since the phones were released, I was really hoping maybe it was related to my problem somehow, haha). Oh well. The fact that the phone does go back into a working state eventually, does give me a big sparkle of hope it'll get resolved eventually. I wish I tried logging into an alt account with the exact same setup before sending the original phone back to Google. Unfortunately it's due in 2 days so I sent it back today. Ironically right around when my new one decided to crap out on me lol
[Google Pixel 7 Pro] simplepinoi177:
so after doing the Play System update, did anyone have any issues with passing SafetyNet?

There was a bug that wouldn't let our launch devices do the Play System update til now, so I don't think @Displax had to deal/consider it and how it might conflict with the P7P....
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yeah, I was hoping it would be the solution for you too.

No changes here after the update. YASNAC still gives me Pass, Pass, BASIC; and Play Integrity API Checker still gives me device and basic integrity.

GPay and Wallet aren't indicating any issue.
[Google Pixel 7 Pro] simplepinoi177:
Great! I'll go update it now after the reassurance...thanks as always!
[Google Pixel 7 Pro] SkylinesHD:
After rooting (or maybe after unlocking the bootloader, not sure), I'm missing the feature "Earthquake alerts" in the "Safety & Emergency" settings

Any idea, why it's gone?
[Google Pixel 7 Pro] wr3cckl3ss1:
Might be asking to the wrong crowd but does anyone know what any of these apps do or have any idea as to why Samsung apps would be on a Pixel 7 Pro. I'm real interested in the app called OEMDmTrigger. I dont know much about decompiling APKs other than running them thru apktool. And the one i did decompile was the Verizon API one which i believe does give alot of functions to how to carrier unlock a device. All the apps minus the API one were pulled from my VZW P7P. The API one I pulled from my already unlocked S22 Ultra S908U which is also from VZW. Any help or input would be greatly apreciated. And just to update on the whole removing the "com.google.android.apps.work.oobconfig" package, i removed it without having to follow the guide i had posted earlier in the thread and also remained carrier unlocked. Idk how it works but as long as you activate the device and keep it running for like a day or so, you can use simple ADB commands or use ADB App Control, to remove it. But be for-warned, what worked for me, might not for you. Proceed at your own risk. And if anyone has an idea about the APKs....shoot me a DM and I can send them to you. Thanks (see pics attached)
[Google Pixel 7 Pro] roirraW "edor" ehT:
You're right - I just checked and I don't have it either. I don't really know for sure mine was there before root and all, and I have no idea why it's gone. It could be due to @Displax Universal SafetyNet Fix v2.3.1 MOD 2.0. If you have that installed, try disabling that, reboot, and check to see if the Earthquake alerts are back.

If not, I'm out of ideas already except that maybe it's a Google bug and hopefully will be fixed with the next firmware update on the first Monday of the month (November 7).

You probably know this much, but the first one must have something to do with Verizon (even if you're not on Verizon, it's possible it would still exist), but otherwise, Samsung makes the CPU and other parts and I believe I saw in an article @Freak07 linked to in the [GS101|GS201] Google Tensor G1 and G2 In-Depth OP that said Google renamed/rebranded some Samsung resources but didn't rename others.

I can't guess anything more specific than that.

Thanks again for the information, and interesting. Good luck!
[Google Pixel 7 Pro] xtravbx:
Unfortunately, I don't pass CTS after the google play update.

Playing around with it now trying to fix it....
[Google Pixel 7 Pro] roirraW "edor" ehT:
If you were already on the Displax USNF v2.3.1 MOD 2.0, if you haven't already, I would try leaving the phone alone for hours or even a day and see if it fixes itself.
[Google Pixel 7 Pro] SkylinesHD:
I'm not able to see/use "Live view" in Google Maps (only the setting, but not in navigation) and GPS calibration by camera (only by compass).

I think this may be caused by the safetynet fix, someone else with the same issue?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Working here, I have USNF v2.3.1 MOD 2.0 installed and functioning 100%:
[Google Pixel 7 Pro] dd805bb:
What mod are you running for your status bar? NICE!!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks! @siavash79's thread [MOD][Xposed+Magisk][Pre-Release] AOSP Mods - System modifications for AOSP-based Android 12+

I LOVE this mod for many features.

Edit: Unblocked status bar here:
[Google Pixel 7 Pro] Superguy:
Understand, but I'm not wanting to wait 3 years to unlock a phone, or even a 45-60 days after I pay it off to unlock it.
[Google Pixel 7 Pro] xstefen:
May kill your cat

pantah-flashall.sh (linux/bash)

pantah-flashall.bat (windows/batch/untested)

based off upstream fastboot.cpp
[Google Pixel 7 Pro] SkylinesHD:
Which kernel are you running?

No matter what I do, it's just not showing..
[Google Pixel 7 Pro] xstefen:
Ive successfully used MOD 2.0 with stock rooted, Despair rooted, and Kirisakura rooted
[Google Pixel 7 Pro] simplepinoi177:
Just checked mine out and I don't have it either...!

no custom kernel, passing safetynet all but strong device, on Google Maps beta program, disabled "heads up", I've "uninstalled updates", I've turned off the systemless hosts and safetynet fix modules...

Just checked my rooted Pixel 5 (A11) and it doesn't have live view either...!

downgraded to Maps just before P7P released, no joy...

just checked my wife's P7P locked bootloader, hers doesn't have live view either....it might be a bug as it's not there on my Pixel 5 (rooted), hers (unrooted), and reverting back to release version & before. I didn't think of it, but maybe live view is server dependent and Google shut if off (hopefully temporarily).

One caveat is I personally set her phone up identically to mine, so I wonder if it's not something I inadvertently set up and isn't playing nice with whatever is causing the conflict...
[Google Pixel 7 Pro] wr3cckl3ss1:
Interesting. Think it'll work for a VZW device?
[Google Pixel 7 Pro] Lughnasadh:
Unlocking your bootloader is not illegal in the U.S.. In fact, Google provides instructions on how to do this on their download page.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Sony, too, allowed (I assume still allows) their bootloaders to be unlocked in general via an official smooth method - however, it would also permanently gimp your device in certain areas such as the camera. I don't remember if you could re-lock the bootloader on them, but even if so, the hardware gimping was persistent no matter what.

I could even still continue to get OTAs with the bootloader unlocked for a while, and then eventually they made it so you couldn't even do that.

I did notice within the past week or two, that at some point - I'm assuming after HTC stopped making phones, at HTCDev they made it so that you could officially unlock the bootloader of many devices, including ones that were previously only able to be bootloader unlocked with paid software by @jcase - which I had no problem with. I officially unlocked both of our old HTC 10s, and I was trying to unlock my Verizon HTC Droid Eris, which is on their list to be able to be officially unlocked, but perhaps mine isn't fully stock enough, so the first step isn't working, and I've Googled all to heck and couldn't find working links to the full stock RUUs for the Eris, except for maybe Android 1.5 and 1.6.
[Google Pixel 7 Pro] xdagee:
your link is not working...
[Google Pixel 7 Pro] V0latyle:
Fair warning, Canary 25204 breaks DenyList and USNF, and it doesn't appear to be possible to downgrade without reflashing the boot image.
[Google Pixel 7 Pro] Lughnasadh:
Working fine here. Are you clicking on the Reddit link and not that other link?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Working for me, too. Edit: Whoops, thought you were talking about my Twitter link. :D

Thank you! I'll add your comment to my post for FYI.
[Google Pixel 7 Pro] Ghisy:
You should click on the "Just got my 7pro" link. It works fine.
[Google Pixel 7 Pro] Lughnasadh:
There's already a Pull Request in for a fix and just waiting review. Looks like this 1 commit will fix it. Hopefully Canary 25205 will be released fairly soon.
[Google Pixel 7 Pro] xdagee:
seen;
[Google Pixel 7 Pro] xdagee:
Yeah, I remember, Sony too. I'm used too HTC with my development, Most of my development work has been with HTC.
[Google Pixel 7 Pro] EtherealRemnant:
I miss HTC phones.
[Google Pixel 7 Pro] Lughnasadh:
Canary Magisk 25205 is out. Denylist is working for me. Don't use USNF but I imagine that's working again as well.
[Google Pixel 7 Pro] V0latyle:
Yeah. And apparently, you can downgrade on the fly by using the Debug release, because debug doesn't check version:

Install debug app

Direct Install to update patch to debug

Reboot

Can now install older version of Magisk
[Google Pixel 7 Pro] xdagee:
Me too. They made the development process so much fun to work with. But these days, it looks like the OEMs are gearing away from developer-focused to a consumer-focused approach. I was hoping the Google Pixel's could have replaced HTC since Google purchased the HTC team, but it turned out to be different. Android modding and customization isn't as much fun as it used to be; the OEMs give us what they want.
[Google Pixel 7 Pro] EtherealRemnant:
That's because Google wants to have a walled garden to print them money like Apple does.
[Google Pixel 7 Pro] Reechings:
Running custom roms or modded stock was great on my Pixel 6 Pro and I'm going for more of the same on my 7 Pro when it arrives. The scene might not be quite what it was at one time but there's still fun to be had.
[Google Pixel 7 Pro] Larakali:
I got my Pixel 7 Pro rn.

What should i do to help here
[Google Pixel 7 Pro] Gordietm:
How did you root the 7 pro without a boot image?
[Google Pixel 7 Pro] Annie the Eagle:
Are you rooted?
[Google Pixel 7 Pro] Larakali:
I didnt yet. Its downloading an update that takes ages to optimize .-.
[Google Pixel 7 Pro] xstefen:
I have no clue. I've only flashed vanilla aosp build images with the bash script to my global unlocked cheetah. Let me know

Edit: it might be completely useless, I come from a long agonizing stay with 1+ where fastboot scripts were very handy. And with all the disable-verity talk happening I sort of made this out of habit lol
[Google Pixel 7 Pro] wr3cckl3ss1:
If you were in my position. Which way would you go?
[Google Pixel 7 Pro] xstefen:
Whatever happens should be easily recoverable so if u don't mind a wipe I see no harm. What do you intend to flash? Trying unlock trick?
[Google Pixel 7 Pro] wr3cckl3ss1:
right now...yes. i was able to get this pixel carrier unlocked by VZW and it still leaves OEM with connect to internet. And VZW is good as they unlocked it sometime in the middle of the night and i could catch a logcat of it to catch their functions, which would of been great and another tool to help in this case.
[Google Pixel 7 Pro] wr3cckl3ss1:
might try swinging thru a GSI
[Google Pixel 7 Pro] SkylinesHD:
Seems like I'm not the only one with the problem. ( @simplepinoi177 also has it )

I'm trying to troubleshoot it, but I really have no idea. I even tried changing the fingerprint and disabling all modules.

Which apps do you have in the denylist? Do you use shamiko or something like that?
[Google Pixel 7 Pro] roirraW "edor" ehT:
It's still early enough in the morning, and I've hardly touched my coffee so far. What is the context/potential use of these? By your second post quoted here and taking a look at the .bat in my sandbox virtual PC, do I understand correctly that they're just meant to make it easier to flash some custom ROMs, partition by partition?

I'm on the stock .031 rooted kernel. Verity and Verification are not disabled.

It shouldn't even hardly get far at all on a Verizon device, so it shouldn't cause any harm at all. At the very first line:

fastboot --disable-verity --disable-verification flash --slot all vbmeta vbmeta.img

It should give you an error since you can't flash partitions with a locked bootloader.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Glad it's solved for now @simplepinoi177. And thank you for the details!
[Google Pixel 7 Pro] SkylinesHD:
Thank you soo much for sharing your experiences!!

I just checked Google Maps again, and for me, it also just came back out of nowhere. Seems like they changed something on their side.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yay!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Updated my Post #3:

A list of other important apps

: - be sure to thank the respective OPs:

Here's the Magisk section of XDA's forums, for rooting. Magisk on GitHub.

@kevin@TeslaCoil's section for Nova Launcher / Nova Launcher Prime - been using this since early 2012!

@jorrik98's thread [Themes / Apps / Mods] Better Internet Tiles - Bring back Wi-Fi and mobile data toggles! (non-root)

@VR25's thread Advanced Charging Controller (ACC)

AccA (Advanced Charging Controller App)

@siavash79's thread [MOD][Xposed+Magisk][Pre-Release] AOSP Mods - System modifications for AOSP-based Android 12+. This is a big one for me, personally.

@Quinny899's thread [APP][ROOT][11+][19/07] Classic Power Menu - Power Menu Replacement w/ Wallet, Controls on Android 11, 12, 13+

Swift Backup

@j4velin's thread [APP] Wallpaper Changer - been using this since mid-2011!

@Jawomo's thread [Themes / Apps / Mods] aodNotify - Notification Light / LED - see my post in that thread here for the proper offsets to use the front camera notification circle on the Pixel 7 Pro.

@Jawomo's thread [APP] dynamicSpot - iPhone 14 Pro Dynamic Island for android!

and will update the thanks list in the OP to reflect these.
[Google Pixel 7 Pro] SOCOM-HERO:
fastboot flashing unlock command is not doing anything on my device. I confirmed drivers are up to date with both adb and fastboot mode, OEM unlocking and USB debugging are both enabled. Any help would be appreciated.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Did you install/update the drivers not just when Android was running (for use with ADB), but also when you have the phone in the bootloader mode (fastboot)? While the phone is in bootloader mode (fastboot), can you take a screenshot of your Windows Device Manager screen?
[Google Pixel 7 Pro] Lughnasadh:
Try a different cable and port. USB 2.0 preferably, and A to C cable. Also make sure you are using the latest Platform Tools (I wasn't sure which drivers you said are up-to-date so I'm throwing this in here just in case.)

Also, are you getting an error of some sort?

EDIT: Just saw your screenshot so never mind about the Platform Tools. However, also try command prompt instead of PowerShell.