[Discussion] Magisk - The Age of Zygisk.

Search This thread

roslanhashim

New member
Nov 18, 2018
2
1
Getting black screen on latest v1.7.86 of this app. Suspect is new detection mechanism. Anyone can test?
Before this version is fine (v1.7.84). Pass safetynet, Shamiko, Added to deny list it just wont work on latest version.

Pixel 6 Pro Latest Nov patch, Magisk 25.2
i feel you bro. had the same issues. not only TnG eWallet not responding, CIMB OCTO detect rooted device. just found 2 solution:–
1: revert back to Magisk 23 (the last version with MagiskHide)
2: install Magisk Delta. i am using this and its work flawlessly.

hope its work for you too.

~kitajagakita~
 

Attachments

  • Screenshot_2023-03-18-22-04-53-578_my.com.tngdigital.ewallet.jpg
    Screenshot_2023-03-18-22-04-53-578_my.com.tngdigital.ewallet.jpg
    525.9 KB · Views: 91
  • Screenshot_2023-03-18-22-05-06-404_com.safetynet.bivek.jpg
    Screenshot_2023-03-18-22-05-06-404_com.safetynet.bivek.jpg
    365.3 KB · Views: 84
  • Screenshot_2023-03-18-22-05-24-413_rikka.safetynetchecker.jpg
    Screenshot_2023-03-18-22-05-24-413_rikka.safetynetchecker.jpg
    255.8 KB · Views: 92
  • Screenshot_2023-03-18-22-05-46-109_io.github.huskydg.magisk.jpg
    Screenshot_2023-03-18-22-05-46-109_io.github.huskydg.magisk.jpg
    268.7 KB · Views: 84
  • Like
Reactions: J.Michael

prokiller1199

Senior Member
Nov 14, 2014
188
45
Johor Bahru
i feel you bro. had the same issues. not only TnG eWallet not responding, CIMB OCTO detect rooted device. just found 2 solution:–
1: revert back to Magisk 23 (the last version with MagiskHide)
2: install Magisk Delta. i am using this and its work flawlessly.

hope its work for you too.

~kitajagakita~
Thanks bro for providing your solution now. Already solved it quite long ago using 2nd solution. Kudos the help!
 

mickeychan1

New member
Oct 5, 2021
4
0
i feel you bro. had the same issues. not only TnG eWallet not responding, CIMB OCTO detect rooted device. just found 2 solution:–
1: revert back to Magisk 23 (the last version with MagiskHide)
2: install Magisk Delta. i am using this and its work flawlessly.

hope its work for you too.

~kitajagakita~
Hi! I'm also having problem with touch n go. I'm on magisk 25.2, universal safety net by kdragon v2.4... all other banking apps pass ...

Please help.... I'm not sure what you mean to install magisk v23?... Does that mean I need uninstall magisk v25 first, then install v23?

Or do I just install magisk delta directly from magisk v25, and if so, is there any guide how to do it?

Many thanks from a fellow Malaysian to another 😊 as only Malaysians uses touch n go app....
 

J.Michael

Recognized Contributor
Jan 20, 2018
1,816
2,067
Samsung Galaxy Tab A series
Hi! I'm also having problem with touch n go. I'm on magisk 25.2, universal safety net by kdragon v2.4... all other banking apps pass ...

Please help.... I'm not sure what you mean to install magisk v23?... Does that mean I need uninstall magisk v25 first, then install v23?

Or do I just install magisk delta directly from magisk v25, and if so, is there any guide how to do it?

Many thanks from a fellow Malaysian to another 😊 as only Malaysians uses touch n go app....
Read the last hundred posts in the main Magisk thread.

The safest way to change Magisk versions is to uninstall Magisk, uninstall the Magisk manager app, reboot, and start over with a different Magisk APK.

There have been recent posts about other procedures.

In this post @Fry-kun described a very simple process that I didn't believe. You can waste five minutes watching the video, or you can read the follow-up posts.
 
  • Like
Reactions: roslanhashim

roslanhashim

New member
Nov 18, 2018
2
1
Hi! I'm also having problem with touch n go. I'm on magisk 25.2, universal safety net by kdragon v2.4... all other banking apps pass ...

Please help.... I'm not sure what you mean to install magisk v23?... Does that mean I need uninstall magisk v25 first, then install v23?

Or do I just install magisk delta directly from magisk v25, and if so, is there any guide how to do it?

Many thanks from a fellow Malaysian to another 😊 as only Malaysians uses touch n go app....
yes... you need to install magisk v25 and reinstall magisk v23.

or

you can directly install MagiskDelta.apk, open it and grant root excess. reboot into recovery and install magiskdelta.zip.
reboot into system - open magisk delta apps. go to settings - switch on MagiakHide - configure MagiskHide by adding all banking apps & tng ewallet. click on 3 dot - show system apps - search google - click to hide Google Play Service, Google Play Service for AR, Google Play Store. if you install Vanced MicroG, make sure you hide it also.

long press Magisk - uninstall.

this method work for me even i have to learn it by hard way
 

superbarney

Member
Dec 5, 2018
19
8
Hi! I'm also having problem with touch n go. I'm on magisk 25.2, universal safety net by kdragon v2.4... all other banking apps pass ...

Please help.... I'm not sure what you mean to install magisk v23?... Does that mean I need uninstall magisk v25 first, then install v23?

Or do I just install magisk delta directly from magisk v25, and if so, is there any guide how to do it?

Many thanks from a fellow Malaysian to another 😊 as only Malaysians uses touch n go app....

I just tried out Magisk Delta. Using that seemed to have allowed the TnG app to run again. Other bank apps and Grab are working fine still too. Hopefully the changes that is in Magisk Delta can be integrated into the original Magisk in the near future.
 

mickeychan1

New member
Oct 5, 2021
4
0
yes... you need to install magisk v25 and reinstall magisk v23.

or

you can directly install MagiskDelta.apk, open it and grant root excess. reboot into recovery and install magiskdelta.zip.
reboot into system - open magisk delta apps. go to settings - switch on MagiakHide - configure MagiskHide by adding all banking apps & tng ewallet. click on 3 dot - show system apps - search google - click to hide Google Play Service, Google Play Service for AR, Google Play Store. if you install Vanced MicroG, make sure you hide it also.

long press Magisk - uninstall.

this method work for me even i have to learn it by hard way
thanks! I will try it!
 

koberulz

Senior Member
Oct 4, 2012
231
26
Perth
I don't really keep up with Android stuff, just pop in periodically when I get a new phone.

I remember seeing that topjohnwu got hired at Google, and as part of that they insisted he remove Magisk Hide functionality. Not sure what happened after that, but I just avoided any Android and Magisk updates and I've been fine. Unfortunately, I accidentally clicked on a Magisk update the other day and now it doesn't work, I get periodic "Magisk has stopped" messages and trying to click on it in the app drawer does nothing.

So...what exactly is its status? It seems to still be going, contrary to the dev-hired-at-Google-and-app-nerfed narrative I was aware of. Not sure how to go about resolving my problem. I guess updating to Android 12 might be back on the table?

Pixel 3.
 

zgfg

Senior Member
Oct 10, 2016
8,968
6,706
Redmi K20 / Xiaomi Mi 9T
Xiaomi Mi 11 Ultra
I don't really keep up with Android stuff, just pop in periodically when I get a new phone.

I remember seeing that topjohnwu got hired at Google, and as part of that they insisted he remove Magisk Hide functionality. Not sure what happened after that, but I just avoided any Android and Magisk updates and I've been fine. Unfortunately, I accidentally clicked on a Magisk update the other day and now it doesn't work, I get periodic "Magisk has stopped" messages and trying to click on it in the app drawer does nothing.

So...what exactly is its status? It seems to still be going, contrary to the dev-hired-at-Google-and-app-nerfed narrative I was aware of. Not sure how to go about resolving my problem. I guess updating to Android 12 might be back on the table?

Pixel 3.
There is a lot to read in the OP posts right in this thread - for the beginning

And then some newer stuff, ongoing in the later posts in this thread, Magisk general, Google Pay thread (if you use it)

Btw, you could search for PixelFlasher XDA thread, a tool for OTA updating Pixel phones and (re)installing/updating Magisk
 
  • Like
Reactions: ipdev and J.Michael

koberulz

Senior Member
Oct 4, 2012
231
26
Perth
There is a lot to read in the OP posts right in this thread - for the beginning

And then some newer stuff, ongoing in the later posts in this thread
I'm not going to read an entire 150-page thread, though, and what I've found seems conflicting. Magisk Hide is dead, but there's a Deny list, but apps can still detect root now because Magisk can't do anything to prevent that...

I need Hide, because my banking and streaming apps won't work otherwise.
 

zgfg

Senior Member
Oct 10, 2016
8,968
6,706
Redmi K20 / Xiaomi Mi 9T
Xiaomi Mi 11 Ultra
I'm not going to read an entire 150-page thread, though, and what I've found seems conflicting. Magisk Hide is dead, but there's a Deny list, but apps can still detect root now because Magisk can't do anything to prevent that...

I need Hide, because my banking and streaming apps won't work otherwise.
I said to read OP = Original Poster posts in this thread to see what's different in the new Magisk and how to configure and use - eg, Zygisk and DenyList instead of the old MagiskHide, about hiding (not only Magisk but the whole 'root') by Shamiko, USNF, the things you're asking for

You don't have time to read 150 pages - I think nobody has hours (if not more - accounting for answering additional questions when you open Pandora box, like where the Module repo is 'gone', etc) to write several pages now exclusively for you about the 'status' of the new Magisk, or do you really expect that?

That's exactly why this thread was opened at the beginning and a lot of patience spent by the OP poster to give the newcomers to the new Magisk v24 (now v25) a quick start

But if it's still too much to concentrate and to read, then better give up and go back to Magisk v23

There is also a fork Magisk Delta - it's based on the new Magisk but with MagiskHide instead of DenyList (it can be used with this new Zygisk or without).
To make hiding easier, Delta also provides Whitelist mode named SuList (in MagiskHide you list those apps you want to hide from, in SuList you list the opposite - those apps you don't want to hide, hence when you install new 'banking' app you don't need to add to MagiskHide and reboot).
Delta has its own thread on XDA (search can find it)
 
Last edited:

koberulz

Senior Member
Oct 4, 2012
231
26
Perth
I said to read OP = Original Poster posts in this thread to see what's different in the new Magisk and how to configure and use - eg, Zygisk and DenyList instead of the old MagiskHide, about hiding (not only Magisk but the whole 'root') by Shamiko, USNF, the things you're asking for
I've read it, and I'm confused.

It implies DenyList replaces Hide, but then the Magisk FAQs say Magisk has no features to prevent apps seeing root. Those seem contradictory to me.

I'm sure there's nowhere near 150 pages of information I actually need, so reading the entire thread would largely be a waste of time.
 

zgfg

Senior Member
Oct 10, 2016
8,968
6,706
Redmi K20 / Xiaomi Mi 9T
Xiaomi Mi 11 Ultra
I've read it, and I'm confused.

It implies DenyList replaces Hide, but then the Magisk FAQs say Magisk has no features to prevent apps seeing root. Those seem contradictory to me.

I'm sure there's nowhere near 150 pages of information I actually need, so reading the entire thread would largely be a waste of time.
DenyList is not exactly for hiding but it partially helps for that

Zygisk provides the mechanism for additional modules to help for hiding - like the Shamiko module

To pass Play Integrity API (no intention now here to describe what it is and how it supersedes the deprecated SafetyNet), you will need the latest USNF

(I think all that above was shortly addressed in the OP posts)

Some 'banking' apps search deeper for 'root' and you may additionally need Hide My Apps (HMA) - btw, that would apply also to the users of the old, pre-Zygisk Magisk (but would require to search for Riru based LSPosed instead of the new, Zygisk-LSPosed)

And again, there is a Delta fork that includes Zygisk but also the old MagiskHide (in the whitelist SuList mode or classical blacklist MagiskHide list) instead of DenyList - exactly because the developer wants to help himself and his users to easier hide

All these are just bullets for further (re)search

Edit:
There is also a MagiskHide module (from the developer of Magisk Delta) for the official Magisk, that gives you back the MagiskHide to the new Magisk v25xxx
 
Last edited:

koberulz

Senior Member
Oct 4, 2012
231
26
Perth
Looking at PixelFlasher, it requires I give the shell root access in Magisk, but I can't do that, because Magisk won't open.
 

zgfg

Senior Member
Oct 10, 2016
8,968
6,706
Redmi K20 / Xiaomi Mi 9T
Xiaomi Mi 11 Ultra
Looking at PixelFlasher, it requires I give the shell root access in Magisk, but I can't do that, because Magisk won't open.
Better ask in the Pixel Flasher thread

Btw, if you just 'blindly' updated from Magisk v23 to the new Magisk v25 (being new with what it brings), there are might be various reasons why "Magisk does not open"

Btw, who does not open: Magisk app or it opens but does not recognize Magisk installed (due to remaining your old 'Hide Magisk' app/manager on the phone), or you go to ADB or Terminal emulator and you cannot grant root access, etc

It would probably be better to uninstall Magisk (by flashing uninstall.zip through TWRP, as described on the official Magisk GitHub page - btw, another guide, official, for the new Magisk) and then to install from scratch (as described in the guide on GitHub or probably by use of Pixel Flasher)
 
  • Like
Reactions: J.Michael

zgfg

Senior Member
Oct 10, 2016
8,968
6,706
Redmi K20 / Xiaomi Mi 9T
Xiaomi Mi 11 Ultra

If I click on Magisk in my app drawer, nothing happens.
Then follow the second part of my post you quoted, fully uninstall Magisk (not just the app) and clean install the new v25 - see the Magisk official installation (and uninstallation😁) guide and possibly (I don't have Pixel) the PixelFlasher guide

Sorry, that's it. Not easy now to jump now (or advise about - for someone's else phone) from Magisk v23 to v25, with the number of unknown variables - his phone and ROM, installed modules and their (in) compatibilities, did he do Hide Magisk app and how he renamed Magisk app or he does not remember that, etc)
 
  • Like
Reactions: J.Michael

koberulz

Senior Member
Oct 4, 2012
231
26
Perth
How do I uninstall? I can't access the app to uninstall it, and the uninstallation instructions just say that if you can't do that, "flash it like any flashable zip", and I have no idea how to do that. I know TWRP stopped working, is that back? The TWRP thread in the Pixel 3 forum hasn't been updated in years. Or can I just flash it with fastboot?
 

Top Liked Posts

  • 1
    I'm having issue bypassing root for HTTP Injector and NapsterNetV apps on both Black Shark 2 and Samsung S22.

    BS2:

    - Android Pie
    - Latest Magisk Alpha with Universal SafetyNet Fix MOD (passes flawlessly) and latest Shamiko. Both apps are added to Shamiko's DenyList. HTTP Injector crashes itself, while Napster says Rooted users are unable to use this config.

    S22:

    - Pixel Experience Android 13
    - Latest Magisk Delta with SUList enabled and all root stuff hidden.

    Injector doesn't crash, but detects root while importing config. Same goes for Napster.

    Here's a dummy NapsterNetV config with root block. Change the extension to .npv4 and import through the app to replicate my problem. Unfortunately, I can't give you an .ehi HTTP Injector file, because my S22 is currently bricked after failed restore.

    UPDATE: Cleaned HTTP Injector's cache and reinstalled. Still detects root, but at least it runs. I've managed to create a dummy file. Change extension to .ehi and import.
    1
    I'm having issue bypassing root for HTTP Injector and NapsterNetV apps on both Black Shark 2 and Samsung S22.

    BS2:

    - Android Pie
    - Latest Magisk Alpha with Universal SafetyNet Fix MOD (passes flawlessly) and latest Shamiko. Both apps are added to Shamiko's DenyList. HTTP Injector crashes itself, while Napster says Rooted users are unable to use this config.

    S22:

    - Pixel Experience Android 13
    - Latest Magisk Delta with SUList enabled and all root stuff hidden.

    Injector doesn't crash, but detects root while importing config. Same goes for Napster.

    Here's a dummy NapsterNetV config with root block. Change the extension to .npv4 and import through the app to replicate my problem. Unfortunately, I can't give you an .ehi HTTP Injector file, because my S22 is currently bricked after failed restore.

    UPDATE: Cleaned HTTP Injector's cache and reinstalled. Still detects root, but at least it runs. I've managed to create a dummy file. Change extension to .ehi and import.
    At the beginning you said "passing flawlessly" - does it refer to SafetyNet (deprecated) or Play Integrity (but without Strong Integrity - that's what is relevant)

    Are you using the latest USNF but from Displax (not the 'official')

    Have you tried with Hide Magisk app

    Disable LSPosed (if you have) and all other irrelevant Magisk modules and try again, but always Wipe Data (not just cache) for those apps you are testing

    If still not passing, install/enable LSPosed and try with Hide My AppLlist (with other LSPosed modules disabled)

    If you had XLua, you must manually delete its remaining folders

    Must not run SELinux Permissive mode

    Some apps may even look if Developer Options are enabled - there is an LSPosed module to hide

    Etc - unfortunately, hiding is not only about SafetyNet, DenyList/Magisk Hide and Shamiko (on top of above, some apps may even look for TWRP folder)
  • 10
    Well yeah, i wouldn't mind a company using something like that in their apps. Bank apps are made by banks, there is a name behind them, there's someone accountable, and most important of all they dont have the kind of access that either Magisk or Xposed do, so in my opinion it is pretty much safe to trust them
    Sure... So you can vote with your feet in any case, but remember this is not about vv's Alpha fork where Appcenter implementation is simply vv's decision... She's free to implement test and debug it in her fork... The objections discussed were to her PR for telemetry in official Canary Magisk which, of course, you'll always have source for.

    Microsoft can ensure private data isn't compromised/abused with Appcenter as it uses their back end, but Magisk is also open to scrutiny by coders in general anyway... Bank apps will need skilled reversers to prove that they're acting honourably.

    So would Jorrit's (chainfire's) SuperSU for that matter, but most rooters in that era wouldn't have given a second thought to the possible (very serious) security breaches they were permitting with closed source root!

    As for Alpha fork, vv has always used it as a test bed for experimental fixes and never promoted it as an alternative Magisk for daily use; it was only ever for those wanting to test innovations or fixes, or as a stop-gap solution until her fixes are merged in Magisk... It seems apparent to me that, with telemetry data continuously coming in, she no longer needs many testers and may be actively discouraging Alpha takeup as a 1100+ Chinese userbase delivers ample data for her prolific contributions to Magisk.

    FWIW, vvb2060's Magisk commit production has been second only to John's (who merges most commits including those of others) for several years now... Just in recent months Shana has been at the top of the leaderboard however, but there's clearly much collaboration also:
    IMG_20230517_193901.jpg


    vv's fixes, and her changes have been at the forefront of Magisk development for some years now... So many major innovations in official Magisk have been developed in vv's Alpha fork and her experimental branches.

    Just to mention a sampling I posted more than a year ago: MTK compatibility, single package delivery, support for 64bit, sepolicy fixes, several isolated process fixes, fixes for UID, MicroG, process names, file based encryption, mount rules for Samsung, auto-close issues bot, reboot menu, multi-user and shared user id compatibility fixes, hidden apps, Chinese doc translations, offline restore app, unsupported environment checking, fix for apex path (a big one), permission fixes, module Installation fixes, Kotlin code cleanup, MagiskHide stopping fix, Renamable App / single package Magisk archive (developed in cooperation with John).... And countless more recent commits for various devices/compatibility, new functionality and major refactoring of magiskinit injection, sepolicy rules and so on.

    Alpha is thus no rogue fork, much less a vehicle for stealing data or scamming any of us and many members here know that the evidence of vv's beneficent motivation is more than anecdotal...

    Whether I choose to do early testing of upcoming Magisk innovations with Alpha or not, I'm certainly not suspicious, rather I'm happy it exists as I am that other test forks and Magisk benefactors are contributing so much to this essential staple modding solution. 😋 PW
    8
    Sorry if i sound rude or condescending, but do you think using a piece of software with full control over your phone made by a developer with an anime profile picture and who doesn't bother to translate anything they say to English is a very good idea?
    From what I've read in the Magisk threads, Yes, it's an excellent idea.

    It's not for everyone. The people who know what they are doing can identify which situations make Alpha or Delta worth trying. The "full control over your phone" is no greater than that possessed by the "regular" Magisk.

    As for not bothering to provide English translations, why should she? She has a big enough fan base that I keep seeing references to her releases. Use it or don't. She doesn't charge anything, and you get your money's worth.
    7
    Sorry if i sound rude or condescending, but do you think using a piece of software with full control over your phone made by a developer with an anime profile picture and who doesn't bother to translate anything they say to English is a very good idea?
    Screenshot_20230516-130542_1.jpg
    See the devs below @topjohnwu down the bottom?
    They are the Alpha devs. Also massive contributors to the main Magisk branch.
    You can trust their software.
    6
    Of course they understand... Seems those that don't are the paranoid... And nobody's saying you can't be paranoid if you want!... 🤪

    [ ... etc. ... ]

    Irrespective of the fact that most of them probably have valid, understandable reasons for wanting to keep their source closed and to be difficult to communicate with in their TG channel, the fact that this is the current reality of Alpha is enough to motivate me not to use it.

    I don't hold it against those developers personally, and I respect their feelings and priorities and decisions about this.

    It's just that if I have a choice (and in this case, I do), I prefer not to use this kind of software that is provided under those constraints.

    As for telemetry, given the way that the current Chinese government utilizes similar telemetry aganst not only their own citizens, but also against others in other countries, I have more fear than usual about this particular telemetry. Even if none of the developers are knowingly working with the Chinese government, it's still possible that people from that government might be able to access the fruits of this telemetry.

    I have as much right to be paranoid about this telemetry as do any of the Alpha developers have a right to be paranoid about discussion-group participants.
    6
    As I understand it, Alpha is not meant for widespread use. Its developers are not looking for lots of users. Its a testbed, meant to be used by a few of their friends, and even then only to address specific problems.

    The rest of the world should wait for the changes to bubble into the official Magisk release.
    Well put...

    This discussion began because we mentioned that Alpha allows Volkswagen app to run and a member wondered if Alpha is trustworthy...

    Alpha solves the issue because it builds Shana's test branch commits and she's got native bridge Zygisk loading working to the point where it's quite useable (but still unfinished)
    IMG_20230506_090803.jpg

    over the last few months...

    The test branches for vv (Nangong Xueshan, @vvb2060), Shana (LoveSyKun, @yujincheng08), Canyie (@canyie) and others are open source, so you could easily build any of their experimental fixes yourself (it's not hard using a GitHub action run), or simply run one of the test branch CI (continuous integration) builds...

    For example, the last collaborative published Refactor zygisk to use native bridge to inject commit was authored by Shana and committed in LSPosed/Metagisk Zygisk branch by 3 weeks ago, and an associated CI build is here:
    Refactor zygisk to use native bridge to inject Magisk Build #61 pushed by yuijincheng08

    That might work fine but many CI builds don't; they're simply test runs with varying usefulness and even successful functioning... Alpha release builds on the other hand, are built using selected commits and have been checked at least for basic functionality by vv, so there's a greater level of reliability despite being bleeding edge stuff.

    I personally haven't used Alpha since John was producing viable Zygisk but not releasing any Canary builds (vv's Alpha served as a Zygisk testbed and POC for many months at the time) due to his mandatory period of restriction on creating/contributing to personal open source projects and Google review of his Magisk Android mod project... The new Zygisk refactoring that is native bridge loading simply made current Alpha builds too tempting for me! 😜... I'll be back to TJW Canary just as soon as we have N/B Zygisk, which Canyie has indicated should arrive with public 27.0 (or perhaps in an earlier Canary build).

    I may be tempted by some other off-the-chart innovation LSP Devs introduce in future and hop on the Alpha bandwagon again, but I'm really eager to see what official Magisk delivers...
    -----------
    FYI: For anyone interested in what changes / innovations are in the works for Magisk or just being tested,

    vv's test branches currently include:
    Shana / LSP project have:
    Canyie has:
    In TJW (official), @osm0sis has:
    🤠 PW
  • 137
    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.
    72
    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.
    62
    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.
    58
    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.
    48
    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.​