When z330 stitched on Windows did not want to be stitched back, I began to figure out why. Knowledgeable people write about a certain QFPROM.
Roughly speaking, while he is not involved - you can sew anything. But if QFPROM is in the firmware, it will be blocked by itself. They say that almost physically something burns out at the same time.
QFPROM, QFUSE is all from there.
When I stumbled upon the unavailable on m330 firmware, signed as no-fused, I assumed that this was what we needed.
In the instruction for flashing z330 in the W10M offered to make them as desirable.
And for a person who has flashed his fresh z330 with this firmware, it did not fall off into the com-port, as it happens with the devices that have already worked on Windows, but tried to launch itself (cyclic reboot on the acer screensaver).
After which he simply flashed the android back, and he successfully got up.
Therefore, it is considered that it is returned.
Alas, no one understood before me how to run that firmware ...
And I, having sewn it, first of all found the BDS menu and Developer Menu in it. After cleaning all the variables in both menus, the firmware started.
The main thing is not to change it for anything later ... Except back to the android.
Posted 05/05/2019 08:20: abc145 The secure boot is turned off there initially. But all sorts of settings gives.
Yes, there is nothing more to look for here .. What was - found. What is not found - the Chinese have deleted a long time ...