Analysis:
I tried once again to derive unlock key with my IMEI – and got the same key
which worked when unlocking the device.
So, there is no “time window” or (ecdsa verify style) “nonce” when generating
the key (which would made it impossible to know whether the given input was
incorrect in the first time)
The probable reason is that I failed to get all keypresses through when entering key (and failed to verify that the IMEI was correct in Sony’s web page (*))
– Sony’s web page highlighted [Submit] button one before the last digit so I
thought it was complete (probable reason – some IMEI keys are shorter ?)
So, in case one gets this “remote: Command did not succeed” one (of not the only)
reason is that mismatching unlock key was entered. (*) The best option to prevent
this happening is to take picture of the screen showing unlock key (and copy-pasting the key along the IMEI) – both IMEI and unlock key are shown there.
Then one can verify that the given IMEI was correct. Alternative (i.e. what I did
after a week) is to retry unlock key derivation in Sony’s web page to see whether
the unlock key changes this time (if not then something else is to be tried (**))
The good thing this happening to me is that I used Android 12 for a week. Found
its good and bad things. It was very slicky and snappy, but annoying in many places (perhaps when it asked voice commands “inadvertently” (please no!)…).
(**) all in all, w/ correct codes, SFOS installation went smoothly. just that “everything in computer science” is “exact science”, so any bit not exacty in straight vertical order, can make things break. perhaps tuning documentation
could help (or then not…)
Anyway, thanks for SFOS. 50€ is decent price for the “calmness” it gives me…