yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Experiments with Momo 4.0 - thanks to @Eng.Raman for hints

---

First set of screenshots without Magisk (original boot.img)

- USB debugging disabled to prevent Momo reporting Debugging mode enabled

Btw, as @pndwal mentioned several times - actually, originating from Github - MagiskDetector false-positively reports initrc modifications)

Second set of screenshots with Magisk Custom:

- Zygisk disabled

- MagiskHide enabled and Momo enlisted - prevents Momo to find SU, but Momo still finds Magisk?!

- USB debugging disabled (to prevent reporting that "Debugging mode is ebabled")

- LSPosed is disabled to prevent reporting that "ART parameters are abnormal"

- Momohider with isolated, setns and app_zygote_magic options enabled - app_zygote_magic is neccessary to prevent Momo complaining that MagiskHide is enabled (causing Momo to declare Broken environment)

---

Momo still reporting:

- "Bootloader unlocked" (both with Magisk and without)

I have KeyAttestation device (TEE) and I don't believe if I could spoof unlocked BL like for SafetyNet (SN passes)?

- Restrictions on non SDK not working prooerly - what is that (and how to fix?

Also without Magisk (original boot .img) - hence not caused by Magisk

- "Found Magisk" and "Partition mounted abnormally" what's that (second one) and how to fix?
[Magisk] Soumy1234:
Interesting. I have almost the same setup except LSPosed is on and BL is locked on custom ROM. My Momo straight up tells me the environment is broken without stating any reasons why. I guess this isn't really a good thing?
[Magisk] paul_cherma:
Hey guys,

I was using the old magisk (the one with magisk hide) and I had repackaged it to an app with a custom name. I uninstalled that app but my modules are still working. Modules like GravityBox and a few other ones. Why is that?

Any tutorial I can follow to install the latest magisk? I've tried searching around but haven't found one yet.

Thank you
[Magisk] pndwal:
May find something you haven't tried here:

https://github.com/topjohnwu/Magisk/issues/985

here:

https://github.com/topjohnwu/Magisk/issues/2841

or even here:

https://github.com/topjohnwu/Magisk/issues/1152 😜 PW
[Magisk] purgy:
The app just manages the actual framework, so removing it doesn't affect modules already set up.
[Magisk] paul_cherma:
I see... Can't find a tutorial on how to install/update to the latest. Any link for that?

Update: was able to switch to the newest canary
[Magisk] zgfg:
Magisk app (former mngr) is not the Magisk itself. You have uninstalled the app/mngr and you can no more manage the Magisk but Magisk is still active (patched img and Magisk database and modules still on /data/adb)

If you don't want Magisk, you had to uninstall Magisk (there was the option in Magisk mngr/app)

Install Magisk app/mngr again to continue managing Magisk, or to uninstall Magisk

You can also flash uninstall.zip

It is documented, go to Magisk Github and read the documentation (tutorial, wiki)
[Magisk] zgfg:
Almost the same = not the same. Small details might be very important

E.g., did you scroll down in Momo and read about MagiskHide causing the broken environment.

As I wrote:

>> app_zygote_magic is neccessary to prevent Momo complaining that MagiskHide is enabled (causing Momo to declare Broken environment)

But without precise details and screenshots cannot conclude what's going on
[Magisk] DomeNinchen:
Hello

Does anyone have a workaround for sparkasse bank's S-Pushtan app?

The app detects despite Magisk hide root

Thanks already
[Magisk] zgfg:
Please use Search this thread for PushTAN

I remember, there was some discussion about
[Magisk] konfuzius4u:
well you did just uninstall the frontend part of Magisk. That does not uninstall the Backend part of Magisk and does not uninstall the modules that you had installed before.

So install again the version of Magisk that you had installed before. Inside the Magisk app uninstall all the modules (reboot). Then complete uninstall the Magisk app from inside the app (important !) and not from the app uninstall section of your Android (reboot). Eventually rename the Magisk APK file to uninstall.zip and uninstall it with your custom recovery. See https://www.didgeridoohan.com/magisk/MagiskUninstall

Edit: just saw that zgfg had also already answered your question.
[Magisk] 73sydney:
A quick browse of threads in Magisk section gives you this

https://xdaforums.com/t/magisk-hide-guide-s-pushtan-app-maybe-more.4294761/

Plus of course theres also the umm search box...
[Magisk] zgfg:
Search in this thread gives me 14 or so posts about PushTan between Sep 29 and Oct 33 - screenshot below
[Magisk] m0han:
you meant Oct 31 ;)
[Magisk] pndwal:
Re. Sparkasse bank S-PushTAN app:

Very interesting detection method used by this.

You will likely easily succeed hiding 'root' (ie. UEE, Untrusted Execution Environment) with Magisk App uninstalled; even 'Hide the Magisk App' doesn't work for the following reasons:

Push-TAN is simply detecting Magisk App which is why freezing this works, BUT 'Hide the Magisk App' alone is not enough as with that only the package name changes. The classes.dex with the code does not change and can be used to identify the app. Their protection engine (Promon) seems to employ simple pattern matching on the installed apps.

Rebuilding the stub app combined with Magisk Hide hides it successfully. As mentioned in GitHub Magisk Issue #1084, "a simple app packer [does] mitigate the detection very easily"

Simple use of luckypatcher and likes won't be enough however. - These may alter file hash signatures, but you "have to know which code patterns are detected to patch the right location"

Re. detection countermeasures:

- Methods for rebuilding stub etc. are mentioned in issue #1084.

- You may alternatively be able to find / use an older S Push-TAN app.

- Airfrozen / Ice box freezing methods also work.

***Edit***

- Just tried LSPosed / Hide My Applist module, and it works with Magisk App active!

Method: see next post.

I posted GitHub Issue and other links here:

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

Hope it helps. 🤠 PW
[Magisk] pndwal:
Further to my post above (edited also) I just discovered a working method!

- I Just tried LSPosed / Hide My Applist module, for this, and it works!

Method:

Put S Push-TAN in Magisk App denylist.

Hide the Magisk app (I haven't succeeded with standard Magisk App).

Next, configure Hide My Applist as follows:

Select S Push-TAN app in Select Effective Apps, Enable hide, Leave Work mode as Blacklist, Select hide methods = API requests and/or Intent queries, Add hidden Magisk App name under 'additional apps invisible', Save this configuration.

* You should be able to use only one of these hide methods. Either method worked for my RN8T w/ Android 10, but a Xiaomi user w/ Android 11+ needs Intent queries set. This likely has something to do with Google's requirement that all apps / updates hosted on playstore from Nov 2021 need to adapt to Android 11 and are prohibited from acquiring app list any longer.

-->> First time I've seen German S Push-TAN app home screen instead of a browser page opening!

👍🎊🎉 PW
[Magisk] Soumy1234:
This is all it shows lol
[Magisk] Eng.Raman:
New Momo 4.0.1 released.

New features:

4.0.1 (2021-11-09)-Support Zygisk

detection

-Adapt to Android 12

-Display check code when no abnormality is detected to prevent tampering of detection results

Update Log ( According to the TG magisk alpha channel):

-Fix false positive in zygisk.

-Repair package management exception detection.
[Magisk] paul_cherma:
I was able to finally install the new Magisk Canary. I am also using the Zygisk-Lsposed module and removed all Riru Modules since they don't work with my Magisk version. Is there anyway I can pass SafetyNet? I tired a few different ways from what I read here but failing so far.
[Magisk] zgfg:
LSPosed will not help you about SN

You have to properly configure DenyList and that was described nin this thread several times (it doesn't nmatter was the post for Alpha or Canary, it matters only is it about DenyList and GMS)

But for particular phones (like Pixels) you need additional modules (particular version of USNF)- again search/read back in this thread

Btw, I don't use Canary (or Alpha) anymore, neither Zygisk nor DenyList and I'm not interested about them now :-(
[Magisk] klemi71:
Mmh, I'm interested in reverting to older version that includes hide, doesn't break riru, ... Can you share download link and tell me how to? I don't have TWRP.
[Magisk] zgfg:
No, I'm using new 23013 but Magisk Custom (Zygisk not obligatory , MagiskHide instead of DenyList and old Modules repo). All the rest in line with the newest Canary

Search for (Magisk) Custom, was posted (links, everything) and discussed here
[Magisk] paul_cherma:
I'm only using Lsposed because I need some modules that need Lsposed to work but yeah I'm using a Pixel device so that makes it even harder for me to pass safetyNet
[Magisk] dcarvil:
I you mean the latest stable version, it is still in the usual place. https://github.com/topjohnwu/Magisk

Scroll down to downloads, and click the Magisk V23.0 icon.
[Magisk] JustLauro:
If you pass Basic Integrity but fail CTS profile you can install USNF 1.2.0 as it doesn't need Riru to work. Or you can wait for version 2.2.0 of USNF, which works with Zygisk. Unfortunately that one is currently early access so you have to wait or pay $5.
[Magisk] tech_head:
If it makes my 9 Pro pass safety net, then I'll bite. I'm not going to bite only to find it doesn't work.

While passing safety net and running pay is high on my list; wasting money is not.

Anyone with a OnePlus 9 pro passing safety net?
[Magisk] paul_cherma:
I'm failing both Basic Integrity and CTS profile so I guess I'll wait. Hopefully it works with my device
[Magisk] JustLauro:
I think USNF only fixes the CTS profile check. Did you activate Zygisk and put Google Play Services to Denylist?
[Magisk] paul_cherma:
Yep, I did. But it's failing both rn. Pixel 5 device
[Magisk] pndwal:
Just to be clear for those following posts here, while @TheHitMan Custom Magisk was removed along with Telegram group, it was quickly revived with new Telegram group and is still active... PW
[Magisk] tech_head:
I'm going to try that route. I may roll back to the older version with MagiskHide included.

I know my OnePlus can't do Pay and I liked being able do pay. Not enough to give up root.
[Magisk] ipdev:
Basic and CTS will fail SafetyNet on stock Google.

The USNF v2.2.0 module will fix SafetyNet.

Cheers. :cowboy:

PS.

Screenshot(s) with and without USNF v2.2.0 active.
[Magisk] paul_cherma:
I'm on a custom ROM, Proton Rom from kdrag0n. He also develops Proton kernel which passes safetyNet without any mods. But I'm running Proton Rom with EX Kernel, so thats why I'm having issues with SN. I'll try the USNF 2.2.0
[Magisk] ipdev:
Proton is on my to try list. ;)

I am not sure if using the Proton kernel would help.

Normally just installing Magisk will break SafetyNet on custom roms that include tricks to pass SafetyNet.

Good luck.

Cheers. :cowboy:
[Magisk] ipdev:
Not a waste of money.

Think of it as a $6 donation and you get a free gift. 🙃

I can can not tell you if it will work on newer OnePlus devices.

I can tell you it fixes SafetyNet on Pixel 3a, 4a, 5, 5a and 6.

Also a sponsor noted that it works on a Pixel 6 Pro.

Even if v2.2.0 does not work for you.

The donation will help encourage the developer to keep moving forward. ;)

Maintaining, improving and fixing what is not working or breaks in the future.

Cheers. :cowboy:

Edit:

Just had time to check.

UNSF v2.2.0 also works on Poco F2 Pro (stock MIUI Android 11).

MIUI v12.5.3.0 (RJKMIXM_20210901.0000.00_11.0_global)​
[Magisk] m0han:
you must be on MagiskCustom 83eb60ed now, i suppose. i am too. all well. btw, have you tried the latest custom LSPosed by the same dev? your thoughts on that, please.
[Magisk] zgfg:
I don't see any reason for Custom LSPosed. I use Riru-LSPosed with Riru (since myZygisk is disabled) and everything works fine
[Magisk] moocow1452:
Thanks for the insight. Regarding carey036's suggestion using Magiskboot to manually change the Magisk patched boot.img, would it be somewhere in the apk, or in source? I looked at https://topjohnwu.github.io/Magisk/tools.html but it didn't really give me an answer one way or another.
[Magisk] Draizix:
What is the link for the new Telegram group for it?
[Magisk] martyfender:
Telegram: Contact @custommagisk

t.me
[Magisk] JakeDHS07:
So it seems that Google Play Services does not want to stay on the DenyList. No matter how often I check it off when I go back it always seems to be unchecked again. Am I missing a save option or is this happening to anyone else?
[Magisk] klemi71:
Depending on USNF version it is removed because it isn't needed.
[Magisk] JakeDHS07:
I'm using the 2.2 zygisk build off patreon
[Magisk] m0han:
i'm aware that detecting init.rc modifications by Magisk Detector is not reliable, but with today's MagiskCustom 8f649048 update, Magisk Detector began reporting 'modified' even after clearing cache & data and restarting.

Another thing: MagiskCustom updates do no get 'dirty-installed' for me. I've to uninstall and do fresh install. Is this a known thing?
[Magisk] zgfg:
I have updated today's Custom (what you call 'dirty' way) with absolutely no problem

And for me MagiskDetector ALWAYS (except one day, one time, until I rebooted) declares init.rc modifications (previously I tested also with Alpha and anary, the same result)

Besides, few days ago I posted screenshot (s) when I flashed the non-patched boot.img (hence without Magisk), and it was constantly showing init rc 'modifications' despite that I deleted Cache and Data or even uninstalled and re-installed MagiskDetector
[Magisk] pndwal:
https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/post-85865045 PW
[Magisk] klemi71:
USNF 2.2.0 instructions are to remove play services from deny list, right?
[Magisk] JakeDHS07:
Never saw that personally
[Magisk] gfrank227:
Hi all, I need some help configuring rclone mount. Firstly, the module won't install on the new magisk canary. But I installed the old 23.0 version and then it installed. But I don't know how to configure it. The github page mentions a config file that I need to place somewhere; but I can't find such a file or know how to configure it to set up an actual mount point.

I'm trying to mount a network location (on my NAS) to be a local directory within internal storage, similar to what I did in linux. Any help is appreciated. Thanks!
[Magisk] DiamondJohn:
I am not using the latest Magisk, however, the play store has undergone many major updates of recent (probably in prep for A12). As part of the upgrade, it will possibly uninstall the previous version and then reinstall itself. It *MAY* be possible that any temp uninstall or the upgrade process they use will remove all references to it in other apps. ie the DenyList. Just pure conjecture.
[Magisk] pndwal:
I hadn't played with that.

Just tried binaries / applets again w/ latest Canary in Terminal Emulator, and note that only magisk * binary * & resetprop + su applets seem to work now.

magiskhide applet is gone now, and neither magiskboot * binary * nor magiskinit * binary * work for me, so no magiskpolicy or supolicy applets either.

These probably work fine in 23.0 (pre MagiskHide removal), and that may do the trick for you.

@ipdev / others have more experience with Magisk Tools. 😬 PW
[Magisk] pndwal:
Further, after John releases public 24.0 he will update documentation too... I'd say things may be clearer then... PW
[Magisk] DiamondJohn:
Just an interesting FYI. I have a Pixel 4A running the stock firmware, which gets monthly updates, including the latest one to A12. I usually manually download flash and root. As I am unlocked & rooted and have modified my boot image, I never expected to get OTA's and have never gotten one thus far. UNTIL earlier this week. I now have a notification asking me if I wish to upgrade to A12 (from A11). I was shocked to be offered an OTA with an unlocked bootloader and Magisk flashed to my boot image. No problem, just a surprising (at least to me) FYI. And I am not the only one. I am running Magisk v23000
[Magisk] pndwal:
Always got em on Xiaomi RN8T! (Not monthly but 😜)...

Just need to remember to restore stock images before taking OTA. PW
[Magisk] ipdev:
You might want to ignore that. ;)

Google pushed the Verizon build by mistake.

Supposedly it will not affect anything for non-Verizon users/devices.

There have been a few articles on it today.

xda's article - Link

Cheers. :cowboy:
[Magisk] xunholyx:
I get OTA notifications most of the time, but I usually use the ota.zip downloaded from Google's website to update
[Magisk] ipdev:
Magisk's DenyList (HideList was the same) is stand alone.

The only way to add or remove package name(s) is manually.

The UI will only show apps that are installed.

If you add an app to the list and then uninstall the app, it will not show in the UI but, is still in the list.

As soon as you reinstall the app, it will show in the UI and will still be hidden/denied.

If you use command line, you can modify the list by adding or removing package names even if they are not installed.

You can preload your list before you install an app for the first time. ;)

Clean up your list because you forgot to remove an app from the list before you uninstalled it. :oops:

As for USNF v2.2.0 it was noted over in the USNF thread.

Guess @JakeDHS07 missed it. ;)

Cheers. :cowboy:
[Magisk] JakeDHS07:
That's so weird. I wonder how it doesn't need root to be denied now. Fascinating stuff. But yeah I did miss it. Alot gets posted on here.
[Magisk] pndwal:
John also said:

Nb. Denylist can be utilised, but "modules don't actually need to rely on DenyList for hiding. They can do everything themselves".

Seems @kdrag0n / latest USNF modules "can do everything themselves", ie it's his own solution. 🙂 PW
[Magisk] pndwal:
Great guide, thanks... I think I followed a similar guide from you a while back, but forgot full path requirement... Pinged you as I thought you'd come through! 👍

I didn't say MagiskBoot was part of Magisk binary however... I clearly said 'magiskboot * binary * isn't working for me'. 😜 ...

Thanks for the method. PW
[Magisk] pndwal:
Great find / insight to!...

Guess I'll be searching w/ 'is:pr is:draft' or simply 'is:pr is:' in future. 👍 PW

Edit: how do I stop XDA's emojis ruining everything?! 😂
[Magisk] DiamondJohn:
I am sure there is a "proper way" to escape the emoticons, but one way is to wrap potential emoticons in {ICODE]

Guess ill be searching w/ 'is:pr is draft
[Magisk] ipdev:
[ICODE]code[/ICODE] for inline code box.

BB code is blocked in code boxes.

[PLAIN]text[/PLAIN] to block BB code in general text. ;)

Cheers all. :cowboy:

Edit:

Found the link I was looking for. ;)

XDA - Help - BB Codes - Link
[Magisk] m0han:
good that you were able to update with absolutely no problem. the dev says on his telegram channel: dirty install fine. in the same breath he says: uninstall apk and install new apk, then flash zip in twrp. and, this is how i could get things running. btw, yesterday i was able to 'download' the latest riru-lsposed from within renamed magisk app and install it from storage. no errors. everything looks fine except for that line about init.rc modifications, which, as they say, could be false reporting.
[Magisk] zgfg:
Actually, I also described on Custom TG channel that I have to (for each Custom ver):

- disable PlayProtect (orherwise it complains)

- Uninstall Magisk app (but that DOES NOT uninstall Magisk itself)

- Install new Custom apk

- re-enable PlayProtect

- patch, flash...

My point was that I just updated Magisk (talking about Magisk, not Magisk app) without uninstalling - otherwise it would be waste of time to install and cinfigure all the modules again
[Magisk] m0han:
i read that too. actually, uninstalling app and installing new apk is what i meant here. and then, i'd rename magisk app, boot into recovery and flash zip in twrp. things would be fine after booting back up. just this last time, magisk detector complaining about init.rc modifications (minor annoyance). btw, i have disabled play protect (i don't usually use play store app).

edit: wonder whether @TheHitMan thinks this needs to be addressed. my previous post here.
[Magisk] pndwal:
You can (probably) flash Magisk .zip from Magisk App (as a module) also; worked with TJW builds. I suspect dev may intend this when stating "Keep in mind you must use apk and zip package. Even patching boot image done with given zip package."

If you mean init.rc issues, canyie noted the false detection in vvb2060 Detector some time ago, saying this result is unreliable (detects 'init.rc modified' even when Magisk isn't installed!):

https://github.com/canyie/Riru-MomoHider/issues/12#issuecomment-907718098

Interesting she's recently fixed this init.rc issue:

https://github.com/topjohnwu/Magisk/issues/4319

with this commit from her fork:

https://github.com/topjohnwu/Magisk/pull/4836

Also, vvb2060 posted new Momo 4.0.1.

Her notes (translated):

She also responded to @osm0sis' query:

saying:

https://github.com/topjohnwu/Magisk/issues/2406#issuecomment-963166974

👀 PW
[Magisk] pndwal:
Latest Magisk Canary:​

Magisk (7e9d4512) (23014)​

Fix crashes when multiple Zygisk module is installed

Fix crashes in magiskboot under certain circumstances

Always unload Zygisk itself after post specialize

Add module suspension state in Magisk app (riru/zygisk modules)

Diffs to v23.0​

[General] MagiskHide is removed from Magisk

[General] Support 64-bit only systems

[General] Support Android 12

[Zygisk] Introduce new feature: Zygisk

[Zygisk] Introduce DenyList feature to revert Magisk features in user selected processes

[MagiskBoot] Support patching 32-bit kernel zImages

[MagiskBoot] Support boot image header v4

[MagiskBoot] Support patching out skip_initramfs from dtb bootargs

[MagiskInit] Support /proc/bootconfig for loading boot configurations

[MagiskInit] Better support for some Meizu devices

[MagiskInit] Better support for some Oppo/Realme devices

[MagiskInit] Support init.real on some Sony devices

[MagiskPolicy] Load *_compat_cil_file from system_ext

[MagiskSU] Use isolated devpts if the kernel supports it

[MagiskSU] Fix root shell if isolated mount namespace is set

[resetprop] Deleted properties are now wiped from memory instead of just unlinking

[App] Build a single APK for all ABIs

[App] Switch to use standard bottom navigation bar

[App] Downloading modules within the Magisk app is removed

https://github.com/topjohnwu/magisk-files/blob/55bdc45955e7ba1fe4d296b6fc06f926ebc9ddd1/notes.md

👍 PW
[Magisk] rodken:
I thought that I was one of the few that still refers to them as emoticons.
[Magisk] Stillhard:
+1 @pndwal for Moderator
[Magisk] moocow1452:
Hey all, checking in. With the Oculus Go, I'm unable to get Kernel Logs with the Magisk boot.img as adb is unresponsive during the initial boot, along with everything else. The device is only usable if I flash the old boot.img, which wipes out the old logs. Is there a recommended way to sneak a script into the Magisk boot.img that will cat ksmg onto /sdcard so that the log will survive a boot reflash, and not otherwise interfere with the boot process? I'd normally tack on something to init.rc with adb root, but since the Magisk flash would probably revert that change as well, I'd figure I should ask around first.
[Magisk] Eng.Raman:
New Magisk alpha 1e05f8c6 (23014) released.

alpha update log​

Magisk (1e05f8c6-alpha)​

[App] Support SharedUserId

[App] Delete the backup file after restoring the boot image

[App] Built-in current version update log

[App] Use local version when unable to download stub

[App] Switch to the modern time API of Java 8

[Busybox] Cancel optimization based on undefined behavior

[General] No longer automatically unlock the device block

[General] Use MagiskHide to hide when Zygisk is closed

[General] Pause loading of zygisk module when zygisk is closed

[App] Speed up the loading speed of the exclusion list

[App] Delete markdown rendering

Github Link.

Change Log.