[REF][ICS] Encryption Unsuccessful Reference

---

Please keep all discussion/theories/questions/general complaints in the original "Encryption Unsuccessful" thread! We need to keep this one clean so we can get to the bottom of this. Meaning, do not post here unless you have facts or something with repeatable results!

This thread is to contain all relevant reference information in regard to the "Encryption Unsuccessful" error seen in this thread. There were many users who encountered this error, and there were also many potential fixes posted in that thread, but most of the usefulness is buried within the clutter and confusion. We decided to create this thread in order to keep track of the important details and things that can be proven as fact.

If you do have something to post here, you must report the following information:
ROM:
Kernel:
When the error happened:
How the error happened:
The steps taken to reproduce/resolve the issue:



or if you need to make a different kind of report, just make sure it belongs here and not in the other thread.

See second post for references.

Work in progress... More to come later

Things to try first after getting the error (try not to press "reset phone"):
-Reboot
-Reboot w/o external SD
-Reboot recovery, factory reset, reboot
-Flash CM7
-Flash to stock

Things we know so far:
-The error can result in loss of access to the internal SD card and /data, no matter what is done to the phone.
-The error happens when the Android system cannot mount /data, therefore assuming it is encrypted and throwing the error. We don't know exactly why it results in the data lockout.
-Pressing "Reset Phone" may or may not affect this
-This error is happening across a wide range of devices and ICS ROMs, not limited to the Galaxy S series
-Sometimes, the lockout can be avoided
-The error can happen when the phone is first booted, or may be on the screen when pulled out of your pocket (most common). Often, a user finds the phone stuck on the bootanimation, but it is very dark. A reboot will then bring up the error.
-Data can be recovered, but currently only in isolated cases without repeatable results.
-Data recovery seems to be random

-Users who get this have had battery issues in some cases. Investigation underway... I don't think this is important
-Users who got a random fix seem to be using Glitch kernel... may or may not be important... Kernel may play a role
-Removing/switching external sd can trigger EU again


Possible causes:
-MTP not unmounting properly (strong arguments for and against this)
-Hardware
-eMMC firmware bug, or similar issue

Possible solutions (after losing access to sdcard and /data):
-Glitch kernel flash Link
ROM: Slim 3.0
Kernel: Semaphore 1.0 scbm
Before the error: Phone was OC'd
Solution: 1-2 months after recieving the error, the user flashed an extracted boot.img of Glitch kernel from Doc's ROM. A week later, all of the original files showed up in recovery. The user rebooted and saw "android is upgrading" and all files from /data and /sdcard were back in their original place, but applications and wifi were having issues. User wiped data and all went back to normal. Since it wasn't an immediate result, it's unclear whether the kernel flash is directly related.
Other: User had external sd fix applied on 32GB sd

-Battery Death
ROM: Infinitum 2.2
Kernel: Glitch B6
Before the Error: User flashed Infinitum, and got the error. They pressed "reset phone" and lost access to their data.
Solution: The battery died, and phone was dead for 8-12 hours. Upon turning on the phone, user saw both sd cards and could access /data.
Other: User had external sd fix applied



eMMC Bug (on other devices):
http://www.xda-developers.com/androi...d-ics-kernels/
and http://forum.xda-developers.com/show...1644364&page=1

Based on this^ (if it is indeed the cause (which it isn't...)):
-A bug in eMMC firmware causes it to corrupt and fail, usually unrecoverable by any means
-The data partition fails because it is the most accessed
-Certain kernel setups can trigger/prevent this
-Caused by wiping data (or perhaps large operations)
-This explains losing /data, but not the sdcard. Perhaps triggered by the synthetic encryption?
-While parts of the eMMC are gone, it is possible to resize the partitions around the bad area. Works on Galaxy Note, may work for us. Not a solution, but a temporary fix.
-This entire theory could be made invalid by the differences between Galaxy S and the phones in those threads.

From my data so far: There really doesn't seem to be any kind of pattern (I could be overlooking something)

^Don't rely on this theory. Our devices are different, and are facing a slightly different issue. Our issue also involves non-Samsung devices, while the above issue is because of Samsung software. I am still collecting data from users on this because it's possible that there is some kind of remote connection.

Well it seems we don't have the same issue. But the similarity of the outcome of these issues could still mean we have a similar issue where hardware ends up failing.


Incident threads:
-[Guide] Encryption Unsuccessful - Reset Android [ICS Issue]
-Encryption Unsuccessful - Fixed



Resources:
-Notes on the implementation of encryption in Android
-Cyanogen's Post
-eMMC Corruption bug discussion

Effected Devices:

Samsung Captivate~~~(Roms->Infinitum 2.2 (CM9) with 3.1.10_IcyGlitch, Slim ICS 3.6 w/ Semaphore 1.1.1sc, Cyantablet 9)
Samsung Vibrant ~~~~ (ROMs-> CM9, AOKP, Zenwich, Passion, Euphoria, Doc's)
Asus Transformer TF101 ~~~~ (ROMs ->CM9)
Asus Transformer TF101g [3g version] ~~~~ (ROMs ->CM9)
Nook Color [not Nook Tablet] ~~~~ (ROMs ->Rack's Dual Boot Cm7/CM9)
Samsung Galaxy SII <--This seems to hark that something is wrong with the EFS but Adam Outler tried something along the similar lines and it didn't pan out.

Will update with more information when something new comes available.

Change Log:
5/20/12 - Put in Hyperlinks to threads/posts where the error was reported or "fixed"

A link that may play a part...

---

Originally Posted by korockinout13

Work in progress... More to come later

Things to try first after getting the error (and not pressing "Reset Phone"):
-Reboot
-Reboot w/o external SD
-Reboot recovery, factory reset, reboot
-Flash CM7
-Flash to stock

Things we know so far:
-The error can result in loss of access to the internal SD card and /data, no matter what is done to the phone.
-The error happens when the Android system cannot mount /data, therefore assuming it is encrypted and throwing the error. We don't know exactly why it results in the data lockout.
-This error is happening across a wide range of devices and ICS ROMs, not limited to the Galaxy S series
-Sometimes, the lockout can be avoided
-The error can happen when the phone is first booted, or may be on the screen when pulled out of your pocket. Seems random.
-Data can be recovered, but currently only in isolated cases without repeatable results.

Possible causes:
-MTP not unmounting properly

Possible solutions (after losing access to sdcard and /data):
-Glitch kernel flash Link
ROM: Slim 3.0
Kernel: Semaphore 1.0 scbm
Before the error: Phone was OC'd
Solution: 1-2 months after recieving the error, the user flashed an extracted boot.img of Glitch kernel from Doc's ROM, and all files were back in their original place. Happened after a week of being on the kernel, so it is unclear whether that is directly related. More info to come...
Other: User had external sd fix applied.

-


Incident threads:
-[Guide] Encryption Unsuccessful - Reset Android [ICS Issue]
-Encryption Unsuccessful - Fixed


Resources:
Notes on the implementation of encryption in Android

Hi, I'm the guy who posted that glitch kernel possible fix post. I was reading what Barney Fyfe posted as his fix, and found something in common. I used a 32gb sd card when I applied the work around. I have no idea if that can play a part in accessing the internal sdcard. I'm just trying to make a connection with why both of us were able to recover our data.

My encryption issue has not reproduced (yet, and hopefully never again), but have since changed my kernel to Devil's Beta and still have access. Hope this can help...

* I was using a 16gb external sdcard before the encryption error came. Changed to 32gb to compensate for lost space.
* After applying work around, access was still restricted to internal for 1-2 months

SMH, even after posting all that stuff in big bold letters, I still posted here..... Sorry.

Bump TTT

There has been 3 people as of the past 2 days that have either come back from the Error or got it, hit Reset and did not get Encrypted.

My Captivate got the reset problem and lost the internal card, a couple of weeks later, the battery died and when I turned it on, the internal card was there again. I didn't do anything but here's what happened.

I started from a CM7 Mubi ROM (don't remember the kernel) and I flashed Infinitum 2.2 (CM9) with 3.1.10_IcyGlitch[INDENT] v14-b6-I896-I897. Then I pressed Reset and lost the card. I flashed Mubi again before realizing it wasn't gonna do anything so I flashed Infinitum 2.2 again.


I applied the solution from the Encryption Guide:

# internal sdcard
dev_mount sdcard /mnt/emmc 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0

# external sdcard
dev_mount emmc /mnt/sdcard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2

I used my phone relatively normal for a few days. At this point, I'd been using 2 Chinese extended batteries that kept dying sometimes after a couple of hours of use, sometimes if the phone was shaken. So a few days ago, the phone died the same way as always, it was dead for several hours, maybe 8-12 but less than 24.

When I turned on the phone, I kept getting 'Unfortunately X program has stopped' for many apps and half my widgets weren't there. So I decided to flash Infinitum LBR (but didn't yet). When I connected the phone to the computer, I saw both cards so I disconnected the phone and realized that both cards were now available, that would be the 3 partitions:

1) Internal Storage 1.85GB
2) USB Storage 13.03GB
3) SD Card 12.92 GB

From the File manager I see:

1) Home>mnt>emmc (which is also shown as Home>emmc, the files are the same)
2) Home>sdcard

I flashed Infinitum LBR and both cards were still there.

SOME of the new apps are installed on mnt/sdcard/android/data

On mnt/emmc I see some of the same folders with older dates (I assumed they're from their previous installation before the reset problem occurred) but I also see newer folders (from today and yesterday).

I don't know which folders are installation files and which are just data. korockinout13 asked if I could access /data, I can but it's empty.

Sorry if I'm not clear enough, I'm still confused.


Edit 1: Dunno if this is relevant but I'll post it just in case.
It seems that both the OP in Encryption Unsuccessful - Fixed and me had battery issues. In my case, my batteries just died randomly but I was able to charge them. My batteries are still crapping out but they last longer.

Edit 2: One thing I forgot to mention is that the vold file doesn't look like above, it looks like this:

# internal sdcard
dev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0

# external sdcard
dev_mount emmc /mnt/emmc auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2

Update 2012-05-30: I noticed that with an app like Headset Button Controller, my profiles aren't saved for good. I mean, they are for a few days (even after removing the battery) and all of sudden, the profiles are gone. I'd used the app for months without any problem until the cards issue so it might be related. I'll email the dev just in case.

Thank you for sorting out all the info, the original thread is now way too lengthy to read.
Although I have a new phone now, I do want to get all the photos and messages in my internal SD back

Originally Posted by korockinout13

If you do have something to post here, you must report the following information:

ROM: Slim ICS 3.6
Kernel: Semaphore 1.1.1sc
When the error happened: 7pm central, 05/18/12. A few minutes prior, I was running a game called Word Off. That was the only new app I'd installed that day. I'd been on SlimICS/Semaphore for about a month prior.
How the error happened: Pulled phone out of my pocket, saw an unfamiliar animation on the screen (it looked like a horizontal gray bar, cycling -- possibly a dark Slim ICS boot screen). Phone was unresponsive. Pulled the battery and rebooted. Got the Encryption Unsuccessful screen on reboot, and I pushed the Reset Phone button (sorry -- hadn't seen this thread yet).
The steps taken to reproduce/resolve the issue: It appears CWM is mounting my external SD card as /sdcard, and can't mount anything as /emmc. I'm 90% sure that's backwards, but don't know why it would be happening. (Or maybe that's normal in this situation and I just haven't seen it yet.)

I can mount the external SD card just fine on USB using CWM and transfer files to it.

Now I'm rebooting without the external SD several times to see if that fixes it. Assuming it doesn't, I'm going to do a Heimdall or Odin flash to CM7 or stock and go from there.

Any suggestions or other things I should try in the name of science?

UPDATE: Formatted my (external) SD card using CWM. Installed Slim 3.7 and we're back in business. Using the vold.fstab hack from here to remap. This seemed much faster than doing a full Heimdall or Odin wipe, and I don't really need both internal and external SD cards anyway.

ROM: Cyantablet 9
Kernel: The one that comes with the ROM
When the error happened: 18/5. Had been using GB MIUI.
How the error happened:Flashed to Cyantablet 9 and in the first boot i got the encryption message. I pressed the reset button. It rebooted into that android symbol and after like 10 seconds it rebooted again into the ROM. I immediately tried accessing my SD cards and both internal and external are working fine.

Samsung Vibrant


C:\1>adb shell
~ $ su
su
root@android:/ # cd /sys/class/block/mmcblk0/device
cd /sys/class/block/mmcblk0/device
root@android:/sys/class/block/mmcblk0/device # cat name hwrev fwrev manfid oemid
date type serial cid
wrev manfid oemid date type serial cid <

0x1
0x0
0x000028
0x4245
02/2012
SD
0xbf06287b
284245202020202010bf06287b00c200
root@android:/sys/class/block/mmcblk0/device #