On my computer it's fine. I just want to listen to my music. Damaged or not.
What causes Damaged SD cards?
Try to reformat it and see if it works. There are several things that can cause a card to go bad.
I have and just spent countless hours getting music on the card and I downloaded an .apk when I got error (Installed and worked fine) then just got error.
How to safe me from these from happening again?
All my apps are gone due to app2sd bummer
sillyshy said:
How to safe me from these from happening again?
Click to expand...
Click to collapse
Just do what you always prolly do. Just make sure to unmount before you disconnect. Sometimes the cards can just go bad. Just make sure to get a name brand card and get a class 6 (you don't have to). It was prolly just a fluke.
Sandisk 8gb class 2 I do unmount error for past 3 months. Know I can't get back my apps2sd to rework after I did a format.
How did you format it? In the phone from UI? If so then it erased your ext partition.
Look in HERE for good guide on how to check what partitions do you have and to format and repartition.
Good luck
If your running swapper, you need to turn it off before mounting. Thats the main cause if its not actually damaged.
I had that happen to me when I tried using Apps 2 SD 2. It said it corrupted my SD, and when ever I tried to unmount from the PC, it would freeze up. I just backed it up, deleted all my partitions, reformated and made new ones. What ever A2SD you're using, make sure you follow tuts correctly.
If you use AppsToSD to partition your card and you get an error saying that your SD card is corrupted or damaged, ignore it. Take out the card, format the Fat32 partition on your PC (a full format, not quick erase). When it's done, both the Fat32 and ext2 partitions will be there. I have experienced that problem several times.
Also, you can do adb to get the files off the ext2 partition before you use the phone to remove the partition and re-format the card.
Well guess what all I did was turn off my phone overnight and charge it. This morning turned back on got the same good message after spending 5 hours putting music onto my card. So this time I am doing a full format of the card and just using fat32 nothing more no apps2sd I think that may be my problem. Cause when using it I don't get the option to safe remove the sd card in SD card settings.
My 2-yr old 8gig Sandisk Class 2 SDHC suddenly went kaput and won't be detected by my Topaz.
This sd card has been previously fat32-formatted and worked for 2 yrs.
Lately, before flashing a cooked ROM, I ran the mtty1.42 if that matters
Now, my phone won't even detect another sdhc (4gig Sandisk, Class 6) which is working fine on my wife's Raphael and/or my PC.
The error message the defunct 8gig SD card gives when connected via card reader to my XP sp2 machine is:
Exception Processing Message c0000013
Parameters 75b6bf7c 4 75b6bf7 c 75b6bf7c
[Cancel] [Try Again] [Continue]
You can't format something that is undetected, right? Any clue, please? Thanks.
Sandisk SDHC Class 2 goes dead, and won't get detected
My 2-yr old 8gig Sandisk Class 2 SDHC suddenly went kaput and won't be detected by my Topaz.
This sd card has been previously fat32-formatted and worked for 2 yrs.
Lately, before flashing a cooked ROM, I ran the mtty1.42 if that matters
Now, my phone won't even detect another sdhc (4gig Sandisk, Class 6) which is working fine on my wife's Raphael and/or my PC.
The error message the defunct 8gig SD card gives when connected via card reader to my XP sp2 machine is:
Exception Processing Message c0000013
Parameters 75b6bf7c 4 75b6bf7 c 75b6bf7c
[Cancel] [Try Again] [Continue]
You can't format something that is undetected, right? Any clue, please? Thanks.
Yea that happens my 1yr 8Gb class 6 dies a while ago but that was from my using it for readyboost and eboostr(unrelated).Now i got this 4gb class 2 thats pretty fast If you had swapper then i think the card could be damaged, try formatting that sd card in recovery mode.
there is a way to reformat the card if its not physically damaged but it seems like yours is. I dont rmr the commands to do it in gparted, butits possible
Related
I have AT&T Tilt with Sakajati's HyperDragon IV Windows Mobile 6.1 OS ROM, I also have this 8 GB micro SD card, which has around 3.5 GB of data, but for some reason I am not able to write on it any more. When ever I tried to format it I get this message which says " The card is write protected" I don't remember putting any password or anything. I can read data from that card on any computer or phone, but can write anymore data on the card. I can't delete anything from the card either.
Can someone suggest what could be wrong with the card and how can I unlock it?
I have tried low level format also, the format completes without any error, but when see in file explorer all the files are still there. If I try to format from SD formatter, I get error "The memory card is write protected", windows format doesn't give any error, just runs and in the end says "Windows can't comeplte the format". Card is working file and have no problem in reading the data it has, just can't write new one ot delete old one.
This is very weird problem... any help/comment is good.
Not sure if this will help....
I've had very similar issues over time...
Because of high TomTom & Music Use.
Both are loaded and work off my SD Card (6 GB worth)
What I finally found that worked for me, was to get a 2nd card and backing up my SD card to my Desktop PC, so later I could transfer to the 2nd SD Card when needed.
Then I do a Complete Format [Full FAT32 Format] of the old SD Card, via the Mini SD adapter on my Desktop PC.
I found that formating within the phone doesn't always work...
If this is not the case I can think of 2 other reasons for potential problems..
~Some ROM's require the removal of SIM & SD Cards when installing?
~If you were using an adapter formating the SD Card and it was not set to write mode?
Best of Luck!
JAC,
Thanks for your reply, but I have already tried FAT32 formatting using micro sd card, but as I said before, but it errored out.I even tried low level format, but didn't work. There is no locking swithc or anythign in micro SD card, not sure how the data can be locked. If it was ecrypted I was not able to read data on other devices. So what happened? Any help!!!
Like everything else, sometimes things just wear out, break or are just low quality to begin with. If you can read it on other devices, then transfer it and get a new card.
There is also a trick used by nefarious suppliers that takes a 4GB (or any size chip) and format it in a way that it appears as a larger chip. Then when you go to write to it the whole thing goes crazy.
This is why I recommend using reputable resellers and buying good quality Name Brand Chips, Like Sandisk or Kingston.
I have a 16 GB class 4 Sandisk card.
I ran the following command and successfully wrote the img to my SD Card
[email protected]:~$ umount /dev/sdg
[email protected]:~$ sudo dd if=nookhoney04.img of=/dev/sdg bs=1M
Click to expand...
Click to collapse
The SD Card now has a system, boot, data, and sdcard partiton. So I assume it was finished. I also received a confirmation message stating that it successfully wrote 3.7 GB to the card.
All appears well, but when resetting the nook, it almost immediately boots into stock instead of the sd card.
Am I missing something, or is this a card issue?
it might be the card, class 4 is really slow for honeycomb
Would "really slow" cause it to entirely skip the boot.
People claim to have got it working with a class 2, even if it is slow, it should still boot...
I appologize for bumping this, but I would really like a more definitive answer than "slow".
MXIIA said:
I have a 16 GB class 4 Sandisk card.
I ran the following command and successfully wrote the img to my SD Card
The SD Card now has a system, boot, data, and sdcard partiton. So I assume it was finished. I also received a confirmation message stating that it successfully wrote 3.7 GB to the card.
All appears well, but when resetting the nook, it almost immediately boots into stock instead of the sd card.
Am I missing something, or is this a card issue?
Click to expand...
Click to collapse
If they're in that order then somethings wrong. It should be Boot,System,Data,sdcard. Also a slow card shouldn't cause the boot sequence to be skipped but there could just be a compatability issue with your card
I suggest trying again to see if it works (btw I never use the BS=1M but that shouldn't cause any problems)
They're in the orter of boot, system, data, sdcard.
I used the bs=1M when I wrote autonooter, I guess I'll try it without that parameter since that's the only thing I can change.
It's kind of odd that the SD card would not boot... I've booted onto this SD card before when testing Froyo and doing some Clockwork recovery.
There are no buttons I have to hold to force a boot?
I am powering it on via plugging it into my computer, though I have tried a hard power on.
This maybe a card issue. So far all 16Gb cards I installed Froyo/Honeycomb booted successfully as long as you do not repartition the card with default head/sec/cyl (must be 255/63/the rest).
However at this moment neither Froyo nor Honeycomb work on any 16Gb card I tried. It installs fine, and boots ok, but after the first reboot the data partition gets corrupted almost immediately, and remounts read-only. If you eject the card, connect it to a Linux machine and run fsck.ext3 on /dev/sd?3 it will fix it, but it will be broken again during next reboot. Same images/files work fine on the same Nook on a 8Gb card.
No need to unmount the card. And normally your sd card is mmcblk0 or mmcblk1? Format your card, insert it into your computers sd card reader and in a terminal type "sudo fdisk -l" look for the device that is the same size as your card. Also, did you use your nook as the card reader for the computer? Most of the time, using the nook as your card reader when writing images doesnt work, you have to use the computers reader directly.
edit: Possible compatibility issues. 16gb's seem to have problems with corrupted partitions when writing sd images.
Hmm, that's interesting, is there any way to change the cyl-dead-sector data on linux?
If not, I guess I'll buy an 8GB class 6+ soon.
http://www.amazon.com/Transcend-microSDHC-Class-Memory-TS8GUSDHC6E/dp/B0026L7DG0
Would that card suffice?
Yes, that card seems to get really nice reviews as far as running HC goes. That or a Sandisk.
Well that card is under $20 dollars, so it works perfectly for me. Thank you for your feedback
I bought A-Data 8Gb class 10 microSD in Fry's, and it seem to work very well. $13.
Not sure how long it gonna last, but if it lasts a year, good enough for me.
The issue I mentioned, however, is not due to the card quality. 'badblocks' utility consistently showed all those cards having NO bad blocks, and I tested at least three different 16GB cards - Wintec, Patriot and A-Data.
RileyGrant said:
Yes, that card seems to get really nice reviews as far as running HC goes. That or a Sandisk.
Click to expand...
Click to collapse
Well, the card came in.... and no luck, same thing... I'm going to try it on Windows instead of Linux, see if that changes anything...
After I "upgraded" to 1.1.0 it jacked up my ability to boot from external SD card. Lots of random process failures and can no longer read my class 10 card at all. Going to revert to 1.0.1 I think... or else flash a CFW on instead. Seems like they added something nasty to the update.
Just to give some newcomers my experiences with the following two cards:
Lexar Class 10 32GB:
Stuck forever at the black screen with the message "android_" at the lower left. Tried both v3 and v4 of the honeycomb SD image. Neither worked.
Transcend Class 6 16GB:
Tried v4. Same pronlem as the Lexar. Stuck forever at the "android_" screen. Switched to v3. Bingo, it booted!
I should be receiving a Patriots 16GB tomorrow and will put it to test.
xdadidida said:
After I "upgraded" to 1.1.0 it jacked up my ability to boot from external SD card. Lots of random process failures and can no longer read my class 10 card at all. Going to revert to 1.0.1 I think... or else flash a CFW on instead. Seems like they added something nasty to the update.
Click to expand...
Click to collapse
Hmmm... that seems interesting... can anyone else confirm this?
I have two SD cards. One gives me the infamous encrypted file system error and the other just sits there looping on the android splash screen. Before updating, both ran honeycomb fine (CL4 and CL10).
I seen to be the only guy left with this problem. I have burned Nookie FROYO to an 8gb card. Using Mini tool partition wizard i then extend the last partition to cover the unused space. Then the Nook boots fine but gives me the 'damaged sd card' error. I tried the Vold method people used on older NF builds, but that seems just to ruin the image. If i don't resize the partition, everything runs fine and i can use the very limited free space on he card as normal. I wanted to try Easeus instead of minitool, thinking it might be something in the software, but i can't get Easeus to see the card at all after it is burned.
Can anyone help?
any advice on where to go here? I also asked at android central, and not getting any hits there either?
Thanks,
Brian
I've also tried deleting the sdcard partition and recreating it the right size. Since resizing didn't work, I thought this might. But it didn't. Still getting the 'Damaged SD card' error.
How is it that I'm the only one out there having this issue? Very frustrating.
-Brian
had same problem through the sd card in my fascinate and tried to format didn't work then plugged in my phone to my usb cable then unplugged went back and it auto formated for me so now i have my nook sd card all good just a little help
Well, I tried that as well. I plug the NC in, and it shows up as two different USB devices. E and F on my Win 7 machine. After quite some time waiting, I can actually open drive F in windows. Unfortunately, when I unplug my NC and try and remount the SD card, it doesn't do anything different. Still gives me the damaged SD card error.....
What else can I do here?
-Brian
I'm having a weird problem with a Nexus One. It had a 2GB microSD card in it that seemed to go corrupt (all the file names went crazy) so I reformatted it and it happened again within minutes. So today I bought a new 8GB microSD card and and the Nexus now gives the error of "Blank SD Card - SD card blank or has unsupported filesystem." It is unable to format the card, but it doesn't give an error. I tried formatting the card to FAT32 on my computer, still the phone thinks it is blank/unsupported.
I'm hoping the SD slot isn't fried... any thoughts?
You could try reformating the SD card in a computer using SDformater with erase on.
I have the same problem for a few weeks now. My phone can't seem to read the sd card at all. Thought it was the sd card so I bought a new one, but problem remains. I know both cards work (have tested them in another phone and the computer reads them). I've tried formatting the card in the phone and reformatting with erase on using SDFormatter in my computer but my phone refuses to read it. Think it might be my sd slot as well...
Currently running CM 7.1.0. Haven't tried a factory reset or flashing another ROM (how would one go about doing that with no sd card?) as I'm not too keen to lose that data if I can help it.
Did you manage to fix it?
I was not able to fix it and after many hours of troubleshooting, so I gave up. Good luck to you, and please reply if you find a solution.
Hi,
2 weeks ago I bought a new Transcend 32GB class 4 microSDcard because the 2GB card that was delivered with my GT-S5830i gave the message "possibly damaged" and after formatting it, the message came back after a few days.
After taking backups I resized my new 32GB with GParted:
the current fat32 partition 1GB less and creating an extra 1GB ext3 partition to use in the future for custom roms.
Everything went well for a couple of days, then I got suddenly the notification that my card was unavailable.
I have a microSD card adapter, so I put the 32GB card in it, but the card was not recognized by my Windows laptop.
(The original 2GB card is recognized by my Windows laptop.)
Conclusion: I can throw away my new card?
I guess this problem is not caused by using GParted? Maybe GParted can corrupt it, but than at least I would be able to mount the SDcard and format it and start over again?
michielvDroid said:
Hi,
2 weeks ago I bought a new Transcend 32GB class 4 microSDcard because the 2GB card that was delivered with my GT-S5830i gave the message "possibly damaged" and after formatting it, the message came back after a few days.
After taking backups I resized my new 32GB with GParted:
the current fat32 partition 1GB less and creating an extra 1GB ext3 partition to use in the future for custom roms.
Everything went well for a couple of days, then I got suddenly the notification that my card was unavailable.
I have a microSD card adapter, so I put the 32GB card in it, but the card was not recognized by my Windows laptop.
(The original 2GB card is recognized by my Windows laptop.)
Conclusion: I can throw away my new card?
I guess this problem is not caused by using GParted? Maybe GParted can corrupt it, but than at least I would be able to mount the SDcard and format it and start over again?
Click to expand...
Click to collapse
If you somehow get the card(s) detected in windows, or if you buy a new card; try MiniTool Partition Wizard Home Edition (Free for windows) to created partitions. It works like a charm for me and many others. Hope this helps you. Cheers and Hit Thanks if I Helped You
some days ago i had similar problem, my microsd was not recognized.
i put the card into my laptop, and formatted using gparted (i use linux).
everything work fine now