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!)
GTP100 Rooted I'm using Install Manager, Android Assistant, Quick application Manage and Root explorer to shift all my application from the phone to the SD card unfortunately I figured out that I have only 200 MB remaining in my phone memory ! Only 4 programs installed on there and the remaining on the SD card as it shows I start searching to figure out the problem using root explorer I found the root
Phone Memory/mnt/asec/secure/asec - 990 MB so I tried to move it to the SD card but once moved it will return back again to the same path!! Even if I tried to delete it will remain the same! also I found another root phone/mnt/asec -670 MB which has almost the same applications by all means using root explorer I cut& paste the first root to the SD card and reboot then only the installed programs in phone works and the other application icons disappeared I was shocked cause even trying to backup my mistake was a hectic work, by all means its again as it was and still facing the same problem any help
[Q] After upgrading to CM10 "emmc" changed to "extSdCard" and related problems
Hi,
I've recently updated my GNote (GT-7000) from CM9 to CM10, and looks like with CM10 the external sd card previously mouted as "emmc" has become "extSdCard".
Since then some of the apps (such as Apollo) have trouble seeing media files, others can't see the sd card at all, and when connecting to the desktop the drive which normally shows the content of the external sd card, only shows a couple of folders of it rather than the whole content as it used to do before (when using CM9 and previous roms I had).
Looked around for possible causes, but didn't find much. Someone mentioned that rommanager might have placed ".nomedia" files on the root of the internal or external sd card causing the problem, but that's not my case. Tried also doing a full wipe and reinstall of CM10, no joy.
Any idea?
Thanks!
- Adriano
That's the standard mount points for cm10 there are apps that will remount the sd and external sd in mnt as on stock roms. I had a quick look but couldn't find them, but I'm sure someone else will be able to find them.
Sent from my GT-N7000 using xda premium
clean install without restoring data of apps
Sent from my GT-N7000 using Tapatalk 2
Thank you for the suggestions -- I tried a clean install as well, but even the builtin apps (Apollo) still had troubles accessing the external sd card (not seeing any of the mp3s I had there). I have now resolved for restoring a CM9 backup I took before upgrading to 10... and everything is working as it used to.
Not sure why I ran into these issues which no one else seems having encountered so far.
- Adriano
I have the same problem except that the files on my internal sd card are not read by apollo player And the gallery. Is there any workaround. The problem started as soon as I upgraded from cm9 to cm10
Sent from my GT-N7000 using xda app-developers app
adri72 said:
Hi,
I've recently updated my GNote (GT-7000) from CM9 to CM10, and looks like with CM10 the external sd card previously mouted as "emmc" has become "extSdCard".
Since then some of the apps (such as Apollo) have trouble seeing media files, others can't see the sd card at all, and when connecting to the desktop the drive which normally shows the content of the external sd card, only shows a couple of folders of it rather than the whole content as it used to do before (when using CM9 and previous roms I had).
Looked around for possible causes, but didn't find much. Someone mentioned that rommanager might have placed ".nomedia" files on the root of the internal or external sd card causing the problem, but that's not my case. Tried also doing a full wipe and reinstall of CM10, no joy.
Any idea?
Thanks!
- Adriano
Click to expand...
Click to collapse
Download ICS SD Binder. Check all 3 options and reboot. The path should be mnt/extSdCard (i think default is odb or so, make sure you change it) . It worked for me and so I'm trying to answer everyone with this problem. Give me feedback soon. And thanks button if I heped.
Quarmzz said:
Download ICS SD Binder. Check all 3 options and reboot. The path should be mnt/extSdCard (i think default is odb or so, make sure you change it) . It worked for me and so I'm trying to answer everyone with this problem. Give me feedback soon. And thanks button if I heped.
Click to expand...
Click to collapse
It didn't -- I don't need to have /emmc bound to /sdcard/external_sd as it was in GB. With CM9 everything for me works just fine with /emmc.
I tried the latest CM10 nightly, and using ICS SD Binder didn't change things. In the latest CM10 now there is also another mountpoint, called /storage/ and underneath sdcard0 and sdcard1 pointing to the internal and external storages respectively. In addition to /sdcard/ and extSDCard. Every few builds there seem to be some new change related to the storage's mount point. Going to wait another while before doing other attempts.
- Adriano
Any update on this question?
seems these are the new mount points even on the New JB roms from samsung
Somehow in some late November nightly, after flashing it, the files on my Internal SD were detected properly and it has all been working properly since. touchwood!
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
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