yashsingh1/xdaforums huggingface dataset:
[Magisk] Tech = Spy-Biz:
Shamiko + Stop enforcing Deny List? OR Shamiko + Deny List Enforced? Do we have to use Shelter also?

Can you give the exact steps you did to get bank apps to work? TIA
[Magisk] Tech = Spy-Biz:
https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/page-91#post-87198517
[Magisk] Mepsipax:
Refer to my first post for how I got my banking apps to work. And yes, shelter was key. When I installed my banking app on my regular profile, it still detected root.

Now, the other app "WeConnect", still detected root in the work profile. That's actually for remote controlling my car, locking and unlocking it, stuff like that.

For that I just followed the installation instructions for Shamiko: Install as Magisk Module, include app in deny list, don't enforce the deny list, reboot. Then it worked.

Out of curiosity, I just tried both apps on my regular profile again, so without using shelter, but with Shamiko in effect.

WeConnect works there, banking app doesn't. Seems like two different approaches for root detection.
[Magisk] Tech = Spy-Biz:
Thanks friend, Though there is a one week old report on Shamiko not working for some banking apps but I will certainly check on your previous posts, never know may work (y)
[Magisk] Mepsipax:
I mean, there's a variety of banking apps with propably different approaches. But keep in mind that I needed Shamiko not for my banking app, but for my car app!
[Magisk] RANJITH THRISSUR:
Guys, I'm on OnePlus 9R, with the method provided in page 68, ie shamiko , lsposed , hide my app... I was able to use ICICI BANK app successfully. Suddenly, yesterday it starts to detect root. I just uninstalled those apps and re do the procedure. Still no luck... Is there any improvisation we need to to on top of the method suggested in page 68?

The help would be much appreciated for every icici imobile app users with a rooted phone.
[Magisk] zgfg:
Magisk Canary update 25202

Momo does no more report Zygote injection found!
[Magisk] pndwal:
You mean April?... Well new Play Integrity API take-up began in June, and SafetyNet was deprecated at the same time...

I guess it could be a coincidence!?... What do you think?...

Maybe you aughta catch up and check if you can achieve MEETS_DEVICE_INTEGRITY verdict using Play Integrity API Checker...

Yup, yup, that might be a good start... 🤪 PW
[Magisk] pndwal:
FWIW, I never had that on A10 MIUI previously... Got Found Zygisk however...

w/ 25201:

PW
[Magisk] martyfender:
On my Android 9 devices, momo reports Zygote injection found.
[Magisk] pndwal:
@zgfg

... Not any more! 😬🤷🤔 ...

w/ 25202:

... Was yours A11 device still?

... Seems we're getting some kind of role reversal here... 🙃 PW
[Magisk] zgfg:
Yeah, also Zygote injection

I forgot that usually Momo does not show that on first test, but if I close and reopen Momo, then Zygote injection is found

I don't have init.rc for long. Don't recall was it solved by checkmarking all Momo processes in DenyList (or with the latest Shamiko)
[Magisk] ashish1989:
I am on custom aosp android 7.1.2 rom on my samsung core prime G360H. As soon as I am enabling zygisk from magisk settings, the phone is stuck on boot logo. I have magisk 25.2 installed in it with xposed 3.1.5
[Magisk] zgfg:
Please check the first page - it must have been described there (and/or long ago in Magisk General thread)

Old XPosesed is NOT COMPATIBLE. Neither Riru (if you have any Riru module)

There is Zygisk-LSPosed instead. But not sure if Zygisk-LSPosed is compatible with A7
[Magisk] ashish1989:
Should I not enable zygisk then? But my play store is not certified. And what about some apps which I want to add in deny list to hide them from seeing root access. What can be the best solution now for all above?
[Magisk] zgfg:
Cannot advise you about A7 (I had A 7-10 3-5 years ago)
[Magisk] ipdev:
I am a bit lost now.

From your prior post (in the USNF thread) you state that you have Zygisk: Yes

This would only show Yes if you enable Zygisk and reboot at least once to activate Zygisk.

Only adding PlayStore to the denylist was what caused the infinite/stalled boot.

Without installing any modules, without enforcing the denylist, without adding anything to the denylist.

Can you boot with just Zygisk enabled?

If not, then since it is an older Samsung (G360H) that was last officially updated to Android 5.1.1(?).

More likely your kernel has not been updated (patched) to work with newer Magisk version.

See Magisk [WontFix] - [GitHub] - Link

- You will have to ask the rom dev if they can update/patch the kernel to work with Magisk Zygisk.​

If you can boot with just Zygisk active, then it is some other conflict that is causing your infinite boot.

Zgfg is correct about older xposed.

LSPosed will work with newer Magisk.

Post # 9 - Points of Interest

Cheers. :cowboy:
[Magisk] martyfender:
That is strange, on my devices, it detects more on the first opening, then less on subsequent openings. However, initrc is always detected.
[Magisk] huskydg:
Use MagiskHide in my latest Canary fork with no zygisk
[Magisk] ashish1989:
Can you share the link?
[Magisk] huskydg:
No, just don't care about momo if your banking app is working
[Magisk] ashish1989:
@ipdev @huskydg @zgfg what I always do in my other phones with A10+ is I enable zygisk and force deny list and add play services only gms and gms.service options in it and flash safetynet fix zip file through magisk, I do not check play store. These instructions are already given, which I do the same and my device is certified in play store.

As my device is old with custom rom having A7.1.2, I am not able to activate zygisk bcoz its not patched with latest versions.
[Magisk] huskydg:
You can even hide root without injecting through riru or zygisk. Riru or zygisk just make hiding root process can handle apps more easily. Inject zygote is not a good idea and can cause more detectable, specially zygisk.
[Magisk] ashish1989:
I can not boot with zygisk active

Even Lsposed supports android 8.1+

I tried that but no luck, phone is stucking at boot logo
[Magisk] ashish1989:
How, through the fork which you were discussing above
[Magisk] pndwal:
Don't add these; USNF will just remove them on next boot anyway unless you use Shamiko etc instead of Enforce Denylist, and even then USNF will hide them itself and Shamiko hiding will be redundant...

So what does this:

mean? 🤔 PW
[Magisk] ashish1989:
Actually the zygisk was activated, before flashing xposed framework zip, that's why I said that. But when I flashed xposed framework zip, phone stucks at bootlogo
[Magisk] pndwal:
You can't use any XPosed AFAIK unless get A8.1 update...

But... If

is actually wrong, you can still use Zygisk and don't have the kernel issue we mentioned...

I knew @kdrag0n's Zygisk parts were disabled as they are all evaluation type fallback / attestation type enforcement related and not needed...

It would be good if (hoped that) @Displax (modded version / official pull request) Zygisk part for targeted fingerprint prop application could remain active as it would complete the solution for Android 7 devices...

Of course this was added principally to trigger a hardware based attestation enforcement bypass also (but for Play Integrity API in this case), but it is also very useful for anyone needing proper targeted CTS Profile Match fix (both on devices w/ hardware keystore and without) for uncertified (China, developer, beta, custom) ROMs... I note that traditional MHPC applies such props globally which is potentially (more) fraught.

🤠 PW
[Magisk] Depressed T.Bear:
Does anyone know why Magisk 25+ refuses to work on certain custom roms and why related issues get deleted on github?

Do alternative forks like magiskDelta work?

I'm just curious..
[Magisk] zgfg:
Maybe a kernel or something not compatible.

Or, some developers pre-build (an old version of Magisk) into the ROM (clearly advised against in the Magisk GitHub documentation - exactly eg since it could cause troubles when users would want to upgrade Magisk)

If you are talking about Issues on Magisk GitHub:

- When opening an Issue, you must provide all required info and Issue must be related to the LATEST CANARY.

If not, Issues will be closed automatically in a second or two by a bot (unfortunately, without any explanation).

Open couple of successfully submitted Issues (status Open) and study how the authors entered their initial comments (filling data about Magisk, phone, Android, etc)

- If ticket survives the bot, it might be closed by developers for a particular reason (eg, that Issue is on your custom ROM side, not Magisk side or so).

But in that case you will receive a mali and you will see who closed the Issue and with exactly what comment/reason (although usually not very detailed)
[Magisk] pndwal:
Issue is most likely Refactoring of 2SI magiskinit injection; some custom kernels (eg Kirisakura, Dr.Ketan(?)) rely on Magisk to strip AVB flags which is no longer done (was only needed for fstab patching)... My guess is that many custom kernel Devs may have updated methods available by now...

Summed up and included methods to disable disable-verity / disable-verification here:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/page-2631#post-87134821

- this may not be enough to fully disable AVB however...

... Can check my posts around June 23 also.

Please link your closed issue...

Not if it's this issue; they built (sync) same commits for Magisk injection etc... 🙃 PW
[Magisk] Depressed T.Bear:
Thanks for your replies! I might mix up some things, actually I don't know if it's working.

The issue is the Magsik Manager app, which stuck on the logo screen and therefore doesn't open since version 25.x.

My rom dev stated the following regarding the issue:

I was just curious if you might have an idea how to solve or work around this.
[Magisk] pndwal:
Oh.. so the App... Is Jaguar a pre-rooted ROM?... Please say exact working Magisk version and App version... Or screenshot Magisk App... 👍 PW
[Magisk] pndwal:
... Bit further; looks like vv has effectively commented here:

https://github.com/topjohnwu/Magisk/issues/5954#issuecomment-1151779493

I'm not familiar enough with the code linked to comment much, but it seems the issue stems from the GrapheneOS base for Jaguar V21 ROM, having to do with a 'gmscompat' issue (and GmsDynamiteHooks.java ?)...

According to label applied, it's not a Magisk issue...

Someone here more familiar with such code may be able to comment further... 🙂 PW
[Magisk] 73sydney:
Smart ROM devs, and ive seen a few, leave magisk as an option, usually an option in Aroma installers, the lazy prebake it directly into the ROM, which is as previously mentioned a quite bad idea...

p.s. even if i see it as an option in an Aroma installer, i usually ignore use the latest from the official link....
[Magisk] Depressed T.Bear:
No, Jaguar is not pre-rooted! :) The last working Magisk app version is 24.3 (24300) (33)

Not pre-rooted! :)
[Magisk] pndwal:
I see from OP there rom can be installed and bootloader locked!... Are you bootloader locked? PW
[Magisk] Depressed T.Bear:
Yes, it's possible, and I'm planning to do so in the future. As of now, my bootloader is unlocked
[Magisk] huskydg:
It's told that hidden ability of zygisk is insufficient
[Magisk] Depressed T.Bear:
I'm gonna try opening an issue on github.. Hopefully it doesn't get closed without someone actually taking a look :/
[Magisk] huskydg:
If Your issue is closed, mostlyyou don't read their report template and don't attach some information according to template.
[Magisk] Depressed T.Bear:
Husky, I really like your work and contributions!

But what makes you think that my issues got closed? It's just that I read that they did - if I open a ticket, I'd add all information needed.

Please be respectful and don't accuse me of wasting their time :)
[Magisk] huskydg:
Oh, sorry, i thought there was your issue on github. But the fact topjohnwu doesn't have time to take a look on github issue.
[Magisk] Nightf0x_007:
First of all thank you huskydg for your magisk fork

Pixel 6 here On a12 i was using zygisk with shamiko & i have an app that is very stubborn in terms of root detection but it was working updated to a13 & it stopped working so i switched to magisk delta stable & returned to use the old methods (riru momohider unshare magiskhide) & the app worked, today when i tried opening the app it didnt work i updated to latest canary build also its not working but 1 thing i noticed that is this app had before an isolated process in the magiskhide menu where it had 2 items now only 1 & this (isolated) process isnt showing up, could this be the cause that the app started to detect root again?

My setup: p6 a13 magiskdelta latest canary, momohider, riru unshare, safetynetfix v2.1.3, mhpc, enhanced mode for magiskhide, magiskhide enabled, initrc hider, device certified, pass safetynet, magisk & lsposed hidde, hidemyapplist xposed module (enables but not using it)

*The only thing i did is i downgraded lsposed to version (6580) from (6599) idk if this could me causing the problem

* Rootbeer all ok, momo cant start service environment broken, applist detector all ok but detects the hidden magisk app
[Magisk] huskydg:
The latest canary delta,magiskhide relies on logcat to detect app process. if your logcat is abnormal or turned off (Logcat Killer), it will not work. If you certainly sure that you do not turn off logcat. Open github issue on my repo and let me know.

Thanks
[Magisk] Nightf0x_007:
No i dont have any logcat killer, how can i check of is abnormal or off?, Some apps which have isolated processes is what detecting root, also some apps that was working just fine started to stop working due to root detection, i think something is abnormal
[Magisk] pndwal:
Many apps are simply switching to new Play Integrity API as SafetyNet API is already depreciated...

Some devices (mostly Android 10 and below) need only standard USNF, but others need a fingerprint prop adjustment to bypass new hardware attestation enforcement... You can check if you pass deviceIntegrity using Play Integrity API Checker (... Don't worry about strongIntegrity yet; no known banks use it yet as it would exclude all users with Android 7 or earlier, and more).

If needed, @Displax's fix, working for most Zygisk users, is here:

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

You may be alright with that and Shamiko now since you say isolated process disappeared from your app...

If you still need old MagiskHide only / @huskydg's delta, his Riru - Play Integrity Fix may be what you need:

https://github.com/HuskyDG/riru-integrityfix

🤠 PW
[Magisk] Nightf0x_007:
Yes i already was having ysnf 2.3.1, will try the integrityfix and see, maybe the whole thing happened when i was switching between magisk builds beta stable and canary and magisk alpha this like made holes in the whole magisk environment and made apps starting to detect root as some apps with not much strong security no more working her, no matter now what im using zygisk & shamiko or riru magiskhide they detect root, maybe i will wait until next month google update & uninstall root completely before updating then reinstalling my root setup again from scratch
[Magisk] pndwal:
Official USNF does not yet fix deviceIntegrity (largely needed w/ Android 11+) for new Play Integrity API, although @Displax's pull request in USNF GitHub is receiving attention...

Expect more and more banks to migrate to this API since Google's Announcement:

https://developer.android.com/training/safetynet/deprecation-timeline

👀 PW
[Magisk] Nightf0x_007:
Yes i have the displax version, imo this is not whats causing problems here, i think switching btw. Different versions of magisk & sometimes using zygisk other times i go back to magiskhide broke something which is causing this behaviour from some apps
[Magisk] pndwal:
Yes, it's possible...

Especially when swapping w/ unofficial builds configuration will often not be aligned with current build property unless it is set up clean, ie. files in /data/adb incl. magisk.db are deleted...

You can always do this after installation to fix inherited incompatible configuration; just delete everything in /data/adb and reboot. Magisk daemon will rebuild configuration files... You can even keep your configured modules etc if you wish and are familiar with the file structure... PW
[Magisk] huskydg:
Why kdragon doesn't update it, or there are no good solution for that?
[Magisk] hahagu:
Hey,

So, I have a Poco F1 and the Nothing Phone (1).

They both have magisk installed, with the following modules.

- Shamiko

-Universal SafetyNet Fix

- Zygisk - LSPosed

However, on the Poco F1, my banking app works fine.

On the other hand, on the Nothing Phone (1), the banking app will detect root.

Using Momo, they both detect Zygisk, even though Shamiko is in use,

so I suppose zygisk is not the issue.

The banking app version is the same. Both devices on Android 12 too.

The app's name is "Toss", and is a Korean banking app.

The app also detects root quite quickly, within a few seconds of launching the app, but not instantly.

How do I go about debugging and possibly fixing this?
[Magisk] huskydg:
Zygisk leaves obvious traces and cannot be fully hidden. It is recommended to close zygisk and use riru instead.
[Magisk] hahagu:
I suspect, though, it's something else than zygisk.

On the Poco F1, Zygisk is still detected, but the app still runs.

On the other hand, on the Nothing Phone (1), I have removed magisk now, but it still fails to run.

Bootloader is unlocked on both of the phones, so I don't really get what is causing this.
[Magisk] pndwal:
For a start, check devices achieve Play Integrity deviceIntegrity using Play Integrity API Checker in case app has integrated PI (SafetyNet is now deprecated) per Google's recommendation... If not, you may need modded USNF:

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

🤠 PW
[Magisk] pndwal:
As you know, he's aware and thanked @Displax for his fix / PR... And he does clearly want to improve the solution and scope the method

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

He has already suggested an idea for adding an end hook, but said:

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

- So it seems he's in no rush himself, and he's happy for other Devs to test / contribute (although none appear to have tried adding hooks etc yet)...

I guess he'll do more on this PR as time allows... If other Dev's haven't had time to test even proposed

idea, then he may think 'why should I rush?'... He probably has a ton of more important maintenance on his plethora of apps, utilities, Proton ROM / kernel builds, etc to do...

Meanwhile, @Displax solution seems a pretty good one to tide us over, for most devices... PW
[Magisk] hahagu:
Did try the modded version 😭

No luck..
[Magisk] pndwal:
So what Play Integrity API Checker results now? PW
[Magisk] hahagu:
The modded version will pass the upper two, but not the last one, which is to be expected.
[Magisk] pndwal:
Yes... That's why I said "check devices achieve Play Integrity deviceIntegrity", (not strong integrity... 😜 PW
[Magisk] Tech = Spy-Biz:
Now 2 bank apps are working out of 3 after the recent update to the bank apps.

I used A11 GSI, PhhTreble App Signature Spoofing, TWRP, Magisk 24.3 & a couple of important modules like Hide-User-Debug, USNF Moded, Hide-Props-Config, microG Gapps module safety net : All passed, Installed the bank apps through Aurora.

For the 3rd bank app Dev Options need to be OFF & Only PlayStore Install allowed not PackageInstaller.

Needless inconvenience from banks, they can just add more steps of verifications instead like Voice Recognition IVR AI (Voice Recognition IVR AI Bots are already functional in these banks helplline numbers) so they can just use that for bank app login verifications on top of other verifications. Its none of the banks business to stop their clients from using rooted devices. Theyre just adding another hindrance to smooth banking operations thereby possibly hampering their own business by wasting both their and their clients time. Thats Stupidity!

Bank Devs did you hear? Pls discuss this with your bosses. Its like going backwards instead of forward.
[Magisk] HippoMan:
I totally agree!

And as I've mentioned here before, every desktop computer is a rooted device, and of course we don't see the banks trying to hinder us from accessing their services from our computers.

And banks gladly issue us debit cards which we keep in our wallets that are just as easy to steal as mobile devices.

Rooted Android devices are just low-hanging fruit. And the amount of fraud that's prevented by trying to fight against Android root is minuscule, given the extremely small percentage of mobile device users who want to use rooted Android devices. I wouldn't be surprised if the amount of money that banks spend for anti-Android-modding software development exceeds the maximum amount of money that could be lost via the hacking of modded Android devices.
[Magisk] pndwal:
Tech = Spy-Biz, HippoMan​

FWIW, I'm answering this here (might be the best place...):

https://xdaforums.com/t/discussion-play-integrity-api.4479337/post-87393295

😝 PW
[Magisk] zgfg:
Currently, I have no info about Device Certified or not in Google Play Settings (screenshot)

I observed that yesterday night when I upgraded my Xiaomi 11 Lite 5G NE from the previous week Xiaomi.eu weekly (MIUI 13/A12) to the current.

I thought it would become Certified over the day, but it's still in limbo

Frankly, last week when I installed Xiaomi.eu Weekly (first time) I forgot to check

Everything else is ok, SafetyNet (with Basic CTS), Play Integrity (Basic Integrity), Play Protect is ok, Netflix eg running with L1, etc

I'm kind of worried to wipe Google Play Data - not knowing would it become Certified or Not

I'm pretty sure I did have similar cases in the past with previous devices, ROMs, Magisk setup, but they used to settle down by itself in
[Magisk] m0han:
Are you able to update apps and/or make in-app purchases on Play Store?
[Magisk] zgfg:
Yes, of course, I install and update apps, but I very, very rarely purchase something, hence I'm not going to try
[Magisk] zgfg:
After wiping only the Cache for Playstore and waiting few more hours, now Certified
[Magisk] mrjuniork:
Mod Info:

Dear people of this thread,

pls stay on topic and do not engage in world-events related discussions. This thread has seen enough of it already.

In the name of peace and prosperity,

Happy Zygisk-related posting,

Cheers everyone
[Magisk] zgfg:
Zygisk-LSPosed update to v1.8.4 (6609) - updated on two phones, ok

Regarding to LSPosed modules:

-CustoMIUIzer13 (for MIUI 13/A 12) updated to 22.09.07

- I also use GravityBox (S) for A12
[Magisk] sir_overthrow:
It happens to me after a while of restarting the mobile. I use mokee android 11 on a moto z2 force. This same problem also happens to me on lineages 18.1 and 19.1.

Reboot, use YASNAC and it passed! but after a while the timeout appears. The funny thing is that from that moment I can not see the files of the internal memory. Although if I search it appears lol... I have used hide props magic all possible configurations, shamiko and safetynet 2.3.1 including a mod from this thread (By display) and without results. What am I doing wrong?
[Magisk] zgfg:
Have you tried without MHPC - just with USNF 2.3.1-mod

Otherwise, must be something specific to your device/ROM
[Magisk] sir_overthrow:
It is curious because there is an unofficial version of lineageos 19.1 that works just installed yasnac. No timeout. AT the moment you use Magisk (in my case to create whatsapp mount part from internal to SD for example). It behaves as mentioned. If I don't change the fingerprint I can't use banks.

But I don't reach that level of depth. Thank you very much for answering ♥