English | 简体中文
A Magisk module to remove bloatware in systemless way / 一个无需修改 system 分区即可移除预装软件的 Magisk 模块
Magisk (Recommended!) 丨 KernelSU (Recommended!) 丨 APatch (Not test yet)
Bloatware Slayer removes bloatwares in systemless way, using specific mount methods from Magisk, KernelSU and APatch. Below are the steps:
- Install Magisk / KernelSU / APatch
- Download and install Bloatware Slayer
- Use App Manager to search for the system app names you want to block, open the app details page and copy source directory. Root Explorer, MiXplorer to manually locate and copy the directory names of pre-installed apps under
/systemis okay too. - Open the file
/data/adb/bloatwareslayer/target.confand add the directories of the bloatwares obtained in step 3, one per line. - Save the changes to
target.confand reboot your device to observe the results.
For example, I need to uninstall XiaoAi Voice Assistant, so I will get the directory XiaoAi Voice Assistant located in by AppManager and soon get its name
VoiceAssistAndroidT, then copyVoiceAssistAndroidTand add it intotarget.conf, save the changes and reboot my device.
target.confsupports commenting out entire lines with the "#" symbol. Bloatware Slayer will ignore commented lines and empty lines.- Bloatware Slayer supports custom paths, for example:
/system/app/MiVideo. In this case, Bloatware Slayer will directly process the custom path without scanning other system directories. Since most modern devices use SAR (System-as-root), the resource directory names you see in AppManager may not start with/system(for example,/product/app/Scanner). To ensure the mount works, you need to add/systemmanually to the beginning of paths. Otherwise, Bloatware Slayer will ignore them.
Bloatware Slayer supports adding
/systemto the APP path directly since1.4.1, adding/systemprefix manually is not enforced anymore. If item/systemexists intarget.conf, this item will be ignored.
- To save the time and reduce the cost of resources, now Bloatware Slayer will update the items of
target.confinto the system path bloatwares located in automatically in each time booting. You can read the chapterConfig Fileto know. - If the resource directory starts with
/data, it means the app was installed as first booting after the initial of ROM setup. You can uninstall it manually and should NOT add it totarget.conf, as Bloatware Slayer's processing will not affect such apps.
Starting from version v1.2.1, Bloatware Slayer supports manually enabling or disabling the following features. Please open the configuration file /data/adb/bloatwareslayer/settings.conf to view and modify the settings if needed.
brick_rescue: To set if module inbuilt brick rescue mode has enabled. The default value istrue.
If setting
brick_rescue=false, Bloatware Slayer will do NOTHING if detecting device cannot boot.
brick_timeout: Sets the timeout for determining if the device has bricked. It requires a positive integer, measured in seconds.
If it is not set in
settings.conf, the default value is300 seconds (5 minutes).
disable_module_as_brick: Determines whether the module should automatically disable itself when the device is detected as bricked. By default, it is set totrue(enabled), but you can set it tofalseto disable this feature.
When enabled, the module will disable itself to prevent further issues. If you set it to
false, the module will only skip mounting without disabling itself. This allows you to troubleshoot and reboot the system after removing unstable items fromtarget.conf, without needing to re-enable the module via Root manager manually.
last_worked_target_list: The worked target list at the last time feature. Bloatware Slayer will backup the latesttarget.confcan boot successfully, and restore it and reboot again as detecting device cannot boot. It is set totrue(enable).
This options cannot work with
disable_module_as_brickenabled. That means if enabledisable_module_as_brick, the optionlast_worked_target_listwill NOT take effect logically.
slay_mode: the method of Bloatware Slayer blocking bloatwares.
MB(Mount Bind), a method that is generally applicable to various Root solutions in most ROMs.MR(Magisk Replace), a method specific to Magisk.MN(Make Node), a method available for Magisk 28102+、KernelSU, and APatch. Insettings.conf, the default value of Bloatware Slayer isMB(Mount Bind), since the method has the highest compatibility.
mb_umount_bind: Asslay_modesetting toMB(Mount Bind) and this option is enabled, Bloatware Slayer will unmount the mount points created by itself and hide the traces by module itself. It is set totrue(enable) by default.
You do NOT need to change this option usually.
system_app_paths: Support customizing the scan of system directories the bloatware located in. Paths starts with/and separated by spaces.
For example:
system_app_paths=/system/app /system/priv-app.
auto_update_target_list: Control the behavior whether to update the items intarget.confto the paths of bloatwares apps during each boot. By default, it is set totrue(enabled) to speed up system boot.
If you prefer to keep your custom comments or retain items in
target.confthat were not found by the module, you can set this tofalse.
update_desc_on_action: Updates the module status description with denylist enforcing status of Magisk and Zygisk Next, and the status when the module is disabled or uninstalled. It is set totrue(enable) by default.
Please read Q&A.
Logs are saved in /data/adb/bloatwareslayer/logs, you can review them and submit them when reporting issues.
When reporting issues, please simply zip the entire logs folder and upload it.
Bloatware Slayer has a built-in brick recovery method. If the device takes too long to boot, it will automatically disable the module's mounting functionality and reboot.
After rebooting, you will see a message in the module status.
Please adjust target.conf by removing entries that should not be disabled and reboot again.
The default wait time is 300 seconds (5 minutes), meaning Bloatware Slayer will disable itself and reboot after waiting for 5 minutes.If your system is updating, temporarily disable or uninstall this module and reinstall it later is recommended.
- Xiaomi HyperOS 2.0.105.0, Android 15, Device: Redmi Note 9 Pro 5G 8+256GB (gauguin, ported ROM)
- Root: Magisk Alpha 28102,28103,28104,29001
- Xiaomi MIUI 12.5.4, Android 10, Device: Redmi Note 7 Pro 6+128GB (violet, stock ROM)
- Root: Magisk Alpha 28102,28103,29001
- DroidUI-X，Android 14，Device：Redmi Note 7 Pro 6+128GB (violet，AOSP based ROM)
- Root: KernelSU with Magic Mount 1.0.3
- Root: KernelSU with OverlayFS 0.9.5
- Flyme 8.0.5.0A, Android 7.1.2, Device: Meizu M6 Note 4+64GB (m1721, stock ROM)
- Root: Magisk Lite 25205
- Derpfest 15.1 Stable, Android 15, Device: Redmi Note 7 Pro 6+128GB (violet, AOSP based ROM)
- Root: Magisk Alpha 28103,28104,29001
- If you encounter any problems, please click here to submit feedback.
- Pull Request is always welcome to improve this module.