Oneplus One Halium 9 port in the works...

Lakotaubp

@MrT10001 There appears to be a bug for now on 20.04 involving the cache resulting in an install error.
Using system settings will download 20.04 but not install it corrctly. Will let you know when fixed.
So close but .....

MrT10001

@Lakotaubp Thanks for letting me know. There appears to be a bug with the latest UT installer as well.

Lakotaubp

@MrT10001 Problem seems to have been identified and is being worked on. Will update when I hear more.

Lakotaubp

I have just installed 20.04 on my OPO using 0.9.10 installer but with a recovery from @TheVancedGamer things should now get merged.

MrT10001

@Lakotaubp Good news. I will wait patiently

TheVancedGamer

@MrT10001 Hi. Could you try installing focal again today? We merged some PRs to get it functioning, hopefully it should work.

MrT10001

@TheVancedGamer Failed again pushing to cache. Used 0.9.7 and 0.9.10 installer and it fails pushing at the last step with the adb error pushing to cache. This is on a windows machine.
Total failure on my Ubuntu machine on the same installers.

Device was soft bricked. Installed TWRP and formatted data, then advanced wiped Dalvik/Cache, system, data, cache and storage three times to recover.

Cleared the cache on the installer to ensure no old stuff is left behind.

Now managed to get 16.04 stable back on and that has issues booting with OTA-25 (hangs on UBPorts Powered by splash screen until you power off from power button).

wdehoog

@TheVancedGamer

Also for me it still fails. See https://pastebin.com/Xg4TGKvB

Is it possible to show some version info in the recovery so we can check if the correct one is being flashed?
The log file indicates the installer uses the one from http://cdimage.ubports.com/devices/. Is that the correct one?

Does it work for you?

wdehoog

@TheVancedGamer

I just tried something. Don't know it is useful information.

I manually installed the recovery and boot images from https://ci.ubports.com/job/UBportsCommunityPortsJenkinsCI/job/ubports%252Fporting%252Fcommunity-ports%252Fjenkins-ci%252Fbacon/job/halium-9.0/lastSuccessfulBuild/artifact/halium_bacon.tar.xz

And the installer now did not show any error (disabled flashing system partitions) . But it is still not working see https://pastebin.com/Yr9sqy7q

Lakotaubp

@wdehoog Can you try flashing the recovery.mg with fastboot then run the installer without bootstrap?

wdehoog

@Lakotaubp That is exactly what I did.

MrT10001

@wdehoog Damn, I was looking at trying that next!

wdehoog

@MrT10001 I tried the halium-9 one. Maybe it should have been one of the other builds of https://ci.ubports.com/job/UBportsCommunityPortsJenkinsCI/job/ubports%252Fporting%252Fcommunity-ports%252Fjenkins-ci%252Fbacon/ so if you still want to try...

By the way the log now shows (see the pastebin): /sbin/sh: make_ext4fs: not found

Lakotaubp

@wdehoog Right I thought you had installed recovery and boot images not just recovery.

Lakotaubp

@wdehoog This is what @TheVancedGamer sent me earlier

can you try cat ~/.cache/ubports/bacon/Ubuntu\ Touch/ubuntu_command | grep device| awk '{print $2}'

This should output the name of the device tarball which has the halium 9 recovery

that tarball is also in ~/.cache/ubports/bacon/Ubuntu\ Touch/

open it in ubuntu, drag the recovery.mg out and flash it with fastboot

then retry without bootstrap

Must admit I don't understand it really, but it might help.
Edit: The recovery I installed with has changed to the one mentioned in the text above so no point in sending you that one.

wdehoog

@Lakotaubp The recovery file appears to be the same as the one I tried (well WinMerge says so).

Copying the data seems to work the install/update fails.

The first error seems to be:

mount -a mount: '/dev/block/platform/msm_sdcc.1/by-name/system'->'/system': No such file or directory

and indeed adb shell shows:

lrwxr-xr-x 1 root root 19 1970-01-01 00:00 system -> /system_root/system
drwxr-xr-x 2 root root 0 1970-01-01 00:00 system_root

root@A0001:/ # ls -l /system_root/
total 0

-edit-

Aha no this is wrong. mount just complains about non existing links the first real error appears to be make_ext4fs: not found
And indeed it does not. But mkfs.ext4 does exist.

wdehoog

@Lakotaubp
Tried to copy from the commandline but it fails:

adb.exe push "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\rootfs-992a3dd9f3fc67917d3abaa9786a86f7af59c60feabf6495223fc170de802863.tar.xz" "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\rootfs-992a3dd9f3fc67917d3abaa9786a86f7af59c60feabf6495223fc170de802863.tar.xz.asc" "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\device-7d4447b99f054a746fffb607d583e8b216227d28039ef6d16d35de81c08ffc3b.tar.xz" "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\device-7d4447b99f054a746fffb607d583e8b216227d28039ef6d16d35de81c08ffc3b.tar.xz.asc" "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\keyring-28992f008be20d562ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz" "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\keyring-28992f008be20d562ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz.asc" "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\version-14.tar.xz" "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\version-14.tar.xz.asc" "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\image-signing.tar.xz" "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\image-signing.tar.xz.asc" "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\image-master.tar.xz" "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\image-master.tar.xz.asc" "C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\ubuntu_command" "/cache/recovery/
C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\rootfs-992a3dd9f...170de802863.tar.xz: 1 file pushed. 12.2 MB/s (463061576 bytes in 36.065s)
C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\rootfs-992a3dd9f...3abaa9786a86f7af59c60feabf6495223fc170de802863.tar.xz.asc: 1 file pushed.
adb: error: failed to copy 'C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\device-7d4447b99f054a746fffb607d583e8b216227d28039ef6d16d35de81c08ffc3b.tar.xz' to '/cache/recovery/device-7d4447b99f054a746fffb607d583e8b216227d28039ef6d16d35de81c08ffc3b.tar.xz': remote write failed: No space left on device
C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\device-7d4447b99...de81c08ffc3b.tar.xz: 0 files pushed. 14.6 MB/s (63824272 bytes in 4.165s)
adb: error: failed to copy 'C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\device-7d4447b99f054a746fffb607d583e8b216227d28039ef6d16d35de81c08ffc3b.tar.xz.asc' to '/cache/recovery/device-7d4447b99f054a746fffb607d583e8b216227d28039ef6d16d35de81c08ffc3b.tar.xz.asc': couldn't read from device
C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\device-7d4447b99...35de81c08ffc3b.tar.xz.asc: 0 files pushed. 0.0 MB/s (488 bytes in 0.481s)
adb: error: failed to copy 'C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\keyring-28992f008be20d562ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz' to '/cache/recovery/keyring-28992f008be20d562ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz': couldn't read from device
C:\Users\neil\AppData\Roaming\ubports\bacon\Ubuntu Touch\keyring-28992f00...62ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz: 0 files pushed.
adb: error: 617-byte write failed: No error

This is df on my device:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 1460812 572 1460240 1% /dev
tmpfs 1460812 0 1460812 0% /mnt
tmpfs 1460812 108 1460704 1% /tmp
tmpfs 1460812 0 1460812 0% /storage
/dev/block/mmcblk0p16 516040 460884 55156 90% /cache
/dev/block/mmcblk0p14 1334432 1284468 49964 97% /system_root
/dev/block/mmcblk0p28 57591248 2244256 55346992 4% /data
/dev/block/mmcblk0p15 5024 4284 740 86% /persist
/dev/block/mmcblk0p1 65488 57424 8064 88% /firmware

wdehoog

Tried it again yesterday.

The installer still installs the old (wrong) recovery.
After manually flashing the correct recovery (see above) the installer seems to successfully finish. But...
After rebooting the first time the recovery appears and when rebooting a 2nd time it fails. Only the splash screen is shown and no adb access.

wdehoog

@TheVancedGamer Hats off to you! What a magnificant piece of work you have done. Fantastic.

Somehow the installer, besides installing he wrong recovery also fails to 'adb push' on my windows machine.

When flashing the correct recovery and doing the copying manually then after a reboot into the recovery the installation process started.

Lakotaubp

@wdehoog I used this recovery https://ci.ubports.com/job/UBportsCommunityPortsJenkinsCI/job/ubports%252Fporting%252Fcommunity-ports%252Fjenkins-ci%252Fbacon/job/halium-9.0/30/artifact/halium-unlocked-recovery_bacon.img from @TheVancedGamer booted into it used all the options under factory reset and ran installer 0.9.8 on Ubuntu and have 20.04 on my OPO. Very close now.