This ensures that the right release key is also embedded in the
recovery that is part of the boot image.
Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
Boot and recovery are already regenerated when running the
sign_target_files_apks script, so GetBootableImage is never called in
the img and ota scripts. It wouldn't work anyway as the function
parameters have changed.
Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
Boot and recovery are already regenerated in sign_target_files_apks,
so the scripts galaxys2_img_from_target_files and
galaxys2_ota_from_target_files have no effect.
This fork of sign_target_files_apks makes sure that the standalone
recovery is rebuilt with the new ramdisk and that boot image from $OUT
is used untouched.
Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
resize2fs.static is placed in install/bin, possible to run without /system mounted.
running it will resize /system to the actual system partition size,
supporting custom pits with block-based OTAs
Change-Id: Id2c82add1f697ae3d7e5a1031f6a6d51a4ee53e0
We were using a deprecated version and with a faulty backuptool.
Use CM releasetools as much as possible
Change-Id: I19fbbcb21b20030f10161fbc798feb02b90a7c7c
The OTA script may be run during a signing process and will not have
OUT variables defined. Use the common methods for getting the boot.img
to match standards.
Change-Id: I4eebf58ec828f18f62176a2862e5fdbb839cb658
