- Oct 10, 2016
Not. It's been extensively discussed.
Hints to search and read: TEE = Trusted Execution Environment.
Particularly, if you 'fix' that for the last TItan, you could ask for 250K - 1.5M $ reward from Google
Not. It's been extensively discussed.
I've posted some information about Play Integrity MEETS_STRONG_INTEGRITY being akin to SafetyNet Evaluation type HARDWARE with CTS Profile match, but since it became a WOT, I put it here:
Apparently not because many peoples confirmed using Wallet by passing only DEVICE, not STRONG
SafetyNet per se is not relevant for Wallet but Play Integrity.I just updated to Android 13 final on my Pixel 5, and now Google Wallet won't work.
It was working fine on 13 Beta 4 though, and Safetynet passes.
Safety Net Request: success
Response signature validation: success
Basic integrity: success
CTS profile match: success
I already had the USNF 2.3.1 module. As I said - it was working yesterday, now no longer working.
Primarily Wallet. Maybe Services Framework. Less likely, Play Store - Play Services is relevant
Out of interest, can we assume you mean you do have @Displax USNF 2.3.1-mod (modified USNF), not official @Kdragon USNF 2.3.1 module?... It would be surprising if the latter fixes Play Integrity w/ Android 13... (I don't need the modded version w/ my Android 10 device however.)... PW
OH. I am using the official one. (I thought you meant module)Out of interest, can we assume you mean you do have @Displax USNF 2.3.1-mod (modified USNF), not official @Kdragon USNF 2.3.1 module?... It would be surprising if the latter fixes Play Integrity w/ Android 13... (I don't need the modded version w/ my Android 10 device however.)... PW
I always thought that messing with GSF changes the primary ID by which Google knows the device. As far as the servers are concerned, said device was basically factory reset. There are many downstream effects of this, but a major one is that this invalidates the tokens used by any app that uses GCM
Hoping push messaging is still working okay for your apps after clearing Google Services Framework, otherwise you'll need to wipe all the affected apps too.
Hm, i hab tried this.. No luck this time. Any idea what I am missing? Google Play Store shows that the device is certified.Have you done/tried the following:
1) toggle magiskhide on
2) added com.google.android.gms.unstable to MagiskHide list (or Deny List in latest Magisk versions)
3) hide (rename) magisk app (from Settings menu)
4) Clear data of affected apps:
5) Test Google Pay
- Toggle Airplane Mode on
- Clear data and cache of:
- Google Play
- Google Play Services
- Google Pay (Warning: this will remove any card and loyalty cards present - you can try without, but is recommended)
- Usually this will be achieved by (exact steps and terminology may change per device or ROM):
- Opening Settings
- Going to Apps, choosing Show All Apps
- Enabling Show System Apps via a menu option
- Locating the app, tapping it and then finding Storage/Cache
- Tapping Clear Data
- Reboot and then Toggle Airplane Mode off
- Open Google Play Store, wait 5 minutes, go to Settings and check Certification at bottom
Well I went and made a new bank account added the new card to gpay and it works fine. Still can't set up the old card... seems like my device is on some sort of blacklist with the old bank.not saying its this, but just for sharing...
but back in my pixel days, about 3 years ago, when i was routinely testing (flashing) 2-4 ROM's a week, i did have a GPay failure that rendered contactless broken. Contacted bank...nope no issue there. Contacted Google via web...yup my account had gotten garbled by too many GPay setup requests from my bank Took them 24 hours to turn around on that one
aka when (too much) ROM flashing goes wrong
only time it wasnt something i could fix with a wipe
Whenever I come to XDA and ask a question I'm normally receive a really unhelpful reply, along the lines of "if you search you will find your answer" This is can be very annoying, especially after I have spent an hour looking and I still can't find the answer? Hence the reason I ask a question.
The reason I say this is because I have got Google wallet working and I will share what I did.
1. Uninstalled Google wallet
2. Deleted both cache and data from play store
3. Updated Xprivacy Lua
4. Reinstalled UNSF
5. Changed fingerprint using su / props
6. Restarted phone
It is pertinent to say here that I fail all api integrity checks using the app on playstore. However Google wallet contactless payment works better than before.
I will keep this updated if I have as any issues.
... And with @Displax USNF_mod it is not needed even for ROMs not passing CTS Profile match (China region, Beta, Developer, many custom ROMS) in most cases. (There may rare be exceptions where this modded module doesn't work.)
The app is running on a device that has signs of attack (such as API hooking) or system compromise (such as being rooted), or the app is not running on a physical device (such as an emulator that does not pass Google Play integrity checks).
If you are having problems with your testing device meeting device integrity, make sure the factory ROM is installed (for example, by resetting the device) and that the bootloader is locked.