yashsingh1/xdaforums huggingface dataset:
[Magisk] Stillhard:
The way i see it in this code

TrickyStore/service/src/main/java/io/github/a13e300/tricky_store/Config.kt at 49554a8bbdc2011b5e1941fd66b07a98bb306701 · 5ec1cff/TrickyStore

Contribute to 5ec1cff/TrickyStore development by creating an account on GitHub.

github.com

This line:

TrickyStore/service/src/main/java/io/github/a13e300/tricky_store/Main.kt at 49554a8bbdc2011b5e1941fd66b07a98bb306701 · 5ec1cff/TrickyStore

Contribute to 5ec1cff/TrickyStore development by creating an account on GitHub.

github.com

Will create the folder etc:

TrickyStore/service/src/main/java/io/github/a13e300/tricky_store/Config.kt at 49554a8bbdc2011b5e1941fd66b07a98bb306701 · 5ec1cff/TrickyStore

Contribute to 5ec1cff/TrickyStore development by creating an account on GitHub.

github.com
[Magisk] Vision:
I thought this line is for when users create manually the folder, for the module can detect the tricky_store folder and the target.txt and keybox.xml inside.

EDIT: From devs.

View attachment 6124542
[Magisk] innit:
So far I've tried these builds but still that folder is not being created on boot.

chiteroman:

Tricky-Store-v1.0.1-35-b1a0755-release

Tricky-Store-v1.0.1-35-b1a0755-debug

5ec1cff:

Tricky-Store-v1.0.1-34-49554a8-release

Tricky-Store-v1.0.1-34-49554a8-debug
[Magisk] Vision:
I know, according to this i open the PR, to create auto the folder and a empty target.txt inside, but the devs say this "The folder should be created automatically on first launch"

EDIT: Can you test this?
[Magisk] Stillhard:
Just do logcat | grep Tricky, you'll see if something wrong while boot, the module will abort and don't do the rest of its process, create PR with the error you found
[Magisk] Vision:
So, for you after reboot the folder is have create automatically?

EDIT: Oh right, you have A11.
[Magisk] Vision:
According some users about Tricky Store module, between @osm0sis, seem like the folder tricky_store in /data/adb not create automatically.

Even though it is included in the code:

TrickyStore/service/src/main/java/io/github/a13e300/tricky_store/Config.kt at 49554a8bbdc2011b5e1941fd66b07a98bb306701 · 5ec1cff/TrickyStore

Contribute to 5ec1cff/TrickyStore development by creating an account on GitHub.

github.com

I have open a issue about this:

Folder not create automatically. · Issue #7 · 5ec1cff/TrickyStore

According some users, between @osm0sis, seem like the folder tricky_store in /data/adb not create automatically. Even though it is included in the code: TrickyStore/service/src/main/java/io/github/...

github.com

Please post log there to resolve this issue.
[Magisk] awtompson:
My wife is in the same boat. Whatsapp works great across platforms.
[Magisk] kodein:
Guys, I tried the tricky store module, but I don't have a valid keybox, so I uninstalled it.

Now I'm using play integrity 16.5 and this morning I went through basic and device, but now I'll only go through basic...

Therefore, I would like to ask if Google has not banned the fingerprint from PIF 16.5 again?
[Magisk] CZ.Kostra:
FP is functional.
[Magisk] TotallyAnxious:
What is this 6 weeks based on? Release date? Also how was this determined?

I must have missed this post.
[Magisk] majorfigjam:
Experience. It applies only to betas, as Sailfish has been going longer.
[Magisk] manjaroid:
"Roughly" six weeks is how I remember the post. Beta 3.1 released July 1, the finale will release in late August, so six to seven weeks.
[Magisk] Tromick:
I have S7 Edge with Stock ROM. It has Magisk v22 but due to it's bug, it gives error while installing, says Magisk v20.4 or above. Any suggested module for me?
[Magisk] Vision:
You can try Kitsune Mask latest stable.
[Magisk] osm0sis:
When the final/stable or next beta gets released doesn't seem to have any bearing on it, it's just roughly 6 weeks from the date of the beta's release.

A15 Beta 2.2 expiring yesterday-ish has continued the trend I already observed from the expiry dates for the previous A14 QPR3 and A15 Betas. A15 Beta 3.0 (i.e. PIF v16.6-beta public print) has roughly 2 more weeks left if the trend holds.

😶‍🌫️
[Magisk] innit:
I'll test it later today and will also try to get a logcat.
[Magisk] Vision:
Try the latest actions build.
[Magisk] sawdoctor:
I suppose the "good news" is if the trend continues we just need to update our print to the latest beta every 6 weeks
[Magisk] HippoMan:
However, discussing this and and other similar strategies in this well-known public forum makes it easy for the Googlefrinchians to learn how their attempts at Play Integrity enforcement are being circumvented, which could lead them to then close these security holes, as they have already done more than once in the recent past.
[Magisk] sawdoctor:
Pretty sure Google already knows. They could kill the sailfish print anytime they want but haven't
[Magisk] cmstlist:
There isn't always an available beta though. Once A15 exits beta, we won't have new public beta ROMs until A16 preview starts many months down the line.
[Magisk] osm0sis:
Bingo. 😉

And exactly, this is something they're intentionally whitelisting then expiring, so it's safe enough for now, though if it becomes too widely and publicly "abused" then us discovering their intentional beta loophole may cause them to rethink their whole system, which could also be bad.. So, still. 🤫
[Magisk] HippoMan:
... which is why I believe that we shouldn't post here in this widely known public forum anything we might unearth about their procedures.
[Magisk] osm0sis:
Exactly, we should stop and let the collective goldfish memory of this thread do its thing. 😘

In reality it's the committing it on GitHub that's more of a problem than this thread, however. 🤷‍♂️
[Magisk] sawdoctor:
Kinda proves your point against all the "Google haters" who blame Google for everything. If Google really wanted us to stop rooting our phones they could just push an update preventing us unlocking bootloaders. They could easily block what we are using.

It must be 12 months now since you told everyone Google just wants us to be more discreet rather than stopping us modding and people still don't believe you
[Magisk] taka2902:
All of those things, shamiko did the right thing, and i believe for this cat and mouse game, we will eventually go into the shadow of closed source to actually "win" the race.

Open source is good but eh, you know google can also see the code.
[Magisk] DIXES:
The authentication status displayed in the Play Store is a fixed value. It will not be re-checked until the app data of the Play Store itself is cleared. Therefore, in fact, that status is not of a reference nature. It would be more correct to directly use Checker to test.
[Magisk] osm0sis:
DIXES has it right, but I'd suggest using the Troubleshooting steps here (minus the reflash) to clear the cached verdicts and get it showing right everywhere for you.

GitHub - osm0sis/PlayIntegrityFork: Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props

Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props - osm0sis/PlayIntegrityFork

github.com
[Magisk] badabing2003:
Google can also analyze binaries.

It's a cat and mouse no matter how you slice it.
[Magisk] pndwal:
Spoiler content hidden.

😉 PW
[Magisk] Vision:
Yeah unfortunately.

And this days, analyze binaries, it can be done in many new ways.
[Magisk] RYZONN:
View attachment 6124951

Hello, P8 Pro with

Play Integrity Fix v16.6 Chiteroman

Zygisk - LSPosed V1.9.3_mod (7244)

Magisk with Zygisk enabled

What i need more to fix?
[Magisk] osm0sis:
Nothing at all. Live your life. 👍
[Magisk] chiteroman:
Google doesn't need to see any code. They can just obligate OEMs to disable unlocking bootloader, but they won't do it.

I told this many times, for Google, all of this, PIF, TEE, Keyboxes... It's just a game, they don't care if 4-5 advanced users have this "power", but when it becomes "one click install" like the first PIF versions (or recent PIF-Strong one) they obviously will (easily) fix everything like they did.
[Magisk] HippoMan:
UPDATE: I decided to move my response to this other thread:

https://xdaforums.com/t/discussion-...ding-cat-and-mouse-game.4425939/post-89616592
[Magisk] majorfigjam:
Well no - the 15 QPR1 betas will likely start late August , possibly even before 15 is formally released.

In any event, we should have 6 more weeks from today?
[Magisk] osm0sis:
Yep. 🤫

All A15 Pixel Beta release dates are here, btw:

Release notes | Android Developers

Release notes and known issues for the latest Android 15 builds.

developer.android.com

😶‍🌫️
[Magisk] Vision:
I think yeah. 😎

View attachment 6125101
[Magisk] SOCOM-HERO:
Is Uber now requiring Strong integrity? I cannot get it to open, instead it opens a lite basic near-web experience that is not good. Using latest PIF 16.5, HMA, Canary Magisk which is hidden. Only app on my phone with issues. I saw a Reddit post claiming Uber can't be beaten?

https://www.reddit.com/r/Magisk/comments/1e2dw2a
[Magisk] cabagekiller:
Uber or Uber driver?
[Magisk] braschlosan:
I spent nearly a year trying to get MyQ garage door application to work with a rooted phone. Today I stumbled across this thread/module and it FINALLY WORKS. Thanks to everyone involved

View attachment 6125131
[Magisk] shadowstep:
Same for me... loads a basic web experience, even though I'm passing PI (strong) as well as SN (full). Root is hidden from Uber (app in DenyList (DenyList not enforced) + Shamiko) + all root/Xposed apps hidden from it (using HMA). Running ZygiskNext as well, which is better in terms of hiding traces than Magisk's in-built Zygisk. No clue what to try next. 🤷‍♂️

EDIT: It is working now. Started working itself after a few days...
[Magisk] Vision:
What if besides all root hide, even Strong, Uber take the device info, but take and device info from DroidGuard, which we send a fake FP with PIF, and make check and see the device info are different 🤔
[Magisk] deechte:
That's very weird. This app has never given me any trouble with root.
[Magisk] sawdoctor:
When did it start? Maybe today cyber outage is affecting it and this is the only way they can get it to work
[Magisk] HippoMan:
I used to have this same problem with Uber Rider (com.ubercab), but after an Uber update around a month or two ago, it started working properly again.

I'm running Uber Rider version 4.527.10000 .

I'm running stock A13 on my Nothing 2 device, and Magisk Alpha 27004 with Zygisk.

I have DEVICE integrity.

Uber Rider is not in the Magisk DenyList.

I'm also running LSPosed 1.9.2.

I have Uber Rider selected in BootloaderSpoofer 3.8, IAmNotADeveloper 1.2.0, and Hide My Applist 3.2, all of which are installed via LSPosed. However, I'm not sure whether any of these 3 LSPosed modules actually make a difference regarding Uber Rider.

I remember reading somewhere that the behavior of Uber Rider might vary depending on the region. I'm in the New York City area. I'm using T-Mobile.
[Magisk] SOCOM-HERO:
com.ubercab (regular app)

I had a previous version that was working, but it suddenly became unsupported (I use Zygisk Detach module to stop play store updates) and I was forced to upgrade. Running old HMA in Magisk v27 did not work, upgraded to latest Shimako/HMA combo using Magisk Canary and still did not improve.
[Magisk] braschlosan:
Not everyone has the app block use because of root or unlocked bootloader but there are many threads around the internet of people with the problem and no help from support. This thread has a few other people that used safetynetfix

https://www.reddit.com/r/myq/comments/17zyh1y
[Magisk] Tatsuya94:
Ask chatgpt

No, really
[Magisk] zgfg:
Sorry for OT but this is really a 'practical' workoriund from CrowdStrike for the BSOD corp servers:

https://www.reddit.com/r/crowdstrike/comments/1e6vmkf

Even easier than the PIF Strong fix 😁
[Magisk] HippoMan:
Deleting a single file on each of probably hundreds or even thousands of computers around the world and then rebooting each of them: could take weeks.

But at least it appears to yield more consistent and reliable results than any of the PIF Strong fixes that are being considered. 😁
[Magisk] Vision:
Another great module archived 😕

GitHub - aviraxp/Zygisk-KeystoreInjection: Generate a valid certificate chain from scratch by injecting custom Keystore provider

Generate a valid certificate chain from scratch by injecting custom Keystore provider - aviraxp/Zygisk-KeystoreInjection

github.com
[Magisk] zgfg:
Before deleting (to be able to), it must be rebooted to Safe Mode or WRE

Yeah, all affected Win servers in the bunkers, with the linited physical access
[Magisk] sensui123:
Could anyone point me in the right direction on how to sign a custom rom? The lineage/CRDroid scripts doesn't seem to apply on this AOSP rom and the dev isn't a programmer and needs some help signing the rom. Thanks in advance.
[Magisk] Nergal di Cuthah:
Maybe this

Sign builds for release | Android Open Source Project

source.android.com

I'm not a devolper but looks like an answer.
[Magisk] osm0sis:
I mean.. it was basically completely built-upon and replaced by TrickyStore, so.. 🤷‍♂️

😶‍🌫️
[Magisk] pndwal:
Since the encrypted JSON response token payload received by the apps server doesn't include any device information (only the integrity and account verdicts) they can't see the spoofed values or make such a check that way...

I've mentioned before that it is surprising that big G itself doesn't (seem to) use this method to detect spoofing and invalidate verdicts however, as of course they do have the device information contained in the requested attestations on their servers. 🙃 PW
[Magisk] Vision:
True.

But unfortunately this need A12+

What happens on A10+?!

Thanks for info.

I appreciate as always.

And I learn something new.
[Magisk] chiteroman:
Working for me, maybe it checks for hardware attestation.

I have a modified system.img with private FrameworkPatch.
[Magisk] Vision:
About modified system.img

View attachment 6125347

EDIT: With private FrameworkPatch, you mean something else beyond the keybox.xml?
[Magisk] osm0sis:
10 was never supported: https://github.com/aviraxp/Zygisk-KeystoreInjection/blob/main/module/customize.sh#L5

As for why now 12 in TrickyStore? Probably limitations in the way the injection needs to be made; expected code needed for the hook or something.

😶‍🌫️
[Magisk] Vision:
Oh yeah, I tried it on A11 and told to change it from API 34 (At first had API 34) to API30, so theoretically maybe can work on A10.

Yeah, after A12+ lot change, and this is only exist on A12

TrickyStore/stub/src/main/java/android/system/keystore2 at master · 5ec1cff/TrickyStore

Contribute to 5ec1cff/TrickyStore development by creating an account on GitHub.

github.com
[Magisk] osm0sis:
30 is Android 11.

Android API Levels

A quick reference table of Android versions with SDK & API levels, version codes, codenames, cumulative usage, and more.

apilevels.com
[Magisk] Vision:
Yeah I know.

Sorry I have write wrong grammar above.

I tried it and told to change it from API 34 to API 30.

At first had API 34.

Question · Issue #2 · aviraxp/Zygisk-KeystoreInjection

Why A14+ only ? Can't this make it for A11+ ?

github.com
[Magisk] chiteroman:
It's a custom version with more hooks.
[Magisk] Vision:
That's is good.

You're lucky 🍀

You have Knowledge.
[Magisk] osm0sis:
🙃😶‍🌫️

Afterthought: Seems like an almost accurate description of Framework Patcher GO actually. 😆
[Magisk] passionicon:
Looking forward to the tutorial
[Magisk] sawdoctor:
And then Trickystore was forked by chiteroman
[Magisk] sensui123:
This is great for building otas. Anyone have similar instructions for building a full update rom while signing?
[Magisk] brunoaduarte:
Anyone been able to bypass Play Integrity with Redroid ?

I've "cloned" a real valid and certified device props into a Redroid 10 emulator, signed and etc (build.fingerprint are exactly the same.) but it's not enough.

I'm using x86_64 architecture for the emulator but the real device is an armv7 cpu, is that an issue?

What else must be done for Play Integrity to pass on a custom AOSP ROM with Redroid?

I know strong integrity won't be possible as it need a hardware key, but what about the basic integrity?
[Magisk] jakell888888888:
I would like to ask, now even if there is a valid key box, it cannot pass the stronghold? It worked fine before. After flashing the phone today, I flashed the module and it said that the power was lost.
[Magisk] osm0sis:
If you're using FP GO then you needed to disable the module before updating your ROM, then after the update is complete and rebooted, flash the module again to patch the updated ROM's files. TrickyStore doesn't have this problem so I'd recommend everyone use that at this point.
[Magisk] Vision:
Nice.

If allowed, with which method?
[Magisk] chiteroman:
Yeah, keep posting Strong screenshots here. Then cry when Google ban your keybox.
[Magisk] HippoMan:
I got the following last January via the GIMP method, and it's still giving the same results:
[Magisk] zgfg:
In that case you will see in logcat that PIF comments that some spoofs are already in place

So something is wrong on your KSU system, as if PIF module is not active
[Magisk] Lord Sithek:
Have you installed Disable Force Encryption (DFE) zip or something else that uses Magisk files? From my experience, it can break loading of modules in KSU
[Magisk] trax69:
Bootloader unlocked
[Magisk] itsmir:
Think I found a solution!! I had data decrypted with DFE-NEO. So reflashed ROM & kernel with a data format, installed the PIF and ZygiskNext modules and voila - I can add a card & no errors popping up. Haven't tried to use as yet - but this is a hige step forward :)
[Magisk] itsmir:
Reflashing without DFE-NEO and a data format solved it for me - thanks for the info!
[Magisk] chiteroman:
Users who use old xiaomi.eu roms, you can try the new pre-release and check PI: https://github.com/chiteroman/PlayIntegrityFix/releases/tag/v12.4

I don't know if it would fix Device verdict. If not and you need it, just use Stock or AOSP.
[Magisk] zgfg:
Actually, No wonder that

Disable Force Encryption​

would cause troubles with Play Integrity - amongst others, droidGuard checks for Encrypted Data
[Magisk] EuK_V:
The storage of my redmi note 9 pro (los 20) is decrypted and i don't have troubles with play integrity checks now with pif module and no problems with payments either.
[Magisk] zgfg:
Can you check in the file (textual, you can open by MiXplorer with root grant to read):

/vendor/etc/fstab.*

do you have fileencryption flag for /data, like:

userdata /data f2fs noatime,nosuid,nodev,discard,inlinecrypt,reserve_root=32768,resgid=1065,fsync_mode=nobarrier latemount,wait,check,formattable,fileencryption=aes-256-xts:aes-256-cts:v2+emmc_optimized+wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,metadata_encryption=aes-256-xts:wrappedkey_v0,quota,reservedsize=128M,sysfs_path=/sys/devices/platform/soc/1d84000.ufshc,checkpoint=fs
/dev/block/bootdevice/by-name/
[Magisk] EuK_V:
I think I don't

/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,reserve_root=32768,resgid=1065,fsync_mode=nobarrier,inlinecrypt latemount,wait,check,formattable+wrappedkey_v0,metadata_encryption=aes-256-xts:wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,reservedsize=128M,sysfs_path=/sys/devices/platform/soc/1d84000.ufshc,checkpoint=fs
[Magisk] zgfg:
Hmmm, still you do have metadata_encryption=aes-256

Documentation:

Metadata Encryption | Android Open Source Project

source.android.com

Not sure what exactly PI looks for
[Magisk] EuK_V:
I won't argue, I don't know, I just tell how things work here.

I have decrypted phone (did it mostly for nandroid backup, saved me many times after my experiments with the system) and gpay and banking apps working.
[Magisk] cangurob:
To the best of my knowledge, I didn't do any sort of forced decryption (DFE?). That said, I'm not completely sure, so if there's a way to check, please guide me.

I ran the following command:

su -c cat /vendor/etc/fstab.* | grep fileencryption

It returned:

:/ $ su -c cat /vendor/etc/fstab.* | grep fileencryption
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,background_gc=off,fsync_mode=nobarrier latemount,wait,check,fileencryption=ice,quota,formattable,reservedsize=128M
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=0,noauto_da_alloc latemount,wait,check,fileencryption=ice,wrappedkey,quota
[Magisk] Graveen:
Latest worked with Poco M4 Pro 14.0.0.5.0 TKEEUKM / october security patches

1) Magisk 26.4 (hidden)

2) Exclusion list: Play Store + GWallet

3) PIF Module (of course :p)

4) cleared PlayStore + GWallet cache & datas, then rebooted

SPIC result: MEETS_DEVICE_INTEGRITY

Many thanks.
[Magisk] nil?:
I have Pixel 6 Pro, latest stable release of the stock ROM (UP1A), latest stable release of Magisk (26.4, with Zygisk enabled), latest stable release of PIF (12.3). I installed the module but Magisk says "Zygisk module not loaded due to incompatibility".

Previously I had used Magisk 26.3 with USNF 2.4.0 MOD 1.2 (modded by Displax), and when I installed PIF for the first time and saw the error about incompatibility I thought it's about old Magisk version so I upgraded it to 26.4. But the module doesn't work with the new version.

What are requirements to successfully enable it? Are there people with stock ROM on P6P who can share me exact way to get it work?
[Magisk] pndwal:
Really? PW
[Magisk] zgfg:
It's actually opposite for me:

- v12.3, Device and Basic Integrity

- v12.4, only Basic Integrity

Xiaomi.eu v12 5/A11
[Magisk] Yusef Kifah:
View attachment 6032949

Pointed out by a fellow community member that device integrity was failing as of late. As recommended, this module passes Device Integrity again on my Nord running latest LOS. Good work!
[Magisk] nil?:
Could someone with this module working grep a Magisk log by 'playintegrityfix' and post what is there?

I have this, but I see and error "Zygisk module not loaded due to incompatibility" and SN check doesn't pass:

1429:11-15 02:57:03.706 899 899 I : playintegrityfix: exec [post-fs-data.sh]
1433:11-15 02:57:03.713 892 894 I : playintegrityfix: loading [system.prop]
1442:11-15 02:57:04.877 892 894 I : playintegrityfix: exec [service.sh]
[Magisk] ghoster76:
This version breaks Device Integrity on Mi 10 Ultra 12.0.15
[Magisk] Vision:
This program PixelFlasher is so good.

So I decided to add it to right-click menu.

View attachment 6125602
[Magisk] Vision:
This new module, go wild.

Even more devs, share their ideas, to make it even more better.

The last missing step (for me at least) is to be able to work for A10+ or at least A11+.

Thanks you for all your hard work 🙏

GitHub - 5ec1cff/TrickyStore

Contribute to 5ec1cff/TrickyStore development by creating an account on GitHub.

github.com
[Magisk] borisSweden:
Let me guess with this more advanced method, you still need a random GApps installed for any boolean value of true?
[Magisk] badabing2003:
Don't brag, I know you're running stock with locked bootloader.
[Magisk] osm0sis:
Play Integrity is part of Google Play Services.
[Magisk] TotallyAnxious:
Husky beta as been added to 16.6. Let the countdown clock begin.
[Magisk] majorfigjam:
Old-ish news, as the same print has been in the 16.6 beta for a few weeks now - before July 9 anyway.

As to the countdown, probably about 2 weeks life from now, given the underlying Husky print was released on June 18.
[Magisk] Roll3r:
I had this problem for months. What finally fixed it was whitelisting it in all ad blockers and firewalls. It's been working fine for at least a month now.
[Magisk] SOCOM-HERO:
What did you whitelist to get it working? I'm running AdAway. Disabling the filter list and/or webserver to default did not change the behavior.
[Magisk] HippoMan:
And for me, Uber Rider is working without my having disabled AdAway and without my having whitelisted anything at all.

More details here:

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89617864
[Magisk] casouzaj:
Wow! PlayIntegrityFix v16.6 (the stable one, released today on chit's GitHub) brought RCS messaging back. Hope it lasts!
[Magisk] majorfigjam:
Likely about two weeks, based on previous experience with beta prints' life expectancies (see above).