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

Lakotaubp · 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

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.

Lakotaubp · 17 Aug 2019, 15:06

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

Tartaros · 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.

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.

Tartaros · 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.

Lakotaubp · 18 Aug 2019, 09:10

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

Tartaros · 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).

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.

Tartaros · 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.

Lakotaubp · 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.

Luksus · 9 Jun 2019, 18:37

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...

Luksus · 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?!

Tartaros · 7 Sept 2019, 09:54

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

maxinova2001 · 9 Aug 2019, 15:10

@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.