<![CDATA[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.

]]>https://forums.ubports.com/topic/5646/pixel-2-xl-taimen-testing-resultsRSS for NodeTue, 14 Apr 2026 15:58:00 GMTThu, 04 Feb 2021 00:33:12 GMT60<![CDATA[Reply to Pixel 2 XL (Taimen) Testing Results on Sat, 06 Feb 2021 07:30:08 GMT]]>@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

]]>https://forums.ubports.com/post/46109https://forums.ubports.com/post/46109Sat, 06 Feb 2021 07:30:08 GMT<![CDATA[Reply to Pixel 2 XL (Taimen) Testing Results on Fri, 05 Feb 2021 19:03:29 GMT]]>@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 ^^

]]>https://forums.ubports.com/post/46087https://forums.ubports.com/post/46087Fri, 05 Feb 2021 19:03:29 GMT<![CDATA[Reply to Pixel 2 XL (Taimen) Testing Results on Fri, 05 Feb 2021 18:32:04 GMT]]>@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.

]]>https://forums.ubports.com/post/46083https://forums.ubports.com/post/46083Fri, 05 Feb 2021 18:32:04 GMT<![CDATA[Reply to Pixel 2 XL (Taimen) Testing Results on Fri, 05 Feb 2021 16:01:21 GMT]]>@atomos Ok if you link me to a zip file and instructions I might be able to include that in the vendor partition

]]>https://forums.ubports.com/post/46076https://forums.ubports.com/post/46076Fri, 05 Feb 2021 16:01:21 GMT<![CDATA[Reply to Pixel 2 XL (Taimen) Testing Results on Fri, 05 Feb 2021 15:54:53 GMT]]>@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.

]]>https://forums.ubports.com/post/46075https://forums.ubports.com/post/46075Fri, 05 Feb 2021 15:54:53 GMT<![CDATA[Reply to Pixel 2 XL (Taimen) Testing Results on Fri, 05 Feb 2021 14:53:51 GMT]]>@flohack I can confirm no audio on whole device.

]]>https://forums.ubports.com/post/46074https://forums.ubports.com/post/46074Fri, 05 Feb 2021 14:53:51 GMT<![CDATA[Reply to Pixel 2 XL (Taimen) Testing Results on Fri, 05 Feb 2021 14:53:04 GMT]]>@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 😉

]]>https://forums.ubports.com/post/46073https://forums.ubports.com/post/46073Fri, 05 Feb 2021 14:53:04 GMT<![CDATA[Reply to Pixel 2 XL (Taimen) Testing Results on Fri, 05 Feb 2021 14:52:30 GMT]]>@atomos Cellular currently should work but no call audio 😛 in fact, no audio at all on the whole device... .Working on it

]]>https://forums.ubports.com/post/46072https://forums.ubports.com/post/46072Fri, 05 Feb 2021 14:52:30 GMT<![CDATA[Reply to Pixel 2 XL (Taimen) Testing Results on Fri, 05 Feb 2021 06:35:43 GMT]]>@maurice
Congratulations bro... Can you please make a short youtube Tutorial of Installing Ubuntu Touch on Pixel 2XL and its a short Review..

]]>https://forums.ubports.com/post/46060https://forums.ubports.com/post/46060Fri, 05 Feb 2021 06:35:43 GMT<![CDATA[Reply to Pixel 2 XL (Taimen) Testing Results on Fri, 05 Feb 2021 05:43:55 GMT]]>@maurice congratulations!!!
bty Cellular working?
pixel phone not supported CHM-CT 4G，always need mod vendor.img. I'll try later in ut.

]]>https://forums.ubports.com/post/46059https://forums.ubports.com/post/46059Fri, 05 Feb 2021 05:43:55 GMT<![CDATA[Reply to Pixel 2 XL (Taimen) Testing Results on Fri, 05 Feb 2021 04:25:58 GMT]]>@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!

]]>https://forums.ubports.com/post/46058https://forums.ubports.com/post/46058Fri, 05 Feb 2021 04:25:58 GMT<![CDATA[Reply to Pixel 2 XL (Taimen) Testing Results on Fri, 05 Feb 2021 03:43:03 GMT]]>@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.
]]>https://forums.ubports.com/post/46056https://forums.ubports.com/post/46056Fri, 05 Feb 2021 03:43:03 GMT<![CDATA[Reply to Pixel 2 XL (Taimen) Testing Results on Fri, 05 Feb 2021 02:53:41 GMT]]>@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
]]>https://forums.ubports.com/post/46055https://forums.ubports.com/post/46055Fri, 05 Feb 2021 02:53:41 GMT<![CDATA[Reply to Pixel 2 XL (Taimen) Testing Results on Thu, 04 Feb 2021 17:22:03 GMT]]>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
]]>https://forums.ubports.com/post/46040https://forums.ubports.com/post/46040Thu, 04 Feb 2021 17:22:03 GMT<![CDATA[Reply to Pixel 2 XL (Taimen) Testing Results on Thu, 04 Feb 2021 16:37:04 GMT]]>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)
]]>https://forums.ubports.com/post/46037https://forums.ubports.com/post/46037Thu, 04 Feb 2021 16:37:04 GMT<![CDATA[Reply to Pixel 2 XL (Taimen) Testing Results on Thu, 04 Feb 2021 16:15:36 GMT]]>@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$
]]>https://forums.ubports.com/post/46036https://forums.ubports.com/post/46036Thu, 04 Feb 2021 16:15:36 GMT<![CDATA[Reply to Pixel 2 XL (Taimen) Testing Results on Thu, 04 Feb 2021 11:03:28 GMT]]>@atomos No you probably need to do this in recovery. The partition is mounted as bind-mount, not easy to set readable....

]]>https://forums.ubports.com/post/46023https://forums.ubports.com/post/46023Thu, 04 Feb 2021 11:03:28 GMT<![CDATA[Reply to Pixel 2 XL (Taimen) Testing Results on Thu, 04 Feb 2021 11:01:38 GMT]]>@flohack can I copy files to /vendor/rfs/msm/mpss/readonly/mbn/mcfg/configs/mcfg_sw/generic/
afer install ubuntu.
i use

sudo mount -o remount,rw /

then do copy command, its says read only filesystem.

]]>https://forums.ubports.com/post/46022https://forums.ubports.com/post/46022Thu, 04 Feb 2021 11:01:38 GMT<![CDATA[Reply to Pixel 2 XL (Taimen) Testing Results on Thu, 04 Feb 2021 08:23:52 GMT]]>@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.

]]>https://forums.ubports.com/post/46017https://forums.ubports.com/post/46017Thu, 04 Feb 2021 08:23:52 GMT<![CDATA[Reply to Pixel 2 XL (Taimen) Testing Results on Thu, 04 Feb 2021 07:44:09 GMT]]>@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!

]]>https://forums.ubports.com/post/46016https://forums.ubports.com/post/46016Thu, 04 Feb 2021 07:44:09 GMT<![CDATA[Reply to Pixel 2 XL (Taimen) Testing Results on Thu, 04 Feb 2021 07:23:04 GMT]]>@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.

]]>https://forums.ubports.com/post/46014https://forums.ubports.com/post/46014Thu, 04 Feb 2021 07:23:04 GMT<![CDATA[Reply to Pixel 2 XL (Taimen) Testing Results on Thu, 04 Feb 2021 05:18:10 GMT]]>Just ran into an issue rolling back. Will have to pick this test up later this week. Thanks for everyone's help.

]]>https://forums.ubports.com/post/46012https://forums.ubports.com/post/46012Thu, 04 Feb 2021 05:18:10 GMT<![CDATA[Reply to Pixel 2 XL (Taimen) Testing Results on Thu, 04 Feb 2021 03:53:27 GMT]]>@atomos ok will try that out and report back. Thanks for the help : )

]]>https://forums.ubports.com/post/46011https://forums.ubports.com/post/46011Thu, 04 Feb 2021 03:53:27 GMT