yashsingh1/xdaforums huggingface dataset:
[Magisk] adinechin:
Hello, I must admit I'm a bit lost between all modules, and it seems that the rules have been changed a lot by Google lately....

Today I cannot find a proper solution, so here is my situation :

I'm on Xiaomi Redmi Note 10 Pro

I'm on a Xiaomi.eu rom (Android 13, v14.0.9.0) so even without root, I don't have any certification

I would like to have the following (I think both need the same "Play Protect" certification

Google Wallet (Pay) working

Netflix available/updatable via Play store

Work apps and work profile which seem to work correctly with Shamiko

What should I install / use :

Magisk stable or Canary

Shamiko

Play Integrity Fix ?

SafetyNet fix ?

I've already tried different combinations, but I cannot find one where the Integrity Checker is completely green and my apps working (or at least not yet)...thanks for your help !
[Magisk] ace2nutzer:
V.15.1 really deserves the previous module description:

"Fu... Play Integrity API"

it seems to be fixed for ever!
[Magisk] Nergal di Cuthah:
Maybe google had end year reports on play integrity effectiveness so they banned a bunch then gave the p.i.g. their papers.

(really it's because a critical mass, of people using custom print different from everyone else, has been reached)
[Magisk] adinechin:
Ok so I have a first level of answer

The developper of Play Integrity Fix recommends using the specific app of Xiaomi.eu for xiaomi.eu users

It seems I still need the safety net fix in addition

I also have shamiko for my work apps

All this is on Magisk Canary

It seems with all this, that I have the integrity to have the wallet working, and play store telling me I'm certified, but not yet to have Netflix available...wait and see...
[Magisk] ace2nutzer:
Btw I've managed to fake official phone status (kernel hack) in phone info lol.

I was hoping to get STRONG pass, but nope. :-/

Could this hack be useful maybe for the future or to fix something else like DRM L1 or whatsoever?
[Magisk] Stаr:
Turns out my Lineage rom tries to spoof a burned fingerprint with a built in ih8sn that also trips prop detection in other apps due to predating the current resetprop findings. I managed to get rid of it by renaming /system/bin/ih8sn, /system/etc/ih8sn.conf and /system/etc/init/ih8sn.rc to .bak. Now I get "Normal" on NativeDetector without needing Shamiko, but I wonder if this could be suppressed more elegantly with something like this commit on PlayIntegrityFork or if that's only possible with proper apps.

I remember a few pages back someone having a similar issue with ArrowOS, maybe it was something like this also suppressible without recompiling the whole rom.
[Magisk] chiteroman:
Check this: https://github.com/chiteroman/kernel_xiaomi_vayu/blob/u/fs/proc/cmdline.c

🤗
[Magisk] Umgak:
What cursed Lineage ROM are you using that bundles ih8sn? That's something that's supposed to be an unsupported optional.
[Magisk] xcl1pse:
Bruh PIF also 😂 very based decisionView attachment 6053283
[Magisk] osm0sis:
Crazy idea... Everyone just stop using Telegram? It's a toxic dumpster fire there full of childish bullsh*t and always has been.

Having a 24/7 team of moderators with conduct rules and posting guidelines is kinda nice to have now, yeah? Welcome back to XDA.
[Magisk] iMoc:
Right in front of my eye 😂
[Magisk] simonpunk2013:
XD, mine is patching seq_read because somehow saved_command_line doesn't include "androidboot.verifiedbootstate" and "androidboot.vbmeta.device_state"
[Magisk] HippoMan:
But then we'll miss out on all those cat pix! :)
[Magisk] Stаr:
Unofficial LOS based on A11 for Redmi 4A with kernel 4.19+KSU from Mi-Throrium. It's a old secondary phone that I mostly use as a IR remote control for my old TV :p. But I also mess around modules and stuff before putting it on my main phone.
[Magisk] Earth-Chan:
Sm-A546E Here. I pass the first 2 verifications but the strong one doesn't. I have tried with shamiko, with different Pif modules. With different advice in the first threads and nothing. Since there are 400 or so pages, I wonder if anyone has managed to pass the 3 verifications with an a54 5g.
[Magisk] Earth-Chan:
OK. I've reached the part where it says this was patched 😢🫡. The good thing is that I can now leave my phone alone.
[Magisk] V0latyle:
Passing STRONG should be impossible if environment is not pure stock and locked.
[Magisk] rogers11:
You should always bear in mind where Telegram originally came from. That's why I can't even begin to understand why people use it at all.
[Magisk] Fishawy:
Today we lost what, 4 or 5 vital Github repos? All because of childish behaviours and unmoderated Telegram trolls.

What's ironic is that they've always combined their comments on XDA with a sh*t emoji, been doing it for years.

Boy did the odds change.
[Magisk] simonpunk2013:
Just my assumption, you have to at least do the following:

1. Enable bootloader spoofer on gms process(with unbanned keybox) because it needs a valid cert chain.

2. Unblock droidguard process, I think droidguard and device with hardware-backed attestation is a must to pass strong, take my oneplus5 as example, even I relocked the bootloader it doesn't pass strong as well, only device integrity, so it is likely due to the use of aosp private key and the lack of hardward-backed attestation.

3. patch '/proc/cmdline' for the bootloader status as chiteroman said, seems droidguard also has permission to read '/proc/cmdline'? if you are using kernelsu, just add the log yourself to the syscalls and see what else files the droidguard/gms reads.

4. Also the '/dev/block/bootdevice/by-name/frp' partition, seems the last bit of this partition will be set to 0 if your device is unlocked, it may correspond to the prop 'sys.oem_unlock_allowed', if droidguard/gms has access to the partition directly, I think you may need to spoof it as well.

5. A working fingerprint with other proper system props spoofed.

You can log the props in pif module to see what the droidguard and gms process read, and try to spoof them all.

Lastly, I am just waiting someone finally open source the strong code:coffee: and for the rest we may just need to deal with finding valid keybox if google bans it :censored:
[Magisk] GN-z11:
I've been shouting this one on Mi10T forum. Yet some "dev" say they prefer using TG etc. It's so annoying as TG isn't even meant to be a replacement or at any level of replacement for XDA.
[Magisk] rogers11:
Telegram is nothing more than a melting pot of weak people who don't realise how much they are being manipulated there.
[Magisk] GN-z11:
Mentioning that, they even said XDA's dying as most "devs" are using TG instead now. Inline with harassment and things, what I hate is also how they have no law and the days of "opensource" is just gone there. Goodluck finding any device sources in every ROM distributed there.
[Magisk] sawdoctor:
Think an official xda app again would help
[Magisk] onegabriel:
Even on signed non stock ROMs that allows bootloader relocking? Is "pure" really reserved for manufacturer ROMs only?
[Magisk] chiteroman:
When you lock the bootloader with custom rom, it uses custom key. Verified boot will be self signed and it should NOT pass Strong.
[Magisk] V0latyle:
To expand on this...

The root of trust (key used to sign firmware) is the first step in hardware backed verification. Only the OEM key is trusted, in terms of an unbroken chain of trust. You can install a custom key, but since that key is untrusted by the OEM or Google, it's of little use beyond the normal functions of a bootloader lock - used to verify the firmware for authenticity.
[Magisk] HippoMan:
In case you didn't notice, the PIF TG group is closed again, and it now looks like it might remain more permanently closed.

From that group ...
[Magisk] TotallyAnxious:
Unless you mod the old app to work this is the best you're gonna get currently https://xdaforums.com/t/app-5-0-relabs-unofficial-xda-client.4623759/
[Magisk] immortalwon:
Whatever happened to the concept of sticks and stones?

Be careful what you believe in those telegram groups, I find it hard to believe a few people, in an obvious and coordinated manner, leaving a few emojis of a clown, is enough to hurt the feelings of a smart and dedicated group of people.

Regardless, their work is and will always be appreciated to this point in android history.

Someone else may need to continue the work or maybe Google will be implementing strong soon, so it will be meaningless.

Perhaps they wanted a way out of this development scene or made a deal with Google

The real truth is somewhere in between
[Magisk] TotallyAnxious:
I think we need to take in to the account the culture the devs come from. I haven't seen anything that would offend me, and I can be quite sensitive and reactive, just check my post history. But I could see how people could help offended if from another culture. My understanding is the devs are of an Asian country. Maybe mostly Taiwanese. But my point is that people of different origin have different sensitivities.

Even people of the same culture can have different sensitivities.
[Magisk] poulopoulosa:
IMHO Opening up a telegram group with free coments where random people can join is like looking for trouble. I believe devs need to use telegram channels only to release updates without giving a platform to people with childish behaviour, hate, transphobia, etc. I went over to that channel and it was a waterfall of negativity it made my stomach turn.

People can say anything they want without foundation in telegram or anywhere, unless they post here on XDA. Here you can see the history of the person, their posts and how credible they are. I haven't experienced here any negativity to the level I did into those telegram groups. Dev's should keep it simple and use forums, I believe it would be best fo their mental health.

When someone demands something and are lazy to work, everyone tells them off! However, I have seen so many people helping each other here, IF they are willing to work too. We dont do what we do for money. It is not a service, it is an exploration we do together which is what makes it fun.
[Magisk] Retrial:
A fixed xda app already spreading around privately.

Please sign this petition if you like:

📝Petition for XDA Fixed/Modded App🗳️

We did it guys!!! Check out the Admin's statement. The fixed app can be found here! Thanks dr.ketan 🫡 🗳️Users please vote above! [POLL ENDED, OUR GOAL WAS ACHIEVED] 💡Reason of petition: Let's start with this: XDA is now owned by Valnet and as...

xdaforums.com

ReVanced patch for xda app would be another solution.
[Magisk] HippoMan:
So far, 100 percent of the votes on that position are "yes".
[Magisk] TotallyAnxious:
It had 39 votes before I just voted. I doubt mods will take action with that few. But mods, please prove me wrong. If I hypothetically already had the modded app, I'd be telling you how much better it is than using the XDA website on Android. But I may have been asked to not discuss the matter, so this is all hypothetical 😉

All I've done so far is suggest a modded app could be a solution.
[Magisk] Retrial:
Moderators want to allow it. Some mods already using the fixed app like I do.

One admin still persist and require the dev who fixed the app to reverse engineering it even further to make it "unofficial" changing logos/names. It's like he thinks the app is open source and things can be changed easily.

I hope soon or later they understand the fixed app is gonna affect only positive the xda forums and the traffic into it and it's one of the reason to stick the community into xda rather going to telegram groups.

Keep voting. 🤞

Edit: Weeeee! Seems your vote had an impact, we did it guys! Check out the latest news! 🥲

The fixed/modded xda app can be found here, thanks to dr.
[Magisk] TotallyAnxious:
I don't want to call that dumb, but...
[Magisk] dmenezes:
Was that with Gimp or MSPaint? 😆
[Magisk] sawdoctor:
I know there's an unofficial app and there's the relabs app. My point was without an official xda app it's not surprising that people started to migrate to another medium ie telegram
[Magisk] sawdoctor:
I saw the original screenshots and it wasn't clown emojis it was extremely vulgar language about them Thier mother and also sexuality. If someone had written to me like that especially about my mother yes I'd be fuming
[Magisk] sawdoctor:
Be over the moon if it some how made it's way to my inbox 🤞
[Magisk] TotallyAnxious:
I promise you my posts have not been directed at you in anyway that implies you were unaware of something. Honestly all my comments today have been directed at the community, but your posts raised points that made me feel the need to comment.

1. Bring attention to the fact the XDA app can be modded to work. I honestly didn't know who modded the app. I just have access to it from a trustworthy source who asked me to not share it. Now I know it's from @dr.ketan because my post also allowed for @Retrial to bring up their petition. Which I was unaware of, plus another XDA app I was also unaware of, that's mentioned in the petition.

2. Bring attention to an open source alternative app. Which could bring more developers to help with its development. If they were unaware of it.
[Magisk] TotallyAnxious:
I'm a heathenous American 🙃 My mom can be a *****.

But I also saw those posts. Wouldn't offend me, but can totally see someone of a different culture, even within America, getting offended by that.
[Magisk] HippoMan:
The sender of such a message would have to be living in a delusional fantasy world if they thought that there is no chance that any recipient would be offended.

Using language like that to insult another person is indeed a conscious attempt to cause that person to feel offense.
[Magisk] Lagartixo:
try put “pif.json” on /data/adb and clean data of “play services” and “play store”

P.S.: avoid making public from where you extracted build.prop to make your personal fingerprint
[Magisk] rodken:
In addition to clearing the data of Play Services and Play Store. One should also clear the data of the Wallet app.
[Magisk] HippoMan:
I just noticed that PIF TG chat has now been re-enabled.

Let the degeneration begin once again!
[Magisk] ScubadooX:
I got a valid fingerprint on my Google Pixel 4 after three tries. I got a valid FP for my Xiaomi Redmi Note 9 on the first try. Both FPs are still working about ten days later.
[Magisk] sawdoctor:
No offence taken whatsoever, we both want the same thing 👍👍
[Magisk] HippoMan:
... and cat pix are now returning.
[Magisk] okij:
So much for "Chat will remain closed." 🤣

Oh well, let's just start posting cat pix here too: 🐱🐈🐱🐈🐱
[Magisk] xSnowLeopardx:
Me who barely knew a TG existed: :giggle:
[Magisk] purgy:
Ignorance is indeed bliss
[Magisk] ace2nutzer:
Yeah, I'd already use this cmdline hack.

I use the following fake flags without any issues:

proc_cmdline_set("androidboot.verifiedbootstate", "green");
proc_cmdline_set("androidboot.warranty_bit", "0");
proc_cmdline_set("androidboot.fmp_config", "1");
proc_cmdline_set("androidboot.flash.locked", "1");
proc_cmdline_set("androidboot.vbmeta.device_state", "locked");
proc_cmdline_set("androidboot.veritymode", "enforcing");

With those flags + this init.rc:

on property:sys.boot_completed=1
chmod 640 /sys/fs/selinux/enforce
chmod 440 /sys/fs/selinux/policy

I get BASIC pass if I don't flash Magisk.

With Magisk, it doesn't pass anything until I install your module.

My goal is to pass also DEVICE without Magisk .. because some of my users want to use my kernel without root.
[Magisk] makeyourself:
I wish it didn't exist. I've basically said this in another thread already but what is the point in Telegram groups in the context of Android modding? It's basically a privatisation of something open and public like XDA. It may help certain individual developers gather "fans" but that's about it and it's at the expense of all of these sort of very silly shenanigans and the drama which has occurred recently. It's also at the expense of everything being discussed openly, publicly and intelligently. And for that yes, once again, I think we'd be a lot better off without it.
[Magisk] ShaDisNX255:
Well I can't speak for other people but personally I use it over XDA when it comes to testing and getting logs.

TG allows me to log in on PC and not have to worry about my device being connected (like WhatsApp used to be in the past). It also allows you to upload higher sized files than XDA which is very important when you're doing multiple tests and doesn't have a cooldown after writing a message. And most recently well the XDA app doesn't have push notifications so that's another +1 TG has over XDA. The ability to communicate instantly when you're in a bootloop is just so important too.
[Magisk] borisSweden:
TG is like Discord, chaotic. I remember the during the whatsapp crisis where the telegram😎f***bois kept saying "use TG". It sucks to use it to find information, its a live chat social media.
[Magisk] acwcanada:
Can someone give reasoning why v15.1 (v14.6) FP not getting "banned" for such a "long time"? I am just curious.
[Magisk] osm0sis:
Either extended holidays or taking a break to work on something else. It definitely should be at critical mass with the 44,000 15.1 downloads, people using older versions with that same print, plus Xiaomi.eu it must be well over 50,000 users...
[Magisk] Stillhard:
in Bahasa, TG (Tante Girang) = M.I.L.F :LOL:
[Magisk] Nergal di Cuthah:
I feel I've learned two things from this post. Bahasa is the formal language of Indonesia and that translation can go wrong or so so right depending.

:D

:love:
[Magisk] sawdoctor:
Maybe Google is about to ban all mismatched fingerprints with an update and screw us all
[Magisk] m0han:
How long will it remain private and confined to the hands of a few?
[Magisk] V0latyle:
Not saying this as a mod, but as someone who comes here for news/updates on PIF...Can we please keep the XDA app discussion to the petition thread? There is an insane amount of traffic in this thread as it is.
[Magisk] V0latyle:
Doubt it.
[Magisk] guniens:
Hi all!

I've been out of the loop for a while as I just discovered both LSposed and SafetyNet Fix are discontinued :oops:.

I would like to migrate to either PlayIntegrityFix or PlayIntegrityFork from Displax's SafetyNet Fix, what's the right way of doing this?

Thanks in advance to anyone and have a nice day!
[Magisk] V0latyle:
Use @osm0sis PiFork, and @TheFreeman193's PIFS to pick a print. His script picks a print at random so you'll have to try a few times before you find one that works.
[Magisk] guniens:
First of all, many thanks!

Can I simply uninstall Displax's module in Magisk, reboot and do the above steps?

Clearing Play Services/Store/Wallet needs to be done once the whole process above is done right?
[Magisk] Umgak:
PIF will auto remove Displax if detected, but otherwise yes, that should be sufficient. The PIFork readme has a list of steps for after you get your successful PI verdict, to restore wallet tap to pay function and device certified status.
[Magisk] guniens:
Think I've understood!

Still a bit confused on obtaining a valid fingerprint via PIFS but nothing impossible, will disturb you again for help eventually.

Thanks again!
[Magisk] playaz44:
From today, no PIF works, tested on Pixel 7 Pro, Pixel 6 and Xiaomi 12t, tested over +50 different pif, various modules (forks and original from this thread) and generated pifs from GeneratePIF. None passes device integrity.
[Magisk] osm0sis:
All my devices are still working on my fork with my found prints. 🤷‍♂️
[Magisk] PatrickJK:
still working for me using osm0sis' fork with the print i've been using for over a month
[Magisk] fbirraque:
Me too
[Magisk] xSnowLeopardx:
Used GWallet successfully today. Full month + some change of using the same found FP and @ v14.4.
[Magisk] linuxares:
osmosis + found pif works great so far
[Magisk] djcsurf:
My pif still working using v14.0 however in preparation I have made 5 fp's using osm0sis script and will test with his latest PI fork when the need arises. As it ain't broke...
[Magisk] dr.ketan:
This is because of huge effort you put on and Thanks to our mod team who always inspirational and the reason keeping me to stick to XDA rather than private social media like TG (we witnessed drama over TG recently) which never going to replace XDA where neutral mod team always protect interest of members. Hope with mod xda app, it will be again more convenient to adhere with our beloved xda community.
[Magisk] wfred:
Check your DM and let me know
[Magisk] GabbyWC:
I wonder if this news has something to do with the public fingerprint bans coming to a pause in recent weeks.

Google confirms it just laid off around a thousand employees

Engineering and Assistant teams were impacted too

www.theverge.com
[Magisk] frasca61:
Today I have been using my first fingerprint for a month! Everything is OK !!!
[Magisk] shadowstep:
Maybe the employee banning the fingerprints got laid off... good riddance, I say. :p /s
[Magisk] TheRomRooster:
yup, osm0sis is pretty much 4-5 weeks on the same Pif for me now
[Magisk] IcecalGamer:
Hey there. I'm on a xiaomi note 12s and i'm not passing Strong_integrity.

Unlocked BL. Rooted Magisc. Hidden magisc. Reboot. Enabled Zygote + deny list (added the req to deny list). Reboot.

Installed the 15.1 Fix. Reboot. Cleared (denied apps data). Reboot.

What did i miss? I was out of the Android game for Years and i'm rrrrusty.

Edit: I'd appreciate some kind and patient soul that would point me in the right direction.
[Magisk] chiteroman:
Pages · chiteroman/PlayIntegrityFix Wiki

Fix Play Integrity (and SafetyNet) verdicts. Contribute to chiteroman/PlayIntegrityFix development by creating an account on GitHub.

github.com
[Magisk] sethieplayz:
You can't pass strong unless you're on stock FW and locked BL
[Magisk] IcecalGamer:
Ah! Thank you for that. Had no point of reference if the posts that showed green ticks passing, we're still up-to-date, possible or one-offs.

Didn't expect such prompt responses, thank you again.
[Magisk] Lagartixo:
confirm that the pif.json file is in the following format (chiteroman):

{

"PRODUCT":

"DEVICE":

"MANUFACTURER":

"BRAND":

"MODEL":

"FINGERPRINT":

"SECURITY_PATCH":

"FIRST_API_LEVEL":

}
[Magisk] purgy:
Also be aware of the difference between tab and multiple spaces, if you are copy pasting stuff info your pif.
[Magisk] badabing2003:
If doesn't matter in json, this is not yaml
[Magisk] ace2nutzer:
I wasn't able to pass DEVICE using the stock fingerprint from Samsung,

with / without pif file.

What i did:

i've just edited the pif file from latest module 15.1, using the props from build.prop (official stock ROM).

Then installed the module and rebooted the phone.

I get DEVICE pass only with the Acer fingerprint.

Any hints?
[Magisk] simplepinoi177:
Depends on what kind of "Samsung" -- you may need to lower FIRST_API_LEVEL (to at very least below 33)

You should consider using the scripts/tools that process the build.prop as it makes sure format and such is correct (spaces, tabs, commas, etc.) instead of manually copying values (just assuming this is what you did from the simple way you describe).

The module wasn't installed already?

Well, it's because the Acer fingerprint is established as passing, your Samsung isn't -- whether it's too new and needs modification, or it just doesn't pass as a viable fingerprint (it happens, which is why the search & hunt for one is such a tedious process). But also, are you making sure you're putting the custom pif.json in the right folder and/or removing the embedded fingerprint/.json (I believe this is how it works; sorry, I hadn't used chiteroman's PIF since before he added the option for custom .jsons and have since been using PIFork)...
[Magisk] trevtdogg:
i'd suggest just keep using the acer fingerprint then :)