huskydg/magisk-files

Kitsune Magisk

This is not an officially supported topjohnwu project.

This is not Official Magisk, please go to this page and download Official Magisk

Download

Stable / Beta

• Kitsune Mask v26.4 Stable

Canary / Debug

We only accept bugreports from LASTEST DEBUG build. Invalid bugreports will be closed instantly.

Kitsune Mask

Kitsune Mask has MagiskHide, SuList and new Zygisk loading mechanism

• Canary (app-release.apk)
• Debug (app-debug.apk)
• Changelog

Kitsune Lite

Kitsune Lite only has SuList feature and no Zygisk built-in or supported. SuList feature depends on logcat to work!

• Canary (app-release-lite.apk)
• Debug (app-debug-lite.apk)
• Changelog

Other version

• Releases page

Source code

• https://github.com/KitsuneMagisk/magisk

How to install

How do I install Kitsune Mask from scratch?

Process like installing Magisk: https://topjohnwu.github.io/Magisk/install.html

How do I switch from the current Magisk to Kitsune Mask and vice versa?

Easy, just do it like when you update Magisk!

Direct Install (Recommended)

1. Install, open, and then grant root access to Kitsune Mask.
2. Inside Magisk, tap "Install" and then "Direct Install". If you don't see this, try restarting the app.

Or flash Kitsune Mask from the current Magisk app

1. Rename the extension magisk.apk to magisk.zip
2. Open Magisk app, click the "Modules" tab -> "Install from storage" and choose magisk.zip

Install Magisk directly to /system instead of patching boot image (Not recommended)

This method is only for ROMs with Permissive SELinux mode or Enforcing SELinux with permissive "u:r:su:s0" context in sepolicy rules, such as user-debug ROMs like LineageOS. Make sure you have a backup of your ROM and a working Custom Recovery. Your ROM and kernel must support read-write mounting and dynamic SeLinux rules patching. This method may cause boot failure, so use it at your own risk!

1. Restore the stock boot image if you have Magisk installed already.
2. Boot to recovery, rename magisk.apk to systemmagisk.zip, and flash it.
3. To update Magisk, use Direct Install into system partition instead of Direct Install.

How to install Magisk into Android emulator

Patching ramdisk is not feasible for the emulator, as the ramdisk partition has insufficient space for Magisk binaries. The following emulators and Android-x86 projects have been tested: NoxPlayer, LDPlayer, MEmu, BlissOS, and PrimeOS.

Step-by-step to install Magisk into an emulator like NoxPlayer, LDPlayer, MemuPlayer, etc

1. Enable Root access in emulator settings and writable system image disk (if available)
2. Install and open Kitsune Magisk app.
3. Grant root access to Kitsune Mask, click "Install" under the Magisk field, and use "Direct Install into system partition" option instead of "Direct Install" option. (If you don't see this option, close and re-open Kitsune Mask app.)
4. Enjoy Magisk feature with Kitsune Magisk!

For some reasons, closing Root access in emulator settings will intentionally removing Magisk su, so do not switch off Root access.

Kitsune module

• To develop Magisk module that might use specific Kitsune Magisk features (early-mount, init.rc injector,...), you can download this module template

Donate me

• Paypal: paypal.me/huskydg
• Thanks for all your supports and hope you have a good day! 👍

Credits

• Magisk author: topjohnwu
• Magisk contributors: vvb2060, yujincheng08, RikkaW, canyie
• Magisk Hide in whitelist mode: MagiskLite
• Zygisk implementation by ptrace: ZygiskNext, Dr-TSNG and 5ec1cff

License

Our license obviously is the same as Magisk's license

Magisk, including all git submodules are free software:
you can redistribute it and/or modify it under the terms of the
GNU General Public License as published by the Free Software Foundation,
either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program.  If not, see <http://www.gnu.org/licenses/>.

magisk-files's Issues

Enable LSPosed for any apps will expose Zygisk

As mentioned above, Momo can detect the zygisk from R6573543B version.

About LIAPP's full implementation of fission detection for the entire Magisk series

Root is detected even when using Shamiko and HideMyApplist.
https://play.google.com/store/apps/details?id=com.rawhand.thewizarddiary

There is a discussion about it on XDA, but unfortunately no progress has been made so far. Help would be greatly appreciated!

Here is the link to the relevant XDA thread about it: https://forum.xda-developers.com/t/blind-app-is-detecting-root-with-magisk-hide.3830678/post-88646103

Thank you in advance for your help. :)

About the Kitsune Mask Loophole

Using version "R65894F03" to flash the magical overlayfs module will cause root to disappear on Kitsune mask. However, you need to change the mask version, authorize superuser rights, delete the overlayfs module and restart to use Kitsune mask.

Root lost

This is the log

magisk_log_2023-11-24T18.11.27.log

The most 2 recent releases breaks ldplayer 9 and mumu 12 player and possible all other emulators.

Can anyone confirm this with the latest release? Tested a lot too and the third latest version and below works without causing the emulator black screen or unable to open most installed apps.

Root lost after updating to the latest version.

so magisk delta 26.4 is out. I downloaded the latest apk and after that I downloaded magisk using the direct method. I rebooted and after that I go into the settings app and it says that the root is lost! I go into 26.4 app and the root is gone. What do I do?

Magisk was denied access to superuser app ?

So I have kitsune mask installed correctly it was working fine a couple of weeks ago but now whenever I open an app that requires root it will automatically say that it was denied although I have put it to agree to superuser request in the settings the only apps that work is the official magisk and SD maid I have also noticed that it denies access to already installed apps and accepts one's that are newly installed I tried reinstalling old apps but to no avail, it is still not working I have tried switching between official magisk and kitsune mask and also tried reinstalling kitsune mask root directly using the direct patch options but it still doesn't work do I have to wait for an update or do I have to redo the root for my Samsung galaxy note 10+ phone? Thank you in advance

R6592CA0F version will cause the camera to fail to start.

Back to normal after brushing into the R6583F3E5 version.

Sources are very hard to find

Hey @HuskyDG, thank you so much for your work!

I had a very hard time finding the source code belonging to the pre-built artifacts/releases in that repo, and was (in the end rightfully) called an idiot on telegram for stating that this is not an open source project because I found only binary stuff and what seemed to be an unmodified Magisk fork.

Are there any chances that you could make it more clear where to find the latest source code of your releases, maybe even merging your latest development branches into main branch when done?
This would help poor half-blind devs like me a lot. 😅

Thanks so much again, please let me know if I can help in any way.

where is bootloop protector?

we need bootloop protector

not installing correctly on waydroid

app installs but the "magisk" part only gives a patch file option to install or update.
not sure what extra info i can give you.
host os: bazzite 39 (universal blue fedora 39 fork)

**邮政银行还是卡第一屏？

**邮政银行还是卡第一屏？
其他银行都能打开了，就邮政银行，大佬能看下？

Source code

Where can i find the source code

Zygisk not enabling on GrapheneOS

Enabling Zygisk and rebooting constantly says unknown signature and refuses to stay enabled.
Here is full log: magisk_log_2023-12-06T16.46.32.log

Momo detects zygisk

Setup magisk hide and hide list, momo still detects zygisk and ART parameter

Unable to hide magisk

Update:
Deleting the /data/magisk folder fixes these apps

Using Latest Kitsune Debug
No modules installed
Enabled Zygisk and Magisk Hide

Fails magisk specific checks in TB checker ,Root Beer
Also cant open digilocker

LOGS
magisk_log_2024-01-03T12.03.17.log

Screenshot

Screen is not turning on after forcing SU

Iinstalled, forced SU list, app told me I have to restart to take effect.
After that - black screen on reboot, reacts only on power button, displayiing Lockdown modal with "Power off" and "Restart" (both works ok).

Mobile root but not showing in kitsune mask?

I just flash kitsune mask using custom recovery my mobile root but module and SuperSU section is disable infact in app show mobile is non rooted check image.
But in root bear apk or tb checker apk found SU file say your mobile is rooted.All previous version working best. Please tell me if any solution.
Thanks ❤️




magisk_log_2023-12-10T20.24.02.log

This section has not been translated into the current language display

My phone keeps unrooting itself after rebooting

When rebooting the phone there's like a 50% chance that Magisk will get broken and needs reflashing in TWRP.
Funny thing is that even though the Magisk app says the root is gone other apps can still get root permission. Modules don't work though.
I'm attaching a screenshot and a log. No idea what's causing this. Before upgrading to Android 14 I never had these kind of problems.

magisk_log_2023-12-07T08.48.32.log

How to downgrade from R6573543B-kitsune (26401) to 26.4 Stable?

Directly installing the APK will result in it not opening and the version number showing 1.0.

Loss of Root

R6561D823, Loss of Root after enabling magisk hide.

CANT WORK NEW UPDATES

THE Great HuskyDG,
I want to ask is it necessary to update the app ? I am still using 26301 Canary so far because the all new Updates not working on my mobile. (after boot when the lock screen come the screen goes black whenever i open mobile lock).
Thanks. (Samsung A30s OS11 - Stock Rom)
Pls replyyy

Hide root will cause the camera to fail to start.

Issue Description

Whenever I try to either open or close sulist while having root hidden for this application, it causes the app to crash. Consequently, I am unable to open the app, or if it does open, I can't take photos or scan QR codes using the in-app camera functionality. Could you please advise on what might be causing this issue and how to resolve it?

magisk_log_2024-01-04T08.42.10.log

Zygisk doesn't work

For some reason, LSPosed doesn't work. I installed it, and I rebooted it the device many times.

"LSPosed is not installed" despite I can clearly see it enabled inside Magisk Manager.

Modules installed:

• Riru v26.1.7.r535.e2f6971ebe
• Riru - LSPosed v1.9.2 (7035)
• SELinux Permissive v2 [DISABLED IN MAGISK MANAGER]
• TrichromeLibrary Squoosh v1.4
• Universal GMS Doze v1.9.0
• YouTube ReVanced v18.45.41 by j-hc

Magisk log: magisk_log_2023-11-26T15.45.21.log

Magisk Installed on device -> R6561D823-kitsune

Mumu Android 12: Magisk magic mount bind mount built-in /system/bin/su su to magisk's mounted simlink su when /system/bin/su exists

HI @HuskyDG you fix the issue with zygisk (in Nox Player, for MuMu with inside zygisk after reboot say reboot to apply changes like the old in Nox Player but with enable and LSPosed latest show infinite boot, need this https://github.com/5ec1cff/ZygiskNext/suites/18119452689/artifacts/1044552394) to work properly, but again not install correctly in Nox Player Android 12 and MuMu Player Android 12 (this happens again in a old version of Magisk Delta and after you fix it but with Kitsune broke again), only if create manually folder sbin and send this file bootanim.rc with some modifications in /system/etc/init/, after reboot is working and detect the root
bootanim.zip

'Zygisk Next' does not take effect.

The latest version of zygisk next ci (v4-0.8.1-177) does not take effect.
Its developers said that they had raised the version requirements, requiring the version to be above 26402. I am using the 26404 version, but it still doesn't take effect.
The following picture is what its developer said.

Wish Bootloop Protection Return

It's a great feature to protect our phone from breaking down. But in the new version this feature is removed and many third party plugins with similar features are disabled.
This makes a lot of people afraid to update to the latest version, but the new version is really good and attractive, except for this one change.
Can the author tell the reason for removing this feature? If possible, can you add this feature back?
Thanks a lot!
Happy New Year!

not installing

not working in bluestacks.
i do this
1- unlock
2- launch
3- root patch
4- install kitsune mask app
5- install
6- install on system partition
7- it says success but when i restart it is not installed

Enforce SuList causes bootloop

Based on the empirical evidence of a bootloop being caused every time I select the Enforce SuList option under settings (with no apps in the actual SuList) on my Mi Pad 6, it seems to me there is something wrong with this option.

The device finally boots after 3 failed bootloops with the options disabled and MagiskHide itself works fine but as soon as I select the Enforce SuList option, it again enters into the bootloop dance.

resetprop

can you bring back resetprop without the some apps detect root

Uncompatible with Mumu/Nox player android 11/12

Keep asking for a reboot even after doing reboot.

HideNavBar no longer works on the lastest debug update

HideNavBar:
https://github.com/Magisk-Modules-Alt-Repo/HideNavBar

LOG:
magisk_log_2023-12-13T00.45.50.log

Details:
the nav bar cannot be hidden.

Termux: no su program found on this device

Termux can't get root access anymore after updating to latest kitsune: R6592CA0F

Termux is enabled in su list.

SafetyNetFix doesn't Work

Latest Delta version: Even with the module installed It simply doesn't work

It's a disappointment.

Sir u made some great modules for magisk. But it's unnecessary making magisk fork kitsune mask,it has no new features just built in 1)magisk hide 2) bootloop protection 3)extra boot options
.
But it's full of bugs.

System not booting after reverting to stock Magisk

Hi
I hope you can help

I was trying Magisk Delta (R65894F03-kitsune) (upgraded from Magisk using Kitsune Manager apk method, not zip). Everything seemed fine, but I noticed that MagiskHide mode was not working while Zygisk was enabled. Pressing the app icon for any hidden app would only show the app splash screen and not load the app properly. When removing the app from MagiskHide it would start up normally again.

So I disabled Zygisk, which resulted in LSPosed Zygisk module not loading... (as expected)
So then installed Riru module and LSPosed Riru, and after reboot Riru seemed to be loading fine according to logs inside Kitsune Manager, however LSPosed manager was saying that LSPosed is not installed.

At this point I thought Magisk Delta is the cause for Riru LSPosed not working, as earlier in the day LSPosed Riru version was working fine for me on official Magisk v26.4 ...

So then I installed official Magisk APK again and tried to "downgrade" back to official version using the in-app/apk flashing method (the same way I upgraded to Magisk Delta, but in reverse) -- however after reboot, this time my system is completely unbootable... It doesn't even reach the flashing SAMSUNG logo stage.

Stuck at this stage:

I've tried to rename the magisk delta apk to uninstall.zip, and flash it with TWRP, and also the same with official magisk.
I also tried to reinstall both versions this way, to no avail
Also tried to install Magisk-Manager-for-Recovery-Mode and use mm binary to disable modules from recovery
But I am stuck at this stage and cant reach system.

At the moment I'm doing a full TWRP backup of /data to see if wiping /data will result in a bootable system... but I suspect system/kernel image is somehow corrupted (similar to #3) and may need to flash stock boot img...?

Update: wiping /data did not work, so it appears the problem is elsewhere

Update 2: Hooray - I managed to restore booting by flashing stock (from ROM) boot.img, flashed magisk & necessary modules, restored /data backup, and now all is well 🙌🏻 Additionally Riru LSPosed is working again on stock magisk, so next step is to try make it work with Delta.

~~

So this could be a warning for other users that "downgrading" back to official magisk via the app should be avoided

Also, I suggest to modify kitsune manager app to disallow toggling MagiskHide if Zygisk mode is active...? this will prevent more confusion for other noobs

Getting Bootloop on Android 14 Pixel OS

Hi.

I have installed the latest kitsune and tried the debug version as well. I get stuck in soft bootloop.
Note that, canary version is working fine. Only Kitsune has this issue.

I have tried updating it through canary app, installed through recovery as a zip, renamed it to systemmagisk.zip and flashed it. Nothing works.

Device: Redmi Note 10 Pro
Rom: PixelOS Android 14

[EDIT]
It was Iconify that caused bootloop as it is not compatible with december a14 patch.

Kitsune Update 😔

Great HuskyDG Sir,
I want to ask is it necessary to update the app ? I am still using 26301 Canary so far because SystemUI.apk is not working on new update (after boot when the lock screen come the screen goes black whenever i open mobile lock).
Thanks. (Samsung A30s OS11)
Pls reply

great work pull up

keep it up good work Husky!

Android System Webview is crashing

Hello, have you experienced a similar problem when using Magisk Kitsune and after enabling "Hide the Magisk app" and updating my Google Play Store to the most latest version, The Android system webview app and Google Chrome may crash unexpectedly.

Installation problem on Redfinger cloud phone because of no selinux supported

Can't remove a module.

I installed a module universal gms doze which can be found here
https://github.com/gloeyisk/universal-gms-doze
It was installed successfully but after installation the name seemed abnormal , can be seen in the screenshot below.

Now i cant remove it. if i do it from the app it just crashes. I tried doing it from a file manager by deleting the folder /data/adb/modules/universal-gms-doze but didnt work. Same happened when i tried deleting it through recovery. Recovery says no such file or folder exists but it certainly is there.

Segmentation fault

The last four builds are causing many applications to crash. Many applications are now consistently throwing a "Segmentation fault" error. But everything is fine on the R657C2E65-kitsune build. On the rest of the builds following it, a lot of applications have started consistently throwing a "Segmentation fault" error.
magisk_log_2023-12-26T04.24.38.log

Root is detecting in latest version 26.4

My all banking apps logged out and saying device is rooted. Also I checked the root in root beer sample app. Edit:- I have flashed safety net fix mod 2.4.0 by displax magisk app is hide as well as apps are also hide is list

[Enhancement] safe root access

Instead of giving root access to apps you can specify any other uid. Such as system or shell. Heres an example

~$ whoami
u0_a456
~$ su
~$ whoami
system
~$

BlueTooth Issue

version name = R657C2E65-kitsune

modules list = Bluetooth Libarary Patch

When SUlist is enforce following errors come up. This blocks any devices like Samsung watch and stuff. Without SUList this error is not there. Attach is the bluetooth log.

12-19 16:15:21.073 2916 2916 I droid.bluetooth: [1219/161521.073737:INFO:com_android_bluetooth_btservice_BluetoothKeystore.cpp(97)] classInitNative: succeeds
12-19 16:15:21.074 2916 2916 D BluetoothKeystoreService: setBluetoothKeystoreService(): set to: com.android.bluetooth.btservice.bluetoothkeystore.BluetoothKeystoreService@f373703
12-19 16:15:21.077 755 755 E keystore2: keystore2::error: Rc(ResponseCode(7)), "In get_key_entry, while trying to load key info. 1002, Some("bluetooth-key-encrypted")"
12-19 16:15:21.077 2916 2916 D BluetoothKeystoreService: loadConfigData
12-19 16:15:21.079 2916 2916 D BluetoothKeystoreService: getCompareResult: 0

bluetooth_logs.txt

MagiskCore + Bootloop Protection

hello, please add magiskcore mode as well as bootloop protection as it was in version 25210, I recently installed the module on my Redmi A2+ smartphone, the module called bootloop and I had to do wipe data so that the smartphone booted, there is no TWRP Recovery on this smartphone and it is impossible to remove a bad module in another way.

Bluetooth

Enforce Sulist removes all the bluetooth devices and resets samsung gear watch

Looking to contact the developer

Greetings!

First of all, thank you for the great project! I was wondering how to get in touch with you to discuss a project.

Thank you in advance.