當前位置：首頁 >

生成release版本的Android系统

發(fā)布時間：2025/4/5 46 豆豆

生活随笔收集整理的這篇文章主要介紹了生成release版本的Android系统小編覺得挺不錯的,現(xiàn)在分享給大家,幫大家做個參考.

1.使用platform密鑰對apk進行簽名

1.1.進入<Android_Source_Path>/build/target/product/security,找到【platform.pk8】和【platform.x509.pem】系統(tǒng)密鑰。
1.2.進入<Android_Source_Path>/build/tools/signapk找到SignApk.java，運行javac編譯成SignApk.class
1.3.執(zhí)行命令java com.android.signapk.SignApk platform.x509.pem platform.pk8 input.apk output.apk

至此，完成。

2. 對1的補充：

<Android_Source_Path>/build/target/product/security下有多對密鑰，詳細如下：

The following commands were used to generate the test key pairs:

? development/tools/make_key testkey? '/C=US/ST=California/L=Mountain View/O=Android/OU=Android/CN=Android/emailAddress=android@android.com'
? development/tools/make_key platform '/C=US/ST=California/L=Mountain View/O=Android/OU=Android/CN=Android/emailAddress=android@android.com'
? development/tools/make_key shared?? '/C=US/ST=California/L=Mountain View/O=Android/OU=Android/CN=Android/emailAddress=android@android.com'
? development/tools/make_key media??? '/C=US/ST=California/L=Mountain View/O=Android/OU=Android/CN=Android/emailAddress=android@android.com'

The following standard test keys are currently included:

testkey -- a generic key for packages that do not otherwise specify a key.
platform -- a test key for packages that are part of the core platform.
shared -- a test key for things that are shared in the home/contacts process.
media -- a test key for packages that are part of the media/download system.

These test keys are used strictly in development, and should never be assumed
to convey any sort of validity.? When $BUILD_SECURE=true, the code should not
honor these keys in any context.

signing using the openssl commandline (for boot/system images)
--------------------------------------------------------------

1. convert pk8 format key to pem format
?? % openssl pkcs8 -inform DER -nocrypt -in testkey.pk8 -out testkey.pem

2. create a signature using the pem format key
?? % openssl dgst -binary -sha1 -sign testkey.pem FILE > FILE.sig

extracting public keys for embedding
------------------------------------
it's a Java tool
but it generates C code
take a look at commands/recovery/Android.mk
you'll see it running $(HOST_OUT_JAVA_LIBRARIES)/dumpkey.jar

3.對3的補充：

在運行第三步的命令前，請在你當前的工作目錄下新建如下結構的文件夾:com.android.signapk，然后將第二步編譯生成的SignApk放入該目錄下。或者也可以將SignApk.java的package聲明刪除后再運行javac編譯。

命令java com.android.signapk.SignApk platform.x509.pem platform.pk8 input.apk output.apk

不單可以對apk文件進行重簽名，也可以對所有的zip文件進行重簽名，包括ROM文件。

網(wǎng)上Android數(shù)字簽名大多是與Android APK相關，而介紹Android系統(tǒng)簽名的方法卻不多。正巧前段時間幫別人做CTS 認證，需要用到給Android系統(tǒng)簽名。

為什么需要給Android系統(tǒng)簽個名才能進行CTS認證呢？原來我們通過make -j4編譯出來的system.img使用的是test key,這種類型的key只適用于開發(fā)階段，而且這種秘鑰是公開的，誰都可以使用。當發(fā)布一款android產(chǎn)品，就需要另外給整個系統(tǒng)簽個名，防止被別人盜用。這種系統(tǒng)就是release版本的Android系統(tǒng)。

下面就詳細介紹下整個過程。

1、生成加密key文件

要對Android系統(tǒng)進行簽名，需要生成四種類型的key文件。

a)releasekey

b)media

c)shared

d)platform

我們就拿releasekey為例簡單介紹下生成過程。

1）進入/android_src/development/tools目錄。

/development/tools$ ls
apkcheck? etc1tool??? hosttestlib? jdwpspy?????? makedict???????? mkstubs???????

axl?????? findunused? idegen?????? line_endings? make_key??? monkeyrunner??? zoneinfo

2）使用make_key工具生成簽名文件

development/tools$ sh make_key releasekey '/C=CN/ST=JiangSu/L=NanJing/O=Company/OU=Department/CN=YourName/emailAddress=YourE-mailAddress'

Enter password for 'releasekey' (blank for none; password will be visible): mypassword ??? <------- 設置你的密碼
creating platform.pk8 with password [mypassword]
Generating RSA private key, 2048 bit long modulus
...............+++
........................................................+++
e is 3 (0x3)

這里要順便介紹下make_key的參數(shù)。第一個參數(shù)是要生成key的名字，第二個參數(shù)是關于你公司的信息。

key的名字很好理解，就是前面提到的4中類型的key，公司信息的參數(shù)比較多，它們的含義如下：

C?? --->? Country Name (2 letter code)
ST? --->? State or Province Name (full name)
L?? --->? Locality Name (eg, city)
O?? --->? Organization Name (eg, company)
OU? --->? Organizational Unit Name (eg, section)
CN? --->? Common Name (eg, your name or your server’s hostname)
emailAddress --->? Contact email address

這樣就生成了一組releasekey,另外3種類型的key的生成方法也基本一樣。

生成后的結果如下：

/development/tools$ ls
makedict? media.pk8?????? mkstubs?????? platform.pk8?????? releasekey.pk8?????? shared.pk8??????
?make_key? media.x509.pem??? platform.x509.pem? releasekey.x509.pem? shared.x509.pem

*.pk8是生成的私鑰，而*.x509.pem是公鑰,生成時兩者是成對出現(xiàn)的.

2 、把pk8和x509.pem文件拷貝到vendor/Modul/security/product_modul目錄

/android_src/vendor/Modul/security/product_modul$ cp ../../../../development/tools/*.pk8 ./
/android_src/vendor/Modul/security/product_modul$ cp ../../../../development/tools/*.pem ./

這一部雖然不是必須的,但最好還是這樣做下,由于牽涉到項目的原因,產(chǎn)品和產(chǎn)品型號就用Modul和product_modul代替了.

3 、回到根目錄android_src

/android_src/vendor/Modul/security/product_modul$ cd ../../../../

大家看后肯定覺得這一步很多余,根本沒有必要單獨提出來,但后來證明把這步提下還是很有必要的,因為第5步的操作必須要在根目錄下執(zhí)行,不然會出錯.在這一點上我是吃了不少苦頭.

4 、編譯系統(tǒng)

/android_src$ make -j4 PRODUCT-product_modul-user dist

這個怎么跟平時的編譯不一樣,后面多了兩個參數(shù)PRODUCT-product_modul-user 和 dist. 編譯完成之后回在/android_src/dist/目錄內(nèi)生成個product_modul-target_files開頭的zip文件.這就是我們需要進行簽名的文件系統(tǒng).

5 、開始簽名

android_src$ ./build/tools/releasetools/sign_target_files_apks -d vendor/Modul/security/product_modul/ out/dist/product_modul-target_files.zip? out/dist/signed_target_files.zip
ERROR: no key specified for:

? CalendarWidget.apk
? Contacts_yellowpage.apk
? SnsAppMain.apk
? fbandroid-1.5.0.apk
? AnalogClockWidget.apk
? MessageWidget.apk
? NewsWidget.apk

上面的意思是使用sign_target_files_apks工具采用vendor/Modul/security/product_modul/下的key對product_modul-target_files.zip文件進行簽名,并把簽名結果放在out/dist/signed_target_files.zip里.

從上面的簽名結果看,簽名并沒有成功,原因是由于有些apk程序已經(jīng)簽過名了或者找不到對應的key. 這也難不倒我們,我們可以通過設置過濾,不對上面的程序進行簽名.方法如下:

通過參數(shù)"-e <apkname>=" 來過濾這些程序.

android_src$ ./build/tools/releasetools/sign_target_files_apks -d vendor/Modul/security/product_modul/? -e? CalendarWidget.apk=? -e ? Contacts_yellowpage.apk= ? -e? SnsAppMain.apk=? -e fbandroid-1.5.0.apk=? -e AnalogClockWidget.apk=? -e MessageWidget.apk=? -e? NewsWidget.apk=? ? out/dist/product_modul-target_files.zip? out/dist/signed_target_files.zip

Enter password for vendor/Modul/security/product_modul//media key>???????? <----- imput the password
Enter password for vendor/Modul/security/product_modul//platform key>????? <----- imput the password
Enter password for vendor/Modul/security/product_modul//releasekey key>? <----- imput the password
Enter password for vendor/Modul/security/product_modul//shared key>??????? <----- imput the password
rewriting RECOVERY/RAMDISK/default.prop:
? replace:? ro.build.tags=test-keys
???? with:? ro.build.tags=release-keys

NOT signing: CalendarWidget.apk
NOT signing: Contacts_yellowpage.apk
??? signing: Mms.apk????????????????????????????
??? signing: SoundRecorder.apk??????????????
??? signing: AccountAndSyncSettings.apk?????????
??? signing: Camera.apk??????????????????????????
.......................................................................
rewriting SYSTEM/build.prop:
? replace:? ro.build.tags=test-keys
???? with:? ro.build.tags=release-keys
? replace:? ro.build.description= test-keys
???? with:? ro.build.description= release-keys
? replace:? ro.build.fingerprint=...........................
???? with:? ro.build.fingerprint=.............................
??? signing: framework-res.apk????????????????????
done.

這樣就完成了android系統(tǒng)的簽名工作.

6 、生成image文件

android_src$ ./build/tools/releasetools/img_from_target_files? out/dist/signed-target-files.zip? out/dist/signed-img.zip
creating boot.img...
creating recovery.img...
creating system.img...
creating userdata.img...
cleaning up...
done.

使用img_from_target_files工具生成signed-img.zip文件.signed-img.zip文件包含了boot.img,userdate.img,system.img文件等.

7 、通過fastboot下載signed-img.zip文件

fastboot update signed-img.zip

通過fastboot就可以把簽了名的系統(tǒng)文件下載到手機上了。

介紹android APK簽名的方法有很多，下面這篇文章寫的挺不錯,有需要的可以參考一下.

http://yangguangfu.iteye.com/blog/723182

自己的key：

. make_key releasekey