[Captivate Android Development] Woody:
I have been following both threads as well, as I have a Vibrant (many users are being hit with this error) and a TF101 and the partitions are set up differently but other than that, the error is still the same. It isn’t a hardware failure but rather a software failure that is causing the error when running ICS. I have a theory, see below.

I had this whole message typed out and then my stupid work firewall logged me out and wiped my message clean. So here it is re-dux.

My wife got a Nook Color (not a Nook Tablet-fyi) yesterday and it has this ability to run ROMs off the SDcard much the same way that your PC can boot off a CD, all the while leaving the stock OS integrity perfectly untouched (very nice feature btw). What you do is burn the img to a MicorSD card and it creates a “mock” internal partition and then the external is Fat32. So I downloaded Rack’s Dual Boot SD IMG which runs CM7.2 and CM9. I booted up into CM7, installed Gapps and let it run. Booted up into CM9, installed Gapps and let it run. She decided that she wanted to rum CM9 as her daily driver, so I set it up that way.

So now you are probably wondering why is he talking about a Nook Color when this is a phone issue (Patience. Need to show how I got to the result). She started to reinstall all of her apps from the market when I thought why not put her TBpro folder on the card and reinstall them that way. I mean that is the whole reason for TB right? So I mounted the NC to the PC and it auto-installed the necessary drivers and then I remembered that ICS uses MTP instead of Mass Storage (from my exp with my TF101). I clicked on the device anyways and lo-and-behold, I saw the internalSD partition that had the img and Gapps on it, as well as the ExternalSD (fat). I tried to copy over the TB folder to the Fat partition and it failed. So, I rebooted into CM7 and plugged it in. No device found. I went into Device Manager and uninstalled the drivers that CM9 installed, rebooted the PC and plugged the NC in. The driver began to install. Once that was done, I copied the files over just fine.

Here is where it all comes together. I rebooted back into CM9 and was greeted with the Encryption Error. I know enough not to hit RESET and I just powered down and back up. It booted fine the second time. Then I checked to make sure the TB folder I had copied over was there and it was bc it was on the Fat partition. I began to install/restore some apps and started to get FCs for every Gapp I had. After panic subsided, I realized what had happened. Since the Gapps were installed on the mock “internal” partition that I had created on the MicroSD, they were now FC-ing b/c that partition was now corrupted. So while I was able to reboot into the ROM, the damage was done and the “internal” was fried. The error doesn’t get thrown until your NEXT reboot (either manually or through something like UV or random reboot) after you try to mount to PC. This is where the ability to boot from SDcard was key.

*********************

I reformatted the sdcard and re-burned the img to it. I was able to repeat this 8 times with the Encryption Error and 8 times without it (only stopped bc it was getting late and I was getting a headache) Each time I got that error was when I was trying to mount to the PC through MTP. The issue isn’t hardware, it is software and how the ICS ROMs mount to the PC. I have feelers out in the Vibrant forums on XDA and Rootz and a few of them have come back stating that they didn’t get this issue until they tried to mount to the PC.

We never had this happen on Froyo, Gingerbread or Honeycomb b/c MTP wasn’t introduced until ICS came out. This is effecting many different types of phones, ROMs (AOSP and AOKP alike) and now 2 know tablets (TF101 and my wife’s NC). All of them running ICS. My solution to avoid this is to unmount your external SD card and copy over the files from your PC through a card reader and then reinsert the card in the phone. Sure it is a pain but isn’t the Error worse?

ps- sorry for the long post but the more you know, right?