Fastboot: booting...FAILED (remote: bootimage: incomplete or not signed)finished.

josepjc · 19 May 2018, 09:23

@advocatux I downloaded this ubports-installer_0.1.13-beta_amd64.deb

advocatux · 19 May 2018, 09:30

@josepjc I would try again with the snap package

josepjc · 19 May 2018, 12:51

@advocatux Don't work, at this moment Ican't enter to bootloader holding the volume down button first and then pressing and holding power button as well. Unbootable

advocatux · 19 May 2018, 14:07

@josepjc in which step the installer failed?

I assume your phone is unlocked, why are you trying to access the bootloader?

josepjc · 19 May 2018, 15:36

@advocatux said in Fastboot: booting...FAILED (remote: bootimage: incomplete or not signed)finished.:

@josepjc in which step the installer failed?

I assume your phone is unlocked, why are you trying to access the bootloader?

Becouse the phone don't boot

advocatux · 19 May 2018, 15:39

@josepjc at which installation step it stopped working?

josepjc · 19 May 2018, 15:53

@advocatux when the installer tells me: press the volume down button first and then pressing and holding power button as well.

advocatux · 19 May 2018, 15:59

@josepjc I see you have filed a bug report (*) already, let's wait to see what the experts have to say about it.

(*) https://github.com/ubports/ubports-installer/issues/266

advocatux · 19 May 2018, 16:01

@josepjc wait, are you using a VM to do the installation?

josepjc · 19 May 2018, 16:24

@advocatux no

advocatux · 19 May 2018, 17:02

@josepjc right, then let's see what the devs have to say

josepjc · 20 May 2018, 07:43

I can access to the recovery mode and I have a SD 2GB

josepjc · 20 May 2018, 10:15

When I put de SD I can't access to the recovery mode, black screen...

humungus · 21 Jun 2018, 11:44

Hello,
this issue is still relevant for me. The workaround with the installer 0.1.12 is just to ignore the wrong image or whatever error occurs. In version 0.1.15-beta I can still not get beyond rebooting in fastboot mode.

advocatux · 21 Jun 2018, 11:59

@humungus what OS is running on your computer? What installer package are you using exactly? Do you have adb and fastboot installed on your computer? Have you tried to run the installer with sudo?

humungus · 21 Jun 2018, 14:55

@advocatux Hello I seemed to have fixed the issue. It is not a tool problem, but one of the installer. The tools are called asynchroniously and eventually hindering each other. I will clean up my code and send the patch to the maintainers.

advocatux · 21 Jun 2018, 17:05

@humungus perfect, I'm glad you found a solution

Scott-Marley · 22 Jun 2018, 09:19

I'm eagerly awaiting this update too. After a failed attempt at flashing 16.04/rc I had to resort to flashing a Fairphone Android stock image (urgh!)

Is there a .zip of the current 16.04 image I can flash manually, preferably with a "flash all" shell script? I'd be more than happy enough with that in the absence of a functioning ubports-installer.

humungus · 25 Jun 2018, 17:12

Hello, afaik the zip is build on the fly from the archives on the recovery system. I did not find a complete zip.

advocatux · 25 Jun 2018, 19:08

@scott-marley you can see here http://system-image.ubports.com/ how the system images are organized.

If you have trusty or xenial [*] running on your computer, you can try to install UT using the command line. You can also try to install that tool on bionic too, I heard it works but I haven't tried it myself on that distro.

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

EDIT: I've just remembered that that method worked on other devices but FP2 on the early days of 16.04 development. I think that's fixed now but I wanted to tell you. Anyway, you can give it a try.

[*] ubuntu-device-flash is only officially available for those releases