yashsingh1/xdaforums huggingface dataset:
[Magisk] zulu88:
I was updating v23 to v24.1 in the Magisk application. On the previous version, where there is no Zygisk, everything worked perfectly.
[Magisk] pndwal:
Thanks for creating issue for this!

https://github.com/topjohnwu/Magisk/issues/5299

It will fix Zygisk issue for various Samsung devices!

Is that fair? Many are giving much practical help... @kramer04 has taken the right approach; ask here first, check existing issues, create one for Samsung Note 9...

You've only complained about new Magisk and members here in two discussion threads... 😕

However, please remember that Zygisk is still in beta (read not stable), and check the issue above... @canyie is now helping... also @yujincheng08 (LoveSy / Shana) and @huskydg...

Canyie (w/ Shana's help) has authored a fix already:

Invalidate Samsung's persist.sys.zygote.early #5348

https://github.com/topjohnwu/Magisk/pull/5348

She pushed a test build yesterday that you could try (in artifacts here):

https://github.com/topjohnwu/Magisk/actions/runs/1782099669

but John has already merged this and pushed his own test build here (only an hour ago):

https://github.com/topjohnwu/Magisk/actions/runs/1788464031

... try that, or wait till next TJW build is released. PW
[Magisk] simplydat:
Thank you so very much for the inspiration.

I was going crazy because one of my payment app keeps crashing no matter what I do. Then using logcat, I found a similar process throwing exception, then I disabled ProcessLifecycleOwnerInitializer in the app providers and the app finally starts.

Although I still don't know what the app detected on my phone that caused the app to crash, but at least now I can prevent the crash.
[Magisk] zulu88:
@kramer04 Thank you very much. Editing init.rc fixed the problem. Thank you all.
[Magisk] pndwal:
Well done!; best place to start! 🤪

I was just talking a look at your issue, but glad it's resolved!

Well said!

I must reiterate that new Magisk Zygisk framework allows for much more powerful hiding as well as making other modules far more versatile / powerful. We have John's foresight to thank for this, and it's only early days for beta Zygisk.

Already, powerful hiding tools have emerged using Zygisk: USNF can target Google's SafetyNet process properly and avoid the device-specific issues of previous solutions for instance. Shamiko initially only hid Zygisk, now hides isolated process leaks and more from bank apps etc. Public release only arrived yesterday, along with public zy-LSPosed; I'm sure hiding issues w/ MIUI etc will ironed out soon enough too. (Last, now public version, fixed MOMO crash issue for me. 👍)

Really, with banks and others employing more and more clever detection methods, it's a bit rich to expect John to do keep up with the hiding game on his own.

What he has done is actually improved Magisk framework to better equip other skilled Devs (and 'determined hiders') to take up this mantle / let their skills 'shine'.

I think he made the right call; it's what Magisk needed and what we all needed... Thanks and well done John! 😀

I hope everyone here considered John's statement in release notes for Magisk 24+:

MagiskHide Removal​

I have lost interest in fighting this battle for quite a while; plus, the existing MagiskHide implementation is flawed in so many ways. Decoupling Magisk from root hiding is, in my opinion, beneficial to the community. Ever since my announcement on Twitter months ago, highly effective “root hiding” modules (much MUCH better than MagiskHide) has been flourishing, which again shows that people are way more capable than I am on this subject. So why not give those determined their time to shine, and let me focus on improving Magisk instead of drowning in the everlasting cat-and-mouse game 😉.

Couldn't have put it better. PW
[Magisk] Prof_Shekhar:
Although I have managed to reinstall Magisk 23 successfully, passed SafetyNet check and able to hide most of the Magisk for most of the non banking applications.

However, when I try to hide the Magisk manager (app) by giving it another name, the Magisk just creates a dummy app but nothing else happens. Magisk manager is still visible in its original form and the 'Hide the Manager app' still doesn't change to Restore the original App.' Screenshot attached.

Can anyone suggest what can be done to hide the manager app?
[Magisk] pndwal:
@mahaseno provided this:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/page-16#post-86352003

That's not an officially hosted json however.

Seems that John somehow hasn't set stable channel properly; It may be calling a generic json calling current stub apk with versionCode = 24. Should be 21 for Magisk 23.0.

I'd be trying setting the official JSON in Custom Channel first:

https://raw.githubusercontent.com/t...4e59f631280cc26ccc6d40a7cf04f7f37/stable.json

Using Canary 23001 (synced with Stable 23.0) may also work...

Also, Magisk is now supposed to fetch stub from installed package when network is not available, so simply turning off data connections may allow hiding to work.

Please report what works (most of us are now using 24.1 +). 👍 PW
[Magisk] simplydat:
I was just as skeptical as you and wanted to stay on Magisk 23 for as long as possible, but root was being detected left and right no matter what I did and I was forced to keep payment and bank apps on older versions.

However, I finally decided to update to Magisk 24 (Zygisk mode) + Universal SafetyNet Fix + Shamiko and BOOM, all the "latest" version of payment and bank apps that did not work in Magisk 23 started working in Magisk 24, and I could finally get rid of Lsposed and Hide My Applist as they were no longer needed to hide root.

So with Magisk 24, you literally only need 2 modules (Universal SafetyNet Fix + Shamiko) to make everything hidden way better than before.

In fact, you probably don't need Shamiko. The bulit-in Denylist in Magisk 24 will work in most cases.
[Magisk] szazs89:
How did you update to v24? Just from the app? Wasn't there any tricky parts?

As for Shamiko, it is needed to hide Zygisk itself.
[Magisk] xabu:
Your first screenshot shows that the app is not hidden yet.
[Magisk] simplydat:
Updated within the Magisk App. No tricky part at all. Literally took less than 30 seconds.

Enforce Denylist was already good enough on all of my bank apps before I installed Shamiko.

The only reason I installed Shamiko was to be future proof so I don't ever have to deal with root hiding again. (Hopefully)
[Magisk] pndwal:
Bit more on upcoming (merged) Samsung Zygisk issue fix:

Invalidate Samsung's persist.sys.zygote.early …

Samsung FDE devices with the "persist.sys.zygote.early=true" property will cause Zygote to start before post-fs-data. According to Magisk's document, the post-fs-data phase should always happen before Zygote is started. Features assuming this behavior (like Zygisk and modules that need to control zygote) will not work. To avoid breaking existing modules, we simply invalidate this property to prevent this non-standard behavior from happening

👀 PW
[Magisk] jbradshw:
I searched this thread but didn't seem to find anything related to my question, but will the modules discussed on the first page ever be in the Fox MM? I'll install them manually but they seem to be important enough to be in there and I can't find any of them in there currently.
[Magisk] simplydat:
Nobody knows.

Fox MM is a third party repo, whether developers will embrace it or users will know about it is a big question.

LSposed tried and failed, now exposed modules are scattered and fragmented.

Magisk completely dropping official repo without any sort of backup plan will lead to the same problem.

Magisk without an official repo is just like Android with Google Play Store and iOS without App store. Modules will be scattered everywhere. Users won't know about them and dev won't have any motivation to create them.
[Magisk] wyt18:
Working for me on Magisk alpha, latest Shamiko, HMA, stock one UI 6
[Magisk] prokiller1199:
Couldn't even open the app after installing HMA, running pixel stock march patch
[Magisk] wyt18:
Was forced to update to 22.0.0, now it force closes after 3s. Found a fix yet?
[Magisk] zgfg:
Check discussion in the HMA thread and better ask there
[Magisk] buebue#8888:
It seems like the Zygote Injection is detectable now. For me the "Payback" app wont work anymore.

PAYBACK - Karte und Coupons - Apps on Google Play

Even more points, exclusive coupons and discounts. Save now!

play.google.com

S20U, Android 13 latest security patch, Magisk Delta (Kitsune 26400), Magisk Hide, Zygisk, lsposed, HMA.

Source:

https://www.reddit.com/r/Magisk/comments/198c0hz
[Magisk] xcl1pse:
Well goodluck fixing your environment then..
[Magisk] samhhmobil:
Welcome on board!

At first: If you use lsposed, zygisk may be detectable again.

Without(!) lsposed the following are my results:

Payback is not detecting zygisk!

(1) Payback IS(!) working with unlocked bootloader, StockRom(!), no root, but due to the unlocked bootloader no Device-Integrity.

(2) Payback IS(!) working with unlocked bootloader, StockRom(!), Magisk 27(hidden), active zygisk, Shamiko 1.0.1 (Google GMS, Payback — and other apps — on denylist, denylist not enforced), PlayIntegrityFix 15.9.7 by Chiteroman.

In THESE two configurations Payback works!

But...

(3) Same device: unlocked bootloader, CustomRom (LineageOS 17/18/19 or 20), NOT rooted, nothing else installed, and: Payback does NOT work.

(4) Changed to the second (rooted) scenario, but only changed from StockRom to CustomRom, and: Payback does NOT work.

So... Payback does not check the status of the bootloader.

Payback even does NOT check Device-Integrity (It works with StockRom and unlocked bootloader without root and without Device-Integrity).

With the usual way (hidden-magisk, active zygisk, denylist, shamiko, playintegrityfix, but NO lsposed) Payback CANNOT detect root or zygisk (tested with use of a StockRom).

But: Payback detects the existence of a CustomRom, even without root, and refuses to work.

So, if you (or somebody else) have a solution to hide the use of a CustomRom, feel free to post the solution here. (Even Momo detects the CustomRom... and... BTW, Momo detects zygisk again, when I use lsposed.)

samhhmobil

EDIT (2024-04-19):

Due to the hint of @crok.bic below I changed just only in /system/build.prop the name of "ro.lineage.build.version" to "ro.whateveryouwant.build.version" (set whateveryouwant to any word you want, for example "hide" or "donaldduck" or "strange" or... ...)

With this small spoof Payback works not just only in the scenarios (1) and (2), but now even in (3) and (4).

Thanks again to @crok.bic
[Magisk] crok.bic:
I would bet a small fortune on that is what triggers it. Many other banking and multimedia / DRM protected app is triggered simply by having "linage" in the list of props (build.prop for example). Try this: mount /system read-write and remove a single char from all prop values that contains lineage in it (ex. lineage -> lineag) then reboot and likely it won't be triggered anymore. It will break the OTA process since the updater will not detect the build properly.. many banking apps are triggered like this (when using crDroid, LineageOS, etc..) and some of these apps are triggered by simpl using Xiaomi.EU for sure (but eliminating every xiaomieu and xiaomi.eu will cause an unbootable state - at least according to my experiments.. YMMV)..
[Magisk] Warzenfinger:
Hello,

I hope this is the right place for my question

I updated LineageOS from lineage-21.0-20240320-nightly to lineage-21.0-20240417-nightly-gts4lvwifi on my Galaxy Tab S5e and now Zygisk won't start.

What can I do?

Best regards
[Magisk] elicoth:
Try removing or disabling LSposed if you have it enabled.
[Magisk] Warzenfinger:
Thank you. With LSposed disabled Zygisk runs, but it's LSposed why I need Zygisk :-(
[Magisk] pndwal:
Does LSPosed+ Zygisk work if all LSPosed modules are disabled? PW
[Magisk] samhhmobil:
You're GREAT!!

Thanks a lot!

It's NOT necessary to change all lineage strings!

It just ONLY looks in build.prop for the existence of "ro.lineage.build.version". If the name of this prop is changed to "ro.whateveryouwant.build.version", then Payback works again.

Thanks a lot again.

samhhmobil
[Magisk] zgfg:
You can try the following - to avoid possibly breaking OTA

If you eg use Systemless hosts, then go to its folder (by root explorer like MixPlorer):

/data/adb/modules/hosts

And create there a file:

system.prop

containing:

ro.lineage.build.version=

Reboot, and the given prop shall be systemlessly removed (unless the ROM enforces the prop only after booting is completed)

When you want to do OTA, rename that system.prop to eg system.bak and reboot - you will again have the original ROMs prop(s)

You can similarly (miss)use any other module's folder and if it already has the system.prop, just add your lines in and reboot
[Magisk] Warzenfinger:
No, they don't :(
[Magisk] samhhmobil:
@zgfg

Nice try, but... it doesn't work.

It creates an empty prop "ro.lineage.build.version“, but the prop itself exists.

And payback does not check the value of that prop, but checks if it exists.

So, renaming it in build.prop seems to be the safe way.

samhhmobil
[Magisk] westruk:
Laso you can use this module

https://github.com/westruk/sensitive_props/releases/download/v5.1/sensitive_props-v5.1.zip
[Magisk] pndwal:
Nice enhanced fork of fork of @huskydg module!...

Of course these are original TJW MagiskHide sensitive prop adjustments + more...

From your readme.md:

(Seems Update README.md hasn't properly updated your sensitive_props main page however?)

👍 PW
[Magisk] westruk:
Don't provoke me😆

Added some lines in code today, maybe help in future.
[Magisk] aadeshiscool:
Can someone try this app and see if it works?

SBI Card - Apps on Google Play

Access your SBI Credit Card account instantly on your Android device.

play.google.com

My set up is currently this and it still doesn't work. Magisk alpha + zygisk enabled + Denylist +lsposed
[Magisk] zgfg:
I don't know for your particular app, but if you want help you need to share more info - like did you put that app to DenyList, what is your phone, ROM, Android version...

Moreover, if you use LSPosed, you probably have also one or more LSPosed modules. Which ones?

Also, to hide LSPosed modules you usually need to use HMA to hide them. So, do you do that and how (screenshots)?

If not familiar with HMA, please scroll back/search theough the older posts

Banking apps don't rely only on Pčay Integrity / Safety Net, but they usuallly apply other detection methids. To help yourself you would need to test with detectors like TBChecker, Ruru, SBCheck, even Momo and try to do your best to pass them (Momo will probably alsways detect something, at least unlocked BL).

Wjen you succeded with that, then apply sane hiding trchniques to themparticulat banking app

Unless you stumble to somebody using that exact app (Pkaystore says that app is not available worldwide to download and test) and to give you a xook-book.

You may alao tey to search for that app on XDA (if it was allready discussed)

I know, not much help from this respinse but some general guidelines
[Magisk] westruk:
Try shamiko
[Magisk] samhhmobil:
I tried.

But it's not helpful for me, because it does NOT remove ro.lineage.build.version (and even some other lineage props remain).

So the manual modification of ro.lineage.build.version in build.prop seems to be the one and only way.

samhhmobil
[Magisk] zgfg:
Modules based on resetprop in service.sh or post-fs-data.sh scripts and system.prop will only set your ro.lineage.build.version to empty, but getprop would still find the prop as:

ro.lineage.build.version=

Somebody has previously reported that it was not enough and that he had to remove los props from the build.prop file
[Magisk] eng3:
I'm trying to get the US citi app working.

Can you clarify your settings in HMA?

When you say "system apps excepted", how did you do this?

When I select whitelist mode, I can goto edit list. There is a checkbox to add system apps to the list, but it is hard to know which one are system apps and which are not.
[Magisk] pndwal:
That was a while ago and RN8T has now sadly died and haven't yet rooted new device...

Used standard whitelist hiding w/o system app inclusion as recommended... If that doesn't work I suspect other detection... My setup (see post above that one) was:

Xiaomi RN8T stock A11 MIUI,

Latest @vvb2060 Alpha Magisk (unofficial)

Magisk App hidden in stub,

Latest Shamiko public release (for proper root hiding),

LSPosed Hide My AppList module (configured to hide in whitelist mode).

OEM unlocking disabled,*

USB debugging disabled, *

Developer options disabled.*

* These may or may not be needed for Citi... Can't recall... 🤠 PW
[Magisk] eng3:
Shamiko? I'll try that out. I haven't rooted a phone for over 10yrs. Alot has changed

For Citi (SG version) you specifically mentioned Hide My applist in whitelist mode. But then you mentioned you said "system apps excepted". My question is really, how do you do this? I see where I can create a whitelist template. I can then select which apps I want visible. There is a checkbox to add system apps to the list, but it is all mixed in so I don't know which are system and which arent. How did you select all the system apps?
[Magisk] beeshyams:
India Citibank needs USB debugging to be disabled. Maybe that helps?
[Magisk] pndwal:
One major change is removal of MagiskHide in 24.0+...

DenyList is NOT proper root hiding (doesn't hide traces unlike MagiskHide, simply reverts current/denies further Magisk/module modifications also unlike MagiskHide); it's more a tool for developers / system testers who use root but need

https://topjohnwu.medium.com/state-of-magisk-2021-fe29fdaee458

Shamiko is the new "MagiskHide" root hiding solution (importantly adding 'ZygiskHide' and more, and hidelist based, although hijacking list from disabled DenyList for convenience) developed by "those who are still passionate about hiding" per:

www.twitter.com/topjohnwu/status/1445598600143073287

You don't need any template for whitelist mode... Just activate it using Work mode toggle...

Exclude system apps should be toggled on, and "Turn off... only when really necessary" as "It is likely to cause crash with it disabled" (per toggle description)...

If you do make a whitelist template and apply it, apps selected will simply be excluded from those invisible to app being configured (per Template manage info dialogue)...

I found the inbuilt dialogue/descriptions sufficiently self explanatory, but I've been using HMA from it's debut... For an exhaustive guide to usage, see Guide from @ipdev and @73sydney, former familiar XDA members, in GitHub repo linked from OP here:

https://xdaforums.com/t/hide-my-applist-a-brief-guide.4519731/

If using HMA on Pixel w/ post March updates (or QPR2 beta) you'll need CI build ("Fix[es] argument order of startViaZygote() hook on 14 QPR2") ATM (+ a GitHub account to download)... See this post:

https://xdaforums.com/t/hide-my-applist-a-brief-guide.4519731/post-89467545

👀 PW
[Magisk] zgfg:
You can find another thread with general instructions how to set HMA (blacklisting and whitelisting) - to check and further ask/discuss about HMA there

Particularly, see OP post #1 in that HMA thread, leading to the detailed HowTo HMA instructions on GitHub

Hide My Applist - A Brief Guide

Hide My Applist Guide Hide My Applist is a LSPosed module by Dr-TSNG (nullptr). Often referred to as HMA. In the simplest terms HMA aims to stop one app detecting a list of other installed apps. - It can often help stop your banking app(s) from...

xdaforums.com

GitHub - mModule/guide_hma: This is a quick guide to hopefully make it a little easier for people new to Hide My Applist.

This is a quick guide to hopefully make it a little easier for people new to Hide My Applist. - mModule/guide_hma

github.com
[Magisk] pndwal:
2nd last paragraph in post above... 😉 PW
[Magisk] m0han:
How did you kill it? ;)

What is keeping you and what is the new device?
[Magisk] pndwal:
https://xdaforums.com/t/hide-my-applist-a-brief-guide.4519731/

I'm a Goon... Dropped it the in water about a year ago... Made like Spike Milligan and immediately cried "It's fallen in the water!"

Opened, disconnected battery, dried w/ heat, then for few days in rice before connecting battery and closing... Worked fine after but lost rotation/gyro (and compass) sensors... Thought they'd snuffed it (sensor hardware had simply vanished in diagnostics) so suffered that (found they're located on main board unlike some other sensors, so no practical fix) for 6 months... Then suddenly sensors came back (I was like "well OK then... ") and everything was sweet for 3 or 4 months... Then screen started blinking out at odd times, but hitting/squeezing would bring it back on... After a month was about to replace screen but started with charging issues... Sometimes would, sometimes wouldn't... Finally died completely and I got new phone... Phew...

But hadn't retrieved data, silly me... So bought battery (cheap) and that had just enough charge to have time to hit phone enough to make screen activate (almost gave up) and get transfers going which failed to complete so I installed a Xiaomi app (for data transfer to new phone) and that finally completed fully with 1% battery left... Double Phew!... And true story.

Time, life, motivation, lack of enthusiasm... 🙃

Redmi Note 12 5G... Nice phone for modest outlay... Has an ingress rating (IP53, better than nothing!) and my first AMOLED screen (makes battery lasting MUCH longer)!...

Yeah, I know... I'll get round to it... (Have rooted tablet in the meantime) 🤠 PW
[Magisk] eng3:
Ah, "App Manage" I missed that.

I also installed Shamiko.

And now the app seems to work. Also Hyundai Digital Key.

I have to disable HMA to see if it was Shamiko or HMA or both.

I did find that if I used the deny function alone or BypassRootCheckPro Lsposed module, the app would crash.
[Magisk] molitar:
Zygisk Next will not enable after installing and rebooting Magisk. Error "failed to inject init"
[Magisk] amk316:
reinstall it

i do that every magisk or firmware update
[Magisk] molitar:
Figured it out.. I had to disable every module that uses zygisk than reboot.. it injected than I was able to turn on Zygisk. It says to disable the zygisk in Magisk but not to disable all zygisk modules until installed.

Now how does this Zygisk Next work since you can't put apps into deny list now is it automatic?
[Magisk] Wolfcity:
What about Shamiko?
[Magisk] molitar:
I also have it installed and it works fine with Zygisk Next. Next just works it seems no matter what I have tried to run so far.
[Magisk] ashish1989:
Sorry to bother you guys, I am getting a strange problem on official magisk 27.0 stable on my stock samsung j7 prime android 8.1 rom with custom kernel.

Whenever I am adding my bank app and gms and gms.unstable processses in denyist the apps are getting stopped, without adding them in denylist, they are working fine. E.g. I added paytm app in denylist, then paytm has stopped error is coming continuously, I added gms and gms.unstable processes in denylist, google play services has stopped error is coming continuously, after excluding them from denylist, they are working fine.

I am also attaching the logcat for your reference
[Magisk] Nergal di Cuthah:
Don't deny google services or gms to deny list it breaks things.

Are you using a play integrity fix (fix, fork or next)?

Edit: might not be needed for 8.1

Is your kernel on @osm0sis' list of banned kernels.

Are you using shamiko?
[Magisk] ashish1989:
Ok will not add gms and gms unstable process now. I am using playintegrityfix by Chiteroman, my kernel is not in the banned list, Osm0sis bro already checked it and yes I am using Shamiko which is working as blacklist mode
[Magisk] J.Michael:
Try a later Canary, I think it's up to 27.4.

Good news/Bad news: With Canary you'll be in a position to report a problem; they're not likely to care about problems related to hiding.