i can produce a working ubtouch install by using the images you have linked from your nextcloud.

i was able to build halium-9.0 from source by emulating some steps in https://gitlab.com/ubports/community-ports/jenkins-ci/halium-build-tools/-/tree/main/ -- if i push the halium-boot.img and vendor.img produced by that build, everything continues working.

if i push the latest android-rootfs.img from Jenkins-CI to /data/, the system also continues working.

if i push the latest vendor.img from Jenkins-CI, with or without the latest android-rootfs.img, the WiFi and Bluetooth break but the system otherwise continues working, including mobile data.

if i flash the latest Jenkins-CI boot.img to that installation, the device will then only boot into the recovery mode. i believe there is a compatibility issue with the "combined" boot image produced here and it might be worth changing the 4th parameter in the Jenkinsfile here to false: https://gitlab.com/ubports/community-ports/jenkins-ci/marlin-sailfish/-/blob/main/Jenkinsfile#L2

i'm still not totally clear on how you are producing the system.imgthat you have in your nextcloud.

@flohack thank you. the system.img doesn't seem to be present, but there is a system/ directory. is it as simple as creating an ext4 filesystem from that tree of files?

also the boot.img provided there doesn't seem to honor break= or bootmode= kernel command line args. does it need to be built with special flags to enable that?

@flohack actually, would you be willing to teach us how to fish? is there a way we can build or extract these vendor.img and system.img ourselves?

is the halium-boot.img the same as from https://ci.ubports.com/job/UBportsCommunityPortsJenkinsCI/job/ubports%252Fcommunity-ports%252Fjenkins-ci%252Fmarlin-sailfish/job/main/ ? is the vendor.img in halium_sailfish.tar.xz the correct one?

@flohack thank you! i was also able to produce a working droidian install on sailfish using your work as a base. really grateful for your efforts here.

@flohack looking at the nextcloud instance, the newest images are from 4 months back. are those the latest ones?

@flohack -- i'm referring to the documentation at https://docs.halium.org/en/latest/porting/debug-build/early-init.html#forcing-debug-mode:

If the device simply reboots when trying to boot and does not bring up telnet, you may build and use the hybris-recovery.img file to attempt to force a shell to come up.

this is the circumstance I'm bumping up against. maybe there is a new way to troubleshoot this?

@flohack -- thank you. i was able to build successfully. however, i'm noticing that the documented hybris-recovery target does not exist, which is making it a bit tricky to troubleshoot init issues. was this renamed or is there another way to force an existing boot image into recovery mode?

@flohack -- thank you. are the device manifests you merged in https://github.com/Halium/halium-devices/pull/282 sufficient? i ran into some build errors and wondered if there were some additional steps/patches i was missing.

@flohack whatever would let me instrument very early stage boot. do you have the instructions you are using to build halium-boot for sailfish handy? anything beyond the standard halium-9.0 build process?

@flohack does the halium-boot.img have debugging enabled? i'm trying to use the same boot image to test out droidian and need to troubleshoot some early stage init issues. not seeing any iSerial results with lsusb.