yashsingh1/xdaforums huggingface dataset:
[Magisk] creezalird:
Just sharing my current set up with new rom PixelOS on Pixel 7

- magisk delta 26.3

- zygisk enabled

- youtube/music revanced/pixelify submodules

- Unmount options ticked on both

- Under mount list, only configured app that requires root such as Swift Backup

- safetynet passed basic by default (PixelOS)

TnG, MAE work

HLB work (only version 1.1.51, newer like 52 will not work for now)

Google Wallet works too for my CIMB CC
[Magisk] kevinco1:
I've added certain apps to the unmount list to hide but I'm confused about when "unmount modules by default" should be enabled and what does it do overall?
[Magisk] zgfg:
It's whitelist mode

In the normal case, blacklist mode, you put to Unmount list only the apps you want to hide root from them.

When you install any new banking app, you must first add it to the list and reboot

In the whitelist mode, it's the opposite. But here you must put to the list all apps that need to use Magisk, root, installed modules, etc.

Eg, V4A and HMA must be listed, otherwise they will not work properly

But when you install a new banking app you will not need to care - it's not in your list hence it should not know about Magisk. But you know, some apps still detect root and its artefacts
[Magisk] spicediablo:
Yes, for now, that's what I did because I couldn't find any better way. If you have any better way, I'm all ears. Rebooting the phone just to use hlb is not practical in my opinion.
[Magisk] spicediablo:
I have updated rhb app to 2.12.1 and found that it is very irresponsive now(need to tap a few times before able to select a function) . However the same version is responsive on a non root phone. Anybody faces the same issue?
[Magisk] lvints:
Have any OP 9r users installed it on Android 11?

Where can I confirm whether it is compatible with Android11? If it is compatible, how do I install it?

I still use Magisk v23.0
[Magisk] CharlieMHz:
I have found somewhat of a workaround. With my current setup only TnG is not working so I'm able to run it in an isolated environment using Island. But the caveat is that since it's isolated, it can't access other data like your contacts, so transferring to your friends would take more manual effort. I'm also not very experienced with this so I don't know if there's any other downsides to using this approach.

EDIT: it's unreliable and stops working after a while, I'm now turning on Enforce DenyList too use the app, and turning it off after I'm done.
[Magisk] chuck4100:
I've been searching for a few hours now and many things say that Magisk Delta has something to enable 32 bit app support but I cannot find the option or anything that says how to actually do it.

Can someone assist me with this?

Is a complete wipe required to even show the option?

Swapped from Magisk 26301 (without wipe yet)

Pixel 7 pro

A13 June update

Magisk-Delta 26301
[Magisk] Charlestai1225:
bruh rhb is not working for newest magisk delta
[Magisk] Charlestai1225:
it will just keep enter to the rhb website, maybe something is wrong with magisk delta
[Magisk] creezalird:
I didn't mention that RHB is working for me. I do not even have RHB account :)

I just tried install and run it. It ran with no issue. but i cannot try login obviously
[Magisk] Unc3nZureD:
I installed magisk Delta and set some settings that was wrong for my device and now it's not booting. I could easily solve it by flashing a non-rooted or even a rooted, but only traditional magisk boot.img.

My question would be, how could I reset all the settings of Magisk Delta in order to begin with default settings? If I boot to magisk delta again, it'll bootloop due to the already saved settings I left.
[Magisk] Charlestai1225:
It can enter but only around 1min and it will close
[Magisk] spicediablo:
For me, it's slow to the point of unusable but I didn't encounter the app closing...

Update:another workaround method is just to create a 2nd space in phone and use rhb on that. I tested this and it worked. Easier than trying to experiment with various root settings to find ways for it to work...However, it doesn't work for Hong Leong connect app.
[Magisk] famaTV:
Hello friends!

I updated to the very latest version 26.301 in LDPlayer 9.057(9), but all modules (systemless hosts and zygic 1.91) are disabled. I can enable but after rebooting LDPlayer, they get disabled. I even tried a fresh copy of LDPlayer without any luck.

Your kind help is truly appreciate it!
[Magisk] CharlieMHz:
Update on this situation, the Island method doesn't seem to be reliable. But I've discovered that turning on Enforce DenyList allows TnG to work. So I'm temporarily using this now, and it doesn't require a reboot.
[Magisk] spicediablo:
Do you mean the circled option?
[Magisk] CharlieMHz:
Ah, you're on Delta, I think it's different. For Delta, it's to unmount all apps and only mount apps that need root. Enforce DenyList is a different thing. I'm using Alpha currently.
[Magisk] spicediablo:
I'm thinking if I should switch to alpha then...
[Magisk] lvints:
Has anyone had a problem with an app that doesn't see root?

I'm trying to use an app called Font Fix to change my font, but it says the phone isn't rooted.

I'm using stable version 26.1, on a OnePlus 9R with A11.

I have 3 modules (systemless hosts, safenety and sony device dummy).
[Magisk] zgfg:
If you have enabled Unmount Modules on Whitelist mode (it's not by default), you must add all apps that need root to the Unmount list - otherwise they don't see root (that's the point of whitelist mode)

And ofc, app must be granted root then
[Magisk] lvints:
I don't remember activating this option. Do you know where I can find it?

I only activated zygisk, bootloop protection and magiskhide.

I forgot to say that I hid the magisk app. Can be it?
[Magisk] scarymoviesg:
Hi everyone. I'm impressed with this version of Magisk and glad I started using it.

I was previously using the TJW version of Magisk, and I was able to update the firmware without losing root or data by following these steps:

1. Download the stock firmware.

2. Extract the AP file and patch it with Magisk.

3. Using Odin, flash the new stock firmware, using the BL, patched AP, and HOME_CSC files.

However, when I tried this method with Magisk Delta last night, my device got stuck in a bootloop. I was forced to do a factory reset to fix it (of coz, I lost everything). I am wondering if there is a different way to update the firmware when rooted with Magisk Delta.

Thank you.
[Magisk] zgfg:
Hiding Magisk app has nothing to do with

Above the Configure UnmountModules you have something like (I don't have my other phone Delta in front of me) UnmountModules by Default - if enabled, that's the whitelist mode
[Magisk] CharlieMHz:
On a device with A/B partition, I've always used the method inside the Magisk app.

Install your phone's update, but don't reboot yet.

Open up Magisk app, and press Install for Magisk

Choose "Install to Inactive Slot (After OTA)". It will install Magisk onto the other partition that you will boot into when rebooting.

Reboot.

Since you mentioned Odin, I'm not very familiar with Samsung devices, so I'm not sure if they're different in this regard compared to other phones.
[Magisk] zgfg:
Have you tried to install to the same phone/ROM and the same way Canary 26301?

Canary 26301 (the same code is in this Delta and also Alpha) has some issues

Eg, I have some issues with my old 'Ramdisk No' phone when patching or Direct installing Delta 26301, I reported to General Magisk thread (intentionally did not mention it was Delta) and (as expected) Pndwal tested on his similar phone but with Canary 26301 and obtained identical issues (he then even opened an Issue on GitHub - I couldn't bcs Canary/Debug version is a must when reporting)

Btw, I don't have Samsung but I've seen user(s) with older Samsung similarly reporting issues about the installation in Magisk General thread for Canary 26301
[Magisk] binoysankar:
Recent update of HDFC Banking app is detecting root. Has anyone found a way for this?

HDFC Bank MobileBanking App - Apps on Google Play

Online Banking app, UPI Fund Transfer, Bill Payment, Recharge, Manage Accounts

play.google.com
[Magisk] zgfg:
Maybe compare with this:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-89030267
[Magisk] binoysankar:
Thanks for the link.

I was thinking HDFC app has implemented some really powerful logic/mechanism to detect root and was scratching my head to figure out what to do.

Finally I ended up Uninstalling Magisk (removing root) in the process and HDFC app was working fine. They I installed Magisk app (just the app not patched it yet). Now HDFC app throws the same error :D

Which means it just checking Magisk app itseems even though I renamed the Magisk to different package name.

I tried HMA then HDFC throws some other error. Need to try it again.

Update: Fixed the issue with HMA. I was doing it wrong earlier
[Magisk] scarymoviesg:
Argh...so Canary 26301 is the reason why. I've not tried the "A/B partition" though. Guess something needs to be done before rooting in order to use this method (something about boot.img). I will learn more about this.. Thank you all.
[Magisk] cognitivedissonance:
I'm still all the way back on 25210 and it has been working just fine. I figured I'd look for updates, but if you're saying that 26301 has major issues maybe I'll hold off for now and hope it gets resolved first. Thanks!
[Magisk] amn1987:
Everytime I enable the Unmount Modules by default option after a reboot the hidden Magisk Manager app keeps complaining about loss of root. Exact message: Restore the Magisk app - The hidden Magisk app cannot continue to work because root was lost. Please restore the original apk.

This time the message came immediately after renaming the app. What's wrong?
[Magisk] zgfg:
Have you put all apps that need to use root - incl. Magisk app itself, into the Unmount Modules List?

Did you also put all LSPosed modules/apps there.

If you didn't, you will have the same problem with those others apps

The same (how to use Whitelist / Unmount Modules by Default) has already been asked and answered in this thread

When you switch from Blacklist mode (original mode, how Delta works when installed) to this Whitelist mode, you must completely reorganize your Unmount Modules List

In one case to he list go apps you are hiding root from, in the other case apps that have to use root
[Magisk] amn1987:
I had searched for Magisk Delta under Configure Unmount but it doesn't seem to be listed!
[Magisk] pxrave:
Hey guys systemless hosts file not work in latest canary. And bug fix? I active deaktove restarts many times. Adaway not work anymore. Any help for this?
[Magisk] zgfg:
Eg, how about this - previous page, ten or so days ago:

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

And there are earlier posts about the same, but previously it was called MagiskHide, not UnmountModules
[Magisk] amn1987:
I had configured it earlier to allow root access for apps that required it and it worked correctly. But the Magisk Manager app was never listed. Upon enabling the Unmount modules by default option, Settings and System UI were auto enabled after reboot. I thought it was necessary so until now I didn't untick them following which MD hasn't complained about loss of root so fat. Unfortunately after all this 2 apps still seem to detect root and can only be made to work in the Work Profile. All my other devices have KSU support where for now pretty much every app that I use works.

Edit: After a reboot Settings & System UI have been automatically added to the Configure mount list. Still root hasn't been lost so far.
[Magisk] zgfg:
If you have KSU, no.need to bother with Magisk (Delta, Unmount modules, etc).

Better use KSU and the modules for KSU (some have been discussed in the Magisk General thread - but better if KSU users would use a dedicated thread about KSU), and you should not have troubles in interactions with Magisk

Unfortunately, I cannot use KSU (kernel for my device is not supported) - but from everyything I've read, KSU is better, you can modularly control which root privileges (files, network, etc) you give to which apps and most important Magisk modules either already support KSU or the versions for KSU can be found on GitHub
[Magisk] Lord Sithek:
Did no one build a kernel with KSU for your device? There is one even for my old pal Redmi Note 4 :LOL:
[Magisk] zgfg:
There is only one but for AOSP and for a different Kernel version. Still I patched (per instructions, by magiskboot to my boot.img) and tried by fastboot boot. .., it booted but touch screen did not work on my MIUI and it was of no use

I'm on Xiaomi eu, hence MIUI 14, not on custom AOSP ROMs
[Magisk] amn1987:
You misunderstood. KSU is available for all my other devices barring the one in which I am using MD.
[Magisk] HippoMan:
Does anyone happen to know whether KSU could work with a custom ROM such as crDroid?
[Magisk] Lord Sithek:
of course, if kernel version is supported or someone build custom kernel with ksu
[Magisk] zgfg:
Start from KernelSU portal:

A kernel-based root solution for Android | KernelSU

A kernel-based root solution for Android GKI devices.

kernelsu.org

and KSU GitHub project:

GitHub - tiann/KernelSU: A Kernel based root solution for Android

A Kernel based root solution for Android. Contribute to tiann/KernelSU development by creating an account on GitHub.

github.com

download the KSU mngr app and test if your kernel is supported

Even if not officially supported, look on the portal if there are links to the GitHub projects.with unofficial KSU kernels for your device
[Magisk] SebaS-DG:
Hello, tried delta on android 11 lineageos on redminote note 7. And it ask me this "requires additional setup" if I tap ok, options, recovery mode tick, next, method "direct install (recommended). Then my device bootloop. And to go back to "normal" I have to enter twrp and flash the zip again. But again it will requires additional setup, when the system boot and open magisk delta app.

What I should do?
[Magisk] zgfg:
The problem is in the latest Magisk Canary 26301, that Delta 26301 is based on (patching Boot img, either when selecting a file or letting it to brick the phone by taking the 'recommended' Direct install)

Mentioned in this thread, Magisk General thread, reported to Magisk GitHub
[Magisk] SebaS-DG:
ouh...

So, if I cancel "requieres additional setup" is no problem? Becuase Im doing that now.

Safety net test passes all

And the shell box app I use in my country, that detects magisk even with safety net mod and others, is ok with delta now, and not using "requires additonal setup"
[Magisk] zgfg:
About hiding root from your app - put to UnmountModules and reboot, try with HMA, etc

It's not related with "Requires additional setup"

Btw, does the main screen in Magisk app show Ramdisk No?

If so, then under Install Magisk disable Recovery (BCS 26301 wants to patch Recovery instead of the Boot)..Then probably, Direct Install will not cause bootloop but will likely ask again requiring 'additional setup'
[Magisk] SebaS-DG:
asd:

found the fix. Using Orange fox recovery "R11.1" for android 11, now is ok.

I was using last twrp then last orange fox, both doesnt work. "R11.1" orange fox is the correct one for android 11 lineageos

---

Ramdisk: No

Did nothing else, but no more pop up of: "Requires additional setup"

Ram Disk NO, is ok? on all my other phones with android 12 or 13, ram disk is YEs.

On my 3 redmi note 7 ram disk is No

Didnt understand what I have to do
[Magisk] HippoMan:
Oh ... I now see that KernelSU manager will tell me if my device is supported.

Thank you!
[Magisk] Prof. Yaffle:
I've had that a couple of times. The fix seems to be to reinstall the Magisk / Magisk Delta app over the top (from within the app seems to be fine).
[Magisk] amn1987:
Tried that several times but seemingly no change but for some reason the issue was resolved finally . A complete uninstall from within the app succeeded but after reboot there was a stub of the Magisk Delta app which then prompted about downloading the app. This kept on repeating endlessly. Tried uninstalling from the recovery but it made no difference. I wonder if Island was somehow to blame...
[Magisk] pndwal:
Any (and only these AFAIK) single 'slot' device launched with Android 9 (ie. A only legacy SAR) is a Ramdisk No device, ie OEM didn't supply generic ramdisk in boot partition (although there may be vendor/other ramdisks there), so that indicator is correct since RN7 is single 'slot' and launched with Android 9.

For Xiaomi, you don't need Recovery Mode Magisk (Magisk patched to recovery ramdisk) since bootloader invariably supports Ramdisk in boot partition and Magisk will add one to support magiskinit... I put details on this here recently:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-89004095

However while the indicator itself was recently fixed (Magisk was misidentifying devices / erroneously detecting from 26105) with Fix device detection scripts and logic and Always check mounts to detect legacy SAR on bootmode in 26202, a Recovery mode user setting retention issue (regression) got missed...

As the Recovery Mode check box is still reverting to checked (selected) in these cases, users are generally leaving it checked (as they don't know better) and Magisk is then patching ramdisk in /recovery partition when taking Direct Install, and recovery.img in Samsung AP binaries when patching these...

Taking Reboot will also cause many devices to boot via recovery (as it's trying to boot system with magiskinit in recovery ramdisk) where Recovery Mode is left checked...

If you/others here tried updating, you likely have both Magisk-patched boot.img and recovery.img now... You may need to start fresh with restored stock recovery.img or unpatched AP binary (if Samsung) to correct erroneous patching before installing 26202+ (... Unless you have an A-only legacy SAR device like Galaxy S10 that actually needs Magisk in /recovery partition).

You will also need to go to Magisk Install in App and uncheck Recovery Mode whenever using App for patching etc, and particularly before rebooting or closing App until this remaining user selection issue/regression is fixed... I made a GitHub Issue for that here:

App loses Recovery mode user setting for A-only legacy SAR devices

and Devs are working on a fix...

Hope it helps... 🤠 PW
[Magisk] amn1987:
Is it necessary for Settings and Settings UI to be the ticked under Configure mount if Unmount modules by default option is enabled? It seems that it's done automatically.

Dunno if it made any difference or not but previously I used to rename the Magisk Manager app as "Admin" but left it at the default "Settings" this time following which Unmount modules by default option has not posed any issues so far for the first time ever.
[Magisk] zgfg:
First, there is a BIG DIFFERENCE what goes to Unmount Modules list if Unmount Modules by Default is enabled or not. Answered at least two times in the last two weeks - please scroll back and look for the posts

In the first case it is Whitelist mode, in the second it is Blacklist mode, hence totally opposite apps must be ticked to the list

I run Blacklist mode and I don't put Settings in (my Settings DOES NOT DETECT/COMPLAIN for Root). But I have to put my native Security app (it complains about root)

In the Whitelist mode, only apps that NEED ROOT. If your Settings (maybe for your custom ROM) really needs root, then (bit only in the Whitelist mode) put Settings in
[Magisk] amn1987:
Yes I understand about the Blacklist part as opposed to the earlier Whitelist. I am using a custom ROM(Havoc R). Just trying to find out what went right this time as my previous attempts to enable UMBD or SuList always resulted in the Magisk Manager complaining about loss of root frequently after a reboot whereas UM or MH worked flawlessly. Settings and System UI are automatically selected under Configure Mount after enabling UMBD. No issues so far so I haven't changed it.
[Magisk] zgfg:
Magisk Manager NEEDS root (and does not complain about root), hence you must put it in the list in the Whitelist mode (Unmount Modules by Default), and you must not put it in if Unmount Modules by Default is not enabled

That's the whole point. And exactly the same another user asked few days ago (it is called Magisk App, not Magisk Manager hence the q & a for Magisk app must be few posts above)

Problem is that ppl don't understand how things work, so they adjust the list for one mode, then they switch to the opposite mode but do not wipe the old list and set a new, opposite list), and then they wonder and have issues

Besides, there are no banking apps that will work only in Whitelist mode (or Blacklist mode). There are only users who don't know to properly set the list for the other mode, hence it works for them 'only in one mode'
[Magisk] xt7xda:
Hi,

I'm using Lineage os 20 (A13) on oneplus9r, with Magisk delta.

Few days back, my banking apps got updated, and they started detecting root.

I updated the magisk delta to 26301, tried magisk also.

Safetynet is passing with basic evaluation.

But in Play integrity, all three are failing.

Feeling clueless.

Need help.

iMobile Pay: Loan, Banking App - Apps on Google Play

Instant Loan, UPI, Fastag, Bill Payments & more for both ICICI & Non-ICICI users

play.google.com

Kotak Mobile Banking App - Apps on Google Play

Kotak Mahindra Bank’s official mobile banking application for Android phones.

play.google.com
[Magisk] HippoMan:
I'm using Delta 26.1 (26100) on my Pixel 7 Pro which is running crDroid 9.8 (Android 13).

When initiating the use of SuList, is there any way to automatically copy all of the references for my currently rooted apps to the SuList?

It seems like I need to enable all of those rooted app references manually in SuList, and that is a pain, because I have over 200 apps on my device and quite a few that are rooted.

Or am I missing something about how to use SuList?
[Magisk] zgfg:
There was sulist-auto-whitelist.zip module that would find and put all apps from modules to the whitelist.

It worked fine with Delta v25, after that it was only necessary to manually put few more apps like Magisk app, AdAway and so

Nevertheless, I don't know why that list is necessary in the whitelist mode. The list must be practically the same like the list for SuperSU (apps granted root) - hence why Delta wouldn't simply use for the whitelist mode (apps need to see root) the same SuperSU list (apps that are granted root)

No matter is it Delta v25 (Auto SuList) or v26 (Unmount Module's by Default)
[Magisk] HippoMan:
Another question concerning Delta 26.1 (26100) on my Pixel 7 Pro which is running crDroid 9.8 (Android 13) ...

Even though I have the Systemless Hosts module enabled and AdAway set to root in SuList, AdAway is still telling me the following ...

Failed to install new hosts file

Unable to copy hosts file to /system partition. Please check Magisk systemless hots module is enabled then reboot.

I read other posts in this thread concerning AdAway, but it now seems to be able to access /system for those other users who are writing about AdAway (and they are only reporting AdAway specific problems, which I know have nothing to do with Delta itself).

Perhaps am I out of luck with 26.1 (26100) regarding /system access, and if so, would I need to upgrade to a later Delta version?
[Magisk] zgfg:
I remember that some versions of Magisk (hence also the Magisk Delta versions) caused issues to modules when systemlessly mounting changes

I don't recall did it apply to v26100

But if you switched the camp to Pixel, why don't you use PF (I guess, the author/app will properly circumvent the Magisk v26301 installation issues if they apply to your phone) to install Delta v26301 - for me AdAway and everything works fine on the latest (Canary) Delta
[Magisk] HippoMan:
Thank you very much!

I was going to use PF with my Pixel 7Pro via the Windows machine I recently obtained, but then I discovered that this Windows box has USB port issues. Also, I don't want to run the risk of ruining things by any possible Linux-related PF glitches.

So, I think I'll just try upgrading to 26301 the "old fashioned" way.