Navigation

    UBports Robot Logo

    UBports Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    (Solved) Stuck on finishing booting Moto E 2015 (surnia)

    Porting
    motorola new device porting
    3
    21
    1530
    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.
    • I
      impreza233 last edited by impreza233

      Hello. I'm trying to port Ubuntu Touch on my Moto E 2015, and I'm having some problems.
      I have compiled my halium-boot and my systemimage without problems. But, when I have flashed my halium-boot and my systemimage to the phone, when it boots, only allows me to connect by telnet. I connect to the ip via telnet and I can execute commands, but ssh access is restricted. Any suggestions?

      advocatux 1 Reply Last reply Reply Quote 1
      • advocatux
        advocatux @impreza233 last edited by

        @impreza233 the other day another user had a similar problem and it seems these instructions https://forums.ubports.com/topic/431/porting-halium-to-nexus-7-deb help him/her

        1 Reply Last reply Reply Quote 1
        • I
          impreza233 last edited by

          Well, I am seeing it for further reference. Thanks!

          1 Reply Last reply Reply Quote 1
          • I
            impreza233 last edited by

            No luck. I will post my images and ask for the community.

            1 Reply Last reply Reply Quote 0
            • I
              impreza233 last edited by

              Well, I believe that I have found the cause of the issue. When I copy the halium-boot, I get this error:
              I: Pushing rootfs and android image to /data via ADB
              adb: error: cannot stat '.halium-install-imgs.potDm/rootfs.img': Value too large for defined data type

              Perhaps this is the cause of the non-existence of rootfs.img

              D 1 Reply Last reply Reply Quote 0
              • D
                doniks @impreza233 last edited by

                @impreza233 halium-install has a -v switch. try that and pastebin the output

                1 Reply Last reply Reply Quote 0
                • I
                  impreza233 last edited by impreza233

                  EDIT: I put here the pastebin (in Spanish): https://paste.ubuntu.com/p/rFg2pvFGwh/

                  D 1 Reply Last reply Reply Quote 0
                  • I
                    impreza233 last edited by

                    Well, I have two images for the community, for testing purposes. halium-boot is for installing, and system.img is for the script. If someone in the community could test it, I would be glad:
                    https://www.dropbox.com/sh/0oqii0tl46k84hj/AACuRRoXu0hnaZO2RjGxR68ja?dl=0

                    1 Reply Last reply Reply Quote 1
                    • D
                      doniks @impreza233 last edited by

                      @impreza233 said in Stuck on finishing booting Moto E 2015 (surnia):

                      EDIT: I put here the pastebin (in Spanish): https://paste.ubuntu.com/p/rFg2pvFGwh/

                      Mhm. Not sure. Can you insert a ls -l in there so we can see the size of the rootfs.img being created. Or maybe convince it to not clean-up at the end so you can do it after the script finished.

                      Also please do a adb shell df /data to check how much space is on the device

                      1 Reply Last reply Reply Quote 0
                      • I
                        impreza233 last edited by impreza233

                        When I run adb shell df /data: https://paste.ubuntu.com/p/GT9Qfg2TDy/
                        EDIT: This is the size of rootfs.img: Formatting '.halium-install-imgs.jC8ap/rootfs.img', fmt=raw size=3221225472

                        D 1 Reply Last reply Reply Quote 0
                        • D
                          doniks @impreza233 last edited by

                          @impreza233 said in Stuck on finishing booting Moto E 2015 (surnia):

                          When I run adb shell df /data: https://paste.ubuntu.com/p/GT9Qfg2TDy/
                          EDIT: This is the size of rootfs.img: Formatting '.halium-install-imgs.jC8ap/rootfs.img', fmt=raw size=3221225472

                          Uhm, right, those numbers are too big, my brain gives up 🙂 But do you see where I'm going? I wanna check if the rootfs.img fits onto that partition. Maybe ls -lh and df -h 🙂

                          1 Reply Last reply Reply Quote 0
                          • I
                            impreza233 last edited by

                            Sadly, rootfs.img does not fit in my /data partition 😞 But my work could be good...

                            D 1 Reply Last reply Reply Quote 0
                            • D
                              doniks @impreza233 last edited by

                              @impreza233 said in Stuck on finishing booting Moto E 2015 (surnia):

                              Sadly, rootfs.img does not fit in my /data partition 😞 But my work could be good...

                              Damn. No, wait. I'm slightly more awake now: your df /data says you have a 5 GB partition and 4.5 GB are free .... the halium rootfs is only like 500MB or so, right? How did you conclude now that it doesn't fit?

                              1 Reply Last reply Reply Quote 1
                              • I
                                impreza233 last edited by impreza233

                                Because the image that writes halium-install on my phone has 3 GB of data, and the script refuses to write it on the partition. I have tested with 2 GB rootfs.img. Still no luck. I will continue researching on this.

                                D 1 Reply Last reply Reply Quote 0
                                • D
                                  doniks @impreza233 last edited by

                                  @impreza233 said in Stuck on finishing booting Moto E 2015 (surnia):

                                  the script refuses to write it on the partition

                                  ok, but as far as partition size and file size are concerned it should fit right?

                                  internet search for the value too big error bring up a lot of very different stuff about 32 bit OS' and filesystem limits, adb limitations ... could that be it? ... what host os do you have? how many bits? which recovery? adb version? could updating any of it help?

                                  https://forum.xda-developers.com/showpost.php?s=44d8b93ac534c41c3b3b0fa5a9f86494&p=76800956&postcount=184

                                  D 1 Reply Last reply Reply Quote 1
                                  • I
                                    impreza233 last edited by impreza233

                                    Host: tested on:
                                    -Ubuntu 16.04 64 bits, adb 64 bits
                                    -Linux Mint 19 32 bits, adb 32 bits

                                    Phone: TWRP 3.21-0
                                    EDIT: adb->this version: https://packages.ubuntu.com/search?keywords=adb
                                    Hope this helps...

                                    1 Reply Last reply Reply Quote 0
                                    • D
                                      doniks @doniks last edited by

                                      @impreza233

                                      ok, but as far as partition size and file size are concerned it should fit right?

                                      ??

                                      Hope this helps...

                                      yeah well, I'm just fishing in the dark here ... maybe try a 64bit 18.04 (live usb maybe), but feels like reaching.

                                      assuming that there's a dot missing in the twrp version number, then 3.2.1-0 isn't super old.

                                      if you want to debug it a bit you could manually create files of various sizes with dd and then adb push them and see what works

                                      1 Reply Last reply Reply Quote 1
                                      • I
                                        impreza233 last edited by

                                        Yes, I'm agree with the fact that the rootfs should fit on my partition 👍.
                                        I will test the image with dd and I will comment the results.
                                        Thanks for your support!!! 🙂 🙂

                                        1 Reply Last reply Reply Quote 1
                                        • I
                                          impreza233 last edited by

                                          Well, @doniks, I have tried creating files of various sizes with dd and doing an adb push with them, and there are some results:

                                          -Images of 1 GB or 1,5 GB are not created by an error of insufficient space in halium-install
                                          -Images of 2 GB or more are created but when I try to push it to the phone vĂ­a adb push (filename) /data it gives me an error of not enough partition size.

                                          I have tried it not only with Ubuntu Touch images, also with Plasma Mobile rootfs and Halium reference rootfs.

                                          1 Reply Last reply Reply Quote 0
                                          • I
                                            impreza233 last edited by

                                            In latest versions of JBBGameich's script this issue has been solved. I have flashed correctly rootfs.img and system.img This thread can be closed.

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