Oneplus One Halium 9 port in the works...
-
@Lakotaubp That is exactly what I did.
-
@wdehoog Damn, I was looking at trying that next!
-
@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
-
@wdehoog Right I thought you had installed recovery and boot images not just recovery.
-
@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. -
@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_rootroot@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. -
@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 errorThis 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 -
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.
-
@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.
-
@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.
-
-
We did it everybody, the OnePlus One now has focal in the installer alongside the devices website!
Please try installing and reporting your progress at https://forums.ubports.com/topic/8936/bacon-goes-focal?_=1682831293004
https://devices.ubuntu-touch.io/device/bacon/release/focal/ is now available in case you want to see what works as of now, help us fill the boxes! -
@TheVancedGamer Sorry. I somehow mamaged to downvote your post. Fat fingers on a small screen. I have upvoted to remove the downvote