Hello All. I received a 32gb Class 4 SD Card for Christmas this year and have had nothing but issues. I am a faithful CyanogenMod 7 user and love the rom. However it constantly dismounts my new SD Card and other odd behavior. I have been testing it on stock 2.2 for a few days now and have had no issues. I have tried factory resets and so forth but nothing seems to make a difference. I have tried the latest MIUI as well. I assumed the SD Card was the issue for the longest time but since it works on stock I don't see how that could be the case. Perhaps a new kernel could help? If so any recommendations? I was running Teamhacksung ICS alpha build #14. It kept the card mounted fine but one issue made it unsuable for me.
Anyway any help appreciated. Thanks for reading!
This is a known issue, and it would help if you SEARCHED and then if you still didn't find the answer(which you would have). Then ask in the CM7 Q&A thread!!!
my apologies sir I am still very new.
I went to restart my Xoom Wifi a couple days ago because it wasn't detecting my local wifi signal and upon doing so it got stuck on the Motorola Dual Core screen.
I was able to access fastboot and send commands to it but could not get it to start up past the dual core screen.
I erased everything on my xoom, reset it to factory and still nothing. I downloaded RSD Lite and flashed what I thought was the US stock ROM and nothing happened...until I pulled out my SD card.
Now it boots all the way and has not issues running. If I put the SD card back in, problems start up again. What in the hell caused my SD card to do this?
So I'm also stuck back on Honeycomb 3.2 and it says my Xoom is up to date?
I guess this is as good a time as any to root and put a different ROM on it.
Has anyone had these issues? If I wasn't clear, this was a stock Xoom Wifi I hadn't done anything to it. I'd been using the SD card for about a month and then this happened.
I think it is a good time for you to root it and flash ICS 4.0.4 custom Rom fro EOS on your wifi xoom.
For the SD Card issue, try to format it first or try another one just to test.
To root and flash ICS ROM, the best out there, use this:
http://forum.xda-developers.com/showthread.php?t=1717402
Good Luck...
+1
10 char.
While having root access and being rom'd might be a way to go... You should also try formatting your sd card. Perhaps it is corrupted and that is messing with your xoom. Honeycomb doesn't write to the sdcard without root in 3.2 and doesn't even look at the sdcard in 3.0, which is probably why honeycomb is working for you.
I got this for the 1st time yesterday since updating to ics. I only updated because my phone kept resetting since I installed a copy numbers to sim card app. Is this warning the ics version of resetting? What I mean is that I never had this warning on gingerbread and it got me thinking that ics removes the sd card to prevent the phone from restarting.
Anyway I sorted the problem by connecting the sd card to an adaptor on my pc then moving all its content onto pc and I then put the empty sd card back in my phone and formatted it and lastly put the files back onto it and its been fine so far.
scorpionatthepc said:
I got this for the 1st time yesterday since updating to ics. I only updated because my phone kept resetting since I installed a copy numbers to sim card app. Is this warning the ics version of resetting? What I mean is that I never had this warning on gingerbread and it got me thinking that ics removes the sd card to prevent the phone from restarting.
Anyway I sorted the problem by connecting the sd card to an adaptor on my pc then moving all its content onto pc and I then put the empty sd card back in my phone and formatted it and lastly put the files back onto it and its been fine so far.
Click to expand...
Click to collapse
I am also experiencing the same problem, the only way it seems for the SD card to be recognised again is by rebooting the phone.
I also experienced this when trying to restore contacts from the SD card.
Are you on ics or gingerbread? Like I said I never experienced it on gb but on gb the phone would reset if it didnt like something on the sd card.
scorpionatthepc said:
Are you on ics or gingerbread? Like I said I never experienced it on gb but on gb the phone would reset if it didnt like something on the sd card.
Click to expand...
Click to collapse
I have just updated to ICS and this has only started happening since that update.
What happened to the phone on GB if something went wrong with the SD?
Did it randomly go blank and have to be turned back on? If so I wonder if there is a fault with my SD card as what I have just described had been happening to me randomly while on GB.
On gb it would restart continueusly if there was a currupt file or if it didnt like something I installed. But this unexpectedly removed thing seems to be something ics does to stop it resetting.
Well I thought I solved the problem but its back again. It seems to happen when I go into gallery which makes me think theres a file in there what it doesnt like so Im going to move all pics to my pc and see if that solves the issue.
scorpionatthepc said:
Well I thought I solved the problem but its back again. It seems to happen when I go into gallery which makes me think theres a file in there what it doesnt like so Im going to move all pics to my pc and see if that solves the issue.
Click to expand...
Click to collapse
I have been having this issue too, but only since updating to the Andromadus Jelly Bean, I was running CM 9 for a while and this issue never occurred nor when I had the NEXX/NK111 Jelly Bean so I've put it down to something in the Kernel 3 code that the Andromadus build is using. It doesn't occur often, but you can guarantee that when it does it's when I really need it not to!
I've tried 2 SD cards, re-formatted, checked, etc and that makes no difference. I've gone several days without it happening and then it will just do it and it can take several reboots before it's stable again. I'm just looking at going back to the NEXX/NK111 builds now, I've not posted enough to be able to put this in the developer forum, but nobody else seems to be having this issue in the Andromadus thread.
RoboFig said:
I have been having this issue too, but only since updating to the Andromadus Jelly Bean, I was running CM 9 for a while and this issue never occurred nor when I had the NEXX/NK111 Jelly Bean so I've put it down to something in the Kernel 3 code that the Andromadus build is using. It doesn't occur often, but you can guarantee that when it does it's when I really need it not to!
I've tried 2 SD cards, re-formatted, checked, etc and that makes no difference. I've gone several days without it happening and then it will just do it and it can take several reboots before it's stable again. I'm just looking at going back to the NEXX/NK111 builds now, I've not posted enough to be able to put this in the developer forum, but nobody else seems to be having this issue in the Andromadus thread.
Click to expand...
Click to collapse
For further info, I've put the JB [ROM][04 SEP 2012][JB 4.1.1] Codename Android Saga 3 Nightly on my phone (not the latest build, that has Kernel 3 and some bugs) and it's been running now for about 36 hours without any issues, the battery life is better than other build's I've tried and I've had no SD card errors so far even when trying to cause one by doing a lot on the phone at the same time (which is the rumoured cause).
I think I might of solved this issue. My 8 gig class 4 card seems to work fine in my desire s yet my 16 gig class 6 card doesnt as it gives the removed message so logic tells me if I get a 16 gig class 4 card all should be fine.
Well I received my 16 gig class 4 card yesterday and transfaired all data to it and all seems fine so far so I guess class 4 cards are more suited for the desire s.
I'm using a 16gb class 10 in my desire S on Andromadus JB. I had the problem originally when I flashed from GB, however many reboots I tried it didn't fix.
I reformatted the card outside of the phone and it's been working fine since (3-4 weeks ago) except for one time. I've no clue what caused it, I went to sleep with it working fine, woke up in the morning with the issue again - a reboot fixed this though. Must be a kernel issue, since I never had the problem on any roms, GB or ICS, that I tried before.
I'm using a 4gb class 2 in my desire S on Official Sense 3.6 and Android 4.04. I had the problem originally when I flashed.
pedroxda-developers said:
I'm using a 4gb class 2 in my desire S on Official Sense 3.6 and Android 4.04. I had the problem originally when I flashed.
Click to expand...
Click to collapse
It is happening on any Sense ICS ROMS!
My wifes brother have HTC ONE V.
He have the same problem at least twice a week!
I think it's common bug for all HTC ICS ROMS!
I found this thread after searching for this issue. I have the T-Mobile Samsung Galaxy S2 and have also been having this issue constantly since updating to ICS.
Hello,
I am very new to all of this and any help would be appreciated. I just rooted and unlocked the bootloader on my verizon galaxy s3 for the first time without any issues (its my second android phone, but my first time rooting). for my first custom ROM i downloaded and flashed CM10.0.0-d2vzw and did everything through ROM mananger. everything went through cleanly, but since it finished i have had a message in my drawer that says the SD card is damaged and that i should try to reformat it. i have the card backed up on my desktop, so if i need to do that its okay, but i was wondering if this is something that happens when you flash new ROMs and if there is something i should have done differently through the process to avoid this and if there is anything i can do to fix it now. Thanks.
What could be the reason for this behaviour? It's got to be a hardware thing, but could it be fixed by me somehow - or should I just give in and send it in to a repairsman?
FYI, I bought this phone used, and even its' previous owner complained about this problem. This didn't bother me at first, as SD card prices were high back then, but storage now is cheap as ****! I'm kinda angry now, actually.
I did try with a variety of SD cards, and I also did try formatting them - but not a single one worked.
Well
1) If you are on Sony's stock ROM - try Cyanogenmod 13 (or even 14). See if it boots when you are on these roms.
2) If you are on custom ROM then probably custom ROM is the reason - flash another custom ROM. Or even stock to see if it works.
3) If the two above failed then the reason is hardware related.
4) It is most likely because of your nickname @stuckbootloader
Option58 said:
Well
1) If you are on Sony's stock ROM - try Cyanogenmod 13 (or even 14). See if it boots when you are on these roms.
2) If you are on custom ROM then probably custom ROM is the reason - flash another custom ROM. Or even stock to see if it works.
3) If the two above failed then the reason is hardware related.
4) It is most likely because of your nickname @stuckbootloader
Click to expand...
Click to collapse
I've already tried the first two - I'm more or less aware that it's a hardware problem; I was asking whether this could be fixed by me or not.