UPDATED (June 2021): 17-distro multi-boot image for Pinephone (incl. 3GiB variant)

[megous]

I re-dd'd and now stretched the partition using steps from https://xnux.eu/log/#toc-resizing-the-pa...-the-image.
A couple notes there (cc @megous)

1. I goofed on the block device (misread it) and fell back to my comfort zone of cfdisks which worked fine, too. I used '[resize]' on the second partition, then '[write]'.
2. the "$ df -h"  final step likely belongs *before* the umount so that you can see the size looks right

That all went well and the Pine boots it so I thought to try the SailFish OS, again.
I can confirm that (after you set locale agree to EULA, etc.) when it says "Start" you can press as guided by the XDA dev (firmly, hold for a quarter second, towards the far corners, top left->right then bottom right->left) and it will skip the tutorial.

That being said, I still ended up in the same loopy place I did last time. It also says "Network Connection failed" despite being authenticated to my wifi. I did say "No Jolla Account" does that deny me from using the system? ?
Video footage of the foolishness and that'll be it for me and SFOS for a while: https://youtu.be/d_iKqvzPfK8
The funniest part was the part I didn't catch where holding the power button gave me a friendly "Goodbye!" before powering off from Jolla

Way to reset the distro is to use btrfs-utils:

btrfs subvolume delete /mnt/distro
btrfs subvolume snapshot /mnt/distro.orig /mnt/distro

You'd have to have the root volume mounted though, so it may only be possible with SD card reader in PC, or as I did it, with Arch Linux ARM running from eMMC, while the multi-distro being on a SD card.

If it's possible to mount multiple btrfs volumes at once, it should be possible to just do it from one of the distros on the multi-boot image itself (just not the one you're trying to reset), if you install btrfs utils.

---

Also don't hold the power button for anywhere close to 6s or more. That just forces the PMIC to cut power, without a proper shutdown of the OS. May or may not cause some corruption. (Probably depends on SD card and current write activity level)