yashsingh1/xdaforums huggingface dataset:
[Magisk] 73sydney:
i asked another member myself about it privately, he might like to comment further as he also was testing using riru, and riru-momohider

and with that i hand you over to @Stillhard ...

ill add an extra tidbit for those who want to user riru-momohider to make adding the additional (optional) config switches automatic at install...

you can:

1) extract the riru-momohider.zip somewhere

2) open customize.sh

3) scroll to bottom, i usually paste the following in just above "ui_print "- Setting permissions""

4) paste the following:

ui_print "- Setting config"

options='isolated setns app_zygote_magic initrc'

for i in $options

do

touch $DATA_DIR/"$i" && ui_print "- Setting config: $i" || ui_print "- Setting config: Failed to create config file"

done

5) rezip folder and install module through magisk as normal

6) dont redistribute it packaged this way, please dont ask me why, or why i didnt just paste a ready made mod of it here, ive been through enough drama the first time :) and trust me, you dont want to go there either. It got spicy y'all....

7) those wanting to do the config changes manually, can refer here:

GitHub - canyie/Riru-MomoHider: A Riru module trying to make Magisk more hidden.

A Riru module trying to make Magisk more hidden. Contribute to canyie/Riru-MomoHider development by creating an account on GitHub.

github.com
[Magisk] 73sydney:
why is literally everything okay when TJW says it....
[Magisk] rogers11:
Because people believe everything that is said on this ****-app.
[Magisk] rodken:
The old tried-and-true method of adding additional coding to existing modules.

-- Works almost every time.
[Magisk] m0han:
From Magisk-Alpha telegram channel: According to telemetry data, the number of zygisk users has reached 78.3%, and after more than 85%, alpha will remove magiskhide.‌
[Magisk] 73sydney:
I swear dementia is setting in (it runs in my family, all jokes aside), because I've not used magiskhide, riru and unsf (riru) in that long now that I'm not passing SN and can't remember how to fix basic integrity and cts. Could be the week of horrendous hours and no sleep too. Perhaps I'll actually try sleeping...

Also, I did not have ro reboot before direct installing delta...

Update: thankfully won't be checking good myself into a home, looks like yasnac was having a bad day earlier...woke up, tested again and passed...

Update #2: wasnt all smooth sailing and tea and crumpets, id forgotten the switch form Canary to Delta would likely sever my connection to my Watch 4, which it did. Stupid Samsung....one day theyll make a device that allows you the owner who paid their premium to actually choose how it works and connects to the other premium devices youve shelled out money to Samsung for. I hate that google didnt make a decent Pixel after the 2XL...i blame them really....never thought id be back dealing with Samsung nonsense again in my life
[Magisk] shadowstep:
Doesn't Shamiko hide Zygisk too? Or does it only "utilize" Zygisk to hide root?
[Magisk] huskydg:
Shamiko hide zygisk but not fully.

There are few app still detect that "Device is rooted" while using Shamiko even Momo doesn't say it found zygisk. But work normally when hiding using MagiskHide (no zygisk). Example: Livin Madiri, Itsme
[Magisk] shadowstep:
Got it. (y) And do these apps detect Riru (i.e. refuse to run when Riru is installed)? If not, that means Riru Hide is better at hiding Riru than Shamiko is at hiding Zygisk. No?
[Magisk] martyfender:
@huskydg I just yesterday switched one of my devices to your debug build. It is good so far and the latest momo does not detect zygisk, unlike the latest official canary debug build. However, in the shamiko module section it states that it is not working because enforce denylist is enabled. And, of course, there is no option in magisk app settings to disable this, unlike the official builds. Was this by design? I just disabled the shamiko module in settings and everything appears to be working without it, so is it no longer needed? I am, by the way using zygisk lsposed with hide my applist with the enhance mode for hidemyapplist to hide apps. Also, I have both zygisk an magiskhide enabled in settings.

Thanks for your efforts with this build.
[Magisk] meric57:
good evening jazziboi, once magisk 24.1 install must activate Zygisk in parameter then install safetynet 2.1.1 and shamiko 0.3.0 (73)
[Magisk] _mysiak_:
Ah, I feel stupid, all the issues were caused by "EDS" Magisk module (app used for mounting encrypted containers). After I disabled their module, Safetynet passes nicely with just Magisk denylist + USNF (+my other usual modules, including lsposed).
[Magisk] nacos:
Could you please post a link to the MyHideApp Lsposed module? Thanks!
[Magisk] _mysiak_:
https://play.google.com/store/apps/details?id=com.tsng.hidemyapplist

I used this app to hide Magisk manager from my banking app successfully (LSposed module was enough, I did not need to install Magisk module).
[Magisk] Umbardacil:
Hi guys

I really rely on your help here 😥

I upgraded Magisk to v24.1, enabled Zygisk, installed USNF module, hid all bank apps and Google pay, Google play services and other stuff in denylist, and I'm still not passing basic test. It says:"can't connect to Google play services"

Tried also to enable USNF module only-no luck.

What am I missing here? What did i wrong? I need to have payment methods working back badly. Please advice 😊

Lucas
[Magisk] Lughnasadh:
Try another SafetyNet checker app for the "can't connect to Google Play Services" message.

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/page-6#post-86337123
[Magisk] Umbardacil:
Thx for the tip 👍

Looks like it passes now, but:

Why doi get "not configured" message here? Does it mean anything, or will it work anyway ( can't test payment now)?
[Magisk] mingkee:
Use Safetynet Checker instead

This one has error connecting Play Services
[Magisk] Rockel:
I have followed all of these steps:

1) Make sure that both Magisk app and Magisk are installed and updated to the new version. Inspect version numbers on the main Magisk window/page

2) Make sure to uninstall all Riru modules (not compatible with Zygisk)

3) Settings, Enable Zygisk and reboot.

Then check on the main window does it show Zygisk Yes

4) Settings, enable Enforce DenyList.

Configure DenyList, enable filters to Show OS and System apps

Find Google Play Services and check-in only the two processes ending with gms and gms.unstable.

You will have to check in all your banking apps and so as you used with MagiskHide.

Always reboot upon reconfiguring DenyList

5) If SafetyNet does not pass, install USNF 2.2.1 and test again.

Always reboot upon installing a module, also if/when you enable Systemless Hosts

But Yasnac keeps failing on SafetyNet Attestation:

Google Play Services API error

7: NETWORK_ERROR

But I noticed that "Configure DenyList" is not holding on to the Google Play Services checks. They get unchecked after reboot.

Someone knows a way around for this¿
[Magisk] Rockel:
Same at my tab.

When I install USNF, gms and gms.unstable get deselected after boot.

After removing USNF it's fine again. But still failing SafetyNet.
[Magisk] rogers11:
Read here (last part).
[Magisk] jons99:
you're not failing safetynet it's just people checked so many times that the app ran out of it's daily limit try with a different app or try again tomorrow early
[Magisk] mingkee:
Yes, I realized that.

This actually makes the process much easier

Just enable Zygisk and enforce Deny List, and download and install USNF for Zygisk and done.

Add app in Deny List which detected root or unable to update due to root
[Magisk] kholdstayr:
I have the same issue mentioned by Rockel. When I try to add Google Play Services to the denylist they get removed after reboot. Any ideas?
[Magisk] dohanin:
Both these are non-issues.

As pointed out by a few posts before, API or network error from safetynet testing apps are due to too many people used it such the its daily quota had exceeded. Try other less popular apps from play store and you'll see there is no problem.

If you have USNF, you don't need to check Google Play Services in DenyList because USNF would have already taken care it necessary process to hide.
[Magisk] mingkee:
Alternative way to check:

Check Play Store

If you can download Netflix or Hulu from Play Store after rooted, you're set
[Magisk] p_void:
Good to see further developments on my favorite root solution. Yet I don't understand the reason for including zygisk where already developed solutions exist such as riru.

Also, won't the inclusion of xposed-like app modification framework built in open the floodgates to tons of original developer unrelated bug reports as happened with xposed itself? I hope the history won't repeat itself again.
[Magisk] spiderpl:
There is no need to hide these services when USNF is installed
[Magisk] oulouloul:
Same here
[Magisk] zgfg:
Same for everybody, and everybody who does not take little time to read what was already few times described during the last days (thread is still small, but getting cluttered with repetitive questions/answers like this) will report the same 'problem' (that is not)

If USNF 2.2.1 is installed, it will take care of Google Play Services (GMS) and will remove GMS from your DenyList - hence don't report as an issue/problem
[Magisk] pndwal:
Of course there is this promise of some fixes to come (Chinese translated):

https://t.me/magiskalpha/510

🙂 PW
[Magisk] m0han:
What do you mean by '

enhance mode

for hidemyapplist'?

Do you mean to say you have disabled Shamiko module in the modules section of Majestic Delta settings?

Could you share screenshots, especially of your magisk modules list and hidemyapplist setup.

I was under the impression that LSPosed Riru should be used instead of LSPosed Zygisk.

Thanks to @huskydg for his Magisk build. Hoping he can elaborate on the way to run his Delta (Stable/Canary/Debug?) and minimise detections.
[Magisk] m0han:
Just sharing what I have attempted with Magisk Delta Canary and Shamiko. I'd appreciate it if experienced folks here throw more light on how my setup should be modified.
[Magisk] huskydg:
I regret to say that shamiko are masturbate you, momo will make you want to hide root crazily.
[Magisk] huskydg:
How does Momo detect some magisk module modifications?

The problem is usually caused by font module. The systemless changes will cause some files of magisk modules to be shown on system partition while the device id is data partition
[Magisk] m0han:
in layman's terms: disregard/discard both?
[Magisk] huskydg:
You can try turning off font module. It cannot be detect again
[Magisk] m0han:
disabled the font module and rebooted. no change.

currently i have both zygisk and magiskhide enabled. disabling zygisk caused issues. should i remove lsposed zygisk and use lsposed riru instead? will all modules work fine?
[Magisk] zgfg:
Stable, Beta, Canary and Debug Channels just got v25.1 updates today.

Changelog:

Magisk Changelog

The Magic Mask for Android

topjohnwu.github.io
[Magisk] martyfender:
Launch the lsposed app, choose the modules tab and enable hide my app list. Click on hide my app list and make sure the enable module is checked. Now click on the gear icon in the lower right to open hide my app list. Then click on install magisk extension, I chose zygisk. I think you need to reboot after this install.

Create a new template, add apps to this list to hide and click on the floppy disk icon to save. Now click on select effective apps and add apps to this list like momo. in the upper right choose show system apps. I add the rename settings app to the list. I add the template to each app. I enable all hide methods for most apps. For the settings app (hidden Magisk app) I select the hide methods only: API requests, intent queries and ID detections only. Don't forget to click the save icon after each operation.

I forgot to mention, back in the lsposed hide my app list page, only enable system framework. Don't enable other apps on this page as momo will detect exposed modules installed and maybe other detections, I can't remember. In my case, if I enabled other apps here, momo would show code injection.

After reboots you should see a module in the magisk app called enhanced mode for hidemyapplist.
[Magisk] m0han:
Unable to install magisk extension. Failed to acquire root permission. [UID] 10290 was denied Superuser rights.
[Magisk] m0han:
... in the lsposed hide my app list page, only enable system framework...

@martyfender, this helped. many thanks. my applist detector and momo are as clean as can be under the circumstances. guess device is running a custom rom and bootloader unlocked cannot be suppressed, or can they....
[Magisk] pndwal:
FWIW, Momo 4.2.0 is no longer detecting Zygisk w/ Magisk 25101 and Shamiko 0.5.0 on RN8T, stock Android 10 MIUI... PW
[Magisk] casouzaj:
Likewise. I'm running AwakenOS 2.8 Plasma (Android 12.1) on my Sony XZ2 (H8296). With the same modules' setup in Magisk Canary 25001, Momo detected Zygisk. Not anymore, after direct updating to 25101.
[Magisk] huskydg:
It doesn't show doesn't mean zygisk is hidden. Try livin madiri and you will know. It only works if you turn off zygisk and use MagiskHide, Shamiko even can't hide
[Magisk] martyfender:
I saw that message in the past but I forget how I solved it. I am always using the latest test version of lsposed from telegram.
[Magisk] huskydg:
Open Magisk app, go to Superuser tab and open root access for it
[Magisk] Eng.Raman:
Totally agree, also the same with Itsme works only when Zygisk Disabled.

https://xdaforums.com/t/itsme-not-working.4454285/post-87000085
[Magisk] huskydg:
magisk alpha is custom magisk fork with telemetry
[Magisk] 73sydney:
I can still make it detect zygisk, if i install Hide My Applist and install the magisk module :)

Eberybody loving on Momo lately....

Though Ive given up HMA for the new updatelocker lsposed module to detach apps from all the app stores, which is mostly what i was using HMA for....
[Magisk] Eng.Raman:
Not sure about untrustworthy fork of alpha builds ( Just a rumor ) BUT ( in my opinion ) it is more stable than All TJW builds ( I never encountered issues with alpha ).

Also I tested your Delta build and it works well on my device ( Thanks to the Magisk Hide support With/Without Zygisk ).
[Magisk] svendsvin:
After updating to 25.1 DenyList Unmount is not needed for my banking apps to work any longer. Momo no more detect Zygisk but still Magisk.
[Magisk] huskydg:
Do you know what is telemetry?
[Magisk] Stillhard:
avoided in Window's world, and now added in android SU env?

It's a strange world, but it's not wayne's

Ponkles not strange tho
[Magisk] martyfender:
Is telemetry always bad? Don't developers use it to find bugs in their software? Please explain to me what data it collects. Other developers use it. The lsposed developer uses it in debug builds. The author states that if you don't want telemetry, don't use the debug builds. And @huskydg you never answered my question about why there is not an option to disable enforce denylist in your builds? Is it because magiskhide needs it to function?

Thanks
[Magisk] huskydg:
Telemetry is not really bad but it is not used by official magisk. Adding it would make someone don't feel comfortable. Magisk alpha is unofficial magisk fork made by vvb2060, it is not official magisk debug build as you said
[Magisk] martyfender:
But not shamiko? Or is it no longer needed with magiskhide enabled, also?
[Magisk] J.PG:
Just updated to v25.1 on my Redmi Note 10 Pro (sweet) with Android 11 (crDroid 7.16).

Google Pay did an update in April that broke it, v25.1 of Magisk seems to have fixed that. banking app still works, but now another random app (Doctolib) detects the root again, weird.

Clearing the data & reinstalling didn't help.
[Magisk] 73sydney:
I dont think it helps to use the trigger term that telemetry has become (thanks to Windows) to negatively portray a long term dev and magisk collaborator, theyre quite clear what the telemetry is, what its used for, and even how to completely avoid it. Using it to determine which direction a project should go is actually more useful than subjective voting.

Saying "my build has no telemetry" while being factual doesnt accurately portray what the other dev is doing with it

Perhaps draw a line under that and avoid mentioning it again and again?

Also your fork is just as "unofficial" as vvb2060's...

Not meant as argumentative, i appreciate your efforts with your own fork
[Magisk] asripath:
Telemetry queries caught the attention of alpha...
[Magisk] aaronmillion:
Thanks for the future many are unable to see yet revealed buddy 😎👍😀
[Magisk] huskydg:
There is also a PR on github about it
[Magisk] slimshouki:
Add this app to the list as well. Its f*cin drivin me crazy

Instapay
[Magisk] huskydg:
Same as Livin by madiri, the app you mentioned only work with MagiskHide and without zygisk. And Shamiko module cannot hide it.
[Magisk] Denny@83:
To me with 25.1:

(I have USNF + lsposed + hidemyapplist)

Denylist not enforcing and Shamiko: Momo detects Zygisk and some bank apps doesn't work

Denylist enforcing and Shamiko not working: momo doesn't detecto modification to the environment - bank apps works fine

in conclusion: Shamiko can't hide zygisk, and if denylist is not enforcing some bank apps doesnt't work
[Magisk] m0han:
momo still reports 'found zygisk' occasionally. on checking again after clearing data & cache, this is seen fixed. not sure if (the method of) updating delta has a bearing on this.
[Magisk] huskydg:
Zygisk is not perfect for hiding and don't expect it to be fully hidden and Shamiko even cannot handle it.
[Magisk] ipdev:
From my last experiment (posted in the general thread).

Magisk General Support / Discussion

Post # 52,172 and 52,212
​

Try with DenylistUnmount instead of Shamiko.

Cheers. :cowboy:
[Magisk] m0han:
Worked fine. But, without thinking, I force-stopped momo, cleared cache and only then checked. Maybe I should've checked without doing all that to confirm whether zygisk can always hoodwink momo. I notice you say 'With DenylistUnmount Momo never found Zygisk'.

However, momo continues to find my 'bootloader unlocked' and 'custom rom'. Any way I can prevent these 2 detections?
[Magisk] huskydg:
There are no way to hide Bootloader unlock because of hardware attestation. If your banking apps work fine, just forget about what momo found.
[Magisk] huskydg:
I think your guys rely too much on Momo divine app

Did you check with banking apps such as "Livin by madiri" instead of just momo?

Livin by madiri is banking app that detect zygisk even stronger than Momo
[Magisk] huskydg:
You tell that shamiko cannot hide in lsposed group, you will be muted
[Magisk] m0han:
i'm interested in @ipdev's statement: 'Momo only found Debugging and OnePlus's broken TEE.

Not the unlocked bootloader

'

. how could he achieve it? i'm not unduly worried about momo; it's just that i'd like to see a 'clean momo', if possible.
[Magisk] huskydg:
OnePlus devices will disable hardware attestation after unlock bootloader, but you should not break hardware attestation because it might cause some problem.
[Magisk] jakito:
It's not really a choice...either we break the hardware attestation or we can't root the phone unfortunately
[Magisk] huskydg:
You can fake that attestation is broken by:

magiskpolicy --live "deny { untrusted_app isolated_app untrusted_app_30 untrusted_app_29 app_zygote untrusted_app_27 } keystore keystore_key *"

To be honest, you should not do that because you might lost or break some specific features
[Magisk] ipdev:
'bootloader'

For OnePlus stock 'OOS'.

- Using the USNF module is enough to hide the bootloader state from momo.

OnePlus has a record of messing up their implementation of 'TEE' by the way.

Not sure if OPPO's stock 'ColorOS' is any better.

'Custom Rom'

Few ideas but, none working at the moment (at least for me). 😜

I might check with momo every now and then but, I only take it at face value. 🙃

If one app (momo in this case) fails (even if a false positive) other apps can also.​

I needed a break from other things and pndwal's question seemed interesting.

So I ran some tests and posted my results. 🙂

Cheers. :cowboy:
[Magisk] huskydg:
Incorrect, USNF blocks only google services from using key attestation, It does not hide bootloader state thrown from hardware attestation and you cannot hide it. You can review the source code to know more. If you see "TEE broken" in Momo app, that's mean key attestation is broken

It's better to look at the reality things (banking apps) rather than using comparison tool meanlessly (Mahoshojo aka Momo). And, I don't say Momo is useless and it is also benefit for ROM developers
[Magisk] huskydg:
How Momo detect some traces:

Detect Magisk and Xposed

HuskyDG Official page

huskydg.github.io
[Magisk] m0han:
Fox's Magisk Module Manager v0.5.2 released.
[Magisk] antoinecimino:
Hi, I am recently facing issues to hide the app myCanal.

The app does not detect root but returns UPES_160 / UPES_159 errors whent trying to launch videos.

I have tried several fixes with no sucess:

- adding the app to Zygisk exclusion list

-- clear cache / data

- re-install app

-- clear data / uninstall app / reboot / re-install app (and add back the app to exclusion list before launching it)

- shamiko (0.5.0)

-- clear data / cache + add app to exclusion list

-- uninstall app / reboot / re-install app (and add back the app to exclusion list before launching it)

I have also tried to re-install previous versions of the app with no success either.

When I unroot my device, the videos work perfectly well.

Also, since the last update, MS Authenticator is not passing the 2 step verification (both approval notif and unique usage codes). I don't know if it is linked to my organization or the MS Auth app itself as I cannot re-install previous APKs for MS Auth (I guess there is some kind of security to prevent re-installing older versions of Auth).

Any idea for either one or the other?

version: NE2215_11_A.14
[Magisk] rodken:
[Maybe] Check that:

-- Your myCANAL app is up to date on the Play Store [you can always revert to an older version]

-- Your equipment is up to date with the latest Android version available,

-- The certificates of your device are up to date,

-- Your equipment is Widevine Level 1 compatible or force 720p quality and/or force WV Level 3

How to force quality in 720p or L3?

-- Open the myCANAL app

-- Click/tap on your profile at the top right

-- Choose the "Settings" menu

-- Press the myCANAL version number 4 to 5 times consecutively

-- The sound "tchi tcha" will be played and then a video "Message of an informative nature" appears on the screen.

-- Make "back to the "DEBUG" section

-- Enable "Limit to HD 720p"
[Magisk] antoinecimino:
Thanks a lot for your message, I tried the fix and it works !

For reference, my original "dirty" fix was to watch multiscreen (probably because the flow was limited there)

What is strange is that my device is L1.. Probably a pb on myCanal app... I forced Limit to 720p and got the flow back.

Although I did not need to check certificates, I don't know how to update certificates it on Android 12. I could only access the list under Password & security / syst. security / credential storage / trusted certificates.

Anyway, it works so thanks a lot.
[Magisk] casouzaj:
Latest Momo (v4.3.1) found Zygisk again. Previous version didn't.
[Magisk] huskydg:
And you realized that you was played in "no exit vicious circle"
[Magisk] m0han:
any 'code injection' issues?
[Magisk] zubies:
is there a new fix? new update from imobile isnt working
[Magisk] huskydg:
Like livin by madiri, Imobile detect zygisk so you need to switch to magisk delta, turn off zygisk and use only magiskhide. Also read [App detect zygisk]
[Magisk] huskydg:
Banking apps detect zygisk and deny to run when zygisk is enabled:

- Livin by Madiri

- ItsMe

- InstaPay Egypt

- iMobile

... etc

The third-party module Shamiko (v0.5.0) even cannot hide zygisk. The only workaround is using Magisk Delta, turn off zygisk and use only MagiskHide
[Magisk] shadowstep:
The same method works fine for me with the latest version.