yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Yup, no 'must reason', but he has certainly explained / given heads-ups regarding his intention to do this as far back as old 20.4 Magisk...

At that time he planned both to integrate overlayfs (already delivered and a real boon especially in the age of shared blocks filesystems as I think you appreciate), and to create the 'native zygote injection/hooking framework' now spawned as Zygisk.

As for 'a decisive explanation about the reasonable advantage of Zygisk model', he said back in December, after some nine months as an apple engineer "I lost all interest in improving the current way of hiding" but native zygote injection/hooking framework would bring "proper ways to 'hide' root and Magisk Manager."

Addressing the major issue introduced also, he said "standardizing code injection to something hidable is my goal."

I'm not sure that there are many issues other than Riru replacement / initial hiding issues. (Reminds me a bit of XDA vBulletin to XenForo migration 😁 ), and I am optimistic that 'standardizing code injection to something hidable' may still be achieved. (I posted a little about Riru hide methods earlier today)...

Here is John's 2020 Heads-Up in context:

Aha! ... "I'd love to try out some new approaches." Well I'm all for that!

To add an observation, it seems that as a (still very young) developer John always liked new challenges. Only five years ago (2016) he'd just learned C++ and knew little in programming but taught himself scripting (from "snippets of shell scripts throughout XDA"). He said SuperSU and Xposed installation scripts were the most prominent he referrenced.

The same year he was first to release Systemless Xposed, then immediately started working on a general solution and in August 2016 released Magisk to the public. 😛...

Personally, I think John loves the challenge / cares about custom Modding more than most of us... All power to him. 😁 PW
[Magisk] rodken:
I am always amazed at how many coders are self-taught, even though coding is not hard to learn and many of them have been able to reach fairly high positions in their career [hint- hint]. It just takes time and peristence which is sometime dependent on the language and the software being tackled.

As long as one is able to demonstrate his/her programming skills during the the entire process, 'it's all good in the neighborhood'.
[Magisk] zgfg:
Don't know did you observe (you were eager about Alpha but before the Canary was released) vvb2060 now took a SIGNIFICANT step back (better to say COMPROMISE) with his today's Alpha 43d11d87 (23010):

- You can choose between Zygisk+Deny or MagiskHide

(maybe you could enable Zygisk together with MagiskHide but I had no interest nor time to test that IMHO pointless combination)

- "Configure Deny List" actually serves both for DenyList (I didn't try) and MagiskHide

- I needed to reboot for MagiskHide to take the effect

- If Zygisk is not enabled, you can install Riru

- I also installed Riru-Momohider and successfully configured the isolated option to hide su from the path

Screenshots attached

Edit: Later also successfully tested with Riru-LSPosed and the modules: GravityBox-R, CustoMIUIzer, Hide My Applist
[Magisk] JustLauro:
Where did you get this Zygisk version of LSPosed from? I can't find it anywhere
[Magisk] zgfg:
Link was in the LSPosed TG channel:

LSPosedArchives

CI Builds are built automatically on every push to the primary branch. They are extremely unstable and only for testing and bugreport, and we don't take any responsibility of the consequences of flashing them. Debug builds have telemetry.

t.me
[Magisk] pndwal:
To parrot someone 'Let me get this out of the way: since I have a full time job now, I don't have much time for Magisk; I need prioritization' ...

I had meant to run / check it by now but priorities intervened / objected...

Now that is keeping MHide alive, +Riru!

This one might be more elegant than TheHitMans Custom M?

Should be able to enable all MomoHider hide options again w/ that.

Nb. setns is better / faster. Re isolated (only): "This feature is deprecated because it will unmount Magisk modified files for every isolated processes, and the unmounting time cannot be well controlled, which may cause some modules to not work." 👍 PW

Edit:

Many will like choice of traditional hide & Riru or Zygisk in up-to-date Magisk...

Still haven't looked, but might do the translation thing for Alpha-with-deny/hide choice Changelog soon.

Tempted Nigel? ... Just teasing ya. 🙄 🤪
[Magisk] pndwal:
Oh no!

😁 PW
[Magisk] 73sydney:
Nigel is tempted

At some point (hopefully soonish) one fork will come out ahead and perhaps the other dev can join in and work together
[Magisk] rossmurray:
New Google Pixel 3 XL user. Upgraded to A12 via OTA. Rooted via ROOT GUIDE steps pinned in 3 XL forum and without deleting data. Had A12 running fine with 23000, even banking app and Google Pay. Testing Magisk Canary build from today. Rebooted and everything seems to run as expected. Toggled on Zygisk, rebooted, and again everything seems to be running smoothly - including banking app and Google Pay.
[Magisk] JustLauro:
Do you have the Canary version by TJW or any custom Magisk version? Because it seems like there is no USN fix module that works with Zygisk.
[Magisk] m0han:
i was using 8276a077-alpha (23001) at that point. I now have d7e7df3b (23010) canary by tjw. my usnf is 2.1.1 and it works for me with zygisk enabled and denylist configured.
[Magisk] JustLauro:
I use d7e7df3b too but I can't install USNF. It says it needs Riru to be installed. Should I just install Riru, then USNF and then uninstall Riru?
[Magisk] m0han:
try using zygisk-lsposed. i'm using v1.6.2 (6180). (i had removed riru before installing zygisk-lsposed.)
[Magisk] JustLauro:
But USNF is a Magisk module. Is there another version of it as a LSPosed module? The only one I can think about is XPrivacyLua, but it doesn't work because I have Google Play Services in Zygisks Denylist.
[Magisk] pndwal:
If wishes were horses... PW
[Magisk] zaczatowany:
Hi guys, i need some help. I update magisk to v23 and everything was ok, but Magisk no more support MagiskHide. So i want to downgrade Magisk and reinstall from previous version by TWRP. Now i have no Magisk, any version i can't install. What i have to do? Trying reinstall BeyondROM v3.7 and now reinstall Magisk, but still no effect. My phone is Samsung S20 Ultra 5G - G988B
[Magisk] Qnorsten:
You have to uninstall from the magisk app, reboot, install old magisk 23 then fastboot flash the patched boot img from that version of magisk.
[Magisk] martyfender:
Try USNF 1.2 or 1.1.1, as they were the last versions that don't require Riru. I am using v1.2 on my Android 9 tablets.
[Magisk] kari kimber:
cuz magisks developer hired google android security dev and developer fear job loosing (he is right).

magisk new version not support magiskhide and downloading modules the magisk app.

solution;

update magisk (canary channel, warning, not released)

hide magisk

turn on zygisk feature and enforce it deny list (warning, not released)

open configure deny list then apply deny list on google play services (gfs) and playstore (maybe clear the app cache & data)

install riru module

restart phone

install universal safety net fix module

restart the phone again
[Magisk] JustLauro:
Thank you, that worked. I'm passing SafetyNet now
[Magisk] JustLauro:
You cant install Riru when Zygisk is enabled, because both edit the same things. Instead of using Universal SafetyNet fix with Riru Download Version 1.2 of USNF (which doesnt need Riru).
[Magisk] Eng.Raman:
In the latest alpha 43d11d87, you don't need zygisk to be enabled just enable magisk hide then install any riru based module as you like.

Zygisk still experimental and it can't be used together with riru at all.
[Magisk] Eng.Raman:
The safetynet passed even without denylisted the google play services (gms).
[Magisk] m0han:
how can i 'fix' my rootbeer sample result?
[Magisk] J.Michael:
...we'd all wear rubber boots.

(Should that have been "Wellies"?)
[Magisk] Eng.Raman:
As i see that you may have modified prop(s) just remove.
[Magisk] m0han:
updated mhpc to 6.1.1 and reset everything. no go.
[Magisk] Eng.Raman:
May be you have another magisk module or a rooted app do some changes on system props.
[Magisk] Didgeridoohan:
If you reset everything you might have just made the MagiskHide props option inactive. Take a look under "Edit MagiskHide props" in the module main menu and see if all options are active (if not, activate).
[Magisk] m0han:
awesome! many thanks.
[Magisk] zgfg:
Now I tested also MagiskCustom from TheHitMan7, latest as of today afternoon e4eeb23e (23010)

Also with Zygisk No and MagiskHide Yes

Successfully tested:

- SafetyNet

- Riru

- Riru-LSPosed (GravityBox-R, CustoMIUIzer, Hide My Applist)

- Riru-Momohider (isolated)

Although he provides his own LSPosed-Riru (aka LSPosedCustom), I used LSPosed-riru-v1.6.2-6180-release.apk

from LSPosedArchives and it worked

---

In my opinion (since I opt for Zygisk No and MagiskHide instead of DenyList)

Pro for Alpha:

- Release apk (MagiskCustom provides only Debug apk)

Pros for MagiskCustom

- Only MagiskHide, you have MagiskHide menu to configure apps | proccesses and you use magiskhide CLI command.

(In Alpha you have to choose between MagiskHide and DenyList, and even if you chose MagiskHide [with Zygisk disabled] you still need to use Configure DenyList to configure apps | processes for MagiskHide and magisk --denylist CLI command - because vvb2060 now uses a single table in his database both for MagiskHide or DenyList, it just depends if you choose MagiskHide or Zygisk+DenyList)

- Modules repo (old repo is still alive for updates of modules previously accepted to the repo, but Repo is removed from Canary and Alpha apks)

All together I prefer MagiskCustom for now but I have to use it for a day to test stability (Alpha worked fine with mainly the same setup for the whole day)

And of course, who knows in future about the maintenance

For now both are aligned with the latest Magisk Canary 23010 but providing the ability to avoid Zygisk (with DenyList) and to use MagiskHide instead - hence to have Riru working and no issues with detection of Zygisk
[Magisk] zgfg:
Deleted
[Magisk] lokopol:
With the latest update, I have a failure to connect mobile wifi, any solution ?.

my device redmi note 7. android 10, ROM stock.

I am attaching catlog, I hope you can see the error. thank you all for your time and effort, greetings.
[Magisk] zaczatowany:
You don't understand... I install Magisk from zip file by TWRP but Magisk Manager show me so i have no magisk installed. I tried install different versions of Magisk but Magisk Manager doesn't see any of it.
[Magisk] Fif_:
Have you tried installing by patching the boot image instead? Installing via recovery is not supported anymore with recent Magisk (including 23.0).
[Magisk] zgfg:
Classic. First thing, go to Apps drawer or Settings/Apps and look for your old Magisk mngr/app and uninstall that old one

If you previously did Hide Magisk app (mngr in the old case) to rename Magisk app/mngr (and to obfuscate it by renaming the package), then upon updating Magisk the new Magisk app cannot see Magisk app
[Magisk] pulpf:
hello i think i read everything but it doesn't work

safetynet is failed.

the riru modules must all be installed? where are they found? i have a oneplus 7t

Oxygen os 1103.1
[Magisk] zgfg:
Generally, Riru cannot help you for SafetyNet. If you properly enabled Zygisk rebooted, Configured DenyList (GMS and GMS unstable), rebooted, you should pass SN.

If not, then you would need USNF and/or MHPC

As mentioned several times here, Riru is broken with Zygisk. And in your Canary, you need Zygisk for DenyList (hence for SN).

Therefore, if you really want Riru, you would need to switch to Alpha or Custom (many posts here how/where/what, etc) and use them as: Zygisk No, MagiskHide Yes (not the new DenyList)

And to avoid troubles when switching the Magisk flavour, better completely uninstall Magisk before you go
[Magisk] pndwal:
Meaning Magisk Update, or Rom?

These symptoms are often an indication of mismatched boot image...

Did you take an OTA update and restore previously patched boot image, or perhaps updated Magisk but patched a boot image extracted from a ROM prior to an OTA update or other ROM entirely?... PW
[Magisk] jons99:
new alpha is out and working fine

Changelog:

- Fixed magiskd may crash

- Support Zygote restart

- Fixed CWD process across namespace in isolated namespace mode

- Improve deny list loading

- Use Traditional Search list in deny list
[Magisk] pndwal:
Pretty funny Dev asks "what's new?", then user provides translation (above) of Dev's Changelog as answer...

I doubt that's what Dev meant by "I also want to know!" (Translated) 🤪 PW
[Magisk] zaczatowany:
Now Magisk Manager show Magisk version but... my buttons on bottom disappeared. And Magisk Manager show me a strange version number to update. And i can't to update Magisk to v23. After i install zip file from TWRP MM still show me v22.1
[Magisk] zgfg:
Sorry, I dont understand what is that - it shows that you have Manager and Magisk, some old version v22.1?!

What do you really want to install, Stable 23000 or latest Canary 23010, or else?

Please, if you are really wanting to experiment with the latest Canary, be aware that you might have problems with SafetyNet, banking aps, etc - is it really neccessary for you and did you folloew and understand (to further apply what would you need) all changes brought by Zygisk, DenyList, etc
[Magisk] zaczatowany:
I just want to instal stable 23 version. And i download zip file, install this zip file by TWRP but MM still show me old version 22.1. And i can't install any modules because the module, log, etc, buttons from bottom of the screen disappeared.

I have no buttons on bottom, just look at the SS. Root Checker shows my phone is no rooted...
[Magisk] zgfg:
It has been discussed here many times, with the new Magisk there is no more Modules repo in the app. You must download all your modules manually (link for Repo was also given previously here)

There is also no more SafetyNet checker n the app. And there is no more MagiskHide but DenyList where you must know how to manually enable GMS to pass SN (all was also described more than once here).

Please be prepare for that, if you didn't follow all discussions here, do the homework and get ready to go along by yourself with all those news and changes

If you still want to install that new Magisk Canary, take Uninstall Magisk to uninstall your old v22.1

Since you have troubles with flashing through TWRP, use the method as recommend on MagisknGithub: install Canary 23010 apk, patch the image and flash it through Fastboot (instructions are on Github and it was also discussed here numerous times)
[Magisk] m0han:
i refer to screenshot 5.jpg in your post above. i have almost the same setup as you. yet, magisk detector reports that 'su file exists in path'. how can i resolve this? i have just installed Momo hider module. any further configuration required? i'm running the latest magisk alpha.
[Magisk] pndwal:
Screenshot showing Magisk not installed, so no bottom menu...

Edit: [Seems you may have a previous manager /app installed causing conflict (can't see Magisk/root). Have you searched settings / apps for that as previously described?]

Actually, seems TWRP might be the issue, and ruined previous root... (This is a common problem and reason John depreciated Custom Recovery installation method...)

If you can restore previous old root (backups?) you should be able to update from app using Direct Install...

With existing old root ensure Magisk App is restored first (not hidden), then uninstall the Magisk App, download the late version (APK) you want, install app, update within app (direct install)...

If you can't restore you should do as @zgfg advised above. PW
[Magisk] zgfg:
To hide su from the path, you need isolated option. On the Momohider Github page you have instructions
[Magisk] lokopol:
thanks for answering. no, my stock ROM worked fine, it was with the magisk update when the wifi connection stopped working.
[Magisk] pndwal:
And you never took OTA since initially Magisk installation? PW
[Magisk] lokopol:
No 🤷
[Magisk] pndwal:
Have you tried new Canary released only an hour ago?

Says fixes crashes caused by patching process; may have been other issues fixed - worth a shot. I'd start fresh ( un-patched boot image) with it... PW
[Magisk] pndwal:
Also, did you ever use Custom Recovery installation, or Patch, Fastboot flash and update w/ Direct Install? PW
[Magisk] Dwightsch:
Okay @topjohnwu you're probably sick of the "sell out" stuff and just flaming over the changes in magisk in this new direction you're taking this great project since your employment at Google. I totally agree with you. I think devs and apps and... Should have the option to "opt out" of any modification. but riddle me this, when I have some banking app, some other system app or whatever and that has nothing to do with the modifications I have using root, should they force me to unroot my phone? It's their choice that I shouldn't mess with their app but is it theirs to demand I either choose banking or modifications to other parts of my phone? My point being, if it's at all possible, consider adding Deny list functionality for system apps because currently it doesn't work on any and Hide options for apps that force you to either choose magisk or their app, regardless of what you're modifying. You can factor out any app or service that Google runs but a "choice" for users to bypass detection and modification for apps and services that insist you don't root android and enforce that whether by themselves or using Google services, would be great and probably in sprit of your current decisions.

Other than that, cheers and thanks.

I hope you stay strong and healthy.
[Magisk] abagm:
Which of the things doesn't match the others?

To my great delight, I discovered a ROM for Samsung S5e (kminilte) with Android 9. Runs great - just can't get Magisk to work. Have tried alpha, Hitman's and JohnWu's new releases. Neither with TWRP nor with the direct patch of the boot.img (and flash via download mode) I get further - the flashing stops with every method when repacking the bootimage, without anything being flashed/patched. Do I have to mount anything manually or so? Honestly, I do not get through meanwhile - is there somewhere a working guide, which system requirements, which flash method and which other requirements should be given? Here in the thread I have bravely read along - as far as I know, I have also tried all the instructions, but no Magisk was installed. I do not need SNP, only ROOT and Hiding Root and the ExSD card module. I'm not sure, but I had the impression that Zygisk (first two alpha versions up to ...31 I could still completely flash via TWRP) brings my device into bootloop /freezing. Should we users (who do not have their own dev skills) rather wait until there is any beta or use an old Magisk classic or have I overlooked / not understood something essential?
[Magisk] pndwal:
Yup - you need to read / follow official Installation Instruction linked from Magisk home page; pay special attention to Samsung section... 😁 PW
[Magisk] m0han:
got it. many thanks. had to run setenforce 1 to get the 3rd screenshot.
[Magisk] pndwal:
Latest Canary Magisk

Magisk (ea75a09f) (23011)

• Make Zygisk survive zygote restarts

• Fix crashes when Magisk environment was not properly setup. This will fix the crashes experienced after installing Magisk with patching boot images.

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

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

• [MagiskInit] Better support for some Meizu devices

• [MagiskInit] Better support for some Oppo/Realme devices

• [MagiskSU] Use isolated devpts if the kernel supports it

• [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

👍 PW
[Magisk] pndwal:
Nb. There may be issues with isolated as per GitHub page for module. - it is deprecated and replaced by setns (need isolated + setns). Without Zygisk you should be able enable all options. In Alpha with Zygisk + Riru co-existing, only isolated & initrc work. PW
[Magisk] pndwal:
LSPosed Telegram group reporting LSPosed & Magisk on WSA + GApps, and just confirmed that GApps works on both arm64 and x64. 🤪 PW
[Magisk] rodken:
According to your screenshot, you might want to toggle your 'Update Channel' so that the current version matches the latest.

There is a newer alpha version released as of this writing?
[Magisk] zgfg:
With or without setns I have no difference. For me only isolated works (hiding su from the path)

With setns but without isolated - su is visible again in the path

Sticking with isolated - it worked to me with all flavours and Magisk versions (of course, without Zygisk and with Riru)
[Magisk] Eng.Raman:
Why you need to run setenforce 1 to get a screenshot ?
[Magisk] Makishima:
I'm on the latest Magisk Canary released a few hours ago, I see people putting Google Play gms and so on on the denylist yet I can't see it listed. Do you do it via terminal? And if so, how? Or are you using a different version of Magisk?
[Magisk] Eng.Raman:
Magisk → Settings → Configure DenyList → Search icon → Show system apps → Search for gms in Filter by name.
[Magisk] Makishima:
Oh... I had already done that but I thought it found nothing. Turns out Play Services was hidden right beneath the search bar. Okay, so I 'deny' gms and gms.unstable right? Also, is it okay to hide the Magisk app with the latest update? Because it kept crashing half an hour ago and had to uninstall and reflash.
[Magisk] zaczatowany:
Sorry, my english not so good to do homework and understand all the posts.... I just want to install Magisk v23 and recover root in my phone. But some crazy things do with my phone. I tried many times to install Magisk-23.zip in TWRP but Magisk Manager still doesn't see any magisk installed or old version 22.1. I have no option to uninstall this... what i have to do? please...
[Magisk] Qnorsten:
Do anyone know what can trigger ART parameters are abnormal in momo?

I have one app that seem to detect root no matter what I do, so I temporarily moved over to magisk alpha to try and use old magisk hide, Riru and Riru-momohider. To try and make momo don't detect root and see if that fixed the app, before I start decompiling the app to figure out what sort of root detection it does.

Update: the cause for art parameters are abnormal, was lsposed. Disabled lsposed and now momo are happy. Didn't fix my other app though, so back to drawing board I guess.
[Magisk] Eng.Raman:
setns works only when the config isolated is enabled ( i.e: It can't be configured without isolated ), referring to the momohider github page.

All the 4 configs worked for me in both magisk custom and alpha but i only need ( isolated+setns+initrc ).
[Magisk] zgfg:
With isolated I kill su and obtain as on the screenshot

What additional do you get with setns?

Please be aware that init rc modifications detection or not is not reliable
[Magisk] Eng.Raman:
Faster safetynet response time.
[Magisk] m0han:
if i don't run that, magisk detector reports 'selinux policy has been modified' ;)
[Magisk] zgfg:
For me the filling was (already on two occasions, with varios Magisk versions) that the phone becomes less fluid with setns
[Magisk] zgfg:
Then you use some module that enforces Permissive mode