Magisk Module Systemless Debloater

[kaefers]

Ok so you didn't need to manually edit service.sh, seems it found all from /apex

There are three you appended BAK to theie names and they were not found - you intentionally 'disabled' them for debloating?

Everything worked just fine, no need to even edit the service.sh

And yes, my way of preventing them from being debloated temporarily - one of them caused a bootloop when debloating, need to still check which one. Was busy with the stuff in the post below!

 

[kaefers]

I spent a lot of time trying to figure out why I got random Android WebView crashes when debloating. Everything seemed to be working just fine (I been debloating for years and got my special list) so wasn't sure what was happening.

Long story short - various apps crashing happens only when uninstalling "UwbApplication" aka "com.samsung.android.uwb". Which is odd enough.

More odd is that the crashing can temporarily be stopped by clearing the cache of Google Play Services ...

Either someone did some pretty bad coding or there are some dependencies that probably should not exist, go figure.

Be happy to share my final list once I am eventually happy with the result which will take some time ;]

 

[kaefers]

Hello 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.. :/ ]

 

[zgfg]

Hello 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.. :/ ]

Sorry, I'm not a Sammy user but my eyes caught that you 'debloat' KnoxCore (and couple of other Knox* services)

Are there any side-effects or benefits?
I'm particularly interested about root detection (by some banking and similar apps) or passing SafetyNet (deprecated) / Play Integrity API (successor of SN).
Ie, Knox (on Samsung) should manage the info if Bootloader was unlocked or not

 

[kaefers]

Sorry, I'm not a Sammy user but my eyes caught that you 'debloat' KnoxCore (and couple of other Knox* services)

Are there any side-effects or benefits?
I'm particularly interested about root detection (by some banking and similar apps) or passing SafetyNet (deprecated) / Play Integrity API (successor of SN).
Ie, Knox (on Samsung) should manage the info if Bootloader was unlocked or not

Hey! Thus far, nothing that I have noticed.

My experience with SafetyNet etc as per the link in my post above, a bit upset about the Google Play Services <> LSPosed issue I come across. | I guess I could technically see if there is any difference when not debloated..

Benefits.. = "illusionary peace of mind" :]

The only thing I didn't bother removing was kgclient / Device Services to avoid getting the screen locked.

My overall goal is to have as much control over permissions (for the sake of it) and running my handful of apps that complain about root, at the same time.

I am but a user but happy to try out whatever to get to that stage. I did notice for example that AFwall isn't an LSPosed module anymore, doesn't show up anymore with LSPosed. I wonder if it's the end of things like XPrivacyLUA. Giving Google Play Services all it wants to know got to be the first step to making value spoofing and permission management pointless if apps can just get a bunch of info via Google Play Services even if they are restricted themselves...

Let me know if you want me to try something

EDIT: I guess the issue isn't all that new ...
https://www.reddit.com/r/androidroot/comments/lw26hd/_/gpt1msz

 

[zgfg]

New version v1.5.0 is released:

Release Systemless Debloater v1.5.0 · zgfg/SystemlessDebloater

Automatically search through packages to find SAR mount points

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 instructions

 

[dkionline]

Still funny, i can delete MiVideo but not MiMusic. @zgfg, What about delete stuff in vendor partition?

 

[zgfg]

Still funny, i can delete MiVideo but not MiMusic. @zgfg, What about delete stuff in vendor partition?

It's not really deleting but mounting over, but it should work

Check what it says in the log file - maybe Not found if the name was not correct.
Scroll down in the log file to find all apps on the System (incl. /vendor)

 

[galih_ken]

Sorry if it has been asked or I haven't read hard enough. I can't debloat MibrowserGlobal, it says "app not found" in the log.

 

[zgfg]

Sorry if it has been asked or I haven't read hard enough. I can't debloat MibrowserGlobal, it says "app not found" in the log.

At the bottom in the log you have a list of all the system apps installed on your phone

Carefully go through that list and find your app - maybe you put the wrong name (name is case-sensitive), miss-spelled, etc

Please read the post #1 about finding and putting the correct names into DebloatList

PS: On my Xiaomi.eu, MIUI 13, there is the app:
/system/priv-app/MiBrowserGlobal/MiBrowserGlobal.apk

Hence for me the correct name is MiBrowserGlobal, not MibrowserGlobal (case sensitive), and I successfully debliat that app

 

[xadad]

After debloat all google app it stuck on logo, how can i reinstall packges?

 

[zgfg]

After debloat all google app it stuck on logo, how can i reinstall packges?

If you could boot:

Remove the apps you shouldn't have to debloat from DebloatList in SystemlessDebloaterList.sh, and then 'install' this module again.
On the next reboot, only the apps from your edited DebloatList (processed at the time of re-installing the module) will be debloated, the others will be un-debloated

Or disable or uninstall the module and reboot.
All system apps will be un-debloated

---

However, since you cannot boot now, use TWRP and its File Explorer, go to /data/adb/modules/SystemlessDebloater/
and put there an (empty) file named exactly: disable

That will disable the module and next time you reboot, all system apps will be un-debloated

Then edit the DebloatList and re-install the module again

---

There are two other options to disable a module (any module)

Go to the official Magisk GitHub and read the Wiki:

GitHub - topjohnwu/Magisk: The Magic Mask for Android

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com

Find there a chapter about disabling/uninstalling modules:

a) by use of booting to Android Safe mode (later when you reboot to system, all Magisk modules will be disabled)

b) or by use of
adb wait-for-device shell magisk --remove-modules
(not sure if that's the correct command - read that Magisk Wiki)

Once the module is disabled, system will boot with all your system apps un-debloated

--

If you uninstall Magisk, all modules will be uninstalled, hence also this one, and your apps will be un-debloated, too

Also, if you just flash your original boot.img (without the Magisk patch), system will boot without Magisk, hence also without the module(s) and therefore with all your system apps un-debloated

(But next time you boot with Magisk, Magisk will find and initialize all the module(s) and therefore your system apps will be debloated again per your previous wrong DebloatList)

As a last resort, Factory reset or wiping the Data partition will also delete the module (actually, all Magisk modules) and you will boot then with all the system apps un-debloated

---

Anyway, as stated in the post #1, debloat the apps on your own responsibility

With the crucial system apps debloated, the system may no more boot

If you have TWRP, you can 'fix' it easily

But if there is no proper custom recovery available for your device, you're in troubles and your best bet will be disabling the modules by one-time booting to Android Safe mode or by the mentioned adb command (but those Magisk tricks are not full-proof and may not work on all devices)

Or, in the worst case by Factory reset (wiping Data)

 

[zgfg]

New version v1.5.1 released:
https://github.com/zgfg/SystemlessDebloater/releases/tag/151

---

Since v1.5.1, Systemless Debloater module supports a new SystemlessDebloater.cfg config file - thanks to @ipdev

Update will create this new config file and transfer your DebloatList

Please delete then your old SystemlessDebloaterList.sh input file and read and use the new config file instead

---

For those who install the module first time, module will create that empty SystemlessDebloater.cfg config file (on Internal memory, Download folder)

Open the config file and read the instructions there

---

Benefit:

With this new config file, you can list but comment out certain apps, eg:

## My list of stock apps for debloating:
Velvet   # Google app
Chrome
# YouTube
Mail

Hence, only Velvet (Google app), Chrome and Mail apps will be debloated

But if you uncomment YouTube (by removing hash sign # in front of the app name), and reinstall the module - then all four apps will be debloated

Observe also how the hash sign # can be used to comment/describe a particular app, like Velvet

 

[m0han]

New version v1.5.1 released...
.... For those who install the module first time, module will create that empty SystemlessDebloater.cfg config file (on Internal memory, Download folder)....

For any change to the config file to take effect, a re-installation and reboot is required, I suppose. Also, from what I see, a space is required after each # sign, right?

 

[zgfg]

For any change to the config file to take effect, a re-installation and reboot is required, I suppose. Also, from what I see, a space is required after each # sign, right?

For a change in the cfg file re-installation of the module and reboot is required

Hash (for commenting out an app name) does not need to be followed by space (spaces are ignored) - space in the example was added for easier reading

Actually, the hash sign # comments out/ignores the rest of that line, ie, anything on the right side of that sign - like in the shell programming

 

[ipdev]

Hi all.

Hopefully this will help with the updated config script.

Still a Work-In-Progress.
Especially the Community List.
Quick edit updating it to the new v1.51.1 release.​

WiKi Pages (GitHub).
Config Script - Link
Community List - Link

Cheers.

 

[zgfg]

Hi all.

Hopefully this will help with the updated config script.

Still a Work-In-Progress.​

Especially the Community List. ​

​

Community List - Link

Usually I debloat additionally:

XiaomiSimActivateService # does not affect (dual) SIM calls and SMSes

MiShare

MiuiScanner

ims

CneApp

PersonalAssistant

QuickSearchBox

 

[zgfg]

Thanks to all who participated over the last two years, specially the users with other phones (Samsung, One Plus, Pixel...) and specially to @ipdev for his endless support in testing and in the ideas for improvements

By help of the moderator, the thread is now moved from Xiaomi / Mi 9T to the General development / XDA community apps / Magisk (with threads for the other Magisk modules of general use):

Magisk

Magisk - The Universal Systemless Interface, to create an altered mask of the system without changing the system itself.

forum.xda-developers.com

The thread itself is still available under the original URL:
https://forum.xda-developers.com/mi-9t/how-to/magisk-module-systemless-debloater-t4180083
and now its new URL:
https://forum.xda-developers.com/t/magisk-module-systemless-debloater.4180083/

 

[zgfg]

Warning:

Mounting systemless changes to /system/* is broken for Magisk Canary 25207-25210 - SystemlessDeblloater (BusyBox and ToyBox, plus several other modules like V4A, JamesDSP, AML) will not work properly

Stay with Magisk Canary 25206 or other (older) Magisk Stable/Canary versions.
No problems with Magisk Delta

Seems that the problem is related to the following issue reported for Magisk Canary (25211 with the fix not released yet):

25210 breaks module loading · Issue #6688 · topjohnwu/Magisk

Device: Pixel 7 Pro Android version: 13 QPR2 Magisk version name: v981ccabb Magisk version code: 25210 With the latest version, mounting all mounts fails saying No such file or directory, i.e. moun...

github.com

 

[chewy74]

Is there a list for lineage os? Specifically browser, calendar and music apps.