yashsingh1/xdaforums huggingface dataset:
[Magisk] bestfootie:
OMG!!!! THANK YOU SO MUCH!!!!! YOU GUYS/GIRLS ARE KINGS/QUEENS!!

So clear!!

The only thing to add for clarity for those who aren't dev's etc, like me, that would've saved 15 mins of faff is that you install the PlayIntegrityFix via Magisk Modules. Install the zip on your computer then copy it to your phone, and then run the installation app from there. Oh and remove the now irrelevant SafetyNet verdict. Oh and

I couldn't do this bit, wasn't sure how to check a string etc, perhaps this could be explained a bit?

My device now has INTEGRITTTYYYYYYY oh yeh baby!! Integral! Integral! Integraaaaaaaaal

Supermarket here I come!!
[Magisk] generalculprit:
Glad to see someone happy. If wallet is working you have Device integrity and your kernel string is not banned.

If you still want to check your kernel string, grab a terminal emulator and type "uname -r". Post the outcome here.
[Magisk] bestfootie:
Is it safe? What does that kernel string mean? What info's contained within it?
[Magisk] HippoMan:
The OP (this thread's original post) explains about the kernel name string.
[Magisk] okij:
Uh well, it contains your banking account details, your birth date, your phone number and the nickname of your girlfriend, so better don't post it. 🤣
[Magisk] bestfootie:
5.10.198-android12-9-[8numberstring]-abS908EXX.......]
[Magisk] generalculprit:
It's safe. It's just a short text string describing your kernel version. Sometimes developers add "vanity" strings to it, which clearly show that your kernel is not original. Those kernel strings get banned, you don't get Device integrity, only Basic.
[Magisk] generalculprit:
-android12(-) is not in the list. That means it is not known as blocked. And since your wallet is working, it actually isn't.
[Magisk] HippoMan:
The list of banned kernel names whose link is posted in the OP will let you know the status of this kernel name.
[Magisk] Wolfcity:
I can only start that list with

- Ingress Prime (augmented reality game)

Definitely checks for strong since this month.

I heard that the McDonald's app is also doing so but I haven't used that app.

Funny how all (German) banking apps don't bother about my rooted device but a game and a fastfood app do....:rolleyes:
[Magisk] Vision:
Thanks you.

McDonald's I test it before days and open, now not have it 😂🤣

Yeah it's really funny.
[Magisk] Aregtheeditor:
Do companies hate rooted users?
[Magisk] Nergal di Cuthah:
I think it's more about gps fakers that companies, like mcdonalds and Pokémon go's developers, hate
[Magisk] Aregtheeditor:
Still hope. Pokemon go works with PIF for now same with pikmin bloom! I tried it today after realization of ingress ban which I rarely played.
[Magisk] Vision:
Yeah, instead companies provide a security apps, even with root, go for easy way and block root 😂🤣
[Magisk] Zaxx32:
My bank app plays nice (Truist Bank) but that could change at any time. :rolleyes:
[Magisk] BunnyPig1:
Exactly my thought as well. Reading about all problems with hiding root from banking app, ID-apps, chasing PI integrity, spoofing bootloader status and such made me paranoid.

But after years of never having any issues I'm very happy I live in a place where they don't (yet) deem it an issue.

Granted my banking app once said "your device seems abnormal". I just said "in the denylist you go then" and it went "screw it, all good". Very pleased.

Again, this could change at any moment but right now I'm very happy.
[Magisk] fbirraque:
The McDonald's app issue must be deeper investigated. :ROFLMAO:

Still working flawlessly for me even just Basic certified.
[Magisk] LLStarks:
Am I the only one that has had a functional wallet and RCS for days with just apatch and nothing else?

I'm not feeling the pain of lacking device like I'm apparently supposed to. Then again, I'm not an ingress player anymore.
[Magisk] manjaroid:
@UberNorse seems to be making progress with Apatch on Pixel 7 Pro but it's probably too soon to call it a done deal for both Wallet and RCS.
[Magisk] fbirraque:
Which device model?
[Magisk] Aregtheeditor:
GitHub - changhuapeng/FrameworkPatcherGO: A Magisk/KernelSU/APatch module to modify framework.jar directly on the phone, to build a valid system-level certificate chain.

A Magisk/KernelSU/APatch module to modify framework.jar directly on the phone, to build a valid system-level certificate chain. - changhuapeng/FrameworkPatcherGO

github.com

Is this a solution for rcs and replacement to pif?
[Magisk] gj4560:
Hi everyone,

Been a while since I've read this thread but I've been having the same RCS issues as everyone else, although my Wallet is working fine. From catching up with this thread, I've found out the reason for that is due to the public xiaomi.eu fingerprint included as part of PIF, and the solution is to switch to a private fingerprint that isn't banned by Google so I have both RCS and Wallet functionality. What is the best way of finding a private fingerprint like this that will work, other than endlessly going through TheFreeman's repository and hoping one of those will work (of which the chances are incredibly low now from what I understand)?
[Magisk] Nergal di Cuthah:
There is no easy way, freeman's is dead all banned, now abandoned. You must find build files (two to three for every device/ROM combo) compile them into pif.jsons and test them. You WILL have to go though hundreds to get one.
[Magisk] osm0sis:
On the positive side of things, I just had someone confirm to me that there are some new dumps added to a prominent dump site which also have prints passing PI, so there're more than the 4 left there that we originally thought! 🎉🤘
[Magisk] beeshyams:
This has been discussed a few pages back... IIRC @Vision commented on this (sorry @Vision ,if I am wrong and wrongly tagging you)

BTW, I am clueless
[Magisk] dr.ketan:
Replacement for PIF - Yes, still RCS won't work with this too
[Magisk] koxipo:
Hello, I dunno if it has something to do with my testing environment but it seems like pretty much any fingerprint I test lately (using the scripts provided by zgfg) yields a device verdict. I tried the scripts with TB checker and SPIC.

I tested prints from the website with plenty of dumps that yielded either no integrity or only basic verdicts yesterday that now yield device, even got prints from google devices dumps on purpose, all of them pass device.

Do other people notice the same thing ?
[Magisk] zgfg:
I can't test now but the post above from Osm0sis was also related to one particular print that wouldn't be expected to pass Device Integrity

If G makes again tectonic changes, that's generally not a good sign, the volcano can erupt any time
[Magisk] arunchegz:
Hi all. Am using Oplus 11r with Apatch. RCS working fine.
[Magisk] Vision:
Yeah, I commented in all this important, I'm always (almost) front.

😂🤣
[Magisk] bkraptor:
If I understand correctly, the theory is that FPs get banned which causes PI/DG and/or RCS to fail. If I were to use a stock phone with the exact build that has a banned FP, would it still be banned? If yes, what would be a reason to ban such a stock phone? Has anyone tested this theory?
[Magisk] Vision:
If stock without root and locked BL, not banned, Google block the virtual FP we use in PIF with some checks.

and If it rooted, still do the same, send the FP to DG, so again failed.
[Magisk] CZ.Kostra:
PIF FAQ #2
[Magisk] zgfg:
No, G still distinguishes original phone with unlocked BL and original prints from the spoofed prints.

Banned prints term relates to being banned for PI or RCS, not for those with that stock prints on their not-modded phones
[Magisk] Aregtheeditor:
How can I root with apatch moving from magisk while keeping data?(for rcs)
[Magisk] bkraptor:
Thanks for a the answers. Flipping the argument around, if G has the ability to intentionally detect a FP when spoofed vs when used on the stock phone, why would they not blanket ban all spoofed FPs (i.e. the spoofed state)? What makes those working FPs special to enable the bypass of this spoof detection ability?

From my naive perspective, knowing that stock phones work fine with the "banned" FPs, it feels like the spoofing is incomplete and there are other datapoints that DG/RCS extract beyond the values in the FPs or kernel strings. So rather than chasing a dwindling supply of un-"banned" FPs, I wonder why the knowledgeable folks are not looking at what other datapoints are being extracted to detect spoofing?
[Magisk] sawdoctor:
[DEV] APatch - an alternative root solution to KernelSU and Magisk

The patching of Android kernel and Android system. A new Kernel-based root solution for Android devices. APM: Magisk module like support KPM: Kernel Patch Module support. (Allow you to inject any code into the kernel, Kernel function...

xdaforums.com

Pretty straightforward
[Magisk] zgfg:
All the questions that have been post and discussed many times

If you know the answer or if you can ask somebody from G to describe what and how they do, please let us know😀

Actually more important would be to know what the next (short time) and future steps G will do
[Magisk] Aregtheeditor:
But will it keep my data?
[Magisk] Aregtheeditor:
wait no I can't do it on Samsung :<
[Magisk] Vision:
I have open a thread (my first), for apps&games need pass PI.

You can write what apps&games need it.

Apps&Games need PI (List)

Here you can post what apps&games need to pass 2/3 (Play Integrity) to show it on Google Play. Some apps&games appear and can download but when open (for apps until now) can't use if not pass DEVICE, because required to pass 2/3. Also from now...

xdaforums.com
[Magisk] Captain_Throwback:
Like PIF, this solution requires a spoofed fingerprint, and it currently uses the same RCS-blocked sailfish print that's included in PIF.

So, while this spoofing solution may help people that have apps that detect Zygisk, it will have the same issue with RCS as PIF. But of course, if you find a working private print, you can replace the sailfish print in the source and use that for spoofing in FrameworkPatch, and then RCS should work. Presumably, you could change it to a print that only passes BASIC and RCS should also work, but that would most likely sacrifice Google Pay/Wallet.
[Magisk] immortalwon:
Is there confirmed evidence that using another private print will help get RCS working? I used another print that wasn't sailfish and RCS was not working, but zygisk was enabled.
[Magisk] LLStarks:
Pixel 8 Pro
[Magisk] Vision:
Yeah, I test it until now, RCS not working, but disabled the Framework Patcher GO module, and only in MagiskHide the gms.unstable and get basic, I think working again.
[Magisk] aliantonio:
I wouldn't recommend any of them if you plan on using RCS. If working RCS isn't a factor for you, then the version you listed is perfectly fine at detaching apps from the play store.
[Magisk] aerotox:
Device integrity OK and banking app suddenly stopped working after OK for months. Redirects me to site about altering device securiy after the app is instantly force closed.

How can I know for sure if it suddenly started checking STRONG? Although that is probably the reason
[Magisk] sawdoctor:
Try shamiko, zygisk assistant and HMA (if you haven't yet) not many if any banks are enforcing strong their just getting better at detecting zygisk/root
[Magisk] aerotox:
Thanks for the tip, have Shamiko but I will try the others
[Magisk] osm0sis:
Always and forever, private prints are confirmed working just fine.

Read my RCS ban summary:

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com
[Magisk] Vision:
Finally.

So frameworkpatch guide after compile on Android Studio, apparently it was working from the start on A11.

Just need it the Scripts-only mode on PIFork (without zygisk) and add GMS.unstable to MagiskHide and finally pass 2/3.

That was the missing piece.

Thanks you @chiteroman and of course @osm0sis for all the hard work and effort. We Appreciate.

We all know where to go for a donation.

View attachment 6114377View attachment 6114378

EDIT: Now only remaining to test RCS with another FP, if anyone have one and can shared via PM, I appreciate a lot, I know ask much, but really I promise keep it private
[Magisk] Stillhard:
w/o zygisk, means still not stable w/ zygisk?
[Magisk] osm0sis:
So if you guys are just hacking framework directly now, why not just go all the way and inject PixelPropsUtils into it?

frameworks_base/core/java/com/android/internal/util/evolution/PixelPropsUtils.java at udc · Evolution-XYZ/frameworks_base

Contribute to Evolution-XYZ/frameworks_base development by creating an account on GitHub.

github.com

I'm not going to volunteer for developing that one, but it's the only logical endgame.
[Magisk] Vision:
I mean, no need to have zygisk enable if you don't want it.

This looks interesting 🤔 unfortunately I'm not that much expert to do it by myself this.

Maybe @chiteroman in the feature, modify more in the framework.
[Magisk] fbirraque:
c/c: @chiteroman

You can get the Locked Bootloader (Zygisk) in this way. Seems promising but unfinished.

bypasskeyattestation/docs/intro.md at main · doom-man/bypasskeyattestation

Contribute to doom-man/bypasskeyattestation development by creating an account on GitHub.

github.com
[Magisk] Hugh9190:
Is it necessary to follow these steps to test RCS, or can I simply change the test fingerprint and use "adb shell am force-stop com.google.android.gms" or "killall com.google.android.gms.unstable"? Device integrity is not important to me, and I've heard that RCS can be tested without passing device integrity checks. Therefore, I need to confirm the most efficient way to test RCS functionality.

I apologize for asking about experimental results here instead of testing it myself. However, I currently don't have a usable fingerprint for comparison. I'm sorry for the inconvenience.
[Magisk] Vision:
You can try only with gms.unstable to MagiskHide or denylist, and get only BASIC and test it if works.
[Magisk] Vision:
And this is excellent:

GitHub - hex3l/PlayIntegrityForkKsBypass: PIF fork that provides attestation by bypassing the Android KeyStore while using a valid keybox. Not complete and explicitly set to work only in the context of Key Attestation app

PIF fork that provides attestation by bypassing the Android KeyStore while using a valid keybox. Not complete and explicitly set to work only in the context of Key Attestation app - hex3l/PlayInteg...

github.com
[Magisk] osm0sis:
That was more a response to everyone saying they needed to downgrade Messages, wipe and update again, and various combinations of those. Point being, none of that was necessary.
[Magisk] Hugh9190:
Why can I only see the 4 apps I installed myself in my denyList? There is nothing related to Google.
[Magisk] Hugh9190:
Thank you ,I just want to know if, after changing the test fingerprint, it is necessary to turn off the switch, restart the phone, and then turn the RCS switch back on? Or can I simply use the command "killall com.google.android.gms.unstable" and then check if RCS is working. The efficiency difference between these two methods is significant.
[Magisk] Vision:
Click in 3 dots and show system apps and search for gms
[Magisk] generalculprit:
That is well understood. But most of us are in the same position as you are, without a private print to test. There is also no commonly known DEVICE "banned" print that is still working for RCS.

You'll just have to hope for someone with one of both to tamper with his own RCS to test it. Maybe someone is willing to.
[Magisk] Hugh9190:
It's easy to understand that those who without a private fingerprint cannot test it, and those with a private fingerprint don't need to conduct this test. On the other hand, it's clear that if someone has a private fingerprint, they can easily test whether it's necessary to restart the phone and toggle the RCS switch, haha.
[Magisk] Hugh9190:
Thank you, I use Magisk infrequently. I've already tried the following:

gms.unstable in the DenyList, "Text message"

both gms.unstable and gms in the DenyList, "Text message"

both gms.unstable and gms in the DenyList, turning off the RCS switch, restarting, and then turning on the RCS switch, "Text message"
[Magisk] generalculprit:
I was just trying to nudge people who could help you. 😉

Additionally, I would clear Messages cache and (if present) carrier services cache, but - as said - unfortunately I cannot confirm that.
[Magisk] hsmith1514:
It's sufficient to killall com.google.android.gms.unstable. You might need to wait a minute for RCS to 'register' or whatever it does in the background, but restarting your phone or messages app, or toggling rcs isn't needed.
[Magisk] Vision:
And works the RCS with only basic?
[Magisk] Hugh9190:
Thank you anyway.

I even tried cleaning gsf, it would take longer, but it seems unnecessary, because if there is a current limiting problem or other problem with gsf, the rcs switch cannot be turned on. On the contrary, if the Rcs switch does not appear or cannot be turned on, you can try cleaning gsf.
[Magisk] Hugh9190:
I also don't have any fingerprints that would make RCS work, neither basic nor device integrity. What I'm doing is identifying the most efficient way to test thousands of fingerprints, and trying to find one that makes RCS work.
[Magisk] aliantonio:
How did you get lsposed to work for you? Every time I install it, RCS breaks for me.
[Magisk] Vision:
I thought you want BASIC, for that I said add the gms.unstable to Denylist, no need a FP.

With this can get BASIC.
[Magisk] koxipo:
Has anyone been able to do some print testing ?

Maybe I'm testing wrong, I have just reinstalled my ROM and rooted it again.

I started the testing script before remembering to turn on the enforcement of denylist in magisk and the prints yielded basic/no integrity.

After toggling the enforcement of denylist, those same prints all yield device integrity now.

Am I supposed to test with the denylist toggled off ?

A few days ago I was getting no integrity/basic integrity results only with the denylist enforced, I don't know where the difference comes from
[Magisk] Nergal di Cuthah:
Private prints are rare. Even before the feb 29 massacre, it took many fails to find a working print. Now it is even rarer. Keep trying is my best advice (though i don't care about RCS so am "happy" using sailfish).
[Magisk] zgfg:
There are people who do read posts here - not just today's posts, who started tested like ten days ago or last week, already found private prints that pass both Device Integrity/Wallet and work for RCS

No need for Framework patching, etc

But anyway, who wants to find will find, it's not hundred pages back. I don't feel obligate to play search engine and to point which posts 👍
[Magisk] koxipo:
Hello,

I'm not sure I understood your reply but my goal wasn't to whine about not finding working prints fast enough. I know that working are rare but my tests say that every print passes device integrity which doesn't seem normal.

I noticed that turning on/off the enforcement of the magisk deny list changes the results I get so I'm wondering what I'm supposed to do with the deny list so I can get proper results that's all.

Could you pls tell me whether the deny list is supposed to be turned on or off ? Or by ''no need for framework patching, etc'' do you mean to say it's not supposed to matter ?

Sorry if it's already been asked, I tried to look in the other thread about tools where I found the script that automated testing but I couldn't find that information.
[Magisk] trevtdogg:
I can confirm that you don't need anything in deny list for pif to work and to have device integrity. I don't have shamiko either, or hma - just normal magisk and lsposed, that's it.

but you seem to have some special attributes where you are passing device with many otherwise burnt prints? maybe it's worth checking with logcat which print is being spoofed to make sure that is the case?
[Magisk] pndwal:
If you don't need device integrity, try with PIF disabled. You may still have BASIC_INTEGRITY with GMS DroidGuard (unstable and possibly need core process) in denylist depending on ROM, and RCS if device itself meets specs. 🤠 PW
[Magisk] diNovoM:
Hey, what are actually the requirements for google chat (need for work)? Is there any 3rd party app to use to work with it?
[Magisk] CZ.Kostra:
What device do you have? What ROM are you using? Doesn't ROM have its own PIF solution? These results are very strange. 🤔
[Magisk] beeshyams:
Excellent round up as usual... Hope I get time to actually read and understand everything, though my technical understanding is rather limited
[Magisk] bentree:
Well, I tried the website that I think you are referring to and couldn't find any after trying 100 recent prints.... By recent, I went as far back as 2 months.

Cheers, Bentree
[Magisk] osm0sis:
Check in my Odds and Ends thread, maybe you're thinking of somewhere different? We found 13 working prints from recently.
[Magisk] koxipo:
I use a POCO F5 running the latest version of Android 14 Evolution X available for it.

I disabled the magisk denylist and I get the expected device with an occasional "no integrity" verdicts now.
[Magisk] CZ.Kostra:
If you perform several PIay Integrity tests with same FP (JSON) and same settings and results are different, PIF collides with "injector" in ROM.

You will have to disable "injector". PIFork by @osm0sis solves these things.
[Magisk] bentree:
Pretty sure as it's the only site that I can find (using a google search) that has a large amount of Android dumps on it. I just blanket tested everything that had been added in the last 2 months, about a 100 prints. I just download the "prop" files and test each one with pixel flasher connected to my phone.

Same way I used to do it before the great ban happened earlier this year.

Cheers, Bentree.
[Magisk] Hugh9190:
All of these prints are also working on Rcs , right?
[Magisk] osm0sis:
Anything working for DEVICE integrity that isn't the current public print works for RCS.
[Magisk] osm0sis:
Pretty sure I mentioned it by name in my most recent post in my Odds thread, so no need to guess about it.

The larger number of the new working ones are from 2 weeks ago. And they seem a bit special, perhaps for obvious reasons.

Edit: Ah, there are actually only 2 new ones from the dumps, and only one of them is special like I mentioned. I had our sources confused. 🤦‍♂️
[Magisk] Cristiano Lira:
I tried an unsigned build of a rom where one particular banking app wasn't working but tried again today and now the app is working, did something change?
[Magisk] osm0sis:
Apps are apps, most don't use PI so likely nothing to do with it.
[Magisk] badabing2003:
Yes

FYI, it works with zygisk enabled. and gms.unstable not in denylist, and no need for MagiskHide.

View attachment 6114661View attachment 6114662View attachment 6114663
[Magisk] Vision:
That's is good 👍

What device and Rom you have?

Which module you have?
[Magisk] badabing2003:
Stock Pixel 5 on the latest A14.

View attachment 6114664
[Magisk] Vision:
Nice, so you don't have to add the gms.unstable to DenyList, PIF fork script-only-mode is enough, that is good.

Yeah the good is you can have and zygisk if you want.
[Magisk] Aregtheeditor:
When I tried on samsung a24 it lagged
[Magisk] mac796:
I have tried about 100 so far still no luck. I'm not giving up. Had to go to work.
[Magisk] passionicon:
13? Any plans to share so we can use?
[Magisk] passionicon:
Have you found an efficient way now? I am looking for a way as well.

Did you try pixel flasher?
[Magisk] simplepinoi177:
What I'm just as worried about is when apps & services & companies will start (or if because Google starts pushing it) requiring Strong Integrity -- it reminds me on how Displax finally found a method to get "MEETS_STRONG_INTEGRITY" and they patched that up so quick enough; so since then I've been cognizant of how Google ain't sleeping on this....
[Magisk] SuperMaximus:
Play integrity checker gives this with v12.2 (was OK with 12). Yasnac does not pass anything.View attachment 6031330