Related
Th weirdest thing happening on my Vibrant with Eugene R2 rom.
When I put a microSD in the slot, it can not use it past 2.19 gb (like if it was a corrupted card), but when I use the same card in my TP2 or in the SD card reader of my laptop, everything is fine. I first noticed this when I was copying over all my files and I kept getting the same errors I have had with fake cards in the past, so I tried my old faithful 8gb and sure enough, when I plug my vibrant as a USB drive, I can not navigate most folders and runing the checkdisk gives me hundreds of corruption errors. When I try to format, it tells me the max is 2.19 gb. When I take the same card (which had always been fine) and put it in the sd card reader, everything is back to normal, including attempting to format (it gives the proper size). My vibrant is doing this with all cards I have tried up till now.
Any clues?
Thanks
Did you ever run an older ULF kernel at some point? Are you running one now?
I had similar issues with both my SD card *and* the internal SD, which was causing all sorts of random system glitchiness. In my case, I suspected that this was due to the problems in early ULF kernels that caused filesystem corruption. I ended up using Heimdall (you'd use Odin if you're on Windows) to restore an official Samsung firmware, then I reformatted both SD cards, and from then on everything was fine.
There's probably a less drastic approach to be taken, but restoring to stock from Odin/Heimdall is a pretty surefire way to get rid of all the gremlins.
Incidentally, it was at that point that I decided to stop flashing anything except official or leaked Samsung ROMs until CM gets released. The price for being an early adopter is just too high
I am not sure what ULF kernels are, but all I have had is stock, then Eugene, then I did a restore to my stock backup (that screwed thigns up) so I reflashed eugene. I don't know how to use odin\can't figure out what files i should use.
julienrl said:
Th weirdest thing happening on my Vibrant with Eugene R2 rom.
When I put a microSD in the slot, it can not use it past 2.19 gb (like if it was a corrupted card), but when I use the same card in my TP2 or in the SD card reader of my laptop, everything is fine. I first noticed this when I was copying over all my files and I kept getting the same errors I have had with fake cards in the past, so I tried my old faithful 8gb and sure enough, when I plug my vibrant as a USB drive, I can not navigate most folders and runing the checkdisk gives me hundreds of corruption errors. When I try to format, it tells me the max is 2.19 gb. When I take the same card (which had always been fine) and put it in the sd card reader, everything is back to normal, including attempting to format (it gives the proper size). My vibrant is doing this with all cards I have tried up till now.
Any clues?
Thanks
Click to expand...
Click to collapse
Julie, I had this same problem with both this ROM, and my proceeding one, ASOPish; as have many, many others!
I too have been wanting a fix, but have not come across one. Because I am able install data onto my micro sd card via the adapter this is what I have resigned to doing. There was a mounting fix posted last month some time, but it didn't work for me, though others state that it did for them.
Sorry I couldn't give you a more workable solution, but at least, for me, this way does work.
FYI I had this problem until nero V3
Eat at Joe's
Having micro sd issues also. I tried moving some music and pics from the internal sd. It put the names but 0 data. I erase them and they come back. I reformatted the 8gb card it said 8gb free. I go back to the gallery or music player and they are all back. Check the sd with a file manager and thete they are.
t1n0m3n said:
FYI I had this problem until nero V3
Eat at Joe's
Click to expand...
Click to collapse
hum... anyone else with this problem fix it by using nero v3?
This is happening on all 2.2 roms.
One issue was fixed, where the internal and external cards were being read opposite to what there were ..., but the issue of reading external sd above 2gigs is still there ...
If I remember correctly, this was the issue when 2.2 was released for the N1 .... they forgot to re-add support for sdhc cards... that's why they pushed 2.2.1.......
Hi guys
I'm having some extremely irritating problems with my A500. It doesn't detect any external sd card I've tried so far. It says external sd is unavailable under storage in settings and the external_sd folder is empty in root/mnt. I've tried 3 different cards so far with no success. Anyone have a any advice for me on how to mount the card? I think the problem might be that it doesn't get mounted when I insert it. I can't root because the GingerBreak mod that's been posted needs an external card to work. So maybe some advice on how to root some other way? Then I can try restore a stock image and see what happens.
I had to insert mine and then reboot the tablet for mine to show inside of a file manager.
Sent from my A500 using XDA Premium App
lawmangrant said:
I had to insert mine and then reboot the tablet for mine to show inside of a file manager.
Sent from my A500 using XDA Premium App
Click to expand...
Click to collapse
Hey, thanks for the tip. I forgot to add it to my original post. I've tried rebooting with all 3 of the cards I have. I'm starting to think it's a hardware problem...
Have the cards you're testing been formatted NTFS or FAT32? If NTFS they probably won't work without some help.
The stock device only deals with FAT32 mSD cards; I haven't tried the NTFSMount app from the Dev forum on an NTFS-formatted card yet, only USB devices.
Vereynn said:
Have the cards you're testing been formatted NTFS or FAT32? If NTFS they probably won't work without some help.
The stock device only deals with FAT32 mSD cards; I haven't tried the NTFSMount app from the Dev forum on an NTFS-formatted card yet, only USB devices.
Click to expand...
Click to collapse
Hey. I've formatted the cards multiple times, to FAT32 every time. Might try exFAT tomorrow just to see what happens.
exFAT didn't work. Not that I expected it to, lol. Maybe the GingerBreak apk can be modified to use the usb storage instead of the external sd. Any idea where I can get the source code to take a look at?
If you've tried multiple cards, all FAT32 and all work on other devices, I'd return the tablet while you can, sounds like a hardware problem indeed
Slight problem with the returning, lol. I live in South Africa and ordered my tab from the USA since my own country is so backwards. I don't really mind not having an external sd card, I just wanna root again since almost all the apps I use need root. I'm considering returning, even if it's gonna take a lot of effort, time and money...
EDIT - Another reason I can't return it (and this is a horrible thing) is that SuperUser Permissions is still installed. The recent update made me lose root. So I'm kinda stuck with this app that's proof that I voided my warranty. The only way to get rid of SuperUser is to use some apps that all need root. To get root I need the external sd to work. To get that to work I need to send it for repairs. A very messed up situation
I'm almost positive that it's a hardware issue now. Even when I try to do an update.zip from recovery mode it can't find the file even though it's on the card. Let's hope they don't see the SuperUser app when I return it...
I thought about maybe waiting for Acer to release an update that will unlock the bootloader. But since the SD card slot isn't working I won't be able to install the update. That so much depends on one little slot amazes me. If you wanna know what the single point of failure for an Android device is, look no further.
I know some android tabs came out without external SD card support. I live in the uk and have a 32GB version and the SD card worked out the box. Maybe you have to wait for an update. Just my 2c though. You won't need an external SD to receive OTA updates though.
Sent from my A500
Here's an image of what recovery mode says when I select Install Update from external source. Seems the system can't mount the card. Sigh
I like that message at the end.... "Install from sdcard complete."
You had rooted before the update, which means it had to have seen the sdcard then. So it's unlikely that the hardware just went bad. Are the sdcards your trying of different sizes, classes, and/or manufacturer?
I'd go with the same sdcard you used when you rooted before and reformat it using the HP USB Format tool. Selecting fat32, of course. And don't select quick format. See if that helps. Sorry if I missed somethiing relevent above.
Here's the link to the HP first tool. http://download.cnet.com/HP-USB-Disk-Storage-Format-Tool/3000-2094_4-10974082.html
Sent from my A500 using Tapatalk
Lol, the "fake it till you make it" strategy. Fail Google.
I've tried it with the original SD and two other ones. My guess is some app tried to mount the external SD in /mnt/sdcard and messed up some associations or dependencies or something.
I'm amazed. After everything I've tried it suddenly worked. I was busy in settings and accidentally selected storage. And there it was in all its glory... A working external sd card! I'm rooted again, backed up and ready to roll!
To anyone finding this thread hoping for answers for a similar problem: It was a hardware problem indeed. I fixed it myself by opening the tab and bending the MicroSD slot's pins back into place.
UPDATE well it looks as though I have found a solution to my woes. I made several attempts of formatting the 2gb card in my laptop to no avail. I tried my old captivate that it originally came out of and the cappy had troubles reading it. I then stuck it in my evo and it registered instant, so I did asdcard format on my evo and then finally the tablet registers the card. In case this helps anyone else
First off someone please enlighten me on the tabs use and the way it mounts the external SD, I read somewhere that it only uses it for media files such as music books and pics. I have an 8GB that belongs in my EVO, and a 2gb that I had for my captivate I was hoping to use in my Tab for now.
Here's my story, maybe someone can shed a little light here: My tab was purchased with Stock 3.1, I was getting annoyed by the constant update request so I went ahead and rooted and installed CWM without incident, then I decided to install the Stock rooted update from here, however when I insert my SD cards they say they are unavailable. So I stick my 2gb in my laptop format to fat32 (should this be different?, typically it works in every other device I own) It still won't read, I did exactly as others point out in other threads but still I am stumped as to how the card is made available to the OS ? Now in a fit of frustration I pulled my 8gb out of my evo put the 2gb in and wham there it is, I put the 3.2 download on the 8gb popped it in tab entered CWM and flashed the update, I don't know if the 2gb is mountable in CWM I will try tonight but the 8gb was mountable through CWM however my 8gb also was not available to Android even after the update.
So what the heck is the use of the external SD and how is it used?
I think you might have an issue with your ROM,
I use my external SD for my titanium backups and other files I want to keep portable. I have used the SD card through my PC via USB and directly by putting into the PC's card reader.
Have you tried using a file manager? I use File Manager HD and the external card shows up as Storage on the left bar.
As for the filesystem, I think I may have originally formatted as FAT but I have also pulled my SD out of my Blackberry and used it to install Honeylicious through CWM,
All in all I dont think you should be having the issues that you are having...
Good luck
If it won't mount in CWM you need to format it in your android phone, that fixed it for me. Once it is formatted correctly you'll see a notification that an SD card is installed. Also my PC wouldn't see it until I put a custom rom on. Also to store items on it you can use a file manager to move things to and from it.
~Sent from my Droid SuperCharge~
>DARKMAN< said:
If it won't mount in CWM you need to format it in your android phone, that fixed it for me. Once it is formatted correctly you'll see a notification that an SD card is installed. Also my PC wouldn't see it until I put a custom rom on. Also to store items on it you can use a file manager to move things to and from it.
~Sent from my Droid SuperCharge~
Click to expand...
Click to collapse
The 8gb card did mount in CWM but would not mount in the OS, or when it would I would get it was unavailable or sometimes even empy when I know there is only about 1 gb free space, I did not test the 2gb in CWM mainly because it was late and I needed to go to bed, but I will try tonight. The 8gb is the one I updated to rooted 3.2 with, I still need to go to 3.2.1 ? Is there a rooted Stock 3.2.1 floating around I really havent looked much into it yet
I have noticed that getting the iconia to read some sd cards is like tossing dice..Most people who have this issue says one card works perfect in every device but not in the iconia.. Some say the card will work sometimes and not others .. Some say the card works in cwm and not with file manager..
The issue here i think is that you have two CARDS THAT ARE FUSSY ABOUT mating with the iconia. OR Your rom .i would read the threads in the rom you are using.. IF still nothing that sounds like your issue ask the DEV about this.. If STILL No luck you can either try to buy a new diffrent card or flash a new rom to try and Diag. this issue..
Good luck..
Silly question
Is your microSD formatted FAT32?
If it is anything else, your unit may have trouble reading it depending on what ROM you are using - Not all ROM's are capable of reading NTFS or other file systems.
Sometimes, microSD's freak out as well, and the only way to get it back to normal is to format it in a Symbian phone (Nokia)
Also, make sure you are using the correct mount point for the card - /mnt/external_sd - Root Explorer and other apps like it can get there.
Other than that, you may just have a bad microSD, I have had many of them die for seemingly no reason.
Hello,
I'm having a strange issue...I am not able to make any modifications to files on my external SD card either directly through the phone or USB via my computer. Operations on the internal SD card work fine.
To be more specific, the changes I make will not "stick" after a reboot. When I say changes I mean anything, whether it's moving, copying, editing or deleting a file(s).
An example of this is if I move a file to the SD card through the computer or on the phone, it will work and show up. Once I reset however, any changes I made will revert, just like I never did it. I attempted to re-flash to a different rom, but I'm having the same issue.
I'm not sure if it's relavant, but I was originally using Slimkat 4.4.4 (build 9). When I flashed a different ROM to see if it worked, I used CM11.
Does anyone know what might be causing this??
EDIT - Please disregard. This appears to be a known issue with Sandisk memory cards and not an issue with the phone. Guess I'm SOL and will have to buy a new one since I got it in 2013...
Thank you!
I have a very strange thing that has just started occurred with my wife's Note 4. It appears that all apps have lost write-access to the SD card.
I first noticed the problem with the camera app. The camera app was configured to write to external storage but when a picture is taken, it says "Unable to save file to SD card. Default storage has been changed to device memory."
The Gallery app is also not able to write to the SD card (cannot create a new album) or move files to an existing album on the card.
Solid Explorer cannot create a new folder on the card.
I've tried to clear app settings for the camera and Solid Explorer. But even after setting everything back up, I still get the same results.
I'm running stock v6.0.1 (EPJ2) rooted. Also, my (seemingly identical) Note 4 does not display any of this behavior. No changes other than normal application updates.
Any ideas what might be going on?
I've had this happen when an SD Card gets corrupted - you can still view and access the files that are already on the card, but you can no longer write to it.
Try the card in a PC and see if that can write to it - if not then your card is likely permanently damaged. I had 3 Sandisk 64Gb cards go like this in two different devices. Tried reformatting them every which way, but nothing would make them writeable again. Have used Samsung cards ever since and never had a failure yet.
Just restart your phone
Sent from this galaxy
SJMarty said:
I have a very strange thing that has just started occurred with my wife's Note 4. It appears that all apps have lost write-access to the SD card.
I first noticed the problem with the camera app. The camera app was configured to write to external storage but when a picture is taken, it says "Unable to save file to SD card. Default storage has been changed to device memory."
The Gallery app is also not able to write to the SD card (cannot create a new album) or move files to an existing album on the card.
Solid Explorer cannot create a new folder on the card.
I've tried to clear app settings for the camera and Solid Explorer. But even after setting everything back up, I still get the same results.
I'm running stock v6.0.1 (EPJ2) rooted. Also, my (seemingly identical) Note 4 does not display any of this behavior. No changes other than normal application updates.
Any ideas what might be going on?
Click to expand...
Click to collapse
There are 3 possible solutions:
Using MS Windows PC
Using Linux PC
Using TWRP Recovery with a proper BusyBox
Let me know which one do you choose & I will explain how.
Kinsman-UK said:
I've had this happen when an SD Card gets corrupted - you can still view and access the files that are already on the card, but you can no longer write to it.
Try the card in a PC and see if that can write to it - if not then your card is likely permanently damaged. I had 3 Sandisk 64Gb cards go like this in two different devices. Tried reformatting them every which way, but nothing would make them writeable again. Have used Samsung cards ever since and never had a failure yet.
Click to expand...
Click to collapse
You nailed it. My card was a 128 GB SanDisk Ultra. Pulled it from the phone and my laptop couldn't write to it either. Copied everything off and copied it back to a new card and there you go.
Grrrr...$^%**# SanDisk.
Out of curiosity, what Samsung line did you end up choosing? I think the EVO+ will be sufficient for me but wondering what you ended up using.
SJMarty said:
Out of curiosity, what Samsung line did you end up choosing? I think the EVO+ will be sufficient for me but wondering what you ended up using.
Click to expand...
Click to collapse
Glad you got it sorted! I've been using a Samsung PRO 64Gb - this is the 128Gb version on Amazon UK:
https://www.amazon.co.uk/dp/B01CRZCLAM
I think the newer version of it is this one:
https://www.amazon.co.uk/dp/B019QO1Q4O
But you're right - the EVO+ is probably sufficient. It wasn't available when I was purchasing:
https://www.amazon.co.uk/dp/B00WR0HIR4