Don't want to lose the ones that are really making a difference.
i717 running Seraphim Collective ICS with tapatalk2
Vibrant users: MTP may be the culprit in your cases. I suggest you create a thread under your forum.
Captivate users: My Captivate, as well as others', threw the error at random. No PC, no MTP, no fanciness. In my case, I pulled my captivate out of my pocket and the error was there.
AFAIK, the internal SD (mmc0/movinand) won't be resuscitated by any Android/OS fixes, as it was confirmed "defective" by the SBL, a set of factory tools, built-in the phone, that is independent of the OS.
Agree, it shouldn't have anything to do with MTP or mass storage. First of all, when my movinand failed it was totally at random, and secondly, USB mounting (whether MTP or mass storage) accesses mmc0 on the filesystem level. It doesn't even access at the block level (since /data is also on the same block device), much less the SD/MMC hardware interface level.
What rom was that ? It's rather strange he got it at first boot as most report it was sudden and the phone was working correctly for a period of time.
Also i'm questioning, what about external sd's ? After reading the OP again i think we should also include if a external sd was present at the moment people got the error message and not just the rom. I'm no divine but i suspect there could be more involve then we think regarding the MTP, the rom used and external sd.
|captivate, encryption, galaxy s, ics|
|Thread Tools||Search this Thread|