Related
I have owned a number of tablets but this is the first time I'm unable to write files to my ext. SD card. Anyone else have this issue?
Thanks
Mr Dasher said:
I have owned a number of tablets but this is the first time I'm unable to write files to my ext. SD card. Anyone else have this issue?
Thanks
Click to expand...
Click to collapse
I have the same issue when using any 3rd party file manager, but doing such through the built in one works. I suspect I just need to back up and format the card through the computer, try that and see how it works.
I ran into the same issue, but reformatting the external SD have no effect. Whether the system is grabbing hold of the extSD and locking out other apps is as yet unknown. Currently I am attempting to figure out how to root the unit so I can gain access with a better FileMngr than the stock one. Still waiting for the download during the reset to finish, so don't know if it will work.
FYI - My device is rooted and I am using ES File Manager and it still does not work.
Mr Dasher said:
FYI - My device is rooted and I am using ES File Manager and it still does not work.
Click to expand...
Click to collapse
Have you format your sd card? I've got same problem, but now it's ok with ES File manager
gacon1000 said:
Have you format your sd card? I've got same problem, but now it's ok with ES File manager
Click to expand...
Click to collapse
Are you sure? Try this:
Reboot the tablet.
Before you do anything else, start ES File manager, and immediately navigate to /mnt/sdcard/extStorages/SdCard.
Menu->New->Folder (leave the default and hit 'OK')
Did it create the folder or show an error message?
(This has become a puzzle for me. Sometimes I can read/write with ES, sometimes I can't. It's damn annoying...)
Mr Dasher said:
I have owned a number of tablets but this is the first time I'm unable to write files to my ext. SD card. Anyone else have this issue?
Thanks
Click to expand...
Click to collapse
I can't post a link to the original post on another forum that worked for me so I will quote it:
Simple solution for external sdcard write access on Android 3.2...if you're rooted
I've found a simple solution for gaining write access to the external sdcard (/mnt/sdcard2) on Android 3.2. The sdcard is mounted r/w, but the owning group is media_rw which is linked to the WRITE_MEDIA_STORAGE permission. Unfortunately, this permission was not required for access to the external sdcard prior to 3.2 so most file management utilities do not request it when they run...meaning they only have read access to the card.
The simple solution, if you're rooted, is as follows:
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 this change, any apps that request the WRITE_EXTERNAL_STORAGE permission (which includes almost anything that access either of the sdcards) will gain group membership in both sdcard_rw AND media_rw, giving them r/w access to both sdcard filesystems.
Interesting that it requires root to fix. You would think that even the Samsung file manager would be able to handle it, but it doesn't.
thaloneus said:
I can't post a link to the original post on another forum that worked for me so I will quote it:
Simple solution for external sdcard write access on Android 3.2...if you're rooted
I've found a simple solution for gaining write access to the external sdcard (/mnt/sdcard2) on Android 3.2. The sdcard is mounted r/w, but the owning group is media_rw which is linked to the WRITE_MEDIA_STORAGE permission. Unfortunately, this permission was not required for access to the external sdcard prior to 3.2 so most file management utilities do not request it when they run...meaning they only have read access to the card.
The simple solution, if you're rooted, is as follows:
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 this change, any apps that request the WRITE_EXTERNAL_STORAGE permission (which includes almost anything that access either of the sdcards) will gain group membership in both sdcard_rw AND media_rw, giving them r/w access to both sdcard filesystems.
Click to expand...
Click to collapse
@thaloneus:
Thanks for finding and posting that procedure. Was having that excact problem and after making the edit to permissions I am now able to write to the external sd card. ES file explorer now allows writing to the external sd as well as Titanium Backup.
Interesting note: Titanium was backing up to the internal sd. Once the external became available to write to I was able to create a backup folder there and ran another batch of backups.
thaloneus said:
I can't post a link to the original post on another forum that worked for me so I will quote it:
Simple solution for external sdcard write access on Android 3.2...if you're rooted
I've found a simple solution for gaining write access to the external sdcard (/mnt/sdcard2) on Android 3.2. The sdcard is mounted r/w, but the owning group is media_rw which is linked to the WRITE_MEDIA_STORAGE permission. Unfortunately, this permission was not required for access to the external sdcard prior to 3.2 so most file management utilities do not request it when they run...meaning they only have read access to the card.
The simple solution, if you're rooted, is as follows:
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 this change, any apps that request the WRITE_EXTERNAL_STORAGE permission (which includes almost anything that access either of the sdcards) will gain group membership in both sdcard_rw AND media_rw, giving them r/w access to both sdcard filesystems.
Click to expand...
Click to collapse
Thanks worked like a charm
Please someone provide me more details or give me the picture of the edited .xml thanks.
Sent from my GT-P6200L using Tapatalk
boonhim said:
Please someone provide me more details or give me the picture of the edited .xml thanks.
Sent from my GT-P6200L using Tapatalk
Click to expand...
Click to collapse
Here is a screenshot of the edited .xml
Sent from my GT-P6210
StingerDog said:
@thaloneus:
Thanks for finding and posting that procedure. Was having that excact problem and after making the edit to permissions I am now able to write to the external sd card. ES file explorer now allows writing to the external sd as well as Titanium Backup.
Interesting note: Titanium was backing up to the internal sd. Once the external became available to write to I was able to create a backup folder there and ran another batch of backups.
Click to expand...
Click to collapse
From what Ive found you need superuser access to the external sdcard to write to it. I've always been able to access the external sdcard with Titanium Backup as the location of the backup was the first thing I changed in its settings when I installed it. Root Explorer can write to it too. The only programs that can't are the ones without superuser access, ES File Explorer is one I have that I can't get its root explorer working, its not requesting superuser access, so it can't write to the sdcard.
Not sure if this has anything to do with the sdcard mounting to a pc as an MTP device instead of MSC or not but really irritated by that protocol. Not sure if this (MTP) is native to Honeycomb or if Samsung wanted the external storage accessed in this way.
Thank so much.
Sent from my GT-P6200L using Tapatalk
kzoodroid said:
From what Ive found you need superuser access to the external sdcard to write to it. I've always been able to access the external sdcard with Titanium Backup as the location of the backup was the first thing I changed in its settings when I installed it. Root Explorer can write to it too. The only programs that can't are the ones without superuser access, ES File Explorer is one I have that I can't get its root explorer working, its not requesting superuser access, so it can't write to the sdcard.
Not sure if this has anything to do with the sdcard mounting to a pc as an MTP device instead of MSC or not but really irritated by that protocol. Not sure if this (MTP) is native to Honeycomb or if Samsung wanted the external storage accessed in this way.
Click to expand...
Click to collapse
If you're still having trouble with apps not writing to the external sd, you might want to edit that .xml file thaloneus had mentioned.
Once I did that I had full access to write to that card from any app. Took me all of like five minutes to edit and test it out.
I'm having some trouble with this procedure. Like everyone else, I couldn't write to my external SD card using ES Explorer or what not, although the stock Samsung My Files explorer could (and strangely, if I use a Samba mount I could write to it from my Win7 PC).
Anyway I've rooted everything, and was about to edit platform.xml, but I can't save it. I don't have the ability to write to the system folder.
I think I've done the Mount rw thing, ES File Explorer's option to do it was disabled, but on File Expert it was available. For good measure, I also used the app "mount /system (rw /ro)" but even with all these tools, I still can't write to the system directory.
I'm at my wits end, any ideas?
Mochan said:
I'm having some trouble with this procedure. Like everyone else, I couldn't write to my external SD card using ES Explorer or what not, although the stock Samsung My Files explorer could (and strangely, if I use a Samba mount I could write to it from my Win7 PC).
Anyway I've rooted everything, and was about to edit platform.xml, but I can't save it. I don't have the ability to write to the system folder.
I think I've done the Mount rw thing, ES File Explorer's option to do it was disabled, but on File Expert it was available. For good measure, I also used the app "mount /system (rw /ro)" but even with all these tools, I still can't write to the system directory.
I'm at my wits end, any ideas?
Click to expand...
Click to collapse
What are you using to edit the .xml file? It may not have root explorer functions.
I used the Root Browser from ROM Toolbox to make and save the edit.
Worked for me with Root Explorer. I have tried most of the free file managers, and Root Explorer is worth every penny to me. It is the only app I have paid for.
StingerDog said:
What are you using to edit the .xml file? It may not have root explorer functions.
I used the Root Browser from ROM Toolbox to make and save the edit.
Click to expand...
Click to collapse
i used the free Astro File Manager to navigate to /system/etc/permissions/platform.xml. When I tapped on the platform.xml file I was given a choice of text editors to open it with. When I finished I was offered the option to save the file.
thaloneus said:
i used the free Astro File Manager to navigate to /system/etc/permissions/platform.xml. When I tapped on the platform.xml file I was given a choice of text editors to open it with. When I finished I was offered the option to save the file.
Click to expand...
Click to collapse
There you are thaloneus!
You made the one post that helped me fix that issue, then you disappeared. Glad to see you're back.
Thanks again!
I just has my USCC Galaxy S3 replaced under warranty. To save my internal SD files, I used an ADB pull /storage/sdcard0 in recovery. When I got the new phone rooted and CM10 installed, I booted to recovery and used an ADB push to restore the files. The files all ended back on the SD card, but now my apps cannot write to the folders on the SD card. The permissions are set to 644, and I cannot change them. I have tried with chmod and through file managers to change to 777, and although they claim success, the permissions stay 644. I'm unsure where to go from here, but I really would like to keep these files on my device. Any ideas on how to fix these permissions? Thanks!
Try copying/moving files around using the phone's file manager, & see if the changes stick. Also try "adb shell" -> "su", and change permissions that way, & see if it sticks.
Make sure you have an updated busybox.
Well, I tried moving them with file manager, su and updated busybox, changing permissions, and then I finally decided to go into recovery, pull, and format /sdcard. Once I did that, my apps were able to use the card again. I then was able to copy over the files via usb mount to windows. This seems to be working so far.
Thanks!
Hi.
When I was trying to add my 8GB SD card as internal memory of my rooted Galaxy Fit, I visited a weblog which guided me to replace the vold.fstab file exist in root/system/etc, with another modified one (with the same name) which was exist on that blog. So, I downloaded the modified vold.fstab and then I removed the original file using Root Explorer and replaced it with the downloaded one. But, after rebooting my device, the SD card could not be recognized nor as an external memory neither as an additional internal memory. I tested it on another device and all of its contents were available yet.
Therefore, what I need is just replacing the original vold.fstab file with that modified one. I tried to do it with Droid Explorer, Android Commander and ADB Browser. All of this programs display the contents of my internal memory on my PC via a USB connection, but unfortunately I have no permission to delete the modified vold.fstab from system/etc for replacing it with the original one.
Now, anybody can help me to have a root access to system files of my smart phone via my PC? Please help me ...
try using adb
you can use adb push command to copy the file from pc to your fit
Sent from my GT-S5670 using xda premium
I tried it, but it says that "You have no root permission to do this action"... Is there any solution please?
type adb shell
then type su
that should give you root permission
Sent from my GT-S5670 using xda premium
I did it. After typing "su" and pressing Enter, a message appears on my smartphone screen for about 2 seconds, which its contents is "Shell has been granted superuser permissions" and then disappears immediately. But still I have no root access to my internal memory and so, I'm unable to copy my original vold.fstab file in /system/etc/.
Although I found an application called Quick ADB Pusher, which it enabled me to install Root Explorer.apk directly trough my laptop on my device, and using Root Explorer I could remove the modified vold.fstab from the above path. Therefore, there is just one problem now; how to copy the original file in the path?
I'm having an issue with my internal storage. Sometimes I cannot modify files or folders using either a file manager (e.g. ES File Explorer or free version of Root Explorer) or when connected via USB to my computer. For a bit more backstory, please refer to my previous thread, which has received no replies and so I am asking for help here.
Basically, I would like to be able to move files and directories freely across my internal storage. Not much to ask for, really. However, some files and folders can't be moved (cut and paste) or simply copied (copy successful, paste fails). This first started when I was on PureNexus (6.0.0, 12/01/2015) with ElementalX 0.07 and rooted with SuperSU 2.62 (not systemless root). I've since returned to complete stock 6.0.1 (flashed factory image using fastboot), and now on systemless root (2.61) for a couple apps that I use.
Symptoms are:
1. could "copy" any file, but could not paste into any directory. ES File Explorer throws an error "/sdcard/directory/file_name: open failed: EACCES (Permission Denied)". Root explorer (free version) would say "Copy failed, file_name to /sdcard/directory"
2. when connected to a computer over USB, can copy files from computer to any directory on phone's internal storage, but cannot delete anything. When I try to delete a file or folder, I get the Windows error message that the destination has been disconnected, etc., even though it's not.
3. if I've copied a file from computer to phone (say music), some files cannot be copied to another location in internal storage, some files can.
Previously when I was on PureNexus with normal root,
If I am on my device and using ES File Explorer and if I am in the path /storage/emulated/0/* then I am unable to copy/move files and directories, as I've described above.
If I am on my device and using ES File Explorer and if I am in the path /sdcard/* then I am unable to copy/move files and directories, as I've described above.
If I am on my device and using ES File Explorer and if I am in the path /data/media/0/* then I am able to do anything I damn well please.
Now that I've reverted to stock 6.0.1 from factory image and with systemless root,
If I am on my device and using ES File Explorer and if I am in the path /storage/emulated/0/* then I am unable to copy/move files and directories, as I've described above.
If I am on my device and using ES File Explorer and if I am in the path /sdcard/* then I am unable to copy/move files and directories, as I've described above.
I do not see anything under /data
Having said all of this, none of my apps have any problems accessing internal storage, be it for data, cache, or writing anything to /Android/data (or obb)/*
Is this a hardware issue? I didn't think it would be, because it doesn't seem like the internal storage is faulty, since everything else runs perfectly fine.
Mod Edit
Hi,
You seem to have found the correct forum in which to post.
This is not a Q&A forum. It is more to guide new users to the best place on the site for their problem .
Please read the OPENING THREAD and the Second one , too.
Thank you for your attention in this matter.
malybru
Forum Moderator
I'm having an issue with my internal storage. Sometimes I cannot modify files or folders using either a file manager (e.g. ES File Explorer or free version of Root Explorer) or when connected via USB to my computer. For a bit more backstory, please refer to my previous thread, which has received no replies and so I am asking for help here.
Basically, I would like to be able to move files and directories freely across my internal storage. Not much to ask for, really. However, some files and folders can't be moved (cut and paste) or simply copied (copy successful, paste fails). This first started when I was on PureNexus (6.0.0, 12/01/2015) with ElementalX 0.07 and rooted with SuperSU 2.62 (not systemless root). I've since returned to complete stock 6.0.1 (flashed factory image using fastboot), and now on systemless root (2.61) for a couple apps that I use.
Symptoms are:
1. could "copy" any file, but could not paste into any directory. ES File Explorer throws an error "/sdcard/directory/file_name: open failed: EACCES (Permission Denied)". Root explorer (free version) would say "Copy failed, file_name to /sdcard/directory"
2. when connected to a computer over USB, can copy files from computer to any directory on phone's internal storage, but cannot delete anything. When I try to delete a file or folder, I get the Windows error message that the destination has been disconnected, etc., even though it's not.
3. if I've copied a file from computer to phone (say music), some files cannot be copied to another location in internal storage, some files can.
Previously when I was on PureNexus with normal root,
If I am on my device and using ES File Explorer and if I am in the path /storage/emulated/0/* then I am unable to copy/move files and directories, as I've described above.
If I am on my device and using ES File Explorer and if I am in the path /sdcard/* then I am unable to copy/move files and directories, as I've described above.
If I am on my device and using ES File Explorer and if I am in the path /data/media/0/* then I am able to do anything I damn well please.
Now that I've reverted to stock 6.0.1 from factory image and with systemless root,
If I am on my device and using ES File Explorer and if I am in the path /storage/emulated/0/* then I am unable to copy/move files and directories, as I've described above.
If I am on my device and using ES File Explorer and if I am in the path /sdcard/* then I am unable to copy/move files and directories, as I've described above.
I do not see anything under /data
Having said all of this, none of my apps have any problems accessing internal storage, be it for data, cache, or writing anything to /Android/data (or obb)/*
Is this a hardware issue? I didn't think it would be, because it doesn't seem like the internal storage is faulty, since everything else runs perfectly fine.
OK, an update to this.
After further investigation, I am finding that my issue perhaps has to do with permissions on files that have been cross copied. By "cross copied", I am referring to anything that I created by file manager or by computer, and attempted to modify using the other device. An example of cross copying would be if I created a folder called "Report PDFs" while connected to a computer via USB, and then tried to copy a bunch of PDFs into it using ES File Explorer. Inversely if I create a folder using ES File Explorer, I cannot modify it or files within it when connected to a computer via USB.
Using the File Manager in TWRP (2.8.7.2) I am able to modify all files at will, without any restrictions. It's only when I'm booted up into Android and accessing storage through a file manager app or via USB connection.
I can repeatedly reproduce this problem now. Any thoughts as to why I don't get access to files/folders due to cross copying?