[Android Software/Hacking General [Developers Only]] osm0sis:
It is getting kinda quiet around these parts. Time to shake things up with something new.. ;)

cwm-Flashify.zip/META-INF/com/google/android/update-binary:

#!/sbin/sh
# Flashify Script: Recovery Flashable Zip
# osm0sis @ xda-developers

OUTFD=/proc/self/fd/$2;
DIR=`dirname "$3"`;
ui_print() {
echo -ne "ui_print $1\n" > $OUTFD;
echo -ne "ui_print\n" > $OUTFD;
}
show_progress() { echo "progress $1 $2" > $OUTFD; }
abort() {
ui_print " ";
ui_print "Your system has not been changed.";
ui_print " ";
ui_print "Script will now exit...";
ui_print " ";
exit 1;
}

ui_print " ";
ui_print "Flashify Script";
ui_print "by osm0sis @ xda-developers";
ui_print " ";
show_progress 1.34 2;

# emmc only; mtd requires dedicated tools to wipe and flash
if [ "$(grep -wE 'boot|LNX|recovery|SOS|radio|modem|RDO' /proc/mtd 2> /dev/null)" ]; then
ui_print "MTD-based boot/recovery/radio partition detected.";
ui_print "Flashing MTD partitions is not supported.";
abort;
fi;

# go local and take first .img file found
# use busybox ls; toolbox/sh won't automatically sort alphabetically
# recovery needs wildcard prefix to support TWRP "openrecovery"
# baseband name can be "radio" or "modem" to cover most devices
cd "$DIR";
image=`busybox ls boot*.img *recovery*.img radio*.img modem*.img 2> /dev/null | head -n 1`;

# determine image type from the filename and define partition names
# also support Tegra board "LNX/SOS/RDO" naming since it's in AOSP
case $image in
boot*)
imgtype="boot LNX";;
*recovery*)
imgtype="recovery SOS";;
radio*|modem*)
imgtype="radio modem RDO";;
*)
ui_print "No image file found to flash.";
abort;;
esac;

ui_print "Supplied image: $image";
ui_print " ";

# make sure boot/recovery is standard Android bootable image format
# there is no standard format for basebands
case $imgtype in
boot*|recovery*)
magic=`dd ibs=1 count=8 skip=0 obs=1 if="$image" 2> /dev/null`;
if [ "$magic" != "ANDROID!" ]; then
ui_print "Android boot magic not found.";
abort;
fi;;
esac;

# find the matching partition in platform architecture
# most devices have a depth of 1 before by-name, some have 2
for i in $imgtype; do
if [ -e /dev/block/platform/*/by-name/$i ]; then
block=/dev/block/platform/*/by-name/$i;
elif [ -e /dev/block/platform/*/*/by-name/$i ]; then
block=/dev/block/platform/*/*/by-name/$i;
fi;
done;
if [ ! "$block" ]; then
ui_print "No partitions found matching \"$imgtype\"";
abort;
fi;

# force expansion of the path so we can use it
block=`echo -n $block`;

# abort radio flashing on devices with split modem partitions
case $imgtype in
radio*)
if [ ! -z "$(ls `dirname $block`/mdm* 2> /dev/null)" ]; then
ui_print "Multi-partition radio flashing unsupported.";
abort;
fi;;
esac;

# one last sanity check before flashing
if [ ! -e $block ]; then
ui_print "Partition name mismatch: $block";
abort;
fi;

ui_print "Flashing to: $block";
ui_print " ";

dd if="$image" of=$block;

ui_print "Done!";
exit 0;

Flashify Script Zip:

I wanted to ease peoples' reliance on "needing" flashable zips for kernel/recovery/baseband images a bit more, along the same lines as cgollner's powerful and visually stunning Flashify App. A few kernel tweaking apps also now allow direct flashing of .img files, which is helping, but otherwise you'd need to repack your own zip, use the command-line or fastboot flash it, and a lot of people don't seem to be up to those tasks.

Flashing this zip will take the

first found

matching image in the same directory as the zip and flash it to the correct partition on many devices (ie. on emmc devices where the partitions are named "boot", "recovery" and "radio"/"modem" per the norm; only exception being Tegra's LNX/SOS/RDO for grouper/tilapia since it's in AOSP). Matching images should be named boot*.img (e.g. boot.img, boot-r16-deb.img, boot-6.15.14-sr-unified.img, etc.) for kernels, *recovery*.img (e.g. recovery.img, recovery-clockwork-swipe-6.0.4.9-maguro.img, openrecovery-twrp-2.7.1.1-flo.img, etc.) for recoveries, and radio*.img or modem*.img (e.g. radio.img, radio-maguro-i9250tdvmk1.img, modem.img, modem-mako-m9615a-cefwmazm-2.0.1701.02.img) for basebands. If it can't find an image or a matching partition to go with it, it bails and does nothing. :good:

It also only accepts boot/recovery images that follow the mkbootimg Android bootable image standard (ie. has "ANDROID!" magic at the beginning), just to be safe. radio/modem baseband images have no such standard, so be careful to only flash verified baseband images for your device.

Attached in the OP! (Blurb still forthcoming since I'm tired and need coffee.) :cool: :cowboy:

Edit: There, blurbed it up. :p

Edit 2: Added some logic to avoid breaking Nexus 6's multi-partition radio by aborting when detected.