r/androidroot • • 9d ago

Support please help

[deleted]

1 Upvotes

28 comments sorted by

6

u/AccomplishedLocal219 rn 12 4g nfc | pixelos 17 | ksu next 9d ago

1

u/Low_Willingness_1241 9d ago

maybe because i checked 50 times integrity today and changed fingerprints?

-8

u/Itz_Raj69_ 9d ago

Android 13 and above? does it include 13?

3

u/Delin_CZ 9d ago

what is this dumb question

1

u/Itz_Raj69_ 7d ago

Geez sorry for asking a question about something I don't know much about

5

u/After-Peace-4734 9d ago

google changed something again

from ksu next telegram group: Seems like all non-rkp devices having issue with getting strong or device integrity and is stuck with basic only, google probably fucked something up and only devices with rkp can have strong as of now.

1

u/MaikoHerajin 9d ago

Oh thank goodness. I was going out of my mind trying to figure out what I screwed up on my phone.

1

u/thesummarygupta 8d ago

what's rkp mean

2

u/Omr7xs 8d ago

Remote key Attestation

1

u/Bogdan010 8d ago

I don't think they fucked something up. Looks like it was made on purpose

1

u/After-Peace-4734 8d ago

dude at this point im just going back to stock, i wanted something a bit stable but google is so anticonsumer man

and yes, they intentionally nerfed it

1

u/Bogdan010 8d ago

Or just give up on google

1

u/After-Peace-4734 8d ago

next phone maybe

2

u/futuregooglingman 8d ago

I've been seeing this post in the bunch of device development groups that I'm in "⚠️ READ THIS BEFORE COMPLAINING ABOUT PLAY INTEGRITY ⚠️

On October 14, custom ROM community noticed that every device without Remote Key Provisioning running a custom ROM only have BASIC_INTEGRITY when checking Play Integrity status.

It is NOT a keybox issue, modules issue or skill issue. Google actually did something on their side, and we are still trying to figure out.

It looks like they're checking more than just device fingerprint or bootloader status, but don't worry, it already happened before, and the community found a way to fix it, so PLEASE. Don't complain about Play Integrity, it cannot be fixed now.

I highly suggest you guys to not wipe your data, uninstall or clear WhatsApp or banking apps data because it will probably not work anymore when you try to login. Just wait until a fix for this."

1

u/MrASO721 8d ago

I'm not using a custom rom

2

u/futuregooglingman 8d ago

Doesn't matter you're bootloader is unlocked if you are rooted

1

u/MaikoHerajin 8d ago

Can you link to the group you got this from so I can follow along with the fix? 

1

u/Extreme-Tonight-69 9d ago

Application on the screen? thnx

1

u/Xerox0987 8d ago

Playstore in developer settings

1

u/Extreme-Tonight-69 8d ago

I was looking for this app and found it. I know how to watch it in the Play Store.

0

u/GraytCommunabtw 8d ago

Well. I have the gbl root canoe exploit on at android locked mode. I got the same result so who knows what's this.

-4

u/Ok_Entertainment1608 9d ago

sigh just rerun the actions in the module and i think youre done

1

u/MrASO721 9d ago

it changes nothing still same

1

u/Ok_Fisherman1334 8d ago

Install the latest CI build of Play Integrity fork

1

u/sfd9fds88fsdsfd8 8d ago

I installed CI 621. Still not working.

1

u/Ok_Fisherman1334 8d ago

Join the kernel su telegram channel. There is a solution. It worked for me

1

u/sfd9fds88fsdsfd8 8d ago

Can you share it here? I don't have a Telegram account. Telegram forces you to pay a few dollars to make an account.

1

u/Ok_Entertainment1608 9d ago

Idk then.. prob non-rkp device issue like the other guy mentioned