problems flashing UBports on Meizu PRO 5 (Android international edition)

BlandCorporation · 23 May 2018, 03:33

Dude thank you so much for your guidance! Your instructions worked perfectly (a minor note for others reading is that the sda43 partition should be named "cache"). I've now got a nifty partition table all set up for 16.04.

I'm currently fighting with the UBports Installer and ubuntu-device-flash to try to get actual flashing of UBports system images to the device working (still the only working system has arisen from your TWRP backup). I've no idea what's wrong, but am wondering if there's an ADB authorization problem preventing the installers/flashers from working. I may try getting a UBports 16.04 image and manually transferring files from it to partitions on the device using the TWRP terminal...

Stefano · 23 May 2018, 04:10

@blandcorporation I might do a new16.04 backup of fresh install and upload it, then you can try to restore it and later update it.

Stefano · 23 May 2018, 19:38

@blandcorporation Here is the 16.04 PRO 5 latest backup zip file, unpack it, put it to your TWRP backup folder and restore.
https://drive.google.com/file/d/1e91EPP0RfP3T8xFsNH26f4ORNeJbz__A/view?usp=sharing

BlandCorporation · 23 May 2018, 22:03

My goodness, thanks again! Genuinely thanks for your guidance on this. It is hugely appreciated.

I actually went and manually downloaded the partition images for 16.04 and (carefully) extracted them on the phone and that worked also. I'm now happily running UBports 16.04 development with Anbox. I can't believe what I'm seeing. What the UBports team has achieved is amazing!

Marathon2422 · 23 May 2018, 23:59

@stefano oow thats tempting

TartanSpartan · 9 Jan 2018, 17:27

@stefano Hi there. I am trying to resize my 64GB Pro 5's partition table to enable me to install Xenial. I installed TWRP again and did an adb shell on my desktop. Following your guide, I get to chroot /system /bin/bash and then the prompt says "bash: groups: command not found". Then the user in the prompt changes to "root@localhost:/#". I then tried the command again and now it says "bash: chroot: command not found". Puzzled, I tried to do it from TWRP's integrated terminal, straight on the phone. Is there a reason a host PC has to do it via ADB, though? Then on TWRP the command returned "bash: groups: command not found", "bash: lesspipe: command not found" and "bash: dircolors: command not found". Are any of these warnings problematic enough for me to not be able to resize the partitions without correcting for them?

Furthermore, can anyone list the exact metrics of their sda41 through sda44 partitions after a succesful resize on a 64GB model? The start and end points, the size, etc?

Note: I came back to edit this message because the browser on my M10 often cuts out because of too many tabs, so I didn't want to lose it and made it a work in progress.

Stefano · 1 Sept 2018, 17:22

@tartanspartan just read the post about, you'll understand it.

TartanSpartan · 1 Sept 2018, 17:45

@stefano As is now clear I elaborated on my problem. The guide does not cater for these issues. Can you please read what I said and see if you can help me?

Stefano · 1 Sept 2018, 17:59

@tartanspartan yeah, it might trow out some errors, but should be ok to continue with resizing. It thrown errors for me too.
With exact sda41 up to sda44 I can't help as I only have 32Gb version of Pro 5. Maybe some else could help?

Math · 11 Sept 2018, 11:08

@Stefano : Hello. I try to put my Pro 5 15.04 in 16.04 (formerly Android) but I can't.
I tried with your method to increase the cache but I have too much error message.
I wonder if you received an echo with the use of gparted. if it works or not.

And second query, if I turn everything except TWRP, will it work with "ubports-installer" or I would still have to increase the cache?

thank you in advance

Stefano · 11 Sept 2018, 12:14

@math if you follow the guide carefully, you should be able to resize the .cache partition. Ignore the error messages and just continue.

By restoring the Backup 16.04 stable with TWRP, just download it, unpack it and then restore it. Afterwards, you'll only need to flash Ubuntu Recovery with fastboot.
But, the future updates (OTA-stable, rc, devel ) might fail due the size of the .cache (if you don't resize it before) , otherwise you should be able to use Ubports installer.

Math · 11 Sept 2018, 15:02

@stefano Thank you very much. I will try again. But you think OTAs in the future will be bigger and bigger. Or it's only for the passage in 16.04

Stefano · 11 Sept 2018, 15:37

@math Difficult to say, but I've seen a discussion of Ubports devs about shrinking the image size of futures OTA's .

Math · 11 Sept 2018, 20:43

@stefano I made the change sda42-43.
But when I wanted to install the 16.04 with ubsports-installer 0.1.20, it still put me the error "boot.img".
Whereas with the version 0.1.12, the installation 16.04 did well.
Hoping that the OTA 5 will be fine.

thank you for your explanations

Stefano · 12 Sept 2018, 05:23

@math Make sure you have installed latest fastboot and adb on your PC and try again.

A Former User · 12 Sept 2018, 10:53

@math I have got the same problem even after resize the partition, what i have done and worked for me :

sudo ubuntu-device-flash --server=http://system-image.ubports.com touch --device=turbo --channel=ubports-touch/16.04/rc --wipe

Stefano · 12 Sept 2018, 20:40

@xray2000 For me as well it was the only option.

Mirv · 29 Oct 2018, 14:02

Noting my success details posted at https://forums.ubports.com/post/14164

Marathon2422 · 29 Oct 2018, 14:18

I have re flashed flyme 6, and downgraded to flyme 5, then flashed the unlocked bootloader,then flashed UB, some times It will not go past the UB,recovery screen, I have then flashed twrp wiped, then flash a twrp made restore of UB,then flashed UB recovery to get a working OTA,and then updated.
I have done this with ch/en, flyme.

I quess,adb,is not,recognized sometimes