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

bq Aquaris E5 HD Ubuntu Edition wants to be OEM unlocked during installation

Scheduled Pinned Locked Moved Support
23 Posts 5 Posters 4.4k Views 1 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.
    • T Offline
      Tartaros
      last edited by 17 Aug 2019, 12:43

      No, there is no indication of progress. Neither a filling progress bar in the installer nor some log on the console. Just the animation in the background window (appearing and disappearing dots, circle spinning around the robot).

      L 1 Reply Last reply 17 Aug 2019, 13:02 Reply Quote 0
      • L Offline
        Lakotaubp @Tartaros
        last edited by Lakotaubp 17 Aug 2019, 13:02

        @Tartaros Give it a little longer, can't remember how long it takes with first time flash should be less than half an houryou should then get pushing files to device iron similar. If it appears to have stuck, stop the installer, disconnect your device. Restart installer, then connect device when asked and try again. Perhaps with another version of the installer like the snap if that still doesn't work.

        T 1 Reply Last reply 17 Aug 2019, 13:49 Reply Quote 0
        • T Offline
          Tartaros @Lakotaubp
          last edited by 17 Aug 2019, 13:49

          @Lakotaubp As I already wrote above, the installer hangs at the point depicted in the image. This also didn't change for about an hour, so I closed the installer, disconnected the device and shut the phone down by holding the volume up and power buttons for about seven seconds. I can still successfully boot into the Canonical Ubuntu Touch, it seems like the installer did nothing at all. I don't think that trying it again would be successful. Is it possible to do the OEM unlock prior to launching the installation process so the installer can directly start its work?

          Unfortunately I have no other choice than using the AppImage as the Snap support is not yet finished for my OS.

          Should I file an issue on Github regarding that the phone cannot be automatically OEM unlocked?

          L 1 Reply Last reply 17 Aug 2019, 14:02 Reply Quote 0
          • L Offline
            Lakotaubp @Tartaros
            last edited by 17 Aug 2019, 14:02

            @Tartaros You have abd and fastboot installed then in a terminal run adb devices then
            sudo fastboot OEM unlock

            That should do it. As for rerunning the installer, sometimes it progresses a bit further each time. It's always worth another run. Sorry I thought snaps could run on Manjaro

            T 1 Reply Last reply 17 Aug 2019, 14:11 Reply Quote 0
            • T Offline
              Tartaros @Lakotaubp
              last edited by Tartaros 17 Aug 2019, 14:11

              @Lakotaubp I expect I need to switch the device to fastboot mode prior to performing the OEM unlock? I will try it tomorrow.

              In theory yes, snaps can be run with Manjaro, but the snap support is still experimental and I do not want a snap error to make my phone a pricy paperweight.

              L M 2 Replies Last reply 17 Aug 2019, 15:06 Reply Quote 0
              • L Offline
                Lakotaubp @Tartaros
                last edited by 17 Aug 2019, 15:06

                @Tartaros Yes after running adb devices to see your device run
                adb reboot bootloader
                Then
                Sudo fastboot oem unlock

                T 1 Reply Last reply 18 Aug 2019, 08:21 Reply Quote 0
                • T Offline
                  Tartaros @Lakotaubp
                  last edited by 18 Aug 2019, 08:21

                  @Lakotaubp I tried as you suggested, but

                  sudo fastboot oem unlock
                  

                  simply hangs after printing a bunch of whitespace characters. I assume that the installer got stuck the same way. Is there any guide on how to unlock the bootloader of the E5? I found some guides for other bq models but none specifically for the E5.

                  L 1 Reply Last reply 18 Aug 2019, 08:35 Reply Quote 0
                  • L Offline
                    Lakotaubp @Tartaros
                    last edited by Lakotaubp 18 Aug 2019, 08:35

                    @Tartaros So when you open a terminal and type:
                    adb devices
                    Your devices is detected, yes. If not you need to grant permisson on your device. There should be a pop up window appear. Then just type the next to commands
                    adb reboot bootloader
                    Wait for that, then it's
                    sudo fastboot oem unlock and that should be it. Your device is unlocked and you can carry on.

                    T 1 Reply Last reply 18 Aug 2019, 08:39 Reply Quote 0
                    • T Offline
                      Tartaros @Lakotaubp
                      last edited by 18 Aug 2019, 08:39

                      @Lakotaubp The device is listed by

                      adb devices
                      

                      (yes, I authorized the device by accepting the popup) and after

                      adb reboot bootloader
                      

                      it is also listed when executing

                      fastboot devices
                      

                      but the subsequent command

                      sudo fastboot oem unlock
                      

                      starts, prints some whitespaces and then does nothing.

                      L 1 Reply Last reply 18 Aug 2019, 09:10 Reply Quote 0
                      • L Offline
                        Lakotaubp @Tartaros
                        last edited by 18 Aug 2019, 09:10

                        @Tartaros Now please try the installer again, after rebooting your phone.

                        T 1 Reply Last reply 18 Aug 2019, 09:35 Reply Quote 0
                        • T Offline
                          Tartaros @Lakotaubp
                          last edited by 18 Aug 2019, 09:35

                          @Lakotaubp The installer still says that the bootloader needs to be unlocked. I think the unlock command didn't work (it didn't even terminate).

                          L 1 Reply Last reply 18 Aug 2019, 10:03 Reply Quote 0
                          • L Offline
                            Lakotaubp @Tartaros
                            last edited by Lakotaubp 18 Aug 2019, 10:03

                            @Tartaros which version of the installer are you using is it still 0.1.21 If it is please try 0,2.1, .2 or .3 they will unlock a locked bootloader. Then see what happens.
                            If you still have an issue after that then I'm a bit stumped if the bootloader is still locked or registering as such. All i can think of is reflashing the canonical UT from BQ to see if that fixes it.

                            Edit: Unless your suspicions are correct and the phone had an issue when returned from Bq, especially if it was not your original device. Though not sure why it would be. Unless they flashed a stock item.

                            T 1 Reply Last reply 18 Aug 2019, 11:30 Reply Quote 0
                            • T Offline
                              Tartaros @Lakotaubp
                              last edited by 18 Aug 2019, 11:30

                              @Lakotaubp I'm using the latest version (0.2.25-Beta), as stated above, it works when setting the phone to fastboot mode prior to launching the installer. I'm not sure whether I want to reflash the original UT image with proprietary tools, maybe I will contact bq regarding that issue and see if they can help me with unlocking the bootloader.

                              I'm pretty sure that the device they sent back to me was a new one as the WiFi and Bluetooth MAC adresses didn't match the ones of the device I sent to them initially. It really seems like they flashed a stock item and locked the bootloader afterwards, maybe with a newer firmware or bootloader version that is not unlockable in the same way as the original devices.

                              L 1 Reply Last reply 18 Aug 2019, 12:26 Reply Quote 0
                              • L Offline
                                Lakotaubp @Tartaros
                                last edited by 18 Aug 2019, 12:26

                                @Tartaros Must be worth getting in touch. One last thing would be to try a live usb stick with Ubuntu 15.04 on it to run the installer.

                                1 Reply Last reply Reply Quote 0
                                • L Offline
                                  Luksus
                                  last edited by Luksus 9 Jun 2019, 18:37 6 Sept 2019, 18:36

                                  Hi,

                                  I got the exact same issue like @Tartaros , with my BQ e4.5.
                                  I am on Manjaro too. But I have flashed ubports with it before...

                                  I also flashed the original old android, then flashed old canonical image and tried again, with exact same result.

                                  But now as I write, I remember that I got this "oem locked" message for FP2 too, which is already on latest ubports RC.

                                  So it seems to be definitly an issue with Manjaro... or the fastboot package of Manjaro...

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

                                  1 Reply Last reply Reply Quote 0
                                  • L Offline
                                    Luksus
                                    last edited by 6 Sept 2019, 18:46

                                    Okay.
                                    I can confirm that the problem is the android-tools package of manjaro-community package.
                                    I uninstalled it, and installed the android-sdk-platform-tools AUR-package.

                                    Now it works, although I am not shure, if the installer is using the AUR package or if it is using it's own tools?!

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

                                    T 1 Reply Last reply 7 Sept 2019, 09:54 Reply Quote 1
                                    • T Offline
                                      Tartaros @Luksus
                                      last edited by 7 Sept 2019, 09:54

                                      @Luksus Thank you for the info! As soon as I find time to, I will try this too!

                                      1 Reply Last reply Reply Quote 0
                                      • M Offline
                                        maxinova2001 @Tartaros
                                        last edited by maxinova2001 9 Aug 2019, 15:10 8 Sept 2019, 15:06

                                        @Tartaros said in bq Aquaris E5 HD Ubuntu Edition wants to be OEM unlocked during installation:

                                        @Lakotaubp I expect I need to switch the device to fastboot mode prior to performing the OEM unlock? I will try it tomorrow.

                                        In theory yes, snaps can be run with Manjaro, but the snap support is still experimental and I do not want a snap error to make my phone a pricy paperweight.

                                        You can try the appimage it works well.
                                        I just tried today the snap installer since the aur package was giving me the same error as yours and it worked flawlessly.

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