Looking for some clarification on app permissions, i.e. Owner, Group, Others, Read, Write, Execute.
Using Root Explorer or adb we can change the permissions of files and folders.
How important is it that a particular application have the correct permissions?
Does is really matter if an app has Group Write if it is not supposed to?
When pushing apps with adb, how are permissions determined? Is it ok to leave them as adb sets them?
I have done alot of adb pushing and the permissions after are never the same as they were originally.
Related
I am trying to sync a rostering app between two devices using dropsync.
The .db files that need syncing are in the /data/data/com.blah.blah/databases directory. Using Root explorer I can change the permissions to give full rw permission to others. The two .db files will then upload to the dropsync server.
The problem is that whenever the app is opened and anything modified, the permissions change back to default and thus dropsync can't access the modified .db
Is there anyway to change this or am I wasting my time? what is the 'sticky' box option in RE?
I'm not sure precisely what "sticky" means, but it's not what you want--it doesn't involve persistence or "sticking".
You could try to make the files not owned by the app but set it so the group is the app. Make sure the group can read/write/execute, or whatever it needs. This way, the app can still use the file but won't be able to change its permissions.
Of course, it could see that it doesn't own the file and refuse to run. I'm not sure what sort of checks the program's authors implemented. This also won't work if the file is deleted and created anew--the new file would be owned by the app.
Yeah thanks for that,
I tried the ownership and group swap earlier, and am pretty sure the app re- writes the db.
Don't think is going to work.
cheers
Well its obvious that the app, when opened sets the permissions to the .db files so that they wont be usable by others. The way you describe the problem is more likely to be a file owner problem and not with the permissions. Try to set the app and the files to the same owner and see if that works. You could always make a script that would change the permissions/ownership of the file.
FYI,
The sticky bit is a special part of the permissions mask for a file or directory. When set on a directory, it tells the system to prevent anyone but a containing file's owner from deleting files in that directory. This is handy if you have a directory that's being used by multiple users on a system as scratch space as it prevents people from wiping out others' files.
For files....the behavior isn't defined.
Hope this helps,
- chris
I am trying to delete a folder in internal storage that has a bunch of sound files in it. I keep getting this error. I have permissions set to 777 and I am root. Also tried terminal and got access denied.
xShockz said:
I am trying to delete a folder in internal storage that has a bunch of sound files in it. I keep getting this error. I have permissions set to 777 and I am root. Also tried terminal and got access denied.
Click to expand...
Click to collapse
Have you changed the permissions on the parent folder as well? I think deleting files/folders requires permissions on the parent.
Also, what file explorer are you using (don't recognize it from the pic) and does it have root permissions?
AliceBToklas said:
Have you changed the permissions on the parent folder as well? I think deleting files/folders requires permissions on the parent.
Also, what file explorer are you using (don't recognize it from the pic) and does it have root permissions?
Click to expand...
Click to collapse
Yeah, that doesnt work either.
If I look at all the existing .apk files in /system/app, I see that they all have 644 as their permissions. Is that what's usually expected?
If I add a new .apk to /system/app, I have read that I need to set its permissions to 755. Is that true?
I also read that I need to change all the existing .apk files from 644 to 755. Is that true as well? If so, I am curious as to why since I am not looking at changing any of those.
WaltA said:
If I look at all the existing .apk files in /system/app, I see that they all have 644 as their permissions. Is that what's usually expected?
If I add a new .apk to /system/app, I have read that I need to set its permissions to 755. Is that true?
I also read that I need to change all the existing .apk files from 644 to 755. Is that true as well? If so, I am curious as to why since I am not looking at changing any of those.
Click to expand...
Click to collapse
--the same question!
--need expert explain
--thanks in advance!!!
Wow, no one can help? :crying:
WaltA said:
If I look at all the existing .apk files in /system/app, I see that they all have 644 as their permissions. Is that what's usually expected?
If I add a new .apk to /system/app, I have read that I need to set its permissions to 755. Is that true?
I also read that I need to change all the existing .apk files from 644 to 755. Is that true as well? If so, I am curious as to why since I am not looking at changing any of those.
Click to expand...
Click to collapse
all apk in system must use 644 for the permission, if not, the apk won't be installed, but not all apk/app working if you put in system folder, for example, if you put opera mini in system folder, the application will not even you have set it the permission at 644,
and the best to add/install new app in system use manually way
1. choose apk that you want
2. put in the system/app
3. set permissions to 644
4. reboot
if success, the app will appear on menu,
Don't forget to hit THANKS button
Hi, I am student from University would like to ask do you know how I can start this task that I gave myself to complete.
list all permissions, check against database of what permissions should be for those applications and flag up if any installed app has more permissions than it should.
I know, application permission is located in the manifest.xml, but if i use ADB method to list all the permissions, I cannot find a method to list all the permission that belongs to one app only. I would like to check and compare to see if any of the installed application has more permission than it should be.
Any help would be appreciated, as I am just learning.
Nicholasc001
After root I deleted DefaultContainerService.apk by mistake but one good thing is I had copied terminal, linuxforandroid and ROOT Explorer to the system/app folder.
Bad thing is these 3 apps are not installed by default even though it is in system/app folder. (Other pre existing apps are installed) when the reset happens.
I am not able to install any apps now without DefaultContainerService :crying:
Even after format I am having root format.
When you move apps to /system, they must have permissions set to 0644 then reboot to have it take affect. If you can find a stock based rom, you should be able to extract that apk and move it to system, set permissions, reboot and good to go.
Partial
The solution is great. i used adb and changed the permission and reset the phone.
I can see the app installed but when i open it it tells failed.
I found temp solution of pushing DefaultcontentProvider through adb but still I want it to be in default app list. Do not want to push after every reset.