Hi, I did try to install ubuntu touch on my nexus 6P, with the installer.
I have all the prerequisites : the latest 7.1.2 flashed and USB debug activated
Rebooted with adb reboot bootloader.
then i flash the TWRP recovery.
Wiped and format all.
If we could have more precision on which partition to wipe or not and which to format, it would be great
Then I launched the installer.
Everything went well so far.
On the reboot of the phone I could see the robot blinking but I could not see the progress bar.
Finaly it reboots and I get stuck on the goolge Logo with the padlock unlocked 
!!!
What can I do ?
I did try the procedure several time by reflashing the 7.1.2 stock rom.
I can tell that if you wipe the cache with twrp you have to repair it otherwise you get the same thing than "potet"
@potet said in Call for testing: Google/Huawei Nexus 6P (angler) owners:
I'm writing this from Ubuntu Touch on the Nexus 6p, so safe to say I got it working. Impressed so far. Thank you!
I did encounter some problems, and made it work on the third try. Unfortunately, these these issues were born out of my stupidity, to the point where I'm kind of surprised it's working right now. This probably makes bug testing the installer less fruitful - sorry about that.
In case you'd still be interested in my experience with thr installer, here it goes:
I decided to be lazy and not install the 8 core image first, to see what would happen. What happened was that the (desktop) installer finished without error, but with a warning before "all done":
warn: undefined {"service":"user-service"}
This resulted in the system booting straight into the ubports recovery, with no blinking mascot or anything.
I then decided to try to flash the 8 core version. This is where I was real stupid/tired, and I flashed it as recovery instead of boot.
Weird thing is, next attempt to install did work out better: No warning, and the blinking mascot showed up after the reboot. However, instead of booting thr system got stuck at an infinite splash screen (the Google one).
As true stupidity is doing the same thing several times expecting different results, this is what I did. I just ran the same exact commands as last time, flashing the boot image into recovery. Only difference is that I chose the 'edge' release channel, but I doubt that made any difference.
In conclusion, the weird part is really that it did work, rather than the bugs along the way. The only error I managed to produce was if I tried wiping ubports data from the ubports recovery screen (after both failed installs):
Wiping ubuntu data...
E:unknown volume for path [/cache]
Formatting /cache...
E:unknown volume for path [/cache]
E:unknown volume "/cache"
Data wipe complete
The only constructive thing I can say regarding the installer is really that expectations for what is supposed to happen could have been clearer: That you're supposed (I assume) to see the boot screen flashing on and going into black a few times while it installs the system. I didn't know if it was supposed to stay in recovery or linger on the splash screen, so I just left it for a while in both positions for good measure. 
But now it works beautifully, despite my worst attempts!
