Related
Tons of new ROMs coming out now based on OTA and adding A2SD+. But one big issue. Quite a number of people have reported problems with corruption of their SD cards when setting the Desire into Disk mode and connecting it to a PC. I've read it the first time here
http://forum.xda-developers.com/showpost.php?p=7463184&postcount=348
and I can confirm it is reproducible.
Regardless if connecting to Windows or Linux, the card gets corrupted. It does not matter if you properly eject the drive. The Desire will respond saying the SD card is Read Only, and the only thing that one can do is to repartition it to fix the card.
I don't know what A2SD+ application everyone uses in their ROMs but I expect it's all based on some common version like the one put in from ieftm. As this is a serious issue it would be great if all you ROM cooks could look into it and try to fix it. Alternatively it may be a good idea to produce non-deodexed versions that save a significant amount of memory when installed normally without A2SD+.
Thanks for considering
I have this problem aswell its a bit of a nightmare there are a few files on my sd card that I can't even delete using andexplorer or my pc. I think the only way would be to remove my card and format it. I have never had this problem before only when I started using the 2.2 rom.
Noticed it before, i took the SD card out and put it into a cardreader, couldnt do anything in windows, said it was read only. Access via USB cable worked though.
Not that much of a issue for me, I mainly transfer files via Wi-Fi anyway, but I guess thats the explanation for the read-only behaviour.
Happened to me today, however I restarted the phone and everything seems okay now... :/
edit: nope, connected the phone again, chose "charge only" and then disconnected. The notification about my card being corrupted occured again, tapped on it and it went away... Dont know what to think..
I have the same problem .. And now it seems like the SD card is totally corrupted. Its not even possible to do a format
Okay thats it... Doing the titanium backup, nand backup and flashing some rom w/o A2SD+... :/
Out of curiosity guys, did the corruption of the SD card occur to the stock SD card that came with the Desire? I had the same problem with the stock card..
It seemed to unmount 3 or 3 times over a week and the next thing I knew it totally died and could not even be reformatted.. Happened on stock 2.1 that came with my Desire.. after I swapped to me own class 6 8gb Transcend I never had the proble again.. Just gonna upgrade to 2.2 now.. *fingers crossed*
Oh and yes.. I use A2SD+ on Modaco's 3.1. But that was after that card got corrupted..
I'm using card that came with the phone.
I'm going to try another Froyo Rom, just OTA rom rooted and we'll see.
Edit: I made my ext3 partition with ROM manager, if it makes any difference...
God dammit!
http://forum.xda-developers.com/showthread.php?t=747480
Yes its the card that came with the phone .. but it happen after i created the 512MB EXT3 Partition ... and I'm running this ROM : http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=741775&highlight=official it doesnt even use A2SD+
I dual boot my pc with windows 7 & ubuntu.... windows 7 scan and fix has repaired mine numerous times
I have class6 A-DATA 8GB and no problem. But with my last G1 i haved same card and with swapping goes to hell... I now correctly unmounting and disconnecting mobile from PC, after i save from PC to card. Flash have problems with writing.
This looks like a serious problem - it happened to me twice already. Devs, please have a look at this!
I have also had similar experience, SD card corrupt, yes it was the original card that came with the phone, EXT2 partitioned and using APSD+
Now why this happend is a mystery, but something I noticed when I tried the SD card in the PC - it was recognized, but said it must be formated, so I tried but it only saw it as a 32mb capacity!!! (it still would not format though - failed format..and since is no longer reconized at all..)
But, this made me think it "MAY" be something to do with the fact that when I did the Ext2 partition I seem to remember it also created a 32mb swap partition, or using Ext2 instead of Ext3. I have since learnt that it is advisable NOT to created a swap partition, so with my new SD card, after more reading about Ext partitions etc, I have only created only the Ext3 partion as I understand this is better than Ext2 and is less prone to corruption, and no swap partition and have had no problem since!
See this excellent post :- http://forum.xda-developers.com/showpost.php?p=7458565&postcount=8
It would be interesting to have some input from one or two of the developers with knowledge in this field to get an idea why this happens, and how it can be prevented.
It is also possible the the SD card was going to become corrupt anyway... with or without the help of Ext? / APSD+ - it does happen!
delta-101 said:
I have since learnt that it is advisable NOT to created a swap partition, so with my new SD card, after more reading about Ext partitions etc, I have only created only the Ext3 partion as I understand this is better than Ext2 and is less prone to corruption, and no swap partition and have had no problem since!
Click to expand...
Click to collapse
my sd was corrupt using a 512MB ext3 partition without swap partition in SD card :/
Try in windows: start > run > chkdsk x: /f
where x = desire drive letter.
I believe i did this in recovery mode > mount usb.
That's what happens when you don't want to use Froyos own A2SD implementetion because "widgetz doesnt workzz on dat."
Apps are not meant to be on an external EXT partition.
Wait until ROMs like CM have built in A2SD+, these hacky shell scripts can cause serious problems for the SD card.
LeeDroid said:
I dual boot my pc with windows 7 & ubuntu.... windows 7 scan and fix has repaired mine numerous times
Click to expand...
Click to collapse
Windows can not access EXTx partitions. As such is unfortunately not possible that it could possibly repair a broken SD-ext partition A2SD+ uses.
delta-101 said:
I have also had similar experience, SD card corrupt, yes it was the original card that came with the phone, EXT2 partitioned and using APSD+
Now why this happend is a mystery, but something I noticed when I tried the SD card in the PC - it was recognized, but said it must be formated, so I tried but it only saw it as a 32mb capacity!!! (it still would not format though - failed format..and since is no longer reconized at all..)
[...]
It is also possible the the SD card was going to become corrupt anyway... with or without the help of Ext? / APSD+ - it does happen!
Click to expand...
Click to collapse
I can confirm the corruption without any APSD+ ROM
I had a Stock Orange FR 2.1 ROM, and the 4Gb card that came with the phone get corrupted definitively (recognized as a 32mb capacity too, it has something to do with the Cylinder-head-sector combination).
Anyway, I'm going to try APSD+ with a class 2 PNY 16Gb, and tell you then if I get a corrupted card.
FYI, the Sandisk warranty is applicable for the original card: replaced in 5 days
I got some problems too with corruped files on my SDcard and had to format it. I'm thinking that from now i'll only mount my card to pc in recoverymode... maybe that is safe to do?
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.
Hello, I'm new to the forums.
Today I bought a 32 GB MicroSDHC memory card for my at&t s3.
Behaviours:
1) I inserted it into my phone and then I tried taking some photos. I set the output path to the card and I took a picture. The picture was successfully saved to the sd card, but when I tried taking a second picture, I received an error: "Cannot write file in SD card. Default storage set to Phone". If I try again to set the memory card as default storage I can again take another photo, but the next one will fail as described again.
2) With SD card mounted to the S3, I plug in the USB to connect it to my computer. I can then see the card and view the files on it. However, I'm unable to write anything on it. (Copying something to the card will freeze my windows explorer)
3) If I insert the card into my computer via adapter, then all works fine. I can write to it fine.
It seems that the problem only occurs when the sd card is used by the S3.
Note: I have checked the card for read-only notches and it has no such thing.
Note2: I have a rooted phone running JB 4.1.1 stock.
Any help will be appreciated. Thank you.
many phones have problems with 32GB class 10 cards. What is yours?
kirkgbr said:
many phones have problems with 32GB class 10 cards. What is yours?
Click to expand...
Click to collapse
well it's a Kingston class 10 one.
BinSlayer said:
well it's a Kingston class 10 one.
Click to expand...
Click to collapse
Maybe you can try reformatting it.
reformat it in what way? I've already tried exFat, Fat32 and NTFS. NTFS and exFat give a "blank card" error, while Fat32 won't let me write stuff like I described. And I've reformat the card a couple of times already.
Edit: well, I did so using windows format app.
Do you know of other better apps?
Also I forgot to mention that I can't format the card via samsung s3 built-in app because it always returns "blank error" in that case.
BinSlayer said:
reformat it in what way? I've already tried exFat, Fat32 and NTFS. NTFS and exFat give a "blank card" error, while Fat32 won't let me write stuff like I described. And I've reformat the card a couple of times already.
Edit: well, I did so using windows format app.
Do you know of other better apps?
Also I forgot to mention that I can't format the card via samsung s3 built-in app because it always returns "blank error" in that case.
Click to expand...
Click to collapse
I also had a problem with a new card and I took mine out and put it back in the phone and it finally worked. I just made sure it was pushed in all the way and seated properly.
I have just tried to use the card on a Galaxy S Plus. It worked flawlessly. I format it from that phone and then I inserted it into the Galaxy S3. It still won't work on the S3.
Why is this? I'm becoming desperate. This issue is bugging me a lot. Please any help will be appreciated.
Update: Even tried a galaxy S2. It works fine. Same problem on S3 though.
Hi guys
Upgraded to Note 2 N7105 International version 4 weeks ago, great phone and really loving all the features.
Trouble is I bought this because I wanted a more powerful phone than my previous Nexus S, so It could handle more powerful apps and games.
So on top of the internal 16gb of internal memory, I installed a Sandisk 64gb external card to store my apps and games, not realizing the phone does not support moving Apps to SD in standard form.
After investigating, found i could do it with a third party app with root access. So I rooted with Chainfires CF Auto Root, and installed link2sd App. My phone is definitely rooted as I have Titanium Backup working, but when i try to move any Apps to SD it says no free memory, and also to check SD card has been formatted with 2 partitions and they are both set to primary, and on the info page for link2sd its says the same about partitioning
I assume this formatting is my problem as the SD card is virtually empty, just 3 pics and 2 short videos on it, and still showing 59gb free when i go to settings/storage.
If this is my problem, how do I get it formatted correctly, I tried to do it through my computer running XP but only get format command, with no option for Partitions or any thing, are there any programs or procedures you can recommend
Thanks in advance
Gary
GaryFromLondon said:
Hi guys
Upgraded to Note 2 N7105 International version 4 weeks ago, great phone and really loving all the features.
Trouble is I bought this because I wanted a more powerful phone than my previous Nexus S, so It could handle more powerful apps and games.
So on top of the internal 16gb of internal memory, I installed a Sandisk 64gb external card to store my apps and games, not realizing the phone does not support moving Apps to SD in standard form.
After investigating, found i could do it with a third party app with root access. So I rooted with Chainfires CF Auto Root, and installed link2sd App. My phone is definitely rooted as I have Titanium Backup working, but when i try to move any Apps to SD it says no free memory, and also to check SD card has been formatted with 2 partitions and they are both set to primary, and on the info page for link2sd its says the same about partitioning
I assume this formatting is my problem as the SD card is virtually empty, just 3 pics and 2 short videos on it, and still showing 59gb free when i go to settings/storage.
If this is my problem, how do I get it formatted correctly, I tried to do it through my computer running XP but only get format command, with no option for Partitions or any thing, are there any programs or procedures you can recommend
Thanks in advance
Gary
Click to expand...
Click to collapse
There is a mod that lets you swap internal memory with sd card. Have a look in this threat.
If you only need to format your sd card to FAT 32 then you should get the GUI version of this app here
SD card format
Thanks for the info Retrorom
Have decided not to go down the internal external memory swap route, for various operational reasons, plus quite a few people seem to be getting issues with it. And the other one didn't seem to have a facility to make your own partitions, which is what i need.
After reading up a bit, From recommendations I have installed a program called Minitool Partition Wizard on my computer.
The only problem now is when i attach the card to the computer, it is showing as only having 27gb of usable memory, whereas in the phone it was showing 59gb. I thought this may be because it needed reformatting, so I formatted on the computer, and it was then only showing 27gb i when inserted in the phone, so i have again reformatted the card in the phone, and again now showing 59gb as it was originally. But i still still only have1 partition, and need 2 for the link2sd program to work
The trouble is when i put the SD back in the the computer it still only shows 27gb that is 32gb short of the 59gb what it shows while in the phone.
Was wondering why this should be, I'm running an old Pentium 4 system with XP on it, would it be that this can not handle or recognise 64 gb cards.
Just to mention i will be upgrading this computer 2 Windows 7 within the next week or so, and also going to build a brand new one in a couple of weeks which will have Windows 7 also , so should be a lot more compatible and flexible if that is the problem
SD Card Format
Update
I've been reading up, and it seems, Windows, especially earlier versions cannot recognize or format SD Cards over 32 gb, something to do with errors in the architecture, which wasn't originally designed for cards of this size.
There is a driver update, to get over this, but negotiating the Microsoft site to download it is proving to be a bit of a mission, It's ridiculously complicated, just sending me round and around in circles to try and find the download.
So if anyone can point me to the download, or a download that will do the job it will be much appreciated
Download exfat support for old XP machine
Download and use file according your XP system 32/64bit
you will get format with exfat format. which support larger size.
Another thing i recommend is 'directory bind' for moving data to ext SD card, this also make hassle free factory reset, Here is guide.
Thanks Ketan
I've already got the exFat support loaded, though it still only shows 27 gb on card
Now looking at the directory bind, and may give that a try later, once I've given it a good read and know i'm not going to do anything wrong .
Will let you know later how it goes
I'm actually surprised the phone supports higher than Windows. Most phones are limited to 32 gb cards are they not?
GaryFromLondon said:
Thanks Ketan
I've already got the exFat support loaded, though it still only shows 27 gb on card
Click to expand...
Click to collapse
have you try formating it on PC with exfat support?
UnL33t My Galaxy Note 2 Automatically recognises the higher capacity
Ketan yes I've tried to format on computer with exfat support, but still only shows 27gb, and when i put back in phone it showed 27gb in there too, so had to reformat it in the phone and now showing 59gb as it was originally,
But still showing 27gb when put in computer
I am going to upgrade my XP up to windows 7 in a couple of weeks, and also going to build a new games machine with Windows 7 on in a few weeks too, do you reckon they will have better support for the higher capacity card built in
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.