GmsCore: SafetyNet started failing
Somewhere around friday morning, SafetyNet started failing (CTS Profile match: false, but Basic Integrity: true). I have not changed anything on my device (OP5T, OmniROM, no root or whatsoever) between the time it worked and the time it stopped working, and I’ve tested on my old phone (OPO) on which it does not work either (but I had to reinstall on OmniROM on it and it has also Basic Integrity: false).
Is anyone else confirming? If not, what should I look for? If yes, I suppose this is due to some DroidGuard update that now detects μG?
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 70 (38 by maintainers)
@ale5000-git could you close this issue? It’s about the old bug fixed by https://github.com/microg/android_packages_apps_RemoteDroidGuard/pull/19
CTS Profile is the extended check. If you’re on a Galaxy device with unlocked Bootloader, that will trip KNOX and thus CTS Profile match fails as the device is seen as tinkered. So that is not an issue, but the correct result.
The only way around this is Magisk.
@jimbo1qaz you mean LineageOS for microG 14.1 (Android 7.1), right? I’m still curious if this is working for someone on LineageOS 14.1…
Could this be a reason? Google Play Certification
You have
scontext=u:r:untrusted_app:s0:c512,c768instead I havescontext=u:r:priv_app:s0:c512,c768Try to put both microG GmsCore and DroidGuard Helper in /system/priv-app to fix it. Also in yours I see
advice":"RESTORE_TO_FACTORY_ROM"probably for the same cause.If it still do not work try the official LineageOS (without microG) and then a flashable microG zip.