Alright I just spent the last hour scouring over threads, trying to find an answer to my problem (which I haven't).
I am unable to write anything to my sdcard when it is mounted. If I try, it simple unmouns immediately.
Initially I thought this was caused from apps2sd, but as I recall I had these issues prior to having that mod, so I know its not that.
It has worked in the past for me, and I've tried to diagnose but, haven't really gotten anywhere. I've googled, I've searched, I've read, I've gotten no where. So instead of "please use the search function", could I actually get some assistances?
I'm just tired of having to turn off my phone, pull out the sd card, put it in the media reader, put whatever I want on it, put it back in the phone and wait for it to boot up. It's just a long process that I ought to be able to avoid.
Have you tried to reformat the partition to fat32? Possibly wiping the entire card and rebuilding the fat32/ext2 partition. If you have a second scared try it and see if your Android sees it as read only too
I've had this happen twice. Both times it was a prelude to the card becoming unreadable as well. Get anything important off of it and reformat with this.
Short story: Was running the latest (as of Dec. 4-5) ICS ROM(s) - the ones with the SD card bug - and my SD card appears to be shot.
Long story:
-----
I had been using the various betas of the ICS ROMs since I noticed Tytung's first Alpha was out and the ROMs had been improving rapidly. I guess when the headphones issue was fixed it caused problems with reading the SD Card which was documented and seems to be well known.
The constant SD messages didn't bother me much, but eventually I noticed launch icons missing and went to the Market to re-download one of the apps I use (I've been flashing so much, I wasn't sure which apps I didn't bother restoring). The Market app tells me I need a SD Card to install apps, so I just figured it's just the instability of the sd card mount for this latest batch of ROMs and I'll flash an older ROM off my SD card when I get the chance. I also noticed the messages started saying I inserted a blank SD Card but I brushed it off (couldn't look into it at the time).
I get home and find out Clockwork refuses to mount my card which means I can't easily wipe and install something else, so I switch to USB storage mode in CWM to simply transfer a ROM from my PC and my PC only sees ~30mb of my 16GB SD! I initially thought it was just some corruption but I tried all sorts of format and partitioning programs and nothing recognizes more than 30mb of space and none have even been able to format that little space that's showing.
I've been Googling for a while and came up with nothing I haven't already tried so I finally decided to post here. Is there any hope for my SD card? Being the holiday season and for once I've got most of my Christmas shopping done early, I'd rather not waste the little money I have left to run out and buy another SD card right away if it's not necessary.
-----
Does anyone have any ideas how I could fix this? I'd greatly appreciate it because I now stuck with WM6.5 and realize how much I didn't miss it for the past year
This is also a heads up for testers to be sure to upgrade their ROM ASAP (or at least to the kernel that fixes this) if they're on a ICS ROM with an SD card bug. I'm not complaining - I know this is a part of testing early builds (please ignore my sorry post count; I've been flashing for quite a while) - but there's no reason for others to go through this issue if it can be helped.
Have you tried EaseUS?
Sent from my LG-VM670 using Tapatalk
Yes,
Try Easus Partition Manager and/or MiniTool Partition Manager.
They can help but you will have to format your SD card I think.
Good luck!
I had the same problem. I plugged my card into a USB reader after it working error free, it then said it needed to be formatted and was only showing 30mb. After formatting repeatedly it still doesn't read. I haven't retired any positioning software but i think the card may just be done with.
Sent from my HD2 using XDA App
probably you'll need a replacement.
have you tried the SD formatter? there's like a 0.000001% chance it will work in your case, but why not try it?
I have an U8800H for about a year. I've used a lot of ROMs with it, and most of them worked perfectly.
Some months ago, Huawei released the 2.3.5 Firmware update for our phone. I installed it and faced the lot of problems that most of them are by now well known and some of them repaired.
But one of these problems was the curious "SD destroyed" problem, that plagues -as I found- a lot of U8800 users but is also so sporadic that is very difficult to pinpoint - and is present in EVERY ROM that is based on 2.3.5 update (.35 kernel).
Let me explain:
After some days with the 2.3.5 update, my phone crashed and rebooted. When rebooted, I found that my Trancend 4GB SD card was not mounted anymore. The phone could not mount it and found it as "destroyed". When I tried to mount it again, some times the phone reported that "SD card was ready to be removed" or such, and others that the card was "destroyed".
The card, though, was perfectly readable by all of my PCs and other phones. The only way to mount it again in U8800 was to copy its contents somewhwere else, format it, put back the contents and insert it again in the phone, after rebooting it. And, strangely, the card was working again perfectly, for 1-2 days at least, until this problem repeat itself.
I thought that the problem was one of the stock ROM's many faults, so I tried a lot of other ROMS, like MIUI, CM7, etc. The problem repeated itself in every one of these ROMS.
I thought that my card was problematic, so I tried to use an older but perfectly unused 2GB Kingston SD card. The problems repeated with this card, also. I also used the new card with the other ROMs. I lost many hours and the problem was always there.
I also tried two 1 GB cards and three 16GB cards. I had the same experience with any of these, emerging after of 2-3 days of use of every card.
I found a lot of forum posts where users are reporting the same problem, without any solution, probably because it happens not to every phone and because it's also sporadic.
I thought that my phone was broken, so I installed the original stock ROM, as the service center would not accept it with a custom ROM. But when I reverted back to the original, the problem disappeared!
With the old stock ROM, everything is running perfectly and the SD card is always correctly mounted.
I tried to go back to the new custom ROMs, only to meet again with the same problem. The new "Gingerbread" ROMs, have obviously a bug!
Now I am using the old stock ROM and I have no problem, again.
I am writing all these to ask If someone has the same problem, and to report it as a bug that is hidden somewhere inside the .35 kernels.
You should have post this topic in the Q/A Section :|
It's not a question, its the report of a bug inside the .35 kernels. It's now specific to one of them, but present to all, that's why I had to create a new thread.
I have found also that the problem lies with the new gingerbread bootloaders and it is not present in the froyo bootloaders.
moving this thread to general section.
Try fix permissions in cwm. It works for me.
Sent from my U8800
I have the same problem with SD cards on my U8800.
It has destroyed 2 cards so far for me. When I first did the official gingerbread upgrade it didn't go well I had to try and install it multiple times and it kept going into boot loops. The end result was that my Class 10 16GB card became so damaged that it wasn't even detectable on multiple PCs with various card readers.
Thanks Huawei £15 down the drain.
My second card and I suspect my third card which is still in my phone, have problems with writing. Small writes are OK but as soon as something writes more than a few MB the card fails silently and the OS or phone thinks the file has been written but it hasn't and then subsequent writes fail. Unmounting and remounting the card in the phone makes it writable again for a while. These symptoms persist even when used on a PC so the phone is doing something bad which damages the card.
This problem occurs with dzo's ICS as well as official GB so I think the original posters assumption that it must be some code in the bootloader that is causing this problem is likely correct.
I'd love Huawei to fix this or find a workaround as I would rather not return my phone because I would likely only get refunded 50% of what I paid originally and I actually really like the phone.
Froyo roms worked fine with the SD card, it is definitely the poor quality Huawei update that has caused this.
I think I have an answer. Back when I started tampering with the phone I had changed the data/internal usb partition sizes as here: http://forum.xda-developers.com/archive/index.php/t-1112857.html
Somewhere I read about a user who had the same problem as us, and he had done the same change.
So today I reverted back to the original partition sizes, installed 2.3.5 stock ROM and the o/c kernel and until now I have no problem.
Maybe something in the new firmware doesn't like the changed partitions and thus the problem is created...
Sensimilla, If you also changed the partition sizes, then we have an answer.
Update: The bug reappeared. After 4-5 hours of heavy use, my 4GB card was once again "destroyed". So the partition sizes had nothing to do with it.
So, I tried what entrapmen suggested. I booted to recovery and chose "fix partitions". And it worked. My card was once again mounted correctly.
I don't know what to say. I will keep posting until we find a more permanent solution...
It seems I found a permanent solution: Install Aurora ICS 4.0.4: http://forum.xda-developers.com/showthread.php?t=1492957
I am using it for about 20hours now and everything runs smoothly. Probably the new Android 4 bootloaders fixed the bug.
(And as an added bonus, our phone gets a radio!)
Hopefully it works for you, too.
lateris said:
It seems I found a permanent solution: Install Aurora ICS 4.0.4: http://forum.xda-developers.com/showthread.php?t=1492957
I am using it for about 20hours now and everything runs smoothly. Probably the new Android 4 bootloaders fixed the bug.
(And as an added bonus, our phone gets a radio!)
Hopefully it works for you, too.
Click to expand...
Click to collapse
Dont get much excited. Im using ics and time to time problem still occurs but not that much. Like i said before a fix permissions resolve the problem.
Sent from my U8800
It's nearly 3 days now with ICS 4.0.4 and the bug didn't appear - and I did some heavy testing. I transfered lots of small and big files to my 4GB card without the slightest problem many times.
I did some more testing on my sdcard and it is indeed damaged. It seems to have been set to read only permanently. Windows 7 doesn't detect this but I downloaded the official sdcard formatter from panasonic and it says the card is read only. Apparently there is a small protected section of the card that is hidden and used for DRM, read only can be marked in this section of the card. Normally this section is only writable by the card manufacturer. I guess as the phone has low level access to the card via hardware this section could have been inadvertently damaged by Huawei's bug ridden update. This is the same state that my previous card ended up in too.
The apparent writing to the card seems to just be the cache on the phone/computer which mounting and unmouting resets.
I will buy another small sdcard and just use it with ICS Aurora this time and see how it goes. I have been using Aurora for the last month anyway. Maybe it will be fourth time lucky.
Just clear the whole MicroSD card with dd program writing it full a random data first and then after that zero.
And if you can not detect the card at all with dmesg program, then that card is destroyed.
It's a week now with ICS Aurora 4.0.4 (206,207 and now 208) and the bug didn't appear at all.
I filled my -previously problematic with 2.3 ROMS- 4GB SD card fully, I even tried to stop file transfers abnormally, pulling the cable. But no problems appeared whatsoever.
So I have to believe that with 4.0.4 the problem is gone.
course, the first time i created this thread, some hangup or another, i was forced to sign-in again, losing my post. so it goes. at least it's suits the general discord-difficulty i am experiencing over here...
at first, i burnt the linked 'generic-sdcard-v1.3-CM7-9-10-larger-Rev5.zip' file to my 2gb Apacer micro SD card, using gparted via linux. i then put the corresponding GAPPS file and the cm-10.1.3-encore file (having added 'update' to the front of the filename), w/out unzipping them. the NC did its thing, and auto-restarted, but when powering-on, it said it was missing some files. it seems to me that somewhere along the process, my NC is deleting/tampering with the files, and then upon restarting cannot locate them. can this be possible? sounds loony.
i am still not sure what the deal is - bad card, perhaps? in some of the other threads i have read, that seems to be the last/worst case scenario; if all else seems correct, probably a bad card.
partially by way of desparation, and partially by way of assuming i had a bad card, i got a class 10, 32gb sandisk sd card. after repeating the aforementioned step-by-step process, the NC refuses to recognize the bootloader, bypassing it entirely, straight into the default.
evidently, the .img file was burned correctly, as my terminal indicates the collection and storage of the file.
i tried over and over to rectify this issue, to no avail. i would be immensely grateful if you were able to help me out.
and thanks so much for spending (what seems like) an awful lot of time helping people out!
looking forward to getting this thing resolved.
I assume you are following my guide listed in my signature. You should now be using rev6 or 7 of the image since those versions have improved kernels to help with finicky cards, which I put that class 10 as. And you do not have to add update to the beginning anymore. The script that runs on boot does delete the zip files when it finishes. And if you read my NC Tips thread, item A10, you will see it is sometimes difficult to burn a card so that it will boot. There are tips there to improve the chances of it burning properly so it will boot.
Sent from my BN NookHD+ using XDA Premium HD app
Strange situation. Tmobile Note 3 upgraded to KitKat, never rooted. After update, strange things occurring in system. Figured the update botched things up so I decided, Knox be damned I'm rooting this thing and starting fresh on a new rom.
It now appears that it's my memory card [official SanDisk 64gb] that is having issues. Have a couple files in LOST.DIR folder and for the life of me, I cannot format the card in Android or Windows. Either says failed or success but regardless, all my files are still on the card and can be mounted, read, and written to without any real trouble.
Really wish to avoid buying another card unless I have to. I've had all 3 Notes and they all have killed an sd card at least once. I almost think it's Sammy's fault.
Can anyone point me in a direction? Most things I've searched for are fixing dead cards, haven't found anything about cards that work but won't format.
Thanks for any help you can offer!
Upon further investigation, it appears that "track 0" has gone bad and I'm SOL.
Welp! Time to buy another card, woop'de'doo