[Discussion] Magisk - The Age of Zygisk.

Search This thread

pndwal

Senior Member
I did not find where it was mentioned but, basically release is the 'lite' version.
The debug version is the 'heavy' version including extra logging and more for debugging the Magisk build. 🙃

I might be wrong but..

Both canary (release) and debug are released at the same time and John does not specify a difference between the two.
They both point back to the latest commit at the time of their release.

Magisk [GitHub] - Release new canary build
magisk-files [GitHub] - Update Canary Channel: Upstream to 9183a0a6
magisk-files [GitHub] - Commit history.​

So I assume the current debug version is still just the debug version of the canary build. ;)

The current Magisk build script.
./build.py --help
Code:
usage: build.py [-h] [-r] [-v] [-c CONFIG] {all,binary,app,stub,emulator,avd_patch,clean,ndk} ...

Magisk build script


optional arguments:
  -h, --help            show this help message and exit
  -r, --release         compile in release mode
  -v, --verbose         verbose output
  -c CONFIG, --config CONFIG
                        custom config file (default: config.prop)

actions:
  {all,binary,app,stub,emulator,avd_patch,clean,ndk}
    all                 build everything
    binary              build binaries
    app                 build the Magisk app
    stub                build the stub app
    emulator            setup AVD for development
    avd_patch           patch AVD ramdisk.img
    clean               cleanup
    ndk                 setup Magisk NDK


Cheers. :cowboy:
Close, but not quite right; this is still correct:
Just a minor note: Magisk Canary is now app-release, not app-debug...

If you installed app-debug, you're either on an old Canary build, or you've installed new Debug instead of Canary...

The 'debug version of the canary build' (built with debug build flag) is not now considered 'Canary', but 'Debug', and not suitable for daily use...

The Canary designation has been re-purposed for builds built with release build flag and deemed suitable for daily use...

Previously, only workflow files built with debug build-flags were supplied to Canary ( https://github.com/topjohnwu/magisk-files/tree/canary ) repo (although likely files built with release flags were actually produced). Ie. we had:
IMG_20220705_105004.jpg

... We now have:
IMG_20220705_105233.jpg

supplied.

The change is that app-debug.apk has become the package for the new Debug channel (ie. it is no longer 'Canary' per se), and app-release.apk is now the new Canary... John clarified that 'Canary is now built as release'...

Confusion probably comes from the fact that the magisk-files canary-tree repo is still used for both, but this of course makes sense considering they are always synced builds produced in tandem so that Debug is simply the debug build of new Canary releases with a new name. (Actually the notes.md file is shared at present)...

This can also be seen by examining the JSON sets at https://github.com/topjohnwu/magisk-files
where canary.json calls app-release.apk and debug.json calls app-debug.apk, but these are the same synced builds hosted at a common URL per commit...

As mentioned, Canary can be used for daily use going forward, but 'Debug builds should only be used if you are actively developing Magisk, or if you want to submit bug reports'. Especially once proposed changes (adding symbols and maybe some sanitizers, and enabling core dumps on debug executables for better debugging and auditing) are made, Debug should not be used daily. 'These changes can be an issue on older devices, and could significantly affect performance'
www.twitter.com/topjohnwu/status/1525753967954628608

😛 PW
 
Last edited:

angelomb

Member
Jun 4, 2013
10
1

Attachments

  • Screenshot_2022-07-04-23-00-34-500_io.github.huskydg.magisk.jpg
    Screenshot_2022-07-04-23-00-34-500_io.github.huskydg.magisk.jpg
    362.5 KB · Views: 85
  • Screenshot_2022-07-04-23-00-27-314_io.github.huskydg.magisk.jpg
    Screenshot_2022-07-04-23-00-27-314_io.github.huskydg.magisk.jpg
    317.3 KB · Views: 85
  • Screenshot_2022-07-04-23-00-20-791_io.github.huskydg.magisk.jpg
    Screenshot_2022-07-04-23-00-20-791_io.github.huskydg.magisk.jpg
    379.2 KB · Views: 84

itt533

Member
Nov 12, 2020
44
4
chennai
so far i enabled app hiding feature in magisk, installed denylistunmount (and disabled "enforce denylist") and safetynetfix modules and put banking apps in denylist. Two banking apps seem to work, at least they don't complain. Not yet tried logging and everything... but gpay is showing a blank screen and seems to hang only. G-play says "device is not certified".
 

Ace_Cole

Member
Jul 5, 2022
25
1
I found out on latest update of "App cloner", I couldn't avoid it detecting root.. I updated from magisk TJW 23.0 official to fork magisk delta 25.1 if incase it will work but no way.. root still detected. Check attached snapshots.
Zygisk disabled
Magisk hide enabled
App added on denylist
 

Attachments

  • IMG_20220705_124421.jpg
    IMG_20220705_124421.jpg
    206.6 KB · Views: 70
  • IMG_20220705_124328.jpg
    IMG_20220705_124328.jpg
    412.1 KB · Views: 70
  • IMG_20220705_124255.jpg
    IMG_20220705_124255.jpg
    129.4 KB · Views: 71

huskydg

Senior Member
Feb 17, 2021
242
246
I found out on latest update of "App cloner", I couldn't avoid it detecting root.. I updated from magisk TJW 23.0 official to fork magisk delta 25.1 if incase it will work but no way.. root still detected. Check attached snapshots.
Zygisk disabled
Magisk hide enabled
App added on denylist
This is warning from your system security app, not from the app itself
 
  • Like
Reactions: J.Michael

Ace_Cole

Member
Jul 5, 2022
25
1
And if you press OK and relaunch the app?
It would launch normally and ignore root, but if I unroot my device, it open normally without that screen.. I'm only concern that it still could detect root after hiding it, and installing those other hidden modules.

Also Magisk detector still see su file exist in path and init.rc modified

Any way to know specific means those app uses in getting root? And how to block it?
 

zgfg

Senior Member
Oct 10, 2016
7,804
5,216
How to solve this? I use Xiaomi Redmi 9 android 10. Thanks 😊
Are you asking about com.miui.securitycenter

Did you add it to DenyList?
See the screenshots

You might need to enable Show System and Show OS apps to be able to see in the Magisk app, Configure DenyList

Alternatively (if it won't show in Configure DenyList), DenyList can be managed through the Terminal:
Code:
su
magisk --denylist ls
magisk --denylist add com.miui.securitycenter
magisk --denylist ls
 

Attachments

  • IMG_20220705_173339.jpg
    IMG_20220705_173339.jpg
    110 KB · Views: 31
  • IMG_20220705_173437.jpg
    IMG_20220705_173437.jpg
    467.3 KB · Views: 31
  • Like
Reactions: J.Michael

Ace_Cole

Member
Jul 5, 2022
25
1
Are you asking about com.miui.securitycenter

Did you add it to DenyList?
See the screenshots

You might need to enable Show System and Show OS apps to be able to see in the Magisk app, Configure DenyList

Alternatively (if it won't show in Configure DenyList), DenyList can be managed through the Terminal:
Code:
su
magisk --denylist ls
magisk --denylist add com.miui.securitycenter
magisk --denylist ls
Okay thanks. I'll try that and give feedback.
 

zgfg

Senior Member
Oct 10, 2016
7,804
5,216
Okay thanks. I'll try that and give feedback.
But I see now that you started by asking about App Cloner

I don't see App Cloner in the MIUI Security. If that App Cloner is a third party app, then adding Security to DenyList would have no effect/not help

Then I don't know why somebody recommended you to add MIUI Security to DenyList - my previous post was exclusively about adding Security to DenyList (since I remember that with some MIUI version and/or some Magisk version, Security was not showing in DenyList or in MagiskHide and I needed to be added through CLI in Terminal)
 
  • Like
Reactions: J.Michael

Ace_Cole

Member
Jul 5, 2022
25
1
But I see now that you started by asking about App Cloner

I don't see App Cloner in the MIUI Security. If that App Cloner is a third party app, then adding Security to DenyList would have no effect/not help

Then I don't know why somebody recommended you to add MIUI Security to DenyList - my previous post was exclusively about adding Security to DenyList (since I remember that with some MIUI version and/or some Magisk version, Security was not showing in DenyList or in MagiskHide and I needed to be added through CLI in Terminal)
Yes..

I was about to post an update because adding MIUI Security Center doesn't help either.

"App cloner" is a third party app. But I can't get it to stop detecting root since the last update. I configured everything but still can't get it to stop bringing the root detected warning before starting.. that's my issue which I hope to get solution from great developers . Thanks
 

Attachments

  • IMG_20220705_170107.jpg
    IMG_20220705_170107.jpg
    161.9 KB · Views: 24

aiamuzz

Senior Member
Dec 24, 2011
504
46
Hi,

Don't know if this is the right place ... anyways ...


Firstly I don't have a clue why my github issue got closed by a bot.

Secondly I need help to get the Banking app working ...

Any help appreciated.

thanks.
 

emyaqin

Member
Dec 14, 2016
20
5
Tangerang
Hi,

Don't know if this is the right place ... anyways ...


Firstly I don't have a clue why my github issue got closed by a bot.

Secondly I need help to get the Banking app working ...

Any help appreciated.

thanks.
Use Shamiko or DenyList Unmount, disable Enforce DenyList
 

martyfender

Senior Member
Mar 9, 2017
3,272
1,750
Indianapolis, IN
Hi,

Don't know if this is the right place ... anyways ...


Firstly I don't have a clue why my github issue got closed by a bot.

Secondly I need help to get the Banking app working ...

Any help appreciated.

thanks.
Please report issues using the latest debug Magisk build (version code: 25101)
Are you on the latest debug build of magisk? You must be to report issues.
 

Top Liked Posts

  • 4
    I was follow your every steps carefully but instead of zygisk hide in momo, now it's start detect debugging mode enable 😮💨.
    It detects what it says. If bothering you, turn off USB/ADB debugging mode.
    Or give up on Momo - it will always detect something
    1
    It detects what it says. If bothering you, turn off USB/ADB debugging mode.
    Or give up on Momo - it will always detect something
    Ok🥲
  • 18
    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
    8
    ... Needless inconvenience from banks ... 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.
    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.
    4
    I was follow your every steps carefully but instead of zygisk hide in momo, now it's start detect debugging mode enable 😮💨.
    It detects what it says. If bothering you, turn off USB/ADB debugging mode.
    Or give up on Momo - it will always detect something
    4
    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
    After wiping only the Cache for Playstore and waiting few more hours, now Certified
    3
    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.
  • 127
    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.
    66
    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.
    59
    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.
    54
    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.
    46
    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.​