yashsingh1/xdaforums huggingface dataset:
[Magisk] i5lee8bit:
VERY WEIRD, guys... Got a message from another person from a certain kernel testing group a few minutes ago, so I decided to test. But the results are WEIRD...

Some testing (Pixel 7 Pro, Oct update, Magisk 26.4 stable official, Shamiko 0.7.4)...

* PIF 9.9 = PI Checker device FAIL, basic pass ; YASNAC = timeout error

* USNF Displax 2.4.0 Mod 2.0 + PIF 9.0 =

PI Checker device FAIL, basic pass ; YASNAC = timeout error

* USNF Displax 2.4.0 Mod 1.3 alone = PI Checker device FAIL, basic pass... BUT... YASNAC = device (CTS) + basic pass.

On to some good(?, albeit confusing) news... Confirmed also that this morning, biometrics died with my main banking app, but after switching back to Mod 1.3, despite the different results from PIC and YASNAC, I was able to re-enroll my biometrics. So the banking app is indeed seeing it as passing again. I would assume tap to pay would work again too, but I haven't tested it.

* I did NOT check USNF Displax 2.0 mod alone, as it's been known for a long time now to be broken in devices shipped with 13+.

A very huge ¯\_(ツ)_/¯ from me, but hopefully this info can help the geniuses and wizards here figure this out? We all appreciate you btw. 🙂
[Magisk] i5lee8bit:
Screenshots, btw.

Edit: in relation to the directly preceding post. No longer getting timeout error in YASNAC and passing both basic and device/CTS. But still showing failed device in PI Checker.

Could the timeout in YASNAC perhaps be a piece of the puzzle? I'm also worried maybe my banking app just uses an outdated method to check device security, although they just did a HUGE overhaul like 2 weeks ago, and so also maybe not. Again, I haven't had a chance to test tap to pay yet.
[Magisk] SuperMaximus:
I tried to find the root cause of the problem with Google Play Services not displaying Location (emergency) notifications and bumped into a problem of Google Play Services + Google Play totally being hidden by Deny List. In my case it's not exactly the deny list but Magisk Delta's Unmount feature. So I had to unmount the below components (unhide root) and then my location-based notifications returned to work, although my Play integrity pass was lost. Tried installing Play Integrity Fixes (9.9 to 11), but nothing changed. Once I hide root from all Google Services, Basic + Device check passes (but I don't solve the issue of location notifications then). Maybe some of the below features need to be unhidden? Screenshot shows Magisk Delta hidden (unmounted = off) and unhidden features (mounted = on).

View attachment 6030477
[Magisk] osm0sis:
YASNAC still showing passing with Basic and CTS on 9.9 here, just PIAC showing Basic passing and Device failing, and tap still working as of a few minutes ago.
[Magisk] i5lee8bit:
WHAT THE HECK IS HAPPENING??? lol!

Yeah, so that change with YASNAC working again must have happened in the middle of my testing... Switched back to PIF 9.9 and I'm now getting BASIC/CTS pass on YASNAC, but device FAIL / basic pass on PI Checker. Biometrics still working on my banking app (and it would immediately fail when either of the checks fail).

Edit:

😅😌 Let's hope it stays that way!
[Magisk] zgfg:
Despite to the bad new that happened today, I still paid by Wallet this afternoon
[Magisk] TotallyAnxious:
Wanted to add that the play store is reporting device as not certified but I can still see and download Netflix in play store.
[Magisk] osm0sis:
I'm also still showing Certified 🤯
[Magisk] Kevin_V26:
Wallet stopped working today. I was on the latest 2.0 safetynet fix mod. I found this module, however this did not work also. From the replies it seems google bypassed these modules. Replying to be alerted for a possible solution.
[Magisk] Unn113:
Fingerprint login into my banking app (millennium) works normally which is weird cause it shouldn't with only basic pass. Haven't tried tap to pay yet, but I'm assuming it'll work.
[Magisk] sawdoctor:
+1 pixel fold
[Magisk] jesvi:
So it's an error we all face currently huh ?

I had no problem until I decided to reinstall the rom and patch it up for safetynet...

Strangely as mentioned by others, Meets_Basic_Integrity alone passes and rest fails...

I can't get my banking apps running, although google gpay alone works...

I used PlayIntegrity Fix v9.9, which seems to not work

also the link seems broken as of now (https://github.com/chiteroman/PlayIntegrityFix/releases/tag/v9.9), was it removed ?
[Magisk] ThePrinceofBirds:
Didn't fix it for me either.
[Magisk] badabing2003:
Something does not add up.

If RCS banning is hitting only people with Griffin (Xiaomi.eu) print, hiding root wouldn't make it pass.

It's the print that is causing the ban, I would strongly doubt that the condition is:

If rooted and Griffin then block.
[Magisk] aliantonio:
Is anyone else having issues with just receiving texts in general now? With RCS disabled, I do not receive SMS/MMS messages until I send a message to myself (no idea why this works).
[Magisk] ThePrinceofBirds:
All of the texts my wife sent when I had RCS on yesterday showed up via SMS all at once at 2330 yesterday. Since that I don't think I'm missing any SMS.
[Magisk] bombadier:
Just tested sending and receiving sms, both working, I have disabled RCS
[Magisk] RAZINARES:
I don't know why its not working for you guys, but it's working for me even after adding play services to the Denylist which breaks the play integrity. Can you guys uninstall Google Messages updates and try ?

View attachment 6086034
[Magisk] osm0sis:
The key is above, he's breaking PIF by enforcing his DenyList, thus failing DEVICE to "fix" RCS, just like everybody else who switched to an old banned print.
[Magisk] sawdoctor:
Rcs messages aren't really popular in my country so hard for me to check but does rcs messages work in a different app like this one

Smart Messages - Apps on Google Play

Upgrade your SMS with Next Generation Texting

play.google.com
[Magisk] ThePrinceofBirds:
I uninstalled messages update and for a minute the textbox changed from "text message" to "RCS messages." I sent a message and it had the dark blue but it failed to go through. A couple of minutes later I lost the RCS Message header in the text box.
[Magisk] Slim2none4u:
Not looking for replacements....looking for a cause and effect in here. More clutter.
[Magisk] sawdoctor:
It's not about replacements or clutter!! It's finding out if Google are targeting rcs chats or just blocking it in the messages app. This will make it easier to try and nail down the fix . Ok that's cause and effect
[Magisk] GabbyWC:
No, Google has not opened the RCS API to third party Android apps. Even without RCS, I consider Chomp SMS to be a better app for SMS and MMS messages so I'll probably switch back to that. As other people in this thread have speculated, the greedy control freaks at Apple may have something to do with Google's latest RCS security measures.
[Magisk] Vision:
So if in PIF add a feature, to spoof the FP (and another FP from this for DroidGuard) with some way not global like DroidGuard into the messages etc. , and the apps not break if read a spoof FP

if the messages see another FP cause problem? like camera break if have global another FP
[Magisk] RAZINARES:
Here is how I got my RCS working.

You need to use PIF(Not ROM PIF) and Play integrity Next module.

After installing these add Play Store, Play Services and Google messages to the Denylist and enforce it.

Now make sure your device integrity fails, otherwise it won't work.

Then clear Google Messages Data and and uninstall updates. After that RCS should be working.

To fix the Play Integrity, generate a new fingerprint from the Play Integrity Next Module.

As osm0sis have already mentioned the key to get the RCS working is to break the Play Integrity.

Adding Play Services to the Denylist will break the integrity and that's when you can get your RCS working.

When RCS is working you can remove Play Services from the Denylist or let Play Integrity Next module to do it automatically for you. And your Play Integrity should pass with RCS working

View attachment 6086045
[Magisk] majorfigjam:
Not sure if this adds anything, but ... in New Zealand this morning, I tried 2 devices

Pixel 6 pro A14, stock with kiri kernel, magisk 27001 hidden, shamiko, denylist off, Osm0sis v8, non-Griffin print , on network A - 2/3 device integrity

Pixel 4A A13, stock, magisk 27001 canary, Osm0sis v8, empty denylist is off, non-Griffin print, on network B - 2/3 device integrity. This device has the bare minimum to pass device integrity, and run adaway.

RCS between the 2 devices works, and encryption codes between devices check out.

I get the same results if I change to Griffin print on 6pro..

So looks like this may be a per Country, or per network provider restriction.
[Magisk] HippoMan:
Thank you!!!!!!!

Could you clarify what you mean by "uninstall updates"? Does that mean uninstall the entire "Google Messages" app? I'm not sure how to separate the actual app from "updates".

Thank you.
[Magisk] wfred:
I recommend textra
[Magisk] RAZINARES:
go to settings>app>Google Messages, there you will find an option to uninstall updates on the top right menu.

Sent from Pixel 7a using ReLabs
[Magisk] Vision:
In the end, Google not let us to make or receive a call 😂🤣
[Magisk] justDave:
See you all on WhatsApp.
[Magisk] g33gz:
I think this might work if your phone has the app installed by default. Don't think it works if you just installed messages off of the app store
[Magisk] Vision:
Something like that, expect update to require strong, after that we live again in the caves 😂🤣
[Magisk] i5lee8bit:
Aren't you still failing DEVICE verdict though? Kinda back to square 1. As @osm0sis already said earlier on this page: https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89429970

We already know old FP's that no longer pass DEVICE but only BASIC for some reason allow RCS to work. But the griffin print which has BASIC + DEVICE passing doesn't allow RCS.

*For now*, IF YOU WANT THE BEST OF BOTH WORLDS (BASIC + DEVICE + RCS) YOU NEED TO FIND A PRIVATE PRINT. Otherwise, you won't have all 3. Until hopefully this gets further figured out.

Now we just need to add RCS integrity checkmark on top of ludicrous integrity or whatever meme integrity lines ppl were photoshopping earlier in this thread.
[Magisk] HippoMan:
Oh, thank you! I forgot about that option.
[Magisk] Vision:
Yeah, can download a older version from a trusted site like Apkmirror or Apkpure
[Magisk] RAZINARES:
i used play Integrity next to generate fp, now Basic+Device+ RCS all three are working

Sent from Pixel 7a using ReLabs
[Magisk] Vision:
Yeah, something like this

View attachment 6086056
[Magisk] Ultimoose:
this worked for me for the moment. The cat and mouse though is going to get damn old.
[Magisk] g33gz:
I'm trying to use play integrity next but it doesn't seem to be working. I click the fpdownloader app and it doesn't seem to do anything.
[Magisk] RAZINARES:
it wont open anything, when you click fpdownloader it will generate new fingerprint. your device should pass the integrity now

Sent from Pixel 7a using ReLabs
[Magisk] ThePrinceofBirds:
Ah! Just tried again and uninstalled updates this way and it worked!

It says I'm still passing device and basic too.
[Magisk] i5lee8bit:
Does play integrity next do the same as osm0sis's autopif (as in just pull Xiaomi.eu's print, that is the griffin config)? Because in that case if we're back on the griffin print, it's likely just a ticking time until it fails again. Not trying to knock your work and research but I just don't see anything major that's actually changed. All the data clearing and hiding just sort of resets it back to a clean slate back to what we already know that basic only will allow RCS to work, but then switching back to the griffin print I'd be surprised it doesn't soon get tripped again.

Note that I wasn't aware that playintegrity next still worked so I'm just assuming it pulls the griffin print otherwise everyone would be using it.
[Magisk] g33gz:
Yeah I was already passing basic and integrity, just rcs is still failing
[Magisk] RAZINARES:
Add play services to the Denylist. Then check if you are passing the integrity. If it fails, then you can set up RCS, uninstall google messages updates , and register for RCS again. Now RCS should be working. Then you can use the fpdownloader to generate a new FP and you will get both integrity and RCS working.
[Magisk] Alitheia:
I've done all that was suggested here and the only thing that happened is now I have to set my Messages settings back up again after deleting data and uninstalling updates. Lol Still no RCS and passing everything.
[Magisk] SchmilK:
I started over with my deny list, had almost everything Google in there.

Limited it to these above.

Retrieved a new fingerprint.

Deleted app data and cache from Messages.

Uninstalled update from Play store (I moved to beta yesterday trying everything. Still in beta)

Turned of play store auto updates.

And then when it started I was asked if I want to join RCS and then got a bunch of rcs messages!
[Magisk] BillGoss:
Just to add more info to this RCS issue:

My wife and I each have both a OnePlus 8T running LineageOS 21 and a Pixel 8 Pro running stock 240305 build (we're in the middle of transitioning to the P8Ps).

Yesterday we were able to use RCS messages between us (https://xdaforums.com/t/rcs-root-not-good.4664381/post-89428544).

But today, she can no longer use RCS, even though it connects to RCS. And this this is true for both her phones.

However RCS is still working just fine on my phones. If I start a new message to her, the empty text entry field in Messages shows "Text message" as opposed to "RCS message". But if I try to text another contact (they have an unrooted, unlocked phone) the entry field shows "RCS message".

All our phones are running Messages messages.android_20240308_01_RCO3.phone_dynamic.

They all use Magisk 27.0 with Zygisk and Enforce DenyList enabled but nothing set in the DenyList, and Mount Namespace Mode set to Global.

They are all using PIFork 8.0 with the X.eu finger print and all the phones pass Basic and Device integrity.
[Magisk] RAZINARES:
RCS will work when your play integrity fails by adding play services to the deny list.
[Magisk] Alitheia:
Right, I did everything suggested, including the deny list and still have no RCS.
[Magisk] SchmilK:
And now mine is broke again :(
[Magisk] rrusek:
Just to clarify. If using magisks kitsune (delta) there is no Denylist only MagiskHide. Addinng Google Play serives (com.google.android.gms) does not break integrity.

Please advise?
[Magisk] Vision:
Oh yeah i forgot about that, yeah Kitsune Mask have improved MagiskHide with zygisk, and not have denylist and enforce, so the PIF broke with enforce, @osm0sis can answer in this
[Magisk] majorfigjam:
Are you both on the same network?
[Magisk] BillGoss:
Yes we are.
[Magisk] AlexS2412:
i tried everything in thread its still just broken sadly. i dont think it can be fixed unless the messages application is patched.
[Magisk] GeTex:
I've got 8.1.0 failing and 10 failing while having RCS working. As mentioned one phone is enforcing deny list on 8 with the xeu print working, the other on 10 uses a private print without enforcement and is working... I have no idea what's going on

Adding data, I have never passed device while having RCS working since January. For unknown reasons on my 8.1 and because of my kernel strings on 10. Also my blocklist is really short on 8.1. Google is doing some hacky stuff
[Magisk] fbirraque:
Hi osm0sis,

I tested the RCS Messaging on two different devices. Redmi Note 8T (EvolutionX, Android 13, Unlocked Bootloader, Safety Net and Play Integrity Fork V8 certified) and a Sony Xperia 10 Plus (Locked Bootloader, Android 10, non mod, certified by default).

Country: Brazil, Carrier: Vivo, and none of them could send or receive RCS (only SMS and MMS working). May the current issue could be related with some Google Server's side? Maybe some maintenance? At least for me seems more a instability then block.

It's interesting for those like me that already have a spare device with stock os and locked bootloader to double check it.
[Magisk] fbirraque:
I have MagiskHide enabled in the Kitsune Mask and can't send or receive RCS. So I don't thing the DenyList could explain the current issue.
[Magisk] Vision:
What exactly you have in Configure MagiskHide ? GMS, Google Play Store and Messages?
[Magisk] SkippRunning:
This definitely worked to fix mine just now. Thanks!
[Magisk] RAZINARES:
osm0sis has already explained it

Sent from Pixel 7a using ReLabs
[Magisk] ThePrinceofBirds:
It fixed mine for about 30 minutes .
[Magisk] fbirraque:
I confirm same issue here.

Stock device and a Rooted Device, none can send or receive RCS now (same carrier)
[Magisk] SkippRunning:
Then it stopped again?
[Magisk] RAZINARES:
You will have to add Play services to the Denylist again and it will work.
[Magisk] osm0sis:
Right, but...

These quotes exactly are what I was going to say. It's only a matter of time until whatever updates Google pushed read the same device status again and you're back to square one with RCS failing.

Hey, great to have you in the rooted Pixel 8 Pro boat with me at least! 😁

Bingo.
[Magisk] fbirraque:
Hi Vision,

As you possible know:

- Magisk, DenyList, works like a BlackList so you must include the apps that won't know you device already rooted... Google Play Store, Google Pay/Wallet, Google Play Services (not necessary when Play Integrity or Fork modules already installed) and others

- Magisk Kitsune Mask, MagiskHide, works like a WhiteList and just need to be enabled, so you only need to include in SUList the apps that should know your device is rooted... Revanced, App Manager, ceMIUIler, custoMIUIler, GMS Flash, AdGuard and others

Spoiler content hidden.
[Magisk] fbirraque:
The Global Carriers move to be just a IP Tunnel must end some day. The only service they will provide is data connection if some disruptive low orbit data technology don't stole it from them too.
[Magisk] ThePrinceofBirds:
Yes. Something even stranger about it is that it only worked with my wife for those thirty minutes. I have two coworkers with RCS but both of them stayed on text message only. I even double checked with one that he still had it on and he said yes. So like, partially fixed for about 30 minutes?

Pixel 7

Magisk 27002

Android 14 March update

No shamiko

Google Fi
[Magisk] SkippRunning:
Mine is still working after doing those steps, and all of my messages are being sent as rcs rather than text.
[Magisk] Ultimoose:
Ditto. Showed up as RCS long enough to test it, then girlfiend started getting "unable to send" messages and RCS was no longer available on my side. Eventually her RCS timed out and droped back to SMS and messaging worked again.
[Magisk] Ultimoose:
FWIW if you roll back updates on Messages the message pairing with a browser is no longer avaialble, it was released in one of the updates later on.
[Magisk] fbirraque:
I read as always a LOT of pages before but still don't know what he said. I'll appreciate if a direct link could be shared.

Anyway my main point is that this whole issue seems like a possible mess up from Google side, maintenance or update for some new feature that doesn't work as expected.

My suggestion is to include in reports here the Country, Carrier and if possible a test with other stock and bootloader LOCKED device. Could be region or carrier specific.

🔧 [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] Alitheia:
Exactly. Also Gemini access is lost (I'm on the BETA.) I don't want to have to use an old version just to get RCS temporarily, (though none of the steps worked for me anyway) so I gave up for now.
[Magisk] s1dest3pnate:
Used fpdownloader and cleared data and cache on Messages app, but RCS still not working. Tried denying those apps mentioned and enforcing and repeating the clear data/cache states, but still not working.

I couldn't careless about passing integrity if that's not needed for RCS. I just want RCS to work. There's a lot of discussion here and it's a bit confusing, but if anyone knows a fix for RCS (for now, but not one that only works for 30 minutes), would love to know the steps.
[Magisk] bigtlt:
So the first time I did the "fix" rcs broke when I got gemini back from Google. This time around I got Gemini back already and still have rcs. Weird. I agree, Google cannot know what they are up to.
[Magisk] trevtdogg:
if you don't care about device integrity, it seems from the reports of others that many of the old prints used will work for just rcs.

you can try installing some of the old stable @chiteroman PIF modules that come with built in prints if you don't know how to find and use an old print for yourself.
[Magisk] i5lee8bit:
{
// Build Fields
"MANUFACTURER": "HMD Global",
"MODEL": "Nokia 7.2",
"FINGERPRINT": "Nokia/Daredevil_00WW/DDV_sprout:9/PKQ1.190118.001/00WW_1_390:user/release-keys",
"BRAND": "Nokia",
"PRODUCT": "Daredevil_00WW",
"DEVICE": "DDV_sprout",
"RELEASE": "9",
"ID": "PKQ1.190118.001",
"INCREMENTAL": "00WW_1_390",
"TYPE": "user",
"TAGS": "release-keys",
"SECURITY_PATCH": "2019-12-05",
"DEVICE_INITIAL_SDK_INT": "24",

// System Properties
"*.build.id": "PKQ1.190118.001",
"*.security_patch": "2019-12-05",
"*api_level": "24"
}

Use with osm0sis play integrity fork. It's one of my really old custom prints. Should pass basic but fail device and I assume should work with RCS (for now...)

Edit: I know one of the older chiteroman PIF modules should also work, but I'd also rather use osm0sis's more stable forks in general anyway 😉

Edit2: bolded the original quote so ppl don't think this is some sort of special config. Also to make life easier for you if you're not already on the fork and/or never used a custom print before:

0. Remove other PIF modules.

1. Flash os's fork: https://github.com/osm0sis/PlayIntegrityFork/releases

2. Go to /data/adb/modules/playintegrityfix and create a file custom.pif.json and copy and paste the code above into it. If the directory doesn't exist after flashing, reboot and check again.

- It's possible that if you already had another PIF modules installed, your new custom.pif.json isn't there after reboot. Check the contents and make sure. If not, repeat step 2 and either reboot again or in terminal as root do: killall com.google.android.gms.unstable
[Magisk] s1dest3pnate:
Disabled TheFreeman193 PIFS module, installed osm0sis play integrity fix and rebooted, modified the example.pif.json and put in your code, renamed to custom.pif.json and saved in /data/adb/modules/playintegrityfix. RCS not working at this point. Rebooted, cleared messages cache/data, still not working. I am indeed no longer passing device integrity though.

Edit: Saw your edits. Confirmed custom.pif.json is still there and contents are correct.
[Magisk] 0ctobot:
I'm really struggling to understand what the point of all this is, and I don't mean to target you specifically as you just happen to be the latest person suggesting such a 'fix'.

You can fail device integrity / pass only BASIC by simply being rooted with no PIF modules installed, so why go through the process of feeding a broken fingerprint to a module that isn't currently doing anything for you, when you could just uninstall the module and achieve the same result?
[Magisk] rrusek:
FYI...

Might not be any point to this. it stopped working for me after about 90 minutes of using an old print.

Went back to the latest print and just turned off RCS chat...

Sent from Pixel 8 Pro using ReLabs