yashsingh1/xdaforums huggingface dataset:
[Magisk] threetwotwo:
Hmm I dont know it works for me (else I wouldnt be able to use Whatsapp). Maybe if you meant for passing device integrity? Well thats a lot of versions to downgrade. 3.8 passed device integrity before recently for me so I don't think downgrading will do much

Whatsapp only kicks you for unlocked bootloader only if your account was banned previously (mine was banned for using unofficial Whatsapp for 24hours), my account got flagged after that so I can't use Whatsapp on a modified phone. Well at least they tried to until I spoofed my bootloader xD
[Magisk] HippoMan:
Let's start posting lots of cat pictures and giving personal insults to one another.

Then, this thread will be as good as Telegram!
[Magisk] Zytrel:
You're looking at it the wrong way. Google doesn't care about YOUR security. Lose your physical card, your problem. Get your Wallet hacked, Googles problem. The Bank will blame Google for advertising a service as "safe". Secondly, Googly apparently made it their priority to just cause as much hassle for any custom rom users (even unrooted ones) to use their apps.

P.S.: Greetings go out to that blonde Google girl at Switzerland. As you're reading along, please have a heart and leave at least some backdoor open for us poor root guys. Thank you. ;)

Regards,

Zy.
[Magisk] V0latyle:
There's been a lot of OT but it's ultimately up to the thread owner how much OT he allows
[Magisk] shoey63:
Looks like it's pretty much open slather 🙄
[Magisk] trevtdogg:
really? there's nothing in the xda rules that allows staff and/or mods to restrict off topic posts?

I would have thought you have the ability to delete / warn / punish (as suits the circumstances best) off topic comments no matter what the thread owner wants.
[Magisk] osm0sis:
And the default should be enforcing it, not NOT enforcing it, if the thread owner hasn't commented...
[Magisk] changhuapeng:
Honestly, there's a reason we come to XDA. If we'd wanted cluttered off-topic chats, we would have joined the various PIF telegram channels instead.
[Magisk] osm0sis:
The OP of this thread doesn't say anything asking mods to allow OT posts, so therefore OT rules should be getting enforced here.
[Magisk] shadowstep:
Spoiler content hidden.

Greetings! I don't usually post in this thread (and prefer lurking in the shadows, no pun intended), but I had something to say...

As @V0latyle has mentioned, the tolerance of off-topic posts depends on the thread owner, and hence under the usual circumstances, off-topic chatter is only removed at the request of the thread owner. However, please understand that this thread is far more significant right now (and has been for a while, I'd say, with that regular banning of fingerprints).

In addition, the thread owner isn't very active here, and so while there hasn't been any objection to off-topic chatter from him, I think it is in everyone's interest that we actively try and avoid off-topic posts here. Sure, a few off-topic posts here and there never killed anybody (in fact they can sometimes lighten the mood, and I'll admit I've had a chuckle or two here and there reading them), but if given a choice, I'd prefer not to read such posts in this thread especially.

It's anyway difficult to guide new users here with the sheer number of pages and information that's mostly lost in between them; off-topic posts just make this task more complex.

So please consider this as a friendly request... not from a moderator, but from a user who reads the thread daily as a root enthusiast, which I'd say we all are. (y)

Thanks for taking the time to read everyone! Back to the topic now... Spoiler content hidden.
[Magisk] wrongway213:
All due respect - as a former mod myself, I strongly disagree with the notion that ALL off-topic is at the thread owner's discretion. XDA Rules do, too.

Source: XDA-Developers FORUM RULES

A large preponderance of posts in this thread break Rule 1 and/or Rule 5.

1. Search before posting

"Use one of our search functions before posting or creating a new thread. Whether you have a question or just something new to share, it's very likely that someone has already asked that question or shared that news."

Moderators shouldn't be allowing blatant, repeated violations of Rule 1. This is *not* at OP's discretion - it's a site wide XDA rule that's not enforced here.

5. Create a thread topic or post a message only once, this includes external links & streaming media.

"As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.

You can bump your unanswered question once every 24 hours

Duplicate threads and posts will be removed

Always post in an existing thread if a topic already exists, before creating a new thread.

Use our search function to find the best forum for your device.

Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.

Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed."

People are allowed to make multiple posts in a row asking inane questions or offering totally useless anecdotes about things that help no one , ie "My fingerprint broke" - things they would have known weeks ago if they followed Rule 1 in this thread. Again, this is not at OP's discretion - these multiple, useless posts that clutter the thread should be handled as stated in Rule 5 by moderators.

TL;DR OP has a say about OT, but OP does *not* get a say about whether XDA 's Rules are enforced in his thread. Yet, mods aren't enforcing the Rules we agree to by signing up for XDA. Why not?
[Magisk] mrjuniork:
Thanks so much for quoting some of our great rules and therefore making it easier for newer members to memorize its important content.

Cheers for that 👍🏻

As a former Mod, you are surely aware, that of course not all off topic posts are at the sole discretion of the thread owners. We are monitoring a vast amount of threads and forums and we are therefore in a constant chain of communication 😊

So a lot gets taken care of, without the OP even being aware of it.

My highly esteemed peer @shadowstep has already spoken wisely about this situation and I fully agree with that.

Now, the following message is definitely coming from a moderator's perspective:

That being said, from now on, no need for any further complaints about off topic posts, which will be removed by the Moderators (as agreed upon with the OP), after being spotted.

As a user, if you come across a post that fits the "off-topic" description, pls be so kind and use the report button. No need to post an off topic post about another off topic post being off topic.

Thx for you understanding and happy FP hunting 🤞🏻

Cheers,

mrjuniork
[Magisk] chiteroman:
I'm releasing my project to pass Strong and have a valid certificate chain on system level:

GitHub - chiteroman/FrameworkPatch: Modify framework.jar to build on system level a valid certificate chain

Modify framework.jar to build on system level a valid certificate chain - chiteroman/FrameworkPatch

github.com

Enjoy :)
[Magisk] Vision:
You're a Genius.

I have Xiaomi Poco X3 NFC A11 MIUI 12.5

One question if i make all this, after can with Magisk/Kitsune mirror only the mod framework.jar to /system/framework/ ? without need to decompile the entire rom and compile and flash
[Magisk] HippoMan:
Oh, so you *finally* allowed yourself to publish this, after so much time of alluding to it without providing anything concrete.

Now we can examine it, test it, and possibly provide enhancements and any fixes we might discover as being needed.

Of course, this opens the door to the Googlefrinchians performing the same kind of examination and then figuring out how to render it inoperable.

Let's see where this leads.
[Magisk] Vision:
I hope Google can't block and touch this until now, is because we mod our framework.jar , at least on devices with Android 10-12 which they do not receive update anymore
[Magisk] Vision:
Until now i did that step and figure out the info

Now using jadx open framework.jar and check these classes:

View attachment 6078124

Now i'm waiting for in progress
[Magisk] Slim2none4u:
Now if someone can get this to work via script on the device :)
[Magisk] Vision:
android.security.keystore2.AndroidKeyStoreSpi

I think we must each one on his own, compile the framework.jar (or maybe if the same device with same Android and share the mod framework), or I'm totally wrong

because @chiteroman say search for

android.security.keystore2.AndroidKeyStoreSpi

But mine is android.security.keystore.AndroidKeyStoreSpi
[Magisk] sawdoctor:
Not sure if I've missed anything the thread has been so convoluted but didn't chiteroman say it only works with a broken Tee? Which would limit it's usage
[Magisk] Vision:
I have asked this question and the answer (little confused me @chiteroman say with a unbanned keybox)

View attachment 6078146
[Magisk] wrongway213:
Trying to ascertain if the latest Play Integrity bans have caused OTAs to fail for unlocked users is clearly relevant. This is a thread about fixing Play Integrity - part of this from the start has been tracking what things Google is directly tying to Play Integrity (such as the recent change from RCS requiring only basic to now requiring device integrity). Very much on topic.
[Magisk] Spartacus500:
I have Android 9.0 and framework.jar deodex, I unpacked it, but I don't see these lines to edit 🤷
[Magisk] Vision:
I do this with jadx, open the framework.jar and go to android/security/keystore/ and i choose AndroidKeyStoreSpi

Maybe is different on Android 9, I have A11

View attachment 6078152
[Magisk] osm0sis:
Last I checked latest bak/smali and apktool don't function on device when dexed anymore due to Android's dalvikvm not supporting some of the newer Java code involved. And unfortunately for ROM framework APK patching you absolutely do need the latest.

That's why my old APK-Patcher PoC project ended up stuck on older versions:

tools: downgrade to last working apktool, update to last working bak/… · osm0sis/APK-Patcher@3e3a764

…smali

github.com

If someone wants to give it a try anyway, the process to dex a jar is pretty straightforward:

[DEV][PROOF OF CONCEPT] APK-Patcher - Easily Mod APKs from Recovery [Flashable Zip]

APK-Patcher -- Flashable Zip Template for Modifying System APKs On-Device from Recovery APK modification can be a tedious task. If you want to provide modified APKs you copy it to PC to decompile using Java applets like baksmali and apktool...

xdaforums.com
[Magisk] ronlkh1965:
Hi is there any solution for the attached integrity failed? Tqvm
[Magisk] majorfigjam:
That is more of a hiding root question than a play integrity question, as you are passing 2/3.

The Singapore government no doubt has its own reasons and ways for enforcing security, but have you tried the usual methods of hiding root? Shamiko. HMA etc?
[Magisk] HippoMan:
It's been mentioned probably hundreds of times in this thread that the only way to guarantee "Strong" integrity is to run with no device rooting or modding and with a locked bootloader.

One or more people have been working on ways to try to force "Strong" integrity on certain groups of otherwise modded phones, but it's not clear yet how workable or reliable this would be.
[Magisk] HipKat:
I keep seeing people requesting STRONG but I have yet to see a need for it myself or in the threads and devices I follow
[Magisk] trevtdogg:
does the strong integrity method still require an un-banana-ed fingerprint, or does it work without the need for a donor print at all?

if the later, then I can see that being a lot more convenient for people to use, even if there's no direct actual need for strong integrity as such.
[Magisk] osm0sis:
PIFork v8 is upon us! :p Thanks for testing, all! 🙌
[Magisk] Spartacus500:
In my case, in Android 9.0, the AndroidKeyStoreSpi file is located in smali classes2, but the line "public class AndroidKeyStoreSpi" not found... 🤷
[Magisk] Utini:
Any reason why your autopif.sh script is not included?

And thanks for the update!

Edit: I know that it is included in the readme Ressources but I meant as a fixed part of the module to e.g. Auto-Check on every reboot or anything like that?
[Magisk] KMohZaid:
my jar file loaded those classes from same dex file mentioned in guide so until unless someone spots different in there dex file we can have a automated scripts that run in termux (and compiling smali, can be done on github workflows)
[Magisk] KMohZaid:
if we cant use lastest bak/smali in mobile then we have to do it in google colab(not good idea but useful for people wiht no pc/low end slow pc).
[Magisk] mkcs:
It seems that v8 is conflict with Shamiko😶
[Magisk] esatch:
All fine for me.
[Magisk] mkcs:
After the upgrade, Zygisk-Next reported that its module files were corrupted. Upon reinstalling Zygisk-Next and restarted Shamiko, it shows unsupported environment. BTW, any idea when device integrity failed? I don't think the fingerprint was banned as it has been working fine for months
[Magisk] CZ.Kostra:
Since I am one of the FP users from Xiaomi.EU, I created a task

FP XEU Checker

for Tasker that checks the new version of XiaomiEUModule (injector). When XIaomi.EU releases a new version of the injector, the task extracts and places the FP into the PIFix by chiteroman or PIFork by osm0sis modules (bak is created from the original json).

If there is no new injector, task check the status of Google Wallet.

If you delete the 'XEUInjector.rss' file in the working directory, task extracts the injector and places the FP again.

This task uses autopif.sh by osm0sis to extract the fingerprint and GPay Checker by Bonoboo to check Google Wallet status.

I run this task before I go shopping so I don't get surprised at checkout. 😁

Maybe someone will use it.

Edit:

-fixed droidguard killing, thank you niko26

-treated the validity of external links to 'rss' and 'sh' files

-modified progress check

-file operations will be performed by Tasker or Shell (switchable)

-changed default working directory (unified with APK)

-created APK in Tasker App Factory from attached TSK (no need Tasker)

-changed link to 'autopif.sh' (osm0sis moved it from XDA to GitHub)

-created v2.0 - added GUI and atomatic mode

-v2.1 - fixed minor bugs

-v2.2 - added removal of custom 'pif.json'

-v2.3 - test GWallet after each unlock

-v2.4 - added ROM info, fixed minor bugs

-v2.5 - changed permissions check, added swipe control

For APK:

The working directory is '/storage/emulated/0/FP_XEU_Checker'.

If you are going to export task as application, I recommend renaming task in Tasker to 'FP XEU Checker' (remove version number) for reasons of work paths.

That the aplication to work, you need to give it ROOT, DRAW_OVERLAYS, WRITE_EXTERNAL_STORAGE, READ_EXTERNAL_STORAGE permissions and enable notifications (you can disable the 'Monitor' and 'Placeholder' notification groups).

For 'auto mode' to work properly, enable autorun, background running and turn off power saving for this app.

Spoiler content hidden.
[Magisk] Utini:
Nice, anything else that you use Tasker for in 2024 with A14.
[Magisk] borisSweden:
Weird thing is that Google Messages without Google Play or Google Services downgrades to the minimal RCS UP standard, for example no iphone reaction translation. Why I know this is because that I backed up a RCS enabled Google Messages from a rooted Gapps enabled phone and transferred it to a microG phone. It worked until November, after that it doesn't work.

Registering RCS has a Google dependency, its a DRM. Sending messages is just FCM that Signal, WhatsApp, BadTG, Allowed, Duo, Hangouts uses, RCS can work without G-Apps but its tricky.
[Magisk] mkcs:
I wonder if it can be edited on the phone directly using APK editors such as NP Manager
[Magisk] CZ.Kostra:
Tasker is a powerful tool. One of the reasons I'm here. 😁
[Magisk] sawdoctor:
Shamiko doesn't play nice with zygisknext. I didn't even have zygisknext enabled just installed at it broke shamiko for me. Had to completely uninstall zygisknext to get shamiko working.

I know it might work for some people but there's a definite issue somewhere with the 2
[Magisk] Spartacus500:
Please look my file, i don't found line to edit 🤷
[Magisk] mkcs:
I uninstalled the play integrity fork v8, Shamiko and Zygisk-Next, and then reinstalled them one by one and they finally work fine together. I think the upgrade of PIF v7 to v8 caused the conflict. However, device integrity still fails. I'm going to check the fingerprint validity🤔
[Magisk] Vision:
Also with APKEditor-1.3.6.jar can decompile source code (smali) from framework.jar quickly and mod the .dex and after building the dex again
[Magisk] Vision:
What line you mean ?
[Magisk] asisandroid:
Does this strong method if it actually works still require a private key or does it work or is it just a joke I did not realise
[Magisk] Vision:
This one little confused me @chiteroman say with a unbanned keybox

View attachment 6078397
[Magisk] Spartacus500:
/* loaded from: classes3.dex */

public class AndroidKeyStoreSpi extends KeyStoreSpi

This line not found my file 🤷
[Magisk] osm0sis:
As the FAQ and the autopif.sh blurb in the README's Resources list states, I still don't think using autopif.sh to have everyone on the same print is the correct end goal here. More statistically distributed usage should still be better in the long run and I still encourage everyone to find their own fingerprint when they have time.

PIFork is a totally normal Zygisk module, just like original recipe PIF, and updates like a normal module. ZygiskNext is the issue here. Shamiko has also always been extremely finicky any time you disable/reenable it, generally needing a full uninstall and reinstall instead. Either way, nothing to specifically do with PIFork.
[Magisk] Vision:
Have you open the framework.jar with jadx-1.4.7 ?

View attachment 6078403
[Magisk] Spartacus500:
I don't know how to do it, so I'm sending my file
[Magisk] Vision:
You have it, just you look in wrong way

View attachment 6078414
[Magisk] Bladius:
why has there been no auto update option for some time now?
[Magisk] Vision:
@chiteroman Search for "newApplication" methods and before the return operation

if have 2 ?

1. .method public static whitelist test-api newApplication

2. .method public whitelist test-api newApplication
[Magisk] Claus….:
Anyone that made it work?
[Magisk] Vision:
I'm in the Instrumentation.smali instructions.

I hope do it right 😂🤣

View attachment 6078562 View attachment 6078556

Edit: I'm stuck here

View attachment 6078487
[Magisk] RichyRicho:
So from my understanding of the last couple of pages, and this link, https://github.com/osm0sis/PlayIntegrityFork/commit/f99696e8945a3aae19ee681a86be51d9ce43f1c4 ,

pickaprint.sh is now pretty much EOL/takes a huge amount of time to find a working print?

And autopif.sh is now the main way forward?
[Magisk] mkcs:
The concept seems to integrate the smali of the patch to the decompiled framework.jar, and then finally compile again to get the output.

I did it on the mobile phone using an apk editor. Anyone else experienced could confirm if I modified correctly?
[Magisk] Vision:
What you do in this step ?

View attachment 6078507
[Magisk] CZ.Kostra:
It's a solution until you find your own FP. Now it's much more complicated because PIG has banned a large number of fingerprints.
[Magisk] mkcs:
I edited on the phone. After the modification, I just compile the dex files like editing an apk
[Magisk] Vision:
Yeah i get this, and in the Replace {API_LEVEL} with the Android version you are running. what you do ?
[Magisk] mkcs:
I totally ignore them. As modifying apk or dex files on a phone are similar to editing a text file, what I did is import the smali of the patch built on Windows, add new lines to modify and save/compile to get the modified .jar:rolleyes:

Build from source code is attached.
[Magisk] Vision:
Mine confused because have .line xx bewteen and need space?

View attachment 6078561 View attachment 6078553
[Magisk] mkcs:
Things I am not sure is the Instrumentation.smali. I have found 2 methods named newApplication where one is static and the other one is not.
[Magisk] Vision:
Yeah exactly, i ask about that @chiteroman before but still no answer.

And whick you mod?
[Magisk] Vision:
Is this right? @chiteroman @osm0sis @zgfg @pndwal . I ask you because you are the great minds

I'm little confused because have .line xx bewteen and need space?

View attachment 6078564 View attachment 6078565
[Magisk] RichyRicho:
I have now tried - https://xdaforums.com/t/module-autopif-next-play-integrity-fix-fork-safetynet-fix.4652252/ - but I only get Basic on this :(

Any got any tips for me?

Edit: Got device integrity now :D
[Magisk] osm0sis:
Read more.

All of pickaprint/PIFS was banned on the Leap Day Mass Ban.

PIFS/README.md at main · TheFreeman193/PIFS

A collection of build properties for the PIF module - TheFreeman193/PIFS

github.com

"AutoPIF Next" stole the "autopif" name from my script. I recommend you use my actual script. It's linked under Resources here:

PlayIntegrityFork/README.md at main · osm0sis/PlayIntegrityFork

Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props - osm0sis/PlayIntegrityFork

github.com

But maybe read my whole README and the FAQ too while you're at it.
[Magisk] Vision:
And what about this ?

Open this project in Android Studio and change EC and RSA keys, you must provide keybox private keys. Compile as release and copy classes.dex file.
[Magisk] fbirraque:
Upgraded from your RC #190

Everything seems fine as before.

Poco F3, MIUI.eu 14, Android 13, Kitsune 27001, LSPosed, HMA

Spoiler content hidden.
[Magisk] Vision:
Anyone until now make the @chiteroman project to pass 3/3 with success ?

And what about this ?

Open this project in Android Studio and change EC and RSA keys, you must provide keybox private keys. Compile as release and copy classes.dex file.
[Magisk] KMohZaid:
we have to edit method which have 2 parameter and 2nd one is context
[Magisk] KMohZaid:
View attachment 6078612

i have put line above aput-object as said

and if we ignore goto,label and ,line lines return comes next after aput-object
[Magisk] KMohZaid:
haha i am stuck on this too
[Magisk] KMohZaid:
@chiteroman your guide is good but not clear as it should be. please people understand
[Magisk] mkcs:
The goal is to compile the project and disassemble it to get the bytecode I think. I didn't care, just run the build command and get the smali.
[Magisk] Vision:
Oh this is good, i think.

With Android Studio compile ? and if yes under build what you select ? because i get some error

You make it to work all this ?
[Magisk] Vision:
Update info.

Eventually it is needed a valid keybox.

I'm confused if need this, i don't think all us can find it, or I'm missing something?

chiteroman/FrameworkPatch

Modify framework.jar to build on system level a valid certificate chain - chiteroman/FrameworkPatch

github.com

View attachment 6078637
[Magisk] eac5:
If someone can share the smali and baksmali fatJars, I'll send you a valid keybox. Cannot for the love of God get gradle build to work.
[Magisk] Vision:
I have the same problem when try to compile only the baksmali have generated.

And i have use the https://github.com/REAndroid/APKEditor for decompile and compile and this maybe help you by @osm0sis

GitHub - osm0sis/APK-Patcher: Patch APKs on-the-fly from Android recovery (Proof of Concept)

Patch APKs on-the-fly from Android recovery (Proof of Concept) - osm0sis/APK-Patcher

github.com
[Magisk] kylechen:
I don't think that's true, no offence of course.

I have worked on anti-cheat projects. Some emulator (customised for cheaters) are so good, there is simply no method/loophole for the OS and programs to find out it is actually inside an emulator, no matter how they try.

With enough effort, there is no road block to make a 1:1 emulator cloning an older android phone (without TEE of course) down to every hardware chip data stream bit. It is just not worth the work yet we are still in script kids stage.