UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Build Ubuntu Touch error : Halium initrd Failed to boot

    Scheduled Pinned Locked Moved Solved Porting
    15 Posts 4 Posters 1.1k Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • MrT10001M Offline
      MrT10001 @linhmieu2
      last edited by

      @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.

      Xiaomi Redmi Note 7.... And more...
      I have too many devices...

      1 Reply Last reply Reply Quote 1
      • K Offline
        k.nacke @linhmieu2
        last edited by

        @linhmieu2 Did you run prepare-fake-ota.sh and system-image-from-ota.sh (see install kernel)?

        You would the flash system.img to the system partition. Also, your deviceinfo_kernel_cmdline seems to miss systempart=/dev/disk/by-partlabel/system.

        L 1 Reply Last reply Reply Quote 1
        • L Offline
          linhmieu2 @k.nacke
          last edited by linhmieu2

          @k.nacke sorry i forgot that, i will try build agian

          1 Reply Last reply Reply Quote 0
          • L Offline
            linhmieu2 @linhmieu2
            last edited by

            hello again
            i rebuild my project with kernel android 12 base , also i add this to cmdline : systempart=/dev/disk/by-partlabel/system

            Preparation: 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.051s
            

            and my device get bootloops , why this happens?
            (sorry for bad english)

            F MrT10001M 2 Replies Last reply Reply Quote 0
            • L linhmieu2 marked this topic as a question on
            • F Offline
              faveoled @linhmieu2
              last edited by

              @linhmieu2 are you sure you need lz4 for ramdisk compression and not gz?

              L 1 Reply Last reply Reply Quote 1
              • MrT10001M Offline
                MrT10001 @linhmieu2
                last edited by

                @linhmieu2 Have you flashed vbmeta.img?

                Xiaomi Redmi Note 7.... And more...
                I have too many devices...

                L 1 Reply Last reply Reply Quote 1
                • L Offline
                  linhmieu2 @MrT10001
                  last edited by

                  @MrT10001 i already do that

                  1 Reply Last reply Reply Quote 0
                  • L Offline
                    linhmieu2 @faveoled
                    last edited by

                    @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)

                    MrT10001M 1 Reply Last reply Reply Quote 0
                    • MrT10001M Offline
                      MrT10001 @linhmieu2
                      last edited by

                      @linhmieu2 Before ubuntu.img is sent to userdata have you formatted it (to EXT4, being Samsung it should be EXT4)?

                      Xiaomi Redmi Note 7.... And more...
                      I have too many devices...

                      L 1 Reply Last reply Reply Quote 0
                      • L Offline
                        linhmieu2 @MrT10001
                        last edited by

                        @MrT10001 okay , i formated userdata partion to ext4 and flash again but this problem continues...

                        1 Reply Last reply Reply Quote 0
                        • 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
                        • First post
                          Last post