yashsingh1/xdaforums huggingface dataset:
[Magisk] sawdoctor:
I don't mean to sound harsh so please don't take it that way. You only really have 2 choices, get the developer of the ROM your using to sign a build and push an update or download his source code and compile the ROM and sign it yourself.

There's really nothing anyone in here can do short of downloading the roms source code and compiling it for you but that's a really time consuming process
[Magisk] Zaxx32:
Q: Is RCS texting working on a rooted Pixel on stock A14 with latest play integrity fix? It meets device and basic integrity checks atm.
[Magisk] angrypizza:
I already did contact the dev of the current rom I'm using.

Crdroid website doesn't say key signing requires compiling fw nor source codes

neither I did ask you to do it for me. did I ?
[Magisk] GeTex:
Probably not
[Magisk] Nergal di Cuthah:
For some no, however some yes and some "some chats yes other chats no"

Some say, non rooted non unlocked devices are having rcs problems too. (edit: according to the next post, rcs is back (I'd say for some))

I don't use rcs so i can't speak for stock rooted pixels (am on a p6p stock rooted passing))
[Magisk] Vicep83:
Seems that RCS is back
[Magisk] GeTex:
Guess I'll go get my work phone and check lol
[Magisk] Zaxx32:
Wish google would leave us rooters running stock roms alone ffs...:mad:
[Magisk] GeTex:
Googles official explanation is they are doing this to stop spam or something. All this tells me is they can't figure out how to properly handle security in RCS so their kneejerk reaction to fix this is simply, ban modded devices from running RCS under the illusion of security
[Magisk] bombadier:
Not for me in the UK it's not, did you have to do anything to get it back?
[Magisk] kornball:
Still reverting to SMS for me. Tried turning RCS off/on and going into airplane mode then reconnecting
[Magisk] Vicep83:
Yes, perhaps an interesting information : I've unrooted my phone with magisk included uninstaller, no data wipe, no bootloader locking so only Basic Integrity, and RCS have been back, or this is just a coincidence and have been restablished at the same time for me
[Magisk] Zaxx32:
Same here...I refuse to unroot so I guess I'm stuck with sms and no read receipts. damn...
[Magisk] markdewet:
I don't use RCS that I am aware of, here in South Africa, however, just to let all know that here in South Africa, with my SM-G955F on RisingOS (A13) and Magisk with @osm0sis PIF v8 and Shamiko v1.0.1 RCS shows as connected, so I assume it means it is working. Just my 2 cents
[Magisk] Zaxx32:
I show connected but when I text it reverts to sms.
[Magisk] kornball:
Yep, disabling RCS again until it's working. It's definitely annoying...

For me in the USA, RCS says it's connected, but it doesn't work. It'd be one thing if it said RCS couldn't connect, but that's not the case. Everything appears to be functioning as normal, but the phone cannot send/receive RCS messages.
[Magisk] markdewet:
Ah I see, OK, fair enough, just thought I could assist. Apologies.
[Magisk] kornball:
No need to apologize! Appreciate you offering your experience in South Africa. Hopefully it's working for you.
[Magisk] markdewet:
Thank you. As I mentioned, I am not sure if I actually use it, so cannot say for sure if it is working. I have an old S3 Mini that MIGHT also support it, I guess I can test sending a message to that phone and see.

EDIT: Nope, the ROM on the S3 Mini has not RCS support, so cannot test with that phone.
[Magisk] Wolfcity:
Yes. Here you'll find more information:

PIF FAQ

PIF FAQ Abbreviations DG = DroidGuard (SafetyNet/Play Integrity) GMS = Google Mobile Services (Google Play Services) PIF = Play Integrity Fix Frequently Asked Questions Q: What is a fingerprint and where does it come from? A: A fingerprint...

xdaforums.com
[Magisk] immortalwon:
This is what my device.mk looks like, are you sure the command on github works the right way? let me know which command at the bottom should be the correct one.

View attachment 6110486
[Magisk] angrypizza:
I just read it. but I've been told earlier that changing the /data/adb/pif.json with a working spoof won't make me pass device integrity nor get gpay to work. is that correct ?
[Magisk] Nergal di Cuthah:
If you have a working spoof then yes use pif.json. But a working spoof is hecka rare and most of us are using sailfish (xiaomi.eu served print) which is builtin to latest pif thus not needing/wanting pif.json

The fact it's a working spoof is defined by getting device in PI, and thus making pay work.
[Magisk] pershoot:
RCS is currently non-functional w./ the cur. pub. print.

Contactless payment is currently operable w./ the cur. pub. print.
[Magisk] majorfigjam:
If I have understood your previous posts, you still have an unsigned rom.

If so, you will not pass device integrity, and gpay or wallet will not work.

For them to work, you need a signed rom, and a correctly configured pif module, with a working (eg sailfish for now) print.

For RCS right now, you also need a working non-sailfish print.

For some other aps, you will need Shamiko, zygisk next and maybe hma.
[Magisk] hackthis02:
I'm trying to figure out if I'm doing something wrong or if it's just a bad time to be learning/testing personal PIF creations. But I notice no matter which fork of Play Integrity Fix I was running or pif.json I had active. The play store's integrity checker always showed my real info. Is this correct?

I'm also including two screencaps because with the same EVERYTHING within 15 minutes it went from MEETS_BASIC to MEETS_DEVICE. Which I thought was odd.

And even though I have MEETS_DEVICE now RCS is still broke.
[Magisk] purgy:
Lol, the system works!
[Magisk] majorfigjam:
Read the FAQ.

This is expected - playstore always shows your real device.
[Magisk] pndwal:
Play Store, Play Protect Service (if separate from GMS on your device) and even GGS core in Play Services all see globally set print which isn't spoofed... Only GMS unstable process (DroidGuard interface) sees spoofed print (actually complete props/field set used by PIF), and services that use that data from server end (eg find my device if you created Google account after applying PIF)... So Play Store etc shows real device details but it's still likely spoofed properly for DroidGuard measurements which is the goal.

RCS is a different matter and seems that also uses DroidGuard measurement esp. for fingerprint prop/field... Works for a different set of prints and trick seems to be to find prints that accomplish PIF w/o sacrificing RCS... RCS may work with PIF disabled (stock print/props/fields set) despite failing DEVICE_INTEGRITY... This makes having cake and eating it too difficult, and a preserve of the higher echelons (at least for now). 😜

👀 PW
[Magisk] BarackMitzvah:
Lol... this is the exact scenario that makes zero sense and wpuld be infinitely happier if it were the converse
[Magisk] Zaxx32:
Noobish question...

Does wallet tap to pay work with only latest play integrity fix and nothing else for those rooted on stock A14?
[Magisk] pndwal:
Why sound angry when people try to help/give perfectly sound advice??... Just cos you don't like the answer?... Or think it's not the truth?? (Really, you should be thanking those being helpful... You can see the 👍 button right?)

That video didn't show you need any special print specific to your device (AFAICS)! As you've been told (and people here generally have experience about how this thing actually works, better than trying to interpret YT videos and fill in the gaps), public print sets generally work on any device...

Obviously it should work if other prerequisites are met... You'll just need to take further measures if ROM is deficient in various ways, eg if SELinux (Security-Enhanced Linux module) is broken or disabled, build is only signed with test keys etc etc...

As it seems the latter applies in your case, what you were told is correct. "Changing the /data/adb/pif.json with a working spoof won't make [your device] pass device integrity nor get gpay to work". You simply need a fix for both issues.🙃 PW
[Magisk] majorfigjam:
I can't be 100% sure about the "nothing else", but can confirm that on a stock A14 Pixel 6 Pro with latest Osm0sis, it works with Google Wallet in the (not enabled) Deny List, and with Shamiko enabled.
[Magisk] Zaxx32:
Gotcha...was asking cuz wallet is showing all 4 green checkmarks regarding setup including 'device meeting security requirements' but I'm not using Shamiko or the Deny List either...(P6a on stock rom). Fwiw I'm passing basic and device integrity...if that even matters for wallet. Damn play integrity cat and mouse game has gotten hardcore...just glad I'm not running a custom rom, I'd have blown a gasket by now! :oops:
[Magisk] terlynn4:
I'm running stock on P7P with chiteroman module and zygisk+denylist. Wallet/Gpay are working for me. (RCS is not.) I'm also running Gpay checker in Tasker and it has been a reliable test so far to let me know when it's broken.
[Magisk] pndwal:
... Further what's above (assuming we're taking Galaxy S7), you don't even need PIF spoofs for passing DEVICE_INTEGRITY!... That's because only devices launched with Android 8+ have Keymaster 3+ which was Google's minimum standard for Hardware keystore backed attestation and the real purchase of PIF is to bypass Google's 'opportunistic' use of HKA... S7 never had it anyway!

Also, you'll likely even have RCS, at least with a late custom ROM, if you don't spoof to DroidGuard!...

Method for you:

With stock and late Magisk, you should also have Zygisk (native bridge Refactoring fixed Zygisk issue for Samsung devices with old Kernels), so probably only need to hide GMS DroidGuard and core processes in denylist (not enforced) with Shamiko hiding (also sets sensitive/global props to non-suspicious values).

With a custom ROM I'm assuming you'll still need a properly signed ROM for the above fix to work... That may (possibly) not be needed when not using DroidGuard targeted spoofs, but I suspect the signing checks will always be performed now... Using official LineageOS would solve that problem...

Also, you'll need a global spoof for fingerprint/security patch prop if using late official LOS (which doesn't spoof as policy) since latest stock prints (which LOS will build with) appear to be dated 09/2022 (matching fingerprint and security patch dates are needed for fingerprint sets published since 03/2018 to pass ctsProfileMatch/DEVICE_INTEGRITY), and these won't match security patch dates for AOSP used by LOS... You can just install MHPC module and configure (using terminal emulator MHPC UI) an S7 fingerprint... MHPC will spoof a matched security patch date for all prints in its preconfigured list.

👀 PW
[Magisk] zetsumeikuro:
It's because you unrooted and you're not using a blacklisted kernel/rom.
[Magisk] Juleast:
Well, people have reported that RCS isn't working with play integrity passing but I just wanted to share that my sister's Pixel 6a with a locked bootloader couldn't send any RCS messages a few days ago either so I think it's still to be decided whether this is an issue with play integrity.
[Magisk] majorfigjam:
Couldn't send any to any device, or couldn't send to a device which itself had a broken RCS setup?
[Magisk] pndwal:
Well...

FWIW, I commented on reasoning back here:

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89386898

Source info:

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89429081

🤠 PW
[Magisk] Juleast:
She couldn't send to devices that had locked bl. I believe one of the recipients had a Samsung. So this could just be a Google servers issue.
[Magisk] pndwal:
... Specifically because no longer spoofing fingerprint or prop/field set Google has 'banned' for RCS purposes or that they are using for current round of tests, and Google server (clearly using DroidGuard supplied device info for this) now sees real device values which allow RCS. 🤠 PW
[Magisk] zetsumeikuro:
I've uninstalled PIF and deleted the pif.json and still didn't get RCS while rooted on my P8P. More Gulag moments. With this "experimenting" complete for now. I'll just go back on my working print and hope for better future solutions.
[Magisk] pndwal:
Are you passing BASIC_INTEGRITY ATM?... Stock ROM? Turned RCS off then on again?... 🙃 PW
[Magisk] zetsumeikuro:
Yup, that's what I did after I removed PIF etc and made sure everything was 100% stock. My only answer is Google logic.
[Magisk] deechte:
Can someone open an "RCS is broken" thread to stop the off topic here once and for all?
[Magisk] simplepinoi177:
it's in a device specific forum, but....

RCS broken (again) after update. Any new fix?

Just updated my P8P to AP1A.240505.005 and RCS broke once again. I'm using PIF (Chiteroman) with FP downloader from daboynb Magisk has all google apps on denylist Storage was cleared from play store, play services, messages and carrier services...

xdaforums.com
[Magisk] osm0sis:
It's also kinda on topic 🤷‍♂️
[Magisk] pershoot:
RCS now uses Play Integrity, for intents and purposes, therein. It is on topic and can be quite critical as it disrupts communication. However, this may or may not be pertinent to you, specifically, depending on your use / use case(s).
[Magisk] GeTex:
Its very on topic, it's just annoying because it's tied to droidguard and not exactly tied to play integrity itself.
[Magisk] mrjuniork:
Unless the OP says otherwise, RCS stuff is being considered on topic.

Since the beginning of this thread (more than 800 pages, 16000 posts and around 1m views), this topic has opened a huge box of contents, which are intertwined in so many ways, hence the sometimes occurring confusion if some topics and/or posts are Indeed off topic or not.

It's being handled with as much touch as possible 😉

Thx for helping and supporting each other, sharing knowledge with each other. That comes a long way.

Cheers,

mrjuniork
[Magisk] recall1:
Hi Guys,

Yesterday i updated my PiF 15.9.7 Module to 15.9.9 directly inside Magisk 26.4 because Play Integrity API Checker suddenly said Device Integrity was not met.

After updating i do not receive Whatsapp Mesages anymore uness i open the app....thats a HUGE Problem....

Oh and Device Integrity still not met.

I tried various things: Uninstalling the module, reinstalling 15.9.7 Module, fashing NikGapps again, Deleting Play Services Cache and Data....No luck

Does anyone here know how to solve this???

Thanks!
[Magisk] chiteroman:
I consider it to be on topic, what's really annoying about the thread is users complaining that some apps (especially games) don't work, most of it is the fault of not properly hiding root / Zygisk / LSPosed...

If you pass the Device verdict and an app doesn't work for you, 99% of the cases it's because there's something wrong with your setup, and the remaining 1% might need the Strong verdict or a valid hardware attestation.
[Magisk] manjaroid:
With my last known-good private print still hanging on, osm0sis's fork, no Shamiko, Wallet and RCS work for me. I'm running stock A14 on a Pixel.

As others have described using the last public print, device integrity still passes but RCS stops working despite a couple appearances that it works. Wallet appears to work but I didn't spend to verify 100 percent.

Could RCS protocol or networks be a problem? I don't think so. No problems reported from my messaging peers (all locked, no root, 2 of 3 US carriers) except for messages not received while RCS stopped on my end. When RCS stops you may still see the RCS prompt but as soon as there's some back/forth or just a single sent message, the prompt switches to SMS (I have 'Resend as SMS...' enabled).

Could RCS group chats be a problem? I think so. There's a pattern that boils down to good/bad/indifferent spoofing but I also ran into Google Messages breaking in a way not seen before. While RCS wasn't working for me using the public print, a group message to RCS recipients didn't send at all and remained stuck after reverting to SMS. Even after reinstalling the private print and getting RCS back, that message wouldn't resend and the whole group thread was borked with unusual errors. I ended up deleting the thread and starting a new one to communicate with the group.
[Magisk] sawdoctor:
Do you have playcurl or anything else similar? Try manually deleting your fingerprint and then flashing latest pif module. It sounds like it's still reading your old print
[Magisk] pndwal:
What custom ROM?... PW
[Magisk] 306bobby:
Now this is interesting. About to swap a sim to my other unlocked phone and see if RCS works between the two
[Magisk] 306bobby:
Your ROM prob isn't signed
[Magisk] 306bobby:
Wallet does indeed work. RCS group chats don't, my phone created an MMS chat in place of it and I stopped receiving from the RCS group.

I've had your issues with the message, it's due to if you have an unsent message with one set of encryption keys, then turn off/back on RCS, behind the scenes a new encryption is used between the users and the message becomes invalid
[Magisk] angrypizza:
will the xiaomi served print setup be enough for device integrity or will I still need to sign the rom
[Magisk] Khnome:
For me rcs was fine on locked stock hyper os 1.0.3 but ded on custom roms with personal pif.json, same device.
[Magisk] Khnome:
Out of curiosity I will flash stock with bl opened
[Magisk] immortalwon:
I just used another working print that's not sailfish but RCS still doesn't work on a custom rom, which means either that RCS is disabled for people with unlocked bootloaders or CR are not supported.
[Magisk] angrypizza:
can you quote the bit I asked you or anyone else to compile things for me.

crdroid website doesn't mention compiling to sign keys and tbh I couldn't ask for something I wasn't even aware of.

I am pretty sure the rest of your message have very good points. if you'll summerize it I'll read it.
[Magisk] generalculprit:
I still have a Lineage device with working RCS and DEVICE integrity (sailfish). 🤷‍♂️

Edit: It's dead, Jim.
[Magisk] Khnome:
Rooted hyper os, no modules installed. RCS working.

View attachment 6110713

View attachment 6110714
[Magisk] immortalwon:
Maybe I am missing a certain service? I have nickGapps full version installed.
[Magisk] pershoot:
This is known and has been reported in this thread. If the print is not banned for RCS purposes (which in this case is your stock device's print which is not being spoofed), then you can continue using the service without issue, if you do not pass DEVICE (in your case it is because your BL is unlocked). Your contactless payments will not work in this scenario.
[Magisk] Hovvinko.cz:
Hi. I'm quite new with this so I need help. I have rooted my phone and installed PIF and my play store stopped workingView attachment 6031049
[Magisk] Hovvinko.cz:
I'm geting Unknown internal google server error when I check integrity on play store
[Magisk] xlxcrossing:
Color me surprised this fixed my "doesn't meet security requirements message" that appeared today after a year or so of using an unrooted stock based A13 flawlessly with Google Pay. I have basic and device integrity up and it's working well.
[Magisk] pndwal:
But in this case we're talking about a utility (Play Integrity API Checker or similar) used mainly by modding community members, not by bank users... We're also NOT talking about a banks calls to PI API, who's quotas are likely much higher/negotiated anyway. See

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89150954

And of course this error has nothing to do with Google server failures...In cases where that might happen however, banks can simply set a variable period before which a passing attestation must be obtained... Nb. Some banks that do do 'in house' detection actually begin a countdown (eg 2weeks) 'grace period' after detecting 'modified environment' and bank app will only fail after that, eg Starling Bank, but yes, their detection methods can be more reliable than PI API's DEVICE_INTEGRITY.

Not sure what you meant here, but the existence of the independent "Key and ID Attestation" model does beg the question why they look that particular Google gift horse in the mouth... While it should be done server end, I don't know of instances where they even do it locally in app... I commented here:

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89150943

🤠 PW
[Magisk] re_endymion:
Same error here after replacing. I've uninstalled Play Integrity API Checker and install and used SPIC in place!
[Magisk] marcopit-92:
Hi guys a question a little OT. My Marriott bonvoy app is detecting root and seems there is no tool or tweak that can hide root to this app, it's been almost 7 months I am trying to use it but nothing, not even with PIF. Is there someone that maybe knows a solution for this super secure app?
[Magisk] sawdoctor:
Try different combinations of Magisk. Maybe Magisk alpha with shamiko or magisk Delta with HMA etc . Sometimes it's zygisk that gets detected sometimes it's a rogue xposed mod
[Magisk] hayvan96:
Thanks, like others Wallet stopped working yesterday. I've switched from Displax's safety fix to PIF, cleared cache and storage of Wallet, play services and store, rebooted, and voilà. Of course had to add again my cards, which is straightforward
[Magisk] straumli:
I can confirm this works great to fix my recent Google Wallet root detection issues on my Pixel 7 Pro. I installed it as the only module in Magisk Delta Canary. Thanks for providing this!!

Could someone perhaps advise if this module could be paired with additional modules to pass SafetyNet, ideally so Microsoft Intune (Business Portal) is not detecting root as well?
[Magisk] Rom:
I test the new 12.1 just now and same issue happen.

Will test next versions so.
[Magisk] alkandery75:
Hi,

Thanks a lot for your Module Update, it's the only one working now especially with Mastercard Travel Pass App. However, due to Play Protect not being certified, the Mastercard App keeps asking to upgrade the Google Play Store.

Help is highly appreciated,,, 🙏
[Magisk] cray-:
Poco X3 Pro, MIUI 12.5.1 Global (prob should update, can't be bothered), Magisk 26.1.

Wallet stopped working yesterday like everyone else. Pretty sure I was running PIF v2.0 from around July? Updated to v12.0 last night. Wallet worked again today. Didn't clear any caches or mess with timezones. Thank you for keeping up with this crazy wack-a-mole game.
[Magisk] zgfg:
Yes, module works fine on MIUI 12-12.5

However, it's spoofing now to Asus ZenFone (PIF logs) don't work on MIUI 14 and cause even Basic attestation to fail
[Magisk] bobby8921:
Still not working after I disabled AdAway.
[Magisk] tryigitx:
View attachment 6031066

Only feedback regarding API limitation is irrelevant.

Also, the extra fix for EU ROM is unreasonable, this is the ROM developers' own problem. There is no need to worry about unofficial roms.

Updating is unnecessary for problems caused by prop files. You can use shamiko by removing the codes like me.

I expressed my opinion about improvements other than the purpose of the module, so it seems like it is more important to try to find the strong vulnerability and comply with Google updates.

So: do not beg and soup the module developer for functions outside the purpose of the module