Skip to content
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

Can't get Play Integrity to pass with real play store #157

Open
LeVraiRoiDHyrule opened this issue Aug 15, 2024 · 13 comments
Open

Can't get Play Integrity to pass with real play store #157

LeVraiRoiDHyrule opened this issue Aug 15, 2024 · 13 comments

Comments

@LeVraiRoiDHyrule
Copy link

Hi,

I am trying to get Play Integrity to work. I have followed https://github.com/nift4/microg_installer_revived#how-do-i-get-the-real-play-store, and the play store is now correctly installed.

I have correctly installed this magisk module:
https://github.com/chiteroman/PlayIntegrityFix

But I can't get Play Integrity to pass. I couldn't find out if the problem comes from this module or from the microg installer. Here is the error I have in SPIC:

Screenshot_20240816-002441_Simple Play Integrity Checker

Would you have an idea of what is wrong?
Thanks in advance for any answer

@nift4
Copy link
Owner

nift4 commented Aug 16, 2024

Are all checkmarks in microG's self test checked?

@LeVraiRoiDHyrule
Copy link
Author

Are all checkmarks in microG's self test checked?

Thanks for your answer. They are, and microG itself is working perfectly. But I can't get the requirements for play integrity to pass.

@nift4
Copy link
Owner

nift4 commented Aug 28, 2024

Sorry, no idea then. I never used or investigated Play Integrity.

@LeVraiRoiDHyrule
Copy link
Author

Hi, thanks for your answer. I will seek for myself how to get play integrity to work. But first, I would like to ask for some help to get the real play store to properly install. I just opened this ticket on the problem with the logs, if you have an idea why I have this issue : #159

Have a nice day!

@Kranzes
Copy link

Kranzes commented Sep 4, 2024

Hey did you get it to work?

@bphd
Copy link

bphd commented Sep 19, 2024

E/keystore2(): system/security/keystore2/src/gc.rs:139 - Error trying to delete blob entry. system/security/keystore2/src/gc.rs:129: Trying to invalidate key.
E/Finsky  (): Caused by: DisplayErrorMessage[Error retrieving information from server. DF-DFERH-01]
E/keymaster_tee(): [ [31mERR [0m]Unexpected title ignore.. title: TEE
E/Finsky  (): [94] oao.c(60): Unexpected android-id = 0
E/Volley  (): [94] kfs.a: Unexpected response code 400 for https://play-fe.googleapis.com/fdfe/integrity
E/Finsky  (): com.google.android.finsky.integrityservice.IntegrityException

@bphd
Copy link

bphd commented Sep 19, 2024

I resolved -9 CANNOT_BIND_TO_SERVICE by resintalling MGIR following instructions if right order (basically deleting user apps of vending and gms, then deleting module that will unmount system apps of vending and gms, then installing same user apps, then installing MGIR to systemize and reboot ig, if I forgot something, read official intructions). And after activating Google Device Registration and Google SafetyNet. Though I don't know at all which of those steps are necessary or not, have to do test one by one

Something like

for i in com.google.android.gms com.google.android.gsf com.android.vending com.github.nift4.microg_installer_revived                                       
do pm uninstall $i                                   
pm uninstall -k --user 0 $i                          
magisk --uninstall-module $i
ksu uninstall $i                                     
pm install -r /storage/emulated/0/Download/$i.apk    
pm install -r --user 0 /storage/emulated/0/Download/$i.apk                                                
ksu install /storage/emulated/0/Download/$i.zip      
magisk --install-module /storage/emulated/0/Download/$i.zip                                               
done

But now I'm stuck at -12 GOOGLE_SERVER_UNAVAILABLE

@bphd
Copy link

bphd commented Sep 19, 2024

As usual, the thing being mysterious

So I managed a new time switching from -12 GOOGLE_SERVER_UNAVAILABLE to BASIC_INTEGRITY, that time by granting every rights to gms and then deny them all. Still consistent across reboot

Though I can't deny battery optimisation, ROM say it's necessary for that app

And second mystrious thing, my CROM don't notoriously support signature spoofing, and I don't have activated ZLSP or FGA, yet spoofing seems fine for GMS

PIF don't seem to change anything to that BASIC_INTEGRITY verdict. And now error -17 CLIENT_TRANSIENT_ERROR REQUEST_HASH_TOO_LONG

@bphd
Copy link

bphd commented Sep 20, 2024

Quite the trip... I permuted ChiteroMan's > @osm0sis Osmosis's > @chiteroman ChiteroMan's and downgraded from BASIC_INTEGRITY to NO_INTEGRITY

I tried fpa from @daboynb DaBoyNB's PC and downgraded to -17 TRANSCIENT_ERROR, reactivated MGIR and upgraded to NO_INTEGRITY. From there nothing works to get BASIC, let alone DEVICE

@bphd
Copy link

bphd commented Sep 20, 2024

And btw that error could be corrected by re reapplying what I did to get BASIC_INTEGRITY. But no known way to get DEVICE_INTEGRITY

@bphd
Copy link

bphd commented Oct 3, 2024

By deactivating persist.sys.pixelprops.gapps persist.sys.pixelprops.gms properties and resintalling vending/gsf/gms and spoofing build and provider (and btw using PIF module, or Osm0sis one when that one bother me) I achieve device integrity. I have difficulties achieving strong integrity but it's probably because my CROM throw UnsupportedOperationException() when DroidGuard ask for certificate chain, have to figure out how to patch from MagiSK, or LSP, or by replacing files

@cleanerspam
Copy link

Strong Integrity is not possible with unlocked bootloader , Strong Integrity hardly passes for custom ROMs with regular Gapps

@bphd
Copy link

bphd commented Nov 7, 2024

Strong Integrity is not possible with unlocked bootloader

Source

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants