-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GMS signature invalid #9
Comments
Hi @zgxgoo , thanks for this report. If I understood correctly, you launched the script with As to why your custom app did not work after few hours - it may be due to the fact that GMS restarted, and was not patched anymore, or perhaps the |
Hi, @kbobrowski, yes , you understood correctly, the output of the script is [allow.js] injecting |
Thanks, I'll check if I can reproduce it |
Pixel 2 android 10
Kamil Bobrowski <[email protected]> 于 2020年8月8日周六 下午5:57写道:
… Thanks, I'll check if I can reproduce it
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADO6A7YCHRO3TGJM2JC4VRDR7UOPLANCNFSM4PXV4NFA>
.
|
@zgxgoo unfortunately I could not reproduce this issue, as I have another one - when I leave the phone connected via USB and frida script running for a few hours, the phone switches itself off. It could be that something strange happens inside GMS, as we are patching quite low level methods which may be used by other parts of GMS, and this could potentially lead to unexpected issues. I'm using quite old phone with Android 6 which may have its own issues, perhaps I'll root Android 10 device soon, would be easier to debug it. |
After i signed the GMS by APP's signature, it worked; then i put the phone in the table for a few hours, the GMS's signature was invalid, and cannot sign again unless reboot the phone .
The text was updated successfully, but these errors were encountered: