yashsingh1/xdaforums huggingface dataset:
[Magisk] HippoMan:
Question about OverlayFS ...

I've read its docs, and they state that using it to set partitions to read-write may not work, depending on the device's kernel.

Is there any way we can determine, before attempting to install OverlayFS, whether our device's kernel would indeed support this switch-to-read-write capability?

I'm running Delta 26.3 on a Nothing 2 A13 OS (version 2.0.3 of their OS).
[Magisk] zgfg:
I don't know how could you determine in advance but I also don't know what prevents you to install the module and tesr

Not sure (it was months ago when ai tried on a phone where it did.not work) - module will tell you that installation failed

And you can simply test by copying (from MiXPlorer or from Terminal: cp, ls, rm) can you copy hosts file to doo and later remove it on /system/etc - few minutes all together (rebooting the phone after installing/uninstalling takes the longest)

It's all systemless, hence after uninstalling as you have never installed and tried
[Magisk] HippoMan:
Oh, well, I'll just give it a try, then.

Thank you!
[Magisk] onoakino:
I'm currently using Magisk Delta (26301), Adaway 6.1.1.

I'm getting an error regarding Adaway about not being able to "copy to /system..."

I have the "Systemless hosts (1.0 by Magisk)" magisk module installed and activated.

On Magisk > Settings, under Magisk, i tapped "Systemless hosts" and a toast notification appeared "added systemless host module".

On Magisk > Settings > Unmount Modules

I enabled the "Unmount modules". I then click on "Configure unmount" and added "Adaway" on the list. (Just like what a user did a couple of pages back).

I still can't get Adaway to work. I still get the same error.

PS: Adding adaway to the "configure unmount" list didn't help. Removing it from the list also didn't. I'm out of ideas.

Any suggestions?
[Magisk] pndwal:
You may remember I said this to you:

as part of recent Treble/Mainline Google 'enhancements'. 😛

So if you have a Super partition, requires A10+ (and can NOT use 'SAR' as defined by Google; A10+ uses 2SI which is 'SAR for Magisk purposes' since final rootdir is system, but not as far as Google is concerned since initial rootdir is rootfs... For Google, SAR means initial rootdir is system, but "as the Linux kernel can't interpret the super partition and so can't mount system itself, system is now mounted by first-stage init, which resides in the ramdisk" in 2SI devices), /system, /vendor, /product and any other sub-super partitions are necessarily locked as RO...

https://source.android.com/docs/core/ota/dynamic_partitions/implement#system-as-root-changes

Also, where dynamic partitioning is enabled the flag PRODUCT_USE_DYNAMIC_PARTITIONS := true is enabled in device.mk...

I'd be surprised if any stock ROMs this modern haven't implemented dynamic (super) partition scheme... Even old legacy ramdisk devices updated to 2SI (automatic with A10+) can be retrofitted with super partitions (PRODUCT_RETROFIT_DYNAMIC_PARTITIONS := true) and partitions moved to super thus became locked RO.

I believe that (most?, all?) custom ROMs still avoid this to keep RW, but I may be wrong...

Hope it helps... 🤠 PW
[Magisk] Stillhard:
You might need overlayfs from here
[Magisk] onoakino:
This is a magisk module, correct?

Flashed. Rebooted. Same error on Adaway. Are there any other extra steps to perform after flashing the module?

edit:

I edited mode.sh to

<b>export OVERLAY_MODE=1</b>

didn't help. It originally was set to "OVERLAY_MODE=0" but it didn't solve the issue. And before I even change the mode to 1, I tried to set the partition to r/w by executing

"su -mm -c magic_remount_rw"

using Terminal, but still no dice.

This module could help me. I just don't know how to use it. 😞

edit oct 31:

I managed to make it work. Downgraded to an older release of adblock. Grant it su permissions AND remove it from "Configure unmount" list. Updating the app and host files working now.
[Magisk] pndwal:
Actually, I missed (above) that you asked about switch to RW capability (which is likely not possible) but really meant just to enable systemless overlays... Please say which partitions you wanted...

Possibly issues will relate to the little drama that played out after this request:

Request for root directory partition support: odm (all), optics and prism (Samsung), my_* (OPPO/OnePlus), vendor_dlkm (Android 12+) #3338

initially addressed with:

Refactor magic mount by unsharing magiskd #6445

but this was partly reverted with:

Remove support of partitions w/o symlink in /system #6682

... Nb. The initial issue remains open and "Plan B: redesigning a new API" per:

https://github.com/topjohnwu/Magisk/issues/3338#issuecomment-1454031655

and comment linked there, remains pending also, depending if feelings haven't been too hurt:

https://github.com/topjohnwu/Magisk/issues/3338#issuecomment-1454409076

😬 PW
[Magisk] HippoMan:
On my device, I ideally would want full RW access to each and every location under /data and /system. And on my device, I realize that this would also involve the "super" partition.

I wrote that to simply answer your question with no hope of actually obtaining those RW capabilities, because now I'm aware that OverlayFS will almost certainly not offer all these capabilities in this manner.

And you have pretty much answered my basic question, which is how can I tell whether or not OverlayFS is likely to enable RW on those partitions on my device: I now am pretty sure that the answer is that it's easy to know that RW cannot be offered on my device in the ways I'm desiring, given my device's characteristics:

(1) Stock A13 ROM ... i.e., not a custom ROM

(2) Indeed uses the super-partition methodology

Again, my current device is a Nothing 2 running its stock OS 2.0.3 ROM (A13) with Magisk 26.3

Thank you for the references to this issues which might possibly relate.
[Magisk] pndwal:
If you only need to mount /system w/ overlayfs (data is RW of course anyway), I'm not sure why you think it won't work for you... Magisk modules do this all the time... Other 'obscure' partitions are the challenge...

overlayfs is of course an alternative to physically writing to a partition and doesn't add back RW capability, also OEMs also implement this... It has the advantage of not messing with /system or other partitions mounted this way, and Magisk's Magic Mount implementation using overlay.d folder was overhauled and improved recently in 26.0 and 26.1... 🙂 PW
[Magisk] HippoMan:
Oh, now I understand better.

Thank you for your further explanation.
[Magisk] onoakino:
I'm currently using Magisk Delta (26301), Android 11, MIUI 12 stock.

Everything passes, except for the things in the screenshots.

I have 3 questions:

1. How to properly hide LSposed modules from Applist Detector (v.2.4 by Nullptr)? Zygisk LSPosed is ver 1.9.2 and I'm using the parasitic mode to open LSPosed.

2. Can LSposed modules be hidden from Applist Detector? If so, how?

3. Applist detector by TSNG. detects "com.topjohnwu..." and other things even though I already uninstalled Magisk 23 after installing MG Delta. As for moe.shizuku, that's for the Storage Isolation app from the playstore, and I already uninstalled it, but it's still showing. Clearing the data/cache of the detector doesn't remove these detection. Any ideas why this would happen?
[Magisk] zgfg:
Please search for Hide My Applist thread, read OP post #1, follow the URL to GitHub Instructions

You can also find many post here about that HMA module
[Magisk] onoakino:
Thank you for your answer.

OK I should have been more explicit. I have installed HMA 3.2-410. I use it to hide my banking apps from detecting root, of course, not just HMA alone, but LSPosed too and the needed modules. One of the screenshots actually show the result of HMA "Detection Test" clearly showing the presence of my installed LSposed modules. So I know enough about HMA. Been using it for years. Been using it since Magisk 23.

But maybe there's something more that I need to know about it, or about Magisk Delta, when it comes to hiding xposed modules. Back when I was using Magisk 23, I use HMA to hide my apps and I never really bothered to use its "detection test". Way back then, for me, as long as HMA helped Magiskhide to make my banking app not complain about being rooted, it was all good.

Right now, using Magisk Delta 26301 + HMA + LSposed, all of my banking apps are working. But unlike before, I am now interested about why the xposed modules being used by LSPosed are being "seen" by the applist detector of HMA.

Can we really get a 100% passing grade on HMA's "Detection test" when our setup is Magisk Delta + LSPosed (parasitic mode) + HMA?

Or maybe we can't really hide xposed modules from these detectors?

Again, my phone passed all tests, except for xposed related tests. You may look at the attachments for comparison. 😊
[Magisk] zgfg:
If I recall, you asked how to hide LSPosed modules from AppList Detector - so the answer was (that's why I directed you to HMA), use HMA to hide LSPosed modules (incl. HMA itself) also from AppList Detector (as well as from Ruru and TBChecker)

Btw, I'm pretty sure that it's also described in the mentioned Instructions.

In fact, AppList detector was provided alongside the HMA as a testing tool, for practicing how to hide from banking apps - in this case imagine the Applist detector as your 'banking' app and hide also from that 'banking' app
[Magisk] iruiz2:
You have to hide your modules from the detection apps using HMA. I have it configured like this and it works (using Delta + lsposed + HMA).
[Magisk] onoakino:
This. I rechecked and found that both of my detectors I have "Enabled hide" turned on my HMA but I was not using my blacklist template for them. Applying my template for these two app detectors did the trick.

Thanks!
[Magisk] zgfg:
You can also use Whitelist mode in HMA, then you don't need Blacklist template - screenshot
[Magisk] iruiz2:
So you just hide everything but system apps using this method, right?
[Magisk] zgfg:
Yes
[Magisk] fuadhdmini:
Hi. Is there any update. Apparently magisk delta won't work with Pixel 8/pro
[Magisk] HippoMan:
Please forgive me if this has been answered before. I already did searches here, but I didn't find anything concerning my question which seems like it could pertain to the latest version of Delta. If I overlooked anything, I apologize.

I'm planning to upgrade my OS, and this might result in my having to do a factory reset, in which case I would have to re-install Magisk.

Is there any way to back up and restore the list of root-enabled apps in the "Configure mount" list in Delta 26301?

I have literally dozens of root-enabled apps in this list, and it will take a lot of time for me to re-enter each of them into the list. And I can't remember a list this long, and it's prohibitively onerous to even type up a list of all of these root-enabled apps by hand.

I'm running A13 on a Nothing 2 device.

Thank you in advance for any ideas and suggestions.

PS: Is there perhaps a directory somewhere that gets created and which has an entry that corresponds to each item in the Conflgure Mount list? Or is there perhaps a file or sqlite table somewhere which contains a list of these items? Or is there some activity which could be invoked which lists these items?
[Magisk] ithehappy:
With latest version of Delta do apps like imobile, hdfc, sbi etc work, and other upi/banking apps as well? Query for my Indian friends
[Magisk] LegendaryCheerio:
this new update doesnt work with my bank.
[Magisk] HippoMan:
I'm trying to get onto the Telegram discussion group for Magisk Delta, but I am not finding any group which shows discussions. All I found in TG are some Magisk-Delta-related groups where either (1) announcments of Magisk Delta releases are posted with no discussion allowed, or (2) some other groups which ask for a Captcha to be completed, but without presenting any Captcha and with no discussions shown.

I always UNMUTE, but I still see no discussions.

If anyone knows how to get into a TG group where Magisk Delta can actually be discussed, could you let me know? Private message is fine.

Thank you very much in advance.

Never mind. I found how to get into the TG group. We have to jump through a bunch of hoops involving going to a "pennbookcenter.com" web site and clicking on a few things in order to get a code that needs to be entered on yet another web site. Then, access is granted to the TG Magisk Delta group.

Well, at least we can get into this TG discussion group for Magisk Delta, unlike Magisk Alpha which is pretty much closed for any discussion.
[Magisk] zgfg:
The group has been renamed in the past and now is called Blast from the silent

There is no (more) invitation link

I think that developer is no more active, group is mainly ran by a bot, but it has almost 4k members

You could try this link (to one of the posts), if you could then subscribe:

t.me/c/1740179387/106044
[Magisk] HippoMan:
First of all, I kept typing Configure "mount" above. That's incorrect, and it should be Configure "unmount".

And I got an answer for this question in the TG discussion forum for Magisk Delta.

I was told that the /data/adb/magisk.db sqllite database holds all the relevant data for Magisk Delta. When I investigated that database, it turns out that it contains a table called "hidelist" which holds the exact contents of the Configure unmount list.

So, I can at least get a copy of that list by querying that table.

This raises another question:

If I back up that database, then reinitialize Magisk Delta 26301, and then load that "hidelist" table with the contents of the backed up version of that table, will that properly initialize my Configure Unmount list with all the apps that were previously managed within that list?

If so, this would be a very convenient way to do backups and restores of the Configure Unmount list.

Any thoughts or suggestions?
[Magisk] HippoMan:
Actually, after I jumped through all those hoops that I mentioned, I got into the "Blast from the silent" group and discovered that it contains sub-groups. One of them is called "Magisk Chat", and it indeed is active with people chatting about the usage of Magisk Delta.

That's where I got the info about the /data/adb/magisk.db that I mentioned above.
[Magisk] sga999:
I wonder if you can give more details about how you got to that Delta group or subgroup. I went to pennbookcenter.com as you suggested. But I didn't see anything there related to telegram. Googling "Blast from the silent" doesn't result in anything for me, but I didn't really expect that to work. I hope you can lead me through it.
[Magisk] HippoMan:
I'll post the steps tomorrow when I have more time.

It required a complicated mass of nonsense, some of whose details I don't remember clearly, because I had to go back and forth and retry a few things before I got it right. I'll have to stumble through it all again in order to recreate the proper sequence of steps.

But I'm glad to do so. I'll try to have it all for you by this time tomorrow.
[Magisk] 2takta11:
Hello friends.

There is an interesting question.

Magisk Delta 26105 (D), miui 12, android 10, Pocophone F1.

I have 3 banking applications installed. Spush-Tan, HBL mobile, Citibank and TBChecker

Option 1:

Magisk with a random package name.

Spush-Tan, HBL mobile detect root, TBChecker is completely green, but sees the renamed Magisk.

Citibank does not detect root.

Option 2:

Restored Magisk application.

Spush-Tan, HBL mobile DO NOT detect root. TBChecker is completely green

Citibank detects root.

I can conclude that Spush-Tan, HBL mobile and TBChecker see the renamed Magisk, and Citibank sees the name of the application.

How can I get out of this vicious circle without Lsposed and HMA?
[Magisk] malcolmy:
Thanks I'll be waiting for you too.
[Magisk] HippoMan:
I'm very sorry for the delay. I probably won't be able to get to this now until tomorrow or the next day. But I'll definitely post the info.
[Magisk] ayobarme:
Hello

Does this method still work. I tried it and it's not working for my starling bank app. I also can't get Google wallet to work.

Thanks.

Pixel 8Pro on magisk delta
[Magisk] westruk:
new improved zygisk and selinux time modification detection
[Magisk] ayobarme:
Thanks.

Please can you help point to where I can get this, I've been searching.

Thanks
[Magisk] giociampa:
I have two additional entries in my block list for Starling:

firebaseinstallations.googleapis.com

firebaseremoteconfig.googleapis.com

However, since those URLs were discovered (and did work) Starling has made further updates that check whether Zygisk is enabled, so the app goes into its 14-day countdown (and also refuses to acknowledge payment requests) if detected.

If you have a Rom that passes SafetyNet out of the box (so no need for USNF or PIFix) then you can run Delta with Zygisk off (and the Unmount Modules switches on, to hide Magisk) then you can get both Starling and Wallet to work simultaneously - otherwise it's a case of one or the other it seems 😕

There is a thread here about Starling if that helps...

Banking app (Starling) detecting Magisk

A banking app I've been using for years has always worked after putting it on the Deny List. I updated it recently and it now won't work with Magisk installed regardless of what I do. As soon as I patch the boot image with Magisk it complains...

xdaforums.com
[Magisk] Nekromantik:
Yes at the moment only way for Google wallet and Starling same time is custom ROM with fix included and then use delta without zygisk.
[Magisk] xdauserxyz:
Does it mean that with Magisk Delta, one must not use zygisk and instead use Riru. Isn't it that Riru will move to Zygisk from v14 of Magisk ?

Can you also pls advise how to use XprivacyLua with Magisk Delta ? Do I need to get Riru, then LSPosed-Riru and then XPrivacyLua ?
[Magisk] zgfg:
Absolutely not. You can use Zygisk with Delta, no need for Riru (although you could probably still use Riru instead of Zygisk, but you may have problems then since Riru is deprecated)

Anyway, the message you are quoting was from June 2022 - since then, Delta has changed upside down.

Instead, please study the recent posts in this thread, relevant to Delta v26 (latest Delta Canary is v26301)
[Magisk] spicediablo:
Hi,

Anybody using standard chartered singapore? As of today, it has been detecting root even with zygisk disabled. Any method to workaround this detection?

Thanks.
[Magisk] iruiz2:
New message on the Delta telegram channel
[Magisk] spicediablo:
Can't wait to update and see if it will better hide Zygisk
[Magisk] samtruman:
Hi to all, i have problem with google wallet, it gives me error about device security requirements, I have 26301 canary delta installed. I tried both with zygisk enabled and disabled.

I run play integrity api check 1.1 and meet only basic integrity, also yasnac gives me cts profile match fail.

Device oneplus 11 android 13

I really don't know what to do
[Magisk] Lord Sithek:
Nothing at the moment, Google made another patch. Waiting for a next version of PlayIntegrity Fix module
[Magisk] spicediablo:
v13 of play integrity is available. Perhaps give that a try?
[Magisk] HippoMan:
Could someone point me to a description of the best way to safely unroot when using Magisk Delta 26301 under Android 13?

I searched and didn't find anything here in this particular thread concerning the mechanics of unrooting Magisk Delta.

I know this is described in other threads for other Magisk versions, but I'd like to make sure that I know the best way to unroot specifically for Magisk Delta 26301 for Android 13.

Thank you vrey much in advance.
[Magisk] xcl1pse:
Same like uninstall magisk?

https://topjohnwu.github.io/Magisk/install.html#uninstallation
[Magisk] HippoMan:
Thank you!

But I stll have questions.

I orginally installed Magisk Delta 26.1 in the standard way, but then I put the following json file URL reference into my Custom Update Channel field (it's for 26301) ...

https://github.com/HuskyDG/magisk-files/releases/download/0fe46c5a-delta/canary.json

I then updated from there in the standard way to Delta 26301.

Now, I know one recommended way to uninstall Magisk is to get the 26301 apk file ...

https://github.com/HuskyDG/magisk-files/releases/download/0fe46c5a-delta/app-release.apk

... and copy it to uninstall.zip, and then flash that in the bootloader.

But will that work in my case, given that I didn't use that particular APK to install 26301, but rather, did it via the Custom Update Channel?

Thank you for any help and clarification.
[Magisk] xcl1pse:
Make sure the version installed and uninstaller.zip is same..
[Magisk] HippoMan:
OK, I think I understand. So even though I installed Delta 26301 via the Custom Module Channel update, I can still rename the Delta 26301 APK file to "uninstall.zip", and it should work to uninstall Delta when I flash it, as long as I am careful to choose the correct Delta 26301 APK file for the 26301 version that I am currently using.

Thank you very much.
[Magisk] solar666:
You can dirty flash the rom as well und delete all magisk files and folders in /data/adb/. to be clean again.

There is a quite good XDA post somewhere, think in alpha thread.
[Magisk] HippoMan:
I've been looking for such a post or tutorial, but I couldn't find it so far.

I'll check the Alpha thread again.

Thank you.
[Magisk] zgfg:
You have also Uninstall Magisk option at the bottom of the Magisk app. Make sure you accept all uninstalling that it asks/offers
[Magisk] HippoMan:
OMG! It was staring me in the face in orange text, and I missed it.

I'll definitely do it that way.

Thank you!
[Magisk] zgfg:
Delta actually installs magisk folder (with magisk executable, magiskboot, magiskinit, etc) to /data/unencrypted folder and just links /data/adb/magisk to /data/unencrypted/MAGISKBIN- see attached screenshots

Moreover, LSPosed modules also put their files elsewhere, and out of /data/adb

Hence if you just dirty flash your ROM and manually delete /data/adb, you will still have dirt leftovers here and there

Much better to properly uninstall Magisk. Btw, I'd do that by rebooting couple of times:

First, I would uninstall LSPosed modules but keep LSPosed itself and reboot.

Then I would uninstall Magisk modules and reboot (on rebooting, Magisk will execute uninstall.sh script for those modules that provided their uninstall scripts, and those scripts will usually properly xlean all leftover files installed outside of /data/adb/modules/<module>

Finally, I would click to the big red Uninstall Magisk button in the Magisk app and will accept all cleanings and restoring it asks/offers
[Magisk] HippoMan:
Thank you! This is exactly what I need to know!
[Magisk] solar666:
Wasn't aware of that and thanks for the heads up in that.

Didn't thought that delta is that different on that specifically compared to original magisk and alpha stream.

Much appreciated 👍
[Magisk] kullurumanoj:
Can someone help me in hiding Microsoft teams detecting root? Magisk with shamiko helps in hiding it but magisk delta doesn't work for me. I had to go back to the original magisk due to this issue.
[Magisk] spicediablo:
Magisk delta+shamiko works for me. Try uninstall and reinstall shamiko 0.7.3
[Magisk] kullurumanoj:
Mine is getting disabled automatically after reboot
[Magisk] cognitivedissonance:
Anyone know whether the issues with 26301 mentioned by zgfg have been corrected? I'm really thinking I need to update now that stuff is starting to break again (Google Wallet and bank apps.) Just did a quick update and it looks like I need to ditch USNF module in favor of Play Integrity Fix Module, is that correct?

Prior to this, Magisk Delta 25210, USNF 2.3.1 MOD 3.0, Zygisk on, MagiskHide on, Enforce SuList off, and then the proper things select in MagiskHide (Google Wallet, GPay, and banking apps) had been working like a charm.
[Magisk] Nekromantik:
anyone now not being able to use MBNA app in the UK as its detecting root even with Zygisk off?
[Magisk] westruk:
Working fine on kernelsu with zygisk next
[Magisk] mGforCe:
Yes, most of Indian apps works with Delta, along with Lsposed + HMA
[Magisk] Nekromantik:
Requires login before it gives you message to say root detected