Flashing on Windows fails claiming that bootloader not unlocked

Jolla Care -

Sometimes an attempt to use the script Flash-on-Windows.bat may fail and give a misleading error report, like that in the picture below.

 

Windows_cmd_-_not_recognized_as_an_internal_or_external_command.PNG


The conflict with the installation script is related to the error messages in the picture above. The commands 'findstring', 'ping', 'find' etc. are used and needed in the script but in this case, they fail as the Windows command terminal cannot find them. This makes the script misinterpret the situation so that it believes that the bootloader is still locked.

The output from "fastboot getvar all" proves that the bootloader is already unlocked.

We have seen the same previously a couple of times. In those cases, the customer has used the Windows PowerShell (instead of the cmd terminal) which sometimes has some conflicting environment variables defined (for those commands above). It has helped to undefine the variables or to use the cmd terminal. 

In this case, the cmd terminal is already used. The internet contains information about similar cases, also with the cmd terminal. The following page, for instance, seems to discuss a similar issue. It may help you out from the problem, after which the flashing script most probably works.

https://helpdeskgeek.com/how-to/fix-not-recognized-as-an-internal-or-external-command/

Have more questions? Submit a request
Powered by Zendesk