yashsingh1/xdaforums huggingface dataset:
[Magisk] Depressed T.Bear:
When I run the code, I get the same result as @sga999 in post #15,161.

For completeness, I am also attaching the two files in this post so that you can take a look at them. I also have curl under /system/bin and wget under /system/xbin.

This version also works perfectly for me! Thank you very much! :)(y)

Good idea, I also installed 'Busybox for Android NDK by osm0sis' via Magisk for testing. This also makes the original version of autopif.sh work without errors!

Edit1: @sga999 Thank you very much for jumping into this topic and providing the crucial information! I really appreciate it (y)😘

@osm0sis Just so I can understand it properly, because I'd like to pass it on to the rom developer. What do you mean by "some kind of half-baked wget"? Is wget (/curl) just outdated and needs to be replaced with the current version?
[Magisk] zgfg:
Yes, Griffin got banned and he immediately updated 15.9.8 with the Clark prints built-in

Don't understand your stance about?!

Check other posts here about, remove your old pif.json and other modules that may install their outdated pif.json
[Magisk] osm0sis:
It's a wget-curl wrapper, so instead of including actual wget the ROM just has a shell script that tries to take wget command line arguments and turn them into the equivalent curl command line arguments. The problem is that it's incomplete and obviously buggy.

Your ROM's wget-curl version is here:

wget-curl/wget at 8168d986b507ec3a058050bf7aca09b69580bbbc · somasis/wget-curl

unfinished and sloppy wrapper for curl that takes wget arguments - somasis/wget-curl

github.com

Latest (still 9 years old) is here:

wget-curl/wget at master · somasis/wget-curl

unfinished and sloppy wrapper for curl that takes wget arguments - somasis/wget-curl

github.com
[Magisk] Depressed T.Bear:
Thank you very much for the information! I will pass this on accordingly, I really appreciate all your help. (y)

Just clicked 'reply to post' a few seconds after you did :D. Your new version in #223 works fine for me.

I would still like to test zipsigner, I just flashed it with Magisk. Can you please give me more instructions on how to test/use it?
[Magisk] osm0sis:
Nah, forget the zipsigner test, that was just to see if your dalvikvm would work with a different jar.

Show this to the ROM maintainers:

android_vendor_lineage

Forked from https://github.com/LineageOS/android_vendor_lineage

git.gugelfrei.de

From some random git, but it's correct.

Can you show the output of toybox on your ROM?
[Magisk] Depressed T.Bear:
Alright, deleted from my brain.

I'll pass it to them, thanks!

Attached is the output of toybox!
[Magisk] osm0sis:
Hmmm, no wget, but they still shouldn't include a broken fake one, I'd argue. They could also probably upstream their toybox to get wget instead.
[Magisk] Rom:
Hi

The module works, but it make an issue on my OnePlus device (A10):

I have the face unlock configured to unlock my device with the camera.

With this module, if i want to unlock my device, it show me a message that the camera is used by another app and so it's not available for unlocking my device.

Is this a known bug ?

Thanks
[Magisk] viniciuskmv:
Xiaomi.EU ROM. But I'm aware that it's a problem with the ROM and not the module.
[Magisk] pndwal:
So assume ROM integrates it's own spoofs for passing PI DEVICE_INTEGRITY...

You may have succes will new PIF module (depending on ROM Devs spoof implementation) if you root... If it's a 'strange' implementation like some XiaomiEU ROMs this might fail anyway...

Non rooted, yes, you'll need to wait... 😜 PW
[Magisk] osm0sis:
OnePlus/Oppo has always had issues with certain props getting reset before boot_completed breaking finger print, etc. Did any version of this mod or Displax's work for your device and not break camera? You'll need to compare the service.sh and system.prop to see if there's anything obvious different.
[Magisk] Rom:
Hi osm0sis

I have not yet tested previous versions of this module.

Previously, I used kdrag0n's Magisk module https://github.com/kdrag0n/safetynet-fix which worked and didn't break anything.

Installing this module automatically marks the kdrag0n module for deletion at the next boot, as I'm sure you already know.

I've tested the Displax module in the past, but I can't remember exactly whether it caused me problems or not on my OnePlus.

I'll compare the 2 files to see if anything looks suspicious.
[Magisk] thesingular:
Gpay does not check installed apps for root so HideMyApplist is useless against it.
[Magisk] marcopit-92:
My wallet back on track! Thanks to dev! I just wanted to say I uninstall xprivacylua and reboot just before it goes fixed. Now I don't know if it made the trick but I also waited 1 hour and 30 after the green ✅.
[Magisk] bobby8921:
I can't add one of my credit cart to wallet (I was able to add another one without issue). Could it be related to safety net or not ?

The error I get is : impossible to finish the setup for the payment without contact. An issue occured during the configuration. Please try later.

I've tried for days and different version of the module.
[Magisk] Rom:
A little bit feedback

I check on the repo of @chiteroman for his module: https://github.com/chiteroman/PlayIntegrityFix to test previous version(s), but the only one on the release page is available and no file downloadable on the first post so i can't do the test of any previous version.

About the two files, i don't see any suspicious things, but i should point out that i've never seriously discovered or made available any module designed to fix anything in SafetyNet, so i must have missed something when i browsed the Magisk module directory of the module.

I did some search and apparently this is a bug that has already been encountered on Samsung and OnePlus devices.

The bug on the Samsung side indicated with a property that the device was rooted and the user interface app (OneUI) literally disabled access to the camera, blocking access to the feature for any app wishing to use it.

Samsung's developers eventually prevented camera deactivation due to this property, via an update to their OneUI.

I haven't seen any discussion of this on OnePlus (for now).

So i restored the last module version of kdrag0n (2.4.0) and the camera access works fine again, and i disabled the new one from chiteroman until a way to fix that to be found.

And i also previously tested the v2.4.0-MOD_2.0 version of Displax which make the exactly same issue.
[Magisk] thesingular:
xprivacylua is not maintained anymore and if you want to use it only for hiding root apps from other apps, HideMyAppList does it much better.

I once tried both apps on my previous phone(Samsung A80 on Android 11) , xprivacylua failed to hide my root apps from other apps but HideMyAppList succeeded.
[Magisk] thesingular:
He removed those yesterday when he discovered they didn't work anymore. I also tried a bunch of those that day so I have those remaining on my phone still (11.0, 10.0, 9.9 and 9.8; all but 9.8 are prerelease versions if I recall right.). I can PM them to you if you want, or you can also ask @chiteroman directly, either way is fine with me.

Speaking of versions @chiteroman, 12.1 seems to be working fine with Zygisk Next(v4-0.8.1).(Either 12.0 or most likely 11.0 broke Zygisk Next but worked properly in the last Zygisk for KernelSU before it was renamed to Zygisk Next(v4-0.8.0))
[Magisk] ozyk100:
Finally

Pixel 7, latest November update on A14 and Playstore finally says that my device is certified

Thanks dev for great app.
[Magisk] Rom:
I would like to specify here that as you mention XprivacyLua, i also tested this app few months ago, and it's setup have left a folder in my /data partition which blocked my banking app, i just had to remove the folder to get my banking app working again.
[Magisk] PipPasadran:
Hi there,

Can anyone help? Running latest Magisk Alpha + shamiko 0.7.4 (189). When using and installing PIF, Google Play Services just crashes whenever I try to do anything related to it. Also, if I'm using PIF, I don't need to denylist any of the google related processes? Does this include pay/wallet?
[Magisk] i5lee8bit:
Do you have any sort of ad blocking enabled? Whether system-wide, VPN, DNS-based, pi-hole, etc - try turning them off first. I had this exact issue, like you, with 1 particular card, across both me and my wife's phones.

Turns out it must have been trying to send a request out to a blocked address. It always failed when trying to do the step with getting a confirmation code which was a big hint. Could be the problem, or maybe not and it's a long shot for you, lol.

I would also try on wifi and on cellular too, in case there's just something wrong with the Internet connection you happen to be on at the time. Turn off VPN if you're using that, etc.
[Magisk] Djtrip83:
I can confirm that it worked for Pixel 6a with Android 13, as in Device Integrity was passed.

I have not tested one of the culprit apps yet (like banking apps).

Good job on this one! Well done!
[Magisk] bakaekze:
Module works perfectly on AOSP based rom, but not on XEU. Thanks!
[Magisk] chiteroman:
v12.1 released to fix GMS crashing issues in few devices. Hope it works! 🤗
[Magisk] djnata:
I have do this and dont work. Xiaomi 13 Pro on xiaomi.eu weekly.
[Magisk] Depressed T.Bear:
I will suggest this and hope that he does it.
[Magisk] An-Unknown:
@osm0sis any way to meet strong integrity in unlock bootloader
[Magisk] Vision:
Unfortunately No, only way, all stock and relock BL.

Or you can try this:

TEE hacking

Post about hacking TEE on Android devices. I will post here some useful resources: https://github.com/chiteroman/Reprogram-TEE-on-Qualcomm-devices https://github.com/chiteroman/FrameworkPatch And leaked keyboxes...

xdaforums.com
[Magisk] rogers11:
Hello, I've tested Scripts-Only Mode on my rooted Nexus 7 with LOS 14.1, DenyList enforced. I just get basic integrity, as without PIFork.

Is it because of uname -r -> 3.4.0-lineageos-g........?
[Magisk] osm0sis:
100%. Fix that first then check again. Custom ROM mileage may vary anyway however, since they may not have all the matching necessary stock ROM values needed to pass.
[Magisk] gerikobcn:
Thanks!! Thaths the point!
[Magisk] rogers11:
Ok, thanks. I will ask, if he removes the "-lineageos" part from the string.
[Magisk] osm0sis:
You can also do it yourself, there are lots of scripts and tutorials in here for how and where to manually edit the string in the compiled kernel/boot.img.
[Magisk] rogers11:
Ok, it's raining here. Something to do now. 😀
[Magisk] An-Unknown:
Try , but hard to understand for noob like me , need video some thing more details document
[Magisk] zgfg:
Don't mind, only for 3lite hackers

Not considered for public bcs G will immediately block

Live with Device Integrity like everybody
[Magisk] Vision:
Yeah understand.

I agree with this.
[Magisk] An-Unknown:
Need because of WhatsApp when you your number was blacklist for use modded WhatsApp, the you can't install in unlock bootloader device

1. I try to fix with bootloader spooof but not working

2. When i login unblock number on same device it will login

3. When i use device with lock BL and try to login blacklist number login successful

To final answer according to my watch it's check device integrity if is basic then not good for blacklist number

( Note device is certified in play store using PIF hide all lsposed module from WhatsApp using hideMyApp lsposed module )
[Magisk] beeshyams:
I

Going by 2&3 it seems to me that the problem is your number being blocked not an integrity issue. 2 is the proof; if it was integrity related you couldn't have logged in
[Magisk] zgfg:
I've seen around about the modded WA and detections

Do you have a problem also with official WA, on the phone with unlocked BL, once your number is blacklisted?
[Magisk] snakechilds:
Hello anyone, could this play integrity technique also work with android emulator? Example bluestacks.
[Magisk] Vision:
Unfortunately No, I have try it in past with lot modify to try it to work but nothing happened.

Maybe I'm wrong and someone else know a way.
[Magisk] An-Unknown:
Ok, so why black list number login in lock bootloader device with office WhatsApp and get error to use unofficial WhatsApp in unlock bootloader device
[Magisk] zgfg:
And unlocked BL but official WhatsApp?
[Magisk] sga999:
@osm0sis, you did some great sleuthing and resolved the "fake wget" issue. But I am curious about one thing you wrote.

"The only reference I can find to that error on Google is this mention of "fake wget":"

(and then you put the link).

Which error did you Google for in order to find that reference? I must be blind and can't seem to find any of my reported errors in the link you mentioned.
[Magisk] beeshyams:
You've got a point. I didn't think of that
[Magisk] An-Unknown:
If number not blacklist login , but number was blacklist then show " unofficial WhatsApp "
[Magisk] DineshValor:
Anyone have PIF telegram group (not channel) created by @chiteroman!?

Once I was added in that group, but left many weeks ago and now I'm unable to find out same group.
[Magisk] wilsonhlacerda:
I don't know the specific case of that user, but I've read lots of others and they do did that test. And it fails.

The overall consensus now is that people that have used unofficial WhatsApp somewhere in the past (unknow period of time) were silently flagged by Meta. No matter if lately they were using official app or not the flag is there. And recently, like last month or so, Meta decided to block (not exactly ban) their number to login (only when settling up) if bootloader is unlocked. No matter if custom or untouched stock ROM, if bootloader is unlocked they are now blocked to login. If they lock bootloader then they can login with success.

That's the findings till now considering all the fail and success cases known. The truth only Meta knows. There is a thread about that here in XDA.

As soon as I saw the first cases I was concerned because in my country it is impossible to not use WhatsApp for everything everyday and I've been a custom ROM user since Android first days (WhatsApp always warn about that when login in, but nothing more than that).

But fortunately I have never tried unofficial WhatsApp apps. And last week I setup/login to WhatsApp on 2 factory reset devices with unlocked bootloader/custom ROM without problems.

It is not clear if WhatsApp is using STRONG for that or checking bootloader by itself. But for what if matters till now what it seems is that: if you have an unlocked bootloader AND have ever used unofficial WhatsApp app, then your number is currently blocked/temporarily banned to login.

By the way, some years ago, 5+ or more, can't remember exactly, WhatsApp do explicitly banned numbers that were using unofficial WhatsApp apps. I remember to see lots of cases. No matter if users were using stock or custom ROMs. People that were catch using unofficial apps, just that, were banned instantly. But that only happened during a period of time, then unofficial apps tried to avoid that or WhatsApp gave up, at least explicitly.
[Magisk] zgfg:
I asked bcs for us who never used unofficial WA, we have no problems running WA on our unlocked phones

Seems, once you're blacklisted due to using the unofficial WA, then M keeps an eye on you

I don't know if you would exclusively use official WA for months, could you get back to the circle of trust
[Magisk] Vision:
Yeah true, I had last month WA (always official), before i deleted.

Not have a single problem.

Kitsune Mask latest stable with PIF Fork v8
[Magisk] sawdoctor:
Pretty sure he closed it down and now he just has the announcement thread
[Magisk] osm0sis:
"Download all URLs given using curl, but using wget's options" from your output 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
[Magisk] sga999:
Funny that I only searched for parts of the error output that occurred due to 3 things you told me to enter. But I added that extra "wget -help" just for fun, so I didn't search for any parts of that! I know...weird decision-making.
[Magisk] Redn2000:
Has anyone else started experiencing Google Messages failing to send RCS today?
[Magisk] fbirraque:
Last Friday my Poco F3 (alioth) that is Play Integrity certified (BASIC and DEVICE) had some strange behavior when checking the Pl through the Google Play Store / Developer option as mentioned in #15.124

Today the device still certified and I didn't change any software or settings but the NFC Payments (Google Wallet) stopped working.

I suggest to check in your device before count with NFC Payments this Monday morning.

EDITED: Some reporting the same Wallet payment issue in the XiaomiEU fórum.
[Magisk] CZ.Kostra:
FP XEU Checker v2.1 - fixed minor bugs
[Magisk] bombadier:
Just tested and RCS seems to be sending/receiving, everything else pif related is working on the latest xiaomi print
[Magisk] Jirachilover:
It used to be that microG can pass safetynet but I'm not sure if microG can pass Play Integrity :x
[Magisk] pndwal:
There have been many positive reports of meeting DEVICE_INTEGRITY on microG systems with proper configuration... 🤠 PW
[Magisk] Jirachilover:
Hmmm, that's awesome. So in that case emulators should be able to do it. Used to be the common setup is microg with emulator to pass it.
[Magisk] Redn2000:
I just tested by restarting with the default fingerprint that comes with the module and now it's working again. Are they blocking custom fingerprints for more recent devices now??
[Magisk] bombadier:
If you read the thread the majority of custom prints got banned and most are using the same print as the xiaomi one, there are still custom prints that work, just not that many of them, I don't have the patience to find another custom print, this module uses that same print
[Magisk] pndwal:
I think microG users need minimal GMS support... They achieve DEVICE_INTEGRITY by configuring denylist (+ Shamiko?) to hide root from 'microG Services Core', enabling 'Device Registration' and 'SafetyNet' in microG settings etc... and there's a 'FakeStore' option (I know nothing about 😉)...

For a long time (2 years?) S/N and Play integrity functions were broken in microG, but it got fixed and worked again with the correct configuration... I know it was working as above a while back with @Displax's special USNF build for microG... I don't know what what special functions for microG @Displax implemented, if newer PIF is fully compatible or what configuration changes MicroG users may make now... @chiteroman may say... Or you could examine @Displax's open source for microG build here:

https://github.com/Displax/safetynet-fix/releases/tag/v2.4.0-MOD_1.3

🤠 PW
[Magisk] Depressed T.Bear:
So, just a small addendum @osm0sis .

I told my rom dev everything we found out. He only said three things to me briefly before breaking off the conversation: a) the wget wrapper is not 'part of' Jaguar itself, it is a part of AOSP, b) the links to wget wrapper for reference are from archived repositories which are roughly 10 years old and c) I should use another terminal o_O :sneaky:

So, I guess there won't be a fix or upstreamed toybox whatsoever.

I'm now using your busybox module for Magisk - which also solves the issue since it replaces wget. I dropped it in the past because it was detected by several apps - Kitsune canary however seems to hide it perfectly fine (y)

Thank you for all your efforts and help!
[Magisk] sga999:
@osm0sis, I discovered a problem with autopif.sh when it is renamed AND using the FX File Explorer app to run the renamed script. This is a rare case, so you may just want to ignore this.

It does NOT fail when executing the script with MiXplorer or X-Plore apps. It does NOT fail when executing in a terminal emulator on the Android device or in a command window on laptop.

You'll see that the problem with FX is when setting DIR, causing wget to fail. The lines that set DIR seem weird.

I'll attach 3 files. One shows the failure for FX, setting DIR incorrectly and resulting in a wget error.

The other 2 for terminal emulator and MiXplorer show DIR being set correctly. Subsequent wget works, but I didn't show you that. The MiXplorer one is a screenshot because I didn't see a way to put the output into a .txt file.

Obviously, I can avoid this by either not renaming autopif.sh. or not using FX to run the script.
[Magisk] osm0sis:
Classic dismissive ROM dev.

wget-curl is not AOSP, it's clearly from Lineage's vendor repo. 🙄

AOSP doesn't have wget and never has: https://chromium.googlesource.com/aosp/platform/system/core/+/upstream/shell_and_utilities/
[Magisk] osm0sis:
User error. Don't rename it. 🤦‍♂️🤷‍♂️

Running sourced in FX is dependent on it knowing its own filename. 😉: https://github.com/osm0sis/PlayIntegrityFork/blob/main/module/autopif.sh#L13
[Magisk] Vision:
A11, Kitsune Mask latest stable with PIF Forkv8.

Something strange (maybe only me).

I test some apps who need pass 2/3 to work with PIF and without.

McDonald's show me the error about security without the PIF module, but I enable again the PIF module and reboot and after open the app and still say the same error, I delete the data the same and even uninstall and reinstall it from my storage say the same, but when install it again via Google Play and open it all good, so this means even if you have backup of a apps can't work? Somehow the app take permission first via Google play when install it and not when install via backup and for that happens?! 🤔
[Magisk] zgfg:
Btw, I'm not quite sure about the wget status in ToyBox in AOSP. It seems to me it should be there

As of A11 release tag it was in Pending (not finished) commands list and looking to the code, with the barebones limited options and functionalities, with the source code from 2016:

https://android.googlesource.com/pl...s/heads/android11-release/toys/pending/wget.c

And indeed, its documented CLI options in TB Help are really minimalist compared to the linux wget MAN pages or busybox --help:

Toybox 0.8.11 command help

Till A13 Release tag wget remained in the Pending list, althoug now enhenhanced by a new co-author, with development continued in 2021:

https://android.googlesource.com/pl...s/heads/android13-release/toys/pending/wget.c

By A14 Release tag it was moved from Pending to the Net list of commands but still with missing eg -c and -T options:

toys/net/wget.c - platform/external/toybox - Git at Google

Sorry if I misunderstood something
[Magisk] osm0sis:
Ah, but wget being in toybox doesn't mean it's being built with AOSP or then exposed in /system/bin as a symlink.

My Pixel 8 Pro on latest stock doesn't even have the wget applet in its shipped toybox.
[Magisk] zgfg:
Mine Xiaomi A13 either but wget.c links above are from android googlesource

https://android.googlesource.com/platform/external/toybox/

Not from landley toybox

https://www.landley.net/toybox/

That's why I'm puzzled
[Magisk] HippoMan:
FWIW ...

I started using wget more than 20 years ago, and for a very long time, it was my "go to" file transfer utility.

But over the years, I started noticing that different OS's (mostly Unix, FreeBSD, and Linux versions) would occasionally offer a wget that didn't behave in a standard manner, or didn't behave properly in the first place ... or in some cases, wget wasn't even offered all, and I would then have to build it from source.

As I encountered these wget inconsistencies more and more over the years, I began to realize that curl is more standardized and better supported, so I started using it more and more.

With this in mind, I'm wondering if perhaps it might be useful to configure some of these scripts to move away from wget and to utilize curl more.

Just a suggestion.
[Magisk] osm0sis:
A pretty standard wget ships with busybox and therefore every root solution; no need to ship a curl binary in every architecture like playcurl does.

Only reason this issue popped up is because I let my script prefer a ROM's wget if they had it, which I presumed would have been from toybox or busybox, but we discovered this wget-curl wrapper monstrosity instead.