devices: Add initial config for Volla Phone X23 (vidofnir)

[JamiKettunen]

Needs testing, should work though :)

[JamiKettunen]

Confirmed working including with bootstrap option selected on my unit which already had UT flashed; what remains to be tested is switching from VollaOS to Ubuntu Touch (and perhaps making sure switching to VollaOS also works)

[J0J0]

I just tried/used this config, coming from VollaOS. Finally, UT is running now, but i hit some bumps on the way:

I first tried with USE_SYSTEM_TOOLS=1 (fastboot version 34.0.1-android-tools) and wipe and bootstrap checked. This failed with:

error: Error: fastboot:format: Error: formatting failed: Error: {"error":{"code":1,"cmd":"fastboot format userdata"},"stderr":"/usr/bin/make_f2fs failed with status 1\nfastboot: error: Cannot generate image for userdata"}

So i tried with the bundled fastboot (fastboot version 33.0.3-8952118) and it did not complain. However, there was an error on the fastboot logscreen on the device, saying that it could not format userdata and that an install script failed. (I'm sorry that i didn't copy it more carefully ...) After a manual reboot, the installer continued and finished with info: All done! .... UT was not bootable at this point.

From there

• i went to the UBports recovery and applied its wipe/factory reset; (upon which the device still wouldn't boot – which was not surprising to me, given that some install scripts didn't run properly).
• i re-ran ubports-installer without wipe and bootstrap. Then UT could start.

[JamiKettunen]

@J0J0 That's... new I guess, never even heard of USE_SYSTEM_TOOLS env var before, which host OS was this on (and with which version of UBports installer)? I only tested previously on my Linux system with UBports installer v0.10.0

[NotKit]

Seems the mentioned issue is with system version of fastboot tool (fastboot format userdata command failing) and unrelated to the config itself, so let's merge it.

[J0J0]

Sorry for the long delay, i was on vacation (well, sort of).

@NotKit

unrelated to the config itself

Well, actually, i don't think so. Maybe, i didn't express myself carefully enough, but starting with "So i tried with the bundled fastboot" i did not use my system fastboot. I understand that maybe my first try left the partitioning/formatting in some intermediate state, but i don't understand why this would compromise the second run. Except, you are saying that the UBports installer is only expected to work in the scenarios "functional VOS -> UT", "functional UT -> VOS" (and similarily for other supported OSes). Is this true? (If "yes", this would be surprising to me. After all, i could use my private OS and then decide to flash UT with UBports installer ...)

\ @JamiKettunen I use ArchLinux.

never even heard of USE_SYSTEM_TOOLS env var before

I never used UBports installer before, so i just tried what the AUR package ubports-installer-git sets up (here the env var is set).

After the failed attempt, i resorted to ubports-installer-bin (also AUR), which just unpacks the v0.10.0-.deb binary distribution.

[JamiKettunen]

@J0J0 Hey again, the issue you hit with USE_SYSTEM_TOOLS=1 is likely https://github.com/nmeum/android-tools/issues/109, but the problem here appears that the installer tries to format userdata as f2fs (default on this device) while it should be ext4 for Ubuntu Touch; I'm about to push a fix for that soon :)

[J0J0]

Ah. So then i assume that my factory reset via the UBports recovery was responsible for correctly formatting the userdata partition (as ext4)?!