yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Without root the calling app should have no permissions for /bin or /xbin (BB is there) or for the BB preinstalled by Magisk as /data/adb/magisk/busybox

Hence it shouldn't be able to use.

Even more, if you put the app to DenyList, then it could not know for the mounted /bin and /xbin (with BB) but only for the plain, original ones as installed by the RON

So that is important for those using Kitsune and SuList - they must additionally whitelist eg Terminal app in SuList

Btw, otherwise think of an easy root checker:

which busybox

If BB was installed which will find and checker will know that phone was modded/rooted

But you can copy busybox to

/dara/local/tmp

chmod 755 and call like

/dara/local/tmp/busybox wget

that will execute wget from busybox, without the need for root to access /(x)bin
[Magisk] HippoMan:
Which modules of yours work and don't work?
[Magisk] aliantonio:
Listed here
[Magisk] pr3dicament:
I literally cannot find the mp4 -- I've been pointed in 50 different directions here.. I looked in the OP and there's a FAQ, but that's all.

Do I use pickaprint? I cannot find where you guys are finding this..could you please point us in the right direction to watch this video? I've been looking all over this thread... it's driving me nuts.

Right now I'm using PlayIntegrityFork + playcurl10.6 and it deleted the prebuilt pif.json when I ran fp. I have a screenshot of the installation and a Magisk installation log if anyone thinks it'd be necessary to see.
[Magisk] D€INOS:
[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms]

osm0sis' Odds and Ends -- Misc./Batch Tools, Flashable Zips, Scripts, etc. General Information In a nutshell, I just wanted a single thread to gather links to some of my other, larger projects, but also serve as a spot I could put some smaller...

xdaforums.com

But as osm0sis said, it's such a great post so it should have its own thread
[Magisk] pr3dicament:
It's great. yes. I just looked at that now (page 191). My question is.. where is that .mp4 that people are talking about?

You could say I'm noob-ish.. I run linux as a daily driver and most of these seem to be bash scripts. I have been trying everything that I could find, but people keep talking about a .mp4 to watch and it isn't in that thread. I need a little bit of help. I understand the stuff, I just need a LITTLE bit of guidance. I've been doing my due diligence, trying to find anything and everything but I haven't, or I'd have found that .mp4. It'd lkely be much more helpful (I'm a visual type) -- I'm even looking at "pickaprint.sh" on github but that's been archived since March. I think I need the video and the instructions that people keep talking about, yet I can't find it. I've seen so many links and been pointed in so many directions that I am starting to get a little frustrated. I think the .mp4 + the directions mentioned would help a lot. I've combed through this and maybe I just didn't see the right post or the right link, but I'm probably gonna need the video.

I can follow instructions very well, or so I've been told. Could you please help us all out? Some don't understand.. it's not about that for me.. I just want to look at this video so I can see what to do.
[Magisk] D€INOS:
View attachment 6113489
[Magisk] pr3dicament:
That's not a link, it's a picture... could you please show an actual link? It would be so helpful. Many of us would be grateful, I'm sure.
[Magisk] markdewet:
[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms]

osm0sis' Odds and Ends -- Misc./Batch Tools, Flashable Zips, Scripts, etc. General Information In a nutshell, I just wanted a single thread to gather links to some of my other, larger projects, but also serve as a spot I could put some smaller...

xdaforums.com

It's at the VERY bottom of the post
[Magisk] D€INOS:
107.35 MB file on MEGA

mega.nz

I mean it was literally from the post you yourself linked earlier.
[Magisk] zgfg:
In that post, there is the link to Mega (good that I didn't cleaned the house)
[Magisk] iSoyer:
Looks like I'm either an i***t or google really put an effort this time. I'm running raphael with SuperiorOS (A13) on newest version of BoolX kernel. Since my wallet stopped working yesterday (phone wasn't rooted, no Magisk installed) I've started digging and today finally installed Magisk with your module, hoping that it would work.

Sadly it didn't, so just to recap what I did step-by-step:

Installed Magisk 26.4

Installed PIF 12.2

Restarted phone

Enabled zygisk

Hid Magisk app

Turned on airplane mode

Cleared data and cache for Google Play Services, Google Play Store and Google Wallet

Restarted once again, this time to recovery for cache/dalvik wipe

Booted into OS

Turned off airplane mode

And all for nuffin, so afterwards I decided to add aforementioned apps to deny list and performed rest of the steps once again, to no avail.

Lemme know if I'm doing something wrong or if you'd need some logs (gonna need a quick manual as I'm not as proficient with Android and shell as I used to be those 10 years ago).

edit 1: I also tried that with MagiskHide module but that didn't work either

edit 2: I don't have Shamiko installed, dunno whether it's needed or not.

edit 3: SELinux is enforcing
[Magisk] tasar:
@iSoyer, Make exactly all steps but no change (Poco F3 with Xiaomi.eu Rom 14.0.7.0), safetynet all fail, Play integrity API checker: all red, and playstore not certified :( Wallet noticed system changes (root)
[Magisk] Difusal:
Today, Google Wallet started working again. Even though the "Your phone doesn't meet the security requirements" warning was still there, I tried tapping to pay and it worked. After that, the warning went away. I am using the 12.1 fix. Thank you!
[Magisk] chiteroman:
Are you using Xiaomi.eu ?
[Magisk] koshakm5:
thanks to your latest update I was able to pass the Device integrity
[Magisk] stathis95194:
Yeap.

xiaomi.eu_multi_NUWA_V14.0.23.9.18.DEV_v14-13

Just realized going back through the messages that it's a ROM issue. I will wait for the Devs to come up with a fix
[Magisk] chiteroman:
Read OP...
[Magisk] sanangel:
Working for me, Pixel 6a
[Magisk] 93ae8074:
¡Gracies, nin! Funciona bien nel KernelSU con ZygiskNext.

--

Thanks, mate! Works fine on KernelSU and ZygiskNext.
[Magisk] tasar:
Sorry, youre right . So i installed latest Global Stock Rom but the same :( Is it the open bootloader that makes the problems?
[Magisk] invy55:
Can you pay with Google tap to pay? I can't even if yasnac says I meet basic integrity...
[Magisk] Homeboy76:
Did you hide the Play Store and Google Pay apps, then clear the Google Play Store and Google Pay cache and data and reboot?
[Magisk] chiteroman:
v12.2 should be final build by the moment, check it:

Release v16.5 · chiteroman/PlayIntegrityFix

Update hook framework: Dobby Fix Device not passing in few devices Improve code Reduce Zygisk libs size

github.com
[Magisk] titomax82:
I don't think that Xiaomi "EU" stock rom is a problem when it's rooted.

I solved the problem in this way (a mix of several forums):

1) Latest Magisk (normal) v26.4 with:

- Options: Zygisk enabled and Hide Magisk app

- No google apps or services in the deny list (only banking and other personal apps)

- Modules: Systemless Hosts (Magisk included) and Play Integrity Fix v12.1 by chiteroman

2) Airplane mode and then manually set date 10 days ahead in the future (to force google's various checks when online again)

3) Force close and clear all (cache+data) of Google's: Play Services, Play Store, Services Framework, Wallet

(clearing wallet data obviously means to add cards again)

4) Reboot

5) Open Wallet and enable again connections and NFC as requested

6) Set date to the right values

With these steps, all working again and PlayIntegrityChecker giving the first 2 flags green (in these days google feels this great amount of checks as an "attack" and my not work, but no matter.

Let me know :D
[Magisk] tasar:
The crew from Xiaomi.eu uploaded new versionen of latest stable and the problem is fixed :) Many new devices uploaded but not all at the moment and only on sourceforge.

My F3 is now certified again, wallet work and integrity checker shows both entries ok , device and basic, strong is red.
[Magisk] cangurob:
Is Magisk necessary for this to work?

I'm running a ROM that has KernelSU built in, so thought I'd go that route....

I'm running zygisknext, with latest PIF, and still fail device integrity.

I've tried installing the latest Shamiko - however I can't find any way of configuring it (I can't access the magisk denylist, not having magisk installed!).

Wondering if I just need to roll it all back, and try going down the magisk route instead...

That would be a shame, as the kernelsu option was so easy to implement (just didn't work...)!

Happy to do more testing / provide more information if it will help work out kernelsu solution better!
[Magisk] gpvecchi:
Update feature of the module in Magisk app is usually broken...
[Magisk] djnata:
What is the link for the new versions?
[Magisk] simplepinoi177:
it's become apparent that this module has been a GODSEND since Google changed things the last 36-48 hours.....
[Magisk] immortalwon:
Yes, but it should scare people why / how aggressive Google is being toward the modding community and security in general. Where will this lead?
[Magisk] zgfg:
And if you click to that 'picture' ?!
[Magisk] pr3dicament:
If you click on the picture, it shows a picture. They pointed me to the video, it was in the middle of the thread and I simply missed it. My eyes are so tired. Been up awhile now.

Thank you so much.
[Magisk] pr3dicament:
Thank you.. so, so much. My eyes are very tired. I haven't slept in almost 72 hours now, I really have been going at this. I appreciate this very much.

Everyone just go there and enjoy, That link he posted is the EXACT post. Don't scroll to the bottom. It's post #3,752 in the linked thread. :)
[Magisk] markdewet:
You are so welcome, I do feel your strain, I am also battling, however, I have given up asking any questions as you either keep getting told to "search" for this or that (when one does not even know WHAT to search for!!) or are spoken to as if you are a fellow experienced developer, not a new person just starting out, using terms that make no sense in isolation and no explanation as to what these terms actually mean, or (my favorite!!) you are grown up, no need to be spoon-fed. Now I just follow the threads and posts and hopefully pick up some crumbs.
[Magisk] zgfg:
Don't hack the phone when tired. I bricked my phones couple of times, and ALWAYS very late in the nights. Always by forgetting or overlooking some small detail that I would otherwise well know and take care about

The script and video cannot brick the phone but anyway
[Magisk] pr3dicament:
I'm aware. I was just doing the reading and couldn't find it. I did technically find it.. I just missed the post, that simple really.
[Magisk] markdewet:
Apologies for the incorrect wording, I meant at the bottom of THAT SPECIFIC post #. Not sure how else to word it.
[Magisk] pr3dicament:
Oh please, it's okay, you said at the bottom, it was close to the bottom... just happens to be in the middle.. plus now the link is right at the correct post.
[Magisk] pr3dicament:
This is something a lot of these users deal with. You do have to understand, though, that the developers don't think that way. They think if you read everything that you will understand it to a T, like they do. It's hard to see it from that perspective, however, I've been here a long time and I can tell you that htey feel underappreciated as well. They write so many guides for us and try to help so much and they do get *****ed at a lot and a lot of people don't understand what they're saying, so it really pisses them off, therefore other developers feel the same and they're answering the same questions over and over with the same information and they just can't stand doing that after awhile.. developers spend a lot of time to get this stuff to work, so, I understand their frustration as well.

Some of us aren't developers, like myself, but I actually am related to a developer, a very high-end one.. and I can tell you that he's always feeling unappreciated. However, he gives the worst explanations possible.. that's also an issue, many of the developers either don't know how to respond to the average user attempting to use custom roms, and they usually do have a short fuse, as I eluded to earlier.

That being said, I understand your frustration. It happens to me too. They've told me "I'm not holding your hand" and i mean they do that with Arch Linux support, it's very similar.. they get mad if you don't read up. It is what it is. Everyone has to look a little more. Since I quoted the correct post-- after you showed me, they did too. It just so happens that you got to it first lol.

My point is: read up if you can, and if you find the correct post, always share it.. but see, if I hadn't quoted the correct post, I do not think they would have helped. See, you helped me and many others.
[Magisk] Iridule:
Notice many have issues with RCS. I haven't kept up with newer methods others seem to be using but shamiko, denylist enforcement, systemless hosts, hide Magisk (on delta version) with PIF module seems to work for me in lineage 20.
[Magisk] zgfg:
Developers also cannot spot some problems 'obvious' to the first time users. In commercial development, the apps must be given to non-developers to test. And after a while, you must rotate and take the new testers who are not familiar

That's a nightmare for developers but they are paid to collaborate with those 'stupid' testers Only that testers would dare to click something that developer (specially the one who wrote that) would never think about and find a trouble And they would find that the app is ugly, not intuitive, etc (once you become too familiar with, you also start thinking that the look and feel is just fine and that changes or improvements are not necessary)

However, for this community development things are different. Somebody spends wees, months and more of his private life and give things for free, then you have wannabies who are lazy to spend 30 minutes or half a day to carefully read something and try to understand, and bother by questions that waste the time and make the threads even worse and more clumsy (to find something, you have to scroll through the tens of pages with ever repeating the same Q&A)

Btw, back in 2016-17 when I started to seriously mod the phone (before that I did root couple of phones back in 2014 by King root, even flashed a custom ROM to the tablet), I silently monitored threads about unlocking Bootloader, ADB/Fastboot, TWRP, Magisk (all totally new stuff for me) for almost two months before I posed the first questions - by that time I already unlocked BL, flashed TWRP and custom ROM, flashed by TWRP all required tweaks for that ROM, installed Magisk, etc

I simply did not need to ask earlier because I was able to find everything in the OP posts and daily discussions. And I felt stupid to ask or comment something that would be obvious to the 'old' guys there

However, at that time Search in XDA (I also subscribed and read a Russian, German and Spain forums by use of Chrome and Translate) -something that unfortunately cannot be confirmed for this 'new' XDA

But similarly, we have to be thankful for what we have [the forum], moderators and old-time users will know what I mean
[Magisk] pr3dicament:
Like I said.. they feel unappreciated.

Regarding how you mentioned you got into it.. same here. I did the same thing. You'll see SOME posts from me on the forums but not many at all and I started modding in 2011. This was the first place I went to, actually. I am very thankful for their efforts, because it takes a LOT of resources and a LOT of time. Like I said, I am related to a developer lol. A very high-end one, higher-end then android, I can say that much, but that's actually all I'm allowed to say. Yeah, I'm actually being serious btw.
[Magisk] pr3dicament:
I have the scripts in my PIF folder, but I made a Testing folder and have no clue what dedyn is. I looked and there's no github or anything for it, searched xda and there were four posts, all in this thread.. what do I do here? I don't know where this collection is.. I honestly am trying to follow instructions here but don't know where this dedyn collection is located. I posted this in that thread as well. I can't find anything anywhere about it so I imagine it's something I just have to know.. I can't find any dedyn collection..
[Magisk] coconutxyz:
I'm out of the loop for a while, so the thing is I will need root to even pass basic integrity now using aosp rom?

I remember all is fine last time if I stay unrooted with custom rom
[Magisk] JEANRIVERA:
You can ask the ROM developer to sign the ROM, and you should be good without root
[Magisk] coconutxyz:
From what I gathered everyone using the rom will be sharing the same key right?
[Magisk] pr3dicament:
So from what I gathered, the collection is gone. So I can't even do this. Why would one point me here if it's not available anymore... ?
[Magisk] pr3dicament:
You won't have RCS either, but yeah.
[Magisk] pr3dicament:
Thank you
[Magisk] wfred:
You can't “create a print”. You have to find a working one. When someone says they are using a private print in PIF they mean a different print than the one the general public uses.
[Magisk] pr3dicament:
People have answered this enough, no need to pile on.
[Magisk] wfred:
Sorry, not piling on. Those other replies came before I read the post I replied to.

But before you continue - what is your goal? What are you trying to achieve? Google Pay, RCS, or both?
[Magisk] pr3dicament:
don't care for google pay as i don't use it. i dont use google for hardly anything at all. RCS, yes, that's what my main goal is since this POS doesnt have the right DRM like my other OnePlus 8T that did a crashdump, i can't get that into EDL. even tried shorting it. Got it once with a paperclip but then it got all scratched up after trying multiple times. I was impatient and didn't use a wire like I should have.

Anyway, my "new" oneplus 8T (same model btw, KB2005) doesnt pass DRM unless the boot loader is locked. It wasn't like this with custom roms on my other 8T and it died only, say, a month ago now.. so now I just want RCS working, it's very important to me.
[Magisk] Thebear j koss:
Sounds like you need a better quality phone more than anything else. I don't know about the 1+8T but they are either cheap POS, or you just a phone destroyer. Lol.
[Magisk] pr3dicament:
I don't have much money. That's why. It's the best phone I bought in 2020, i had to get a quick one a month ago and it is a cheap POS, less than 200 bucks but that's not the point here..
[Magisk] pr3dicament:
I've had the same phone for years.. hardly a "phone destroyer" at all. I try to fix them and I do successfully, both hardware and software.. but I'm no genius. I don't do development.
[Magisk] pr3dicament:
My 6T is still running strong. It's been six years with that one.
[Magisk] tom1807:
To which Zygisk Detach do you refer?

I installed this version which seems to be very reliable and detaching an app from the PlayStore.

I previously used another version (don't recall from where) but that didn't work at all.

Cheers

Tom
[Magisk] pndwal:
The RCS issue for PIF users seems to be that compatibility is determined by fingerprint(and other?) property(s) and for some obscure reason Google is checking this identifier via DroidGuard (even though not requiring PI DEVICE_INTEGRITY verdict)... Likely it's a server end check with last DroidGuard data for PI or S/N calls cached, but could also be getting it on device via GMS somehow.

This means that generally a compliant device's native props work fine for RCS (and there's no extra security layer here at all!)... However, because we spoof a print for DroidGuard and PI with PIF, functions that normally work with no changes can be broken as @kdrag0n predicted, and RCS is one casualty we are now aware of...

@kdrag0n actually introduced a mechanism (spent months working on it in fact) for USNF to avoid this very issue with "Dynamically patch build fingerprint in GMS process" which will "unpatch" after that process ends, but unfortunately @Displax found unfixed issues that may affect some devices with it (USNF 2.4.0), and rather than tackle the issue he simply took the pragmatic(?) approach and disabled the "unpatch" function. Next, @chiteroman forked a @Displax build with unpatch disabled for PIF, and the rest is history...

I put details in these 3 posts about how @kdrag0n's "Dynamically patch build fingerprint in GMS process" could fix the RCS w/ PIF compatibility issues (ie. how we could have both RCS as well as PIF, contactless, banks etc working without the need for private prints that don't block RCS for PIF spoofing) whether Google uses a server end check with cached DroidGuard data or gets it on device via GMS:

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

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

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

Unfortunately this hasn't been taken seriously so far. But we still have the RCS/PIF conflict, and I don't really have the time or energy to keep arguing about the merits of the "Dynamically patch build fingerprint in GMS process" with "unpatch" commit...

@chiteroman, maybe you could you take a look at this and consider the possibility of reverting @Displax's Do not unpatch changes commit to fix RCS?... (There may be issues with it needing further fixes for some devices of course.)

In guessing that this may be all we need (assuming RCS gets DroidGuard data on device via GMS), but if it's a server end check for cached DroidGuard data (from PI calls), my initial idea for modding PIF to do a second call itself should work (ie. first, the dynamic prop/field spoofing occurs immediately on app call detected, next, have PIF make it's own 'fake' call with stock prop/field set immediately afterward to reset server side caches).

Thanks, 🤠 PW

Lets Make PIF great again!
[Magisk] neonblind:
So, G did it again and blacklisted sailfish for A8, 8.1 and maybe (can't test) A9 devices like they did before with griffin. A10+ seems to be okay for now but that was the first indicator banning the print completely.

Does anyone running these old Android versions tested "scripts-only-mode for Android <10 ROMs" with fork v9 and got device integrity back?
[Magisk] JEANRIVERA:
if I understand right, if someone is able to make lets say a module that can revert the props and/or fingerprint back to stock exclusively for messages app, in theory we could achieve both RCS & PIF,

or another alternative make a PIF module integration that blocks messages app from reading the modified props from the PIF module.

just brainstorming......
[Magisk] Vision:
Probably, and for only basic you can just add to DenyList or MagiskHide the com.google.android.gms/com.google.android.gms.unstable
[Magisk] pndwal:
To be clear, unless it's OnePlus etc with broken keymaster implementation ("broken TEE"), scripts-only-mode is

actually for devices launched with Android <8

running any version of Android [but Android 10 + has been noted to break the fix on some devices; your mileage may vary.]... If launched with A8+ and OEM implemented hardware backed (Keymaster Hal 3+) keystore properly, your ROM (running) version simply won't help even if "<10"!... You won't ever pass DEVICE_INTEGRITY with scripts-only mode!

Launch version is key; running version isn't. 👀 PW
[Magisk] virbus:
unzip -l /system/etc/security/otacerts.zip

testkey.x509.pem, lineage.x509.pem

uname -r

4.14.329-VantomSyndra

I use magisk hide and zygisk running with denylist added google wallet

thank you google pay works on custom rom project elixir 4.1 a14 magisk 27.0 Mi 9t/k20
[Magisk] coconutxyz:
oh so root is still needed
[Magisk] Vision:
Is on the game, if Google continue this game as I read with custom Rom 😂🤣
[Magisk] coconutxyz:
yea, tired of this tbh

if they look for unlocked bootloader then it's game over