Need 64GB Driver. - Galaxy S III Q&A, Help & Troubleshooting

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.