Quote:
Originally Posted by sclause
- - - -
Have you ever had this problem?
Thx.
SClause
|
Yes - it has been seen before.
Something in the parts of the firmware that is not (normally) touched by Kubrick.
Does your fastboot utility have a way to get the firmware (u-boot/bist aka fastboot) version number?
You may have a version that has a bug in the mode set command.