yashsingh1/xdaforums huggingface dataset:
[Magisk] rsk_kelkar:
That's a wonderful idea. Although when I tried I find most jsons have below text in all fields

"inaccessible or not found"

Edit: I downloaded the code and ran it locally on my device. Seems like the fields are ok now. The new json file also shows the correct info as per the randomly selected file.

Only I don't know now if it's applied. I have set FORCEABI="arm64-v8a,armeabi-v7a,armeabi" but on ten's attempts don't get the device integrity to pass. Something to note is while I'm checking the play integrity via Play Store it shows the build fingerprint of the original device. Is this expected?

Edit2: Got device integrity pass after a few more tries. I notice the build fingerprint when checking integrity from play store still shows my original device so I guess it's expected. One thing to note is some jsons have FIRST_API_LEVEL empty. I'm not sure if all my failed attempts had this empty but the one that finally worked is not empty ( and it is required to be not empty).

May be all jsons with empty FIRST_API_LEVEL can be removed? As they won't work anyway
[Magisk] TheFreeman193:
Sorry for the delay in getting back to you!

The collection is not curated so you can expect to need multiple tries, just as with trying random build.prop files. The information that shows up in the Play Store verdict popup will always be your real device since the PIF module only spoofs values for the backend Play Services (GMS) processes.

FIRST_API_LEVEL (DEVICE_INITIAL_SDK_INT in Java env) wasn't present in earlier versions of Android and thus isn't checked for profiles from these builds. If the value isn't set in the build properties my automation scripts leave that value blank in the JSON files they create. You can read more about the property in the AOSP docs.
[Magisk] shoey63:
@TheFreeman193

Users on @osm0sis v5 fork now have to run the included migrate script on the older style pif.jsons, such as those in your repository.

Can it be automated in ./pickaprint.sh?

For reference

#!/bin/sh

case "$1" in
install) INSTALL=1; shift;;
*) echo "custom.pif.json migration script \
\n by osm0sis @ xda-developers \n";;
esac;

item() { echo "- $@"; }
die() { [ "$INSTALL" ] || echo "\n\n! $@"; exit 1; }
grep_get_json() { grep "$1" "$DIR/custom.pif.json" | cut -d\" -f4; }
grep_check_json() { grep -q "$1" "$DIR/custom.pif.json" && [ "$(grep_get_json "$1")" ]; }

if [ -f "$1" ]; then
DIR="$1";
shift;
else
case "$0" in
*.sh) DIR="$0";;
*) DIR="$(lsof -p $$ 2>/dev/null | grep -o '/.*migrate.sh$')";;
esac;
fi;
DIR=$(dirname "$(readlink -f "$DIR")");

[ -f "$DIR/custom.pif.json" ] || die "No custom.pif.json found";

grep_check_json api_level && die "No migration required";

[ "$INSTALL" ] || item "Parsing fields ...";

FPFIELDS="BRAND PRODUCT DEVICE RELEASE ID INCREMENTAL TYPE TAGS";
ALLFIELDS="MANUFACTURER MODEL FINGERPRINT $FPFIELDS SECURITY_PATCH DEVICE_INITIAL_SDK_INT";

for FIELD in $ALLFIELDS; do
eval $FIELD=\"$(grep_get_json \"$FIELD\")\";
done;

if [ -z "$ID" ] && grep_check_json BUILD_ID; then
item 'Deprecated entry BUILD_ID found, changing to ID field and "*.build.id" property ...';
ID="$(grep_get_json BUILD_ID)";
fi;

if [ -n "$SECURITY_PATCH" ] && ! grep_check_json security_patch; then
item 'Simple entry SECURITY_PATCH found, changing to SECURITY_PATCH field and "*.security_patch" property ...';
fi;

if grep_check_json VNDK_VERSION; then
item 'Deprecated entry VNDK_VERSION found, changing to "*.vndk_version" property ...';
VNDK_VERSION="$(grep_get_json VNDK_VERSION)";
fi;

if [ -z "$DEVICE_INITIAL_SDK_INT" ] && grep_check_json FIRST_API_LEVEL; then
item 'Deprecated entry FIRST_API_LEVEL found, changing to DEVICE_INITIAL_SDK_INT field and "*api_level" property ...';
DEVICE_INITIAL_SDK_INT="$(grep_get_json FIRST_API_LEVEL)";
fi;

if [ -z "$RELEASE" -o -z "$INCREMENTAL" -o -z "$TYPE" -o -z "$TAGS" ]; then
item "Missing default fields found, deriving from FINGERPRINT ...";
IFS='/:' read F1 F2 F3 F4 F5 F6 F7 F8 <<EOF
$(grep_get_json FINGERPRINT)
EOF
i=1;
for FIELD in $FPFIELDS; do
eval [ -z "\$$FIELD" ] \&\& $FIELD=\"\$F$i\";
i=$((i+1));
done;
fi;

if [ -z "$DEVICE_INITIAL_SDK_INT" -o "$DEVICE_INITIAL_SDK_INT" = "null" ]; then
item 'Missing required DEVICE_INITIAL_SDK_INT field and "*api_level" property value found, setting to 25 ...';
DEVICE_INITIAL_SDK_INT=25;
fi;

item "Renaming old file to custom.pif.json.bak ...";
mv -f "$DIR/custom.pif.json" "$DIR/custom.pif.json.bak";

[ "$INSTALL" ] || item "Writing fields and properties to updated custom.pif.json ...";

(echo "{";
echo " // Build Fields";
for FIELD in $ALLFIELDS; do
eval echo '\ \ \ \ \"$FIELD\": \"'\$$FIELD'\",';
done;
echo -e "\n // System Properties";
echo ' "*.build.id": "'$ID'",';
echo ' "*.security_patch": "'$SECURITY_PATCH'",';
[ -z "$VNDK_VERSION" ] || echo ' "*.vndk_version": "'$VNDK_VERSION'",';
echo ' "*api_level": "'$DEVICE_INITIAL_SDK_INT'"';
echo "}") > "$DIR/custom.pif.json";

[ "$INSTALL" ] || cat "$DIR/custom.pif.json";
[Magisk] TheFreeman193:
Later today I expect to release an updated version of the pickaprint.sh script with additional features. At the same time, I'll be updating the collection to use key names compatible with the @osm0sis fork, in order to use the new features such as arbitrary prop and Java class value spoofing. The script will detect and remove these additional properties (and convert the key naming scheme) if it detects the @chiteroman module when it copies a selected profile.
[Magisk] TheFreeman193:
The v2 pickaprint.sh script is now on GitHub, along with an updated collection formatted for @osm0sis PlayIntegrityFork. The script converts profiles back to the @chiteroman format on-the-fly if you're using the original module.

Additionally, the script is now interactive, so you can reject/accept profiles after testing them to automatically build failed/confirmed lists. For this you need to execute the script locally; updated instructions are on GitHub in the README.
[Magisk] mochamoo:
I have gotten this far but stuck here. I have a somewhat basic understanding of termux. But not sure what to do now. Uninstall and try again? Best way to uninstall pickaprint? thanks

p.s. running on my pixel 7 pro

p.s.s. I removed the JSON directory to try again. After a few tries it excluded some and moved to failed and then I got this same message again.

View attachment 6052778
[Magisk] mochamoo:
Have gotten a bit further by including the alternate ABIs. I have tried the alternate ABIs and so far no luck but going to keep trying more. FYI, I am not using a beta version of any build. I'm on released Android 14

edit: went through all of them and didn't get a hit. Will deal with it more another day. In the meantime am sticking with PIF 15.1. I must be missing something.
[Magisk] TheFreeman193:
Hi there, apologies for the delayed reponse.

I see from your screenshot that you're using an old version of the script. It may be worth re-downloading and trying with the latest (v4).
[Magisk] mochamoo:
trying v4. so far no luck. I've got termux and check integrity (dev op) in split window and just going back forth check integrity / n / check int / n .
[Magisk] shoey63:
Some devices, Pixel 7/8 for example, need the PIF directory changed to arm64-v8a,armeabi-v7a,armeabi by entering this code into the terminal.

export FORCEABI="arm64-v8a,armeabi-v7a,armeabi"

Check the

The JSON file I tried doesn't work​

and

The script detects the wrong ABI list on my device​

sections in the GitHub README
[Magisk] mochamoo:
finally got a couple. I did have the forceabi set already.
[Magisk] TheFreeman193:
v4.1 of pickaprint.sh is now available on GitHub.

Additional options were added; you can see them with ./pickaprint.sh -?

Also included are some fixes to the conversion of JSON files to the chiteroman JSON format if you're using his module. This should resolve JSON read errors caused by trailing terminal commas when the last version of the script was used with some versions of the collection.

You should also note that the brief pause in stricter integrity checks over the holiday period has ended. This means a number of device profiles/fingerprints are, once again, blocked for software-backed evaluation causing failure of DEVICE_INTEGRITY.

However, the majority of profiles I previously tested and found to work in the collection on my devices are still working. A bit of persistence should merit you a working profile in most cases. Please consult the README on the main GitHub page as there is important information on what to do if you run into issues.
[Magisk] dmitro.derkach:
tried on Pixel Experience 13 on Redmi Note 11 (spes)

didn't work

any working fingerprints for Redmi Note 11?
[Magisk] badabing2003:
With which module?
[Magisk] dmitro.derkach:
this one https://github.com/chiteroman/PlayIntegrityFix
[Magisk] badabing2003:
Try with this:
[Magisk] dmitro.derkach:
works, thanks
[Magisk] shadowstep:
A suggestion: Try and avoid using white font colour. Not everyone uses a dark theme... and the white coloured font is unreadable for all such users (me included). :)
[Magisk] TheFreeman193:
Oops, I must have clicked white instead of clear formatting and I couldn't tell. Fixed!
[Magisk] Fishawy:
And I thought you intentionally used white on a white background to try and trick Big G if they ever come across this post. 🤦🏻‍♂️

Too much conspiracy theory. 😄
[Magisk] Hotdizzle:
Thank you so much for this. Worked like a charm. All I had to do is copy and paste.
[Magisk] qaz.xc:
After 20th attempt using PlayIntegrityFork with Poco F4 on crdroid latest it checked both BASIC and DEVICE integrity.

Still better than manually changing stuff.

Let's see for how long.

Had to clear play store cache & storage even after reboot to show affected apps.

Thank you very much, it's getting hard these days.
[Magisk] TheFreeman193:
Please see my response to a similar question for this.

It looks like the abuse detection sensitivity or requirements for the DEVICE verdict have increased again, and a number of profiles/fingerprints have stopped working like they did in December.

There are plenty, even in my public collection, that still pass DEVICE integrity however so this is clearly not a mass-block of publicly shared prints. It just means we need to work a little more to find working ones.
[Magisk] awtompson:
I must have tried more than 100 finger prints before I found one that worked. It took me by surprise when it passed and I almost kept going. Thanks for this. I haven't been worried about PIF since I use Google Wallet on my pixel watch but my bank sent me a new card and I had to get Wallet working on my P7Pro to add it.

Thanks again.
[Magisk] Mr. Apocalypse:
I haven't logged into XDA in years, but I dusted off my login just to come here and thank you for this. I've tried about 80 fingerprints before I found one that works on my Pixel 7 Pro.

Thanks again and keep up the great work sir!
[Magisk] dodger666:
As with Mr. Apocalypse, haven't been around much lately, but with google's recent developments, it's good to know there are people still fighting the good fight. Thanks to you, TheFreeman193, I now have 45 working fingerprints, where as yesterday I had none...

Cheers
[Magisk] Appreciative:
I noticed my in-app purchases weren't working. I'm showing certified in play store but I think I'm not if I clear cache. I'm back to 1/3 (basic) and can't find a fingerprint with PaP that works now. I tried about 40x and never got 2/3 on PI. My confirmed ones all say not working now also. Can someone force close play store (or clear cache of it) and check PI with their pickaprint prints?

anyone else having issues completing in-app purchases since late January?
[Magisk] TheFreeman193:
Could you open a terminal emulator and run:

uname -r

Some kernel release strings are now blacklisted and this causes all working prints to pass only BASIC. I've just checked and there are lots of working prints in the collection.
[Magisk] Appreciative:
Indeed I can but I solved my issue. I think I know why but maybe it was something else too. I set up a new device (op11) and for whatever reason, that invalidated my card on my op9p. I had to completely re register it as Google pay and tap to pay, then in-app purchases worked again on 9p.

For good measure, uname -r:

5.4.61-qgki-g680a0fd
[Magisk] TheFreeman193:
No worries - I'm glad to hear you got it working!

Sometimes with payment methods it'll take a few days of passing DEVICE integrity for these to work again because Pay/Wallet stores the attestation status in its own database. This could explain your experience if you've recently been failing integrity. Clearing Pay/GMS data and re-adding payment methods, as well as just waiting a few days, both usually resolve this.

For future reference, you can read the aforementioned status from a root shell with:

sqlite3 /data/data/com.google.android.gms/databases/android_pay "SELECT fails_attestation FROM Wallets"

You should get a '0' (zero) for every payment method added if all is well. You may need to install an sqlite3 instance if your ROM doesn't provide one; the Termux emulator provides one via pkg install sqlite from a non-root shell. You can then access it from a root shell at /data/data/com.termux/files/usr/bin/sqlite3.
[Magisk] Appreciative:
This is super useful info. In my telegram journey to find people having issues with in app purchases, I actually found a couple guys that had a similar problem. I will be sure to pass this info on for future people. Even if it wasn't my issue, and I'm not totally sure, it will help for sure. Thanks 👍
[Magisk] awtompson:
Woke up this morning with no passing tests, not even basic. This time it only took me 5 tries to pass device. I wonder how long this cat and mouse game will go on.
[Magisk] kevinwu128:
I've tried over 100 prints. Still not passing. Have these all been blacklisted? I'm running s20fe stock rom..

Also, I've tested the latest xiaomi print and this works fine. But trying to get a more unique one
[Magisk] TheFreeman193:
There seems to have been a large wave of blocks on software-backed integrity in recent days. I am investigating along with some other excellent minds and will report back when I know more.
[Magisk] sawdoctor:
So far I've seen one person post that their fingerprint hasn't been burnt that's it. Every other working print apart from the new xaiomi one seems to have been burnt in 1 go. Was really hoping it was a glitch in the matrix with it being a leap day yesterday and that had thrown a spanner in the works
[Magisk] amk316:
thanks for the script

but if i was google i will use it to download all fp and band them!!!

its batter to put few fp for a day or two and release new fp on the fallowing time period.
[Magisk] Nergal di Cuthah:
They don't need to they already have a database of every official rom's build.props
[Magisk] zoisa:
Hi, i used this wrong, i used without v7 fork installed, i start to say no a few FPs without pass even basic, then i realized i need V7 fork, i installed and then i pass both, i got lucky i supose :)

Then i tried use this:

You can mark the current profile (pif.json or custom.pif.json) as confirmed working using the -i argument:

./pickaprint.sh -i

But i got that:

Looking for installed PIF module...

Detected osm0sis module. Will use /data/adb/modules/playintegrityfix/custom.pif.json

Profile '/data/adb/modules/playintegrityfix/custom.pif.json' doesn't exist - can't add it to confirmed

How i can mark my FP then? Thx.
[Magisk] TheFreeman193:
As mentioned by @Nergal di Cuthah Google collects basic information from every device that uses Play Services. They have access to the device profile for every unique build of Android that's ever interacted with Google servers.

The purpose of this collection was specifically not to have thousands of people all using a single profile/fingerprint, because that sticks out like a sore thumb statistically. Even the huge wave of blocks we've seen lately, which has invalidated more than 90% of previously working prints, doesn't seem to be based on public collections like PIFS or raw dumps like tadiphone. No single collection or dump has seen the 100% coverage we would expect if it had been scraped for blocking purposes.

In any case, this latest wave of blocks is pretty devastating and I'm no longer recommending the PIFS collection for devices with the most common ABI list (arm64-v8a,armeabi-v7a,armeabi). There are no working prints in that directory anymore.
[Magisk] TheFreeman193:
This is curious. Did you run ./pickaprint.sh -i as root?

What do you get if you run these two commands:

ls -l /data/adb/modules/playintegrityfix/

cat /data/adb/modules/playintegrityfix/module.prop
[Magisk] zoisa:
Yes, first i use su, then cd for the folder, then the command, and i get:

Using busybox '/data/adb/magisk/busybox'

Looking for installed PIF module...

Detected osm0sis module. Will use /data/adb/modules/playintegrityfix/custom.pif.json

Profile '/data/adb/modules/playintegrityfix/custom.pif.json' doesn't exist - can't add it to confirmed

For the first i get:

total 43

-rw-r--r-- 1 root root 8760 2024-03-03 08:33 classes.dex

-rw-r--r-- 1 root root 1833 2024-03-03 08:33 common.sh

-rw-r--r-- 1 root root 328 2024-03-03 08:33 example.app_replace.list

-rw-r--r-- 1 root root 764 2024-03-03 08:33 example.pif.json

-rw-r--r-- 1 root root 3279 2024-03-03 08:33 migrate.sh

-rw-r--r-- 1 root root 283 2024-03-03 08:33 module.prop

-rw-r--r-- 1 root root 1497 2024-03-03 08:33 post-fs-data.sh

-rw-r--r-- 1 root root 1484 2024-03-03 08:33 service.sh

drwxr-xr-x 2 root root 3488 2024-03-03 08:33 zygisk

For the second:

id=playintegrityfix

name=Play Integrity Fork

version=v7

versionCode=70000

author=osm0sis & chiteroman @ xda-developers

description=Fix CTS profile (SafetyNet) and DEVICE verdict (Play Integrity)

updateJson=https://raw.githubusercontent.com/osm0sis/PlayIntegrityFork/main/update.json
[Magisk] zoisa:
Im using pif.json outside this folder, because i use your script before install it @TheFreeman193, right? Thats why custom.pif.json dont exist, but i thought works with pif.json and custom.pif.json reading the description. :(
[Magisk] TheFreeman193:
My script detects which PIF module you're running and copies it to the appropriate location in either /data/adb or /data/adb/modules/playintegrityfix. If you ran my script while chiteroman's module was installed, the script will have copied it to /data/adb/pif.json. You can try searching there - I don't understand how you would pass DEVICE with the osm0sis module if there was no custom.pif.json file, however.
[Magisk] zoisa:
Because i had pif.json using your script (when i used without module, your script say to me that i dont have any so it would use pif.json, and start ask if it works or no, i try 6-7 more or less without pass basic, then i remembered i uninstalled the module, i reinstall it and voila, i pass both) , so when the module dont have custom, use pif.json (at least say this in description), any of this has sense for you? I dont have knowledge. :(
[Magisk] fbirraque:
I had 20 functional saved FP and now none work anymore. The last huge wave of block was sucks!
[Magisk] TheFreeman193:
This means the script was placing the prints at /data/adb/pif.json. You may be able to find the last print tried there.

The falling back to pif.json mentioned in the osm0sis module documentation refers to /data/adb/modules/playintegrityfix/pif.json, per these lines in the source code.
[Magisk] TheFreeman193:
In light of the comprehensive blocks, I have archived the GitHub repository as of 2024-03-03.

You can find additional information at the top of the README.

Sorry folks, there's no more I can do given the current state of affairs.

In the meantime, you can try using the latest profiles from the Xiaomi.EU app project.

@osm0sis has a useful script to automate this.
[General Questions and Answers] Evostance:
I couldnt find the alt name for the Omnia so I thought I would ask in here.

The Omnia runs WinMo 6.1 much like the X1 and other devices on this forum.

Is there a way of getting TF3D onto the Omnia or did I just miss the topic?
[General Questions and Answers] invd:
Please use the Q&A Thread, "Development and Hacking" is only for contribution...
[Samsung Galaxy Tab A series Questions & Answers] ve_x0r:
Hi!

Can someone help me bypass FRP on my SM-T500? I've tried many methods found on the internet, but they are not working...

Model: SM-T500 | Samsung Galaxy Tab a7

OS	Android 10, upgradable to Android 12, One UI 4
Chipset	Qualcomm SM6115 Snapdragon 662 (11 nm)
CPU	Octa-core (4x2.0 GHz Kryo 260 Gold & 4x1.8 GHz Kryo 260 Silver)
GPU	Adreno 610
[Samsung Galaxy Tab A series Questions & Answers] mvikrant97:
Use Android Utility V124 software and then trigger a Chrome Browser using MTP mode.

Then install the apk below and factory reset the tablet.

Factory Reset APK
[Samsung Galaxy Tab A series Questions & Answers] ve_x0r:
Where to download this software? I cant find any legit link :/
[Samsung Galaxy Tab A series Questions & Answers] ve_x0r:
View attachment 6046153
[Samsung Galaxy Tab A series Questions & Answers] khollyo:
hello

i dont this will work

i have the same tab t500 and i cant find a way to unlock FRP
[Samsung Galaxy Tab A series Questions & Answers] morgenmuffel:
Am I correct in assuming for this to work I would need to be able to enable debugging on the phone:
[Samsung Galaxy Tab A series Questions & Answers] lewmur:
AFAIK the ONLY way to get it unlocked is the send it to Samsung tech support, along with legit Proof of Purchase, and have them unlock it. There are paid services that claim to do it, but I have yet to see anyone on XDA say they found one that worked.
[Samsung Galaxy Tab A series Questions & Answers] LazMike:
I can get into it and I can get into Chrome and I can download apks but it won't let Chrome install the apks
[Samsung Galaxy Tab A series Questions & Answers] Noeb:
Any update on unlocking the FRP ?????
[Samsung Galaxy Tab A series Questions & Answers] lewmur:
samfw.com claims they can unlock it. I haven't heard of anyone who tried it. If you do, please let us know the results.
[Samsung Galaxy Tab A series Questions & Answers] Noeb:
I will check it out.. That's where I'm stuck right now.
[Samsung Galaxy Tab A series Questions & Answers] tiagocristino:
Hi guys,

I wounder if someone have already tried Android Utility PRO V130?

​
[Samsung Galaxy Tab A series Questions & Answers] tiagocristino:
Did you flash it to Android 10?
[Samsung Galaxy Tab A series Questions & Answers] BigPhat99:
can confirm just used the samfw.com browser unlock tool it cost 40$ but it did it in a matter of seconds
[General Questions and Answers] Ryosuke_420:
I have a Samsung phone with OneUI 4.1 Core

i have been tying to make good lock come pre installed because oneui core dosen't have good lock compatibilities and i've been developing a rom for that

i installed HomeUp as system app via Lucky Patchers and copied the etc/permissions file from the phone and put the apk in system/priv-app

However when i try the same thing with QuickStar or NavStar they don't work . Only if i install them via Lucky Patcher .

What am i missing here ?

FIX :

i just needed to disable signature verification .
[General Questions and Answers] SheffSamsung:
Hello. We have a problem... we tried to find a way to encrypt, because many methods did not work, and we got a working one But the problem is different now, after a reboot it restores fstab.m168. Who knows how to remove file restoration?
[Google Pixel 6 Pro] Super_Pedro:
Hi guys,

I am waiting to recieve a brand new Pixel 6 pro here in Spain.

I have read in different sites and tutorials about heating and lagging issues, specially in Android 14 update. Don´t know if the unit that I bought will bring updated Android or not, actually.

If not, would you recommend to stay on Android 13 or upgrade to 14? another point is that I am not sure if A14 will carry good some modded apps that I use; and I would like to have it unrooted at least a few months, to confirm that hardware works well.

Comments, experiences and opinions will be very welcome.

Thank you in advance for your nice feedback!
[Google Pixel 6 Pro] Zaxx32:
Heating n lagging issues have been pretty much fixed. A14 is the the best release since A10 imo Battery life also better than ever too! ...plus decent feature drops on to...:cool: