• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Apps [How-To] Signing ROMs

after signing update.zip, put in /mnt/sdcard apply update from sdcard
E:signature verification failed

i can't install recovery;img too, no device found with bm drivers

shit!
 
Why not working for me? i have followed all the steps, sign successfull a zip rom. when i want to flash the signed rom i got "validade certification failed" :( what is the problem? :( please i need help, my tablet is dead
 
I am doing R&D on FOTA(Firmware Update Over the Air) using Nexus 7-Wifi(grouper). For which I followed the following steps.

1. Downloaded the android source from source.android.com for v 4.2.2_r1 and v 4.3_r1
2. Downloaded the binaries for grouper, extract it to my source folder.
3. Then I compiled the source code using following commands.
i. source build/envsetup.sh
ii. lunch full_grouper-userdebug
iii. make -j8 dist
4. After few tries, I had success in compiling the source for Nexus 7(grouper).
5. I got following files in $out/source_4.2.2/dist folder
-----------------------------------------------
adb*
android-common-carousel.jar
android-common.jar
android-info.txt
android-support-v13.jar
android-support-v4.jar
android-support-v7-gridlayout.jar
build.prop
com.android.nfc_extras.jar
fastboot*
full_grouper-apps-eng.root.zip
full_grouper-emulator-eng.root.zip
full_grouper-img-eng.root.zip
full_grouper-ota-eng.root.zip
full_grouper-symbols-eng.root.zip
full_grouper-target_files-eng.root.zip
gpl_source.tgz
guava.jar
installed-files.txt
jsr305.jar
mkbootfs*
mkbootimg*
mkyaffs2image*
mp4parser.jar
package-stats.txt
ramdisk.img
signapk.jar
vendor_owner_info.txt
-----------------------------------------------
6. Then I generated my own keys using /development/tools/make_key tool for media, testkey, releasekey, shared, platform.
Assume my keys are locate at /keys folder.
7. Then I created a signed target zip file using following command.
/source/build/tools/releasetools/sign_target_files_apks -v -p ../host/linux-x86 -d /keys full_grouper-target_files-eng.root.zip signed_target_files.zip
8. From signed target zip file I create
/source/build/tools/releasetools/img_from_target_files -v -p ../host/linux-x86 signed_target_files.zip signed_img_from_target_files.zip
9. Then I flashed the signed_img_from_target_files.zip using fastboot command using the following script:
----------------------------------------------------------------------
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot reboot-bootloader
sleep 10
fastboot -w update signed_img_from_target_files.zip
----------------------------------------------------------------------
10. The device gets flashed well and is working, but I am getting an log while flashing in which it is unable to find boot.sig, system.sig and recovery.sig
11. Now the otacerts.zip file contains a testkey which is not the one that I signed it with.
file located at "/system/etc/security/otacerts.zip" on device.
12. Now since the otacerts.zip is signed with the default key it gives a mismatch error which I tried to flash an OTA update which is signed by the my custom key.

Now my doubt is:
How can I add boot.sig, recovery.sig and system.sig to signed_img_from_target_files.zip?
Is there anything I am doing wrong?
Does the recovery checks the current ROM keys from "/system/etc/security/otacerts.zip"?
What is the correct procedure to sign the OTA update?
 
Hey, thats a great guide, I was trying to mod the rom that was meant for xoloQ1010i, to my Xolo-Q1010. It helped...let me try this method and come back on the result..cheers
 
Hello everyone!

This quick guide will teach you how to sign ROMs!

WARNING : YOU WILL NEED AT LEAST A BASE KNOWLEDGE OF HOW TO USE COMMAND PROMPT.


The knowledge of signing ROMs can prove useful to anyone! By knowing how to sign ROMs, you can modify your favorite ROM to add or delete APKs, so when you flash the ROM your favorite apps will be present! Or you can delete apps you don't use so they will not be installed when flashing the ROM!


Before starting, you need a couple of things. First you will need Java SE Development Kit and Java SE Runtime Environment . You can download them HERE.

After you have downloaded and installed both, you will need a very useful tool made by someone at XDA-Developers (if you know who it is please let me know).

Download this tool (attached) and unzip everything inside of it into one common folder. I personally unzipped everything into my Android SDK folder.


Signing
Now run the autosign.bat. You will have to go through commands 1(Set PATH variable for SDK) ,2 (Set CLASSPATH variable for signing tool) and 3 (Install registry entries). They are very easy to use and just follow the instructions. If you are asked to confirm and/or replace a file, always select yes!

Now you are finally ready to sign! There are two options to sign the .zip

1)Find the ROM (.zip) and right click and select "Resign Zip". If you use this option a command prompt box should quickly appear and disappear.

OR

2) Using the Autosign.bat, select option 4, and then write the directory and file name of the ROM. For example,

D:\Android\ROMs\YourROMHere.zip

It will hang for a bit at the part where it says "signing", and then it should say something along the lines of "Successfully completed if no errors above"

If this helped you, comment below!

GREAT!!!! Mate!!!! It worked great on my Xolo-Q1010...Running like charm
 
Hello everyone!

This quick guide will teach you how to sign ROMs!

WARNING : YOU WILL NEED AT LEAST A BASE KNOWLEDGE OF HOW TO USE COMMAND PROMPT.


The knowledge of signing ROMs can prove useful to anyone! By knowing how to sign ROMs, you can modify your favorite ROM to add or delete APKs, so when you flash the ROM your favorite apps will be present! Or you can delete apps you don't use so they will not be installed when flashing the ROM!


Before starting, you need a couple of things. First you will need Java SE Development Kit and Java SE Runtime Environment . You can download them HERE.

After you have downloaded and installed both, you will need a very useful tool made by someone at XDA-Developers (if you know who it is please let me know).

Download this tool (attached) and unzip everything inside of it into one common folder. I personally unzipped everything into my Android SDK folder.


Signing
Now run the autosign.bat. You will have to go through commands 1(Set PATH variable for SDK) ,2 (Set CLASSPATH variable for signing tool) and 3 (Install registry entries). They are very easy to use and just follow the instructions. If you are asked to confirm and/or replace a file, always select yes!

Now you are finally ready to sign! There are two options to sign the .zip

1)Find the ROM (.zip) and right click and select "Resign Zip". If you use this option a command prompt box should quickly appear and disappear.

OR

2) Using the Autosign.bat, select option 4, and then write the directory and file name of the ROM. For example,

D:\Android\ROMs\YourROMHere.zip

It will hang for a bit at the part where it says "signing", and then it should say something along the lines of "Successfully completed if no errors above"

If this helped you, comment below!


I got this: Error: Could not find or load main class testsign
I kidda succ at java but can someone help me please ;-;

Here is my *everything*!

************************

Behold the power of

\\ // //=\\ // \\
\\// // \\ // \\
//\\ // // //=====\\
// \\ //====// // \\

Anything is possible.
Stericson

************************

**************
Your choices:
**************

(1) Set PATH variable for SDK
(2) set CLASSPATH variable for signingtool
(3) Install registry entries
(4) Sign files manually
(5) Pull Files from phone
(6) Push files from phone
(7) Exit

Type choice number: 4

**************************
System setup, please wait...
**************************

Please type the full path of the file.
Path?: Gapps_9.0.zip

Gapps_9.0.zip will be resigned!

Do you want to proceed? yes/no?

Type input: yes

**************
Signing File!
**************

Error: Could not find or load main class testsign

File signed successfully if no Errors above.


**************
Your choices:
**************

(1) Set PATH variable for SDK
(2) set CLASSPATH variable for signingtool
(3) Install registry entries
(4) Sign files manually
(5) Pull Files from phone
(6) Push files from phone
(7) Exit

Type choice number:
 
Back
Top Bottom