I re-downloaded everything, but no luck.
When you say
system.img you mean
system-202003262.img from this link in the initial post system.img???
In that case it would be the command I used in my reply from the 17. Nov 2020 here:
user@ubuntu:~/lgg6_ubuntu$ ./halium-install/halium-install -p ut ubuntu-touch-hybris-xenial-arm64-rootfs.tar.gz system-20200326.img
As I am not sure if you meant to rename that system-img file, I tried also this, but no success.
user@ubuntu:~/lgg6_ubuntu/halium-install (master)$ ./halium-install -p ut ../ubuntu-touch-hybris-xenial-arm64-rootfs.tar.gz ../system-20200326.img Debug: Chosen rootfs is ../ubuntu-touch-hybris-xenial-arm64-rootfs.tar.gz Debug: Chosen android image is ../system-20200326.img Debug: Chosen release is ut Debug: Compress images before pushing: false I: Writing rootfs into mountable image I: Writing android image into mountable image I: Running post installation tasks enabling SSH ... [done] Please enter a new password for the user 'phablet': Enter new UNIX password: Retype new UNIX password: passwd: password updated successfully I: Shrinking images e2fsck 1.45.5 (07-Jan-2020) resize2fs 1.45.5 (07-Jan-2020) Resizing the filesystem on .halium-install-imgs.e951D/system.img to 129095 (4k) blocks. Begin pass 2 (max = 1758) Relocating blocks XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Begin pass 3 (max = 4) Scanning inode table resize2fs: No space left on device while trying to resize .halium-install-imgs.e951D/system.img Please run 'e2fsck -fy .halium-install-imgs.e951D/system.img' to fix the filesystem after the aborted resize operation. I: Cleaning up user@ubuntu:~/lgg6_ubuntu/halium-install (master)$ fastboot flash boot ../halium-boot_h870_datapart.img target reported max download size of 536870912 bytes sending 'boot' (16368 KB)... OKAY [ 0.581s] writing 'boot'... OKAY [ 0.149s] finished. total time: 0.730s user@ubuntu:~/Downloads/lgg6_ubuntu/halium-install (master)$ fastboot reboot rebooting... finished. total time: 0.171s
Rebooting to bootloader and running
fastboot flash boot halium-boot_h870_datapart.img after the failing halium didn't change anything afterwards, of course. So this did not work as well.
Any other suggestions?
Not sure what you want to tell me with "Your halium-boot won't let you boot correctly because it is thought to bootsttap from
systempart to be
OTA compliant, while halium-boot install rootfs and system in
I have no clue what "datapart" is. What is that?
What should I understand from that sentence? Halium does not let me boot, ... that is bad, right? What shoudl I do then/instead?
Is there some instruction to it?
Regarding the telegram channel: I I joined it. But ... why?
You want me to post my continuing issues there and here or only there?
So far it does not look like any help there.