111

[Discussion] Magisk - The Age of Zygisk.

 1 year ago
source link: https://forum.xda-developers.com/t/discussion-magisk-the-age-of-zygisk.4393877/page-85#post-86986605
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.

[Discussion] Magisk - The Age of Zygisk.

meric57

Senior Member
Oct 2, 2017 Hettange Grand
Hello, made with the john Wu installation as explained in the tutorial, to know depending on the certain mobile model may not be compatible with magisk23.4. I think looking at the posts to find out where to ask the question for your model, just that your the answer to your problem should be here in a post on this forum.
try to put your model in your signature with maximum info.
Several months ago I switched to the magisk alpha builds because it still had magiskhide. Soon after I started using zygisk when it was refined further. John now seems to be releasing new builds much more frequently than vvb2060, so I am considering switching back to John's builds.
Is there any reason to stay on magisk alpha builds?

Thanks

Yeah, MagiskHide was never an intended reason for using unofficial alpha Magisk, but many went to it for that reason as per:

Alpha will remove magiskhide once all popular Riru modules have released zygisk version and magisk stable version has officially released zygisk.

(Translated)

Really, it's a private fork with the purpose of testing vv's fixes and enhancements, intended for adoption in official Magisk, by Chinese Devs (incl. LSP Devs) and others.

Many fixes first appearing in her lower tier test branches (eg MTK branch in the past) are made available thru Alpha branch for more thorough testing before Pull Requests are made for TJW Magisk adoption.

Many many fixes have come to Magisk this way, including most major fixes for MediaTek compatibility, fixes for Samsung, 64 bit, late (v4) boot images, compatibility for new devices, custom ROM compatibility incl. SIM/MAC addresses issues, hiding functions (including difficult ones like Isolated process leaks), etc, etc.

Magisk would be completely different if it hadn't been for vv's builds going back to 2018. However, until recently Alpha and her other forks have gone relatively unnoticed here despite their impact.

I brought vvb2060's builds to the attention of this XDA forum simply because there was no better substitute for debug Canary builds with regular updates that I was aware of during John's Google review process period... Her Alpha Magisk worked well for those wanting to be on the bleeding edge.

Currently however, I've been back using TJW Canary as daily driver since Zygisk 23010. It's plenty cutting edge enough for me*...

Basically, I see no reason myself to be on Alpha now unless you are aware vv is working on some fix for your device / SOC / Android version etc, which is not highly unlikely.

*Nb. All of @vvb2060's builds should be considered non-stable 'bleeding edge' builds if Canary is 'cutting edge', and users should have contingency plans.

🤠 PW

Last edited: Wednesday at 9:48 AM

Mindfreak14

Senior Member
Feb 26, 2011 Mumbai
Okay it worked for me. I just removed the ICICI bank app from Xprivacylua and then used Airfrozen app to freeze magisk app and then the ICICI bank app worked as usual

The latest 14.7 iMobile Worked for you ?? Great !! Can you please list down the apps/modules you have enabled for it to get working. It will be great help.

I'm trying it since a day with latest zygisk ,LSposed, HMA .. but no luck yet.

rodken

Senior Member
Jan 11, 2010
Really, it's a private fork with the purpose of testing vv's fixes and enhancements, intended for adoption in official Magisk, by Chinese Devs (incl. LSP Devs) and others.

Basically, I see no reason myself to be on Alpha now unless you are aware vv is working on some fix for your device / SOC / Android version etc, which is not highly unlikely.

*Nb. All of @vvb2060's builds should be considered non-stable 'bleeding edge' builds if Canary is 'cutting edge', and users should have contingency plans.

🤠 PW

I've been using Alpha as daily driver since 2021 even though it has been on the cusp of being non-stable - I guess that at some point I'll keep my fingers and toes crossed that I don't fall down into that dreaded rabbit hole of corrupted data.

The latest 14.7 iMobile Worked for you ?? Great !! Can you please list down the apps/modules you have enabled for it to get working. It will be great help.

I'm trying it since a day with latest zygisk ,LSposed, HMA .. but no luck yet.

Zygisk , Shamiko, Airfrozen app to hide magisk before you open the app you need

before you open your app check with Rootbeer whether this is any other detection

amk316

Senior Member
Dec 14, 2011 Samsung Galaxy S20
hi
it seams that Applist Detector found some abnormality in my phone even its restricted in XprivacyLua to "get applications" , how to fix this?
Screenshot_20220603-064929.jpg

etmatrix

Senior Member
Jan 6, 2015
Today I upgraded to Magisk 24, on my device I have also LSPosed.
In previous version riru and magisk hide was separated, so I could hide root for an app and hook with lsposed, now if I put the app in denylist, lsposed is not working.
I see many people use shamiko for hide root and continue to use lsposed, but I don't like because it's closed source.
I found an alternative DenylistUnmount (open source) is not perfect as shamiko but I think is good for many apps. I installed about 30 banking apps and only one detect root with DenylistUnmount but root is detected also with shamiko. So also shamiko is not perfect.
Has anyone tried this module yet?

Reactions: ipdev and pndwal

zgfg

Senior Member
Oct 10, 2016 7,220 4,665
Today I upgraded to Magisk 24, on my device I have also LSPosed.
In previous version riru and magisk hide was separated, so I could hide root for an app and hook with lsposed, now if I put the app in denylist, lsposed is not working.
I see many people use shamiko for hide root and continue to use lsposed, but I don't like because it's closed source.
I found an alternative DenylistUnmount (open source) is not perfect as shamiko but I think is good for many apps. I installed about 30 banking apps and only one detect root with DenylistUnmount but root is detected also with shamiko. So also shamiko is not perfect.
Has anyone tried this module yet?

Riru and Zygisk do not work together

With Magisk v24 you must use LSPosed-Zygisk (not the old LSPosed=LSPosed-Riru) - if needed scroll/search through the old posts, this is something that is coming back every month or so (when somebody, like you now, upgrades with delay to v24)

And if must have been emphasized in the posts on the first page in this thread (when Magisk v24 was brand new)

Reactions: 73sydney

Today I upgraded to Magisk 24, on my device I have also LSPosed.
In previous version riru and magisk hide was separated, so I could hide root for an app and hook with lsposed, now if I put the app in denylist, lsposed is not working.
I see many people use shamiko for hide root and continue to use lsposed, but I don't like because it's closed source.
I found an alternative DenylistUnmount (open source) is not perfect as shamiko but I think is good for many apps. I installed about 30 banking apps and only one detect root with DenylistUnmount but root is detected also with shamiko. So also shamiko is not perfect.
Has anyone tried this module yet?

I haven't; looks like a great alternative to Shamiko for those wanting proper root hiding w/ LSPosed modules working but are closed-source wary! May give it a try when I have more time... Looks like it needs much refinement at this stage however.

Actually, I had looked briefly at LSPosed_mod from this dev (mywalkb), but haven't had time to play with anything there...

PS. Some things to consider:
- Riru had inbuilt hiding (from v22):
https://github.com/RikkaApps/Riru#how-does-hide-works
whereas Zygisk makes no attempt to hide itself; Zygisk hiding is incorporated in Shamiko. (Not sure if Denylist Unmount hides Zygosk)
- Shamiko incorporates other hiding methods including isolated process leaks (unshare), modified init.rc traces etc, previously refined by LSP Devs, notably vvb2060 and Canyie.
- Canyie's original Riru-MomoHider module was open source. For her reasons for making its successor Shamiko closed, see here:
https://github.com/canyie/Riru-MomoHider#deprecation-notice
- To compare hiding performance, use Momo, also mentioned on Riru-MomoHider page linked above. Scroll down for it's TG link.

I put a complete Shamiko function list here:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-86889071

Thanks for heads-up! 👍 PW

Last edited: Today at 1:40 PM
Riru and Zygisk do not work together

With Magisk v24 you must use LSPosed-Zygisk (not the old LSPosed=LSPosed-Riru) - if needed scroll/search through the old posts, this is something that is coming back every month or so (when somebody, like you now, upgrades with delay to v24)...

But this user just means that when hiding root from bank apps, it's either denylist or LSPosed hooking but not both with Zygisk builds... Ie. XprivacyLua, HideMyApplist and other Xposed modules used for hiding won't work for apps in denylist since Magisk modifications are reverted for these.

Of course Shamiko solves this problem as user acknowledges, but he/she is reporting an alternative, if a less refined one... PW

Last edited: Today at 2:27 PM

TheDon13

Senior Member
Oct 9, 2010
Hi all

Have been happily using Google Pay and all banking apps (apart from Chase!) that like to detect root on my rooted Xiaomi Mi 11 Lite 5G for past few months with no issues at all

Out of the blue, Google Pay yesterday started giving me the "Not set up" message on all my bank cards within that app. Checked phone still passes safetynet check and all my banking apps still work as Magisk (Hide) is frozen within Sd Maid....so I am very puzzled.

Advanced root checker confirms definitely still rooted & Ad Away all fine kepping those pesky ads at bay. So folks, any ideas pls?

Thanks in advance

ipdev

Recognized Contributor
Hi all

Have been happily using Google Pay and all banking apps (apart from Chase!) that like to detect root on my rooted Xiaomi Mi 11 Lite 5G for past few months with no issues at all

Out of the blue, Google Pay yesterday started giving me the "Not set up" message on all my bank cards within that app. Checked phone still passes safetynet check and all my banking apps still work as Magisk (Hide) is frozen within Sd Maid....so I am very puzzled.

Advanced root checker confirms definitely still rooted & Ad Away all fine kepping those pesky ads at bay. So folks, any ideas pls?

Thanks in advance

I do not use gPay but, it was discussed the other day in the general thread.

pndwal found a solution and posted it in the [Discussion] Google Pay Magisk Discussion Thread.
Post #2,464.

Give it a try and see what happens. 🙃

Cheers. :cowboy:


About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK