Originally Posted by dpmurphy81
One can assume that the captivate can have this problem also the hardware is no different really from the vibrant. And I feel in my opinion that it is related to the quality of the flash memory chip itself weather you have this problem. compound this with the relentless conversion of the RFS file system it is just a matter of time I believe. The trade off of speed is stability. But that is only my opinion...
That actually is a pretty big assumption. Just because two phones appear "similar" based on the published specs doesn't mean their insides are at all related. We already know that from a strictly hardware standpoint, even the two GSM cousins in America (the Vibrant and the Captivate) have different physical hardware inside, and many other versions of the i9000 abroad vary quite a bit too. Samsung produces these phones in very large batches, and who knows exactly what the differences are in the individual components put onto each board.
And as far as I'm aware, there's not been a single case of repeated "lag fix" operations causing damage to the hardware. Which makes sense when you think about it too. If I load a single 720p movie onto my internal SD (OneNAND), that probably requires a lot more NAND cells to be touched than an entire system/data/dbdata/cache lag fix being applied. Since all those operations really do is backup the partition, delete the partition, format a new partition, and then restore the data back over. Not really the most intensive thing you can do with your internal SD...
The OP's problem probably lies somewhere in PEBKAC. Not unmounting storage cleanly from the PC, or accidentally unplugging during a file transfer, battery came out unexpectedly at some point, etc. I end up re-flashing my ROM so regularly that I never really have time for little problems to build into big problems, but that might have happened here. Just so many corrupt sectors before the OS finally gives up trying to deal with it. Either way, since formatting seems to have fixed the problem, and this storage is solid-state, not mechanical, the problem is probably not in the hardware.
- Samsung Galaxy S 4 (SGH-i337) -- Custom i9505 build | KT's latest i337 kernel | Primary Phone
- Samsung Galaxy S II (SGH-I777) -- CM 10.1 | Kernel Varies | Backup Phone