When I do a data transfer between my Mac and my G1 running Cyanogen, the SD Card immediately comes back as corrupted. I am unmounting properly.
When I have the stock Donut on the G1 it works fine, no corruption.
Any ideas?
This used to happen to me all the time. I guess the card wasn't compatible with the phone. I was using fat32+ext2, fat32+ext3 or even fat32 on it's own and I was always having problems.
If it doesn't happen on stock donut I assume it's an issue with our ext partition (if you have one).
I would agree with you except I am able to 100% reproduce it on the 3 SD Cards I have. I am using this method to partition my SD Card through the console of the Cyanogen bootloader: http://androidandme.com/2009/08/news/how-to-manually-partition-your-sd-card-for-android-apps2sd/ I have rooted and unrooted my phone a few times trying to troubleshoot this and it happens every single time.
What happens if you only use fat32?
I've had issues w/ two cards, including the one that came with the phone. If you can, try a Transcend card.
I have not tried just one partition of FAT32 under Cyanogen. I am going to try moving a file via USB with Cyanogen 4.2.4 in a moment. If that corrupts the card I will try just a single FAT32 partition.
I have used the SD Card that came with the phone, an 8GB Class 6 Transcend, an 8 GB Class 4 Patriot (which I know have issue with the Dream so I don't really count that) and a brand new 8GB Class 6 ADATA.
I really appreciate your help.
It appears that the latest CyanogenROM (4.2.4) has solved my issue!
I have done a bunch of 1GB+ file transfers via USB back and forth with my Mac, created directories, deleted files, etc and it's holding steady (just one random reboot but I can't say if it's related or not).
Hello, I'm not glad that i have to post this topic, but i think the whole story about "Waiting for SD card" problem will never end. I have 3 SD's at home, even one not works.
What i tried:
- i read a lot of topics about this problematics
- i tried to format my cards to fat32
- i tried clean cards
- i tried to format with special tools
- i tried customize startup.txt with msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave etc.
- i tried 5 versions of android, even one not works...
I will be very glad if someone helps me or gives me an advice what should i try
Thanks a lot!
Is any one of the sd cards you tried a "class 2"? Seems that class 6 sd cards have this problem.
unstable_ said:
Hello, I'm not glad that i have to post this topic, but i think the whole story about "Waiting for SD card" problem will never end. I have 3 SD's at home, even one not works.
What i tried:
- i read a lot of topics about this problematics
- i tried to format my cards to fat32
- i tried clean cards
- i tried to format with special tools
- i tried customize startup.txt with msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave etc.
- i tried 5 versions of android, even one not works...
I will be very glad if someone helps me or gives me an advice what should i try
Thanks a lot!
Click to expand...
Click to collapse
no need to try more versions on your current SD cards. Go to look for some very old one, better smaller then 2GB.
I got 5 in my home, 2 of them works. Both of them are 2GB, bought 3 yrs ago.
None of new one could be used.
i realised the old versions of sd card works but the newer ones dun.
U shuld change SD card~~
Pretty Disappointing... I'm stuck too. I'm suprised it hasn't been fixed yet can't be that hard compared to everything else they've acheived.
I hope everyone involved keeps up the hard work but it'd be great for someone to revisit this problem.
its a hardware problem of the sd card, not a software problem.
it will never be fixed (its not possible).
its not like an sd card is too expensive ^^ just get another one...
have a look at this thread
N!ghty said:
its a hardware problem of the sd card, not a software problem.
it will never be fixed (its not possible).
its not like an sd card is too expensive ^^ just get another one...
have a look at this thread
Click to expand...
Click to collapse
I tend to disagree. SD is a well known standard on the market.
The card that I have works fine for more than a year in Windows Mobile with Touch HD card reader. Without a single problem during that time. So everything: operating system, SD card and HTC HD card reader are fine.
It doesn't work with Android, so there is something wrong. Either with SD card initialization procedure, drivers or operating system (Android).
Unfortunately, I can't effort using 2GB card. I'm using my phone e.g. for books reading, music, photos, games etc. It's not only a phone I hope that all these hard working Android guys can fix this issue.
mlemanczyk said:
I tend to disagree. SD is a well known standard on the market.
The card that I have works fine for more than a year in Windows Mobile with Touch HD card reader. Without a single problem during that time. So both: operating system and HTC HD card reader are fine.
If it doesn't work with Android, it's Android's problem. Either with SD card initialization procedure, drivers or operating system (Android).
Click to expand...
Click to collapse
we are not looking at the sd card when its detected by the operating system but by the device itself.
the problem might be that the device is simply not capable to use some sdcards without the proper drivers (which the os then provides). what im saying is: before you enter the os the device might not detect some particular sd cards, but once the os is booted, it does.
the issue here is simple: if the device doesnt support the sd card, the os wont boot, this has nothing to do with the os.
if you dont believe me:
try flashing a WM rom from the "problem sd card". u will see: it wont work.
now try booting android from the same sd card. u will see: it wont work.
now get another card u can boot android with.
now try flashing a WM rom from this sd card. u will see: it will work.
conclusion: its a hardware problem.
i must say im not an expert but im not stupid either. i tried what i explained myself and thats just how it is...
if someone has a better explanation please correct me
N!ghty said:
we are not looking at the sd card when its detected by the operating system but by the device itself.
the problem might be that the device is simply not capable to use some sdcards without the proper drivers (which the os then provides). what im saying is: before you enter the os the device might not detect some particular sd cards, but once the os is booted, it does.
the issue here is simple: if the device doesnt support the sd card, the os wont boot, this has nothing to do with the os.
conclusion: its a hardware problem.
Click to expand...
Click to collapse
What you're saying may be right. I'm not an expert either, so these are only my conclusions.
I think that what may be failing is the HSPL (Bios) that most people here loaded. I'm pretty sure that I was able to flash from SD card on my stock ROM. At some point it stopped working. I'll try to rollback to stock SPL (I'm not sure how to do it, yet) and confirm. So changed HSPL may be the issue.
Another question is, why SD drivers in either case are not loaded with the boot image. I don't know Android internals, so I can't tell if this is possible. But it would help in this case.
In both cases I don't think this is hardware issue that can't be resolved.
N!ghty said:
we are not looking at the sd card when its detected by the operating system but by the device itself.
the problem might be that the device is simply not capable to use some sdcards without the proper drivers (which the os then provides). what im saying is: before you enter the os the device might not detect some particular sd cards, but once the os is booted, it does.
the issue here is simple: if the device doesnt support the sd card, the os wont boot, this has nothing to do with the os.
if you dont believe me:
try flashing a WM rom from the "problem sd card". u will see: it wont work.
now try booting android from the same sd card. u will see: it wont work.
now get another card u can boot android with.
now try flashing a WM rom from this sd card. u will see: it will work.
conclusion: its a hardware problem.
i must say im not an expert but im not stupid either. i tried what i explained myself and thats just how it is...
if someone has a better explanation please correct me
Click to expand...
Click to collapse
Sorry. You are wrong. I am frequently flash my phone using SD card with HSPL. But the card also face problem with Android. So definitely not the hardware problem.
Hello
I have 2 card's, one 8GB from Transcend and one 4GB from Kingston, and the kingston only works with android!
UPDATE: Transcend Class 6, Kingston Class 4
cereal86 said:
Hello
I have 2 card's, one 8GB from Transcend and one 4GB from Kingston, and the kingston only works with android!
Click to expand...
Click to collapse
lucky guy
From my personal experience on my Kaiser I can confirm that newer SD cards do indeed seem to cause problems in Android, especially with installing or running from SD.
I have 3 SD cards I normally use for my phones, the newest a 4Gb class 6, which I have never been able to use for Android on Kaiser or Blackstone, I can't even flash with it, it just never works, using it for data storage works fine, just can't run Android from SD or Flash with it, the other 2 are 2Gb class 2's, both work just fine for flashing, and work great when using them for running Android builds from SD on Kais and Blac hardware.
My conclusions? Well I fall into the 'hardware problem' camp, mostly, since I can't flash either Winmo or Android with the class 6, it may be the card, but I wonder sometimes if it's the capacity, since both the class 2's are almost the same age as the class 6, all are sdhc, all 3 are from the same manufacturer , (SanDisk), in fact the only real difference is the capacity.
Waiting for SD Card
I have also tried a Transcend 8 GB SD Card and it doesn't work.
The same files on a Tanscend 1GB SD Card work just fine, so it's definitely a hardware problem caused by the card.
I've tried everything - formatting the card with different tools and different cluster sizes, partitioning the card below 4GB - all without success.
For all you guys out there with the "waiting for SD card" problem: Get a different (small) card !! - It's worth it !
what about this - copy files in the package into device internal memory and boot from there(i don´t know where to change booting directory in cfg...). if it created data.img on the sdcard, it would be fine solution...
kosmodisk said:
what about this - copy files in the package into device internal memory and boot from there(i don´t know where to change booting directory in cfg...). if it created data.img on the sdcard, it would be fine solution...
Click to expand...
Click to collapse
Not sure it's that simple... once winmo is killed, the internal memory would have to be accessed natively by Android. It could be different for every device (where as SD is a standard, device agnostic format, internal memory isn't)
Whilst most HTC devices will work in an almost identical manner, there is no guarantee of what the internal memory is (it could actually be a HDD in theory).
I had this problem with my Transcend 8GB SD card, nothing solved it so I traded it for a Sandisk 8GB SD card with a colleague.
Works fine now. ^^
kalyster said:
I had this problem with my Transcend 8GB SD card, nothing solved it so I traded it for a Sandisk 8GB SD card with a colleague.
Works fine now. ^^
Click to expand...
Click to collapse
I'm using a Transcend 8GB card...the one that came with my blackstone with no problems at all. Don't think I did anything special though, formatted to FAT32, installed android from a CAB (in this thread) loaded Android and then I copied my WinMo files back to the SD card as well.
One 2GB sandisk card I had though didn't work at all until I formatted it to FAT32 under linux, then it worked fine in WinMo and Android.
A friend also suggested to me trying to reduce the 'allocation unit size' when formatting the card but I've not tried that approach.
maybe u can try format SD Card to FAT (not FAT32 formatted i think.. maybe it FAT16)! i have 8gb and 2gb SD Cards.. and that all cards not work untill i formatted my 2gb SD Card to FAT!
CMIIW..
The 8gb card that came with my Desire HD works perfectly as you expect. But i wanted to upgrade so i bought a class 4 Kingston 16gb microsd card.
So i unmount the card, take it out, then put the new one in... and when i go to storage management it has unknown for everything. When i take the card out the OS says "Card removed, insert new one", i put the old one in and it works perfectly.
I then reformatted with windows and made it 16kb fat32 and the exact same thing happens.
The card works perfectly on the computer and is not an ebay fake.
Any suggestions?
Edit- i just loaded up CWM and it easily saw my sd card. So i dont know whats going on there. I partitioned it using CWM and now am installing a different rom and hopefully the problem will be fixed without me even knowing what the issue was.
Still any suggestions will be appreciated.
patriotaus said:
The 8gb card that came with my Desire HD works perfectly as you expect. But i wanted to upgrade so i bought a class 4 Kingston 16gb microsd card.
So i unmount the card, take it out, then put the new one in... and when i go to storage management it has unknown for everything. When i take the card out the OS says "Card removed, insert new one", i put the old one in and it works perfectly.
I then reformatted with windows and made it 16kb fat32 and the exact same thing happens.
The card works perfectly on the computer and is not an ebay fake.
Any suggestions?
Edit- i just loaded up CWM and it easily saw my sd card. So i dont know whats going on there. I partitioned it using CWM and now am installing a different rom and hopefully the problem will be fixed without me even knowing what the issue was.
Still any suggestions will be appreciated.
Click to expand...
Click to collapse
Most of the steps you took, make sense to me, but I am not an expert on this.
One question, can you let all of us know what the result was, after you flashed a different ROM? Might help someone with similar issues.
Hi all.
I have a 16gb micro sd card class 2 (sandisk).
Yesterday the message "damaged sd card" came on my notification bar.
I tried to format the card but i got no luck. With every i use i got errors (gparted, windows native tool, ubuntu disk manager).
So i bought a 8gb micro sd card class 4 (maxell) for replacement.
Sadly my htc legend doesn't accept this card neither...same message.
This time i'm sure the card is ok...because it works fine on any PC/Device i tried (including my girlfriend's samsung spica).
At first i though i might got an usb brick...so tried
fastboot oem enableqxdm 0
with no luck...then i tried flashing another rom (aliba's Cyanogen 6.1, SuperBler V4)...same behaviour.
with dispair I took my girlfriend's 2gb microsd (sandisk) and tried this time with success!!
So 2 gb sdcard works.
8 gb not.
what do you suggest, crappy new sd card? or my phone got problems with sdhc?
What's brought all the old devs back?!
I've never seen that kind of behavior before... Hmm...
TheGrammarFreak said:
What's brought all the old devs back?!
I've never seen that kind of behavior before... Hmm...
Click to expand...
Click to collapse
errors bring us here!
I can add one more to the solving puzzle:
in recovery (S-OFF) i can mount the card but while coping/reading it gives me I/O errors and than i have to reboot recovery to let it read some more (till a next I/O error...)
!!!
I'm Experiencing the same proplem. Yesterday I got the same error message "Damage SD card" I cant go into clockwork recovery mode to format SD card, I get the E:faliled to open/Sdcard/update.zip(no such file or directory). Its a 4GB Sd card and Im running CyanogenMod-7.0.0.-RC0-Legend-Kang....
Caifan09 said:
I'm Experiencing the same proplem. Yesterday I got the same error message "Damage SD card" I cant go into clockwork recovery mode to format SD card, I get the E:faliled to open/Sdcard/update.zip(no such file or directory). Its a 4GB Sd card and Im running CyanogenMod-7.0.0.-RC0-Legend-Kang....
Click to expand...
Click to collapse
I'm waiting to try a different SDHC card. I think it's related to bad quality sdhc.
I was able to format the SD card via PC recoverywindows.bat...so far no problems but who knows maybe in a near future I will probably get the DAmage SD card message again.
I had the exact same thing myself a while back. Although it probably won't help you, I took it out and cleaned the contacts (no doubt superfluous but you have to try everything, right?) and put it back in (twice), and it worked. It's been running fine for months now
Ok...I've bought a new Lexar 16GB MicroSD Class 4 to replace my old Sandisk 8GB Class 4 card.
I copied everything across. However, I get random phone freezing.
The freezing only occurs when I have the new MicroSD in. I've replace it already with a new one, but it seems my phone doesn't like it.
I've tried:
1) Checking drive for errors
2) Reformatting drive using Windows
3) Reformatting drive using Android
4) Factory Reset phone
But its still the same.
[EDIT] It seems that Android is corrupting something on my card, because when I run chkdsk it comes up with the "Errors are Fixed" dialog....it says it puts the :"files in a 'FOUND' folder". However when I look into the MicroSD, there is no 'FOUND' folder. Also, copying files to and from the MicroSD card in Windows works fine.
HELP! and thanks.
You Saw this thread? http://forum.xda-developers.com/showthread.php?t=1025501
mkmck said:
You Saw this thread? http://forum.xda-developers.com/showthread.php?t=1025501
Click to expand...
Click to collapse
Ok..I'll give it a go. Using SD Formatter with Full (Overwrite) option. I hope this works.
[EDIT] SD Formatter has not solved problem. Also, reformatting in 8k, 16k, 32k, 64k not working.
Annoyed.
I think Milestone2 have a SD card compatibility issue .many kind of sd card can't run well on the device .but sandisk is good on it .
I have the same problem, can´t fix... I think is a bug ...