No matter what I try, I can't manage to delete system apps.
I'm rooted but nothing is working! I've tried:
Titanium backup, Root Explorer, System app remover - all with root granted permissions and even tried Selinux changer to permissive - all fail.
I've used Titanium Backup to freeze a number of system apps but I really want to delete Netflix as its coming up with errors about incompatible device and so need it deleting to start a fresh!
cd993 said:
No matter what I try, I can't manage to delete system apps.
I'm rooted but nothing is working! I've tried:
Titanium backup, Root Explorer, System app remover - all with root granted permissions and even tried Selinux changer to permissive - all fail.
I've used Titanium Backup to freeze a number of system apps but I really want to delete Netflix as its coming up with errors about incompatible device and so need it deleting to start a fresh!
Click to expand...
Click to collapse
I don't think you can unless you do to via a debloating magisk module
Related
I have installed titanium backup and should have permission to delete car home
But when i delete my phone only reboots 1time in I.P.V 2times and after reboot car home is still there in my list what to do
Hello!
You must mount your root-partition r/w.
You could use ES File explorer for this.
After that deleting apps with titanium backup should work.
Is Titanium in the granted list in Super User app?
If yes remove it the force a new Super User access authorisation.
Hey all,
I have rooted my HTC One. SuperSU works, as well as Titanium Backup, etc.
Some issues...
BusyBox will not install, and AdAware properly alters the hosts file, but after a reboot, AdAware is disabled and the hosts file seems unmodified.
I've also noticed that trying to make some applications "system apps" (sys/app) via Titanium Backup, it seems to work, and applications detect as having system permissions, but after a reboot the apps and permissions are gone.
Any ideas?
Thanks!
The system partition is shadowed, writing to it is temporary. For AdAware the fix is to flash a ROM with a symlinked hosts file, perhaps busybox is similar.
BenPope said:
The system partition is shadowed, writing to it is temporary. For AdAware the fix is to flash a ROM with a symlinked hosts file, perhaps busybox is similar.
Click to expand...
Click to collapse
Hmm...
I also noticed this...
I am using a Notification widget called Power Toggles, and one of the buttons is a Shutdown/Restart button. When I click it, and select Shutdown, Restart, Recovery, etc. it fails "because it doesn't have root access." I have given the application root permissions.
What is going on?
Titanium Backup Pro will not restore system apps.
Samsung Galaxy S6 SM-G920T
Titanium Backup 7.1.2 with Pro
Stock rooted with CF-Auto-Root
Tried SuperSU v2.45 - v2.46 - v2.49
The Problem
I made backup of apps that I would like to remove from the phone. I did a test by removing Amazon App. When I try to restore app, Titanium hand at restoring app, spinner will go for as long as I leave my phone on. Kill Titanium, reboot phone and I get a toast popup that Amazon has stopped. Amazon app icon in app draw, I touch to start app and get the same toast popup that Amazon has stopped. Start Root Explorer Pro navigate to system/priv-app Amazon app folder is not there. Navigate to system/app Amazon app is located here, but not in a folder and not with any support files. I tried this with a few other apps and it does not matter if they are located in system/priv-app or system/app same result.
I have search and found older threads that suggest changing Application Processing Mode to Interactive, but no mode changes have helped.
I also tried changing Mount namespace separation in SuperSU.
When applying these changes I have reboot the phone.
Any Ideas, please help.
Thank You
Nobody used Titanium Backup?
Nobody used Titanium Backup?
Can I get a Confirmation From Someone.
Muffin-Factory said:
Nobody used Titanium Backup?
Can I get a Confirmation From Someone.
Click to expand...
Click to collapse
You can try to use the titanium backup option of turning your backed up apk into a twrp flash able update zip.
I did try the search, but the answers were not clear as to the following questions:
If I am using systemless root, and I uninstall system apps, would that effectively modify "/system" and OTA updates will fail to install?
Also, I read that Titanium Backup is unable to uninstall system apps with systemless root and I need to manually delete the "/system/app/<app name>" folder with something like Root Explorer (mount /system r/w), is that true?
Thanks in advance
poodleDoo said:
.... delete the "/system/app/<app name>" folder with something like Root Explorer (mount /system r/w)...
Click to expand...
Click to collapse
OTA will fail on rooted devices.
System apps can be disabled in Settings. When deleted wit a rootexplorer the system partition is modified.
NLBeev said:
OTA will fail on rooted devices.
System apps can be disabled in Settings. When deleted wit a rootexplorer the system partition is modified.
Click to expand...
Click to collapse
Sorry, I should've been more clear.
I just installed FlashFire, and I am running systemless root.
If I delete a system app, would it prevent FlashFire to apply a OTA update; or is this a moot point?
And, I've read that with systemless, TiB does not actually remove system apps, is that true?
As for why I want to delete instead of just disable; why not?
Thanks
poodleDoo said:
If I delete a system app, would it prevent FlashFire to apply a OTA update....
Click to expand...
Click to collapse
The OTA checks modifications of system partition.
And, I've read that with systemless, TiB does not actually remove system apps, is that true?
As for why I want to delete instead of just disable; why not?
Click to expand...
Click to collapse
There is a lot written about 'systemless'.
The idea is that system files/folders are bind/linked to a 'su' folder. Apps are thinking that system is not modified.
Not all apps can be removed. Recently also Gmail can't be deleted. Disabling is the only option.
If you physically delete or change anything OTA will not work. Systemless SuperSU works by creating a Skylink with the user data partition and a modification withing the boot.img (the kernel). Any modification of any partition causes OTA to fail. So to successfully take an OTA you need to flash back the stock boot.img at the very least. Also the system.img if you made any modifications, and recovery if you are on twrp . . And modem.img and bootloader.img if they are not the ones that match the build you are on.
Sent from my Nexus 6 using Tapatalk
I'm having a problem getting to move any user app to the system partition on my Nexus 6. I'm using the Pure Nexus ROM, now rooted with Magisk, Android 7.1.2. The thing is, I have tried to do so when I was on Stock ROM, also tried it with SuperSU root instead of Magisk with no difference whatsoever. Link2SD doesn't work but neither worked system/app mover by j4velin.
What should I do to get that to work? Thanks in advance...
You're using Magisk... There are modules for that.
Two actually. And they can be installed from the Manager:
https://forum.xda-developers.com/apps/magisk/module-terminal-app-systemizer-ui-t3585851
https://forum.xda-developers.com/showthread.php?t=3477512
Take your pick.
Didgeridoohan said:
You're using Magisk... There are modules for that.
Two actually. And they can be installed from the Manager:
https://forum.xda-developers.com/apps/magisk/module-terminal-app-systemizer-ui-t3585851
https://forum.xda-developers.com/showthread.php?t=3477512
Take your pick.
Click to expand...
Click to collapse
Well right now for some reason Magisk isn't installing anything on my device, however I was wondering, if there is a method which installs the app as system and that the app continues to be there even if I unroot my device?
Dorlan2001 said:
Well right now for some reason Magisk isn't installing anything on my device, however I was wondering, if there is a method which installs the app as system and that the app continues to be there even if I unroot my device?
Click to expand...
Click to collapse
The whole design concept of Magisk is to protect the system partition from being modified. It does that by sym-linking directories. Using Magisk, as designed, the apps will go into the Magisk.img, not system. When booted, it'll look like the apps are in system but if you unroot they'll be gone.
If you don't care about modifying the system partition, you can move an app manually. User apps are in /sdcard/data/app and system apps are in /system/app. Once moved, you'll have to edit the permissions for the folder to rwxr-xr-x (755) and the apk inside the folder to rw-r--r-- (644).
ktmom said:
The whole design concept of Magisk is to protect the system partition from being modified. It does that by sym-linking directories. Using Magisk, as designed, the apps will go into the Magisk.img, not system. When booted, it'll look like the apps are in system but if you unroot they'll be gone.
If you don't care about modifying the system partition, you can move an app manually. User apps are in /sdcard/data/app and system apps are in /system/app. Once moved, you'll have to edit the permissions for the folder to rwxr-xr-x (755) and the apk inside the folder to rw-r--r-- (644).
Click to expand...
Click to collapse
Thanks for the info mate! It was really helpful to me to get to understand how Magisk works, and to be able to make the changes I wanted to my system using Root Explorer. Is so weird though, that those apps who claim to automate things, don't work on my device...
Thanks again!!!! :good: