@fredldotme
I was able to update to Ubuntu Touch Version 33 today without problems.

My phone was actually able to startup today after being shut off over night.
I then checked the updates again and Ubuntu touch Version 26 was listed as available again.
I tried to install and got a glowing circle like I did when I initially installed it and then it booted up to show the update is still available.
I leave that update for now while I check the system out.

@fredldotme

Thank you for your work, I managed to install it with a slightly different procedure as I wrote in my last comment.
Today I got a system update and installed it and now the phone is stuck in a reboot loop until I force shutdown it with power and volume up and waiting for three vibrations.

Is that expected that over the air updates do not work yet?
And I had no sim inserted in case that is relevant. I just tested it with wifi so far.
I will try to reflash it again soon.

@bkos I also had sailfish on my device before and the same failed to recovery problem as you.
I managed to install it eventully a few days ago by installing twrp https://eu.dl.twrp.me/suzu/ with version 3.2.3-0 that that was mentioned in an earlier post.
The I got a bit further with it failing with "/cache/recovery/': remote couldn't create file: Is a directory" and then checked with adb shell and saw that the directory /cache/recovery was not there and created it.

then it got further and ended with

2019/10/28 21:30:45 Created ubuntu_command: /home/sonny/.cache/ubuntuimages/ubuntu_commands273504541
2019/10/28 21:30:45 Rebooting into recovery to flash

and then twrp came and i could not see those ubuntu commands.

Then I tried

fastboot flash oem SW_binaries_for_Xperia_AOSP_N_MR1_5.7_r1_v08_loire.img

again and then

ubuntu-device-flash touch --device=suzu --channel=16.04/community/fredldotme/devel --bootstrap

and this time it worked with another recovery screen.

I have no idea, this is my first time flashing ubports, but maybe its that there was something missing which twrp then provided and then flashing the recovery from the AOSP worked then.