[solved] Mx4 - Installer blocked at "waiting for recovery mode"

Slayne

Here is the tip, if somebody has the same issue (waiting for recovery mode) :

Phone on "recovery mode".

Terminal :
sudo adb devices

If ‘no permission’ :
sudo adb kill-server
sudo adb start-server

Stefano

@slayne also unplugging from a PC then
adb kill-server
then plugging in again
and start adb start-server again

halucigenia

@advocatux It's still on the old Canonical Ubuntu Touch reset to base build without any extra installed apps (sorry that was not clear). I will see what I can do with ssh when I get back home.

advocatux

@halucigenia hmm you'll need adb to set & config ssh

hummlbach

@slayne And it didn't work with the latest installer for you? I'm asking because I had the same issue with the nexus 4 and it seems to be fixed for the nexus 4 with the latest version of the installer... Perhaps the fix (if there was one... :)) was in a device specific part of the installer... @NeoTheThird can you tell anything about that?

Slayne

@hummlbach No, even with the latest installer (*.21) it didn't work. The installer couldnt debug my recovery mode.

But i read several posts about the Mx4 and this phone seems a bit specific (many versions ?).
And i read several posts of people having the same problem as i had.

At least i hope this can help some people, or maybe help to improve the installer.

halucigenia

@advocatux Catch 22. even adb connect [IP address] returns Connection refused.

advocatux

@halucigenia if you really want to use that phone, probably it's better to fix the usb issue before trying anything else. Maybe it's an easy repair, like dirty connections.

Have you tried to use other usb cables? Have you tried to gently wiggle the usb cable connector?

halucigenia

@advocatux Yes, I have tried everything that I can think of to get USB working again.
The Ubuntu device now has the USB module from another flyme MX4 and the flyme MX4 has the Ubuntu devices USB module, USB still works fine on the flyme device with the same cables that I use in the Ubuntu device. It must be hardware other than the USB module or a software related problem.

I have been here before - See https://forums.ubports.com/post/4741

I just thought that this thread might have something that I have not yet tried.

advocatux

@halucigenia ah, I see

Josele13

This post is deleted!