You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apps from List 1 are easily removed after rebooting but Apps from List 2 have no effect even on selecting apps and rebooting system .Also none of the apps that are selected have any user updates installed .
Only way to remove these apps is to use adb
I have also included the module folder for you with screenshots
Link Folder.zip
The text was updated successfully, but these errors were encountered:
@cleanerspam In fact, the directories in List 2 are not even added to De-Bloater. I really don't know Magisk can handle it (since it is not under /system directory). Of course, there is nothing wrong to try if you (or someone else) are willing to test.
I have uploaded the files and screenshot .
I am ready to test if you have any new ideas that might allow debloating on these partitions (I have magisk root but these partitions are read only , any modifications made to them in system mode causes bootloop ) so my only option is systemless methods
@cleanerspam In fact, the directories in List 2 are not even added to De-Bloater. I really don't know Magisk can handle it (since it is not under /system directory). Of course, there is nothing wrong to try if you (or someone else) are willing to test.
It can if you manually mount bind a empty folder on it on post-fs-data, like:
mount --bind $(magisk --path)/.magisk/modules/Debloat/empty /my_carrier/app/someappname
Directories that have System Apps
List 1
Now comes the partitions that are only used by Realme
List 2
Apps from List 1 are easily removed after rebooting but Apps from List 2 have no effect even on selecting apps and rebooting system .Also none of the apps that are selected have any user updates installed .
Only way to remove these apps is to use adb
I have also included the module folder for you with screenshots
Link Folder.zip
The text was updated successfully, but these errors were encountered: