[Discussion] Magisk - The Age of Zygisk.

Search This thread

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,017
34,060
Halifax
GT-i9250
Google Nexus 4
Seems not, but Canyie has fixed her GitHub link to Momo from MomoHider page https://github.com/canyie/Riru-MomoHider ('depreciation notice' introduces Shamiko - MomoHider may not be a 'thing' anymore...) however (Link to momo apk is dead #22 / Fix #22, 54d76a6), so at least we can link to that on XDA since we can't post TG links as file source...

Momo is linked under 'Test':
https://github.com/canyie/Riru-MomoHider#test

👀 PW
Sigh.. guess I'll secretly install Telegram just to download things. 🤷‍♂️🙄🥲
 

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,017
34,060
Halifax
GT-i9250
Google Nexus 4
You don't need to install Telegram. You can do it in using your browser.
Follow canyie's link. And then, if you strip off the last level from the URL, you can see all the posts, including the latest version of Shamiko.
Couldn't get the actual download to work in Chrome on my phone or laptop, even with Desktop mode and Incognito, not without a Telegram app installed. 🤷‍♂️
 
Last edited:

martyfender

Senior Member
Mar 9, 2017
3,268
1,746
Indianapolis, IN
Sigh.. guess I'll secretly install Telegram just to download things. 🤷‍♂️🙄🥲
I am just curious why you don't want to install telegram. About a year ago, or so, I uninstalled telegram because I got tired of the juvenile, posts on an android app dev forum, lspeed. I feel now that telegram is better moderated, but that is mostly based on the magisk alpha, lsposed. etc that I am now on. Is there some other security issues with it that I am not aware? I have most notification in it turned off so it doesn't constantly annoy me.
 
  • Like
Reactions: osm0sis

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,017
34,060
Halifax
GT-i9250
Google Nexus 4
I am just curious why you don't want to install telegram. About a year ago, or so, I uninstalled telegram because I got tired of the juvenile, posts on an android app dev forum, lspeed. I feel now that telegram is better moderated, but that is mostly based on the magisk alpha, lsposed. etc that I am now on. Is there some other security issues with it that I am not aware? I have most notification in it turned off so it doesn't constantly annoy me.
Nah just the childishness nonsense you mention. I was on a few Android groups at one point and they were all pretty obnoxious. That and when I tried having a public profile getting random "Hey are you THE osm0sis from xda? Cool! Just checking." roughly every couple days was ridiculous. Made me fairly certain I'm doing just fine with xda, Twitter, email, GitHub, Slack and TWRP's Zulip. 😜
 
Last edited:

meric57

Senior Member
Oct 2, 2017
188
35
Oeutrange
Samsung Galaxy Tab E
Hello suite updated shamiko module to version 0.5.0 (110)
I have this message which appears with a red cross shamiko doesn't worksince enforce denylist is enabled
Also in modo mod v4.1.1
message the environement is abnormal
 
Last edited:
  • Like
Reactions: Lughnasadh

Stillhard

Senior Member
Sep 25, 2016
138
109
Nah just the childishness nonsense you mention. I was on a few Android groups at one point and they were all pretty obnoxious. That and when I tried having a public profile getting random "Hey are you THE osm0sis from xda? Cool! Just checking." roughly every couple days was ridiculous. Made me fairly certain I'm doing just fine with xda, Twitter, email, GitHub, Slack and TWRP's Zulip. 😜
Luckily to get the file(s) from every TG public channs/groups, you don't even need to join/exist in there, just leech and go - no one will notice :LOL:
 
  • Like
Reactions: rodken and osm0sis

meric57

Senior Member
Oct 2, 2017
188
35
Oeutrange
Samsung Galaxy Tab E
Hello,i launch momo is this normal or do fixe something.
Thank you
 

Attachments

  • Screenshot_20220518-093042_Momo.jpg
    Screenshot_20220518-093042_Momo.jpg
    330.4 KB · Views: 76
Last edited:

73sydney

Senior Member
Nah just the childishness nonsense you mention. I was on a few Android groups at one point and they were all pretty obnoxious. That and when I tried having a public profile getting random "Hey are you THE osm0sis from xda? Cool! Just checking." roughly every couple days was ridiculous. Made me fairly certain I'm doing just fine with xda, Twitter, email, GitHub, Slack and TWRP's Zulip. 😜

I mostly get on there for about 5 minutes a day for early releases, and to post random things in the invite only dev groups that are all so full of random off topic nonsense that my offerings like "butternut pumpkin" in complete isolation, seem to escape attention....
 

73sydney

Senior Member
Hello,i launch momo is this normal or do fixe something.
Thank you

Could be worse, my S20+ looks like this, yet all still works....

My S20+ does indeed have decrypted /data, debugging mode on and unlocked bootloader.
Wish zygisk wasnt found, but thats its.

Screenshot_20220518-180727_Momo.jpg


update:

Actually this trick seems to have solved the Zygisk detection


01010000011011110110111001101011011011000110010101110011
 
Last edited:
  • Like
Reactions: HippoMan

BillGoss

Senior Member
Sep 2, 2010
5,294
4,656
Sydney
OnePlus 8T

pndwal

Senior Member
Ok, good... So no more blanket 'TG is not allowed as file source'.

New rule states:

What about download links?

Download links from hosts, platforms or other sources are allowed as long as they do not require registration. Some Telegram links require registration for downloads, so they will not be allowed. Please check them before posting.


However apart from 'preview pages' it seems TG can't be accessed without registration including files hosted there. So effectively there is no change / the rule remains the same. 🙁

(Ie, there is no XDA accepted download source for vv2060 / Rikka Momo 'root' detector as it's only officially hosted on TG which requires registration for file access. Nb. This was also the case with Canyie's Shamiko until it recently got a presence in LSPosed GitHub.)

Re this:

What is NOT allowed?

Posts like For support, join my Telegram group: https://t.me/abc. This means you're not willing to provide support to users on XDA.


I think this cannot be inferred; a dev may well be willing, but as they wish to support a non-English userbase, they choose TG for discussion and support purposes, just as Russian Devs might prefer to use 4PDA... XDAs English-only policy is is the issue; it's a matter of XDA's willingness to allow non-English support rather than a Dev's reluctance...

This is very much the case with the LSPosed Devs who are the most prolific contributors to Magisk. Many have their own predominantly Chinese discussion groups, Eg, Rikka (Riru core framework module, YASNAC, Sui, [Momo]...), vvb2060 (Alpha & Lite Magisk, Momo...), Caynie (Dreamland XPosed, Bravo Magisk, Shamiko...), LoveSy aka yujincheng08, Shana (LSPosed etc) and others.

These generally wish to communicate in Chinese with fellow Android modders / other Chinese devs...

Putting this here since "Device Forum Rules (Please Read before Posting)" thread you linked is locked, and actually "Not open for further replies."...

👀 PW
 
Last edited:

0purple

Senior Member
Mar 14, 2021
132
24
Redmi 9
Could be worse, my S20+ looks like this, yet all still works....

My S20+ does indeed have decrypted /data, debugging mode on and unlocked bootloader.
Wish zygisk wasnt found, but thats its.

View attachment 5617005

update:

Actually this trick seems to have solved the Zygisk detection


01010000011011110110111001101011011011000110010101110011
Screenshot_20220511-092645_Momo.png


What packages do I select to hide? Tried both LSPosed and Magisk, didn't work. Also, Shamiko now causes "Partition mounted abnormally".

Not really related, but modules that systemize things like libs, apks cause "found file modified by magisk modules". Is there any eay to fix those? "TEE is broken" is ROM's fault afaik so jo way to fix it.

Lineage 19.0
 

zgfg

Senior Member
Oct 10, 2016
7,593
4,995
Could be worse, my S20+ looks like this, yet all still works....

My S20+ does indeed have decrypted /data, debugging mode on and unlocked bootloader.
Wish zygisk wasnt found, but thats its.

View attachment 5617005

update:

Actually this trick seems to have solved the Zygisk detection


01010000011011110110111001101011011011000110010101110011
Be careful with enabling Momo in HMA

I never enabled Momo in HMA because (as the name says), Hide My Applist hides applications (like Magisk APP - not the Magisk itself), and as Momo says, Momo does not look for applications

Nevertheless I tested now by enabling Momo in HMA (Effective apps, Enable Hide):

1) enabling File detections or All hide methods does not help to hide TWRP folder.
Simply renaming TWRP folder to TWRP.bak works perfectly for me (without Momo in HMA)

2) Without Momo in HMA, my Momo v4.1.1 does not detect Zygisk.
When I configured Momo in HMA by using All Hide Methods (saved and rebooted) - Momo did complain that Zygisk was found !!!
Hence I disabled Momo in HMA, saved, rebooted and it was fine again - Momo did not find Zygisk.
I tested once again with Momo in HMA (Enable Hide, All hide methods), saved in HMA, rebooted and Momo again wrote Zygisk found

All together, I don't see a use/need for enabling Momo in HMA, Select Effective Apps - without, I have no problem with Zygisk found

And with Momo in HMA, All hide methods - then my Momo finds Zygisk?! (and it does not help to prevent finding TWRP folder)

Xiaomi 11 Lite 5G NE, A11
 
  • Like
Reactions: ipdev and 73sydney

martyfender

Senior Member
Mar 9, 2017
3,268
1,746
Indianapolis, IN
Be careful with enabling Momo in HMA

I never enabled Momo in HMA because (as the name says), Hide My Applist hides applications (like Magisk APP - not the Magisk itself), and as Momo says, Momo does not look for applications

Nevertheless I tested now by enabling Momo in HMA (Effective apps, Enable Hide):

1) enabling File detections or All hide methods does not help to hide TWRP folder.
Simply renaming TWRP folder to TWRP.bak works perfectly for me (without Momo in HMA)

2) Without Momo in HMA, my Momo v4.1.1 does not detect Zygisk.
When I configured Momo in HMA by using All Hide Methods (saved and rebooted) - Momo did complain that Zygisk was found !!!
Hence I disabled Momo in HMA, saved, rebooted and it was fine again - Momo did not find Zygisk.
I tested once again with Momo in HMA (Enable Hide, All hide methods), saved in HMA, rebooted and Momo again wrote Zygisk found

All together, I don't see a use/need for enabling Momo in HMA, Select Effective Apps - without, I have no problem with Zygisk found

And with Momo in HMA, All hide methods - then my Momo finds Zygisk?! (and it does not help to prevent finding TWRP folder)

Xiaomi 11 Lite 5G NE, A11
Do you have momo added to the magisk/shamiko denylist though? In my case, I find I have to do this to hide zygisk. Sometimes it does find zygisk, though. Like before, it is not consistent.
 
Last edited:

pndwal

Senior Member
Last edited:
  • Like
Reactions: ipdev and osm0sis

BillGoss

Senior Member
Sep 2, 2010
5,294
4,656
Sydney
OnePlus 8T
Maybe I'm being dense, but please can you tell me how Momo can be downloaded from here without registering an account (giving phone number etc) for Telegram? - I always get "Download Gailey" when trying this from a browser...

Thanks, PW
I thought I had downloaded the APK using the browser, but it seems that I used the Telegram app to download it.

Sorry for the misdirection.

Edit: but I didn't need to join the group. I just had to install Telegram, click on the link I posted and then select Download from the 3dot menu on the post.
 

pndwal

Senior Member
I thought I had downloaded the APK using the browser, but it seems that I used the Telegram app to download it.

Sorry for the misdirection.
👍
Edit: but I didn't need to join the group. I just had to install Telegram, click on the link I posted and then select Download from the 3dot menu on the post.
But if I'm not wrong, you needed to register to use Telegram (and give a phone number etc), and apparently that's the clincher...

I believe links to files not actually hosted on TG can work, but Momo links seem to be to TG hosted files... PW
 
  • Like
Reactions: ipdev and BillGoss

Top Liked Posts

  • 2
    It kind of works now, but I have to choose if I want Zygisk on (=No Mobile Network) or Zygisk off (=Older version of Magisk).
    I did flash the recovery image to get Magisk onto the device to begin with, everything else is "direct install (recommended)".
    No A/B stuff..
    Very interesting...

    So can I assume 7T has recovery_a/_b partitions as I believe 8T does, and that you also patched either recovery_a or _b in Magisk App some time back?

    If this is correct, I'm guessing Zygisk-off somehow causes device to reboot to system via recovery, and you thus have old Magisk since you patched recovery image (which is also a boot image containing ramdisk of course) with that some time ago...

    Note: Magisk in recovery and customised protocol for reboot via recovery to system w/o special adapted recovery key combo was designed for A-only legacy SAR devices specifically as these require Magisk in recovery partition as they have no ramdisk in boot... You seem to have used it on your 2SI device and there is no reason it shouldn't work apart from the fact that Magisk in boot partion is far more desirable / convenient...

    If I'm correct about a/b partitioning in 7T, your modern 2SI boot type device will of course have ramdisk in 4 partitions, recovery_a and _b, also boot_a and _b... This is fairly unique as most 2SI devices use recovery in boot partition (w/ a hybrid ramdisk) and have no actual recovery partitions.

    Again, if I'm right you can test theory by booting from powered down state using recovery key combo with this adjustment: As soon as you press the key combo and the device vibrates with a splash screen, release all buttons to boot into Magisk. (If you wanted to boot into the actual recovery mode, you would long press volume up until you see the recovery screen.)
    https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery

    Please reply to confirm (or correct) this! 😛 PW
    1
    This is still intriguing me... I see this is OnePlus 7T, and it happens on rebooting...

    Just wondering if you have ever patched / flashed recovery image on this device?... Or is device swapping between A/B system slots somehow? (Do you have working systems on both?... Perhaps Magisk in boot_a and boot_b?)... PW
    It kind of works now, but I have to choose if I want Zygisk on (=No Mobile Network) or Zygisk off (=Older version of Magisk).
    I did flash the recovery image to get Magisk onto the device to begin with, everything else is "direct install (recommended)".
    No A/B stuff..
  • 6
    Latest Official TJW Canary (release) & Debug (debug) Magisk builds:

    Magisk (f42c089b) (25102)​

    • [MagiskInit] Fix a potential issue when stub cpio is used
    • [MagiskInit] Fix reboot to recovery when stub cpio is used
    • [General] Better data encryption detection
    • [General] Move the whole logging infrastructure into Rust

    Diffs to v25.1​

    • [MagiskInit] Fix a potential issue when stub cpio is used
    • [MagiskInit] Fix reboot to recovery when stub cpio is used
    • [General] Better data encryption detection
    • [General] Move the whole logging infrastructure into Rust
    https://github.com/topjohnwu/magisk-files/blob/8fce25209918072f18b5bb056c43f596f771324d/notes.md

    👍 PW
    5
    Is it possible to find out what an app detects? I have Shamiko 0.5.1 installed and somehow a banking app still detects root. This is the app: https://play.google.com/store/apps/details?id=ro.raiffeisen.eToken&hl=ro&gl=US
    I just tried it on my phone (stock rom, Magisk 24.3, Shamiko 0.5.0, USNF).
    Without doing anything, it detects root.
    Adding it to denylist, still detects root.
    Freezing the Magisk app, goes through!
    5
    How should I hide apps?
    ... its just an addon script that (attempts, as best possible) to hide whatevers in the Deny List
    Just to avoid confusion/ be clear, Shamiko does not hide apps (in denylist or otherwise)...

    It's akin to old MagiskHide, and hides traces of root from apps in the list...
    ### Introduction
    Shamiko is a Zygisk module to hide Magisk root, Zygisk itself and Zygisk modules like riru hide.

    Shamiko read the denylist from Magisk for simplicity but it requires denylist enforcement to be disabled first.
    @appleman_wp
    If you wish to hide apps detected by banks etc, try the Hide My Applist LSPosed module...
    I don't think Shamiko has a "Settings". I think you use the Magisk Manager app's deny list. If you do not "Enforce Deny List" in Magisk, then Shamiko will use Magisk's Deny List to tell it what to hide [traces of root] from.
    (Edits mine.)

    Generally Shamiko is used without settings / extra configuration.
    ### Usage
    1. Install Shamiko and enable Zygisk and reboot
    1. Configure denylist to add processes for hiding
    1. *DO NOT* turn on denylist enforcement

    However it can actually be reconfigured (by those game / mavericks 😛) for whitelist mode usage. Note caveats:
    #### Whitelist
    - You can create an empty file `/data/adb/shamiko/whitelist` to turn on whitelist mode and it can be triggered without reboot
    - Whitelist has significant performance and memory consumption issue, please use it only for testing
    - Only apps that was previously granted root from Magisk can access root
    - If you need to grant a new app root access, disable whitelist first

    ... ts theoretically possible to... bootloop your device... At which point myself and the other senior members will pass around the chalice of your tears and drink heartily from it...
    Sadist! 😜 PW
    5
    I just tried it on my phone (stock rom, Magisk 24.3, Shamiko 0.5.0, USNF).
    Without doing anything, it detects root.
    Adding it to denylist, still detects root.
    Freezing the Magisk app, goes through!
    It's now been reported a number of times that freezing the Magisk app helps thwart root detection in many cases.

    So ... I now believe that what we need to do is not talk about that publicly too much, so that the banking-and-other-kinds-of-app developers who might check these forums don't catch on to the fact the Magisk app itself doesn't actually provide any run-time Magisk functionality.

    This way, those developers will keep thinking that checking for the existence of a non-frozen Magisk app itself is sufficient.

    Given the intelligence level of some of the banking people who lamely think that it's important to block root access under Android in order to "protect" their provided banking functionality, this ruse might actually be quite effective in many cases.

    After all, anyone who accesses a bank via their desktop computer is doing so on a rooted machine, and those idiotic banking software designers don't even care about "protecting" us against that. And those same banks issue us debit cards that we carry in our stealable wallets, and they don't prohibit us from using those debit cards, either. They go crazy only over trying to protect people against rooted Android devices, which are no more insecure than desktop computers and wallet-borne debit cards.
    4
    I have a problem with shamiko. I tried many times to install it via magisk. Itinstalls itsuccessfully however the app is not showing in the app drawer. Could someone help why shamiko is not on my device?

    It doesnt get added to the app drawer, its a module...many/most modules do not include an app in them

    Look in your list of modules section (last menu item in bottom right) in Magisk Manager, you'll find it there
  • 120
    This is a discussion and help thread for the newer versions of Magisk.

    The main goal of this thread is to help users migrate to Magisk v24+
    • SafetyNet
      Basic integrity Pass
      CTS profile match Pass
    • Play Protect certification
      Device is certified

    Feel free to discuss or give links to other Magisk related issues.
    Fixes for gPay, banking apps and/or other apps and games that detect a 'compromised' Android system.
    Please try to restrain from discussing alternative (unofficial) Magisk builds that include changes that were removed or can not be included in the official Magisk builds. 🙃

    Please read John's State of Magisk (medium.com)

    Starting with the Magisk 23 (23010) canary builds.
    • MagiskHide is removed.
      MagiskHide masked the sensitive properties of the device to hide it from SafetyNet.
      Renaming (repackaging) the Magisk app is/was not part of MagiskHide.
      You still have the option to Hide the Magisk app under setting.​
    • Magisk Module online Repo is removed.
      The Magisk Module online Repo is still available and can be accessed outside of the Magisk app.​
    • Everything SafetyNet is removed.
      This includes the SafetyNet check that was incorporated into the Magisk app.​
    • Zygisk is introduced.
      Zygote + Magisk = Zygisk​
    • The Deny list replaces the Hide list.
      The Hide list (more or less) hid Magisk from the process on the list.
      The Deny list is similar but instead of hiding Magisk from the process, Magisk is unloaded so there is nothing to hide.​

    Starting with the Magisk 23 (23017) canary builds.
    • Magisk supports update channels per module.
      Each module can include it's own update link.​
    • Hide Magisk offline.
      You do not need internet connection to rename (repackage) the Magisk app.​

    What does this mean?
    Not much.
    It is just the next step in Magisk's development.
    Zygisk is a big step forward. ;)

    Even before these changes in Magisk, the xda family and the Android community have always been active and willing to share. :D

    Jump to Post


    This is post will be updated once Magisk v24 is released.
    63
    Magisk
    The Magic Mask for Android.

    Magisk Links:
    GitHub
    Release Notes

    Download Links:
    Stable and Beta releases.
    Canary
    • GitHub
      The notes.md file is the change log.
      The app-debug.apk is Magisk canary.
      Click on app-debug.apk and choose View Raw or click on the Download option.​

    Credits:
    topjohnwu
    All who contribute and support this project.
    57
    Modules

    MagiskHide Props Config
    This module allows you to add, change and adjust prop values systemlessly using Magisk.​

    MagiskHide Props Config Links:

    Download Links:

    Credits:
    Didgeridoohan
    All who contribute and support this project.


    Universal SafetyNet Fix
    It has been a year now since kdrag0n figured out how to 'trick' SafetyNet.
    This 'trick' has been implemented properly into quite a few custom roms.
    For custom roms that do not include it and/or stock roms, he turned it into a module.​

    Universal SafetyNet Fix Links:

    Download Links:

    Credits:
    kdrag0n
    All who contribute and support this project.
    52
    Apps

    Fox's Magisk Module Manager
    This app allows you to manage and install Magisk modules.
    Including from an online repo.​

    Fox's Magisk Module Manager Links:

    Download Links:

    Credits:
    Fox2Code
    All who contribute and support this project.

    Play Intergrity API Checker
    This app shows info about your device integrity as reported by Google Play Services.
    If any of this fails could mean your device is rooted or tampered in a way (for example you have an unlocked bootloader).​

    Development:

    Download Links:

    Credits:
    1nikolas
    All who contribute and support this project.

    YASNAC - Yet Another SafetyNet Attestation Checker
    YASNAC (short for Yet Another SafetyNet Attestation Checker) is an Android app that demonstrates SafetyNet Attestation API.​

    YASNAC Links:

    Download Links:

    Credits:
    RikkaW
    All who contribute and support this project.
    43
    Force Basic Attestation

    Newer devices are designed to support hardware attestation.
    Currently there is no way to hide the sensitive device properties when checked using hardware attestation.​

    To get around this, kdrag0n figured out how trick SafetyNet that the device does not support hardware attestation.
    SafetyNet will then fall back to check using basic attestation.

    Note:
    This method will work for devices that support hardware attestation and devices that do not.
    • Enable Zygisk.
    • Install the USNF module.
    • Reboot

    To keep posts short, the instructions are hid by spoiler tags.
    If you have not installed Magisk.
    Follow the installation link in the Magisk post.​

    Download the Universal SafetyNet Fix module.
    Download link is in the Modules post.​

    1. Enable Zygisk
      • Open the Magisk app.
      • Go to Settings.
      • Scroll down to the Magisk section.
      • Toggle Zygisk on.
      • Go back to the Magisk Home screen.
    2. Go to Modules.
      • Select Install from storage.
      • Navigate to the Universal SafetyNet Fix module zip file and select it.
    3. Reboot.

    The USNF module will adjust the sensitive props that are needed to pass SafetyNet.
    Depending on the device and system (ROM) configuration, you might need to adjust a few more.
    See the Adjust Prop values post.​