yashsingh1/xdaforums huggingface dataset:
[Magisk] TheDon13:
Hi all

Have been happily using Google Pay and all banking apps (apart from Chase!) that like to detect root on my rooted Xiaomi Mi 11 Lite 5G for past few months with no issues at all:)

Out of the blue, Google Pay yesterday started giving me the "Not set up" message on all my bank cards within that app. Checked phone still passes safetynet check and all my banking apps still work as Magisk (Hide) is frozen within Sd Maid....so I am very puzzled.

Advanced root checker confirms definitely still rooted & Ad Away all fine kepping those pesky ads at bay. So folks, any ideas pls?

Thanks in advance
[Magisk] ipdev:
I do not use gPay but, it was discussed the other day in the general thread.

pndwal found a solution and posted it in the [Discussion] Google Pay Magisk Discussion Thread.

Post #2,464.

Give it a try and see what happens. 🙃

Cheers. :cowboy:
[Magisk] TheDon13:
Thanks, I sussed it by clearing data & cache not just in gpay, but Google play services & Google services framework. Then rebooted, re added cards, all seems to fine again now 🙂
[Magisk] etmatrix:
Thank you I know very well the differences between riru and zygisk

Thank you for clarify my post
[Magisk] Mindfreak14:
It's still not working for me, as per post here in the group, i also used LSPosed module & HMA App .. I removed both of them and still the imobile app 14.7 detects it and doesn't work. Can anyone pls help with how to get this working.
[Magisk] vaidhy2007:
Hi. I am using Magisk 24.3. Enable Zygisk, Disabled Enforce Denylist. Added ICICI in deny list. Installed Shamiko.

Using Airfrozen to freeze magisk https://github.com/hyongbai/AirFrozen/releases

Then ICICI should open without an issue
[Magisk] GreekPilot:
New Momo version is even more aggressive....
[Magisk] CDzungx:
Yea, finding a solution for this :oops:
[Magisk] m0han:
FMMM update available
[Magisk] zgfg:
Something from Changelog I don't see in the app?
[Magisk] Mindfreak14:
Ok now this worked nicely. May be new version of airfrozen did the trick. Thanks a lot Dude, you are a saviour !! Hope this works for all future updates as well. Thanks again ! :)
[Magisk] jakito:
Hi! This question is completely off topic but no one is answering me on the original thread and you all sound extremely nice and knowledgeable. I apologize again for the off topic.

How would I restore a backup made using this Magisk Module? I have the backups done but would like to know how to restore them. The backedup partitions come in a .img format if that helps. I've always used TWRP so I don't really understand how this works.

Thank you very much
[Magisk] zgfg:
You should be better off asking where the guide was posted, bcs here some can only guess what partitions you backed up, how partitions look on your device, etc

Generally, TWRP can flash img files but:

- for some devices proper TWRP might not be available

- TWRP should offer you which target partition to flash to and you have to select, but again some TWRP versions will not offer you to flash img files to Persist and similar other partitions (hence you would not be able to restore by flashing that img through TWRP)

You can use the same dd command (disk-dump) that you supposidely used for backing up.

Google first for dd to learn/understand its syntax

Eg, if you backed-up (through adb or Terminal) by eg:

dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img

then you could restore by reverting if= (source) and of= (target):

dd if=/sdcard/persist.img

of=/dev/block/bootdevice/by-name/persist

But if certain partition is read-only it will not allow writing (restoring) over, and on some devices messing with certain partitions may result with loosing IMEI, DRM L1, etc

All these things might be device specific hence better check in the original guide or with the users of the same your device
[Magisk] jakito:
That's a lot of information. Thank you!
[Magisk] J.Michael:
How did you install Magisk?

The thing you did to write the magisk-patched.img can probably be used to write other images, you just have to change something to indicate to what partition you want to write.

If the so-called backup is not an image of a partition, then you are stuck with the program that created it, or some process that understands how to generate an image file from the backup; but once you have an image of a partition, you are back at Point A.
[Magisk] heinhuiz:
@ipdev can you add https://github.com/mywalkb/DenylistUnmount to this post, as an open source alternative to Shamiko? Many users are posting positive results with this module.
[Magisk] svendsvin:
I had this problem with Shamiko 0.5 constantly crashing my bank app, so I changed to DenyList Unmount and it just works. Sweet!
[Magisk] brackenhill_mob:
Thank you - I never thought to swap Shamiko 0.5 for this, but it stopped my banking app from constantly crashing.
[Magisk] Fif_:
Seconded. Denylist Unmount is a great alternative to Shamiko.

My setup is described in https://xdaforums.com/t/app-xposed-6-0-xprivacylua-android-privacy-manager.3730663/post-86991973
[Magisk] m0han:
@heinhuiz, @svendsvin, @brackenhill_mob, @Fif_ ... so, one can

remove Shamiko

and use Denylist Unmount instead, right? says so on the home page: There is a better module Shamiko but it's closed source. :D
[Magisk] Fif_:
DenyList Unmount works for me.

It's very simple compared to Shamiko, but likely not as powerful as Shamiko to hide stuff. As long as I pass SN, I'm happy. YMMV.
[Magisk] ipdev:
I bookmarked it the other day when I ran across the link in a different thread. 🙃

I added Denylist Unmount to Points of Interest.

Unfortunately my time has been short lately. 🙁

Life and sidetracked by other projects.

I have been meaning to update Post #9 for awhile now.

Post #9 was to be a catch all post for additional links recommended in the threads.

I have been trying to figure a good way to format/layout and categorize it.​

This is my current WIP.

Still needs to be formatted better. The secondary title needs to be reworded. Add/reword descriptions.

Other cleanup and format/layout.

Spoiler content hidden.

Cheers. :cowboy:​
[Magisk] 1manshow:
Is this method still working with latest iMobile app version from ICICI bank? I've followed the steps to no avail. I even tried using XprivacyLua method instead of HMA as well. Even Denylist Unmount instead of Shamiko as well. Uninstalled/reinstalled everything couple of times to ensure it's nothing related to some broken module/app. Any help would be appreciated. Thanks.
[Magisk] svendsvin:
Works for me as well but Momo is not happy. Detects both Zygisk and Magisk.
[Magisk] kjonca:
I don't know if this is good place, but

Magisk 25 (renamed) + zygisk + Enforce deny list and still polish bank app can detect magisk (it is konylabs based)

Message is "We detect use of Magisk or similar tool with this app. For your protection, the app will be closed. Please disable Magisk or contact support. (Ref: 6908) (7144:E16A 600000)
[Magisk] casouzaj:
In my Xperia XZ2 running Unofficial AwakenOS 2.7, Magisk Canary 25001, Zygisk enabled, deny list properly configured, but not enforced, with modules USNF 2.2.1 and Denylist Unmount v0 2 active, both SN tests pass, my phone shows as certified in Play Store settings and all my banking apps run flawlessly.
[Magisk] kjonca:
Forgot to mention: I have USNF2.2.1 installed.

I added Denylist Unmount but this did not help.
[Magisk] casouzaj:
Have you switched off 'Enforce Deny list'? Otherwise, Denylist Unmount will not work. After having done that, wipe data of the apps which previously accused your phone of being rooted, and reboot your phone.
[Magisk] kjonca:
Yes, I have disabled "Enforce deny list'. It is not clear form me what do you mean "wipe data" - "Clear app data" is enough or I should do something on system partition?
[Magisk] m0han:
he wrote wipe data of the apps which previously accused your phone of being rooted. i guess he meant 'Clear app data' from settings > apps > see all apps > (app in question) > storage & cache
[Magisk] casouzaj:
Yes, Settings > Apps > Select app > Storage > Clear data.
[Magisk] kjonca:
If so - this did not help. I also re-installed app. I does not thelp.
[Magisk] shadowstep:
Yep, running fine for me. I'm on version 14.8 of the app.
[Magisk] 1manshow:
Would you please list me the steps you did exactly to make it work? Thanks.
[Magisk] J.Michael:
Had you tried Shamiko?

What about Hide My App?

And lots of cache wiping and rebooting between steps.
[Magisk] shadowstep:
They're already there in the post you quoted before. Nonetheless, you can find my post here.
[Magisk] 1manshow:
Thanks, already tried those, not working for me, I'm using Redmi Note 5 Pro with AOSIP Rom installed on it
[Magisk] pndwal:
Just for clarity:

As I understand it, both of these modules are for hiding some traces of root while allowing Magisk modifications to be applied to a particular app (denylist will revert such modifications, which prevents additional hiding solutions incl. LSPosed modules from being applied to or working for apps in list).

Also, neither module makes the changes needed or helps in passing Google's SafetyNet attestation; this is the purpose of Universal SafetyNet Fix (and MagiskHide Props Config where ROMs lack a properly matched and certified device fingerprint).

So you don't actually need either Shamiko or DenyList Unmount if you're bank app simply requires passing SafetyNet and/or obfuscated Magisk App (use Hide the Magisk app function in Magisk App settings).

🤠 PW
[Magisk] Fif_:
Thanks for the recap @pndwal, but shouldn't that be:
[Magisk] pndwal:
Well DenyList function will do this as stated. (Enforce setting is a given...)

While these other modules source (hijack) denylist, it is still fully deactivated; they are only making use of the list to avoid the need for another (which should more appropriately be called HideList in fact) and for 'convenience'.

Unless enforced, TJW's DenyList function is inactive. Also, the fact that the list itself may be used for non-Deny 3rd party module purposes is also beside the point. 😜

I must say however, using the correct terminology is not easy even for the Devs themselves... Case in point, #01 GitHub issue for DenyList Unmount module... PW
[Magisk] zgfg:
At the end of the day, what for was TJWs DenyList functionality useful?

Bcs, USNF removes GMS from the list and applies its own functionality to GMS to pass SN

And now we have two other modules (Shamiko and this Unmount DenyList) that both require that DenyList must not be enforced (hence to prevent TJW's DenyList functionality to be applied) and instead, those two modules hijack the DenyList to apply their own (more useful) hiding functionality to the apps/services listed there

Ok, maybe the purpose was to make Google happy by providing the method (original DenyList functionality) that Magisk changes can be excluded (denied) from the given apps/services
[Magisk] pndwal:
So we're analysing what Magisk is to different users here... Seems Magisk = root-hiding to 80% of users, but I doubt that includes John.

You speak of 'more useful hiding functionality', but that is obviously what John wanted other Devs to handle. Remember this post series?:

www.twitter.com/topjohnwu/status/1445598597521633285

Denylist supplies a means for 'Magisk to get out of the way' and was never intended for hiding; it was to remove hiding features after all!

For 3rd party Magisk-hide modules, Devs must make DenyList itself 'get out of the way', but that's no biggie!

Rather than just to 'make Google happy', I believe John was truthfully 'transforming MagiskHide codebase into something he felt is valuable', particularly in the long term...

You ask "At the end of the day, what for was TJWs DenyList functionality useful?", but it seems John is focusing beyond this to a day when HW KA is properly deployed...

When that day arrives, many may ask "At the end of the day, what are DenyList-hijacking hiding modules useful for?"...

'Well may we say 'John save the denylist!

... because nothing can save The hidelist hacks!'.

Any semblance here to speeches given by commoners or prime minister's past or present is entirely conspiratorial coincidental.

... Don't think for a minute that this will stop me using these modules while I can however... I think it's unlikely that John avoids their use either (at least privately 😜).

😛 PW
[Magisk] zgfg:
Yeah, I remember all that. I just say that apparently the original DenyList functionality hardly anybody needs - do you know of any particular app where the original DenyList would be really needed

Maybe there is somewhere but in that case it would be better that Shamiko and Unmount provide their own lists so that we could distinguish: I need DenyList for app1, Shamiko hiding Zygisk for app2 and Unmount to hide whatever it does for app3
[Magisk] etmatrix:
Which version? I tested Momo 4.2.0 and Shamiko 0.5.0 (110 and 112), zygisk is detected.
[Magisk] pndwal:
Yup, seems Denylist is not really for general (end) users and that John likely intended these to use Magisk with Enforce denylist disabled while 'hide' module Devs stepped up and 'started doing their jobs'...

I agree that 'hiding' modules having proper hidelists and being fully divorced from denylist may be good. I guess they'd need their own 'dashboard' apps, or config (.ini etc) files... Meanwhile, it tis what it tis...

Where DenyList makes sense is as a development tool, and John clearly had Devs rather than end users in mind when first spruiking it. For example he points to the advantages of deny over hide for speed of development in his 'State of Magisk 2021' blog:

Nb. scripts/emulator.sh became scripts/avd_magisk.sh on Jan 20.

The text there indicates that this applies to developing root apps and modules, besides Magisk builds:

##########################
# AVD Magisk Setup
##########################
#
# Support emulator ABI: x86_64 and arm64
# Support API level: 23 - 31 (21 and 22 images do not have SELinux)
#
# With an emulator booted and accessible via ADB, usage:
# ./build.py emulator
#
# This script will stop zygote, simulate the Magisk start up process that would've happened before zygote was started, and finally restart zygote. This is useful for setting up the emulator for developing Magisk, testing modules, and developing root apps using the official Android emulator (AVD) instead of a real device.
#
# This only covers the "core" features of Magisk. For testing magiskinit, please checkout avd_patch.sh.
##########################

Further, Mishael (of former XDA fame) said:

The pdf cited includes:

John responds:

Replys:

So Magisk is really a cutting edge tool invaluable for Devs testing app, regression and security (penetration) testing.

While 80+% of users will likely not relate to his, John is rubbing shoulders with the 20-% of users who use Magisk for development purposes. With respect to Zygisk, it seems that this was the audience he was directing his remarks "I strongly value the ability for apps to fully “opt-out” of modding, and it is important to me that Magisk is able to “get out of the way” to.

Comments relating to end users expectations / disappointment with the HideList (user friendly) --> Denylist (dev friendly) transformation:

🤪 PW
[Magisk] pndwal:
From the getgo Shamiko was for hiding Zygisk / 'root'. Zygisk hiding has been improved however, especially in last build. See link below.

0.5.0-112 was a minor fix; same features as 0.5.0-110...

I put full changelog (my edit) here:

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

🤠 PW
[Magisk] vaidhy2007:
https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-86993091

Please check the attached post.
[Magisk] 1manshow:
thanks mate, tried that as well, alas still don't work for me! got tired due to this so had to remove root completely to make it work as I need the app...

Rest all other root and banking app from Indian bank worked fine, it's just this stubborn ICICI crap which is somehow still detecting root no matter what I do!
[Magisk] daemonicvs:
maybe this is good news for you: the xlua-folder was/is not the cause for root detection by some apps on my phone. it was/is the absence of the cia-spy-services.

i tried microg but it did not work. but then i recognized that the versions were outdated and the current versions were shown as incompatible or so (i dont know why). so i installed the current microg version as a system app (flashing via twrp). the apps in question now can register at cloud messaging and the microg-safetynet-test passed. i dont know if registering at cloud messaging is a requirement for passing safetynet. and i dont know if GCM is sufficient or if the apps really need passing safetynet. but at least they work ;D

in magisk i added the apps to the deny list and activated enforcing the list. thats how everythings works for me
[Magisk] razrielsch:
Is Magisk + Zygisk able to hide TRWP ? Cos this is dtected by the Applist detector as Abnormal Environment. May this blocks DKB and other banks too
[Magisk] m0han:
try this: save your backup elsewhere and delete twrp folder from internal/external storage. if remaining in /data/media/0/ delete from there too.
[Magisk] zgfg:
Please do not cross-post the same question to both threads.

You just asked the same:

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

in that other thread and you were answered there
[Magisk] daemonicvs:
i forgot to mention that i use usnf magisk module and magiskhide props cfg but i dont know if this is necessary and i dont know if i changed the fingerprint via props
[Magisk] vaidhy2007:
This works for me on 3 phones that i tried. Probably you are doing something wrong, Are you on telegram ?
[Magisk] 1manshow:
hmm, that's weird as I tried almost everything many times over, doesn't work for me with that stubborn app. My telegram ID is @a1manshow
[Magisk] winner71:
After some times problem solved, now after update to momo 4.2.0 "found zygisk" appear again 😁
[Magisk] nayak.aj:
Were you able to sort this out ? i am having the same issue now on my S8
[Magisk] nayak.aj:
Hi guys ...

! Only support SDK 27+ devices

! Installation Failed

any work around for this please ? happens while installing the Shamiko module on my Samsung S8
[Magisk] pndwal:
Seems need to wait for fixes in the works:

https://t.me/magiskalpha/510

So seems Shamiko hiding is broken by Magisk 25.0+, but a fix is already on the drawing board...

My tests indicate issue may be in 24315+:

That TG post continues:

Interesting translation; may enhance understanding of DenyList... Seems 'disable "enforce denylist"' = 'turn off the "comply with the exclusion list"... 😛 PW
[Magisk] zgfg:
SDK 27 refers to Android 8.1 - seems you have an older Android.

Not sure if you could find Shamiko build supporting the old Androids (8.0 and lower)

You may try with DenyList Unmount - although I also don't know what Android versions are supported (I'm on A11 hence I usually don't pay attention when installing)

IMHO, you will have similar problem with Zygisk-LSPosed
[Magisk] nayak.aj:
Thank you for your reply , I found the issue and it is related to the kernel version. It is also marked as wontfix in git.

Basically needs kernel version >3.18

Zygisk cannot activate on some old Samsung devices with old kernel (3.19-) · Issue #5395 · topjohnwu/Magisk

For some old Samsung devices, there's a kernel restriction that whenever exec an ELF from /proc, the process can no longer call some systemcalls. For kernel 3.19+, the workaround is fexecve, but it...

github.com
[Magisk] pndwal:
So real issue is no Zygisk... As mentioned there, if a custom kernel is available for your device, this should fix your issue... PW

Edit: seems S8 has official 9.0!... If you upgrade I'm guessing you'll have newer / fixed kernel... 🤔

Edit 2: This seems to confirm Zygisk now works on S8 w/ Android 9:

https://github.com/topjohnwu/Magisk/issues/5353#issuecomment-1029160257
[Magisk] nayak.aj:
Exactly. Should be a relatively easy fix. I haven't used the phone in 2 years or so and looking to trade it in for an s22 ultra. Gotta hide root before that :-D
[Magisk] pndwal:
See my edits above... Update to Android 9 will fix... 👍 PW
[Magisk] nayak.aj:
Thank you ! Very kind of you to dig that up :)
[Magisk] m0han:
Fox's Magisk Module Manager v0.5.1 is available
[Magisk] huskydg:
If your banking apps work fine, you should forget about what Momo found. Momo is known to have false detection of some check, someone report to me that it detect code injection on locked bootloader, "found zygisk" EVEN device doesn't install magisk.
[Magisk] shoey63:
Exactly.

In fact I read on one of the Magisk Alpha TG channels that TJW has referred to Momo as a "masturbation app"

Make of that what you will😊
[Magisk] Stillhard:
Now imagine 'that lonely girl' is doin' it all the times :LOL:
[Magisk] m0han:
going solo in solitary solitude ;)
[Magisk] martyfender:
Has anyone here tried huskydg's magisk delta and if so, what are your thoughts about it?

Thanks
[Magisk] m0han:
+1 to that. keen to know the steps taken to migrate and also prevent/minimise detection. @huskydg
[Magisk] dr4go:
@martyfender @m0han Switched from Alpha to Delta. 😉 Works perfectly fine so far. The steps are as usual:

- Unhide if hidden (restore the hidden app)

- Install delta apk

- Grant delta apk root from original Magisk / Alpha

- Flash Magisk through Delta using Delta's direct install

- Reboot

- Uninstall original Magisk / Alpha App only
[Magisk] Nekromantik:
Anyone here have issue with latest version of Shamiko and some banking apps?

My Starling app keeps closing itself when I have enabled Shamiko but if I disable it and revert to enforce denylist the app works fine but one of my other apps does not work without shamiko!
[Magisk] svendsvin:
https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-86914971

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-86998303
[Magisk] huskydg:
Try using my build, turn off zygisk (optional) and enable MagiskHide.

About Zygisk: Zygisk is still not perfect for hiding and zygisk leave very obvious traces for some apps such as Livin by Madiri (only work without zygisk). The problem is not "root is not hidden" but "Zygisk is not hidden". Riru has RiruHide to hide itself from scanning /proc/<pid/maps but Zygisk doesn't have hiding method and DenyList doesn't hide zygisk. If you are using LSPosed, recommended to use Riru for now.

Kitsune Magisk

If you apps are still detecting root, try install Riru - MomoHider: https://github.com/HuskyDG/Riru-Momohider/releases/tag/0.0.8-all-configs
[Magisk] Nekromantik:
thanks both
[Magisk] m0han:
- Unhide if hidden (restore the hidden app)

- Install delta apk

- Grant delta apk root from original Magisk / Alpha

- Reboot

- Flash Magisk through Delta using Delta's direct install

- Reboot

- Uninstall original Magisk / Alpha

isn't that Reboot required?
[Magisk] dr4go:
Why should this be required? Do you reboot your phone every time if you grant a new app root rights?
[Magisk] m0han:
Delta's direct install was not seen (there was only the vbmeta option) for flashing Magisk through Delta. Got it only after a reboot.