Related
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!)
I completed manual nooting and was restoring the apps from TI backup.
However, I wasn't able to restore Angry bird. I get "Unable to Install" error.
I could not install through the Amazon market either, it had same error.
All other apps are installing just fine all 3 flavors of angry birds won't install.
It isn't that crucial, but it would be good if I can get this working.
Thanks.
This might help
Potential fix for Angry Bird install after manual nooter
A lot of people are saying that you can't install angry birds with the SD card installed. This sounds like the problem that I had with my Droid X. To fix it I had to delete the file left from the prior install under .android secure on the SD card. I guess that Froyo sometimes has issues with this file getting corrupt on the micro SD and then it can't install correctly during updates and reinstalls. I think you lose all previous data but at least you have it working normally now with the SD card installed. I'll try it on my nook and post back. I would have put this in the manual nooter thread but I don't have enough posts to post there.
I formatted my sd card and it had no effect. I also tried several times with the card in and with it out and it still failed. What I ended up trying was using adb command line (adb install XXX/XXX.apk) and it worked perfectly. I now have Angry Birds 1.53 installed and working. I don't know why the app store can't install, but the command line method did work. Of course this will only work if you have adb setup on your computer correctly.
Note: I initially tried to do a copy and paste the apk to system/apps to install via astro file manager but the directory seems to be read only.
had the same issue - had to install it manually.. took my backed up copy and using adb
adb install "Angry Birds 1.5.2.apk"
not sure what the issue is... some people said it was the 4mb issue, but i was able to get some >4mb files installed no problem... hopefully one of the devs can figure out why.
Try to remove sd card, that was the only way I could install angry birds. I did pay for the one that B&N has. I have all installed now. Hope this helps.
The way I got them to install was to copy the apk file in the /data/app folder and then set permissions to rw-r--r-- then reboot
BN bug
To install angry birds, you need to get the apk on your nook and then install without an SD card in the slot. BN has acknowedged this is a problem in their FAQ. http://bookclubs.barnesandnoble.com...estions/m-p/979622/message-uid/979622#U979622
"Q4: When I try to install “Angry Birds”, I get an error. Help?
This issue is being investigated by our engineering team.
WORKAROUND: Please remove any microSD cards from your NOOK Color and try again. You can reinsert the card after installation has completed. "
This is how I got it to install:
1. go to settings, device info, unmount SD card
2. remove SD card
3. download the apk from my dropbox account and
4. install
The catch is that market requires an SD card to download
So, I just installed the 4.4.2 OTA and I immediately noticed one big problem: I wasn't able to modify content on my SD card. I wasn't able to delete folders, or create folders, or create files. Reading content was no problem, and the camera app was able to save pictures to the card, but going through a file manager wouldn't work.
I started to do some research and I found this post from the developer of my chosen file manager, FX:
https://plus.google.com/+TodLiebeck/posts/gjnmuaDM8sn
Then, while getting ready to post this, I found another related thread:
http://forum.xda-developers.com/showthread.php?t=2641936
I thought this was a big enough deal to warrant a new thread here. Bottom line is you may want to hold off on this update, or at least go in with your eyes open because for a lot of people, like me, this is a BIG problem. It's damned near a dealbreaker for using my S4 as a matter of fact. Note that it does seem you're able to use the My Files app, but that's almost useless to me: FX has SMB support and I'm constantly pulling files off my server. I even have FolderSync set up to run every night, but I don't expect that'll work either (I'm about to try now).
Whether Samsung spits out a fix quickly, or whether I can root and fix this, it's a pretty significant problem. Be aware folks!
Then I will update after a stable de-knoxed ROM is available.
Sent from my SPH-L720 using Tapatalk
Thanks.for this. I think I will still update as I plan on staying unrooted and will use "my files".
Sent from my SPH-L720 using Tapatalk
anees02 said:
Then I will update after a stable de-knoxed ROM is available.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I'm all for avoiding Knox, but in this case it appears to not be Knox-related after all... looks like it was a permission change that Google mandated for devices with external storage and Samsung followed the specification to the letter. I think Tod Liebeck explained it better than I can though. I can only hope Samsung gets it together and quickly releases a patch... I've read in another thread that they may have done this before and quickly put out a fix... if so, shame on them for making the same mistake twice, but so long as a fix is forthcoming, so be it. I'm not so sure there will be one though, that's my concern.
It's early to call that is the bug since nobody mentioned this issue.
And all are busy how to update.
I will wait 48 hours until all things be more clear.
Could you try another SD card and tell us if the issue is happening to the new sd card?
Sent from my SPH-L720 using Tapatalk
anees02 said:
It's early to call that is the bug since nobody mentioned this issue.
And all are busy how to update.
I will wait 48 hours until all things be more clear.
Could you try another SD card and tell us if the issue is happening to the new sd card?
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Thing is, it was something that was apparently talked about before the update on other devices with 4.4.2. It's not a bug per se, Samsung did what Google told them to do, and Google told them to do it, I'd bet, to push people towards cloud storage since they don't want external storage used anymore anyway. None of that matters though because the fact is it's hurting some users (though I'd agree that not all will be impacted- it all depends on how you use your device).
A different card wouldn't matter, it's not related to that at all. It's a permission change that Google mandated with 4.4 (or 4.3, I've seen some conflicting info) that only impacts devices with external storage, and Samsung chose to follow Google's specification exactly in this case, to the detriment of (some) users.
FYI, *IF* you're rooted, here's a solution that fixes this. Worked for me and easy to do:
http://forum.xda-developers.com/showthread.php?t=2524277
Just remember to keep a copy so you can quickly undo it to take an OTA since I assume it'll stop an OTA.
Soooo lemme get this straight... Lets say I update to KitKat (NAE)and root it, and I have apps on my computer (like Flappy Bird APK for instance), I now cannot copy the Flappy Bird APK onto my SD Card then place it (using a root explorer) in system/app and use it?! If so this is a huge deal-breaker... Or am I misunderstanding this and there's more to it?
thankfully you can still create on the SD card from a computer when plugged. but i can confirm you cannot create anything on the SD card from ES file explorer, you can still create on the internal storage just fine tho
Joe0113 said:
Soooo lemme get this straight... Lets say I update to KitKat (NAE)and root it, and I have apps on my computer (like Flappy Bird APK for instance), I now cannot copy the Flappy Bird APK onto my SD Card then place it (using a root explorer) in system/app and use it?! If so this is a huge deal-breaker... Or am I misunderstanding this and there's more to it?
Click to expand...
Click to collapse
You can still copy from your computer if you use a USB cable... if you instead have a shared drive on your PC and connect to it via SMB from a file explorer, you won't be able to copy a file to the SD card.
In addition, using a third-party file explorer you won't be able to create, rename, delete or edit files or directories on the SD card, nor will you be able to copy files from internal storage to your SD card. This is strictly a limitation placed on non-system apps (meaning any you yourself install).
If you're rooted though, a quick edit to a single system file will deal with this, but nobody should *have* to do that.
fzammetti said:
You can still copy from your computer if you use a USB cable... if you instead have a shared drive on your PC and connect to it via SMB from a file explorer, you won't be able to copy a file to the SD card.
In addition, using a third-party file explorer you won't be able to create, rename, delete or edit files or directories on the SD card, nor will you be able to copy files from internal storage to your SD card. This is strictly a limitation placed on non-system apps (meaning any you yourself install).
If you're rooted though, a quick edit to a single system file will deal with this, but nobody should *have* to do that.
Click to expand...
Click to collapse
That's ridiculous... what the hell Android/Samsung?!
Wow! Not trying to rub it in or anything but thank goodness I switched to the Nexus 5. What a nightmare. I hope Samsung fixes it soon for you guys
Sent from my Nexus 5 using Tapatalk
Thanks for this, lets go here for any further discussion...http://forum.xda-developers.com/showthread.php?t=2646762
I have Baseband G900AUCU2ANG3
Rom is 4.4.2
Build number KOT49H.G900AUCU2ANG3
It is a rooted SM-G900A with safestrap installed and working.
Heres my problem. I am having problems with writing to my External SD card. I used app2sd to move only the apps that are specified in the app manager as moovable, and had success.
But I used SDfix for correcting the r/w of the sd with limited success. Though most pics moved successfully, lately, when I move them, some "break". Also, I have around 20 movies on the SD working, but, also lately, when I move newly downloaded movies, sometimes I have success. Other times the video only party transfers or breaks completely. The wierd thing is that the same video can do all three things. Break sometimes, partially move, and in some cases successful transfer. I have checked the permissions of everything and it seems to check out. I have busy box pro and rom toolbox pro installed also, but even using rom toolbox i have the same problem. I have even tried my pc, but when I put the SD back in my phone, same thing. I also noticed that some items successful moved will be either broken later or just gone. This includes photos, movies, saved PC programs and more. Can anyone help me figure this out. Ive tried and checked everything I can think if.
Hello folks.
I've been deleting files form SD card, using MTP. Deletion works without error, files are not shown any more.
However: The SD-card does not show any more free space as before the deletion.
Any suggestions?
Device Moto G 2. gen
stock rom 6.0
Hello folks.
I'm wondering if my question is not clear.
I have 30MB left on my SD, even though I did delete a bunch of stuff.
I really could use a hint - would like to copy some new content to it, once I get more "free" space...
Well, how have things turned out?
You know about the extra restrictions regarding external storage added in Android 6. You can barely use the SD card as it is, let alone have Windows do things to it.
Have you tried checking the storage with a file manager? ES File Explorer and X-plore could be granted some sort of write permission - see if the files are still there and delete them through your phone - although those two have a recycle bin option, make sure you uncheck it first.
And start using Temasek's custom ROM in the first place. If you're using the SD card as much as I do, that's the only reasonable option when it comes to Android 6.