yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] ljubo87bg:
Maybe a stupid question:

I purchased the device from Telstra, but I haven't updated the firmware since November and now I can see there is a specific Telstra version. I'm not sure what the difference is. Any idea anyone? I also want to know if it would work if I flash the universal image on this device, not the Telstra-specific one. Would I have to do some extra/different steps?

Thanks in advance to anyone that puts in the effort to answer a noob.
[Google Pixel 7 Pro] Fishawy:
I'm not sure about going from Telstra to Univeral on Pixels. Used to do that normally on OnePlus (EU to Global and vice versa). My P7P - also in AU - is unlocked and not carrier-linked.

Does your build have specific Telstra mention in the name? If so, I would assume safety and go ahead with the Telstra build. Or alternatively, you can let the device update noramlly if you're not rooted.

Hope the more Pixel-experienced members here can assist you further.

P.S.: I LOVE how you're been on here since 2008 and this is your first post! :D
[Google Pixel 7 Pro] ljubo87bg:
Thanks for the quick reply Fishawy! Doesn't say anything about Telstra in the build name or anywhere in Settings apart from the SIM info, but I rooted it on the day it came, so no updates for me :D I'll wait for someone more Pixel-experienced to chime in... just in case :)

P.S.: That year only shows when the forum needed an account to download an attachment..... I wasn't even a developer back then... I've been here forever, just never had a question that wasn't answered. That speaks well about my search skills I reckon :P
[Google Pixel 7 Pro] Fishawy:
Indeed it does! 14 years no questions, amazing 😄

If no Telstra, then I would use the Global build, but that's just me. You should wait for others to confirm though.

You also might wanna take a look at the Pixel Flasher tool, which can be found in a separate thread on this forum. Makes flashing a lot easier with less room for error, which is handy for a Pixel-beginner like myself.
[Google Pixel 7 Pro] Ghisy:
Yup.

Not on my P7P. Everything is fine (see screenshot).
[Google Pixel 7 Pro] Schroeder09:
Do this again for February?
[Google Pixel 7 Pro] Skysurfer77:
EDIT: Seems that I'm not alone:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/page-149

Hi all,

for me it is the same. Update via PixelFlasher and root directly with it. SO smoothless!!

But now Google Wallet is not working again, also Netflix is not viewable in Play Store. (Both are hints that there are problems with SafetyNet.

Checked with YASNAC App:

Model

Pixel 7

Android version

13 (API33)

Security Patch Level:

2023-02-05

Google Play Services version

23.03.13 (190400-503260631)

Result

Basic integrity

Pass

CTS profile match

Fail!

Evaluation type

BASIC

Magisk App is hidden and Denylist ON
[Google Pixel 7 Pro] Ghisy:
Have you checked if your Play Store is certified? (Settings/About). If it's not try clearing data for it and check again, it should be certified now. (keep in mind you'll have to define your settings again for the Play Store).
[Google Pixel 7 Pro] Schroeder09:
the part about defining settings is key!! I almost always forget that I have to turn auto updates off after doing this. It will inevitably update my revanced-patched youtube or other modded apps (themed apps, etc!), and cause an hour of pain to correct it.

Don't forget to re-setup your settings in play store!
[Google Pixel 7 Pro] V0latyle:
Better idea to use Play Integrity Checker to determine device state. While Play Store will show "Uncertified" without MEETS_DEVICE_INTEGRITY, it's possible to pass this while still failing BASIC_INTEGRITY. You must pass both in order to use apps like Wallet and GPay.
[Google Pixel 7 Pro] Wmateria:
It's because the recent Wallet update somehow denies Magisk even if you are Magisk Hide or usingg SafetyNet. YANSAC may say every thing is alright, but Wallet stops working on either January or February patchw. Download the January 13 version of wallet.APK @ the APK pure website and it should work.
[Google Pixel 7 Pro] NippleSauce:
I have resolved this issue on my end. First, try connecting to any WiFi network and sending an RCS (text) Message to someone else with Android and RCS. If it doesn't work over WiFi, then you are having the same issue that I was having.

Essentially, the Google Messages RCS "Chat" services did not set up properly on the February update - as for the first time, it asked me if I wanted to enable that setting during the new update's initial start-up. Unfortunately, it only tried to set-up "Chat" over WiFi, however, this service NEEDS to be set-up over cellular data. But once it fails once, it refuses to try again and stays failed forever, and thus, the RCS messages will still work - but will only work over cellular data (which is a way for you to identify if you've run into the same issue).

Anyway, to resolve this issue, open the Messages app and navigate to its settings page. Then, disable "chat features". Next, turn off WiFi on your phone. Then, completely close out of the Messages app. Then, navigate to its app info page, press "Force Stop" and then clear its cache and data (your message history is stored on your Google account - so you won't lose it - so no worries there). Immediately after doing this, restart your phone. Then, once it boots up again, open the Messages app and navigate back to its settings menu and enable the "chat features" setting. This time, with it setting up "Chat" over cellular data (since your WiFi is disabled), it will setup properly and successfully (this will take around 5-10 minutes and you will get a notification once it fully sets up the feature). And once it is fully and properly configured, you can then turn WiFi back on and your RCS Messaging will work over WiFi again - as it should!

But here's the funny part. I was failing the YASNAC check as well. But after resolving this RCS Chat issue, I ran YASNAC again and had passed every safetynet check, haha. Now, my GPay setup works without issue. So, there is a great possibility that anyone facing issues with GPay or GWallet on the February update is facing this issue due to the new RCS Chat setup feature at boot failing to properly configure the chat services setting.

Why this is causing a safetynet issue - I do not know lol.

Anyways, my apologies for the lengthy post. But lemme know if this helps - as it resolved the issue for me!
[Google Pixel 7 Pro] Skysurfer77:
Thank you all for your messages. My Play Store Version is now 34.3.18-21 [O] [PR] 507552939

I deleted Cache and Data and rebooted, At the moment there is no sign if of device certification. I'll wait until it comes up and than decide what to try next if it fails.
[Google Pixel 7 Pro] meinlet:
Hello everyone,

here my bizzare issue with P7P.

I installed feb update and after that i couldnt pass integrity check.

I have installed Safetynet 2.4 and force denylist on, i tried to disable every magisk module and after countless reboots nothing.

So i decide unistall magisk and unroot to do everything from scratch.

After unroot (unistalled magisk and flash original init.boot.img) i recheck integrity with YASNAC etc and still can't pass the ckeck, wtf? Just to be clear right now i am rootless and still can't pass integrity checks.

Any suggestion?
[Google Pixel 7 Pro] Schroeder09:
how'd you update? did you use pixel flasher and maintain root? did you dirty flash with the traditional ADB commands? If you did this did you try maintaining root?
[Google Pixel 7 Pro] meinlet:
Through ADB commands, I didn't maintain root.
[Google Pixel 7 Pro] Schroeder09:
and this was dirty flashing (remove "-w" from the flash-all.bat file)? Do you have the verification flags disabled for a custom kernel?
[Google Pixel 7 Pro] Ghisy:
Something like this I guess? https://play.google.com/store/apps/details?id=gr.nikolasspyr.integritycheck&gl=US
[Google Pixel 7 Pro] meinlet:
Yes, I removed -w from bat file. Don't know about flags im not using custom kernels.

FYI i re-root and I still can't pass integrity checks but banks apps work fine, Netflix doesn't even let me find it in play store.
[Google Pixel 7 Pro] V0latyle:
Yep, that's what I use.

A locked bootloader on stock firmware should pass all 3.

An unlocked bootloader will always fail STRONG integrity but you can use USNF 2.3.1 MOD with Magisk to pass BASIC and DEVICE, which should be sufficient as nothing uses STRONG.
[Google Pixel 7 Pro] roysun:
This may be a dumb question, but I'd rather ask it than find out the hard way that I shouldn't try it: can I dirty-flash (ie, "remove -w") the January update over the February update to go back?

Basically, it sounds like Google is playing with new ways to detect root, and CTS checks are failing intermittently at the very best for everyone on the February update (https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/page-148). Based on that thread, a solution could be a long ways away.

I was on December, I flashed February, now I want to go back to January or December without wiping data. Safe?
[Google Pixel 7 Pro] Schroeder09:
Why the hell are they doing this? They're gonna make android another iphone and destroy their own product. This seems like a solution in search of a problem. Are there really many users using root who are losing their bank accounts and personal data BECAUSE they're rooted?
[Google Pixel 7 Pro] Pixel86:
Hiding the MAGISK app worked for me on the February 2023 update. Hide the app , then reboot.
[Google Pixel 7 Pro] vurtomatic:
Hi @V0latyle I was using v2.4 by kdragon because the update showed up in Magisk.

I just installed v2. 3.1 MOD that you linked, but I'm failing the Play Integrity API Check for Device Integrity. Is that normal? Pass Basic Integrity. Should we stick with 2.3.1 or update to 2.4?

YASNAC shows pass for Basic Integrity.

Wallet launched without root warning. Play Store shows device isn't certified. (I cleared data/cache for Wallet and Play Store.)
[Google Pixel 7 Pro] V0latyle:
I'd try removing the module completely, rebooting, then installing it again. Use USNF 2.3.1 Displax Mod 2.1.

Play Store will show uncertified if you're not passing DEVICE_INTEGRITY
[Google Pixel 7 Pro] Lughnasadh:
Seems like Google has been playing some shenanigans this morning. You may have to also hide the Magisk app (and reboot) to pass Play Integrity.
[Google Pixel 7 Pro] Bxperiaz3:
Not meeting device integrity as of this evening.

Magisk hidden

Shamiko

Enforce deny

Displax usnf

Anything else I can try? It's been perfect up until today. January build p7p
[Google Pixel 7 Pro] EtherealRemnant:
Interesting. I don't meet device integrity either, just checked, but my Wallet is working fine.

I'm also on the beta which I didn't think suffered from this issue but apparently does. *shrug*

Glad that I got this here Samsung Galaxy Watch 4 Classic because I'd be pissed if my tap to pay stopped working suddenly. Don't have to worry about it anymore since watch isn't rooted.
[Google Pixel 7 Pro] Josh:
Same for me, Google wallet work fine and bank app but meet device integrity not pass .on latest February build but on beta before works fine.
[Google Pixel 7 Pro] roysun:
Magisk was already hidden for me, but for fun I unhid and rehid and rebooted. No change. Based on the other thread I referenced, this is a new issue and doesn't behave consistently: sometimes the safetynet check comes back okay, and sometimes it doesn't. I've run it several times in a row and gotten different results.

Rebooting usually gets you a good YASNAC result for a minute or two. If you run the Play Integrity API Checker, you'll likely see it failing "MEETS_DEVICE_INTEGRITY" every time on the February update - I have, and that seems to be the recurring theme in the Magisk thread I linked to.

If anyone out there knows the answer to my original question, I'm still keen to know: can I safely dirty flash back to an earlier release? ie, from February back to January?

I'd rather go back to a working version and wait this one out; it seems like a gong show right now. It will work for folks for a few days and then suddenly, Play Store is uncertified and Wallet stops working.
[Google Pixel 7 Pro] iTudorS:
Im still on January update, didnt get february yet, everything was working fine untill today, I tried paying with wallet, and It would not work.

checked YASNAC, CTS profile doesnt pass, reboot phone, CTS passes, wait 1 min, CTS doesnt pass, random results.

Tried everything except wiping the phone, which I refuse to do.

nothing seems to work.
[Google Pixel 7 Pro] vurtomatic:
That still didn't work unfortunately 😔

Uh huh, my Magisk is already hidden (renamed).

This Feb update is a bummer.

From what I'm reading in the USNF thread, it's Google messing around.

At least—fingers crossed—my banking apps, Ticketmaster, are working.
[Google Pixel 7 Pro] stroke55:
I assume that it won't have any effect. I'm still on the December build having the same issues.
[Google Pixel 7 Pro] JakeDHS07:
It was an update to GPS. It's unrelated to what build you're running.
[Google Pixel 7 Pro] schmeggy929:
Those that are failing MEETS_DEVICE_INTEGRITY. Go back in Magisk, Settings Configure DenyList. Then click 3 dots(top right) and check Show system apps. Check everything that has Google in the package name. Then open Google Play Store, settings and About and check for Play store update. Finally open Wallet and check Integrity.

These steps worked for me. I open Wallet, asks for fingerprint and completes no problem.
[Google Pixel 7 Pro] HerrGordon:
Didn't make any difference here. Still fails device integrity. :(
[Google Pixel 7 Pro] roirraW "edor" ehT:
@Displax Universal SafetyNet Fix v2.3.1-MOD_3.0 on GitHub - I haven't followed if the changes are applicable to Stable Android as well, or if they are geared towards DP1. I'm also not sure I can find @Displax' sub/temp OP in @kdrag0n's Universal SafetyNet Fix thread.

Edit: @Displax's XDA OP here.
[Google Pixel 7 Pro] JakeDHS07:
Still failing device integrity. Urgh I got excited for a second there.
[Google Pixel 7 Pro] JakeDHS07:
Working build of safety net fix is now posted 🤘

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/post-87198517
[Google Pixel 7 Pro] vurtomatic:
It works. Meets Device Integrity, added credit card back to Wallet. Fingers crossed no more issues.
[Google Pixel 7 Pro] xdrc45:
Can confirm this is working on my P7P. Thanks for sharing.

I did have to clear cache for Google Play store and play services for Yasnac to pass
[Google Pixel 7 Pro] x111:
just got "TQ1A.230205.002" update and double tap to wake on lockcreen again doesn't work !!

Google, cammon fix this already, we need a native double tap to wake feature !!
[Google Pixel 7 Pro] synesthete:
There is a setting tap to wake to lock screen setting in Settings > System > Gestures > Tap to check phone. Is that not sufficient for you purposes?
[Google Pixel 7 Pro] x111:
not sufficient, it must be double tap to eliminate accidental wake.

also, I meant to say that double tap to lock on lockcreen doesn't work again.

on top of that, there is still no solution to disable screen wake on charging, discharging.

highly annoying.
[Google Pixel 7 Pro] iTudorS:
this worked like a charm, that was a fast fix!, was about to wipe the phone and start over from the desperation, but this fixed everything, wallet works added the card back and all good!
[Google Pixel 7 Pro] Skysurfer77:
Cat and Mouse game...

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/page-91#post-87198517

Installed this: safetynet-fix-v2.3.1-MOD_3.0.zip

Reboot

Then flight modus ON and deleted Data and Cache from Play Store, Play Protect and Google Play Services...

Flight modus OFF

After a few minutes... et voila

Is working again!
[Google Pixel 7 Pro] oko17:
So with having now safetynet-fix-v2.3.1-MOD_3.0.zip, it's safe to flash the February Image to Pixel 7 pro?
[Google Pixel 7 Pro] re_endymion:
Like Skysurfer77 said, with the latest safetynet-fix-v2.3.1-MOD_3.0.zip, it works for me!
[Google Pixel 7 Pro] oko17:
Thanks!
[Google Pixel 7 Pro] SchmilK:
I tried everythign yesterday on the 2.4 versions and couldn't get tap to pay to work and had to resort to sticking a card in a reader *eww*

This morning I installed that, rebooted and tap to pay worked with no additional intervention or cache cleaning! Magisk app wasn't even hidden :)
[Google Pixel 7 Pro] Nekromantik:
2.4.0 is broken for Google Wallet and needs fixing

Use Disaplex MOD
[Google Pixel 7 Pro] NippleSauce:
Hey all! This an edited version of my previous comment - where I was rather (unnecessarily) angry. So, my apologies there =/.

In the end - what I should have said - was that I think that I found a solution to that safetynet pass failure that many of us have been experiencing since flashing that February update. I believe that my possible solution comment is 2 pages back from this comment =). If anyone could please give that a shot and write back as to whether or not it has helped to resolve their safetynet problem, that would be great - as that is what fixed the problem for me =D.

Anyways, my apologies again for what I had written. I feel rather bad about it now =/

But also, I have to send a HUGE thank you to @roirraW "edor" ehT for helping me to realize that I was acting out of place. I have a brain issue nowadays and occasionally do not realize when I'm stepping out of my own shoes.
[Google Pixel 7 Pro] T.A.R.D.I.S.:
Hello

Flashing february update, root with Magisk, Lsposed with Themer and Aosp mods and it works fine.

No issue with AOSP mods and Themer.

No issue with my french banking app with USFN 2.4.0 (i don't use Google Wallet). So, i don't try with 2.34 as others guys!

There is always an issue with Font Manager : app banking is crashing, as with December and january update.

Continuing to test my device.
[Google Pixel 7 Pro] OzBoy1:
Maybe, just maybe, they were composing their messages while the solution was being posted, therefore they would not have seen the post before.....maybe!
[Google Pixel 7 Pro] NippleSauce:
My apologies. I am having a bad day today.

But I would imagine that users would check back to a thread after commenting on it if its recent topic has been to discuss the problem that they are experiencing.

But anyway, I just want someone else to try that method, haha. It is literally what resolved the problem for me and I hope that I didn't just get extremely lucky, haha. Because if it is what is causing the problem, then the implementation of that new "Activate Chat features" option that appears after first booting into the February build is what is possibly causing it.
[Google Pixel 7 Pro] roirraW "edor" ehT:
ADB/Fastboot (SDK Platform Tools) updated to v34.0.0, as @Lughnasadh hinted we would be getting soon.

No changelog at https://developer.android.com/studio/releases/platform-tools yet - I'll update when it has.

Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip

Mac: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip

Linux: https://dl.google.com/android/repository/platform-tools-latest-linux.zip
[Google Pixel 7 Pro] Schroeder09:
These weren't required to install the Feb update though right? These weren't available a couple days ago when everyone was flashing the Feb update. I'm guessing we're better suited to use them though if we haven't flashed yet?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Correct. I updated to February yesterday (finally) using 33.0.3.

It shouldn't hurt anything to use 34 for the February Stable update. It's possible that 33.0.3 would no longer work with any updates that come out after today. I wouldn't expect any difference, but I always use the very latest available to flash, so even though it won't make any difference, yes, I'd use 34 if I hadn't already updated to February.
[Google Pixel 7 Pro] EtherealRemnant:
It's usually going to be many months to years even before Google deprecates old features and forces people to update platform tools. Doesn't hurt to keep them up to date obviously (barring any unexpected bugs anyway) but it's not generally been a case of you being forced to update right away.
[Google Pixel 7 Pro] roirraW "edor" ehT:
SDK Platform Tools release notes | Android Studio | Android Developers

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

developer.android.com
[Google Pixel 7 Pro] Zizzl:
Thanks. I updated to platform tools 34.0 and had big issues in flashing the February image with the Pixelflasher. It ended up in a corrupted device / bootloop. Though it must have been something with the image but had the same error on January image which I tried as a fallback... Went back to platform tools v 33.0 and now everything is working again: February image successfully flashed with PixelFlasher.
[Google Pixel 7 Pro] pp085ster:
For the Font Manager issue, I use CFI with AFDKO (Download link for CFI flashable script) and am using a custom font without any issues for many months now.

Here's @nongthaihoang explanation as to why custom fonts create issues.

Hope it helps!
[Google Pixel 7 Pro] T.A.R.D.I.S.:
Thanks!! I'll follow your advice and try CFI 👍
[Google Pixel 7 Pro] Ghisy:
Good thing I was on 33.0.3 when I updated to February. Seems like the newest 34 version of platform tools is problematic...

I'm staying on 33.0.3 for now!
[Google Pixel 7 Pro] JakeDHS07:
I wonder if they are even aware yet that the new release is broken
[Google Pixel 7 Pro] roirraW "edor" ehT:
@Schroeder09, see the posts above about people having trouble using Platform-Tools v34.0.0, so better to stick with 33.0.3 for now after all.
[Google Pixel 7 Pro] roirraW "edor" ehT:
@Displax Universal SafetyNet Fix v2.4.0-MOD_1.0 on XDA or GitHub - besides the single fix listed in this version on GitHub, this should take care of Fox's Mmm (Magisk Module Updater) from popping up that there's a new version of USNF, since @Displax' 2.3.1-MOD_3.0 is considered older than @kdrag0n's official v2.4.0.
[Google Pixel 7 Pro] Displax:
There is new post :)

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/post-88132825
[Google Pixel 7 Pro] Lughnasadh:
@Dave_247 created an issue about the apparent bug in Platform Tools 34.0.0. Suggest people go there and +1 and/or comment to grab Google's attention so they can fix it.

Thanks for opening up that bug report Dave!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thank you very much!
[Google Pixel 7 Pro] rester555:
Knowing 34.0.0 platform tools has a bug. Has anyone flashed February update with 33.0.3?
[Google Pixel 7 Pro] badabing2003:
Yes, and it works.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yep, many people have, including me, since 34.0.0 wasn't out when I flashed the February firmware.

@Displax Universal SafetyNet Fix v2.4.0-MOD_1.1 on XDA or GitHub.
[Google Pixel 7 Pro] Lughnasadh:
Platform Tools 33.0.3 also worked for me when flashing A14 DP1 (Pixel 6 Pro) as well as QPR2 Beta 3.1 (Pixel 7 Pro).
[Google Pixel 7 Pro] Namelesswonder:
Anyone that updated their platform tools and needs to downgrade can use these links.

Windows

https://dl.google.com/android/repository/platform-tools_r33.0.3-windows.zip

Mac

https://dl.google.com/android/repository/platform-tools_r33.0.3-darwin.zip

Linux

https://dl.google.com/android/repository/platform-tools_r33.0.3-linux.zip
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks! Added to the OP and to my 6 Pro thread/OP.
[Google Pixel 7 Pro] Fishawy:
If it can be added to the OP here as well, with a note about the problematic 34.0.0, it would be really appreciated.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I already had, but thank you! I also just now put the links to 34.0.0 in a spoiler warning not to use them.
[Google Pixel 7 Pro] Jon8RFC:
Oops, nevermind. Sorted it out. Was using v33.0.0 instead of v33.0.3.