AOSP Signing Builds - Does “Make Otapackage” Produce A Signed ZIP(Release Keys)?

[Nate Robbins]

I followed these instructions https://source.android.com/devices/tech/ota/sign_builds#release-keyswhere I create signed images, and then a signed OTA package.

However, when I adb sideload signed-ota_update.zip, this is what TWRP tells me:

Installing zip file '/sideload/package.zip'
Target: Android_aosp_bullhead/bullhead:7.1.2/N2G47O/nate:05051512/userdebug/release-keys
mount: failed to mount /dev/block/platform/soc.0/f9824900.sdhci/by-name/system at /system: Device or resource busy
symlink: some symlinks found
Updater process ended with ERROR: 7

This is when I wipe everything execpt internal storage and I flash the ZIP. When I flash this ZIP once, and then I flash it overtop again (without wiping) it simply hangs.

Can someone help me with this? Thanks :)

[Mohammad Saleh Dehghanpour]

Did you find the answer? If I run make otapackage, then the produces images like boot.img, ... are signed ? (even with test keys which are placed at build/target/product/security .. )

Thanks