yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
You cannot delete anything from System if your SAR is read-only (modern devices launched with A11/12, also A10 for some vendors) - not even by custom recovery like TWRP

If /system, /vendor, etc are read-only, you cannot change anything there - that's why systemless rooting is needed (also for adblocking by AdAway, where it cannot change /system/etc/hosts file), etc
[Magisk] abeloman:
Any idea why debloating MIUI trips SafetyNet? I've tried many times, and I had to remove module in order to pass SafetyNet
[Magisk] m0han:
I just experimented in TWRP and was able to delete whatever I tried to. My device was launched 2 years ago with A10. Don't know about it's SAR; maybe it is RW. https://m.gsmarena.com/xiaomi_poco_x3-10461.php
[Magisk] zgfg:
I debloat two phones and absolutely never have any problem with SafetyNet

The module itself cannot affect SafetyNet.

However, who knows which apps you debloated, resulted in loosing SaferyNet.

Eg, maybe you debloat GApps...
[Magisk] zgfg:
Fine, and?

I have two phones (Xiaomi, with MUII - not some AOSP/GSI, etc custom ROMs)

Xiaomi Mi 9T, launched with A9 or A10, but upgraded to A11.

On that phone I can debloat and make any changes on the System I want through TWRP.

System is read-only when booted to Android, but in TWRP it is read-write

New phone, Mi 11 Lite 5G NE. Launched with A11 and upgraded to A12.

Already with A11, System was read-only both in Android and custom recoveries

If you don't believe, please Google and read about different types of SAR=System As Root (or find and read pndwal"s eseys about SARs about in Magisk threads). Or buy a new phone (already launched now with A12)

There are also thread(s) here on XDA with a guide how to make Super partition (containing the whole SAR) read-write. The method is pretty complicated, you practically have to re-cook the ROM on the PC.

If it would be that easy as using custom recovery to write/edit your Super, nobody would mind to do develop and play with that method
[Magisk] m0han:
Interesting. Keep up the good work.

Maybe my case is System is read-only when booted to Android, but in TWRP it is read-write. Forgot to mention I'm on A12.1 of 23rd Sept since the last couple of days.

Spoiler content hidden.
[Magisk] zgfg:
And one more clarification: "launched with" does not mean OS the phone was bought by this or that user but how the phone was originally launched to the market.

That info can be found eg on GSMArena.com

Because, some phone might have been launched with A10 but the vendor later upgraded ROM to A11 or A12.

Somebody later buys the phone and he already gets A11 - but that phone (model) was still originally launched with A10

That's because the phone was designed for the Google's requirements announced for the phones to be launched with A10.

Vendor later upgrades the ROM to A11 but generally, Google's requirements for upgrading A10 to A11 (and later A12) are less stringent (OTA cannot upgrade your hardware😁) than for the new phones to be originally launched with A11 or A12
[Magisk] Arnav74:
My log file is here, you can see all the other bigball stuff. Not sure what it's for. Could be ColorOS related stuff.

https://pastebin.com/MSWKJruP

I have already uninstalled it. As m0han said, I restored all the debloated Omoji app, cleared data, and then uninstalled the debloater (It was an app that was granted root, not a magisk module).

I tried reinstalling using my Debloat list. Here is the log file again, it's basically the same as the previous one. https://pastebin.com/bD8utjDt

Here is the page of Omoji in the settings, under Manage Apps. I don't see uninstall option.

The app was not installed or updated by Google Play. It is not in the playstore at all. This can be seen when going to the APKMirror page for Omoji and clicking the Play Store link -- it leads to nowhere.
[Magisk] zgfg:
When you post to XDA, you have Attach files option as on the screenshot

PLEASE use that, you can attach log file, screenshot, etc

I block pastebin, ingur, whatever on my phone - and there is absolutely no need to use those external clouds while you can simply attach everything here directly to the XDA post
[Magisk] Arnav74:
Sure, sorry I am new to posting on XDA and did not realize I could do that. The files are attached to this post.
[Magisk] zgfg:
Since your Omoji app is in some 'new'/strange folder my_bigball:

/system/my_bigball/app/Omoji/Omoji.apk=com.oplus.omoji

Try with the attached SystemlessDebloaterList.sh

(my_bigball folder added to SarMountPointList)

No guarantee, let's test please
[Magisk] Arnav74:
It worked! Thank you! Log file attached.
[Magisk] Arnav74:
Wait, actually I'm not sure if it worked. In the log file it shows it's okay, but I still see Omoji in my settings app and it keeps asking me to create my Omoji (image attached)
[Magisk] zgfg:
You had to reboot.

Now, use root explorer like MiXPlorer and check do.you have file:

/system/my_bigball/app/Omoji/Omoji.apk

It should not be that APK there.
[Magisk] Arnav74:
I have definitely rebooted right after reinstalling the module. I have just done it again to double-check. Unfortunately, the APK is still there (image attached). I have provided log file again, although it should be the same from last time as I did not change anything.
[Magisk] zgfg:
Something is really strange with your my_bigball - let's move to the private conversation, check my post there
[Magisk] andybones:
Thank you for this!

It is working wonderfully on my Pixel 5 Android 12L Stock ROM.
[Magisk] zgfg:
Based on the issues with your (OnePlus, ColorOS, A13) /my_bigball folder that is not mounted to /system and the Magisk REPLACE mechanism cannot be applied, now the new module version v1.4.9 was pushed to the Alt Repo (update should be also available through the Magisk app, Modules, scroll to Systemles Debloaters, take Update)

v1.4.9 uses now both the REPLACE mechanism and service.sh script - service.sh script debloats (by mounting dummy apk to them) those stocky/system apps that are not installed to /system (but eg to your /my_bigball stock partition)
[Magisk] Arnav74:
Awesome. I will try it out in a few days as I am very busy for the moment
[Magisk] AnonVendetta:
@zgfg Working fine on Pixel Experience Android 13 GSI on my Galaxy Tab S7+. I've never used a systemless debloater (any mod), setting this up is really easy. I'm an old school Android user since its' earliest days, also have been rooting etc for many years, so I'm used to deleting "for real". I've grudgingly gotten used to the systemless way, but old habits die hard. Either way, thanks for the mod.
[Magisk] yassine2217:
Hi

sorry for this reply i use coloros on my One+7pro

The partition my_bigball does not allow modification it is only on readonly
[Magisk] zgfg:
Of course that it is read-only

Thus is this module for SYSTEMLESS changes

If not familiar with new Android read-only System partitions and Magisk systemless root/changes, please google, read, learn about
[Magisk] kaefers:
Hey!

Kudos, great app, once I got the list together (which took a while) it's a very quick debloat method, love it [ I wish it would reckognize package names like com.samsung.aasaservice directly instead of having to specify the correct application name ;) ]

I have been testing around on how to best debloat my S22 Ultra (Exynos) without running into issues. Initial setup here: Link

All works well but I am unable to debloat any /apex/ or /prism/ apps, see log, here some examples:

/apex/com.android.apex.cts.shim/app/CtsShim@1/CtsShim.apk=com.android.cts.ctsshim

/prism/app/SwiftKey-market-arm64-v8a-release/SwiftKey-market-arm64-v8a-release.apk=com.touchtype.swiftkey

I know I could go ahead and get rid of them via adb, but was wondering if there is anything this tool could be doing about those?

Log attached with the entire 277 apps to be debloated ["aggressive but still boots" ..]

Thanks! :)
[Magisk] zgfg:
To debloat apps from /prism:

Open:

/Download/SystemlessDebloaterList.sh

Check, does it contain the statement:

SarMountPointList="<List of some paths>"

Like:

SarMountPointList="/product /vendor /system_ext /india /my_bigball"

If it contains, replace with the one below.

Also, if it doesn't contain, then just add:

SarMountPointList="/product /vendor /system_ext /prism"

And then 'reinstall' the module

Btw, I have omitted /india and /my-bigball since (by your log) you don't have those partitions - but some others do have and need them in the SarMountPointList

---

You can try adding /apex also to the SarMountPointList but I doubt it would work - try and send a log

Even better, open and carefully edit (eg by MiXplorer):

/data/adb/modules/SystemlessDebloater/service.sh

After the last line:

$MountBind $DummyApk <some path to the APK file>

Add the following:

$MountBind $DummyApk /apex/com.android.apex.cts.shim/app/CtsShim@1/CtsShim.apk

and similarly for the other apps from /apex

And then reboot!

Unfortunately, be aware that every time you 'reinstall' the module, service.sh script will be overwritten and you will need to edit again

Be very carefully since /apex may contain services that would cause bootloop or malfunctions if you debloat them
[Magisk] kaefers:
Thanks so much for the detailed reply, I will try that out! Will make a copy of the edited service.sh as I will be reinstalling a few more times to see how far I can debloat.

I got all backed up with TWRP, so even if something goes wrong, I can always just restore.

Thanks again :)
[Magisk] kaefers:
Worked just fine with SarMountPointList="/product /vendor /system_ext /prism /apex" !

Had to remove a few apks from my /apex/ list but majority of the /apex/ apps are gone (e.g. in System App Remover Root). 436 apps down to 164 and still booting :D | Log attached FYI

Great work! 🙌
[Magisk] zgfg:
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?
[Magisk] kaefers:
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!
[Magisk] 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 ;]
[Magisk] 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://xdaforums.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.. :/ ]
[Magisk] zgfg:
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
[Magisk] kaefers:
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
[Magisk] 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
[Magisk] dkionline:
Still funny, i can delete MiVideo but not MiMusic. @zgfg, What about delete stuff in vendor partition?
[Magisk] zgfg:
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)
[Magisk] 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.
[Magisk] zgfg:
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
[Magisk] xadad:
After debloat all google app it stuck on logo, how can i reinstall packges?
[Magisk] zgfg:
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)
[Magisk] 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
[Magisk] m0han:
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?
[Magisk] zgfg:
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
[Magisk] 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. :cowboy:
[Magisk] zgfg:
Usually I debloat additionally:

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

MiShare

MiuiScanner

ims

CneApp

PersonalAssistant

QuickSearchBox
[Magisk] 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.

xdaforums.com

The thread itself is still available under the original URL:

https://xdaforums.com/mi-9t/how-to/magisk-module-systemless-debloater-t4180083

and now its new URL:

https://xdaforums.com/t/magisk-module-systemless-debloater.4180083/
[Magisk] 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
[Magisk] chewy74:
Is there a list for lineage os? Specifically browser, calendar and music apps.
[Samsung Galaxy S10 Themes, Apps, and Mods] Mini Jay:
Hey everyone ! Samsung has recently released a new module on Good Lock to customize the Samsung keyboard called Keys Café.

Unfortunately for those who bought one of the S10 series in Hong Kong it isn't available yet, and even by downloading the apk of Keys Café, the keyboard customized don't apply to the keyboard.

My S10 is running OneUI 2.5 and the latest version of the Samsung keyboard. The Samsung keyboard from the HK variant is a bit different from the international version of the Samsung Keyboard. That may explain why the apk doesn't work on the Samsung keyboard from the HK variant.

Did anyone using one of the S10 series bought in Hong Kong happen to have got Key Café working ?
[Samsung Galaxy S10 Themes, Apps, and Mods] rename_nick:
anyone?
[Samsung Galaxy S10 Themes, Apps, and Mods] sxeMonster:
Guys, I have the same problem, and I believe it is simply impossible to make it work, unless good lock would be officially available in HK. We should just wait and hope.
[ASUS ROG Phone 3 Questions & Answers] riccohead:
Can anyone help me to unlock bootloader and root my asus ROG 3. Please help me..

Thank You
[ASUS ROG Phone 3 Questions & Answers] bASKOU:
First can you tell if you have a global phone or a Tencent games phone ? You can see it simply from the back of your phone on the bottom of it is written Republic of gamer or Tencent games.
[ASUS ROG Phone 3 Questions & Answers] riccohead:
Its Republic Of Gamers
[ASUS ROG Phone 3 Questions & Answers] elmor0:
Please search this forum - there are already numerous helpful posts on this topic.
[ASUS ROG Phone 3 Questions & Answers] bASKOU:
Look here https://www.xda-developers.com/asus...ock-tool-firmware-kernel-sources-release/amp/ you'll find all you need there
[ASUS ROG Phone 3 Questions & Answers] riccohead:
Thank you baskou