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

Can't install on Nexus 4 that has Ubuntu touch

Scheduled Pinned Locked Moved Support
8 Posts 4 Posters 1.2k Views 1 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.
    • J Offline
      James T
      last edited by 10 Oct 2018, 20:19

      Having successfully installed ubports (15.04 stable) on a "new" Nexus 4, and transferred everything useful, I figured it would be good to put a newer version on my old device, so I selected 16.04rc as the version to install.

      However when I run the installer, I get an error about a failed adb push (see below)

      {"message":"Command failed: adb -P 5038 push \"/home/james/.cache/ubports/pool/ubports-f2bcfd75eb7d6fc4fce749774ed6338f84de3fc19bac8e03147e2d39a2596c99.tar.xz\" /cache/recovery/\n","stack":"Error: Command failed: adb -P 5038 push \"/home/james/.cache/ubports/pool/ubports-f2bcfd75eb7d6fc4fce749774ed6338f84de3fc19bac8e03147e2d39a2596c99.tar.xz\" /cache/recovery/\n\n    at ChildProcess.exithandler (child_process.js:282:12)\n    at emitTwo (events.js:125:13)\n    at ChildProcess.emit (events.js:213:7)\n    at maybeClose (internal/child_process.js:921:16)\n    at Socket.stream.socket.on (internal/child_process.js:348:11)\n    at emitOne (events.js:115:13)\n    at Socket.emit (events.js:210:7)\n    at Pipe._handle.close [as _onclose] (net.js:549:12)","killed":false,"code":1,"signal":null,"cmd":"adb -P 5038 push \"/home/james/.cache/ubports/pool/ubports-f2bcfd75eb7d6fc4fce749774ed6338f84de3fc19bac8e03147e2d39a2596c99.tar.xz\" /cache/recovery/","level":"debug","timestamp":"2018-10-10T19:47:56.306Z"}{"level":"error","message":"Devices: Error: Adb push error: ","timestamp":"2018-10-10T19:47:56.317Z"}
      {"level":"error","message":"Devices: Adb push error: ","timestamp":"2018-10-10T19:47:56.317Z"}
      {"level":"debug","message":"Running platform tool exec cmd adb -P 5038 shell stat -t /cache/recovery//ubports-f2bcfd75eb7d6fc4fce749774ed6338f84de3fc19bac8e03147e2d39a2596c99.tar.xz","timestamp":"2018-10-10T19:47:57.353Z"}
      {"message":"Command failed: adb -P 5038 shell stat -t /cache/recovery//ubports-f2bcfd75eb7d6fc4fce749774ed6338f84de3fc19bac8e03147e2d39a2596c99.tar.xz\nerror: no devices/emulators found\n","stack":"Error: Command failed: adb -P 5038 shell stat -t /cache/recovery//ubports-f2bcfd75eb7d6fc4fce749774ed6338f84de3fc19bac8e03147e2d39a2596c99.tar.xz\nerror: no devices/emulators found\n\n    at ChildProcess.exithandler (child_process.js:282:12)\n    at emitTwo (events.js:125:13)\n    at ChildProcess.emit (events.js:213:7)\n    at maybeClose (internal/child_process.js:921:16)\n    at Socket.stream.socket.on (internal/child_process.js:348:11)\n    at emitOne (events.js:115:13)\n    at Socket.emit (events.js:210:7)\n    at Pipe._handle.close [as _onclose] (net.js:549:12)","killed":false,"code":1,"signal":null,"cmd":"adb -P 5038 shell stat -t /cache/recovery//ubports-f2bcfd75eb7d6fc4fce749774ed6338f84de3fc19bac8e03147e2d39a2596c99.tar.xz","level":"debug","timestamp":"2018-10-10T19:47:57.377Z"}
      

      I tried doing a reset from the ubuntu system settings app but that didn't change anything.

      The GUI also claims I don't have an up-to-date installer, but the version 0.1.21-beta is the same as the version on GitHub.
      Does anybody have any suggestions?

      L A T 3 Replies Last reply 10 Oct 2018, 20:40 Reply Quote 0
      • L Offline
        Lakotaubp @James T
        last edited by 10 Oct 2018, 20:40

        @james-t I might have miss understood but update 15.04 to the dev channel in system settings then you should be able to go to 16.04 dev again by updating from system settings. Then you can stay there or go to 16.04 stable or rc the same way.

        1 Reply Last reply Reply Quote 0
        • A Offline
          advocatux @James T
          last edited by advocatux 10 Oct 2018, 21:16 10 Oct 2018, 21:14

          @james-t @Lakotaubp is right. Another method is this: you can switch channels running sudo system-image-cli -vvvv --switch ubports-touch/16.04/rc 🙂

          (The -vvvv option is in case you want the terminal output more verbose, you can skip it otherwise)

          1 Reply Last reply Reply Quote 1
          • T Offline
            Thomas_ww @James T
            last edited by 10 Oct 2018, 21:22

            @james-t I made an update from 15.04 to 16.04

            System Settings / Updates / Update settings / Channels / Release candidate
            System Settings / Updates

            it properly worked.

            1 Reply Last reply Reply Quote 0
            • J Offline
              James T
              last edited by 11 Oct 2018, 07:09

              Sorry, I didn't make it clear -- the old device doesn't have Ubports, it currently has Canonical's Ubuntu Touch, and my understanding was that the Ubports update system doesn't support upgrades from the Canonical base.

              L T 2 Replies Last reply 11 Oct 2018, 07:31 Reply Quote 0
              • L Offline
                Lakotaubp @James T
                last edited by Lakotaubp 10 Nov 2018, 10:25 11 Oct 2018, 07:31

                @james-t https://docs.ubports.com/en/latest/ all the info is in here under install : )

                1 Reply Last reply Reply Quote 0
                • T Offline
                  Thomas_ww @James T
                  last edited by Thomas_ww 10 Nov 2018, 09:53 11 Oct 2018, 09:49

                  @james-t use the Installer https://ubuntu-touch.io/de_DE/get-ut . I used the debian-Package for Linux-Mint. it will install 15.04 on Nexus.

                  Then make an update to 16.04
                  System Settings / Updates / Update settings / Channels / Release candidate
                  System Settings / Updates

                  1 Reply Last reply Reply Quote -1
                  • J Offline
                    James T
                    last edited by 12 Oct 2018, 16:36

                    Problem solved. It was nothing to do with the phone or the installer! It was an unstable USB connection!

                    1 Reply Last reply Reply Quote 0
                    4 out of 8
                    • First post
                      4/8
                      Last post