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!
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?
Hello,
I am little confused about phones storage. Hope someone can help me.
OK, When I first configured my phone I installed TitaniumBackup and restored all my apps and data from my former phone HTC Sensation. Then I copied Sensations SD Card data to Nexus' internal storage via Windows. For example also the folder "WhatsApp".
When I connect the phone to my PC I can see its internal storage. In the folder "WhatsApp/Database" I can find some files like "msgstore-2014-01-17.1.db.crypt" or "msgstore-2014-01-16.1.db.crypt".
Now I open ES FileExplorer, go to device/sdcard: there I can see mainly the same folders I copied from Sensation to Nexus. WhatsApp is also there. When I look inside I can't find any files like "msgstore-2014-01-17.1.db.crypt" I see on "internal storage" via PC. but I see others like "msgstore-2014-01-24.1.db.crypt". What?! I don't understand that.
OK, next Test: Via PC I copy a file named 123test.txt to the Whatsapp Folder. Again I look via ES FileExplorer on the phone, what happens. Ola, I can see 123test.txt in device/sdcard. But not e.g. "msgstore-2014-01-17.1.db.crypt". Aha... strange.
And while writing this question I had to copy the filename of "msgstore-2014-01-17.1.db.crypt" from Windows explorer to paste it here. And now I can see also "msgstore-2014-01-17.1.db.crypt" in device/sdcard on my phone, but not the ohers like "msgstore-2014-01-16.1.db.crypt". I touch a file in Windows Explorer on "internal storage" and after that it's copied to device/sdcard?
This can't be normal?! That's zero transparent... and weird...
Can someone please clear it up for me?!
THANKS!
dbsoundz said:
Hello,
I am little confused about phones storage. Hope someone can help me.
OK, When I first configured my phone I installed TitaniumBackup and restored all my apps and data from my former phone HTC Sensation. Then I copied Sensations SD Card data to Nexus' internal storage via Windows. For example also the folder "WhatsApp".
When I connect the phone to my PC I can see its internal storage. In the folder "WhatsApp/Database" I can find some files like "msgstore-2014-01-17.1.db.crypt" or "msgstore-2014-01-16.1.db.crypt".
Now I open ES FileExplorer, go to device/sdcard: there I can see mainly the same folders I copied from Sensation to Nexus. WhatsApp is also there. When I look inside I can't find any files like "msgstore-2014-01-17.1.db.crypt" I see on "internal storage" via PC. but I see others like "msgstore-2014-01-24.1.db.crypt". What?! I don't understand that.
OK, next Test: Via PC I copy a file named 123test.txt to the Whatsapp Folder. Again I look via ES FileExplorer on the phone, what happens. Ola, I can see 123test.txt in device/sdcard. But not e.g. "msgstore-2014-01-17.1.db.crypt". Aha... strange.
And while writing this question I had to copy the filename of "msgstore-2014-01-17.1.db.crypt" from Windows explorer to paste it here. And now I can see also "msgstore-2014-01-17.1.db.crypt" in device/sdcard on my phone, but not the ohers like "msgstore-2014-01-16.1.db.crypt". I touch a file in Windows Explorer on "internal storage" and after that it's copied to device/sdcard?
This can't be normal?! That's zero transparent... and weird...
Can someone please clear it up for me?!
THANKS!
Click to expand...
Click to collapse
Maybe it's because I haven't finished my coffee yet, but I reread your post a few times and only sort of understand what you are trying to figure out...
Since the Nexus doesn't have external storage, then the Internal Storage you see in Windows is /sdcard. It sounds like maybe either the database files from your Sensation might not have transferred over to the Nexus correctly, or the older file maybe was rewritten with the version of the app on the Nexus? Or if it just doesn't show up when you copy the file to the phone while it is still plugged in, then it might not show up in a file manager on the phone until you unplug it and then the phone rescans the media to sync the contents so file managers can display everything. This is common behavior with the MTP set up. Let me know if I am not on the right path with the info and I'll see if I can help clarify more.
es0tericcha0s said:
Maybe it's because I haven't finished my coffee yet, but I reread your post a few times and only sort of understand what you are trying to figure out...
Since the Nexus doesn't have external storage, then the Internal Storage you see in Windows is /sdcard. It sounds like maybe either the database files from your Sensation might not have transferred over to the Nexus correctly, or the older file maybe was rewritten with the version of the app on the Nexus? Or if it just doesn't show up when you copy the file to the phone while it is still plugged in, then it might not show up in a file manager on the phone until you unplug it and then the phone rescans the media to sync the contents so file managers can display everything. This is common behavior with the MTP set up. Let me know if I am not on the right path with the info and I'll see if I can help clarify more.
Click to expand...
Click to collapse
Hello es0tericcha0s,
what I do not understand is: Why do I see on my PC other files then on my phone?
Why I looked at that: On phones with SD Card I backuped all my SD Card before ROM changes. Then I just copy my backup back to SD Card. But now I am not sure what to backup. If I backup my internal storage via PC I have definitily not the current data in it!
I don't understand that behaviour?!
dbsoundz said:
Hello es0tericcha0s,
what I do not understand is: Why do I see on my PC other files then on my phone?
Why I looked at that: On phones with SD Card I backuped all my SD Card before ROM changes. Then I just copy my backup back to SD Card. But now I am not sure what to backup. If I backup my internal storage via PC I have definitily not the current data in it!
I don't understand that behaviour?!
Click to expand...
Click to collapse
I'd have to go with good old buggy MTP. I've seen lots of these 'ghost files' in Windows explorer with my previous phone (GNEX). If both file manager apps and for instance adb shell do not show files that Windows explorer via MTP does show, you can safely assume Windows explorer is wrong.
Tip: for a more secure data transfer, copy your /sdcard content from your PC to the N5 using the adb push command. I believe there are even GUIs for adb nowadays if you don't like working on the command line.
Guys... I still do not understand that thing...
I installed CM11. Copied via Windows Explorer my Titanium Backup folder to internal storage. Nothing else. Then I restored WhatsApp to see what happens. Everything worked fine. Whatsapp is OK but has no media file I sent or received. OK, I can copy them from my backup to internal memory. BUT I CAN'T SEE ANY WHATSAPP FOLDER in my Windows Explorer. But in my phone file explorer I can see it!
This can't be normal!
How does one can make a consistent backup of it's phone with that behaviour?!
EDIT: After I rebooted the phone I can also see the WhatsApp folder in Windows... :/
Like I said: MTP is buggy. For reliable file transfers via usb use adb push and pull commands.
Sent from my Nexus 5 using Tapatalk
This is sooo strange...
I made a TWRP backup. Then I used adb pull /sdcard/ /sdcardbackup to copy my storage with my TWRP backup to PC. But I can't find the backup on my PC after adb finished the copy job. Where is it? I searched with the explorer on the phone:
/sdcard/ -> I am redirected to /storage/emulated/legacy - this view is identical with my backup on pc
/storage/sdcard0/ -> I am redirected to /storage/emulated/legacy - same as above
/storage/emulated/ -> There are folders 0, legacy and TWRP and there I found my backup.
Shouldn't I find TWRP backups on my sdcard, storage, emultade, legacy or I don't know how the place is called?!
OK, I try to copy thios TWRP backup to my PC:
- via PC: I can't, because I see only the "internal storage"
via adb: I can't, too: E:\Nexus 5\android-sdk-windows\platform-tools>adb pull /storage/emulated/TWRP /TWRPbackup DOES NOT WORK
BUUHUUUUUUUUUU unbelievable
How do you check where your data is? I don't...
You used a relative path for the destination folder, meaning that folder was created on the location where your adb executable is. Look for it there or use an absolute path for your destination folder.
Sent from my Nexus 5 using Tapatalk
You're supposed to adb pull from /sdcard not /storage
If you didn't change directory (cd) in cmd / terminal, then your pulled data is in the directory that opens by default in cmd. Open cmd to see what path you let it default to. Often c:\users\username
Don't forget if you're in windows, you need to
adb pull /sdcard/source \destination
And linux
adb pull /sdcard/source /destination
Sent from my Nexus 5 using Tapatalk
dbsoundz said:
This is sooo strange...
via adb: I can't, too: E:\Nexus 5\android-sdk-windows\platform-tools>adb pull /storage/emulated/TWRP /TWRPbackup DOES NOT WORK
.
Click to expand...
Click to collapse
Hello,
copy command should be ok. hoever. Why is TWRP backup saved to location /storage/emulated/TWRP, not on "internal memory"?
Really guys... this can't be normal. is there something wrong with my phone or ROM?!
dbsoundz said:
Hello,
copy command should be ok. hoever. Why is TWRP backup saved to location /storage/emulated/TWRP, not on "internal memory"?
Really guys... this can't be normal. is there something wrong with my phone or ROM?!
Click to expand...
Click to collapse
No, it's something wrong with you. I'd be easier to copy the backup to the phone memory visible to a PC using a root explorer and then copy it to the PC that way if you can't get adb working
As I understand, lollipop should bring back the write access to SD card for third party apps.
However, the app "Ftp server" still cannot write to the SD card.
I cannot root the device due to company restrictions.
Any ideas or suggestions?
Bump!
Yeah, no root no acces.
TheTeslaCoil said:
Yeah, no root no acces.
Click to expand...
Click to collapse
I got this reply from the developer of FTP server pro:
"Basically I would need to use a new set of functions created by google (which are not standard); but I can not do that as I am using a standard implementation of ftp protocol."
So apparently there is a non standard implementation available?
waxxan said:
I got this reply from the developer of FTP server pro:
"Basically I would need to use a new set of functions created by google (which are not standard); but I can not do that as I am using a standard implementation of ftp protocol."
So apparently there is a non standard implementation available?
Click to expand...
Click to collapse
This is exactly mine problem too. I have upgraded to Lollipop in hope to be able to write via FTP Server app to SD card again but it still doesn't work.
Is there another FTP app which can do it?
Also isn't there any other file browser app which can write to SD card (like pre-installed File Commander) ?
Yea, the preinstalled file commander can write to sd. It even have a ftp client.
But I want the other way around.
Have tried a few of the free most popular fpt server apps, but same problem on them all.
Probably/maybe if you make it a system app it'll work. (use Titanium backup for that)
Nvm that's only applicable if you have root, sorry i forgot you can't root...
For those who are interested. FTP server pro has now been updated, and support full access to SD card.
https://play.google.com/store/apps/details?id=com.theolivetree.ftpserverpro&hl=en
No dice, FTP server pro only writes to it's proprietary folder, not to SD card in general.
It is working on my Z3 at least. You might have to choose custom folder, then point the custom folder to the SDcard. That is how i have it configured.
That does the trick ! Thanks !!
Custom Folder
LG G4 - I set up the custom folder to be home but I'm still seeing the root (/). If I try to delete or transfer files -- no dice.
Non-rooted phone.
I'm on non-rooted too. Directly after selecting the sdcard as custom folder, I had the option to grant write access as described here:
https://metactrl.com/docs/sdcard-on-lollipop/
Wobstar said:
I'm on non-rooted too. Directly after selecting the sdcard as custom folder, I had the option to grant write access as described here:
...
Click to expand...
Click to collapse
I didn't receive anything about write access or otherwise after the the window opened to let me select the SD Card.
You have set home folder to custom? And then opened the activated browser just below the home folder option? And select external SD card in that option?
If yes and it didn't work, I would suggest reinstalling the app...
Wobstar said:
You have set home folder to custom? And then opened the activated browser just below the home folder option? And select external SD card in that option?
If yes and it didn't work, I would suggest reinstalling the app...
Click to expand...
Click to collapse
Well it helps to follow ALL the instructions... this is important:
"Don't navigate down into any subfolder. You must select the top-level root folder of the SD card. This is important."
This FTP-Server worked for me:
https://play.google.com/store/apps/details?id=com.theolivetree.ftpserver
In the settings you can select your root directory, don't select "ext. SDCard" it will only let you write in the apps own folder on the SDCard. Select personalized home directory than android asks you were your root directory should be, select your SDCard and confirm it, this should do the trick.
(Tested on LG G4 - Android 6.0)
Hope it works for everyone ;D .
CyanogenMod 13 + ROOT
Yes, writing to external card seems to work this way.
But deleting from the external card does not work. When trying to delete a file i get the error:
error 450: no permission to delete
Why?
I use FAT32 storage on my USB OTG storage. On lollipop i was able to delete or copy files to the storage but since I've updated to Marshmallow recently, i only have read access.
Any idea how to get around this?
I've tried the stock file manager as well as File Manager app.
I had same problem with mine when I used my mac to format usb, partition map was GUID instead of master boot once i changed that worked ok. Not sure if that's any help to you though.
neopeo said:
I use FAT32 storage on my USB OTG storage. On lollipop i was able to delete or copy files to the storage but since I've updated to Marshmallow recently, i only have read access.
Any idea how to get around this?
I've tried the stock file manager as well as File Manager app.
Click to expand...
Click to collapse
Have you ever turned off USB debugging?
dan7four said:
I had same problem with mine when I used my mac to format usb, partition map was GUID instead of master boot once i changed that worked ok. Not sure if that's any help to you though.
Click to expand...
Click to collapse
I have no idea what GUID or master boot is. But i did format it on Windows using 'guiformat'. Something I found on the web and have used previously many times.
bininga59 said:
Have you ever turned off USB debugging?
Click to expand...
Click to collapse
I just tried that and it didn't make a difference.
Same here, having problems with OTG after updating my S6 to marshmallow, should have read this forum before updating... bummer...
neopeo said:
I use FAT32 storage on my USB OTG storage. On lollipop i was able to delete or copy files to the storage but since I've updated to Marshmallow recently, i only have read access.
Any idea how to get around this?
I've tried the stock file manager as well as File Manager app.
Click to expand...
Click to collapse
I think I found the solution, I noticed that my S6 running marshmallow, when I plug my otg to the phone, I accidentally made the ES File Explorer the default, I can't access the OTG via Samsung's default File Manager. So I went to Applications, go to ES File Explorer, clear defaults... plug my OTG Again, this time don't choose ES File Explorer, if it pops out, cancel it. Then the Samsung's File Manager will now recognize the OTG, and boom, I can now use my OTG properly via Samsung's File Manager... Try it out...
It appears i HADN'T tried the file manager app (i thought i did). That app DOES allow deleting. It's just the stock samsung file explorer that doesn't allow write/delete access.
Problem solved.
Well. It looks like file manager intermittently has write access. Very odd.
It's stopped now. So i guess i did previously try it.
Very frustrating.