Pixel 2 XL (Taimen) Testing Results

maurice · 5 Feb 2021, 03:43

@atomos Yes, same issue. Also tried a different port and several USB C cables.

~/Desktop/ubports/halium-install$ ./halium-install-standalone.sh -p ut -s ubuntu-touch-android9-arm64.tar.gz system.img 
[sudo] password for :      
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.0eqim/system.img to 231448 (4k) blocks.
Begin pass 3 (max = 20)
Scanning inode table          XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
The filesystem on .halium-install-imgs.0eqim/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
* daemon not running; starting now at tcp:5037
* daemon started successfully
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.220s
user	0m0.025s
sys	0m0.721s
Error: Couldn't copy the files to the device, is it connected?
I: Cleaning up
umount: .halium-install-rootfs.o87p7: not mounted.
adb: device offline

Second attempt:

~/Desktop/ubports/halium-install$ ./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.zPBDe/system.img to 231448 (4k) blocks.
Begin pass 3 (max = 20)
Scanning inode table          XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
The filesystem on .halium-install-imgs.zPBDe/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.zPBDe/system.img:...157.2 MB/s (948011008 bytes in 5.750s)
adb: error: failed to read copy response
I:    Renaming to system-as-root compatible system image
adb: no devices/emulators found

real	0m12.006s
user	0m0.043s
sys	0m1.377s
Error: Couldn't copy the files to the device, is it connected?
I: Cleaning up
umount: .halium-install-rootfs.ZVxrz: not mounted.

maurice · 5 Feb 2021, 04:25

@Flohack @atomos SUCCESS!

After trying multiple times using the Macbook air ports. I tried a different setup. Used an external USB/USB C dock (Dell Universal Dock D6000) with a USB C to USB C cable connected to the phone.

So Macbook Air (2013) -> Dell Universal Dock -> Pixel 2 XL.

And when trying the script it finally worked!

~/Desktop/ubports/halium-install$ ./halium-install-standalone.sh -p ut -s ubuntu-touch-android9-arm64.tar.gz system.img 
[sudo] password for :      
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.Yy132/system.img to 231448 (4k) blocks.
Begin pass 3 (max = 20)
Scanning inode table          XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
The filesystem on .halium-install-imgs.Yy132/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
.halium-install-imgs.Yy132/rootfs.img:....0 MB/s (3221225472 bytes in 109.898s)
I:    Pushing android image to /data via ADB
.halium-install-imgs.Yy132/system.img:...27.5 MB/s (948011008 bytes in 32.918s)
I:    Renaming to system-as-root compatible system image

real	2m22.986s
user	0m0.438s
sys	0m6.972s
I: Cleaning up
umount: .halium-install-rootfs.5pR4w: not mounted.

Now on to testing capabilities. Thanks for all your help and input. @Flohack recommendation to try different host ports helped!

atomos · 5 Feb 2021, 05:43

@maurice congratulations!!!
bty Cellular working?
pixel phone not supported CHM-CT 4G，always need mod vendor.img. I'll try later in ut.

fmajoka · 5 Feb 2021, 06:35

@maurice
Congratulations bro... Can you please make a short youtube Tutorial of Installing Ubuntu Touch on Pixel 2XL and its a short Review..

flohack · 5 Feb 2021, 14:52

@atomos Cellular currently should work but no call audio in fact, no audio at all on the whole device... .Working on it

flohack · 5 Feb 2021, 14:53

@atomos Is the modification adding files or replacing them? Because with a replace I will have a hard time. Ofc I can add files if they are needed, or merge configs etc

maurice · 5 Feb 2021, 14:53

@flohack I can confirm no audio on whole device.

atomos · 5 Feb 2021, 15:54

@flohack thanks!
no replacing, just add ".mbn" files and lines of configs.
not working yet, in android OS, need do factory rest.

l'll format my phone reinstall ut, do more test.

flohack · 5 Feb 2021, 16:01

@atomos Ok if you link me to a zip file and instructions I might be able to include that in the vendor partition

atomos · 5 Feb 2021, 18:32

@flohack
carrier option is aways set to None. even I had selected my SIM card's carrier(CHN-CT), no lucky with your vendor.img.
so I back to Android 9, lineageOS17.1, all of them works fine.

in android OS(8.0-11.0), its supported CHN-CT(with 3g), mod vendor.img can supported 3g, LTE, VoLTE. just need copy files from other android phone with Snapdragon 835.

flohack · 5 Feb 2021, 19:03

@atomos Well modem doesnt work at all on the device, not specific to your country. I will try to work on it, gimme some time ^^

atomos · 6 Feb 2021, 01:06

This post is deleted!

atomos · 6 Feb 2021, 07:30

@flohack

thanks. I will test other things first.

I upload CHN-CT supported files, with simple declaration in zip, you can download from here:
https://www.dropbox.com/sh/habqlbh4chhrs0v/AAAsQbUJ-fdg3Ft1dUVtuocca?dl=0