Thanks for pointing out. Will have it added.
1 Like
Xiaomi MI8 1.20-t-20240222382228-dev-dipper
Edit : I also have the problem @mossroy is talking about, after two attempts, the SafetyNet test fail, and i have to restart the phone to make it pass again.
I see the same behavior (SafetyNet Test passes, then after a few other runs, it fails consistently). And on several different devices: FP3, FP5, SM-P610 (Samsung Tab S6 lite), SM-G900F (Samsung S5)
Steps to reproduce:
- Restart the device
- Run app “SafetyNet Test”, and click on “run test”. Test passes
- Do it a second time. Test passes
- Do it a third time. Test fails
- Do it again an again. Test always fails
Similar behavior with YASNAC app: first 2 tests succeed, and the following ones make the app crash.
Restarting the device is a workaround.
It looks like a bug, so I created https://gitlab.e.foundation/e/backlog/-/issues/7874 with some detail
SM-P610: 1.20-t-20240222382228-dev-gta4xlwifi
FP5: 1.20-t-20240220382010-stable-FP5
FP3: 1.20-s-20240220382012-stable-FP3
SM-G900F: 1.20-r-20240221382014-dev-klte
Can confirm successful passed safetynet test on Samsung S5 Galaxy (klte) running e.os 1.20-dev.
Initial check on FP2 was successful:
Subsequent tests after 2 or 3 retries start to fail as on other decices.
According https://developer.android.com/privacy-and-security/safetynet
Avertissement : L’API SafetyNet Attestation est obsolète et a été remplacée par l’API Play Integrity. En savoir plus.
.
Samsung Galaxy s4 (jfltexx)
with setting OFF
.
Samsung Galaxy s4 (jfltexx)
with setting ON
Today I can confirm successful passed safetynet test on Google Pixel 3a (Sarge) running e.os 1.21-t-dev (unrooted).
1 Like
Just saw this update on the compatibility list.
Why do we need to use these tools to know if device is rooted, etc.?