as seen above in the desire forum, im having this issue. it just occurred today.
i have a 16GB Sandisk, stock and unrooted. i move about 4 apps to SD card (out of the 30 ish apps i have, only 4 were available to be moved to SD).
post here if you have seen this and:
if your rooted
how many apps on SD card if any
size of card and if this happened pre or post froyo.
if you installed the leaked version of froyo and/or deleted it.
seems all of us having this issue posted today or within a day or so.. so it seems like it may be Froyo related... maybe installing certain apps to card and /or having auto updates checked maybe the cause.... *shrugs*
Well, I started having this problem today, after the Froyo update and the first time since the update that I moved something to the phone from the laptop with the USB cable.
I took the 16G SanDisk card out of my EVO, put it in an adapter and plugged it into my WindowsXP laptop, backed up everything on the card then reformatted the card while still plugged in. Moved 90% of the backup back onto the card, put it in my EVO and voila! Works fine. I did notice though that I had less than a G left on the card when all of this started. I don't know, but I'm wondering if the amount of free space affects this.
I'm too much of an Android novice to help with suggestions, but that's what worked for me.
The Following User Says Thank You to Tigrisan For This Useful Post:
i realized the other day that i have about 3.5 gb left. i didnt know i had such little space left. maybe you are right in that the low memory may trigger something..
i plan to do what you did right now. i too just noticed this error just today... odd isnt it? :-)
I wish there was more info from others having this problem as far as how much room they have left on their card and just what they did when it happened.
Like I said, when I transferred everything back on using the adapter and the laptop, I didn't have any trouble though admittedly, I left off one of the movies so I'd have a bit more room. But over the next week, I'll play with it a bit more and see what happens, what it takes to recreate it.
I do think it's got something to do with Froyo though. Then again, I could be wrong. I often am *sigh*
The Following User Says Thank You to Tigrisan For This Useful Post:
I dont know if this helps but my desire was having a similar problem the other night. it was coming up with read only errors and couldnt do anything that wrote to the sd card. i tried restarting the phone, unmounting and remounting the card andd even taking it out as well as battery with no joy. i hooked it up to my mates ubuntu pc to see if i could change permissions but no go.
I was all set to do a format, i plugged the phone into my windows 7 pc as a disk drive to backup the data.... windows rather than connecting normally said that it needed to scan the volume for potential errors so I clicked "ok" and windows fixed whatever the problem was and its been perfect since !!
The Following 3 Users Say Thank You to bigr1979 For This Useful Post:
If someone's out in left field, the !Report button is to the left of their post.
If someone gives you right-on advice or positively contributes, the Thanks button is to the right.
Remember - it's our forum and we're all in this together - so let's keep it cool.
what i ended up doing was just backing up data on the ltop, format the card in the ltop, put it back in the evo, format, then i loaded apps up from ltop to phone in mass storage mode. i was getting CRC errors by doing that on some folders, so i took the card out put it in the ltop and continued to add apps that way.
this was last night and this AM no SD errors thus far.
i DID the froyo fix that EarlyMon started and i have not yet put apps on SD card that are compatible with moving to sd card so i plan to do that at some point today and monitor.
The Following User Says Thank You to marctronixx For This Useful Post:
Ran into this problem just now. Will try reformatting later tonight. Basically never had this problem before but it started showing up after I filled my 8gb card up until I had 500gb left. The last three files are large and its only when I try to open them tbat I get this error otherwise everything else is working fine. I think maybe it has something to do with how much of the card space is used?
I think that's got to be it. When you hit a certain level on the SD card, it starts giving that message. I left more room on mine this time, like I said, and haven't had a problem with it since. I've been working all week though and haven't had a chance to test the theory.
Seems like those who put enough info in as to what's going on when it happens have all said the same thing, they have little to no room left on the card when it happens.
The Following User Says Thank You to Tigrisan For This Useful Post:
Just a heads up, there was some considerable debate in June about which way to format the SD card.
One guy strongly and vehemently and in no uncertain terms insisted that the phone's format be used as it created the expected hierarchy for the card - and that for larger cards, it was the only way to go.
I'm not expert in SD cards by any stretch of the imagination - so I'm just tossing that out, as said, as a heads-up.
The Following User Says Thank You to EarlyMon For This Useful Post:
yes im an old school windows guy and i always did the format in the handset. its an easy thing to do re: format in the device.. if that makes mr. Evo happy, then who am i to interfere?
The Following 2 Users Say Thank You to marctronixx For This Useful Post:
Hmmm...I guess I never thought about it. I just did mine with the card adapter in the laptop and so far, I haven't had any problems at all. Doesn't mean I won't. Just that I haven't.
Hmmm...I guess I never thought about it. I just did mine with the card adapter in the laptop and so far, I haven't had any problems at all. Doesn't mean I won't. Just that I haven't.
I didn't have any trouble that way either, but after hearing that dogs would sleep with cats and rain would rise from the ground to sky, I decided to play it safe and go with the handset format.
I've also read that Windows formatting can degrade lifetime, per this:
so like clockwork yesterday (saturday 14 august 2010) around 1'ish i saw this card error again. this time when i would click on the SD card error in the notifications tab so it would try and resolve the issue, it would immediately spit the error back.
the difference between this and the behavior i saw a week ago to the day was that once i clicked on that notification, it would seem to work for a bit before the error popped up.. now it just stayed there..
i could not access any videos or photos but could look into the folders and saw the folders.. just obviously could not do any editing since it was in read only...
i took the card out of the handset, copied it to the ltop, formatted in the ltop and copied BACK over the contents. i didnt format it in the evo, just kept it in the ltop.
have not seen the error thus far and i have 10gb's left on the Sd card (16 gb sandisk)
The Following User Says Thank You to marctronixx For This Useful Post:
Keep us posted - this one is just bugging me to no end.
The PC Synchronization service obviously needs to running unabated in order for the SD card to be recognized by a d/ltop. If you think to, if the problem recurs, kindly check and make sure that's running. I've not seen your problem associated with that observable, but my thinking is if you're doing nothing to PC Sync and one failure associates with the other, maybe we can light a few Camels and see if we can find a cause.
Do you use aLogcat? You can pause it and mail yourself system logs - could be helpful (I think you do, I think we've posted on that together before, but I often suffer from CFR so I thought it best to ask).
The Following User Says Thank You to EarlyMon For This Useful Post:
yeah i used/use aLogcat especially on my pro2 but a time or two on the evo...
interesting bugger indeed. it could be the card is starting to show signs of failure like the hard drive "click" when the heads hit the stop.. but i digress...
I've been having the same issues. I just reformatted my 16gb card via the phone and am about to copy some of my pictures and music back to the card. Hopefully all goes well and this problem will not happen again.
The Following User Says Thank You to Connectz For This Useful Post:
lets hope bro.. i mean all was well during the week but then on Saturday at almost around the same time this happened again.. that was weird.. this time i jsut formatted in the ltop and not the phone to see if that would make a difference...
I have a16gb sandisk....i was setting here trying to stream a vid that wouldn't so I restated the phone. WHEN everything loaded it tries to prepare sim card and then says sd card is mounted as read only. Anybody know how to fix this?
its not your sim card rather its your SD card is preparing.
smoke this thread over. i had it happen to me two separate times. both times required a reformat. the first time i reformatted in the handset, this second time i formatted it in the computer (im running old school XP) and over a week its been solid.
Yea sim card was a typo...so how do I copy sd card to laptop? Just hook phone up via usb and copy folder over or do I need top back it up a certain way
yeah there are steps earlier in this thread on what others did..
but yeah put the sd card into your computer, copy the files.. format the card, copy the files back over.. put card in the handset.. you are good to go...
most computers have SD slots. if you do not have such a slot nor have any access to a machine that does, then you would have to connect your handset to the machine. this is slow over USB . also if the cable becomes detached from the handset or the machine you lose your sync..
more variables come into play when you do it this way but yes you can connect via usb.
is your card nearly full? how much storage space do you have left on it?
If your laptop doesn't an SD card reader built-in, you buy a usb dongle for that - google "usb sd card reader" to get an idea of how they look and how inexpensive they are. Personally, I don't think they're a bad investment, but ymmv.
Assuming your phone's problems don't extend to disallowing you to connect via usb (it _should_ work), general procedure is here: wont update
The Following User Says Thank You to EarlyMon For This Useful Post:
thanks for the help...what a headache.First a little back story...on my laptop i was not able to root because i couldn't install new .net frameworks to open simple root and couldn't get my laptop to recognize my phone on top of it.When i rooted my phone i did it on a another person's laptop which i won't see until next week maybe later...
now i tried installing htc sync,sdk component,and then booted into a recovery and updated adb with drivers from sdk....still a no go.I plug my phone in through usb,set it to disk drive,go to my computer,click on removable f drive and it still says "insert disk"
this is driving me nuts...something so easy yet running into walls.Also i have an sd card slot on my laptop but it's huge and and would swallow my micro sd card the evo takes
you need a microsd adapter. they can be had at wally world, staples,officedepot, target, etc.. they cost pennies... they are handy things to have...
yes you dont have to go thru all of that.. lol.. just go grab an adapter and use your ltop to do the work.. make a copy onto the hard drive, format, reinstall our backup and put back in the handset..
I was all set to do a format, i plugged the phone into my windows 7 pc as a disk drive to backup the data.... windows rather than connecting normally said that it needed to scan the volume for potential errors so I clicked "ok" and windows fixed whatever the problem was and its been perfect since !!
This worked for me on my desire too. I had been copying files to the phone and unmounted the sdcard from the computer ungracefully (which is a bad habbit which I do far far to often... but it usually doesn't create any hiccups). Usually I just click past that popup which says that it was unmounted ungracefully and "do you want to perform a scan for errors" but after reading your post I did the scan and it worked perfectly afterwards.
I booted into recovery (rooted phone, I couldn't be stuffed taking the sd card out and finding a card reader) and mounted the sd card to the pc from recovery console.
Prior to all of this I had a day old nandroid backup and noticed that after a wipe and fresh rom reinstall it was fine, but after putting my nandroid backup back on it was unhappy again so was hoping someone would be able to save me a bunch of stuffing around... So on that note thanks for the tip dude, saved me a wipe, rom install and a few hours worth of reconfiguring and setting up.
Last edited by mistahd33; August 27th, 2010 at 11:15 AM.
I've had my first experience of this tried as suggested. I reaformated my sd card while connected to my phone, transferred the documents back over. ejected and still the same problem occurs
do what i did the second time this happend to me..
format the card IN THE COMPUTER (i have a PC running old school winxp) and X-fer files back to card while its still in the computer. you may need a SD card reader or adapter.. i did this and have not see the problem since. the original time i did it in whilst the card was in the phone and a week later the error appeared...
do what i did the second time this happend to me..
format the card IN THE COMPUTER (i have a PC running old school winxp) and X-fer files back to card while its still in the computer. you may need a SD card reader or adapter.. i did this and have not see the problem since. the original time i did it in whilst the card was in the phone and a week later the error appeared...
im stock, non rooted froyo'ed....
Thanks, The ltop won't even recognise the sd card while in the phone now so will have to pop out and get a reader or adaptor.
I had this problem and reformatted everything, then just last week I had it again. This time though it happened right after I had taken a picture. Rebooting the phone seemed to fix it until I tried to look at that picture again, then it locked up the card again. So, accessing the folder the image was in via my PC, I deleted the picture and it is all well again so far...
how much memory is left on your cards? early on (early mon?! lol couldn't resist) i thought it had something to do with this .. re; remaining memory...
The Following User Says Thank You to marctronixx For This Useful Post:
how much memory is left on your cards? early on (early mon?! lol couldn't resist) i thought it had something to do with this .. re; remaining memory...
nearly 14gb (16 card) I found some hyrogliphic named files and can't delete them. I can't reformat the card either. Looks like I may have to get me another card
I have an Incredible which I just recently upgraded to froyo and I am receiving this message as well. I don't think its my card as this never happened before upgrading..
you are experiencing what the others in this thread are experiencing. its an issue with froyo and how it writes to card.
have not been able to pinpoint the cause....
Quote:
Originally Posted by soco352
I have an Incredible which I just recently upgraded to froyo and I am receiving this message as well. I don't think its my card as this never happened before upgrading..
yo everyone having issues with this, i just had the same problem and fixed it
i can't say for sure what exactly causes it, there are a bunch of technical things it could be... but basically i was getting my sd card mounting in read-only mode (even though it's a high quality card, class 6, 8gb)
1 reboot into recovery (i'm using AmonRa - not sure if it's the same in clockwork)
2 go to Other
3 repair Ext partition
that's it... somehow my last nandroid backup left me with about 60mb of space free and it must have locked the card or something. this should fix it. also do a check disk (chkdsk in terminal or right-click on the drive and hit 'check for errors') just in case there was any corruption to the fat32 partition.
I did and tried everything and then started to think about what could be the culprit.
I really, really like Dual Mount Widget, but when I kept it off and never utilized it... all my problems were solved.
I have been worry free for 2-3 months now and the only change that worked was keeping it off my phone. I think that with the combination of Froyo caused issues. It worked great before the Froyo, but not after. Hope this helps and good luck.
I had this problem on a 32GB SDHC, and I was able to fix it.
(For clarification, since this thread is getting so long, the issue was that my Evo kept telling me that the SD card was mounted in read-only mode and a good deal of stuff seemed to be missing.)
I popped the SD card into my Mac, started Disk Utility, and clicked the 'Repair Disk' button. It found a bunch of crap, fixed it, and when I put the card back in the phone everything was fine.
I imagine this is the same thing that happens when select 'repair partition' while in recovery mode, and I would assume that Window's disk utility could do the same thing if recovery mode isn't an option.
The Following User Says Thank You to seanonymous For This Useful Post:
I had this same issue and I couldn't get it to mount. I did some googling and had found a post somewhere where someone had said that it was a photo thumbnail that was corrupted. That was exactly my problem. I copied everything over to my computer. I ran chkdsk on it and had it fix the corrupt files since unlocker couldn't delete the files. I formatted thedisk on my pc, copied everything backand like magic, I am back in business.
I guess the moral of the story is always let your photo thumbnails populate.
Hi all, complete newbie here. I dont mean to be rude or anything but aren't you all forgetting that this must be a fault? I've had this recurring "mounted read only" fault now since having my DHD. I've reformatted in phone, l/top, repaired using various different card tools and it still comes back. I've been losing photo's i've taken with camera and been unable to access other photos and saved data. I've requested info from HTC but they just asked me to do what everyone else already knows.
In a month i've tried 4 different memory cards, but still i've ended up with this issue. If people have only been getting this fault since updating/installing froyo, does it not certainly point to a software (or is it firmware) issue?
Also, I dont think i've read of anyone getting this fault with previous soft/firmware or with anyone on Gingerbread. (if i'm right in thinking Gingerbread is newer)
Many of us with Froyo aren't having this problem - so all we really know is that it seems pathological somehow - therefore, we just keep overturning stones and trying to find some common ground.
You are right though, it's hard to know what's what when things change.
In some cases, it might be a defective phone - masked by the time of the Froyo upgrade being coincidental - who can know?
Or - there's some process that may be seemingly abusive to the card's directory structure in some Froyo-only way - and some are running that process, others are not.
Others seem to have traced to bad thumbnails (see post above yours) or to not unmounting the card before ejecting from the PC - but there doesn't seem to be one known cause just yet.
"Posted by Kirosana on 3 Oct 2010 10:25 AM
I solved the problem easily. Just go to Menu/Settings/SD&PhoneStorage. Then pull down the notification bar and tap where it tells you that the sd card has an unexpected problem, while it is working to solve it quickly tap Unmount SD Card on the previous screen a few times, this should allow you to format the card to the phones specification. Thus solving the problem in it's entirety"
When Sprint announced their first ever 4G handset at CTIA in March 2010, they dropped a bombshell on the mobile world. The HTC Evo 4G is a device that introduces a lot of firsts when compared to other North American handsets. This is the first Andr... Read More
"SD Card Mounted READ ONLY" alert -- Post Froyo
tried as suggested. I reaformated my sd card while connected to my phone, transferred the documents back over. ejected and still the same problem occurs 
