yashsingh1/xdaforums huggingface dataset:
[Magisk] mrjuniork:
Ok, let me put an end to this now.

My previous post was basically addressed to the OP @chiteroman in order to publicly remind him, since this is his thread, that it's on his terms what is deemed off topic.

If @osm0sis wants to open his own thread is simply his decision, and he has already stated that this is very much connected to the topic at hand.

He is is not hijacking this thread! He is sharing his knowledge and educates us noobs, which is basically what XDA is about.

Like I said, the OP has to set the standards for this thread, not a user. Despite that, anything that's violating our forum rules, will be dealt with, as usual.

So, I kindly ask you to refrain from such posts from now on.

Cheers,

mrjuniork
[Magisk] heathrow1:
I am still on play integrity fix 14.0 with my first fingerprint which I found two months ago. Still passing device with this setup. Any need/advantage to update the module?
[Magisk] H4X0R46:
OnePlus 11 5G

It passes the others but not strong integrity. Am I doing something wrong here? View attachment 6064139
[Magisk] majorfigjam:
Refer post 10675, on the previous page.
[Magisk] H4X0R46:
Thanks for that.... Damn that bums me out! I wonder if in time.... There will be a way 🤔 Android development has a funny way of finding a way haha Thanks dude!
[Magisk] V0latyle:
You can't pass Strong on an unlocked bootloader.
[Magisk] mingaldrichgan:
Honestly I thought @Slim2none4u intended it as a harmless joke.
[Magisk] HippoMan:
My advice: if it ain't broke, don't fix it.
[Magisk] H4X0R46:
And I'm gonna venture to say that most if not all apps that check this API will require strong integrity to pass.... Damn.
[Magisk] majorfigjam:
Only as and when they choose to support only devices capable of returning strong integrity, ie newer than Oreo.

I've seen some corporate apps apply that restriction (the old Fraedom app for one only supported 9.0), but not many others.

App developers may not want to burn their customers with legacy devices.
[Magisk] XDM inc:
of all the non working ones THIS one DOES work👍
[Magisk] Umgak:
G Suite only requires device integrity at most, which can be passed with an unlocked bootloader by spoofing an older device with this module. It's up to individual apps what level of integrity is required, and most seem content to leave it at Device, since many phones don't even support Strong at all.

This one is currently in active development, the others are all legacy projects that are no longer maintained. So it makes sense.

Your old device might have some other module that's detectable - I remember I used to have issues with EdXposed back in the day which would cause SafetyNet to fail. Otherwise, it may be based on abilist - I remember PIFS tries to match spoofed prop to the abilist of your real device, so depending on age it may not work with the same donors. getprop | grep ro.product.cpu.abilist to get your device's abilist.

Please refrain from denylisting Play Services - any time a process is denylisted, Magisk breaks all mounts within its space, which will cause PIF to unload! PIF will handle the hiding mechanism itself, and will repeatedly attempt to remove Google Play Services from denylist at boot. This is normal, and absolutely necessary for module function.
[Magisk] ihavenolifee:
Got it. Will keep that off of the Magisk Hide.

Still, even without that on the Magisk Hide list, still having that "connection issue".

It states "Check your network connection, Make sure you're connected, then try again"

Trying to figure out what could be blocking this connection to google or google wallet. Have made sure no DNS/adblocking, and also tried different networks/mobile data.

Even tried to use a VPN and no success. Seems like something adblock/DNS related but I've even factory reset the phone....
[Magisk] V0latyle:
You'd be wrong.
[Magisk] H4X0R46:
I'm honestly glad I'm wrong, not gonna lie 😅
[Magisk] Nergal di Cuthah:
Some of us follow the agreement we took by posting in this site (other words rules say read) ;)
[Magisk] GabbyWC:
I don't think that most people here would mind if the user who you directed this message to was banned for his repeated nonsense. The fact that you asked him kindly is a courtesy that he should also take as a serious warning.
[Magisk] trevtdogg:
I must say, in my opinion the op currently has enough info as it is.

it mentions the banning (banana-ing) of prints, and the kernel blocking.

it links to an info thread that discusses the need to spoof a fingerprint, that passing strong is not possible, and also includes a link to the noob friendly guide.

sure it could maybe be a little better, or include more links and details, but the basics and crucial info are all there.

if people here act like they want to be soon fed, just point people to the op and tell them to read up about it.

the answers really are not hidden or difficult to find or anything.
[Magisk] wugga3:
ROM?

Kernel?

Device???

Any way... What, if any previous configuration did you have that was working, if working prior to this current situation????

Not sure if it previously worked with any prior configuration.... So in other words, what's changed if anything to cause this result now?

Sorry if I've missed something from your prior posts here if any....

Why I'll ask any of this is due your update of both magisk and PIF.... From what little I understand, which is admittedly zero, even after reading every single post from start to finish... I'll say that I'll doubt magisk 27 is to blame... And doubt PIF 15.4 is to blame either

So if this was working properly before and isn't working properly more then what's changed?

Thanks and cheers
[Magisk] m0han:
Even if @osm0sis were to create a new thread (which, I understand by now, he wouldn't), I don't think cross-posting (here) would stop.
[Magisk] frasca61:
My phone still works with my first fingerprint of December 12th and Chiteroman Dev V2, but I have verified that I have Google Play Service and Google Play Store on the list of Magisk blocks and also in Hyde My App, with this configuration, Google Wallet works e also Banks App. My device is certified by Google......
[Magisk] purgy:
Just wanted to say thanks @osm0sis for the kernel edit guide, I'm back at 2/3 with my "Stupid" (nee sultan) kernel.View attachment 6064297
[Magisk] straightcore:
osm0sis

Same fingerprint

View attachment 6064299
[Magisk] greg.chalk:
Hello,

I have chiteroman module. It stopped working a few months back. After reading forum I found that I need to install a fingerprint from another device. I thought it to do it sometime in the future cause now I don't have time.

Still haven't search for fingerprint but this happened:

Shamiko had an update but required canary magisk, so I updated magisk to canary and then updated Shamiko.

Surprise: Basic integrity and device integrity pass again!

My wallet works again!

I haven't installed any fingerprint or anything!

How it's possible?

Just wanted to share my experience.

Thank you for your work!

I have a pixel 4 XL with magisk, chiteroman module, Shamiko, mindetach and systemless hosts.
[Magisk] simplepinoi177:
[All XDA Members] Feedback/Recommendations for XDA

After reading a few threads and comments from our members I thought it may be worthwhile to create a Feedback, Recommendations or Idea's thread for XDA. We want to improve our forum for developers and the normal users. So, rather than sending...

xdaforums.com
[Magisk] xcl1pse:
Chiteroman was so kind, he broke his promise that he will not include any fingerprint for new version and so on, but on latest PIF v15.5 he included the working one for his lovely user 😙
[Magisk] sawdoctor:
Your going to have to give a bit more information like device, software, kernel etc. i know osmosis switched from shadowhook to Dobby around then but I've not heard of Dobby causing issues for anyone. He did add more fields but your print should be migrated by the install script
[Magisk] greg.chalk:
Thank you for your response!

That's nice 😃.

That means I still have to search for fingerprint at some point 😉.
[Magisk] simplepinoi177:
Honestly, this is now what's necessary to run this PIF module for many users.

You could say the same thing about when implementing one's own fingerprint became a requirement -- "has this become a 'fingerprint' thread?!"

These are aspects that are a part of PIF now currently, and hence are on-topic and applicable/relates. Even if/when fingerprints were "way more advanced" and had just "adds confusion", it's become the reality of the situation. And while some other threads had been created, most go to this one because this is the main branch (of a module that they're currently trying to use) and they see all the experts that offer support still frequent here. So while it might be more organized to create/move the discussion to another dedicated thread (which I personally doubt how necessary/needed it would be), there's still value having the discussion here
[Magisk] Vision:
New Year, new us :ROFLMAO:

View attachment 6064337
[Magisk] gloops100:
Hello all,

I installed Magisk through TWRP. The device is fully rooted.

Play integrity is working (I've modified build.prop), all is working.

I want to install the latest OTA update, and I've been trying to do it using this guide. I'm stuck on step 2:

When I follow these instructions, I get this error:

How can I install the update and stay rooted? (seems related to "build.prop" modification)

Phone : Xiaomi Mix Fold 3

Firmware : 1.0.2.0 UMVCNXM

Magisk : 26.0 + Zygisk - LSposed + Shamiko
[Magisk] Aldenar:
Something strange happened.

I was failing device.

Today, I updated Magisk app + the magisk-patched boot image, then... I started passing device again!

Without updating PIF along with it as well.

How is that possible?
[Magisk] osm0sis:
The fingerprint format hasn't changed since v5, so it's not a migration issue. @straightcore, please PM me your fingerprint and device setup and we'll figure out what the issue is. 🙂
[Magisk] mierdaseca:
Swapping PIF 15.4 to osmosis fork and clearing Google play/ services cache fixed it for me.

Prior to that, PIF worked fine up to 15.1 I think it was, after that, at most I could add a card to Google wallet, but not use it.

I have yet to try, but Google wallet doesn't say anything about root now.
[Magisk] galaxysyes:
Can someone help meplease? Tried everything think but still not get device integrity. Already tried osmOsis and chiteromam play integrity but didn't work. Device xiomi 10t pro

View attachment 6064407View attachment 6064408

View attachment 6064406
[Magisk] Tamsta_T:
"user_test_keys" never worked for me, look for fingerprint signed with "user release-keys" (fingerprint line should end with user/release-keys).
[Magisk] Umgak:
Your device's kernel contains a banned name. You can try to edit your boot.img with a hex editor and search for lineageos, then change it to something else. You need to find the block that looks like the one in this post https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/page-518#post-89308791

It may be easier to search for (none) or PREEMPT to find this instance of the name. You only need to edit this one, not any others. Keep the length the same, you can just change one letter if you want. Then, repatch the image in Magisk and flash it.

EDIT: Update your OS to the latest version. Your LineageOS maintainer is looking out for you ;)

(Edit 2: Added a link to the commit in question)
[Magisk] zgfg:
Google Play Store and Services are NOT NEEDED to be in HMA (repeated in this thread tons of times)

HMA = Hide My Applications and they don't look for Magisk app or your LSPosed apps, so no need to hide them from Google Play Store or Services

Your old FP works bcs it was not banned and bcs you don't have problems with Custom kernel.(not bcs you use enabled HMA for them)

You can simply disable them from HMA and retest

----

I don't know what do you mean by 'list of Magisk blocks', but if you mean DenyList in Magisk, then you can also safely remove them from DenyList (or MagiskHide in the old Magisk)

Play Store does not need to be in DenyList and PIF takes care for Play Services instead of DenyList.

And Play Store tests Play Integrity through Play Services

---

But all that as above applies only to Google Play Store and Services

For your banking apps:

- You must keep them in DenyList

- Keep them in HMA if they worked fine with HMA so far (it may be not needed for some banking apps but will not hurt)
[Magisk] Teuba:
Well, I use Lineage too but the device is now discontinued (monet)...

I tried to compile the kernel myseld to change the name but got an error that I don't understand.

I there like a streamlined "how-to" compile a Lineage kernel somewhere? I found a bunch but they all have different steps and that doesn't sound very reliable I guess.
[Magisk] V0latyle:
Generally, questions regarding compiling kernels wouldn't belong in this thread...
[Magisk] remoh:
You can try this guide (but that is not compiling but hex editing)

🔧 [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] tom1807:
FYI, updated to Magisk 27.0, got a PlaySystem Update (2x 720kb), updated Shamiko to v1.0.1 (300).

Custom Fingerprint continues to do its job since December 12, 2023 with PlayIntegrity Fork v7.0.

Cheers

Tom
[Magisk] EuK_V:
Today I got an update for my phone hoping for removing "lineage" from kernel name, too.

No.. "lineage" is still there. So I decided to report a bug to Lineage and found that someone did it 3 days ago:

https://gitlab.com/LineageOS/issues/android/-/issues/6655

It seems Lineage doesn't care..
[Magisk] V0latyle:
0.7? Whose fork?

Didn't know there was a Magisk update, thanks for the tip!
[Magisk] ph03n!x:
You have LSPosed - have you enabled Google Play Services in any of the modules? Also, have you enabled Enforce Deny List in Magisk with Google Play Services selected (disable Enforce Deny List, use Shamiko instead).

Finally, try different fingerprints - might take a while, and the same print that passes in one device needn't pass the other...
[Magisk] nek46:
greetings from greece, install magisk the last version 27.0 and play integrity 15.5 and i saw this

test with Gpay all ok device htc u ultra rom, custom lineageOS android 12

now how long it will last I don't know but ok, sorry for my bad English
[Magisk] ArzZenic:
It's gonna die soon, as you're using integrated FP in the new version.

RIP Cat, you were loved since 5th Dec.
[Magisk] CityKev:
If I didn't have Play Integrity could I use a second space on my Redmi Note 10 Pro for banking apps etc whilst having having unlocked bootloader and root on my primary space?
[Magisk] sawdoctor:
I have a second user on my pixel which is rooted on the main user. My Bank apps don't detect root on the second user but can't guarantee it will work for everyone
[Magisk] osm0sis:
And yet we've got reports of several other maintainers removing it. 🤷‍♂️
[Magisk] EuK_V:
Maintainers of official lineage roms?
[Magisk] osm0sis:
Yep. npjohnson is an official maintainer and someone else mentioned another one in here over the last couple days.
[Magisk] EuK_V:
So, maybe I should try to contact maintainer directly?
[Magisk] osm0sis:
If they're open to that. Try their thread.

As I said before, it may be an issue of how to frame the concern.

Like they don't want to participate in the cat and mouse game, and we can't blame them for that, but they could also just easily remove their unnecessary banned kernel string branding and not contribute inadvertently to any issues their users are having.
[Magisk] downhere:
I tried that too, but my bank app detected root (as did for main/admin user).

LineageOS 20.0, Kitsune 27001, PIF v7.

I didn't do any extra setup for the second user.

Interesting point was that Google reported the spoofed phone / fingerprint as device for the second user (security alert).
[Magisk] EuK_V:
Ok, I'll try. But even if they don't, it's not such a big problem to edit the kernel from time to time. If Google doesn't come up with something else...

Gonna update less often now...:)
[Magisk] majorfigjam:
Looking on the bright side for now ..... no obvious new surprises from Google today.

I just updated to Google's February patch UQ1A.240205.002, Play Services 24.02.13 and Play Store 39.5. on my Pixel 6Pro (for now with stock kernel), and I'm still passing device integrity and wallet security requirements. There's still no Play System update available to me since November.

For what it's worth, I have Magisk 27001 Canary, with Shamiko 1.0.1 and Google Wallet is in my (unenforced) deny list.
[Magisk] Umgak:
Looking at that gitlab, this was submitted as a bug, and was closed for being not a bug. It will likely go over better as a request to the maintainer directly.

Like the one I posted from the Gerrit earlier! Or also all of the ones that flat out never had it to begin with for that matter - mine has always been stock qgki, just with upstream changes.

No reason to denylist. Also, Play Store and OS updates shouldn't have any effect on passing PI in general - the DroidGuard process runs and updates silently in the background, regardless of all else, so posts like "X new version still works" aren't really necessary.
[Magisk] V0latyle:
I haven't found this to be necessary

I have no Google apps in DenyList and I have had no issues with contactless pay
[Magisk] majorfigjam:
Maybe it's not needed, but as the saying goes - "If it ain't broke"
[Magisk] sga999:
I succeeded in unpack/patch/repack with magiskboot, as I posted in this thread earlier. But I like to learn and am interested your method. I haven't done anything with scripts for a long time and need some info.

I copied the script to /system/bin, only because I think I've done that in the past. I made it executable. But here's what I get without giving it any options. It says it's inaccessible, yet it does go ahead, and it shows me the options. Same result in both terminal emulator or in adb shell, both with su.

126|mata:/system/bin # sh ./kerpat.sh

: inaccessible or not found

Usage: ./kerpat.sh [OPTIONS] replacement_text

OPTIONS:

-offset OFFSET Set the offset for patching the kernel (can be decimal or hex format. Default: )

-bootfile FILE Set the bootfile to patch (default: auto-extract)

-flash Flash the patched boot image after patching (default: )

-compression COMP Set the compression method for the patched kernel (default: auto-detect)

-slot SLOT Set the slot to flash the patched boot image (default: auto-detect)

-magiskboot PATH Set the path to magiskboot binary (default: )

-check_kernel Check if the kernel is in the known banned list and exit

-h Show usage information

: inaccessible or not found

./kerpat.sh[18]: exit: bad number: 1

Is /system/bin the right place to put it? Can it be put in /sdcard instead? Is 'sh ,/kerpat.sh' the right way to execute it?

I apologize for asking something basic, so if you want to PM me instead of continuing here, that would be great.
[Magisk] majorfigjam:
Except that many casual readers with stock roms and an "update obsession" (like me) may be wondering if it's safe to update without risking PI, and I'm letting them know that in this case it is.

Who knows what Google may be hiding in their monthly patch release.
[Magisk] badabing2003:
put it in /data/local/tmp

then run it like this

sh ./kerpat.sh

It should extract boot.img from your device, unpack and decompress, you should get a kernel_unpacked file in the directory.

Inspect kernel_unpacked to determine the offset

then run again

sh ./kerpat.sh -offset 0xXXXX TEXT

or

sh ./kerpat.sh -offset 0xXXXX -flash TEXT

(including -flash) will flash the updated kernel

where XXXX is the offset in hex, or you can do in decimal form without the 0x prefix.

And TEXT is the replacement text that you want to apply at the offset.

For example if your kernel has lineage in it and you want to replace the i with 1

Point the offset at position i and set the text to 1

You can use the -check_kernel flag before patching to see if it is in the banned list, and test again after patching + rebooting
[Magisk] sga999:
Thanks so much for the quick response! That did the same thing, i.e. inaccessible or not found, yet it goes ahead with showing the options. No kernel files are placed in /data/local/tmp.

EDIT: I tried option -check_kernel, but result is the same. That inaccessible message is trying to tell me something.
[Magisk] badabing2003:
You're running as root right?
[Magisk] Umgak:
I was considering writing something like this and trying to implement auto offset detection. The Linux [giant block of 00 bytes] (none) [more 00 bytes] kernel string format is unique and should be present in any decompressed kernel image, so I was planning to detect it off of that, in case you want to implement scanning for and parsing the kernel string.
[Magisk] sga999:
Yes, you'll see the # before I issued the command.

EDIT: I copied your lines and pasted into a file. Can it be a problem with CR/LF or something like that? I know I've had an issue like that before. Yet it does actually run and display the options.

EDIT2: Or is that #!/bin.sh correct at the top?
[Magisk] Princknoby:
Dude, thank you so much for this!

I managed to make my own personalized string thanks to the step-by-step instructions you described, and I obtained the certification I needed.

I thank everyone.

@remoh

@osm0sis

@chiteroman
[Magisk] badabing2003:
Line endings could definitely mess it up.

after the line #/bin/sh add this line and run again

set -x

provide the output
[Magisk] sga999:
YES! I won't put the output since it did put the kernel files there. If you really want it, I can paste it. It immediately starts extracting them and does not display the inaccessible error. Strange that it does run and show options after that error.

So I had just used a text editor on Windows that must be inadequate or I would need to tell it something about the end of line. Can you suggest a Windows app that would not mess this up when pasting? Maybe Notepad++?
[Magisk] badabing2003:
There is really nothing sensitive in the output, you can paste it here in case it is showing some errors.

you can run dos2unix on the file in Android (assuming that you have it on our Android)

or in N++

right click on Windows (CR LF) in the status bar and select Unix (LF) then save

View attachment 6064617
[Magisk] sga999:
It did not get errors, so I thought I didn't need to paste it. I haven't actually gone through the next steps, so I'll get to that soon. But it definitely unpacked it.

Thanks for the info on ways to get CR/LF correct.

I REALLY appreciate your very fast assistance!
[Magisk] zgfg:
Use Notepad+-+

You can make visible tabs and EOLs,

fix/replace the EOLs

You can compare changes between the versions of your scripts, you can download and install add-ons to work with eg hexadecimal files, to validate the syntax of JSON files, to indent script or JSON for better readability, etc

---

Btw, you can also copy the line by line from the given script to Terminal emulator, but it's tedious for a long script
[Magisk] dosbuddy:
Same setup as mine.

Also updated to Magisk 27.0 and Shamiko 1.0.1

FP is from 29.11.2023

Everything fine (2 of 3).

Thank you all!
[Magisk] sga999:
When you said "Inspect kernel_unpacked to determine the offset", what do you use to do that on Android? I had been using Windows HxD to look at the unpacked file.
[Magisk] tom1807:
I meant PlayIntegrityFork v7.0 from @osm0sis.

I corrected it.

Sorry for the confusion.

Cheers

Tom
[Magisk] osm0sis:
v7

7.0 if you really must. :p