Jan 05, 2018 open settings, and then open all app. In this list find the app named 'Documents' click on that app and click on 'enable'. Return to Fx explorer app. Continue the process. Open the memory card.
![Write Write](/uploads/1/2/5/6/125629084/667391205.png)
After some searching, I wasn't able to find anyone who described quite exactly my problem, and no one had a solution. So, after days of fighting this, I finally fixed it, and decided to post my solution.HTC Droid Incredible running OEM 2.2 on VerizonProblem:My Internal Phone Storage was getting mounted as 'read-only' and I couldn't write to it.Symptoms:. Whenever I booted the phone it would say 'There's a problem with your SD card' in the notification bar.
However, going to settings SD & phone storage - it revealed that my SD card was fine, and my internal storage was 'read-only'. Astro File Manager Clearly showed my emmc folder as unwritable (and nothing happened when I tried to write to the folder). My photo gallery would only show photos taken since the problem began. This symptom was the same as in this post (with no solution):Back story:I had my phone connected via USB as a Mass Storage Device to a windows machine and was transferring a folder called 'BensPictures' that contained approximately 400 megs of photos to the root of the Internal Storage. About 50% of the way through, windows made the device disconnect sound, and alerted me that the USB storage device was no longer available, and that data had been lost in the transfer.
I've seen the error before, but never when actually transferring anything. I just popped in a USB thumb drive (wish I did this first.) and used that to complete my file transfer.A few hours later I realized that my phone was doing some odd things, such as the gallery problem described above.
And then I started getting these messages about something being wrong with my SD card in my notification bar.After a few hours of poking around, I discovered that my Internal Memory was now 'read-only' and there was what astro was calling a file called 'BensPictures' in the emmc folder. This 'file' had no permissions, and tapping and holding on it did nothing.Solution:I fired up my TerminalEmulator (my phone was NOT rooted at this point) and began to poke around.
Trying to remove anything from the emmc folder gave me a 'filesystem read-only' error, but trying to remove this 'BensPictures' file gave me error: 'Unable to remove file: I/O error'I started playing around with the mount command, and quickly learned that I couldn't do anything without rooting my phone.The only thing useful I was able to do at this point was list out the existing mounts by running 'mount' in my terminal.Doing this, I saw that one of the mounts was this. Umount /mnt/emmcAnd then re-mounting using a similar command like above (minus the 'remount' option). The device did remount, and was accessible, but it was still read-only.I tried mounting the device to a different location, and it was still read-only.I tried a lot more things here. Honestly, I don't remember a lot of them.
But I tried everything I could think of.Finally, I started thinking about fsck. I discovered that Android has a fsckmsdos command, and since the internal memory on the Droid Incredible is vfat, this was perfect.I mounted the internal storage (still in read-only mode) and copied everything to my SD card as a backup, and then ran. I love you!Thank you for posting these detailed instructions.
My Droid Incredible's internal storage recently became read-only too. After trying several things I found these instructions.
![Storage Storage](/uploads/1/2/5/6/125629084/305008371.png)
I recently experienced the same problem with my Samsung Galaxy S2 GT-I9100 where the internal phone memory suddenly became read-only while the SD card was still OK.Before stumbling over this thread (after scouring the web to no avail for possible causes and solutions) I tried many things (short of a factory reset) including trying to format the internal storage (which silently failed because it was still read-only)!After reading the posts above I found the culprit responsible for the read-only mount. The 'Android' folder had some garbage file names in it. My phone wasn't rooted and I can't believe there wasn't any built-in function for checking the integrity of the file system.
I guess they thought it could never become corrupted. Truth is I still don't know what corrupted those garbage files, it must have been some messed app update from the Google Play market.So the only solution was to root my phone and since I'm no expert at that I searched for the easiest way to do it. Luckily I found the Framaroot app which does just that, root your phone in one click by using an exploit tailored for your particular phone:The 'Aragorn' exploit worked nicely for my S2 GT-I9100 (Android version 4.1.2). The next steps were a walk in the park:I installed SuperSU and Terminal Emulator from the Google Play market, fired up Terminal Emulator, executed 'mount' to find the name of my internal storage, then executed 'su' to make myself root and finally used fsckmsdos as described above to fix my corrupted folder (truncated it and deleted the garbage entries).After rebooting the phone, my internal storage was once again mounted as read-write and everything was back to normal.
Thank you for posting this thread and I hope this solution will help someone else too with their corrupted read-only file system. Hello, sorry for the bumpage on this, but I've had 2 days of my tablet playing up and I'm sure it's coz the internal memory is read only. The problem is, I'm getting the 'Unfortunately, the process.has stopped working' pretty much every second! And it's everything, from gapps, to Ebay, to Calendar, to Play Store. Making it impossible to type anything in the emulator, which I can get up, but not type anything into, since as soon as I press OK, another pop up comes up (thank you to whoever designed that piece of brilliance!!! ( )I've tried a full format, cache/dalvik wipe and tried to install a new ROM, but it won't write, so no go.Any suggestions?
Hi,I have rooted my Micrimax A120 and I couldn't remember what I did. But problems started to arise in my phone gallery was not working properly,the gmail account sync was experiencing problems and I thought of formatting so I downloaded a recovery.IMG and flashed it using mobile uncle tools and it flashed and I started to factory reset my phone but it failed. I couldn't factory reset my phone the recovery said that: unable to mount on folder emmc (or) unable to Mount in cache. I installed terminal emulator and tried everything you said but none could change the read only mode of my internal SD card.I couldn't flash a new rom without wiping data.Any suggestions? The problem with giving advice for devices that you're not sure about comes down to their background.While I appreciate your advice in general, please consider adding next time a disclaimer that restorecon only applies to Android with SELinux - which I believe was Android 4.3 but you can check me on that, thanks.That was all permissive mode back then fwiw I didn't see restorecon use come along until later.Btw - our Mini-SDK advice is better than a full platform-tools download for rooters and covers the 3 major operating systems.
Yep, fsckmsdos did the trick. I am using rooted galaxy note 1. I can't using camera or load picture from LINE. I installing Terminal Emulator then on terminal emulator i type su. Then type mount and i can see which path that broken.
In my case, i have several path which broken. /dev/block/dm-1, /dev/block/dm-13 etc. It's easy to find it. Then i am using fsckmsdos /dev/block/dm-1 and the emulator asked me 2 question and i type.
Do it for all broken path and reboot my phone. Now it's work again thanks. Having trouble. I followed the OP and completed a root and ran the mounting and fsckmsdos commands.