What's the proper way to uninstall the pre-installed apps on Cyanogen like "Terminal Emulator," "Voice Dialer," "Car Home," "Latitude," "Navigation," and others, without messing things up in weird ways? I've tried using Blade Buddy and other techniques to mount the system as read-write but the system still won't offer me the ability to uninstall these permanent apps.
Thanks in advance.
aegrotatio said:
What's the proper way to uninstall the pre-installed apps on Cyanogen like "Terminal Emulator," "Voice Dialer," "Car Home," "Latitude," "Navigation," and others, without messing things up in weird ways? I've tried using Blade Buddy and other techniques to mount the system as read-write but the system still won't offer me the ability to uninstall these permanent apps.
Thanks in advance.
Click to expand...
Click to collapse
Don't uninstall. Freeze/block them using Titianium Backup Pro or the free Gemini App Manager. They will disappear from everything and won't run in the background, but still will be installed.
Sent from my NookColor using Tapatalk
I elected to su to root, remount /system as read/write, and then remove the offending apk files from /system/app. This effectively removes those apps which are either useless or annoying for Nook Color users, like "Camera" and "Car Home" and obsolete versions of "AndroidTerm," "Spare Parts," and "ROM Manager."
They disappear immediately for a nice, clean fix. I recommend wiping the Dalvik cache and rebooting after doing this, too.
Quick steps:
Start Terminal or login remotely using SSHDroid Pro (I much prefer the latter).
Type these things:
mount -o remount,rw /system
cd /system/app
ls -al
Then just type "rm filename.apk" where "filename.apk" is the app you want to remove. The filename rarely matches the name of the app on your launcher. Your apps disappear magically and immediately and may cause alarms to popup until you reboot.
I recommend deleting these from /system/app:
CarHomeGoogle.apk (unless you somehow find a need for this one in your car)
AndroidTerm.apk (and download the newest version from Google Play Android Market called "Terminal Emulator").
Camera.apk (worthless on Nook)
SpareParts.apk (badly outdated even in CM 7.2.0-RC1, download latest in the Market, and BladeBuddy, too)
RomManager.apk (likewise, get updated RomManager Premium one in the Market and pay the developer)
VoiceDialer.apk (since Nook doesn't have a microphone)
Phone.apk (this will popup errors until you reboot because Android's internals really seem to want this app to keep living no matter what, but rebooting makes things fine).
Note, don't delete "CMParts" as these are the Cyanogenmod settings in the Settings app.
Also, when people refer to "clearing the cache" or "clearing the Dalvik cache" or "wiping the cache" or "wiping the Dalvik cache" the easiest way to do this is by using RomManager's ClockworkMod feature and choosing "Reboot into recovery" and choosing "wipe cache partition" from the orange text menu that appears there. Or, choose "Mounts and storage," then "umount /cache," then, "format cache."
When you reboot your Nook Color after clearing this cache it *will* take up to seven or more minutes to start up so give it some time. You haven't killed it, so just be patient. If you abort this long restart it will just make your apps run slower for the first day but after that everything will run fast and fine.
Very informative aegrotatio . Thank you.
CyanogenMod's file manager seems to be stuck in safe mode, even though I have a rooted device and even have a modified kernel. I've not been able to figure out exactly what's happening. It says that only the accessible file systems are the storage volumes.
Anyone else have this problem, or does anyone know how to fix it?
RogueSly said:
CyanogenMod's file manager seems to be stuck in safe mode, even though I have a rooted device and even have a modified kernel. I've not been able to figure out exactly what's happening. It says that only the accessible file systems are the storage volumes.
Anyone else have this problem, or does anyone know how to fix it?
Click to expand...
Click to collapse
The default for the CM file manager is for root access to be turned off. With the file manager open go into settings and allow root access. Once you exit settings you'll have full access.
Nut_House said:
The default for the CM file manager is for root access to be turned off. With the file manager open go into settings and allow root access. Once you exit settings you'll have full access.
Click to expand...
Click to collapse
That's the problem. It won't allow root access, even though the phone has root access. The menu for the access mode is disabled.
RogueSly said:
That's the problem. It won't allow root access, even though the phone has root access. The menu for the access mode is disabled.
Click to expand...
Click to collapse
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
If you accidentally refused root access the first time you have to go into the SU app and clear out the File manager permission and start over.
Nut_House said:
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
Click to expand...
Click to collapse
I've already tried installing the latest nightly version and ran a permission fix on it, but end up with the same result. I'll try clearing cache, dalvik, and then fixing again.
gharlane00 said:
If you accidentally refused root access the first time you have to go into the SU app and clear out the File manager permission and start over.
Click to expand...
Click to collapse
The file manager doesn't have any permissions in SuperSU and never asks for any since it's not in root access mode. :\
Nut_House said:
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
Click to expand...
Click to collapse
Yeah, still the same result. Clearing dalvik and cache didn't work.
Just grab es file explorer.
Sent from my SPH-L720 using xda app-developers app
RogueSly said:
Yeah, still the same result. Clearing dalvik and cache didn't work.
Click to expand...
Click to collapse
same problem.
tried to install supersu, reinstall busy box on bin and xbin, fix permissions, no luck, option still greyed out.
file manager always worked for me as root, both on cm-based ROMs and aosp.
this time it is not working with the combo saberMod and matrix on N4.
(i think this is a device-independent issue)
---------- Post added at 08:20 PM ---------- Previous post was at 08:07 PM ----------
After a lot of tentatives I solved it.
I am not 100% sure of which change made it though
I think it was by using ES root manager and resetting system as R/W.
Sent from my Nexus 4 using xda app-developers app
Alternate fix
I also had the same issue and resolved it by tapping the menu button on the top left corner. when you do this, another menu button appears in the top right corner. Hit that, then settings, and choose root mode. Took me a while to figure out!!!
solved...
Installing busy box should resolve the issue...
Sorry for bumping, I have busybox and su installed, init.d support as well, but Cyanogen's File manager still cannot access root (option is grayed out). I'm on a stock Prestigio rom. It worked previously, but I reflashed firmware and now it doesn't work on this new firmware. Any thoughts?
Hi terirem and everybody,
I had this issue recently and I've managed to fix it. This is what You should do:
Short run:
Type in rooted phone terminal:
su
am start com.cyanogenmod.filemanager.ics
done
Long run:
1. Of course You need rooted phone, I've installed also BusyBox but I am not sure if it's necessary.
2. Install Terminal application
3. Install (if it's not installed yet) and run cyanogenmod file manager then minimize it by pressing home button (make sure You don't do anything else on Your phone to don't kill file manager process, it needs to be alive for 4th point)
4. I will make all commands bold for easier reading. run your terminal app and type: top -n 1 (this command will list all your running applications just once).
5. Find cyanogenmod in last "name" column, mine has name: com.cyanogenmod.filemanager.ics (if you can't find it you can try the one I had for 7th step, should probably work)
6. Type: su You will be asked to give superuser permissions to terminal, agree. Now instead of $ an # should appear, this means all commands from now on have root privilage.
7. Now we will finally rerun filemanager again with superuser permissions, type: am start com.cyanogenmod.filemanager.ics (if you had different name of filemanager just write the one you got after am start)
8. Go to cyanogenmod filemanager general settings and change access mode to root (it should be finally available, if not make sure again You typed am start with root permissions in terminal, if still doesn't work then forget about point 9).
9. Give me a beer, or actually simple thanks is enough, I need to stop drinking.
My SuperSU is kept auto-granting and system storage is kept read-written, also I cleared the every caches.
The CM file manager is still not shown a root mode to me.
I have J-rummy’s ROM toolbox as an alternative root explorer, but sometimes is less readable than CM file manager.
There is a guy forgetting to let the system storage read-written to remind him.
I did this with CM file manager - make sure you have root access not just safe mode in general settings. When you open filemanger it is granted super U access and then you can edit and save without issues
CM Dev Settings
In Dev options is Root access set to Apps and ADB?
For anyone else still having this problem, just erase the File Manager data (Settings | Apps | File Manager | Storage | Clear Data) with SU turned on in developer options. Then press the hamburger icon in the top-right of the app, press the settings icon on the bottom, click on General settings and you will see Access Mode
bsevcenk said:
For anyone else still having this problem, just erase the File Manager data (Settings | Apps | File Manager | Storage | Clear Data) with SU turned on in developer options. Then press the hamburger icon in the top-right of the app, press the settings icon on the bottom, click on General settings and you will see Access Mode
Click to expand...
Click to collapse
I am on CM13, now with SuperSU installed since I couldn't get the root option there to work well with some other apps for some reason.
File Manager now doesn't show any option for 'safe mode' or otherwise at all in settings. I cleared the data. I started it as in the earlier post. Nothing.
In the Developer options root is allowed, although only for ADB (the apps option has gone).
passtim said:
I am on CM13, now with SuperSU installed since I couldn't get the root option there to work well with some other apps for some reason.
File Manager now doesn't show any option for 'safe mode' or otherwise at all in settings. I cleared the data. I started it as in the earlier post. Nothing.
In the Developer options root is allowed, although only for ADB (the apps option has gone).
Click to expand...
Click to collapse
same here for me.
I'm working on a fix for now.
EDIT
If you're on a systemless SuperSU, use a terminal or ADB shell to input the following lines:
Code:
su
mount -o remount,rw /system
ln -s /su/bin/su /system/xbin/su
id74em8 said:
same here for me.
I'm working on a fix for now.
EDIT
If you're on a systemless SuperSU, use a terminal or ADB shell to input the following lines:
Code:
su
mount -o remount,rw /system
ln -s /su/bin/su /system/xbin/su
Click to expand...
Click to collapse
Apologies, but I'm no expert at these things. What is a 'systemless' SuperSU?
Is making a link as you suggest safe?
Hey guys, I wasn't planning on sharing this script I made about a week ago, but it makes such a big difference that it would be a crime to keep it to myself. I don't know about you, but Lollipop runs so much slower than KitKat after installing apps. The most annoying part is the general UI lag and responsiveness of apps like Chrome. I was reading google's documentation on how to properly configure memory management for low memory devices and came up with this script. You'll have the performance of KitKat and the custom 5.1.1 ROMS, but on Motorola Stock 5.0.2 firmware. I only tested on my XT1034, but it should work on XT1032 as well on stock ROM. I didn't test this on custom ROMs because I prefer stability. AND the fact that MinFree is write only, the script won't work well on custom ROMs I believe.
You'll get KitKat performance while keeping the multitasking abilities of Lollipop. ie, the music app won't get killed.
It should work on Stock Kitkat to an exent, but ZRAM is really needed, so find a KitKat kernel that has ZRAM enabled to see the same benefits.
This is what you'll need
Busybox https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
init.d script support https://play.google.com/store/apps/details?id=com.ryosoftware.initd&hl=en
Terminal Emulator (Optional) https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
Instructions:
1. Download the Zip on this page and extract it and put it wherever you want. I put it in the Root of the emulated sd card.
2. Download and install busybox. Run the app and grand it root access. Let it finish scanning your system and once it's done select the install button. You can get rid of the app once it's installed if you're worried about space, but don't uninstall from within the app, do it from system settings to keep busybox on /system.
3. Download and install init.d script support. Run the app and select "try to acquire root privileges." Grant it root access. Also, select "Run script at boot time" and under "Execution delay" select "No delay." Under "Select foder" add the folder "Scripts" and select the floppy disk icon to save the directory of the script. Select "Run" now to execute the script. The changes should have taken effect.
How to check if it's working
1. Open Terminal emulator and grant it root access, type "SU" and hit return/enter.
2. Type this "cat /sys/module/lowmemorykiller/parameters/minfree" without the quotes. and it should return these numbers: 12288,15360,18432,21504,24576,30720
3. Types this "cat /proc/sys/vm/min_free_kbytes" and it should return 2048
4. Type this "cat /proc/sys/vm/extra_free_kbytes" and it should return 0
Now go about your normal use and you'll notice a difference in performance. Let me know if this actually helped you out! To uninstall delete the script folder you extracted and the apps you downloaded and reboot. That's it!
For clarity sake here is what im trying to do.
take camera folder that has camera.apk in it with camera.odex in the arm64 folder and move it into my system/priv-app/ that should hypothetically install it as a system app after a reboot.
Im doing this on a nexus 6p with android N preview 2 and the only file explorer that mounts the system as R/W is FX File Explorer (While in booted system; i have full control via TWRP though)
I do reboot because i know 5.x+ requires reboots between system changes.
I have done this via FX and is stays there even after reboots. Ive done this via TWRP and stays after reboot.
my issue is that after a reboot, the camera app does not show in the system. Its not is the app list in settings and i cant find any instance of the android system recognizing it.
I have this issue no matter what the app is unless i install the app as a non-system app first then manually create its folder system in system/priv-app/ and copy the apk to its newly created folder then uninstall the non-system app version and reboot. But i cannont do that with every app. Some have to be system apps from the beginning or they refuse to install (as expected)
Any help on this will be hugely appreciated!
Any ideas guys?
Same problem on my Nexus 5 with Nougat rom. I hope someone can help.
I have had the Oneplus 5 for many years. After each update of OxygenOS I uninstalled some system apps (Chrome Google Photos, Gmail, Google Movies etc) in Solid Explorer (with root access).
But, since the update to OxygenOS 10.0.0 with Android 10 this does not work anymore. Solid Explorer says that the app has been deleted, but after a reboot it is still there.
When I try to uninstall one of the apps with Titanium Backup, the message "Cannot remove system app. Failed to locate the apk file."
Does anyone have an idea how to permanently uninstall and delete system apps?
Thanks!
Berta Paneslowski said:
I have had the Oneplus 5 for many years. After each update of OxygenOS I uninstalled some system apps (Chrome Google Photos, Gmail, Google Movies etc) in Solid Explorer (with root access).
But, since the update to OxygenOS 10.0.0 with Android 10 this does not work anymore. Solid Explorer says that the app has been deleted, but after a reboot it is still there.
When I try to uninstall one of the apps with Titanium Backup, the message "Cannot remove system app. Failed to locate the apk file."
Does anyone have an idea how to permanently uninstall and delete system apps?
Thanks!
Click to expand...
Click to collapse
On Android 10 it's not possible anymore to delete system apps directly from OS, even with root access. You must use Titanium for show the path of apps you want deleted, system apps are located on :
system/system/app
system/system/priv-app
Go in recovery TWRP
> mount Cache, System, Vendor, Persist, Data, Firmware partitions
> Advanced > File Manager > system/system/priv-app/Gmail > "Folder" button on right bottom > Delete
Do the same thing for all apps that you want deleted.
Actually,it does get deleted from a root explorer, however, few apps have symlinks as well, or few apps have stubs as well. Hence those may invoke reinstallation automatically. Those are the ones which need to be deleted permanently from recovery (especially).
As you have discovered, several apk files are system linked and so every reboot will bring them back. To counter this I use the xXx debloat script. The module is flashed in Magisk and allows one to select which apps and services you want removed. Here is a link to the module on xda: https://forum.xda-developers.com/showpost.php?p=82391573&postcount=2.
You can flash the module with stock settings or make a custom profile as I did.
I have a question or two...
1) Is it ok to convert Chrome and Google Maps from system to user apps in android 10?
2) Will first deleting the app using TWRP, then install it from Playstore convert the app from a system to a user app?