I just realized that it could be also because of the changes I've made
(in Mesa driver side) .. however since I don't have way to capture or
see the log I'm not sure if this would be the case. Usually I can see
the Android boot logo even if surfaceflinger is not able to start but
now it simply stucks in the very first screen displaying Intel logo and
bunch of red errors from bootloader.
In any case, it would be helpful if someone can confirm that 'flashing
lock' can be safely removed.
On 3/8/19 1:48 PM, Tapani Pälli wrote:
I'm building Celadon for development purposes. I'd like to 'unlock' the
device and so far I've been removing 'flashing lock' from installer.cmd
script to achieve this. However, now I noticed this does not work
anymore. If I remove 'flashing lock' line, the device won't boot at all.
Is this a bug somewhere or is there another way to unlock?