Ubuntu Touch on the Galaxy S5 help

ubuntunoob

@nero355
I have the log file
Output is here:
https://pastebin.com/E0127KTN
Not too sure what to make of it.
Thanks.

nero355

I am not sure either...

I do see some errors related to partitions and mounting them : Perhaps that is the issue ?!

ubuntunoob

@nero355
How can I fix that?
Thanks.

nero355

@ubuntunoob
You can try umount to unmount the partition and make sure it's not in use before flashing ?!

That's all what I can think of for now...

Good luck!

ubuntunoob

@nero355
How can I go about doing this?
Is this in twrp?
Sorry, I'm new but willing to learn put in the effort!
Thanks.

nero355

@ubuntunoob
Like I said earlier : TWRP Terminal

And then regular Linux commands like umount :

umount /data

for example will make sure the DATA partition is no longer mounted!

And something like this :

mount /system-data/ /data

Will mount it again as it was IIRC

ubuntunoob

@nero355
I did the steps on twrp:

umount /data

but now after mounting I get this error:

mount /system-data/ /data
mount: mounting /system-data/ on /data failed: No such file or directory

nero355

@ubuntunoob
:grinning_squinting_face: You are not supposed to do both steps!

Just the first one if you are having /DATA related errors!

But now that you did let me explain why the second one went wrong :
Because the directory /data does not exist

ubuntunoob

@nero355
I ran the first step

umount /data

before flashing Ubuntu Touch but still same error:

./halium-install -p ut ubports-touch.rootfs-xenial-armhf.tar.gz system.img
[sudo] password for hplaptop: 
D: Chosen rootfs is ubports-touch.rootfs-xenial-armhf.tar.gz
D: Chosen android image is system.img
D: Chosen release is ut
D: Compress images before pushing: false

I: Writing rootfs into mountable image
I: Writing android image into mountable image
I: Running post installation tasks
enabling SSH ... [done]
Please enter a new password for the user 'phablet':
Enter new UNIX password: 
Retype new UNIX password: 
passwd: password updated successfully
I: Shrinking images
e2fsck 1.45.7 (28-Jan-2021)
resize2fs 1.45.7 (28-Jan-2021)
Resizing the filesystem on .halium-install-imgs.amKTn/system.img to 53956 (4k) blocks.
Begin pass 2 (max = 30486)
Relocating blocks             XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Begin pass 3 (max = 18)
Scanning inode table          XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
The filesystem on .halium-install-imgs.amKTn/system.img is now 53956 (4k) blocks long.

I: Unmounting images
I: Pushing rootfs and android image to /data via ADB
I:    Pushing rootfs to /data via ADB
adb: error: failed to copy '.halium-install-imgs.amKTn/rootfs.img' to '/data/rootfs.img': couldn't read from device
.halium-install-imgs.amKTn/rootfs.img:....1 MB/s (1412783680 bytes in 220.153s)
I:    Pushing android image to /data via ADB
adb: error: failed to get feature set: no devices/emulators found

real	3m40.164s
user	0m0.283s
sys	0m1.996s
I: Cleaning up
umount: .halium-install-rootfs.kzAAa: not mounted.
error: no devices/emulators found

I don't why I get this error:

error: no devices/emulators found

The device is clearly there:

adb devices
List of devices attached
fa8d9901	recovery

mostafa3bdou

Hello Guys, can you please let us know what is the latest updates for this device? the development for this ROM still in-progress or stopped or what? and what is the latest state, can it be used for daily use?

Lakotaubp

@mostafa3bdou Please contact the porter directly they are the only ones who know for sure. The deatils will be on the device page of https://devices.ubuntu-touch.io