Why do you need a clean Management Engine Region?

An Apple MacBook will not run properly or not run at all without a proper management engine. When a new Macbook is turned on for the first time the Bios and the CPU perform a "handshake" allowing them to work together. So in turn, if your management engine gets corrupted,, and you try to copy the efi from another macbook of the same model, it will still not work because the cpu knows its not the original bios. 


What are some signs of a of a corrupted Management Engine?

  • Macbook will boot, chime, load the OS, but the WiFi, and/or the graphics will behave irregular.

  • Macbook will boot, chime, but will not load an OS and gets stuck on the loading bar. (This can also be an SMC issue)

  • Macbook will boot, chime, but stays on a black or white screen and doesn't even reach a loading bar.

Now if you have a fried, or completely corrupted bios, the computer won't even attempt to turn on. But there are many reasons a Macbook wouldn't turn on as well, so don't think doing this will magically fix your broken Macbook. 


How do you set a new, clean Management Engine Region?

Well luckily doing this does not actually mean you have to rewrite or change the code, but just copy and paste over the old ME, with a fresh one. Clean ME regions can be found here, in Section B1. You will being downloading a .bin file, and will need something like HxD to open and edit the file. 

Clean Management Engine Regions

You'll need to make sure you download the correct ME region, based on the processor of your logic board. Or you can use this ME Analyzer to tell you what version of ME you need for your EFI. 

ME Analyzer (Once you extract the folder, just drag an drop your .bin file onto the MEA.bat file, a cmd window will open and give you the info.)

Now you will either need to pull your corrupted efi off of the bios on your logic board (using thaGH05T's tutorial) or pull it off of another board with a good EFI. This other board needs to be the exact same model. All Apple Logic boards have an 820-XXXX number stamped on them denoting the model of the board. This can also be found using the mac's serial number. 


Once you have your EFI file(corrupted or from another board) and your clean ME region opened in HxD(or similar)


You can get to this view by going to Analysis tab at the top and then selecting File Compare. 

In the Management Engine file window right click the column on the right and click select all.

Make note of the number at the bottom where it says length. (circled in red)


Copy this selection and head over to your corrupted EFI file, or EFI file from another logic board.

In this window and do a search for "KRID".


You can now see where the Management Engine region starts right in front of the "€.@" above "KRIDA".

We will first left click and put our cursor in the first empty space, left of the € symbol. Now right click and hit "Select Block". 


Hit the Length circle and type in the length of the ME region.

This would be the number that was circled in red in the first picture.

(Please note this number will change from EFI to EFI)


Now all you have to do is right click on the selection  again and click "Paste Write", this will overwrite the old Management Engine with the new clean one.


You can now save the file, and load it back on to your bios chip. Please note that if you using a efi from a different board you will also need to change the serial number. You can find out how to change the serial number in thaGh05t's tutorial. This EFI file is now ready for a first time boot with any Macbook logic board of the same model. 

0 #5 curiousdave 2017-08-01 20:39
FIrst of all the RAW file is not going to work in the firmware and the machine will not bot as usual. The RAW file need to work on the settings with the FIT tool. It is not that easy to dump the file.
The suggestion said blank board serializer to serialise the board is not going to work as the board is not blank.
ME region is the major driver for the machine and there is no easy work for this without knowing what to do. The ghost got no clue about the ME region or firmware other than tried to fix his 2012 Air for 6 months without success.
It take a lot of time and effort to learn about ME region and need the correct tool with file.
The old corrupt file is required to make the firmware works as all the chip ID need to match.
0 #4 D G 2017-05-30 16:49
Please i want to know why you make a search in the corrupted bios with the word KRIDA?
+1 #3 sdfsdf 2016-04-08 05:01
0 #2 Joe 2016-04-08 05:00
This is exactly what I'm looking for! Thanks!

Can you link to the tutorial you meant with pulling the EFI of another board? There are other tutorials on this site but they are for removing the EFI password, I just like to make sure I'm following the right one as this is the first time for me.
-1 #1 KingBonecrusher 2016-03-22 15:29
Nice Article :-)

Some hints. The ME Firmware is the 1.5MB/Consumer, also called Intel Entry Management Engine. There seems to be not enough space to use the 5MB/Corporate Full Management Engine.

Here some Info about the ic contents:

1) FLash Descriptor = 4.096 Bytes
2) OEM Section = 256 Bytes
3) PDR Region = 4.096 Bytes
4) ME Region = 1.544.192 Bytes [ AMT DISABLED ]
5) BIOS Region = 6.750.208 Bytes

That means it should be possible to create a full clean file. I haven`t found any Gbe Region. So where is the mac saved?

1) create 8MB file filled with FF
2) copy Descriptor / ME Firmware / Bios to the correct offsets
3) flash it back
4) use Apple Blank Board Serializer

Don't know if this works, will test it maybe....

Who's Online

We have 405 guests and no members online


  • c12bit
  • Igprokopenko
  • yllovera11
  • yllovera1