Hi
I've had this problem a couple of times, but never like this.
The sd stopped working and said damaged, happened before, the PC can read it, did a backup and formated, it had to be exFAT or it said it was damaged.
That did the trick last time, but now it doesnt allow me to write in the card, I can read everything on it, but when I try to rename something or delete it doesnt do a thing, it didnt work on es file or the file browser that came with the tablet.
The sd works fine on PC.
It has the latest update and original rom, havent even root it
Anyone knows?
Mine stopped also now and then. After upgrade to android 6 this problem is over but android 6 apps can not all write to sd card.
I have 6.0.1 and had no problems for a while, then this started, now it sometimes also stops while copying files from my pc to the tablet
Related
It happened yesterday when I upgraded to xrom. I have formatted and repartitioned my sd card. Nothing is working. When I connect my sd card to my computer I noticed a lot of weird files were being stored on it. They reappear every time I delete them.
My phone is creating files like this "qxdm_20090910_184004_3.dm" (32 megs!)
hmm....very interesting... reboot into recovery and repair the ext files? it might work. most likely not, but its worth a shot.
I though about trying that but I don't have cyanogens recovery .
Mine just did the "sd card has been removed" thing half an hour ago.
I just copied a new theme .zip to my sdcard and then rebooted into recovery.
I could not apply the update since it could not mount the mmcblk0p1 partition. When boot all the way up to android i get the icon saying that the sdcard has been removed.
i just did an adb push of a file to my /sdcard from the recovery console and it returned no errors...but i cannot see any files on the card.
wtf.
Any ideas?
Yeah my problems still not fixed. I have searched the XDA, forums, Google, none have offered any solution. I have found a lot of people with this same problem.
are you using swapper? if you dont turn it off, this could happen.
i would recommend getting cyans recovery image, it has a lot of tools to debug.
get a live cd of linux/gparted and see if you can see all your partitions. if not, your sd card is most likely dead. try reformatting. if that doesnt help, you may need to get a new card.
if it does show up on your pc, but doesnt work on your phone, then post here again
Have the same problem. Got it right after updating cyanogenmod 4.1.2 I've also been looking for answers and I think I'm just gonna get a new one
I have never used swap. I tried installing cyans recovery image through terminal but it can't find my sd card. I can still update my rom through jfs utility. My sd card works perfectly fine on my computer.
Something like this happened to me a while ago. It first said Sdcard was damaged and i couldnt access it via any file manager. I rebooted and turned out all my apps went up in the air and dissapeared and my fat32 partition was gone to. i reccomend backing up your sdcard and reformatting your card then go froom there
I have already tried all that. Nothing so far has worked :-(. Man this is horrible. I can't even take pictures!
Hi all,
I have a problem with my G1, running on latest Cyanogen mod. After restarting the card cannot be read and it is seems to be checking the sd card, if it really happens I dunno. What is weird is that I can access the card from recovery mode (shell), and it is not damaged (at least the windows doesn't detect damage while it is in the card reader. So that implies that the problem might be in the Android system.. anybody has a clue how to solve this? Thanks a lot.
Edit: solved it, deleted fsck_msdos from bin and it works flawlessly again
Can always wipe and reflash. Or if you have another sd card laying around and put that in to see if it recognizes it.
I'm having the same problem How did you delete the fsck_msdos from the bin?
theinstagator said:
I'm having the same problem How did you delete the fsck_msdos from the bin?
Click to expand...
Click to collapse
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
I was having this same issue..it would typically take up to 5 minutes or more to "check for errors" after a boot.
To fix this I backed up my sdcard, reformatted, copied everything back, then reflashed. Everything was fine after that.
i have somewhat the same problem but in my case it sometimes say blank sdcard or damged sd card it read fine when plugged into an sd card reader any help
Thanks. It worked by simply deleting fsck-msdos but it keeps giving SwiftKey3 error " unable to load language packs". Keyboard still OK. I have xperia x10 mini rooted running android 2.1 E10i.
hmaxos said:
Thanks. It worked by simply deleting fsck-msdos but it keeps giving SwiftKey3 error " unable to load language packs". Keyboard still OK. I have xperia x10 mini rooted running android 2.1 E10i.
Click to expand...
Click to collapse
Well, after getting other errors such as "no enough space" from Platinum Backup (there was a space on SD Card), I had to go to Format the SD after copying everything. Then I copied back the important folder the SD. I also had to reinstall SwiftKey. Now everything is fine and no data loss.
SD card Checking for errors
sajjji said:
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
Click to expand...
Click to collapse
Well I will try to backup and format it.... If it works then good if not then I will have to root my LG P880 .
My Problem is "preparing external sd card checking for errors" now that error is not showing while following above steps but now when i click my memory card that is not opening and after opened my memory card my internal device memory also not opening .
baka.yarou said:
Hi all,
I have a problem with my G1, running on latest Cyanogen mod. After restarting the card cannot be read and it is seems to be checking the sd card, if it really happens I dunno. What is weird is that I can access the card from recovery mode (shell), and it is not damaged (at least the windows doesn't detect damage while it is in the card reader. So that implies that the problem might be in the Android system.. anybody has a clue how to solve this? Thanks a lot.
Edit: solved it, deleted fsck_msdos from bin and it works flawlessly again
Click to expand...
Click to collapse
Simple fix, Difficult decision. Remove SD Card from slot then Factory reset phone. Once it comes too just go through all steps to setting up device then reinsert the SD Card into the slot. BOOM!
thank you very very much it worked for me
baka.yarou said:
Hi all,
I have a problem with my G1, running on latest Cyanogen mod. After restarting the card cannot be read and it is seems to be checking the sd card, if it really happens I dunno. What is weird is that I can access the card from recovery mode (shell), and it is not damaged (at least the windows doesn't detect damage while it is in the card reader. So that implies that the problem might be in the Android system.. anybody has a clue how to solve this? Thanks a lot.
Edit: solved it, deleted fsck_msdos from bin and it works flawlessly again
Click to expand...
Click to collapse
thank you so much but it is read only please help
yeah...
supremeteam256 said:
Can always wipe and reflash. Or if you have another sd card laying around and put that in to see if it recognizes it.
Click to expand...
Click to collapse
i am having same issue i always changes roms please can you halp me..
still not working mine is lenovo K3 Note And my Phone is rooted. It is showing Preparing SD card checking for errors
Didn't work for me.
Hard reset don't work.
Delete the fsck.msdos but don't work.
The fsck.msdos file comes on every wipe back.
I think this is a cm issue.
On stock no problems with my external sd card on my HTC One M8.
I'm going crazy...
No need to go to bin.. just put ur SD card in other mobile.. it will show fcsk files when u open the SD card.. just delete those files. Then remove the SD card and put it back in Ur mobile.. Then restart it mobile.. problem solved..,,,
Anitha Sivakumar said:
No need to go to bin.. just put ur SD card in other mobile.. it will show fcsk files when u open the SD card.. just delete those files. Then remove the SD card and put it back in Ur mobile.. Then restart it mobile.. problem solved..,,,
Click to expand...
Click to collapse
ive deleted the fcsk file on bin
the notif "preparing sd card" was gone but another problem occured, i cant even open my storage, ext sd card and even internal card ive tried your solution, ive put my sd card on another device, i cant find any fcsk files that you mention i cant even delete any file from my card using another mobile :crying::crying::crying:
It worked.... Thanks bro..
:good:
sajjji said:
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
Click to expand...
Click to collapse
sajjji said:
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
Click to expand...
Click to collapse
Bloody Brilliant. I have no idea why I could not find this solution two years ago. I have spent several hours searching for this solution, several times. In my case, I needed to remove the fsck.exfat file in the /system/bin folder.
My attention span is extremely short. I have been living with a 3 to 4-minute card scan for a 256GB microSD in my Samsung Note 3 for two and a half years. For all of the reboots I have done (which must be near a thousand, if that's not severely underestimated) I have had to deal with waiting to use my phone. I can't tell you how discouraging it has been to have such a powerful, useful device crippled by such a stupid flaw: that of checking the SD card that you rarely remove, for errors, every single time the phone is rebooted, even after graceful reboots called by the "proper" methods.
I can't tell you how many times I have rebooted my phone, only to forget the reason I rebooted it, because my phone took 4 minutes to reboot.
Productivity to the cubed-root.​Pisses me off.
Someone who has more voice than me please get the Android People to change this. As of Nougat, this is still the default behavior. How can an organization be so stupid...? I have no doubt that just this flaw has sent many people to the Apple camps. Who the cuff in their right mind would want to deal with such a hassle?? Are they seriously unaware of the trend for people to actually believe that their devices, machines and technology ought to be doing things faster than previous generations?
(Please just take the following cynicism with a grain of salt. I just learned the above fix, something I really should have figured out a long time ago/kicking myself!!) :crying:
For the anally-inverted who might bring up the obvious argument that your phone will no longer be able to detect or fix corruption, all that needs to be done is the following:
1) move the fsck.exfat (or whatever the formatting) file to a different folder. In my case I moved it to the /data folder
2) use some delay scripting program that will symlink the fsck.exfat file to a tmpfs location say, 30 seconds after boot; or longer if needed. This intermediary step is necessary in order to create a temporary symlink, which will be nonexistent upon reboot.. If we didn't create a temporary symlink, the fsck.exfat command would be immediately available after each reboot (which we don't want) because symlinks are normally permanent. Therefore, this step will need to be run after every reboot (but again, time-delayed).
3) the last command is to create another symlink, linking the tmpfs fsck.exfat symlink created in the last step back to the /system/bin folder (or wherever it originally resided). So this is a symlink of another symlink. This step actually should only need to be done once, since this symlink should remain after reboot, even though it is initially broken upon reboot until the previous command recreates the intermediary symlink. It should become effective again when the previous step is run by the time-delayed scripting program.
Now your phone has the ability to check the card upon you calling the fsck.exfat routine through normal means, one of which can just be a simple unmount -> mount request from the Android system settings . Your card won't be needlessly fsck-checked to death every bloody time you reboot your phone.
(If you found this tutorial helpful and desire to quote or improve upon it, please cite/credit me for the inspiration! It came through much effort and learning!)
Hello.
This is my first post.
I have seen the noob video, I know I am not special. And still:
I have searched the forums, but my problem is different. Most of the posters don't know what caused this error. I know what caused mine. I have actually unexpectedly removed the SD Card. Kind of. Funny story: transferring data (green bar on windows not loaded at all, window stuck on calculating time/finding files etc -technically no data has been transferred), windows explorer decides to go all "Not responding" on me (thank you microsoft). The genius in me tells me to unplug the phone, so I do. Yay! explorer.exe is ok now. Too bad my SD card isn't.
There are some files on it... but none of the folders that I created, so I lost everything except photos and stuff. I have backed them up on my PC. When I connect my phone (which I have to do manually by going into USB settings so that my PC recognizes anything -auto play doesn't appear anymore-), instead of showing up as my phone, it shows up as a media device with stuff on it (folders like Android, DCIM, but none of my manually created folders containing music etc.).
I repeat, I have actually unexpectedly removed my SD card.
I right clicked on the drive in the PC and clicked Format. It warned me. I didn't care, I was desperate. In just one second, it said formatting complete. No files missing, however (still those Android, DCIM etc. folders).
I have a Samsung Galaxy S Advance GT-I9070 (this forum section, I think). I have flashed the I9070XXLQ4 (android 4.1.2) from Russia on it (a few weeks ago). Not root, or any custom ROM's.
Recap. I have unexpectedly removed my SD card. I want my games back. Or at least formatting it, making it usable.
Formatting the SD card from the phone settings has done it. I am a noob.
try formatting the sdcard on your phone thru the settings>storage..
re-download all your games or transfer them on the sdcard after the format.. if you have back up on your pc or other storage..
as for your pc.. try a reboot.. to correct the drivers of your phone as storage device..
jaycm1130 said:
try formatting the sdcard on your phone thru the settings>storage..
re-download all your games or transfer them on the sdcard after the format.. if you have back up on your pc or other storage..
as for your pc.. try a reboot.. to correct the drivers of your phone as storage device..
Click to expand...
Click to collapse
Thanks, I've managed to do that before you posted (but I'm a noob and I can't edit posts so quickly). It did it. Although I was hoping not to lose everything.
vici30 said:
Thanks, I've managed to do that before you posted (but I'm a noob and I can't edit posts so quickly). It did it. Although I was hoping not to lose everything.
Click to expand...
Click to collapse
is your sdcard a genuine one?.. no offense.. but there are a lot of fake sdcards in the market today..
actually i have a fake one.. its 8gb.. now, half of it is corrupted already.. my tablet hung due to it..
Hi guys.
I hope it's not the wrong thing to revive this old thread.
I was recently installing an RUU onto my phone. After the install completed, the phone restarted and it began checking the SD card again for an RUU - and it found one, as I had not by then removed/renamed it. So, after waiting for it to verify the RUU, selecting "no" to installing it, it restarted again and again it started looking for an RUU. By this time, I was getting impatient, so I tried to remove the SD card quickly before any actual data access happened.
WRONG
My SD card became RAW, inaccessible to Android or Windows. Testdisk and various free versions of paid-for undelete tools (like EaseUS) found only files from waaaaay back, before I had ever used the card in Android. As a precaution, I took two RAW copies of the full card onto two harddisks and compared the MD5 of each (match).
A little wary of the risk of using various features of testdisk, I thought the best thing to do next was a format (not quick format) to exFAT in windows and run all the undelete tools again. No results. Then I found this thread and, as suggested, tried formatting using Android. All software returned no results again.
What else can I do? The contents of the card should still be as they were (unless the formatting twice effected that). Am I correct to assume that the card (128gb) would have been formatted exFAT by Android 5/6?
In testdisk, are "superblock" or "boot" forms of recovery any relevance to me?
Thank you!
(PS: Android is working fine, I'm only having problems with the SD card contents)
Please forgive me if this has been posted, my searches have not turned up anything helpful...
I am having an issue with my external SD card since root, I can not write to it or format it. I have tried various different apps on my windows and mac machines to try and format it. It keeps saying that its "write protected". Its a 64 gig PNY card that is only about 2 months old. In a fit of rage and frustration I ran down to the local walmart and picked up an 8 gig card, formatted it in the phone, it worked for about 20 minutes and has now done the same thing. I have even tried doing a factory restore on my phone to no avail. I can read the files from the windows computer and copy them OFF the SD card, but it will not allow me to delete any nor format it. In my phone it shows there is no files on the card, yet shows 15 gigs are being used. Any help would be greatly appreciated. Again sorry if this has been posted before.
Thanks from a long time lurker
Don't tell me root alone broke your sdcard.
Try this guide, and choose one of the steps with the factory reset.
http://forum.xda-developers.com/showthread.php?t=2785185
Please dont get me wrong, I dont think root had anything to do with it. I am not sure what it was. After root I noticed my phone being really laggy (which I now know was the whole xposed s-health ordeal), and assumed that may have played a role in my issue. Since a factory restore though everything else has been great, except for the sd card seems to be write protected somehow.
DieselPhreak said:
Please dont get me wrong, I dont think root had anything to do with it. I am not sure what it was. After root I noticed my phone being really laggy (which I now know was the whole xposed s-health ordeal), and assumed that may have played a role in my issue. Since a factory restore though everything else has been great, except for the sd card seems to be write protected somehow.
Click to expand...
Click to collapse
I was waiting for you to say something about xposed, since that seems to be the most common factor in all of the issues after root.
I have a really strange problem that started all of a sudden today.
When I used UMS to transfer stuff into my 8GB Sandisk micro SD everything was fine but when I unmounted and tried to access the card using the Documents file manager that comes in AOSP the app kept crashing. "Unfortunately, Documents has stopped working"
I tried all kinds of things like formatting the card with exFAT but it is still persisting. Sometimes the SD card wouldnt mount.
I tried the "Scan Fix" that comes when you plug it in a windows 7 pc but now even that option won't show up as sometimes the card just doesnt get mounted. Sometimes it did but sometimes it didnt
So i thought maybe that was the end of my card's life so I tried another SD card (1 GB) but the same thing is happening. It is mounting fine with UMS and i can copy stuff into / from it but the Documents app is still crashing. Have tested the same with two different ROMs and it crashes on both
I don't understand what the problem is. Surely both cards havent gone bad because the 2nd one works with another phone I have. I will have to check the 8GB one as well.
Anyhow, would anyone have any idea what is going wrong or what might be a possible solution for this?
Help :crying:
Quick update.
I flashed back stock and the card seems to be working (both of them)
What the hell?
What could have happened?
Update. Its somehow fixed after I have installed stock and re-rooted and flashed custom ROM :good:
EDIT: THE PROBLEM SEEMS TO BE BACK WTF?
EDIT: Documents is crashing but ES file manager works