Encryption unsuccessful

[JC]

Hello,

When building the ICS as a rootfs, and deploying it through an SD card, I am getting an "Encryption unsuccessful" screen, followed by the "Encryption was interrupted and can\'t complete. As a result, the data on your tablet is no longer accessible." message.

What causes this message and how can it be disabled, to allow the system to load up?

Thanks,

[Jean-Baptiste Queru]

If you're on a PandaBoard, be sure to follow the instructions
carefully, specifically "fastboot flash userdata" and then "fastboot
flashall" (without -w).

For anything else, this sounds like a porting issue. Please ask android-porting.

JBQ

> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>

--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.

Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.

[JC]

Thanks, will do so. Indeed, using the fastboot instructions in the Pandaboard readme file all goes through just fine.

[Jean-Baptiste Queru]

Yup, with encryption support in ICS, Android has become a lot more
picky about having all the filesystems initialized with valid data,
and mistakenly assumes that anything that's not zero or valid is
encrypted, refusing to go any further.

In Gingerbread and before, anything that wasn't valid was expected to
be invalid, and Android would just re-initialize it, regardless of
whether it was zero or not.

You're lucky you didn't have to work with Honeycomb, where zeros were
considered encrypted.

JBQ

On Thu, Dec 1, 2011 at 7:58 AM, JC <jcra...@gmail.com> wrote:
> Thanks, will do so. Indeed, using the fastboot instructions in the
> Pandaboard readme file all goes through just fine.
>

[JC]

Thanks so much JBQ for the details.

The reason I am asking the question is that I am trying to setup the x-loader, u-boot, kernel based on the omapzoom, compile them, and then run in top of them the ICS. We will use an OMAP4460 on our product, and - in the mean time - am using Pandaboard to get the tool set ready.

There were other problems I have encountered so far, including the creating of the rootfs, via the mktarball.sh.

But now this encryption problem seems to be a little more involved. Anyways, I have posted the question to the porting group, and in the mean time, am starting to dig deeper into ICS, to see if encryption can be bypassed.

[abhimanyu singhal]

Probably you might have got the solution by this time but I too faced the same issue, where I used my modified xloader/uboot and kernel and was avoiding fastboot
Problem is due to cryptfs looks for another partition for footer and key initially. Generally we make two partitions 1) xloader/uboot/kernel 2) Android fs.
For disabling encryption I disabled the feature from system/core/init/builtins.c where it sets the property for crypto

In do_mount()
- property_set("ro.crypto.state","encrypted");
+ property_set("ro.crypto.state","unencrypted");
- property_set("vold.decrypt",1);

Android ICS boots without encryption on panda and on blaze-mdp.
cheers!