yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Unofficial LOS, like many custom ROMs, manipulates props (eg builds with certified fingerprint and matches security patch date) and integrates @kdragon SafetyNet fix (as per his Proton builds) so these pass SafetyNet w/o Magisk... Scores of ROMs are now building @Displax's fix for new Play Integrity deviceIntegrity verdict (Ie. adding certified but mismatched device fingerprint to bypass enforcement of a hardware based attestation verdict) into their frameworks_bases also... See the string of references at the end of this issue:

https://github.com/kdrag0n/safetynet-fix/pull/207

Official LOS will never do this due to their strict policy not to tamper security signals...

That's why @Displax modded USNF module (not official) may be needed for many bank apps to work w/ official LOS as suggested above (and no need for MHPC)...

👀 PW
[Magisk] sir_overthrow:
I don't know English very well (null). I understand that they are still working on the Universal Play Integrity Fix. I tried the XDA Mod from safetynet but after a while, timeout. I read the forums that you have written to me but I don't really know what I should look for. Should I wait patiently? Thank you for your patience.
[Magisk] sir_overthrow:
I finally got it using magisk delta (canary release) with safetynet fix displax mod. :DDDDDDD. Thanks to everyone who has written in this thread. Without you I wouldn't have made it. I love you! ❤️
[Magisk] DineshValor:
I was follow your every steps carefully but instead of zygisk hide in momo, now it's start detect debugging mode enable 😮‍💨.
[Magisk] zgfg:
It detects what it says. If bothering you, turn off USB/ADB debugging mode.

Or give up on Momo - it will always detect something
[Magisk] DineshValor:
Ok🥲
[Magisk] blksith0:
Hey how do we hide that we're using a custom ROM (which Momo detects)?
[Magisk] DineshValor:
Momo app help to find suspicious activity detection in your device, such as magisk, zygisk, Tee, custom rom, dubugging enable, oem unlock (bootloader unlock), etc
[Magisk] 73sydney:
oh good, a new Momo discussion in the thread

let me grab some popcorn....
[Magisk] huskydg:
Bring new good thing, this app can break hiding stuff

resetprop · Issue #23 · HuskyDG/magisk-files

can you bring back resetprop without the some apps detect root

github.com
[Magisk] Spartacus500:
Hello, today in the morning Play integrity was the first 2 correct, and in the afternoon only the first 1 correct 🤔
[Magisk] DineshValor:
Where did u check this? App name?
[Magisk] pndwal:
TB Checker.

Are you using official USNF, or Displax modded version?... Anything configured in MHPC?

Also, what is YASNAC result? Device? ROM? PW
[Magisk] DineshValor:
Thanx, do u able to hide xposed modules?
[Magisk] DineshValor:
SafetyNet Fix Mod solved my issue same as yours.
[Magisk] pndwal:
Yup... All green in all tests for me except strong/virtualIntegrity...

I have two LSPosed modules + HMA LSPosed module... Use that... PW
[Magisk] Spartacus500:
YASNAC all 2 pass ok. Before yesterday I updated the newest Magisk 25.2, then the newest Shamiko and Lsposed and until this morning there were two integrities correct, and in the afternoon suddenly device integrity fail ... Samsung Galaxy S7 Edge 9.0 Pie NFE 2.2. I do not use the modules you provided.
[Magisk] pndwal:
So your device is to old for Hardware Attestation, ie won't need to use tricks to fall back to basic attestation...

Seems NFE is a custom ROM so likely uses a later kernel than the latest S7 stock which has limitations preventing Zygisk from working... (W/ Shamiko working Zygisk must be workng on your device)...

Also, being a custom ROM I'm not sure what Fingerprint prop it's built with for CTS Profile match...

I'm not sure why CTSProfile would pass but not deviceIntegrity on you device that uses basic attestation natively but I suspect either 1) a module may be the issue (Play Integrity API may detect more issues than Safety net), 2) some sensitive prop(s) needs setting to a 'safe' value, or 3) a fingerprint prop other than the original/expected one, although passing for SafetyNet, may have been used in ROM build...

Please reboot after disabling all modules to test 1) and report results...

If no module is causing the issue, please install MagiskHide Props Config module and reboot (no need to configure anything in a terminal emulator as we're just testing the Edit MagiskHide props function which is the only function enabled/active by default when module is enabled) to test 2) and report results...

If neither of these changes work, please disable MHPC module, install this mod of Universal SafetyNet Fix (includes a Play Integrity fix as well as sensitive prop manipulation and more):

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87198517

to see if it's targeted fingerprint spoofing (or something else it alters) fixes 3)...

If fix for 3) works you can keep it (and it should be fine), but alternatively it is likely that setting a different certified fingerprint prop globally using MHPC module will also work... You could swap USNF_mod for MHPC and try S7 prints from it's list... Please report results...

🤠 PW
[Magisk] blksith0:
Yeah - I know that... I was using the app. Sir.

I was asking how to fool the app.

Ah, forget it, I'm passing the YASNC check so that's good enough.
[Magisk] ardiesel:
I'm on Pixel 6 Pro. Rooted and latest magisk. OTA update came thru. I haven't installed. When in magisk I pressed restore images and got a warning "no stock backup". Won't complete restoration so I can download the update. Any ideas on what I can do?
[Magisk] Spartacus500:
SafetyNet fix 2.3.1 Mod solved the problem 👍
[Magisk] dcarvil:
You can manually download and install the update. See https://developers.google.com/android/images. Edit flash-all.bat and remove the -w from the last line to prevent wiping data. Reroot after by patching boot.img.

You can also sideload the OTA. See https://developers.google.com/android/ota. I've never tried that, so don't know if that method is better.
[Magisk] pndwal:
I'd be very interested to know if you can still pass deviceIntegrity if you uninstall that and install MagiskHide Props Config module and reboot as I suggested above (no need to configure anything in a terminal emulator as we're just testing the Edit MagiskHide props function which is the only function enabled/active by default when module is enabled) to test if the actual issue is that some sensitive prop(s) needs setting to a 'safe' value, or if a fingerprint prop other than the one used in ROM build is needed, and report results...

Of course this is purely academic but would help to understand what changes are actually needed on pre-hardware key attestation (ie. pre-keymaster 3 Android 8 launch version) compliant devices...

Of course no version of USNF should actually be needed for Galaxy S7 Edge since Basic evaluationType attestation is used by default... Even if unconfigured MHPC (to fix sensitive props; nb. USNF does that too) isn't enough, using MHPC to configure a different fingerprint globally (enter 'props' in a terminal emulator and follow prompts... I'd also be interested to know if Galaxy S7 Edge fingerprint works or if a mismatched device fingerprint is needed) should do the trick...

🙂 PW
[Magisk] Spartacus500:
@pndwal

I will write like this, my Rom NFE 9.0 Pie is on Bootloader and Baseband since the original last version 8.0 Oreo, the whole system is on 9.0 Pie, Rom 100% stock without any modifications, I made Magisk root myself. The fingerprint from S7 Edge to NFE 9.0 Pie doesn't pass SafetyNet, and I'll explain why, the latest S7 edge version is at 8.0 Oreo and the NFE system is at 9.0, so the fingerprint from 8.0 to 9.0 is wrong. For SafetyNet to be correct, the fingerprint can be from another Samsung (my S8 +), such as the S8 PLUS which has the latest version 9.0 Pie. The request that the fingerprint from another device passes SafetyNet correct must be from the same android version (eg 9.0) as on our 9.0 device, and the security date must match.
[Magisk] pndwal:
But it's a custom ROM of course, not 'stock'...

Ah... Suspected you already used a different fingerprint to pass S/N... How are you applying the S8 print (it's not clear if NFE ROM builds this)?

Nb. If you apply any fingerprint via MHPC module's list the module also changes ro.build.version.security_patch to the matching date so experimenting is easy... Also, different API level (Android version) prints work fine for many devices... PW
[Magisk] ardiesel:
How about that sideloading the OTA update, will that break root?
[Magisk] dcarvil:
Sorry, I've never tried the sideload, so I don't know what it would do. My guess is that it would break root, but it is only a guess.
[Magisk] pndwal:
Either approach will restore stock images, so root is lost and installing Magisk again will be needed after installation...

However it may be possible to install Full OTA ROMs for 'sideload' from system in the same way as incremental OTAs are installed, to the inactive slot... But I'm not a Pixel guy and I don't know if it is...

If that can be done and you're happy to swap slots instead of just restoring stock images on current slot, you should be able to preserve root by having the OTA installed to the inactive slot and having the Magisk app install Magisk onto this updated slot. Method here:

https://github.com/topjohnwu/Magisk/blob/master/docs/ota.md#ota-upgrade-guides

👀 PW
[Magisk] dangtranhoai:
Thanks so much, frozing magisk app did help for HSBC app.
[Magisk] ardiesel:
So I actually went ahead with the side load of the OTA, it worked fine I just had to reflash the boot img after and reroot. It wasn't so bad, you know. Eventually I'll be on a custom rom maybe that'll make things easier I don't know. I can't really find too many Android 13 roms that I really like yet or have the access to.
[Magisk] sahil2903:
Unable to see google pay icon in Magisk hide app​

I have installed safetynet and props config and entered my device via temux but I cannot see google pay icon in the magisk hide the app memu, so I tried to hide wallet but no avail :(

Additionally I cannot see google pay icon in my home screen, it tends to come and go (weird behavious)

- using lineageOS

- Oneplus 8T EU
[Magisk] 73sydney:
https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-87481637
[Magisk] mikelucky:
Similarly, some look for the TWRP folder (reasoning: why would someone have TWRP folder if TWRP is not installed).

You simply delete TWRP folder (or just rename) and they no more find it and 'complain' (ofc, they don't tell you in plain they found Magisk, Magisk app, TWRP folder or what - they just refuse to work)

yes,it works,although it's an empty folder,some apps still think twrp installed...
[Magisk] rubnduardo:
Hello guys. Thanks so much for all your hard work, it's awesome.

My problem:

I'm on P3XL pixeldust A13 magisk 25.2 + Zygisk + USNF

and

SN passed (YASNAC, both) // Play Integrity only STRONG failed

For dumb but nevertheless important reasons (spoiler: im in venezuela and depend on the wellsfargoapp LOL) i need the app to properly work but since out of stock rom it doesn't, just loads a webapp in a seamless way, which doesn't push notifications, among other less important stuff.

I'm currently doing research both in this thread and others. I've read there are several different ways apps blacklist devices and personally i think it's not the app but some Play Store security feature. I'll keep working on this.

Any advice or help to solve this is deeply cherished, and I thank you all in advance.
[Magisk] rubnduardo:
So to update a bit, pixeldust a13 does not pass stronintegrity and when i wiped everything and try it outofthebox wellsfargoapp worked as it should.

I tinkered yesterday the whole day, got in some troubles with twrp 3.7 recovery (restore is broken?) and ended up flashing stock via google online flashing (allbat did not work, i was SO F SCARED).

Today im setting my apps and stuff but nothing besides twrp. MOMO found twrp and magisk (which i dont have, nothing not even closely related), i changed TWRP folder name and MOMO doesn't find twrp nor magisk.

Wellsfargoapp is triggered by something related to my google account, i think. When i open my account from the browser i get the standard app, whereas from the android app im still getting the limited one.

I've read about wiping play store, gms, and gmsunsntable cache, which i think im gonna try but i dont want to go blind. Do anyone has some experience or pointers to fix this?

Thanks in advance.
[Magisk] AhmadOkda:
did you try shamiko ?
[Magisk] rubnduardo:
I have not. I was thinking about finding out the problem before root to avoid layering it.

Here are two photos of the exact same app. The one with the biometric option is what it should be. Pixeldust with TWRP, no further setup other than google account, got me the proper app. The difference now is that i set up my acc and stuff but no root, no nothing.

Before trying root + shamiko i was thinking of wiping data and cache (?) of playstore and gms (?), but i'm kind of blind.

Any suggestions? Or should i go with root right away and try shamiko? [USNF did not fix the problem when i tried it rooted, per my first post]

EDIT: the devices are diff but it's an example, as i got the one on the left when pixeldust outofthebox only google acc set (no sync, no nothing).
[Magisk] pndwal:
No devices I'm aware of other than Rog Phone 3 pass this w/ unlocked B/L... (But their may be others shipped w/ busted keymaster implementations that pass...) However no banks etc require more than deviceIntegrity yet AFAIK.

Interesting... Thanks for reporting...

... gmsunsntable cache (?)

I haven't read that you put app in denylist... Did you?

If more hiding is needed you can substitute denylist for Shamiko (read Zygisk hiding(not perfect) + MagiskHide restorer (enhanced)).

You'll need to do this also before using other hiding methods that rely on injection into zygote... In thinking particularly of Hide My Applist LSPosed module. (It won't have desired effect w/ denylist active as that reverses / blocks all modifications to apps in list whereas Shamiko allows these like old MagiskHide.)

For basic hiding, wipes needed etc however, principles here:

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-87481637

🤠 PW
[Magisk] darywira:
Dear Mr. Huskydg , is there anyway to hide magisk from this app ? thank you
[Magisk] knasiotis:
I have a question, I used this applist detector and it detects magisk app as a gptekjgml.ah, the thing is i've done all steps, zygisk, universal safety net, changed magisk name via its option and the props config. Is there any way to hide magisk completely?
[Magisk] pndwal:
... Use HIde My Applist LSPosed module to properly hide Magisk / other apps... 👍 PW
[Magisk] huskydg:
There are always the ways to detect magisk
[Magisk] knasiotis:
now both xposed modules and magisk are detected
[Magisk] martyfender:
in HIde My Applist, hide the the renamed magisk, by default, named settings and go into /data/adb/modules/riru_lsposed/system.prop and add # to the start of the the line:dalvik.vm.dex2oat-flags=inline-max-code-units=0. save and reboot. There may be more. in HIde My Applist that you may need to hide also.
[Magisk] knasiotis:
I

I "enable hide" for the apps, I save. Then I go to settings and I press to hide Hide My Applist. I do not have /data/adb/modules/ path. Both are still detected

EDIT: I am on eu rom 13.0.13 android 12 for clarification with magisk+zygisk and magiskhide props config

Same thing, service is started

FINAL EDIT: I WAS DOING IT WRONG. https://android.stackexchange.com/q...sing-advanced-root-modded-framework-detection this guide helped a lot! Thanks for your help as well!
[Magisk] pndwal:
Are you using 3.0.4 beta? Or older version...

... But you're selecting the wrong apps here... See below...

So you mean just hiding HMA icon in launcher drawer were? - won't help hiding from Applist Detector...

From root explorer... Do you see /data/adb?... But I doubt you really need the changes mentioned...

I see you have HMA in in Effective Apps... If the other app is obfuscated Magisk, you should remove it... You don't need either of these...

Next, create a blacklist template with Magisk, XPosed modules (HMA, other) and any other app you wish to hide selected there and save it as needed...

Next, in Effective apps list select Applist Detector then enable Hide and select the template you just created for it... Also, in old HMA version I think you can select hide methods... IIRC you see 5 but need to select the first 3 only... Save the profile if old version...

You can add any Apps that detect other apps to Effective apps list and detected apps to the template, use a custom template for each app or just add detected apps as Invisible apps each app you hide them from...

Might be better for you to simply use @Displax's forked/modded USNF w/ fix for Play Integrity as it also sets a passing fingerprint prop targeted to GSM, and disable MHPC...

🤠 PW
[Magisk] pndwal:
🤔... Is this to bypass a detection in Momo?... Or is that needed for Applist Detector for you? PW
[Magisk] martyfender:
You are correct, it is for abnormal art parameters detected in momo. other apps do not detect it if hidden in hide my applist.
[Magisk] rubnduardo:
Momo is just a reference, don't rely on it as basic or fundamental, as said before it's always gonna find something, it happened to me on stock custom.

Remember reading the thread to optimize it :D (it was discussed recently).
[Magisk] rubnduardo:
Ok, i'm gonna follow your advice but where is gmsunstable? Can't find anything but Play Services aka gms.

Also I have not used denylist, i'm gonna completely skip it and go shamiko. I'll report later.
[Magisk] m0han:
maybe @pndwal meant this?
[Magisk] pndwal:
You said

I said

I guess member means that, but hasn't clarified...

Of course if using Zy-USNF there's no need to do that, and it'll be removed on next boot anyway...

If meant clearing cache, this will be for main GMS, ie. Google Play Services... Also, clearing GMS data is more likely to have the desired effect...

😜 PW
[Magisk] rubnduardo:
Idk how to get there, i searched for it in apps, cleared play services' cache.

Yeap, I'm doing that, following your recommendations. From what I read it's going to take a while (?).

Thanks for the help.
[Magisk] m0han:
Try Magisk app » Settings » Configure DenyList, maybe. I forgot how it is in official Magisk.
[Magisk] pndwal:
Please say which specific recommendation... Its still not clear what you're attempting... (If you have USNF working with Zygisk you DON'T NEED to put com.google.android.gms.unstable in denylist...)

And what's going to take a while?... This? 😁 PW
[Magisk] huskydg:
Not to be rude, Momo is not the strongest detection, there are plenty of apps which i discovered that do more detection, maybe livin by mandiri is the strongest banking app that hard to bypass with current hiding method (MagiskHide, MomoHider, Shamiko...). Firstly canyie said it could detect SIGCONT used by MagiskHide. But i didn't think so, because app crash with MomoHider also. After having done some tests, I found out that it could know there was someone enter mount namespace before (just guess). People use this app can only unload magisk (temp unroot) or hide/unmount magisk globally before using it. What you said is exactly what I told people here before to stop them from mental masturbating with how they make momo feel happy by using shamiko *considered* to best hiding 💁‍♂️

And i said if their app worked, simply ignored momo detection.

Am i talking right? Dear @pndwal 😉
[Magisk] rubnduardo:
I'm trying to get the 'proper' app from wellsfargoapp to work, which seems to change to a lesser functionality one because of some security feature which i think relies in google services, as explained here:

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

I'm not using denylist as ive got zygisk and displax USNF. I'm going with your instructions:

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-87481637

where you state (although talking about google pay) it may take some days, but i don't know for sure about the wellsfargoapp.

Thanks for the help again.
[Magisk] pndwal:
But you'll need your app in denylist at least to hide root from it! Same principle as for G Pay... Will likely need proper hiding module, eg Shamiko to replace denylist...

Nb. USNF is for SafetyNet or Play Integrity bypassing, not root hiding...

I believe I was talking about G Pay/Wallet resetting detection slowly if data isn't cleared... It's generally an instant fix if you clear data... PW
[Magisk] ColinHu:
how should I fix YASNAC safetynet attestation time out error. I did it once, and it worked. But I uninstall an app, then it become not working. I try to uninstall Magisk 25.2, and reinstall everything. But YASNAC still shows attestation time out. And all the app still not working. Please help!!! Thanks!!!
[Magisk] zgfg:
Does your ROM have GApps - particularly Google Play Services?

Also, phone must be on the network - it needs to connect to Google with your G account - hence must not be blocked
[Magisk] ColinHu:
I'm not sure. How should I check that? I was just followed the thread (XDA) to root my oneplus 6t from t-mobile version to the international one. And then, unlock the boot loader, root, and download the Magisk 23.0, then update to 25.2. And follow all the steps try to make things going.

I was able to passed YASNAC safetynet before but now it says "Something went wrong. Attestation response timeout."
[Magisk] zgfg:
Stock ROMs should have GApps.

As also said above (edited), phone must be on the network to access G with your G account (account must be set, connection must not be blocked)
[Magisk] oulouloul:
Ive tried freeze magman (this is my name repacked magisk manager) with titanium backup but no luck. Ive freezed it, uninstall and reinstall banking app. But it can still detect root. Unbelievable.
[Magisk] Lord Sithek:
I'm not sure if that is you who didn't understand me or the opposite 😅 I meant that we can't use Magisk app when it is freezed (freezing and unfreezing, well, too much hassle). But we can use it (at least in most cases) with the the help of HMA. Even if a bank app detects repackaged Magisk app, if we hide Magisk app with HMA AFTER REPACKAGING IT, this usually helps to fool that bank app
[Magisk] Robbo.5000:
For the many users, who don't want to tinker with everything, but just install a custom ROM of choice, all of this is a means to an end, of enabling banking and financial apps. Once these is achieved , most won't need to use Magisk Manager from one month to the next, so it's no great shakes that it's frozen.

For the occasional time you need it, then it's easy to unfreeze.

Those fortunate enough to have this work for them, freezing an app is a lot easy than installing lsposed, then installing and configuring HMA.
[Magisk] Lord Sithek:
Well maybe. Everyone can do what is easier for him. Personally I use Magisk app quite often and use LSPosed for many different purposes, so it's more beneficial for me. But yea, I'm not against freezing 😉

PS. I'm not sure though if after Magisk unfreezing a bank app would not require clearing data and setting it up from the scratch... And that would be much hassle...
[Magisk] Robbo.5000:
The recommendation in that situation is to temporarily freeze the banking app(s) before unfreezing Magisk Manager. Then thaw then out after refreezing Manager app. A bit of hassle, i know, but saves starting from scratch in the banking apps. For those non tinkerers, this scenario is rare enough to make this solution worth considering.
[Magisk] zgfg:
You can use AirFrozen app - give it root grant

It freezes/unfreezes by:

pm disable-user <pkg>

pm enable <pkg>

But it has a very friendly UI.

Look at my screenshot - all those apps I keep frozen.

When I need one of them, I click on, it unfreezes and opens.

When I'm done, long press and freeze

That way you can easily freeze Magisk app and when you need, you unfreeze and open in a fraction of second

No troubles with Hide Magisk app (that does not prevent some banking apps to find, no HMA