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.
Related
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.
Hello,
I'm a new owner of a phone with android, since a month ago. The problem with my phone is that some time ago it started rebooting about 2 times per day (in some cases rebooting even I'm not touching it)
I tried removing almost all applications and didn't work (the first app was task killer since I read that's not needed).
One thing that may be helping the phone rebooting itself is that some times I see this notification: "SD card removed unexpectedly".
I have a 8gb class 2 card. But I tried with a 4gb class 4 card and same message appear. I tried formating both cards and didn't work.
Anyone can please help?
Best regards,
Pedro
and my P500 do a restart the card SD (2GB, which was from the market) and probably due to the firmware of the LG (it has a .10 b) so I expect the update from LG that fixes the problem
Sent from my LG-P500 using Tapatalk
thousands of us are facing this problem. LG are idiots to have released the phone with such a glaring defect.
But also thousands of us doesn't have any problems with this. It's really strange and you can not say, that LG is idiots - maybe everything works before on testing. Maybe some factory failed in collecting, maybe some wrong series of components... maybe.... who knows.
One think is true - they should face up to problems and not do, that nothing happened.
So the only thing that I can do, is wait for an software update from LG? (perhaps android 2.3 resolve it?)
pedroh said:
So the only thing that I can do, is wait for an software update from LG? (perhaps android 2.3 resolve it?)
Click to expand...
Click to collapse
I doubt whether this is related to software, since other phones don't face this issue. The phone has crashed several times at the end of a call, and I couldn't even press the disconnect button. When the phone doesn't even be stable and do the basic phone features properly, nothing else matters.
I also had this problem.
SanDisk 8GB cl2: reboot 2-3 times daily. Best 1% / hour battery.
SanDisk 2GB cl2: remount frequently. 1% / hour battery.
Original card that came 2GB(Samsung?):NO reboot,NO remount, 2% / 8 hours (night) battery!!!
My sd card didn't remove but the device some times start a reboot, and after a few seconds it enter on the phone (after the text ANDROID when i can see the desktop), when the phone signs he's mounting the sd, the phone goes on reset again and do this for several times, and i can't acess to the device. Some times he works normally.
I tryied to start the device without the sd but when he resets he still reset even without sd, so i don't think this isn't a sd question.
Some one else have this problem?
I update to the v10b by lg suite yesterday. I dont have the random reboot problem anymore for the last 24 hr. and I play pocket legend and like ever 2 hours the phone must reboot with the v10a. Now I am very happy with the v10b. no reboot for the game playing but i felt the graphic is little bit slower than v10a. and I am also factory reset my phone after update. So I can tell is it because the firmware or some software on the card or the root causing the reboot. But I am sure I am a happy pocket legends player. I am also using my old nokia 8g class 4 sd card with the original sd back up.
After I update to v10n, I've been runing android whitout rebooting and unmounting for about 125 hours (and growing).
I can say the software solved the problem because im using same card and I didn't factory either the phone or card.
My software version is already v10b by default but I'm still experiencing this "sd card removed" problem plus my phone also reboots it self rarely...
I've read threads about this problem and they recommend updating the software to v10e...
I contacted LG about this: It seems that the reboot bug is SIM-card related. Here in germany, Eplus (and their retailers) SIM-cards seem to be affected.
hi after updating to 2.2.1 v10n i dont have sd card error and reboots that often but sometimes i cant see the apps installed on the sd card. has anyone noticed this too? after remounting the sd card i can again see the apps and can access them but it keeps on appearing and its quite annoying! plz help!
i have both problems rebooting sd card and disappearing apps
i also have v10n
muff99 said:
I contacted LG about this: It seems that the reboot bug is SIM-card related.
Click to expand...
Click to collapse
Based on my experience, I'd say the reboot is triggered by the unexpected sd card removal after moving apps to the sd card. Until I've seen some working prove, I'd assume the idea with SIM-cards is just another theory.
xtho said:
Based on my experience, I'd say the reboot is triggered by the unexpected sd card removal after moving apps to the sd card. Until I've seen some working prove, I'd assume the idea with SIM-cards is just another theory.
Click to expand...
Click to collapse
I have the phone from late october and experimented a lot with this problem.
In my case it only happen if I move some apps on the sdcard, if I don't move any apps on the sd card, no reboot happens. Also it seem more frequent when data connection is not "stable".
Some user reported they were able to turn around the problem keeping wifi on all the time, but it is a solution I like
In the last couple of months I used the phone with all the apps on phone memory and never had the problem again...
I got this phone a week ago and it's been rebooting ever since.. I even updated to v10f and now it says something about the SD Card after reboot and the SD card wont work after that.. so I have to reboot manually for the SD card to become active again... this phone is nothing but headache... but I'm still happy with it..
Do custom ROM's also reboot randomly?
you need atleast a class 4 sd card, im using class 4 16 gb sandisk. Absolutely no problems at all.
ccdreadcc said:
you need atleast a class 4 sd card, im using class 4 16 gb sandisk. Absolutely no problems at all.
Click to expand...
Click to collapse
Did u manage to get class 6??
nt available in most shops of mumbai.
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
A weird issue manifested on my phone today ... the phone started, upon boot up, to spontaneously reboot. It would boot up within 30s, at which point I unlock it an pulldown the notifications screen (to see what was going on).
I saw several instances of "media scanner running" occurring - over the course of various trials I would see the following messages alternate on the top status bar.
Media scanner running... (system storage)
Media scanner running... (SD card)
Media scanner running.... (USB storage)
Media scanning completed​
...while below in the notification areas I'd see the "Media scanning", "Media scanning...USB storage" etc messages periodically appear.
The phone would first lockup, then reboot perhaps 3 out of every 4 startups. Several of those times the last message I saw prior to the lockup was Media scanner running.... (USB storage).
I pulled out the 32FB Sandisk SD card, then tried booting the phone several times, and this time no issue - booted up fine, no lockups nor auto-reboots. Note though that I've had the SD card installed for over a week, and the problem only cropped up today.
There were two SD card-related changes I'd made last night: 1) used ES File Explorer to cut/paste ~400MB of video from the onboard camera storage to the SD card and 2) copied 1.75GB of MP3 files to the SD card.
The MP3s I had copied to /media/music (direct from laptop to SD, using a microSD-to-USB adapter), while the videos (MP4s, created by GS2 camera app) were moved by ES File Explorer to /DCIM/Camera.
So at the moment my phone is working fine (4 clean boots), though sans SD card - any ideas why "media scanner" may be choking upon scanning the SD card? Should I move the SD content to a different directory, or just kill media scanner?
I've seen issues like that but usually with no name low quality SD cards, with them either bad or modified to register as larger.
I'd backup what you have on the card and format it using the phone. If it's still giving you issues try it on a computer and download a program to check the memory sectors to make sure there are no read write errors.
A good free one is ariolic diskscanner. Can't remember if it can scan SD cards though, though I'd be a little surprised if it couldn't.
You don't want to disable media scanner, not even sure if that's possible. Many things require it to be working.
Sent from my SAMSUNG-SGH-I777 using XDA App
thanks for the tip - I mounted the SD on my PC and backed everything up, then tried deleting the ~2GB Media directory ... no dice, still locked/booted on the first boot up. Going to next clear the other large diretory (DCIM) and see what happends, and then finally reformat the card entirely. Will report back...
so i wiped and formatted the card in the phone ... rebooted several times with the newly empty card, and so far the lock/boot issue hasn't recurred.
Copying all files save the media stuff onto the card, will repeat the test; and then finally will put the media back and see how things go; will report back.
Good deal. Hope that's the last time it gives you trouble.
Sent from my SAMSUNG-SGH-I777 using XDA App
This is so weird. I've had this problem as of yesterday.
I'm having the exact same issue... but with a Galaxy S 4G.
I tried re-flashing my phone but I realized it was the SD card causing the problem because the internal phone storage scans just fine.
I've tried 2 different SD cards (one Samsung, one Kingston) - backed up my files on my Mac and tried formatting both cards, putting the files back on the SD cards and booted the phone.
Same problem was happening.
The phone boots up fine without the SD card but I am at loss what to do considering most of the apps I use need the SD card to run.
Try formatting them using the phone.
Could be a corrupted file on your SD card. If after the format the phone works fine, put the files back on one at a time and see if that's what's messing it up.
Try also changing the format type. Seems androids like fat32 a little better.
Sent from my SAMSUNG-SGH-I777 using XDA App
netarc said:
so i wiped and formatted the card in the phone ... rebooted several times with the newly empty card, and so far the lock/boot issue hasn't recurred.
Copying all files save the media stuff onto the card, will repeat the test; and then finally will put the media back and see how things go; will report back.
Click to expand...
Click to collapse
so far so good ... went a day w/o any spontaneous reboots, thought I do want to do a few more startup trials, but fwiw, formatting the SD card (in the phone) seems to have done the trick.
I do realize now that when I first inserted the card in the phone, I just started using it, I didn't bother formatting it - doh!
netarc said:
so far so good ... went a day w/o any spontaneous reboots, thought I do want to do a few more startup trials, but fwiw, formatting the SD card (in the phone) seems to have done the trick.
I do realize now that when I first inserted the card in the phone, I just started using it, I didn't bother formatting it - doh!
Click to expand...
Click to collapse
I have this same issue -- when my MiscroSD card is in, and it goes to media scan, the phone just keeps resetting... SO annoying
question: how do I format the external SD ?
Removed
Same problem on Samsung Galaxy Ace
I'm experiencing the exactly same problem on my rooted Samsung Galaxy Ace (Gingerbread 2.3.6).
Reboots with SD card mounted and working fine with SD card unmounted.
I'm using Link2SD with a 2nd ext2 partition, and when SD card is unmounted, all Linked apps work perfectly fine.
I've tried removing and re-inserting SD card and also recreating mount scripts to no use.
What might be the possible causes of this problem???:crying:
Please help :fingers-crossed:
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...