UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

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

    Scheduled Pinned Locked Moved Support
    39 Posts 10 Posters 11.4k Views 4 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
      Reply
      • Reply as topic
      Log in to reply
      This topic has been deleted. Only users with topic management privileges can see it.
      • IngoI Offline
        Ingo
        last edited by Ingo

        Not sure if it helps, but in the Fairphone forum there were some instructions how to sign TWRP images so that they can be used for a one off boot (without installing).

        It's basically this: https://z3ntu.github.io/2017/06/16/Signing-boot-images.html

        I tried to fiddle around with the ubports-installer sources and added some debug output to see the exact command that fails and gives the "FAILED (remote: bootimage: incomplete or not signed)" error:

        fastboot boot "~/.cache/ubports/images/FP2/boot.img"

        If I sign the image according to the link above and use that instead, I don't get the error.

        Edit: it seems this is already being worked on https://github.com/ubports/ubports-installer/issues/184 and the problem is not with the file being signed or not.

        1 Reply Last reply Reply Quote 0
        • LuksusL Offline
          Luksus
          last edited by

          @josepjc , @Scott-Marley :
          I also had to reflash my FP2 with android stock image, because the ubports installer version 0.1.13 "broke" it.
          After that I used the ubportsinstaller 0.1.9 and it worked like a charm...

          Devices: BQ e4.5, Fairphone 2, Fairphone 3, Lenovo X605F, Pinephone, Moto Z2 Force, OnePlus5T

          1 Reply Last reply Reply Quote 0
          • S Offline
            Scott-Marley
            last edited by

            Cheers for the advice everyone, I also stumbled with the unsupported "ubuntu-device-flash" in bionic, but as @Luksus also mentioned, v0.1.9 worked fine for me too (eventually, took a couple of goes).

            I'm now on 16.04/rc and just now got the W26 OTA update. 🙂

            1 Reply Last reply Reply Quote 1
            • humungusH Offline
              humungus
              last edited by

              Hey,
              in github is stated that the issue might be fixed. Maybe you can give it another try. I will do so later.

              1 Reply Last reply Reply Quote 0
              • PoltoP Offline
                Polto
                last edited by

                Did the same as @Luksus.
                Link to installer: https://github.com/ubports/ubports-installer/releases/tag/0.1.9-beta
                Thank you all for helping my phone out of its misery 🙂

                advocatuxA 1 Reply Last reply Reply Quote 0
                • advocatuxA Offline
                  advocatux @Polto
                  last edited by

                  @polto just for the record, there's a new installer version with all those old issues fixed

                  https://github.com/ubports/ubports-installer/releases/tag/0.1.18-beta

                  1 Reply Last reply Reply Quote 1
                  • J Offline
                    james
                    last edited by james

                    I managed to install Ubuntu Touch on a Fairphone 2 using the following method. I'm not sure every step is necessary, but I'll list them just in case.

                    • Laptop running Ubuntu 18.04
                    • Installed ubports-installer_0.1.9-beta_amd64.deb via command line (not Ubuntu Software) using 'sudo dpkg -i ubports-installer_0.1.9-beta_amd64.deb'. 1.20-beta failed repeatedly despite trying the deb, snap, and various permutations of this list.
                    • I had installed and reinstalled various versions of the OS on the Fairphone 2, but a fresh install of Fairphone Android manual switcher (fp2-sibon-18.04.1-manual-switcher) worked.
                    • Enabled developer mode with USB debugging enabled.
                    • Selected 'trust device every time'.
                    • Allowed ADB access to apps.
                    • Launched Ubports using CLI: 'sudo ubports-installer'
                    • Stepped through the wizard, using 15.04-stable, and wipe device.

                    Now I'm enjoying Ubuntu Touch - thank you!

                    LakotaubpL 1 Reply Last reply Reply Quote 1
                    • LakotaubpL Offline
                      Lakotaubp @james
                      last edited by Lakotaubp

                      @james Great well done. You might want to consider moving it to the dev channel in update settings. That way if you don't want to try 16.04 yet, you will have the ability to update from your phone rather than the installer on or around the 30/08(ota5).
                      Until then 16.04 if you want to try it will need the installer that includes ota4 at the end if this month.
                      Also nearly forgot 15.04 is not getting any updates so you may as well be dev anyway its as stable as 15.04 will be.

                      J 1 Reply Last reply Reply Quote 0
                      • J Offline
                        james @Lakotaubp
                        last edited by

                        @lakotaubp Wonderful, thanks for the advice.

                        1 Reply Last reply Reply Quote 0
                        • 5 Offline
                          5AhYoh2so
                          last edited by

                          @james YMMD, finally a working solution.Using the old installer (0.1.9) did the trick.

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post