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
    12 Posts 3 Posters 246 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 Offline
        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 Offline
              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 Offline
                  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)?

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

                    @arjune Yes, and make sure that /data is formatted to ext4 (with fastboot format:ext4 userdata) and mounted when you pushed it.

                    Be aware that the device will probably fail to boot on first try.

                    May the source be with you

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

                      @ikoz bootloop

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

                        am I supposed to put the ONE FILE (ubuntu.img) in the data folder or do I flash the image?

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

                          My deviceinfo file: <QUOTES>" deviceinfo_name="Motorola Moto e 2020"
                          deviceinfo_manufacturer="Motorola"
                          deviceinfo_codename="motorola-ginna"
                          deviceinfo_arch="aarch64"
                          deviceinfo_kernel_source="https://github.com/arjunet/android_kernel_motorola_sdm632.git"
                          deviceinfo_kernel_defconfig="ginna_defconfig hallium.config"
                          deviceinfo_kernel_source_branch="lineage-17.1"
                          deviceinfo_kernel_cmdline="console=ttyMSM0,115200,n8 androidboot.console=ttyMSM0 androidboot.hardware=qcom user_debug=30 msm_rtb.filter=0x237 e$deviceinfo_kernel_apply_overlay="true"
                          deviceinfo_flash_pagesize="2048"
                          deviceinfo_flash_offset_base="0x80000000"
                          deviceinfo_flash_offset_kernel="0x00008000"
                          deviceinfo_flash_offset_ramdisk="0x01000000"
                          deviceinfo_flash_offset_second="0x00f00000"
                          deviceinfo_flash_offset_tags="0x00000100"
                          deviceinfo_bootimg_header_version="2"
                          deviceinfo_bootimg_qcdt="false"
                          deviceinfo_bootimg_os_version="10"
                          deviceinfo_bootimg_os_patch_level="2021-02"
                          deviceinfo_use_overlaystore="true"
                          deviceinfo_halium_version="10"
                          deviceinfo_prebuilt_dtbo="dtbo.img"
                          deviceinfo_bootimg_board="ginna"
                          deviceinfo_bootimg_partition_size="67108864"
                          deviceinfo_use_overlaystore="true"
                          deviceinfo_system_partition_size="3000M"
                          deviceinfo_flash_method="fastboot"
                          deviceinfo_generate_bootimg="true"<QUOTES>"

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

                            My output when unpacking boot image: <QUOTES>" arjune@Laptop:~/fairphone_fp3/temp$ python3 unpack_bootimg.py --boot_img boot.img --out out
                            boot magic: ANDROID!
                            kernel_size: 9975472
                            kernel load address: 0x80008000
                            ramdisk size: 753714
                            ramdisk load address: 0x81000000
                            second bootloader size: 0
                            second bootloader load address: 0x80f00000
                            kernel tags load address: 0x80000100
                            page size: 2048
                            os version: 10.0.0
                            os patch level: 2021-02
                            boot image header version: 2
                            product name:
                            command line args: console=ttyMSM0,115200,n8 androidboot.console=ttyMSM0 androidboot.hardware=qcom user_debug=30 msm_rtb.filter=0x237 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 earlycon=msm_hsl_uart,0x78af000 androidboot.usbconfigfs=true vmalloc=300M loop.max_part=7 printk.devkmsg=on androidboot.hab.csv=12 androidboot.hab.product=ginna androidboot.hab.cid=50 androidboot.boot_devices=soc/7824900.sdhci buildvariant=user
                            additional command line args:
                            recovery dtbo size: 0
                            recovery dtbo offset: 0x0000000000000000
                            boot header size: 1660
                            dtb size: 305084
                            dtb address: 0x0000000081f00000<QUOTES>"

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

                              Was /data mounted correctly when you pushed the rootfs? Did you format userdata? Also, you seem to have overlaystore enabled but overlayfs in kernel is not enabled (unless I missed something).

                              Anyway, it is better for you to ask in t.me/ubports_porting, there are more knowledgeable than me people there that can help you, and real-time communication is preferred because porting can take a long time to succeed.

                              May the source be with you

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