Related
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.
can a sd card be damaged if its not removed while you gain root or cwm or flash a rom? i have a sandisk 64gb class 10 that use to work fine before i flashed my S3. After i flashed freeSG3 my sdcard wouldn't mount, keeps saying sd unexpectedly removed. it came preformatted as exFAT and worked fine on the stock tw rom. i stuck in my computer and it said it needed formatted so i reformatted as exFAT and copied a couple files to it. soooo.. im assuming it isn't damaged since it works in my computer. still no luck getting it work on my phone though. I tried my other sd's to see if it was the rom maybe but they work just fine, its only this card. im confused to why it isnt working now, but use to work but still works on my computer. ive only had it for a couple weeks and luckly i got it off of amazon so i can still return it. i've tried rebooting my S3, i even tried to mount in it my vibrant after i reformatted even though i know the vibrant doesnt suppport 64 gb.. it said damaged sdcard. ill give it a few more days of research before i send it in for a new one, im hoping i can get it to work again. my other option i was thinking about doing was to restore my phone back to stock to see it would work again. i dont really want to do that but i think i will for the hell of it before i try returning it.
Your SDCard is not damage, as I've mention in your other thread you are probably running a custom kernel that doesn't support exFat.
Either reformat your card as FAT32 or NTFS or flash back to stock kernel that does support exFat.
exFAT is a proprietary Microsoft product. They don't release licensing to open source software like Android. Apparently Samsung as some kind of licensing deal with Microsoft to use exFAT that's why the stock kernel will work with newer SDCARD formatted as exFAT.
I am going to piggy back on this thread and say that I have the "unexpectedly removed" bug
S3 running stock 4.0.4 - it works fine with a 2gb microsd, but I just bought a 32gb micro sdhc class 10 and it just won't read.
Tried exFAT, Fat32 - NTFS doesn't read on the card.
Suggestions?
darkphantom said:
I am going to piggy back on this thread and say that I have the "unexpectedly removed" bug
S3 running stock 4.0.4 - it works fine with a 2gb microsd, but I just bought a 32gb micro sdhc class 10 and it just won't read.
Tried exFAT, Fat32 - NTFS doesn't read on the card.
Suggestions?
Click to expand...
Click to collapse
I was using 32gb card earlier on Stock Rom-unrooted, rooted, RcMix and Xquisit roms without any issue. I know you would have tried but have to ask, did you try copying any data onto the card on a PC? May be some bad sectors are causing it to not recognize.
Can you tell me if CWM or TWRP recognize the card?
I don't have any issues with all my cards - 16gb, 32gb and 64gb ultra sdxc.
I've been putting off rooting it since I was content with the factory rom, but I guess I have no choice. I'll check CWM after I root it.
However, I can't copy any data onto it. Also, the phone recognizes the card but it keeps unmounting/remounting it.
how can I tell if CWM sees the card? Even after root, the phone sees the card, just can't copy anything to it.
Did anyone ever have a fix for the "unexpectedly removed".
Had the problem before. Reformatted sdcard and odin back to stock then flashed cm10 with no problems.
Recently went back to TWFrosty, and the problem exists again. Could it be from going back and forth between TW and Aosp?
My card is fairly new, about 2 mths? Maybe 3.. Weird error, it shows my external sd card blank, then all of the sudden if I leave it be all my files will show back up. Also it has went so far to ask me to reformat the card with my phone. I just avoid the answer, and eventually all my files come back. When I'm near a computer and it does this, I'm able to still see all of the files on the external sdcard on my PC, just not on my phone.
Thanks for all the help..
Billy G.
Sounds like you need to backup then reformat the card. You didn't say what kind/size it is or what format. That can help.
Sent from my SGH-T999 using xda premium
Sandisk/32gb/fat32
Sent from my SGH-T999 using xda premium
Well I've got same problem with my 32 SanDisk. Sometimes it's shown on my computer and my phone and tablet, but for the most part its just not showing at all. IdK what the hell is wrong with the thing. I have another one just like that one, and so far (knock on wood) no problems, so my hardware is ok........
juanflight said:
Well I've got same problem with my 32 SanDisk. Sometimes it's shown on my computer and my phone and tablet, but for the most part its just not showing at all. IdK what the hell is wrong with the thing. I have another one just like that one, and so far (knock on wood) no problems, so my hardware is ok........
Click to expand...
Click to collapse
Crazy. Let me know how it goes.. aosp is working for me for now. We shall see..
Sent from my SGH-T999 using xda premium
For large (32/64GB) cards, if you're going to use an AOSP ROM, you have to format to FAT32 (or ext3/4). TW based roms will format to exFAT if you format it inside the phone. The drivers for exFAT aren't included in AOSP though.
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.
okay, i've tried and looked for a similar issue but so far i can't find anything related.
I have a sandisk microsd ultrahc card 16gb.
the card itself works extremely well, both in my device when using the stock / custom samsung based roms,
Didn't really notice this untill i tried out android 4.3, at wich i thought first could be a bug in the rom, the settings kept fc'ing the moment i opened up the storage part, and a com.android.media kept fc'ing the moment i attached the usb cable.
as i thought 4.3 was the culprit i flashed 4.2.2 wich also had similar issues up until the moment i removed the card from my device and restarted, everything worked smoothly afterwards.
I've tried using exfat / fat32 both with cluster of 4096 and 8192 and neither of those helped in any way. Turns out that both TWRP and CWM (yes i tried it in both) also can't seem to mount the sd-card.
Is there any workaround for this issue? or do i have to get myself another sd-card?
I think it's the ROMs man messing things up...i tried android 4.3 yesterday and my whole android directory changed like I had to go into a folder called 0/0/0/my android files. to reach my files etc couldn't mount from sdcard couldn't copy things across from pc...I just flashed back my original stock firmware and everything is good..... android 4.3 is pretty messed up..give it time to mature still very buggy
Sent from my GT-N7105 using Tapatalk 2
The messed up folder i should get used to thoug its because of the multiple user profiles things are getting a bit messy.
Its something they added in 4.2.2 i believe
Best way to do it is to flash the rom and afterwards copy back everything to the sdcard.
Didn't have any issues with another sd card i still had laying around but that thing even thoug class 4 doesn't get more than 1mbps transfer speed.
Sent from my GT-N7105 using xda premium
if the sdcard works on your pc with directly like by using an mmc adapter or sdcard to USB converter then your card is ok if it just didn't work on the phone it has to be a software issue our maybe the hardware mmc port is faulty??!
Sent from my GT-N7105 using Tapatalk 4
thats just it, the sd card works like a charm untill i upgrade to 4.2.2 or 4.3. however both recoveries can't mount the sd-card either.
its not one of those black ones that goes to class 10, but an ultra hdsc class 1 so might be something related to not being able to work properly with anything higher than class 10
nope....the class issue has nothing to do with software.....that's purely the job off the chip electronics/hardware.... I would say a combination of your recoveries and ROMs like I had the same issue once the custom recoveries maybe can't point to the location/ section of the memory card...try changing to different version of the recovery...maybe that could help but be sure the recovery is supported on your device...these are risky issues...so only do it at your own risk
Sent from my GT-N7105 using Tapatalk 4
i've tried several versions of CWM both touch and normal, also philz (yesterday but touch didn't work as it should so won't stick with that one) and TWRP but none of them could mount/find the external_sd, the only think properly working with that sd card is the stock samsung and custom roms based on stock.
(not particulary fond of TWRP, i like the layout and how it works, i just don't like the backups of that recovery, can't copy them to my computer, the extensions keep giving me an error and they are located on the phone's storage)
the sd card couldn't be found in my sensation xe neither i remembered just now after i stopped using the 4.0 stock rom and switched to custom roms, at the time i didn't really see a connection and thought my sd card just didn't want to work properly in my sensation anymore, But having the same issues, and using another sd-card in the phone worked again. Used the ultra sd card in my tabled and because i didn't use that one anymore and someone in my family needed a 16gb one for tomtom europe i gave my good one away )
gonna get myself a new sd-card this afternoon as the 8gb i had laying around isn't getting higher transfer speeds then 1mbps at most even if its a class 4. a shop nearby has a class 10, 16gb for 13 euro's so reckon thats not a bad deal, might even go for the class 10 32gb for 26 euro's if they have it in stock.
I have a 64gig card and had similar problems. With phils recovery it only works when formatted fat32. Think that exfat is not supported. With stock kernel it mounts exfat with any other kernel i tried it would only mount fat32. I think samsung kernel has support for exfat and others dont. So it might not be adroid related but kernel related.
Grumps said:
I have a 64gig card and had similar problems. With phils recovery it only works when formatted fat32. Think that exfat is not supported. With stock kernel it mounts exfat with any other kernel i tried it would only mount fat32. I think samsung kernel has support for exfat and others dont. So it might not be adroid related but kernel related.
Click to expand...
Click to collapse
weird thing is though, even when formatted to fat32 and not exfat, android 4.2 and 4.3 will not recognise my card, also the recoveries i only get an error when i want to mount my sd-card
my tablet which is running an aosp version of android 4.0 or 4.1 (can't quite remember) could handle the sd-card just fine, while both my phones have issues with it.
solved it by buying myself a new sd card, ^^ now i can at least safely backup to my external card instead of the internal memory.
OK my problem is I have the tab 3 10.1 with a 64gb micro SD card in it and the only way to root is to put a smaller SD card in because for some reason it can't read the 64gb micro SD card and when I want to make a backup in cwm it says it can't mount the 64gb micro SD card but if I use anything smaller everything works fine so my question is, is there a work around or some way to Make my tab 3 mount the micro SD because I'd like to install other roms and stuff but I'm not going to I till I can make a backup first. Also with the 64gb card in my tab 3 everything else works like watching videos stored on the SD or music on the SD, anyways any help with this issue would be much appreciated.
Sent from my GT-P5210 using xda app-developers app
you MIGHT have better luck if you format the SD card in some other file system. Other than that I'm not sure
You could buy an 8 gig one and swap it too
DopeShow said:
OK my problem is I have the tab 3 10.1 with a 64gb micro SD card in it and the only way to root is to put a smaller SD card in because for some reason it can't read the 64gb micro SD card and when I want to make a backup in cwm it says it can't mount the 64gb micro SD card but if I use anything smaller everything works fine so my question is, is there a work around or some way to Make my tab 3 mount the micro SD because I'd like to install other roms and stuff but I'm not going to I till I can make a backup first. Also with the 64gb card in my tab 3 everything else works like watching videos stored on the SD or music on the SD, anyways any help with this issue would be much appreciated.
Sent from my GT-P5210 using xda app-developers app
Click to expand...
Click to collapse
Have you tried both recoveries? CWM and TWRP if neither work you may have to format to fat32.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Yes I've tried every recovery out there and with cwm it does this count down from 10 that says connecting then after it gets to 1 it says aborted because it cannot mount the micro SD and yes its formated to fat32 and I've tried exfat and every other format nothing works, and in my first post when I said I couldn't root from the micro SD I mean by going into cwm and loading zip file from there it does the same thing and says it can't connect, that's why everytime I root my device this way I have to borrow a 32gb micro SD and everything works fine
Sent from my GT-P5210 using xda app-developers app
Same problem with my 64g card. MY 16g works great. Cant seem to get the 64g formatted in either my phone or the Tab3. I can sometimes get the Tab3 to recognize the card and it will show the files on the memory card but once I go into recovery there is nothing there.
My 64gb card is recognized while the device is in regular running mode like I can go into settings and then storage and see the card there and how much space is used and free the Only time the card doesn't work right is when I'm in recovery mode because for some reason in recovery mode the system says it can't mount it and that is my whole problem, I need a way to fix it so my 64gb card can be mounted and used while in recovery mode.
Sent from my GT-P5210 using xda app-developers app
It's either a recovery issue or a driver/kernel/bootloader issue, a case that the Tab 3 10.1 development is far from being active.
It looks like it can't allocate space that exceeds 32GiB.
Also wrong thread.
Trying formating your SD card on the computer to fat32 or extfat .
Sent from my GT-I9505 using XDA Premium 4 mobile app
I've already done that and the card works fine example in the device it only stops working in cwm recovery saying it can't be mounted
Sent from my GT-P5210 using XDA Premium ANDROID Developer's App
Thread cleaned of off topic posting and unnecessary non-related junk.
(yes, we can do this)
Any more silly ridiculous junk posted, and this thread will be closed permanently.
If the OP wants to keep this in open forums, we cannot prevent this and welcome the debate, as it seems fitting.
Cheers
MD
My thoughts...
Running the tab in normal mode allows the 64gb card to be read. However, if you start in CWM or TWRP recovery, you are no longer in the "normal" mode and the tab does not recognize the 64gb card. In recovery mode, it is possible that the memory allocations are limited where as in normal mode, 64gb is OK.
In this case, for rooting, maybe you should load the root file on internal memory and not the memory card. I use 4gb cards and neither CWM or TWRP could work with them. I think the issue is in the recovery programs and not the Tab, save for memory limitations set by the base firmware.
Again, JMHO and I may be way out in left field here.
TWRP after 2.4 supports exfat. What version are you using? Many people have posted that TWRP 2.7.0.0 has hosed sd support and people have posted earlier versions like 2.6.*.* and now 2.7.0.1 work fine. I'm guessing you've were trying a broken version.
Your phone is a computer running the linux operating system. Hardware works by way of software called drivers that allow the system to communicate with various devices like drives and radios. The drivers in linux are built into the kernel which is the heart of the system or they are loaded as modules. When building a kernel you can add or subtract any number of various drivers you may or may not need into the system. The stock Samsung kernel has the various file system (fat32, exfat, ext3, etc) drivers built into it and that's why your sd card is recognized and works fine within the Samsung custom Android operating system you're running. TWRP and other recovery systems are bare bones operating systems that you load in order to perform maintenance functions like loading firmware or running backups. When the devs for TWRP compiled their kernel (processed all the changes to their new kernel and made it ready to operate) for version 2.7.0.0 they screwed up by either leaving out support for cards of a certain size, file systems of a certain size, support for certain filesystems or used experimental buggy drivers. This is why your card doesnt work in recovery.
You should try a different version of the recovery you desire. You might also want to try formatting the sdcard as another filesystem like ext4. The CWM thread for your tablet forum.xda-developers.com/showthread.php?t=2432467 says that 64gb support is very buggy and that CWM is not being worked on anymore for your device. Some people say it works for them though. Page 1 of the TWRP thread for your device (which is final on version 2.7 which may mean his last build killed 64gb support) mentions earlier versions working with 64gb cards. You may want to ask people posting early in the thread if they have an early version they could upload for you.
If you own a mac or linux system or burn a linux cd( ubuntu live cd) you could format your 64gb microsd as ext3 or ext4 and it should have no issue unless it's a problem with the capacity of the microsd in which case you could try to create one partition on the microsd card of say 25gb. That could work if partition size and not disk capacity is the problem.
Those seem to be your options along with just buying a 32gb, 16gb, 8gb, 4gb, 2gb card to root with. Memory is getting cheaper and images to flash ROMs and recoveries are generally small. You could probably buy one in your local drug store for $5. If money isn't tight, there's your easiest solution. You could borrow a smaller card from someone too if money is tight. They are pretty common in phones going back 6 years now. If you want to learn more about your phone and get hands on experience try another method above.
Good luck. Hope you get it going.
GorillaPimp said:
TWRP after 2.4 supports exfat. What version are you using? Many people have posted that TWRP 2.7.0.0 has hosed sd support and people have posted earlier versions like 2.6.*.* and now 2.7.0.1 work fine. I'm guessing you've were trying a broken version.
Your phone is a computer running the linux operating system. Hardware works by way of software called drivers that allow the system to communicate with various devices like drives and radios. The drivers in linux are built into the kernel which is the heart of the system or they are loaded as modules. When building a kernel you can add or subtract any number of various drivers you may or may not need into the system. The stock Samsung kernel has the various file system (fat32, exfat, ext3, etc) drivers built into it and that's why your sd card is recognized and works fine within the Samsung custom Android operating system you're running. TWRP and other recovery systems are bare bones operating systems that you load in order to perform maintenance functions like loading firmware or running backups. When the devs for TWRP compiled their kernel (processed all the changes to their new kernel and made it ready to operate) for version 2.7.0.0 they screwed up by either leaving out support for cards of a certain size, file systems of a certain size, support for certain filesystems or used experimental buggy drivers. This is why your card doesnt work in recovery.
You should try a different version of the recovery you desire. You might also want to try formatting the sdcard as another filesystem like ext4. The CWM thread for your tablet forum.xda-developers.com/showthread.php?t=2432467 says that 64gb support is very buggy and that CWM is not being worked on anymore for your device. Some people say it works for them though. Page 1 of the TWRP thread for your device (which is final on version 2.7 which may mean his last build killed 64gb support) mentions earlier versions working with 64gb cards. You may want to ask people posting early in the thread if they have an early version they could upload for you.
If you own a mac or linux system or burn a linux cd( ubuntu live cd) you could format your 64gb microsd as ext3 or ext4 and it should have no issue unless it's a problem with the capacity of the microsd in which case you could try to create one partition on the microsd card of say 25gb. That could work if partition size and not disk capacity is the problem.
Those seem to be your options along with just buying a 32gb, 16gb, 8gb, 4gb, 2gb card to root with. Memory is getting cheaper and images to flash ROMs and recoveries are generally small. You could probably buy one in your local drug store for $5. If money isn't tight, there's your easiest solution. You could borrow a smaller card from someone too if money is tight. They are pretty common in phones going back 6 years now. If you want to learn more about your phone and get hands on experience try another method above.
Good luck. Hope you get it going.
Click to expand...
Click to collapse
yes ive tried multiple recovery's and they all do the same thing and cannot read the 64gb micro sd and yes I have my sd formatted to fat32 and I am on windows on my laptop but I can format the micro sd to ext3 or 4 but my question is, if I do that and its formatted to ext3 will I still be able to access my tablets drive space through my laptop like I can now with it being on fat32, because if I cant then that would be pointless for me to do because then I wouldn't be able to add and take things off my sd while its in my tablet., also I said in my first post that this problem doesn't happen using a smaller micro sd like 32 or smaller it only happens with the 64gb, so it has to do with the size some how
GorillaPimp said:
TWRP after 2.4 supports exfat. What version are you using? Many people have posted that TWRP 2.7.0.0 has hosed sd support and people have posted earlier versions like 2.6.*.* and now 2.7.0.1 work fine. I'm guessing you've were trying a broken version.
Your phone is a computer running the linux operating system. Hardware works by way of software called drivers that allow the system to communicate with various devices like drives and radios. The drivers in linux are built into the kernel which is the heart of the system or they are loaded as modules. When building a kernel you can add or subtract any number of various drivers you may or may not need into the system. The stock Samsung kernel has the various file system (fat32, exfat, ext3, etc) drivers built into it and that's why your sd card is recognized and works fine within the Samsung custom Android operating system you're running. TWRP and other recovery systems are bare bones operating systems that you load in order to perform maintenance functions like loading firmware or running backups. When the devs for TWRP compiled their kernel (processed all the changes to their new kernel and made it ready to operate) for version 2.7.0.0 they screwed up by either leaving out support for cards of a certain size, file systems of a certain size, support for certain filesystems or used experimental buggy drivers. This is why your card doesnt work in recovery.
You should try a different version of the recovery you desire. You might also want to try formatting the sdcard as another filesystem like ext4. The CWM thread for your tablet forum.xda-developers.com/showthread.php?t=2432467 says that 64gb support is very buggy and that CWM is not being worked on anymore for your device. Some people say it works for them though. Page 1 of the TWRP thread for your device (which is final on version 2.7 which may mean his last build killed 64gb support) mentions earlier versions working with 64gb cards. You may want to ask people posting early in the thread if they have an early version they could upload for you.
If you own a mac or linux system or burn a linux cd( ubuntu live cd) you could format your 64gb microsd as ext3 or ext4 and it should have no issue unless it's a problem with the capacity of the microsd in which case you could try to create one partition on the microsd card of say 25gb. That could work if partition size and not disk capacity is the problem.
Those seem to be your options along with just buying a 32gb, 16gb, 8gb, 4gb, 2gb card to root with. Memory is getting cheaper and images to flash ROMs and recoveries are generally small. You could probably buy one in your local drug store for $5. If money isn't tight, there's your easiest solution. You could borrow a smaller card from someone too if money is tight. They are pretty common in phones going back 6 years now. If you want to learn more about your phone and get hands on experience try another method above.
Good luck. Hope you get it going.
Click to expand...
Click to collapse
also IDK if you know this but there isn't many recovery's out there for the galaxy tab 3 10.1 the only one I use is bindroid_cwm_p5210_santos10wifi and even with this recovery it has a slight lag to it when using it.