[go: nahoru, domu]

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 pass device integrity with 16.x #342

Open
46620 opened this issue Jun 19, 2024 · 17 comments
Open

Can't pass device integrity with 16.x #342

46620 opened this issue Jun 19, 2024 · 17 comments

Comments

@46620
Copy link
46620 commented Jun 19, 2024

After flashing any of the 16.x builds, I can only pass BASIC. Removing the module I start passing DEVICE.
image
image

When trying with release key, the ROM doesn't pass DEVICE with or without the module.

Evo-X: 9.0
A14
ROM is signed with a testkey

@BurakSomuncu
Copy link

how did you got v16.1?

@46620
Copy link
Author
46620 commented Jun 19, 2024

@BurakSomuncu It's in the telegram group, same with 16.2 which I'm currently testing before updating this.

@46620 46620 changed the title Can't pass device integrity with 16.0/16.1 Can't pass device integrity with 16.x Jun 19, 2024
@BurakSomuncu
Copy link

@46620 yeah, it's still not working

@Sedat5665
Copy link

Yes, I have the same problem and it still doesn't go away.

@BotchedRPR
Copy link

Same for me.

Redmi K70 Pro, x.eu rom, 16.2

@46620
Copy link
Author
46620 commented Jun 19, 2024

tested after signing my ROM, I now only pass device and fail everything else.

@BurakSomuncu
Copy link

signing my ROM

how do we sign the ROM? or how do we check if the ROM is signed or not.

@46620
Copy link
Author
46620 commented Jun 19, 2024

signing my ROM

how do we sign the ROM? or how do we check if the ROM is signed or not.

Ask your maintainer. Check with adb shell unzip -l /system/etc/security/otacerts.zip. If it doesn't say releasekey then you're most likely not signed.

@BurakSomuncu
Copy link

it's signed, thanks.

@46620
Copy link
Author
46620 commented Jun 19, 2024

After flashing Evolution-X official and this module I can only pass BASIC and nothing else. Will update the original issue with this information.

@BenJewell
Copy link

How did you get 16.2? 16.0 is the latest on GitHub here, and in the Magisk repo.

@BurakSomuncu
Copy link

@BenJewell search for "Play Integrity Fix Telegram" in Google, APK is in the Telegram channel.

@40ZqTYY4ag3tAO4hdlxR1
Copy link

Same here , only passing baskic , CTS profile match = fail

Still No RCS 🥳

@androidacy-user
Copy link
androidacy-user commented Jun 20, 2024

After flashing Evolution-X official and this module I can only pass BASIC and nothing else. Will update the original issue with this information.

Yell at your maintainer to use private keys for signing if possible.

In some cases, it seems like rom provided release keys are blocked all the same

@osm0sis
Copy link
Contributor
osm0sis commented Jun 20, 2024

I've yet to see any proof anything but the testkey is banned.

Anyway, that's not the problem with 16.x.

@androidacy-user
Copy link

I've yet to see any proof anything but the testkey is banned.

Anyway, that's not the problem with 16.x.

Users in a ROM group are reporting that that ROMs release keys are failing but maintainer private release keys are not. Can't independently verify it currently however.

@osm0sis
Copy link
Contributor
osm0sis commented Jun 27, 2024

I've yet to see any proof anything but the testkey is banned.

Users in a ROM group are reporting that that ROMs release keys are failing but maintainer private release keys are not. Can't independently verify it currently however.

More vague hearsay without the official ROM's name, download link, and/or the output of unzip -l /system/etc/security/otacerts.zip

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

8 participants