Need help to flash Meizu5 pro originally on Android. Problem with the cache partition



  • This is a well known problem: The Meizu Pro5 which shipped originally with the Flyme Android has a cache partition of 490MB whereas those who shipped with ubuntu have a cache of 700MB.

    As such, flashing of ubports fails because of incorrect cache partition.

    I've checked all over here and the internet but there are no useful sugestions, since people mention something along the lines of "There are now many ways to do partitioning", however I'm not comfortable enough doing it (mostly for fear of bricking the device) and I think a tutorial on how to resize the cache and other partitions of the phone would come in handy since there are surely other cases like mine (bought an original android Meizu 5, switched to canonical ubuntu touch and now cannot switch to ubports). Any method really, either TWRP, fastboot, etc...

    Any help appreciated, thanks!


  • Community

    Have you been using SP Flash Tool to switch from Flyme to Ubuntu? If not, there are more problems as you have a bootloader that cannot be unlocked.

    You'll need to punch in your device's model here and flash the Ubuntu factory image with SP Flash Tool. Please be careful with SP Flash Tool, don't check anything like "Format All", and read through any prompts carefully. It can and will brick your phone if used incorrectly.



  • @UniSuperBox that first link is broken.


  • Community

    @advocatux I'm still learning this forum, and i think I always will be. Fixed.



  • @UniSuperBox

    "The student's progress is satisfactory".



  • Thanks for the SP Flash Tool link, I will check it out. I'm confused about your first link though, you linked me to a website related to BQ products although I'm trying to get a fix for my Meizu phone?

    EDIT: Apparently the SP Flash Tool does not support the Meizu Pro 5 (only the MX4 appears on the list) so we're back to square one :-/

    EDIT2: Sorry I wasn't using the correct version, I'm checking SP Flash Tool and it seems to be the way to go. However, I do need the "scatter file" for the Meizu Pro 5 ubuntu edition, which will be used to change the phone partitions. A 15min check over the internet yielded no results so far... If someone can help with this, it would be very much appreciated.

    EDIT3: Can't get a scatter.txt file. I think its time to go back to android. This phone is unusable right now with the canonical ubuntu version, nothing is working (sim not registering, most of the apps crash, etc...). Maybe I will check again some months from now if someone found a way to install ubports on those Meizu Pro 5 that were originally shipped with the android 495MB cache partition. :-/



  • @mlinodasilva How interesting. I have an Android version and had no problems to flash either Canonical or Ubports version on it.
    Had acctually another one Android version and also no problem to install.

    Make sure when flashing to clear recovery folder as if there is no room, the flash will fail.

    Device/cache/recovery and delete all inside of that folder.



  • Here is the dump from when I try to flash ubports:

    503.0 # ubuntu-device-flash --server=http://system-image.ubports.com touch --device=turbo --channel=15.04/stable --bootstrap --recovery-image=recovery-turbo.img
    2017/08/19 16:12:19 Device is |turbo|
    2017/08/19 16:12:19 Flashing version 1 from 15.04/stable channel and server http://system-image.ubports.com to device turbo
    646.98 KB / 321.93 MB [___________________________________________________________________________________________________________________________________________________________________________________________________________________________] 0.20 % 646.49 KB/s 8m28s2017/08/19 16:12:20 Cache formatting was not successful, flashing may fail, check your partitions on device
    1.35 MB / 321.93 MB [______________________________________________________________________________________________________________________________________________________________________________________________________________________________] 0.42 % 768.35 KB/s 7m6s
    Can't boot recovery image
    

    Each time I have wiped the cache folder using TWRP, so for me it is a mystery why other people like you can successfully flash an android meizu pro 5 but not me.

    My problem was that I flashed canonical image on a stock chinese android meizu Pro 5, after changing the firmware to international, etc... Then at some point I broke my screen and it took me a few months for getting a new one. When I came back, canonical had discontinued ubuntu touch and ubports was just starting. When I couldn't flash my phone two months ago I figured I would wait for the community to have improved tools, but it seems I'm not yet there, so I think I migth have something strange going on over my partition structure although I never did touch them (so this should be the same stock android partition system.

    The only thing I found out about the scatter file is that it is supposed to be the mediatek MT 6795 scatter file, but the only thing I found on the web was this link for flashing android: http://flashromandroid.top/2017/03/4767-simple_step_flash_android-meizu-pro-5.html

    Again, I am simply not familiar at all with the concept of scatter files, which is why I thought about asking for help here. Unfortunately it seems I have a very specific issue with my phone though, so it's a bit frustrating on my end :).



  • @mlinodasilva It can't be Mediatek scatter file when Pro 5 has a Samsung Exynos processor.
    Maybe if you, from TWRP recovery wipe all, then reboot to fastboot mode and type: fastboot -w,
    then reboit to TWRP recovery and maku sure you have a update.zip on your ExternalSD and flash an Android Flyme international version, the one with unlocked bootloder( the same one when you have done it for the fist time).
    Then normally boot it, make sure developer option is selected, usb debbuging.
    Reboot to TWRP and wipe it all completely.
    Then flash Ubuntu recovery-turbo.img via fastboot and flash Ubports again.
    I would not use the option bootstrap, it never worked for me, nor the recovery addition.



  • @mlinodasilva try to flash the recovery-turbo.img first and then just reboot to recovery and flash it without the bootstrap and recovery additios. It has to work!



  • @Stefano Allright, thank you for the help I'm going to follow the steps you suggest and I will let you know the outcome



  • I tried your method, this is what I got.

    554.0 # ubuntu-device-flash --server=http://system-image.ubports.com touch --device=turbo --channel=15.04/stable
    2017/08/20 02:06:24 Device is |turbo|
    2017/08/20 02:06:24 Flashing version 1 from 15.04/stable channel and server http://system-image.ubports.com to device turbo
    2017/08/20 02:06:25 Start pushing /root/.cache/ubuntuimages/ubports-touch/15.04/stable/turbo/version-1.tar.xz to device
    2017/08/20 02:06:27 Start pushing /root/.cache/ubuntuimages/pool/device-60f53a5768e9340729d3a5ef9263bd3a9726792e7d0dbf830e5b124938dd419a.tar.xz to device
    2017/08/20 02:06:27 Start pushing /root/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
    2017/08/20 02:06:27 Start pushing /root/.cache/ubuntuimages/gpg/image-master.tar.xz to device
    2017/08/20 02:06:27 Start pushing /root/.cache/ubuntuimages/pool/ubports-d50c18b27590af5734a826c4f7857d8909b0e0f902d21af142a780620c8eb58b.tar.xz to device
    2017/08/20 02:06:27 Start pushing /root/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
    2017/08/20 02:06:27 Done pushing /root/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
    2017/08/20 02:06:27 Done pushing /root/.cache/ubuntuimages/gpg/image-master.tar.xz to device
    2017/08/20 02:06:27 Done pushing /root/.cache/ubuntuimages/ubports-touch/15.04/stable/turbo/version-1.tar.xz to device
    2017/08/20 02:06:27 Done pushing /root/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
    2017/08/20 02:07:03 Done pushing /root/.cache/ubuntuimages/pool/device-60f53a5768e9340729d3a5ef9263bd3a9726792e7d0dbf830e5b124938dd419a.tar.xz to device
    2017/08/20 02:07:44 Done pushing /root/.cache/ubuntuimages/pool/ubports-d50c18b27590af5734a826c4f7857d8909b0e0f902d21af142a780620c8eb58b.tar.xz to device
    2017/08/20 02:07:44 Created ubuntu_command: /root/.cache/ubuntuimages/ubuntu_commands016270558
    2017/08/20 02:07:44 Rebooting into recovery to flash
    

    Unfortunately phone displays: "Update failed, contact support"

    Not yet there...



  • @mlinodasilva I think those semi-secret Canonical partner devices seem to have some extra snags, but i have had the same problem as you on my Nexus 4. For me deleting all in .cache/ubuntuimages and install again solved the issue. You could try that unless you get any better device specific instructions here.



  • @mlinodasilva Have you flash the recovery-turbo.img downloaded from Ubports site?

    Try again, install TWRP recovery, wipe it all clean, install recovery-turbo.img again.

    Go to your Home folder on PC, enable to view hidden files, go to .cache/ubuntuimages and delete all folders from there.

    Then try again to flash it like before without bootstrap and recovery option.



  • Allright, this is turning to be quite the challenge...

    The recovery image I'm using is the one from ubports (as in the short tutorial to flash the Meizu Pro 5):
    wget http://cdimage.ubports.com/devices/recovery-turbo.img
    check.

    The TWRP image I'm using TWRP_3.0_m86_patched_st0rm77
    link here: https://forum.xda-developers.com/meizu-pro-5/development/recovery-twrp3-0m86patchedst0rm77-t3469296
    check

    Now I'm doing this exact procedure when I start again:

    fastboot flash recovery TWRP_3.0_m86_patched_st0rm77.img
    fastboot reboot
    #I switch to TWRP
    adb devices #I check that phone is visible
    adb push recovery-turbo.img /sdcard/
    #I switch to TWRP and flash the .img in the recovery (not system) partition
    #I reboot to recovery mode and have the ubuntu logo with the wine color background
    ubuntu-device-flash --server=http://system-image.ubports.com touch --device=turbo --channel=15.04/stable
    

    And then once the procedure I posted previously completes I have the error screen when I reboot the phone.

    Now regarding the cache clearing that you guys suggested, I couldn't find any .cache folder. I tried to look with TWRP and using adb from my laptop. No can do.

    I'm putting some info about my filesystem in hopes that it can shed some lights to some of you guys who know better

    PS: BTW: I'm flashing my phone as root from my laptop since otherwise adb doesn't recognise the phone, I'm assuming this is not a problem correct?

    PS1: In TWRP I can do an advanced wipe of the following partitions:
    Dalvik/ART Cache
    Cache
    System
    Data
    Internal Storage
    Micro SDCard
    USB OTG

    Which ones should I try wiping? I'm a little weary of doing anything harsh for fears of bricking the phone...

    585.0 # adb shell df -h
    Filesystem                Size      Used Available Use% Mounted on
    tmpfs                     1.3G     24.0K      1.3G   0% /dev
    tmpfs                     1.3G    624.0K      1.3G   0% /tmp
    /dev/block/sda43        495.9M    435.5M     50.2M  90% /cache
    /dev/block/sda41          2.4G      1.9G    495.2M  80% /system
    
    599.0 # adb shell ls -la 
    __bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
    __bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
    __bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
    drwxr-xr-x   26 root     root             0 Aug 20 15:50 .
    drwxr-xr-x   26 root     root             0 Aug 20 15:50 ..
    drwxr-xr-x    2 root     root             0 Aug 20 15:50 boot
    drwxr-xr-x    4 root     root          4096 Aug 20 11:05 cache
    lrwxrwxrwx    1 root     root            13 Apr 20  2016 charger -> /sbin/healthd
    drwxr-xr-x    2 root     root             0 Aug 20 15:50 custom
    drwxr-xr-x    2 root     root             0 Apr 20  2016 data
    -rw-r--r--    1 root     root          4520 Apr 20  2016 default.prop
    drwxr-xr-x   10 root     root          3240 Aug 20 15:50 dev
    drwxr-xr-x    2 root     root             0 Aug 20 15:50 efs
    drwxr-xr-x    3 root     root             0 Aug 20 15:50 etc
    drwxrwxrwx    2 root     root             0 Aug 20 15:50 external_sd
    -rw-r--r--    1 root     100          18281 Apr 20  2016 file_contexts
    -rw-r-----    1 root     root          1188 Apr 20  2016 fstab.m86
    -rwxr-xr-x    1 root     100        1195720 Apr 20  2016 init
    -rwxr-x---    1 root     root          3516 Apr 20  2016 init.rc
    -rwxr-x---    1 root     root           159 Apr 20  2016 init.recovery.m86.rc
    drwxr-xr-x    3 root     root             0 Apr 20  2016 license
    drwxr-xr-x    2 root     root             0 Apr 20  2016 oem
    dr-xr-xr-x  180 root     root             0 Jan  1  1970 proc
    -rw-r--r--    1 root     100           3909 Apr 20  2016 property_contexts
    drwxr-xr-x    2 root     root             0 Aug 20 15:50 recovery
    drwxr-xr-x    3 root     root             0 Apr 20  2016 res
    drwx------    2 root     root             0 Mar 27  2016 root
    drwxr-xr-x    2 root     100              0 Aug 20 15:50 sbin
    drwxrwxrwx    2 root     root             0 Aug 20 15:50 sdcard
    -rw-r--r--    1 root     100            526 Apr 20  2016 seapp_contexts
    -rw-r--r--    1 root     100             74 Apr 20  2016 selinux_version
    -rw-r--r--    1 root     100         135303 Apr 20  2016 sepolicy
    -rw-r--r--    1 root     100          12529 Apr 20  2016 service_contexts
    drwxr-xr-x    2 root     root             0 Aug 20 15:50 sideload
    drwxr-xr-x    3 root     root             0 Aug 20 15:50 storage
    drwxr-xr-x    2 root     root             0 Apr 20  2016 supersu
    dr-xr-xr-x   13 root     root             0 Aug 20 15:50 sys
    drwxr-xr-x   24 root     root          4096 Oct  4  2016 system
    drwxrwxr-x    2 root     shell           60 Aug 20 15:50 tmp
    drwxr-xr-x    5 501      root             0 Apr 20  2016 twres
    -rw-r--r--    1 root     100           3984 Apr 20  2016 ueventd.m86.rc
    -rw-r--r--    1 root     100           4790 Apr 20  2016 ueventd.rc
    drwxrwxrwx    2 root     root             0 Aug 20 15:50 usb-otg
    
    603.0 # adb shell ls -la /cache/recovery
    __bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
    __bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
    __bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
    drwxrwx---    2 root     root          4096 Aug 20 15:50 .
    drwxr-xr-x    4 root     root          4096 Aug 20 11:05 ..
    -rw-rw-rw-    1 root     root             7 Aug 20 15:50 .version
    -rw-rw-rw-    1 root     root     115227232 Aug 19 23:19 device-60f53a5768e9340729d3a5ef9263bd3a9726792e7d0dbf830e5b124938dd419a.tar.xz
    -rw-rw-rw-    1 root     root           473 Aug 19 23:12 device-60f53a5768e9340729d3a5ef9263bd3a9726792e7d0dbf830e5b124938dd419a.tar.xz.asc
    -rw-rw-rw-    1 root     root           864 Aug 20 11:08 image-master.tar.xz
    -rw-rw-rw-    1 root     root           473 Aug 20 11:08 image-master.tar.xz.asc
    -rw-rw-rw-    1 root     root           900 Aug 20 11:08 image-signing.tar.xz
    -rw-rw-rw-    1 root     root           473 Aug 20 11:08 image-signing.tar.xz.asc
    -rw-rw-rw-    1 root     root          1504 Jun 18 00:10 keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz
    -rw-rw-rw-    1 root     root           473 Jun 18 00:10 keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz.asc
    -rw-r--r--    1 system   system           0 Aug 20 15:36 last_install
    -rw-r-----    1 root     root       1152002 Aug 20 15:50 last_log
    -rw-r-----    1 root     root          2957 Aug 20 15:36 last_log.1
    -rw-r-----    1 root     root          2957 Aug 20 11:18 last_log.2
    -rw-r-----    1 root     root          2957 Aug 20 11:18 last_log.3
    -rw-r-----    1 root     root          2957 Aug 20 11:18 last_log.4
    -rw-r-----    1 root     root          2957 Aug 20 11:09 last_log.5
    -rw-r-----    1 root     root          2735 Aug 20 11:07 last_log.6
    -rw-r-----    1 root     root       1100423 Aug 20 11:07 last_log.7
    -rw-------    1 system   system     1152002 Aug 20 15:50 log
    -rw-r--r--    1 root     root          2348 Aug 20 15:50 recovery.fstab
    -rw-rw-rw-    1 root     root            74 Aug 20 15:50 storage.fstab
    -rw-rw-rw-    1 root     root     337566344 Aug 19 23:24 ubports-d50c18b27590af5734a826c4f7857d8909b0e0f902d21af142a780620c8eb58b.tar.xz
    -rw-rw-rw-    1 root     root           473 Aug 19 23:12 ubports-d50c18b27590af5734a826c4f7857d8909b0e0f902d21af142a780620c8eb58b.tar.xz.asc
    -rw-rw-rw-    1 root     root           714 Aug 20 11:09 ubuntu_command
    -rw-rw-rw-    1 root     root           448 Jun 18 00:10 version-1.tar.xz
    -rw-rw-rw-    1 root     root           473 Jun 18 00:10 version-1.tar.xz.asc
    
    604.0 # adb shell ls -la /system
    __bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
    __bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
    __bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
    drwxr-xr-x   24 root     root          4096 Oct  4  2016 .
    drwxr-xr-x   26 root     root             0 Aug 20 15:50 ..
    drwxr-xr-x    2 root     root          4096 Sep 13  2016 android
    drwxr-xr-x    2 root     root          4096 Oct  4  2016 bin
    drwxr-xr-x    2 root     root          4096 Apr 17  2015 boot
    lrwxrwxrwx    1 root     root            14 Oct  4  2016 cache -> /android/cache
    drwxr-xr-x   10 root     root          4096 Oct  4  2016 custom
    lrwxrwxrwx    1 root     root            13 Oct  4  2016 data -> /android/data
    drwxr-xr-x    4 root     root          4096 Jun 17 03:45 dev
    drwxr-xr-x  111 root     root          4096 Jun 17 03:45 etc
    lrwxrwxrwx    1 root     root            16 Oct  4  2016 factory -> /android/factory
    lrwxrwxrwx    1 root     root            17 Oct  4  2016 firmware -> /android/firmware
    drwxr-xr-x    3 root     root          4096 Oct  4  2016 home
    drwxr-xr-x   19 root     root          4096 Oct  4  2016 lib
    drwx------    2 root     root          4096 Jan  1  1970 lost+found
    drwxr-xr-x    2 root     root          4096 Sep 13  2016 media
    drwxr-xr-x    2 root     root          4096 Apr 17  2015 mnt
    drwxr-xr-x    3 root     root          4096 Oct  4  2016 opt
    lrwxrwxrwx    1 root     root            16 Oct  4  2016 persist -> /android/persist
    drwxr-xr-x    2 root     root          4096 Apr 17  2015 proc
    drwxrwxrwx    4 root     root          4096 Jun 17 23:34 root
    drwxr-xr-x    7 root     root          4096 Oct  4  2016 run
    drwxr-xr-x    2 root     root          4096 Jun 17 23:14 sbin
    drwxr-xr-x    2 root     root          4096 Sep 13  2016 srv
    drwxr-xr-x    2 root     root          4096 Apr  6  2015 sys
    lrwxrwxrwx    1 root     root            15 Oct  4  2016 system -> /android/system
    drwxrwxrwt    2 root     root          4096 Sep 13  2016 tmp
    drwxr-xr-x    2 root     root          4096 Sep 13  2016 userdata
    drwxr-xr-x   10 root     root          4096 Oct  4  2016 usr
    drwxr-xr-x   13 root     root          4096 Aug 24  2016 var
    lrwxrwxrwx    1 root     root            22 Oct  4  2016 vendor -> /android/system/vendor
    


  • Edit as a way of a new post since akismet flags my edits as spam???

    Now regarding the cache clearing that you guys suggested, I couldn't find any ubuntuimages inside the /system/root/ .cache folder. I used adb shell ls -la /system/root/.cache.

    BTW I never posted the link discussing the android vs. ubuntu devices partitions, it may come in handy as a reference for this device: https://forum.xda-developers.com/meizu-pro-5/help/meizu-pro5-32gb-64gb-partition-tables-t3460085

    EDIT: flashed again the recovery image then did ubuntu-device-flash after wiping cache and system through TWRP -> Advanced wipe and I still get the Update failed message.



  • @mlinodasilva It's the cache on your pc that you should delete. In your case /root/.cache/ubuntuimages since you install as root.



  • @hans1977se oooooh I see.

    It didn't work though. After flashing I got the same error screen, see below the steps I made:

    (removed because Akismet still flags this as spam will try to repost separately)

    It did re-download the packages from the remote server but apparently this was not enough



  • 614.0 # adb push recovery-turbo.img /sdcard/
    #I switch to TWRP and flash the .img in the recovery (not system) partition
    #I reboot to recovery mode and have the ubuntu logo with the wine color background
    
    615.0 # rm -rf /root/.cache/ubuntuimages
    
    2017.08.20 17:32:30 
    root@patashnik: /home/doktorcaligari/configs/meizu_pro5 
    616.0 # ubuntu-device-flash --server=http://system-image.ubports.com touch --device=turbo --channel=15.04/stable
    2017/08/20 17:32:35 Device is |turbo|
    2017/08/20 17:32:35 Flashing version 1 from 15.04/stable channel and server http://system-image.ubports.com to device turbo
    2017/08/20 17:32:35 Start pushing /root/.cache/ubuntuimages/ubports-touch/15.04/stable/turbo/version-1.tar.xz to device
    2017/08/20 17:32:35 Done pushing /root/.cache/ubuntuimages/ubports-touch/15.04/stable/turbo/version-1.tar.xz to device
    992 B / 109.89 MB [________] 0.00 % 7.39 MB/s 14s2017/08/20 17:32:35 Start pushing /root/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
    2017/08/20 17:32:35 Start pushing /root/.cache/ubuntuimages/gpg/image-master.tar.xz to device
    2017/08/20 17:32:35 Start pushing /root/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
    2017/08/20 17:32:35 Done pushing /root/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
    991 B / 321.93 MB [________] 0.00 % 10.41 MB/s 30s2017/08/20 17:32:35 Done pushing /root/.cache/ubuntuimages/gpg/image-master.tar.xz to device
    2017/08/20 17:32:35 Done pushing /root/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
    109.89 MB / 109.89 MB [======] 100.00 % 1.03 MB/s 
    2017/08/20 17:34:22 Start pushing /root/.cache/ubuntuimages/pool/device-60f53a5768e9340729d3a5ef9263bd3a9726792e7d0dbf830e5b124938dd419a.tar.xz to device
    144.91 MB / 321.93 MB [=======>______________] 45.01 % 1.12 MB/s 2m37s2017/08/20 17:34:44 Done pushing /root/.cache/ubuntuimages/pool/device-60f53a5768e9340729d3a5ef9263bd3a9726792e7d0dbf830e5b124938dd419a.tar.xz to device
    321.93 MB / 321.93 MB [===========] 100.00 % 1.49 MB/s 
    2017/08/20 17:36:11 Start pushing /root/.cache/ubuntuimages/pool/ubports-d50c18b27590af5734a826c4f7857d8909b0e0f902d21af142a780620c8eb58b.tar.xz to device
    2017/08/20 17:37:19 Done pushing /root/.cache/ubuntuimages/pool/ubports-d50c18b27590af5734a826c4f7857d8909b0e0f902d21af142a780620c8eb58b.tar.xz to device
    2017/08/20 17:37:19 Created ubuntu_command: /root/.cache/ubuntuimages/ubuntu_commands448925269
    2017/08/20 17:37:19 Rebooting into recovery to flash
    

    EDIT: For the sake of it, I tried the procedure from a previous thread: https://forums.ubports.com/topic/238/trouble-porting-to-the-meizu-pro-5-ubuntu/9

    ubuntu-device-flash --server=https://system-image.ubports.com / touch \ --download-only --revision=2 --device=turbo --channel=ubports-touch/legacy

    but I get the same "Update failed, contact support message.



  • @mlinodasilva It still looks like a possible problem with the cache, I think, but also it would be nice to know what is in the 991 bytes file and the 992 bytes file. It might be that it contains "Invalid request", or something, which would mean that you don't have access to all the files before you install.

    So, i think you should check the content of those two small files and try one more time to clear the cache. I.e: rm -fr /root/.cache/ubuntuimages/.


Log in to reply
 

Looks like your connection to UBports Forum was lost, please wait while we try to reconnect.