yashsingh1/xdaforums huggingface dataset:
[Magisk] shadowstep:
Thanks for testing! Good to know (for future reference) that it also checks for VPN.

That was it! Thanks a lot! I was using the IAmNotADeveloper module to hide the fact that Developer Options were enabled, which was working fine until this new update. Removing that module completely (I was only using it for iMobile) fixed the issue...

Spoiler content hidden.

There was one more issue though - the app was now complaining about my debugging settings; it basically wanted me to disable USB debugging, but I didn't want to do that. So I found a module by @huskydg which fixed that detection too! So now everything's fine.

Thanks for testing! I may not post that often here, but I've been following this and other related threads for a long, long time now. Looking forward to NB Zygisk as well as KernelSU becoming more mature!

Thanks for the suggestion, but that didn't help. I've messed with that toggle earlier, and it led to a few apps crashing/not working, so I just reverted it and called it a day (as I've mentioned above).

Thanks! I've already fixed the issue now. :)
[Magisk] Lord Sithek:
May I ask which module is that?
[Magisk] noidtrue:
well, I also encounter the USB debugging problem while playing PUBG new state. The game asks me to disable USB debug, which I have always turned off. any thoughts?
[Magisk] genesis89:
Hi, I'm new to Delta (previously on Alpha) and I'm having a pretty major issue with Touch n Go app and Google apps. I can't get both to work at the same time. If I wanna use Google apps, I'll have to disable 'Enforce SuList' but if I wanna use the Touch n Go app, I'll have to do the opposite. My phone is Poco F3 and the I'm currently on the latest PixelOS.

Edit: Never mind. Both are working fine now. Not exactly sure what I did.
[Magisk] amn1987:
Maybe the Developer Options needs to be turned off completely.
[Magisk] shadowstep:
Attached with the post. :)
[Magisk] Lord Sithek:
thank you

Is it available anywhere in public?
[Magisk] amn1987:
UPI Lite can't be setup in my Magisk rooted device although UPI itself works fine. Both Phonepe and Paytm display that UPI Lite is blocked in this device due to regulatory restrictions. I gave a try with HMA as well but it made no difference. No such issue in case of another device rooted with KSU.
[Magisk] mGforCe:
Welcome.

Can you share the module name which hides USB debugging pls? Thanks.

Edit: Got it
[Magisk] shadowstep:
I found it in Magisk Delta's TG Discussion Group.

I don't use UPI Lite/have never tried using UPI Lite, so I can't comment. But it could be because of some other restriction entirely, and not root (since UPI itself works fine). Or maybe the app is requiring Strong Integrity for UPI Lite (although it's very unlikely; I don't think an app will lock certain features behind Strong Integrity while other features continue to work without it - if that's even technically possible, that is).

(y)
[Magisk] mGforCe:
Anyone able to get Bhim working with Zygisk & Lsposed on?

For me, I tried following:

HMA + Shamiko, Bhim unselected from all Lsposed modules >> failed

HMA + Shamiko >> failed

HMA -Shamiko >> failed

Surprising that SBI Yono works but Bhim failing :P :(
[Magisk] zgfg:
Something is fishy here. I have two Xuaomi phones with Xiaomi.eu ROMs:

Newer, with A13 and Magisk Canary 26301 and older with A11 and Delta 26301(with Unmount modules by default).

Shamiko only on the newer phone with Canary

Zygisk-LSposed on both, as well as HMA and Ruru. And four or five other LSPosed modules on each

On the older phone I even run LSPosed app (not its parasitic shortcut)

On both phones, Ruru feels ok. It reports only Accessibility (I need for AA)), unlocked Bootloader and Developer Options. Ruru does not detect HMA or any other LSPosed module

---

BUUUT:

Last week I was experimenting with Vold isolation in HMA on my newer phone and at some point I realized that Ruru started to detect HMA

I lost the whole evening, trying all possible combinations that came to my mind (although I was pretty sure that I knew how I had it previously when Ruru didn't report HMA; I also tried the other combination, exactly like on my older phone where Ruru also did not detect HMA) but no avail

Eventually, I uninstalled HMA, installed the older v3.1.1 (still no avail), then updated back to v3.2, set again one of the combinations that an hour ago did not work - and Ruru suddenly stopped reporting HMA

---

Couple of days later I similarly played with Magisk, LSPosed and HMA on my older phone, and at one point Ruru also started to report HMA (together with the LSPosed app)

Again I went through all combinations, I was deleting Data and Cache for Ruru in between, no success

I tried to recall how I solved few nights ago on the other phone. I still don't believe that it was the key, but I had no other option anymore. So I also reverted back to HMA v3.1.1 and then updated to v3.2. Not sure at which point I enabled Vold isolation (before or upon the update), and I got it - Ruru no more reporting HMA (nor LSPosed)

---

So on both phones I have now HMA v3.2 with Vold isolation enabled. On both Ruru v1.1

On the older phone I have Work mode Whitelist + Exclude System apps in HMA for Ruru

On the newer phone, Work mode Blacklist and a template with LSPosed app, Ruru and other LSPosed modules enlisted

I don't want to experiment more (it still works on both phones) but I think those differences are not important. Probably I could put the opposite way (Blacklist work mode with a template to the older phone with Delta, Whitelist + Exclude System apps to the newer with TJW Canary) and they would also work

But when they didn't work - they didn't. I tried then one way and the other, one day on one phone, the other day on the other phone and then no combination worked

I still cannot believe that the trick was in downgrading and upgrading HMA
[Magisk] ewong3:
this is becoming so unpredictable and trial and error an exercise... will ksu / nb-z be so drastically different to render groping in dark like this a past?
[Magisk] HippoMan:
I agree about how crazy things have gotten.

And please forgive my ignorance: what is "nb-z"?
[Magisk] ewong3:
saw it here:

https://xdaforums.com/t/discussion-...third-party-magisk-fork.4460555/post-89055673

but not sure what it is... new as i am to the whole magisk world...
[Magisk] mGforCe:
Indeed, to0 much of trial and error.

Apps which were detecting bootloader unlock etc (and hence hidden with Bootloader Spoofer etc modules) are now working only if un-selected from these modules.

So clearly they stopped relying on bootloader status and moved to something else - zygisk / lsposed etc.

Also while NB-Z is touted to be the next thing, not sure if it will cover recent detections brought in.

For my case Magisk D with Unmount and Magisk A with Shamiko (latest across both magisk forks) giving same benefits and issues
[Magisk] mGforCe:
Continuing my experiments, disabled Lsposed Zygisk in Magisk Alpha and Bhim worked.

So it is something to do with Lsposed or Lsposed Modules.
[Magisk] kevinco1:
Strange, doesn't show up in my module list
[Magisk] shadowstep:
Because it's not a traditional module. It unpacks your boot image, does modification in one of the boot scripts, repacks the boot image and flashes it to the current slot. That's why it won't show up in your modules list.
[Magisk] kevinco1:
Thanks for the info, as long as it's working then I'm satisfied.

One other thing, will this effect any custom kernels I've flashed since those patch boot as well?
[Magisk] HippoMan:
Please forgive me if I missed something in this thread which pertains to my following question:

What do I put into the "Configure unmount" list on Delta 26301 which will allow me to go into root via "su -" from inside of an adb shell session? ... or is there a different way to enable this capability in Delta 26301?

Right now, when I do "su -" in an adb shell session, I get a "Permission denied" error. I know that I'm properly rooted, because apps that request root that I put into the "Configure unmount" list are all sucessfully obtaining root.

Also note that "Rooted debugging" is indeed enabled in Developer settings.
[Magisk] asripath:
https://xdaforums.com/t/discussion-...third-party-magisk-fork.4460555/post-89051665

Also

You would need to enable adb root in developer options

Edit

Does com.android.shell has root permissions?
[Magisk] Cristiano Lira:
What app and modules do I need to use to hide Magisk/custom rom nowadays? I was running Magisk 25 with the Magiskhide module but an app that I use started saying that I have a modified system and also I can't update it on play store - I get something like "your device is no more supported". I just use Magisk for JamesDSP and Kernel Adiutor, don't use Lsposed or anything else.
[Magisk] HippoMan:
I tried both Whitelist mode and Blacklist mode (with opposite sets of apps), and "su -" doesn't work in either case in "adb shell".

Also, when I disable "Umount modules" and run the old-fashioned way, "su -" still doesn't work in "adb shell".

Did you read the following statement in the comment of mine that you are replying to? ...
[Magisk] HippoMan:
Oh, I figured out how to fix this!

In old-fashioned mode (i.e., without "Unmount modules"), I noticed that [Shared UID] Shell was in the Superuser list, but it was disabled. Once I enabled [Shared UID] Shell for Superuser, "su -" started working in "adb shell".
[Magisk] Cristiano Lira:
Where is the hide list?
[Magisk] zgfg:
That's my whole point why there are two lists for Whitelist mode

You put shell to one but forgot to enable in the other

The same is for all other root apps, like Terminal Emulator, MiXPlorer, etc - you must make sure to have them in both lists - hence why simply the Whitelist mode would not automatically use SuperUser list, it would be more practical, intuitive and friendly
[Magisk] HippoMan:
I understand about the two lists.

But I didn't know about the [Shared UID] Shell app (or service, or whatever it is), and I didn't know that this is the app/service which affects whether or not things like "su -" work in "adb shell". So I didn't know to enable or disable it.

I only discovered [Shared UID] Shell when investigating this problem and wondered if it might be the cause of "su -" not working.

My original question here (although I probably didn't ask it clearly enough) was to ask which app/service controls "su -" in adb shell, so I can enable it for root if it's disabled.
[Magisk] shadowstep:
Shouldn't have an impact on your custom kernel. It uses the existing boot image as base, so if you're using a custom kernel, it'll use that boot image as base, make the insertions, repack and flash.
[Magisk] zgfg:
I still don't understand the need for two lists, IMO Delta may use for Unmount Modules by Default the existing SuperUser list

Regarding ADB shell su - on the official Magisk it used to be enough to enable ADB for root in the Settings - as on the screenshot

I didn't test on Delta, I rarely use adb, I always tend to use Terminal emulator
[Magisk] HippoMan:
It's much easier for me to type on my computer keyboard than on the much smaller device keyboard, and that's why I like "adb shell".

As for the two lists, I tend to get confused as to which combination of settings is for "Whitelist" mode, and which is for "Blacklist" mode.

It might be nice in a future Delta version to actually put the words "Whitelist" and "Blacklist" in the Settings, to help us remember this.
[Magisk] Prof. Yaffle:
I've come a bit unstuck when enabling Enforce SUList. I've rebooted and the UI doesn't load. I've tried the ADB command to disable SUList but no joy. I can get back in to my phone by dirty flashing my ROM but every time I try and flash Delta again it must be picking the SUList setting up as it crashes the UI again. I can get root back by flashing standard Magisk so I'm just wondering if there's anything I can do to get rid of the SUList setting before flashing Delta again please?

Edit.

I think I've figured it out. I just renamed /data/adb/magisk.db and rebooted.
[Magisk] asripath:
As mentioned

Edit

Does com.android.shell has root permissions?
[Magisk] HippoMan:
Yes, but I didn't know that [Shared UID] Shell is the name of the service that allows "su -" to work in ADB mode. Did you know that?

My original question here was asking about how to control "su -" in ADB. I already understood about Blacklist, Whitelist, etc. I was trying to find out if there is an app or service which controls that, which I could enable in Magisk. I only stumbled upon the fact that [Shared UID] Shell is the name of the service I was looking for.

And it turns out that in older versions of Magisk, the Magisk code enabled root for ADB automatically, without any service such as [Shared UID] Shell needed, but that starting somewhere in the 26.x series of Delta, the Magisk code stopped setting ADB to root by default, and we then had to start using Shared UID] Shell for that purpose . Did you know that?

Again, my question had to do with these issues, not with the mechanics of Blacklist. Whitelist, etc.
[Magisk] zgfg:
Root was not given by default to adb, it was controlled by Magisk app Settings/Superuser/Superuser access- screenshot (from Settings in Magisk Delta!) below and yesterday in the post #1429

Btw, I remember how it that to be turned on (Superuser access to Apps and ADB) whenever you first time install Magisk, if you wanted to use adb shell su

I tested yesterday and on TJW 26301 Canary that option (Superuser access to Apps and ADB) solely controls if ADB has root privileges or not

However, on Magisk Delta 26301 you have to have both: that option in the Settings and [SharedUID] Shell in the SuperUser list.

Leave the [SharedUID] Shelll in the SuperUser list and change SuperUser access to Apps only in the Settings, adb shell su will no more work.

Or vice versa, only with that option in the Settings, without [SharedUID] Shell in the SuperUser list, adb shell su also won't work

Plus, in the Whitelist mode (Unmount modules by default), [SharedUID] Shell must also be in the Configure Mount list.

In fact, you can not remove it from the Configure Mount list - remove, reboot and [SharedUID] Shell will be automatically back in the Configure Mount list (the same for System UI service)

(In fact, in that whitelist model every root app must be both in SuperUser list and in the Configure Mount list - hence the second list must be filled as a duplicate of the first - and IMO, Delta app could either by itself copy the whole SuperUser list to Configure Mount list, or even work without Configure Mount list, by automatically mounting for all apps that are listed in the SuperUser list)
[Magisk] asripath:
Congratulations on your self discovery...

What is the package name of the service/app
[Magisk] HippoMan:
Yes, I now remember that. Not "automatic", but we didn't have to somehow know about something undocumented called [Shared UID] Shell in order to get ADB root to work. We used to be clearly presented with an explicit setting, and Magisk itself managed that behavior depending upon that setting.

Now, all we can do is stumble upon that [Shared UID] Shell service and have to guess what its purpose is.
[Magisk] HippoMan:
Yes, and we need to understand what the purpose of [Shared UID] Shell is in the first place before we can know whether to enable or disable it in both lists. Anyone who reads this current discussion will now know about this, but it would be nice if that service was documented somewhere.

And I'm optimistic that a (hopefully not too distant) future Delta release will provide such documentation and will offer more capabilities to help keep the two lists in sync for all apps and services.
[Magisk] HippoMan:
That [Shared UID] Shell service is not offered as an app, and it isn't even mentioned anywhere in the device Settings. And I couldn't find any mention of this in a network search.

Therefore, I can't easily find any package name that's associated with it. And anyway, that package name isn't needed when we enable or disable that service in the Delta lists.
[Magisk] zgfg:
com.android.shell is a system preinstalled app

:/ # pm list packages -f | grep shell
package:/system/priv-app/Shell/Shell.apk=com.android.shell
[Magisk] iamthechickengod:
I upgraded to 26301 canary while still having Magisk Delta hidden.

I updated the boot with direct install and install to inactive slot then rebooted.

It seems the hidden Magisk app lost root so I uninstalled the hidden Magisk and reinstalled the original Magisk Delta apk then rebooted.

Now, I am trying to hide it and everytime I do, root gets lost. This is my first time working with Delta so things may have deviated from the official Magisk.

If it matters, I am using this on an NP1 with NothingOS 2.0.2 hotfix.
[Magisk] therealashish:
Happening the same at my end too.

Using Nothing phone 2.
[Magisk] iamthechickengod:
I probably screwed up a sequence. Pretty sure I had this problem before but it's been so long I may have forgotten how to fix it. Unsure if I should uninstall completely and redo the root process.
[Magisk] spicediablo:
Hi, just updated to latest canary(26301-8775765) but whenever I try to hide magisk app, i get prompted with root lost and need to reinstall magisk app again. Basically, same problem as @iamthechickengod and @therealashish Any idea what is causing this?

Update:complete uninstall and install again but problem is still there, unable to hide my magisk app now...anybody can advise?
[Magisk] fenrir_ac:
Last time unmount method works for me (no problem with tng + hlb connect + zygisk) but aosp mods and systemless lawnchair broke it totally and I couldnt find other way round. For now I just use kernelsu and everything seems to work with no issue. Kernelsu however is kernel dependent. So I really hope someday everything can be put together with magisk unmount.
[Magisk] iamthechickengod:
No but the problem persists after completely uninstalling canary and trying debug which is expected.
[Magisk] spicediablo:
After trying a few more times, now even after flashing the patched image, my magisk manager is still showing magisk as not installed as shown below....attached my magisk log here to see if it helps to troubleshoot the error.
[Magisk] iamthechickengod:
Try rebooting.
[Magisk] spicediablo:
Rebooting doesn't help, still magisk is not detected... During the troubleshooting for hiding magisk app, i also deleted my second space as I thought it was causing issue but now I don't dare to move further as I can't even install magisk by flashing using fastboot now. Hope some experts here can give me some pointers...Should have unhide before attempting to update....
[Magisk] iamthechickengod:
Agreed. It ought to be included in a guide.
[Magisk] spicediablo:
Update doesn't happen all the time so I tend to forget. It would be nice if app can be restored automatically before script for updating runs.

Update: Found magisk was installed but somehow it automatically hides and rename as 'settings'. Hiding magisk app with stable build is fine, only the delta(canary) version is having issue hiding. Perhaps I should try with an older version of canary....

@iamthechickengod @therealashish , here's what I did. I fallback to the old magisk delta manager(0fe46c5a version)>when the prompt additional setup requires, press cancel>proceed to patch the boot image and fastboot flash>if additional setup requires, again press cancel> then hide the magisk app, there won't be any error.

I found out that the moment you agree to additional setup, the hiding mechanism will produce error. I am not sure of the significance of the additional setup...

After making sure no error, i unhide the magisk app and install the update to the latest version and try to hide magisk app, there were 2 superuser prompts for the hidden magisk app and when I grant access, the same "magisk app needs to restore error" came up again... Is this something to do with updated app with superuser requirements?
[Magisk] zgfg:
I see on TG channel that many have reported same/similar problem for the latest 8775765-Delta and they returned to the previous Delta version
[Magisk] spicediablo:
Thanks for confirming that error. I am currently on older version. Had to restore the modules after countless installs/uninstalls. Hopefully, a fix will be out soon.
[Magisk] spicediablo:
With the latest RHB app, even creating 2nd space will not work. Anybody has any workaround on this?
[Magisk] m0han:
Can't see how magisk can

automatically

hide and rename as 'settings'. AFAICS, this step requires a bit of deliberate

user action

. BTW, do you guys really have to 'hide' Magisk app? It has a different package name 'io.github.huskydg.magisk'. That apart, installing the debug version of the latest update would've helped get the requisite info/details/logs for @huskydg to check and fix the issue.
[Magisk] spicediablo:
I'm not sure how but I usually don't rename it as 'settings'. I forgot to unhide before updating so i'm not sure if it was caused by that...
[Magisk] HippoMan:
"Settings" is the standard name which is offered by Magisk when going through the hiding procedure. Just clicking OK when doing the hiding will accept that "Settings" name, although that name can optionally be changed before clicking OK, if desired.
[Magisk] vudungcom:
Hello,

I need your help,, i can not hide magisk from applist detector, it found lsposed installed on device then i can not use banking app

https://play.google.com/store/apps/details?id=vn.com.techcombank.bb.app&hl=en&gl=US

Could you giave it a try. Thanks.
[Magisk] iamthechickengod:
How do you do a downgrade? Do you need to uninstall the problematic one then reinstall or can you just install over it?
[Magisk] amn1987:
I just freeze the Magisk app and Applist Detector doesn't complain anymore. Not that it prevents a very few apps from still detecting root. I have uninstalled LSPosed altogether as well which helped in case of a few other apps. HMA and modules to hide Dev Options were problematic. Some apps only run in Work Profile(Island). I have not extended root to Island.
[Magisk] zgfg:
I didn't do the downgrade - I didn't even update to this last Delta

But I always keep my last patched boot.img and then I install the older Magidk app and flash my old patched boot.img
[Magisk] spicediablo:
For me, I just download the older version apk from github and use it to patch the boot.img, then fastboot flash it
[Magisk] vudungcom:
but i need to use Lsposed frequently, freeze them cause other issue, i have to freeze and unfreeze many time.
[Magisk] spicediablo:
Hi,

My latest configuration as below:

Magisk delta canary version 0fe46c5a, app hidden

All banking apps and HMA added to unmount list

Zygisk enabled

HMA version 3.2 hidden all banking apps

HLB connect app version 1.1.52 and TouchnGo version 1.8.7 are detecting root. Disabling zygisk also doesn't help. Anybody has any configuration that works with them? Applist detector screenshot attached for your reference.

For HLB connect even disabling magisk and magisk in core mode doesn't help. I tried installing bootloader spoofer but it doesn't help as well. Root is still being detected.

Much appreciated for your inputs. Thank you.
[Magisk] amn1987:
I tested and both apps didn't complain about root. LSPosed is disabled and I never enable Zygisk. I have disabled Developer Options as well. Magisk app didn't need to be frozen.
[Magisk] spicediablo:
Isn't it when you disabled Zygisk then lsposed will not work? Lsposed will only work with Zygisk enabled, right?

I tried disabling zygisk which also suspended my lsposed. No luck still. I shared my unmount list here to see if there are any issues with them.
[Magisk] amn1987:
I was using Riru LSPosed. I ditched Zygisk after switching to MD as Shamiko wasn't able to hide it from many apps.

P.S. Kernel SU isn't available for your device assuming it is the Poco F2 Pro?

Edit: I had to restore a TWRP backup from August so MD is no longer on the latest Canary and MagiskHide instead of Unmount Modules but I don't think it makes any difference. BTW uninstall HMA and check. Also any modules to hide Dev. Options if any.
[Magisk] spicediablo:
Yes my device is Poco F2 Pro. Can I confirm that Riru LSPosed will support HMA as well?