microG support
j0110 opened this issue · comments
Hey there,
Thanks for your work!
I found that latest release (2.4.0-MOD1.3) fails to pass safety net (both CTS and basic integrity) while version 2.3.1-MOD3.0 do successfully the job.
Is there any particular reason?
Thanks !
Same here! I use a Poco x3 Pro with LineageOS 19.1 (Android 12L) latest build and only 2.3.1-MOD3.0 works for me. Have tried all releases but no success.
Same here , Not working with latest module or any module except with 2.3.1-Mod-3.0
Same here , Not working with latest module or any module except with 2.3.1-Mod-3.0
Do not use microg
@j0110
@AndiDink00x
Do you also use microg?
Yes, it is a problem?
Yes, it is a problem?
Yep, use normal GMS.
@Displax im using microg , the question is why does work with gms and not with microg ?
@j0110
@AndiDink00x
Yes, that is the problem. Just use normal GMS.
Anyway, could you send your logcat during trying SN/PI tests with latest MOD and getprop command?
@Displax
using latest release
@AndiDink00x
Do not use termux for log, use adb or separate programs to grab logcat.
Can you confirm that v2.3.1-MOD_3.0 works good?
And please test if v2.3.1-MOD_2.1 work/not work?
@AndiDink00x
@j0110
Yes, both work.
@Displax yeah both versions work for me also
@AndiDink00x
@j0110
Try this build
safetynet-fix-v2.4.0-MOD_1.3-microG-test.zip
It works !
@AndiDink00x @j0110
Try this build safetynet-fix-v2.4.0-MOD_1.3-microG-test.zip
@Displax Yeah it works !!!
EDIT : Microg SN fails (integrity check failed) but YASNAC test passes ... also after some quick retries YASNAC crashes.
EDIT (2) : it seems that it is not stable , in SN history in microg shows that also YASNAC fails after couple retries thats why it crashes
OK, same for me in fact
@AndiDink00x
@j0110
So, same problem not happens on v2.3.1-MOD_3.0 ?
@Displax its stable on 2.3.1-MOD_3.0
@AndiDink00x
@j0110
Strange... We just got basic integrity and after 2-3 tries it crashes as before...
@AndiDink00x
@j0110
New build
safetynet-fix-v2.4.0-MOD_1.3-microG.zip
@AndiDink00x @j0110
Try this build safetynet-fix-v2.4.0-MOD_1.3-microG-test.zip@Displax Yeah it works !!!
EDIT : Microg SN fails (integrity check failed) but YASNAC test passes ... also after some quick retries YASNAC crashes. EDIT (2) : it seems that it is not stable , in SN history in microg shows that also YASNAC fails after couple retries thats why it crashes
Same as this, for the new build.
Same as this, for the new build.
Too strange... Can you send your getprop when my original MOD-3.0 installed, than disable/delete it - reboot, and save getprop once again. Thanks.
@Displax
ok i dunno what is happening, with 2.3.1-mod3.0 now after 2 tries it leads to "integrity check failed" , same as the 2.4.0-microg
these are the props
ok i dunno what is happening, with 2.3.1-mod3.0 now after 2 tries it leads to "integrity check failed" , same as the 2.4.0-microg
these are the props
So it completely same behavior of this versions. I think microG has "wait timeout" for requests.
Please test on this build safetynet-fix-v2.4.0-MOD_1.3-microG-test.zip but do not send SN requests very often.
Just run several test (at least 10 times) at 5 min. intervals.
@AndiDink00x
@j0110
@Displax
After some testing i found out that there is no "timeout", both in microG and YSN there are only 2 available passes after that they fail, but if microG is closed/reopened the available successful SN passes are refreshed.
For example: opened YASNAC tried 2 times successfully , 3rd time fails-crashes(YASNAC crashes only on "integrity check fail") , closed the app on backround, just launched microG and closed it, then reopened YASNAC and again passed only 2 times.
That happens with also microG.
Hey. I didn't want to hijack the thread but I didn't find any contact info from you @AndiDink00x .
I also have a Poco x3 Pro but I am one step back. I still can't get SafetyNet to pass (I am using microG).
Do you have any directions or instructions that you could share?
EDIT:
Steps I have taken:
- I have microG (crDroid), with signature spoofing and Magisk
- Enabled Zygisk, rebooted
- Enforced DenyList, rebooted
- Added to DenyList: microG Services Core (all 4 activities? - unstable, persistent ui), microG Framework Proxy and YASNAC
- Installed Universal SafetyNet Fix and MagiskHide Props Config, rebooted
5.1 - No props for X3 Pro. Didn't actually do anything - Enabled in microG device Google Device Registration, Cloud Messaging and Google SafetyNet
- Tried to pass SafetyNet attestation.
- Results: Basic integrity pass. CTS profile match fails.
@anonimou0 user:Undisputed00x on discord
@AndiDink00x
So there is other restriction. Please send logcat from crashes. I don't think it's my module's "problem".
Anyway there is no need to check SN status more than twice in a row. No such app do this, so no real problem on it.
@AndiDink00x
Try this, not sure if it fix "problem", but anyway...
safetynet-fix-v2.4.0-MOD_1.3-microG-unload.zip
@Displax
same thing ...
Ok. So I release microG version "as is" because this behavior should not affect applications in real life. Just do not run attest more than twice in one session.
https://github.com/Displax/safetynet-fix/releases/tag/v2.4.0-MOD_1.3
Did anyone end up managing to pass the safetynet attestation completely on microg? If so, what steps should I take to get it to work? The best I ever get is "CTS Profile does not match"...
Did anyone end up managing to pass the safetynet attestation completely on microg? If so, what steps should I take to get it to work? The best I ever get is "CTS Profile does not match"...
Just use verison 2.3.0. I am using it now and everything work ok with it including microg
Just use verison 2.3.0. I am using it now and everything work ok with it including microg
Wait, so I shouldn't use the latest version? Even though the latest version has (and is the only version to have) a MicroG-specific release? Also, There's no 2.3.0 version of the mod, do you mean 2.3.1 or should I not even use the mod?
Just use verison 2.3.0. I am using it now and everything work ok with it including microg
Wait, so I shouldn't use the latest version? Even though the latest version has (and is the only version to have) a MicroG-specific release? Also, There's no 2.3.0 version of the mod, do you mean 2.3.1 or should I not even use the mod?
Sorry, I was incorrect in version. I am using 2.4.0-1.2 now. And everything work.
Sorry, I was incorrect in version. I am using 2.4.0-1.2 now. And everything work.
I see, but how come the previous version works and the current one, supposedly made specifically for MicroG, doesn't? Shouldn't this issue be re-opened in that case?
@Void-0000 if it works why open the issue
if it works why open the issue
Apparently, the latest version (1.3) doesn't work, while the previous one (1.2) does. Unless I've missed some part of the process to make it work, this seems like a bit of a problem.
Did you manage to get the latest version working with MicroG?