yashsingh1/xdaforums huggingface dataset:
[Magisk] Danny94:
Tried already, thats not working neither. GMS is removed automatically with most playintegrity fixes.

Currently im on rom xiaomi.eu 20.3.26 (miui11) from 2020-03-27 (last miui 11 beta).

Below i attached screenshots but with Displax play integrity fix because the xioami only one does not pass basic.

I tried:

PlayIntegrityFix.zip

PlayIntegrityFix-XIAOMIEUONLY.zip

safetynet-fix-v2.4.0.zip

safetynet-fix-v2.4.0-MOD_2.0.zip

safetynet-fix-v2.4.0-MOD_2.0-STRONG.zip

I tested now rom v20.3.26, V11.0.3.0, V11.0.4.0 none does work.

Might its an issue with the fingerprints and security patch level.

It looks like xieomi.eu does add fingerprint + fingerprint_real, aswell others like build date security patch level _REAL, may visible to play integrity. Tried to modify the security patch level to something higher like 2020-03-01 with magiskHideProps together with fingerprint. -> no chance... miui 11 is my last option for a good rom :(.

Edit: For trial i flashed xiaomi.eu V12.5.6.0, unlike miui 11 this version (miui 12) does pass device, basic and strong integrity witouth magisk. All miui 11 roms passed basic integrity witouth magisk only.

Displax play integrity 2.0 is enough to make all integritys pass again on xiaomi.eu V12.5.6.0 with magisk, but i dont want miui12.

Edit2: miui12 V12.0.6.0 witouth magisk does fail aswell device and strong integrity same like miui 11.

Edit3: id like to try the global rom (miui 11 v11.0.4.0 mi 9t pro global), on my redmi k20 pro china, but im not sure if it coould be a compatibility problem because the china version has more ram and storage (8 instead of 6 and 128 instead of 64gb i think). And it could may lock bootloader...
[Magisk] pndwal:
PI API simply needs correctly set mismatched but passing fingerprint prop for many HK compliant devices to bypass Google's server end enforcement of hardware-backed deviceIntegrity verdicts... I'll put details in the following post; Please check that...

It seems that the way XiaomiEU implement their global fingerprint spoofing is interfering with UNSF's GMS targeted Angler (Huawei/Google Nexus 6P Android 6 "google/angler/angler:6.0/MDB08L/2343525:user/release-keys") fingerprint and breaking the enforcement bypass, or (possibly) some other prop is breaking the verdict itself... I think we can assume that @Displax was right about many of the XiaomiEU custom ROM builds...

Assuming USNF's targeted Angler print spoof is working, you don't need matching security patch level date value... Reason given below...

Nb. Play Integrity API didn't exist (except on the drawing board) when your ROMs were built... They were concerned only with passing S/N natively...

Also, back then many ROMs were implementing inbuilt SafetyNet fixes in strange ways that were not Magisk USNF compatible... PixelExperience was notorious among others...

It does seem strange that Momo finds the two differing Xiaomi fingerprint prop values; For all devices I've had, incl. w/ custom ROMs, I get only the correct ROM set values in both fields despite the fact that USNF is actually targeting GMS with Angler print... But I'd say that's probably a red herring...

I think either @kdrag0n / @Displax critical prop changes are simply not being applied as @Displax indicated, or XiaomiEU was setting 'sensitive' prop values we haven't discovered that PI detects and breaks deviceIntegrity....

We did confirm ROM is running selinux enforcing didn't we? 🤔...

Promised details coming up... 😉 PW
[Magisk] Danny94:
@pndwal thank you very much for your effort, yeah it seems like you were right, xiaomi.eu did break device integrity on miui11.

I just installed the global official Miui 11 v11.0.4.0 provided by xiaomi. This version same like the xiaomi.eu versions did not pass device integrity by default.

But after installing magisk and "safetynet-fix-v2.4.0-MOD_2.0.zip" i finally pass device integrity (+basic integrity) and the device is google play certified.

The global rom did not lock bootloader but replaced my recovery. I gona try to unbloat it as good as possible and maybe try to port some improvements from xiaomi.eu. Overall im only interested into:

Optimized GPS settings for EU

Optimized Battery consumption

Optimized RAM consumption

and get rid off china bloat, ads, dangerous stuff running in the background...

So maybe i will stay on this rom now unless Igor can upload a build for me or give me instructions to "improve" this rom. I gona check if i can find some hints inside xiaomi.eu zip.

Thanks to you all for help.
[Magisk] AnyNameYouWish:
I'm a bit lost with all recent updates and new modules.

I have a rooted Pixel 5 with official firmware and july update.

Using Displax's safetynet-fix-v2.4.0.zip

Wallet app worked perfectly until last week, but I tried and failed to pay today.

I don't pass any integrity anymore

What should I do in order to pass at least device and basic integrity?

Thanks for support :)
[Magisk] mGforCe:
Sorry for late reply...

Yes, Xprivacy is not supported any longer but last released version works fine. I am on A13 too, but now I am on Magisk Delta which has got back MagiskHide

Regarding SBI Yono, even I have had no success else would have posted.
[Magisk] mGforCe:
Hello Folks,

On my Redmi Note 9 Pro (curtana) with LineageOS 18.1 (Android 11) unofficial rom, I am finding that AppList Detector is able to detect Magisk App and XprivacyLua.

My setup is following:

Magisk Delta (with app renamed)

MagiskHide configured to hide for Applist Detector

Zygisk enabled

Lsposed installed with HMA, XprivacyLua etc

HMA configured to hide root apps with AppList.

Anything else to be done? Any tips?

PS: Magisk app renamed is bd.ftftdzg.fwh (no magisk anywhere in name)
[Magisk] zgfg:
Use HMA to hide Magisk app (in fact, with that you don't need to rename the package for Magisk app) and Lua

Btw, are you using Zygisk-LSPoded, not the deprecated (Ed)Xposed

And not sure do you really need Lua and for what. You have HMA and you can install Magisk module App Data Isolation as on the screenshot

(don't ask for the link, find on GitHub, the author - second name - has strictly prohibited to 'advertise' the module on XDA 🤭)
[Magisk] mGforCe:
Thanks @zgfg

Yes, I am using Lsposed only... corrected.

Let me check, don't think have hidden the magisk renamed in HMA. Let me check

Xprivacylua, I was using to hide access to my contacts, location etc to few notorious apps like Truecaller etc. Also Axis Bank app (Indian Bank) worked, in past, only with Xprivacy when we restricted access to few things, here. Later I will explore Axis Bank without Xprivacy.

Noted on the other app, let me search and find.
[Magisk] mGforCe:
Post this magisk module, do I need to do something in HMA?
[Magisk] pndwal:
Just a heads-up/reminder - For some apps we do need both HMA and inbuilt 'Hide the Magisk app' stub obfuscation (at least with official TJW Magisk... Probably not with less known forks unless banks start searching for these differently signed builds)...

The notorious Sparkasse pushTAN is an example that would fail with one or the other but worked with both...

I have confirmed that their Promon security engine finds full Magisk app hidden by HMA by some trickery, and it also can detect the hidden Magisk App by using classes.dex code (which transfering Magisk binaries to stub data doesn't change, but rebuilding with different signing keys apparently does). Magisk obfuscated in stub app is successfully hidden from Promon with HMA however (using intent query hiding or other)... seems this blocks the classes.dex pattern scanning...

I previously gave references here:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-88232383

👀 PW
[Magisk] zgfg:
Once you configure HMA to hide one or two root apps (like LSyposed modules), it's trivial to add Magisk app

+ For some apps just to repackage Magisk app (Hide Magisk app from inside the Magisk app Settings) is not enough, hence both are needed

+ For some apps one or another is enough but regarding to often troubles with updating Magisk when Magisk app is repackaged, it's much more convenient to hide it with Magisk app

+ Many users repackage Magisk app and then don't know to find it (they don't remember the new app name and package name is scrambled, and they don't know how to search through all apps they have)

Hence my preference is to use HMA for hiding app and to use Hide Magisk app (repackaging) ONLY when HMA is not enough for certain 'bamking' app.

More convenient and less troubles
[Magisk] zgfg:
Please find the XDA thread about configuring HMA, read OP post #1 there and follow the link (from that post) to the updated HMA Guide on GitHub, study, configure and enjoy😁
[Magisk] mGforCe:
Thank you.

Yes I have read about configuring HMA in past - learnt it few months back after reading various notes. So HMA is already configured and working for most apps and playstore de-linking.

This is the revised guide right? https://github.com/mModule/guide_hma#hide-my-applist-guide

My query was that after installing this App Data Isolation, are there any additional tweaking needed for HMA? Or both are independent?

Also post AppDataIsolation, does app installation becomes slow? I felt so
[Magisk] zgfg:
They are independent, I need both for eg TB Checker.

I never observed any performance issues
[Magisk] ThassioPauletto:
Good afternoon everyone, I'm new here, but I've already scoured this entire forum.

I managed to get through the integrity checks, however my bank app (C6 Bank) won't open at all.

If anyone can help me, I don't know what else to do.

Below is my cell phone data.

Samsung S10

Magisk Canary (26104)

Lineage OS 20

I will attach the evidence of how I am doing.
[Magisk] J.Michael:
Did you (force stop, clear data, clear cache, reboot)*3 on the bank app?

Does "Hide My Applist" show up as an app? Did you include it in the list of apps to be hidden? (Not hidden from, hidden)
[Magisk] ThassioPauletto:
Good afternoon, I created a template in the "HMA" with the magisk application and the HMA itself, other bank applications are working... only C6 Bank is giving me trouble.

I restart phone and clear, not working :(
[Magisk] J.Michael:
Is "Trator" the renamed Magisk manager app.

Did you ever have TWRP installed? Do you still have a directory named TWRP?
[Magisk] ThassioPauletto:
Hi, this "Trator" is Magisk hide, I installed LineageOS using the custom recovery provided by them.

So if you have any remnants of the root done previously in OneUI that I used TRWP a long time ago...

When I upgraded to Lineage OS I did a factory reset and cleared the cache.

Now it may be that the noob question comes, How do I validate if there is something with the name TRWP?
[Magisk] pndwal:
Did you search for "C6"? 😜

C6 is among the banks doing extra checking for Zygisk.

I tested new WIP native bridge Zygisk loading (apparently coming in Magisk 27.0) as a POC in Alpha fork (builds Shana's Metagisk with NB Zygisk) back in April with many bank apps and C6 was working. See this:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-88468151

and post above for links (and my device setup)...

Nb. NB loading was the basis for Riru's RiruHide and Zygisk hiding for NB hooking is already implemented in Shamiko but still needs improvement... With Shamiko and Alpha NB implementation Zygisk is hidden sufficiently for C6 and many other banks however.

👀 PW
[Magisk] ThassioPauletto:
So, it was this post that brought me to the forum, but I don't know how to do that, I don't understand how to do this NB (Nitive Bridge) do I have to install Riru? and get the modules that I have in magisk that use Zygisk and download them to riru? (Shamiko, LSPosed and Play Integrity Fix)

Do I have to change the magisk? Or is it not available yet?

Give me a light, I'm kind of noob and above all, I use the translator to understand in English.
[Magisk] pndwal:
Zygisk memory can be detected in official Magisk at the moment. The hooking (injection) method used cannot be hidden fully... C6 and other banks detect it...

Shamiko module hides Zygisk sufficiently to hide Zygisk from detection methods used by some bank apps already, but some, detecting Zygisk memory (incl.C6), find it and won't run.

You don't need old Riru, but you do need Magisk with hideable hooking, and Native Bridge loading (method from Riru) achieves this.

Developers are aiming to have Native Bridge loaded Zygisk ready for Magisk 27.0, and no doubt Shamiko (from the same LSP development team) will also be further improved to hide all Zygisk traces with the new loading method, but it already hides native bridge loaded Zygisk memory and that's sufficient for many bank apps incl. C6...

The developers are building the new Magisk with NB loaded Zygisk in a Magisk fork called Metagisk, but builds are private... At intervals, builds including the work-in-progress commits are published in another fork called Alpha...

If you are desperate to use the C6 app immediately you can download recent Alpha Magisk as well as Shamiko from Telegram or GitHub...

I recommend that you wait to try properly finished Magisk with native bridge loaded Zygisk in official 27.0(?) public Magisk release however...

Hope it's more clear... 🤠 PW
[Magisk] wilsonhlacerda:
Use fork Magisk Alpha v26103 + USNF Mod by Displax + Shamiko + hide Magisk by changing its name on settings + turn ON Zygisk + turn OFF enforce deny list + add C6 to deny list (sou brasileiro e não desisto nunca 😁)
[Magisk] J.Michael:
I was flailing, just throwing out anything I've seen mentioned in these threads.

I don't remember the location of the TWRP directory. I would expect it to be under /data, maybe under /data/local.

You could try (in a terminal emulator)

find /data -iname \*twrp\*
[Magisk] Stillhard:
Magisk Delta /w SuList is enough, Zygisk is not the problem in that app
[Magisk] pndwal:
So this is 'MagiskHide SuList'?... Guessing Zygisk is enabled with this?

Nb. Delta went to native bridge loaded Zygisk loading with 25.2 delta5, but original Maru POC NB-Zy (not new WIP Metagisk NB-Z with many compatibility fixes)... Latest fdac22ba-delta change log still lists '[Zygisk]: Switch to use native bridge by 5ec1cff' in 'Diffs to official Magisk'...

As C6 apparently works with both Alpha and Delta, My guess is that Zygisk in official Magisk is the problem/detected, and that 'MagiskHide SuList' is actually not needed (except that it may be needed using old NB-Zy from @/5ec1cff)... Please say what I'm missing... 👍 PW
[Magisk] Stillhard:
Yes
[Magisk] pndwal:
... So apparently current TJW Zygisk is detected per:

and native bridge loading must be used whether (old) in Delta or (new) in Metagisk/Alpha... This user may need your configuration ('MagiskHide SuList') to get C6 Yellow working with Delta however... 👀 PW
[Magisk] Legitsu:
we should not be targeting fixes for specific apps @J.Michael is correct the right approch is to render magisk/zygisk undetectable PERIOD

move it out of accessable memory scamble the addresses to keep apps from blindly probing looking for it

the fix eventually is going to be not magisk but kernelSU get it out of the user space period and out of reach of prying apps
[Magisk] HippoMan:
Agreed.

I've been very happy with Magisk for a long time, but given Google's OS "enhancements" and all of the anti-root/anti-modding work which is being done by an increasing number of app developers, Magisk has now lost most of its value for me ... sadly.

I'm now eagerly looking forward to KernelSU or something similar to be available and usable for my device, so I can finally say, "Well, Magisk, it's been great, but now it's time to move on. Bye bye".
[Magisk] Legitsu:
what gets me is why are they even checking for root you need to unlock the bootloader to get root these days.

let alone checking for things like lsposed/shamiko which are not things a bad actor would be using anyway
[Magisk] spicediablo:
Hi, did you have problem with the latest pb engage version 2.63.0. Mine was just stuck at the terms and condition page.

Update:it's fixed with a reboot.
[Magisk] Legitsu:
even on the latest alpha momo is still finding zygisk

is there a option I need to tick to enable native bridge or is the implamentation just incomplete

edit so enforced denie list works but it breaks the following

1. bootloader unlock spoofer/TEE spoofer

2. iamnotadevloper module which hides usb debugging/dev options

3. shamiko

seems like there is more work to be done

you can either hide zygisk

or

hide your bootloader/dev/usb/debug/use lsposed modules

seems to me the easy fix would be allow scoping of enforced denie list or perhaps whitelist/blacklists are the way

that or magisk needs to scope in doing a better job of hiding the bootloader/dev options status ...

currently none of the apps I am using care about the zygote/zygisk being injected BUT do care about the dev options/bootloader status

bit of a catch 22
[Magisk] pndwal:
No option... NB is WIP... Shamiko is compatible and hides, but not yet fully... Momo Zygisk detection has also improved...

The delay with TJW 27.0 may be due to need for more work needed in Shana's Metagisk fork... Alpha changelog still says:

• [Zygisk] Refactored loading method, same as riru [under testing, unstable]

(translated)... New injection detection may now detect NB Riru also...

Even if Zygisk is still detectable in 27.0, Shamiko improvements will likely continue for Zygisk after release... Nb. NB loaded Zygisk has been WIP since March already, countless fixes have been made and continue to be made...

Of course it does... It doesn't really hide, just reverts/denies further Magisk (incl module) modifications... So any modules that inject into zygote etc break, at least for apps in denylist... Moreover, font modules and others break even though this is not the cause, but Shamiko includes a fix for fonts in apps included in hidelist (ie hijacked denylist)...

Denylist is a development tool (eg. for testing apps without root in a rooted environment)... MagiskHide is gone... Use Shamiko or Denylist Unmount module if you're paranoid about closed source...

Best bet is still NB loading + Shamiko...

Nb. Tee spoofer is highly experimental (hacked together) solution and admits to relying on on-device verification (banks won't do this), eg per Key Attestation app/POC, anyway...

FYI, Shamiko has whitelist mode option... Extract readme file from zip archive for usage/caveats...

Magisk no longer does any hiding (won't manipulate expected signals of 'subvert Google's security model as John has said)... Except for Hide the Magisk app... Nb Google generally views app detection by other apps (based on some permission loopholes) as an abuse which seems to be why they view app hiding as a fair game!...

Google have published a foolproof means for apps to detect AVB state independent of Play Integrity / SafetyNet APIs, and (if apps decipher keys/certificates using their own servers there's no known bypass anyway... We cannot hide Yellow (locked with custom keys) or Orange (unlocked) state... Nb. vvb2060/Rikka's Key Attestation is a POC, but only a 'sample that demonstrates the verification of a certificate on the Android framework and not

on a server'... as such, it's detections can be spoofed... Nb. 2. I have no idea why interested parties have been slow to implement this... But I'm sure they'll wake up sooner or later... (To me, this says 'don't get too optimistic' and 'be real')...

🤠 PW
[Magisk] zgfg:
1) and 2) are LSPosed modules. Did you check in the Magisk app, Modules, did LSPosed show a mark that it didn't load - if so, all LSPosed modules wouldn't work

Shamiko and Zygisk-LSPosed require Zygisk. I guess, they might both showed the mark that they didn't load

Did you try with Riru-LSPosed instead
[Magisk] Keks95:
after six years of satisfaction with my galaxy s8, above all because of lineage os... its time to say goodbye..

the last problems were a little bit annoying, but i locked my new banking account because of the root-detection of the tan app and without the app i cant do anything.... now i'm a very happy google pixel 7a user... thank you for all your help and many thanks to the developer of the lineage-os port for the s8...
[Magisk] Legitsu:
then the next step is writing our own attestation server to spoof responces or possibly start hacking on the play services or improving microg

right now local attest still works and it should work for a awhile yet as not all devices support remote attesatation
[Magisk] Keks95:
i switched my banking to DKB, the TAN-App worked for 6 times, then suddenly reset, end... the registration expired, called the DKB, my device is unsecure and blocked....
[Magisk] pndwal:
Do you mean to intercept the very X.509 certificate a bank app would call from hardware-backed keystore (ie. one containing the attestation certificate extension data), presumably using custom software on the device(?), send this to your own server and use an ASN.1 parser library to extract the attestation certificate extension data (which involves breaking ASN.1 cryptography including the bank app's attestationChallenge value provided to them at the key creation time in ATTESTATION_CHALLENGE authorization tag), spoof the values before re-encrypting, returning and injecting the spoofed X.509 certificate back into the bank app's data stream before it is processed on their server? 👀

If you want to see how this thing works, here's the basics:

https://developer.android.com/training/articles/security-key-attestation

... But I'm with you... Where can I sign up?

Mmm... But who said it's about the device?... The app can do local extraction/verification of key certificates (eg vv's Key Attestation POC) but this is easily subverted... Likewise if the app/Dev chooses server based extraction/verification only your hacking brilliance has any show of success... 😛 PW
[Magisk] pndwal:
Do you mean Sparkasse pushTAN app?

It's working with new native bridge loaded Zygisk, coming soon to official Magisk...

Nb. This is a WIP, but s-pushTAN works for me already per:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-88467665

Nb. 2. Previously we needed HideMyApplist LSPosed module for s-pishTAN, but this seems to have changed... I've just confirmed it's still opening ok without that on my device...

👀 PW
[Magisk] Keks95:
No, Sparkasse was my bank till this week, but the pushtan also locked me Out twice Last year. With my New bank i have to use this App:

DKB-TAN2go - Apps on Google Play

TAN2go — Secure TAN receipt on smartphone or tablet for your DKB banking.

play.google.com

Worked a few Times and suddenly detected the root. Magisk and all the other Stoff were configed correctly.
[Magisk] pndwal:
Getting this far with Alpha fork and Magisk app hidden:

... PW
[Magisk] ashish1989:
My phonepe app is detecting root when I am using upi payment. I am using

Magisk 26.1 stable

Zygisk enabled

Shamiko 0.7.3 working in blacklist mode

USNF by Displax 2.4 mod 2

Added play services and phonepe in denylist

HMA 3.2 with Lsposed

App is hidden from lsposed, magisk and hma

Ruru shows abnormal environment

TWRP, SU file and magisk file are found

Kindly help what to do?
[Magisk] Keks95:
yeah, without config the magisk hide etc the app closes directly and switched over to chrome. i set up a passwort and entered my first login credentials, because QR-Code wont work because the camera hung up - known issue with rooted device and the tan2go. after setting up these thing, the app just worked finde. but after 6 TANs generated, i ended up in the screen you just screenshotted. and after trying a second setup-process, the app told me my credentials allready used and blocked.
[Magisk] DaOldMan:
26.2 stable? I have seen only 26.1 on topjohnwu github. Am i missing something?
[Magisk] ashish1989:
Corrected it
[Magisk] Homeboy76:
<< Edited >>

Try using USNF by Displax v2.4.0-MOD_1-3?
[Magisk] ashish1989:
I tried latest mod 2.0