Related
Im using the Root Explorer v2.10.2(which is the latest) to delete some unwanted system apks in system/apk folder, and im pretty sure i have already deleted those apks, but when i go into Settings->applications->manage applications, i still can find those deleted apks. Altho they are like 0 bite in memory, but still looks very annoying to me. Is there any way to get rid of those things in 'manage applications'? I have tried to search keywords in RootExplorer, and deleted the apk folders under data/data, and reboot my phone, and they are still there..
Also, if i click on any of those apks, "settings" will FC.
tzf123 said:
Im using the Root Explorer v2.10.2(which is the latest) to delete some unwanted system apks in system/apk folder, and im pretty sure i have already deleted those apks, but when i go into Settings->applications->manage applications, i still can find those deleted apks. Altho they are like 0 bite in memory, but still looks very annoying to me. Is there any way to get rid of those things in 'manage applications'? I have tried to search keywords in RootExplorer, and deleted the apk folders under data/data, and reboot my phone, and they are still there..
Also, if i click on any of those apks, "settings" will FC.
Click to expand...
Click to collapse
Did you try running fix_permissions?
Binary100100 said:
Did you try running fix_permissions?
Click to expand...
Click to collapse
hmm.. what is fix_permissions?
i searched on google and it says:
From a running ROM
To execute the fix_permissions script on your phone:
Open the "Terminal" app from the application drawer.
Type
su
fix_permissions
when i type fix_permissions in terminal, it indicates fix_permissions not found, i also tried fix_permissions.sh, still not found
tzf123 said:
hmm.. what is fix_permissions?
i searched on google and it says:
From a running ROM
To execute the fix_permissions script on your phone:
Open the "Terminal" app from the application drawer.
Type
su
fix_permissions
when i type fix_permissions in terminal, it indicates fix_permissions not found, i also tried fix_permissions.sh, still not found
Click to expand...
Click to collapse
what rom and recovery are you using?
Binary100100 said:
what rom and recovery are you using?
Click to expand...
Click to collapse
SMOKI 0.6.3, RA-hero-v1.6.2
it seems like the fix_permissions command can be used in CM ROMS..
tzf123 said:
SMOKI 0.6.3, RA-hero-v1.6.2
it seems like the fix_permissions command can be used in CM ROMS..
Click to expand...
Click to collapse
Try running fix_permissions from recovery.
its not working... those apks still stay in 'manage applications'.. altho recovery said its successful
Binary100100 said:
Try running fix_permissions from recovery.
Click to expand...
Click to collapse
LOL, problem solved, by editing the packages.xml under data/system, somehow the apk details are recorded in that file, so i just delete the corresponding codes and reboot my phone, walllllaaaaaaaaaa
AND, thanks a lot for your guide, LOL
tzf123 said:
LOL, problem solved, by editing the packages.xml under data/system, somehow the apk details are recorded in that file, so i just delete the corresponding codes and reboot my phone, walllllaaaaaaaaaa
AND, thanks a lot for your guide, LOL
Click to expand...
Click to collapse
Glad that you got it solved.
Also I hope that you don't mind by I edited your title because your problem wasn't specifically related to the Root Explorer app. This problem would occur if you had used any other means of removing the system app. By editing the title it'll make it easier for those that need assistance with a similar issue post their problems and find solutions. Adding [Solved] is effective to let them know that a resolution is available within the thread.
And it's not my guide, it's a reference for others that can't find the answer with the apparently evasive search feature.
Hey guys, I'm new to the rooting and xda community. I just rooted my mt4g a few days ago and am trying to figure out how to remove the tmobile "my account" application. I have seen a thread on xda where someone claimed to have removed it. I'm currently on ice glacier (latest version) i have titanium and super manager and busy box and all that jazz but im still not able to get it removed. Even after trying to force remove with titanium. if anyone could point me to the proper thread that has detailed instructions on how to remove that dastardly app or a video walkthrough that would be great. thanks for your help guys.
thefireinside369 said:
Hey guys, I'm new to the rooting and xda community. I just rooted my mt4g a few days ago and am trying to figure out how to remove the tmobile "my account" application. I have seen a thread on xda where someone claimed to have removed it. I'm currently on ice glacier (latest version) i have titanium and super manager and busy box and all that jazz but im still not able to get it removed. Even after trying to force remove with titanium. if anyone could point me to the proper thread that has detailed instructions on how to remove that dastardly app or a video walkthrough that would be great. thanks for your help guys.
Click to expand...
Click to collapse
easiest way in your case would be to open Super Manager > give it SU access via the settings menu > file explorer > then go do /system/app and look for it and delete it.
Go to Settings -> Apps -> Manage Apps, scroll to the app, select, and hit uninstall. If the uninstall button is greyed out, download a root file manager (such as Root Explorer, for example), and manually delete the APK from /data.
ive tried over and over through titanium and super manager, it just will not remove. i have also tried to find and remove the selfhelp.apk which seems to be what its listed under but all with no luck. still keeps popping up using my data and being annoying. thanks for your input guys.
thefireinside369 said:
ive tried over and over through titanium and super manager, it just will not remove. i have also tried to find and remove the selfhelp.apk which seems to be what its listed under but all with no luck. still keeps popping up using my data and being annoying. thanks for your input guys.
Click to expand...
Click to collapse
The only other thing I can think of is file permissions. You need a file manager that allows you to change the permissions to the appropriate type to allow you to remove a file. You can do that in Root Manager (change it form R/O to R/W).
thefireinside369 said:
ive tried over and over through titanium and super manager, it just will not remove. i have also tried to find and remove the selfhelp.apk which seems to be what its listed under but all with no luck. still keeps popping up using my data and being annoying. thanks for your input guys.
Click to expand...
Click to collapse
are you making sure to change the settings to SU access, and changing the ~/system folders to R/W.
TeeJay3800 said:
The only other thing I can think of is file permissions. You need a file manager that allows you to change the permissions to the appropriate type to allow you to remove a file. You can do that in Root Manager (change it form R/O to R/W).
Click to expand...
Click to collapse
to do this you want to go into the adb to terminal and type
Code:
$ su
# mount -o remount,rw -t yaffs2 /dev/mtdblk3/block /system
be care full this will make the entire phone r/w, deleting the wrong thing will FUBAR the phone.
then you'll want to type
Code:
ls /system/app
and see if it's in there, if not
Code:
ls /data/app
when you find it you'll want to type, depending on data or system you'll need to change it accordingly.
Code:
rm /______/app/<app name>
when you are done deleting what you want change everything back to -ro
Code:
mount -o remount,ro /dev/mtdblock3 /system
More information can be found here.
Haha yes, you can easily FUBAR the phone. FYI, Root Explorer can change file permissions with the click of a button, without having to do it manually through terminal.
I feel like I'm promoting RE a little too much, but it's what I've used for a long time with great success, so naturally it's what I suggest. neidlinger's method will accomplish the same thing, with the advantage of learning what's going on "behind the scenes."
As I'm new to rooting, is there any roms that come without myaccount already?
Sent from my HTC Glacier using XDA App
thefireinside369 said:
As I'm new to rooting, is there any roms that come without myaccount already?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
most of them do not include this in the ROM.
I've been running cm7 nightlies and now stable 7.0 for some time now. I have the new radio, ladios' kernel, and the sdcard read fix flashed.
I installed super manager and successfully deleted some of the stock cm7 media off my phone last week. Today, I came across the new GPS.conf files and wanted to try them.
Super manager couldn't switch the system to r/w despite saying "ok"
When I try to delete or write in the system with EStrongs file explorer, ghost commander, or android mate, they all give strange errors. The deleted files disappear but reappear after reboot. If I try to paste a file in system/etc I only get an error.
Superuser is successfully allowing permissions. I have the latest busybox. I have r/w enabled in each file manager.
I even tried an adb push test which first said "system is r/o only". The next try was "successful" but didn't do anything.
I'm still new with adb so I probably did something wrong. I typed in that r/w command, mount now shows: /dev/block/mtdblock3 on /system type yaffs2 (rw,relatime)
I can't figure out what changed and what I need to do to get r/w permissions. My only theory is that i had uninstalled and reinstalled super manager earlier and that somehow messed with my permissions.
You cannot permanently modify the system partition while the phone is booted into Android. The only way is to use adb while the phone is in recovery mode. Any changes you make while the phone is booted will be lost after a reboot.
Go check on those media files you thought you deleted. I bet you'll find they are still there.
Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...
jamus28 said:
Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...
Click to expand...
Click to collapse
You don't need to sign them on the aria
Sent from my Liberty using XDA App
jamus28 said:
Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Click to expand...
Click to collapse
Those programs will work on some phones but not the Aria.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...
Click to expand...
Click to collapse
It really is as simple as adding or removing a few files from the zip file if you want to modify it.
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?
Hi, playing around with an app called "Resolution Changer Pro", I set my phone to 350x350 in order to try a few things how my smartwatch would behave, which has also android and 400x400.
That went OK, and I was able to get back to fullHD fine.
Then I also changed the DPI accidentally to 100 and then the phone crashed.
Rebooting results in a black screen and I can´t do anything....
With adb I tried to set the resolution back to something usable, and the reply was that the window manger is not running.
Then I tried to get hold of the build.prop with adb and checked the DPI setting there, which was 480 .. the defailt setting.
Now my android knowledge is at the edge, and I don´t have an Idea how to reset the settings back to normal.
What could I do without deleting everything and re-flashing?
Pros.. what should I do ??? :crying::crying:
Flash same rom via recovery.
maitrot said:
Hi, playing around with an app called "Resolution Changer Pro", I set my phone to 350x350 in order to try a few things how my smartwatch would behave, which has also android and 400x400.
That went OK, and I was able to get back to fullHD fine.
Then I also changed the DPI accidentally to 100 and then the phone crashed.
Rebooting results in a black screen and I can´t do anything....
With adb I tried to set the resolution back to something usable, and the reply was that the window manger is not running.
Then I tried to get hold of the build.prop with adb and checked the DPI setting there, which was 480 .. the defailt setting.
Now my android knowledge is at the edge, and I don´t have an Idea how to reset the settings back to normal.
What could I do without deleting everything and re-flashing?
Pros.. what should I do ??? :crying::crying:
Click to expand...
Click to collapse
First you have to flash TWRP in order to use terminal in recovery.
Download AROMA Filemanager from here thanks to @amarullz
Go into recovery then flash it. (don't forget to mount system partition first.)
Guide to path /system/ then select Menu->open console
type in
vi build.prop
Click to expand...
Click to collapse
Once you open the build.prop with vi , you can now use the arrow button to guide to your section.
There's two mode in vi, edit mode and connamd mode.
You have to enter "i" first to enter edit mode
Once you finish editing, press Esc on top and now you are back to command mode
Enter following command to save the file and quit:
:wq
Click to expand...
Click to collapse
Now press Close on right top then press menu and exit file manager, reboot your device.
You are done.
TIPs: Here's an useful command to delete a line that you can't use delete to eliminate
In command mode, type in following command to delete a line:
:dd
Click to expand...
Click to collapse
1. Ok, flashing the same rom did not help... this was the first thing I tried.
2. I already tried to work with my build.prop, which I downloaded with adb from the device.. I already said that in my first post.
In the build.prop the dpi setting is at 480, like I said. Modyfiying it from twrp with vi is the same as downloading it via adb and then modyfiying it locally and uploading it again..... this did not help, dpi was at 480, like I said.
Strange... right?
Where is the screen resolution saved? Dpi is in build.prop, but where is the resolution saved at?
The problem must be somewhere in the data partition, since flashing does not help. I erased system and re-flashed. no help.
maitrot said:
1. Ok, flashing the same rom did not help... this was the first thing I tried.
2. I already tried to work with my build.prop, which I downloaded with adb from the device.. I already said that in my first post.
In the build.prop the dpi setting is at 480, like I said. Modyfiying it from twrp with vi is the same as downloading it via adb and then modyfiying it locally and uploading it again..... this did not help, dpi was at 480, like I said.
Strange... right?
Where is the screen resolution saved? Dpi is in build.prop, but where is the resolution saved at?
The problem must be somewhere in the data partition, since flashing does not help. I erased system and re-flashed. no help.
Click to expand...
Click to collapse
Then you should backup before flashing or doing root permission changes.
You can now do a fully backup , data, cache anything And then flash the stock firmware via SP_FlashTool.
If you boot, then try to restore the partition one by one.
jwchen119 said:
Then you should backup before flashing or doing root permission changes.
You can now do a fully backup , data, cache anything And then flash the stock firmware via SP_FlashTool.
If you boot, then try to restore the partition one by one.
Click to expand...
Click to collapse
Ok, I did that... made a backup of all partitions, erased everything and re-flashed latest dev firmware.
Off course, everything works fine now, but all my settings and stuff are lost.
going back to my old data partition, the problem is back.
How can I get back to my old settings? What do you mean one by one?