<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Where did the binary come from? In distro version? It's really
recommended to use a ChromeOS version of Flashrom to flash
Chromebooks - makes things easier.<br>
</p>
<p>Yes, it is well known that the ME can interfere with its being
overwritten amongst other things. :)</p>
<p><a class="moz-txt-link-freetext" href="https://www.flashrom.org/ME">https://www.flashrom.org/ME</a><br>
</p>
<br>
<div class="moz-cite-prefix">On 25/05/17 00:34, Alejandro Flores
wrote:<br>
</div>
<blockquote
cite="mid:CAK9N+2FMFfPY4QNnMk5PKPBEVWhoMbRX2scpwnbWX71hut196g@mail.gmail.com"
type="cite">
<div dir="auto">
<div>
<div class="gmail_extra">Problem is solved. I was using an old
precompiled version of flashrom to write the bios. When I
compiled a new binary from latest source it gave an error
when I tried to write the rom.</div>
</div>
<div class="gmail_extra" dir="auto"><br>
</div>
<div class="gmail_extra" dir="auto">It said it would be unable
to write to ME since the ME is currently active and in use.
The old binary hadn't given any error and presumably tried to
write to ME and failed silently leaving some mix of new and
old that failed signature verification. </div>
<div class="gmail_extra" dir="auto"><br>
</div>
<div class="gmail_extra" dir="auto">I confirmed this by using a
hardware writer to verify first that the rom on chip is not
the rom I intended to write and then writng the correct rom.</div>
<div class="gmail_extra" dir="auto"><br>
</div>
<div class="gmail_extra" dir="auto">ME now works as expected. I
wonder though if this is expected behavior to be unable to
flash the ME from a running system or if it is just my model
of laptop?</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</body>
</html>