No, I didn’t because apparently you could use that, “except on the Fairphone 2 where this method does not work”.
But this info seems to be over a year old now, perhaps I could give that a shot anyway.
Edit (as root, sudo was the same):
ubuntu-device-flash --server=http://system-image.ubports.com touch \ --device=FP2 --channel=ubports-touch/16.04/stable --bootstrap --wipe 2018/12/01 23:59:16 Expecting the device to be in the bootloader... waiting 2018/12/01 23:59:16 Device is |FP2| 2018/12/01 23:59:16 Flashing version 3 from ubports-touch/16.04/stable channel and server http://system-image.ubports.com to device FP2 68.99 MB / 68.99 MB [=====================================] 100.00 % 12.71 MB/s 378.89 MB / 378.89 MB [===================================] 100.00 % 17.86 MB/s Can't boot recovery image
… same for the devel channel … and
fastboot itself works, so what’s wrong here?
In Fastboot mode, to boot a recovery (or any) image, the image would have to be signed (how to do this is known). Since I don’t know where ubuntu-device-flash downloaded the files to, I can’t have a look.
There are images for boot, recovery and splash at http://cdimage.ubports.com/devices/, file date is June 30, 2018.
The recovery image there is not signed, so it can’t be booted with fastboot as is. Edit: I signed it, and fastboot can boot it … makes no difference, though.
I suspect the stuff that ubuntu-device-flash downloads is from http://system-image.ubports.com/pool/, but it looks too cryptic there for me.