[Miscellaneous Android Development] OfficerJimLahey:
More Info...

INSTALL CONSIDERATIONS:

There is an option between recoveries, CWM and TWRP. Both have their purpose, so it comes down to personal preference. For the lesser amount of hassle (see below), I would recommend TWRP. Download and instructions for TWRP are in the resources section of the first post, here is how one can install CWM for the F3Q (expand following spoiler):

Download F3Q-Utilities.apk to your computer (from http://androidforums.com/threads/recovery-unofficial-cwm-6-0-5-0-fx3q.863081/)

Put F3Q-Utilities.apk on to the external SD card of the phone

Run F3Q-Utilities.apk on the phone/install it

Open the app that is created on the phone (app name: F3QUtilities2)

In F3QUtilities2 app, choose "Begin", and then "Install CWM"

"Install CWM" will probably not work... so, you must manually add the .LOK file

Download .LOK file to your computer (from http://xdaforums.com/showpost.php?p=54757168&postcount=188)

On the phone, use File Manager to find "/sdcard/f3qutilities" (alternatively, the full path could be "/storage/sdcard0/F3QUtilities2")

Determine if the .LOK file in that directory is 0 bytes; if the .LOK file is 0 bytes, rename the newly downloaded .LOK file (on your computer) with the same name that the 0 byte .LOK file has

Put the newly downloaded and renamed .LOK file on the phone (I put it on the SD card initially)

Restart the F3QUtilities2 app (choose "Begin", and then "Install CWM"

After choosing "Install CWM", open File Manager and then move the newly downloaded/renamed .LOK file to the "/sdcard/f3qutilities" folder (replace the 0 byte .LOK file)

Switch back to F3QUtilities2 app and again choose "Install CWM"

This should complete the CWM install (however, the "Reboot to Recovery" button in the F3QUtilities2 app will probably not work)

Go to "Play Store" on your phone and search for "OUD HitSquad Manager"; find and download the app

Open the app; go to "Recovery Options"; go to "Reboot to Recovery" - This should restart the phone in CWM recovery

TWRP was more flexible than CWM in terms of access to recovery. CWM will factory reset the device if accessed via the bootloader (and apparently only that - not that it matters once the ROM is installed). CWM will however, not install the ROM out of the box (until recently will fail on a set_metadata_recursive error). I now have a "CWM Edition" of the ROM, and since it works with TWRP as well, every new version is set to be for CWM too. But for more information on what was done, expand the following spoiler...

This guide assumes a Windows PC.

Download update-binary.zip to your computer (file and instructions from http://xdaforums.com/showthread.php?t=2532300)

Unzip update-binary.zip (i.e. extract the file) to some place on your computer

Use 7-Zip to navigate to "/META-INF/com/google/android" within the unzipped ROM

Drag and drop the unzipped/extracted "update-binary" file into the "/META-INF/com/google/android" directory (this should replace the old "update-binary" file in the zipped ROM)

The ROM should be ready to be installed as normal (i.e. upload zipped ROM to the phone's SD card, enter recovery, etc.)

TWRP currently has a broken wipe function, and limitations when it comes to backup. For example, if you use Link2SD, TWRP will back up the linked data, not the link, creating a backup that will end up being too big to restore. A nandroid is still recommended - I would just trust a dd backup more - you can always do both! (Also, if you haven't backed up your EFS to be put in a safe place, now is the time.) Because of these shortcomings, you should issue the following commands via adb shell (while in TWRP) to work around:

This process should be done regardless if you are using CWM or TWRP!

# Back up EFS (Just in case)
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/external_sd/modemst1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/external_sd/modemst2.img

# Back up existing ROM
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/external_sd/system.2014-11-12.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/external_sd/boot.2014-11-12.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/cache of=/external_sd/cache.2014-11-12.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/userdata of=/external_sd/userdata.2014-11-12.img

# Wipe /cache and /data
umount /dev/block/mmcblk0p15
mke2fs -T ext4 /dev/block/mmcblk0p15
umount /dev/block/mmcblk0p14
mke2fs -T ext4 /dev/block/mmcblk0p14

# Restart TWRP
reboot recovery

From there you can install the ROM. If you have problems and need to back out, issue the following commands to restore:

# Restore device
dd if=/external_sd/system.2014-11-12.img of=/dev/block/platform/msm_sdcc.1/by-name/system
dd if=/external_sd/boot.2014-11-12.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd if=/external_sd/cache.2014-11-12.img of=/dev/block/platform/msm_sdcc.1/by-name/cache
dd if=/external_sd/userdata.2014-11-12.img of=/dev/block/platform/msm_sdcc.1/by-name/userdata

# Reboot
reboot

The restart looks glitchy at first, but the device ends up starting normally.