ScenarioYou get a new Samsung Galaxy S3 (SG3) with Ice Cream Sandwich (ICS) 4.0.1 (operating system - OS) in late 2012. You then purchase a brand new SanDisk 32gb class 10 chip. The chip is formatted as a FAT32. You insert the chip and over time you might remove it to view it on the computer edit it, then re-insert the chip in your device. after some time (say 3 or 4 months). The chip is working, when suddenly one day it cannot be mounted. You try removing the chip and loading it on the PC (it works). You insert the chip in the SG3 (it will not mount). You shut down the phone remove the battery and the sim card along with the chip. Put them all back in place and turn the SG3 on (this may work on 1 or 2 attempts). It still is not seen by the sg3). You search the web and get a variety of answers and some speculation.
Now you are up to speed with me. what next?
Action taken
I took the chip out and defragmented the chip on a windows pc (just going through the process of elimination). I had a theory that perhaps the OS on my phone is buggy. Based on this theory I applied a volume name on the chip. (that is I selected the chip in windows explorer and in the right click-properties option, I name the chip - with no spaces or special characters in the name). I inserted the chip back in the SG3 and it's seen and it works. Why?
I suspect it is the operating system. It may have somehow been corrupted by an app install. I am going to restore the last backup I made to eliminate this possibility before any further harm is done to the chip.
The word on the web is that some people have seen their chips fried by their device. This seems to indicated that new instructions were introduced and are causing the device to perform in a destructive way. Perhaps the instructions tell the device to remember the volume label of the chip so it will not be recognized and further instructions may have been inserted that will cause the device to fry any future chips that are inserted.
Word on the web is that Samsung (as of the date of this posting) has done little to nothing to address this problem.
It would be great if others posted on this thread (if their scenario matches mine) with actions taken to resolve the issue. This string needs to see other (out of the box approaches or outcomes) that can be noted for other viewers.
In the end we should see closure on this issue for this device.
If this thread is followed by others.
Note: I am not good at following up on these things. so my apologies if your inquiries are not answered (nothing personal).
Hope this helps
Now you are up to speed with me. what next?
Action taken
I took the chip out and defragmented the chip on a windows pc (just going through the process of elimination). I had a theory that perhaps the OS on my phone is buggy. Based on this theory I applied a volume name on the chip. (that is I selected the chip in windows explorer and in the right click-properties option, I name the chip - with no spaces or special characters in the name). I inserted the chip back in the SG3 and it's seen and it works. Why?
I suspect it is the operating system. It may have somehow been corrupted by an app install. I am going to restore the last backup I made to eliminate this possibility before any further harm is done to the chip.
The word on the web is that some people have seen their chips fried by their device. This seems to indicated that new instructions were introduced and are causing the device to perform in a destructive way. Perhaps the instructions tell the device to remember the volume label of the chip so it will not be recognized and further instructions may have been inserted that will cause the device to fry any future chips that are inserted.
Word on the web is that Samsung (as of the date of this posting) has done little to nothing to address this problem.
It would be great if others posted on this thread (if their scenario matches mine) with actions taken to resolve the issue. This string needs to see other (out of the box approaches or outcomes) that can be noted for other viewers.
In the end we should see closure on this issue for this device.
If this thread is followed by others.
Note: I am not good at following up on these things. so my apologies if your inquiries are not answered (nothing personal).
Hope this helps
but after that it stopped
Facebook
Twitter
Instagram