How to sign android x86 with release keys

[shridutt kothari]

Hi All,

The standard procedure to sign the AOSP build with release keys mentioned on below URLs

1. http://jhshi.me/2014/11/09/aosp-release-tools/

2. https://android.googlesource.com/platform/build.git/+/android-4.2.2_r1/tools/releasetools/sign_target_files_apks

is not working for Android-x86 code.

Typically few commands are not working in Android-X86 environment:

like make dist, and sign_target_file_apks as we do not have a zip file here instead we only have a single iso file.

Any suggestion on how to sign the iso while building with release keys.

--

Thanks,

Shridutt

[Henri Koivuneva]

Hi!

I haven't tried that, but maybe you could do mka first, then go to out/target/product --> to find the built all files in the system folder there. Then if it's possible to sign them and the other required stuff, try that, and then do mka iso_img? I wonder if this could work for you. Please report back.

That should use the signed files from the out folder. This way I've experimented with integrating various prebuilt things like fonts and apps.

[DDS Central]

Why bother ? This seems nothing more than a cosmetic change in About box.

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+unsubscribe@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.

[Henri Koivuneva]

Yeah. Mostly cosmetic. If building it for devices that will be sold or used in work environments etc. It can be used to verify the image has been signed with the private release keys owned by that company, and not some third party or a possible hacker.

Some root detectors in apps can be triggered by test-keys flag too.. though I haven't faced any yet that I remember. 

Example: http://www.skholingua.com/blog/detecting-root-andorid

Why would the build need to be signed with release-keys in your case?

You received this message because you are subscribed to a topic in the Google Groups "Android-x86" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-x86/DCXcqgirBKA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to android-x86+unsubscribe@googlegroups.com.

[shridutt kothari]

I have signed individual files with my release keys, i have only one issue now, As in AOSP with the standard procedure the final system, boot images are also signed with release keys.

How can we sign our iso_img with release keys? 

Because even after signing each file with release keys, the after booting device shows "build is signed with test keys" in the settings -> about screen. (See attached file)

Any idea on signing the final ISO, like we sign in AOSP??

Thanks.

Shridutt

[Chih-Wei Huang]

It doesn't make sense to sign the ISO.
The android itself knows nothing about the ISO.
Let alone its signature.

I guess you need to rebuild the whole image
after you changed the keys.


--
Chih-Wei
Android-x86 project
http://www.android-x86.org

[shridutt kothari]

Hi Chih,

I have replaced the keys, but after rebuilding it's still showing test keys as shown in previous image, 

Whereas when i download Android-X86 iso from http://www.android-x86.org/download, it shows ROM is signed with release keys in the Settings screen.

So please can you tell what steps you follow exactly before releasing Android-X86 ISOs on the website.

Thanks,

Shridutt