I bought 64 gb card and it works on samsung stock galaxy s3 rom BUT when i switched to Cyanogen10 mod it started showing damaged card,
I know it is because the stock has driver for that card,
My question is has someone ported or can someone please port the driver from stock and make it workable on custom roms.
Thanks.
exFAT is not and probably will never be supported by CM9 or 10.
Your card needs to be FAT32-formatted to work.
Alright trying hopefully this works and doesnt screw up my card.
d4fseeker said:
exFAT is not and probably will never be supported by CM9 or 10.
Your card needs to be FAT32-formatted to work.
Click to expand...
Click to collapse
didnt work now the phone doesnt even show damaged card, its acting like card is not even inserted.
How exactly have you formatted the card? Windows onboard utilities won't let you format a 64GB card as FAT32, so my guess is you formatted it as NTFS.
Unfortunately CM cannot read NTFS either, you'll need another kernel for that. (And to date none has been released)
Try the HP Usb Format utility to create a FAT32 partition.
d4fseeker said:
exFAT is not and probably will never be supported by CM9 or 10.
Your card needs to be FAT32-formatted to work.
Click to expand...
Click to collapse
Why is this?! Does AOSP not come with exFAT support, it's something Samsung builds into the kernel afterwards?
Disappointed, as I was tempted to try CM, but no 64GB support renders my card next to useless.
Disappointed, as I was tempted to try CM, but no 64GB support renders my card next to useless.
Click to expand...
Click to collapse
FAT32 doesn't mean the card is restricted to 32GB, it means a file can be 2^32 bytes long which is 4GB.
FAT64 (ExFat) has a limit of 2^64 bytes per file which equals 16 Exabyte (1Exabyte = 1024 Terabyte)
It's possible for FAT32 partitions to be as large as 8 Terabyte, which is roughly 1000 times the size of harddisks when FAT32 was released.
Windows, for some stupid compatibility reason with a 12 year old operating system (Windows 2000) does not allow to format FAT32 partitions to a size larger than 32GB, hence the usual confusion.
As described above, here is the tool you need: http://www.softpedia.com/get/System/Hard-Disk-Utils/HP-USB-Disk-Storage-Format-Tool.shtml
Why is this?! Does AOSP not come with exFAT support, it's something Samsung builds into the kernel afterwards?
Click to expand...
Click to collapse
ExFat is patent-encumbered, meaning every distributed binary copy of Cyanogenmod would theoretically cost the developers the license fee.
(At least for US-based downloads, most other countries see software patents as what they are - ridiculous and unenforceable)
Furthermore -and a very big issue- is the instability of the exFat code for GNU/Linux (and by extension, Android) which causes data loss, corruption and other negative side effects.
It's highly recommended not to use exFAT with Samsung-firmwares either.
d4fseeker said:
How exactly have you formatted the card? Windows onboard utilities won't let you format a 64GB card as FAT32, so my guess is you formatted it as NTFS.
Unfortunately CM cannot read NTFS either, you'll need another kernel for that. (And to date none has been released)
Try the HP Usb Format utility to create a FAT32 partition.
Click to expand...
Click to collapse
i used easeus partition: i deleted partition first and made new one with fat32 file system,
which didnt work, after that i deleted the partition again and formatted using stock galaxy s3 rom and it works again but limited to stock rom only like before.
atleast the card isnt dead.
d4fseeker said:
How exactly have you formatted the card? Windows onboard utilities won't let you format a 64GB card as FAT32, so my guess is you formatted it as NTFS.
Unfortunately CM cannot read NTFS either, you'll need another kernel for that. (And to date none has been released)
Try the HP Usb Format utility to create a FAT32 partition.
Click to expand...
Click to collapse
ill try this software as well.
d4fseeker said:
How exactly have you formatted the card? Windows onboard utilities won't let you format a 64GB card as FAT32, so my guess is you formatted it as NTFS.
Unfortunately CM cannot read NTFS either, you'll need another kernel for that. (And to date none has been released)
Try the HP Usb Format utility to create a FAT32 partition.
Click to expand...
Click to collapse
I didnt get a chance to try Hp software i cant across this other software and it work.
Thank you though
d4fseeker said:
FAT32 doesn't mean the card is restricted to 32GB, it means a file can be 2^32 bytes long which is 4GB.
FAT64 (ExFat) has a limit of 2^64 bytes per file which equals 16 Exabyte (1Exabyte = 1024 Terabyte)
It's possible for FAT32 partitions to be as large as 8 Terabyte, which is roughly 1000 times the size of harddisks when FAT32 was released.
Windows, for some stupid compatibility reason with a 12 year old operating system (Windows 2000) does not allow to format FAT32 partitions to a size larger than 32GB, hence the usual confusion.
As described above, here is the tool you need: http://www.softpedia.com/get/System/Hard-Disk-Utils/HP-USB-Disk-Storage-Format-Tool.shtml
Click to expand...
Click to collapse
Thanks, though I realised this - the whole reason I need a 64GB card is to copy movies onto there, because I travel a lot... many of them are over 4GB, which is the issue I have with using FAT32.
d4fseeker said:
ExFat is patent-encumbered, meaning every distributed binary copy of Cyanogenmod would theoretically cost the developers the license fee.
(At least for US-based downloads, most other countries see software patents as what they are - ridiculous and unenforceable)
Furthermore -and a very big issue- is the instability of the exFat code for GNU/Linux (and by extension, Android) which causes data loss, corruption and other negative side effects.
It's highly recommended not to use exFAT with Samsung-firmwares either.
Click to expand...
Click to collapse
Maybe I should look at ext3 instead, though then I'd have problems putting it straight into my Windows machine. Though, exFAT has been 100% stable for me so far.
many of them are over 4GB
Click to expand...
Click to collapse
Ok that is a problem for FAT32. You didn't mention it so I assumed you mistook the 32 in FAT32 for 32GB as many people do.
Maybe I should look at ext3 instead
Click to expand...
Click to collapse
Since you should never need to remove or directly access the card (MTP mode or File transfer through 'Samba Fileshare' App) that should be a solution. For your own computers, you could use the following driver:
http://www.fs-driver.org/
It allows read-write access to EXT2. EXT2 being EXT3 without journaling support (and thus fully backwards compatile) that could do the trick.
Pententially you'll need to re-enable the journal again through tune2fs on the Smartphone after having used an EXT2-driver. Not sure though since the journal is only relevant until a clean dismount is made.
You should however also be able to load the NTFS-module in the kernel or recompile the CM10 kernel with the required options.
If you need to plug the SDcard into your computer a lot, that may be the only solution until Gokhanmoral is back.
Related
If you have been having issue with exfat card even after formatting it to fat32 this is probably the solution for you
The 64gb exfat card i have never worked on custom roms no matter what software i used to format it to fat32.
But finally it worked with this one software, Just make sure you follow the instruction correctly.
http://software-files-a.cnet.com/s/...&pid=12572695&psid=10863346&&fileName=epm.exe
First use easeus to delete the partion in 64 gb card.
then Click Start menu, select Run and enter diskmgmt.msc
You need to find the disk with unallocated space. Right click on it and select "New Partition" and follow these steps, clicking "Next"
Enter the maximum size for the Partition Size
Choose assign a drive letter. I used F:
Select "Do not Format this partition"
Click Finish
Now you have a drive letter, this is what we will pass to the formatter
http://www.ridgecrop.demon.co.uk/download/fat32format.zip
Now download a copy of fat32format. Extract the EXE file to C:\
Click Start->Run and enter cmd (as admin)
type this - C:\fat32format f:
enter y to continue
Now the sd card should work on phone.
Source: http://www.ridgecrop.demon.co.uk/index.htm?guiformat.htm
Thanks to DroidGnome for linking me this site.
An easier alternative which doesn't require CMD or the use of multiple tools is HP Usb Format Utility:
http://www.softpedia.com/get/System/Hard-Disk-Utils/HP-USB-Disk-Storage-Format-Tool.shtml
d4fseeker said:
An easier alternative which doesn't require CMD or the use of multiple tools is HP Usb Format Utility:
http://www.softpedia.com/get/System/Hard-Disk-Utils/HP-USB-Disk-Storage-Format-Tool.shtml
Click to expand...
Click to collapse
If it works then sure. i already used 3 recommended softwares all failed so i dont know if this will work.
Thanks for this guide
I always format and re-partition in Linux ...
I always format and re-partition in Linux ... and currently all my large microSD cards have been re-partitioned with the following layout:
- free space (4 MB on 32GB, 16 MB on 64GB - since that's how those came from factory )
- main partition (primary partition 1 - I format that as Fat32 in Linux but then I go to Win7 and re-format to exFat; exFat works perfectly in Android 4.x from Samsung (and good mods) and the CWM recovery from CrisKelo ROM can work just perfectly with exFat when doing backup/restore; other (even newer) CWM versions/alternatives might NOT be OK with exFAT or stuff over 32GB!
- 512 MB Linux swap (primary partition 2) - this gets mounted by special mods that give the kernel virtual memory
- free space at the end (at least 4 MB on 32GB, at least 16 MB on 64GB)!
The only drawback is that at this moment there is no program (on PC or phone) that can resize exFAT - so you need to reformat! That is in contrast to NTFS / FAT32 / ext2 / ext3 / ext4 - which can all be resized perfectly - and IMHO NTFS could be a better option that exFAT (for journaling, even if I do not write that much anyway), but unfortunately there is no serious support for it on CWM; ext3/ext4 could also be even better from the Linux standpoint (but not for the usual Windows user that might have problems reading it) - but again is (surprisingly) not so supported by either CWM nor most ROMs
Just got new Sandisk 64GB cards and was having a heck of a time getting them to play nice with Paranoid Android, this guide was simple, painless and most of all, effective. Thank you much for posting this information.
Works with cyanogenmod nightly 2013-02-17 and ubuntu
So I have tried it out and it worked.
omar300 said:
If you have been having issue with exfat card even after formatting it to fat32 this is probably the solution for you
The 64gb exfat card i have never worked on custom roms no matter what software i used to format it to fat32.
But finally it worked with this one software, Just make sure you follow the instruction correctly.
http://software-files-a.cnet.com/s/...&pid=12572695&psid=10863346&&fileName=epm.exe
Link seems broken.
Click to expand...
Click to collapse
Thank you!! Was wondering what I had done wrong with a custom ROM not reading the 64Gb card I had, now it does: )
great to see i helped some people.
ok so software to erase partition is called EaseUS incase this link gets broken in future just google, if im late with reply again in future.
http://download.cnet.com/EaseUS-Partition-Master-Free-Edition/3000-2248_4-10863346.html
Just wanted to say THANKS
I have been trying to get my 64GB working for days after install wicked rom 5.1 for my Samsung S4, noting worked till I found this post GREAT work and thanks so much!!!!
YOU RULE!
Thanks!! I have only been able to get my Scan Disk Ultra 64G card to work with Perseus kernel and would have to flash it to all Roms then use a hack to swap the internal to get it to work. It was a Pain in the ass and limited my Kernel usage. THANK YOU SO MUCH WHAT A USEFUL POST!! Stick to this plan it works. I have yet to see any other solution. I been dealing with this problem since I had my Galaxy note2 almost a year now.
PS do not use that crappy HP USB format 2.2 whatever program some guy suggested a bunch of malwar garbage I cant get off my computer now THANKS BUDDY Crawl back under a rock which you came.
Thanks for the wonderful help everyone who got it working
Sent from my SHG-M919 using XDA Premium 4 mobile app
so which format type is better for some1 running stock rom on galaxy note 2..... with a 64g sandisk ultra..... its alrdy working without any particular format....worked with factory settings but right now d mmry card is acting up cos of d script I used 2 swap....am only guessing.... so is it better 2 format to ex fat or fat32?
mortallkombat said:
so which format type is better for some1 running stock rom on galaxy note 2..... with a 64g sandisk ultra..... its alrdy working without any particular format....worked with factory settings but right now d mmry card is acting up cos of d script I used 2 swap....am only guessing.... so is it better 2 format to ex fat or fat32?
Click to expand...
Click to collapse
i have no idea the swap system, as stock, it already has driver for ex fat but since you changed some stuff it might have ruined that driver.
try your card on another phone with stock rom and same android version. if it works then you dont need to change sd card format, just reinstall ROM on your phone.
PhatNerd said:
Thanks!! I have only been able to get my Scan Disk Ultra 64G card to work with Perseus kernel and would have to flash it to all Roms then use a hack to swap the internal to get it to work. It was a Pain in the ass and limited my Kernel usage. THANK YOU SO MUCH WHAT A USEFUL POST!! Stick to this plan it works. I have yet to see any other solution. I been dealing with this problem since I had my Galaxy note2 almost a year now.
PS do not use that crappy HP USB format 2.2 whatever program some guy suggested a bunch of malwar garbage I cant get off my computer now THANKS BUDDY Crawl back under a rock which you came.
Click to expand...
Click to collapse
i know, that is reason i posted this. i tried about 10 software and then i found this weird way of doing it and it actually works.
all those fancy software dont do anything besides slowing computer down.
glad to know i was of some use
I have a 64 GB SD card on my S4. Thankfully it is working with TWRP which now has support for exFAT.
Are there any custom kernels for the Vz S4 that support exFAT?
Since I don't have any files bigger than 4GB I may downgrade the file structure to FAT32 if that is the only way to use a custom kernel on my S4.
swieder711 said:
I have a 64 GB SD card on my S4. Thankfully it is working with TWRP which now has support for exFAT.
Are there any custom kernels for the Vz S4 that support exFAT?
Since I don't have any files bigger than 4GB I may downgrade the file structure to FAT32 if that is the only way to use a custom kernel on my S4.
Click to expand...
Click to collapse
I'm interested in this as well...only one I'm aware of so far is by Ktoonsez, in this thread: http://forum.xda-developers.com/showthread.php?t=2294083.
Here's what I got from the kernel dev, Ktoonsez:
Originally Posted by Redflea:
Just wanted to confirm that this:
"Thanks to Talustus we now have exFAT for Touchwiz and AOSP"
...means that I can leave my 64GB SD card formatted to exFAT, correct?
Faux is still saying on his kernel thread says that he provide exFAT support due to Samsung's licensing of MS proprietary exFAT format, which hasn't been released as it isn't open source. How was that gotten around on this kernel? Thanks...
Reply from Ktoonsez: A developer named Talustus wrote one from scratch. It work for 90% of the people I would say, some cheapy SDcards seem to have trouble, Samsung cards will work 100% of the time. The exFAT card must be in the phone upon boot up and the exfat partition must be on partition 0 or 1 for my code to pick up on it. To get best chance of success, format the card using Windows 7 or 8 for exFAT, that will guarantee the whole card will be formatted to exFAT on partition 0
Click to expand...
Click to collapse
I've also asked on the Chronic kernel thread here:
http://forum.xda-developers.com/showthread.php?t=2319243
Faux's kernel does not support exFAT.
So I did a bunch of searching the web and also searched this forum a lot. Can't figure out a workaround for the Fat32 sd card requirement on the Venue 8 android tablet. I would like to be able to play larger files than 4 gig from the sd slot.
I tried using NTFS and exFat and the tab won't see the card in either case.
I also have a China tab (Momo8) and it sees NTFS just fine, am I correct in assuming this is a restriction put in place by Dell for some reason?
Thank you in advance for any help!
merlin11221 said:
So I did a bunch of searching the web and also searched this forum a lot. Can't figure out a workaround for the Fat32 sd card requirement on the Venue 8 android tablet. I would like to be able to play larger files than 4 gig from the sd slot.
I tried using NTFS and exFat and the tab won't see the card in either case.
I also have a China tab (Momo8) and it sees NTFS just fine, am I correct in assuming this is a restriction put in place by Dell for some reason?
Thank you in advance for any help!
Click to expand...
Click to collapse
Could be Dell not enabling NTFS support due to licensing issues, note that only FAT32 isn't encumbered by patents and royalties. Both NTFS and exFAT require licensing. It's likely Dell not wanting to deal with it. If you aren't planning to plug in your microSD directly to your computer, just format the microSD card with ext4 if you're worried about not able to upload files bigger than 2 GB.
deltatux
Thanks for the reply deltatux.
I have a couple more questions. Your reasoning seems logical, and is further supported by the Momo8's unrestricted formats and not being a name brand tab from the USA... Even though they all come from overseas...
1. How do I format it with ext4?
2. If I do that and have a HD video of my kids skiing (rather large file), can I load that from the computer to the card somehow? That would be the purpose, to share some of that stuff with members of the family who are slightly technically challenged and can't use YouTube and such...
Otherwise I can use Power Director to split up the movies, but that's less desirable.
deltatux said:
Could be Dell not enabling NTFS support due to licensing issues, note that only FAT32 isn't encumbered by patents and royalties. Both NTFS and exFAT require licensing. It's likely Dell not wanting to deal with it. If you aren't planning to plug in your microSD directly to your computer, just format the microSD card with ext4 if you're worried about not able to upload files bigger than 2 GB.
deltatux
Click to expand...
Click to collapse
I jus tried using a 64Gb sd card, formated as ext4, and the venue 8 does not recognize it, it says that it's blank.
I also want to watch movies > 4Gb,
Thanks for the sugestion.
Sent from my Venue 8 3830 using Tapatalk
merlin11221 said:
Thanks for the reply deltatux.
I have a couple more questions. Your reasoning seems logical, and is further supported by the Momo8's unrestricted formats and not being a name brand tab from the USA... Even though they all come from overseas...
1. How do I format it with ext4?
2. If I do that and have a HD video of my kids skiing (rather large file), can I load that from the computer to the card somehow? That would be the purpose, to share some of that stuff with members of the family who are slightly technically challenged and can't use YouTube and such...
Otherwise I can use Power Director to split up the movies, but that's less desirable.
Click to expand...
Click to collapse
To format, you can use Linux and run the GParted tool to format the partition to ext4.
etraud.a said:
I jus tried using a 64Gb sd card, formated as ext4, and the venue 8 does not recognize it, it says that it's blank.
I also want to watch movies > 4Gb,
Thanks for the sugestion.
Sent from my Venue 8 3830 using Tapatalk
Click to expand...
Click to collapse
That's odd, blank as in cannot read the card or it's just filled with free space? The odd part is that all the partitions in Android 4.0+ are all formatted with ext4 so the tablet has ext4 support since that's the standard filesystem for Linux and Android.
deltatux
Could this be an Intel Atom issue? I've been told Intel needs to update the Atom software for KitKat to function. Just wondering if this problem goes away when Intel updates the Atom software and KitKat is applied? (A Dell source tells me Dell is waiting on Intel to be able to release 4.4, and they expect this to be complete late March - early April.)
dmkozak said:
Could this be an Intel Atom issue? I've been told Intel needs to update the Atom software for KitKat to function. Just wondering if this problem goes away when Intel updates the Atom software and KitKat is applied? (A Dell source tells me Dell is waiting on Intel to be able to release 4.4, and they expect this to be complete late March - early April.)
Click to expand...
Click to collapse
Yes, all Android updates generally will require the SoC manufacturer to release what's known as the "Board Support Package" that contains all the Android optimizations and drivers required to run properly for that particular chipset. If the manufacturer doesn't release a BSP, there will not be an Android update no matter how you slice it. This is the reason cited why the Galaxy Nexus will not get official Android 4.4 release since Texas Instruments has since pulled out of the SoC market. This is also likely the same story for Samsung and Sony devices running on ST-Ericsson's NovaThor SoC platform as well. As these companies no longer provide any SoC support, no new official Android builds will run on the devices that uses their chipsets.
As for an Intel Atom issue, not sure, I don't see why it would be since Android, like Linux uses the ext4 as their primary operating system, so unless someone modified something, I don't see why ext4 can't be supported for microSD cards...
deltatux
deltatux said:
Yes, all Android updates generally will require the SoC manufacturer to release what's known as the "Board Support Package" that contains all the Android optimizations and drivers required to run properly for that particular chipset. If the manufacturer doesn't release a BSP, there will not be an Android update no matter how you slice it. This is the reason cited why the Galaxy Nexus will not get official Android 4.4 release since Texas Instruments has since pulled out of the SoC market. This is also likely the same story for Samsung and Sony devices running on ST-Ericsson's NovaThor SoC platform as well. As these companies no longer provide any SoC support, no new official Android builds will run on the devices that uses their chipsets.
As for an Intel Atom issue, not sure, I don't see why it would be since Android, like Linux uses the ext4 as their primary operating system, so unless someone modified something, I don't see why ext4 can't be supported for microSD cards...
deltatux
Click to expand...
Click to collapse
Thanks deltatux, you seem to have a wealth of knowledge. I also formatted a 32gig card with ext4 and the Venue 8 says it's blank. It says the same thing for NTFS and ExFat, that it's a "blank storage device or unsupported file format". Then it asks if you want to format the card, which ends with a microSD card formatted to Fat32...
I did find an app while searching on the Venue. I searched for "NTFS support" or something similar. The program needs the tablet to be rooted and then it will support NTFS, ExFat, and others I believe. It is called Paragon exFAT, NTFS & HFS+, and is a free app. It is an interesting lead though to an otherwise unsolved issue!
If anyone gets time and has luck before I do please post here and let us know!
Merlin
Alternately I just found another thread in this forum oddly enough from a google search, hinting that this is not a problem specific to just the Venue... Was trying to see if I could find a workaround without rooting. Check it out if you like.
http://forum.xda-developers.com/showthread.php?t=1724078
Merlin
merlin11221 said:
Thanks deltatux, you seem to have a wealth of knowledge. I also formatted a 32gig card with ext4 and the Venue 8 says it's blank. It says the same thing for NTFS and ExFat, that it's a "blank storage device or unsupported file format". Then it asks if you want to format the card, which ends with a microSD card formatted to Fat32...
I did find an app while searching on the Venue. I searched for "NTFS support" or something similar. The program needs the tablet to be rooted and then it will support NTFS, ExFat, and others I believe. It is called Paragon exFAT, NTFS & HFS+, and is a free app. It is an interesting lead though to an otherwise unsolved issue!
If anyone gets time and has luck before I do please post here and let us know!
Merlin
Click to expand...
Click to collapse
I guess Dell might have disabled support for ext4 for microSD then. It's likely we need a custom kernel to get these features into the tablet. ext4 has no licensing requirements so I don't see why it didn't work. Have you tried to format to the previous ext3 file system? Maybe that might work? Not sure.
exFAT and NTFS will require licensing, which some manufacturers do not support, so far I know LG and ASUS do support it on their devices, not sure about Samsung and Dell though.
merlin11221 said:
Alternately I just found another thread in this forum oddly enough from a google search, hinting that this is not a problem specific to just the Venue... Was trying to see if I could find a workaround without rooting. Check it out if you like.
http://forum.xda-developers.com/showthread.php?t=1724078
Merlin
Click to expand...
Click to collapse
You'll need root, and this method should work in theory since most Linux distributions do use the open source NTFS driver but it only provides basic NTFS read/write operations and generally not optimized meaning performance may be sluggish and it may be bad for battery life. Once rooted, one can try this method for sure!
deltatux
No I did not try ext3, was running late last night and had to work this am. Is rooting difficult? I would like to get this working before our ski trip in a couple weeks. Is it likley that I mess up the tablet rooting? Sorry but this is the first time I have needed to alter a mobile device for any reason...
Merlin
merlin11221 said:
No I did not try ext3, was running late last night and had to work this am. Is rooting difficult? I would like to get this working before our ski trip in a couple weeks. Is it likley that I mess up the tablet rooting? Sorry but this is the first time I have needed to alter a mobile device for any reason...
Merlin
Click to expand...
Click to collapse
Unfortunately, there's no rooting methods released for this device, you'll have to wait.
deltatux
deltatux said:
Unfortunately, there's no rooting methods released for this device, you'll have to wait.
deltatux
Click to expand...
Click to collapse
Just a little update for everyone. I tried some more file formats once I got home.
NTFS, ExFat, ext3, and ext4 all say "blank SD card or unsupported file format". Then I get prompted to format in the Venue to Fat32.
Fat and ext2 both do nothing, can't even try to mount, and get no error message. It only shows a message when removed.
So I guess it is shrinking video files, waiting for root, or just playing them on the MOMO...
Thanks again for all the effort though! And please post if anyone finds a solution.
Merlin
merlin11221 said:
Just a little update for everyone. I tried some more file formats once I got home.
NTFS, ExFat, ext3, and ext4 all say "blank SD card or unsupported file format". Then I get prompted to format in the Venue to Fat32.
Fat and ext2 both do nothing, can't even try to mount, and get no error message. It only shows a message when removed.
So I guess it is shrinking video files, waiting for root, or just playing them on the MOMO...
Thanks again for all the effort though! And please post if anyone finds a solution.
Merlin
Click to expand...
Click to collapse
Looking at the SlimROM thread for the original Nexus 7, it seems the microSD file system support comes down to kernel support. In order to properly support microSD format other than FAT32, someone needs to enable it on the kernel...
http://forum.xda-developers.com/showpost.php?p=50192804&postcount=484
deltatux
I dont know if there is already info on this subject, but i recently got a sandisk 64G mSD and it didnt even seem to last a year - kept getting into 'read-only' mode for some reason..... i though it was my KKDS_1.4 (4.4.4) rom, link2sd and all the other stuff there, but dont know if that's the case kept having to do the following to get it out of read only mode :
Plug SD into windows and :
Start > Run > cmd
type "diskpart" -> runs diskpart.exe from system folder
type "list volume" -> now you see all your connected drives, see which one is the drive
type "select volume #" -> # being the letter of your drive
type "attributes disk clear readonly" -> removing the protection
Then open your SD, you can now edit, delete, move files.
However this didn't seem to last long... and think the SDcard on its last leg - even though i didn't use it much.... i did have a ton of pictures, videos, programs and music on it but still had about 12G free but was really slow - even though its one of the SanDisk Ultra 64G XC I (UHS Class 1).... Granted I do use Link2SD and have partitioned the card as follows [59G Fat, 4G ext4, 1G Swap], but cant account for things taking so long, and then sometimes finding the card in read-only mode.
Anyhow... from my reading i dont think android will even use the 'swap' space i made, so on future SD I plan on a 4G ext4 (for second partition) with the remaining 60G as a FAT32, ExFat, or NTFS - for my KitKat (4.4.4) Device - will one filesystem be better an any other for the first partition (windows / linux compatible) - im thinking NTFS (reliable & windows compatible) but not sure if KK supports write mode to NTFS filesystem? There is also ExFat - but not sure about android support for that either... Know many people suggest raw FAT but just not possible with todays bigger cards so kinda seem stuck with FAT32.
Regressing and getting to the heart of my post here, I was wondering if there has been any long term studies of Which mSD Cards last longer and transfer data pretty fast? Perhaps there are ones more reliable... thought Sandisk was pretty good (my USB 3.0 SanDisk Extreme 64 GB Flash Drive kicks butt) I know the technology is different but the 64G Ultra SDXC was UHS Class 1. (so at least class 10)... but its only a year old and already giving me trouble... what are the better cards out there -- and what filesystem should the first partition be set to to make it last (and usable in a windows [or linux] environment) ?
I did read over a few good posts :
http://forum.xda-developers.com/showthread.php?t=1544156
and http://forum.xda-developers.com/showthread.php?t=1150369
as well as a few other places here , here , here , and here
Im starting to think that since im using Link2SD perhaps class 10 card not optimal for the ext4 r/w , but i do use the primary partition quite a bit (like a flash drive ans dont want to wait eons while transferring all my tunes and videos etc to phone.....
Has anyone done any research into these issues? Are there any cards the use SLC nand? or just last longer?
Can anyone comment on any of this.
steve_77 said:
Anyhow... from my reading i dont think android will even use the 'swap' space i made, so on future SD I plan on a 4G ext4 (for second partition) with the remaining 60G as a FAT32, ExFat, or NTFS - for my KitKat (4.4.4) Device - will one filesystem be better an any other for the first partition (windows / linux compatible) - im thinking NTFS (reliable & windows compatible) but not sure if KK supports write mode to NTFS filesystem? There is also ExFat - but not sure about android support for that either... Know many people suggest raw FAT but just not possible with todays bigger cards so kinda seem stuck with FAT32.
Click to expand...
Click to collapse
I just answered on the other thread, but I wanted to add that AFAIK Android doesn't support NTFS (at least not without serious jigging) and I think exFAT is close to the same situation. Why? These are proprietary Microsoft formats (arguably FAT32 is as well, but it is based on the standard FAT16 and has been opened up considerably) that even for a Linux system have to go through hoops to get the drive to properly write (well, not too bad, install the ntfs-3g package).
I know using a thread it not necessarily the best way to ask a question but since the cause of this issue is unknown (and might just be SD corruption) and there are a few other threads where it might come up, this thread can be used as a reference.
The issue is: An SD card that rather suddenly became unwritable in every way and can no longer be mounted by Android (although it is detected) but on which all existing data was undamaged, can be viewed and copied via USB card reader to Windows or Linux PC. The drive behaves much as if it was write protected or as if the file system (particularly the FAT) was corrupted in a way that mimics digital SD write protection. Here are the details.
L5.1.1/CM12.1 December 2015, SuperSU 2.65, TWRP3.0.2,
- 64GB Sandisk Ultra SD, initially accepted as formatted or formatted upon first use to Fat32; Working fine for a few months as repository for static data (ROM zips and app apks), work material (frequently edited text, DOCX and XLSX files), as well as apps and app data with a dynamic presence on the drive.
- Drive suddenly stopped appearing on device in CM and in TWRP. When re-inserted in CM, the system detects a card but times out as it is unable to find a mount point. Attempts to mount SD card in ROM result in the following error in CatLog:
"E/Vold (222): /dev/block/vold/179:65 failed to mount via VFAT (No such device or address)
E/Vold (222): Volume sdcard1 found no suitable devices for mounting "
- Attempts to repair, partition or format the drive in TWRP result in mount error and the details of the drive have zeros where there should probably be other values.
/external_sd | | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Wipe_Available_in_GUI Removable Is_Storage
Primary_Block_Device: /dev/block/mmcblk1p1
Alternate_Block_Device: /dev/block/mmcblk1
Display_Name: MicroSD Card
Storage_Name: MicroSD Card
Backup_Path: /external_sd
Backup_Name: external_sd
Backup_Display_Name: MicroSD Card
Storage_Path: /external_sd
Current_File_System: auto
Fstab_File_System: auto
Backup_Method: files
MTP_Storage_ID: 65537
- With SD in card reader attached to PC, the contents of SD are visible and can be copied to PC but files cannot be copied from PC to SD card. It looks like they are copied but they are gone when card reader is disconnected then reconnected. Same in Linux Ubuntu 14.x.
- Unable to delete or reformat partitions in any utility that I tested including: Dedicated GParted boot USB, EaseUS Partition Master, HP USB Disk Storage Format Tool on PC, GParted in Ubuntu 14 VM, GParted in Ubuntu 10.x live CD/USB.
- Although the SD drive shows as Fat32 in GParted, Windows 7 only offers exFat and NTFS as formatting options. Some research shows exFat can digitally "write protect" drives with a dirty bit or byte which causes very similar symptoms.
- Windows Chkdsk requests to convert lost chains to files but must not be doing so as this occurs on every scan.
Soooo...the questions are: What in the realm of relatively normal android use might cause this? Has anyone heard of a disk or partition management setting or common form of drive corruption that could cause this? Could such a thing be caused by a file manager? A 32GB replacement SD is doing OK but I'm left wondering if the issue with the 64GB SD card was caused by a utility on the device or if it was just SD corruption (that looks conspicuously like digital write protection).
[EDIT] A minor correction I should make: The reason Windows 7 only offers NTFS and exFAT is not because the drive is damaged (although it may be) but rather because Windows 7 cannot format USB drives over 32GB with FAT32 although it can mount and use larger FAT32 SD drives that were formatted elsewhere. In this case I let android do the initial format months ago (Fat32) and never had problems during the times I connected it to card reader (although I usually leave it in the device and use Wifi or MTP through device USB to PC).
[] AL [] said:
Since your running 12.1, I imagine that you don't flash too many nightly build's... So this (not) variable is may be put aside from suspects list.
Click to expand...
Click to collapse
Correctamundo
[] AL [] said:
Recovery: well, I don't know but for that, I'm always following the if it ain't broke, don't fix it rule. You have specific reasons to keep it updated? Like you, I've also read many posts reporting USB related issues with v > 3.0. I still use v2.8.7.0 on my device and don't feel the need to update soon.
Click to expand...
Click to collapse
I'm now on the fence about reverting to the longer standing 2.8.7 version of TWRP, but since the primary maintainer for my Otus CM12.1 and CM13 ROMS (@squid2) also creates the build of TWRP and has included in his 3.0.2 version some forward fixes that might be better for CM13 especially where encryption is used, I have been updating it. A consideration in this regard is; what if it was not the different version of TWRP that caused this but rather a one-time instance of something that went wrong in the act of flashing it - which I would be more at risk of because I do occasionally update TWRP.
Hmmmm...I did recently restore a nandroid of stock Moto L 5.0.2 then flashed stock recovery in an attempt to install a pending L5.1 OTA (Moto finally released it!) which failed AFAIK due to unlocked bootloader, then I flashed TWRP 3.0.2 and restored a CM12.1 nandroid. If that was a factor it merely planted the seed of the problem but did not grow into the problem until some other later action .
[] AL [] said:
As for apps, what I find strange is that even a format didn't fix things up with it.
Click to expand...
Click to collapse
The drive became un-writable in every way including the ability to format or change any properties of the drive in any drive/partition manager even though the data was all there in perfect shape. Ironically the problem with the drive is now protecting the data
[] AL [] said:
...I would hope to believe that a file explorer alone can not mess it up THAT much alone...
Click to expand...
Click to collapse
Likewise but at this point it would not surprise me considering that Android is a bit fast and loose with more basal aspects of the system including drive management.
Ultramanoid said:
I've used extensively SanDisk 64 GB microsdxc cards with Android. Given all the information you've given, I'd lean towards physical card failure.
It happens. In my experience, very rarely, but it does.
If the same thing happens again to another of your cards anytime soon, that's when you should start a serious investigation about it.
To be honest I've had more smartphones failing on me for a myriad different reasons in the last few years than problems with a card from a reliable manufacturer.
I have washed some of these cards in the washing machine by mistake, and I've used some intensively non-stop every single day for two or three years without an issue. I've run OSes from them often, and always replaced them for another because of speed or space concerns, very rarely because of failure.
They are incredibly resilient. And yet sometimes ( again, rarely ) one will spit input / output errors, or simply die on me, no matter what the format, filesystem, or OS. In fact it happened once with a brand new card that I had just used for a couple of weeks, the irony...
Click to expand...
Click to collapse
Good points. Thanks! I've had similar experiences with Micro SDs surviving through accidental washings as well as heavy use as USB boot drives running various utilities or Linux distributions (one of which had a persistent cache cache right on the card - thats a lot of read/writes) and I can't remember encountering a corrupted SD card that was not physically damaged.
That being said I did once support an outdoor system of over 300 units each of which ran off of a proprietary Linux system on an 8GB SD card where SD card corruption was not uncommon but those "devices" were exposed to thermal extremes, traffic vibrations, and poor quality field work and remote management the likes of which our devices rarely experience.
At first I was leaning toward SD card corruption but now wonder if this was an accidental digital write-protect, perhaps caused by an extremely localized bit of SD card corruption... or something like that... and that is an area where android is faster and looser than many other device/OS combinations.
What is the result of fsck with Linux ?
Ultramanoid said:
What is the result of fsck with Linux ?
Click to expand...
Click to collapse
Similar to Windows chkdsk; In Ubuntu 14.x Live USB boot, fsck (supposedly) reclaims lost clusters, and reports "free cluster summary wrong...". When option to fix is selected the command cannot gain write access to the drive. Re-scan verifies same errors persist.
Here's an idea that worked for me once with a card that refused to be formatted on Linux and OS X; try with a digital camera or DSLR, you may need a micro to SD adapter.
In that case though, mine was a defective card indeed. The camera did format it, and was usable for a little while, before giving errors again, and I discarded it definitely.
Edit : to be precise, the camera did not recognize it and offered to format it ( to FAT being an old DSLR, but a new camera might go for exFAT, and you already suspect foul play because of exFAT ), which worked, and then I could format it again ( ext4 ) in Linux. As mentioned, the card failed again soon afterwards anyway.
Ultramanoid said:
Here's an idea that worked for me once with a card that refused to be formatted on Linux and OS X; try with a digital camera or DSLR, you may need a micro to SD adapter.
In that case though, mine was a defective card indeed. The camera did format it, and was usable for a little while, before giving errors again, and I discarded it definitely.
Edit : to be precise, the camera did not recognize it and offered to format it ( to FAT being an old DSLR, but a new camera might go for exFAT, and you already suspect foul play because of exFAT ), which worked, and then I could format it again ( ext4 ) in Linux. As mentioned, the card failed again soon afterwards anyway.
Click to expand...
Click to collapse
I tried that yesterday in a relatively new camera that is supposedly capable of handling 64GB SDXC but the camera reports that the card could not be used but offered not other information.
As to exFAT - this correction to my initial assessment of the situation: The reason Windows 7 only offers NTFS and exFAT as formatting options is not necessarily because the drive is damaged or had a read only flag applied (although both off those thing now seem likely*) but rather because Windows 7 cannot format USB drives over 32GB as FAT32 even though it can mount and use them if they were formatted elsewhere. This does not really change things other than meaning that the available Windows formatting options are not informative.
* I just called SanDisk support and learned that the card supposedly has some sort of data preservation feature where; when an imminent potential failure is detected the card is indeed digitally write protected. This might mean that there is a way to undo the digital protection although that would put the data risk and the protection is non-standard as the Windows Diskpart command line utility does not show the disk or the volume as write protected.SanDisk even offered to replace the card but I declined (for now) because I want to hack at it some more. At least there now seems to be an understandable mechanism for how this happened.
Thanks for throwing some thought into it
It's interesting, the card I mentioned was a 64GB one, but the camera formatted it to FAT creating a 32GB partition, same limit as Windows. It pretty much ignored the other half of the card that showed up just as free space, but it also undid whatever was blocking the formatting before, which may have been that protection scheme from SanDisk as in your case. Good to learn about that.
Interesting...
I have the same issue with my Samsung 64gb sd. I was moving a zip file from internal sd to external sd with ES File Explorer and all of a sudden my phone froze and I had to hard reset. When I rebooted external was screwed. I have been looking for days for a fix and have come up with nothing. TWRP can see the card but no values. Please any help would be very much appreciated because I have ALL the pictures of my 2 week old son stored in ext sd.
noob4598 said:
I have the same issue with my Samsung 64gb sd. I was moving a zip file from internal sd to external sd with ES File Explorer and all of a sudden my phone froze and I had to hard reset. When I rebooted external was screwed. I have been looking for days for a fix and have come up with nothing. TWRP can see the card but no values. Please any help would be very much appreciated because I have ALL the pictures of my 2 week old son stored in ext sd.
Click to expand...
Click to collapse
See if this helps. Read through it, it has allot of helpful information.
http://forum.xda-developers.com/showthread.php?t=1192508
noob4598 said:
I have the same issue with my Samsung 64gb sd. I was moving a zip file from internal sd to external sd with ES File Explorer and all of a sudden my phone froze and I had to hard reset. When I rebooted external was screwed. I have been looking for days for a fix and have come up with nothing. TWRP can see the card but no values. Please any help would be very much appreciated because I have ALL the pictures of my 2 week old son stored in ext sd.
Click to expand...
Click to collapse
The incident about which I created this thread was sudden as yours was. Try viewing the contents of the SD card in a card-reader on a computer. If you can see the contents and copy to the computer but cannot write to the SD card you may be experiencing the same issue describe in the OP of this thread (irreversible dirty bit write protection due to impending failure detected), in which case you would have to backup the data on the card and get a new one. Also, it is best to keep internal/adoptable storage completely out of this equation as that re-formats and encrypts the SD card.
@MatisyahuSerious
Since this was a bit OT for LOS I've expanded upon this post (https://forum.xda-developers.com/showpost.php?p=71903594&postcount=4155) here where the reply is less off topic.
Off course there are many other bad things that can happen to SD cards, and frequent ROM flashing and TiBU backups put a particular stress on them. Another factor, at least in my case, is that when a high speed SD card (eg Sandisk Ultra red/grey) is used in a USB 3 port (to move data much quicker than MTP) the SD card gets so hot that the painted logo scorches and changes color. Those thermal cycles cant be good for the cards either. I've had 3 go bad in about 6 years, one in the manner described in linked post.
A bit of somewhat related OT: For what this is worth I once supported a system which ran Linux based OS from 8GB SD cards and the most frequent fix was to replace corrupted SD cards. SD cards have gotten better, and some brands may be better than others, but they were not originally designed to handle so much fast R/W and IMO the SD industry is still catching up.