yashsingh1/xdaforums huggingface dataset:
[Magisk] GeTex:
Because if you don't spoof the fingerprint, you will be present a userdebug fingerprint which WILL NOT allow RCS, you need to spoof a user release key which is only found when the bootloader is locked.

Depending on your device and os version, some prints aren't compatible, as the working print on my nexus doesn't work on my pixel for example.

Probably need to try a different print. Or give up on RCS. I'm really finding myself constantly disappointed and paranoid thanks to these latest arbitrary changes from Google with RCS. It's day like this I actually have told myself I either might have to go to locked stock or I might even buy an iPhone because at least it just works. And I can't stand iPhones.
[Magisk] i5lee8bit:
Honestly my ultimate point has always been the same as what osm0sis suggested like 5 months ago which unfortunately is even harder than it used to be back then: find your own working custom print. That's been the best suggestion that has rung true since all this tightening up started. Otherwise the ultimate fix is to unroot and lock your bootloader. The barrier of entry is going up and while I don't like it and I'm as pissed as the next person, it's the unfortunate truth of the matter right now.

Also I'm not sure if using absolutely NO module will still allow RCS to work. There are other things the module does than only "feed a broken fingerprint". But perhaps you're right, I just haven't seen anyone test or report it yet. Like I said before, I'm using my own custom print AND I DON'T EVEN USE RCS so I really don't even have a reason to test other than sheer curiosity and to hopefully contribute towards learning more about the situation...

Edit: @GeTex ninja's me to it with a much better explanation, lol thanks. And also was gonna reply to @s1dest3pnate that I did test on my Pixel 4 XL (A13) with the same BASIC-only Nokia print and was able to RCS. So at least I can confirm it does work on my particular device.
[Magisk] GeTex:
I originally ended up here because RCS stopped working without a spoofed print on two different devices. I had never even heard of play integrity fix until January. If I disable the modules RCS stops working in under 24 hours guaranteed.

@chiteroman @osm0sis seeing that RCS doesn't actually care for device integrity, but it cares about the specific fingerprint in use, and you two are the active module developers, this thread is splitting into two distinct issues. People who want to pass device to use Wallet, and people who want a valid fingerprint to use RCS. I'm unsure but perhaps the topic should be split into a new thread as I can see this becoming very confusing? Just wanted to say something before it gets any more split and confusing for people.
[Magisk] fbirraque:
Hi @osm0sis

I'm sorry in advance if I'm missing something but how could this issue with RCS be related to Play Integrity Certification if even my not rooted Sony 10 Plus and with locked bootloader after the last update of Carrier Services and Google Messages couldn't send or receive RCS anymore?
[Magisk] Nemosfate:
Pretty much agree. I use PIF for RCS on my phone and gave up to only using GPay on my pixel watch.
[Magisk] GeTex:
I have seen multiple people saying this, uninstalling the recent updates to messages and carrier services may resolve your issue for now. I think Google fired the shotgun to wide spread and is actively breaking RCS even for stock users.

I've been worried about this for a while. When a finger print is "banned" what happens to stock devices running those fingerprints too? Do they also stop working???
[Magisk] fbirraque:
So it's a messed up from Google side then nothing to do and it isn't Play Integrity related. A new update must come to fix it soon.

But it's just my opinion!

NOTE: My Device passing BASIC, DEVICE and even STRONG. As I mentioned it's non mod and with locked bootloader
[Magisk] acwcanada:
He is not rooted and bootloader is locked, the picture he included showing that his device passed all three including strong which supports his claim, where you get the impression that his device only passing basic?
[Magisk] bdr127:
Asking again today since I didn't get a reply yesterday...

Is there an easy way to check if RCS is actually working if you don't know anybody with an Android phone using RCS? Literally every single one of my extended family members, neighbors, and friends all have iPhones... :rolleyes:
[Magisk] GeTex:
There is not, DM me, I'll give you my work phone number

Im actually working on getting a 3rd cheap phone number just for users to text RCS to test for now
[Magisk] GeTex:
I get the impression from my eyes failing me
[Magisk] majorfigjam:
Since the answer is no doubt lost in the hundreds of preceding pages, I'll repeat it yet again.

Stock locked devices with "banned" prints are not affected by the ban. If you need technical detail as to why, then search the thread.
[Magisk] acwcanada:
If I understand user fbirraque's case correctly, seems there are normal users which they don't know anything rooting their phones and are using RCS right now got the same problem as most of us here. So we may all barking on the wrong tree, may be it is only simple that the big G did some stupid mistake when they upgrade their message app.
[Magisk] osm0sis:
F to the A to the Q
[Magisk] fbirraque:
That's exactly my best guess.

The Google's movement seems so stupid for me that's I doubt even the Gemini AI could do it.
[Magisk] GeTex:
Let me try and be slightly more clear. I am NOT talking about for integrity, I am talking about RCS which users are having issues with while still even passing integrity. My stock Pixel 4a lost RCS last night as well, simply rolling back a single OEM build and getting off the latest restored RCS. Update to latest and it breaks. I'm still trying to figure out whats going on.

EDIT: I have no idea whats going on anymore. My P4a RCS is working again on latest when I switch simcards to use a different carrier, switch back and its broken on latest. Google wtf???

EDIT2: Ignore me, just questioning my sanity, everything works on my 4a again, my 6p on 8.1 works with the public print in Play integrity fork but not platy integrity fix, my pixel 1 works with no public prints but works with my private prints, my P4a lost RCS on VZW but works on TMO but after a factory reset works on current again with VZW. Im so confused. Think I've done enough embarrassing myself for the night, sorry everyone!
[Magisk] pndwal:
Because this has been repeated several times, please notice that @osm0sis didn't really say that; just that users with griffin print (that seems to break RCS) may be able to get RCS going when PIF module breaks due to denying modifications to the GMS DroidGuard/attestation (com.google.android.gms.unstable) process.

This is because RCS is somehow seeing the print or print set sent to servers by GMS which will be the native devices print/props/fields if PIF is broken this way simply because Zygisk module parts, including the fake keystore registration (resulting in on-device fallback to BASIC-only attestation) and, critically for RCS, the Driodguard-targeted prop/field spoofs (resulting in the griffin print set being sent in attestation data to the Google PI back end to spoof a device slated to accept a BASIC-only server side evaluationType) cannot work since the modification is denied/reverted for DroidGuard (which sends the attestations to G via GMS core)... With PIF broken, RCS can succeed or be reset as long as the devices native print set (now seen by GMS and PI back end) is not rejected by RCS.

Nb. that denylist mode breaks PIF if active with the DroidGuard/attestation process in the list... Solutions using hidelist mode (proper root/mod hiding) like Shamiko module, old MagiskHide, stand-alone MagiskHide modules, Delta/Kitsune hiding implementations, DenylistUnmount module etc. won't break PIF as they don't work by reverting/denying Magisk or module modifications, simply by hiding root and modification traces and spoofing non-suspicious signals (props and more).

... FWIW, It still seems likely to me that RCS may be obtaining print and other data from G server PI back end just like Google registration, Find device and other facilities do. This may still be experimental resulting in observed RCS failures on stock/locked devices, and may or may not involve cross-checking a print set obtained by different means (eg Play Store obtains native print/prop information despite PI API recieving the spoofed set), meaning that RCS may not break on devices where the targeted/spoofed print set matches the native (global) set (eg stock/locked devices)... Of course there are likely other kinds of cross checks, algorithms etc at play here also.

👀 PW
[Magisk] zgfg:
If you have a custom ROM with userdebug prints it doesn't mean that the others here must have

Ppl may have stock firmwares with just Bootloader unlocked and Magisk or KSU installed

Or there are ppl here with custom ROMs like Xiaomi.eu that also comes with rekease-keys

Hence for them, with no PIF, they pass Basic Integrity. And the propsed 'guide' does nothing else than telling RCS that you 'switched' from one one phone/ROM to another, for the beginning it's enough to pass Basic only, but after some time RCS will recognize and stop working

So let's 'extend' the 'guide'. Every hour, when RCS stops working, change from one prints to another that passes Basic only - and forget Wallet and other apps that require Device Integrity 😁
[Magisk] PH_Android:
Getting errors with autopif.sh, please see image
[Magisk] zgfg:
Issues with your Terminal Emulator. Use something simpler than perhaps Ternux

There are also other ways to do exactly the same - ie, to obtain the Griffin prints from Xiaomi.eu injector.

The easiest: use PI Fix module from chiteroman, it comes with the built-in Griffin prints

Or, take the attached custom.pif.json and follow the guide how to 'install' for the PI Fork module
[Magisk] Ultimoose:
Not that I'm aware of friend. It will show connected just fine, its only when you have a thread with someone on RCS that you'll be able to validate the E2E and see the "neener neener you don't get this anymore" message from Google.
[Magisk] PH_Android:
Thank you. Chiteroman's Pi Fix helps me pass basic, but not device integrity.

Went back to osm0sis' PI Fork and tried your custom.pif.json. Play Integrity API Checker causes my phone to hang.
[Magisk] Vision:
Yeah i know it, because me too i have Kitsune Mask.

Thanks for extra info. I appreciate.

Yeah, i mean if Google make the same in the phone app like he did in messages with rcs
[Magisk] CZ.Kostra:
Uninstall PIF and reboot. Then do a 'clean install' of PIFork. Place 'custom.pif.json' in '/data/adb/modules/playintegrityfix' and reboot your device again. Test the integrity.
[Magisk] ardiesel:
I don't know if it matters, but I have found that people trying to message me are sending through their own RCS and their phone thinks I am on RCS even though mine does not work. Subsequently, I am not receiving their messages at all, hence since theirs is not broken on stock and theirs thinks I am connected, theirs are not switching to sms to send. Theirs is sending but I am not receiving.
[Magisk] zgfg:
Make sure you followed everything from the FAQ, starting with Zygisk, DenyList, etc

Find also how to take PIF logcat to see does the module spoof as expected

Every time when you change the module you nust reboot (basics of Magisk usage)
[Magisk] osm0sis:
That's stuff that's in the README, but yes. 👍
[Magisk] bombadier:
Turn RCS off
[Magisk] PH_Android:
Thanks, did 1 and 3 earlier but got the result I posted. Will do PIF logcat next time.
[Magisk] Dark_Eyes_:
I guess you guys have already figured this out, but I tried removing PIF completely, I don't even pass BASIC now but RCS works like a charm... P7P stock ROM.
[Magisk] zgfg:
For some time - check and update over an hour or more
[Magisk] Mr. Apocalypse:
This is what i ended up doing this morning on my stock Pixel 7 Pro, RCS came back almost instantly on the next reboot. If Google doesn't get their crap together both this 7 Pro and this Watch 2 is going in the trash.
[Magisk] 0ctobot:
Well, no, that may be the case if you're on a custom ROM but not if you're on stock, which I am, and I would assume a good majority of Pixel users are so at the very least it would be a good distinction to make that if you're stock simply uninstalling the PIF module will bring RCS back.
[Magisk] Reznor7:
Can someone link me an FAQ or wiki so I can learn more about what this module is actually doing in its spoofing attempt. I'm on a stock, unlocked, and rooted OnePlus 11, and I'm having the same problems as others. With PIF, integrity/safetynet pass, but no RCS. I'm confused as to the difference between public and private keys that some claim to have. Been rooting Androids since my first Motorola Droid Bionic, but these current developments are making me feel like a noob all over again!
[Magisk] AiM2LeaRn:
im a bit confused, when you say "removing PIF completely", do you mean:

deleting the /data/adb/pifs folder?

or uninstalling the magisk chiteroman module?

or BOTH deleting the folder and the module?
[Magisk] miXOnIN:
Hi guys!

I have 2 devices OnePlus 9Pro and OnePlus 3T, both stock with root access (Magisk 27.0)

I had Play Integrity Fix v15.9 installed, both devices successfully passed MEETS_DEVICE_INTEGRITY, but a few weeks ago 3T began to pass only BASIC (9Pro works well)

What I tried:

1. Updated both devices to Play Integrity Fix v15.9.6 (9Pro works but 3T doesn’t)

2. Installed the same /data/adb/pif.json (9Pro works but 3T doesn’t)

3. Installed another module on 3T (Play Integrity Fork v8), generated custom.pif.json

4. Tried to exclude com.google.android.gms from DenyList

5. Cleared data in PlayMarket, Google Services, Wallet...

Since this key works on OnePlus 9 Pro, I believe that it works; previously on the 3T everything worked the same for the last few years with the 9 Pro, I don’t know what has changed.

Please help!
[Magisk] ashish1989:
Same case is with me, I also have two devices i.e. Oneplus 6 and Samsung J7 Prime, both with custom rom. On my Oneplus 6 with same setup everything works but not on my Samsung J7 Prime with same setup. Everything is different for every device I think. In short Go_gle is the culprit.
[Magisk] neonblind:
Welcome to the club, my two older devices didn't pass device integrity as well with the griffin print. a sony x compact with stock android 8.0 (since some weeks) and a lenovo tab with stock android 8.1 (since wednesday).

which android versions are your devices, the j7 prime and the OnePlus 3T?
[Magisk] ashish1989:
Oneplus 6 - A14

J7 Prime - A9

J2 2016 - A7

Oneplus 6 has no problems at all
[Magisk] neonblind:
J7 Prime - A9 -> that seems to be the culprit. most of the users griffin failed are on android 8.0, 8.1 or 9. google did something here (api 26-28).

i asked @miXOnIN for his OnePlus 3T :)
[Magisk] cmstlist:
Well I do appreciate the broadcast message on the Telegram channel... I'm on my last day of a 2-week trip and would not have known my RCS had started failing without that broadcast. Too busy today to figure out any better solution than disabling RCS. Hope the community figures this one out.
[Magisk] Ultimoose:
Yes report back after an hour or two have passed if it's still working. So far various things have gotten it to work temporarily but in the end without a private print nothing seems to stick.
[Magisk] miXOnIN:
@neonblind

3t - 9

9pro - 11
[Magisk] neonblind:
@miXOnIN

yeah, A9 again. i think the only solution for now is to find another working print for these old devices. i think every print from the freeman repo is banned. someone tested it in this thread. i can't find a working one for myself. its a frustrating process when you cant write scripts and automate the process somehow.

maybe you find one yourself: https://dumps.tadiphone.dev/dumps

🔧 [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] Nergal di Cuthah:
Nearly, i think 2% worked based on post 29 February tests

However freeman closed the repo
[Magisk] osm0sis:
0% in arm or arm64.

There are about 30 (total, not percent) left in all of tadi.
[Magisk] GeTex:
Good point, I'll show myself out
[Magisk] zgfg:
For me RCS (and Wallet) is ok - but with 'private' prints that do pass Device Integrity
[Magisk] forserg:
It is rediculous. I flashed latest stock firmware with patched AP file trough Odin, plus flashed latest magisk zip trough TWRP. After reboot still no magisk, no root rights. Installed magisk.apk, still no option to fihish set up. How long can I dance with it, more than week past by:) Any help?

SM-G975F, Android 12
[Magisk] 0ctobot:
Just wanted to add, after reading this I went on a deep dive for obscure 8.1.0 devices that were exclusive to a particular country and it seems I've also managed to find one that is both passing device integrity and allowing RCS transmission, for what it's worth.
[Magisk] rrusek:
Sorry the the noob question. Just recently got into the whole PIF thing (due to the RCS issues). not really sure about the 8.1.0 to the 6.0.1. Is there somewhere you can try to point me for a clarification? Trying to figure out how to get a working print.

Thanks,

RJR

Sent from Pixel 8 Pro using ReLabs
[Magisk] trevtdogg:
if your only issue is RCS and you are running a stock rom then remove any PIF modules and it should work.

If that doesn't work, you can try an old public print as many still work for RCS even though they no longer give device integrity.

if you need device integrity as well, then you'll need to privately find one of the few other remaining working prints to use.
[Magisk] Vision:
For all noobs.

Please first read the excellent guide by @osm0sis is explain everything about this, and if you still don't understand, then ask here

You can find it in the

TOP LIKED POSTS - All time scroll a little and 178

View attachment 6086418
[Magisk] AlexS2412:
is the telegram group gone? the app seems to say it no longer exists.
[Magisk] Vision:
View attachment 6086422
[Magisk] bentree:
I'm starting to think that RCS not working is a broader issue. My partner has a locked Sony 1II and as of this morning she no longer has RCS. Her RCS was working fine when this all started originally. The messages simply fail to send on her end. Don't know what google is doing but it's screwing up stuff.

Cheers, Bentree
[Magisk] i5lee8bit:
Someone else also mentioned something similar. Hopefully big G actually screwed the pooch in such a big way that it makes headlines again and they need to back off a bit for a while and make things a bit easier for us.

...doubt it though lol
[Magisk] aliantonio:
I removed PIF module and RCS still isn't working on latest messages app. If I uninstall updates and downgrade the app, it works. So it seems something in the latest app version is detecting root also.
[Magisk] RAZINARES:
Have you tried adding play services to the denylist?
[Magisk] intel_core_i7:
Let's see what Google has to offer on April Fools
[Magisk] aliantonio:
Yep. Still not working. RCS says connected but only sends as SMS
[Magisk] pndwal:
I already told you, YOU CAN'T flash Magisk as .zip on your A-only legacy SAR Samsung device!!!

You MUST ONLY patch via App with Recovery Mode selected and then boot via Recovery!!!

On your device magiskinit must be injected in /recovery ramdisk... Installation should work (only) if you see and select Recovery Mode before patching AP, flash patched AP with all binaries and boot to system with Magisk via recovery key combo (with key release timing considered)...

If you do all that (not just boot to system or reboot) and app still doesn't detect Magisk/root, it's possible you may still have a hidden Magisk App (ie. stub with custom name) installed... Remove any instances via device settings, Apps, and reinstall full Magisk app if necessary... 🙃 PW
[Magisk] s1dest3pnate:
I can confirm the same. Thanks for letting us know!
[Magisk] V0latyle:
This may depend on the device/build...

Many Samsung implementations don't seem to work if Magisk is installed the "right" way by patching the AP file. Certainly doesn't on my T290. However, flashing TWRP, then installing Magisk via TWRP, seems to work pretty well for most. It's no longer officially supported but it works well enough.

I suspect he's dealing with a different problem, likely the stub as you mentioned.
[Magisk] osm0sis:
You probably just needed to wait longer for the fail state to reset...
[Magisk] s1dest3pnate:
No, it definitely didn't "feel" that way. I installed a custom pif a couple hours ago, and cleared cache/data on the relevant apps, and let it sit for some time and RCS was not working. As soon as I had "uninstall updates" on the Messages app, RCS started working again. It's pretty clear to me there is something in the latest app versions that is blocking RCS for us now.

Edit: I can also replicate the issue. If I install the latest Messages again, RCS immediately stops working. If I uninstall updates, it immediately starts working again.

Edit2: Standby. I tried installing Messages beta to see if it would work on that, and it doesn't. And then I uninstalled updates again and now it isn't working again.
[Magisk] chiteroman:
Strong for everyone!
[Magisk] intel_core_i7:
I wish :ROFLMAO:
[Magisk] fbirraque:
I also have a Sony Xperia 10 Plus with Stock OS and Locked Bootloader.

For a few days in the past week the RCS didn't work either but today everything seems to be flawless again and I didn't change anything.

Spoiler content hidden.
[Magisk] osm0sis:
Obviously it's part of the updated app, my point is waiting or just wiping app data would also do the trick if you removed your PIF json/module or switched to a different working print.

We're in the middle of methodically testing this right now and so far that's the case.
[Magisk] pndwal:
Of course... This specifically concerns A-only L-SAR devices as I made clear.

These are basically the only devices where installing Magisk via TWRP is not an option if Bootloader doesn't support Magisk in /boot partition however.

S10 series was originally mentioned by John Wu as being among "The worst type of device to ever exist as far as Magisk is concerned" (Type III boot type, Late 2018 - 2019 devices that are A-only, all launched with Android 9), requiring Magisk installation in /recovery ramdisk because of lack of bootloader support for ramdisk in /boot which is why changes to allow for Recovery mode Magisk were added... Nothing has changed for most devices needing Recovery mode Magisk; S10 series bootloaders haven't been updated to accommodate ramdisk in /boot so in-App flashing is required. (Installing via a custom recovery, eg. TWRP, CANNOT work since that will only ever patch boot.img or initboot.img.)

... Sure, other A-only legacy SAR (A9 LV) devices, notably Xiaomi, broke the mould by retaining bootloader support for ramdisk in /boot even though not used by the OEM implementation, so further changes in Magisk (to add basic ramdisk parts to boot.img on devices where "Ramdisk= No") were made to allow traditional Boot mode Magisk installation in these devices... Few (if any) such (A9 LV, A-only) Samsung devices have the requisite bootloader support for this however. 👀 PW
[Magisk] s1dest3pnate:
Gotcha, didn't know it was already understood the latest app had something to do with RCS not working.

My RCS is back to not working again though. Maybe my custom fingerprint is no good...
[Magisk] Ultimoose:
Nothing seems to be a permanent fix other than having one of the few obscure non-banned prints left. Downgrading the app lets it work for a little while but it then breaks again. I've tried a few things as a semi-educated novic and I could get it working for a little while but inevitably within 30 to 60 minutes it dies again or RCS never connects for me at all.