Meizu pro 5 without any os.
-
@bontemps Just try to flash the Unlocked Bootloader zip file that I send you the link. It should work.
-
I am relay not used to the smartphone world.
So, for me it is more magic than anithing, because i don't understand in depth what i'm doing.
So, when you say to flash the Unlocked Bootloader,
Does it mean: fastboot flash bootloader Unlocked_bootloader_pro5_update.zip -
@bontemps No, just flash the zip file. Do not extract it, just put it to your externalSD and click INSTALL
Do it from within TWRP recovery. No fastboot this time.
The Unlocked_bootloader_pro5_update.zip is a flashable zip file, it means can be flashed with TWRP recovery. It's whole Flyme Android firmware. -
@bontemps If you manage to flash it, reboot it and let it run, it takes up to 5 min to start FLYME, then go to Developer options, enable Usb debugging.
Reboot to recovery wipe it in TWRP recovery (don't worry, it's safe), reboot to bootloader, flash Ubuntu recovery, reboot to recovery and try Ubuntu-device-flash -
So, it is flashed, it boot in fastboot and TWRP.
But the problem is that i always can't mount the /data partition.
So, i think i can't restore the backup(same situation). -
I tried to reboot it and it went wrong, it restart in cycle, enter TWRP, in TWRP they are some process runing on a window and it restart the same.
-
@bontemps Wipe it inTWRP again, and flash it again.
-
I can't access TWRP, it is booting in cyrcle.
So maybe i should reflash TWRP. -
Actually, i tryed to reboot it using TWRP.
And now, it continually boot, enter TWRP, and reboot immediately, i have no time to use TWRP meanwhile. -
This post is deleted! -
@bontemps we need to fix the partition.
Go back to fastboot and type: fastboot -u
It suppose to format partition before erase, so try this first and then try to flash TWRP, and then that update.zip -
@bontemps You may also try this command, just copy and paste:
fastboot update update.zip
(where ''update.zip''is your renamed Unlocked_bootloader_pro5_update.zip placed on your PC in your Home directory)
-
@bontemps Herelink text is a little bit more about fastboot have a look.
Also in fastboot type fastboot --help and it display all the options.
Maybe another wipe would help.
Give it a try. I had a similar situation with the phone and was panicking that I bricked it, but in the end I sorted it out. I remember that I done : fastboot -w and also fastboot -u and one of them helped. -
@bontemps Any luck so far???
-
Very well, the /data partition was corrupt.
I have just formated it with TWRP and restored the backup.
The phone work very well and i directly made the update to ubport version 2.
Thank you very much for the help and the files. -
@bontemps Yeeeeeeesss!!!!! I told you we'll fix it. Enjoy it.
-
This post is deleted! -
Sorry, i was disconnected.
So, i don't remember clearly but there simply was a button in one of the TWRP's tools.
It was written on it: format /data (or something like that). -
https://forum.xda-developers.com/meizu-pro-5/how-to/tutorial-restore-hard-bricked-lost-t3838461
unlock bootloader only windows 7 -
I had Meizu Pro 5 Ubuntu Edition but run into the https://forums.ubports.com/assets/uploads/files/1528013524195-8a15d567-ca4b-44ca-a1ce-84fdb7e0aec7-image.png screen when first trying to update it to Ubports 16.04/stable channel.
Somehow now later I managed to flash - with ubuntu-device-flash - from within 16.04 ubuntu installation (actually, 16.04 lxd container with usb vendor specific passthrough). I did that by booting to Ubuntu's recovery installation with power button + volume up - this is where you might need the recovery-turbo.img but I had it flashed already.
I verified that from within my lxc container (where I had added lxc config device add CONTAINERNAME meizu usb vendorid=18d1) I was able to see the device with 'adb devices'. Then I ran ubuntu-device-flash --server=http://system-image.ubports.com touch --device=turbo --channel=ubports-touch/15.04/stable - I thought it got stuck after downloads, but actually then it started the "Pushing" phase. And even more to my surprise, it rebooted to flashing phase with Ubuntu prorgress bar going back and forth, and then booted into working Ubports installation! Even though I specified "15.04/stable", it seems it too pointed to 16.04 already, ie OTA-5.
The greatest thing was that since I didn't need to specify --bootstrap or --wipe, it was even the same installation I used as my main phone back in the days, so I had all my apps and photos intact.
