yashsingh1/xdaforums huggingface dataset:
[Magisk] TraderJack:
Can you maybe shed some light on this for me. I'm about 99% sure that in the past not only did I read from multiple sources that you should hide Google Play Store and Google Services Framework (and possibly Wallet too), and additionally almost equally sure that in the past if I did not do this then I would not properly pass checks. I can't say that all were required, but it certainly seems that the advice to add these used to not be a myth and at least one was required. I remember on more than one phone rebuild not passing checks (this might have been SN and/or Play Store certification checks) until I added these to deny list.

Based on your advice and the other's that echo it I just went in to check my DenyList settings and I have Play Store, Wallet, and GSF added but NOT GSM.

Up until 3 days ago my device worked fine, passing BASIC/DEVICE/CTS checks and working with Wallet. This is with TJW Magisk, Shamiko, HMA, and using USNF 2.4.0 Mod 1.2. All of this without having GSM added at all. And, just to be clear I was using USNF and not PIF (I just installed that today).

So could you:

A) Corroborate if I am remembering correctly or not that adding some of these others in Deny was previously required?

B) Explain, if you can, how my device worked with USNF up until this week's change without GSM being added to Deny?

C) Confirm whether or not we need to hide *anything* with PIF now? It isn't clear to me from your quoted post if you are saying we have to add those 2 GMS components if we are using PIF, or if we don't need to hide anything?

It sounds like maybe we don't need to hide any Google app at all and the only things we need to put in the Deny List are those 3rd party apps, like banking, which give us issue.

EDIT ON C ABOVE: I think some of the confusion was that you were responding to some about ROMS with built in fix that don't need PIF and so need to manually exclude GMS? I'm still not sure though because PIF GH page says:

So to me it still isn't clear if PIF users need to exclude anything on Deny List (when using Shamiko)

EDIT ON A ABOVE: It a possible these exclusions were necessary with old Magisk and the hide list?

thanks!
[Magisk] TraderJack:
Just to chime in I first noticed a problem with Bonvoy a few weeks ago when I tried to book a room. I hadn't used it for months. I think I just needed to add it to the DenyList and every thing works. You can check a few posts up for my system config. But, briefly, I use TJW Magisk/Shamiko/Zygisk LSposed with the latest Bonvoy without issue!
[Magisk] TraderJack:
Curious why you need Walmart on there? I use it weekly including WMpay and never had the need to block it, it doesn't ever complain about root to me (?)
[Magisk] marcopit-92:
Still I cannot use it on my phone. I tried to fix in many ways but nothing worked. Some of you guys use custom roms, some of you different magisk app, some of you different modules, now I won't try messed up with Magisk or custom roms on my main phone honestly just for this app, also because this Asus phone has some compatibility issues with custom roms version. if some of you has my same setup and can access the app then I don't know what to say.. honestly I can't and I had to downgrade to an older version as searched on web, that was my only solution till now. I was thinking at this point that some older module like Riru maybe left some files and the app still detect it..
[Magisk] bigknowz:
Thanks, don't have Windows, using 🐧 on Chromebook. @osm0sis, thoughts?
[Magisk] osm0sis:
Yep that simg2img output probably means it's not sparse.

Did you try the commands as written?

mkdir -p ~/tmp;
sudo mount -t auto -o loop,ro,noatime system.img ~/tmp;

Some don't allow rw anymore, and there are lots of system image formats now (ext4, ext4-dedup, erofs, etc.). Also if you were in / then sys is an important directory you shouldn't use.
[Magisk] Aarif goku:
Are you Setting the SDK_INT value to 24? anything above might fail.
[Magisk] badabing2003:
You don't necessarily have to mount, you can unzip with tools like 7-zip and similar.
[Magisk] osm0sis:
Doesn't handle erofs, I believe. Not sure about ext4-dedup either.
[Magisk] badabing2003:
Right, but it should for the one he's trying. :)
[Magisk] TurboLed:
On Windows, this tool works well for extracting img:

[GUIDE] How to extract system files from stock firmware

First of all: Tool to be used in this guide was developed by user And_pda from Russian 4pda.ru forum. So all credits must go to And_pda The original thread (in Russian) is here. Actually the original thread is about several tools to works with...

xdaforums.com
[Magisk] CZ.Kostra:
Check out README sections Failing DEVICE verdict.
[Magisk] shoey63:
But why use PC at all? Just extract prop files on the phone with Zarchiver and use gen_pif_custom.sh to create a custom.pif.json

Edit: unless you are using pixelflasher
[Magisk] majorfigjam:
Install and use PeaZip. Google for instructions to install on Chromebook. You do not need to mount images to extract build.props for the device type you mentionned.
[Magisk] shadowbullet707:
I'm also on the same boat too. I don't pass either, it was passing before not anymore. Sailfish doesn't pass my device. Pixel 6 Pro. Checking the readme doesnt solve my issue. It just straight up doesn't pass anymore. It's just over a sudden, also using PIF none fork. If this cat and mouse with Google keeps up, it's fine. My device runs fine without it. Wallet and tap to pay is not needed when you have muscle memory to pull out your wallet. I rarely use GPay anyway.
[Magisk] sawdoctor:
Strange really strange, sailfish fingerprint is still working for most people. Have to hope Google hasn't started rolling out some sort of block
[Magisk] shadowbullet707:
Yeah, I tried everything in the book. I also found a private print and that isn't passing either. It was like last night I got it to pass and now its not. I'm just at a loss. So I reverted back to sailfish to see what happens later. Thank god I'm not the only one that is not going insane lol. xD Google stop being childish lmao. Its our device and we have the right to do what ever we want to our handsets. If we want to root we will root lol.
[Magisk] Captain_Throwback:
And you're on stock ROM?
[Magisk] shadowbullet707:
Yes, I haven't been on a custom ROM in so long after Resurrection Remix back in the day with Nexus 6P. My Pixel 6 Pro is on the latest A14 June update.
[Magisk] zgfg:
Custom ROM or kernel, signing keys and name - have you checked?

Modules and LSPosed modules - which ones do you have and have you tried by disabling them (reboot afterwards)?

Have you checked the PIF logs to make sure that JSON fields are read and applied?

Topics are covered by FAQ

Edit: Crossing off custom ROM per your answer above
[Magisk] shadowbullet707:
signing keys, I have no idea what to do with those. All my modules I've been using when I first rooted and got on the PIF Module and everything been passing with RCS before until Google banned the print. All the stuff on the print is all Sailfish when I installed the PIF Module. Then later I found a private print and used PixelFlasher to install the private print That been working for 2 days straight and straight up not passing anymore. Assumed that It got banned by google. Fiddle around last night and got it to pass twice and just fail all over again. Reverted back to the Sailfish no luck. I just gave up on this lol. Not even worth the time to fix it. PIF still works for other things so I'm not messing with it. I can still at least use my bank apps without issues for some odd issue or my bank doesn't check for root or unlocked bootloader. COD M works fine and Pokemon Go still plays without issues. I did also turned off every single one of my modules and leaving PIF on, sadly no luck on that either. I'm just gonna leave it as Google banned my device entirely. It can't even do a Play Intgrity test either or the PlayStore version. Doesn't say backoff or anything it just shows up blank. TB checker also says null and all things failed. (Sailfish) / SafetyNET (Yes I know its discontinued), usually it says all 3 passed. Just the first one passed.

I've been on 40 console bans on Xbox 360s on a RGH and 20 console bans on PS3 consoles so I know how it goes finding a private CID for CFW PS3's and a KeyVualt for RGH/JTAG consoles. Google is just relentless so idk what to say anymore.
[Magisk] bigknowz:
Thanks to all that chimed in, ended up doing everything on my phone, RCS working 👍
[Magisk] pndwal:
I think someone reported Sailfish started failing for them on official PIF but worked when switched to @osm0sis' PIFork (and configured Sailfish) no?... Might be a regression and work with previous official build(s) too I guess... 🤔 PW
[Magisk] wfred:
If it's a currently maintained well known rom and labeled official it should be okay. Ask in the rom's thread to make sure
[Magisk] BillGoss:
Brilliant!

Using ZArchiver let me do the whole process entirely on phone.
[Magisk] shadowbullet707:
So like I re did this turn off everything but PIF and now its passing. So its a module and i don't know which will break it from passing. Going through all of them will be a hassle. So I just go like turn off one by one after reboots and see what triggers it? Also I do have gms undtable and gms in denylist but no enforce since I have shamiko on. I don't know if that does anything, not sure. Should I just show a picture what I have installed as module wise on Magisk/LSPosded? LSPosed Mod was the one. Bruhhhh
[Magisk] pershoot:
If you have a proper print (going off of your post above) which is known working for RCS + contactless | wallet (which is not the current public print), if you switch to APatch (latest is 10763; bmax121) + Zygisk Next (latest is 106-2; Dr-TSNG) + PIF (I use fork v9 (osm0sis) but chiteroman's should also work) + LSPosed mod (7295 is latest; mywalkb), that should also work for you.
[Magisk] BillGoss:
[

I just tested this and:

- 7-Zip on PC works perfectly to extract the build.props.

- ZArchiver on Android works perfectly to extract the build.props.

So I can do the whole process to generate the fingerprint starting with a factory image on either PC (using WSL to run gen_pif_custom.sh) or phone.

Thanks guys!
[Magisk] pndwal:
👍

Yup... Or turn on one by one w/ reboots...

No need for GMS in denylist even with Shamiko, unless you want to fix font module issue with system UI... Then just have GMS core process selected to enable Shamiko fix...

👍... Why using modded one?

🤠 PW
[Magisk] BlackSoulxxx:
They all said its impossible to leak, but the banned list keep getting longer every so often:rolleyes:

I can share some details: yesterday update to revocation list made me lost half of my stash. A lot of them was from a single OEM.
[Magisk] shadowbullet707:
The OG one is Archived and it crashes when I open it. So I used the Forked version of LSPosed Mod that is supported. It was working in the May Feature but June's update broke it so it can't open without crashing.

As for the denylist I'l remove gms and unstable since I have shamiko.

Either way It was LSPosed but I'm gonna re install the mod version and go through other modules are in there and disable one by one after a reboot and check PIF and see if it passes and find out who is triggering it.
[Magisk] pershoot:
@shadowbullet707

Data from my testing:

🔧 [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] denzel09:
If you have a stash, can you send one? Obviously i will not share it :censored:
[Magisk] pershoot:
LSPosed non-mod seems to not be working properly on latest A14 (which I came to realize after the fact).

Please see my messages with you tagged on it some pages back.
[Magisk] dcarvil:
If you have a lot of modules, I'd do a binary search instead of one by one. Turn off half the modules. If it passes, you know the problem is in the half turned off. Turn on half of them. If passes, then turn on half of the remainder. If doesn't pass, turn off half of the ones just turned on.

That should save some time if you have many modules.
[Magisk] shadowbullet707:
I don't have much modules so I figured out who was the problem. it was bootloader spoofer, once I toggled it off. PIF passed.

I was never tagged. I'm new replying here can you tag me? I'll reinstall the original LSPsoded but for me it crashes but lets see what you said. I'm using the Zygisk and not Riru
[Magisk] pershoot:
Not you; @pndwal.
[Magisk] D€INOS:
A (small sample size) observation regarding fp passing DEVICE: Among the 13 fingerprints I've found so far, they all have been A10-A11, mainly A11. 3 passed with api level 30.

3 prints were from the old now gone pif.dedyn.

Might be useful info, a slight deviation from the old recommendation.
[Magisk] pndwal:
Tagged me... I think he said NOT working anyway. 😜 PW
[Magisk] pershoot:
Please follow my testing methodology and what I have advised, if you want LSPosed. I have linked you throughout (above).

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

🔧 [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] shadowbullet707:
link? I would like to test.
[Magisk] pershoot:
I have already linked you (above). Please read the posts I have written.
[Magisk] shadowbullet707:
Wait do I have to uninstall magisk? what about the Modules that I have installed?
[Magisk] pershoot:
I could not get things to work on Magisk; admittedly I did not try for too long (i'm on borrowed time before EL Goog notices anything off and kiboshes contactless (which I use heavily; not just for pay purposes) which would require me to wait ~1.5-2 days before potential restoration).
[Magisk] shadowbullet707:
My Magisk is working fine now with my setup now since I figured out what was the issue. Bootloader spoofer kills the PIF passing. Once I disabled it it passed again with my private print with LSPosed Mod.
[Magisk] passionicon:
If everyone has a private print now. Does that still make it private 🤔.
[Magisk] majorfigjam:
Only if everyone had the same "private" print, which is definitely not the case.
[Magisk] kholdstayr:
If you show me your private print I'll show you mine

/s
[Magisk] pndwal:
You should check, but I understand modules are essentially compatible... And I believe you can have the two SU solution coexisting, but forgotten details... To remove Magisk you'd need to take Uninstall, Restore Images and delete magisk.db and magisk directory from /data/adb to remove conflicting(?) configuration but keep modules in place...

But do your due diligence. 😜 PW
[Magisk] pndwal:
Digital print, or Polaroid needed? 😜 PW
[Magisk] HippoMan:
And there already is a thread which is specifically dedicated to questioning the Googlefrinchians and to general ranting ... all of which will be totally on topic in that thread. For that kind of questioning and ranting, as well as any complaining and whining, don't do it here, and instead go to the following thread:

https://xdaforums.com/t/discussion-magisk-the-root-hiding-and-mod-hiding-cat-and-mouse-game.4425939/
[Magisk] pershoot:
I believe I have read in passing that they 'can' both be in use (not sure one would want to), but in that scenario, Magisk modules take precedence. With that being said, I do have Magisk (mgr.) still in place but not activated as my ramdisk isn't patched accordingly and doesnt have the hooks to it (this is only so I can go back swiftly for potential future testing).
[Magisk] zgfg:
Btw, I think I asked you exactly that, way back in the post #18199, which modules and LSPosed modules you have and have you tried by turning them off

You answered something (like you were no more interested), but nothing about which modules you have and have you tried with the modules disabled

Now, hours later, the culprit was in modules....
[Magisk] shadowbullet707:
Well so far I found the module that was not passing my PIF so I didn't have to through all of them. One module was boot loader spoofer on LSPosed fixed it. My setup is okay now. Unless you have any suggestions. It's still passing so that's all it matters.
[Magisk] zgfg:
No further suggestions from my side (if that would be taken in vain again 😁)

Just generally, be systematic and next time when advised, try to follow, it would go faster and with less ink here

Btw, Bootloader Spoofer, per se, AFAIK (whenever I tested but its earlier versions) should not interfere with PI - however it MUST NOT be applied to gms
[Magisk] chiteroman:
v16.4 released!

Spoiler content hidden.

Release v16.4 · chiteroman/PlayIntegrityFix

Misc improvements in code Remove keybox.xml parsing due DroidGuard detections (better use FrameworkPatch) Add BOARD and HARDWARE fields in json

github.com
[Magisk] David B.:
What kinds of issues was keybox.xml support causing, and do you have plans to bring back support for it?

Being able to use a keybox via PIF would be preferrable to using FrameworkPatch given that it causes performance degradation.
[Magisk] tryigitx:
If you removed Keybox.xml support because Google banned keyboxs, you are wrong.

Because Google's Keybox pool is so large, it has really advanced methods. They have to use cache for the server.

And I agree with the other comment. Even though the frpatch method is the best, it requires removing files that affect the performance experience. For example, the startup time of the phone increases by +5 seconds .d
[Magisk] badabing2003:
As far as I know, it didn;'t work.

I placed a revoked keybox.xml in /data/adb/ and it was still using the device's keybox, and passing Device Integrity.
[Magisk] osm0sis:
Oh it definitely worked, at least with a working keybox and DEVICE_INITIAL_SDK_INT >29... 🧐🤷‍♂️
[Magisk] Vision:
I don't have so much problem about frameworkpatch method, but I have the problem the apps I have on MagiskHide all close immediately with dummy boot-framework.art, and as read a possible solution is with PathClassLoader or something similar, but I don't understand how exactly make it.

View attachment 6117651
[Magisk] David B.:
It does work. Since I want RCS to work, I had to mess around with finding a private print that would work with it, but once I found one, I had no problems at all. I plan to continue using it. Or at least, I plan to continue using it if I am able to find a keybox that was not impacted by today's revocation update. ☹️

Perhaps @osm0sis can add it to his fork? 😁
[Magisk] osm0sis:
Nope!

Sorry, no support for stolen goods in my fork... 😬

See the last paragraph here:

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

Anyway... 😶‍🌫️
[Magisk] gj4560:
Hey everyone,

I'm in the process of finding a private fingerprint and I've found a repo I can test them from and I've read all of the supporting guides and whatnot, however I still have some questions.

Should I only look for fingerprints that are from Android 8.1.0 devices? I know they have to be release-keys to have the best chance of passing device integrity but not sure if the Android version matters that much. I've tried some Android 14, 13, 9 and 8.1 fingerprints with no success yet, I only pass basic or sometimes nothing at all.
[Magisk] zgfg:
I don't know for your particular repo but generally there are still working prints from other Android versions, particularly A11 and higher

Btw, there was a similar q and answer here just two or three days ago, and similar posts several times during the last month (and since the last ban)
[Magisk] majorfigjam:
You are likely wasting your time, unless you have a highly automated process, a lot of spare disk space and a very fast data connection

The main repo has thousands of device roms, and less than 100 are known to work.

If you read the last week's posts, there are enough clues to locate an rcs supporting print or two, at least until Google decides to kill them off.

As Osm0sis recently noted, Google are prone to making changes on 29th of the month, so this coming weekend may be painful.
[Magisk] zgfg:
Last ban was on May 25 (May 29 was 'reserved'' for changes in RCS). And before that there was the ban on Feb 29 - hence nothing on Mar 29 and Apr 29
[Magisk] osm0sis:
Mar 29 was the first RCS test ban. Then just a smattering of specific print bans through April, IIRC. Late May was also the testkey ROM ban.
[Magisk] chiteroman:
After reading that, now I have a question, is sharing keyboxes illegal?

They are private files that only OEMs should have but they are not proprietary software either, they are just XML files.

I don't think there are any legal problems in this regard, especially with keyboxes that are already on the blacklist. But with the ones that work.... Who knows if Google could sue or something.

If any staff has a problem with that, I can delete everything about keyboxes on XDA.
[Magisk] denzel09:
Chatgpt tells that sharing keybox.xml is illegal, so ... 🥶
[Magisk] Vision:
To provide assistance what is a keybox, and what is its use etc. for learning purposes is legal.

The other half is Robin hood.

View attachment 6117781
[Magisk] osm0sis:
In my understanding a keybox.xml is corporate IP leaked from a breach of one kind or another: NDA or hack. So something illegal and prosecutable had to occur for us to be able to download them, making them stolen goods/IP, and possession of them at all is probably therefore also illegal. I doubt they'd sue the receiver for that, especially where this is by far the tamest of uses for one, but yeah.. 🤷‍♂️

Them being worth ~$10,000 on the dark web should probably be your first hint that they're not exactly above board. 😛
[Magisk] jakell888888888:
No, please don't delete this area, it will help a lot of people, technology knows no borders, the forest is big, every person's idea is independent, we appreciate everything you do.
[Magisk] chiteroman:
Seems logical 🤔

Dark web = 99% scam
[Magisk] badabing2003:
I believe you guys, but how do you explain this?

My test was extremely simple.

Install 16.3 reboot test key attestation, it showed the device's.

Test PI, it passed device.

Put a revoked keybox.xml in /data/adb/keybox.xml

Reboot

Repeat test.

Same results.

Why didn't key attestation test still showed the device's keybox and not the revoked one?
[Magisk] zgfg:
I don't see a problem about your modules with support for he keyboxes, or with discussions about - as long as you don't share the ones

---

Btw, publicly available ROM archives with extracted keyboxes (among other legal files like build.props) should be also illegal
[Magisk] osm0sis:
If those were your only steps then it sounds like you forgot to raise DEVICE_INITIAL_SDK_INT >29 to trigger the keybox to be used.
[Magisk] changhuapeng:
My sentiments are the same as osm0sis's in regards to keyboxes' legality. However, I don't see any problem with sharing information and tools for keyboxes. It's pretty much similar to video game emulation where distributing game ROMs (i.e. warez) is kinda illegal but sharing the emulation software or information are not.
[Magisk] osm0sis:
They're not actually from the ROM dump though, it's not like we can dump one from our devices.
[Magisk] badabing2003:
I'll test again, thanks.
[Magisk] Vision:
The PIF module can't hook into like the frameworkpatch method, for that the key attestation show the same as before install the PIF.
[Magisk] badabing2003:
That would explain it, thanks.