-
@Keneda Right, if you have theCanon Canonical image working correctly all you need is the UBprots Installer. First double check dev mode us on and that adb detects the device correctly. Choose the wipe option when asked and that should be it. One tip when adb detects the device tape everything down. The connection on the usb port on mx4 can be a big problem. You may need to try a few cables. One that works on another device may not on the mx4. Good luck, keep persevering.
-
Dev mode is on.
Don't know how to directly check adb works but drivers are installed like asked in UBports software, and the fastboot part of the update is working well in UBports, software correctly exchange data with phone and then go to recovery, and then get stuck, same point, each time.I think if USB cable was the problem, it would not work with SP Flash Tool either.
I really think my problem is recovery not working properly, like i said, when i boot recovery, i don't have any menu, any choice, only thing i have is this, even after fresh canonical image install :
-
@Keneda Fastboot puts recovery onto the device, then from there it down loads and pushes the file s to the device. If the first bit has worked you should have UBports recovery installed at least. Reboot to fastboot then in a terminal run fastboot devices and see if your device is listed. If it is thats one issue sorted.
Just noticed your on Windows. Please try 15 sec ADB from XDA developers it works well with windows https://forum.xda-developers.com/showthread.php?t=2588979Edit: As I said just because a cable works with one thing don't rule it out. Try another if you can.
-
Edit: As I said just because a cable works with one thing don't rule it out. Try another if you can.
I tried all cables i have home, 4 at first like i said in my OP, and later a fifth, i also tried all USB2.0 ports on my PC (as 3.0 may cause problems).
I'll try adb thing later. -
So i tried adb and it doesn't work, been trying for almost one day switching drivers, cables and so, and nothing happens when doing the adb devices on console.
I'm very desapointed as i use this phone since 2015 for daily use and now i can't do nothing with it...
I'm stuck with a deprecated flyme MX4 or a UT deprecated one, more deprecated than before since i noticed the image given here with spflash tool is a "r26" one and not the last OTA 15 i had before.
I think my only way out would be a ubport image that i can flash with SP Flash tool as this is the only program that works for me.
-
@Keneda One other thing you can try is a live usb stick with Ubuntu installed on it, and run everything on that.
Edit: r26 was Canonical the installer should just work with it if we can sort the ADB issue. Trying to remember anything else done to fix this in the past. You could try searching the net again for answer or maybe someone here will have an answer. I will check back tomorrow. -
You are not alone. I have tried to install Ubports on my Meizu mx4 Ubuntu edition for nearly a year nothing works and I have tried all recommendations I got from telegram nothing worked. I think it must be some problem with the installer because I have tried to install both from Windows and Ubuntu computer and tried many different cables and it seems to be so for many with the Ubuntu edition
-
Ouraaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa!!!!
I suceeded!
Now i'll tell what was the problem if that can help anyone ( @Masayoshi maybe i.e) : ADB driver must be installed 3 times for 3 "differents" devices (but same phone).
In fact, when you connect MX4 (whatever mode) to the PC (windows at least) it detects it as a new device and then installs driver (or not, or you don't let him do and then install it yourself, anyway...).
As i understood from beginning, we must install the ADB driver when plugging MX4 in fastboot mode (what i've done before doing this topic).
But that's not all!In normal boot, connected to PC, in dev mod, they are 2 devices for MX4 (not every time...), one must be MTP drived, the other need to be ADB drived.
Now when you connect it to PC when UBPort software asks it, it auto detects the phone, and you don't even need to reboot in fastboot, software makes it itself!
In "Alcatel ABD Device", "Android ADB Interface" was MX4_Ubuntu_Edition before driver install (ADB)
In "Appareils mobiles", "MX4 Ubuntu Edition" was the same before driver install (MTP)
To be sure wich one is, enable/disable dev mode in phone, when it's off, only one device is here (MTP one)But that's not all... again!
We must install ADB driver when plugging phone to PC into recovery mode too!
In recovery PC sees only "MX4", install ADB driver here.
If not, after UBPort software auto-detects phone and then reboots it in fastboot, and then in recovery, it looses connection to phone...I must say something else, ADB drivers installed for each normal, fastboot and recovery MX4 "device", only normal and recovery mode give me a "ping" in an ADB command shell, but adb's working with UBport software when in fastboot so not a big thing...
And now the graal (it has been the longest 4 days for me since a long time...
) :
Now i'm trying to restore my data, another quest for me lol (contacts done, but MMS and attachment not working).
-
Well done on both install and persistence. I think the adb connection "path" between the installer and device was getting lost at various points during the process. Still your there now. Enjoy.
-
@Lakotaubp said in Problem upgrading MX4 from OTA15 to ubport:
Well done on both install and persistence. I think the adb connection "path" between the installer and device was getting lost at various points during the process. Still your there now. Enjoy.
When i only had adb installed for "fastboot device", i lost connection each time exactly the same point.
Same when i succeeded having MX4 recognized by UBport by installing ADB for "normal" device, was excited as i though i won, and then, exactly same point, just after entering recovery, bam!, lost connection.
That's what made me think "hey, could there be a "recovery device" too?"...PS : i'm not the giving up kind, yes
-
L Lakotaubp moved this topic from Support on
-
K Keneda referenced this topic on
-
K Keneda referenced this topic on