According to this post by @Manoj , the bootloader on the T2e first batch cannot be re-locked after flashing to /e/. However, this has been some time ago and Since then the upgrade problem of the first batch of T2e has been solved by a manual upgrade from 1.0 to 1.5. Updating via OTA is working for these devices smoothly (at least for me) ever since, the same way as for the emerald. The instructions for re-locking the bootloader for the emerald seem general enough (to the uninitiated) to be executed on the 2e as well (except for the “before rebooting” part, but maybe that’s not necessary), so my question is:
Can the Teracube2e’s (running 1.8) bootloader be now re-locked with these instructions?
I personally find the message “Orange state…” VERY annoying… it always gives me the feeling that something is wrong with the device. And of course (and with the same token), if the target audience of /e/ is the general public, then it should not be happening.
Some more details about this relocking issue and (possible) security issue therein are at Teracube 2e Orange State at Reboot.