FP6 stuck in bootloader after install

No need to apologise. I started to write Eos Web Installer Support improvements when I read of people launching into flashing their brand new phones as if it was dead easy and needs zero preparatory understanding.

Now you are oversaturated with information. I recommend to sleep on it. I find myself repeating myself but I do understand that the links I have given you are not dead easy reading.

Good that you have come to this conclusion regarding dates on your own.

However get_unlock_ability=0 tells us something other than the proper install instruction has happened (yes, of course, eosinstaller installer did something and you recovered the phone). No harm done … except

User experience tells us that if you install and lock in one flow then one will see get_unlock_ability=1 – what is the difference, does it matter? You would like “define”. [1]

I completely empathise with your predicament, but I would only aim to try to point you towards “minimum risk reading material”.

Is something different and of no concern today. :slight_smile:

[1] Locking has to ensure full device integrity. Say that integrity cannot be confirmed one might expect locking to fail with error. It is however complicated by lock being a two stage command.

1 Like