Make unlocking more flexible

[NeoTheThird]

Some newer devices don't use fastboot oem unlock, so we need a new config option that's fed into the oem lock error handling. Fun! Other devices require a key such as this: fastboot.exe -i 0x0fce oem unlock 0xKEY.

[robiwan1]

...what about adding unlock code to the "fastboot oem unlock..." command????

[NeoTheThird]

that's exactly what's the idea here.

[robiwan1]

fantastic, i think the fastest and easiest way to implement is, to add a var in config json like this:
"unlock_code": [""],
If unlock_code is empty (default in all config files) - just run "fastboot oem unlock" as before. If there is an unlock_code, run "fastboot oem unlock 0x<unlock_code>"

[robiwan1]

How can i set my unlock code? I did not find any config or input file to pass the code to the fastboot command. I used version 0.8.0...

[NeoTheThird]

@robiwan1 Yes, this is not implemented in the installer yet. Follow the guide in the link that the installer shows you.

[robiwan1]

Sorry for making multible comments at the same matter - i was not sure which post would be the best for asking. I saw this "New unlock features" #53 and thought, this means that it is implemented yet. Specially because i saw code to "accept oem unlock code".

[NeoTheThird]

@robiwan1 sorry for the confusion. the pull request you commented on implemented prerequisites to fix this in our library that handles fastboot. The new library calls will now need to be implemented in the installer. This requires changes to the config specification, as well as changes to the installer's UI and backend code. Working as fast as we can, but it'll be at least another week before it'll be considered stable.

[robiwan1]

@NeoTheThird Thanks for the explanation. I Don't want you being in such a hurry! ;-) I unlocked now from cli with the fastbook-command from appimage (/tmp/.mount....) and the installer finished successfully. BUT now my Sony xpedia x perf. hangs in a boot loop. I have tried system images stable, devel and edge without success...

[robiwan1]

i now stuck exacly in the closed issue #1503...