hello all
I do not understand this action to
can you detail
"change permisions ro rw-r-r, reboot!"
thank you
ps: if there was a Frenchman I'm ok
Linux based OSes all use a similar file permission system you can read in detail on Wikipedia:
http://en.wikipedia.org/wiki/Filesystem_permissions
To change permissions I like to use Root Explorer, here is a video tutorial:
http://www.youtube.com/watch?v=RI08wNsanLY
or just go into recovery and sellect fix permissions
Using Root Explorer
I used Root Explorer, went into system/app, and if you select the view button you can select details instead of icons, this will show you the permission settings of your other applications. rw-r--r--
by long pressing on your application you wish to change, select permissions from the menu. A pop up shows the follow titles.
Read Write Execute
Owner
Group
Others
Select the boxes to match your permission.
Owner: Read and Write
Group: Read
Others: Read
cyneogenmod
hello
new problem after having instaler miracle V1 and V2 I have this message when trying to open cyano
"closing process com.android.settings"
someone has a small idea to settle the problem?
Related
Since i got some problems on both my streaks while permanently rooted (lost network connectivity during calls and some crashes) i found a way to keep my lcd density setting saved without being permanently rooted. You have to add the lcd density value in build.prop since it's missing on Froyo.
Here you go:
- root your device with z4 from market
- install root explorer from market
- open root explorer and navigate to /system
- be sure to change "mount r/o" to "mount r/w" in the top left corner
- now search for "build.prop" and longpress it
- select "open in texteditor" to edit the file
- add the following line: "ro.sf.lcd_density=220" (change the value to your desired number)
- save changes and hit "mount r/w" again to change to r/o
- exit root explorer
- now run z4 and press undo-root
- after root is being removed uninstall z4 and reboot your device
Your LCD density is now saved to your desired value without being permanently rooted!
Hope this helps some of you who face similar problems with rooted streaks!
Or if you use DJ Steve's build, you can already edit the update.zip file beforehand .
As the question says, how to install? Permissions need to be changed?
when you get the apk use something like root exporer or w/e to push it to /system/app and set the permission to rw-r--r--
Code:
read write execute
owner X X -
group X - -
Others X - -
Don't forget to reboot afterword
I thought this might help and add to the knowledge base of our subforums. This is a basic, roughly pieced together reference. So, some of you may have noticed mention of setting file permissions to 644, for example (or 755). This format of file permissions is called CHMOD (short for "change mode"). It determines how much access a file should have. For the sake of simplicity, I'll leave it at that.
I'll go over what each digit (1-7) represents, which is some variation/combination of having read, write, or execute permissions. In Root Explorer, for example, there are three lines - Owner, Group, and Others. In file permissions, the three digits represent the permissions allowed for the aforementioned Owner, Group, and Others. The first digit represents Owner, the second digit represents Group, and the last represents Others.
644 =
Owner - 6
Group - 4
Others - 4
*644 is also referred to as rw-r-r (i.e., read and write permissions for Owner, read only permissions for Group, and read only permissions for Others).
Here's what each number is the equivalent to:
Code:
[B]0[/B] - No Permissions
[B]1[/B] - Execute Only
[B]2[/B] - Write Only
[B]3 [/B]- Write and Execute Permissions
[B]4[/B] - Read Only
[B]5[/B] - Read and Execute Permissions
[B]6[/B] - Read and Write Permissions
[B]7[/B] - Read, Write, and Execute Permissions
Most system files have permissions of rw-r-r/644, while scripts have 755.
FYI, each number of a bitmask with three buts.
1 = execute
2 = write
4 = read
To get the combo you want, add the numbers together for the bits you want.
Note that while you can set a file to be executable but not readable, this usually doesn't work or causes WEIRD stuff to happen.
that helped. thank you : )
!!! You require root rights !!!
1. If you have old or any other flashplayer, uninstall it;
For further manipulation, I used RootExplorer
2 . Copy ,,Flashplayer.apk" to the folder /system/app and set permissions to "rw-r - r -
3 . In folder /system/lib create a new folder name "plugins". This folder permissions set to "rwxr-xr-x"
4 . In Folder "plugins" , create another folder name "com.adobe.flashplayer" and just change permissions to "rwxr-xr-x"
5. Copy ,,libflashplayer.so" to the folder /system/lib/plugins/com.adobe.flashplayer and set permissions to "rwxr-xr-x"
6. Reboot the device .
7. After restarting the application menu, run flashplayer.
If you see settings page flashplayer, then it is working
Tested and it's working on my Lenovo K900
hi Everyone,
I'm sticked with the common issue of how to make writable the external SD.
I've read topics on the forum:
http://forum.xda-developers.com/desire-601/help/how-to-writable-external-sd-kitkat-t2877686
http://forum.xda-developers.com/desire-601/help/sd-card-permissions-off-t2833195
http://forum.xda-developers.com/showthread.php?t=2687734
Well ok, but I'm a noob so sometimes it's not clear, sometimes it's not working for me.
So let's explain:
- My device is rooted (it was made by a tech using TWRP if I'm right)
- SuperSU is installed
1/ I tried some apps like SDfix and Int-SDCard Write fix
> Result = KO
2/ I tried to manually modify the platform.xml file > sometimes the editor does not want to save the modification, sometimes it says OK but the file don't seem to be modified (the last modification date is still 2014). Permissions are: rw-r--r--
a. Using Rom Toolbox, I go the file and edit it with:
-FX TextEdit > Get a Warning = "This file is on read-only filesystem. You will not be able to save any changes unless you first remount it as read/write'
> Result = KO
- RB Text Editor: it seems i can edit it. Save the file without warning message 'Saved'. But once back on the /system/etc/permissions folder, nothing looks modified (not today's date). I can reopen the file and see the modification by the way. But once I reboot, I go back the my original issue.
> Result = KO
- ES Text editor: can't even save the file
> Result = KO
So what ?
I've seen this message coming along:
"if you are rooted then you doing something wrong (did you maybe forgot to mount system as R/W ?).
If you are unable to do modify platform.xml then you doing something wrong or yours device isnt rooted."
> At what moment is it possible to mount the system with R/W grants ?
I'm fed up with not being able to write on SD card....................
Thx in advance !!!!!
Opening a terminal on my phone:
- i can't 'cp file1.xml file2.xml' in /system/etc/permissions
- i can't 'chmod 644 file1.xml'
Each I get "Read-only file system"
Flash your stock kernel with insertcoin or kofilakernel