Magisk Module Systemless Debloater
- Thread starter zgfg
- Start date
It is a good place for dumb users who would not know to access something on /data
You need it only when installing/upgrading the module
For regular use and rebooting you can temporarily move it somewhere else
I see, thanks! I'll just store it somewhere else and put it back when I'm updating then.It is a good place for dumb users who would not know to access something on /data
You need it only when installing/upgrading the module
For regular use and rebooting you can temporarily move it somewhere else
I really like this module, thanks.
Im on a ported Miui14 rom for Redmi K20 Pro, having some issues with a few apps :
system/app/...
MIUIAccessibility (com.miui.accessibility)
MIUIPersonalAssistant (com.miui.personalassistant)
MiConnectService2_13_253 (com.xiaomi.mi_connect_service)
MINextPay (com.miui.nextpay)
MIUPTsmService (com.unionpay.tsmservice.mi)
those are not found when reinstalling the module.
Im sharing informations for Miui Accessibility (package manager app):
Mi Acessibility (name)
com.miui.accessibility (package id)
/system/app/MIUIAccessibility (path)
/data/user/0/com.miui.accessibility (directory)
/system/app/MIUIAccessibility/lib/arm64
Not sure why those apps actually are not found, have debloated around 35 other apps.
Im on a ported Miui14 rom for Redmi K20 Pro, having some issues with a few apps :
system/app/...
MIUIAccessibility (com.miui.accessibility)
MIUIPersonalAssistant (com.miui.personalassistant)
MiConnectService2_13_253 (com.xiaomi.mi_connect_service)
MINextPay (com.miui.nextpay)
MIUPTsmService (com.unionpay.tsmservice.mi)
those are not found when reinstalling the module.
Im sharing informations for Miui Accessibility (package manager app):
Mi Acessibility (name)
com.miui.accessibility (package id)
/system/app/MIUIAccessibility (path)
/data/user/0/com.miui.accessibility (directory)
/system/app/MIUIAccessibility/lib/arm64
Not sure why those apps actually are not found, have debloated around 35 other apps.
Last edited:
Go to Settings, Apps and take Uninstall - to uninstall updates for those apps
Please read post #1 how and why
Those apps cannot be uninstalled or disabled, those are system apps. Im gona add the package id for all aswell.
In the log file they are listed like that below "stock packages":
/system/app/MIUIAccessibility/MIUIAccessibility.apk=com.miui.accessibility
/system/app/MiConnectService2_13_253/MiConnectService2_13_253.apk=com.xiaomi.mi_connect_service
/system/app/MINextPay/MINextPay.apk=com.miui.nextpay
/system/app/MIUPTsmService/MIUPTsmService.apk=com.unionpay.tsmservice.mi
/system/priv-app/MIUIPersonalAssistant/PersonalAssistant.apk
this one i could solve by: MIUIPersonalAssistant -> PersonalAssistant
Edit: with root file browser i checked and they are exactly on the path written above
system -> app -> MiConnectService2_13_253 -> MiConnectService2_13_253.apk
..
(im using latest official magisk 26.1 and latest debloater version 1.5.3)
in the log file there is nothing else then:
MINextPay --- app not found!
MIUIAccessibility --- app not found!
MIUPTsmService --- app not found!
MiConnectService2_13_253 --- app not found!
Last edited:
Please attach your SystemlessDebloater.log
Also, do you use old SystemlessDebloaterList.sh
or the new
SystemlessDebloater.cfg
Please attach both or the one of them you use
Also, are you on the latest v1.5.3 - if not, please first update to v1.5.3
Btw, I'm on Xiaomi.eu Stable 14.0.8 (Xiaomi Mi Late 5G NE) and I successfully debloat also that MiConnectService (under that name)
My cfg, sh and log files are zipped and attached
Cannot guarantee that on your MIUI all apps have the same name but try and send your sh, cfg, log as above
Last edited:
Im using the new SystemlessDebloater.cfg. Have attached both log and cfg below.
Yes im on latest magisk and debloater.
Yeah its strange, i debloated so many system apps (35) witouth any problem, no clue why the mentioned ones (4) dont work. There is no typo, case sensitive issue, space or anything different to the other system apps.
Im on Miui Ori 14.0.1, android 12 (its a ported rom for redmi k20 pro / mi 9T pro)
Last edited:
I downloaded your zip but neither MiXPlorer nor Windows could extract
They see the content (two files) but extracting fails - eg, on Windows, err 0x80004005 when attempting to extract
Please download by yourself and make sure that it properly extracts
You can extract my zip correctly both on MiXplorer and Windows
(I will mainly use MiXPlorer - if I need to use some tar or whatever on the PC it will take much longer time - hence pls make sure that MiXPlorer can properly extract)
i have been using 7-zip on pc. I unluckily dont have mixplorer anymore.
I have renamed SystemlessDebloater.cfg to SystemlessDebloater2.log.
So you should be able to download both directly from xda and open them with editor witouth using any archive program.
Yeah, then it was named zip but wasn't standard zip
Download and extract, copy the two files mountList.sh and service.sh to /data/adb/modules/SystemlessDebloater
Overwrite the two existing files you will find there with these new ones
You will need MiXPlorer or some root explorer
(or TWRP or adb) - please find your wayIt's important that files keep the exact names as above, eg, that Windows or something (if you use) do not append txt extension or so
Also, file names are case sensitive - the scripts must keep their names as in my zip file
Do not reinstall module ! - only reboot the phone and then send me the service.log file from the same directory
Ok, i have followed the steps carefully and in attachment you can find the log file.Yeah, then it was named zip but wasn't standard zip
Download and extract, copy the two files mountList.sh and service.sh to /data/adb/modules/SystemlessDebloater
Overwrite the two existing files you will find there with these new ones
You will need MiXPlorer or some root explorer
It's important that files keep the exact names as above, eg, that Windows or something (if you use) do not append txt extension or so
Also, file names are case sensitive - the scripts must keep their names as in my zip file
Do not reinstall module ! - only reboot the phone and then send me the service.log file from the same directory
Edit: the system apps seem to be debloated, all 4.
What could be the reason they are not being found through the usual process ?
Last edited:
Per log, all apps, incl. those four are debloated
Use root explorer (like MuXPlorer - root must be granted) and go to /system/app/Joyose/
But not from TWRP - this is systemless module, no hard changes, just mounts by Magisk every time you reboot to the System
and check how Joyose.apk looks like (that is one of the app you did not have problem with)
It will be chmod 666, size 0 bytes
You can also check from Terminal emulator - see my screenshots but I did for my debloated Easter egg.apk
Then do the same for your four apps you had a problem with - all are on /system/app
Eg:
/system/app/MiConnectService2_13_253/MiConnectService2_13_253.apk
You can read their paths in the mountList.sh I sent you
You can also find their paths in the SystemlessDebloater.log you sent me - you just need too search further down through the file for eg MiConnectService2_13_253
We we'll check another time why it failed to find them regular way - but you see now, how you can find in the SystemlessDebloater.log, add them manually to mountList sh and reboot (I have upgraded my phone with Factory reset and being busy to have it ready for daily use again)
Attachments
Last edited:
Ok, thanks for your time, tell me if you need further informations to fix the issue why it failed to find them.
Meanwhile i will use the mountlist.sh to debloat the other apps, thanks.
I will add you aswell the screenshots from MINextPay (one of the problematic ones) and Joyose (debloated). And if you wanted me to sent the informations in attachment of the app "undebloated" i will share them aswell, tell me.
Attachments
Last edited:
Is there a difference between the system debloater in this thread and this one here? This one just has a list of the system apps, and you choose a number to input in CMD, and it debloats it.
https://forum.xda-developers.com/t/module-terminal-debloater-v17-3-2-debloat-systemlessly.3584163/
And what about this one that is on F-droid? You don't have to use a terminal command, but instead they have an app with a list of your apps ready to debloat instead of typing command line.
The one in this thread looks really complex for a noob like me, but these one with the especially the last one with the separate app, looks easier. But I care about complete wrote of the system app as well as any trace data. Which one would be better?
https://forum.xda-developers.com/t/module-terminal-debloater-v17-3-2-debloat-systemlessly.3584163/
And what about this one that is on F-droid? You don't have to use a terminal command, but instead they have an app with a list of your apps ready to debloat instead of typing command line.
The one in this thread looks really complex for a noob like me, but these one with the especially the last one with the separate app, looks easier. But I care about complete wrote of the system app as well as any trace data. Which one would be better?
Unluckily i have replaced the SystemlessDebloater.cfg and SystemlessDebloater.log file when copied the download folder of my old installation above the new installation. (somehow did not ask )
Is there any way to get it back "SystemlessDebloater.cfg" ? I did hours of trial and error of app debloating, with a lot of comments.
Edit: in case not i could atleast copy all debloated apps from mountlist.sh
And on this rom i did not have issues with "not found" (successfully debloated ~75 apps)
Is there any way to get it back "SystemlessDebloater.cfg" ? I did hours of trial and error of app debloating, with a lot of comments.
Edit: in case not i could atleast copy all debloated apps from mountlist.sh
And on this rom i did not have issues with "not found" (successfully debloated ~75 apps)
Last edited:
Yes, if you still have mountlist.sh, all debloated apps are listed there
Please open your log, you will see:
Input DebloatList=""
Hence, check do you do everything correct:
- Remove SystemlessDebloaterList.sh
from Download folder (if you have it)
- Make sure that your conf file is in Download folder, named exactly as:
SystemlessDebloater.cfg
Eg, it must not have (additional) txt extension (added by Windows if you edited on the PC)
- Reinstall the module
- While installing, it will list the input list of apps to debloat
- You can also open the log file and check yourself did it read the input list
- If it again says that that the input list is empty, double-check every step above
- After the successful installation (when the input list won't be empty), reboot
Module guaranteed works on your MIUI 14, A13 but as described above, some of your steps were not correct and the module, at the time of installation (!!!) did not find SystemlessDebloater.cfg (named exactly as that, with no additional/different extension) in the Download folder on Internal memory
As above, cfg file must be there when Installing (not later, after you installed)
There is an issue with the import code and new version of busybox.
github.com
Fix regex by ipdev99 · Pull Request #4 · zgfg/SystemlessDebloater
Due to update in Magisk's BusyBox. BusyBox v1.36.1-Magisk (2023-09-02 05:30:11 PDT) multi-call binary. The current Magisk sed errors out when generating the "$TmpConfigFile" sed: bad regex '^\s*$':...
github.com
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
4I'm so sorry to derail the thread, but I had a similar problem with my Moto G Stylus 2022 4G and I wanted to share a possible solution. Assuming the Youtube app came pre-installed on your phone, follow these steps: 1) Open Youtube app info window and uninstall all updates, clear data/cache 2) Install Systemless Debloater Module and add Youtube to SystemlessDebloater.cfg then Reboot 3) Install your preferred Youtube APK 4) Install TeMeFi app (from XDA thread) 5) Open TeMeFi -> Application Info -> Detach Package from Playstore -> DETACH -> com.google.android.youtube -> 3 - Invalidate the data, block any... -> YES - I accept full responsbility 6) Now check Play Store, Youtube app won't be able to reattach and your preferred apk will remain intact.
Also I wanted to report that the v1.5.3b fix is working with Magisk 26.3 on my XT2211-2. Thank you so so much for the fix and for this wonderful module in general @zgfg
Before, I was using Terminal Debloater but that module is a bit outdated and was not able to scan apps in the /oem/ or /system_ext/ folders. I was also using Universal Android Debloater, but that application couldn't remove apps like Carrier Hub or the T-Mobile app. Today I finally decided to make the complete switch to Systemless Debloater and I love it! I was able to uninstall more than 110 apps/bloatware+ all with just one module and now my phone runs so fast. 
Thank you for sharing your amazing work with the world.2
This module overlays the preinstalled YouTube app with an empty (zero byte) file.<SNIP>
I debated the original YouTube app. And installed the REX YouTube app.
When I reboot the phone, your module removed the new YouTube app, and when I disable your module then after I reboot the phone I get the original YouTube app
Is there anything to do ? Please help
On boot, the preinstalled version of YouTube can not be loaded since there is nothing to load.
Hence the second part of your findings.
"and when I disable your module then after I reboot the phone I get the original YouTube app"
The first part is wrong.
"When I reboot the phone, your module removed the new YouTube app"
This module does not target apps installed in userdata so, it can not remove the new YouTube app that you installed.
What you seem to be describing sounds like is the "mod" version(s) of YouTube you are trying is not being loaded on boot.
Depending on how the "mod" version is being installed, could be security removing the "mod" version on boot.
Or something completely different. ¯\_(ツ)_/¯
Note:
If the "mod" version you are installing is a newer version than the stock preinstalled version, you do not need to remove the preinstalled version.
On boot, system will find both and load the newer version.
If the newer version can not be loaded, it will remove the newer version apk file and load the older version.
Cheers.
2There is an issue with the import code and new version of busybox.
Fix regex by ipdev99 · Pull Request #4 · zgfg/SystemlessDebloater
Due to update in Magisk's BusyBox. BusyBox...
github.com
22Hi Zgfg,
Thanks for great module! It is the only one which worked properly on A13. Samsung has some of system level ones in /system_ext and yours found it properly. The terminal_debloater (debloat) didn't work as it is not able to handle "/system_ext".
Given it seems like you take bug reports here instead of GitHub, here is what I did run into.
With:
### SystemDebloaterList.sh
```
DebloatList="
GmsCore
GoogleServicesFramework
Phonesky
"
```
It debloats it nicely and generates
### SystemlessDebloater.cfg
```
## My list of stock apps for debloating:
GmsCore
GoogleServicesFramework
Phonesky
```
Any subsequent run with just `SystemlessDebloater.cfg` file or together with `SystemDebloaterList.sh` doesn't set properly the DebloatList.
I've looked through the code and it looks good to me, tried it manually as well and looks good. Only when run from Magisk level on Install, somehow it doesn't get it right. (Magisk v26300). -
18Magisk Module Systemless Debloater
Download:
GitHub - zgfg/SystemlessDebloater: Select and systemlessly debloat preinstalled system apps. Supporting up to System As Root (SAR), Dynamic partitions and Android 13. Module must be installed through Magisk app, not TWRP
Select and systemlessly debloat preinstalled...
github.com
Wiki pages by @ipdev:
with his examples of apps that can be debloated (Android, Google, Oppo, Samsung, Xiaomi, LineageOS):
*** Yet another System(less) debloater, how and why?
- Systemless means that all changes made are active only when Magisk is loaded and module is enabled.
For OTA or anything, just disable the module (or boot without Magisk) and your system partitions are no more affected
- For Android up to 9 and/or 10 (depending on devices), system partitions were read-write, hence hard-debloating by use of eg TWRP, Titanium, etc (to delete the pre-installed system apps) was possible
This is no more possible for the phones released with Android 10 and higher.
System (System As Root, Dynamical partitions) becomes read-only on the file-system level and stock apps could be debloated (the same holds for any changes on the system partitions) only by the systemless approach - by use of Magisk to dynamically overlay the required changes at boot time
Hence, this module also uses the Magisk REPLACE mechanism and dynamical mounting through the module's service.sh script
- The module debloates only (stock) apps pre-installed to the system partitions, traditionally named as /system, /system-ext, /product, /vendor and /apex; plus additionally on A12 and A13 devices, variably named system partitions like /india, /my_bigball, etc
Hence sorry, to debloat user apps installed to /data, please use the other methods (first of all, just simply uninstall them or at least uninstall their updates)
- Originally I started development with Xiaomi Mi 9T (MIUI 10-12.5, Android 10-12) and later continued with Xiaomi 11 Lite 5G NE (MIUI 12-13, Android 11-12). However, the module relies on the common Magisk overlay mechanism and the list of apps to be 'debloated' is configurable hence there are many users who successfully use this module on the various other devices (like Pixel, Samsung, One Plus, etc.), with the stock or custom ROMs, and with up to Android 13
- Original, default list coming when the module is installed will be empty - user must define then himself which apps should be debloated, depending on his device, ROM and preferences
To (re)configure the list of apps for debloating, simply edit the (textual) /Download/SystemlessDebloater.cfg config file on Internal memory.
Module automatically installs the config file with instructions inside but with the empty list
(Re)configure your list of system apps you want to debloat, reinstall the module (always through the Magisk Manager, not TWRP) and reboot - to take your changes in effect
You only need to provide the proper names (not package names) for the preinstalled system apps, the module will find their exact System paths
- However, the user bears the risks and responsibility himself (device may no more boot when certain system apps are removed/debloated) but the Troubleshooting section below provides instructions how to recover, even from the bootloop cases
Nevertheless, whenever you want to 'debloat' some service or app you are not familiar with, please google first to find what that app is really about and is it generally safe to be debloated (on your but also on the other phones and even by other methods, it doesn't matter)
Don't be afraid of the module and debloating, but be cautious what are you going to debloat
*** Installation
- Download the latest module from GitHub - scroll down, open Assets and find the latest v1.5.3 zip:
https://github.com/zgfg/SystemlessDebloater/releases/tag/153
- In Magisk app (manage), open Modules tab and take Install from storage, navigate to the downloaded SystemlessDebloater.zip (as is, do not unzip)
Read what Magisk prints while installing and find the module's log in /Download/SystemlessDebloater.log file on Internal memory
To finish the installation (it applies to all Magisk modules), reboot the phone
- First time the module will not debloat anything - it will just create the input/config file /Download/SystemlessDebloater.cfg on Internal memory
Open that config file, read the instructions in the file and fill your own list of app names for debloating - look at the commented examples you will find in that config file
- Save the config file, reinstall the module and reboot.
Inspect the log and consult the Troubleshooting section below if needed
- To find what system apps you have on your phone and what are their exact names, scroll down through the SystemlessDebloater.log to the "System apps, not debloated" section
Find e.g. a line:
/system/app/Email (com.android.email)
Then copy/add just the Email name (supposed that you want to debloat the built-in Email app) into the SystemlessDebloater.cfg config file
Repeat for the other apps you want to debloat. Then reinstall the module (only on the reinstallation, module processes the config file) and reboot
Fine tune your list of apps for debloating but every time reinstall the module and reboot
- Last but not the least: Once debloated, apps can no more be found (until you reconfigure, disable or uninstall the debloater) under the Settings / Apps
Hence, if you want to delete their cache or data, do Clear cache/data before debloating the apps
Moreover, before trying to debloat any app, look first if you could simply Uninstall that app (ie, if it was a user and not the system app) from Settings / Apps
If Uninstall is not available for that app, try to Uninstall updates: updates are also installed to Data while SystemlessDebloater 'debloats' only from the System - hence the app's update on Data may still remain there
*** Troubleshooting
- What if I eg have configured the app EMail to debloat, but the app is still present?
Check if you have missed to perform Uninstall / Uninstall updates from Settings, Apps - perform, reboot and test again
Check if you have miss-spelled the application name - correct in the config file SystemlessDebloater.cfg, save, reinstall the module and reboot
App names are cases sensitive - eg, the correct name might be Email, not EMail
- To help yourself, use eg Package Manager app (from Playstore) where you can search for all the apps/services, find their exact names and installation paths (to see are them System or User apps)
- What if I change my mind and I want to un-debloat and use Email, but to debloat now eg, Chrome browser?
No problem, reconfigure the list in SystemlessDebloater.cfg, save, reinstall the module and reboot
- What if after a week or so, I realize that some functionalities on the phone were affected?
Sorry, you had decided to debloat the 'wrong' apps/services
Google about which app(s) are safe to debloat or not, reconfigure your list in the config file, reinstall the module and reboot
Or disable the module and reboot, to figure out was the problem really due to debloating
- Oops, what if I have a bootloop (phone does no more boot since the 'wrong' apps were debloated)?
If you have TWRP with the read/write access to Data, navigate to /data/adb/modules/SystemlessDebloater and by using Advanced / File explorer from TWRP, create a dummy file named disable (without extension) in that folder
Reboot and Magisk will boot but with the debloater disabled - hence, all the previously debloated apps will be un-debloated now (to see if debloating was really responsible for the bootloop)
Instead of dummy file named disable, put the remove dummy file to trigger Magisk to uninstall that module on the next reboot (all that applies to any module possibly causing your bootloops)
If the proper TWRP is not available for your device and ROM, boot to the Android Safe Mode - google for a key-combo to boot in, for my Xiaomi it takes (re)booting with Vol+ and Vol+ pressed simultaneously
Don't do anything in Android Safe mode but reboot then to 'normal' mode - Magisk will boot now with all the modules disabled (this method does not work for Magisk v20.4 or earlier)
You will have to re-enable MagiskHide/DenyList (don't worry, your list of apps to hide the Magisk from was not lost), re-enable the other modules, correct SystemlessDebloater.cfg, reinstall debloater and reboot
There is also a third method (adb wait-for-device shell magisk --remove-modules), but search yourself and read about from the Wiki Documentation on the Magisk GitHub page
*** Enough for the theory, install now and practice debloating4New version v1.5.0 is released:
Release Systemless Debloater v1.5.0 · zgfg/SystemlessDebloater
Automatically search through packages to find...
github.com
With Android 13 there are now ROMs where the additional system partitions are variably named like /india, /my_bigball, etc - the module now automatically finds and includes those names into the list of partitions to be scanned for debloating
Also, debloating from /apex is now supported - but be careful, services pre-installed to that partition are usually essential for the proper booting and functioning of your device
Of course, the module is still only for debloating the System apps, for user apps on /data partition use the other methods (simply uninstall the unwanted user apps or disable them by pm disable command, etc) - see also the OP instructions4I'm so sorry to derail the thread, but I had a similar problem with my Moto G Stylus 2022 4G and I wanted to share a possible solution. Assuming the Youtube app came pre-installed on your phone, follow these steps: 1) Open Youtube app info window and uninstall all updates, clear data/cache 2) Install Systemless Debloater Module and add Youtube to SystemlessDebloater.cfg then Reboot 3) Install your preferred Youtube APK 4) Install TeMeFi app (from XDA thread) 5) Open TeMeFi -> Application Info -> Detach Package from Playstore -> DETACH -> com.google.android.youtube -> 3 - Invalidate the data, block any... -> YES - I accept full responsbility 6) Now check Play Store, Youtube app won't be able to reattach and your preferred apk will remain intact.
Also I wanted to report that the v1.5.3b fix is working with Magisk 26.3 on my XT2211-2. Thank you so so much for the fix and for this wonderful module in general @zgfg Before, I was using Terminal Debloater but that module is a bit outdated and was not able to scan apps in the /oem/ or /system_ext/ folders. I was also using Universal Android Debloater, but that application couldn't remove apps like Carrier Hub or the T-Mobile app. Today I finally decided to make the complete switch to Systemless Debloater and I love it! I was able to uninstall more than 110 apps/bloatware+ all with just one module and now my phone runs so fast. Thank you for sharing your amazing work with the world.4Thanks a lot to @ipdev for discussing and sharing ideas, encouraging and for successful testing on Xiaomi Poco F2 (debloater found most of the same MIUI apps as above) and OnePlus 5T
Also, thanks for your successful test on Pixel 3aXL with Android 11:
Works on Pixel 3aXL. (Stock Android 11. Magisk canary.)
Attached the SystemlessDebloater.log from 3aXL.
And the SystemlessDebloaterList.sh I use for testing. (remove the .txt)4Hello again
Pretty much figured out the above, got some 160 odd apps leftover with everything seemingly still working. The last bit I found is that removing EuiccService breaks Background usage limits app selection within Battery and Device Care.. Hope it helps someone. Btw - I do use System App Remover ROOT (for now) to remove whatever apps it can remove, e.g. not Apex. Might update .sh below at some point again.
[ *** = temp disabled FYI | ymmv ]
Found another (unrelated) issue in the meantime on my Samsung Android 13 journey, here: https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/post-88010513
[ Fwiw, I could either give up on restricting Google Play Services but knowing that it does request e.g. cam and mic access annoys the .sh out of me. Or I could go and use something like AndroidFaker and AppOps but it's just not the same (yet) as XPrivacyLUA. At that rate, might as well buy an iPhone soon.. :/ ]
