-
@Invy Nope. Still fails.
user@ubuntu:~/Downloads/lgg6_ubuntu$ fastboot devices LGH87051b7ab76 fastboot user@ubuntu:~/Downloads/lgg6_ubuntu$ fastboot flash boot halium-boot-20200326.img target reported max download size of 536870912 bytes sending 'boot' (16216 KB)... OKAY [ 0.530s] writing 'boot'... OKAY [ 0.158s] finished. total time: 0.689s user@ubuntu:~/Downloads/lgg6_ubuntu$ sudo ./halium-install/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.oWUv6/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.oWUv6/system.img Please run 'e2fsck -fy .halium-install-imgs.oWUv6/system.img' to fix the filesystem after the aborted resize operation. I: Cleaning up error: no devices/emulators found user@ubuntu:~/Downloads/lgg6_ubuntu$ sudo ./halium-install/halium-install -p ut ubuntu-touch-hybris-xenial- system-20200326.img ubuntu-touch-hybris-xenial-arm64-rootfs.tar.gz ubuntu-touch-hybris-xenial-edge-arm64-rootfs.tar.gz ubuntu-touch-hybris-xenial-arm64-rootfs.tar.gz.part ubuntu-touch-hybris-xenial-edge-arm64-rootfs.tar.gz.part user@ubuntu:~/Downloads/lgg6_ubuntu$ sudo ./halium-install/halium-install -p ut ubuntu-touch-hybris-xenial-edge-arm64-rootfs.tar.gz system-20200326.img Debug: Chosen rootfs is ubuntu-touch-hybris-xenial-edge-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.l0c8k/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.l0c8k/system.img Please run 'e2fsck -fy .halium-install-imgs.l0c8k/system.img' to fix the filesystem after the aborted resize operation. I: Cleaning up error: no devices/emulators found -
@basti this is more likely due to adb, rather than to
halium-install, the last command must be executed when the device is inrecovery mode. Not in bootloader one -
@Guf Ok. Not sure how to get there now. Cant connect to ADB anymore. Phone stucks in boot screen.
- Is there some instructions where this calling for
recovery modewas mentioned?
- How can I recoever from my mode now?
- Is there some general instructions I can look at?
-
@basti Is the smartphone stuck in this screen?
Try this one:
- Turn off the smartphone
- Hold the power button on the back and Volume down
- When the LG logo appears, keep holding Volume down, release the power button and press the power button again briefly.
After a few seconds a recovery menu should appear
I strongly recommend to install TWRP for the LG G6, you should be able to install everything from here. -
@Invy Thanks for the answer. We make steps forward.
I managed to install TWRP on the recovery partition. But the UT install still fails:
user@ubuntu:~/lgg6_ubuntu$ adb devices List of devices attached LGH87051b7ab76 recovery user@ubuntu:~/lgg6_ubuntu$ adb reboot recovery user@ubuntu:~/lgg6_ubuntu$ ./halium-install/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.xmRsa/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.xmRsa/system.img Please run 'e2fsck -fy .halium-install-imgs.xmRsa/system.img' to fix the filesystem after the aborted resize operation. I: Cleaning upSame result with both files:
ubuntu-touch-hybris-xenial-arm64-rootfs.tar.gz
ubuntu-touch-hybris-xenial-edge-arm64-rootfs.tar.gzWhat can I do next?
-
@basti Did you install your device with halium-install? I just updated the instruction at the very beginning.
Halium-install usually installs rootfs.img and system.img indatapart, so you need to flash the image, as described above.
Please, inform me if you still have problem booting.
Take it easy, you can recover your old system (previous UT or Android, or LineageOS), whenever you want. -
Sorry, @Guf
I assume you have other stuff to work on, but I really do not see where there is any "instruction at the very beginning".Yes, I installed my device with halium-install like adived on another website.
./halium-install -p ut ../ubuntu-touch-hybris-xenial-arm64-rootfs.tar.gz ../halium-boot_h870_datapart.imgI ran it two times, as in between I accidentally disconnected my hub.
First time I got this:
user@ubuntu~/Downloads/lgg6_ubuntu/halium-install (master)$ ./halium-install -p ut ../ubuntu-touch-hybris-xenial-arm64-rootfs.tar.gz ../halium-boot_h870_datapart.img Debug: Chosen rootfs is ../ubuntu-touch-hybris-xenial-arm64-rootfs.tar.gz Debug: Chosen android image is ../halium-boot_h870_datapart.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) e2fsck: Attempt to read block from filesystem resulted in short read while trying to open .halium-install-imgs.buA1T/system.img resize2fs 1.45.5 (07-Jan-2020) resize2fs: Attempt to read block from filesystem resulted in short read while trying to open .halium-install-imgs.buA1T/system.img Couldn't find valid filesystem superblock. I: Cleaning up * daemon not running; starting now at tcp:5037 * daemon started successfullySecond time this:
user@ubuntu:~/Downloads/lgg6_ubuntu/halium-install (master)$ ./halium-install -p ut ../ubuntu-touch-hybris-xenial-arm64-rootfs.tar.gz ../halium-boot_h870_datapart.img Debug: Chosen rootfs is ../ubuntu-touch-hybris-xenial-arm64-rootfs.tar.gz Debug: Chosen android image is ../halium-boot_h870_datapart.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) e2fsck: Attempt to read block from filesystem resulted in short read while trying to open .halium-install-imgs.KXEbs/system.img resize2fs 1.45.5 (07-Jan-2020) resize2fs: Attempt to read block from filesystem resulted in short read while trying to open .halium-install-imgs.KXEbs/system.img Couldn't find valid filesystem superblock. I: Cleaning updmesg gives me:
[108202.343962] usb 4-1.1: USB disconnect, device number 7 [108235.365911] usb 1-5.4: USB disconnect, device number 54 [108247.636692] usb 1-5.4: new high-speed USB device number 55 using xhci_hcd [108247.749933] usb 1-5.4: New USB device found, idVendor=18d1, idProduct=4ee2, bcdDevice= 3.18 [108247.749941] usb 1-5.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [108247.749946] usb 1-5.4: Product: h870 [108247.749950] usb 1-5.4: Manufacturer: lge [108247.749953] usb 1-5.4: SerialNumber: LGH87051b7ab76 [108252.972953] usb 1-5.4: reset high-speed USB device number 55 using xhci_hcd [108253.181260] usb 1-5.4: reset high-speed USB device number 55 using xhci_hcd [108271.461219] usb 1-5.4: USB disconnect, device number 55 [108283.732721] usb 1-5.4: new high-speed USB device number 56 using xhci_hcd [108284.288833] usb 1-5.4: device descriptor read/64, error -71 [108284.509663] usb 1-5.4: New USB device found, idVendor=18d1, idProduct=d001, bcdDevice= 3.18 [108284.509668] usb 1-5.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [108284.509671] usb 1-5.4: Product: Failed to boot [108284.509674] usb 1-5.4: Manufacturer: Halium initrd [108284.509676] usb 1-5.4: SerialNumber: halium-initrd [108284.513451] rndis_host 1-5.4:1.0 usb0: register 'rndis_host' at usb-0000:00:14.0-5.4, RNDIS device, ae:1e:f9:33:ba:70 [108350.166237] perf: interrupt took too long (4932 > 4931), lowering kernel.perf_event_max_sample_rate to 40500 [108433.253688] usb 1-5.4: USB disconnect, device number 56 [108433.253868] rndis_host 1-5.4:1.0 usb0: unregister 'rndis_host' usb-0000:00:14.0-5.4, RNDIS device [108454.743919] usb 1-5.4: new high-speed USB device number 57 using xhci_hcd [108454.857641] usb 1-5.4: New USB device found, idVendor=18d1, idProduct=4ee2, bcdDevice= 3.18 [108454.857644] usb 1-5.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [108454.857645] usb 1-5.4: Product: h870 [108454.857647] usb 1-5.4: Manufacturer: lge [108454.857648] usb 1-5.4: SerialNumber: LGH87051b7ab76 [108460.008128] usb 1-5.4: reset high-speed USB device number 57 using xhci_hcd [108460.216318] usb 1-5.4: reset high-speed USB device number 57 using xhci_hcd [108482.246405] EXT4-fs (loop1): mounted filesystem with ordered data mode. Opts: (null)I still only see the TWRP screen on my phone. No UT is booting and there are nowhere instructions on what to do next!
-
@basti you used the wrong file with the halium-install: the command needs to be feeded by the rootfs.tar.gz (you did it correct) then by
system.img. At this point, it won't fail.
So far, you need to reboot in bootloader, and from pc execute fastboot flash boot halium-boot_h870_datapart.img (that you will download from the very first post).
Your halium-boot won't let you boot correctly because it is thought to bootsttap fromsystempartto beOTA compliant, while halium-boot install rootfs and system indatapart
Anyway, the 3rd line of the very first post, suggest to join a telegram chanbel that i created today -
I re-downloaded everything, but no luck.
When you say
system.imgyou meansystem-202003262.imgfrom 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:
https://forums.ubports.com/topic/3729/ubuntu-touch-on-lg-g6-h870-model-call-for-testers/60?_=1606258586640user@ubuntu:~/lgg6_ubuntu$ ./halium-install/halium-install -p ut ubuntu-touch-hybris-xenial-arm64-rootfs.tar.gz system-20200326.imgAs 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.171sRebooting to bootloader and running
fastboot flash boot halium-boot_h870_datapart.imgafter 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
systempartto beOTA compliant, while halium-boot install rootfs and system indatapart"
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. -
https://forums.ubports.com/category/80/lg-g6 your new discussion space.
