My MT4G is permrooted with s=off. I am running Ice Glacier 1.1.6. I used the stock ROM for 4 days without any SD card problems. Since flashing IG, the phone is erasing my SD card every damn day. I am switching between a Sandisk 16 GB and a MicroTek 32 GB and mostly using the SD card for music storage.
I will put in a freshly formatted card (using PC running Win 7, card formatted with FAT32) with my music loaded and at some point the next day the phone will give me a message stating "SD card blank or has an unsupported file system". The phone will not format or mount the card. I'll format and load my music onto the other card, swap them, and the next day the same thing happens. I can be listening to music (mp3) and the phone will fail to load the next song, saying the file format is not supported, then the card gets nuked. I use the default "Media Room" player. Other times I will just pull the phone out of my pocket and see that the SD card has been erased.
Both cards were error free in my old Touch Pro 2.
Suggestions?
Same here, s=off running CM7 latest nightly (18). SD card just went blank today. I'm going to try another microSD first then try RC1 instead.
I ran H2testw on the 32 GB card. No errors, read 17 MB/s, write 14 MB/s. The problem is with the phone or software.
I flashed Royal Glacier and have been using it for a week without any SD card problems.
I thought this was a problem with Iced Glacier. everytime I flashed to IG this happened, but when I flashed a different ROM everything worked fine, SD card works perfectly. try to flash Royal Glacier and see if that works
Same thing happened to me when I flashed cm7 rc2,then went to clockwork recovery to only find that I cnt do nothin with the phone cause nothin wants to mount just keeps showin errors... sd card got wiped clean!
Related
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).
Hi Guys,
First off, thanks to everyone involved in the HD2 developement, it only took me an hour or so of reading posts to get android running on my phone
So, I'm having problems, and I think it's due to the memory card. I'm using the Scandisk 2GB (don't know class) that came with the phone (UK, o2). It has just enough space to run android so it'll do for now.
I tried changing my Radio from 2.12 to an earlier version, as my signal was cutting out in low-signal areas. I managed to brick the phone (used wrong version I think) and had to connect the SD card to my PC via card reader to get a different radio back on there.
When I connected it to windows, it said I had to format the card to be able to use it... It then formatted it at around 950mb, FAT32... After sorting the Radio and booting into winmo, I formatted the SD card which gave me 2GB again. I reloaded Android (I've now tried Mattc's froyosense 1.7 and mdeejays sense 1.3) and now everytime I unlock the SIM card, I get a series of errors:
The process com.htc.bgp has stopped unexpectedly. Please try again.
The application Stocks (process....
It'll loop through these errors untill I turn off the phone.
This was using Radio 2.10. I've just changed back to 2.12, which was running fine before, and I'm having the same issues. These started while I was using the Energy winmo rom, and I've tried it with ChunkyRom too (both vers of Android I have too).
Is this likely to be the SD card failing? I did see something about wiping the phone before flashing a new winmo rom, is this worth trying?
Cheers
Well, it looks like it is the SD card.
After a few more tries it's now getting to the HTC Quietly Brilliant screen and looping through the animation...
im guessing your running out of room on the card..
you said it only has 950mb free?
is that before or after the data.img file is created?
I have a problem too with a 8gb sdhc card i get the message failed to mount the sd card... I had formated it but i get the same error...With a 2gb card everything works fine!
It reporting a 2GB card as a 1GB card in windows basically. I've replaced it with a new 8GB card and all seems to be working well!
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
Had my HD2 for over a year now and finally got fed up of lack of WinMo apps, which my housemate with his iPhone loved to point out all the time. So I decided to try out Android a few days ago.
Read all tutorials etc and installed Skink's clean desire rom v1.3 using cwm. Got everything set up and was really pleased with my shiny new phone. Everything was working like a dream!
I decided to get a new 16 GB SD card as my 8GB card was full of music etc. Here is where the problems started...
To get all data onto 16GB SD card:
I partitioned it using cwm using same size partition size as on 8GB (1024mb)
Copied all files on 8GB fat32 partition onto 16GB fat32
With the 8GB SD card in the phone did a backup using cwm
Copied backup onto 16GB card inserted it into phone and did a restore
Now the fat32 and ext3 partitions on the 16GB card and 8GB card should be the same, so everything should carry on working fine when i boot up my phone.
It didn't I just kept getting lots of stopped unexpectedly errors until finally everything stopped loading even the home screen, and I'd have to remove battery. However if I just put my old 8GB card in everything worked fine as before
So after much frustation I gave up on this method and decided to just wipe everything on 16GB card and start from scratch:
Formatted 16GB card
Repartitioned it using cwm
wiped data, cache, dalvik cache
installed clean desire rom from sd card
booted up started reinstalling all apps etc
Now here is where things get very strange, I'd start reinstalling apps and reconfiguring to how it was before and then randomly I'll get a stopped unexpectedly error, like process.android.media or something similar. But it seems as if everything would carry on working, then slowly I get more errors until for example as soon as you click on internet you get an error and it closes.
I believe the problem lies with the sd card seeing as that is the only thing that has changed. I also think this rom stores more than just apps on the sd card. Because after I get a few of these stopped unexpectedly errors nothing is saved on the phone. For example I'll change the ringtone from x to y click ok, but when I click back on change ringtone it's still on x. But I can still play music that is stored on the sd card. After I reboot the phone for a while I can make changes and they are persistent but eventually I end up back at this strange state. It's almost as if I can read from the SD card but not write to it.
Another example when I've got to this strange state, I'll add a folder to home screen, add apps into etc. But when I restart the folder has gone.
If I reinsert my 8GB card and do a restore, I get everything back and it works perfectly. But I want to use my 16GB card, that's why I bought it!
My questions are:
Does anybody have an idea of what is going on when it gets into this strange state?
Does anybody know how to fix it?
Is there some way of testing the SD card?
Should my first method of getting all data onto new sd card have worked?
SD Cards are:
Samsung 8GB class 6
Transcend 16GB class 6
Sorry for the long post, any suggestions are greatly appreciated
I just flashed SlimBean 4.3.build.2.2-OFFICIAL-1738 to my Galaxy S3 I747 (AT&T version).
Since then I'm having problems accessing my external SD card that I'm pretty sure is fine since it's what I just flashed the rom from. When I first tried to mount the card in SlimBean it wanted to format it. I let it try to format, but it seemed to struggle - took a long time and got a little unresponsive.
I've pulled it and formatted it fat32 in a PC using an adapter, but SlimBean still does not work with it. Mounting, unmounting and attempts to access this card seem to have caused one freeze and one random reboot. All seems good with the rom when the card is out, or as long as I don't try to access it.
I successfully ran a TWRP backup of my new SlimBean system to this external SD. Behavior of the card is still spastic in SlimBean. It keeps showing card was removed followed by preparing the card over and over in the notification area when I try to access it from ES or Slim file explorers. I was able to see from the ROM that the TWRP backup files are there and they appear to be the right size, but the card is behaving badly.
Anyone else ever run into this problem, or have any ideas as to a solution?
I'm still fighting this SD card. I've formatted it fat32 with GParted (quick). Formatted it with a terminal mkdosfs -F 32 (sloooow). Now my phone can see it and I can browse files I've put there using a computer, but the phone can't write to the SD card. Also a media player, using rocket player, can play back songs; however, it only plays back the first 4 - 6 seconds then skips to the next song.
I'm starting to suspect a faulty card or slot in my S3. Still hoping someone from the community might have solved a similar problem....