@HMZ47 said in Sony Xperia X Performance F8131:
Wipe system data & cache partitions inside twrp.
Reboot to bootloader and launch the installer.
For me it worked after I formated data inside TWRP and then did the wipes.
I sort of had the same issue today (among others), but a helpful member of the german UBports Telegram group helped me with the install. It runs now- Wohooo!
The trick was to use TWRP to format AND wipe the data partition. Afterwards it went smoothly.
This was addressed in this post already.
I got to play a bit with my new phone today. Wohooooo!
Not sure where to put the bugreports, also, I am not sure if they are halium or ubports specific.
Here they are:
Battery indicator seems to be a bit arbitrary. while on charge and then later while in use it got stuck at two percent for quite some time.
Performance: not very fast most of it is UI related I think. Probably caused by the lack of hardware acceleration? (If so, how could we get this going?)
Couldn't get the Falcon launcher to run. It installed fine but then I never saw a way to activate it.
Scaling of fonts in the UI (via UT tweak tool) is buggy, when set to 20 some Dialogs and screens do not fit hte display anymore.
Cheers and thanks to all involved here,
I have no clue why, but following @hsce1 's instructions worked for me, I got Ubuntu touch on my SIIIneo. Thanks everyone!!!!
With standalone I don't mean the zipped version. When you do "make" in the cloned folder a script gets creeated that is called halium-install-standalone.sh and that doesn't work.
With systemwide I meant that you seem to have your halium install script in your $PATH since you don't have a ./ in front of your "halium-install" command (if you have, your instructions are wrong).
I used the git clone files and they do not work on my setup (see the four last posts).
OK, I slept it over and also think that there is something wrong with halium-install.
I clone the script from git, put all the imagefiles in this folder and run:
./halium-install -p ut ubports-touch.rootfs-xenial-armhf.tar.gz system.img
Of course halium-install is not installed system whide that is why I have to use the ./ . I now think that there might be the culprit since your instructions don't use it.
When I use make, it gives me a script called halium-install-standalone.sh in a local bin folder which cannot be installed (no "make install" available). When I run hte standalone script it exits with an error BTW. I found no instructions about how to install the current halium- install system wide. I am sure chucking the script in /usr/bin won't do it :).
Your link ( https://github.com/JBBgameich/halium-install/releases) gets me to a page where I don't see any link to download stuff, what am I missing? Edit: found it, it is under Assets.
[14506.583270] usb 2-1.2: new high-speed USB device number 41 using ehci-pci [14506.691529] usb 2-1.2: no configurations [14506.691542] usb 2-1.2: can't read configurations, error -22 [14506.779122] usb 2-1.2: new high-speed USB device number 42 using ehci-pci [14507.079205] usb 2-1.2: device descriptor read/64, error -71 [14507.297126] usb 2-1.2: New USB device found, idVendor=18d1, idProduct=d001, bcdDevice= 2.28 [14507.297133] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [14507.297137] usb 2-1.2: Product: SAMSUNG_Android [14507.297140] usb 2-1.2: Manufacturer: SAMSUNG [14507.297143] usb 2-1.2: SerialNumber: halium-initrd [14507.301658] rndis_host 2-1.2:1.0 eth0: register 'rndis_host' at usb-0000:00:1d.0-1.2, RNDIS device, 00:00:00:00:00:00 [14507.362236] rndis_host 2-1.2:1.0 enp0s29u1u2: renamed from eth0
I tried again with an 5.1 Android, used the cloned installer, used your heimdall, and now I don't even get to the ubuntu boot screen.
No clue what to do next.
Funny, I just did this.
The -p ut option works now. dmesg output is:
[ 9620.086869] usb 2-1.2: new high-speed USB device number 20 using ehci-pci [ 9620.200193] usb 2-1.2: New USB device found, idVendor=18d1, idProduct=d001, bcdDevice= 2.28 [ 9620.200199] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 9620.200203] usb 2-1.2: Product: SAMSUNG_Android [ 9620.200206] usb 2-1.2: Manufacturer: SAMSUNG [ 9620.200210] usb 2-1.2: SerialNumber: Halium initrd Debug telnet on port 23 on rndis0 192.168.2.15 - also running udhcpd [ 9620.207225] rndis_host 2-1.2:1.0 eth0: register 'rndis_host' at usb-0000:00:1d.0-1.2, RNDIS device, 00:00:00:00:00:00 [ 9620.250120] rndis_host 2-1.2:1.0 enp0s29u1u2: renamed from eth0 chris@funkbook:~$ ssh email@example.com ssh: connect to host 192.168.2.15 port 22: Network is unreachable
On reboots I don't even get the RNDIS device.
Will start over...
I got it from there: https://gitlab.com/JBBgameich/halium-install/-/releases
I downloaded the zip file, unzipped everything, put the imagefiles in the folder as well and ran the script.
Well, with the above command I got to pick a unix password, but still hangs at the boot screen.
./halium-install ubports-touch.rootfs-xenial-armhf.tar.gz system.img ut
works, I'm trying to boot as we speak. I keep you posted.
Actually I didn't use -p ut because the script then exits.
./halium-install -p ut ubports-touch.rootfs-xenial-armhf.tar.gz system.img usage: ./halium-install rootfs.tar[.gz] system.img [release] positional arguments: rootfs.tar[.gz] system.img optional arguments: release: run common post installation tasks for release. supported: none, halium, pm, ut defaults : none
it was lineage 7.1.
I just reformated /data to ext3, but no improvement.
There are two different kinds of s3 neos around. One with Sony and one with a Samsung camera module. May this be it (not sure which one I have. Will reflash android 5.1 (which one did you use) and then we'll see.
Thank you very much for your time and efforts,
chris@funkbook:~/Downloads/s3neo/halium-install-continuous$ ssh firstname.lastname@example.org ssh: connect to host 10.15.19.82 port 22: Network is unreachable
OK, I redownloaded the files, the checksums match. Reflashed with your heimdall (still no passwords though). Same result, the device hangs at the bootscreen, I even left it overnight. RNDIS comes up in dmesg. Any Ideas on how to get some logfiles off of that thing?
BTW, AFAIK I never was asked for my passwords during install as was indicated by your instructions.
Enter your local host´s sudo password when prompted the first time The second time, enter the intended device lock password