yashsingh1/xdaforums huggingface dataset:
[Magisk] GeTex:
My 4a stopped working on stock for a short bit, but then started again, did my device possibly switch A/B groups? My Nexus lost RCS on chiteromans module but yours still worked, my pixel didn't work on either module but worked on my custom print.

I'm always just anxious I will wakeup to broken RCS again lol.

I sent you a DM with a number to test RCS a few days ago
[Magisk] D€INOS:
FYI, I sent rcs messages from a locked bootloader work phone yesterday to my private phone with Griffin print and I didn't receive those now when rca went back on.
[Magisk] GeTex:
Are you messages on your work phone in the state of "sending" 'sent" or "failed to send". Just curious
[Magisk] casouzaj:
Until yesterday, my Xperia 1 II, running LineageOS 21, and my wife's Xperia XZ2 running LineageOS 20, although our RCS settings showed as 'Connected', could send each other SMS/MMS messages only. From today, we are being offered RCS messages to be sent, instead.
[Magisk] YHMWU7Rc9TkDAtu4NT6:
Just updated to chiteroman v15.9.7 from github ( updated through magisk app on the phone ).

RCS working, able to send and receive messages between two phones ( stock one where RCS never broke , and rooted daily driver with lineage OS )

Thank YOU chiteroman 🫡

May pestilence befall the house of Google , for these "RCS SILENT FAIL" shenanigans :poop:​
[Magisk] Nergal di Cuthah:
Please read the above posts which state it was not due to module update, it began working for everyone update or no, fix or fork
[Magisk] YHMWU7Rc9TkDAtu4NT6:
Yes, first read the thread ( past 12 hours worth of posts ) , then checked the phone , RCS was not working even after Restart+Disable/Enable RCS+Restart & waiting for 30ish minutes.

Then, noticed the github notification for the v15.9.7 Play Integrity Fix , tried it. Usual Install+Reboot+Enable/Disable RCS+Restart.. and after about 5ish minutes was able to send and receive.

Not sure what worked. 🤷

My whole issue with all this is "Silent Fails" ... You wanna knowingly/unknowingly break functionality, go ahead do it. But please throw up obvious errors for senders and receivers. Had someone email to ask me why my phone was off or broken because messages were not being delivered.
[Magisk] ThePrinceofBirds:
When I had used one of the methods to get it to work again momentarily (about 30 minutes) I had noted that it only worked with my wife and not with my two coworkers who have RCS. The coworkers are definitely on stock. Now that it's back for everyone RCS is working for them too.

Just thought I'd mention it again because it lends to the theory that whatever they did, if purposeful, was causing false positives for normal users.
[Magisk] V0latyle:
I still think the RCS issues were something bigger, not necessarily due to root. It started failing on my wife's locked stock Pixel 5a a few days ago, and has been intermittent for me as well - at least when downloading media. It seems a lot of non rooted users were having issues too.
[Magisk] osm0sis:
Then why did switching from the griffin print to a different working private print get RCS working again for all who found one? The evidence was pretty clear.
[Magisk] GeTex:
I switched prints and immediately had RCS again. Google has been denying RCS based on the presented print. Just this time they banned a lot more then just their intention is my guess. I hope it isn't a sign.
[Magisk] osm0sis:
Also seems like the end of every month is now officially "f*ck with the PIF crowd" day over at Google. 🫤

Late January was the kernel strings ban, and a number of print bans, removing vast chunks (often with clear Android version or security patch date cutoffs) of previously working prints for many devices.

Leap Day in February was of course the mass ban of 95% of known working prints.

Late March was the RCS restriction test on the current mass-used public print, while keeping it otherwise SN/PI passing (though it was also narrowly preceded by several reports of it starting to fail SN/PI on older Android versions/devices).
[Magisk] pndwal:
Cos it wasn't one thing or the other; both things were happening and obscuring the cause... More fiddling will no doubt be done before iOS w/ RCS joins the party IINW.

FWIW, I put stuff in that lot about iOS RCS take-up etc too. PW
[Magisk] AlexS2412:
mine is stuck on "setting up" for rcs and my myaccount.google.com/phone says auto verification is pending for a day now. despite this fix probably working for everyone else i think Google or my carrier blacklisted me for trying to verify too many times. any ideas?
[Magisk] majorfigjam:
If you have 2/3 device integrity, then the old method of uninstalling updates to the messages may work. If messages is not a built in system app, then uninstall fully and find an older apk on a parallel store.

Once the RCS verification works on the old version, you can update again and it should carry on working.

If you don't have device integrity, ie no working fingerprint, RCS will work at first but then break after a while once it has updated, as RCS needs device integrity. Or it used to, before google played round over Easter.

If it breaks, you'll need to follow the faq post to get device integrity, then try again.
[Magisk] justDave:
Try clearing the data for carrier services.
[Magisk] GabbyWC:
Try the instructions here and see if those two steps work for you.
[Magisk] AlexS2412:
So ive fixed it. the solution was to go into the settings app, and under the google account settings there is a hidden tab for mobile data and messaging. while on data only i had to toggle auto verification off and on, after having turned off the deny list, used the may version of messages with latest play integrity fix 15.9.7 and shamiko, as well as clearing data for all play services and carrier services, then i was able to verify rcs and it finally works. **** google for hiding these settings View attachment 6086903View attachment 6086904View attachment 6086905View attachment 6086906View attachment 6086907
[Magisk] trevtdogg:
since we've seen that RCS does not need device integrity to work, should we move any RCS discussion to a different thread and keep this thread for play integrity?

I'm sure there are many others like myself who don't use RCS and this is all mostly off topic now I believe.
[Magisk] majorfigjam:
In fact, RCS seemed to have needed device integrity to work.

While the recent issues have shown that having device integrity may not be sufficient to enable RCS, not having it - at least until recently - guaranteed that it would not work.

There are 2 key impacts (at least) for device integrity - ie wallet and RCS - and the fact that you're not interested in RCS doesn't mean that others aren't.

If it is now working for devices without device integrity, then that may be a clue to the wider issue of spoofing.
[Magisk] simplepinoi177:
My apologies if this is not new news, but I currently don't have the capability (working devices) or time to read up on every page since last Friday, but I just wanted to input this as an update on the goings-on with PIF, Play Integrity passing, RCS, and such...
[Magisk] Clarnc:
Hi,

Is it impossible rn to get passed device integrity without custom pif?

Can't use my wallet for mouth and it getting me bored

OnePlus 8
[Magisk] majorfigjam:
Unless you unroot and lock your device, you need a spoofed fingerprint to get device integrity, which should enable you to use Wallet.

Read this and follow the links in it to find out how.

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] zgfg:
Please read FAQ post (look for the most liked posts and read them and other docs they links) to see why with your prints from your phone - with unlocked Bootloader, Droid Guard forces Strong Attestation, but Strong attestation fails and Droid Guard then doesn't care to test Device Integrity (saying that it didn't pass either), and you pass at best Basic Integrity that's not enough (for Wallet, etc) - Device Integrity is required

Therefore you need custom pif to trick DroidGuard to attest spoofed Device Integrity instead and to pass

Asked, answered, described and discussed many times

---

Unless you have an older phone (A7), then a different procedure applies - that has also been discussed recently, look on GitHub, PI Fork module, for the CI build
[Magisk] ardiesel:
Of course, the day after RCS goes back to working on rooted, Google issues another update to the messages app, I'm not updating it. This is all getting too frustrating, it's like they are purposely making us fail.
[Magisk] bombadier:
Not sure that an app update would affect this, I took the update and RCS is still working

Version

messages.android_20240321_01_RC02.phone.openbeta_dynamic

com.google.android.apps.messaging
[Magisk] ardiesel:
Are you on a rooted device? I've updated the app several times to have the RCS suddenly not working again. Until I found this module i was dead in the water every time.
[Magisk] bombadier:
Yeah rooted pixel 7a, I am using PIFork v8 and the griffin print, at the moment both wallet and RCS is working, think it is a coincidence that it stopped working when you updated the app, the drama over the last few days was down to something google was doing as most people who had RCS stop working were/are using the known griffin print
[Magisk] ardiesel:
I don't even know what that means. What PIFork is or using a print. I don't know how to add that to my device.
[Magisk] Vision:
Please read this

🔧 [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] bombadier:
Then you have come to right place to find out, absolutely everything you need is right here by reading,take some time, enjoy the experience
[Magisk] V0latyle:
I wasn't aware of that. My mistake.
[Magisk] aliantonio:
As others have stated, my RCS is back working with PIF installed and enabled. Took the update for both PIF and messages and RCS is still working, so it seems to have been something on Google's side. Glad it's working again, but this is getting all too frustrating. I've been rooted for over 10 years and I'm finally getting close to my wit's end with it. Breaking messages and Google Pay is unacceptable for me. If I have to unroot, there's nothing keeping me from switching to a non-Pixel or even an iPhone at this point. The gap is getting that much smaller.
[Magisk] HippoMan:
These are not Pixel-only issues, so unfortunately, switching to another type of Android phone will almost certainly not help.
[Magisk] D€INOS:
I deleted the messages after a while so I dont know
[Magisk] i5lee8bit:
I say this as a proud Korean... Forget Samsung.

Oh, and PIF! RCS! STRONG! VIRTUAL! ATTESTATION! GOOLAG! EXCELLENT GUIDE! MODULES! VAPES! There, back on topic.
[Magisk] markfm:
View attachment 6087094

Your friend is probably using Samsung's Messages app (bottom one in the screenshot), as opposed to Google's (top one in the screenshot). It's analogous to Samsung's Phone app having the same name as Google's Phone app.
[Magisk] markfm:
While it won't truly remove the app, for a non-rooted phone you can still enable developer options and USB debugging, then use a command like:

adb shell pm uninstall -k --user 0 com.samsung.android.messaging

to make it disappear (no longer seen in the apps tray)

Less intrusive, simply disabling it, can be done from Settings - Apps, or by:

adb shell pm disable-user --user 0 com.samsung.android.messaging

(I always do an initial force close/clear data on an app that I want to do the above to.)
[Magisk] AiM2LeaRn:
my guess is, let the masses take on the update(s) first and then do the "rug pull" and enforce the more stricter restrictions later, why would g00000gle "show their hands" if they just barely rolled out the new update and fewer than average number of people have received it. this is of course just my 2 cents, not that its proven or anything.

HOWEVER, in my opinion this thread and people with RCS issues should start posting their messages and google play services VERSION numbers along with version of android. the data and feedback.input is just very fragmented.
[Magisk] osm0sis:
See FAQ #8

https://xdaforums.com/t/pif-faq.4653307/
[Magisk] fbirraque:
If people start to read before post this thread size could be 10% the current one
[Magisk] zgfg:
It's not only about RCS posts like the last days

And it could be even 10x smaller, taking into account how many repeated questions we had like:

My SN fails (what should I do)

My PI fails

My device is Not certified

My NFC payments fail

I installed the 'module' but still failimg

Where can I find custom prints

Can I use my own prints from the phone

etc
[Magisk] sawdoctor:
Sorry for the ot but you disable an awful lot of bloatware without root using Knox. I disabled so much with adhell3 on my fold 3 when I had it
[Magisk] ashish1989:
I am on the same boat, done everything like you on my android 7.1.2, still fails basic and device integrity both
[Magisk] forserg:
Thats exactly what I was doing whole week, uninstaled old Magisk 26.1 , patched AP with selected recovery mode in Magisk 26.4 and flashed all binaries. What am I missing? I did everything the same when I installed magisk 26.1 and rooted the phone at first. Could it be the

reason for this trouble that wrong CSC firmware was flashed before?
[Magisk] pndwal:
How are you booting to Android? PW
[Magisk] ArclightX:
Same.

This morning RCS just magically started working. I hadn't even updated PIF to v15.9.7 or anything. It just started working out of the blue.

Phone: P7P - March 2024 Update

Magisk 27002 (D)

PIF v15.9.7

PlayCurl v10.2

Shamiko v1.0.1

Denylist (Basically everything "Google" on it) etc.. etc.. etc..
[Magisk] osm0sis:
Probably best not to hit reply yet when you're still 4 pages behind on catching up... 🫤
[Magisk] majorfigjam:
Just updated the very latest Google April update AP1A.240405.002 on Pixel 6 Pro, up to date Play Store and Play Services, and still have device integrity with both Griffin print and a "private" print.

RCS and Wallet seem to be unaffected by the update, which is probably as expected given gms is separately updateable.

Edit: oddly though, I just noticed I no longer have Device is Certified showing in Play Store. Maybe it will show up eventually.
[Magisk] intel_core_i7:
My Galaxy S5 running stock 6.0.1, never modified also doesn't show device is certified in play store. Basic and device passes
[Magisk] forserg:
My reply was deleted "due to being completely off topic", but thank you a lot for trying to help..
[Magisk] neonblind:
...and suddenly device integrity is back on both old android 8.0/8.1 devices.

🔧 [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

please test @miXOnIN @ashish1989
[Magisk] marisaleh:
I need your help guys,

I am on my old Nexus 6 ,

I installed the crDroid Rom on it and rooted it using the latest version of Magisk but it keeps failing the device integrity with using the latest release

of the play integrity fix

I have just discovered that this Rom

is in the banned list

Please someone help me to get it

to pass , is there a particular fork

of the module that will fix it ??
[Magisk] osm0sis:
So all of their shenanigans with the griffin print have ended, for now anyway. I was wondering if that would be the case.
[Magisk] s1dest3pnate:
Well, new symptoms going on with RCS possibly... Messages app crashing, intermittent sending/receiving of texts, texts disappearing, showing as unread on both sides even though it was read.

One person that I text with RCS was unable to open our conversation (after all of these recent issues with RCS and me changing FPs and such). Messages would just crash. After deleting the conversation and starting a new one, they were able to open it and text me. Then I texted them back and they got it but even though they saw it, it showed unread on my side and theirs. We sent a few messages back and forth, and some of the messages I sent just disappeared on their side (notice all of the empty space in the attached screenshots) and some were just never received either on their side or my side.

Their phone is a Pixel 8 stock unrooted, and mine is a Sony Xperia 5 IV rooted/unlocked.
[Magisk] ashish1989:
Magisk delta? Where did you find the old file. Its kitsune mask now and on my android 7.1.2 the zygisk is not working, I don't know why
[Magisk] osm0sis:
You still using Xposed is why you will never pass SN/PI. We were over this a few times.
[Magisk] neonblind:
I was talking about your A9 samsung J7 prime. it should pass device intergrity now. would be interesting to know.
[Magisk] pndwal:
Yeah... This has veered OT since your original post though. But @mrjuniork has kindly reproduced my last response so I can simply move this somewhere more appropriate as I should have done earlier...

To be clear, this is really about installing/updating Magisk using Recovery mode for some "Ramdisk = No" devices (A-only and L-SAR, launched with Android 9) and not PIF related... Moving conversation here:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-89437383

🙂 PW
[Magisk] DooSHeK:
Same here. For a few days Device Integrity fail and now, just like that Device Integrity Pass
[Magisk] fbirraque:
Maybe some side effect but after update to the latest Google Play Services (Beta) the apps and whole system performance seems smoother then before.

I'm just saying... (link)

Google Play Services Public Beta Program | Google Play services | Google for Developers

developers.google.com
[Magisk] pndwal:
He said Zygisk isn't working... What am I missing? 🤔 PW
[Magisk] pndwal:
Did you mean "for a month"?

Does Momo report broken TEE for your OnePlus device?... With no modules installed, does YASNAC say you're passing basicIntegrity and evaluationType = BASIC?...

If so, PIF probably isn't needed... Let us know. 👍 PW
[Magisk] wfred:
It's likely the kernel that rom uses. Check this list.

If it is the kernel you'll need to change the name. Search this thread for instructions on how to do that

🔧 [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] ashish1989:
You are right, in my A9 Samsung J7 Prime, I am passing device and basic integrity both
[Magisk] ashish1989:
Yes, I have tried fresh install of my A7 device with kitsune mask stable latest. Zygisk is not working in it.
[Magisk] bdr127:
I just updated my Pixel 6 to the April 2024 update (AP1A.240405.002) and my Play Store says "Device is Certified." 🤷‍♂️
[Magisk] Nergal di Cuthah:
I believe @majorfigjam solved their issue with deleting playstore data
[Magisk] pndwal:
Galaxy J2 2016? Kernel pre- 3.19?

Some pre 3.19 Samsung kernels with exec limitation broke Zygisk and there was no fix with LD_PRELOAD loading... With the move to native bridge loading (major Zygisk refactoring) in official Magisk from 26403, the old Samsung kernel issue should be gone (fixed) however (according to@canyie). 🙂

... Kitsune Magisk moved from LD_PRELOAD to ptrace + fuse (ZygiskNext method). I've no idea if that helped Sammy kernel exec limitation issue at all, bit stable Kitsune is 26400 based I think?... Still, you may need native bridge (ie official) for Zygisk fix ATM.

PIF is a Zygisk module but you don't need the Zygisk parts for your pre- A8 LV device for PI DEVICE_INTEGRITY anyway of course... PIF Fork's scripts-only-mode should work for your device however... as the simplest of several options... 👀 PW
[Magisk] ashish1989:
You are right, official magisk latest stable is working fine in it and I am also using PIF Fork by @osm0sis in it, but all have gone in vain as I am using old Xposed in it. I think kitsune mask dev should update his stuff too for older devices below A8.
[Magisk] zgfg:
Now, when Zygisk works for you, ehy don't you uninstall the old XPosed and install LSPosed - Device Integrity shall work (Ii have LSPosed with several modules since ever)
[Magisk] ashish1989:
But Lsposed don't work under A8, if I am not wrong, if that work, it would be my first choice then as I am on A7
[Magisk] Vision:
ZygiskNext not working ? I think work 26402 and after
[Magisk] ashish1989:
ZygiskNext can be used with magisk, I thought its only for kernelSU
[Magisk] marisaleh:
Thank you for your help

yes it is listed as banned

uname -r has returned the following:

3.10.108-lineageos-gc241c1575b6

so it is lineageos, and this is unfortunately

in the banned list

but I can't see any clear

instructions in the thread

on how-to change the name
[Magisk] Vision:
I think work according to this

View attachment 6087772
[Magisk] ashish1989:
But zygisk is working in official magisk, I was talking about kitsune mask, in which zygisk was not working in my A7 custom rom.
[Magisk] Vision:
Yeah, i know, in a older version of Kitsune Mask, zygisknext work, maybe work in a new

Official Magisk with zygisk not work? except the Kitsune Mask zygisk
[Magisk] wfred:
Start here and go a few pages on both sides. I don't have that issue so I can't give you any instruction.

🔧 [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] xcl1pse:
with A7, ptrace init based zygisk such as ZygiskNext and Kitsune Magisk will never work for you. It was working on official magisk since it injecting system native bridge which is already on android since ~2014
[Magisk] Vision:
Like the old Riru.

And in old version Kitsune Mask before renamed had a version with zygisk native bridge.
[Magisk] GabbyWC:
There's a recent Telegram poll here which asks if users would like LSPosed maintenance to resume. If that happens, I think it's likely that Shamiko will also have updates in the future.
[Magisk] pndwal:
Yeah, ZygiskNext needs (theoretically): Android 8.0+ (API 26+)... TJW Magisk had NB from 26403 as I mentioned above... On this member's device the issue is apparently the Sammy old-kernel restriction ("whenever exec an ELF from /proc, the process can no longer call some systemcalls. For kernel 3.19+, the workaround is fexecve, but it does not exist for the old kernel")... Native bridge solves this, but I don't know if ptrace Zygisk does, so may not run even with custom A8+ ROM unless kernel is also updated...

Yeah, but it was never updated to new... Based on old Maru Magisk native bridge POC from 5ec1cff until moved to ptrace+fuse from 5ec1cff and Dr-TSNG ZygiskNext project...

Kitsune may now a bit stuck again it seems as starting from version v4-0.9.2 ZygiskNext is no longer licensed under the GPL-3.0 License... all rights to the software are now "reserved by the owner" with conditions including:

👀 PW
[Magisk] marisaleh:
Thank you, I had a look but this is really

involved requiring the editing of the kernel by obtaining the kernel from

the Rom, don't know where to get

that from, and also involves using a

hex editor to do that.

To be honest I was hoping that there

will be a fork of the play fix module to

do that