Pixel 2 XL (Taimen) Testing Results
-
Hi @Flohack I attempted to conduct the test but I'm not able to get past the loading of the UBPorts while TWRP Recovery is running.
I'm at the last step.
~/Desktop/ubports/halium-install$ sudo ./halium-install-standalone.sh -p ut -s ubuntu-touch-android9-arm64.tar.gz system.img D: Chosen rootfs is ubuntu-touch-android9-arm64.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.5 (07-Jan-2020) resize2fs 1.45.5 (07-Jan-2020) Resizing the filesystem on .halium-install-imgs.zkOht/system.img to 231448 (4k) blocks. Begin pass 3 (max = 20) Scanning inode table XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX The filesystem on .halium-install-imgs.zkOht/system.img is now 231448 (4k) blocks long. I: Unmounting images I: Pushing rootfs and android image to /data via ADB I: Pushing rootfs to /data via ADB [ 0%] /data/rootfs.img
Issue is that the pushing of rootfs to /data never completes. Not sure if I messed up the step before with wiping and formatting the partitions as I had wiped all the partitions instead of just cache and system using TWRP.
Trying these steps using Linux Mint on an 2013 Macbook Air.
-
Here's a replication of the steps following https://pad.ubports.com/p/HaliumHowToTestInstall
Here's the contents of my folders:
~/Desktop/ubports/halium-install$ ls platform-tools/ taimen/ halium-install-standalone.sh system.img twrp-3.5.0_9-0-taimen.img ubuntu-touch-android9-arm64.tar.gz platform-tools_r30.0.5-linux.zip taimen.zip
There are two folders "platform-tools" and "taimen".
Here are the steps I took:
Prepare for Installation
-
Download the latest root filesystem: wget https://ci.ubports.com/job/xenial-hybris-android9-rootfs-arm64/lastSuccessfulBuild/artifact/ubuntu-touch-android9-arm64.tar.gz
-
Download the customization of the device: halium-boot, system and vendor image provided by porter : http://twoot.bin.org.in/nextcloud/index.php/s/kFjWTt39MqNNnzs . Downloaded the Taimen files.
-
Download TWRP Recovery for your device: https://twrp.me/Devices/ - Note: DO NOT download the ZIP file for the TWRP installation that gained work with UT. You just need to download the .img file to get started! Downloaded twrp-3.5.0_9-0-taimen.img : https://dl.twrp.me/taimen/twrp-3.5.0_9-0-taimen.img.html from https://twrp.me/google/googlepixel2xl.html
-
Install Android platform tools: https://developer.android.com/studio/releases/platform-tools
Export the subfolder platform tools and cd inside
sudo cp adb / usr / bin && sudo cp fastboot / usr / bin
- Install additional packages:
sudo apt install qemu-user-static qemu-system-arm e2fsprogs simg2img
- Download halium-install:
wget https://github.com/JBBgameich/halium-install/releases/download/continuous/halium-install-standalone.sh
Set it to executable:
chmod 755 halium-install-standalone.sh
- Add udev rules for Android devices (this is also done by the Ubports Installer):
sudo curl --create-dirs -L -o /etc/udev/rules.d/51-android.rules https://raw.githubusercontent.com/snowdream/51-android/master/51-android.rules
sudo chmod a + r /etc/udev/rules.d/51-android.rules
Restart the sudo udev service
sudo service udev restart
On the Pixel 2XL Phone:
-
Enable developer mode in Android, allow USB debugging and OEM unlock: https://www.howtogeek.com/129728/how-to-access-the-developer-options-menu-and-enable-usb-debugging-on-android-4.2/
On the same page, enable OEM unlocking -
Connect your device
Confirm the security warning on the Android device
Check with adb devices if the device is listed
adb devices
- Shut down your Android and boot into fastboot mode
Power up, press and hold Vol-Down until the robot appears
Check with fastboot devices if the device is listed
fastboot devices
- Unlock the bootloader with "fastboot flashing unlock"
~/Desktop/ubports/halium-install$ fastboot flashing unlock < waiting for any device > OKAY [ 6.037s]
Confirm the warning on the device
- Return to the bootloader on the phone and Flash partitions
Issue fastboot flash boot halium-boot.img
fastboot flash boot halium-boot.img
Example:
~/Desktop/ubports/halium-install/taimen$ fastboot flash boot halium-boot.img Sending 'boot_b' (16444 KB) OKAY [ 0.499s] Writing 'boot_b' OKAY [ 0.159s] Finished. Total time: 0.679s
Issue fastboot flash vendor vendor.img
fastboot flash vendor vendor.img
Example:
~/Desktop/ubports/halium-install/taimen$ fastboot flash vendor vendor.img Sending 'vendor_b' (355036 KB) OKAY [ 10.774s] Writing 'vendor_b' OKAY [ 1.692s] Finished. Total time: 12.470s
- Boot TWRP recovery by running fastboot boot twrp-xy.img
fastboot boot twrp-3.5.0_9-0-taimen.img
Example:
~/Desktop/ubports/halium-install$ fastboot boot twrp-3.5.0_9-0-taimen.img Sending 'boot.img' (40960 KB) OKAY [ 1.206s] Booting OKAY [ 0.001s] Finished. Total time: 1.301s
Once TWRP loads on the phone
- Wipe cache and system.partition and format data partition to remove encryption
NOTE on this step I had actually wiped all the partitions and formatted all partitions (Dalvik / ART Cache, System, Data, Internal Storage, Storage). Every time I run TWRP using fast boot, adb says "Recovery" when I try adb devices:
~/Desktop/ubports/halium-install$ adb devices List of devices attached [DEVICE ID] recovery
The only way to restore TWRP menus was to fastboot flash all three of the taimen stock images:
~/Desktop/ubports/halium-install/taimen$ fastboot flash boot halium-boot.img Sending 'boot_a' (16444 KB) OKAY [ 0.483s] Writing 'boot_a' OKAY [ 0.155s] Finished. Total time: 0.661s ~/Desktop/ubports/halium-install/taimen$ fastboot flash vendor vendor.img Sending 'vendor_a' (355036 KB) OKAY [ 11.425s] Writing 'vendor_a' OKAY [ 1.632s] Finished. Total time: 13.061s ~/Desktop/ubports/halium-install/taimen$ fastboot flash system system.img Sending 'system_a' (356840 KB) OKAY [ 11.241s] Writing 'system_a' OKAY [ 1.678s] Finished. Total time: 12.925s
Then when I fastboot twrp it brings up the appropriate twrp menus show up on the phone.
Install the actual UT OS
Issue ./halium-install-standalone.sh -p ut -s ubuntu-touch-android9-arm64.tar.gz system.img
Add parameter -i if you want to install also your public key for easier SSH accessNOTE at this point I had actually rebooted back to the boot loader.
~/Desktop/ubports/halium-install$ sudo ./halium-install-standalone.sh -p ut -s ubuntu-touch-android9-arm64.tar.gz system.img D: Chosen rootfs is ubuntu-touch-android9-arm64.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.5 (07-Jan-2020) resize2fs 1.45.5 (07-Jan-2020) Resizing the filesystem on .halium-install-imgs.bfcXQ/system.img to 231448 (4k) blocks. Begin pass 3 (max = 20) Scanning inode table XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX The filesystem on .halium-install-imgs.bfcXQ/system.img is now 231448 (4k) blocks long. I: Unmounting images I: Pushing rootfs and android image to /data via ADB I: Pushing rootfs to /data via ADB [ 0%] /data/rootfs.img
Note: It remains at [ 0%] /data/rootfs.img
- Issue ./adb reboot [Unable to complete]
-
-
When wiping the Cache and System partitions using Advanced Wipe this is what TWRP displays:
Updating partition details... ...done Full SELinux support is present. Wiping Dalvik Directories... Cleaned: /data/dalvik-cache... -- Dalvik Directory Wipe Complete! Formating System using mkefs... Done. Updating partition details... ...done
When I try to format using TWRP:
Failed to unmount '/data' (Device or resource busy) Updating partition details... ...done
-
@maurice said in Pixel 2 XL (Taimen) Testing Results:
The only way to restore TWRP menus was to fastboot flash all three of the taimen stock images:
no need get twrp menu. when u flash haluum-boot.img, vendor.img.
fastboot boot twrp.img.
twrp always on first screen.
just run the last install command.then adb reboot. -
@atomos Thanks. I tried a different version of TWRP and I'm getting some progress but then the phone disconnects:
Using: twrp-3.3.0-0-taimen.img
~/Desktop/ubports/halium-install$ sudo ./halium-install-standalone.sh -p ut -s ubuntu-touch-android9-arm64.tar.gz.1 system.img D: Chosen rootfs is ubuntu-touch-android9-arm64.tar.gz.1 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.5 (07-Jan-2020) resize2fs 1.45.5 (07-Jan-2020) Resizing the filesystem on .halium-install-imgs.2BE8t/system.img to 231448 (4k) blocks. Begin pass 3 (max = 20) Scanning inode table XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX The filesystem on .halium-install-imgs.2BE8t/system.img is now 231448 (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: 65544-byte write failed: Success I: Pushing android image to /data via ADB adb: error: failed to get feature set: device offline I: Renaming to system-as-root compatible system image adb: device offline real 0m11.016s user 0m0.066s sys 0m0.898s Error: Couldn't copy the files to the device, is it connected? I: Cleaning up umount: .halium-install-rootfs.aWTBw: not mounted. adb: device offline
It gets to about 25% then fails. I will try another version.
-
Trying an earlier version of TWRP 3.2.3-1:
~/Desktop/ubports/halium-install$ sudo ./halium-install-standalone.sh -p ut -s ubuntu-touch-android9-arm64.tar.gz.1 system.img D: Chosen rootfs is ubuntu-touch-android9-arm64.tar.gz.1 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.5 (07-Jan-2020) resize2fs 1.45.5 (07-Jan-2020) Resizing the filesystem on .halium-install-imgs.OTiWz/system.img to 231448 (4k) blocks. Begin pass 3 (max = 20) Scanning inode table XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX The filesystem on .halium-install-imgs.OTiWz/system.img is now 231448 (4k) blocks long. I: Unmounting images I: Pushing rootfs and android image to /data via ADB I: Pushing rootfs to /data via ADB [ 0%] /data/rootfs.img [ 6%] /data/rootfs.img adb: error: 65544-byte write failed: Success I: Pushing android image to /data via ADB [ 0%] /data/system.img [ 82%] /data/system.img adb: error: failed to read copy response .halium-install-imgs.OTiWz/system.img: 1 file...ipped. 159.6 MB/s (948011008 bytes in 5.665s) adb: error: failed to read copy response I: Renaming to system-as-root compatible system image
Then adb freezes and screen remains unresponsive.
-
@maurice
mine:
macbookair2013mid with ubuntu 20.04.
pixel2 xl 128g with android 9 factory image.
download and install <- all like you did.
format data in twrp first, when everything ready.
flash halium-boot.img.
flash vendor.img.
fastboot boot twrp.img(3.50) then sreen just show twrp logo.never get menus.
install last install commad.
adb reboot. -
@atomos could the issue on mine might be that I have to roll back to android 9 before trying the steps?
For example should I be rolling back to 9.0.0 (PPR1.180610.009, Aug 2018) from https://developers.google.com/android/images ?
-
@maurice I think u need rolling back to 9.0.0(lineageOS 16 )
-
@atomos ok will try that out and report back. Thanks for the help : )
-
Just ran into an issue rolling back. Will have to pick this test up later this week. Thanks for everyone's help.
-
@maurice Its really strange but it could be your USB cable, or try different port on your host. Definitely this is an error related to the ADB protocol. So it looses connection to your device from time to time.
You can try yourself, push a bigger file into /data (few hundred megs) like:
adb push xy.tgz /data
and see if that goes through.Note that this has nothing to do with clearing partitions. You can also try an older TWRP version. We might also be able to use the UBports recovery, let me try to build that tonight.
-
@Flohack
can i use google factory image9.0(lineageOS16)'s vendor? all pixel phone not supported China Telecom 4g. so I need root the phone in android 9 and copy some mcfg_sw.mbn files into /vendor/rfs.... for 4g. thanks! -
@atomos You can use GoogleΒ΄s vendor partition but I found some things wont work with it. Might have problems with sensors, GPS, Camera. But give it a try.
-
@flohack can I copy files to /vendor/rfs/msm/mpss/readonly/mbn/mcfg/configs/mcfg_sw/generic/
afer install ubuntu.
i usesudo mount -o remount,rw /
then do copy command, its says read only filesystem.
-
@atomos No you probably need to do this in recovery. The partition is mounted as bind-mount, not easy to set readable....
-
@flohack just tried adb push using TWRP 3.2.3.0, seems that the push is failing around 100mb.
~/Desktop/ubports/halium-install$ adb push ubuntu-touch-android9-arm64.tar.gz /data adb: error: failed to get feature set: device offline ~/Desktop/ubports/halium-install$ adb push ubuntu-touch-android9-arm64.tar.gz /data adb: error: failed to read copy response.tar.gz ubuntu-touch-android9-arm64.tar.gz: 1 ... 97.2 MB/s (616134854 bytes in 6.048s) adb: error: failed to read copy response ~/Desktop/ubports/halium-install$ adb push ubuntu-touch-android9-arm64.tar.gz /data adb: error: failed to read copy response.tar.gz ubuntu-touch-android9-arm64.tar.gz: 1 ...103.4 MB/s (616134854 bytes in 5.684s) adb: error: failed to read copy response ~/Desktop/ubports/halium-install$ adb push ubuntu-touch-android9-arm64.tar.gz /data adb: error: failed to read copy response.tar.gz ubuntu-touch-android9-arm64.tar.gz: 1 ...109.3 MB/s (616134854 bytes in 5.376s) adb: error: failed to read copy response ~/Desktop/ubports/halium-install$ adb push ubuntu-touch-android9-arm64.tar.gz /data [ 1%] /data/ubuntu-touch-android9-arm64.tar.gz adb: error: failed to read copy response.tar.gz ubuntu-touch-android9-arm64.tar.gz: 1 ...108.5 MB/s (616134854 bytes in 5.418s) adb: error: failed to read copy response ~/Desktop/ubports/halium-install$ adb push ubuntu-touch-android9-arm64.tar.gz /data adb: error: failed to get feature set: device offline ~/Desktop/ubports/halium-install$
-
Testing using TWRP 3.2.3.0 (fails at 100mb)
~/Desktop/ubports/halium-install$ fastboot boot twrp-3.2.3-0-taimen.img Sending 'boot.img' (40960 KB) OKAY [ 1.187s] Booting OKAY [ 0.001s] Finished. Total time: 1.313s ~/Desktop/ubports/halium-install$ adb push ubuntu-touch-android9-arm64.tar.gz /data adb: error: failed to read copy response.tar.gz ubuntu-touch-android9-arm64.tar.gz: 1 ...109.3 MB/s (616134854 bytes in 5.378s) adb: error: failed to read copy response ~/Desktop/ubports/halium-install$ adb push ubuntu-touch-android9-arm64.tar.gz /data adb: error: failed to read copy response.tar.gz ubuntu-touch-android9-arm64.tar.gz: 1 ...109.9 MB/s (616134854 bytes in 5.348s) adb: error: failed to read copy response ~/Desktop/ubports/halium-install$ adb push ubuntu-touch-android9-arm64.tar.gz /data adb: error: failed to read copy response.tar.gz ubuntu-touch-android9-arm64.tar.gz: 1 ...108.1 MB/s (616134854 bytes in 5.436s) adb: error: failed to read copy response
Testing using TWRP 3.2.3.1 (fails at 100mb)
~/Desktop/ubports/halium-install$ fastboot boot twrp-3.2.3-1-taimen.img Sending 'boot.img' (40960 KB) OKAY [ 1.209s] Booting OKAY [ 0.001s] Finished. Total time: 1.310s ~/Desktop/ubports/halium-install$ adb push ubuntu-touch-android9-arm64.tar.gz /data adb: error: failed to read copy response.tar.gz ubuntu-touch-android9-arm64.tar.gz: 1 ...110.1 MB/s (616134854 bytes in 5.336s) adb: error: failed to read copy response ~/Desktop/ubports/halium-install$ sudo adb push ubuntu-touch-android9-arm64.tar.gz /data [sudo] password for : adb: error: failed to read copy response.tar.gz ubuntu-touch-android9-arm64.tar.gz: 1 ...109.8 MB/s (616134854 bytes in 5.350s) adb: error: failed to read copy response
Testing using TWRP 3.5.0.9 (Does not upload, frozen at 0%)
~/Desktop/ubports/halium-install$ adb push ubuntu-touch-android9-arm64.tar.gz /data [ 0%] /data/ubuntu-touch-android9-arm64.tar.gz ~/Desktop/ubports/halium-install$ adb push ubuntu-touch-android9-arm64.tar.gz /data adb F 02-04 11:28:55 40783 40783 file_sync_client.cpp:473] protocol fault: failed to read stat response: Success Aborted (core dumped)
-
Did some more tests. Was looking at the wrong string, it looks like adb push does work.
~/Desktop/ubports/halium-install$ cp ubuntu-touch-android9-arm64.tar.gz ubutuarchiverenamed ~/Desktop/ubports/halium-install$ adb push ubutuarchiverenamed /data adb: error: failed to read copy response ubutuarchiverenamed: 1 file pushed, 0 ...108.0 MB/s (616134854 bytes in 5.438s) adb: error: failed to read copy response ~/Desktop/ubports/halium-install$ adb push ubuntu-touch-android9-arm64.tar.gz /data adb: error: failed to read copy response.tar.gz ubuntu-touch-android9-arm64.tar.gz: 1 ...102.3 MB/s (616134854 bytes in 5.741s) adb: error: failed to read copy response ~/Desktop/ubports/halium-install$ adb push system.img /data adb: error: failed to read copy response system.img: 1 file pushed, 0 skipped. 63.1 MB/s (365404512 bytes in 5.520s) adb: error: failed to read copy response ~/Desktop/ubports/halium-install$ adb push twrp-3.5.0_9-0-taimen.img /data adb: error: failed to read copy response twrp-3.5.0_9-0-taimen.img: 1 file push...d. 7.8 MB/s (41943040 bytes in 5.136s) adb: error: failed to read copy response ~/Desktop/ubports/halium-install$ adb push vendor.img /data adb: error: failed to read copy response vendor.img: 1 file pushed, 0 skipped. 64.2 MB/s (363557072 bytes in 5.404s) adb: error: failed to read copy response
I also tried to use the install script without the password and user parameters which allows the system image to push, but it fails pushing the rootfs :
~/Desktop/ubports/halium-install$ sudo ./halium-install-standalone.sh ubuntu-touch-android9-arm64.tar.gz system.img D: Chosen rootfs is ubuntu-touch-android9-arm64.tar.gz D: Chosen android image is system.img D: Chosen release is none D: Compress images before pushing: false I: Writing rootfs into mountable image I: Writing android image into mountable image I: Running post installation tasks I: Shrinking images e2fsck 1.45.5 (07-Jan-2020) resize2fs 1.45.5 (07-Jan-2020) Resizing the filesystem on .halium-install-imgs.uXTvp/system.img to 231448 (4k) blocks. Begin pass 3 (max = 20) Scanning inode table XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX The filesystem on .halium-install-imgs.uXTvp/system.img is now 231448 (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: 65544-byte write failed: Success I: Pushing android image to /data via ADB adb: error: failed to read copy response .halium-install-imgs.uXTvp/system.img:...147.9 MB/s (948011008 bytes in 6.112s) adb: error: failed to read copy response real 0m12.719s user 0m0.045s sys 0m1.496s I: Cleaning up umount: .halium-install-rootfs.Hcs48: not mounted.
But if I try to use the script using "-P" or "-S" I get the following:
~/Desktop/ubports/halium-install$ sudo ./halium-install-standalone.sh -p ut -s ubuntu-touch-android9-arm64.tar.gz system.img D: Chosen rootfs is ubuntu-touch-android9-arm64.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.5 (07-Jan-2020) resize2fs 1.45.5 (07-Jan-2020) Resizing the filesystem on .halium-install-imgs.V34FH/system.img to 231448 (4k) blocks. Begin pass 3 (max = 20) Scanning inode table XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX The filesystem on .halium-install-imgs.V34FH/system.img is now 231448 (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 get feature set: device offline I: Pushing android image to /data via ADB adb: error: failed to get feature set: device offline I: Renaming to system-as-root compatible system image adb: device offline real 0m0.016s user 0m0.008s sys 0m0.005s Error: Couldn't copy the files to the device, is it connected? I: Cleaning up umount: .halium-install-rootfs.mFbra: not mounted. adb: device offline
~/Desktop/ubports/halium-install$ sudo ./halium-install-standalone.sh -p ut -s ubuntu-touch-android9-arm64.tar.gz system.img D: Chosen rootfs is ubuntu-touch-android9-arm64.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.5 (07-Jan-2020) resize2fs 1.45.5 (07-Jan-2020) Resizing the filesystem on .halium-install-imgs.2YQgD/system.img to 231448 (4k) blocks. Begin pass 3 (max = 20) Scanning inode table XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX The filesystem on .halium-install-imgs.2YQgD/system.img is now 231448 (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: 65544-byte write failed: Success I: Pushing android image to /data via ADB adb: error: failed to get feature set: device offline I: Renaming to system-as-root compatible system image adb: device offline real 0m6.227s user 0m0.019s sys 0m0.715s Error: Couldn't copy the files to the device, is it connected? I: Cleaning up umount: .halium-install-rootfs.dqGZa: not mounted. adb: device offline
-
@maurice said in Pixel 2 XL (Taimen) Testing Results:
sudo ./halium-install-standalone.sh -p ut -s ubuntu-touch-android9-arm64.tar.gz system.img
have you try no sudo?
./halium-install-standalone.sh -p ut -s ubuntu-touch-android9-arm64.tar.gz system.img