yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Just to be clear, fallback to SMS seems reliable (no messages are missed but rich content cannot be sent) when one or other device has RCS disabled in settings, so if modders are concerned messages may be missed, disabling RCS so that messaging always behaves like an old/incompatible device may be their best option.

Fallback to SMS also appears to be reliable when a device is detected as not meeting hardware and software compatiblity requirements by Google.

However, as I've mentioned before, the case of RCS breaking because a prop/field set is detected as spoofed via DroidGuard is a different matter... We know that the 'print' is not simply causing the device to be deemed below spec because real Sailfish (first Pixel) devices can use RCS. So Google is clearly employing a method using prints + other measurements to detect spoofing or tampered device in a similar way to how they 'ban' prints for PI DEVICE_INTEGRITY purposes...

Just like bank apps or G Pay/Wallet (contactless component) silently failing when DEVICE_INTEGRITY is not met, RCS may simply be failing as detected tampering simply means that some individual component required for RCS has been disabled in the background. Since this scenario falls outside expected use, Google may simply not have built in the necessary handshakes for triggering real-time fallback to SMS, although the messaging app seems to 'catch up' with failed attempts or cached detection results and trigger the fallback some hours later in many cases.

I'm not sure if this actually qualifies as a bug, but Google could implement proper handshaking for realtime fallback to SMS in tampering cases, or proper popup warnings(?), in future I guess... Or not...

Anyway, there are clearly many options for informed modders.

Think it's still the fingerprint issue... seems handshaking for E2EE is properly accommodated but may change... The coming IOS integration for cross platform messaging slated for September iOS18 release reportedly will work without Google's E2EE. (They've only agreed to adopt GSMS standards)... Of course if E2EE is adopted as GSMA RCS standard before then, Apple may reconsider.

👀 PW
[Magisk] badabing2003:
No I didn't, because if you read my response, I was not referring to any specific user, instead I was telling how I would do it if I were in a similar position (ie when something is over my head).

Again that is not the point, yes there are way too many entitled users that expect to be spoonfed, people only react when it boils over, and it doesn't necessarily happen to the worst offenders, but insulting the ones that are actually trying to help you doesn't help.

Overreacted? or felt insulted? and rightfully so, imagine you're @osm0sis, a well respected member of this communutity who's done so much for so many years, and here comes someone self proclaimed technically challenged and gives you advice about how you should write up your FAQs or help out others, how'd you feel?

No he was not just saying that, he said:

I'd be insulted if I was @osm0sis

The FAQ is a 14 point FAQ, and points 5,7,8,9,10,11,12,13,14 touch upon Droidguard one way or another.

And the Readme which @osm0sis referred to, literraly says this:

Google Play Services DroidGuard process (com.google.android.gms.unstable)

Now go on and tell me that that's not good enough, but this is?
[Magisk] TotallyAnxious:
@markdewet @trevtdogg

@osm0sis is very tolerant to BS. I pretty much only reply to him with sh*tposts and he doesn't mind.

The respect he has here is very deserved. Many of things you use are either entirely or partially due to him. His guides are as detailed as they need to be. Often more so. If you find them challenging then change your approach to learning them. I have no dev background and I've made kernels, magisk modules, ramdisk mods, had a commit to the official git for cyanogenmod on the M8, and more. I share not to boast but to share what is possible for everyone here. All from reading. Often the same thing dozens of times. Tons of googling as well.
[Magisk] bigknowz:
Pixel 8 Pro
[Magisk] majorfigjam:
Then all you need is 7Zip-ZS (Windows) or something like Peazip for Linux.
[Magisk] osm0sis:
@badabing2003 pretty much captured the essence of my feelings here. Thanks for that. I'd also like to point out that I'm pretty much the only one who's actually ever documented anything here, and I only did it because nobody else would step up.

It's been generally pretty Spoiler content hidden.ing thankless and this thread is exhausting, especially every time some new bullSpoiler content hidden. goes down and the Telegram crew pour in and display their attention spans and unwillingness to read.

I didn't spend all that thought and time trying to make sense of this for everyone and organize/write it in an overall approachable, thorough yet concise way, to have people just go "naw too hard" and bury the thread in piecemeal repetition ad nauseam. Hence, yeah, it was very frustrating for me to see someone outright say they preferred that.

Anyway I was thinking about unsubscribing lately, before all the recent drama, so I think I'll follow through on that since my fork remains stable and serves its purpose to be less chaotic and more futureproof for the advanced users around who know better, and as far as I'm concerned it won't ever need support added for any illegal warez keybox Strong nonsense. I have zero interest in that. So yeah, @ me if you need me or find me in my thread with the other sensible people. ✌️
[Magisk] bigknowz:
not working
[Magisk] majorfigjam:
Then you're not doing it right, or you don't have a genuine P8P factory image.**

Categorically, any Pixel factory image, beta or otherwise, that is downloaded from Google's site can be unpacked with 7Zip-zs or PeaZip.

I walked someone through the 7zip process step by step in language that someone who advertises themself elsewhere as a s*****s a*********r might understand, and it definitely works.

** Edit: you don't need to mount the images, only extract from them.
[Magisk] HippoMan:
I'm totally with you. When I occasionally write posts that explain how frustrating it is to deal with people who don't try to figure things out on their own and who repeatedly want to be told answers to questions that already have been documented and already been answered here numerous times, and when I occasionally urge people to read the OP and other docs, you are the one I am always thinking of and sympathizing with.

I'm sure that this thread would be a *lot* less informative if all your documentation and explanations were removed. In other words, I know there are numerous people who have indeed read what you have contributed and then learned a lot from your contributions ... me included. So, your much-appreciated work has not been in vain, at all.

To any of you who don't like the level of what you consider to be technical know-how that is reflected in these painstakingly laid out docs, then I invite you to write your own documentation which you believe to be more easily approachable and newbie-friendly, and then point questioners here to your own docs.
[Magisk] HippoMan:
UPDATE: Hmm ... maybe we can agree on a standard blurb that we all can post if we believe that the questioner's answers can be found by searching and reading. Maybe something like this:

READ THE FIRST SENTENCE OF THIS THREAD'S OP

And that first OP sentence could be something like the following:

Before posting any questions in this thread, please demonstrate that you have indeed read all the following text in this OP, and that you have indeed followed and read all the links contained in this OP which pertain to your questions, and that you have indeed utilized the search function to try to locate information which is pertinent to your questions.
[Magisk] Aarif goku:
Found 395 revoked once and they reverted back to 94.. Compromised boxes have little to no life so be careful.

Source: https://android.googleapis.com/attestation/status

Edit: seems entries are being updated and it has 389 now.
[Magisk] mrjuniork:
PSA:

I assume that everyone now made their point about stuff?

As much as I understand the shared opinions, frustrations and disappointments, they are indeed cluttering the thread and make it very challenging to extract needed information.

You could always create off-topic threads, tag the users you need to address something to, and we can all move on accordingly.

All further off-topic posts will be deleted without further ado. And most of you know that this has become quite a tiny area, since the OP and I have given quite the breathing room when it comes to express something.

If that is being taken advantage of, I would have to tighten things up a little 😊

We should now get back on all the dozens of topics that have gotten a part of this whole thing when it started more than 900 pages ago!

Cheers,

mrjuniork
[Magisk] majorfigjam:
Question to moderator(s)

In view of this categoric statement from the OP, can we now assume that questions about broken TEE, as well as hacked or leaked keyboxes (ie warez) etc will also be dealt with summarily?
[Magisk] majorfigjam:
Not speaking for mods, but questions about pif and rcs are on topic - some prints allow rcs with pif, the common one doesn't.

Questioning Google's motives, and general rants about rcs interoperability probably are not.
[Magisk] BillGoss:
You don't need simg2img - it's not a sparse image.

I mounted it using:

sudo mount -o loop,ro,noatime <partition>.img /tmp

And then I just browsed /tmp to see the files.

Fyi, I use WSL on my Windows 11 PC. And the commands only works in WSL2 (fails in WSL1)

Credit due to @osm0sis for telling me what I've just to you.
[Magisk] mrjuniork:
It will be handled with care and oversight. If I post something OT and the OP replies to me, then there is no need to step in as a mod. So we've got many layers to look at, which, from a psychological point of view, is the fun part of helping out and supporting this great community ☺️
[Magisk] Thebear j koss:
How come some don't get deleted and others do? I've had 4 RCS posts deleted today alone. While I still see tons of RCS is broken posts going back to March. I'm just trying to figure out what is on topic here and what isn't? Why do some get a pass and others don't? I mean I can see the people who post stupid, hateful posts because they may not agree with someone getting deleted, but posts that pertain to the topic, give an honest opinion, and are not rude or hateful are not allowed? I'm mean I've been around long enough that mods get final say and XDA isnt a true community anymore, but the deletion of posts just because it isn't of popular opinion or has a different view doesn't deserve to be deleted. This isn't a fix RCS or find me a working key or how to sign a ROM topic, this is to get play integrity fix. Users should complain or find other means to fix the other issues that may arise... Sorry to the devs here, you guys are appreciated and you are never given the accolades and respect you deserve. Too many users and abusers to continue anything with civility here. Things are just constantly off the rails and reading 10 pages a day of unnecessary posts is just out of control. I can't see why anyone would deal with the headache...
[Magisk] mrjuniork:
We are not going to have a public discussion about this. You can always send me a PM and then I could lay out some things, when time allows me to.

So please, no more mod engagement in a development thread.

Thx in advance 👍🏻
[Magisk] BlackSoulxxx:
Some keyboxes has been revoked/banned by Google from yesterday update. They acted very fast and can revoke a keybox just by screenshots of people checking the validity of them keybox. FYI
[Magisk] pndwal:
Suppose you mean an OEM/strong one? ☹️... Can you say which device is now compromised? 👍 PW
[Magisk] JazonX:
Question for the current PIF Hunters;

After the last ban wave - most of my Android 11, 12 PIFS are banned.

To find success;

Which year security patch / Which android version build props should we search for as of now?
[Magisk] majorfigjam:
The ones already mentioned by name on this forum? Several times!

Start after post 17630
[Magisk] zgfg:
There are still A11 and higher prints
[Magisk] JazonX:
No. I'm not asking for names.

General Criteria for successful prints so I can hoard a few for the stressful times ahead, since now I have some time to put some factory roms under the microscope.

eg;

Android 8<10 | Not higher than 11 , Not less than 8.1.0

Security Patch - Not less than 2017 - Not higher than 2018

Thanks a lot for this confirmation, I shall keep testing if any comes across.
[Magisk] Tony.Montana.:
Hello,

guys I'm sorry if not the proper place to ask, but I've read

@osm0sis​

@Mitezuss​

talking about this same issue.

I'm on POCO X3 NFC ArrowOS rom that unfortunately has

test key signature

and cannot pass MEETS_DEVICE_INTEGRITY anymore.

So to use google wallet etc, I want to install new custom ROM that has

approved key signature

.

How do I know, before installing, if these other custom roms (Nitrogen OS, LineageOS, CRDroid) have this correct signature? Is the only way to ask its creator?

Thank your for your support
[Magisk] BlackSoulxxx:
I cant tell you what specific device(s). I have insider contact, the OEM responsible for revoked keyboxes has been contacted by Google with some very "strong" words.

However, strong integrity can still be achievable even with revoked keybox, with certain combination of fingerprints. Google still allow certain locked bootloader devices to pass strong even with revoked keybox, and we can mimics it.
[Magisk] majorfigjam:
Your choice. You'd save yourself a LOT of time.
[Magisk] markdewet:
Just want to confirm that my Google Wallet is working 100%, including tap to pay, Using PIFFork, Shamiko and latest signed LineageOS 21.0. Thank you to Osm0sis (PIFFork), as well as to all those that assisted. It really is much appreciated. Regrettably I cannot attest to RCS working or not as it is not a function much used here in South Africa.
[Magisk] zgfg:
Is this a banking app (usually they don't explain what they find) or Momo
[Magisk] denzel09:
Oh WOW, hope devs can found this "way"
[Magisk] shaw790:
Im still unable to get device integrity. Can someone help?

Im using apphide to hide the modules also. Still this is the result. Will it help if i switch to kitsune?

View attachment 6117431
[Magisk] Tony.Montana.:
which ROM are you on? If it's a custom ROM it may be signed with a test key and for this reason DEVICE_INTEGRITY is not passing
[Magisk] shaw790:
Im having oneplus stock rom.
[Magisk] jakell888888888:
It's not practical, and it happens that my friend and classmate who works at Google says it's impossible unless you have a key but I've asked a lot of phone manufacturers and they say it's impossible to leak. So for now it's a death marriage that's all I know so far.
[Magisk] kholdstayr:
I have a Moto Edge+ 2022. I want to pass device . I'm not interested in key boxes. I can't pass device using the sailfish print, and from what it looks like, nobody else can.

I read people mention Husky on here. I managed to figure out what that means, and also figured out how to get the files and generate a print. But that still didn't work for me.

I tried Chito and Osmosis with the print. In fact, I generated several prints from different Husky firmware updates.

So I guess I'm asking, can anyone give me a hint on something I might be able to try next? Thanks in advance!
[Magisk] sawdoctor:
The sailfish print and the one you managed to deduce are still passing device integrity so might be something with your set up. Sailfish is failing rcs but still passing device integrity
[Magisk] chiteroman:
For some reason that I don't understand, the module is not running. It's as if ZygiskNext ignored it, it's either that or the logcat is not complete... Try filtering through the logs of my module.
[Magisk] pndwal:
Regarding:

Folks, if ROM has working fix for PI DEVICE_INTEGRITY it will still work with Magisk!... However you DON'T need PIF as it's main functions (triggering fallback to on device basic attestation and bypassing server end enforcement of hardware-backed verdicts) are already performed!!!...

You DO need to hide root from GMS however as always...

In the good old days MagiskHide did that for you... You now simply need to do it manually now if not using PIF etc...

Just add Google Play Services (GMS) com.google.android.gms.unstable (Droidguard/attestation) and com.google.android.gms (main process) to the denylist... DenyList enabled will be enough for this but Shamiko is recommended for better root hiding from apps...

As @DanGLES3 said above (ninja'd!), PIF is NOT required if you hide root from GMS yourself as described above...

🤠 PW
[Magisk] pndwal:
Oh!... I did wonder...

Can you try with latest?...

If you/others can't use latest Bonvoy with TJW Magisk ATM, they may need to wait for next Magisk build with native bridge loaded Zygisk (this massive refactoring is already merged upstream), or use Alpha which already has it, as I originally suspected...

👍 PW
[Magisk] pndwal:
Absolutely nothing?!

I've addressed that several times in my responses, and while this is clearly your mantra, it's NOT true!... MUCH has been done to secure web based banking etc, and if extra functions like hardware support for biometric scanning or contactless payments are added to such (browser based) solutions, strong verified boot attestations or equivalents (working Secure Boot etc) will undoubtedly also be mandated.

Please don't avoid assimilating stuff simply because it's inconvenient for you! 😉 PW
[Magisk] pndwal:
Please see this above:

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

🤠 PW
[Magisk] K0rgar:
Thank you, did tick gms main process and unstable, disabled the pi module and passing the integrity check.

Thank you thank you.
[Magisk] zgfg:
Xiaomi.eu hides itself but not your Magisk - Magisk is not part of Xiaomi.eu, you installed Magisk and you have to care about to hide it

Xiaomi.eu cannot look what Magisk version/fork you may have installed, what modules you use, do you have Zygisk or Ritu, do you have Shamiko or not, do you have LSPosed and its modules, etc

And what bank from which corner of the world you have to hide all that stuff (that has nothing to do with Xiaomi eu) form that banking app
[Magisk] RosarioDV:
Thank you both! It is working now! And I now have a better idea how this works
[Magisk] Catfriend1:
Success !

- Xiaomi mi 8 with Pixelexperience: Magisk 24.6 + Shamiko 0.7.4 + DenyList "gms + gms.unstable" + PlayIntegrityFix 12.3 = working

- Xiaomi mi 13 with Xiaomi.eu 14.x stable: Magisk 24.6 + Shamiko 0.7.4 + DenyList "gms + gms.unstable" = working
[Magisk] cangurob:
That is the entire log file...

I'll try to uninstall it all, and reinstall.

How do I access the logs for your module?
[Magisk] digger16309:
Confirmed - the Bonvoy app v10.23.1 works perfectly for me with TJW Magisk stable 26.4 on a P6P running A13, Shamiko, PIF, LSPosed, all latest versions, Bonvoy in deny list.
[Magisk] BROKEN1981:
Do you have a link for Applist detector? Not sure where to find it on Pay Store
[Magisk] pndwal:
It's an LSPosed module from LSP associated Dev... Naturally you'll find it in LSPosed repo if you already have that installed...

An XDA guide thread is here:

https://xdaforums.com/t/hide-my-applist-a-brief-guide.4519731/

... See the OP...

👀 PW
[Magisk] EuK_V:
Tested payments (gpay) on two phones samsung a70 and redmi note 9 pro, both los20, magisk 26.3, pif v12, with dev's recommended settings. Working well, all the payments went through.

Thanks again @chiteroman! (y)
[Magisk] noncomjd:
OnePlus 8T Oxygen 13, Magisk with Zygisk-LSPosed, Seamless host, deny list enforced and KGDrgon Safety Net Fix was failing safety net and Google Pay was not working.

As suggested above removed Safety Net fix, disabled Zygisk and seamless host and download installed Play Integrity Fix and passing Safety next and Google Pay is working.

Thanks!
[Magisk] TraderJack:
Just posting my experience to add to any relevant data points. I'm still on a Pixel 3 XL running A11 and haven't seen many posts on devices this old, so thought I'd chime in.

Everything was working fine until about Wed/Thu this week when I woke up to my device telling me through a notification that that it no longer met standards for Pay to work.

I didn't bother with it too much as I had been thinking about rebuilding my phone over the next week, but confirmed yesterday that indeed my Wallet didn't work when I tried to pay with it. I tried to check with Play Integrity checker but I was running into the too many requests API issue (and didn't realize at the time that Play had it's own checker). Tonight I tried again with PI checker and sure enough I only was passing BASIC not DEVICE.

I was running USNF 2.4 (MOD 1.2?) but was quickly pointed to this thread and found out that many people were experiencing this same issue. I installed the latest PIF 12.3 and rebooted and viola! I passed BASIC and DEVICE with PI checker. YASNAC and Google Play Store checker also all report fine with CTS profile also passing.

HOWEVER, my Wallet was still stating that my device didn't meet standards even a couple hours after reboot. The fix which worked for me was:

Clear Cache only (not data) Wallet and Play (not sure this was required)

Turn on Airplane mode

Set date forward 1 week

Reboot - For some reason even after trying this twice and my phone being in Airplane mode it kept coming back up with the correct date. But, after 2 or 3 times trying this I simply reset it back to the forward date after my reboot (while never taking out of airplane mode).

Then I checked Wallet and it still said it didn't meet standards, but after waiting about 5 minutes I went back in and it said it was now working!

Set date back to normal.

So much thanks to @chiteroman for this as well as all my fellow XDAers who were diligently testing over the past few days making all these notes which allowed me to fix easily enough.

Do we have a more precise explanation of exactly what Google changed over the past few days and how the update PIF now deals with it? I haven't been involved actively in about a year and so a concise update to refresh me would be appreciated!

For posterity, here is my full config:

Pixel 3 XL Android 11 (10/1/21 Security Update, 1/1/21 Google Play System Update)

Kiri kernel 4.9.278

TJW Magisk 25.2 (hidden)

PIF 12.3

Shamiko 0.6

Zygisk - LSPosed v.1.9.2

HMA 3.1.1-404

XPrivacyLua - FWIW this is installed, but not activated via LSPosed