I was previously using a UHC-1 speed 64GB MicroSD card in the MicroSD card slot on my TF101. This worked great in ASUS stock ICS, and also ASUS stock ICS w/ Guevor kernels. I decided to try out a few JB builds. So far, every JB build, and combination of kernels that I have tried does not allow me to read this card. I can read a smaller 4GB card just fine. Even if I put it in an adapter and stick it in the dock SD card slot, it still won't read. After verifying that I could still read it on my PC, I even reformatted the card as exFat from a PC, and that still yielded no success in reading it on the TF101.
To date, I've tried the official CM10 nightlies and EOS3 (with KAT 1.0.1 and Harmony JB kernel). None of these combinations, on any of the revisions (I tried back-dated versions also) seem to work with the card. It shows it present, but it can't mount it.
Anybody care to throw a stab at what may be going wrong?
I searched around a bit, and nobody has stated any such problems. (That or my google-fu is lacking)
I would hate to have to go back to ICS after going through all this trouble.
(Yes, I wiped, and wiped, and wiped, and wiped again. I even cleaned the entire user data section as well as everything else, I even reflashed things from scratch from the PC).
Sent from my Transformer TF101 using Tapatalk 2
ryocoon said:
I was previously using a UHC-1 speed 64GB MicroSD card in the MicroSD card slot on my TF101. This worked great in ASUS stock ICS, and also ASUS stock ICS w/ Guevor kernels. I decided to try out a few JB builds. So far, every JB build, and combination of kernels that I have tried does not allow me to read this card. I can read a smaller 4GB card just fine. Even if I put it in an adapter and stick it in the dock SD card slot, it still won't read. After verifying that I could still read it on my PC, I even reformatted the card as exFat from a PC, and that still yielded no success in reading it on the TF101.
To date, I've tried the official CM10 nightlies and EOS3 (with KAT 1.0.1 and Harmony JB kernel). None of these combinations, on any of the revisions (I tried back-dated versions also) seem to work with the card. It shows it present, but it can't mount it.
Anybody care to throw a stab at what may be going wrong?
I searched around a bit, and nobody has stated any such problems. (That or my google-fu is lacking)
I would hate to have to go back to ICS after going through all this trouble.
(Yes, I wiped, and wiped, and wiped, and wiped again. I even cleaned the entire user data section as well as everything else, I even reflashed things from scratch from the PC).
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
I think it has to be fat32 formatted to be seen, at least in recovery. I believe the JB ROMs are currently unable to read NTFS, not sure about exFat.
sidneyk said:
I think it has to be fat32 formatted to be seen, at least in recovery. I believe the JB ROMs are currently unable to read NTFS, not sure about exFat.
Click to expand...
Click to collapse
Yeah you're usually safe just sticking with FAT32.
But if you get too frustrated at that SD card, I'd be glad to take it off your hands for you, haha.
ryocoon said:
I was previously using a UHC-1 speed 64GB MicroSD card in the MicroSD card slot on my TF101. This worked great in ASUS stock ICS, and also ASUS stock ICS w/ Guevor kernels. I decided to try out a few JB builds. So far, every JB build, and combination of kernels that I have tried does not allow me to read this card. I can read a smaller 4GB card just fine. Even if I put it in an adapter and stick it in the dock SD card slot, it still won't read. After verifying that I could still read it on my PC, I even reformatted the card as exFat from a PC, and that still yielded no success in reading it on the TF101.
To date, I've tried the official CM10 nightlies and EOS3 (with KAT 1.0.1 and Harmony JB kernel). None of these combinations, on any of the revisions (I tried back-dated versions also) seem to work with the card. It shows it present, but it can't mount it.
Anybody care to throw a stab at what may be going wrong?
I searched around a bit, and nobody has stated any such problems. (That or my google-fu is lacking)
I would hate to have to go back to ICS after going through all this trouble.
(Yes, I wiped, and wiped, and wiped, and wiped again. I even cleaned the entire user data section as well as everything else, I even reflashed things from scratch from the PC).
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
Did you ever get a solution? I just got a 64gb UHS-1 card and am having all types of problems with accessing it. I am using KatKiss 4.3_029. I started getting no access to write access errors in TB, and copying files to it would just stop and say the disk might be full. I reformatted it exFAT using the SDFormatter tool on a PC, and wrote many fles to it on PC with no problems, but on ANdroid am seeing 0 byte files and all kinds of weirdness. I fixed permissions, I Edited the platform.xml file's WRITE_EXTERNAL_STORAGE permission. Before doing the exFAT format, I had tried formatting in TWRP. None of these things fixed my problem. I even have the problems when installed in the dock in an SDCArd adapter.
Does anybody have any other ideas?
I formatted my 64GB card as vfat within Linux and I think I did it while it was in my card reader front panel. Now I have 63GB of storage that works in twrp and 4.4.2.
Sent from my SM-N900T using XDA Premium HD app
bradysd4 said:
Did you ever get a solution? I just got a 64gb UHS-1 card and am having all types of problems with accessing it. I am using KatKiss 4.3_029. I started getting no access to write access errors in TB, and copying files to it would just stop and say the disk might be full. I reformatted it exFAT using the SDFormatter tool on a PC, and wrote many fles to it on PC with no problems, but on ANdroid am seeing 0 byte files and all kinds of weirdness. I fixed permissions, I Edited the platform.xml file's WRITE_EXTERNAL_STORAGE permission. Before doing the exFAT format, I had tried formatting in TWRP. None of these things fixed my problem. I even have the problems when installed in the dock in an SDCArd adapter.
Does anybody have any other ideas?
Click to expand...
Click to collapse
I eventually switched over to KatKiss on my TF101, but I also now use a TF701. exFAT, in general, does not work for auto-mount. Mostly due to licensing restrictions and stupidity like that for the core of the OS. You can format a 64GB card as FAT32, but you need a special tool to do it, as Windows won't let you format anything over 2GB as FAT32, and instead switches to vFAT/exFAT or NTFS, which are... less compatible and will not auto-mount. Now, I would have to go back and look at my TF101 device, but I lost the MicroSD from it (which was sad, as it had tons of pictures from a DSLR I took during a trip that not all had been cloud backed-up when I lost it). So more recent KatKiss kernels/ROMs may be able to auto-mount exFAT or vFAT along with older FAT32. NTFS will never auto-mount it seems (at least not as read/write), but can be mounted read/write if you have the right kernel or tool combination.
Also, I've never had the formatter in either CWM or TWRP work properly since the days of the OG Droid (Motorola Milestone A855).
ryocoon said:
I eventually switched over to KatKiss on my TF101, but I also now use a TF701. exFAT, in general, does not work for auto-mount. Mostly due to licensing restrictions and stupidity like that for the core of the OS. You can format a 64GB card as FAT32, but you need a special tool to do it, as Windows won't let you format anything over 2GB as FAT32, and instead switches to vFAT/exFAT or NTFS, which are... less compatible and will not auto-mount. Now, I would have to go back and look at my TF101 device, but I lost the MicroSD from it (which was sad, as it had tons of pictures from a DSLR I took during a trip that not all had been cloud backed-up when I lost it). So more recent KatKiss kernels/ROMs may be able to auto-mount exFAT or vFAT along with older FAT32. NTFS will never auto-mount it seems (at least not as read/write), but can be mounted read/write if you have the right kernel or tool combination.
Also, I've never had the formatter in either CWM or TWRP work properly since the days of the OG Droid (Motorola Milestone A855).
Click to expand...
Click to collapse
OK, I reformatted to FAT32 last night using Easus disk partition software on Windows, re-copied a bunch of files to it, but haven't had a chance to test it yet. I couldn't get mini-tool partition software (which others had mentioned using) to work on Win8.1. If that doesn't fix it, I may try to get it replaced by mfg.
UPDATE: It seems like that (reformat with easus to FAT32) fixed it. No problems today. Yay! Back to 64gb MicroSD.
bradysd4 said:
OK, I reformatted to FAT32 last night using Easus disk partition software on Windows, re-copied a bunch of files to it, but haven't had a chance to test it yet. I couldn't get mini-tool partition software (which others had mentioned using) to work on Win8.1. If that doesn't fix it, I may try to get it replaced by mfg.
Click to expand...
Click to collapse
I didn't use any partition manager software (if I was on linux, possibly, but I'm rockin' the Win 8.1 on my box at the moment, other systems in storage). I used a command line tool for formatting FAT32, it is GPL and such. Located at http://www.ridgecrop.demon.co.uk/fat32format.htm .
It seemed to work pretty well, but you have to decipher the command line options a bit.
Related
I am the following setup on my Charge
Voodoo based kernel; regular and over clock
Sd card read fix patch
EE4 fully stock up to date
CWR 4.x.x.04 - the one without voodoo options
This is my second incident with card going bad. The first time I used it for two weeks and card became unreadable. Tried reformat from the phone and on CWR level without any success.
On second ocasion phone worked also two weeks without any issues - till I suddenly got on power up "bad card" pop up. Tried to reformat - failed.
I booted into CWR and to my surprise I was able to browse the card. I deleted cache, Davlik, boot part, reapplied voodoo and ovclock kernels, reapplied card read error pathch - in all possible sequences without much susccess. I do not have voodoo controls under my version of CWR (too bad) and since I do not have memory card - I cannot download and install 3rd party voodo control to try to enable and disable and see if it makes a difference.
I am without access to my pc for a week so Odin or repartitioning lwith pit file and full stock reflash are not an option for me right now. I tried mount SD on a windows machine - without much success as it sees is un formatted. CWR sees it without issues and let's me reflash kernel and patch zips.
I am sure that I will get it working eventually - but would like to ask our opinion AFAYK what is going on? I hate having to lose my cards with pics and data with is not backed up regularly. This is my first device I lost an SD card.
I am assuming that it is related to the voodoo Linux based file system. do you think running a full stock on a voodoo has anything to do with it?
Thanks in advance
i was under the impression that the "Sd card read fix patch" wasn't needed any more.
You might have a bad device that keeps toasting your cards. Have you tried viewing your card in a Linux machine?
Sent from my GT-P1000 using XDA App
I have tried both ways - with and without the patch
You said you were able to mount your sd on a windows machine. Any reason you can't use that machine and odin off of it? Its just a quick download away.
I do not have access to a linux box. Factory reset, Odin and options under CWR are the only options that I usually use. Can I test my phone without a Linux box?
I was just thinking Linux might try to force read it since it ignores file permissions etc. Also, you can't format the SD card within CWM.
Sent from my GT-P1000 using XDA App
It was not my computer - I just wanted to test if i can see sd card on a wintel box. In the long run I do not mind doing the pit file with full stock flash - I just do not want to find myself burning more cards
If you fix it and it does it again i would definitely go to a Verizon store and have it checked out.
Sent from my GT-P1000 using XDA App
Use a small sd card sufficient enough to do everything you want to. If it happens again take it to verizon fully stock and they should replace the phone and SD.
Just to add more to the puzzle
I have second Charge absolutely the same setup.
When I tried to load SD card that is unreadable on the original Charge on the phone level
- I get the same damaged card error.
CWR on both phones can read it.
Just out of curiosity, are these 32gb cards?
Android has a known issue with 32gb cards getting corrupted if they are not formatted with a 32kb allocation size.
The workaround is to re format the card with your windows PC to FAT32, 32kb allocation size. Do a full format, not the quick format.
The two cards that got damaged are leftover cards from my fascinates. 16GB. One of them was reformatted and the other one was not - just reused it the moving all files from root folder to a folder called "Old" ( while mounted on my pc)
I used to be on an non Voodoo kernel/rom on my fascinates, when I installed voodoo kernel on Charge - file system got converted (per female voice)
Apparently I am not the only one with this problem
I stumbled upon this
http://forums.androidcentral.com/verizon-droid-charge/111200-wiping-sd-card.html#post1179362
Looks like that reusing a 16 GB card from fascinate is the issue in both instances.
I am still eager to learn what is the issue?
@Racer
Is it related to a different block size that is used by Samsung to format SD s on Charge? do you have more details on it? Do you know if I can possibly salvage my cards?
garryo said:
@Racer
Is it related to a different block size that is used by Samsung to format SD s on Charge? do you have more details on it? Do you know if I can possibly salvage my cards?
Click to expand...
Click to collapse
It is a problem with the interaction between android and some firmwares in the sdhc cards. It isn't really something that is Samsung specific.
I did some research on it and it solved my problem (similar to yours) that I had with my PNY 32gb class 10 card.
I would definitely try formatting your cards with a windows pc, full format, fat32, 32kb allocation size before I gave up on them.
here are some links:
http://forum.xda-developers.com/showthread.php?t=1010228
http://www.patriotmemory.com/forums...-LX-Series-MicroSD-Problems-on-Android-phones
So I've been looking around for help on this across various sites and I've had no luck fixing my problem.
I'm running the most recent CM10 nightlies, which I read might influence which formats the phone can read, and even after I formatted the card to FAT32 via the gui app and easeUS partition editor my phone still says my card is damaged. When I try to format it it just says "unmounting card" with the spinning circle and sits there, never unmounting and formatting like it wants to. I tried to mount/unmount and format in CWM, no dice. This card is brand new out of the package today so there's been no previous use or problems.
Am I just going to be unable to use this card while running CM10, would I have to go back to a TW ROM or stock to make it read correctly? It will show up on my computer when I plug it in and files transfer to it fine so I figure it's a problem on the phone's side. My old 16gb card from my DX works fine and that's what I'll use in the meantime but the space is dangerously low, hence why I jumped on this 64gb card when it was an Amazon deal.
If anyone has some insight or experience with this I'd really appreciate it, I'm guessing it's a problem with CM10 or I missed some tiny step somewhere but I've tried a lot and had no success.
weavethesource said:
So I've been looking around for help on this across various sites and I've had no luck fixing my problem.
I'm running the most recent CM10 nightlies, which I read might influence which formats the phone can read, and even after I formatted the card to FAT32 via the gui app and easeUS partition editor my phone still says my card is damaged. When I try to format it it just says "unmounting card" with the spinning circle and sits there, never unmounting and formatting like it wants to. I tried to mount/unmount and format in CWM, no dice. This card is brand new out of the package today so there's been no previous use or problems.
Am I just going to be unable to use this card while running CM10, would I have to go back to a TW ROM or stock to make it read correctly? It will show up on my computer when I plug it in and files transfer to it fine so I figure it's a problem on the phone's side. My old 16gb card from my DX works fine and that's what I'll use in the meantime but the space is dangerously low, hence why I jumped on this 64gb card when it was an Amazon deal.
If anyone has some insight or experience with this I'd really appreciate it, I'm guessing it's a problem with CM10 or I missed some tiny step somewhere but I've tried a lot and had no success.
Click to expand...
Click to collapse
What exactly is the partition editor you used, and why? The GUI program to format it to fat32 is sufficient...
I would guess either it's the card(what brand btw?) or the partition editor.
Brian Gove said:
What exactly is the partition editor you used, and why? The GUI program to format it to fat32 is sufficient...
I would guess either it's the card(what brand btw?) or the partition editor.
Click to expand...
Click to collapse
It's the "SanDisk Ultra 64 GB microSDXC Class 10 UHS-1 Memory Card 30MB/s with Adapter SDSDQUA-064G-U46A", I've noticed a lot of GS3 owners have been buying something similar or the same.
I used EaseUS Partition Master as well as the fat32 gui program that's been circulating, sounds like you know the one, and while the format was successful the phone still sees the card as damaged and won't completely unmount the card when I try to format it like it says.
You try formatting it on a windows computer
Sent from my SCH-I535 using xda app-developers app
Jarredw said:
You try formatting it on a windows computer
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yeah I'm using Windows 7
weavethesource said:
Yeah I'm using Windows 7
Click to expand...
Click to collapse
use this program linked below for formatting to
fat32.
http://www.ridgecrop.demon.co.uk/index.htm?fat32format.htm
weavethesource said:
It's the "SanDisk Ultra 64 GB microSDXC Class 10 UHS-1 Memory Card 30MB/s with Adapter SDSDQUA-064G-U46A", I've noticed a lot of GS3 owners have been buying something similar or the same.
I used EaseUS Partition Master as well as the fat32 gui program that's been circulating, sounds like you know the one, and while the format was successful the phone still sees the card as damaged and won't completely unmount the card when I try to format it like it says.
Click to expand...
Click to collapse
That's there exact same card I got. Format it again with the gui but DON'T use the partition program. I guarantee that's what is messing you up.
Brian Gove said:
That's there exact same card I got. Format it again with the gui but DON'T use the partition program. I guarantee that's what is messing you up.
Click to expand...
Click to collapse
Did you use the sd adapter to plug into the computer or you did it while it was inserted in the phone already? I did the latter, idk if buying an sd slot to usb would change anything.
I am having the same problem. I thought I had a bad card, so I sent it back. Now I am searching for a solution as well. I will give this a try later tonight.
weavethesource said:
Did you use the sd adapter to plug into the computer or you did it while it was inserted in the phone already? I did the latter, idk if buying an sd slot to usb would change anything.
Click to expand...
Click to collapse
I used the adapter and put it directly in my computer to format it.
Brian Gove said:
I used the adapter and put it directly in my computer to format it.
Click to expand...
Click to collapse
Ah ok, looks like I'll have to buy an sd-usb plugin then.
Had the same issue on two different cards and eventually they said that they were an unsupported raw format. Called sandisk and they said there are a lot of issues with the 64gb class 10 cards and the SGSIII. I am on my third one. This one has been working almost perfectly. I often get a unmounting remounting issue with the card, but I am not blaming the card yet as ever since I flashed the cracked aboot I have been having odd issues. I am going to put my phone back to stock and start over here today or tomorrow.
Sent from my SCH-I535 using xda app-developers app
I fixed it
I bought a multi-SD plug-in with USB, slid my card in there, ran the gui on the card, put the card back in my phone and it worked fine, the phone recognizes it. For whatever reason the card didn't want to format while it was in the phone despite my manipulations, so plugging the SD into the computer is crucial I think.
Thanks for the support guys.
I have done everything described here, and still have what the OP says. Card is not recognized, like its not even plugged in to the phone, is formatted as FAT32 and works in windows.
sparkerjc said:
I have done everything described here, and still have what the OP says. Card is not recognized, like its not even plugged in to the phone, is formatted as FAT32 and works in windows.
Click to expand...
Click to collapse
Well, I literally fought this for 3 hours, and finally I just deleted the entire partition and formatted the card in the stock ROM. Then I pulled the card and formatted with EaseUS partitioner as FAT32 and put it back in and it worked. Then I flashed back to CM10 and it still works.
How frustrating this is....
After quite a bit of researching + trial and errors, I'm kind of stumped on this one...
Basically what I'm trying to do is get a 128GB SDXC card recognized in a Verizon Galaxy S3 [(via SD to Micro SD cable (NOT OTG)].
However it comes up as Blank SD card or unsupported format.
It reads perfectly fine on my HTC Thunderbolt running ROM version "liquid.mecha.20111118.145810" with "imoseyon-6.2.1AOSP" kernel.
Also reads perfectly on HTC Sensation running PARANOIDANDROID
Steps I've tried:
- Format Card: fat32, ntfs, exfat, ext3, ext4 (via EaseUS Partition Master) - Comes up as Blank SD card or unsupported format.
- Also tried all available allocation unit size for fat32 - Still the same thing
- Tried formatting on the S3 itself - Still the same thing
- Tried formatting on the Thunderbolt and transferring the card over - Still the same thing
ROM's Tried:
- Stock VRALG1
- Stock VRALF2
- Stock Root VRALHD DE-ODEX
- Stock Root VRALHD ODEX
- Incubus26jc_JellyWiz_VZW_10_10_12_RLS9_Note2_Edition
- Liquid-JB-v2.0-RC4-d2vzw
- Bean's Custom Stock Rom Build 14
- CleanROM 2.5
- CleanROM Ultra Lite Edition
- cm-10-20121005-NIGHTLY-d2vzw.zip
- PARANOIDANDROID 2.18
- Slim Bean 2.6.0
- Synergy Oct-03 0416_r73
All comes up as Blank SD card or unsupported format.
Here's a picture of the thunderbolt and the cable. It runs into the MicroSD card slot in the back of the phone.
(Since I can't add pictures yet due to post count, just add http in the beginning)
://imgur.com/LG2vA
://imgur.com/tG4yt
I sure hope it's not a limitation just on the S3 itself.
I'm going to go back and try different ROMs on my thunderbolt to see if it's related to a specific ROM or kernel, then probably proceed to testing different phones.
However any type of feedback is greatly appreciated :fingers-crossed:
Bump
Great effort! I hope you'll keep us posted on your progress.
Perhaps Samsung is intentionally blocking cards larger than 64GB on these phones. Have you tried apps such as NTFS mounter and tried mounting the card with other file systems such as NTFS/EXT3/4 etc? Maybe this will get around any space restrictions that Samsung may have imposed on the Android file system. But it seems like you already have.
Perhaps this thread may help out as well:
http://forum.xda-developers.com/showthread.php?t=1797499
It would be interesting to see what SDXC controller the S3 uses. If it is the same as on a phone where the 128GB card works perhaps it may be possible to patch the S3 with the driver in the other phone.
You should try different kernels, not ROMs
g00ey said:
Perhaps Samsung is intentionally blocking cards larger than 64GB on these phones. Have you tried apps such as NTFS mounter and tried mounting the card with other file systems such as NTFS/EXT3/4 etc? Maybe this will get around any space restrictions that Samsung may have imposed on the Android file system. But it seems like you already have.
Perhaps this thread may help out as well:
http://forum.xda-developers.com/showthread.php?t=1797499
It would be interesting to see what SDXC controller the S3 uses. If it is the same as on a phone where the 128GB card works perhaps it may be possible to patch the S3 with the driver in the other phone.
Click to expand...
Click to collapse
Glebun said:
You should try different kernels, not ROMs
Click to expand...
Click to collapse
Thanks for the suggestions.
Yes I already tried using NTFS mounter with all the other file systems, nothing was being detected or coming up at all. Maybe NTFS mounter is targeted more towards OTG connection, not too positive on that one.
I forgot to mention I did try different kernels. Whichever came with the ROMs and including KT747, Lean, and Trinity (also the variants with touchwiz and AOSP).
I've also gotten around to testing the Samsung S3 variants on T-Mobile, AT&T, and Sprint... None of them detected the card.
However a friend of mines lent me his Korean variant S3 (SHV- E210S with Exynos) and that phone detected the card perfectly fine.
Phones that also were tried were: LG Spectrum, Galaxy S2 (International), myTouch 4G. All of them detected the card even in recovery.
*I don't believe it's kernel related, if all the other phones were able to detect it in recovery...
I also contacted Samsung via e-mail but they weren't much supportive on the whole topic. Just a simple answer of the Galaxy S3 was never meant to support anything above 64GB (in which I find that untrue with the Korean variants at least).
I'm about out of ideas on what left there is to try... hopefully someone can come up with something.
I really liked the S3 but having a 128GB memory card sitting around would be a waste.
Going to test on my friends Note II since Verizon is going to be getting their own also, then will probably just ships.
Hopefully my information has helped someone.
Have you tried a small capasity SD card to see if it has to do with the connection or if it has to do with the size?
kris333 said:
Have you tried a small capasity SD card to see if it has to do with the connection or if it has to do with the size?
Click to expand...
Click to collapse
I believe it would just be the size issue on the S3. 64GB SDXC works fine. 128GB does not.
Shouldn't have anything to do with card or connection if it worked on 5+ other phones.
BattousaiJimmy said:
After quite a bit of researching + trial and errors, I'm kind of stumped on this one...
Steps I've tried:
- Format Card: fat32, ntfs, exfat, ext3, ext4 (via EaseUS Partition Master) - Comes up as Blank SD card or unsupported format.
- Also tried all available allocation unit size for fat32 - Still the same thing
- Tried formatting on the S3 itself - Still the same thing
- Tried formatting on the Thunderbolt and transferring the card over - Still the same thing
Click to expand...
Click to collapse
I am very interested in the outcome of this
Getting a 128Gb SD card working in the S3 would be awesome!
Have you tried 2 64Gb FAT32 partitions? or maybe several smaller partitions.
Maybe even just a single 64Gb partition
My 2c
Ben
Has anyone figured this out? I just bought the converter and a 128GB SDXC card. At first I was on the TW Jellybean K3 11B ROM I hooked it up without formating and the ROM recognized it as 120GB. So I plugged it into my PC to throw some files on it some ROMs and back ups etc, then I put it back in my phone went into recovery to flash a ROM that I put on the card and it was taking forever? As if the converter cable was slowing down the speed? So anyways I ended up flashing a aosp ROM of of my micro SD card (Carbon 4.2.2) then I plugged my converter with the 128gb card back in but the ROM wouldn't recognize it? So I tried formatting it in recovery and on the ROM but I'm still having no luck?? Any Suggestions or ideas how to get it to work? Thanks!
Sent from my SCH-I535 using Tapatalk 2
If you will scroll down or search, there is already a thread on this and the OP got it to work. The name of the thread is "Will this give me more memory?"
HHF2 said:
If you will scroll down or search, there is already a thread on this and the OP got it to work. The name of the thread is "Will this give me more memory?"
Click to expand...
Click to collapse
Yea that's my thread. I found this thread trying to get my phone to recognize my SD card?
Sent from my SCH-I535 using Tapatalk 2
My bad, I didn't pay attention to the usernames since I thought yours was working.
BattousaiJimmy said:
After quite a bit of researching + trial and errors, I'm kind of stumped on this one...
Basically what I'm trying to do is get a 128GB SDXC card recognized in a Verizon Galaxy S3 [(via SD to Micro SD cable (NOT OTG)].
However it comes up as Blank SD card or unsupported format.
It reads perfectly fine on my HTC Thunderbolt running ROM version "liquid.mecha.20111118.145810" with "imoseyon-6.2.1AOSP" kernel.
Also reads perfectly on HTC Sensation running PARANOIDANDROID
Steps I've tried:
- Format Card: fat32, ntfs, exfat, ext3, ext4 (via EaseUS Partition Master) - Comes up as Blank SD card or unsupported format.
- Also tried all available allocation unit size for fat32 - Still the same thing
- Tried formatting on the S3 itself - Still the same thing
- Tried formatting on the Thunderbolt and transferring the card over - Still the same thing
ROM's Tried:
- Stock VRALG1
- Stock VRALF2
- Stock Root VRALHD DE-ODEX
- Stock Root VRALHD ODEX
- Incubus26jc_JellyWiz_VZW_10_10_12_RLS9_Note2_Edition
- Liquid-JB-v2.0-RC4-d2vzw
- Bean's Custom Stock Rom Build 14
- CleanROM 2.5
- CleanROM Ultra Lite Edition
- cm-10-20121005-NIGHTLY-d2vzw.zip
- PARANOIDANDROID 2.18
- Slim Bean 2.6.0
- Synergy Oct-03 0416_r73
All comes up as Blank SD card or unsupported format.
Here's a picture of the thunderbolt and the cable. It runs into the MicroSD card slot in the back of the phone.
(Since I can't add pictures yet due to post count, just add http in the beginning)
://imgur.com/LG2vA
://imgur.com/tG4yt
I sure hope it's not a limitation just on the S3 itself.
I'm going to go back and try different ROMs on my thunderbolt to see if it's related to a specific ROM or kernel, then probably proceed to testing different phones.
However any type of feedback is greatly appreciated :fingers-crossed:
Click to expand...
Click to collapse
I believe it may specifically be a limitation of the Verizon s3 version. I have a 256gb card working fine on an att Note 2, and att and tmobile s3s have been proven to work as well.
I have tried using ES file explorer, the Asus file manager, and FX file explorer. I get a copy failed message every time I try to copy a file to the removable SD card.
Anyone else have this issue?
You can't know your limits until you exceed them.
duckredbeard said:
I have tried using ES file explorer, the Asus file manager, and FX file explorer. I get a copy failed message every time I try to copy a file to the removable SD card.
Anyone else have this issue?
You can't know your limits until you exceed them.
Click to expand...
Click to collapse
Have you tried to reformat the card with fat32?
I just did. Seems I'm only having issues with the 32 GB size cards. Acting like they are read only. Can't find such a setting anywhere. Is there another format that should work?
You can't know your limits until you exceed them.
duckredbeard said:
I just did. Seems I'm only having issues with the 32 GB size cards. Acting like they are read only. Can't find such a setting anywhere. Is there another format that should work?
You can't know your limits until you exceed them.
Click to expand...
Click to collapse
Have you tried with the latest kernel (JB version .25) and what make and model of your sdcard? just wonder if compability issue and are we talking about Micro sdcard or full size sdcard? On the full size there is a little switch on the side to block writting to the card.
I'm only having issues when I'm using the tablet to copy files. I'm on CleanROM Inheritance. I don't recall if I had this issue with the stock rom. Sometime tonight I will make a backup of my current and then flash to stock rom. Since I'm talking about the removable SD card, it could only be the micro SD that is installed in the tablet. There is no switch on that card.
Sent from my HTC PH39100 using xda app-developers app
I think flashing the _that nodpi kernel should resolved your issue, give it a try.
Sent from my ASUS Transformer Pad TF700T using xda premium
Link to said kernel?
You can't know your limits until you exceed them.
duckredbeard said:
Link to said kernel?
You can't know your limits until you exceed them.
Click to expand...
Click to collapse
download this http://d-h.st/M6j then flash with twrp, during the install pick _that_nodpi_stock kernel.
That did it. Did it replace the overclock kernal I selected when I flashed CROMI 3.2?
Sent from my HTC PH39100 using xda app-developers app
duckredbeard said:
That did it. Did it replace the overclock kernal I selected when I flashed CROMI 3.2?
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
Yes, it replaced what ever kernel you selected during cleanrom installation. Since it stock kernel, you can no longer Overclock.
Is there another kernel that can be the fix and still give us over clock?
You can't know your limits until you exceed them.
duckredbeard said:
Is there another kernel that can be the fix and still give us over clock?
You can't know your limits until you exceed them.
Click to expand...
Click to collapse
Sorry but nope, I believe as soon as Asus release source code, _that is going to make an OC version for this and it's going to be awsome. For now we just have to wait.
Similar Problem With A Samsung Micro SD Card
duckredbeard said:
That did it. Did it replace the overclock kernal I selected when I flashed CROMI 3.2?
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
Hi.
I'm having a problem with my Samsung Micro SDXC I (Class 10) card. I've been messing abut with it for days now, formatting, re-formatting in exFAT, FAT32, NTFS but the problem persists; whenever I try to copy data across to the card, the first time the card is inserted, it starts to copy, sometimes even up to 1.5Gb of data but often much less, but then gives me a 'Write Error' or 'I/O Error' message & stops working. Sometimes it also deletes other data on the card when the error occurs. then, until I unmount the card again, it barely functions at all!
A big factor in buyinh this tablet, unlocking, then rooting it was so that I'd have an awesome, small, tablet that had loads of storage & could be transported around very easily. If I can't get the cards to work with it, that's a big part of it's usefulness to me down the drain.
I tried to download the kernal that was mentioned above the message of yours that I'm replying to but the file has been moved. Do you still have it?.......or know how I can resolve my problem without it?
Any help would be much appreciated.
Thanks.
dan5001 said:
Hi.
I'm having a problem with my Samsung Micro SDXC I (Class 10) card. I've been messing abut with it for days now, formatting, re-formatting in exFAT, FAT32, NTFS but the problem persists; whenever I try to copy data across to the card, the first time the card is inserted, it starts to copy, sometimes even up to 1.5Gb of data but often much less, but then gives me a 'Write Error' or 'I/O Error' message & stops working. Sometimes it also deletes other data on the card when the error occurs. then, until I unmount the card again, it barely functions at all!
A big factor in buyinh this tablet, unlocking, then rooting it was so that I'd have an awesome, small, tablet that had loads of storage & could be transported around very easily. If I can't get the cards to work with it, that's a big part of it's usefulness to me down the drain.
I tried to download the kernal that was mentioned above the message of yours that I'm replying to but the file has been moved. Do you still have it?.......or know how I can resolve my problem without it?
Any help would be much appreciated.
Thanks.
Click to expand...
Click to collapse
You don't say which rom or firmware you are currently using. Without knowing that I wouldn't go blindly flashing kernels that are nearly a year old
It could be that your card is actually damaged as I can copy files just fine on mine. I'm using a SanDisk Ultra uhs-1.
ROM & Firmware
sbdags said:
You don't say which rom or firmware you are currently using. Without knowing that I wouldn't go blindly flashing kernels that are nearly a year old
It could be that your card is actually damaged as I can copy files just fine on mine. I'm using a SanDisk Ultra uhs-1.
Click to expand...
Click to collapse
Hi sbdags,
Roger that
I'm not bad with most things tecchie but whilst I know which ROM I'm using, I'm not sure what the firmware is.
I recently updated to CROMI-X 5.2.2 from an earlier version in the hope that that might include an update or something that would solve my SD card problem.......it didn't
With regard to 'Firmware', I'm not sure where that's listed on the tablet but in the 'About' tab in my settings, it says:
Android Version - 4.2.1
Kernal Version - 3.1.10-g215ae8bf [email protected] # 1
Build Number - TF700 CHROMI-X 5.2.2 - 10.6.1.27.5 WW DEODEX
Pad EC Version - PAD-EC20T-0216
MobileDock Version - DOCK-EC20N-0207
I hope the firmware information you need is in there somewhere?
The card I bought is the latest 64Gb Samsung Micro SDXC Pro UHS-1 (Class 10) with write speeds of 20Mb/s & 70Mb transfer speed. I had read the formums & was torn between this card & the SanDisk 64Gb Ultra Micro SDXC (Class 10), the two-tone red/grey version, presumably like the one you're using but the Samsung was faster & at the time I bought it, the Samsungwas almost £15 cheaper. Since they were both reported to work, I opted for the Samsung card; maybe that was a bad decision?
I've just ordered the SanDisk 64Gb card, in the hope that that one will work because as i said, it really would be a shame if I can't make use of the extended storage that the SD crads give.
Do you use your SanDisk card in Micro SD form in the tablet or SD form in the dock.....or both......& have you got them formatted to exFAT or some other format?
Thanks again for your attention.
dan5001 said:
Hi sbdags,
Roger that
I'm not bad with most things tecchie but whilst I know which ROM I'm using, I'm not sure what the firmware is.
I recently updated to CROMI-X 5.2.2 from an earlier version in the hope that that might include an update or something that would solve my SD card problem.......it didn't
With regard to 'Firmware', I'm not sure where that's listed on the tablet but in the 'About' tab in my settings, it says:
Android Version - 4.2.1
Kernal Version - 3.1.10-g215ae8bf [email protected] # 1
Build Number - TF700 CHROMI-X 5.2.2 - 10.6.1.27.5 WW DEODEX
Pad EC Version - PAD-EC20T-0216
MobileDock Version - DOCK-EC20N-0207
I hope the firmware information you need is in there somewhere?
The card I bought is the latest 64Gb Samsung Micro SDXC Pro UHS-1 (Class 10) with write speeds of 20Mb/s & 70Mb transfer speed. I had read the formums & was torn between this card & the SanDisk 64Gb Ultra Micro SDXC (Class 10), the two-tone red/grey version, presumably like the one you're using but the Samsung was faster & at the time I bought it, the Samsungwas almost £15 cheaper. Since they were both reported to work, I opted for the Samsung card; maybe that was a bad decision?
I've just ordered the SanDisk 64Gb card, in the hope that that one will work because as i said, it really would be a shame if I can't make use of the extended storage that the SD crads give.
Do you use your SanDisk card in Micro SD form in the tablet or SD form in the dock.....or both......& have you got them formatted to exFAT or some other format?
Thanks again for your attention.
Click to expand...
Click to collapse
Well the ROM is mine so you are all good there. Lol. I only use fat32 as that is how the cards come.
Are you copying the files in esfileexplorer? Are they single files? Total size?
File Sizes
sbdags said:
Well the ROM is mine so you are all good there. Lol. I only use fat32 as that is how the cards come.
Are you copying the files in esfileexplorer? Are they single files? Total size?
Click to expand...
Click to collapse
Hi sbdags.
I've tried using both the File Explorer that was included with CHROMI-X & another one from the Play Store that I use on my phone called Astro; the same thing happens with both. As I say, the card seemed okay to begin with but all I had put on it was my Nandroid & Titanium backups (approx. 2Gb total with lots of small files included). The problems started when I tried to copy a season of a TV series onto the card to free up space on the internal SD card. It started off okay & I wasn't expecting any problems but then approx 1.5Gb, I got an I/O write error & then all the problems I described in my first post.
As an aside, the card performed best when formatted to FAT32 but according to the SD Card Association, SDXC cards come formatted as exFAT, so that's how it's currently formatted; I thought if that's how it came & it initially worked okay, maybe that would solve the issue. Again, I was wrong!
So, I'll format it back to FAT32 again but as I've already had it in that format, I wouldn't anticipate any change to the card's behaviour.
The 64Gb SanDisk card should be here in a few days, so I'll be able to report on whether that one works or not then.
Did you have to re-format yours when you first got it or are the SD Card Association talking nonsense? Oh, & you didn't say whether you're able to use your cards in both micro form in the pad &/or full-size form in the dock? Also, was the Firmware information you asked for in that mass of stuff I listed. If not, where do I find it, so I know for the next time you ask
Thanks again
dan5001 said:
Hi sbdags.
I've tried using both the File Explorer that was included with CHROMI-X & another one from the Play Store that I use on my phone called Astro; the same thing happens with both. As I say, the card seemed okay to begin with but all I had put on it was my Nandroid & Titanium backups (approx. 2Gb total with lots of small files included). The problems started when I tried to copy a season of a TV series onto the card to free up space on the internal SD card. It started off okay & I wasn't expecting any problems but then approx 1.5Gb, I got an I/O write error & then all the problems I described in my first post.
As an aside, the card performed best when formatted to FAT32 but according to the SD Card Association, SDXC cards come formatted as exFAT, so that's how it's currently formatted; I thought if that's how it came & it initially worked okay, maybe that would solve the issue. Again, I was wrong!
So, I'll format it back to FAT32 again but as I've already had it in that format, I wouldn't anticipate any change to the card's behaviour.
The 64Gb SanDisk card should be here in a few days, so I'll be able to report on whether that one works or not then.
Did you have to re-format yours when you first got it or are the SD Card Association talking nonsense? Oh, & you didn't say whether you're able to use your cards in both micro form in the pad &/or full-size form in the dock? Also, was the Firmware information you asked for in that mass of stuff I listed. If not, where do I find it, so I know for the next time you ask
Thanks again
Click to expand...
Click to collapse
I've never tried my card in the dock to be honest. Both my cards; 32GB and 64GB are SanDisk, I am not sure now what they cam in but I am using fat32 as I formatted them myself.
As for the stuff you posted I just wanted to know the rom and bootloader version. So CROMi-X 5.2.2 on 10.6.1.14.10 would have ben enough. Maybe the kernel helps too. In your case you are using the stock kernel. You may get better results on thatv4 kernel?
SD Cards & Kernels
sbdags said:
I've never tried my card in the dock to be honest. Both my cards; 32GB and 64GB are SanDisk, I am not sure now what they cam in but I am using fat32 as I formatted them myself.
As for the stuff you posted I just wanted to know the rom and bootloader version. So CROMi-X 5.2.2 on 10.6.1.14.10 would have ben enough. Maybe the kernel helps too. In your case you are using the stock kernel. You may get better results on thatv4 kernel?
Click to expand...
Click to collapse
Cheers.
So, I think I've grasped that the kernel is similar to the BIOS on a PC; is that correct?
When you say that I may get better results using _that's v.4 kernel, what improvements are you thinking I might see?
dan5001 said:
So, I think I've grasped that the kernel is similar to the BIOS on a PC; is that correct?
Click to expand...
Click to collapse
Not really, the kernel is ... the kernel. The core of the operating system. Under Windows it's ntoskrnl.exe.
You could compare the bootloader with the PC BIOS - its main function (nowadays) is to start the operating system.
I've tried formatting the sdxc-card in so many ways now. Using both diskpart. minitool partition wizard, sdformatter and easeus partition manager.
Tried using FAT32, exFat and NTFS. None of them works. When using exFat the card is recognized and the phone asks if I want to format, but nothing happens after it says it's erasing the sd card.
The card works perfectly fine in Windows formatted as exFat.
I'm running stock ICS 4.0.4 if it helps to know.
I also have a friend who is using a 64gb sdxc card on the same type of phone.
Which version he's using I do not know.
Does anyone know how to solve this?
knerlington said:
I've tried formatting the sdxc-card in so many ways now. Using both diskpart. minitool partition wizard, sdformatter and easeus partition manager.
Tried using FAT32, exFat and NTFS. None of them works. When using exFat the card is recognized and the phone asks if I want to format, but nothing happens after it says it's erasing the sd card.
The card works perfectly fine in Windows formatted as exFat.
I'm running stock ICS 4.0.4 if it helps to know.
I also have a friend who is using a 64gb sdxc card on the same type of phone.
Which version he's using I do not know.
Does anyone know how to solve this?
Click to expand...
Click to collapse
I thought, the Desire S can work with up to 32GB sd-cards. I've read it many times on different web-sites.
NVardan said:
I thought, the Desire S can work with up to 32GB sd-cards. I've read it many times on different web-sites.
Click to expand...
Click to collapse
So I've read also, but since my friend is using a 64GB without a hitch it should work. Unless it's only possible when using a custom rom? For a short period I managed to get the phone to see the card and report all 64GB, but then it was unmounted. Managed to do this using a certain cluster size as exFat if I remember right.
knerlington said:
So I've read also, but since my friend is using a 64GB without a hitch it should work. Unless it's only possible when using a custom rom? For a short period I managed to get the phone to see the card and report all 64GB, but then it was unmounted. Managed to do this using a certain cluster size as exFat if I remember right.
Click to expand...
Click to collapse
You could ask your friend, the correct model of the SD-Card, and buy the one he also has, or test his one and see, if it's related with your hardware or not. I'm still a bit noob, so, you'll better also hear opinions by other XDA members.
Might have found the issue
I downgraded from ice cream sandwich to gingerbread(?) 2.3.3 while I at the same time rooted the phone and set the bootloader to s-off.
Now the phone itself has managed to format the card and recognize ~62GB/64GB. I successfully formatted it using cwm too and the phone still recognizes it. At the moment I'm partitioning the sdxc-card with a higher cluster size since it was really really slow when I tried to copy a file from windows. Note that it's a class 10 card.
Appears to be a problem with ICS. If anyone else can confirm this we're set here I think.
knerlington said:
I downgraded from ice cream sandwich to gingerbread(?) 2.3.3 while I at the same time rooted the phone and set the bootloader to s-off.
Now the phone itself has managed to format the card and recognize ~62GB/64GB. I successfully formatted it using cwm too and the phone still recognizes it. At the moment I'm partitioning the sdxc-card with a higher cluster size since it was really really slow when I tried to copy a file from windows. Note that it's a class 10 card.
Click to expand...
Click to collapse
Ok, the good news is, you made the phone to recognize it! That's really good, taking into account that reviews said it's only capable of having up to 32GB standard SD-card.
NVardan said:
Ok, the good news is, you made the phone to recognize it! That's really good, taking into account that reviews said it's only capable of having up to 32GB standard SD-card.
Click to expand...
Click to collapse
Formatting the card as FAT32 with a primary and active partition is the only way I can get the card to be recognized.
But as soon as I try to copy something to the card it gets removed and unusable again.
Could there be a need for several partitions? One primary and one logical perhaps?
I've changed to flinnys version of CM10.1 build 22 called andromadus (jelly bean) which at a couple of times reported the card as damaged.
Tips on software for checking and possibly fixing a damaged one?
knerlington said:
Formatting the card as FAT32 with a primary and active partition is the only way I can get the card to be recognized.
But as soon as I try to copy something to the card it gets removed and unusable again.
Could there be a need for several partitions? One primary and one logical perhaps?
I've changed to flinnys version of CM10.1 build 22 called andromadus (jelly bean) which at a couple of times reported the card as damaged.
Tips on software for checking and possibly fixing a damaged one?
Click to expand...
Click to collapse
Haven't had any such experience, so can't help with that one, sorry
Sent from my Desire S using Tapatalk 2