yashsingh1/xdaforums huggingface dataset:
[Magisk] majorfigjam:
Ok so your ctsProfileMatch fails verification.

Safety net is deprecated, so that is not too helpful.

Read Post 1 on Page 1, then the linked faq, then the linked Osm0sis resources.

If you can't work out what is wrong, come back with more information about your device: model, rom, modules installed, other apks such as lsposed.
[Magisk] SoulsAssassins:
Hey ! I can't acces where I found build prop the website seems off since yesterday anyone has the same problem?
[Magisk] dr.ketan:
Something really weird happening since y'day. I posted video of Gpay+RCS working was surprised indeed. No idea if it is regional but on my device A14 fingerprint getting passed lol!

PS : Similar FP tested by my tester and it fails that's why suspecting regional
[Magisk] majorfigjam:
Well some A15 prints seem to work quite well, and not regional so far as I have read. Google seems to be beta testing something.
[Magisk] taka2902:
Is rcs really PI based? I just bought my mom an old note 9s phone, unlock bootloader and got kernelsu root to debloat stuffs, and by my surprise the rcs was enabled successfully without having to bypass PI
[Magisk] denzel09:
Which folder is this about Dedyn?
[Magisk] HippoMan:
That seems like a reasonable possibility.

Also, I'm sure that some Googlefrinchians are reading this public thread in order to learn how modders are bypassing Googlefrinchian security, so they can make their security stronger in the future. If so, these beta prints might be a way for them to entice us modders to use them and therefore provide the Googlefrinchians with more data about how we perform our modding efforts.

In any case, these XDA threads are a publicly readable treasure trove of information about the ways that we modders are bypassing integrity checks and other security.
[Magisk] D€INOS:
Yeah I noticied yesterday that it's down. Hopefully temporary.
[Magisk] 306bobby:
It's fingerprint based. If your phones default fingerprint is valid and you pass basic it should work
[Magisk] zandatsu06:
Is the sailfish fp is the main reason why i can't use RCS? if i hunt one working fp the RCS will work again, right? can someone confirm this.....
[Magisk] bombadier:
Yes
[Magisk] SoulsAssassins:
You can search selfish in the search bar or read few pages back to see it
[Magisk] Vision:
Always say what you know and know how to do.
[Magisk] Aarif goku:
Oh cool I'll take a look about the related query. It'd be intresting if strong can be achieved without those illegal keyboxes without hacking tee but by just injecting and modifying responses. But that's just a sweet dream. Currently I'm optimistic with lack of knowledge let's see what heartbreak I'll have to read through that might change my thought.
[Magisk] TurboLed:
Hmmm. On my Pixel 6 Pro, it seems if I just turn off the PIF module and reboot, RCS stops working.

EDIT: May it depend on what root method is used (magisk vs APatch/KernelSU)? I'm on Kitsune because it fixed my work profile with Intune, haven't tried newer methods yet.
[Magisk] cabagekiller:
same tadiphone seems down
[Magisk] SoulsAssassins:
Hmm...seems not only me hope it will be back soon 😓
[Magisk] alekyiv:
I am don't understand for wat this Google RCS when there are so many different messengers such as Viber, WhatsApp, etc.? Like not to install them and have everything out of the box to improve communication with iPhone users?
[Magisk] purpleman2k:
It's only a matter of time (and not a very long time if you ask me) before more and more apps require STRONG in order to work. We have seen many apps try to detect root in creative ways, some more successful than others -- but the will is there. .If Google's providing this API and legitimizes the use of it (not to mention that older non-pif-compatible devices that can't pass strong are aging out) -- unless some alternative bypasses are found -- root is going to be very short lived.

By the way - as I'm not familiar with the mechanics of the RCS mechanism -- would a modded version of the Messages app be able to bypass the PIF check? I know that RCS is run by the carriers, wasn't sure if there's an actual dependency on Google's servers approving service only if server-side checks are passed.
[Magisk] TurboLed:
Most of us don't care at all about SMS/MMS/RCS and would love that all our friends and unknown contacts send us texts by Messenger/Google Chats/WhatsApp. But in reality people are stuck with their habits, especially iPhone users.

Asking an iPhone friend to not text you by SMS, almost mission impossible, because they're used to just type a phone number in iMessage and text.

Now with RCS, if your friend has an Android phone but knows nothing about apps or computing in general, he will continue to text you in the SMS texting app. But guess what, he will have RCS enabled automatically and you will suddenly receive his messages even if you are abroad using WiFi without doing anything.
[Magisk] numan732:
I have a private print and my rom is testkey build. Pi is basic but Rcs is working fine.
[Magisk] mike.s:
Going a bit in the weeds, and not a generalized solution, but...

It seems that RCS and Wallet cache their results, so once "OK", they continue to work for a while. Might there be the possibility of updating cache behind their back (e.g. constantly moving a time-to-live into the future)? It would require figuring out the data structure they use, and may not even be possible if they somehow encrypt or hash things. But I'm not a dev - just a thought.
[Magisk] zgfg:
Dedyn was an on-line source with build.props and the already created custom.pif.json files (but they have to be migrated with the new script)

You should test, I'm not going to disclose the prints (or the Manufacturer/folder names) for the sake of protecting the private prints for whoever mined himself and uses them
[Magisk] zgfg:
Read the FAQ post and you shall know that Strong Integrity cannot be obtained by the private prints (only Device and RCS)
[Magisk] denzel09:
I mean, which is the site? Can you post the link of the site?
[Magisk] zgfg:
Dedyn? - is DEAD
[Magisk] cambunch:
Mine broke on its own accord, but the fact that it was working for a little bit was the most success I've had since the huge blacklist in May.
[Magisk] cabagekiller:
Yeah. Rip to the may massacre. I had one for a few months until then. My newest one died a few days ago and tadiphone is down so I can’t hunt for a new one either.
[Magisk] Lord Sithek:
Hi all, I updated my Tasker project for testing fingerprints to make some adjustments and to include recent changes. If anyone still intereted in using
[Magisk] borisSweden:
There are some projects trying to create the open source client for RCS. But the question is how to use RCS when Google controls all the servers and how to activate it. To activate it you need Google Apps like Google Play Store and Google Play Services. If the registration could be circumvented trying to pass integrity wouldn't be needed.

For a non-play integrity dependent RCS, we need an alternative server for the whole protocol.
[Magisk] cambunch:
While I didn't use your Tasker project specifically, your post did help me figure out what I was missing in getting my custom PIF to work. I currently have RCS working (who knows for how long though). Thank you!
[Magisk] majorfigjam:
Latest Pixel stock A14 July update for today (ap2a.240705.004) does not so far appear to affect viability of "private" prints.
[Magisk] flyoffacliff:
The same reason people still use SMS (and email for that matter). It just works, and literally with any cell phone. No central servers to go down or be compromised, and no need to convince everyone you communicate with to download a special app for you. Because most people don't have them and it's hard to break the cycle when there are so many.
[Magisk] pershoot:
To add to the recent VPN testing, if you use Google Fi, it's VPN seems to work (turns on / sets up and shown in VPN; it's shown in status bar when connected; didn't leave it connected for much after that).
[Magisk] geokilla:
I'd like to thank @majorfigjam for the step by step instructions on how to get pif.json created and @cabagekiller for offering his assistance.
[Magisk] pndwal:
Well, both DEVICE and STRONG are really TEE related, but DEVICE doesn't require TEE...

PI (and S/N) uses both opportunistic (for DEVICE) and always enforced (ie. STRONG) hardware backed key attestation (HKA).

Ordinarily HKA is needed for both DEVICE and STRONG in post-A7 launched (Keymaster HAL 3+) devices but not for DEVICE in older devices. (Of course STRONG is simply not available for devices launched with A7 or earlier.)

Both S/N ctsProfileMatch w/ BASIC-only evaluationType and PI DEVICE_INTEGRITY ordinarily require either a pre-A8 device or some keystore related error causing a fallback to basic attestation to pass (which works as these labels only opportunistically require HKA). PIF module (except if using a 'scripts-only-mode') always triggers this (injects code using Zygisk into GMS to register a fake keystore to force an exception or similarly simulate a non-HKA compliant device, and trigger fallback to basic attestation).

Further, both ctsProfileMatch with HARDWARE_BACKED evaluationType and STRONG_INTEGRITY ordinarily can't be had without HKA (ie. there's no provision for passing these with a BASIC-only evaluationType. Read 'HKA is always enforced').

🤠 PW
[Magisk] Aregtheeditor:
Welp, I may give up on rooting on my next phone. I may buy a pixel as my next phone idk if it is worth to root it anymore
[Magisk] Claus….:
No, you will just be more creative now.
[Magisk] Claus….:
Please don't delete anything. If you ask a corporation then everything is ilegal they don't like and what they don't like is losing power. As you write, I don't see anything illegal.
[Magisk] cabagekiller:
Is tadiphone down for good now? It's been a few days.
[Magisk] zgfg:
Which address are you opening
[Magisk] cabagekiller:
I am using https://dumps.tadiphone.dev/dumps. is that the wrong one?
[Magisk] generalculprit:
He seems to be using https://gitlab.com/Android-Dumps
[Magisk] cabagekiller:
Interesting. That one seems to be a bit outdated. But I'll try to find a fp.
[Magisk] Nergal di Cuthah:
Not on topic but I'm sure they have a way, which may require new hardware to fix.

That said, can we return to the actual topic, which isn't broken pixel 6 series, there's a topic for that in the p6 boards.
[Magisk] Iridule:
I am using the print found in PIF module and everything works fine. RCS only broken on pixel 8?
[Magisk] pershoot:
It is not only limited to shiba. For most, that particular print has been banned from RCS use. Why it still works for that purpose for a select few, is anyone's guess (phone type (older?), particular network governance, etc., etc.).
[Magisk] Iridule:
There is a module I use called PIxelify for photo backup, Makes the phone appear as pixel 1. Wonder if that has anything to do with it?
[Magisk] 93ae8074:
It stopped working for me this very morning in KernelSU. :-(
[Magisk] Cavaler:
I have lived without Magisk or anything like that for a year now, and had no problems even though ROM is quite old (09.2021) - until 3 days ago Wallet suddenly stopped working!

So I decided, what the hell, added Magisk 26.4, PIF 12.3, tried various combinations of DenyList.... DEVICE_INTEGRITY and BASIC_INTEGRITY now pass, but Wallet still says "doesn't meet security requirements". What could I be missing?
[Magisk] Klappp:
Try clearing the data for wallet and google play services. reboot and see if that works.
[Magisk] chiteroman:
Fix and improvements! by chiteroman · Pull Request #44 · Displax/safetynet-fix

Hello @Displax I updated your module for users who still want to use it. I tested it in my vayu and it's working.

github.com

If you want to try it:

Release release · chiteroman/safetynet-fix

Fix new Play Integrity update, DEVICE verdict is green again. Strip native libs size. Unmap module from unstable GMS process. Spoof first_api_level to 32 if prop value is greater than 32 or prop do...

github.com

🤗
[Magisk] Fishawy:
Yea that one fails SafetyNet on my P7P. Thanks for attempting to fix it.

Back to PIF 12.3 for now.
[Magisk] railsonhak:
It's falls here. And keeping crashing wallet app! Thanks for your effort
[Magisk] TraderJack:
@marcopit-92

Just a warning/update. The module I mentioned seems deprecated (I can't find a zip of it anymore).

I was able to bypass it with a custom script, but this only worked in Momo 4.3.1, it still fails on 4.4.1.

If you look near the bottom of my post here you will see some more info.
[Magisk] osm0sis:
But.. why? Just makes things more confusing. 😲
[Magisk] lssong99:
Just updated to 12.3 from 9.x and all test fails (Device and BASIC).. everything worked normally under v9.x....

Not sure what changed then but beware when upgrading.

Pixel 8 pro stock magisk rooted with ZygestNext.

Edit: after some reboot it seems pass on both test....
[Magisk] pndwal:
Thanks!... (Even if needs more work)... 😛

Much easier to see code changes here at least, for an amateur sleuth like me!... But please say how this still differs from your PIF solution... (Aside from PIF working!)

Guess safetynet-fix-v3.0.0-MOD.zip is really safetynet-fix-v2.4.0-MOD_3.0.0.zip, ie @kdrag0n 2.4.0 base, @Displax/@chiteroman 3.0.0 mod(ification)...

Also, just realised what I said earlier is wrong 😬 so I struck it out:

I believe you did say we may need to clear data for Google Services Framework however... Please can you say how this can help/what cached results it stores?... I'm not aware of this being required before...

Re:

I was going to ask about it for clarity, but it seems to be gone from OP with today's edit... So seems PIF still works as USNF did and it was a misunderstanding?

Thanks, 👍 PW
[Magisk] pndwal:
But PI DEVICE_INTEGRITY was failing on 9.x, no?...

I believe that what changed is that everything wasn't working normally; this was already failing (since last Wednesday) which may explain why you needed the extra reboots...

... I still don't think there were any exceptions to failing results on old builds variously spoofing Marlin, angler and walleye fingerprint props etc since Google's Nov 8 changes(?)... 🙃 PW
[Magisk] marcopit-92:
I just did not install it cause I couldn't found compatibility with stock ROM. Seems in the description says it is just for custom so I did not take the chance. I tried devoptshide module but did not worked, but I am ok I don't need those, as now all my apps run perfectly with PIF and SHAMIKO
[Magisk] chiteroman:
Maybe someone want to still using old module without hooks.
[Magisk] nil?:
Hi guys, trying to use this module in order to recover my ability to pay with the raven, it's gone about a week ago.

I see an error saying "Zygisk module not loaded due to incompatibility", it's PIF 12.3 with Magisk 26.4 and LSPosed 1.9.2 (7024).

What incompatibility does the error indicate?
[Magisk] osm0sis:
Ah okay wasn't clear what the difference was. Thanks!
[Magisk] VuYeK:
Hi, I need someone who can explain exactly how it works and where the problem is. I have Xiaomi 12X with latest DEV XiaomiEU ROM (not latest stable version with fix mentioned in earlier posts). I don't want to switch to stable version because data wipe is required and that would be hell for me. I have PIF 12.3 and when I check integrity in the Play Store, the first time I get nothing, and the second time I get BASIC and DEVICE integrity. It's always the same with Play Integrity checking apps. Google Wallet does not work fully - it shows that the phone does not meet the security requirements and, in fact, contactless payments do not work, while Google Pay in different apps sometimes works sometimes not. I need clear information about what else I'm doing wrong, and whether I really need this stable version of the ROM with the mentioned fix, or whether the problem is somewhere else (because on the second click I always pass BASIC and DEVICE integrity)
[Magisk] oo8tcu:
so on my Pixel 4a BASIC and DEVICE integrity pass, but adding a card to wallet requires confirmation by my bank (ING) through my bank's app. I think this worked before, but now the banking app stalls forever when trying to confirm this to Google Wallet. I don't really see anything of relevance in the logcat:

11-13 13:27:02.006 1638 5178 I ActivityTaskManager: START u0 {act=de.ingdiba.bankingapp.a2a cat=[android.intent.category.DEFAULT] pkg=de.ingdiba.bankingapp cmp=de.ingdiba.bankingapp/com.ing.mobile.diba.googlepay.AppToAppActivity (has extras)} from uid 10235
11-13 13:27:02.020 1638 5176 W ActivityTaskManager: Tried to set launchTime (0) < mLastActivityLaunchTime (717231)
11-13 13:27:02.140 8486 8592 W Parcel : Expecting binder but got null!
11-13 13:27:02.144 1638 5176 D CoreBackPreview: Window{5728a0f u0 de.ingdiba.bankingapp/com.ing.mobile.diba.googlepay.AppToAppActivity}: Setting back callback OnBackInvokedCallbackInfo{mCallback=android.window.IOnBackInvokedCallback$Stub$Proxy@261bca5, mPriority=0}
11-13 13:27:02.156 8486 8486 W OnBackInvokedCallback: OnBackInvokedCallback is not enabled for the application.
11-13 13:27:02.156 8486 8486 W OnBackInvokedCallback: Set 'android:enableOnBackInvokedCallback="true"' in the application manifest.
11-13 13:27:02.158 1638 1825 I ActivityTaskManager: Displayed de.ingdiba.bankingapp/com.ing.mobile.diba.googlepay.AppToAppActivity: +152ms
11-13 13:27:02.175 8486 8592 W Parcel : Expecting binder but got null!
11-13 13:27:02.178 1638 5176 D CoreBackPreview: Window{fe89134 u0 de.ingdiba.bankingapp/com.ing.mobile.diba.googlepay.AppToAppActivity}: Setting back callback OnBackInvokedCallbackInfo{mCallback=android.window.IOnBackInvokedCallback$Stub$Proxy@95d041e, mPriority=0}
11-13 13:27:04.719 3152 3152 D BoundBrokerSvc: onUnbind: Intent { act=com.google.android.gms.udc.service.START dat=chimera-action:/... cmp=com.google.android.gms/.chimera.PersistentApiService }

Banking app broken or PIF breaking the banking app?
[Magisk] Klappp:
Anybody else got it working but still getting their payments declined?
[Magisk] pndwal:
Please can you clarify?... Didn't USNF use hooks?... I think @kdrag0n added hooks to set and restore the fingerprint (mismatch) etc dynamically at runtime only to avoid adverse effects (2.4.0)... @Displax eventually fixed timing/sync issues and moved his mod builds to 2.4.0 base...

Do you mean your different hooks?... Or am I missing something?... Ta, PW
[Magisk] pndwal:
The issue is even Devs here don't know exactly how inbuilt spoofing in XiaomiEU ROMs works... Some ROMs seem compatible and others break PIF...

Seems you are doing nothing wrong except choosing a ROM with outdated spoofing/fix for device integrity attestation that also breaks PIF... Clean ROMs (that don't spoof) incl. Custom don't do this, and many with spoofing don't either...

Nb. While you have passing verdicts, G Pay/Wallet checks cached failures on starting app obtained and cached even when not running (including failed DEVICE_INTEGRITY, disabled password/pattern/biometric scanning even if re-enabled before G Pay/Wallet use, and maybe more security red flags) so late starting or intermittent failures often trip G Pay/Wallet but not banks looking for MEETS_DEVICE_INTEGRITY...

FWIW, Devs like @Displax and @chiteroman have called XiaomiEU's DEVICE_INTEGRITY fix implementation 'very strange'... You may need ROM Dev's update or to switch ROMs... 🙃 PW
[Magisk] pershoot:
Perhaps there is an edge case there for your particular environment. You may want keep an eye out for it to potentially catch up to you as it has for most everyone else. It will be a silent failure. You should enable resend as SMS in options so your sends can revert and also be at the ready to inform your recipients.
[Magisk] Iridule:
TBH i don't use RCS for messages I use google voice. I Just noticed it is still connected and working however.
[Magisk] pershoot:
Being connected is not the same as working properly. You will see it connected, but sends and receives via RCS will not work. Try to chat with Gemini using RCS (take note of the '...' connected bit with that entity and the actual printed dialog in the send box) and observe.
[Magisk] Iridule:
seems You are correct. such a shame RCS broken :(
[Magisk] lpedia:
Although other messages can switch to SMS and send OK, if you've turned on "Automatically resend as text" in the RCS settings, be aware that RCS groups are still completely broken, because they can't receive SMS messages. The Details on the group will show it's no longer encrypted; the field for entering text will say "Text message" rather than "RCS message", and you'll neither receive messages from nor be able to send them to the group. Any you try to send to the group will simply disappear - not even retaining your copy.
[Magisk] intel_core_i7:
Some off-topic stuff, mods please move or delete if necessary.

Another custom ROM bites the dust?

View attachment 6120089

EvoX by @joeyhuab will cease development (?)

I don't use discord so no idea about if this is true or not, and all telegram channels has been closed for a while.

Android modding in general and custom ROM specifically just gets less and less support these days, the corpo have won.
[Magisk] mrgbuzz:
Yes. from Discord, its been discussed at length. Joey and Anierin have spoken quite a bit about it.
[Magisk] joeyhuab:
Sorry for the OT response as it has been brought up.

The reality of everything is, me and Anierin are both currently unemployed and we are uncertain if we will be able to continue the project beyond August due to lack of funding. It's really hard to sustain and manage servers, the Discord and maintain several device all at once and almost receive nothing in return for our efforts.

We don't even have a working website due to being outdated and not having a proper web developer and web designer. We haven't had a rebrand in years due to not having a ROM designer as well.

It's just sad as we always do our best to catch up with whatever BS Google tries to throw at everyone (play integrity and RCS fixes included) and only a select few in the community appreciate the lengths we go.

Another annoyance is that Google broke Circle to Search (which we were spoofing) after A14 QPR3's changes. Truly utter disappointment on the part of the team and our users.

If our financial situation improves, then we'll be able to continue.

We've been here for 5+ years

. It's just the overall lack of community support recently that has derailed us from maintaining the ROM as we also need to focus on our personal lives.
[Magisk] intel_core_i7:
.

Question has been answered
[Magisk] intel_core_i7:
It's a never ending process: the ones who make and use the ROM are often unemployed and not free financially, when they do they just... don't have anymore time into all of these. It's pretty much how every tech (and hobby in general) based communities end in the last 20 years I suppose.
[Magisk] chiteroman:
Updated Key Attestation Demo app

Play Integrity Fix

Key Attestation Demo app updated! Now it includes Secret Mode! Certificate serial numbers and dates will be hidden when it's enabled. Also I disabled (by default) attest device ids, strongbox... Commit: https://github.com/chiteroman/KeyAttestation/commit/34bf394db19bd70b3e507a186a4e6ed15d53b927

t.me

View attachment 6120349

With secret mode we can flex that we have a valid and unbanned keybox 🙃

Commit: https://github.com/chiteroman/KeyAttestation/commit/34bf394db19bd70b3e507a186a4e6ed15d53b927
[Magisk] badabing2003:
Why is the revocation list embedded in the app rather than it being fetched at runtime? (in case there's more on the list) or is this only used when offline?
[Magisk] jakell888888888:
Does this mean that we don’t need a valid keybox to perform strong authentication?@osm0sis
[Magisk] badabing2003:
No, this is just a test app.
[Magisk] xcl1pse:
At this point people sharing attestation test just to flex 😂