yashsingh1/xdaforums huggingface dataset:
[Magisk] TraderJack:
As mentioned, I needed to continue rebuilding and so don't want to keep testing things that may break my setup. While I did not test these things as systematically as what I reported on, I'm pretty sure (90%+) from the behavior I experienced from prior tests that the answers would be no to both.

I would not be adverse to trying to test them again (since I think based on my prior tests I can fix), but I'm curious what your methodology is?

If the answer were Yes to either of those questions, what insight would it provide in showing that the Momo app was not problematic in the way I demonstrated?

I suppose we could say that the issue with only Shamiko and LSposed, and not just LSposed but I'm not sure how that helps since I believe all 3 of these apps are basically maintained by the same people and they don't seem interested in acknowledging the problem, much less fixing it. I'm recording the info here more to let others know if they see similar inconsistencies and also as a warning that Momo may not be reporting properly. TBH, I'm not completely sure if I have an ART issue or not because how do I know wihch results to trust - the ones that I get after I install the app or the one I get only after I reinstall the app? :)
[Magisk] J.Michael:
I'm not saying anything about whether Momo is faulty. Clearly, there is something wrong with it.

I asked about a sequence that I thought was the only one you didn't report. Just trying to exhaust all possible sequences. No idea how it affects isolating the problem.

Except I thought you always said "LSposed and Shamiko" -- I wondered whether there was any evidence that Shamiko was part of this problem.

I agree, it is depressing when you can't get consistency from a computer.
[Magisk] TraderJack:
Ok. To clarify for anyone else as well.... A lot of my initial tests (which were exhaustive, but not quite as controlled) saw the same results with or without Shamiko. The main reason I installed Shamiko for my formal testing was:

1) Most people will be using Shamiko with LSposed Zygisk

2) Without Shamiko installed and Momo listed in the Deny List, all sorts of additional errors are listed as I listed above (found SU, Magisk, Zygisk, etc). So by having it there it whittles it down to only the main issues that can't be bypassed (user debug, bootloader, etc).

But, because I have OCD on this crap, I did some additional tests...

No. Because uninstalling LSposed requires a reboot. So if you remove it, reboot, then remove and reinstall Momo, Momo will still not report ART error (if it wasn't prior to uninstall). This goes further to show that while Momo seems to be the problem here, it is LSposed that is somehow confusing it.

No. I tested without Shamiko in this last round and it is irrelevant in the ART warning.

Additionally, in this last round of testing I only disabled the modules (not uninstalled). I did this to save myself some work and because theoretically it shouldn't matter. I placed my phone in airplane mode so that I wouldn't have any integrity issues while removing all my fixes. So, again, in theory this is fairly easy to test.

And one last thing I changed on these tests is that I removed Momo from the Deny List. This shows more warnings in Momo, but since I am only interested here in scoping the ART error, I just ignored them. Your last post triggered something in my brain that thought perhaps something linking into the DL could have been the culprit, but it doesn't look like it was.

UPDATE: Before posting this I did a couple of more tests and I think the problem can be summed up more succinctly in this way:

If Momo is installed PRIOR to LSposed being active, it will not report the ART error.

However if you install Momo after LSposed, it will display the ART error (this

includes

a reinstall/

upgrade

).*

If the error is generated by #2, it will not go away even if LSposed is removed.

The only way to remove the error is to disable LSposed, remove Momo, reboot, and install Momo first.

* This also includes removing the app and reinstalling with a Swift backup (which technically should be restoring all data).

IMHO, until the LSposed team can address this issue, I just can't rely on Momo's results to be completely accurate. The behavior it exhibits seems to indicate that it is somehow storing data outside normal app parameters (to compare some previous results). I can't explain it, maybe someone else can...
[Magisk] lukypuie:
BancaMPS app now working after upgrading to Android 14 stable on my Pixel 6

Don't know what changed.
[Magisk] nil?:
Hi there, I tried to solve the problem with broken Google wallet and made and attemt to install MagiskHide v1.10.3 to Magisk 26.4 (raven, UP1A Oct release); the installation stuck on the second line (Installing .zip); I made several reboots and after every reboot I found that Magisk says that the device requires additional setup to work properly and suggests a one more reboot. Then I decided to uninstall Magisk, upgdade ROM and install it again. I upgraded to UP1A Nov release and installed Magisk 26.4 again. No modules, but it still asks me for 'additional setup' and reboots. And when I'm trying to install any module, now I have the same problem: installation stucks on the second line.

Does anyone know what I might have broken?

UPD: found the problem; according to Magisk's source code, it tries to call env_check function from manager.sh and then show such a message if some components aren't present, in my case /data/adb/magisk/util_functions.sh was empty; after manual re-pulling Magisk can install modules.
[Magisk] nil?:
Hi, that's me again. I found that in some cases an installation of something via Magisk (including modules and Magisk files) results in nullified files. Last time this encountered with a AOSPMods module. I took the dmesg logs from the boot but I don't know where to look. Logs are attached. Maybe it's a bug in Magisk, maybe it's an issue with my device. Help is appreciated.

Files:

- dmesg-bad.log and dmesg-good.log are logs of cases where

the same

zip archive was installed as nullified files and correctly respectively;

- magisk-bad.log and magisk-good.log are logs from Magisk UI of abovementioned cases.

# This result corresponds to dmesg-bad.log
raven:/ # for file in /data/adb/modules/AOSPMods/*; do echo $file; xxd $file | head -1; done

/data/adb/modules/AOSPMods/build.type
00000000: 0000 ..
/data/adb/modules/AOSPMods/module.prop
00000000: 0000 0000 0000 0000 0000 0000 0000 0000 ................
/data/adb/modules/AOSPMods/service.sh
00000000: 0000 0000 0000 0000 0000 0000 0000 0000 ................
/data/adb/modules/AOSPMods/sqlite3
00000000: 0000 0000 0000 0000 0000 0000 0000 0000 ................
/data/adb/modules/AOSPMods/system
xxd: read: Is a directory

# This result corresponds to dmesg-good.log
raven:/ # for file in /data/adb/modules/AOSPMods/*; do echo $file; xxd $file | head -1; done
/data/adb/modules/AOSPMods/build.type
00000000: 310a 1.
/data/adb/modules/AOSPMods/module.prop
00000000: 6964 3d41 4f53 504d 6f64 730a 6e61 6d65 id=AOSPMods.name
/data/adb/modules/AOSPMods/service.sh
00000000: 504b 474e 414d 453d 2273 682e 7369 6176 PKGNAME="sh.siav
/data/adb/modules/AOSPMods/sqlite3
00000000: 7f45 4c46 0201 0100 0000 0000 0000 0000 .ELF............
/data/adb/modules/AOSPMods/system
xxd: read: Is a directory
[Magisk] sawdoctor:
Spotted a new "Private Space" settings page in Android 14 QPR2 Beta 1. Tapping "Create Private Space" creates a new profile of type android.os.usertype.profile.PRIVATE, which seems to be a new type of user in Android.

If I had to guess, this "Private Space" will let you hide apps on your phone from other people.

Android 14 QPR2 Beta 1 is preparing a new "app quarantining" feature.

Under Settings > System > Developer options, there's a hidden "Quarantined Apps" page that lets you "quarantine" apps. I'm not sure yet what quarantining an app entails, though, so I'll have to dig deeper.

Do we think either of these features could be utilised by Magisk going forward? Be nice if we could use them to hide root
[Magisk] pndwal:
If installing from zip, major refactoring (26.0+) means you will only have partial root and you need to reinstall Magisk while booted eg by taking Direct install on opening the App, to 'fully root' and gain module support as the changes require system to be analysed and Magisk selinux/module rules directory to be set with booted system... This makes more devices compatible with Magisk and still allows you to use the deprecated custom recovery installation method if you wish even though it's "no longer recommended"... Hope it helps, 👀 PW
[Magisk] HippoMan:
I would be extremely surprised if the Googlefrinchians ever provide any facility to actually make it *easier* to hide root.
[Magisk] Shantanu:
I just want to confirm that this method still works on the latest version of iMobile Pay and I'm so grateful for this quick and easy to follow tutorial! I was literally at the verge of buying a cheap temp phone just to use this banking app. Thanks a lot!
[Magisk] mGforCe:
One of Indian Fintech app is detecting root these days even after the usual approach of hiding.

Tata Neu - Shop, Travel, Pay – Apps on Google Play

One app for all your needs

play.google.com

Spoiler content hidden.

TataNeu app v3.5.1 is working fine. Versions after that are giving error of unsafe environment.

Specific for TataNeu app:

Root apps Hidden via HMA,

Configured to not see Magisk

Tried with & without selection under BootloaderSpoofer

Still no success. Any pointers / tips?
[Magisk] westruk:
Try kernelsu, no detection on v4.1.1
[Magisk] invalid_hash:
Are you still able to hide the ICICI app from root after the new update? Can You please check this https://xdaforums.com/t/banking-apps-using-lookout-com-services-to-detect-the-root.4639250/
[Magisk] mGforCe:
My phone doesn't have Kernelsu available.

Thanks for checking
[Magisk] mGforCe:
Yes, it is working fine for me. 17.2 or 17.3 started giving problem but update with update of Lsposed, they started working again.

Some users complained that 17.4 started giving issues again, but not for me.

There is a thread on imobile here https://xdaforums.com/t/imobile-app-is-not-working.4635029/ where people have success with ZygiskNext. You want to try that.

PS: I am on Magisk Delta
[Magisk] mGforCe:
On the same setup, I tried Zygisk Next after disabling inbuilt Zygisk.

Same status, TataNeu v4.1.1 is detecting root :(
[Magisk] TraderJack:
So I wanted to post another follow up regarding the various errors Momo might be throwing out for people. In my post quoted above I explain one scenario where you might see the "ART parameters are abnormal" detail and how to fix it.

I've just discovered at least one reason for another item in Momo "Suspicious traces":

"Restriction on non-SDK interfaces is not working"

I had asked about this previously and was told that it had to be an issue with my ROM, but this didn't make any sense because I was using a stock Pixel ROM. One post explains that this issue is due to a deodexed ROM. While this may indeed cause the issue, it isn't the only way. The following article has been referenced before and indeed it holds the key to the solution in some cases (including mine).

Specifically the issue is in the following system setting:

130|crosshatch:/ # settings get global hidden_api_policy
1

The article above explains this setting. If set, it allows the restricted APIs to be used and so, when Momo attempts to use a restricted API it succeeds. The solution, as the article states is to remove this setting:

130|crosshatch:/ # settings delete global hidden_api_policy
Deleted 1 rows

Now, when Momo attempts to launch the restricted API, it cannot:

11-24 14:58:26.541 18078 18102 W b2060.mahoshoj: Accessing hidden method Landroid/content/pm/ApplicationInfo;->getHiddenApiEnforcementPolicy()I (greylist-max-o, reflection, denied)

And Momo will not report the SDK suspicious trace!

The question now is why would you have this value set on your system in the first place?

Most likely, it is a rogue app doing this as there are apparently several ways to get around these SDK restrictions.

In my case, the culprit was an unexpected app: Tasker.

Specifically, the Tasker apps Task: Kill App

Everytime I run a Tasker Kill App task (using root privilege or not), Tasker will set the hidden_api_policy back to "1".

I've provided this info to the Tasker dev for explanation. In the meantime, I am using a different shell method to kill apps.

I suspect there are other Tasker tasks that will mess with this setting, but this is the one I was able to track on my device.

Hope this helps others.
[Magisk] morTimar:
App "keeps stopping" after Zygisk activation, Galaxy S7 Exynos, Android 8​

Hello all,

I updated to Magisk 26.4 stable but as well did try canary on my Samsung Galaxy S7 (Exynos) w/ Android 8.0.0.

After activating Zygisk without any module, apps have stopped/keep stopping (e.g. Android System WebView, WiFi Direct, CSipSimpel, my keyboard app).

After rebooting the magisk app still says "Zygisk: No".

Any idea how to fix this?

Many thanks in advance!

Device: Samsung Galaxy S7 (Exynos)

ROM: [ROM][G930F/FD][ALEXNDR] * U8EUE1 * DevBase v7.4
[Magisk] rodken:
Try switching to Riru to see if that resolves the issue or uninstall any modules temporarily to see if they're causing the app crashes.

Maybe, wipe Magisk and reinstall.
[Magisk] J.Michael:
Actually, since your original question did not mention "magisk hide", I doubt that that was what he meant.

He chided you for not making it clear whether you were asking a question, or making a blanket statement, or reporting a problem. I counter-chided him for not making his answer unambiguous.

From what I have been reading, one of the two interpretations of "magisk hide" is no longer part of the program. This "loss" is more than compensated for by the new "deny" function of Zygisk. Many people report success in passing SafetyNet under the new regime. The lack of one of the two "magisk hide" options is of no consequence -- except that you should stop looking for a button to enable it, because you won't find those words anymore.
[Magisk] Spartacus500:
A similar situation here, tested on Samsung devices, Magisk Zygisk hide + Shamiko does not help, but I found a solution in the log and after disabling this process, the application works
[Magisk] amit_coolcampus:
Can you please help with the name of the app you used to disable the process. And which log did you find that process in, Magisk?
[Magisk] amit_coolcampus:
Native magisk hide was a function of magisk since it was changed to Magisk Zygisk. Basically both fulfil the same purpose but the way of reaching to the destination is slightly different.
[Magisk] beeshyams:
How did you use 3C..very interesting. I asked over there (3c thread just now).. You may like to answer there. Thanks
[Magisk] Spartacus500:
CCSWE App Manager 5.0. It searches for the log by entering the name of the application that detects root, it is not always possible to find the cause.
[Magisk] szazs89:
Just in case you would decide to give up the new Magisk and want a working version 23.0, see this.
[Magisk] amit_coolcampus:
I tried to use this app. This doesn't move ahead of ¨activating knox¨ page.
[Magisk] martyfender:
Shamiko 0.4.2-97 has been released.
[Magisk] pndwal:
Those downgrading to 23.0

Are you guys having issues Hiding the Magisk app even with App Installed = 23.0 / Update channel correctly set to Stable? PW
[Magisk] zgfg:
Look for the posts (I've seen them at lesst three times since yesterday) describing how you have to set the Custom channel to point correctly/exactly to the particular old v23

With your setup, Update channel points to the latest Stable v24 (released few days ago, not to your old v23 from 9 months or so ago)
[Magisk] pndwal:
With my setup it does.

I'm wondering if those who have App Installed = 23.0 / Update channel correctly set to Stable have the issue. This should point to JSON correctly calling stub versioncode 21 (not current 24)... PW
[Magisk] neilth:
I have a Pixel 2XL which is rooted with Magisk 24.1that I cannot get certified in the Play Store. It is running LOS 18.1 and nothing I have tried has resolved this problem. It had been fine until several months ago running Magisk 23.1 when at some point certification was lost. I had hoped that upgrading to the latest Magisk software would remedy the situation, but no such luck. The YASNAC app tells me that I am running a version of Google Play Services which is too old, which is incorrect. This phone is using version 21.48.15, which should be fine. The system fingerprint is correctly set to Pixel 2XL Android 11 and all sensitive props are set active. I have included several relevant screenshots illustrating my configuration and the YASNAC error I am experiencing. I have looked through this entire thread, but I couldn’t find anything relevant to my certification problem.
[Magisk] pndwal:
No, neither hide nor MagiskHide = Zygisk.

The Zygisk powered denylist is a feature that does preserve parts of the MagiskHide code however.

Zygisk is a new (hooking) framework that injects code into zygote in order to allow modules to run their codes in apps etc. It supercedes Riru which is now deprecated.

Riru couldn't initially hide itself from from "/proc/maps string scanning", but later (v22.0+) RiruHide (based on Haruue's concept) was integrated to make the memory of Riru and modules anonymous (hidden) memory.

Zygisk has no integrated hiding solution, nor does Magisk root itself any longer.

The new MagiskHide is Universal SafetyNet Fix (ATM 😛).

The new 'RiruHide' is Shamiko (Hides Zygisk XHook and modules)... And it hides extra 'suspicious traces' in addition.

🤠 PW
[Magisk] zulu88:
Have you fixed your problem? I have exactly the same on Note9 after Magisk 24.1 update. I can see that everyone in the forum has a lot to say, but when there is a real problem, there is no meaningful answer.
[Magisk] szazs89:
I am not a developer, but have you tried to install Magisk as recommended here? https://github.com/topjohnwu/Magisk/blob/master/docs/install.md

(I had struggled with this problem, too, but finally gave up and managed to got back v23 with working SafetyNet check and self-hiding)
[Magisk] Prof_Shekhar:
I believe I have uninstalled the previous possibly Magisk v 23 with the help of one run of theAdb command with success result.

Should I run few Adb command few more times to be sure?

Is there a way to check presence of any previous version of magisk on my system, so I can remove each one of them?

As per your advice, I have searched every instance of

As per your advice, I have searched every instance of com.topjohnwu.magisk from Android data folders. No it doesn't appear in any more searches.

But the Magisk installation is still failing due to "unable to check signature" error.
[Magisk] Prof_Shekhar:
Finally, managed to reinstall Magisk 23.0 successfully following the instructions given here by topjohnwu:

Installation

The Magic Mask for Android

topjohnwu.github.io

It was most straight forward with easiest of all methods. No possibility of someone going wrong.

Would like to sincerely thank senior member & creator of Magisk for such an easy & foolproof method to root Samsung Phone 🙏🏻🙏🏻
[Magisk] xabu:
Now that you know how to go back, it's easier to take a step forward ¯\_( ͡❛ ͜ʖ ͡❛)_/¯
[Magisk] J.Michael:
Any chance you were updating from a hidden/renamed Magisk app?

You should unhide / restore the manager app before installing a new manager app.
[Magisk] morTimar:
Yes I did but since yesterday

I uninstalled Magisk completely and

installed 26.4 activated Zygisk without adding any modules and got the error

installed 26.3, activated Zygisk without any problem but Zygisk never really activated (Zygisk No")

adding USNF 2.40 was possible but says Zygisk is not enabled

installed latest Magisk-Delta, activated Zygisk (it's on, Zygisk: yes) but could not get past Safetynet Check so far.

Al in all I do not have any idea what causes the issue with Magisk 26.4 & Zygisk activation and apps keep stopping.
[Magisk] morTimar:
Solved it for me for the moment. More precisely tried to update Magisk in the 1st place because Google Wallet did not work anymore.

- uninstalled Magisk through the app

- installed latest Magisk-Delta because Magisk 26.4 did not work for me (see info in previous post)

- did hide Magisk itself

- activated Sygisk

- installed "PlayIntegrityFix" https://github.com/chiteroman/PlayIntegrityFix thanks to this thread https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/ and my Google Wallet is working again :)

- did hide the apps I wanted to in "MagisHide" but did not "Enforce SuList"
[Magisk] J.Michael:
"Enforce SuList"?

Did you mean "Enforce Deny list"?

I was under the impression that the only time there was any point to adding to the Magisk Deny list but not Enforcing Deny list was when using the Shamiko module.
[Magisk] morTimar:
It's because I installed Magisk Delta, a fork of Magisk as far as I understand.

"Enforce Deny list" seems to be called "Enforce SuList" there.
[Magisk] m0han:
@morTimar is right about Enforce SuList. Apps in DenyList (Kitsune Mask) are auto-populated from previous version of Magisk Delta.

Edit

: I don't have Shamiko module.
[Magisk] m0han:
https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89189323
[Magisk] mGforCe:
Hello Folks,

A long term user of Magisk, but on an old spare phone (Redmi Note 7 Pro, violet) am exploring KernelSU.

Some question on xposed modules detection by TBChecker even when HMA is active.

First, details on setup

Derpfest A14 rom which has kernel su synced

Now I installed following: KernelSU_v0.7.1_11366-release.apk and it showed me working at top.

Within KernelSU, went to bottom left button and installed Magisk modules as usual:

PlayIntegrityFix

Zygisk Lsposed

ZygiskNext

​

Then, rebooted and installed below Xposed modules

BootloaderSpoofer 1.2

HMA 3.2

Pixelify GPhotos

And then, configured HMA to hide root related apps from TBChecker, AppListDetector, RootBeer etc

While applistdetector and rootbeer doesn't detect anything, TBChecker is able to detect all Xposed modules and KernselSU even when hidden.

So - do we need to do anything further when using KernelSU + Zygisk + Lsposed + HMA. Any tips/pointers will be helpful?

PS: Not sure if this is the right thread or not to post.
[Magisk] J.Michael:
Did you run detection checks at every stage?

I thought I remembered that with KernelSU installed, you then did not have to do some of the things that were needed with the regular kernel. Like, don't enable Zygisk; or, don't install LSposed.
[Magisk] mGforCe:
Not at every stage, but atleast twice...after installing KSU and post all installed.

KSU app was detected by TB Checker at the first stage itself.

Even with KSU, we do need Zygisk, Lsposed etc. Just that we don't need to patch boot image or install Magisk apk.
[Magisk] GolDeN_xXx:
Hi, may I ask for updates?

Does it still work?

I unable to work on my TnGo eWallet, Standard Chartered and RHB, even though I have created the second space using Island.

Any advice?
[Magisk] CharlieMHz:
Hi, well that post was almost 3 months ago, but the setup now is still very similar, but with small differences:

Magisk Alpha 7826d752-alpha

Shamiko 0.7.3 (183)a

Play Integrity Fix 14.2

LSPosed 1.9.2 (7024)

HMA 3.2-410 to hide root apps like Magisk, HMA itself, App Manager, etc.

Try starting clean, with no modules loaded. Then start adding some modules to see if the banking apps start working. Also, I don't use Island.
[Magisk] steve8x8:
I was hit by this issue on a Sony z3c, waiting for the next stable clock tick - should I go for a canary instead?
[Magisk] pndwal:
Well since the fixes were already merged, I said may want to wait for 'next build' which was Canary... I purposely didn't say 'wait for stable'...

Up to you, but I'd be testing fixes in Canary...

BTW, it also sports 'early release' native bridge loaded Zygisk!... PW
[Magisk] GolDeN_xXx:
I am using ArrowOS. Although it passed 2 out of 3 of the Play Integrity, the SCB and RHB bank app still cannot be opened from the device.
[Magisk] Nergal di Cuthah:
Deny list? Shamiko? HMA? There are plenty solutions that might help you