Hi Hackborn

I do not think it's device-level work or only porting issue, but the
understand to Android recovery feature.
Anybody familiar with recovery, can help?

Thanks.

On Jul 24, 2:25 pm, Dianne Hackborn <[email protected]> wrote:
> Hi, questions about device-level work should be posted to android-porting.
> Thanks.
>
>
>
> On Thu, Jul 23, 2009 at 11:06 PM, Xinyu Chen <[email protected]> wrote:
>
> > Hi
>
> > I'm doing enhancement to Android recovery feature for Freescale's i.MX
> > platform.
> > Main target is to add EXT3 partition support based on the original MTD
> > partition, and let android rootfs running on movi-nand or SD card can
> > do recovery.
>
> > As the normal recovery procedure, recovery service unpacks the
> > update.zip after reading update command. It reads the public key in /
> > res/keys from rootfs into a structure before apply the update-script:
> > typedef struct RSAPublicKey {
> >    int len;                  /* Length of n[] in number of uint32_t
> > */
> >    uint32_t n0inv;           /* -1 / n[0] mod 2^32 */
> >    uint32_t n[RSANUMWORDS];  /* modulus as little endian array */
> >    uint32_t rr[RSANUMWORDS]; /* R^2 as little endian array */
> > } RSAPublicKey;
> > This public key is used to decrypt the .SF file's signature stored
> > in .RSA file, and compare to the .SF file's SHA-1 digest. This makes
> > sure .SF file is correct.
> > So in our recovery implement, we will have own keystore, and create
> > own /res/keys.
> > But I can not find the res/keys file in the android source or, in the
> > recovery image which used to hack G1 to get root permission.
>
> > My question is:
> > 1. Does the hacked recovery rootfs image remove this verification
> > codes? (As I dump the recovery binary, seems no "res/keys" symbol)
> > 2. What's key file's format, and how to generate it from a
> > certification file?
>
> > Thanks.
>
> > BR
> > Xinyu Chen
>
> --
> Dianne Hackborn
> Android framework engineer
> [email protected]
>
> Note: please don't send private questions to me, as I don't have time to
> provide private support, and so won't reply to such e-mails.  All such
> questions should be posted on public forums, where I and others can see and
> answer them.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to