yashsingh1/xdaforums huggingface dataset:
[Magisk] dknight178:
Thanks for replying.

I have two devices which have basically the same user apps (including the ones in the screenshots):

1) Oneplus 9 pro (Android 11) - BPI and citibank ph, along with barclaycard UK all working fine; halifax and other lloyds not working

2) Oneplus Open (Android 13) - barclaycard UK works but not BPI and Citibank ph.

Given this, I have tried using lsposed mod + HMA (blacklist and whitelist) + bootloader spoofing but still not working.

Pls see screenshots attached. Pls note titanium backup, systemiser

and energized modules are also in my oneplus 9 pro. I only installed applist detector and momo to try to figure out why I am having issues - momo not working but applist detector is fine. I've also tried freezing magisk manager with icebox but still same error.

Also, I have turned off developer mode for BPI app which is required.

Hope you could pls help me. Thanks
[Magisk] bobbarker2:
Anyone having problems with 26404? Everything was running smooth on 26403. I updated to 26404, rebooted and now Google Play Services is crashing, apps that have root permission that worked before are no longer getting it.

The Magisk log this error:

01-02 08:19:11.007 911 913 E : cp_afc /debug_ramdisk/magisk32 -> /debug_ramdisk/.magisk/zygisk/lib/libzygisk.so failed: No such file or directory (os error 2)

Not running any modules besides Play Integrity Fix. I even removed it and rebooted and still get this error
[Magisk] fbirraque:
None issue on Poco F3 (MIUI14.eu)

Running smoothly.
[Magisk] casouzaj:
Neither in my wife's Xperia XZ2, running LineageOS 20. It's just like with the previous version.
[Magisk] arda99:
Latest R6592CA0F breaks su in termux.

as it now injects to /apex/com.android.runtime/bin/su

in termux, modify the su script(nano `which su`) and add above path or termux can't find su.
[Magisk] dipseeet:
i went back to 403
[Magisk] xcl1pse:
Just do pkg upgrade in termux. Husky already submit that problem and merged into main. If termux tools isn't updated, change termux repo
[Magisk] dknight178:
Hi All,

I am on Android 13 using kitsune (whether magisk hide or enforce SU) + PIF + lsposed/ HMA (blacklist). Even if I remove HMA, the result is the same.

I am struggling with these two banking apps:

- https://play.google.com/store/apps/details?id=com.bpi.ng.app

- https://play.google.com/store/apps/details?id=com.citibank.CitibankPH

The UK banking apps are mostly fine but I struggle with these two. It is worth noting that for Citi - it momentarily works sometimes if I clear data and force close then restart, but after the first loading it will now detect my phone is rooted. BPI doesn't work even if I use bootloader spoofer or not - it says threat detected.

I've tried ice box to hide the repackaged magisk, titanium backup, terminal emulator (all of which are also on my Oneplus 9 pro) but still not working.

Weirdly enough my Oneplus 9 pro (Android 11) with the same setup and apps minus HMA can handle these two perfectly fine.

Momo also doesn't work even if I allow background access and turn off battery optimisation. Nothing gets triggered from applist detector. Device is certified and passes play integrity.

Appreciate your help on this, thanks
[Magisk] dknight178:
For some reason, I managed to fix my issue using shamiko + kitsune + HMA.
[Magisk] dominicsyyy:
installed shamiko 0.7.5 and BPI app now works! thanks
[Magisk] WhoIsJohnGalt1979:
Please correct me here. BPI would work with any alpha or kitsune with shamiko. HMA is not required. The only bottle neck is you need to keep Developer option disabled.
[Magisk] dominicsyyy:
im using delta/kitsune with shamiko, other magisk mod im not sure. before im using original magsik (pixel 7 Android 13) and having problems thats why i switch to delta/kitsune.
[Magisk] dknight178:
Not sure but it seems I need HMA for other banking apps
[Magisk] zgfg:
Why not. Its needed for many apps. Standard case
[Magisk] HippoMan:
I'm running stable Kitsune 26400 under A11 on my Pixel 5.

I'm thinking of upgrading to this new 26404 release.

I've read and I understand the change log. I just want to know if anyone has encountered any issues or "gotchas" with 26404 as compared with 26400.

Thank you in advance.
[Magisk] xflowy:
can someone help me here: i wanna switch to delta/kitsune. what is the new version?

R65976974-kitsune (26404)

or

26.4-kitsune-2

?

One is 2 days old, the other 3.

Also: do i need to additionally install ZygiskNext?

Thanks!
[Magisk] mGforCe:
I updated to the latest version on A11 (LOS) on Redmi Note 9 Pro (curtana). No issues observed so far.
[Magisk] Depressed T.Bear:
Hi Hippo, I'm on the latest (canary) Magisk Kitsune. So far, I have not noticed any issues.

Just a few things to mention: after 26403, you need to run 'pkg -upgrade' in Termux. Otherwise, it won't find the new located su binaries and tells you that you're unrooted.

Secondly, the new Shamiko (> 0.7.5) is no longer compatible with Kitsune. If you want to benefit from it's improved hiding mechanisms, you have to use canary standard magisk. I'm not sure about magisk alpha, I heard some voices, claiming that it's also not working there.

Thirdly, Kitsune will (soon? now?) be incompatible with ZygiskNext as magisk module. It's adviced not to use Sulist then since it will break some modules.

So far, noone could answer my question what exactly happens, since ZygiskNext is (widely) implemented inside Kitsune. So it's unsure right now if Sulist would only be adviced to use if no other magisk modules are used... We urgently need some clarification from Husky.

Lastly, Kitsune will change or changed the systemless host function. The editable host file will be moved from its standard location to a new one, which will break apps like Adaway /malwack until they adapt to the new path.

--- edit

Small disclaimer: If I didn't get something right, please don't crucify me and just correct me with the right Information. The latest changes resulted in heated arguments and it was hard to follow all of them.

Depends what you consider 'new'.

The stable one can be found under

Stable / Beta​

26.4 Stable

On github.

If you want the bleeding edge version (which most of us use), you want the Canary (app-release.apk), latest as of now is R65976974-kitsune.

ZygiskNext is (widely) included in Kitsune. The latest version(s) of ZygiskNext however are NOT compatible anymore! (same as Shamiko beginning with version 1.0.0)
[Magisk] mGforCe:
I have been on Kitsune and before that on Delta. Have been upgrading through Direct method. Never had to do this manual pkg-upgrade.
[Magisk] HippoMan:
Many thanks to @mGforCe and @Depressed T.Bear !!!
[Magisk] Depressed T.Bear:
I think I didn't express very well :D not Kitsune needs this command. It's the Termux terminal app - if you use it.

You're welcome buddy! 😊
[Magisk] zgfg:
For ages, AdAway uses Systemless hosts (if enabled in Magisk app) hence AdAway does not write to the /system/etc/hosts - moreover, on A11 (on some phones startingbeven with A9) and newer (excluding custom ROMs where developers maybe intentionally do not apply), System is READ-ONLY on the file-system level and irregardless of Magisk or Kitsune, the hosts file is not editable

For that reason, TJW had years ago implemented SYSTEMLESS rooting in Magisk

So, AdAway does not write to /system/etc/hosts aka /etc/hosts but to /data/adb/hosts/system/etc/hosts and Magisk (official or Kitsune) mounts that hosts file to /etc

And there is no need to 'reinvent the wheel' here, it works perfectly

---

However, there are other serious issues with Kitsune

- Viper4Android (Repackaged).cannot install. Open the V4A app, it says No driver, it starts to install and halts then after 20%

And the installation never finishes. Not after reboot.

And AML does not help

However, same phone, same ROM, same V4A (Repackaged) imodulennstalls with no issues, with or without AML

I have also problems with BusysBox module. In Kitsune 26403 it didn't work at all (no BB applets were mounted from /data/adb/modules/... to /(x)bin

Now in v26404 Kitsune mounts them again (even Kitsune v26404 Changelog says that it was fixed) - however now Kitsune mounts them not only to /(x)bin (correct) but also duplicated to / (incorrect)
[Magisk] Depressed T.Bear:
Thanks for your, as usual, good and informative answer @zgfg 👍

I already knew, however, how the 'systemless host' feature works. Good read for all others though!

I found it just worth noticing since Husky announced a couple days before:

Regarding your busybox issue, this info might be useful as well:

I might find the time later next week to test osmosis busybox module on the latest Kitsune. In theory it should work regardless.
[Magisk] zgfg:
The comment you.quotef for BB was from the time of Kitsune 26403 when BB module did not work - Kitsune v26403 did not mount BB applets

After that, it was fixed, the fix was mentioned in Kitsune v26404 Changelog and Husky even commented separately his fix (that it was a bug in v26403) in another issue on GitHub

Otherwise, generally about the use/need for BB, it was already answered here previously, with more technical details

So just shortly, the point is not in the need/use of BB for other modules (that functionality has always been provided by the Magisk itself, hence it is noting new or specific for Kitsune), but for users who may want to run shell scripts (calling various Unix/Linux utilities from Terminal Emulators.

Also, maybe not needed for Termux (if Termux provides it's own BB) - but Termux is not the only and single Terminal Emulator

But I have now observed (and commented in the previous post).that Kitsune v26404 now mounst.BB applets (from the module) not only to /bin or /xbin (how it has to) but also to the plain root / (which is not how the systemless rooting should work)

So when you test BB module, check do you see the installed BB applets only in /bin or /xbin (depending on your ROM) or also in the plain root /

However, I'm really more CONCERNED with the problem that Kitsune restrictions now block Viper4Android
[Magisk] HippoMan:
PS: I have Zygisk enabled in Kitsune 26404 (and I had it enabled in 26400, also).

I'm running LSPosed-zygisk version 1.9.2 (just like in 26400), and there are no apparent Zygisk-related problems.

And no Shamiko.
[Magisk] uschipower:
By the way, huskyDG also invented a Magisk-Module called overlayFS, which should make /system and other RO-Partitions possible to mount as RW.

Of course only if kernel support overlayFS.

Although I could install overlayFS (which should mean that kernel support it), I cannot change anything on /system in running Android.

Does anybody know how so solve this?

ROM: AndyYan's LOS20 Treble GSI

Device: Lenovo TB-X505F

manufactor-related-paritions: Android 9

File-Manger: TotalCommander

Intension: Rename /system/addon.d to something else
[Magisk] sawdoctor:
I didn't think it's just a kitsune issue, if you read the official Magisk GitHub there's a lot of posts from users who lost root/no su after upgrading to latest magisk canary.

Not sure why some devices are affected and others not but it's a magisk bug in general
[Magisk] sawdoctor:
Did you edit mode.sh ? I'm not sure what the default value is but it needs to be set to 1 to enable read/write and then reboot
[Magisk] uschipower:
yes, as described at github, I changed value to 1 in mode.sh and made a reboot -> no change.

Neither TotalCommander nor MIXexplorer can mount /system as RW or can change any Folder/File on /system
[Magisk] zgfg:
I had OverlayFS installed 3-6 months ago, I tried on both my phones, one with Magisk Delta, another Magisk Canary (and with no KSU)

I later switched Delta and Canary between those two phones

There was no problem or any indication at installation (so don't count on that), installation went fine on both

However, on one phone (MIUI 14, A13) OverlayFS successfully nounted System as read-write out-of-the-box, on the other (two years older phone, MIUI 12.5, A11) never (no error, just System was still read-only). Although I experimented with the script and/or I switched from Canary to Delta

IMO, it's all up to the kernel
[Magisk] mGforCe:
Luckily I never faced this issue in my daily device. Has been on Delta / Kitsune only.

But yes, in one of my spare devices, root was lost suddenly while I don't remember doing anything. I conclused that I would have done some tweak w/o realizing its impact. Now I know!
[Magisk] Depressed T.Bear:
I'm sorry, I'm not to long on canary Kitsune. I came around Christmas from stable Magisk.

Though, both quoted messages were posted on 02.01.2024 and I was pretty sure that 26404 was already released there. 🤔

Thanks for the further Information, I'll check it later this week!

I'm only using the in-built zygisk+magisk hide+Sulist. All my modules currently work as INTENDED :)
[Magisk] uschipower:
from with partition does the kernel come from?
[Magisk] zgfg:
Kernel is in boot

You can extract (and repack) Kernel from Boot by use of magiskboot

Read instructions (for manual replacing of Kernel) on KSU
[Magisk] zgfg:
Closing comments from my side (since I will now irreversibly uninstall Kitsune and clean install Magisk also to my second/backup phone)

As mentioned yesterday, I was trying audio mods on Kitsune 26404 (audio mods are always one of my main reasons for rooting and installing Magisk)

I tried on Kitsune each of them, with and without AML:

- V4A Repackaged v2.7.2.1

- V4A Reverse engineered v0.6 .1

- JamesDSP v5.8

No success. V4A app can never install drivers (it starts and stalls), JDSP app force-closes on launch

Then I (dirty) flashed Magisk Canary over Kitsune and now both JamesDSP and Viper4Andriid work (I tried both Repackaged and Reverse engineered) with no problem (I can also run both JDSP and V4A with the help of AML)

Same phone, same ROM
[Magisk] HippoMan:
Nice to know you're successful!

A question, just to make sure I understand properly ...

By "(dirty) flashed", do mean the following? ...

* Un-hide Kitsune

* Disable all Magisk modules without deleting them

* Reboot

* Install the Canary APK

* Do the "direct" install option in Magisk

... or were you referring to a different procedure?
[Magisk] zgfg:
No, I just installed Magisk Canary app, granted it root and made Direct 'upgrade' to Magisk Canary, uninstalled Kitsune app and rebooted

As expected, modules and root grants survived but I had to fill DenyList (since Kitsune stores Magisk Hide list to a different table in magisk db)

When time permits I will fully uninstall Magisk and go over clean
[Magisk] HippoMan:
I see. Thank you for explaining.
[Magisk] uschipower:
would you be so kindly and explain this?

Which manual do you think of exactly?

My devices are older one, lenovo TB-X505F and TB-X605L, latest stock rom was android 9 + 10.

Kernels are V3.18.120 and 4.9.205
[Magisk] sawdoctor:
Have you seen the James dsp telegram group chat? There's a post/explanation/potential fix been posted today
[Magisk] zgfg:
KernelSU.org

official site.

Search for magiskboot / scroll down till you come as on the screenshot

Did it twice and described steps in PIF thread and Magisk General thread but the posts are buried down (specifically in the PIF thread, it's maybe hundred pages back now)

But KSU gives you the needed howto

Btw, you don't need PC, ADB.

Since you have Magisk, use Terminal Emulator and call directly, eg:

su -c /data/adb/magisk/magiskboot --help

On Delta/Kitsune, /data/adb/magisk/magiskboot is not the binary itself but a link to the binary (Kutsune installs Magisk binaries to a different path) hence the same command will also work
[Magisk] zgfg:
Nope, too late now

Anyway, I prefer V4A over JDSP, and specially the Repackaged over Reingeneered Beta (Beta still doesn't support Convolvers)
[Magisk] uschipower:
ok, so far, i understand.

On a android-system which has an installed magisk, there is a tool called magiskboot.

I also have the boot.img file somethere on the device, f.ex. /storage/emulated/0/

should i use the boot.img from stock rom downloaded from manufacture, or should i take modified boot-partition saved with TWRP into boot.img-file (boot modified by Magisk, Disable_Dm-Verity-fec-quota.zip, etc.)

Step4:

I extract boot.img with that tool.

Is there only 1 file in boot.img or more?

Is the name of the file always "kernel"?

where do I find the extracted file(s) - in the same directory of boot.img?

Step5, Replace kernel with Image: mv -f Image kernel

I dont understand this.

What is "Image"? A File?

If yes, where do I get this file, and which one is the correct one?

Thanks.
[Magisk] Swap_File:
I just made the switch from Magisk to Kitsune Mask, and figured I'd report my findings:

Magisk 26404 + Shamiko 1.0.1 will stay hidden from Marriott Bonvoy, but not LIAPP (Blind).

Kitsune Mask 26404 will be hidden from LIAPP (Blind) but not Marriott Bonvoy.

Kitsune Mask 26404 + Shamiko 0.7.5 will work with LIAPP (Blind) and Marriott Bonvoy (Great!)

I didn't try Kitsune Mask 26404 + Newer Shamiko since earlier in the thread someone said it wasn't supported.

I'm also running Play Integrity Fork v5 and LSPosed 1.9.2 with a handful of modules. I did not have to hide the Kistune Magisk App.
[Magisk] zgfg:
Please follow their guide

I unpacked my boot.img and replaced the Kernel with one unofficial KSU kernel for my device but not for my ROM (that was the closest I could find since my device is not supported by KSU). So I repacked boot.img back (again with magiskboot) and tested by fastboot boot ..., not by fastboot flash boot ... (hence not by permanent flashing)

It booted but even the keyboard to unlock the SIM and screen did not work - so I safely rebooted back to 'normal'

If you want to play, please do on your own and be aware that if you permanently flash the boot.img you (wrongly) cooked, you could brick your phone

So better don't - if you want KSU, study instructions on their site, find and download their app to check if your phone/ROM is supported. And if so, flash only their pre-cooked boot.img with the KSU

Sorry, I don't want to assist in that, and I have tested twice, did not work for my phone as described, so I will not play again to be able to provide you further details and instructions
[Magisk] amn1987:
Did you try to flash the KSU kernel in stock OEM ROM or in any custom ROM? I have read that it's not supported in the former. I have only used custom ROMs in which the stock kernel includes support for KSU by default.
[Magisk] zgfg:
Lisa, Xiaomi.eu Stable 14 (custom ROM but based on MIUI)

qgki kernel (in the ROM), hence not (officially) supported by KernelSU

I found only one KSU kernel on GitHub for my device (supporting qgki kernel) but noted by developer that the kernel is only for AOSP ROMs (my Xiaomi.eu is not the AOSP ROM)

So that is the only thing I tested (as described, unpacked my boot.img, replaced with that kernel, repacked) and tested by temporarily booting - to my surprise it did boot (no bootloop) but keyboard did not work to unlock the screen

I have no plans to switch to AOSP ROM just to try KSU (I like to stay on Xiaomi.eu)

I didn't even want to remove screen and SIM unlock and to try again

Pretty sure I would then come to the next issue (maybe WiFi, maybe 5G, who knows - this is my daily driver and I need full and stable functionality with screen and PIN lock protection), since the developer clearly noted that his kernel is compatible only with AOSP ROMs, not with MIUI
[Magisk] amn1987:
Got it.For my devices there are some custom kernels that are also compatible with MIUI but I haven't checked if KSU is supposed to work in MIUI or not. I ditch MIUI in all my devices ASAP in favor of AOSP/CAF based custom ROMs so KSU is an additional bonus in my case.
[Magisk] zgfg:
For official KernelSU check with their official manager - screenshots
[Magisk] amn1987:
None of my devices launched with kernel 5.x. All are 4.x and supported unofficially only. In some cases KSU can be kept disabled and Magisk can be used instead.
[Magisk] Jon.StatiK:
Not 100% certain but I'd almost bet money it had something to do with granting root and Enforce Su List in Kitsune. I've experienced almost identical issues in the past not realizing how it's root list works rather than deny list. Not saying you don't know, just speaking from experience.

I'm currently using JDSP on A14 with no issues and have been using it for a long time now.

Either way, good luck on your endeavors.
[Magisk] zgfg:
I had a clean installation with no whitelist and JDSP app asked and got the root grant

Btw, previously, with up to v26401 (or certainly up to v263xx) I had both V4A and JDSP (with AML) installed with no problem.

Even in whitelist mode (unmount modules) I additionally checked V4A and JDSP in the list and it worked in those earlier Delta versions
[Magisk] Schmye Bubbula:
Magisk module to fix "su" problem introduced by recent update of Kitsune, by Marius Purwin, with his permission, on Telegram group, Unofficial Magisk Forum [SFW]:

Mod Edit: Link Removed

(I had to click, "View in Group" to be able to click it to download the zip file.)

(Also attached below.)

It makes a symlink pointing back from the original /system/bin/ to the new location so that everything still works like they used to, such as only having to enter "su" without further ado to get root in Termux, or restoring some now-otherwise-broken apps that call root.

This works for me in most apps that broke with the new su mounting location, such as Termux and Lucky+Patcher, but at least two other of my apps keep getting denied root: ReVanced Manager, and Package Manager — I wonder what's up with them.

If this module passes muster, then seems to me it ought to be folded-in to Kitsune as a matter of course. (Husky?!)

(Someone earlier said this happens in stock Magisk, too?)

--

Magisk Kitsune has changed the mounting su location from

system/bin

to

/apex/com.android.runtime/bin

to minimize the use of bind mount. For most apps (that don't change/hardcode PATH variable), this change should not break anything. For a known app like Termux which hardcodes PATH and fails to locate su you can call

/debug_ramdisk/su

instead.
[Magisk] zgfg:
From whom and with whose permission?

In the service.sh in your zip it clearly says:

# Magisk Module: Magisk built-in BusyBox v1.0.7

# Copyright (c) zgfg @ xda, 2022-

# GitHub source: https://github.com/zgfg/BuiltIn-BusyBox
[Magisk] ZerkerEOD:
Anyone know what's going on with the telegram update channel saying it's dead?
[Magisk] fbirraque:
I also wanna know
[Magisk] Godlydevils:
Magisk Devs fought with each other, Lsposed went on maintenance because of an old comment by admin member of magisk so I guess some Chinese people attacked kitsune's group or maybe huskydg stopped maintenance because of threats
[Magisk] sawdoctor:
Unfortunately there seems to be some hostility between the Vietnamese and Chinese Devs. Really is a shame as it just makes modding/root hiding harder
[Magisk] Godlydevils:
I just hope HuskyDG comes back & wish to see his work & contribution, since I've used his magisk, I've never touched any, I don't want him to go
[Magisk] ZerkerEOD:
He is still on their github closing pretty much any issue and marking it as spam preventing people from commenting back. he also adds no comments as to why. I can't install it anymore and having to switch back. I tried modding the init_boot.img on several OTA updates checked md5 before and every time magisk says it isn't installed. I tried the new canary builds and the older 26400 build and nothing works.