yashsingh1/xdaforums huggingface dataset:
[Magisk] zfk110:
"I'm currently using Havoc-OS-v4.19-20231012-judypn-Unofficial-GApps.zip on my LG V40, and I previously passed the SafetyNet check without any problems by using safetynet-fix-v2.4.0-MOD_1.2.zip. However, for the past two days, I've been failing the SafetyNet check. I upgraded to safetynet-fix-v2.4.0-MOD_2.0.zip, but I'm still failing the CTS profile check. I also attempted using this module, but it didn't resolve the issue. Unfortunately, I couldn't find information about adding a fingerprint when reading the OP (original post). Any assistance with resolving the CTS failure or adding a fingerprint would be appreciated."
[Magisk] Flr Power:
Did you ever think about changing your username to ARM_x_xx?
[Magisk] intel_core_i7:
Well i have a laptop with an i7 so that's the result.

If I change my username after an ARM CPU then it would be Qualcomm Snapdragon XXX
[Magisk] Nergal di Cuthah:
1) safetynet is depreciated and safetynetfix hasn't worked since november (maybe even october).

2) pif is the way to go. YASNAC is nigh useless. You need a play integrity checker (there's one built into playstore (you must invoke PLAYSTORE developer mode to get it)

3) read this https://xdaforums.com/t/pif-faq.4653307//unread

And this

How to search & find your own fingerprints [noob friendly]: A Comprehensive Guide w/ tips & Discussion for Complete Noobs (from one)

It seems Google has banned more than 95% of custom fingerprints, so this thread/guide has kind been laid to the wayside. But it's still a great resource to understanding the foundations of fingerprints and all that... This is for any/all utterly...

xdaforums.com

4) if you have a pc/linux/mac(?) and a phone that supports fastboot Pixel Flasher makes this much easier
[Magisk] zfk110:
I used this and it is passing now, Thanks

PlayIntegrityNEXT/Fp_Downloader.apk to use with play integrity by chiteroman at main · daboynb/PlayIntegrityNEXT

Contribute to daboynb/PlayIntegrityNEXT development by creating an account on GitHub.

github.com
[Magisk] Flr Power:
I was going to say, where have you been all this time. Did you just get out of jail or something 😳
[Magisk] Bladius:
the method (placurl + fp_downloader) above does not work for Redmi Note 10. Additionally, the fp command is not recognized in Termux
[Magisk] Umgak:
You will need to use su before fp will work. The script isn't in Termux's data directory, but in /system/bin where it is not accessible by default.

Not that I recommend the PINext method anyway - getting your own print or even finding one via PIFS will make you much more resistant to Google banwaves. See the FAQ, How to search for fingerprints guide, and the PIFS thread for more info.
[Magisk] Nergal di Cuthah:
What method above?

Whay do you mean "doesn't work"?

What fp command in termux?

Please be more clear and verbose in your issue or it will be impossible for someone to help you.
[Magisk] pulpf:
my posts are not reproaches

Everyone has a life and that's normal, but it's hard to find your way around the length of this forum if you haven't been there from the start.

It was to avoid the annoyance of repetitive questions that would undoubtedly be reduced
[Magisk] pndwal:
[An answer that will hopefully help those trying to get an overall perspective and see the big picture, but one that will no doubt be unpopular with many modders here.

So if anyone simply wants their ears tickled, please don't click below. 🙃 ]

Spoiler content hidden.

Spoiler content hidden.

Hope the WOT above gives some insight and may broaden perspectives, 🤠 PW.
[Magisk] YMatrix:
Hey,

I'm running 15.2 with my custom FP without issues - should I upgrade to 15.4?

If yes, I didn't understand the new line in the pif about the kernel?
[Magisk] xcl1pse:
Why you need an update if there's no problem occur from your device. The kernel thingy in latest PIF doesn't work so you can ignore that.

Meanwhile me who still enjoy using older release lol
[Magisk] V0latyle:
If it ain't broke don't fix it.

That being said...You should upgrade to PiFork.
[Magisk] EuK_V:
I probably have a similar situation with one of my phones. Is there a way to decompress boot.img and then compress it back after the changes?
[Magisk] chiteroman:
Use magiskboot: https://topjohnwu.github.io/Magisk/tools.html#magiskboot
[Magisk] boualemdz:
Help please
[Magisk] osm0sis:
Tu as besoin de trouver une fingerprint que marcher.

Si tu as d'autres questions, nous parlons seulment en anglais ici.

---

You need to find a fingerprint that works.

If you have other questions, we only speak in English here.
[Magisk] EuK_V:
Is it possible that boot.img does not contain kernel release strings at all? Can't find anything.

I was able to edit boot.img of my other phone (replacing 'lineage' word) successfuly. Passing device now. But not with this one...
[Magisk] YMatrix:
You mean the pif fork by @osm0sis ?
[Magisk] V0latyle:
Yep.
[Magisk] rat7lol:
Don't think so? It's possible that your first boot.img is compressed. Have you checked uname -r and if it contains a banned string? Perhaps something else is wrong with your configuration
[Magisk] Veiranx:
I know you and others might get tired of seeing us newbies asking the same already-answered questions. Thank you for your patience! You and the others who help out are the real MVPs!

As a side note to the design of these forums, it'd be great if there was a 'sticky' function for certain posts within threads so we all could have a place to go to for these repeat questions. I'll have to look around to see if we have a suggestions area on XDA!
[Magisk] EuK_V:
Outcome of uname -a does contain banned "lineage" word:

4.14.190-lineage-ga174265aae #1 SMP PREEMPT Fri Dec 15 17:22:48 CET 2023 aarch64 Toybox

I unpacked boot.img and still can't find anything. Strange..
[Magisk] V0latyle:
There is...Sort of.

Right side of the page, you'll see the top liked posts within this thread.

@osm0sis created an excellent FAQ too....
[Magisk] osm0sis:
Did you unpack it in magiskboot so that any kernel compression was also handed? You possibly wouldn't be able to see any strings if it's compressed still. I think there are some kernels that just don't have any strings in plain text also.
[Magisk] immortalwon:
We need a new P.I.F update for the latest unpublished changes of kernelsu. The new KSU moves all modules to modules.img and prevents modifications. How do we update play integrity fix for this?
[Magisk] osm0sis:
They already were and always have been in a modules.img (and modules_update.img) on KernelSU and APatch because they use overlayfs. KernelSU's app handles installing all standard modules (which PIF is) just fine.
[Magisk] Sheist!:
Shocked. (but pleasantly) Huzzah! :cool:

The playcurl + PIF 15.4 works. DEVICE passing sticks after reboot.
[Magisk] zfk110:
"don't fix if it's not broken" it was working for me 'till three days ago! :cowboy:

:cowboy::cowboy:
[Magisk] CZ.Kostra:
I was in a creative mood, so I modified the "FP Changer" for Tasker a bit:

1. random or gradually selection

2. will migrate FP for PIFork v5+

Maybe someone will use this task.
[Magisk] EuK_V:
Thanks @chiteroman @osm0sis @rat7lol for your comments and assistance.

I finally managed to edit lineage kernel on my samsung device. My issues were as mentioned due to compression.

Passing device with original kernel now!
[Magisk] immortalwon:
Disregard I said this, it's working now. I had to wipe the modules.img and start over. Works good now.
[Magisk] Terminator.J:
Whew, thanks for the heads-up, boss!

I'm on it!
[Magisk] TotallyAnxious:
And today I learned donkeys have floppy members. Thanks Wikipedia!
[Magisk] Wolfcity:
Maybe sometimes erected members?

Anyway, I like the new name !:cool:
[Magisk] maniacbb:
Google makes the reworking process difficult for us all the time. I've tried several methods but I can't get through this verification process and pass(meets_device_integrity and meets_basic_integrity)

I using this method GeneratePIF where I have to search for files myself. My question is do I have to "Enforce DenyList" option enabled in magisk and "Configure DenyList" mark the Play Store and Google Play services so that the magisk doesn't see them?

Or maby it enough just to select the "Zygisk" option alone? In addition, I also have, hidden magisk apk(renamed) and installed such modules as "Play Integrity Fix" "playcurl" and "Systemless Host"

I have the same result with this method PlayIntegrityNEXT(not working)

Although I read that since 25.01 google again made an update and detects kernel names(system I don't know what to call it)

I wonder if it could just be the fault of the system name itself that I am using? It is LineageOS. If so, should I ask "guardian of my device" to change the name of (system kernel?) they create? I know that they do not automatically hide root . However, it might be worth asking? I have a POCO F3
[Magisk] WhoIsJohnGalt1979:
Not needed. Enable Zygisk and use the latest Shamiko. Please do not have any google component in the Deny list.
[Magisk] trevtdogg:
yes this is most likely the problem. see the previous discussions here over the last few pages for details of how to fix - basically either renaming the kernel or using a different kernel.
[Magisk] Nergal di Cuthah:
Rather, editting (and possibly recompressing) the code of the kernel to remove vanity names from the version code.

Sorry "renaming" it sounds like all they have to do is call it another filename.
[Magisk] HippoMan:
Yes. It's important to the Googlefrinchians that kernel developers have humble personalities and don't exhibit any vanity when deciding how to name their kernels.

If I ever develop a kernel, I'd never choose a vanity name like "LineageOS", and instead, I'd choose an extremely humble name like "HippoKernel".
[Magisk] osm0sis:
...

# credits to chiteroman and osm0sis
# This script needs v15.2 play integrity fix by chiteroman
# https://github.com/chiteroman/PlayIntegrityFix/releases/download/v15.2/PlayIntegrityFix_v15.2.zip
# script modified by x1337cn

What the f*ck. chiteroman has nothing to do with my script. And x1337cn basically did nothing at all to it except move the pif file, add `killall com.google.android.gms.unstable` and rename it? He didn't even force the deprecated fields to properly support chiteroman's format. Just useless. :mad:

Don't use that trash. Use my original script, and anybody that's used a file explorer app can figure out how to move a file and force stop Google Play Services...
[Magisk] Nergal di Cuthah:
Morally, whether right or wrong good or 'don't be evil', it's what the Googlefrinchians are doing.

Maybe but ...first I've heard this advice to use specifically Chinese devices rather than "don't use known brands and phones" pretty sure zte and oppo are big enough that they have their share of bans. Am i wrong?
[Magisk] HippoMan:
Yes, I understand. Once a Telephone Sanitizer, always a Telephone Sanitizer.
[Magisk] Umgak:
Lots of working props, from both Chinese and not Chinese brands. Most public FW dumps only have like 1 or 2 versions, those are the first ones people find when people Google firmware dumps and are the first ones to be restricted. However, you can use ANY firmware version from eligible phones. Look on xda sections for phones that should be eligible (pre-9 but upgradable to 9+) for repos of flashable images, download them all, dump them (tools vary based on ROM format, I've been mostly working on sparse images which use sdat2img), test with Pixel Flasher. If you know how to write scripts you can automate everything with bash/powershell/python.

I wouldn't say "use Chinese phones" or "don't use popular phones" are accurate. I'd rather say, "cast a wide net" - check open betas, old versions, new versions, everything. All of my dumps so far are from the same phone - and it's a OnePlus, which are super popular, but only 40% were restricted.
[Magisk] sawdoctor:
You'd like to think so but judging by some of the comments/post's in this thread I'm not certain some users even know what a file explorer is let alone Google Play Services
[Magisk] TotallyAnxious:
Why does Google have play services? Are they targeting children?
[Magisk] Nergal di Cuthah:
Without a websearch this requires a user to know what phones fall in that range. However once a model is found xda is a good place to search for stock ROMs that's what i finally did and (after a few dead fileshare links) i found one uploaded to xda that worked perfect
[Magisk] glennza:
I seem to have lost Device Integrity on my tablet. Was previously working with Play Integrity Fork 7 but just started failing I have tried many (50?) fingerprints using Pixelflasher and Freeman193 but only get Basic Integrity.

How do I know if the kernel name has been blacklisted? It is a Lineage variant but uname gives me "3.4.113-Deathly-1.0+". I wouldn't be surprised if they had blacklisted "Deathly" kernels?

Anyway, I opened boot.img in a hex editor but cannot find Deathly or Lineage. Based on what I learned from recent comments, I downloaded Magiskboot and "decompressed" boot.img. All I got was a file called "kernel" and one called "ramdisk.cpio". I open kernel in the hex editor but didn't find Deathly or Lineage.

Now I'm stuck. Any ideas? Thanks.

Note: my phone is fine. still on December FP.
[Magisk] badabing2003:
Yes Deathly is banned
[Magisk] osm0sis:
Thanks for checking!

But is it -Deathly or -Deathly-? Every keyword I've found requires either one or both dashes to trigger the ban.

Also what about deathly? Always good to check the lower case of every suspected keyword as well. 🙌
[Magisk] glennza:
Was there a guide for renaming? My efforts were unsuccessful
[Magisk] pershoot:
Nope, haven't tried.
[Magisk] zgfg:
Your app is not avail available outside of your country

If you don't use LSPosed modules, then uninstall LSPosed itself

Alternatively, install HMA and hide all LSPosed modules (incl. HMA) from your app.

And keep LSPosed module but uninstall the LSPosed app

There is a separate thread about HMA, there, from the post #1, follow a link to GitHub to read Instructions
[Magisk] hyad94:
Shamiko works like magiskhideprops.conf module, its needed to hide magisk root, the difference is magisk hide prop is not maintained since 2021, many banking apps, apps and games doesnt work with magisk hide props. Shamiko is more recent, and works better. My banking app works with Shamiko and not with magiskhideprops.conf.
[Magisk] zgfg:
Shamiko is very different technique than MHCP.

Play Integrity Fix, too

MHCP has nothing with Zygisk and by its manipulation of prop(ertie)s it can never hide Zygisk

Btw, there is another developer who has taken over MHCP, you can find his TG channel and you can have an updated MHCP but it will not help you
[Magisk] Essentrix:
You guys are such a wealth of knowledge along with patience; incredible!

Appreciate all the assistance you provide. 🙏
[Magisk] mac796:
I got a question pixel 7 pro I just updated too Android 14 Im still using safety net fix by displax. All my banking apps and everything we're working I was passing basic integrity and safety net. When I run root beer app it detects root. selinux flag enabled. I thought I remember there used to be an app that changes back to permissive or doing it yourself in shell. Should I not worry about this? I tried that shamiko it didn't seem to change anything.

View attachment 6020367
[Magisk] banerni:
Hello,

Thank you for your effort.

I changed the link so that the APK is downloadable.

HMA was also unsuccessful.
[Magisk] aygul12345:
Where is the donation link on the post #1?
[Magisk] drahtwurst:
as mentioned before Commerzbank Banking
[Magisk] jhotayex:
I have tried all and this as well but i am seeing cts profile mismatch. Og Universal safety net module worked before but i am seeing cts error from the yesterday idk why it is happening. Is there any other way i can pass that?
[Magisk] chiteroman:
Which device, rom, Android version... Also you can provide module logs.
[Magisk] dmenezes:
Keeping everyone posted, I just solved the mystery of the non-working banking app.

Turns out it had nothing to do with failing MEETS_STRONG_INTEGRITY, that was a red herring and a bad assumption on my part 🤦

The real reason for that banking app failing to work was that I hadn't configured it properly in Magisk's DenyList.

Here's what I had to do to properly configure it:

a) Open the Magisk app;

b) Tap the gear icon ⚙️ at the top right corner, to enter Settings;

c) Turn on "Enforce DenyList";

d) Tap "Configure DenyList" to enter the list of apps for DenyList;

e) Search for the app on that list, tap on it to turn it on; this will open a sub-list of associated app IDs immediately under it;

f) Make sure every app ID on that sub-list is also turned on.

And that's it, once I rechecked all the above steps and fixed the misconfigured ones, that effing banking app started working like a charm.

Hope this is useful to someone else.
[Magisk] jhotayex:
My device is Xiaomi 11 t pro

Rom: Xiaomi eu 13.0.6

Android v: 12
[Magisk] jhotayex:
My device is Xiaomi 11 t pro

Rom: Xiaomi eu 13.0.6

Android v: 12

Please look into it.
[Magisk] Hitman478™:
@chiteroman OMG i can't believe it!! It works! and i did nothing! Just flashed the module and go! I did tried everything for pass play check but nothing works till now. Thank you very much!!

Btw, i'm on pixel 7 android 14 (not beta)
[Magisk] chiteroman:
Completly uninstall Magisk, reboot and check Play Integrity, by default Xiaomi.eu should pass BASIC and DEVICE, if you don't pass DEVICE verdict np, but if you don't pass BASIC without Magisk it means something is wrong in your ROM and you should reinstall it.

Also you can try to remove all modules (except mine) and try again. Pixelfy module gave problems in the past to some users.
[Magisk] mmbaknnba:
This is maybe ridiculous, I know there're many apps, but is it possible to check Play Integrity/SafetyNet with command via Termux? A glance/hint/simple result maybe?
[Magisk] liver20:
Anyone knows if works CaixaBank sign latest build? With safetynet fix by displax not works and have to install old build pf CaixaBank sign
[Magisk] chiteroman:
Root of trust should be Self-signed... Bad TEE implementations 🫣

Also TEE should sign with custom key but it's using Google 😂

Remove the screenshot with device name or enjoy to be listed here: https://android.googleapis.com/attestation/status
[Magisk] xflowy:
hey guys! is there a way to get strong_integrity check with the fix from op? i am on stock 7p a14 with root (ofc 😅).

thanks!
[Magisk] osm0sis:
If the kernel file split+decompressed by magiskboot didn't have Deathly anywhere in it then you're out of luck, unfortunately. Go tell the developer to fix it, and/or change kernels.
[Magisk] badabing2003:
To be consistent with your list, then I'd say -Deathly- because when I tested I only replaced the string after the dash, so the preceding dash is there, I think probably every banned string would start with the dash.

I'll test lowercase next.
[Magisk] osm0sis:
To test without the trailing dash I do like -Deathlyb

If you could confirm that passes (i.e. trailing dash is required for ban), that would be great! 🙂

I also do always test like bDeathly just to see, but haven't seen one that doesn't need the leading dash yet. 👍
[Magisk] badabing2003:
deathly

-deathly- lowercase is not banned

but -Deathly without the trailing dash is still banned.

UPDATE:

The leading dash for -Deathly is part of the ban, without it it's not banned.
[Magisk] Nergal di Cuthah:
For clarity are those actual b's or supposed to be dashes
[Magisk] osm0sis:
... b's to determine which dashes are necessary, as I explained. Could be any letter or number though, of course. 👍
[Magisk] HippoMan:
What if a spoofed kernel name something like the following is chosen? ...

5.10.160-android12-9-33234-g832242f3ec2f7-a4d29da71

My phone's listed stock kernel name (via "uname -r") follows the above format, although here I've replaced everything after "android-12-9-" with random values, as follows: "33234" are random decimal digits, and everything to the right of "33234-" are groups of random hex digits, except for the first character in the block following "33234-". It's "g" on my phone, and the rest of that block and the following block are random hex characters. I'm guessing that the "g" could probably be any alphabetic character.

Also, if I'm not mistaken, the "5.10.160-android12-9" part of it is related to the GKI version of the kernel, and if so, there are also lots of other valid combinations of components to choose from for that part of name.

Seems to me that the Googlefrinchians would have a much harder time deciding between actual, valid kernel names and spoofed names in patterns like that, than it would be for them to simply identify names like "-Deathly-", "LineageOS", "HippoKernel", etc.

... or is the kernel name fixed length, such that a 9-character name like "LineageOS" could not be replaced with a much longer name in the format I suggested here?

If so, what if we just replace the name with a group of the same number of characters which just consists of random hex digits, or something like that?
[Magisk] Nergal di Cuthah:
I wonder if they're looking at matching kernel string to fingerprint, so a 8-9 print stock likely doesn't have a 5.10 kernel (maybe they do but I've seen lower kernels listed when people come here with theirs).

Repeated caveat: i know little of kernel save that the tensor chip's 5.10 is being replaced with some 6.x
[Magisk] Umgak:
No evidence they are yet - it'd be a huge undertaking to pair every submitted set of fingerprint+extra fields to a specific kernel string. It would make it much more difficult to spoof, but look at how annoying it already is for us to extract a single bootimg to patch the string. They'd have to extract ALL of them, unless the data is already sitting in some db somewhere (fully possible).
[Magisk] zgfg:
Unfortunately, I used to delete the banned ones from my store (hence didn't retest myself now)
[Magisk] Umgak:
It almost seems like the restricted ones are only restricted for some period of time since we've had a few (like the v14.6 fingerprint) start working again after some time.
[Magisk] zgfg:
Yeah, for most of users that's enough. They banned, new PIF module (at that time with the built-in prints) came out or Xoaomi.eu released the new Injector, hence users moved out. They can un-ban, only a few will notice and use them again
[Magisk] Lord Sithek:
I just wonder - what is the point of un-"banning" such a print? 🤔 Does the "ban" harm anyone but those who misuse them for spoofing like us? 😅
[Magisk] sawdoctor:
Ready the discussion on chiteroman GitHub about this it seems they might be looking at a GPU mismatch . If the GPU divers in the device don't match those of the fingerprint sent it will fail. If I've read and understood properly (good chance i haven't 😂) this hasn't been implemented yet but it is what the Devs are worried about.

I'd hazard a guess that banning kernel names is part of Google's testing of Thier new implementation
[Magisk] ARSHD:
My phone lost Device Integrity on 25 January. Before that date it worked good, since begining of december 2023, using PlayIntegrityFix_v14.0 and individual PIF.

I have tried different alternative options: PlayIntegrityFix_v15.4 and PlayIntegrityFork-v7 with several individual PIFs.

As well as PlayIntegrityFix_NEXT (noticed that it download each time same PIF file. New time of the file in file explorer but all data in PIF file same).

But none of these options helped me to get Device Integrity status.

uname -a

Linux

localhost

4.9.219-Noble-4.0

#17 SMP PREEMPT Wed Dec 27 18:19:33 +03 2023

aarch64

Toybox

Does anyone have information whether Noble kernel also in blacklist?
[Magisk] zgfg:
Probably it does, for real owners of those phones with the particular FPs, under some circumstances Or they are not sure about. Btw, if banning was 100% safe, they would have 'banned' all of them long ago
[Magisk] majorfigjam:
Again, you're going over old ground. The "ban" does not affect users of bootloader locked, stock devices with those fingerprints.

I know that from experience, as my old Oreo 8.1 Moto G5 Potter" passes 2/3 when locked and reset, but not if it's rooted. Its print also fails in my Pixel, unlike its related device which has provided a working print for over 2 months now.