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

impreza233 · 3 Sept 2018, 10:32

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 · 3 Sept 2018, 11:53

@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

impreza233 · 3 Sept 2018, 12:08

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

impreza233 · 3 Sept 2018, 13:53

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

impreza233 · 3 Sept 2018, 16:39

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

doniks · 4 Sept 2018, 04:45

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

impreza233 · 9 May 2018, 19:47

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

impreza233 · 5 Sept 2018, 19:22

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

doniks · 5 Sept 2018, 22:06

@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

impreza233 · 9 Jun 2018, 08:34

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

doniks · 6 Sept 2018, 11:44

@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

impreza233 · 6 Sept 2018, 11:52

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

doniks · 6 Sept 2018, 19:57

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

impreza233 · 9 Jun 2018, 20:01

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.

doniks · 6 Sept 2018, 20:17

@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

impreza233 · 9 Jun 2018, 20:25

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

doniks · 6 Sept 2018, 21:02

@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

impreza233 · 6 Sept 2018, 21:04

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!!!

impreza233 · 17 Sept 2018, 19:23

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.

impreza233 · 17 Feb 2019, 20:54

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.