This worked (re-enabled writing to sdcard2) for me on my Sony Tablet SGPT112USS updated and rooted ICS 4.0.3. I used ROM Toolbox app to mount the file system as rw, used a text editor to make the change to platform.xml, then used ROM Toolbox to mount the file system back to ro. Hope this helps. Found this on the web. Thanks to the original poster (forgot their handle).
1. Using a root-enabled file manager, navigate to /system/etc/permissions and make sure you have mounted the file system r/w.
2. Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission.
3. Add an additional group definition for this permission...<group gid="media_rw" />
4. Save the changes to the file.
5. Restart your tablet.
After editing platform.xml file my both sdcards are not writable anymore...looking for some help on this
Your changes made the platform.xml file invalid and thus unusable causing more errors ont he way. Check it with XML parser for errors (loading it in browser like firefox or chrome, which supports xml will do) - the couse will be probably something trivial like using wrong quote characters or unclosed xml tag.
ok i have easy solution for those who cannot change permission to vendor
i downloaded AntTek Explorer
https://play.google.com/store/apps/...251bGwsMSwxLDEsImNvbS5hbnR0ZWsuZXhwbG9yZXIiXQ..
this xplorer enable rw to vendor partition
to do this, enable superuser when it pops up to the AntTek App
then click the yellow circle flashing icon on the upper right corner
then choose root on the pop up
then go to system, then try to find vendor folder, press and hold it
choose remount partition on the new pop up, choose RW
then its now RW
vendor partition have a lot of junk apps, if you can remove some of it by using another xplorer (such as SuperManager)
a lot of space will be free'd. you can put some of your apps there to that system will not be easily full.
the right permission for the apps on the vendor/app partition is:
O O -
O - -
O - -
take note that if you turn off your phone, the vendor partition will automatically set again to R/O
Thanks man,
Your post realy helpfull for me,
Finally i can Allow RW to Vendor Partition in my Xperia Neo :good:
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
In my search to find a way to disable the fixed bootanimation on my X96 I not only found the solution but also some nice "feature".
A normal bootanimation comes as a bootanimation.zip and usually without sound.
A video boot is a MP4 file with sound and all
To enable video boot a line in the build.prop needs to be edited/added:
service.bootvideo=1 this enables the bootvideo, service.bootvideo=0 makes use of the normal bootanimation.zip, same for not having this line.
The actual bootvideo is as said a MP4 file named bootvideo and is located in the etc folder of the system partition - if not you need to make one
Any resolution the box supports can be used here but for obvious reasons it should be only as long as the actual boot might take.
There should be a file bootplayer inside the /system/bin folder - this is used to play the video.
In case it still won't work with all the above files you need to add a service in the init.amlogic.rc file of your kernel.
Code:
service bootvideo /system/bin/bootplayer /system/etc/bootvideo
class main
user root
group system
disabled
oneshot
I tested and confirmed it works with basically any MP4 video on my X96 but assume it should work the same way on all 3.14 kernels.
Another option, you can do so
Code:
#service bootvideo /system/bin/bootplayer /system/etc/bootvideo
service bootvideo /system/bin/bootvideoplay.sh
class main
user root
group system
disabled
oneshot
and place to /system/bin/bootvideoplay.sh with this
Code:
#!/system/bin/sh
MARK=/data/media/0/Download/bootvideo
if [ -f $MARK ]; then
bootplayer /data/media/0/Download/bootvideo
else
bootplayer /system/etc/bootvideo
fi
If there is a file /data/media/0/Download/bootvideo (internal sdcard) , will be play this video
Nice one!
Did not even consider using a check in the init file - will keep that in mind for sure
Checked the way with the script but no matter what I try it simply shows no video at all.
But works fine by just using the medi folder instead of ETC, SDCARD won't work either.
For the SD it makes no difference is SDCARD is used for the path or the direct mountpoint.
Seems the bootplayer is a bit restricted if it does not run directly as a service.
But can't be bothered too much as I only use one video anyway LOL
Still image
There is a way to remove the X96 image as the first image? I changed the video all ok, but the image before bootvideo remains the same. What is tha file that I need to change? Thanks a lot!!!
That would be the bootlogo, flash a new one or use an app tp change it.
I only exchange them together with the firmware and so far did not bother otherwise.
Downunder35m said:
That would be the bootlogo, flash a new one or use an app tp change it.
I only exchange them together with the firmware and so far did not bother otherwise.
Click to expand...
Click to collapse
I searched all the bins for the bootlogo file, but I can't find it. Do you know in wich bin it is located?
No bin, inside the bootloader partition
Downunder35m said:
No bin, inside the bootloader partition
Click to expand...
Click to collapse
Hi, friend. Thanks for your reply. I'm a bit newbie. How can I access the bootloader partition and access its contents?
Downunder35m said:
In my search to find a way to disable the fixed bootanimation on my X96 I not only found the solution but also some nice "feature".
A normal bootanimation comes as a bootanimation.zip and usually without sound.
A video boot is a MP4 file with sound and all
To enable video boot a line in the build.prop needs to be edited/added:
service.bootvideo=1 this enables the bootvideo, service.bootvideo=0 makes use of the normal bootanimation.zip, same for not having this line.
The actual bootvideo is as said a MP4 file named bootvideo and is located in the etc folder of the system partition - if not you need to make one
Any resolution the box supports can be used here but for obvious reasons it should be only as long as the actual boot might take.
There should be a file bootplayer inside the /system/bin folder - this is used to play the video.
In case it still won't work with all the above files you need to add a service in the init.amlogic.rc file of your kernel.
Code:
service bootvideo /system/bin/bootplayer /system/etc/bootvideo
class main
user root
group system
disabled
oneshot
I tested and confirmed it works with basically any MP4 video on my X96 but assume it should work the same way on all 3.14 kernels.
Click to expand...
Click to collapse
Hello,
I set the 1 in the build.prop, added the line to the init.amlogic.rc and put my mp4 intro video and your attached files to the places. 1. Reboot -> I become your x96 bootvideo. I deleted the bootvideo file from your attached files and I dont become a bootvideo. Whats wrong? My bootvideo.mp4 is already in the system/etc/
getting permission error
unfortunately, I am getting permission issue. I have verified that I am root and write permission to root. I am using X96mini Amlogic Box . any help?
p281:/ # whoami
root
p281:/ # cp /sdcard/virtukiosk-video-v1.mp4 /system/etc/bootvideo1
cp: /system/etc/bootvideo1: Read-only file system
1|p281:/ # ls -ld /system/etc/bootvideo
-rw-r--r-- 1 root root 9149031 2017-10-09 09:31 /system/etc/bootvideo
p281:/ # ls -ld /system/etc
drwxr-xr-x 13 root root 4096 2017-10-09 09:48 /system/etc
p281:/ # ls -ld /system
drwxr-xr-x 20 root root 4096 2018-01-04 17:49 /system
p281:/ #
Thank you! works perfectly.
I just edit the build.prop seems it was there (bootvideo and bootplayer) already in my MXIII S802 box.
@ nigam214
Try to use EZ Explorer or any Root explorer for easy File transfer.
Hi.
I have a problem.
i can see my files in this path : /data/media/0/android/obb ( i have read and Write access)
but i cant see any files in this path : /storage/emulated/0/android/obb . it is empty and i can't write any thing on it.
how can i fix it?
Android is able to mount a single partition into multiple point in system (which represented in folder).
As in each folder, a user and an application have a different permissions regarding any execution against the folder.
Thus, the difference that you're experiencing. To solve this is to set the permission of both folder in the same way.
To set the permissions, your phone have to be rooted and using an application that could change folder/file permissions.