With Magisk 24 a couple of things have changed and its got me confused maybe someone here can help me understand.
Previously, with MagiskHide I could select apps for which Magisk would be hidden. In addition, I had riru/lsposed with a couple of modules, afwall+ donate and xprivacyLua for example. I selected all user installed apps for both these modules. So I basically had hidden magisk, and magisk and lsposed modules worked on selected apps.
With Magisk 24 it seems differently, but maybe I misinterpret.
With Magisk 24, I enable zygisk with enforce deny list. The description says that selected processes will have all Magisk modifications reverted.
I installed lsposed canary version which works with zygisk on Magisk 24 (on 2/2 it will be pushed to the stable channel). I installed the same modules, afwall+ and xprivacylua. Except that now all the apps that are on the zygisk denylist are marked as such in the lsposed module list. I suspect this means lsposed as a zygisk module is also reverted on apps on the denylist.
So if thats correct, basically we cannot have Magisk hidden and still have LSPosed modules applied, such as AFWall and XprivacyLUA.
Is that correct or am I misinterpreting the denylist description?
droidvark said:
With Magisk 24 a couple of things have changed and its got me confused maybe someone here can help me understand.
Previously, with MagiskHide I could select apps for which Magisk would be hidden. In addition, I had riru/lsposed with a couple of modules, afwall+ donate and xprivacyLua for example. I selected all user installed apps for both these modules. So I basically had hidden magisk, and magisk and lsposed modules worked on selected apps.
With Magisk 24 it seems differently, but maybe I misinterpret.
With Magisk 24, I enable zygisk with enforce deny list. The description says that selected processes will have all Magisk modifications reverted.
I installed lsposed canary version which works with zygisk on Magisk 24 (on 2/2 it will be pushed to the stable channel). I installed the same modules, afwall+ and xprivacylua. Except that now all the apps that are on the zygisk denylist are marked as such in the lsposed module list. I suspect this means lsposed as a zygisk module is also reverted on apps on the denylist.
So if thats correct, basically we cannot have Magisk hidden and still have LSPosed modules applied, such as AFWall and XprivacyLUA.
Is that correct or am I misinterpreting the denylist description?
Click to expand...
Click to collapse
Your misinterpreting it, deny list just denies access to zygisk to the apps you selected, you have to use LSPosed zygisk version as Rieu will not work with it. Everything else works the same
Darkaeluz said:
Your misinterpreting it, deny list just denies access to zygisk to the apps you selected, you have to use LSPosed zygisk version as Rieu will not work with it. Everything else works the same
Click to expand...
Click to collapse
Thanks! Yes I am using the Zygisk version (and I think you meant riru, rieu sounds like an autocorrect mistake ).
Maybe I didn't explain it very well. I tested it with several apps in different situations and it works like I suspected. For example, XprivacyLua can deny apps access to the clipboard. When an app is on the denylist in Zygisk and has access to the clipboard denied in XprivacyLua, it still has access to the clipboard. Once I remove the app from the denylist, XprivacyLua starts working and selected apps are denied access to the clipboard.
In other words, LSPosed modules do not work on apps that are on the denylist. During my trials I also noticed the short popup message in LSPosed saying that it might not work on apps on the denylist.
I think this is a serious regression from previous versions.
The OP has a valid question. I hope someone can answer.
I have the same query as OP. How do we configure denylist in tandem with other modules?
If any bank app is selected in the denylist, then in XPrivacyLua the same app is given a label "On denylist"
droidvark said:
With Magisk 24 a couple of things have changed and its got me confused maybe someone here can help me understand.
Previously, with MagiskHide I could select apps for which Magisk would be hidden. In addition, I had riru/lsposed with a couple of modules, afwall+ donate and xprivacyLua for example. I selected all user installed apps for both these modules. So I basically had hidden magisk, and magisk and lsposed modules worked on selected apps.
With Magisk 24 it seems differently, but maybe I misinterpret.
With Magisk 24, I enable zygisk with enforce deny list. The description says that selected processes will have all Magisk modifications reverted.
I installed lsposed canary version which works with zygisk on Magisk 24 (on 2/2 it will be pushed to the stable channel). I installed the same modules, afwall+ and xprivacylua. Except that now all the apps that are on the zygisk denylist are marked as such in the lsposed module list. I suspect this means lsposed as a zygisk module is also reverted on apps on the denylist.
So if thats correct, basically we cannot have Magisk hidden and still have LSPosed modules applied, such as AFWall and XprivacyLUA.
Is that correct or am I misinterpreting the denylist description?
Click to expand...
Click to collapse
same here :v
so much confusion lol
droidvark said:
Thanks! Yes I am using the Zygisk version (and I think you meant riru, rieu sounds like an autocorrect mistake ).
Maybe I didn't explain it very well. I tested it with several apps in different situations and it works like I suspected. For example, XprivacyLua can deny apps access to the clipboard. When an app is on the denylist in Zygisk and has access to the clipboard denied in XprivacyLua, it still has access to the clipboard. Once I remove the app from the denylist, XprivacyLua starts working and selected apps are denied access to the clipboard.
In other words, LSPosed modules do not work on apps that are on the denylist. During my trials I also noticed the short popup message in LSPosed saying that it might not work on apps on the denylist.
I think this is a serious regression from previous versions.
Click to expand...
Click to collapse
In order to make this work before what you need to do is configure the dentist and enforce toggle on. Reboot phone. Search Magisk alpha thread on telegram. Download latest Shamiko Magisk module. Toggle the enforce toggle off then flash the Shamiko module and reboot. all will work like before
Ps riru doesn't work on zygisk yet as far as I know and there is lsposed zygisk version you will need to run attached below. Remove riru core and old lsposed prior to flashing new one
Also if you need more hiding ability use hidemyapplist xposed module for other stuff
toolhas4degrees said:
In order to make this work before what you need to do is configure the dentist and enforce toggle on. Reboot phone. Search Magisk alpha thread on telegram. Download latest Shamiko Magisk module. Toggle the enforce toggle off then flash the Shamiko module and reboot. all will work like before
Ps riru doesn't work on zygisk yet as far as I know and there is lsposed zygisk version you will need to run attached below. Remove riru core and old lsposed prior to flashing new one
Click to expand...
Click to collapse
Thanks gonna try this out.
edit: everything works fine. thanks!
looks like shamiko takes the denylist and enforces it while preserving the ability for the same list to be accessible for lsposed modules. nice thing.
EGYPT2021 said:
Thanks gonna try this out.
edit: everything works fine. thanks!
looks like shamiko takes the denylist and enforces it while preserving the ability for the same list to be accessible for lsposed modules. nice thing.
Click to expand...
Click to collapse
Been using it this way for 3 plus months
Shamiko is actually a zygisk hide itself
Thank you guys for offering a possible solution but after the tests i took i think this shamiko module is just a visual module. To share one of my test results i installed this app Device info pro and on the system tab it says root management app Magisk....
So there is no solution yet i think to have zygisk deny list configured for the some app and use for example xprivacylua lua on this app and have them both working toghether properly..
okwhateverok said:
Thank you guys for offering a possible solution but after the tests i took i think this shamiko module is just a visual module. To share one of my test results i installed this app Device info pro and on the system tab it says root management app Magisk....
So there is no solution yet i think to have zygisk deny list configured for the some app and use for example xprivacylua lua on this app and have them both working toghether properly..
Click to expand...
Click to collapse
Shamiko is not a visual mod... It hides zygisk.... Maybe read a little. Also did you turn denylist toggle off before flashing shamiko.
Exactly, if shamiko v0.4.3 was not a visual mod (at least on system level) i should not be able to see what app does provide root if i got this app enabled on the magisk denylist and got this same app completely blocked by xprivacylua using Lsposed 1.7.2 zygisk.
This means that this is a pure cosmetic mod, but thanks to the developers anyway.
I think i had done a little more than only read a little haha...
Nvm
Hi, I have a similar question. I use SeftyNet from kdrag0n, works fine with a banking app (denyList + enforce)
Can I add programs preventively? For example most of Google, all banking apps (before I run them)?
Could this slow down the system? Or make the applications will not work properly?
After reading this thread, I have a question. I wonder whether to use SeftyNet from kdrag0n, or Shamiko ?
PS I've had a lot of work lately and a long pause on Android systems, And I'm just catching up.
okwhateverok said:
Exactly, if shamiko v0.4.3 was not a visual mod (at least on system level) i should not be able to see what app does provide root if i got this app enabled on the magisk denylist and got this same app completely blocked by xprivacylua using Lsposed 1.7.2 zygisk.
This means that this is a pure cosmetic mod, but thanks to the developers anyway.
I think i had done a little than only read a little haha...
Click to expand...
Click to collapse
Did you find an answer? Lsposed modules + Denylist enforced or somehow else?
I did not find a solution nor the developers did so far...
This all while running the latest version of Shamiko v0.5.0 and Lsposed Zygisk v1.8.3.
But still i want to thank the developers for their hard work because it is actually the manufacturers android developers who does close these doors for their users to modify and control their own devices.
No delta anymore
FYI .... I found out that for some funny reason one banking app with a wierd name like /data/data/com.uniken.r2fa4a.boi will not add via GUI . If you add it to denylist via GUI it will auto uncheck. Its aint a system app why then does Magisk ( latest as I type ) refuse to add it ? Go Figure. In the meantime , found a workaround by using ---denylist add < package > on command line. So far it seemed to have worked. But dunno why GUI would'nt take my commands
huskydg said:
I have a fork that restore MagiskHide from DenyList. MagiskHide can be enabled no matter Zygis is enabled or disabled. After enable MagiskHide, zygisk module will still be loaded on denylist. I also add hide zygisk, hide for isolated process and app zygote into MagiskHide.
Where is this?
Click to expand...
Click to collapse
magiskhide is already inc in the magisk --denylist command just that there is no seperate bin for that in the new one .
Thanks @toolhas4degrees ! I also use XPrivacyLua and wanted to maintain security/privacy restrictions while also hiding root for certain apps. The Shamiko mod works!
Related
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)
State of Magisk: 2021
State of Magisk: 2020
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.
MagiskThe Magic Mask for Android.
Magisk Links:
GitHub
Installation Instruction
Frequently Asked Questions
Magisk Documentation
Magisk Troubleshoot Wiki (by Didgeridoohan)
Release Notes
Download Links:
Stable and Beta releases.
GitHub
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.
Modules
MagiskHide Props Config
This module allows you to add, change and adjust prop values systemlessly using Magisk.
MagiskHide Props Config Links:
GitHub
xdaThread
Download Links:
GitHub
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:
GitHub
xdaThread
Download Links:
GitHub
Credits:
kdrag0n
All who contribute and support this project.
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:
GitHub
Download Links:
GitHub
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:
GitHub
Download Links:
PlayStore
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:
GitHub
PlayStore
Download Links:
GitHub
PlayStore
Credits:
RikkaW
All who contribute and support this project.
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.
Spoiler: Instructions
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.
Basic Attestation<Reserve>
Older devices that can not support hardware attestation there are other options.
Enable Zygisk.
Enable Denylist.
Add com.google.android.gms.unstable to the Denylist.
Add com.google.android.gms to the Denylist if needed.
Reset the sensitive prop values for the device.
Click to expand...
Click to collapse
Due to other modules and methods that require DenyList to be inactive, this method is more for reference.
For ease of use and compatibility, I would recommend using the USNF module instead.
See the Force Basic Attestation post.
This post will be updated in a few days.
Adjust Prop values<Reserve>
Reset sensitive prop values.
Spoiler: Instructions
Download the MagiskHide Props Config module.
Open the Magisk app and select the Modules option.
Select Install from storage option.
Navigate to where you saved the MHPC module and select it.
When the install is done, reboot.
Open a terminal app (or adb shell) and type props in the command line.
Make sure to grant root access
Select the Edit MagiskHide props (active) option.
(Currently option number 4)
It will show you the sensitive props that need to be adjusted.
If they all show (active) no changes needed.
If there is a prop value that shows as (enabled, not active) then you need to activate it by selecting it or a for all.
You will be prompted to set MagiskHide sensitive props?
Enter y(es), n(o) or e(xit):
If you are using a custom rom, you might also have to adjust the build fingerprint and security date.
From the MHPC main menu select Edit device fingerprint option.
(Currently option number 1)
Select Pick a certified fingerprint option.
(Currently option f)
Select the latest certified print for your device.
If your device is not listed, choose a device that is close to yours.
This post will be updated soon.
NotesandCommon Issues<Reserve>
Spoiler: SafetyNet
<Reserve>
Spoiler: Play Protect certification
<Reserve>
Spoiler: PlayStore App Purchases and Updates
<Reserve>
Points of Interest.
LSPosed
Zygisk releases are now included.
Download Links:
GitHub - Releases
Shamiko
Download Links:
GitHub - Releases
Denylist Unmount
Download Links:
GitHub - Releases
Yay! I get post no. 10!
Good to see this thread up Doc! ... How are you linking / promoting it?
Want mentions in Magisk General Discussion thread, or not for now?...
I note that this thread has the advantage of having an active OP...
So what? - Means I can post rubbish and it will be cleaned! ... Love a clean house... Hope you're a good housekeeper @ipdev! PW
zputnyq said:
Hi all,
I'm on TJW's canary 23019.
Does anyone know/could explain what is/are the difference(s) with enforce denylist activated and not activated ?
Click to expand...
Click to collapse
denylist (which preserves some of MagiskHide infrastructure) is active, or not active...
Nb. For Zy-Shamiko hiding module solution to work, this needs to be deactivated for Shamiko to do the hiding itself; Shamiko just uses the same list for convenience / simplicity... PW
Edit: Lets kickstart things here!
pndwal said:
denylist (which preserves some of MagiskHide infrastructure) is active, or not active...
Nb. For Zy-Shamiko hiding module solution to work, this needs to be deactivated for Shamiko to do the hiding itself; Shamiko just uses the same list for convenience / simplicity... PW
Edit: Lets kickstart things here!
Click to expand...
Click to collapse
Ok, I get it. Thank you.
I was confused since I use an old device which doesn't really need this part to do the hiding & on v23017 John made that part work along with the configure denylist, I mean configure denylist is greyed out when denylist part isn't active.
zputnyq said:
Ok, I get it. Thank you.
I was confused since I use an old device which doesn't really need this part to do the hiding & on v23017 John made that part work along with the configure denylist, I mean configure denylist is greyed out when denylist part isn't active.
Click to expand...
Click to collapse
You could do worse than read the first 5 posts here! PW
Thanks @ipdev
I tried to put a short help for probably the most frequent posts/questions soon to expect.
(Sorry for cross-posting, I first put to the old and cluttered General Magisk thread but this is now better place)
===
Please carefully read Magisk Changelog and OP posts in this thread
Study the Magisk documentation from the official Magisk Github page - particularly about installing Magisk (if not familiar with patching the image in Magisk app and flashing the patched img from Fastboot- different from the old school about flashing Magisk zip through TWRP)
a) No more MagiskHide. New technology instead (for more or less the same - to help hiding root): Zygisk+DenyList
b) No more built in SafetyNet checker. Install from PlayStore e g: YASNAC to check your SN
c) Modules window does no more connect to the old Modules repository.
You must download module zip files manually and "Install from local storage".
Or search for and install Fox Magisk Module Manager (Fox Mmm) app - it will connect to the new, alternative repository and the old 'official' repo, allowing you to install from both
---
0) If upgrading Magisk and if you previously did "Hide Magisk app/Mngr" from Magisk app/mngr - always "Restore Magisk app/Mngr" before upgrading Magisk
1) Make sure that both Magisk app and Magisk are installed and updated to the new version v24 version. Inspect version numbers on the main Magisk window/page
2) Make sure to uninstall all Riru modules (Riru is not compatible with Zygisk that comes with Magisk v24)
3) Settings, Enable Zygisk and reboot.
Then check on the main window does it show Zygisk Yes
4) Settings, enable Enforce DenyList.
Configure DenyList, enable filters to Show OS and System apps.
Find Google Play Services and check-in only the two processes ending with gms and gms.unstable.
You will have to check in all your banking apps and so as you used with MagiskHide.
Always reboot upon reconfiguring DenyList
5) If SafetyNet does not pass, install USNF 2.2.1 and test again.
Always reboot upon installing a module, also if/when you enable Systemless Hosts
Note: Once you install/enable USNF 2.2.1, it will remove Google Play Services from your DenyList - but don't worry, USNF takes care of GMS
6) If you are on non-certified custom ROM and you still don't pass SN - then you will need Magisk Hide Props Config module - check for and consult the MHCP thread
---
If you want to hide Zygisk, then instal Shamiko module - and you must disable Enforce DenyList (although DenyList must stay configured).
But Shamiko is really not essential (might help for some banking apps but it's irrelevant for SafetyNet)
---
Banking apps - out of scope for this post (also, this thread is about the Magisk v24 itself, not abkut the particular banking apps)
Go to Magisk Github documentation, read Wiki, there is a section with tips you should try first
If putting your banking app to DenyList (now, instead of the old Magisk Hide) and hiding Magisk app does not help, and the other tips from Wiki do not help (like renaming TWRP folder and so), search in this thread how to use Hide My Applist (Zygisk-LSPosed module)
Every time you apply another tip to your troublesome banking app - go to Settings, Apps, and delete Cache and Data for that banking app before you try to open it again (some apps will cache that they previously found the phone was rooted)
Even with HMA, there are certain banking apps that cannot be tricked (on some phones like Xiami, etc)
---
Momo - absolutely not essential for your life
When you pass SN, Momo might still detect that your Bootloader is unlocked - you cannot hide it from Momo on e.g. Xiaomi phones
Generally, treat Momo as 'banking' apps (add to DenyList and reboot)
Momo does not look for apps (Magisk app, LSPosed mngr, LSPosed modules), hence for Momo you don't need to bother with HMA
Basic tips for Momo: Remove/rename TWRP folder, disable USB Debugging - for the rest, search for Momo posts in this thread - but still, there will be findings you could not hide from Momo (not encrypted Data, custom ROM, etc)
===
PS: Magisk Alpha v24.1 (vvb2060 and her team) has departed their way (different package name, revival of MagiskHide?), hence this post is now (mainly) for the official TJW Magisk Stable and Canary v24
(Some parts do apply also to Alpha but use Alpha on your own risk and ask the other Alpha users about the Alpha status and practices)
===
Last but not the list - there night be specifics for certain phones (like flashing with Odin for Samsung, end so on)
This post is generic, for your specific practices read/search through this thread and also on your phone/model subforuns on XDA
Hello - sorry if obvious but I'm having issues getting some apps checking for root to pass. I think the issue might well be the statement related to "Google Play Services and check-in only the two processes ending with gms and gms.unstable."
Regardless of whether I tick just these two, or if I tick the whole of Google Play Services, once I reboot and if I go back into Magisk the app reports that these services are no longer hidden.
This is Pixel6Pro Stock, January update, Magisk canary (but 24001 that synced with the public build) + Zygisk + USNF 2.2.1
Thank you
Chris
@ipdev
Thread was pinned. Thx for your effort
Nice. Will we be able to run a module like fakegapps without riru/LSPosed?
crypticc said:
Hello - sorry if obvious but I'm having issues getting some apps checking for root to pass. I think the issue might well be the statement related to "Google Play Services and check-in only the two processes ending with gms and gms.unstable."
Regardless of whether I tick just these two, or if I tick the whole of Google Play Services, once I reboot and if I go back into Magisk the app reports that these services are no longer hidden.
This is Pixel6Pro Stock, January update, Magisk canary (but 24001 that synced with the public build) + Zygisk + USNF 2.2.1
Thank you
Chris
Click to expand...
Click to collapse
No, you don't need to add Play Services processes w/ Zy-USNF as I explained here:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-86321879
Download YASNAC and check if you pass SafetyNet, then that you have Play Protect Device is certified in Play Store settings... If you have these, Bank app is using its own custom detection methods... PW
kurtn said:
Nice. Will we be able to run a module like fakegapps without riru/LSPosed?
Click to expand...
Click to collapse
Yes, Use Zygisk-LSPosed. PW
pndwal said:
No, you don't need to add Play Services processes w/ Zy-USNF as I explained here:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-86321879
Download YASNAC and check if you pass SafetyNet, then that you have Play Protect Device is certified in Play Store settings... If you have these, Bank app is using its own custom detection methods... PW
Click to expand...
Click to collapse
Yes I appreciate that. I guess my question was if it is correct that after reboot USNF deselects the gms and gms.unstable
Thanks for the explanation.
FYI found what was triggering the app and got it working. Before I had just renamed Magisk (I renamed to MagicApp if that matters) but that didn't work. Also "pausing" the app wasn't enough.
I needed to actually uninstall the Magisk Manager app itself.
So the mechanism being used by the other app wasn't looking for Magisk/SU, but the app iself.
The App failing doesn't have any local file permissions so must've been something else.
Actually I found two apps failing root check and both were resolved by uninstalling the (renamed) Magisk APK.
So I wondered if the app was simply listening to debug messages.
So I reinstalled and then reproduced the failure looking into ADB logcat.
I could see during opening and just before the protection was triggered logcat events against the ".Magisk" app related to denying access. Uninstalling Magisk app stopped those messages and then the app was able to start.
Should Magisk "hiding" the magisk manager app by renaming it from ".Magisk" also have relabelled all of the messages and such related to the app?
I just realized there was a new public Magisk release yesterday, v24, and reading through the changes I see there are two that kind of impact me: MagiskHide and the central module repository removals.
So far I had been using MagiskHide because of its ease of use, list apps, tick box, and that's it (I haven't encountered apps that detected Magisk or root status, although I know it's insufficient for some). For modules, for example, the one that moves user certs to the system store, I just searched directly from the Magisk app and it was all good as well.
But things change from now on with those things being deprecated and removed and because there isn't much to go about in the release notes I was wondering if someone could direct me to the way of doing things now.
- What's the most apt, prevalent, or recommended replacement for MagiskHide? From the release notes I gather its a module, but I'm clueless as to which one or whether there are more than one option.
- If searching for mods and directly installing them is not available through the app, is there anything like it? Or is it all manual now? I.e. look for a module around the net, download it, copy it / decompress it somewhere in the device and install it.
Thanks for everything!
KaoDome said:
I just realized there was a new public Magisk release yesterday, v24, and reading through the changes I see there are two that kind of impact me: MagiskHide and the central module repository removals.
So far I had been using MagiskHide because of its ease of use, list apps, tick box, and that's it (I haven't encountered apps that detected Magisk or root status, although I know it's insufficient for some). For modules, for example, the one that moves user certs to the system store, I just searched directly from the Magisk app and it was all good as well.
But things change from now on with those things being deprecated and removed and because there isn't much to go about in the release notes I was wondering if someone could direct me to the way of doing things now.
- What's the most apt, prevalent, or recommended replacement for MagiskHide? From the release notes I gather its a module, but I'm clueless as to which one or whether there are more than one option.
- If searching for mods and directly installing them is not available through the app, is there anything like it? Or is it all manual now? I.e. look for a module around the net, download it, copy it / decompress it somewhere in the device and install it.
Thanks for everything!
Click to expand...
Click to collapse
[Discussion] Magisk - The Age of Zygisk.
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...
forum.xda-developers.com
Here. First 5 post and you should know all you need
So, I read through that thread. It certainly solved a few issues for me. Like getting safety net, getting a repository, etc.
But it didn't have anything I see to replace magisk hide, even in the Fox Magisk Module Manager.
Do I just need to know other terminology now? Or is there something else I'm missing?
Quantumrabbit said:
So, I read through that thread. It certainly solved a few issues for me. Like getting safety net, getting a repository, etc.
But it didn't have anything I see to replace magisk hide, even in the Fox Magisk Module Manager.
Do I just need to know other terminology now? Or is there something else I'm missing?
Click to expand...
Click to collapse
I don't get it, Magisk Hide is good for passing SafetyNet and you said you got it. Anyway, for SafetyNet you can use the Universal SafetyNet Fix module.
If you meant the hide list, there's now the Deny list. To quote:
The Deny list is similar but instead of hiding Magisk from the process, Magisk is unloaded so there is nothing to hide.
Click to expand...
Click to collapse
Porpet said:
I don't get it, Magisk Hide is good for passing SafetyNet and you said you got it. Anyway, for SafetyNet you can use the Universal SafetyNet Fix module.
If you meant the hide list, there's now the Deny list. To quote:
Click to expand...
Click to collapse
Yes, it's for some banking apps, Concur, and others, none of which have any business checking for root, but all check for Magisk and such in other ways, and prevent usage.
If the deny list is how to do that now, I'll give that a go. Thank you
Quantumrabbit said:
Yes, it's for some banking apps, Concur, and others, none of which have any business checking for root, but all check for Magisk and such in other ways, and prevent usage.
If the deny list is how to do that now, I'll give that a go. Thank you
Click to expand...
Click to collapse
And where did you find the deny list?
fusk said:
And where did you find the deny list?
Click to expand...
Click to collapse
Settings enforce deny list. You need to enable zygisk and reboot prior also in settings.
Also there is an add on module shamiko that has more hide features after you configure denylist
H
toolhas4degrees said:
Settings enforce deny list. You need to enable zygisk and reboot prior also in settings.
Also there is an add on module shamiko that has more hide features after you configure denylist
Click to expand...
Click to collapse
How to add modules shamiko & how to more hide features
Spartacus500 said:
H
How to add modules shamiko & how to more hide features
Click to expand...
Click to collapse
Shamiko is a flashable only need to slash magisk module. You can find it in the magisk alpha thread on telegram. You need to configure denylist first and reboot then turn off the enforce denylist toggle and flash the shamiko module.
If you are using lsposed download hide my applist xposed module and search how to use it if you want more coverage
Pm me if you want links
I'm having a lot of trouble. Duo Mobile (a 2FA app) is still able to detect that I'm rooted. Here's what I've done:
1) Installed Magisk & Manager app version 24.1 (24100)
2) Enabled Zygisk (and rebooted of course)
3) Enabled Enforce DenyList
4) Added com.duosecurity.duomobile and ALL Google Play Services submodules to the DenyList
5) Installed Universal SafetyNet Fix v2.2.1 from https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.2.1
6) Hidden the Magisk app
7) Completely uninstalled & reinstalled Duo Mobile (and verified that it's still on the DenyList
This is incredibly annoying, is there anything I'm doing wrong? Is there a way to verify that the SafetyNet Fix is working as expected? Magisk doesn't have a "Check SafetyNet" option on the app anymore.
Drakinite said:
I'm having a lot of trouble. Duo Mobile (a 2FA app) is still able to detect that I'm rooted. Here's what I've done:
1) Installed Magisk & Manager app version 24.1 (24100)
2) Enabled Zygisk (and rebooted of course)
3) Enabled Enforce DenyList
4) Added com.duosecurity.duomobile and ALL Google Play Services submodules to the DenyList
5) Installed Universal SafetyNet Fix v2.2.1 from https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.2.1
6) Hidden the Magisk app
7) Completely uninstalled & reinstalled Duo Mobile (and verified that it's still on the DenyList
This is incredibly annoying, is there anything I'm doing wrong? Is there a way to verify that the SafetyNet Fix is working as expected? Magisk doesn't have a "Check SafetyNet" option on the app anymore.
Click to expand...
Click to collapse
This is quite weird and definitely shows how different devices handle root detection. I a Samsung S10+ and just installed Magisk 24 with enforce DenyList earlier this week. Today I just installed Duo Mobile and it works fine. I do not have it in the DenyList, and Magisk is not hidden. I use a custom SafetyNet fix that was installed when I originally installed an AIO TWRP/Magisk/SafetyNet fix after unlocking my bootloader. I also fail SafetyNet checks.
Have you tried Shamiko? It didn't help me pass SafetyNet so I removed it.
Unfortunately I don't have any other fixes for you but you can check SafetyNet with apps from the play store, I use YASNAC and SafetyNet 'attest'.
What phone are you using?
Drakinite said:
This is incredibly annoying, is there anything I'm doing wrong? Is there a way to verify that the SafetyNet Fix is working as expected? Magisk doesn't have a "Check SafetyNet" option on the app anymore.
Click to expand...
Click to collapse
There are SafetyNet checker apps you can download from the Play Store or F-Droid such as YASNAC.
danbest82 said:
Have you tried Shamiko? It didn't help me pass SafetyNet so I removed it.
Unfortunately I don't have any other fixes for you but you can check SafetyNet with apps from the play store, I use YASNAC and SafetyNet 'attest'.
What phone are you using?
Click to expand...
Click to collapse
I'm using a Oneplus 6. At your suggestion, I tried Shamiko, but so far it hasn't worked.
anonymous-bot said:
There are SafetyNet checker apps you can download from the Play Store or F-Droid such as YASNAC.
Click to expand...
Click to collapse
I tried Momo from the Magisk alpha telegram channel, and it's been helpful so far, but it's detecting Magisk/TWRP files and I don't know where they are located. Is there a way to find where these files it's detecting are? This might be what Duo is detecting.
When I run YASNAC, it passes the SafetyNet check.
Drakinite said:
I'm using a Oneplus 6. At your suggestion, I tried Shamiko, but so far it hasn't worked.
I tried Momo from the Magisk alpha telegram channel, and it's been helpful so far, but it's detecting Magisk/TWRP files and I don't know where they are located. Is there a way to find where these files it's detecting are? This might be what Duo is detecting.
When I run YASNAC, it passes the SafetyNet check.
Click to expand...
Click to collapse
Get VD Infos and use it to scan your files. You can find it on XDA.
Drakinite said:
I'm using a Oneplus 6. At your suggestion, I tried Shamiko, but so far it hasn't worked.
Click to expand...
Click to collapse
Hmm ok. Like I said shimako didn't work for me either. I'm not sure why Duo is still detecting root. For reference this is what is on my DenyList:
Drakinite said:
I tried Momo from the Magisk alpha telegram channel, and it's been helpful so far, but it's detecting Magisk/TWRP files and I don't know where they are located. Is there a way to find where these files it's detecting are? This might be what Duo is detecting.
When I run YASNAC, it passes the SafetyNet check.
Click to expand...
Click to collapse
YASNAC is the replacement for Momo it looks like since Momo is Riru based (https://github.com/canyie/Riru-MomoHider)
simplydat said:
Get VD Infos and use use to scan your files. You can find it in XDA
Click to expand...
Click to collapse
Ok so this one is more helpful, but I'm not sure how to hide these that appeared. Any idea what ro.kernel.qemu.gles is? I looked through my list of installed apps and nothing like that showed up.
Should we switch to private messages to not spam the thread? Or perhaps staying in here can be helpful for those with the same problem?
Drakinite said:
Ok so this one is more helpful, but I'm not sure how to hide these that appeared. Any idea what ro.kernel.qemu.gles is? I looked through my list of installed apps and nothing like that showed up.
Should we switch to private messages to not spam the thread? Or perhaps staying in here can be helpful for those with the same problem?
Click to expand...
Click to collapse
OMG WAIT, it finally worked! I don't know what changed, but Duo is now no longer detecting root. Gotta love when things magically start working when you don't know what changed.
Drakinite said:
OMG WAIT, it finally worked! I don't know what changed, but Duo is now no longer detecting root. Gotta love when things magically start working when you don't know what changed.
Click to expand...
Click to collapse
Awesome. Hope it stays that way!
Hi,
I've switched to the new method with the DenyList & Shamiko (v0.5.0) on OnePlus 6 recently - Magisk (v24.3), however it doesn't seem to hide root from Google Pay. Can it still be a bug with Magisk, when it can't hide system apps? In the changelog of Shamiko it mentioned that it was fixed in Magisk "24102+", I'm not sure what version is this, but I imagine it's not released yet. If so, is there a way of installing this version early?
Thank you!
antivirtel said:
Hi,
I've switched to the new method with the DenyList & Shamiko (v0.5.0) on OnePlus 6 recently - Magisk (v24.3), however it doesn't seem to hide root from Google Pay. Can it still be a bug with Magisk, when it can't hide system apps? In the changelog of Shamiko it mentioned that it was fixed in Magisk "24102+", I'm not sure what version is this, but I imagine it's not released yet. If so, is there a way of installing this version early?
Thank you!
Click to expand...
Click to collapse
Version 24102 would be v24.102. So your Magisk 24.300 is newer.
This is not an officially supported topjohnwu project.
If you are looking for official Magisk source, please go to this page
Introduction
Custom Magisk fork by HuskyDG. Sync with official Magisk adding back MagiskHide.
http://huskydg.github.io/magisk-files
REPORT BUG IS STILL ACCEPTED ON XDA THREAD BUT PLEASE INCLUDE ADDITIONAL INFORMATION SUCH AS LOGCAT AND MAGISK LOG
.
Good day @huskydg! Delta has been running all things smoothly on my end except for the Keytrade Bank application.
I've briefly mentioned it before over here but I think this might be a better place to find a solution. I'm trying to avoid LSPosed but if there's no other solution I'll go for that anyway.
Any ideas are most welcome! Thank you for your time.
OnePlus 6T
OOS 11.1.2.2
Hidden Magisk 25.1-delta (25100)
Zygisk disabled
MagiskHide enabled
DenyList checked for pretty much all Google/Gov/Financial apps and com.google.android.gms
Timmmmaaahh! said:
Good day @huskydg! Delta has been running all things smoothly on my end except for the Keytrade Bank application.
I've briefly mentioned it before over here but I think this might be a better place to find a solution. I'm trying to avoid LSPosed but if there's no other solution I'll go for that anyway.
Any ideas are most welcome! Thank you for your time.
OnePlus 6T
OOS 11.1.2.2
Hidden Magisk 25.1-delta (25100)
Zygisk disabled
MagiskHide enabled
DenyList checked for pretty much all Google/Gov/Financial apps and com.google.android.gms
Click to expand...
Click to collapse
Keytrade Bank is working with Delta / magiskhide
do you have enforce or permissive?
try to flash momohider module or join telegram group we have husky files to flash
you dont need to hide magisk app and you should flash safetynetfix 2.1.3 riru
Timmmmaaahh! said:
Good day @huskydg! Delta has been running all things smoothly on my end except for the Keytrade Bank application.
I've briefly mentioned it before over here but I think this might be a better place to find a solution. I'm trying to avoid LSPosed but if there's no other solution I'll go for that anyway.
Any ideas are most welcome! Thank you for your time.
OnePlus 6T
OOS 11.1.2.2
Hidden Magisk 25.1-delta (25100)
Zygisk disabled
MagiskHide enabled
DenyList checked for pretty much all Google/Gov/Financial apps and com.google.android.gms
Click to expand...
Click to collapse
It's working on OOS 11.0.8 on my OP7 Pro. Your problem comes very probably from the hidden Magisk. If that doesn't solve it, Riru + Riru MomoHider should do the trick
Timmmmaaahh! said:
Hidden Magisk 25.1-delta (25100)
Click to expand...
Click to collapse
Try not to use "Hide the Magisk app" option
Timmmmaaahh! said:
Good day @huskydg! Delta has been running all things smoothly on my end except for the Keytrade Bank application.
I've briefly mentioned it before over here but I think this might be a better place to find a solution. I'm trying to avoid LSPosed but if there's no other solution I'll go for that anyway.
Any ideas are most welcome! Thank you for your time.
OnePlus 6T
OOS 11.1.2.2
Hidden Magisk 25.1-delta (25100)
Zygisk disabled
MagiskHide enabled
DenyList checked for pretty much all Google/Gov/Financial apps and com.google.android.gms
Click to expand...
Click to collapse
I installed this app out of curiosity on two my devices: 1) Xiaomi Redmi Note 4 with custom ROM Android 10, rooted with Magisk Delta 25.1 (using Riru, LSPosed and MagiskHide); 2) Xiaomi Mi Note 10 with Xiaomi.eu ROM Android 11, rooted with official Magisk 25.1 (using Zygisk, LSPosed and Shamiko). And what I observed:
1) On the first device with custom ROM I was not able to fool Keytrade Bank app even with using MagiskHide enabled, repackaged Magisk Delta app, (I know it's rather redundant, but just in case , hidden LSPosed manager and using HideMyApplist properly configured. I suppose it may be involved with the old security patches because my ROM isn't being updated for Android 10 anymore.
2) On the second device I couldn't fool Keytrade app until I used HideMyApplist LSPosed module. It suggests that Keytrade is looking for a specific packages installed... Then by a process of elimination I determined it was the HideMyApplist app itself which causes the Keytrade app to crash! But since you dont have LSPosed installed at all, maybe there is another package which Keytrade app is looking for... Anyway, looks like running Keytrade is possible even with official Magisk and Shamiko (maybe even with Enforce DenyList as well)
EDIT: Pardon, it turned out that with only HideMyApplist app hidden Keytrade crashes after a while too. But I have 13 different apps with root access hidden with another template and with that applied to Keytrade I'm able to start a profile creation process
Sir, i tried using this app in zenfone max pro m1 with latest masgik v25 with zygisk enabled. So after giving super user request YES 2 times (it prompts for 2 prompts one after another) i opening settings and enabled "magisk hide" and did reboot device.
But after reboot the root request automatically resets and i've to redo procedure again
BUT after disabling zygisk the root request reset issue didn't happened. So i did add the "instabiz ,My jio" apps to test if it detects root or not , but it still detects root.
SO how do i make it work ?
akhil17kr said:
Sir, i tried using this app in zenfone max pro m1 with latest masgik v25 with zygisk enabled. So after giving super user request YES 2 times (it prompts for 2 prompts one after another) i opening settings and enabled "magisk hide" and did reboot device.
But after reboot the root request automatically resets and i've to redo procedure again
BUT after disabling zygisk the root request reset issue didn't happened. So i did add the "instabiz ,My jio" apps to test if it detects root or not , but it still detects root.
SO how do i make it work ?
Click to expand...
Click to collapse
after enable magiskhide
flash riru module
flash safetynetfix 2.1.3
go to denylist , add google services
reboot
add apps to denylist
pitelasssss said:
after enable magiskhide
flash riru module
flash safetynetfix 2.1.3
go to denylist , add google services
reboot
add apps to denylist
Click to expand...
Click to collapse
which riru module to flash ? also do i need to disable the zygisk in order to use this app as with zygisk enabled the root request resets.
akhil17kr said:
which riru module to flash ? also do i need to disable the zygisk in order to use this app as with zygisk enabled the root request resets.
Click to expand...
Click to collapse
if you want to use delta with magiskhide disable zygisk
https://github.com/RikkaApps/Riru/releases/download/v26.1.6/riru-v26.1.6.r527.cdcb9f34c6-release.zip
https://github.com/kdrag0n/safetynet-fix/releases/download/v2.1.3/safetynet-fix-v2.1.3.zip
work perfectly fine with Livin, but i can't open Jago app.
Magisk Hide enabled
safetynet-fix 2.1.3
Riru - MomoHider
Lord Sithek said:
(...) Then by a process of elimination I determined it was the HideMyApplist app itself which causes the Keytrade app to crash! (...)
Click to expand...
Click to collapse
OMG, that's it!! How stupid of me. I had reinstalled HideMyApplist but couldn't configure it as it needs LSPosed and forgot about it. After uninstalling, Keytrade immediately worked! Thank you!
Timmmmaaahh! said:
OMG, that's it!! How stupid of me. I had reinstalled HideMyApplist but couldn't configure it as it needs LSPosed and forgot about it. After uninstalling KeyTrade immediately worked! Thank you!
Click to expand...
Click to collapse
Haha, glad I could help!
LSPosed has released new Shamiko which fixed Found zygisk for latest Momo but the banking apps that won't run with zygisk enabled like Livin by Madiri still not open.
Releases · LSPosed/LSPosed.github.io
Contribute to LSPosed/LSPosed.github.io development by creating an account on GitHub.
github.com
razael25 said:
work perfectly fine with Livin, but i can't open Jago app.
Magisk Hide enabled
safetynet-fix 2.1.3
Riru - MomoHider
Click to expand...
Click to collapse
nvm, its worked now
Tried Magisk Delta and sure enough it did pass the Instapay app. Used magisk hide, randomize package name, riru, momohider, unshare, and safety net. Downside is even though I have safetynet module, still can't pass basic attestation and somehow I broke momo app. For the momo app, I should only have init.rc as the failed test 'cause somehow momo can't see device is custom ROM and unlocked bootloader. Weird.
Edit: Safetynet passed, I just forgot to add gms and gms unstable in denylist.
BigChungus321 said:
Tried Magisk Delta and sure enough it did pass the Instapay app. Used magisk hide, randomize package name, riru, momohider, unshare, and safety net. Downside is even though I have safetynet module, still can't pass basic attestation and somehow I broke momo app. For the momo app, I should only have init.rc as the failed test 'cause somehow momo can't see device is custom ROM and unlocked bootloader. Weird.
Click to expand...
Click to collapse
Hide google gms from magisk denylist ,
restore magisk app with original name ,
instapay you need Egypt location to fully load the app, use Vpn if you want to try
momo app will show environment is broken with magiskhide
Will Shamiko work with this custom Magisk? I know Shamiko needs Zygisk enabled. But it also needs "enforce denylist" disabled. However, this app doesn't have that option. So, does this app enforce denylist or does it not enforce it? Since there is no toggle for this setting.
AnonVendetta said:
Will Shamiko work with this custom Magisk? I know Shamiko needs Zygisk enabled. But it also needs "enforce denylist" disabled. However, this app doesn't have that option. So, does this app enforce denylist or does it not enforce it? Since there is no toggle for this setting.
Click to expand...
Click to collapse
MagiskHide toggle is DenyList toggle
MagiskHide will keep zygisk to be loaded for apps on denylist
Shamiko will work even it say it's not working. It say it is not working because it receives denylist_enabled flag sent by zygisk.
And.. If you use shamiko, why not use official magisk.
I think your banking app will work fine without shamiko if it doesn't detect zygisks. Shamiko cannot completely hide zygisk.
Hello everyone,
I'm trying to pass Momo test, but I cannot figure out how to remove all warnings on Momo.
I joined a screenshot of Momo.
Magisk modules:
-aurora services
-fdroid extension
-lsposed
-Magisk hide props config
-microg installer revived by nift4
-universal safety net fix
Zygisk activated
Magisk v25.1
Lsposed v1.8.3
(All apps are on denylist excepted LSPosed and termux, and denylist is activated.)
Thanks for your help.
Why not just ignore and remove Momo detection?
An app is still detecting root... so there's clearly an issue...
The real issue is "Found zygisk"
MicroCloud0110 said:
All apps are on denylist excepted LSPosed and termux, and denylist is activated.
Click to expand...
Click to collapse
Why do you add all apps into denylist? It is meanless and can break many modules
To hide Magisk to them.
It works on apps such as whatsapp, but an app is still detecting zygisk.
I removed the "found zygisk" warning by using shamiko.
But I still got the "running custom ROM" warning...
I have an LG V40 that had been rooted for a long time with an early Magisk - cannot quite recall the version right now. But yesterday I managed to update both Magisk and Manager to v 25.2 as I was looking for a way to hide root from the Play Store app as the damn thing seems to block even visibility (no less install) of some apps on this phone - I am sure because it is rooted as I can see/install the same apps on non-rooted devices.
The V40 has also had EdXposed and a number of its modules installed for a long time. It is on v 0.4.6.1 with Manager app v 4.5.7 and has all been working well enough.
After making it to Magisk 25.2, I enabled Zygisk because that was needed to set up a deny list onto which I hoped to put Play Store app and, maybe, Play Services in my effort to hide root. It seems that in doing this EdXposed got disabled and things got strange on the device until I was somehow able to get things back to before I enabled Zygisk. So now I have Magisk 25.2 - no Zygisk - with EdXposed 0.4.6.1 and all seems stable again.
But in my reading I get the distinct impression that I should be moving to Zygisk and that in doing so I will be breaking EdXposed so will need to transition to Lsposed. And this is where I have no real idea how to proceed. First off, I have no idea if the Xposed modules I am using ( Gravity Box [P] v 9.1.3, Untoaster Xposed v 1.2.8, XDowngrader v 1.1, Xposed Edge v 5.5.6, and Secure Settings v 1.3.6u2) will even work with Lsposed. Also, I have no idea of the steps I need to take - and the order in which to take them - to make the transition.
After yesterday's roller-coaster, I thought it best to ask for pointers before I try to move on - and quite possibly shoot myself in the foot again.
So your suggestions/tips/pointers are appreciated. I need some detail as this is clearly an area in which I am far from expert. Thanks!
Flash safety net fix latest zygisk version. Uninstall ed Xposed use lsposed zygisk magisk module. Set you deny list then turn force deny list toggle off and flash shamiko module. If you need more hiding for certain games use dev opts hide Xposed module and hide my applist xposed module
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
GitHub - LSPosed/LSPosed.github.io
Contribute to LSPosed/LSPosed.github.io development by creating an account on GitHub.
github.com
[XPosed]DevOptsHide (Hide deve - Apps on Google Play
Bypasses check of the apps which requires developer options disabled
play.google.com
Thanks. Before uninstalling EdXposed, must I disable or otherwise do anything with the Xposed modules I have installed? If just left there, will Lsposed "see" those modules? Or will I have to get them downloaded and installed again? It appears that the Xposed repo I have always used up until now is gone. And I am not clear yet if modules that worked well in EdXposed will do so in Lsposed.
Also, at what point should I engage Zygisk? Right now it is NOT enabled?
Thanks alot for all the help.
Well, I believe I managed to get through all of the changes, replaced Riru/EdXposed with Zygisk/Lsposed. I had to reconfigure Xposed modules but it seemed like my Xposed modules were pretty much working as expected under Lsposed as they did under Xposed. One exception was the Quick Tiles in Xposed Edge. The tiles are there, they work in that they toggle the states of things (BT, Mobile Data, etc) and show a toast message indicating the state change. But the tiles simply would not change their UI state as they did under EdXposed. Hmmmm.
Despite all of this and more - following directions found in several places - I still cannot seem to hide that the phone is rooted from Play Store. It simply will not show some apps as the result of my searches. Grrr!
So having taken a TWRP backup of the new situation for future consideration, I have gone back to a TWRP backup taken just before starting this entire trip. I am now back to Riru/EdXposed and all that was working before is working once again.
Cheers