Changed my device fingerprint using Props Config module of Magisk. Passes all safety net tests in the magisk app, used another safety net tester and also got certified on play store. But this only lasted a day.
The next day, I check if it stills works in magisk app, but sadly it shows safety net api error, turns light red and has failed both cts profile and basic integrity. Also, another safety net tester app I used failed too. Play store certification wasn't visible now.
I waited, thinking if the safety net api qouta was exhausted, as I read on some article on Google.
After waiting for some hours, play store and another safety net tester app I used has passed and certified. But the magisk app remains unchanged.
Anyone has any idea what is going on?
Related
So, PayPal and android pay finally integrated. And the only way that the integration will show up in either app is to have play services version 11.0.56. *pic below* However, this update is only supposed to be available to certain parts of the US currently I guess as it was just released about a week ago and they want to soft release.
After I did initial research, I found that I could simply download the updated play services and install. Which worked great initially. (everyone without integration capabilities should be on version 10.x.xx)
Got it set up and properly situated, while on WiFi. Kind of ignored the Google play services won't run unless you update(downgrade) it notification. *pic below*
Went to the store to realize I have no data capability on my phone. Tried just about everything so far besides downgrade because I want the integration.
So to my question vvvvv
*Does anyone know if Google play services/framework is capable of blocking all data traffic? *
Because it still shows I have great data connection(as I use the tmobile lte booster and always have good in home data. Testes with another phone to make sure booster isn't messed up) , but any app I try to use that is connected to Google play, does not have a connection. But everything works perfectly over WiFi
UPDATE: Went to remove my Google account to add it again. Upon removing Google account, sim status shows absolutely no service now
Also, I am on Tmobile
-pulled sim out and back and showing service again. But still not able to access any app connected to play store
Double Update-
**Solved**
For some reason it stopped dns capabilities of ipv6. Which is weird given the apn has been running ipv6 stock in the apn from tmobile... So i switched to my apn which is ipv6/ipv4.
Just still not sure what happened there to make that issue
after getting the update from one plus for 6T to android 10.3.0. the play store pops up say "device is not certified" now I cannot use Google Pay. Is there any way to fix this
My phone is a T-Mobile to International Conversion no root or bootloader is lock
From my understanding I'm in the same boat, the only fix I see in other forum's is rooting, or waiting for TMobile to put out a10. Which will probably take along time
This has been answered many times.
To be certified by Google, the ROM digital fingerprint must be communicated to Google by the manufacturer.
As you have modified your device by installing an OOS designed for another phone (yes technically global OP6t is a different phone compared to TMob one), there is a mismatch in parameters transmitted to Google leading to a non certified device.
The only solution is to root and use a Magisk module to modify your phone digital fingerprint towards a recognized one. (Magiskhide props config)
Complaints are to be addressed to TMobile.
Is this still an issue? I'm rooted and use Magisk to certify but I can't play games like Mario Tour and I'm considering going back to stock.
Striatum_bdr said:
This has been answered many times.
To be certified by Google, the ROM digital fingerprint must be communicated to Google by the manufacturer.
As you have modified your device by installing an OOS designed for another phone (yes technically global OP6t is a different phone compared to TMob one), there is a mismatch in parameters transmitted to Google leading to a non certified device.
The only solution is to root and use a Magisk module to modify your phone digital fingerprint towards a recognized one. (Magiskhide props config)
Complaints are to be addressed to TMobile.
Click to expand...
Click to collapse
I just wanted to say thank you for sharing this.
I know these types of things are shared in many places, but unfortunately its hard to figure out where to look sometimes. So thanks for being redundant it was helpful!
Until february i used my lepro 3 with Gpay and NFC also worked for paying.
Now i cannot add NFC to Gpay anymore, it says the phone has maybe changed or rooted. (it is still on stock FW)
When i look in playstore the phone is not certified for playprotect (i dont remember if it was before)
Can anyone tell me if he is using his lepro 3 with gpay and does NFC still work?
Is the phone certified for play protect?
Anyone facing this problem? My google pay is inconsistent when on public transport and in retail stores.
Could it be software issue?
Can you type Oxygen version, root or no? And can you find in Google play settings certification of you device?
alf_and_co said:
Can you type Oxygen version, root or no? And can you find in Google play settings certification of you device?
Click to expand...
Click to collapse
Also having problem with my NFC with public transport.
Never work for public transport before, but ok with retail payment
my is Oxygen OS 10.5.10.IN11AA, no root.
not sure if this is the Google Play Cert
Version 20.6.19-all [0] [PR] 316598174
OOS 10.5.10.IN11AA
Google Play Services Version 20.21.17
Google Pay Version 2.111.306
I tried toggling on the '' non standard NFC tag support '' in developers option. Doesnt work as well.
Many op8p users also faced the same problem in my country.
Tried re-adding my cards several times, cleared cache of google pay,google play services,google framework.
Downgrading app versions.
On public transport, my phone just vibrates and will prompt " does not work " or " move closer ". Never worked, receiver receive nothing.
In retail payment, it worked about 90% of the time with 10% requiring to tap twice.
I have similar issue.
- I use polish banking application that uses NFC for contactless payment.
- In retail payment, 90% of the time is successful, 10% requires to tap again.
- In vending machine almost every payment is rejected (I got 1 successful payment but I can't reproduce it again). I used same banking application on my xiaomi mi8 with same vending machine and worked good.
- I tried google pay and it doesn't work too (at least it shows some error on screen)
- no root, oxygenos 10.5.9.IN11BA
In conclusion it's not a problem with google pay but with nfc as other payment apps have same problem.
IIRC on the teardown video, the NFC chip is in behind the camera. It's maybe in too deep inside the phone for it to work correctly everytime.
Sent from my IN2023 using Tapatalk
Came looking to see if I was the only one with an NFC issue
Mine has been working perfectly since I got the phone, then yesterday I went to use it at a POS in a shop and it wouldn't work......move closer/slower etc. so I used my bank card itself.
I got the train and said I had low balance when I got off so went to top up my leap card (Irish transport card) and it fails the second it tried to read the card.
FYI I have sucessfully topped up my leap card dozens of times on the phone.
Next I went to get something to eat. I tried using it at the restaurant POS and worked first time, no problem.
Then this morning I just tried using it in shop POS and everytime it pinged and gave me a tick mark and showed the card as if it completed OK but the shop unit did not register anything (I also know the transaction did not go through as revolut did not show the transaction). I used my bank card and it worked.
I have just tried my leap card again and it is still not working.
This is very frustrating as I use NFC payment everywhere.
Anyone know if I can see logs for the NFC chip?
Why did it suddenly just stop working, I haven't had any updates.
Running Oxygen OS 10.5.12.IN11BA
Play services Version 20.33.14(120400-327249014)
Google Pay Version 2.116.328438545
Not had this problem before, could your case be the cause? Or anything else in your hand?
The range has impressed me with mine.
Currently rooted and using xXx and Gpay is still good.
It looks the oneplus 8 pro nfc chip is very weak. For me the strongest signal is under oneplus logo on the back. I found out the nfc chip is under the keypad at vending machine (not under display). Now to make it work I must keep my phone very closely to the terminal.
I need to get close on a number of NFC readers...no biggie.
GPay is working in my watch, for now atleast. I've seen an xda developers post where someone got it working (https://forum.xda-developers.com/t/guide-gpay-in-unsupported-country-yes-india-too.4262597/ )
So I've been scratching my head since, then sadly thay method didn't work. It's saying that gpay is already installed on my watch, tried abd to remove it and it didn't work. So I've reset the watch and while setting it up, I switched on vpn on my phone to us. And guess what it worked and Gpay showed up in the app drawer. Tried to set the card up and it actually worked, but in the middle it asked me to choose my google account, it kept loading, so tried turning off vpn and now it's working flawlessly. Some times when i open gpay it says not available in your location. Then I've connected it to my phone with BLUETOOTH, not wifi mind me, with vpn connected and after sometime again it is working. It is working after a reboot too, hope it stays that way. And I've tried to make a payment at a supermarket and it worked. Looking forward to use to more often. And i forgot to mention that I've updated all apps through PlayStore and still it didn't disappear, but i got a system update and didn't update yet thinking it might disappear.
I'll update the thread if something happens. Peace