ATT SGS 3 flashed Aokp JB 64sd card not working? - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

I flashed the
[ROM] AOKP(Jellybean & ICS) Task & Ktoonsez Run a Train(8/13)(TGFY ONLINE!!! also tried [ROM][OFFICIAL] CyanogenMod 10 Preview Builds for SGH-I747 (08/10)
Today. I have a 64gb sdxc card and it's reading "Damaged card". Is this a common fix and does it have any fix?
Hope my sd card didn't get damaged...
Thanks,
Satya

You need to format it in FAT32 with EaseUS or something else...

I had the same thing happen (exfat 64G card corrupted by the attempted mount under AOKP/CM10) - really irritating. Someone claimed the card would still mount under Recovery and they could pull the contents using adb, but I had no luck with this and had to reformat (but fortunately I could reconstruct the contents). fat32 is limited to 4G file size so I stuck with exfat under a Sammy-based rom (Wanam), at least until exfat support is sorted out under CM10.

plaut said:
I had the same thing happen (exfat 64G card corrupted by the attempted mount under AOKP/CM10) - really irritating. Someone claimed the card would still mount under Recovery and they could pull the contents using adb, but I had no luck with this and had to reformat (but fortunately I could reconstruct the contents). fat32 is limited to 4G file size so I stuck with exfat under a Sammy-based rom (Wanam), at least until exfat support is sorted out under CM10.
Click to expand...
Click to collapse
FAT32 is NOT limited to 4g in size, which is why EaseUS is recommended...

BNaughty said:
FAT32 is NOT limited to 4g in size, which is why EaseUS is recommended...
Click to expand...
Click to collapse
Unless you're talking about a particular extension of FAT32 (e.g., FAT+), the maximum size of a single file is 4GB - 1 byte. The entire volume can be much larger, of course (up to 16 TB with 4096 byte sectors).

plaut said:
Unless you're talking about a particular extension of FAT32 (e.g., FAT+), the maximum size of a single file is 4GB - 1 byte. The entire volume can be much larger, of course (up to 16 TB with 4096 byte sectors).
Click to expand...
Click to collapse
Then I misread what you said, i apologize... you're right 4g file size...

Related

ICS doesn't support files bigger than 4gb?

When i tried to download 6gb movie today the torrent application said that android doesn't support files larger than 4gb at the moment.
I believe this was the case with the fat32 file system, but i'm with galaxy nexus with 16GB build in memory, so i find it hard to believe it's still with the archaic fat32? Actually what's it's file system and if the reason is somewhere else can it be fixed?
Fking1 said:
When i tried to download 6gb movie today the torrent application said that android doesn't support files larger than 4gb at the moment.
I believe this was the case with the fat32 file system, but i'm with galaxy nexus with 16GB build in memory, so i find it hard to believe it's still with the archaic fat32? Actually what's it's file system and if the reason is somewhere else can it be fixed?
Click to expand...
Click to collapse
Im just guessing here but the files are saved to your memory card. So if thats FAT32 then yeah 4GB would be your limit, you should check that first I guess
It depends entirely on the file system used on the SD card. Most SD cards are formatted Fat32, which has a file size limit of 4GB. However, on Galaxy Nexus, I believe the "SD card" is using ext3, which has a file size limitation 16GB (when using 1KB blocks). I can say with absolutely certainty that I have copied over files as large as 9GB to my Galaxy Nexus successfully.
The file system is ext4, the 'sdcard' is virtual - it's a directory on the main partition, not a seperate partition (that's why UMS isn't supported).
AFAIK no flavour of linux or unix uses fat32.
Dunno why your system won't let you go over 4Gb, it may be an error in your torrent app, or maybe its setup assumes all sdcards are fat32 and isn't actually checking...
Yeah that seems to be the most logical reason, thank you guys for the input.
Why did that thread stop there? I need to know which torrent client you are using lol. If it's the torrent client then try other ones right? Why are you currently using?
Also, i heard that changing the kernel might be the solution to the problem if it really isn't the torrent client. I wish i could elaborate more but i unfortunately don't understand what it does per say

4 gb file size limit

Hi,
I'm running into a 4 gb file size limit for hd movies. Could someone please list the options for getting around this issue on the one x?
I'm wondering which ROMS support something more modern than fat32 so that we can get around this issue.
Thanks
If they're MKVs you can always split them with something like tsMuxerGUI
It is not the limit of the Rom. It is based on partition of your ad. Formatting ad card in ntfs will allow you to store more than 4gb movie.
Sent from my HTC One X using Tapatalk 2
But my One X has no SD card. How do you proceed to format it using NTFS?
I don't think the OneX can read NTFS, so I wouldn't format it that way. Besides, I think you need S-OFF before messing around with partition formatting.
I'd just split the mkv.
jonshipman said:
I don't think the OneX can read NTFS, so I wouldn't format it that way. Besides, I think you need S-OFF before messing around with partition formatting.
I'd just split the mkv.
Click to expand...
Click to collapse
What about if I had an evo 4g lte? It has an sd card slot, which I could format with ntfs. BUt then could the evo 4g lte read it?
Changing partition has to be done on own risk. It may cause some problems. If you done and it works let us know.
I just tested and confirmed that the Evo 4G LTE supports only Fat32.
When I formatted the card to NTFS, the Evo showed a notification that the card had an unsupported filetype. When I hit "ok" to format the card, the Evo automatically formatted it back to Fat32.
Bummer, o well.
Digitalthug said:
I just tested and confirmed that the Evo 4G LTE supports only Fat32.
When I formatted the card to NTFS, the Evo showed a notification that the card had an unsupported filetype. When I hit "ok" to format the card, the Evo automatically formatted it back to Fat32.
Bummer, o well.
Click to expand...
Click to collapse
Sounds like your test just proves it doesn't like ntfs, and formats to fat32 by default. Have you tried ext3?
Not sure what the state of Windows support is these days for ext3, certainly not natively, but there used to be a couple of open source efforts.
Well the ext3 partitions on my dual-boot system from Arch Linux never showed up on Windows. I had to get another software to access those files which is a pain imo.
Try a format like exFAT, I remember it not having the 4GB file-size limit and being supported cross platform, except it never caught on much if I'm correct..

Problems Formatting SD Card/Working In Phone

I seem to be having problems formatting my Sandisk 64GB MicroSDXC (Class 10) card in FAT32 & having it work in my AT&T Galaxy S3. The card comes preformatted in exFAT, and it works in the phone just fine that way. But, I heard it's best to format it in FAT32 due to some issues I saw about some people having some of their music files not show-up (if they have a rather large music collection, which I do - 85GB's worth!) in whatever music playing program they're using, so I'm attempting to format it with FAT32 to avoid that. Now, Windows 7 (x64) does NOT allow you to format drives via FAT32 (unless you go into DOS), so I've used a couple of different programs (Fast32Format, EASEUS PartiionMaster); I got a message on my Galaxy S3 saying my SD card was damaged or missing when I used Fast32Format); a bunch of services stopped working on the phone when I formatted it using EASEUS PartionMagic, and I even tried formatting it in NTFS (which I think that Android doesn't support) & got a message my SD card was blank and Android wouldn't even mount it!
What am I doing wrong? How can I format it in FAT32 and have it work in my Galaxy S3?!! Do I even really need to use FAT32 instead of exFAT?
Thanks,
Dennis
dmw_4814 said:
I seem to be having problems formatting my Sandisk 64GB MicroSDXC (Class 10) card in FAT32 & having it work in my AT&T Galaxy S3. The card comes preformatted in exFAT, and it works in the phone just fine that way. But, I heard it's best to format it in FAT32 due to some issues I saw about some people having some of their music files not show-up (if they have a rather large music collection, which I do - 85GB's worth!) in whatever music playing program they're using, so I'm attempting to format it with FAT32 to avoid that. Now, Windows 7 (x64) does NOT allow you to format drives via FAT32 (unless you go into DOS), so I've used a couple of different programs (Fast32Format, EASEUS PartiionMaster); I got a message on my Galaxy S3 saying my SD card was damaged or missing when I used Fast32Format); a bunch of services stopped working on the phone when I formatted it using EASEUS PartionMagic, and I even tried formatting it in NTFS (which I think that Android doesn't support) & got a message my SD card was blank and Android wouldn't even mount it!
What am I doing wrong? How can I format it in FAT32 and have it work in my Galaxy S3?!! Do I even really need to use FAT32 instead of exFAT?
Thanks,
Dennis
Click to expand...
Click to collapse
EaseUS worked fine for me - the one thing that screwed me up the first time is when you tell it to format it, you also have to tell it to apply it. And hopefully the "Fast32" was autocorrect - you should just be using FAT32 - and I don't think I changed the block size. HTH
alacrify said:
EaseUS worked fine for me - the one thing that screwed me up the first time is when you tell it to format it, you also have to tell it to apply it. And hopefully the "Fast32" was autocorrect - you should just be using FAT32 - and I don't think I changed the block size. HTH
Click to expand...
Click to collapse
I apologize for bringing up this old-ish thread, but I always see that every time someone makes a new thread, they get bombarded with "use the search feature", so uhh, I did .
I've got a Class 10 SanDisk Ultra 64GB MicroSD XC card, that refuses to work with my Galaxy S3. I've got CM10 on it, do you think that might be the issue? If so, how do you think I can rectify it (what format would work?)
I've used EaseUS to delete the partition, and recreate using FAT32, but no dice, still getting a "damaged card" notification. I can seemingly use the card fine on my PC and my Mac, but nothing on the phone.
Any help would be greatly greatly appreciated
Vaesar said:
I apologize for bringing up this old-ish thread, but I always see that every time someone makes a new thread, they get bombarded with "use the search feature", so uhh, I did .
I've got a Class 10 SanDisk Ultra 64GB MicroSD XC card, that refuses to work with my Galaxy S3. I've got CM10 on it, do you think that might be the issue? If so, how do you think I can rectify it (what format would work?)
I've used EaseUS to delete the partition, and recreate using FAT32, but no dice, still getting a "damaged card" notification. I can seemingly use the card fine on my PC and my Mac, but nothing on the phone.
Any help would be greatly greatly appreciated
Click to expand...
Click to collapse
Well, this is ominous given that I ordered this micoSD and it just shipped. I read lots of reviews on Amazon and those with S3 phones seemed to have no issues using card as is, although they didn't specify precisely which version of S3 they had. The S3 natively supports 64 GB, so I would think it would work out of the box, so to speak. A number of reviewers said they used this microSD in older phones that supposedly supported only up to 32 GB. They formatted in phone, getting something like 59 GB of usable space.
I'm using stock ROM with CWM on I747.
cm10
it is an cm10 issue
mrky said:
it is an cm10 issue
Click to expand...
Click to collapse
A more complete response...its a known issue with AOSP based JB ROM's. This is pulled from the AOKP FAQ, since it is an AOSP based ROM as well this should help you out.
Will my 64 gb sd card work? Except it works fine with a 64GB card. http://rootzwiki.com/topic/28124-doe...card-standard/ The SGSIII is the first phone to support exfatl, but the support is Kernel based, some people are having trouble with the replacement kernels and exfat support. The solution is to force it to format in FAT32. http://www.online-tech-tips.com/comp...ive-to-fat-32/ I know, because I've done it. --- Don't respond without actually doing research. I have no problem spoon feeding information, especially when the information you put out there can increase misinformation. The SGSII also supports a 64GB card as well. http://androidforums.com/samsung-gal...ing-sgsii.html naturefreak85l;
EDIT - Apparently the links are dead, but there a many methods to choose from to format and SD in FAT32.

[Q] 64GB SD card on CM10.1

I recently bought a 64GB SanDisk Ultra MicroSDXC card and right after I got it, I started to play around with it.
Like I knew, stock-CM10.1 doesn't support exFat, but I decided to just plug the card in and watch if the phone would suggest me to format it to compatible format. But nothing happened. So I went to Settings->Storage, and boom, force close.
I thought that maybe it was just impossible to format the card on android, so I formatted it on Windows (to fat32) but no luck. Still fc when I try to go to Storage Settings.
Next thing I tried was recovery-mode:
-fat32 in koush's touch recovery -> cannot mount external_sd
-exFat in PhilZ's "exFat compatible recovery" -> the same thing
Then I really began to think that this whole damn card wasn't supported at all. So I tried one more time.
Clean CM10.1 flash, a try with fat32 and exFat, and after that (and after 0 successful attemps) those both formats one at a time with RedPill kernel.
And nothing worked.
But one of my attempts was not very far from success: when I was on stock fresh CM10.1, I also tried Paragon's app for mounting NTFS-partition and it actually worked. The app itself confirmed that "partition was mounted and it was nearly 60GB large". But in settings and in file managers the card wasn't recognized.
The second odd thing that I noticed (actually because of a half-accident) was that if I formatted the card to fat32 BUT set the size of the partition to exactly 32GB the card was up and running perfectly.
So my questions are:
Is there someone who has 64GB sdcard working perfectly on AOSP rom? And if yes, what is your setup?
Is it some kind of bug in CM10.1/even in all AOSP-roms out there that cards over 32 gigs don't show up at all? And if it is just a bug can we expect it to be fixed in near future?
Or is Touchwiz based rom the only solution?
And if someone is asking what software I used to format the card on Windows I tried:
- fat32format
- HP USB Disk Storage Format Tool
- EASEUS Partition Master
- and of course stock Windows' format tool
And what formats I tried:
- fat32
- exFat
- NTFS
- ext4
Thanks in advance
I have the same sd card working on tw and aosp. I had to plug it into the computer and google formatting exfat 64 micro sd cards and youll find an app online. Download it to your comp and itll guide you through the rest. 10mins at max is all it should take. Hope it helps
Sent from my SGH-T889 using xda app-developers app
Do you remember what aosp roms/kernels have you used while the card has been working as it should?
And do you have any clue what was that app you used to format your card?
4rm45 said:
Do you remember what aosp roms/kernels have you used while the card has been working as it should?
And do you have any clue what was that app you used to format your card?
Click to expand...
Click to collapse
I'll get on my computer tomorrow and tell you. But as far as ROMs and kernels, since I formatted my SD card to fat32 I use it for both tw and aosp roms from miui, to aokp, jellybam and all tw ROMs. Once your formatted properly it'll work for any ROM and kernel
?Finsh Him?
rambo8987 said:
I'll get on my computer tomorrow and tell you. But as far as ROMs and kernels, since I formatted my SD card to fat32 I use it for both tw and aosp roms from miui, to aokp, jellybam and all tw ROMs. Once your formatted properly it'll work for any ROM and kernel
?Finsh Him?
Click to expand...
Click to collapse
Okay, good, thanks
EDIT:
Thank god, I got it working. When I downloaded and installed MiniTool Partition Wizard to my computer I noticed that somehow the whole partition of the sd card was changed to logical instead of primary. I simply formatted it to primary fat32 partition and now it works, finally.
And last but not least I have to say a big thank you.

[Q] Error writing to 64gb card

I'm using the 7 inch model and it writes to the 32 gig card, but it will not write to my 64 gig. I've tried various formats (NTFS, FAT, FAT16, FAT32, maybe a few others) and it will read the 64 but will not write to it. Anyone know why this is?
Try exFAT.
ketut.kumajaya said:
Try exFAT.
Click to expand...
Click to collapse
I tried that last night. No luck. I put the card in and view it in the storage part of settings. It displays 62.5 gb available. Then I try to create a folder or move something over to it, and I get a message saying could not write file. Then I looking in the storage part of settings again and it says 0.00 b available. For some reason it wants to read the drive as full when it is empty. I don't have it rooted yet. Does that matter?

Categories

Resources