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

    Porting Ubuntu Touch to Motorola Moto E 2020 (ginna).

    Scheduled Pinned Locked Moved Porting
    6 Posts 3 Posters 115 Views 2 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.
      • A Online
        arjune
        last edited by

        Hi I'm trying to port Ubuntu Touch to my Motorola Moto E 2020 (ginna). I'm doing the standalone kernel method. But for some reason when I do the halium-install script: <QUOTES>"For Halium 9.0 ports, use this command:

        path/to/halium-install -p ut -s path/to/ubuntu-touch-android9-arm64.tar.gz path/to/[SYSTEM_IMAGE]"<QUOTES> the script starts copying rootfs.img but then it STOPS copying at 24% each time. Anyone know what to do?????

        stanwoodS ikozI 2 Replies Last reply Reply Quote 0
        • stanwoodS Offline
          stanwood @arjune
          last edited by

          @arjune Maybe you can get some help through this Telegram group:

          https://t.me/ubports_porting

          Redmi Note 9S Stable
          If God has a computer, it must be a GNU/Linux

          1 Reply Last reply Reply Quote 0
          • ikozI Offline
            ikoz @arjune
            last edited by ikoz

            @arjune Don't use the halium-install script. Use only the commands at the end of the standalone kernel method.
            Build:

            ./build.sh -b workdir
            ./build/prepare-fake-ota.sh out/device_genia_usrmerge.tar.xz ota
            ./build/system-image-from-ota.sh ota/ubuntu_command images
            

            Install:
            Flash boot.img to boot partition.
            If you have systempart in your cmdline flash system.img to system, otherwise push rootfs.img to data partition as ubuntu.img.


            As stanwood said, the telegram porting group is more active.

            May the source be with you

            A 1 Reply Last reply Reply Quote 0
            • A Online
              arjune @ikoz
              last edited by arjune

              @ikoz so just dont use the halium installer and just flash and then just boot and it'll work????? (oh and TWRP says that boot.img is larger than target device)

              ikozI 1 Reply Last reply Reply Quote 0
              • ikozI Offline
                ikoz @arjune
                last edited by

                @arjune Yes, just flashing the 2 partitions is enough. Also, boot.img can be flashed in either bootloader or fastbootd mode, while system.img only on fastbootd (it is a sparse image).

                TWRP says that boot.img is larger than target device

                It should be flashed with fastboot flash boot boot.img, make sure deviceinfo_bootimg_partition_size is set correctly. TWRP is the recovery, I don't get how it is involved.

                May the source be with you

                A 1 Reply Last reply Reply Quote 0
                • A Online
                  arjune @ikoz
                  last edited by arjune

                  @ikoz ok I did those, now do I just boot and it will boot into ubuntu touch? (I flashed the boot partition as boot.img and renamed rootfs.img to ubuntu.img, and moved the ubuntu.img to the data folder. Is that what I was supposed to do)?

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post