[Q] How to delete or clear Superuser Permissions log? - Galaxy S I9000 General

After rooted my Galaxy S, everything work fine except one problem that I need help.
Under Superuser Permissions, I have seen a very long log, and there is no way to delete or celar them off my Galaxy s. For sure it will take up storage memory. No clear log option in Settings of Superuser Permission 2.3.4.
Any friend here can tell me how can I delete or clear this Superuser log? So that it won't eat up my storage space
Thank for advise and solutio n in advance

Related

Superuser permission blank

I am new to this whole rooting business so please forgive me. So I just finished rooting my device by putting update.zip into the internal memory and help the power button with the volume button. I then turn the device back on and immediately hit superuser permission app and it is blank. Did I do something wrong? How do I get other root apps on to this device? Thanks
If you have the superuser permission app and your phone is not a brick, then it seems you did evrything correctly. The permissions app is just a list of apps that need superuser permissions to work correctly. So because you have no other root only apps that need super user permissions the list is empty. When you install an app that needs super user permissions it will popup in the middle of the action and ask if "you want to grant permissions to this app" if you trust the app then hit allow. You should get a small confirmation after hitting allow.
Root apps are all over, some are in the market other aren't.
Now go download some root only apps.
I have a few I would recommend in the sticky fyi. ^ is correct, all sounds normal/good to me from what you described.

[Q] How to clear/delete Superuser Permissions log?

After rooted my Galaxy S, everything work fine except one problem that I need help.
Under Superuser Permissions, I have seen a very long log, and there is no way to delete or celar them off my Galaxy s. For sure it will take up storage memory. No clear log option in Settings of Superuser Permission 2.3.4.
Any friend here can tell me how can I delete or clear this Superuser log? So that it won't eat up my storage space
Thank for advise and solution in advance

Moving apps to the /system/apps directory?

I have about 60mb free in the /system/apps and would like to move my apps that are on the /data/apps partition to the system memory... so that way I don't have to worry about memory going down on the apps i know I want to keep..
Currently running cyanogen 6.0. I tried using root explorer to move the apps to the system but when i install them they aren't actually in the /system/app...
Thanks,
-Nigel
If you're using root explorer you don't actually "install" them. You just move them to the /system/app/ dir. After you do that you'll probably have to change the permissions on the file. To do that:
long press the .apk
select permissions
select all of the boxes on the 'read' column (left column)
select the 'user' 'write' box (top middle)
uncheck the other 5 if needed
You'll most likely have to reboot afterwards and you might need to clear the cache/davlik in recovery if you're getting FC's
If they're still not showing up fix the uid apk permissions in recovery or terminal
Recovery:
other > fix uid mismatches
Terminal emulator:
Code:
su
fix_permissions
Get Titanium backup for root -> Under "Batch" operations you have an option to move apps to SD and vice versa. You can select apps that you would like to move and run it.
Thanks for the reply.
The above method worked perfectly fine!
I think my problem was that I didn't reboot or wipe the chache...lol I just expected everything to be updated and when I checked it it still didn't chnage I was a little confused.! Awesome. Just freed up about 40mb!
I have titanium backup but dont' want to install apps to the SD card... I don't see that as a benefit.. when there is space else where that will never get used. Where as the SD cardw will keep growing due to music and things like that..
thansk for the help!!
-Nigel

[q] help removing pre-installed bloatware after rooting

my mt4g is rooted but i cant delete or move the bloatwares.
astro>system>app (it says: error deleting files)
i dont understand whats going on bcus the steps seem simple but somehow its neither deleting nor allowing it to be moved to my sd card.
any help would be most grateful. thanks in advance.
-----------------------------------------------------------------------------
and one last question. now that my phones rooted, s=off, may i delete visionary, the terminal emulator, and superuser???
>> i have more tasks running now that its rooted along with my inability to remove the bloatware
For your first question, astro cannot delete system apps if you're not mounted r/w, which you wont be by default. Root Explorer gives you the option to mount r/w and then delete apps. alternatively, you may want to install titanium backup and use the "freeze" feature so you can easily restore them if you want in the future.
You can remove visionary, and the terminal emulator if you want, but you'll need the superuser app to grant root permission to any apps that require root in the future.
Don't arbitrarily delete bloat. Use Titanium to freeze apps you don't want like option94 suggested. Some of those apps are tied into the sense ui and deleting them can make things screwy. After freezing in Titanium, if everything is working well, you can delete if you want. Make a nandroid backup before you do anything permanent. I would leave the stock rom alone and flash a rom like iced glacier which is basically optimized stock with all the bloat removed. Don't forget the make backup part.
Sent from my HTC Glacier
thanks i didnt quite understand what 'mount r/w' means or what it really does but as long as changing it to 'mount r/o' makes those unnecessary apps go away, im happy. thanks again
r/w = read/write - you'll be able to make changes
r/o = read only - you wont be able to make changes.

[Q] CyanogenMod file manager not able to switch to root access.

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?

Categories

Resources