yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Q&A, Help & Troubleshooting] Theshawty:
If it wont format properly, have you tried removing the exFAT partition and make a new partition with the FAT32 filesystem?
[Galaxy S III Q&A, Help & Troubleshooting] luigig:
I received my 64GB card formatted as xFAT and formatted to FAT32 in few secs using this program: http://www.ridgecrop.demon.co.uk/index.htm?guiformat.htm.
[Galaxy S III Q&A, Help & Troubleshooting] rajamar:
luigig

Thanks so much for that link. It worked great in seconds just like you said.:good:

I spent over 6 hours a couple of days ago moving 40G from my 64GB SanDisk to try and change the format from exFAT to fat32. My primary machine is Win 7 64, but I also tried on XP. None of the previous tools did anything.

One important thing I did discover was that the write protect tab on the SanDisk carrier sticks out just enough so that inserting it into the reader on both my machines moved it into the write protect position. AHA -- now we're getting somewhere, I thought. Trimmed it down with an exacto knife so I could insert it without moving the tab, but it still got a message that the format tool could not read the card layout. I had been getting write protect errors.

For the record my symptoms were a little different. When I first got the card I copied about 20G over USB from my Win 7 64 machine. I found about 30 files (out of 2500) had extraneous double extensions like [filename].mp3ation.mp3 or [filename].mp3m).jpeg and these garbled extension files were 0 bytes. (TIP - use ASTRO to search for *.mp3, *.jpg, *.mp4 or whatever and in advanced settings filter for files < 1K.) So the majority of the files copied OK and were playable on the S3, however when I would open the the external 64G card through USB I could not see most of the folders I knew were there. Also during this time Kies was crashing when I tried to use it. Another little piece of nastiness was that the S3 could not delete or rename the 0 byte files.

So after I was unsuccessful in reformatting to fat32 I inserted the card carrier into the Win 7 machine and blew away everything on the card. I copied over 40G, saved a file list of everything on the card and put it back into the S3. Same situation - garbled double extension 0 byte files. About 64 out of 5700 files. I noted the garbled 0 byte files and put the card reader back into the Win7 machine. All the "bad" files were just fine. CONCLUSION: ICS on a stock S3 CANNOT properly handle exFAT cards - it thinks perfectly fine files have garbled extensions and then can't even delete them. This confirms what the Samsung tech told ImgBurn (thanks for the great technical rundown BTW).

Now that the card is fat32 everything is as it should be. All 40G of files display properly through USB and Kies air smoothly displays all files without crashing on the S3.

I've been following this thread since it started and really appreciate everyone sharing their experiences - both good and bad. I really wish Samsung and/or SanDisk were a lot more up front about this. It would sure save a lot of frustration!
[Galaxy S III Q&A, Help & Troubleshooting] rurikc:
My problems and some possible directions ...

Sandisk SDXC Class 10 64 GB on the Samsung Galaxy S3:

After transferring files to the phone (wifi or just USB ... any method)

Some files and directories become "locked" / inaccessible:

- listed with the size of zero

- listed with the date of 01/01/1970 10:00

- unmovable/ undeletable

- corrupted name: part of the ending of another file name appended to the end of the name of the "locked" file

Workaround: rename the OTHER files, shortening the name seems to help, especially the one that was appended to the end in the name,

Doesn't work with automatically generated filenames e.g. Titanium backups.

The corrupted files are easiest spotted with Wifi File Transfer Pro because it displays a lock icon in the listing that is easy to spot.

Deleting a directory involves a two step process:

- first delete will only remove the unlocked files AND will subsequently unlock the locked one

- second delete will remove the rest

I've not been able to spot any patterns of behaviour except.:

It just seems to be more likely if there are many files with long filenames in the same directory but is not a given.

It also seems to have some consistency, e.g. backup, format, restore seems to trigger the same files.

It also seems to be localised to directories, i.e. problems in one dir do not affect files in another dir.

So far looks almost certainly to be a software (Samsung) problem, not a hardware problem. The phone formats the card as exFAT so it should be supported. It looks to me as a rather nasty bug ! Very disappointing.

Some users are not affected but it is likely lust luck.

Cheers,
[Galaxy S III Q&A, Help & Troubleshooting] rajamar:
Please reread my post above - we experienced the same thing, just described it a little differently. The SIII cannot handle perfectly structured files on an exFat card.

Most importantly - Did you reformat to fat32? It solves all the problems.

---------- Post added at 06:51 PM ---------- Previous post was at 06:38 PM ----------

For anyone still having problems formatting a 64GB card to fat32: several threads keep referring to the fact that Window 7 cannot do a fat32 format through Disk Manager leaving the impression that it is no longer possible in Win7. However, you will be pleasantly surprised if you drop to a DOS prompt (Run box cmd) and issue a format /? command. The help screen shows the syntax for fat32 formatting along with a warning. (It boils down to just be sure to use a 32K cluster size when formatting a "large" drive.)
[Galaxy S III Q&A, Help & Troubleshooting] leighmyers1291:
San Disk 64GB Micro SDXC Card

Hi guys,

bought myself a new card (as stated in title) and i was extremely excited for it to arrive. Rip it open, first thing i do i put it into my phone and it says it is preparing card and then comes up with a notification for me to safely remove card, which i though was a little bit odd, so went to Settings>Storage and clicked mount SD card... Same problem, goes to mount it and then just flashes up Safe to Remove in notifications bar... highly annoying!

Dont want to format to FAT32 if can be avoided because it is PAINFULLY slow as i have previously experienced!

if anyone could be of assistance i would be extremely grateful!!!!????
[Galaxy S III Q&A, Help & Troubleshooting] rajamar:
Bite the bullet

Several of us who have shared our 64GB experiences have have spent many frustrating hours trying to get the exFAT cards to work. Reread the posts - it can look like things are fine for a while, but then you get file and folder problems. Samsung techs have have even said it doesn't work. I know the SIII shows perfectly fine files as 0 bytes with mangled file extensions.

I haven't noticed any speed differences. However, I was just happy to get the FAT32 on it and transfer 40GB of music and photos over without any file corruption. I didn't do any speed tests.

Now, with that said, your "Safe to Remove" loop is not consistent with my (and others) experience on first insertion and boot of the SIII. After putting it alongside sdcard as extSDcard under /mnt, mine was seen. When I ran the stock camera app it immediately saw the card and asked if I wanted to store new pictures there.

What happens when you look at the card with a desktop or laptop?
[Galaxy S III Q&A, Help & Troubleshooting] leighmyers1291:
Putting the card into a computer, it works fine, no problems, its just the phone, ive put it into FAT32 now, but transferring my 25GB of music took just over 2 hours, where compared to exFAT took 40mins! i suppose now its done and working i should just leave it (only have to put it on there once i suppose). Just was hoping that maybe someone (highly unlikely samsung) had figured a fix for it, as exFAT seems to be the 'preferred' choice for the SDcard etc.

Thanks for your help tho! really appreciate it!
[Galaxy S III Q&A, Help & Troubleshooting] Skully☺:
Thanks a lot. It worked on my SII just as well in less than a minute :D
[Galaxy S III Q&A, Help & Troubleshooting] eXtremeDevil:
Hello to all.

Recently I bought a 32 microSDHC card for my SGS3. The thing is that the phone will ONLY recognized if it is format as FAT32.

Now, I want to use ExFAT because of the FAT32 4GB limitation. But the phone doesn't recognize the card formatted as ExFAT. In some other forum someone told me that, although he was unsure, the ExFAT filesystem is only recognized on the SGS3 if the card is of 64GB or more.

Can someone confirm this? If the argument above is bull****, then is a problem of my phone or my card's?

Thanks in advance.
[Galaxy S III Q&A, Help & Troubleshooting] eXtremeDevil:
Anyone?
[Galaxy S III Q&A, Help & Troubleshooting] johrikushagra:
Just insert the card and format it from the phone. There are times when it would not show on phone. It doesn't really matter. Just go in settings-storage and format sd card

Sent from my GT-I9300
[Galaxy S III Q&A, Help & Troubleshooting] eXtremeDevil:
I'm not saying that at all. Have you actually read me? If I do what you're saying the phone format it as FAT32 and I want ExFAT...
[Galaxy S III Q&A, Help & Troubleshooting] rurikc:
That was exactly why I posted: It was described differently.

And for me it was very difficult to find the info (in particular: this thread and the proposed solution).

And yes fat32 solves almost all problems except the well known ones:

- file size limit of 4GB

- lack of optimisation for flash type memory

Cheers. :)
[Galaxy S III Q&A, Help & Troubleshooting] eXtremeDevil:
Is that related with my issue?
[Galaxy S III Q&A, Help & Troubleshooting] d4fseeker:
Are you on samsung-official?

Aopk/Aosp/cm based Roms do not have exFat.

It's a horribly broken filesystem (especially it's linux implementation) go with NTFS (requires a corresponding kernel or injecting the modules) or (best of all) EXT4 if Fat32's limitation ia no-go for you
[Galaxy S III Q&A, Help & Troubleshooting] eXtremeDevil:
So I guess is my ROM's problem after all...
[Galaxy S III Q&A, Help & Troubleshooting] nativerobot:
I don't know if anyone else was running into issues formatting as fat32 like I was. I was formatting as fat32 but the problem I was having is that I was setting my partition to logical and not primary which was causing it to not mount while in my phone.

Spent too long trying different file systems until I realized that I wasn't setting my partition correctly. Should be easy enough to do in diskpart or if you're more visual you can use minitool partition wizard.
[Galaxy S III Q&A, Help & Troubleshooting] mesh626:
I'm having a problem where I successfully format the exfat card to fat32 however when I insert it to my phone it says damaged card. I'm going to try minitool program someone put up and see if it works after that.
[Galaxy S III Q&A, Help & Troubleshooting] kampj007:
More Card Issues

I seem to be having the same issue as you all my card is a 32 Gb Card and i didnt have problems until i switched the storage on the camera to external, for some reason after that is when i started having all my issues. I lost videos and now the card is saying Corrupt in the phone and the computer, I think i wont lose too Much from the card but i sure hate to chance it

Info for the record

Samsung Galaxy GS3

Tmobile t-999

Stock Rom not rooted etc

4.1.1

baseband t999uvdlja
[Galaxy S III Q&A, Help & Troubleshooting] zoomaj:
64gb micro SD Issue

hello all,

i seem to be having a problem as described by a previous member, where by when i am copying data to the memory card, after like 2 mins the card just stops responding!

i have a samsung galaxy s3, on jelly bean 4.1,

the 64gb class 10 card arrived in the post yesterday, it was the genuine packaging ordered from mymemory.com

i actually sold my 32gb to buy this one.

anyways i put the micro SD in the SD adapter then connect it to my laptop via the sandisk micro mate card reader,

started copying data and after a few mins, i got an error message saying target destination cannot be found, so i checked my computer only to realise the card was no longer there!

so i ejected the card and put it back in, and windows detected it, im on windows vista, started copying data and the same again, after a few mins the card dissapeared!!!

then i decided to do some reading and managed to format the card to fat 32 from Exfat using the guiformat app.

3rd time transfering data and the same problem again!!!

i never had this problem with my 32 GB card, infact i have never had a card fail on me from sandisk in the last 10 years!

so i am pretty clued up,

as a last resort i put the card in my phone, and connected the s3 via usb to the laptop and scrolled to memory card, and started copying data!

strangley enough the card never dissapeard and i managed to copy over 25GB of data to the card within an Hour!

so my question is, is it possible i have a damaged memory card or SD adapter? why does it keep ejecting when using the adapter in micromate but works fine in the phone itself when connected to the laptop,

also at fat 32, my samsung smart tv also recognises the card, where as on Exfat it didnt,

im in 2 minds as to sending the card back, as a previous user said he tried 2 cards and had the same problem, i dont want to use the card for a few months and experience data failure, id rather sort the problem out now!

if anyone has had a similer experience please share,
[Galaxy S III Q&A, Help & Troubleshooting] danxmanly:
Just got my S3 a week ago and put a 64GB sdxc card in it, formatted it, threw about 10 gig worth of data on it and it seemed to work fine. Sunday morning I got a notification a new release was out for OS ( on Verizon ), so I updated and today when I went to use my camera it said no external card found, and it reverted back to saving on the phone's main memory.

When you go to settings / storage, you can see the card with total memory and free space available, but going to file explorer reveals no files. Tried unmounting / remounting the card to no avail.through the phone's settings. But can only get it to show back up by physically removing / reinserting the card. All my files are still there after all that.

So I've gone ahead and reformatted the card in the phone under the latest update and am in the process of loading it back up with data. So far about 20 gig of transfers and it's still taking it. Will report back later on the latest results, but I would like to avoid formatting to fat32 as it looks like may have done to cure the problem. Weird it just seems to lose file structure and not the files and a simple removal / reinsert brings it back to life. However, with this freakin otter case I have it's really not that easy to do on second thought! LOL
[Galaxy S III Q&A, Help & Troubleshooting] zoomaj:
hey danx,

are u copying data with memory card in your phone?

or are u using a card reader to transfer the data? i have a sandisk micro mate but the card comes up with cyclical redundancy error! when i copy data to it!

im sending it back in a few days! gonna run that h2test on it first il report back results
[Galaxy S III Q&A, Help & Troubleshooting] danxmanly:
I was just transferring files via USB cable while the card was in the phone.

My problems are still sporadic with this 64 gb card:

Sometimes upon power up of phone, the card shows to be corrupted. Yet in the settings menu, the card shows as mounted along with total space and used space listed properly..

Most times, a simple unmount / remount of the card via the settings menu will cure the problem. However, sometimes only a physical removal / reinsertion of the card will get it to be recognized.

I had one issue on my old Droid X2 with a 32 gb card that was cured by a rescan and repair while the card was inserted in my PC card reader. I'm about to get to that point in time with this card. It's weird that once it's recognized, it usually works for about 2 days before it becomes problematic... and then when I do get it to be recognized again all the files are still there and it works fine.
[Galaxy S III Q&A, Help & Troubleshooting] danxmanly:
So it would seem that this Sandisk 64Gb card looses its file structure in my Galaxy S3 on occasion which renders it useless. I can pull the card out and insert it in my PC and the files are there. Ran a disc check and card cks out fine as well.

Sometimes I notice when the card is working in the phone, that not all my mp3 files show up properly in my phone's media player. I have 80 or so artists, yet only about a dozen show up correctly, then the rest in a folder labeled "unknown".

I formatted the card as fat32 in my PC, but once I did that and put all my music files back on it the phone did not recognize the card. I saw where some have had success with the fat32 format, so I'll research more into why my phone didn't like that... but would prefer to figure out why 64 gb sdxc looses its structure.
[Galaxy S III Q&A, Help & Troubleshooting] jdagreek:
Samsung needs to figure this out !!!

If the phone is supposed to support 64 GB then it needs to .... I have all these problems that people are talking about on my PC the 64 GB card always works !!! In the phone it fails ...

32 GB cards always work in the phone !!!
[Galaxy S III Q&A, Help & Troubleshooting] vicky4112:
Thank you very much... Making it a primary partition finally worked... however my 64 GB is now 32 GB.
[Galaxy S III Q&A, Help & Troubleshooting] rahulrai:
GT N7000

i just bought a 64 gb card last evening and my samsung galaxy note is supposed to support only upto 32gb but i used EaseUS Partition Master 9.2.1 Home Edition to format the card thru my pc & voila.....my note now reads all the 60gigs....hope it helps some one...:good:
[Galaxy S III Q&A, Help & Troubleshooting] Theshawty:
I dunno what kind of low-quality china crap card you use, but my Sandisk 64GB SDXC UHS-I card has never failed me so far and it's been formatted to FAT32 since day three.
[Galaxy S III Q&A, Help & Troubleshooting] FrankZabelli:
exFAT file system on microSD cards

You need to try the Long Path Tool, helped me.
[Galaxy S III Q&A, Help & Troubleshooting] x625:
Have similar problem on microsd 64 sandisk formated in exfat. Gonna try format in fat32 . And report it back after usage confitmed.

But im intrested Why there is no fix for this important problem ??? There are many good dev in this forum and google and samsung head quarters but why this is just ignored topic : (
[Galaxy S III Q&A, Help & Troubleshooting] danarama:
There's an overall problem admitted by sandisk on their 64GB cards so I can't take claims the S3 is to blame as substantiated when these cards are used.

I have one myself but no issues.
[Galaxy S III Q&A, Help & Troubleshooting] Ign0tus:
I have a GS3 with 4.1.2 stock. I also have a Sandisk 64GB card in it. The issue that I have run into is that a few files over time are now showing as 0 byte files in ES File Explorer. They are mp3 files. In my media player (media player pro) the files show up as unknown artist and unsupported file format. I will likely switch to fat32 soon like many other people. I'm not having the types of issues that other people are reporting like a corrupted card, losing entire directories, or mangled file extensions. I've just had maybe 10 mp3 files lost as 0 byte files. The file names are still intact, but they cannot be played or modified. I can delete or overwrite them fine with ES. It's still annoying and I expect more files to eventually become corrupted.
[Galaxy S III Q&A, Help & Troubleshooting] HeZoR:
It's a sandisk's manufacturing fault.

Under certain circumstances the cards may lock up and the card becomes inaccessible.

I'm unlucky too, my card was mounted whenever it wanted to, and now mounts read only on every device connected.

I've reported to the sandisk support center Q/A and hope for a quick reply/replacement.
[Galaxy S III Q&A, Help & Troubleshooting] lorenzo_btbw:
hi, I've a sandisk 64gb ultra uhs-1, it has arrived formatted exfat (bought from Amazon). I've two issues:

1) stock audio player won't recognize all my mp3 (I read is a bug from the app)

2) when I turn on the phone, the live wallpaper won't load my images stored in the extsd

is it an exfat compatibility issue?

thank you
[HTC One X] dragonesdenano:
hi, My friend tried to flash with low battery ,then to solve the problem, he entered recovery and Format system...

What can he does to get to life his phone

We we are trying is this..

"If you DON'T have custom rom or Nandroid backup on internal SD card

Originally Posted by torxx View Post

So here a method which always works (many people have issues with flashing RUU's etc. having a bootlop.)

Download a RUU from here, thanks to Football!

Now open the .exe and make sure that it fully started.

Don't click anything, just go to windows icon and search for %temp%.

You will now find some folders, just search through these folders for the ROM.zip.

If you found it, you can copy it to your desktop or somewhere else.

Extract it with WinRar,7-zip or something like that and take the boot_signed.img and system.img.

Now copy the two files into the folder where the fastboot.exe is placed (if you have installed the Android SDK, it should be in platform-tools)

Plug in your One X, go into the bootloader and go into fastboot mode.

Navigate with the cmd in the folder with the fasboot.exe and the two .img's.

Now type in that:

Code:

fastboot flash boot boot_signed.img

After that:

Code:

fastboot flash system system.img

If everything worked, just reboot:

Code:

adb reboot "

Just trying different sort of things,

thanks in advance!!!!

Cheers:)
[HTC One X] jdunne:
If you have the latest version of CWM:

You can just enter recovery again and charge from the recovery screen. RUU's need 30% to initiate but you're better off just leaving it overnight to charge. From there run your RUU, plug in the phone and wait. The RUU will work from fastboot so I don't see why you would need to extract the rom from your %temp% files. You're just adding more risk.

If you do not have the lastest version of CWM (i.e. the one from march to early april):

Search the forum for the charging scheme. I'm not 100% but I'm pretty sure it went something like plugging it into your computer quite a few times over and over to get it to build up a little charge.

Honestly though, your friend should read the guides before flashing. I'm assuming this is his first experience flashing, but for further reference always have at least 75% battery and a nandroid backup.

Good luck
[HTC One X] dragonesdenano:
I know, i m in Grupoandroid helping people, and there is not like here, so people do things without reading, he wanted to Wipe data/factory ...but did format system, i m just trynig to help him only,

Well .. tomorrow we will try to run Ruu, now phone is in recovery, last with charging fix, so tomorrow I wil tell

Thank you very much for ur help

My idea is to pass him my nandroid backup, cause we are same region x.xx.707.xx

But we ll see tomorrow, noe "chraging time"

Thanks agian mate a see you tomorrow!!!!:)
[HTC One X] dragonesdenano:
Ok, good news, sent him my nandroid backup...phone running again...

Using charging fix recovery he could fill bayery 100% over the night, then flash my nandroid, now he has not only his phone working but last firmware too.

Mod can close thread...and very thanks for the Help!!!

Enviado desde mi HTC One X usando Tapatalk 2
[EVO 4G Q&A, Help & Troubleshooting] ReapersDeath:
Ok so after i decompile images and what not, i go into the shared folder, but my question is, how the heck are these .dat pngs??? they are png files but had .dat and when ever y add .dat to the end of the editied files i wanted, it has no effect on the apk..
[General Questions and Answers] tyreeves17:
okay so im having a little trouble flashing cwm recovery on my sidekick 4g. i tried the rom manager method,. i tried the method where you change the recovery image manually. havent had no luck at all. when i go to my stock recovery to "reinstall packages all it says is "E:failed to verify whole file signature

E:signature verification failed

installation aborted.

help??? please and thank you.. :D
[General Questions and Answers] efranco12:
Im having the same issue hoping this can be resolved