Cannot Read Data on My Thumb Drive

Thread Starter
Later on 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 information technology, and decided to post my solution.
HTC Droid Incredible running OEM 2.two on Verizon

Problem:
My Internal Phone Storage was getting mounted as "read-but" and I couldn't write to it.

Symptoms:

Whenever I booted the telephone it would say "There's a trouble with your SD card" in the notification bar. Yet, going to settings > SD & telephone 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 photograph gallery would only testify photos taken since the problem began. This symptom was the same as in this post (with no solution): http://androidforums.com/incredible...telephone-storage-read-only-afterward-2-2-update.html

Dorsum 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 independent approximately 400 megs of photos to the root of the Internal Storage. About fifty% of the way through, windows fabricated the device disconnect sound, and alerted me that the USB storage device was no longer available, and that information had been lost in the transfer. I've seen the error earlier, but never when actually transferring anything. I just popped in a USB pollex drive (wish I did this get-go...) and used that to complete my file transfer.
A few hours after I realized that my phone was doing some odd things, such every bit the gallery problem described in a higher place. Then I started getting these messages almost something being incorrect 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 signal) and began to poke around. Trying to remove anything from the emmc binder gave me a "filesystem read-simply" error, only trying to remove this "BensPictures" file gave me error: "Unable to remove file: I/O error"

I started playing around with the mountain command, and quickly learned that I couldn't practise annihilation without rooting my telephone.

The only affair useful I was able to do at this point was list out the existing mounts by running "mount" in my last.

Doing this, I saw that one of the mounts was this:

/dev/block/vold/179:3 /mnt/emmc vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

I knew that was the internal memory. The important role there is Since I couldn't practise everything I needed to (like change the mounts), I rooted my telephone.
Everything that took place from this signal on was with my phone rooted.

The adjacent thing I did was install SSHDroid and so I could run commands from my reckoner over SSH.

In one case I had SSH working, the beginning affair I tried was to remount the internal memory with read/write enabled using this command:

mount -o remount,rw,errors=go on -t vfat /dev/block/vold/179:iii /mnt/emmc

The command appeared to work, simply the mount was still read-only. I tried unmounting using:
And so re-mounting using a similar command like to a higher place (minus the "remount" option). The device did remount, and was accessible, but it was yet read-merely.
I tried mounting the device to a dissimilar 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 fsck_msdos command, and since the internal retentivity on the Droid Incredible is vfat, this was perfect.

I mounted the internal storage (still in read-merely style) and copied everything to my SD card as a fill-in, and then ran:

fsck_msdos /dev/block/vold/179:3

I got this output:

** Phase one - Read and Compare FATs

Attempting to classify 845 KB for FAT

Attempting to classify 845 KB for Fatty

** Phase 2 - Cheque Cluster Chains

** Phase 3 - Checking Directories

/BensPhotos starts with free cluster

Information technology found my broken directory! I said 'y'es and it continued to tell me about several Lost Cluster Chains, and finally finished with a

***** FILE Organization WAS MODIFIED *****

I thought to myself, "This bad directory couldn't crusade all those issues...could it?" and I and so rebooted my telephone, and the Internal Phone Storage was back to it's proficient-ol' self. Readable and Writable
I'grand a couple reboots later (although just a couple hours) and it appears to be working however!

I sincerely promise that if someone else is having an issue like this, this helps them at least get on the right rail!

Download the Forums for Android™ app!

Download

I love you!
Cheers for posting these detailed instructions. My Droid Incredible's internal storage recently became read-only also. Later trying several things I constitute these instructions. They worked perfectly.

I had never rooted a phone before and was a little intimidated, but the 'unrevoked' tool made information technology simple.

The but things I did differently from your instructions (after rooting the telephone) were:

Instead of downloading SSHDroid I ran the fsck_msdos command from Terminal Emulator.

Later rooting the phone and running Final Emulator, I typed "su" to run in SuperUser mode before running fsck_msdos.

fsck_msdos was asking me to verify a TON of changes so I hit ^C (hold down the scroll button and hit C) to terminate it, then I ran fsck_msdos with the -y pick to automatically reply "yes" to every question:

fsck_msdos -y /dev/block/vold/179:3
Another borked Incredible due west/ "read-simply" emmc, "SD Carte du jour problem" and thousands of missing photos fixed with fsck & terminal emulator... thank you, OP!
I recently experienced the aforementioned problem with my Samsung Galaxy S2 GT-I9100 where the internal phone memory suddenly became read-only while the SD card was even so OK.
Before stumbling over this thread (after scouring the web to no avail for possible causes and solutions) I tried many things (curt of a factory reset) including trying to format the internal storage (which silently failed considering information technology was nonetheless read-only)!

After reading the posts to a higher place I found the culprit responsible for the read-only mountain. The "Android" folder had some garbage file names in it. My phone wasn't rooted and I can't believe there wasn't whatever built-in function for checking the integrity of the file system. I guess they idea information technology 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 marketplace...

And so the only solution was to root my phone and since I'one thousand no skilful at that I searched for the easiest style to do it. Luckily I establish the Framaroot app which does only that, root your phone in one click by using an exploit tailored for your detail phone:

http://forum.xda-developers.com/showthread.php?t=2130276

The "Aragorn" exploit worked nicely for my S2 GT-I9100 (Android version 4.1.two). The side by side steps were a walk in the park:

I installed SuperSU and Terminal Emulator from the Google Play market place, fired upwards Terminal Emulator, executed "mount" to notice the name of my internal storage, then executed "su" to make myself root and finally used fsck_msdos as described above to fix my corrupted folder (truncated it and deleted the garbage entries).

After rebooting the phone, my internal storage was one time again mounted as read-write and everything was dorsum to normal. Thank you for posting this thread and I hope this solution will assist someone else too with their corrupted read-only file system.

-- My YouTube Aqueduct
Htc incredible su binary v3.0.three.2
I take bt5 arm boot folder in my internal storage because i practise not have a sd large plenty to store information technology. well when always i try to admission information technology with terminal i become denied. it seems like you guys are going in the management that i need to get permissions to access the os. I really desire this to work whatever help would be appreciated.
it is supposed to install the SSH if memory is read-only?
I can not do annihilation, not install or uninstall. how else can modify the internal retentivity to brand it as read-write?
Hello, sorry for the bumpage on this, but I've had 2 days of my tablet playing upwardly and I'm sure it'due south 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'south everything, from gapps, to Ebay, to Calendar, to Play Store. Making it impossible to type annihilation in the emulator, which I can go up, but non type annihilation into, since as before long as I press OK, some other pop up comes up (thanks to whoever designed that piece of brilliance!!! >( )
I've tried a full format, cache/dalvik wipe and tried to install a new ROM, merely it won't write, so no go.

Any suggestions?
Howdy,
I have rooted my Micrimax A120 and I couldn't think what I did. simply bug started to ascend in my phone gallery was not working properly,the gmail account sync was experiencing problems and I idea 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 telephone simply it failed. I couldn't mill reset my telephone the recovery said that: unable to mount on binder 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 carte.
I couldn't flash a new rom without wiping data....
Whatever suggestions?
Howdy, I had the same trouble (not the same device).
I've tried endless solutions proposed on xda, and similar sites: setting permissions, ownership group change, remounting the storage in rw mode, etc, every solution failed, merely non this one:

0.Your phone needs to be rooted.
one.Connect your phone to the PC (usb debugging enabled, etc)
2.Open up a final(Mac/Linux) or cmd.exe (Windows).
Mac/Linux - you'll need the adb executable (I don't really know how to set up on Mac), and on Linux it depends on your distribution (on Arch information technology can exist found in the AUR)

Windows - download android platform-tools (which contains adb.exe, fastboot.exe, etc)

iii. In one case in the final blazon

#Make sure that your device is attainable through adb
#SSH-like service for your Android phone
#Use information technology as root (at this point your phone will probably enquire you to give
super-user permissions to adb shell, confirm information technology)
Finally, this is where the magic happens
#I highly recommend the homo page of restorecon

restorecon -five -R /data/media
The problem with giving advice for devices that you're not sure about comes downwardly to their background.
While I appreciate your advice in general, please consider adding next time a disclaimer that restorecon just applies to Android with SELinux - which I believe was Android iv.three simply you lot tin check me on that, cheers.

That was all permissive fashion back then fwiw I didn't run across restorecon apply come along until later.

Btw - our Mini-SDK communication is better than a full platform-tools download for rooters and covers the 3 major operating systems -

http://androidforums.com/threads/adb-guide-updated-2014-xi-xi.443072/#post-5389081
How-do-you-do,
My device in not rooted . What can I exercise?
(This kind of problem its a very hard challenge !!)
I will thanks a lot any suggestions.

Luciano.
Having trouble. I followed the OP and completed a root and ran the mounting and fsck_msdos commands. (still read-just)
after the restart its as if nothing ever happened and has returned back to read-only.
Can y'all help me if I need to run extra commands or am I a special case?
- galaxy s2
****output from mount command run through SSH ****
root@android:/ # mountain
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,style=755,gid=m 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/cake/mmcblk0p9 /arrangement ext4 ro,noatime,barrier=i,data=ordered 0 0
/dev/block/mmcblk0p7 /enshroud ext4 rw,nosuid,nodev,noatime,bulwark=ane,journal_async_commit,information=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p12 /preload ext4 ro,nosuid,nodev,noatime,bulwark=one,data=ordered 0 0
/dev/cake/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p4 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/cake/vold/259:three /storage/sdcard0 vfat ro,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-one,shortname=mixed,utf8,errors=remount-ro,discard 0 0
I have the same problem. Former the internal storage become read-simply later on i rebooted my device and randomly wipe internal storage itself. I don't copy files. I just play games. is there a fashion to foreclose this in the future?