yashsingh1/xdaforums huggingface dataset:
[Magisk] CZ.Kostra:
I think the "revival" was a error or a "deliberate confusion?". 🤔
[Magisk] majorfigjam:
I suspect it was a 'honeytrap', as was the extended Christmas non- banning. A great time to collect data on all those devices using the same fingerprint, and to put in place a secondary check on kernel strings for them.

It would be interesting to know how many otherwise stock roms with only custom kernels have been affected by the latest move, as compared to those with LOS or other custom roms.

In my personal sample size of 1, my a14 pixel with Kira kernel remains unaffected.
[Magisk] zgfg:
Or you are going over the ground Fine for you but one example does not prove for all and and every case.

And otherwise, why would they bother to un-ban

This is not the kids world of Tic-Toc, influencers, etc. If ppl here who think it's all chaotic ever worked in the big and serious corporations, would know that changes in the infrastructure must be planned, internally prepared and tested on the staging environment, authorized, etc.

And if there are no clear reasons for, ground mngrs would never authorize the ad-hoc changes. No matter how well planned, something can always go wrong, and nobody wants to be responsible for and grilled by their bosses

For the preparation and pre-testing, all expenses (man hours of the architects, engineers, technicians) must be accounted for. And on the other side there are always some pet projects under the high pressure from the headquarters that have to be worked on and finished, where the bonuses (on the bright side) and jobs (on the other side) are depending on

So why would they bother to un-ban if you know and guarantee that banning them was 100% safe. And again, if you tell them it is safe, they can go and ban the others instead of wasting time and money on un-banning some
[Magisk] trevtdogg:
who says they "bothered"? maybe all the original bans were implemented from the start as just temporary bans with a set time limit.

just because we notice a change at a certain time, doesn't mean it was caused by an action at that same time.
[Magisk] zgfg:
again, what would be the purpose of setting only a tine limit if you can guarantee to Gogglre that banning is 100% safe

but anyway. we're wasting our time
[Magisk] changhuapeng:
My opinion is that there was never an un-ban of fingerprints. Laypersons must have been confused about the fingerprints un-banning and spread such rumours when chiteroman reused in his module, fingerprints from certain devices but of different versions. The reused fingerprints were from Nvidia Shield TV and Google Taimen, if I remember correctly.

Perhaps, people also thought that their prints were banned and un-banned when they upgraded chiteroman's module that were caused by his multiple code refactors.
[Magisk] osm0sis:
I'm honestly quite baffled that they're banning minor and EOL kernels and ROMs, and somehow got @eng.stk's wrong, while blatantly omitting 3 of the largest currently active kernel developers, @Freak07, @tbalden and @DespairFactor. 🤔🤯
[Magisk] bl3d2death:
Is there an easy instruction for non experts how to get own pif.jason files from roms?
[Magisk] elgab:
After reading this topic for some weeks, smells like planned obsolescence apple fetish, I bet 1 lung and 1 kidney they plan to sell more phones and kill the independent ROM since the entire goolag ecosystem is just collapsing. The youtube app is a racket at this point, showing you nagscreens to pay; you say no but the app insists. rapist UX design.

no i dont plan to buy iphone - rofl
[Magisk] osm0sis:
There's a Complete Noobs' Guide: https://xdaforums.com/t/how-to-sear...scussion-for-complete-noobs-from-one.4645816/

It's basically an explainer of my guide. 👍

The UI Workflow Guide is also excellent: https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/page-179#post-89189970

It includes some shortcuts for using pre-made json files which mine doesn't since mine's focus was on making your own.

Then everything else you may need to reference is in this section and under Resources in my README: https://github.com/osm0sis/PlayIntegrityFork?tab=readme-ov-file#about-custompifjson-file
[Magisk] HippoMan:
I've also worked quite a bit in the IT departments of various businesses, some of which are large corporations. Based on my own experience, my guess is that the project to change the integrity checking methodology was completed a couple months ago, and that part of it involved providing the ability to banana and de-banana fingerprints. This entire project would indeed have required preparation, coding, testing, management approval of work and expenses, management sign-off, official roll-out procedures, etc.

And another part of my guess is that once this new software was in place, the actual work of banana-ing and de-banana-ing any given fingerprint or set of fingerprints could be performed on a case-by-case basis using this software, probably by one or more designated people or small groups of people. Using this software, the actual banana-ing/de-banana-ing itself of any given FP or group of FP's at any given time wouldn't require the same levels of preparation, coding, testing, management approval of work and expenses, management sign-off, official roll-out procedures, etc.

This could explain what we have been seeing regarding banana-ing and de-banana-ing of certain FP's.

But who knows? These are just guesses of mine.
[Magisk] chiteroman:
v15.5 released !

Release v15.5 · chiteroman/PlayIntegrityFix

Revert spoof kernel release (it didn't work). Kernel developers should implement in kernel the spoof or rename kernel localversion. Minor improvements.

github.com
[Magisk] Slim2none4u:
Would it be possible to pin this to the top of the thread like a poll so that we can maybe stop seeing the same "is there a guide" question every 10 posts. I understand everything is in the OP and this is NOT for me....Running the same print since December.

But if these guids are pinned like a poll, they will be at the top of evey page.

The the answer is.... TOP OF PAGE
[Magisk] osm0sis:
And back to ShadowHook, and revert the crashy C++ JVM hooking, and include the current Cat print from Xiaomi.eu... 🫤

And you're welcome for the updated scripts you took without credit, again! 😠

Edit: You'll notice any time something I commit isn't completely mine I include a Co-authored-by credit. I've put you there multiple times, as well as @arda99 and @TheFreeman193 and @aviraxp. That's proper manors, etiquette, and having integrity (no pun intended).
[Magisk] 666biker:
hex editing of my LOS 18.1 OP3T for banned kernel string finally bring my google pay working again. Thanks for fiding this info and suggested workaround solution for that.
[Magisk] picarica:
does device integrity check passes on lineageoOS i cant find anynone checking, because it never passes, i tried https://github.com/TheFreeman193/PIFS but it seems that my kernel is blacklisted 4.14.320-lineageos-g6cb257da1f47 is it ? if so is there any way to use different kernel or make it work somehow ?
[Magisk] 5nickers:
I don't know what he does but with his version I can meet device integrity while your version only gives me basic integrity. Same fingerprint.

OnePlus 8, stock rom, android 13
[Magisk] osm0sis:
You just didn't migrate the fingerprint to my fork's more futureproof format, or you're actually using his included Cat one and didn't realize it. If you want to PM me with your print I'll help you figure it out.
[Magisk] :
15.5 comes with build-in fingerprint again, which is likely to be burnt soon. Again. 😉

Fingerprints should be converted between PIF and PIFork, IIRC.
[Magisk] osm0sis:
Can confirm -Noble is banned! Added it to the list.

Yep, no doubt about it. One of the first we noticed banned.

Check the list:

🔧 [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

You'll have to look into whether your device has another kernel that'll work and isn't banned, but you should let your ROM maintainer know they should fix it.
[Magisk] matfcb:
15.5 Basic passed, Device no. I downloaded new fingerprint, Device still not passed.
[Magisk] Nergal di Cuthah:
Keep trying, not every print will work

Custom kernel?
[Magisk] matfcb:
Xiaomi.eu software, I didn't install anything else.
[Magisk] Nergal di Cuthah:
To my understanding xiaomi.eu has its own spoof. Are you running both spoofs (this will result in a fail if i understand correctly)
[Magisk] zgfg:
Fot Xiami.eu you must first properly disable/debloat their own injector

/product/app/XiaomiEUInject/XiaomiEUInject.apk
[Magisk] matfcb:
I don't have Inject module. ROM for my device didn't have that.
[Magisk] :
Should have for now. You might have another problem.

How?
[Magisk] Umgak:
Could also magisk patch the new boot image before flashing it, so that you don't have to reflash magisk after, since losing root makes getting it back slightly harder. Either way, move patched boot image to phone, magisk select and patch file, move twice-patched image back, fastboot flash boot. Honestly, I'd personally magisk patch it all the way up before part C, right after you've repacked it.
[Magisk] matfcb:
Fp Downloader from Play Integrity Next.
[Magisk] :
So you might have overwritten xiaomi's fingerprints with itself.

You have another problem.

What is the outcome of "uname -r" from a terminal emulator?
[Magisk] matfcb:
It worked before on the same fingerprint. 15.4. I remove the fix, reboot and I will install it again and see if it works.
[Magisk] Wolfcity:
On my testing device (Moto g 5+) I'm running lineage unofficial 18.1.

It used to pass 2/3 with the same print I use on my main device (Xiaomi Mi 9T, xiaomi.eu 12.5.2, A11) since the beginning of December.

Since the "google kernelstring check" appeared it passes only basic.

Output of uname -r and uname -a is

$ uname -r
3.18.120-perf+

:1$ uname -a
Linux localhost 3.18.120-perf+#6 SMP PREEMPT Tue Oct 10 19:12:15 C
EST 2023 ar
mv81

So no banned strings.

Also other prints of my collection only pass basic on that device while all are working on my Xiaomi.

It's just my testing device but I'm curious what is happening there and if there's something new going on.
[Magisk] helidwarf:
I just swapped to lineageos from xiaomi.eu on my poco x3, used to pass basic and device just fine, now fails device.

uname prints

4.14.326-lineageos+

which is not on the banned list yet.

Wonder whats going on hmmm.
[Magisk] osm0sis:
What do you mean? -lineageos was the first added to the list after -Sultan 🤔
[Magisk] Nergal di Cuthah:
The "list"is far from comprehensive. This is a new thing and @osm0sis is just begun testing
[Magisk] helidwarf:
God I must be blind
[Magisk] Nergal di Cuthah:
View attachment 6063656

@osm0sis i was working on the assumption that the + was a difference so answered on that assumption. Guess not
[Magisk] osm0sis:
Nope. The string is -lineageos which means anything can come after.
[Magisk] Nergal di Cuthah:
So just banning donkey would kill the above posted's changed kernel name? (Edit tried to find it to link for remembrance but sooo many pages and neo doesn't care search is broke)
[Magisk] matfcb:
4.14.180-perf+
[Magisk] bl3d2death:
Hey... I used the FP Downloader.

Root check says: safety net pass and for play integrity= meets device Integrity.

Gpay don't says anymore unsecure device and seems to work (actually can't test the app ATM)

But Payback App still detects root. So what's wrong? Wrong play integrity?
[Magisk] Nergal di Cuthah:
PI is not the end all be all solution. Probably detects something else. Learn about shamiko, hma and other cooperative methods some which will trick payback some won't gotta try many solutions
[Magisk] Stаr:
KernelSU actually just fixed that with this commit. Seems to be a new vector apps are using for detection.
[Magisk] osm0sis:
Uhh, the banned strings are exactly as shown in my list post.
[Magisk] bl3d2death:
So Nothing I can do so far? Wait for an Update? Cause @chiteroman updated the module only few hours ago.
[Magisk] Stаr:
If it's the same issue as the KernelSU one then I believe it'd require an update in Magisk itself.
[Magisk] Nergal di Cuthah:
Was a hypothesis to try to understand. Postulating that the guy who changed their kernel name to do with donkeys would be (hypothetically) banned by google adding "donkey" (without the quotes), with no mind to words before/after donkey, to the list. It was to better understand the function of the block to use a single part of the kernels's vanity name to stop them from adding a word to the string and getting around the block. They couldn't change a single letter (for instance change the second word to "ducks")
[Magisk] bl3d2death:
Thx for the answer. I don't used kernelsu before.

Is it faster updated or what's the differences between magisk and it?

Magisk Beta v27 came out yesterday. Someone knows if it's patched there?
[Magisk] xcl1pse:
Its for ksu., no point for magisk to include that commit, just check your environment. I tested that and no warning after initial setup.
[Magisk] bl3d2death:
Don't know what exactly you wanna say
[Magisk] sawdoctor:
KernelSu and Apatch both patch the kernel where magisk is a systemless root. The advantage of kernelsu and Apatch is they are better at hiding root. They essentially do the same thing as magisk but depending on your device you might have to compile/patch the kernel. Not all Magisk mods work on KernelSu and Apatch but there's plenty of guides/info if you Google
[Magisk] xcl1pse:
Ah my bad. My reply was for the second paragraph you asked
[Magisk] sga999:
Well, I guess we can't expect the string to be in the same order in all images. I didn't read what you wrote closely enough, thinking the 1st one I found would be correct. After flashing, it booted fine, but the kernel version didn't change, so it didn't hurt anything, but it didn't help either. Then I read your instructions again.

For me, instances 1,2,5 had no path, 3,4 did. So I changed the 3 no path ones (I had already done 1)...and it crashed my device! I was able to flash a good boot image back.

So before I do it again, I hope someone can say more about this. I may have read something by @osm0sis that described what to look for. But I haven't found that post yet.

My string is -lineage- (18.1 on Leeco Le Pro 3). Number 1 (that didn't help) has 'preempt' uppercase maybe 100 hex after the string. 2 had 'preempt' lowercase about 20 hex after. 5 had 'preempt' uppercase about 40 hex after. Maybe we were told to match what uname told us? Since changing 1 did not hurt, I think I'll try putting 2 back to lineage, leaving 1,5 with the change, so 2,3,4 with lineage. But I'll wait a little and see if someone gives me any advice.
[Magisk] matfcb:
Everything worked fine on Xiaomi Mi 9 Pro 5G Android 11 PIF 15.4. On 15.5 I can't pass Device. Magisk Canary latest version.
[Magisk] osm0sis:
I usually search for PREEMPT until I find the area in my screenshot here: https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/page-518#post-89308791

I repeat, that's the *only place* I needed to change it for the desired effect.
[Magisk] sga999:
I was impatient so I went ahead, knowing it might crash it again. Flash worked well, PIF fork v7 is also with a .json that I thought would work.!

Before that, I decided to update to the latest Lineage 18.1 (Feb 1, 2024). That kernel was VERY different from the prior one. There was a similar #1 that I didn't modify this time. Then there were LOTS of paths or error message strings or whatever, which I didn't touch. Then the last one was similar to previous #5 That's the only one I changed. Thanks @osm0sis for a general idea and @remoh for more specifics.

EDIT: Thanks, @osm0sis, I was composing this before your response arrived.
[Magisk] ew:
I have a moto g100 running the latest version of lineageOS -and still passing 2 of three.

Output of uname -r and -a:

uname -r

4.19.304-perf+

uname -a

Linux localhost 4.19.304-perf+ #1 SMP PREEMPT Mon Jan 29 03:40:04 UTC 2024 aarch64 Toybox

Maybe there is something else going on in your case.
[Magisk] HippoMan:
Please forgive me if this has been discussed here and I somehow overlooked it:

Does anyone happen to know whether the kernel name string shown in the hex dump is a \0-terminated string which could therefore be of variable length, or whether it's treated as a fixed-length string, in which case its name would have to be changed to something with the same number of characters?
[Magisk] ihavenolifee:
Hmm, having an issue with google wallet now, even with play integrity passing and google wallet showing that it has no root or restrictions.

Adding the card, even directly from banking apps, gives the popup error "Check your network connection".

Is this something that has a solution to it?
[Magisk] Utini:
So I guess this is one reason why you made your own fork?

I never understood why making a fork instead of working on one module together but that might explain it.
[Magisk] knoedelcc:
Sounds like an issue with adblocking (connection to necessary service is somehow blocked):

Can you disable your adblocker temporary and retry?
[Magisk] sawdoctor:
Have you added any Google apps/services to deny list or anything like that?
[Magisk] mierdaseca:
Banking, Netflix and McDonald's app work fine, but I cannot use Google pay, it says my device might be rooted.

I checked with "simple play integrity checker" , sometimes, it fails, but if I run the test again, it passes with "meets device integrity".

I also tried installing shamiko (never needed it before), forcing close Google play services and deleting its cache, but nothing. I also tried adding all Google related system apps to magisk denylist, force closing Google play devices, and deleting cache, but still detects it.

Using magisk 27 + pif 15.4
[Magisk] sawdoctor:
Don't add your Google apps to deny list or anything like that or you'll probably never pass play integrity
[Magisk] mierdaseca:
I tried both: adding them and not adding them
[Magisk] CZ.Kostra:
What ROM do you have?

It looks like PIF is conflicting with another method to bypass PI.

Google apps remove from DenyList!!!
[Magisk] mierdaseca:
CCr

Crdroid 9.6, without any banned string in the kernel.

I currently have no Google apps in the deny list, but I also tried adding them, just in case.
[Magisk] badabing2003:
What @CZ.Kostra says.

You must have a rom that does it's own spoofing and you have to disable their injector app to get it to work.

Use the @osm0sis fork and check the notes, to know how to disable it.
[Magisk] osm0sis:
It's null terminated, so you could make it look shorter if you want by filling the rest of the line with nulls, but you're hacking in a compiled kernel so you can't actually make the line shorter or longer. Arguably might be better for it to remain the same length as the original too.
[Magisk] Slim2none4u:
So this is now a kernel modding thread? Nice having to read through a bunch of garbage about modding kernels in a PIF thread. This place has gone to the dogs! Over 10k answers to read through. OUT OF CONTROL!!!
[Magisk] mrjuniork:
It's in the hands of the OP 🤷🏻

But yes, some topics here are definitely worth their own thread 😉
[Magisk] marisaleh:
poco x3 pro rooted with

Magisk 27.0

PIF v15.5

When I run Integrity Checker

I get this

Is this a good enough result

How important is it to pass

Strong Integrity, and how do I pass it
[Magisk] :
Your kernel string looks ok. But why did you update to 15.5 if 15.4 was working? 😉
[Magisk] osm0sis:
I think he was just trolling, because it's very on topic since Google started banning kernel uname release version strings. 😛
[Magisk] osm0sis:
15.4 still had the crashy C++ JVM stuff, so either 15.1 or 15.5 would be the the way to go, if you're staying on chit's.
[Magisk] zgfg:
Kernel - only for the last 15ndays or so

And the rest is garbage? - nice words
[Magisk] CZ.Kostra:
Strong integrity pass is now impossible with an unlocked bootloader.
[Magisk] :
You can't pass strong on a rooted device unless you learn to ride a hippo: https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89262699
[Magisk] Slim2none4u:
I think you have made many threads and could just make another, I think you have hijacked this thread. Kernel banning and hense the modding thereof should be in its own thread. It way more advanced than just this PIF thread and adds confusion and unwated/unneeded garbage.
[Magisk] HippoMan:
Thank you very much.
[Magisk] osm0sis:
The *Play Integrity* kernel banning is very much part of PIF. Get off your high horse. The unnecessary comments are ones like yours.
[Magisk] justDave:
Can the OP rebase a thread? 😏
[Magisk] marisaleh:
I see , so he's got it to pass everything

But it doesn't show how he did it ,

What additional modules did he use ?

As it is at the moment , it's impossible

I agree , too much researching , editing

And trialling , too much information on

the forum ,

We need a very short summary from

all this information so that we can

narrow down the procedure for getting

a solution, otherwise it's like searching

for a needle in a haystack !!!
[Magisk] justDave:
... or we could just continue to live without passing strong.

EDIT: Here's a handy mnemonic: "Two out of three ain't bad."
[Magisk] Umgak:
That was a joke post. Hence the EXTRA_STRONG_INTEGRITY and SUPER_DUPER_STRONG_INTEGRITY sections.

You won't pass MEETS_STRONG_INTEGRITY.

Spoiler content hidden.

🤨
[Magisk] HippoMan:
In order to get those results that I posted, I used a module that I have not seen mentioned here.

The module is called GIMP.
[Magisk] Wolfcity:
Thanks for that piece of information.

Crazy thing is it started right when the kernel string banning thing appears.

I don't see a kernel for that old device to make an A/B check.

Maybe I'll flash another ROM (A9/10 in this case as there aren't that much other ROMs running A11 and pass PI)

The device had reached EOL with Oreo.....🙄

As said, it's just for testing so no harm for me if it doesn't pass PI.
[Magisk] linuxares:
Just for anyone updating to Magisk 27.

Osmosis fork works without any issues. Actually everything works fine so no need to worry about your fingerprint getting detected in case you upgrade.
[Magisk] ph03n!x:
I read 535 pages of this conversation - just to keep track. And thanks to @osm0sis and @TheFreeman193, passed Basic and Device again in like 1 minute. I was on @chiteroman's modules for while (Thanks a lot for all the work to you, @kdrag0n and @Displax for PIFS/ USNF, and all variants in between that kept us going). Thanks again!
[Magisk] ihavenolifee:
It looks like the only adblocking thing I have, at least that I know of was adguard dns, and that was disabled already upon testing. Thank you for the reply. Same issue, which is strange.

I have put google play services/google wallet on Magisk Hide. This never had an issue before, and back then this was needed to get it working for the "security requirements". I believe I have tried with this not hidden too, and had the same issue. Thanks for the reply.
[Magisk] ihavenolifee:
merged to one above, thought I could delete this post sorry.
[Magisk] sawdoctor:
They complain about the posts from Devs like yourself and others but are still using your work.
[Magisk] matfcb:
I updated to have the latest PIF.

On Play Integrity Fork I don't even pass Basic BTW.
[Magisk] osm0sis:
That 100% means you missed something in the setup instructions. Happy to help if you want to PM me your print.