[Discussion] Magisk - The Age of Zygisk.
- Thread starter ipdev
- Start date
Have you tried the app on your device to see if it detects root or not using island?
Well incompatible modules can cause boot loops... Worth disabling small just in case, but I think you likely have this issue:
Failed to update in recovery patch mode #5673
... Seems Direct install to update isn't working, but that a new patch / flash with Odin works (ie. as a workaround):
https://github.com/topjohnwu/Magisk/issues/5673#issuecomment-1106681080
The issue is active and marked as a regression, so I'd watch that space... PW
Because riru core itself cripples the whole OS compared to zygisk in addition to already gone out of support. All modules are zygisk now
Last edited:
Can you disable Zygisk when you want to use this one troublesome app, then reenable Zygisk when you are done?
This is my current solution. However, it involves reboots and risk of bootloop but it works for the time being
Problem... After Momo 4.1.1 found magisk a few days ago, today ESET also found rooted device. Shamiko didn't manage to hide root, also I tried to hide renamed Magisk from ESET with HMA but no success.
PS: I solved the Magisk detection.. After a lot of experiments, I disabled shamiko, enabled forced deny list, reboot, disable force deny list, enable shamiko, reboot and the miracle was done. I guess that shamino was needed a reset..
PS: I solved the Magisk detection.. After a lot of experiments, I disabled shamiko, enabled forced deny list, reboot, disable force deny list, enable shamiko, reboot and the miracle was done. I guess that shamino was needed a reset..
Attachments
Last edited:
I created a blacklist that hides Magisk, Titanium and HideMyAppList
I set HMA to Enable All Hide Methods on all the HSBC apps (Reward +, easy invest and HSBC HK) and chose that blacklist
paarkhi
Senior Member
Can you please tell how to hide / detach Youtube from playstore by HMA, thank you, I'm sorry if it's explained elsewhere in the thread but I read this thread from page 68 to the end and have started reading from the start and got your post also here but unable to understand how to do it
Thanks once again for various posts explaining other things in this thread
Last edited:
Check this post in this thread and the links there:
https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-86376291
paarkhi
Senior Member
what steps should I do so that xposed module are not detected in Applis detector as in your screenshot, I have hidden Applist detector in magisk and rest everything is ok but xposed modules are being detected (SS attached), thank you
Attachments
I did nothing specific...You may want to select "read applications" for Applist Detector in XprivacyLua
Actually mileage varies across rom for these xposed modules and their settings.
For eg. I am seeing Abnormal Environment whereas it is all good in your case.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
6
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 reboot6
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...Can someone try this app and see if it works?
My set up is currently this and it still doesn't work. Magisk alpha + zygisk enabled + Denylist +lsposed
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 guidelines5
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.
samhhmobil4
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)..3
@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 -
145This 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.
Jump to PostMagisk - Modules - Apps - Force Basic Attestation - Basic Attestation - Adjust Prop values - Notes - Points of Interest
This is post will be updated once Magisk v24 is released.74MagiskThe Magic Mask for Android.
Magisk Links:
GitHub
- Installation Instruction
- Frequently Asked Questions
- Magisk Documentation
- Magisk Troubleshoot Wiki (by Didgeridoohan)
Download Links:
Stable and Beta releases.
Canary
- GitHub
Thenotes.mdfile is the change log.
Theapp-debug.apkis Magisk canary.
Click onapp-debug.apkand choose View Raw or click on the Download option.
Credits:
topjohnwu
All who contribute and support this project.62Modules
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.58Apps
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.49Force 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.
- 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.
- Go to Modules.
- Select Install from storage.
- Navigate to the Universal SafetyNet Fix module zip file and select it.
- 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. - SafetyNet
