I've read upon the DAMAGED SD CARD problem with android, but most of the phone becomes virtually unusable, mine says it's damaged but market works, and I can install apps to phone memory, even with APPS2SD enabled. If I try and copy my files to the computer, it stops halfway with 'perimeter incorrect', glad I did a backup like 1 week ago. Funny thing is, in recovery the SD card is fine, I can make backups, I even tried to repair SD Ext Partition, no luck.
Its probably Android thinking it's damaged without it really being so. Totally confused since I warning/error is on the ongoing notification. Also when I go into the SD card & phone storage shows information as unavailable and SD information widgets can't read it either. I don't mind formatting and copying everything over, but it kinda works, but android thinks it's corrupted or something. Very weird. Also I did nothing out of the ordinary, but with computers or machines random errors can occur. I had the partition in place for a 3 weeks now, installed MCR 3.1 couple of weeks ago and using it pretty much like this, but since the WIFI hanged (kept saying it's turning off but being stuck) I rebooted and the message came up.
Is it possible to fix it how it is? Or shall I just re-format and copy everything again. I'm just worried it may happen again.
Related
Hi everyone,
First things first, sorry if this was covered somewhere else in the forums, I really didn't find this question anywhere so I "had" to post this.
I got my Samsung GT-I9003 4GB a month ago, and everything was working perfectly until 3 days ago. It starts showing an "Internal SD card unexpectedly removed" error whenever the phone goes standby, then it forces me to terminate processes one after another, and finally it shuts down. I hadn't done any kind of ROM flashing nor rooting the device until the problems arose, so I don't know where the problem comes from.
I've tried to re-flash froyo 2.2.1 in my device, but the problem keeps showing up.
I found in this forums this thread (http://forum.xda-developers.com/showthread.php?t=1088474) covering the possibility of swapping both internal memory and external SD. It works great, but I still had problems with the "external SD card" being "unexpectedly removed"...
It crossed my mind if it was possible to modify the vold.fstab file further to only detect the external SD card as the internal memory and ignore the internal memory, as if it wasn't even on the phone. I don't know if that's even possible (since I don't know much about file systems nor Android), but I'd appreciate your thoughts on the matter.
same issue
eikur said:
Hi everyone,
First things first, sorry if this was covered somewhere else in the forums, I really didn't find this question anywhere so I "had" to post this.
I got my Samsung GT-I9003 4GB a month ago, and everything was working perfectly until 3 days ago. It starts showing an "Internal SD card unexpectedly removed" error whenever the phone goes standby, then it forces me to terminate processes one after another, and finally it shuts down. I hadn't done any kind of ROM flashing nor rooting the device until the problems arose, so I don't know where the problem comes from.
I've tried to re-flash froyo 2.2.1 in my device, but the problem keeps showing up.
I found in this forums this thread (http://forum.xda-developers.com/showthread.php?t=1088474) covering the possibility of swapping both internal memory and external SD. It works great, but I still had problems with the "external SD card" being "unexpectedly removed"...
It crossed my mind if it was possible to modify the vold.fstab file further to only detect the external SD card as the internal memory and ignore the internal memory, as if it wasn't even on the phone. I don't know if that's even possible (since I don't know much about file systems nor Android), but I'd appreciate your thoughts on the matter.
Click to expand...
Click to collapse
Was having the exact same problem with a further twist, the issue occured almost every half an hour at office and very rarely at home. Tried a factory reset and also GB update via Kies. Problem was still present, so have given it to samsung service and the service rep informed me that it was most likely a motherboard issue.
Recently one of my friends had the same issue. Samsung service center replaced the motheboard and the issue seems to be resolved.
Check this out to recover from a broken (but not fully broken) internal sd card ->http://forum.xda-developers.com/showthread.php?p=30195720
Awesome newb video by the way! Made me laugh...
Just rooted and I like it, I don't wanna go back, but I can't get the microsd to pick up...I'll give all the info I can--def newb to root/droid but my background is IT, so hopefully we can figure out how to fix it so I can keep the root and not go back to stock(if that would even repair the problem)
Got a pny 32G microSD, droid incredible 4g lte(Verizon) that I rooted using the unlock script and fakeCID and then loaded Vipers Venom LTE custom rom...somewhere in this process-I think right after unlocking-it quit accessing the sd card...I've looked around and read some things about this 'USB brick' thing, but I don't know if it's applicable to me...here's what it does now:
SD card is in phone, but under 'Storage' Total Space and Available show unavailable, and everything else is greyed. If I try and pull the card the phone gives me the 'sd card unexpectedly removed' error.
Windows XP has no issue reading/writing to this card with a card reader. I've formatted a few times fat32 with xp(which i hate doing)and put it back in the phone, with the phone off, booted, and nothing happens. Oddly, when it first happened, after installing the custom ROM, when I'd do this procedure the phone would see the card on boot, but stay forever on 'preparing sd card/checking for errors' and never complete.
Back on the phone side of things, booting into the 'recovery mode', where you flash and whatever, it can see the card, see it's contents, and I wrote some sort of log to the card(option in the menu), so it can access it...oddly, I could not load my Viper rom from the microsd card, it failed on the file, but put it under some folder on the phone and that's how i ended up flashing the ROM, which I was nervous about doing as everything I saw said put the rom on the external sd card...
If I plug the phone into the XP pc via usb cable, choose use as disk drive, no problem accessing phone data, but 'please insert disk' on the card. Cannot push data when in usb debug mode via adb commands either. Oddly, dunno if this is related, it gives me 2 drives and also a CD ROM drive--tried dialing that##7 number for the option to disable cd rom, but it was already disabled. Dunno if this is related, but throwing it in there.
Tried chkdsk on the sd card with Xp, no errors, no problems. Hell, the card's not two weeks old and I've only had the phone a little over a month. I've done a bit of research the past couple of days and the only thing I haven't tried is the very confusing procedure i've seen for some of these 'usb brick' problems, but is that my problem. I'm hoping if all else fails i can go back to stock, just downloaded the stock rom, but will that even fix it? Gots to have my trailer park boys on my sd card to watch! Thanks for the help guys and gals! Sorry for the long post, but I like to give info--if kernel version or any other data like that is required, I can post it.
zazaray said:
Got a pny 32G microSD, droid incredible 4g lte(Verizon) [...] it quit accessing the sd card...
SD card is in phone, but under 'Storage' Total Space and Available show unavailable, and everything else is greyed. If I try and pull the card the phone gives me the 'sd card unexpectedly removed' error.
Windows XP has no issue reading/writing to this card [...] formatted a few times fat32 [...] and nothing happens. Oddly, when it first happened, after installing the custom ROM, when I'd do this procedure the phone would see the card on boot, but stay forever on 'preparing sd card/checking for errors' and never complete.
[...] booting into the 'recovery mode', where you flash and whatever, it can see the card, see it's contents [...]
Click to expand...
Click to collapse
i tried to slim down your quote, but from my experience i'd still say the sd-card is somehow busted! i had a similar prob with the SD card in my Dinc4G two weeks ago. i _was_ r/w quite fine even from custom rom and at one point, the card just quit. removing and reinserting just ended in "preparing sd-card" and directly after that "safe for removal" ... wasn't able to access it any more within Viper, recovery (TWRP for me) was still seeing the card fine just like on your end.
putting the SD-card into a Win-laptop it _appeared_ fine and came error-free with scandisk etc ... BUT when i tried to backup all data from it before formatting (had like 10G on my 16G card) there were a couple of files that failed to read and i could NOT recover at all anymore. I formatted the SD-card again after that (full format, not fast/quick!) ... and put most of the files back. it is working again now in my Dinc4G but the card sure has some defect sectors (and usually _tends to die soon_ after such errors appear first!
i'd heavily recommend that you try to source some other micro-sd card first and try if you custom rom can read from it again. if that works fine and you see your SD-card from within the settings menu in the rom. you can be pretty sure that it's really the card.
PS: even brand new mem cards tend to fail at times :cyclops: ... just try to erase all private data on it (means: _fully overwrite_ with other stuff until the card is completelly filled) ... and then try to get a replacement from where you got your (fairly new) SD card from.
hope that helps a bit
i agree with the above post... try a different card. if formatting it doesn't fix it, it's time to try a new card.
j13smiley said:
i agree with the above post... try a different card. if formatting it doesn't fix it, it's time to try a new card.
Click to expand...
Click to collapse
Thank you for the help, I resolved this issue, as it is the card, but now I have a different issue, unfortunately...
Hi,
I have Galaxy S3 running CM10.1 Siyah Kernel (problem has occured over several months of various CM10.1 nightlies) and I just cannot figure out why the following is happening. Please read the thread carefully because I've ensured that every sentence contains details which should be important clues to the root of the problem.
Sometimes following reboot, the phone completely refuses to read my memory card. In this state, the phone does not give me the Unmount option, but when I remove the memory card directly then it does show the 'Removed SD card in the' notification. Now if I insert it again, it shows 'Preparing SD card' in the notification and this notification doesnt go away by itself (which it should if the mount is successful) and the card does not mount. This situation does not change no matter how many times I repeat the process. After several attempts, I get the ongoing 'Damaged SD Card' notification. Dozens of reboots dont help either.
After loads of trial-and-error's, I have concluded that almost everytime that this issue has occurred was when the memory card was in-use (playing songs etc. Accessing anything off the memory card basically), although on rare occasions it has also occurred when no apps were in use at all. This gets me to believe that the software is failing to properly release some kind of lock on the memory card before rebooting.
Now the only way to get the memory card working again on the cellphone is to put it in my laptop memory card reader, and it can instantly read the memory card. Now if I safely remove the memory card from my laptop and insert it in the S3, then it always mounts on the first go. Now it will work perfectly again, until some completely random time (usually at least 1 week away) when it will start its problem again.
Also note that whenever this problem occurs, Developer Options does not load and crashes.
I want to reiterate that this is not repeatable each time. Even if the conditions are exactly the same (well, as far as I can see as an end user anyway), the problem will very likely just occur in just 1 out of the 50 attempts.
I have already got the memorycard+sim card slot replaced from samsung under warranty. I have also paid extra to buy the SanDisk memory card from SanDisk themselves based in the Czech Republic - so it is extremely unlikely that it is hardware fault.
Can anyone shed some light on this situation? Feel free to ask for any clarifications, I have tried to put as much information as possible.
Thanks
Make a nandroid, flash a stock rom and test again. Format the card using sd formatting tool first.
If that cures it then ask your kernel or rom chef for help.
So i have been having this problem for a few months now, and its driving me crazy.. I've read every thread on XDA about sdcards, but nothing seems to apply here
When I reboot, my phone launches External2Internal so my 32GB SD can be used as my internal drive, and I've used it fine for a very long time.. but recently the sd card just disappears after some period of time. it seems to happen whenever my phone goes to sleep or the screen goes off and is locked, i suppose
after I reboot the phone it works fine again..
I quite think its from a malicious program.. but I cant be sure
recently, I installed a bunch of sd card tools to rescan, remount, test etc.. and I also installed an External2Internal update... and after all that, the sdcard contents appear to have been deleted, even after multiple reboots, when viewed with ES File Explorer.. However all the contents appear in good condition when viewed with Total Commander.. .
and since all that tinkering, because the sd card seems on some level to be deleted, programs like avast are getting corrupted errors on their virus scans, such as "invalid context during scan".. an error it doesnt get when the sdcard is unmounted completely, but only now that it mounts as appearing mostly empty to es file explorer and probably most other programs.
so it seems like one of the USB tools or the External2Internal update has done something malicious to my card... or maybe it was a last ditch effort by some dorks malicious code from a program i deleted in trying to get this all sorted out
anyone else having this problem or know how it can be fixed?
and I prefer to try and find out what is causing the problem and fix that problem, rather than just reformatting the card or buying a new card, since i'm sure it will just happen again someday
thanks
-
This happens to me as well, the only difference is that I don't use External2Internal but the jellybean option "default write disk: SD card"
I have a samnsung S5 Plus with Lineage built nightly, the phone restarts quite often, (it could be a problem with the touch, or heating ?). That is why I don't keep the back cover on so I can remove the battery when it gets in that crazy loop and I did that often. (I'm using this phone only at home, so the battery doesnt really fall unexpectedly)
This time I was browsing the internet and tried to post an ad with captha, the phone got quite hot, and I turned it off. Its possible that I removed the battery before it went completely off, and that could be an issue if Android was writing something to disk. But I'm using the card as external storage (no apps installed on it) and I dont understand if the system was writing anything to disk exactly at that moment. Or if there could be any other problem?
When I turned my phone on the microSD card (1 year old, barely used) is not recognized ("the disk inserted was not readable by this computer), both my phone and my macbook ask to format or initialize it.
I don't know what data I lost, and dont know if any data could be recovered, but I'd like to know what you think.
You could recover it but it would be very hard to. I think the SD card is corrupted
I tried data recovery software but no file found, I dont know if I should insist to try other software.
I don't remember if I had important files, there were 15GB, but a lot of backups and install files.
Now I trie dto see if I can format the card but thats no longer an option
"Unable to write to the last block of the device"
I even tried to use some tricks to write zeros first and then to format but that does not work.
Its the first memory that I ever break. And it was new. I dont know if its my fault or its manufacturer's fault...