@flohack I can confirm no audio on whole device.
M
Posts made by maurice
-
RE: Pixel 2 XL (Taimen) Testing Resultsposted in Google Pixel 2/2 XL
-
RE: Pixel 2 XL (Taimen) Testing Resultsposted in Google Pixel 2/2 XL
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!
-
RE: Pixel 2 XL (Taimen) Testing Resultsposted in Google Pixel 2/2 XL
@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 offlineSecond 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. -
RE: Pixel 2 XL (Taimen) Testing Resultsposted in Google Pixel 2/2 XL
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 responseI 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 -
RE: Pixel 2 XL (Taimen) Testing Resultsposted in Google Pixel 2/2 XL
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 responseTesting 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 responseTesting 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) -
RE: Pixel 2 XL (Taimen) Testing Resultsposted in Google Pixel 2/2 XL
@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$ -
RE: Pixel 2 XL (Taimen) Testing Resultsposted in Google Pixel 2/2 XL
Just ran into an issue rolling back. Will have to pick this test up later this week. Thanks for everyone's help.
-
RE: Pixel 2 XL (Taimen) Testing Resultsposted in Google Pixel 2/2 XL
@atomos ok will try that out and report back. Thanks for the help : )
-
RE: Pixel 2 XL (Taimen) Testing Resultsposted in Google Pixel 2/2 XL
@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 ?
-
RE: Pixel 2 XL (Taimen) Testing Resultsposted in Google Pixel 2/2 XL
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 imageThen adb freezes and screen remains unresponsive.
-
RE: Pixel 2 XL (Taimen) Testing Resultsposted in Google Pixel 2/2 XL
@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 offlineIt gets to about 25% then fails. I will try another version.
-
RE: Pixel 2 XL (Taimen) Testing Resultsposted in Google Pixel 2/2 XL
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... ...doneWhen I try to format using TWRP:
Failed to unmount '/data' (Device or resource busy) Updating partition details... ...done -
RE: Pixel 2 XL (Taimen) Testing Resultsposted in Google Pixel 2/2 XL
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.zipThere 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.shSet 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.rulessudo chmod a + r /etc/udev/rules.d/51-android.rulesRestart the sudo udev service
sudo service udev restartOn 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.imgExample:
~/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.679sIssue fastboot flash vendor vendor.img
fastboot flash vendor vendor.imgExample:
~/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.imgExample:
~/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.301sOnce 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] recoveryThe 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.925sThen 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.imgNote: It remains at [ 0%] /data/rootfs.img
- Issue ./adb reboot [Unable to complete]
-
-
Pixel 2 XL (Taimen) Testing Resultsposted in Google Pixel 2/2 XL
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.imgIssue 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.