Skip to content

Instantly share code, notes, and snippets.

@corna
Last active January 21, 2022 02:09
Show Gist options
  • Star 3 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save corna/d637a7c3279f41e9be65b43b673d54d3 to your computer and use it in GitHub Desktop.
Save corna/d637a7c3279f41e9be65b43b673d54d3 to your computer and use it in GitHub Desktop.
Output of intelmetool on a Thinkpad X220T with coreboot and me_cleaner
❯ sudo ./intelmetool -s
Bad news, you have a `QM67 Express Chipset Family LPC Controller` so you have ME hardware on board and you can't control or disable it, continuing...
MEI was hidden on PCI, now unlocked
MEI found: [8086:1c3a] 6 Series/C200 Series Chipset Family MEI Controller #1
ME Status : 0x1e003052
ME Status 2 : 0x16320172
ME: FW Partition Table : OK
ME: Bringup Loader Failure : NO
ME: Firmware Init Complete : NO
ME: Manufacturing Mode : YES
ME: Boot Options Present : NO
ME: Update In Progress : NO
ME: Current Working State : Recovery
ME: Current Operation State : M0 with UMA
ME: Current Operation Mode : Normal
ME: Error Code : Image Failure
ME: Progress Phase : BUP Phase
ME: Power Management Event : Pseudo-global reset
ME: Progress Phase State : M0 kernel load
ME: Extend SHA-256: 4e84181ebfd078b12ba58d8811007b7eeefa420b40e59b4a46d82f86922a0a06
ME: has a broken implementation on your board with this BIOS
ME: failed to become ready
ME: failed to become ready
ME: GET FW VERSION message failed
ME: failed to become ready
ME: failed to become ready
ME: GET FWCAPS message failed
Re-hiding MEI device...done
@ilikenwf
Copy link

ilikenwf commented Sep 23, 2017

@corna

To mod Aptio bios, you first have to remove it from the Aptio encapsulation using UEFItool to extract it (http://www.win-raid.com/t455f16-Guide-How-to-flash-a-modded-ASUS-ASRock-Gigabyte-AMI-UEFI-BIOS.html)

Otherwise, in regard to the ME, the trick is to use AMIBCP (4 for Aptio IV 5 for aptio V)to toggle an option to on under the flash options for these ASRock boards that forces an ME update on flashing. I also put a slightly newer ME version image in the bios using the intel tools (http://www.win-raid.com/t596f39-Intel-Management-Engine-Drivers-Firmware-amp-System-Tools.html) and toggled some other options to allow flashrom to work later too, all before stripping.

I also used UBU to update the microcode.

Once done modding the image, you need to flash an old version of the bios first, prior to the modded image's version. Then flash your modded version twice. The first time will get it installed, the second will trigger the ME image re-flash.

MEI was hidden on PCI, now unlocked
MEI found: [8086:8cba] 9 Series Chipset Family ME Interface #1

ME Status   : 0x1e020191
ME Status 2 : 0x164d2142

ME: FW Partition Table      : OK
ME: Bringup Loader Failure  : NO
ME: Firmware Init Complete  : NO
ME: Manufacturing Mode      : YES
ME: Boot Options Present    : NO
ME: Update In Progress      : NO
ME: Current Working State   : Initializing
ME: Current Operation State : Bring up
ME: Current Operation Mode  : Debug
ME: Error Code              : No Error
ME: Progress Phase          : BUP Phase
ME: Power Management Event  : Pseudo-global reset
ME: Progress Phase State    : 0x4d

ME: Extend SHA-256: a8e0f5e1bf5388d5721b6458f356cbdc731d15159cd923ccf40aafa779320157

ME: failed to become ready
ME: failed to become ready
ME: GET FW VERSION message failed
ME: failed to become ready
ME: failed to become ready
ME: GET FWCAPS message failed
Re-hiding MEI device...done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment