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

    [Porting] Call for Testers

    Scheduled Pinned Locked Moved Oneplus 5/5T
    123 Posts 30 Posters 50.3k Views 10 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.
      • M Offline
        michi2302
        last edited by

        Hi, I have installed ubuntu touch like in https://pad.ubports.com/p/HaliumHowToTestInstall.
        when I Issue ./halium-install-standalone.sh -p ut -s ubuntu-touch-android9-arm64.tar.gz system.img - I get:

        😧 Chosen rootfs is ubuntu-touch-android9-arm64.tar.gz
        😧 Chosen android image is system.img
        😧 Chosen release is ut
        😧 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':
        Geben Sie ein neues UNIX-Passwort ein:
        Geben Sie das neue UNIX-Passwort erneut ein:
        passwd: password updated successfully
        I: Copying ssh key to the user 'phablet'
        I: Shrinking images
        e2fsck 1.45.6 (20-Mar-2020)
        resize2fs 1.45.6 (20-Mar-2020)
        Die Größe des Dateisystems auf .halium-install-imgs.ymhtd/system.img wird auf 118902 (4k) Blöcke geändert.
        Start von Durchgang 3 (max = 24)
        Die Inode-Tabelle wird gelesenXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
        Das Dateisystem auf .halium-install-imgs.ymhtd/system.img is nun 118902 (4k) Blöcke lang.

        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: no devices/emulators found
        I: Pushing android image to /data via ADB
        adb: error: failed to get feature set: no devices/emulators found
        I: Renaming to system-as-root compatible system image
        adb: no devices/emulators found

        real 0m0,012s
        user 0m0,010s
        sys 0m0,000s
        Error: Couldn't copy the files to the device, is it connected?
        I: Cleaning up
        umount: .halium-install-rootfs.UI62L: nicht eingehängt.
        adb: no devices/emulators found

        any hints ?

        Michael

        R 1 Reply Last reply Reply Quote 0
        • R Offline
          Raysun96 @michi2302
          last edited by

          @michi2302 Is your phone in recovery mode?
          Check adb devices

          1 Reply Last reply Reply Quote 0
          • M Offline
            michi2302
            last edited by

            yes, fastboot devices is ok, but adb devices doesnot show any device when phone is in fastboot mode

            usb debugging is on
            phone is unlocked

            1 Reply Last reply Reply Quote 0
            • arubislanderA Offline
              arubislander
              last edited by

              @michi2302 said in [Porting] Call for Testers:

              yes, fastboot devices is ok, but adb devices doesnot show any device when phone is in fastboot mode

              adb devices never shows any devices when the phone is in fastboot mode. Unless you meant to say recovery mode, the behavior described is expected.

              🇦🇼 🇳🇱 🇺🇸 🇪🇸
              Happily running Ubuntu Touch
              Google Pixel 3a (20.04 DEV)
              JingPad (24.04 preview)
              Meizu Pro 5 (16.04 DEV)

              M 1 Reply Last reply Reply Quote 1
              • M Offline
                michi2302 @arubislander
                last edited by

                @arubislander

                yes thats it - my phone was allways in fastboot-mode - new in recovery-mode all was fine

                🙂 - THX

                M 1 Reply Last reply Reply Quote 0
                • M Offline
                  michi2302 @michi2302
                  last edited by

                  so next problem, after successful installation - my phone is in the 1+ logo powered by android ??
                  I had originally installed a custom rom with trwp - maybe that's the problem ?

                  arubislanderA 1 Reply Last reply Reply Quote 0
                  • arubislanderA Offline
                    arubislander @michi2302
                    last edited by

                    @michi2302 I am not sure there already is a custom boot logo for the Oneplus 5/5T.

                    As long as your phone boots into Ubuntu Touch, then all is well.

                    🇦🇼 🇳🇱 🇺🇸 🇪🇸
                    Happily running Ubuntu Touch
                    Google Pixel 3a (20.04 DEV)
                    JingPad (24.04 preview)
                    Meizu Pro 5 (16.04 DEV)

                    M 2 Replies Last reply Reply Quote 0
                    • M Offline
                      michi2302 @arubislander
                      last edited by

                      @arubislander thx for reply

                      right - the bootlogo is probably from android 11 - other question to run "./halium-install-standalone.sh -p ut -s ubuntu-touch-android9-arm64.tar.gz system.img"
                      I have the recovery.img from "http://twoot.bin.org.in/nextcloud/index.php/s/2Zk2Lz8cZCdqArT"
                      installed is that correct ? - because without recovery adb will not run.

                      thx

                      1 Reply Last reply Reply Quote 0
                      • M Offline
                        michi2302 @arubislander
                        last edited by

                        @arubislander no phone does´t boots in Touch hangs on android boot logo

                        arubislanderA 1 Reply Last reply Reply Quote 0
                        • arubislanderA Offline
                          arubislander @michi2302
                          last edited by

                          @michi2302

                          I will have to gracefully bow out now, as I do not have a OP 5/T.
                          But just to get this clear for anyone dropping by to help you. You are in fact saying the installation failed because your phone does not boot to Ubuntu Touch. Correct?

                          🇦🇼 🇳🇱 🇺🇸 🇪🇸
                          Happily running Ubuntu Touch
                          Google Pixel 3a (20.04 DEV)
                          JingPad (24.04 preview)
                          Meizu Pro 5 (16.04 DEV)

                          M 1 Reply Last reply Reply Quote 0
                          • M Offline
                            michi2302 @arubislander
                            last edited by

                            @arubislander
                            yes, right - no problems during installprocess. but phone does not boot to ubuntu touch.

                            I 1 Reply Last reply Reply Quote 0
                            • I Offline
                              Ianus @michi2302
                              last edited by

                              @michi2302
                              You can fastboot into TWRP and use adb shell to connect to your phone and examine the image files.
                              They are in /data/.
                              android-rootfs.img (size 487022592)
                              rootfs.img (size 3221225472)
                              Sizes from my working OnePlus 5.

                              You can also check if you have flashed halium-boot.img and vendor.img.
                              fastboot flash boot halium-boot.img
                              fastboot flash vendor vendor.img

                              M 1 Reply Last reply Reply Quote 0
                              • S Offline
                                Shadowbird2468
                                last edited by

                                I did half of the device checks, I'll do the rest later.

                                Working

                                Actors: Manual brightness
                                Actors: Torchlight
                                Actors: Vibration
                                Bluetooth: Driver loaded at startup
                                Bluetooth: Enable/disable and flightmode works
                                Bluetooth: Persistent MAC address between reboots
                                Bluetooth: Pairing with headset works, volume control ok
                                Camera: Flashlight
                                Camera: Photo
                                Camera: Video
                                Camera: Switch between back and front camera
                                Cellular: Carrier info, signal strength
                                Cellular: Data connection
                                Cellular: PIN unlock
                                Endurance: Battery lifetime > 24h from 100%
                                GPU: Boot into UI
                                Misc: Shutdown / Reboot
                                Misc: Battery percentage
                                WiFi: Driver loaded at startup
                                WiFi: Persistent MAC address between reboots
                                WiFi: Enable/disable and flightmode works
                                Sensors: Automatic brightness
                                Sensors: Rotation
                                Sensors: Touchscreen
                                Sound: Loudspeaker
                                Sound: Loudspeaker volume control
                                Sound: Microphone
                                Sound: Earphones detected, volume control

                                Not working

                                Actors: Notification LED
                                Misc: Date and time are correct after reboot (go to flight mode before)
                                Misc: Online charging (Green charging symbol, percentage increase in stats etc) #No green charging symbol
                                Misc: Offline charging (Power down, connect USB cable, device should not boot to UT) #Boots into Oneplus logo

                                S 1 Reply Last reply Reply Quote 0
                                • M Offline
                                  michi2302 @Ianus
                                  last edited by

                                  @ianus can I also use Helium-recovery instead of twrp ?

                                  thx for reply

                                  I flohackF 2 Replies Last reply Reply Quote 0
                                  • S Offline
                                    Shadowbird2468 @Shadowbird2468
                                    last edited by

                                    This post is deleted!
                                    1 Reply Last reply Reply Quote 0
                                    • I Offline
                                      Ianus @michi2302
                                      last edited by Ianus

                                      @michi2302
                                      I don't know. But
                                      fastboot boot twrp-xy.img
                                      will not overwrite your boot or recovery partition on the phone. The phone will boot directly from the image file.

                                      M 3 Replies Last reply Reply Quote 0
                                      • flohackF Offline
                                        flohack @michi2302
                                        last edited by

                                        @michi2302 No, sorry, the Halium recovery does currently not mount all the partitions correctly, and it wont give a warning, so if you try to push files with adb they are just pushed into tmpfs mounts. You can use it if you manually mount data in recovery. But for the moment I recommend TWRP, our recovery will only be needed when we have OTA updates in place

                                        My languages: 🇦🇹 🇩🇪 🇬🇧 🇺🇸

                                        1 Reply Last reply Reply Quote 0
                                        • M Offline
                                          michi2302 @Ianus
                                          last edited by

                                          @ianus thx for reply
                                          my /data is empty ?

                                          michi@Core5M:~/Downloads$ adb shell
                                          root@OnePlus5:/ # ls /data
                                          root@OnePlus5:/ #

                                          regards

                                          1 Reply Last reply Reply Quote 0
                                          • M Offline
                                            michi2302 @Ianus
                                            last edited by

                                            @ianus
                                            now I have tested ./halium-install-standalone.sh -p ut -s ubuntu-touch-android9-arm64.tar.gz system.img

                                            and after success I had:

                                            adb shell

                                            root@OnePlus5:/ # cd data
                                            root@OnePlus5:/data # ls
                                            android-rootfs.img rootfs.img

                                            and then I reboot phone

                                            check again and /data is emty ??

                                            1 Reply Last reply Reply Quote 0
                                            • M Offline
                                              michi2302 @Ianus
                                              last edited by

                                              @ianus

                                              so now the phone boots up !!
                                              the problem was the recovery.img I downloaded from http://twoot.bin.org.in/nextcloud/index.php/s/2Zk2Lz8cZCdqArT

                                              now I installed trwp an all went fine...

                                              thx for help - have a nice day

                                              I 1 Reply Last reply Reply Quote 1
                                              • First post
                                                Last post