(Solved) Stuck on finishing booting Moto E 2015 (surnia)
-
@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 -lin 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 /datato check how much space is on the device -
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 -
@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=3221225472Uhm, 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 -
Sadly, rootfs.img does not fit in my /data partition
But my work could be good... -
@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 /datasays 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? -
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.
-
@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?
-
Host: tested on:
-Ubuntu 16.04 64 bits, adb 64 bits
-Linux Mint 19 32 bits, adb 32 bitsPhone: TWRP 3.21-0
EDIT: adb->this version: https://packages.ubuntu.com/search?keywords=adb
Hope this helps... -
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
ddand thenadb pushthem and see what works -
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!!! -
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.
-
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.
-
@impreza233 I've locked it
