yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] jhjhjhjhjhjh:
Yep opened up camera app im on Beta 14 3.1 and an update notification popped up now macro enabled.. update from playstore version 8.9
[Google Pixel 7 Pro] Fishawy:
Thanks for that. Same here.

Weird how this update is only prompted from within the app. Play Store wasn't showing any update available.
[Google Pixel 7 Pro] synesthete:
That is weird. I hadn't checked the play store since earlier today, so I wasn't sure if it had been available there or not.
[Google Pixel 7 Pro] xdrc45:
Thanks! That worked for me too
[Google Pixel 7 Pro] roirraW "edor" ehT:
@Displax has updated Universal SafetyNet Fix Mod to v2.4.0 Mod 1.3 on XDA (and on GitHub, linked to in the XDA OP, as well).
[Google Pixel 7 Pro] Ghisy:
Nice but I don't see any changelog, even on GitHub?
[Google Pixel 7 Pro] synesthete:
It is hidden in the spoiler tag:
[Google Pixel 7 Pro] GuyInDogSuit:
So, browsing through this thread regarding my incoming new T-Mobile P7P arriving later today, would I be correct in assuming that the device would need to be carrier-unlocked by T-Mobile before I could unlock the bootloader? No way around it?

The only other promising info was from post #917 by @wr3cckl3ss1.

This guide linked in the post does state that the OEM unlock option will still be grayed out, so that gives me the impression that it's not going to circumvent the waiting period.

I don't mind not being able to root it, but I've seen some pretty interesting mods that do require Magisk and whatnot.
[Google Pixel 7 Pro] roirraW "edor" ehT:
That's correct. You have to pay off the T-Mobile device or let them know that you're going to be visiting another country and require a permanent SIM unlock so that you can use a SIM card from elsewhere. SIM unlock is different than bootloader unlocking, but in this case (not all), if you achieve permanent SIM unlock on a T-Mobile Pixel, then it will allow you to enable bootloader unlocking.

Since I don't have a T-Mobile device (I have a factory unlocked one direct from Google), I can't speak to the methods the user mentioned in the post you linked.

But definitely also correct, if the bootloader unlocking toggle is grayed out, then you can't enable the toggle, so you won't be able to unlock the bootloader.
[Google Pixel 7 Pro] GuyInDogSuit:
I've managed to do the second option (visiting another country) with a OnePlus phone before. It was surprisingly easy to convince them since the phone was barely a week old, but considering I've been a long-time customer, not really, I guess. I suppose I should try that again, especially IF what I read about the dual-SIM capability is true. I likely won't be able to use my Lifeline SIM in it without SIM-unlocking the Pixel first. Then again, that line uses Verizon, so I'm not sure. Was looking into switching from SafeLink anyway, as their service blows. /shrug
[Google Pixel 7 Pro] GuyInDogSuit:
{Mod edit: Quoted post has been deleted. Oswald Boelcke, Senior Moderator}

What?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Verizon June Factory Image:

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com
[Google Pixel 7 Pro] justDave:
Why?
[Google Pixel 7 Pro] TotallyAnxious:
Sometimes the updated configs for carriers aren't sent to Google in time for an update so they release another firmware that has those new configs, once Google gets them.
[Google Pixel 7 Pro] supermansaga:
Can 26102 and Displax 1.3 take care of the new Pixel Tablet? Anyone knows? Thx
[Google Pixel 7 Pro] roirraW "edor" ehT:
It looks like the answer to that is in the Google Pixel tablet section:

https://xdaforums.com/f/google-pixel-tablet.12745/

Good luck, and have fun with your new device (assuming you got one)!
[Google Pixel 7 Pro] roirraW "edor" ehT:
The above are from the Android 14 Beta 3.1 thread.

Has anyone else had experience with needing this Magisk Module in order to pass certifications?
[Google Pixel 7 Pro] rester555:
What kind of certifications? Can you provide an example?
[Google Pixel 7 Pro] roirraW "edor" ehT:
The kinds that are normally passed in the following apps by either an unrooted (and possibly non-bootloader unlocked) device, or rooted but with successfully working mitigations (Universal SafetyNet Fix / Mod).

I wasn't sure if anyone had found it necessary to use the "safetynet sensitive props by huskydg" Magisk Module on Stable Android 13 on the Pixel in order to pass, or if it has only been limited to Android 14 DP/Beta users, as far as Pixel users are concerned.
[Google Pixel 7 Pro] synesthete:
I don't use that module and currently pass two of the 3 tests. Is the module supposed to allow you to pass all 3? Google pay and Google VPN work.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Same here on 13 Stable June, using USNF v1.4.0 Mod 1.2, although 1.3 is available.

I don't believe so.

I interpret @gpvecchi's remark in my Android 14 Beta thread (quoted in my post #2,614 above) as meaning they couldn't pass the normally passable (with a USNF Magisk Module) two certifications until they used that Magisk Module - or at least pass one of the two.
[Google Pixel 7 Pro] synesthete:
Ah okay. I'm on the latest stable Android 13 June update with USNF 2.4.0-MOD_1.3. I haven't had any problems.
[Google Pixel 7 Pro] simplepinoi177:
I can reaffirm +2 (from my two P7Ps) that I've had the same outcome/experience as @synesthete. Stock ROM Android 13 June. Nothing more needed than Displax's mod and regular ol' denylist.
[Google Pixel 7 Pro] Schroeder09:
Did anyone's battery life increase by 36% and 2hrs SOT from the June update?
[Google Pixel 7 Pro] Ghisy:
Has anyone else been having their Play Store misbehave recently on the P7P?

Since yesterday, whenever I update my apps, it just freezes. If I FC it, the downloads resume. I tried clearing data+cache, updating to the latest version available on apkmirror, same thing. It's really annoying...

(P7P, June update, Kirisakura kernel, Play Store version is 36.3.12-29 [o] [PR] 54203371)
[Google Pixel 7 Pro] roirraW "edor" ehT:
No issues here. Most of the time, I let auto-update do its thing whenever it feels like it, but I just manually checked for updates, there were 30 available, and 8 have installed fine without any problem so far.

I'm on P7P, June Stable update, no custom kernel, Magisk Stable 26.1, Play Store version 36.2.11-29 [O] [PR] 539142984. Manually clicking "Update Play Store" says "Google Play Store is up to date". Google Play System update was May 1, 2023, but manually checking prompted me to Restart to update, but still says May 1, 2023 after rebooting. All apps are up-to-date now, so nothing else I can check.

Hey! Off-topic, but clicking "Play Store version" in the App 10 times enabled "Developer". I have no idea where this "Developer" is. I'll have to Google later.
[Google Pixel 7 Pro] Lughnasadh:
Developer Options are under the "General" category in the Play Store settings. From there you can enable "Internal app sharing" and check your Play Integrity status.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks! Cheers.
[Google Pixel 7 Pro] Lughnasadh:
No problem! I should mention that that's where it is located on A14B3.1. On A13 it might have been a slightly different setup/location.
[Google Pixel 7 Pro] Ghisy:
Oh, didn't know about this developer mode either! Thank you!

I'm also rooted with the same version of Magisk. Same version of the Play System too.

I just uninstalled updates for the Play Store and will let it auto-update. I never had this freezing issue before. Not sure where it comes from.
[Google Pixel 7 Pro] supermansaga:
Probably because Tensor G2 sucks.
[Google Pixel 7 Pro] WhoIsJohnGalt1979:
Fixed. Music doesn't stop when phone screen is off through UAPP dedicated mode through USB DAC. Now we will wait for next month's update for Google or UAPP to mess it up. Witnesses!!
[Google Pixel 7 Pro] Ghisy:
Yeah, same thing. I can't figure out what's going on with the *** Play Store! :/
[Google Pixel 7 Pro] hpower1:
monthly update done again (June 2023), magisk 26103, using platform tools v33.0.3, no issues. Thanks to all for keeping this thread updated with useful info.
[Google Pixel 7 Pro] Ghisy:
Play Store is back to normal today! Go figure! 🤷‍♂️
[Google Pixel 7 Pro] roirraW "edor" ehT:
New ACC release https://github.com/VR-25/acc/releases

@VR25's thread Advanced Charging Controller (ACC)

Although I've been using CrazyBoyFeng's ACC Settings instead of AccA or just ACC.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yay, after 3.5 years, I can finally set reminders by voice again in the car (they show up as Tasks now, but I can still say "Set a Reminder for half an hour from now to tell Google to fix this."), after so many complaints and feedback filed with Google, and across four different devices, three of them Pixels.

Edit: Honestly, who knows when they started working again. After trying every so often over that long a period of time, I got tired of trying, and had been setting calendar events instead.
[Google Pixel 7 Pro] pp085ster:
I got a notification yesterday that there had been some changes to the way the assistant works, it now uses the phone's mic for voice commands instead of using the mic of whatever Bluetooth device is connected. For me it's fixed one of the most frustrating issues that I had, which is that whenever I connected my Bluetooth headset and started playing music, it would skip/stutter for like 30sec before playing music smoothly - apparently this was related to the assistant (if disabled it would play music smoothly from the get go). That issue now seems to be fixed (finally!!)
[Google Pixel 7 Pro] reaper000:
And here's the corresponding Magisk 26.1-rooted init_boot.img for convenience sakes
[Google Pixel 7 Pro] GuyInDogSuit:
I've found that filing bugs or feedback, and expecting any sort of updates or fixes, let alone a response, is about as effective as beating a dead horse. I'm shocked something like your case was ever even fixed. Even though it just sounds like an unintended "bonus" from a new feature/change.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Absolutely. I have no doubt that the fact it's working now is a fortunate accident, and I know Google could taketh away any moment, again. :)
[Google Pixel 7 Pro] GuyInDogSuit:
Hopefully that won't be the case.
[Google Pixel 7 Pro] roirraW "edor" ehT:
They finally moved 34.0.1 release notes above the never-existed 34.0.0 RC2. Still no 34.0.3 notes. Of course, in five minutes, someone at Google could re-reverse the release notes, as I've seen that happening with some of Google's pages every once in a while, like two people are editing the same webpage at the same time, overriding what the other editor is doing. 🤷‍♂️

SDK Platform Tools release notes | Android Studio | Android Developers

Android SDK Platform-Tools is a component for the Android SDK.

developer.android.com

NEW version of release notes:

OLD:
[Google Pixel 7 Pro] Gordietm:
Has anyone tried 34.0.3 yet?
[Google Pixel 7 Pro] badabing2003:
avoid it if you can, 33.0.3 is solid
[Google Pixel 7 Pro] esjames:
Well, I think I hit the verizon jackpot! I'm on build # TQ3A.230605.012.A1 (Verizon/NVNO) and I am able to unlock my bootloader.
[Google Pixel 7 Pro] supermansaga:
Hello. What's the so-called Magisk canary custom update channel url? Experimenting how to do that on a windows 11 with MagiskOnWSALocal. Thx
[Google Pixel 7 Pro] GuyInDogSuit:
Early bleeding-edge builds. Use at your own risk.

Also, not sure what WSA has t o do with this guide?
[Google Pixel 7 Pro] supermansaga:
This guide has helped me with MagiskonWSALocal on Github. Now I can run Android 13 supposedly on a Win 11 PC, though it remains a pixel 5 not pixel 7 pro and can't pass safetynet. I am grateful, but I digress and apologize
[Google Pixel 7 Pro] simplepinoi177:
Just wanted to confirm....you have a Pixel 7 Pro purchased from Verizon/Verizon-variant, took the OTA, and now you can unlock your bootloader?????🤨🤨🤨🤨🤨
[Google Pixel 7 Pro] esjames:
I purchased it from visible and is financed. Just made my first payment, maybe that's the difference?? Dunno but visible is owned by Verizon.
[Google Pixel 7 Pro] roirraW "edor" ehT:
If you want to, you can verify whether or not it's considered a Verizon variant:

https://www.reddit.com/r/GooglePixel/comments/89tf9g/_/hk31jky

I used this method once when I bought a used Pixel that I couldn't enable OEM unlocking - it was supposed to be a Google Edition (factory unlocked) but was a Verizon Edition.
[Google Pixel 7 Pro] jhjhjhjhjhjh:
I have a Spectrum/Verizon model thanks for ths tip,

I entered my imei # and no mention of Verizon..yes im happy now if i want to root i can unlock the bootloader..yay...again great tip

..:)
[Google Pixel 7 Pro] esjames:
It comes up a as a FI model.

I guess they don't lock their devices down out the gate.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yep, Google Fi Pixels, as far as I know, are always the "Google Edition" factory carrier unlocked model. Obligatory, "Your Mileage May Vary". :)
[Google Pixel 7 Pro] flesheatingbeatles:
Greetings awesome xda-developers contributors,

I have an unlocked Pixel 7 Pro on TQ1A.221205.011, bootloader unlocked, and I have several questions.

Should I skip magisk on this build and sideload an OTA image and magisk the updated build? A better question is: am I at risk of running into a brick if I do so, depending on the build I chose? Or should I work in steps to the most recent build per directions I've seen here?

If I sideload one of the following will I have to unlock the bootloader again? Am I at risk of achieving an unlockable bootloader just for having touched a Verizon build? Like a disease?

There are two images for the most recent build. TQ3A.230605.012 (global?) and TQ3A.230605.012.A1 (Verizon and VMNOs). Since I want to continue with Verizon service the latter would be in order it seems, unless it could be problematic (as above) and should be avoided.

Will I have enhanced service due to specifics in the latter build or will those be for Verizon phones which have Verizon specific radio bands and my phone doesn't have them?
[Google Pixel 7 Pro] GuyInDogSuit:
Holy Q-and-A session, Batman!

I didn't know that bit about how updates would usually hit around the first Monday of every month, so that's good to know.
[Google Pixel 7 Pro] roirraW "edor" ehT:
LOL!

Cool. FYI, occasionally Google will delay a month's release by days or even weeks - and they either never or nearly ever announce that it's going to be delayed, although from memory, it sometimes leaks out why it was delayed at some point - either that, or we guess it's because of some huge vulnerability-of-the-month or bug which was recently discovered (and they wanted to fix before release).

So, you can expect the monthly stable firmware updates the afternoon of the first Monday of every month, but when it doesn't, don't worry - it'll come out when it's ready.

FYI, I always announce in this thread (and edit the thread title) when new Stable firmware comes out.

Normally, the latest ADB/Fastboot (SDK Platform Tools) is the best to use, but all the v34.x.x versions of it have had one bug or another. The very latest is less buggy than the previous, but we all highly encourage you to use the known, good v33.0.3, which @Namelesswonder was kind enough to link to five months ago (February). Also quoted below. Yes, we've had buggy versions that long, and yes, Google has been told the latest version is still buggy. :(

And I know this is all a lot of information to digest, but keep in mind that when new firmware comes out, it's common that eventually an old version of the Platform Tools will no longer work to flash the new firmware, but that hasn't been the case yet, with Platform Tools v33.0.3.

Hopefully, Google debugs the Platform Tools completely and makes another release before Android 14 becomes stable in another month or so, but I'm not going to hold my breath.

If you ever want to be cautious when a new update comes out, just either wait for users in the thread to volunteer the information that they updated to the new firmware successfully with X version of Platform Tools, and rooted with Y version of Magisk, or ask if no one happens to mention those items.
[Google Pixel 7 Pro] supermansaga:
Hello, I received a blackmail from a johnblue@1077.com. Should I blame the rooting? The guy is stupid to leave his wallet address. I don't mind being a porn star. He said he used so-called drive by exploit
[Google Pixel 7 Pro] LLStarks:
Just ignore it. It's a very old template threat. Guy has absolutely nothing on you and the exploits mentioned do not exist.
[Google Pixel 7 Pro] synesthete:
Just got a notification to update to the latest feature drop, but I'm not seeing it on https://developers.google.com/android/images#cheetah yet. I'll be keeping an eye on the factory image page so I can update with root.

EDIT: July factory images are now up on the Google Developers site.
[Google Pixel 7 Pro] ScottHW:
My P7P updated over the air, so I need to restore root access.

I downloaded the newest factory image ( cheetah-tq3a.230605.012.a1-factory-170d1863 ), extracted into folder w/ platform tools.

Modified flash-all.bat to NOT wipe.

Running the script flash-all.bat seems to work fine; phone boots up.

Extracted the init_boot.img file

Used Magisk to patch it

Tried to use fastboot flash init_boot magisk_patched-26100_DcOWL.img

Phone goes into a bootloop

I can get out by running flash-all.bat again. Several attempts have given the same results.

Any thought? Help is much appreciated.
[Google Pixel 7 Pro] roirraW "edor" ehT:
What version of Magisk?

Edit: Also, it updated OTA to what version of the firmware?
[Google Pixel 7 Pro] roirraW "edor" ehT:
No July Stable firmware yet, but this is updated:

Pixel Update Bulletin—July 2023 | Android Open Source Project

source.android.com
[Google Pixel 7 Pro] ScottHW:
Magisk v26.1

Went to Build Number TQ3A.230605.012.A1

I checked "Android version" before going to the Google stock firmware download page.

Edit: Well... hmmmm.... I guess I can't find a screenshot to confirm that it actually did OTA update to the .A1 version. I did NOT buy this phone from Verizon, and don't think I had Verizon firmware previously....

Maybe that is my problem ?
[Google Pixel 7 Pro] Lughnasadh:
Maybe you have a Magisk mod that needs updating???
[Google Pixel 7 Pro] supermansaga:
But they have my phone number and email. This is disturbing... Appreciate the insight
[Google Pixel 7 Pro] roirraW "edor" ehT:
Any official Google firmware for your device will be interchangeable with other versions with the same device from the same month (or as an update from any previous month on any firmware). That is, using Verizon firmware on a non-Verizon Pixel won't cause any issues. The firmware changes are optimizations to work with that particular carrier.

If you're using Verizon as a carrier, that's why you got the Verizon OTA. There was no May Verizon firmware - only Global. You can change back to Global, although you'll keep getting OTAs unless rooted with the Developer Options toggle for automatic updates turned off - although Google is able to force updates through regardless, which they do on rare occasions when they think it's important.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yes! Good point!

@ScottHW, see

Find problem apps, Magisk, and LSposed Modules by (three different methods)

in the third post of this thread.
[Google Pixel 7 Pro] Lughnasadh:
Links are up 👍
[Google Pixel 7 Pro] roirraW "edor" ehT:
July 2023 Stable firmware:

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

Google Pixel Community

Edit 3: NOW, the July page at this link is present:

Android Security Bulletins | Android Open Source Project

source.android.com

Edit: Ninja'd. :D
[Google Pixel 7 Pro] roirraW "edor" ehT:
@flesheatingbeatles, July firmware is out. See post above ^ . :)
[Google Pixel 7 Pro] roirraW "edor" ehT:
NOW, the July page at this link is present:

Google Pixel Update - July 2023 - Google Pixel Community
[Google Pixel 7 Pro] madmuthertrucker:
I would say triple check that you are using the right init_boot.img. I have put the wrong one in and it bootlooped on me.
[Google Pixel 7 Pro] ScottHW:
@Lughnasadh and @roirraW edor ehT nailed it;

I've been struck by 👏 👏

I've been struck by a smooth Module

I used Safe Mode to disable all Magisk Modules, which thankfully pulled me out of the bootloop.

Then re-enabled one by one; took several rounds of falling back to Safe Mode.

DisableFlagSecure v7.0 by @mehedihjoy seems to have been the cause of the problem.

I wrote my post #184 over on that thread.

Hopefully they can get it sorted out. I just found that module recently and it restored a root capability via XPosed/LSPosed that I had appreciated.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Glad you got it solved. @Lughnasadh definitely deserves all the credit to think to suggest that possibly being the issue. I'm too tired today to think myself out of much of anything. 🤣

Edit: And thanks for sharing the details, and for reporting the issue in the module's thread.
[Google Pixel 7 Pro] Fishawy:
Still A13? Any heads up or just BAU via PF?
[Google Pixel 7 Pro] GuyInDogSuit:
lmao, now I've got that song in my head.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yes, Android 13. Android 14 is still in Beta. Beta 4 and/or any release candidates still haven't been released yet.

I don't know what those are, sorry.
[Google Pixel 7 Pro] Fishawy:
Apologies, Business As Usual via PixelFlasher :D
[Google Pixel 7 Pro] supermansaga:
I successfully updated to 0705, but my Google play system update remains on May 1.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Ah! Thank you.

I like the manual method. 😁
[Google Pixel 7 Pro] Homeboy76:
Did you disable/remove the modules before you patched the init_boot.img?

Flash the init_boot.img:

fastboot flash init_boot init_boot.img
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yep, they solved it (no, they didn't disable the Magisk Modules). It was a Magisk Module, as @Lughnasadh had suggested they check:
[Google Pixel 7 Pro] Homeboy76:
:oops: My apologies @Lughnasadh, I didn't see your reply.
[Google Pixel 7 Pro] roirraW "edor" ehT:
We all do the same thing from time to time. I've definitely tried to help someone who already solved their issue before. 😁
[Google Pixel 7 Pro] rester555:
Is platform tools still an issue? Still only using 33.0.3? Has anyone tried July build with the newer platform tool and root with 26.1 magisk?
[Google Pixel 7 Pro] Fishawy:
I just played it safe and used 33.0.3 with the latest PixelFlasher. Updated and rooted with Magisk 26.1 Stable. No issues.
[Google Pixel 7 Pro] synesthete:
I used platform 33.03, Magisk 26.103 and the latest stable July build with no issues.
[Google Pixel 7 Pro] rage302:
...same here! :cool: (Pixel Flasher on Windows)
[Google Pixel 7 Pro] GuyInDogSuit:
Yeah, mine too. No new updates to install, either.
[Google Pixel 7 Pro] Fishawy:
Sideload "Main Components" app from ApkMirror. You will have the July security patch.

Fun story: I've had the July patch since 16-Jun. No joke. 🤷🏻‍♂️
[Google Pixel 7 Pro] JakeDHS07:
It's been discovered that those only change the numbers displayed and don't actually contain any of the substance of the actual updates from what I remember
[Google Pixel 7 Pro] TotallyAnxious:
You are correct. "Main Components" just changes the reported date. Doesn't include the mainline modules meant to go with that updated "Main Components".
[Google Pixel 7 Pro] reaper000:
Anyone desiring root on the July 2023 Verizon build, here's your magisk-patched init_boot.img...
[Google Pixel 7 Pro] Ghisy:
Look at that: Google releasing an update (almost) on time! 👏

Tonight is update night then!