Page 5 of 12
#61 RE: Intel Engine: Firmware Repositories by NSAfarm 10.04.2017 03:39

avatar

Here is 4.2.60.1060_AMT_PRD_RGN.bin
https://mega.nz/#!RzoXBITI!yAWUD_zY0mU9f...OtPm-TnW77rCQxs

I cleaned it per the guide.

#62 RE: Intel Engine: Firmware Repositories by plutomaniac 10.04.2017 14:00

avatar

SPI/ME dumps and those that get exported by the cleanup guide should always be reported as EXTR. Was the original dump also shown as RGN when viewed in MEA? If yes, please upload the dumped ME region as well to see if I can tweak MEA a little bit to detect it properly.

#63 RE: Intel Engine: Firmware Repositories by NSAfarm 10.04.2017 17:29

avatar

Yep, shows up as RGN. Here is the full one with all data.


https://mega.nz/#!A6QHwIQa!NXRNkXXzVK6JD...L2hIrS4Lvz3uptQ

#64 RE: Intel Engine: Firmware Repositories by plutomaniac 10.04.2017 17:37

avatar

Now that I think about it, you can't have performed the cleanup guide with a clean/RGN 4.2.60 because we don't have such firmware. The last ME4 AMT RGN we have at the repositories which can be used at the cleanup guide is 4.2.10.1023. In fact, the only difference between the two previous uploads are some useless extra padding at the end of the region, nothing else. I do need to improve the EXTR detection of ME4 firmware at MEA but other than that, in order for you to perform the cleanup guide you need to use 4.2.10.1023_AMT_PRD_RGN and then update manually via FWUpdate.

#65 RE: Intel Engine: Firmware Repositories by NSAfarm 10.04.2017 22:11

avatar

I downloaded the latest RGN, ran the update and then downloaded the ME firmware. Then I did the cleanup guide to remove the "data" settings. So did it not work?

#66 RE: Intel Engine: Firmware Repositories by plutomaniac 11.04.2017 04:46

avatar

You said "downloaded the RGN and run the update". I assume you mean FWUpdate. Thing is, you cannot use RGN/EXTR firmware at FWUpdate v4, only Update (UPD) images which are not the same. So you must have updated the ME of your SPI chip via FWUpdate to 4.2.60 by flashing the UPD image. So now you have a dirty/dumped (EXTR) 4.2.60 ME region. At step 4 of the cleanup guide you need to select an RGN, how did you do that if we don't have the RGN of 4.2.60? That's what I'm asking as it's not possible to clean a 4.2.60 EXTR dump. The only possible thing to do is to take the dumped 4.2.60 EXTR and clean it with 4.2.10 (or whatever the latest AMT_RGN is). That way you flash back the cleaned+configured 4.2.10 which you can then update via FWUpdate if you like to 4.2.60 using the UPD image. If at that point you dump the ME region, that is not considered "clean" as the system run at least once between flashing and dumping.

#67 RE: Intel Engine: Firmware Repositories by NSAfarm 11.04.2017 05:09

avatar

I kinda see what you're saying in that its not a fresh RGN. I was going by what MEA said and file size.


I took the latest RGN dump (4.2.10.1023) and replaced the FF filled ME region via FPT. Then I used FW update to flash 4.2.60 as you said. Following that I backup the ME region fully with FPT again (~2.3MB) and then put it through intel flash tool to strip the settings/nvars/etc. It comes out the same size as an RGN file and MEA recognized it as such. Before the larger dump was recognized as extracted.

#68 RE: Intel Engine: Firmware Repositories by plutomaniac 11.04.2017 16:01

avatar

First things first, ignore MEA until it is fixed to properly detect your dumped firmware as EXTR and not RGN. I don't understand the first sentence about your dump being 4.2.10 (thought it was 4.2.60) and those FF replacements? I must be missing something, was your ME region filled with padding for some reason? Since this has become way more confusing than it should be, I'll build a hypothesis and the steps that define it:

1) Your system currently has firmware 4.2.60 either from the manufacturer or because you used FWUpdate some time in the past.
2) For some reason you want to follow the ME cleanup guide, which does not "remove/strip" settings but transfers them after cleaning "dirt" (read Section A)
3) You dump your current SPI image with the dirty 4.2.60 ME region (EXTR, ignore MEA showing it as RGN)
4) You follow the cleanup guide and at step 4 you need to pick the closest RGN firmware from the repository
5) Since we don't have the RGN for your SKU and version (AMT, 4.2.60) you must pick the closest which is 4.2.10
6) The output of the guide produces a new SPI image based on your dump but with cleaned+configured 4.2.10 ME region
7) Flash that new SPI image back and now you have a system with a healthy 4.2.10 ME region
8) If you want to update to 4.2.60 you can use FWUpdate with the 4.2.60 UPD image from ME thread
9) Now your system has a healthy 4.2.60 ME region

To make some things clear:

a) ME firmware can be Regions (RGN/EXTR) or Update (UPD) images
b) RGN are stock/unconfigured regions from Intel, must be configured first for use at systems
c) EXTR are dirty/configured regions extracted from working systems
d) UPD are partial "Regions" meant for FWUpdate use only, no settings stored there
e) Any dumps from working systems include Extracted (EXTR) ME regions, never RGN
f) The cleanup guide does not convert EXTR to RGN. EXTR configuration is transfered to a clean (RGN) which lacks any dirt/initialization data

#69 RE: Intel Engine: Firmware Repositories by NSAfarm 11.04.2017 16:29

avatar

My region was filled with padding, thats why fitcv4 was crashing on the backup. Me was disabled. So you're right, the dump should be EXTR.

#70 RE: Intel Engine: Firmware Repositories by e.v.o 12.04.2017 15:41

avatar

Zitat von plutomaniac im Beitrag #125
To make some things clear:

a) ME firmware can be Regions (RGN/EXTR) or Update (UPD) images
b) RGN are stock/unconfigured regions from Intel, must be configured first for use at systems
c) EXTR are dirty/configured regions extracted from working systems
d) UPD are partial "Regions" meant for FWUpdate use only, no settings stored there
e) Any dumps from working systems include Extracted (EXTR) ME regions, never RGN
f) The cleanup guide does not convert EXTR to RGN. EXTR configuration is transfered to a clean (RGN) which lacks any dirt/initialization data


Could this also be added to the start posting or to the ME FW Tools thread?

#71 RE: Intel Management & Trusted Execution Engine: Firmware Repository by Sergioz 03.05.2017 12:02

Hi. This is my first post here. Yesterday I encountered one of the rarest ME versions never seen before (by myself). It comes from Apple Macbook Pro 13 with two Thunderbolt 3 ports (USB-C). Computer was sold in Jan 2017. Sorry if I'm offtopic here but I'm really lost at this point as where I can get a clean ME for this system. I searched the web and there's no such version out there. At least, I found nothing. The version is 11.0.12.1010. I can post extract here if you want to. It's not clean, obviously but maybe someone wants to have it. Interestingly the size is 1.2MB unlike other ME supplied with Apple laptops. Anyone knows anything about this version?

#72 RE: Intel Management & Trusted Execution Engine: Firmware Repository by plutomaniac 03.05.2017 14:44

avatar

@Sergioz

Hello and thank you for your report. The firmware I have found from Apple machines are 11.0.3.1000 and 11.0.12.1002 but not 11.0.12.1010. So please upload your dump for me to keep that firmware, even if it's not clean.

Zitat von Sergioz im Beitrag #128
[...] where I can get a clean ME for this system. [..]

That depends. In the past, Apple was using their own ME SKUs for their mobile systems (1.5MB, 5MB, 1.5MB Apple) but I don't know if the same applies to their SKL (ME 11.x) based systems. Finding Macbook users who can help figuring such things out is unfortunately very rare. Back to my "it depends" statement:

If Apple is using a custom ME 11.x SKU then you can only update to latter versions of the same SKU via FWUpdate (11.0.3.1000 --> 11.0.12.1002 --> 11.0.12.1010) and the firmware cannot be cleaned as seen at the cleanup guide because we lack equivalent RGN variants which we will not find because only Apple has them. In such case, one can take their official UEFI updates, extract the EXTR ME region from within (should hopefully be Configured only, not Configured+Initialized - read section A of cleanup guide) and use that as a "clean" firmware for reflash.

If Apple is not using a custom ME 11.x SKU then you can take any latter RGN from the repository and follow the cleanup guide.

To test if Apple is using a different SKU, you can try updating to a normal ME 11.0 firmware via FWUpdate and see if it works. However, make sure you can recover from bad flashes in such case via a programmer.

#73 RE: Intel Management & Trusted Execution Engine: Firmware Repository by Sergioz 03.05.2017 16:25

@plutomaniac Hi. Thanks for such a detailed answer. I removed the serial, and locks from the dump. Otherwise it's completely working and verified dump for the following model: MBP 13 i5 2.0 Late-2016 Retina without touch bar. I flashed it successfully and it works 100%. I'd prefer you to have the whole thing, so you can extract other data whether you need it. Let me know if this works for you. Feel free to delete the attachment once you finished working with it.

#74 RE: Intel Management & Trusted Execution Engine: Firmware Repository by tojoski 03.05.2017 16:32

Can someone point me in the general direction of what SPS image I will need for this:

#75 RE: Intel Management & Trusted Execution Engine: Firmware Repository by plutomaniac 03.05.2017 17:04

avatar

@ Sergioz:

Thank you very much. Indeed posting the whole SPI image was a good idea, there was also an older CPU microcode which we didn't have at the database, aside from the ME firmware. I've now added the latter to ME Analyzer. If you can recover from bad flashes and want to try if updating to newer 11.0 firmware works (to do the cleanup guide in such case) then you can follow the steps above (under Windows though). Otherwise, I thank you again for your help.

@ tojoski:

For what purpose do you need a different SPS firmware? I don't know what you need exactly, I was never able to understand how the SPS versioning works. It's not linear like ME and TXE firmware and also we don't have any SPS 2 tools to work with. It's one of the reasons as to why MEA does not support SPS firmware anymore.

Xobor Forum Software von Xobor
Datenschutz