Google Play Protect certification lost? Can't use Google Pay. - LG V35 Questions & Answers

Hi folks,
LM-V350AWM here running flashed Pie (V350AWM20d). Haven't tried to root, flash modded boot.img, anything. For a few weeks after flashing Pie, Google Pay was working just fine. Now in the last week my device has lost its Play Protect certification (which prevents me from using Google Pay). Nothing has really changed software-wise.
On my old G6 we had root and TWRP so Magisk could just trick the SafetyNet check, but I can't think of any reason why the certification would be lost with neither. Possible interference with Blokada's "VPN?"

I and my friend with LG V40 have the same problem! If you can find the solution please post it here.

Same here.

Bumping, anyone figure out a fix?

Related

Safety.net Issue on Pogo

Hi, since 2 days they've been an update in the safety.net detection from google. I cannot log in pokemon go anymore. My configuration is 8.2.4 global, phone is not root, just unlocked, i had installed before superSu and Magisk. Has some people here recorded having the same problem ? Do you have some idea on a way to fix it ? My safety.net was not passing but the game was working, i have cts profile mismatch and basis integrity false.
You need to lock your BL for pass safetynet, or use Magisk and bypass It

[Q] H870DS failing SafetyNet API checks

Hi everyone,
I have a LG G6 (H870DS/SEA) and it's a great device. Even better with Oreo, now the device doesn't have the problems we've had on Nougat.
Let me tell a quick story about security and this device. I've upgraded officially (using LG Bridge) to Oreo one month ago, I think. Everything worked at the time: my bank account, Pokémon GO (which uses SafetyNet) and every single application that depends on device certifications.
Recently, after seeing so many posts about the new ThinQ features, the bright camera mode and the rename, I decided to flash the CIS firmware using LGUP and UPPERCUT to make the G6 detectable by LGUP. No problems, SafetyNet was indeed working at the time (attested using Pokémon GO).
After some time w/out using the device, I decided to go back and use it. Yesterday, I tried to open my bank application and it failed several times with the same error code. I thought that it was some kinda of problem with my account, but then I realized that SafetyNet problems actually does the same things when the CTS profile mismatchs or something else prevents SafetyNet to be attested.
With that in mind, I decided to install a "SafetyNet checker" and see what was actually going on. Boom. SafetyNet failing multiple times. It says my device doesn't support SafetyNet (which is a lie, IMO). Initially, my thoughts were that, upon flashing the CIS firmware, something broke and SafetyNet end up broke. Tried to flash the last SEA firmware, no luck. Tried to revert back to the original SEA Oreo firmware (which I flashed the CIS firmware on top), no luck at all.
Apart from my bank application, Pokémon GO and any application that eventually uses SafetyNet for security checking, everything else works. I just don't know what happened with this, as I don't know if my device is still "official" or a red bright light was powered during the flash process (which, IMHO, I doubt, otherwise I'd have seen this on the start).
At this point, I think I'm stuck into this unless a bootloader unlock comes along sometime (this is not impossible, but let's keep hoping for now) and Magisk + its modules are activated in order to hide SafetyNet approval.
TL;DR:
- My phone is failing on every SafetyNet test and I just don't know why;
- It runs official firmware. However, it went through LGUP flashes 2-3 times now;
- There are no root or bootloader unlock methods to this specific model, so there were no unofficial modifications whatsoever;
- The problem started recently, as the SafetyNet depended applications seemed to work after the first flash;
- The first flash actually changed the region (SEA>CIS), so I just don't know if this is the real problem or this is just an unfortunate coincidence;
- I just reverted the phone to its normal region (SEA), and it keeps failing;
- According to multiple SafetyNet checkers, it just says it's uncompatible and tells something about an empty payload. Neither the CTS profile is available;
- Just in case, if someone wonders about the versions I've used until now, the order of the flashing process is:
SEA Nougat -> SEA Oreo (LG Bridge) -> CIS Oreo (LGUP+UPPERCUT) -> SEA Oreo (20C/LGUP+UPPERCUT) -> SEA Oreo (20A/LGUP+UPPERCUT)
If this problem is also happening with someone, or happened to someone else and eventually had a fix, please show the way. If you had the problem, please answer the questions below:
- Have you ever used LGUP with this device? If yes, which firmware did you flash?
- There was a region/carrier change? (eg.: SEA -> CIS, CIS -> EUR, TIM BRAZIL -> BRA and so on)
- SafetyNet dependents were working after the flash?
- Did you wipe your device after the flash? (if you've answered "yes" to the first question).
Thanks in advance.
Mr. I.
(PS: this is NOT a thread to ask for a bootloader unlock. Please don't answer this just to ask for a solution to this. Thanks!)

CTS profile mismatch, is it possible to fix it for stock without Magisk?

Hi all!
I decided to go back from ArrowOS Pie to stock 8.1. I used this procedure and a POTTER_RETAIL_8.1.0_OPSS28.85-17-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip file from here. Everything is great, even Netflix is accessible via Google Play, but device from Google Play perspective is still uncertified. Safetynet check says there's CTS profile mismatch, therefore Google Pay won't work.
Is there any way to fix this without unlocking the bootloader again and applying Magisk? I heard that ROM files Motorola vendor uses for flashing their devices could help, was any version of it released or leaked for potter?
Thanks for any suggestions!
K

Google Device

I finally installed 10.3.0, rooted, and am using the SafetyPatch module to bypass Safetynet on my OnePlus 6t T-Mobile phone converted to International.
Now my Google account show shows my device as Huawei P20 Pro. How do I change this?
redcodefsu said:
I finally installed 10.3.0, rooted, and am using the SafetyPatch module to bypass Safetynet on my OnePlus 6t T-Mobile phone converted to International.
Now my Google account show shows my device as Huawei P20 Pro. How do I change this?
Click to expand...
Click to collapse
Under some circumstances it is necessary to change the "fingerprint" of your device to appear as if it is another device in order to pass CTS.
... Oddly I too had problems with Safety net when first flashing over to 10.3, I got lost in translation somewhere because after re-flashing it a few times with both the local upgrade method and TWRP now it passes Safety-net by default, no extra Magisk module necessary.
I am rooted without TWRP, last time I tried going through TWRP but it flashed on both partitions and I lost My OS.

SafetyNet Pass?

Hello!
I am using a T-Mobile device converted to the newest Open Beta. Before, I converted it using the method which does not require a bootloader unlock; however, my device wouldn't pass Safetynet and I couldn't use Google Pay or download Netflix from the Play Store. Now, I've unlocked the bootloader, rooted my device, tried to use Magisk Hide and my device still doesn't pass Safetynet. It says "cts profile : false". Can anybody help me? What apps do I need to hide Magisk from? Are there any modules that can help with this? I would really like to be able to use Google Pay and be on Android Q, but I don't want to be stuck waiting on T-Mobile to roll it out.
Use magisk module called props to pass safety net

Categories

Resources