Generating the keys
Note: You only need to run this once. If you ever rerun these, you’ll need to
migrate between builds - see Changing keys
From the root of your Android tree, run these commands, altering the subject line to reflect your information:
$ subject='/C=US/ST=California/L=Mountain View/O=Android/OU=Android/CN=Android/emailAddress=android@android.com'
$ mkdir ~/.android-certs
$ for x in releasekey platform shared media; do \
./development/tools/make_key ~/.android-certs/$x "$subject"; \
done
You should keep these keys safe, and store the passphrase in a secure location.
Generating an install package
Tip: If you wish to preserve your data coming from a Lineage build you
didn’t build, see Changing keys.
Generating and signing target files
After following the build instructions for your device, instead of running brunch <codename>,
run the following:
$ breakfast <codename>
$ mka target-files-package dist
Sit back and wait for a while - it may take a while depending on your computer’s specs. After it’s finished, you just need to sign all the APKs:
$ croot
$ ./build/tools/releasetools/sign_target_files_apks -o -d ~/.android-certs \
out/dist/*-target_files-*.zip \
signed-target_files.zip
Generating the install package
Now, to generate the installable zip, run:
$ ./build/tools/releasetools/ota_from_target_files -k ~/.android-certs/releasekey \
signed-target_files.zip \
signed-ota_update.zip
Then, install the zip in recovery as you normally would.
Changing keys
Warning: Builds with these patches are insecure - they reset the keys
on all packages at every boot. Install them for as little time as possible.
You can set up your own migration builds by running:
$ repopick -t cm-data-migration
Then, follow the instructions to generate an install package.
Going back
After installing the migration build, you can switch back to building normal builds:
$ cd vendor/cm
$ git reset --hard github/cm-14.1
$ croot
$ cd frameworks/base
$ git reset --hard github/cm-14.1