Installing e/OS on my new FP6 was a bit of a bumpy ride as it got stuck on the fastboot screen after I installed the OS with the installer. I finally got it to work by installing the latest version via the Command Line.
My question is now if it is safe to close to bootloader after this rather unconventional way to install the OS. I do not want to “brick” the device I just bought.
Thanks for the help!
This is a complete reinstall of system so any previous errors are expected overwritten.
- (A study of eosinstaller threads show many examples of installer errors overcome by CLI manual install, many such users go on to report successful relocking.)
Relocking depends on observation of the “rules” on install page to avoid the anti-rollback hazard.
When you lock and the device won’t boot then you have the mentioned antirollback problem. Then you could unlock the bootloader again and it shoul boot again.
Waiting for a newer security patch is the the solution, with 3.2 it might be lockable again.
That sound like a reasonable idea, thanks. 