@sagar.pradhan Please post a link or two to those.

But seemingly they are all fixed: (-edit: opps. reading further I see there are many not fixed. Sorry about that. )

https://bugs.launchpad.net/ubports-android/+bugs

@tom
" I flashed ubuntu over the baseband of cm12.1. I thought that was what the advice was! "
Yes, I think that was the advice.

My cheap advice about mixing systems -> " dual booting is just not worth the trouble."

I changed the status of my attempt to stopped.
I don't have any interest in in-depth learning about node.js or javascript so best for me to quietly bow out of this bounty.
Someone with the skill set already might find is a trivial bounty to fix.

The purpose of this topic is to document the Recovery image details of the FP2 as I initially received it.

<icon>
horizontal android, chest door open, exposing red triangle with exclamation point.

Android system recovery <3e>
r4275.1_FP2_gms69_1.9.3
 
Volume up/down to move highlight;
enter button to select.

reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
apply update from sdcard

Plugged USB cable results in dmesg:

[65653.044636] usb 3-1: new high-speed USB device number 25 using xhci_hcd
[65653.173731] usb 3-1: New USB device found, idVendor=2ae5, idProduct=9039
[65653.173738] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[65653.173741] usb 3-1: Product: Android
[65653.173744] usb 3-1: Manufacturer: Android
[65653.173747] usb 3-1: SerialNumber: f8c9f680
[65663.005036] usb 3-1: USB disconnect, device number 25
[68831.732542] perf interrupt took too long (2509 > 2500), lowering kernel.perf_event_max_sample_rate to 50000

Scrolling down and selecting option "apply update from ADB"
FP2 responds with same icon.
Text bottom of screen:

Now send package you want to apply
to the device with "adb sideload <file name>"

resulting dmesg:

[69031.019059] usb 3-1: new high-speed USB device number 26 using xhci_hcd
[69031.148680] usb 3-1: New USB device found, idVendor=18d1, idProduct=d001
[69031.148687] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[69031.148690] usb 3-1: Product: FP2
[69031.148693] usb 3-1: Manufacturer: Fairphone
[69031.148696] usb 3-1: SerialNumber: f8c9f680

Oppsie : ) Waited too long.

Now send package you want to apply
to the device with "adb sideload <file name>"...

Timed out waiting for package.

Installation aborted.

Reselecting option "apply update from ADB"

adb devices reports.

List of devices attached 
f8c9f680        sideload

This is just a heads up on getting adb access while running the stock android version.

Do the usual ->settings->about phone
Then tap Build Number till it tells you are a developer.
Then go back:
Now select [] Developer options
Turn on debugging.

Now connect USB cable and "USB computer connections" should then be available to make selections.

Actually if you want adb shell to work you must unselect all options.

Then a pop-up asking if you want to authorize such and such computer access, Say yes.

And adb shell should work.

Hm I would suggest that what you have asked for is available on GitHub but perhaps start with wiki.ubports.com.

Reading rootstock script and modifying it to your needs is good way to learn this process. I have also been doing this.

Are you able to flash and use the boot and recovery partitions?

Great you are trying Ubports out.
So it sounds like AppArmor permission problems. Hmm, but other apps are working?

What did you flash your N5 with?

I'll attempt to tell you how to find the ones built by the Ubports Jenkens server.
If you execute this

ubuntu-device-flash -v --server=http://system-image.ubports.com touch --channel=ubuntu-touch/devel_rc-proposed –device=hammerhead --download-only

Then look in

~/.cache/ubuntuimages/pool  

You will find among other files, this one

59147132 Dec 21 18:57 device-1343cffe4d2fe5b529e198a4182e1b20de176d284b1d340f5b44f3ac25896e79.tar.xz

If you then extract you will find two directories labeled partition with boot.img and recovery.img within and another directory labeled system.

OK. Stable channel is rather old at this point. I've had the best results with using current devel_rc-proposed but with rootfs of 7/28/2016. It's not straight forward how to do that though. I think very soon we will have better options available.