Navigation

    UBports Robot Logo

    UBports Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    Failed installation to MX4

    Meizu MX4
    2
    4
    394
    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.
    • R
      reedzsu last edited by

      At the last step, the installer cannot push the ubports 16.04 files to MX4. The device is unlocked, booted, and sucessfully installed ubports 15.04 by TWRP. Please help me.

      R 1 Reply Last reply Reply Quote 0
      • R
        reedzsu @reedzsu last edited by

        error information:
        Error: adb:push: Error: {"error":{"code":1},"stdout":"adb: error: failed to copy 'C:\Users\abixz\AppData\Roaming\ubports\arale\Ubuntu Touch\ubports-a95fdf05c877099caaabe104ff9b7b1a848ee4868b74c23f1f13232b58d9085d.tar.xz' to '/cache/recovery/ubports-a95fdf05c877099caaabe104ff9b7b1a848ee4868b74c23f1f13232b58d9085d.tar.xz': remote No space left on device\r\nC:\Users\abixz\AppData\Roaming\ubports\arale\Ubuntu Touch\ubports-a95fdf05c877099caaabe104ff9b7b1a848ee4868b74c23f1f13232b58d9085d.tar.xz: 1 file pushed, 0 skipped. 1.7 MB/s (368184352 bytes in 212.294s)\r\nC:\Users\abixz\AppData\Roaming\ubports\arale\Ubuntu Touch\ubports-a95fdf05c877099caaabe104ff9b7b1a848ee4868b74c23f1f13232b58d9085d.tar.xz.asc: 1 file pushed, 0 skipped. 0.6 MB/s (488 bytes in 0.001s)\r\nC:\Users\abixz\AppData\Roaming\ubports\arale\Ubuntu Touch\device-83fddedbd574169d9ccf1d55ab25c8b3956062e71e693cd8a23c32e2cdd4d48a.tar.xz: 1 file pushed, 0 skipped. 2.1 MB/s (110714872 bytes in 51.100s)\r\nC:\Users\abixz\AppData\Roaming\ubports\arale\Ubuntu Touch\device-83fddedbd574169d9ccf1d55ab25c8b3956062e71e693cd8a23c32e2cdd4d48a.tar.xz.asc: 1 file pushed, 0 skipped. 0.5 MB/s (488 bytes in 0.001s)\r\nC:\Users\abixz\AppData\Roaming\ubports\arale\Ubuntu Touch\keyring-28992f008be20d562ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz: 1 file pushed, 0 skipped. 1.2 MB/s (1564 bytes in 0.001s)\r\nC:\Users\abixz\AppData\Roaming\ubports\arale\Ubuntu Touch\keyring-28992f008be20d562ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz.asc: 1 file pushed, 0 skipped. 0.3 MB/s (488 bytes in 0.001s)\r\nC:\Users\abixz\AppData\Roaming\ubports\arale\Ubuntu Touch\version-15.tar.xz: 1 file pushed, 0 skipped. 0.4 MB/s (468 bytes in 0.001s)\r\nC:\Users\abixz\AppData\Roaming\ubports\arale\Ubuntu Touch\version-15.tar.xz.asc: 1 file pushed, 0 skipped. 0.4 MB/s (488 bytes in 0.001s)\r\nC:\Users\abixz\AppData\Roaming\ubports\arale\Ubuntu Touch\image-signing.tar.xz: 1 file pushed, 0 skipped. 1.1 MB/s (940 bytes in 0.001s)\r\nC:\Users\abixz\AppData\Roaming\ubports\arale\Ubuntu Touch\image-signing.tar.xz.asc: 1 file pushed, 0 skipped. 0.5 MB/s (488 bytes in 0.001s)\r\nC:\Users\abixz\AppData\Roaming\ubports\arale\Ubuntu Touch\image-master.tar.xz: 1 file pushed, 0 skipped. 1.0 MB/s (900 bytes in 0.001s)\r\nC:\Users\abixz\AppData\Roaming\ubports\arale\Ubuntu Touch\image-master.tar.xz.asc: 1 file pushed, 0 skipped. 0.5 MB/s (488 bytes in 0.001s)\r\nC:\Users\abixz\AppData\Roaming\ubports\arale\Ubuntu Touch\ubuntu_command: 1 file pushed, 0 skipped. 0.8 MB/s (716 bytes in 0.001s)\r\nadb: error: failed to copy 'C:\Users\abixz\AppData\Roaming\ubports\arale\Ubuntu Touch\device-83fddedbd574169d9ccf1d55ab25c8b3956062e71e693cd8a23c32e2cdd4d48a.tar.xz' to '/cache/recovery/device-83fddedbd574169d9ccf1d55ab25c8b3956062e71e693cd8a23c32e2cdd4d48a.tar.xz': remote No space left on device\r\n13 files pushed, 0 skipped. 1.7 MB/s (478906740 bytes in 266.478s)"}

        T 1 Reply Last reply Reply Quote 0
        • T
          tera @reedzsu last edited by tera

          @reedzsu it looks like you've hit the issue with the cache partition being too small for the update files to be stored on the phone, can you check the size of the partition number 15 (/dev/mmcblk0p15)?
          You can use lsblk in a terminal for instance, it should be at least 700MB to work from some threads i read recently

          A few days ago, i actually repartitioned a resurected original MX4 with Android, i did killed/bricked it years ago, and following the help of this thread which is another solution to your problem as well: https://forums.ubports.com/post/47969 (see steps 9.0.STAGE 2)
          I have kept the info how to repartition using the Philz recovery image, on another laptop though, so can post it later as well here

          R 1 Reply Last reply Reply Quote 0
          • R
            reedzsu @tera last edited by

            @tera ,thanks for your information.
            I had sovled by parted tool.
            I had resized the cahe and system size.
            The device works well.
            Many thanks.

            1 Reply Last reply Reply Quote 1
            • Referenced by  Lakotaubp Lakotaubp 
            • First post
              Last post