Magisk Module Systemless Debloater (REPLACE)

[zgfg]

Systemless Debloater updated to v1.45:

Release Systemless Debloater v1.4.8 · zgfg/SystemlessDebloater

Verbose logging by default: listing all not debloated stock system apps

github.com

1) If you use new Magisk Canary 23017+ or Alpha 23016+, you will see the Update icon/link in the new Magisk app, Modules section

2) If you use Fox Magisk module manager (Fox Mmm), you will see the icon/link to this thread in XDA

See the screenshots

---

Select and debloat preinstalled system apps. Supported up to SAR, Dynamic partitions and A12. Module must be installed through Magisk app, not TWRP - see instructions in the OP posts in this thread

 

[RMX3370]

Please If possible update the script to add debloat from custom locations for example
In Realme Devices with dynamic Parttitons
It has system apps in various partitions
Examples

Spoiler: See Apps Not Removed

/my_product/app/OplusLocationServiceForeign/OplusLocationServiceForeign.apk
/my_product/priv-app/HotwordEnrollmentOKGoogleHEXAGON.apk
/my_heytap/app/Chrome/Chrome.apk
/my_heytap/app/YouTube/YouTube.apk
/my_heytap/priv-app/GmsCore/GmsCore.apk
/my_heytap/priv-app/Phonesky/Phonesky.apk
/my_preload/del-app/com.spotify.music/com.spotify.music.apk
/my_region/app/Google_Messages/Google_Messages.apk

Proposed solution
Allow adding custom directories
Or direct path to .apk to be removed

For example entering
my_heytap/priv-app/Velvet/Velvet.apk in /storage/emulated/0/Download/SystemlessDebloaterList.sh
Should remove it using magisk replace on next boot

 

[onimorza]

Works great on my OnePlus Nord with A11 OOS 11.1.7.7 ! Thanks a bunch!

 

[zgfg]

Please If possible update the script to add debloat from custom locations for example
In Realme Devices with dynamic Parttitons
It has system apps in various partitions
Examples

Spoiler: See Apps Not Removed

/my_product/app/OplusLocationServiceForeign/OplusLocationServiceForeign.apk
/my_product/priv-app/HotwordEnrollmentOKGoogleHEXAGON.apk
/my_heytap/app/Chrome/Chrome.apk
/my_heytap/app/YouTube/YouTube.apk
/my_heytap/priv-app/GmsCore/GmsCore.apk
/my_heytap/priv-app/Phonesky/Phonesky.apk
/my_preload/del-app/com.spotify.music/com.spotify.music.apk
/my_region/app/Google_Messages/Google_Messages.apk

Proposed solution
Allow adding custom directories
Or direct path to .apk to be removed

For example entering
my_heytap/priv-app/Velvet/Velvet.apk in /storage/emulated/0/Download/SystemlessDebloaterList.sh
Should remove it using magisk replace on next boot

Could you please 'install' the module again with the attached input file

Verbose logging enabled:
VerboseLog="true"

And please share the log

 

[RMX3370]

Could you please 'install' the module again with the attached input file

Verbose logging enabled:
VerboseLog="true"

And please share the log

Module is able to remove / replace files from these directories

/system/system_ext/app/ /system/system_ext/priv-app/ /system/app /system/priv-app /product/app /vendor/app​

But fails to do so in

/my_carrier/app /my_carrier/priv-app /my_heytap/app /my_heytap/priv-app /my_product/app /my_product/priv-app /my_region/app /my_region/priv-app /my_stock/app /my_stock/priv-app​

 

[zgfg]

Module is able to remove / replace files from these directories

/system/system_ext/app/ /system/system_ext/priv-app/ /system/app /system/priv-app /product/app /vendor/app​

But fails to do so in

/my_carrier/app /my_carrier/priv-app /my_heytap/app /my_heytap/priv-app /my_product/app /my_product/priv-app /my_region/app /my_region/priv-app /my_stock/app /my_stock/priv-app​

Module has Readme file and it precisely describes (also the OP posts above) from which partitions it currently deblotes

Hence yes, it does not debloat from some /my* partitions - I could consider to extend the module in future

What is your phone, ROM, Android version coming with those /my* partitions?

Also, module is case sensitive (intentionally) when it looks for the apps.
Check your LOG file, and search for the apps it didn't debloat.
You will see that you have Stk (but not STK) on your /system_ext, hence simply rename STK in the sh input script to Stk and 'install' thenmodule again, it will also debloat Stk

There are maybe more system apps (in the supported partitions) you could find their exeact nanes in the log, correct in the input sh and run again

PS:
Do you really want to debloat GmsCore?
Seems to be Google Play Services:
GmsCore.apk=com.google.android.gms
It would affect GApps and SafetyNet

Generally, you debloat on your own risk (it's Systemless debloating, hence just disabling the module and rebooting reverts to un-debloated state). Of course, currently you cannot debloat GmsCore since it's on your /my_heytap partition

 

[RMX3370]

Module has Readme file and it precisely describes (also the OP posts above) from which partitions it currently deblotes

Hence yes, it does not debloat from some /my* partitions - I could consider to extend the module in future

What is your phone, ROM, Android version coming with those /my* partitions?

Also, module is case sensitive (intentionally) when it looks for the apps.
Check your LOG file, and search for the apps it didn't debloat.
You will see that you have Stk (but not STK) on your /system_ext, hence simply rename STK in the sh input script to Stk and 'install' thenmodule again, it will also debloat Stk

There are maybe more system apps (in the supported partitions) you could find their exeact nanes in the log, correct in the input sh and run again

PS:
Do you really want to debloat GmsCore?
Seems to be Google Play Services:
GmsCore.apk=com.google.android.gms
It would affect GApps and SafetyNet

Generally, you debloat on your own risk (it's Systemless debloating, hence just disabling the module and rebooting reverts to un-debloated state). Of course, currently you cannot debloat GmsCore since it's on your /my_heytap partition

Realme GT NEO 2 , Launched with Android 11 RUI 2.0 has super/dynamic partition
I want to remove all google apps no , till custom ROM is available for my device so I can use microG
I hope in future module can remove all system apps even if they are not in standard directories because most OEMs now don't follow rules and they will fill bloatware in the most unreachable directory

 

[zgfg]

Realme GT NEO 2 , Launched with Android 11 RUI 2.0 has super/dynamic partition
I want to remove all google apps no , till custom ROM is available for my device so I can use microG
I hope in future module can remove all system apps even if they are not in standard directories because most OEMs now don't follow rules and they will fill bloatware in the most unreachable directory

Not sure if
/my_heytap
/my_product
/my_region
/my_stock

are properly supported by Magisk for REPLACE mechanism

I'll send you an experimental version - please check your PM, test and respond there

PS:
Unfortunately REPLACE mechanism in Magisk did not work for the given /my_* partitions, but the new SystemlessDebloater v1.4.6 was released, supporting configurable list of SAR partitions/file-systems to debloat

 

[zgfg]

Systemless Debloater is now available from the relatively new Alt(ernative) Repo:

GitHub - Magisk-Modules-Alt-Repo/SystemlessDebloater: Select and systemlessly debloat preinstalled system apps. Supporting up to System As Root (SAR), Dynamic partitions and Android 12 (not tested on Android 13 yet). Module must be installed through

Select and systemlessly debloat preinstalled system apps. Supporting up to System As Root (SAR), Dynamic partitions and Android 12 (not tested on Android 13 yet). Module must be installed through M...

github.com

- for easy finding and installations through Fox Magisk Module Manager app

Also, in future, whenevernmodule would be updated, you would be able to update it directly through Magisk v24 app - as on the screenshots

 

[zgfg]

Debloated my brand new Xiaomi 11 Lite 5G NE, MIUI 12.5, A11, SAR, Dynamic Partitions, A/B device

Debloated 40+ system apps, no problem.
SystemlessDebloaterInput.sh is attached - remove Facebook, GMail and so from my list if you use those apps

Btw, I debloat the stock YouTube because I need an older version of YT app for Vanced YT root

 

[Techguy777]

I'm not going to lie the terminal module was so much easier to use. I haven't looked through the whole thread yet but the dynamic partitions or super img are now set up with vendor apps system product apps system product private apps and I believe even a couple others like system_ext apps which I am sure people won't want to uninstall they seem important. But the problem is I don't understand how your module will find apps that aren't in system and system private apps. I'm having troubles like people I see . I'm just trying to test it with calculator app or Google maps in system products apps section and it won't find them.

 

[zgfg]

I'm not going to lie the terminal module was so much easier to use. I haven't looked through the whole thread yet but the dynamic partitions or super img are now set up with vendor apps system product apps system product private apps and I believe even a couple others like system_ext apps which I am sure people won't want to uninstall they seem important. But the problem is I don't understand how your module will find apps that aren't in system and system private apps. I'm having troubles like people I see . I'm just trying to test it with calculator app or Google maps in system products apps section and it won't find them.

Names of the apps must be provided exactly

Nevertheless, you can run once, inspect the log file, correct the input list and try again

---

Pls put the attached
SystemlessDebloaterList.sh

to your /Download folder,
install the module again
and provide back the resulting
SystemlessDebloater.log

---

Btw, be aware of two facts:

1) On the new devices with read-only filesystem on the /system, not even TWRP could write/delete over the /system - you can only make changes in the Systemless manner

2) On the new SAR A/B devices there is no separate Recovery partition but custom recovery must be flashed to Boot - however, Magisk also flashes to boot (patch and flash), hence you could not have permanent TWRP with Magisk in parallel

 

[Techguy777]

Names of the apps must be provided exactly

Nevertheless, you can run once, inspect the log file, correct the input list and try again

---

Pls put the attached
SystemlessDebloaterList.sh

to your /Download folder,
install the module again
and provide back the resulting
SystemlessDebloater.log

---

Btw, be aware of two facts:

1) On the new devices with read-only filesystem on the /system, not even TWRP could write/delete over the /system - you can only make changes in the Systemless manner

2) On the new SAR A/B devices there is no separate Recovery partition but custom recovery must be flashed to Boot - however, Magisk also flashes to boot (patch and flash), hence you could not have permanent TWRP with Magisk in parallel

This is my file I made inside downloads folder do you understand what I did wrong or nothttps://drive.google.com/file/d/1COpuJbSJDKyiejF9VTHXS27uB9NYleRQ/view?
usp=drivesdk

SystemlessDebloaterList.sh

drive.google.com

 

[Techguy777]

Names of the apps must be provided exactly

Nevertheless, you can run once, inspect the log file, correct the input list and try again

---

Pls put the attached
SystemlessDebloaterList.sh

to your /Download folder,
install the module again
and provide back the resulting
SystemlessDebloater.log

---

Btw, be aware of two facts:

1) On the new devices with read-only filesystem on the /system, not even TWRP could write/delete over the /system - you can only make changes in the Systemless manner

2) On the new SAR A/B devices there is no separate Recovery partition but custom recovery must be flashed to Boot - however, Magisk also flashes to boot (patch and flash), hence you could not have permanent TWRP with Magisk in parallel

Give me the file with those 2 apps to flash and I will see what I did wrong. Setup a file that should work and I Will download it and then flash the module again and see if it works. Because the one you already gave doesn't work either. So I don't understand what the hell it is. I'm supposed to. I'm doing everything. Give me the file all set up so I can flash it and then I can see and compare it to the one I have

 

[Techguy777]

Names of the apps must be provided exactly

Nevertheless, you can run once, inspect the log file, correct the input list and try again

---

Pls put the attached
SystemlessDebloaterList.sh

to your /Download folder,
install the module again
and provide back the resulting
SystemlessDebloater.log

---

Btw, be aware of two facts:

1) On the new devices with read-only filesystem on the /system, not even TWRP could write/delete over the /system - you can only make changes in the Systemless manner

2) On the new SAR A/B devices there is no separate Recovery partition but custom recovery must be flashed to Boot - however, Magisk also flashes to boot (patch and flash), hence you could not have permanent TWRP with Magisk in parallel

SystemlessDebloater.log

drive.google.com

 

[m0han]

....On the new devices with read-only filesystem on the /system, not even TWRP could write/delete over the /system....

there is a twrp available for poco x3 with a feature that runs a script that turns rom to r/w. also, seems there is a separate zip file (systemrw_1.32_flashable.zip) for that on 4pda. just an fyi.

 

[zgfg]

SystemlessDebloater.log

drive.google.com

Please, before wasting time, read the OP posts at the beginning of the thread

OP instructions clearly say that SystemlessDebloaterLust.sh must be in Download folder, not your subfolder or something

And your log also says that input file was not found (line 10):
>>Input file not found, creating a template file!

I GAVE YOU THE INPUT FILE you had to use, but you had to USE IT PROPERLY (proper path) - then it would debloat and/or we would see from the log file if/why not

If not following instructions, it can't work

PS: You need the input sh file in /Download folder (not subfolders or any other place) ONLY when you're 'installing' the module (first time or later when you're changing the stock apps to debloat)

After that, you can inspect the log file (it's very simple, don't hesitate to open and read), and if you need, adapt your sh file and 'install' again

Once you are finished (and rebooted), you can delete both the sh file and log - better back-up to some place, for future if/when you would like to change your debloating

After the successful installation, module does no more need the sh file and log (if they bother you seeing them in Download folder)

 

[applyscience]

does any Oneplus user know if this can remove odm? id love to be able to remove that and my usual program for debloating doesnt remove it

De-Bloater | F-Droid - Free and Open Source Android App Repository

Use the power of Magisk to de-bloat system applications systemless-ly

f-droid.org

 

[zgfg]

I always get this error again. Happens all the time but worked,back to this.

To anyone else finding this to be unreliable (for now) I highly suggest the debloater from fdroid, it doesn't work on everything, but its reliable

De-Bloater | F-Droid - Free and Open Source Android App Repository

Use the power of Magisk to de-bloat system applications systemless-ly

f-droid.org

Which error, where?

Provide your SystemlessDebloater.log

 

[Techguy777]

Please, before wasting time, read the OP posts at the beginning of the thread

OP instructions clearly say that SystemlessDebloaterLust.sh must be in Download folder, not your subfolder or something

And your log also says that input file was not found (line 10):
>>Input file not found, creating a template file!

I GAVE YOU THE INPUT FILE you had to use, but you had to USE IT PROPERLY (proper path) - then it would debloat and/or we would see from the log file if/why not

If not following instructions, it can't work

PS: You need the input sh file in /Download folder (not subfolders or any other place) ONLY when you're 'installing' the module (first time or later when you're changing the stock apps to debloat)

After that, you can inspect the log file (it's very simple, don't hesitate to open and read), and if you need, adapt your sh file and 'install' again

Once you are finished (and rebooted), you can delete both the sh file and log - better back-up to some place, for future if/when you would like to change your debloating

After the successful installation, module does no more need the sh file and log (if they bother you seeing them in Download folder)

Are you all there? When I flash your module it puts the files in the download folder and that's where they stay I don't move them.