Zitat von plutomaniac im Beitrag #3074

---

@ myDNA:

Update to the latest 11.6 firmware. Read the first post to understand whether the vulnerability even applies to your case.

---

Zitat von myDNA im Beitrag #3097

---

Is there a special reason why I should downgrade[?] to the latest ME firmware v11.6 when I already have v11.7.0.1229? Does it have something to do with why I can no longer find v11.7.0.1229 on page 1 but a placeholder instead? [unless I am mistaken I am certain that I downloaded ME firmware v11.7.0.1229 update that I used to update my system, from page 1 a few months ago? why is there only a placeholder for it now?]

I've read all of page 1 but I can not decipher anything meaningful that would shed some light on these particular questions. Anything to help me understand this, would be very appreciated. TIA for any help and for your patience.

---

Zitat von wasisdn im Beitrag #3098

---

read this post from plutomaniac:
Intel Management Engine: Drivers, Firmware & System Tools (204)

---

@The Engineer
Did you manage to enable that hidden Me FW re-flash option?

@ Ferrous

I've tried your method but nothing hidden appeared.
here are my computer specs.

@The Engineer
You have to access them with this guide.
To enable the Me FW Image Re-Flash use

setup_var 0x226 0x1
 

.
After reboot, you will be able to reflash ME Region.

Hi all, I am new to this excellent forum. Alt-P or RShift RCtrl LAlt F2 wasn't working either on my Asrock H77Pro4-M board.
An external programmed BIOS ME update is "featured" to be rolled back on next reboot by the same BIOS. Even when BIOS ME version is higher than original ME. Shame you Asrock.
After cleaning the Intel ME from BIOS using the excellent tool by Nicola Corna and a reboot, BIOS powers down and up, then throws a screen "INTEL ME UPDATE" w/ user uninterruptible progress bar. Thus I ended up with the same old uncleaned ME.

I could temporarily stop reflashing by putting the BIOS chip on HOLD. Unfortunately, the program just waits the flashing to be finished... To circumvent the reflashing behavior completely, user Lordkag already found a nice assembly mod. Being a relatively noob on assembly, I found a nice and simple solution using the nifty UEFI Tool and an external programmer:

GUID 8F5C2D02-[...]
 

GUID 5820EEB4-[...]
 

Zitat von plutomaniac im Beitrag #3101

---

@ ilario:

What don't you understand from the first post exactly? Have you read it carefully?

---

Intel(R) MEManuf Version: 11.6.29.3287
Copyright(C) 2005 - 2017, Intel Corporation. All rights reserved.
 

Windows OS Version : 10.0
 
FW Status Register1: 0x90000245
FW Status Register2: 0x00F60506
FW Status Register3: 0x00000200
FW Status Register4: 0x00084400
FW Status Register5: 0x00000000
FW Status Register6: 0x40000000
 
  CurrentState:                               Normal
  ManufacturingMode:                          Disabled
  FlashPartition:                             Valid
  OperationalState:                           CM0 with UMA
  InitComplete:                               Complete
  BUPLoadState:                               Success
  ErrorCode:                                  No Error
  ModeOfOperation:                            Normal
  SPI Flash Log:                              Not Present
  Phase:                                      ROM/Preboot
  ICC:                                        Valid OEM data, ICC programmed
  ME File System Corrupted:                   No
  PhaseStatus:                                AFTER_SRAM_INIT
  FPF and ME Config Status:                   Match
 
FW Capabilities value is 0x31111A40
Feature enablement is 0x31111A40
Platform type is 0x41110321
No Intel Wireless device was found
Feature enablement is 0x31111A40
ME initialization state valid
ME operation mode valid
Current operation state valid
ME error state valid
OEM ICC data valid and programmed correctly
MFS is not corrupted
PCH SKU Emulation is correct
FPF and ME Config values matched
 
Request Intel(R) ME BIST status command... done
 
Get Intel(R) ME test data command... done
 
Warning 463: A test returned from FW does not match known test by the tool: App(34) Comp(0) Test(2)
 
Get Intel(R) ME test data command... done
Total of 11 Intel(R) ME test result retrieved
 

Policy Kernel - Boot Guard : Self Test - Passed
Policy Kernel - Embedded Controller : Power source type - Passed
MCA - MCA Tests : Blob - Passed
MCA - MCA Tests : MCA Manuf - Passed
SMBus - SMBus : Read byte - Passed
VDM - General : VDM engine - Passed
Policy Kernel - ME Configuration : PROC_MISSING - Passed
Unknown App(34) - Unknown Comp(0) : Unknown Test(2) - Passed
 
Clear Intel(R) ME test data command... done
 

 

MEManuf Operation Passed (with warnings)
 

@ plutomaniac:

Sorry for the delay. The laptop in question is not my own. I work for a small business and address all of our internal IT needs. I confess that I failed to check the BIOS version before attempting to flash it. Based on the purchase date and information dialog box that pops up when running the BIOS .exe file from within Windows (see attached image), my best guess is that it was A00. As far as problems, the laptop has never performed as fast as I expected it to based on the hardware configuration, but I am not aware of any specific problems. I did not run MEInfo or MEManuf prior to experiencing the problem.

I do agree that the reboot issue could be associated with the battery losing connection. After using it for a week, the User of this laptop states that the main issue he is experiencing is that there is no video shown on the laptop screen when he opens it after he undocks it (black screen). The only way to recover is to reboot. I have done some searching and it seems that the main solution is to flash the BIOS to the latest version. As you know, I cannot do that successfully.

I removed the cord + battery for 1 minute, then re-ran MEInfo and MEManuf. No change. I got the same errors.

FYI, I also attempted to flash all 9 available versions of the BIOS without success (same error).

Can you offer any other solutions?

Thanks! Updated from Intel ME 11.6 Consumer PCH-LP Firmware v11.6.29.3287 ->> TO->>Intel ME 11.7 Consumer PCH-LP Firmware v11.7.0.3290
My system : 100-series SKL-U , i7-6500U (mobile)

MEInfo Output:

@ plutomaniac:

When I ran fptw -d spi.bin, I got "Error 26: The host CPU does not have read access to the target flash area. To enable read access for this operation you must modify the descriptor settings to give host access to this region". I don't have any experience with EFI Shell and there was not an option for that in the BIOS. After some research, I was able find a shellx64.efi binary file and boot to a Shell> prompt from a USB drive. However, when I ran command setup_var 0x2D4 0x1, it gave me "'setup_var' is not recognized as an internal or external command, operable program, or batch file."

What am I doing wrong?

@Ferrous

Actually I don't know what is this, I think there is another method but I'm afraid to try it without asking you.
I intend to use AMI Firmware Update Utility in efi mode using this command

AfuEfix64.efi E1762IMS.70X /me /meuf

I got the idea from this link
http://www.msi-bios.com/msi-bios-flash-utility-id-15.html

but I don't understand "- /ME command fail - When BIOS support MER commands." written in the "What's new:" section