• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
UBports Robot Logo UBports Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Pixel 2 XL (Taimen) Testing Results

Scheduled Pinned Locked Moved Google Pixel 2/2 XL
33 Posts 4 Posters 6.8k Views 3 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A Offline
      atomos @maurice
      last edited by 4 Feb 2021, 02:20

      @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.

      M 1 Reply Last reply 4 Feb 2021, 02:39 Reply Quote 0
      • M Offline
        maurice @atomos
        last edited by 4 Feb 2021, 02:39

        @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.

        M 1 Reply Last reply 4 Feb 2021, 02:47 Reply Quote 0
        • M Offline
          maurice @maurice
          last edited by 4 Feb 2021, 02:47

          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.

          A 1 Reply Last reply 4 Feb 2021, 03:26 Reply Quote 0
          • A Offline
            atomos @maurice
            last edited by 4 Feb 2021, 03:26

            @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.

            M 1 Reply Last reply 4 Feb 2021, 03:45 Reply Quote 1
            • M Offline
              maurice @atomos
              last edited by maurice 2 Apr 2021, 03:47 4 Feb 2021, 03:45

              @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 ?

              A 1 Reply Last reply 4 Feb 2021, 03:52 Reply Quote 0
              • A Offline
                atomos @maurice
                last edited by 4 Feb 2021, 03:52

                @maurice I think u need rolling back to 9.0.0(lineageOS 16 )

                M 1 Reply Last reply 4 Feb 2021, 03:53 Reply Quote 0
                • M Offline
                  maurice @atomos
                  last edited by 4 Feb 2021, 03:53

                  @atomos ok will try that out and report back. Thanks for the help : )

                  M 1 Reply Last reply 4 Feb 2021, 05:18 Reply Quote 0
                  • M Offline
                    maurice @maurice
                    last edited by 4 Feb 2021, 05:18

                    Just ran into an issue rolling back. Will have to pick this test up later this week. Thanks for everyone's help.

                    F 1 Reply Last reply 4 Feb 2021, 07:23 Reply Quote 0
                    • F Offline
                      flohack @maurice
                      last edited by 4 Feb 2021, 07:23

                      @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.

                      My languages: 🇦🇹 🇩🇪 🇬🇧 🇺🇸

                      M 1 Reply Last reply 4 Feb 2021, 16:15 Reply Quote 0
                      • A Offline
                        atomos
                        last edited by 4 Feb 2021, 07:44

                        @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!

                        F 1 Reply Last reply 4 Feb 2021, 08:23 Reply Quote 0
                        • F Offline
                          flohack @atomos
                          last edited by 4 Feb 2021, 08:23

                          @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.

                          My languages: 🇦🇹 🇩🇪 🇬🇧 🇺🇸

                          A 1 Reply Last reply 4 Feb 2021, 11:00 Reply Quote 0
                          • A Offline
                            atomos @flohack
                            last edited by atomos 2 Apr 2021, 11:01 4 Feb 2021, 11:00

                            @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.

                            F 1 Reply Last reply 4 Feb 2021, 11:03 Reply Quote 0
                            • F Offline
                              flohack @atomos
                              last edited by 4 Feb 2021, 11:03

                              @atomos No you probably need to do this in recovery. The partition is mounted as bind-mount, not easy to set readable....

                              My languages: 🇦🇹 🇩🇪 🇬🇧 🇺🇸

                              1 Reply Last reply Reply Quote 0
                              • M Offline
                                maurice @flohack
                                last edited by 4 Feb 2021, 16:15

                                @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$ 
                                
                                
                                M 1 Reply Last reply 4 Feb 2021, 16:33 Reply Quote 0
                                • M Offline
                                  maurice @maurice
                                  last edited by maurice 2 Apr 2021, 16:37 4 Feb 2021, 16:33

                                  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)
                                  
                                  
                                  M 1 Reply Last reply 4 Feb 2021, 17:22 Reply Quote 0
                                  • M Offline
                                    maurice @maurice
                                    last edited by 4 Feb 2021, 17:22

                                    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
                                    
                                    
                                    A 1 Reply Last reply 5 Feb 2021, 02:53 Reply Quote 0
                                    • A Offline
                                      atomos @maurice
                                      last edited by 5 Feb 2021, 02:53

                                      @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
                                      
                                      
                                      M 1 Reply Last reply 5 Feb 2021, 03:43 Reply Quote 0
                                      • M Offline
                                        maurice @atomos
                                        last edited by 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.
                                        
                                        
                                        M 1 Reply Last reply 5 Feb 2021, 04:25 Reply Quote 0
                                        • M Offline
                                          maurice @maurice
                                          last edited by 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!

                                          A fmajokaF 2 Replies Last reply 5 Feb 2021, 05:43 Reply Quote 1
                                          • A Offline
                                            atomos @maurice
                                            last edited by 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.

                                            F 2 Replies Last reply 5 Feb 2021, 14:52 Reply Quote 0
                                            13 out of 33
                                            • First post
                                              13/33
                                              Last post