Magisk Module Systemless Debloater

Search This thread
By:
Advanced…
ipdev

ipdev

Recognized Contributor
Feb 14, 2016
2,399
1
4,835
Google Nexus 10
Nexus 7 (2013)
chewy74 said:
Is there a list for lineage os? Specifically browser, calendar and music apps.
Click to expand...
Click to collapse
Still working on it. 😉
CommunityList - [Github Wiki] - Link
Need to add jelly (browser), etar (calendar), eleven (music), along with a few others to the LineageOS section.

I hope to have time this weekend to clean up and add a few things to the list. 🙃

Cheers. :cowboy:
 
  • Like
Reactions: chewy74, zgfg, Lughnasadh and 1 other person
T

TheNewHEROBRINE

Senior Member
Aug 26, 2021
329
104
20
Italy
OnePlus 8T
For me when I debloat a system app that has an icon in the app drawer, it gets replaced by an app with the default Android icon and the name equal to the package name of the debloated app. Why isn't the app completely disappearing from the app drawer?
 
zgfg

zgfg

Senior Member
Oct 10, 2016
8,976
6,714
Redmi K20 / Xiaomi Mi 9T
Xiaomi Mi 11 Ultra
TheNewHEROBRINE said:
For me when I debloat a system app that has an icon in the app drawer, it gets replaced by an app with the default Android icon and the name equal to the package name of the debloated app. Why isn't the app completely disappearing from the app drawer?
Click to expand...
Click to collapse
That's very strange . Have you, as instructed, uninstall all (user Data) updates of that app you have debloated. If not, then please do, then reboot, install the module again (keep your previous cfg file with the list of apps to debloat)

If after all that still the same, provide the info about your device, ROM, Android version and attach your cfg and log files, and note the name and package name of that problematic app(s)
 
  • Like
Reactions: TheNewHEROBRINE
Arju87

Arju87

New member
Oct 31, 2022
3
1
Good morning, I can confirm that it works great on Oneplus 7t with A12, I have successfully removed YouTube.
What happens if you remove the module from magisk?
 
zgfg

zgfg

Senior Member
Oct 10, 2016
8,976
6,714
Redmi K20 / Xiaomi Mi 9T
Xiaomi Mi 11 Ultra
Arju87 said:
Good morning, I can confirm that it works great on Oneplus 7t with A12, I have successfully removed YouTube.
What happens if you remove the module from magisk?
Click to expand...
Click to collapse
As it says in the OP - it is systemless module, no hard changes on the System. Besides, even with root, System is read-only on the new phones - and that's the reason why systemless changes (changes are only mounted by Magisk on every reboot) work, while debloaters that try to make hard changes (to really remove system apps via eg TWRP) cannot work on the phones with SAR file-system read-only

You disable the module or uninstall, or uninstall Magisk, and reboot, everything goes back (no more mounting, hence no more debloating)

Like Systemless hosts, etc
 
Last edited:
  • Like
Reactions: ipdev and Arju87
T

TheNewHEROBRINE

Senior Member
Aug 26, 2021
329
104
20
Italy
OnePlus 8T
zgfg said:
That's very strange . Have you, as instructed, uninstall all (user Data) updates of that app you have debloated. If not, then please do, then reboot, install the module again (keep your previous cfg file with the list of apps to debloat)

If after all that still the same, provide the info about your device, ROM, Android version and attach your cfg and log files, and note the name and package name of that problematic app(s)
Click to expand...
Click to collapse
I solved my problem, although I don't know exactly how, but now I have a question. Is there any advantage to using this method rather than using pm uninstall?
 
Last edited:
zgfg

zgfg

Senior Member
Oct 10, 2016
8,976
6,714
Redmi K20 / Xiaomi Mi 9T
Xiaomi Mi 11 Ultra
TheNewHEROBRINE said:
I solved my problem, although I don't know exactly how, but now I have a question. Is there any advantage to using this method rather than using pm uninstall?
Click to expand...
Click to collapse
With pm disable-user or pm uninstall -k --user 0 you debloat for that user (0) but the system app is still installed for the alternate user 999

Also, if you eg have the latest (YouTube) app pre-installed to System and for some reason you need to install an older version of the same app, then if you debloated that app (YT) by pm, downgrading would not work

Anytime you want to install that older (YT) version, package manager would recognize that the same package name but an older version is still installed to the system, and would prevent downgrading

If debloated by the module, package manager cannot see the same package name (its pre-installed System installation folder/apk file is mounted over by a dummy), hence you can freely install the older version of that app

---

pm list packages -u
will print also the packages un-installed by pm

pm list packages -d
will print packages disabled by pm

showing how pm still finds the packages it did disable or 'un-install'
 
Last edited:
  • Like
Reactions: TheNewHEROBRINE and ipdev
R

rah84

Member
Oct 24, 2013
13
0
Hello,(Damn i have not known that i wrote so much, i think my english is not so good)
Please please i need asap help!
It seems i have removed some needed stuff in order to run system funcionllities.
First of all after debloating and rebooting i get crashing apps like all or many apps or background services that did tried start.
App like for example my Nuki widget (smart door lock) which just opens the app and run through the full app to open my door or whatever from BT. Nothing happens when i click the button to open the door, thats pretty weird..and iam sure with this problem i will have problems in other szenarios.
Thats not all.
google services is gone. I cant add/remove Google accs, PlayStore is gone.
I dont know what to do, i run the script with an empty *.cfg debloat list and rebooted. That havent helped. After all, the system runs just flawlessly except the told ones (havent tested much because i try to restore Google)) only device health still getting crashed and Messages.
About the apps crashing i came to the conlusion that wipe dalvik/Art cache would maybe helped...
Anyway after all i found out there is a new system update.
I totally forget this that i can just reflash the fw so i have all apps again.
No this havent helped too, gms still gone, playstore all the google related stuff. Nuki dont work.
To Test Gmail i have installed it but no way, force close
This is my *.cfg File under attachment
Too bad i have needed to save the *.log file right after that had happened because this log file is though not helpfull because i run preety often the Module and deleted i then after firmware upgrade too.

I also made also backup of all the apps with Swift Backup some day ago, they found thats only gsf is not on the phone, so i restored it with all the data with no effect
Please for any Help ;(

PS. I dont use any Samsung related stuff as seein..no Google payment methodes, i dont play games, I removed before or later the system upgrades If i have not forget it then rerun the module

I dont want to factory reset, this would be much much Work :(

My Phone is the S21 Ultra G998B
 

Attachments

  • SystemlessDebloater.log
    107.5 KB · Views: 9
  • SystemlessDebloater.cfg.zip
    767 bytes · Views: 11
Last edited:
Primokorn

Primokorn

Senior Member
Nov 17, 2012
11,535
7,738
OnePlus 8 Pro
Code: 
product/app/Calculator2/Calculator2.apk=com.oneplus.calculator
This is the app I want to remove (line taken from the log file after a first flash).
I added Calculator2 into the SystemlessDebloater.cfg file. Nothing found during the new flash... Why?

EDIT: maybe because of an empty line between the commented apps and the one I have added
 
  • Like
Reactions: ipdev
zgfg

zgfg

Senior Member
Oct 10, 2016
8,976
6,714
Redmi K20 / Xiaomi Mi 9T
Xiaomi Mi 11 Ultra
Primokorn said:
Code: 
product/app/Calculator2/Calculator2.apk=com.oneplus.calculator
This is the app I want to remove (line taken from the log file after a first flash).
I added Calculator2 into the SystemlessDebloater.cfg file. Nothing found during the new flash... Why?

EDIT: maybe because of an empty line between the commented apps and the one I have added
Click to expand...
Click to collapse
Cannot analyze anything without the log file that you will find in Download folder

And first, try to analyze yourself - if it doesn't find the app, then you gave the wrong name for the app

But in the log file you have list of all stock files, hence use the search to find the proper name and then put the proper name to your cfg file

Also, did you read the OP posts - if it's not the system app (but app installed to /data) then don't use this module for. There are other ways to get rid of Data (user) apps - btw,Nin that case you will not find the app in the list in the log - since the module does not look for Data (user) apps
 
Primokorn

Primokorn

Senior Member
Nov 17, 2012
11,535
7,738
OnePlus 8 Pro
zgfg said:
Cannot analyze anything without the log file that you will find in Download folder

And first, try to analyze yourself - if it doesn't find the app, then you gave the wrong name for the app

But in the log file you have list of all stock files, hence use the search to find the proper name and then put the proper name to your cfg file

Also, did you read the OP posts - if it's not the system app (but app installed to /data) then don't use this module for. There are other ways to get rid of Data (user) apps - btw,Nin that case you will not find the app in the list in the log - since the module does not look for Data (user) apps
Click to expand...
Click to collapse
Thanks but I found the solution as mentioned in the EDIT.
FYI yes I always read OP, read the troubleshooting section and try to analyze the log myself before posting.
The log didn't mention anything and yes it was a system app.
All good now 👍
 
  • Like
Reactions: ipdev and zgfg
zgfg

zgfg

Senior Member
Oct 10, 2016
8,976
6,714
Redmi K20 / Xiaomi Mi 9T
Xiaomi Mi 11 Ultra
Primokorn said:
Thanks but I found the solution as mentioned in the EDIT.
FYI yes I always read OP, read the troubleshooting section and try to analyze the log myself before posting.
The log didn't mention anything and yes it was a system app.
All good now 👍
Click to expand...
Click to collapse
Good that you solved

But I'm still puzzled how an empty line would mess

Also, log file would show how the list of apps names for debloating was read from the cfg file - hence it's always important to read the log file SystemlessDebloater.log (as the one attached below)
 

Attachments

  • SystemlessDebloater.log
    62.4 KB · Views: 3
Primokorn

Primokorn

Senior Member
Nov 17, 2012
11,535
7,738
OnePlus 8 Pro
zgfg said:
Good that you solved

But I'm still puzzled how an empty line would mess

Also, log file would show how the list of apps names for debloating was read from the cfg file - hence it's always important to read the log file SystemlessDebloater.log (as the one attached below)
Click to expand...
Click to collapse
I can reproduce. I have attached the files.

So the problem wasn't the empty line before my system app but the empty at the end.
 

Attachments

  • SystemlessDebloater.log
    73.9 KB · Views: 6
  • It_works.cfg.txt
    1.2 KB · Views: 13
  • it_does_not_work.cfg.txt
    1.2 KB · Views: 9
Last edited:
zgfg

zgfg

Senior Member
Oct 10, 2016
8,976
6,714
Redmi K20 / Xiaomi Mi 9T
Xiaomi Mi 11 Ultra
Primokorn said:
I can reproduce. I have attached the files.

So the problem wasn't the empty line before my system app but the empty at the end.
Click to expand...
Click to collapse
Ok, thanks, so you had empty Input DebloatList in the log file, indicating that it didn't parse anything from the cfg file

That is, it was not really about where was the comment or not, but the bug that the last app name in the cfg file is not parsed if it's not followed by an empty line

Attached is a very simple cfg file (5 apps with no empty line after the last app name) and with the excerpt from the corresponding log file (showing only 4 apps in the debloat list)

Btw @ipdev, there is also a bug if two or more app names are listed in the same line, separated by spaces (original sh input files did not have these issues) 😀
 

Attachments

  • cfg-missing-empty-line-at-the-end.zip
    378 bytes · Views: 5
Last edited:
ipdev

ipdev

Recognized Contributor
Feb 14, 2016
2,399
1
4,835
Google Nexus 10
Nexus 7 (2013)
@Primokorn @zgfg
Looks like it is a limitation of the read command. :unsure:
Code: 
[[email protected] sDebloater]$ sed -e '/^#/d' -e 's/#.*//g' -e 's/\"//g' -e 's/[ \t ]//g' -e '/^\s*$/d' it_does_not_work.cfg.txt > tmp.tx
[[email protected] sDebloater]$ cat tmp.tx 
Calculator2[[email protected] sDebloater]$ while read i; do echo $i; done < tmp.tx 
[[email protected] sDebloater]$
Notice the command prompt shares the same line with Calculator2 (after the cat command) since the was no carriage return at the end of the line.
The read command returns nothing.

Code: 
[[email protected] sDebloater]$ sed -e '/^#/d' -e 's/#.*//g' -e 's/\"//g' -e 's/[ \t ]//g' -e '/^\s*$/d' It_works.cfg.txt > tmp.tx
[[email protected] sDebloater]$ cat tmp.tx 
Calculator2
[[email protected] sDebloater]$ while read i; do echo $i; done < tmp.tx 
Calculator2
[[email protected] sDebloater]$
I will have to look into it a bit more.

Cheers. :cowboy:
 
Last edited:
  • Like
Reactions: Primokorn and zgfg
ipdev

ipdev

Recognized Contributor
Feb 14, 2016
2,399
1
4,835
Google Nexus 10
Nexus 7 (2013)
zgfg said:
<SNIP>
Btw @ipdev, there is also a bug if two or more app names are listed in the same line, separated by spaces (original sh input files did not have these issues) 😀
Click to expand...
Click to collapse
Not quite a bug. 😉
It was a trade off between multiple names and including comments inline.
Plus keeping the output temp file clean of extra spaces and empty lines.
I was trying to keep the sed command somewhat short. 😄​
​

That is why the instructions say. 🙃
ConfigScript - [wiki.github] - File Format
- One name per line.

Cheers. :cowboy:
 
  • Like
Reactions: zgfg
ipdev

ipdev

Recognized Contributor
Feb 14, 2016
2,399
1
4,835
Google Nexus 10
Nexus 7 (2013)
ipdev said:
@Primokorn @zgfg
Looks like it is a limitation of the read command. :unsure:
Code: 
[[email protected] sDebloater]$ sed -e '/^#/d' -e 's/#.*//g' -e 's/\"//g' -e 's/[ \t ]//g' -e '/^\s*$/d' it_does_not_work.cfg.txt > tmp.tx
[[email protected] sDebloater]$ cat tmp.tx 
Calculator2[[email protected] sDebloater]$ while read i; do echo $i; done < tmp.tx 
[[email protected] sDebloater]$
Notice the command prompt shares the same line with Calculator2 (after the cat command) since the was no carriage return at the end of the line.
The read command returns nothing.

Code: 
[[email protected] sDebloater]$ sed -e '/^#/d' -e 's/#.*//g' -e 's/\"//g' -e 's/[ \t ]//g' -e '/^\s*$/d' It_works.cfg.txt > tmp.tx
[[email protected] sDebloater]$ cat tmp.tx 
Calculator2
[[email protected] sDebloater]$ while read i; do echo $i; done < tmp.tx 
Calculator2
[[email protected] sDebloater]$
I will have to look into it a bit more.

Cheers. :cowboy:
Click to expand...
Click to collapse
Warning: Still testing. 😉
commit

Cheers. :cowboy:

Edit:
Using "It_works.cfg.txt"
SystemlessDebloater_v1.5.2.zip
Code: 
Input DebloatList="
Calculator2
"

Final DebloatList="
Calculator2"

SystemlessDebloater_v1.5.2-mod.zip
Code: 
Input DebloatList="
Calculator2

"

Final DebloatList="
Calculator2"

Using "it_does_not_work.cfg.txt"
SystemlessDebloater_v1.5.2.zip
Code: 
Input DebloatList="
"

Final DebloatList=""

SystemlessDebloater_v1.5.2-mod.zip
Code: 
Input DebloatList="
Calculator2

"

Final DebloatList="
Calculator2"
I do not like the extra space/blank line added to "Input DebloatList".
B.
 
Last edited:
  • Like
Reactions: galaxys
ipdev

ipdev

Recognized Contributor
Feb 14, 2016
2,399
1
4,835
Google Nexus 10
Nexus 7 (2013)
ipdev said:
Warning: Still testing. 😉
commit

Cheers. :cowboy:

Edit:
Using "It_works.cfg.txt"
SystemlessDebloater_v1.5.2.zip
Code: 
Input DebloatList="
Calculator2
"

Final DebloatList="
Calculator2"

SystemlessDebloater_v1.5.2-mod.zip
Code: 
Input DebloatList="
Calculator2

"

Final DebloatList="
Calculator2"

Using "it_does_not_work.cfg.txt"
SystemlessDebloater_v1.5.2.zip
Code: 
Input DebloatList="
"

Final DebloatList=""

SystemlessDebloater_v1.5.2-mod.zip
Code: 
Input DebloatList="
Calculator2

"

Final DebloatList="
Calculator2"
I do not like the extra space/blank line added to "Input DebloatList".
B.
Click to expand...
Click to collapse
@zgfg
Better way. 🙃

My Fork - [github] - commit

Using both Using "It_works.cfg.txt" and "it_does_not_work.cfg.txt"
Code: 
Input DebloatList="
Calculator2
"

Final DebloatList="
Calculator2"
No extra space/blank line added to "Input DebloatList".

Cheers. :cowboy:

PS.
I also added an uninstall script to clean up data/local/tmp log.
 
Last edited:
  • Like
Reactions: Primokorn, zgfg and galaxys
zgfg

zgfg

Senior Member
Oct 10, 2016
8,976
6,714
Redmi K20 / Xiaomi Mi 9T
Xiaomi Mi 11 Ultra
ipdev said:
@zgfg
Better way. 🙃

My Fork - [github] - commit

Using both Using "It_works.cfg.txt" and "it_does_not_work.cfg.txt"
Code: 
Input DebloatList="
Calculator2
"

Final DebloatList="
Calculator2"
No extra space/blank line added to "Input DebloatList".

Cheers. :cowboy:

PS.
I also added an uninstall script to clean up data/local/tmp log.
Click to expand...
Click to collapse
Thanks👍
@Primokorn - v1.5.3 with the cfg fix is released:
github.com

Release Systemless Debloater v1.5.3 · zgfg/SystemlessDebloater

Fix for SystemlessDebloater.cfg config file
github.com github.com
 
Last edited:
  • Like
Reactions: ipdev and Primokorn
You must log in or register to reply here.

Similar threads

T
  • Sticky
Magisk General Support / Discussion
Replies
56K
Views
6M
zgfg
zgfg
T
  • Locked
  • Sticky
Magisk - The Magic Mask for Android
Replies
56
Views
6M
T
topjohnwu
T
  • Locked
[CLOSED][BETA][2018.7.19] Magisk v16.7 (1671)
Replies
7K
Views
3M
T
topjohnwu
fOmey
[MODULE] Smali Patcher 7.4
Replies
8K
Views
2M
C
cepuchin
yochananmarqos
  • Sticky
Collection of Magisk Modules v2
Replies
1K
Views
1M
J
jacomail95

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 17
    zgfg
    zgfg
    Magisk 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 github.com

    GitHub - Magisk-Modules-Alt-Repo/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 github.com

    Wiki pages by @ipdev:

    ConfigScript

    Guide for the Systemless Debloater Module...
    github.com github.com
    with his examples of apps that can be debloated (Android, Google, Oppo, Samsung, Xiaomi, LineageOS):

    CommunityList

    Guide for the Systemless Debloater Module...
    github.com github.com


    *** 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 debloating
    View
    4
    kaefers
    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 ;]
    View
    4
    zgfg
    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:
    Code: 
    ## 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
    View
    4
    zgfg
    zgfg
    xadad said:
    After debloat all google app it stuck on logo, how can i reinstall packges?
    Click to expand...
    Click to collapse
    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...
    github.com 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)
    View
    4
    zgfg
    zgfg
    New version v1.5.0 is released:

    Release Systemless Debloater v1.5.0 · zgfg/SystemlessDebloater

    Automatically search through packages to find...
    github.com 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
    View

New posts