Build Ubuntu Touch error : Halium initrd Failed to boot
-
@linhmieu2 Could that be the issue, you have built of LineageOS21 (Android 14) and used Halium 14, however as far as I know (which is not a lot with porting) UT generally likes a stock Android ROM.
-
@linhmieu2 Did you run
prepare-fake-ota.shandsystem-image-from-ota.sh(see install kernel)?You would the flash
system.imgto thesystempartition. Also, yourdeviceinfo_kernel_cmdlineseems to misssystempart=/dev/disk/by-partlabel/system. -
@k.nacke sorry i forgot that, i will try build agian
-
hello again
i rebuild my project with kernel android 12 base , also i add this to cmdline : systempart=/dev/disk/by-partlabel/systemPreparation: I created a tarball containing the system and rootfs partitions. structure of my tarball like this : tarball/ ├── boot─ dtb Image.gz ramdisk.img.lz4 (and zipped this with gz) and I renamed rootfs.img to ubuntu.img because i follow this guide https://docs.ubports.com/en/latest/porting/build_and_boot/standalone_kernel_install.html . (mv rootfs.img ubuntu.img) after do that , i run prepare fake ota.sh and system images from ota.sh with this tarball and i have this : [user@cachyos-x8664 images]$ ls system.img ubuntu.img and i flash system + rootfs + boot new : [user@cachyos-x8664 utbuild]$ fastboot flash boot boot.img < waiting for any device > Sending 'boot' (12216 KB) OKAY [ 0.561s] Writing 'boot' OKAY [ 0.152s] [user@cachyos-x8664 utbuild]$ fastboot flash system images/system.img Resizing 'system' OKAY [ 0.004s] Sending sparse 'system' 1/11 (262140 KB) OKAY [ 10.996s] Writing 'system' OKAY [ 3.662s] .... Finished. Total time: 168.645s Flashing the userdata partition: [user@cachyos-x8664 utbuild]$ fastboot flash userdata images/ubuntu.img Sending sparse 'userdata' 1/11 (262140 KB) OKAY [ 15.605s] Writing 'userdata' OKAY [ 3.586s] ... Finished. Total time: 187.735s [user@cachyos-x8664 utbuild]$ fastboot reboot Rebooting OKAY [ 0.001s] Finished. Total time: 0.051sand my device get bootloops , why this happens?
(sorry for bad english) -
L linhmieu2 marked this topic as a question on
-
@linhmieu2 are you sure you need lz4 for ramdisk compression and not gz?
-
@linhmieu2 Have you flashed vbmeta.img?
-
@MrT10001 i already do that
-
@faveoled im sure im not use .gz in ramdisk
$ file halium-boot-ramdisk.img.lz4
halium-boot-ramdisk.img.lz4: LZ4 compressed data (v0.1-v0.9) -
@linhmieu2 Before ubuntu.img is sent to userdata have you formatted it (to EXT4, being Samsung it should be EXT4)?
-
@MrT10001 okay , i formated userdata partion to ext4 and flash again but this problem continues...
-
L linhmieu2 has marked this topic as solved on
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login