Need help. Big issue after update CSME 12.x

Hello guys :slight_smile: I wanted to uptade CSME firmware on my Aorus x5 v8 laptop (i7 8850H - HM370) but I think I lmake a mistake and I need your help :confused:
I download the latest CSME firmware on the first page (12.0.6.1120 Consumer H), the latest PCM firmware (300.2.11.1014 H B) and I merged both with FIT to make the update with FWUpdate.
The update succeded but after the reboot many issues appears, my sata hdd are no longer detected, my m2 are detected once in ten, screen stuck on OEM logo, bios show 4 memory slots instead of 2, when windows gets to start the battery icon indicates “plugged in, not charging” and many time shutdown alone.
I conclude that the firmware didn’t match with my laptop because of the “firmware type” was “region, stock” but I didn’t care about that :frowning:
The times Windows was able to start, I did a dump of my old FW (12.0.0.1062) and try to merge it with latest PCM on FIT but FIT doesn’t arrives to open my FW file.
Also, I tried to update my old FW (without PCM) but I have an error with SVN are lower and didn’t match altought the same SVN appears on both file with ME Analyser, and I have the same message with another old FW+PCM where the SVN is also the same, only the Version Number Control change.

Reassure me, tell me there is a solution or a possible firmware downgrade who will solve my problem :confused:

Thank you

Hello,

The CSME + PMC combo you picked is correct. Run MEInfo -verbose and show its output. Run Flash Programming Tool with the command “fptw -d spi.bin” and let me know if you see any error. Attach the FWU image you created after first merging CSME 12.0.6.1120 + PMC 300.2.11.1014 H B.

Thank you for your answer :). Here are all the requested informations

Spi.bin + Merged CSME FW/PMC

Meinfo


Intel(R) MEInfo Version: 12.0.6.1120
Copyright(C) 2005 - 2018, Intel Corporation. All rights reserved.



FW Status Register1: 0xA0000255
FW Status Register2: 0x3B850106
FW Status Register3: 0x00000020
FW Status Register4: 0x00004000
FW Status Register5: 0x00000000
FW Status Register6: 0x00400000

CurrentState: Normal
ManufacturingMode: Enabled
FlashPartition: Valid
OperationalState: CM0 with UMA
InitComplete: Complete
BUPLoadState: Success
ErrorCode: No Error
ModeOfOperation: Normal
SPI Flash Log: Not Present
Phase: BringUp
ME File System Corrupted: No
PhaseStatus: UNKNOWN
FPF and ME Config Status: Not committed
FW Capabilities value is 0x31119140
Feature enablement is 0x31119140
Platform type is 0x72000391
No Intel Wireless device was found
Intel(R) ME code versions:


SMBIOS Table Data
SM BIOS Spec Version : 2.8
Starting address: 0x3F1BF000
Table Size in Bytes: 4404 ( 0x1134 )
Number of Table Entries: the 95 ( 0x5F )

Table Type 4 ( 0x 04 ) found, size of 0 (0x 00 ) bytes
BIOS Version FB02

SMBIOS Table Data
SM BIOS Spec Version : 2.8
Starting address: 0x3F1BF000
Table Size in Bytes: 4404 ( 0x1134 )
Number of Table Entries: the 95 ( 0x5F )

Table Type 4 ( 0x 04 ) found, size of 0 (0x 00 ) bytes
Table Type 0 ( 0x 00 ) found, size of 68 (0x 44 ) bytes
Table Type 1 ( 0x 01 ) found, size of 91 (0x 5B ) bytes
Table Type 2 ( 0x 02 ) found, size of 97 (0x 61 ) bytes
Table Type 3 ( 0x 03 ) found, size of 81 (0x 51 ) bytes
Table Type 8 ( 0x 08 ) found, size of 25 (0x 19 ) bytes
Table Type 9 ( 0x 09 ) found, size of 23 (0x 17 ) bytes
Table Type 10 ( 0x 0A ) found, size of 33 (0x 21 ) bytes
Table Type 11 ( 0x 0B ) found, size of 21 (0x 15 ) bytes
Table Type 12 ( 0x 0C ) found, size of 21 (0x 15 ) bytes
Table Type 32 ( 0x 20 ) found, size of 22 (0x 16 ) bytes
Table Type 34 ( 0x 22 ) found, size of 19 (0x 13 ) bytes
Table Type 26 ( 0x 1A ) found, size of 29 (0x 1D ) bytes
Table Type 36 ( 0x 24 ) found, size of 18 (0x 12 ) bytes
Table Type 35 ( 0x 23 ) found, size of 27 (0x 1B ) bytes
Table Type 28 ( 0x 1C ) found, size of 29 (0x 1D ) bytes
Table Type 36 ( 0x 24 ) found, size of 18 (0x 12 ) bytes
Table Type 35 ( 0x 23 ) found, size of 27 (0x 1B ) bytes
Table Type 27 ( 0x 1B ) found, size of 30 (0x 1E ) bytes
Table Type 36 ( 0x 24 ) found, size of 18 (0x 12 ) bytes
Table Type 35 ( 0x 23 ) found, size of 27 (0x 1B ) bytes
Table Type 27 ( 0x 1B ) found, size of 17 (0x 11 ) bytes
Table Type 36 ( 0x 24 ) found, size of 18 (0x 12 ) bytes
Table Type 35 ( 0x 23 ) found, size of 27 (0x 1B ) bytes
Table Type 29 ( 0x 1D ) found, size of 27 (0x 1B ) bytes
Table Type 36 ( 0x 24 ) found, size of 18 (0x 12 ) bytes
Table Type 35 ( 0x 23 ) found, size of 27 (0x 1B ) bytes
Table Type 26 ( 0x 1A ) found, size of 29 (0x 1D ) bytes
Table Type 28 ( 0x 1C ) found, size of 29 (0x 1D ) bytes
Table Type 27 ( 0x 1B ) found, size of 30 (0x 1E ) bytes
Table Type 29 ( 0x 1D ) found, size of 27 (0x 1B ) bytes
Table Type 39 ( 0x 27 ) found, size of 184 (0x B8 ) bytes
Table Type 16 ( 0x 10 ) found, size of 25 (0x 19 ) bytes
Table Type 17 ( 0x 11 ) found, size of 109 (0x 6D ) bytes
Table Type 19 ( 0x 13 ) found, size of 33 (0x 21 ) bytes
Table Type 221 ( 0x DD ) found, size of 98 (0x 62 ) bytes
Table Type 221 ( 0x DD ) found, size of 388 (0x 184 ) bytes
Table Type 221 ( 0x DD ) found, size of 208 (0x D0 ) bytes
Table Type 221 ( 0x DD ) found, size of 32 (0x 20 ) bytes
Table Type 7 ( 0x 07 ) found, size of 29 (0x 1D ) bytes
Table Type 4 ( 0x 04 ) found, size of 185 (0x B9 ) bytes
Table Type 20 ( 0x 14 ) found, size of 37 (0x 25 ) bytes
Table Type 130 ( 0x 82 ) found, size of 22 (0x 16 ) bytes
MEBx Version 12.0.0.0008
GbE Version Unknown
PMC FW Version 300.2.11.1014
Descriptor Version 1.0
Vendor ID 8086
FW Version 12.0.6.1120 H Consumer

PCH Information
PCH Version 10
PCH Device ID A30D
PCH Step Data B1
PCH SKU Type Production Pre-QS Revenue
PCH Replacement Counter 0
PCH Replacement State Disabled
PCH Unlocked State Disabled

FW Capabilities 0x31119140

Protect Audio Video Path - PRESENT/ENABLED
Intel(R) Dynamic Application Loader - PRESENT/ENABLED
Service Advertisement & Discovery - NOT PRESENT
Intel(R) Platform Trust Technology - PRESENT/ENABLED
Persistent RTC and Memory - PRESENT/ENABLED

FW Type Production
TLS Disabled
Last ME reset reason Power up
Local FWUpdate Enabled
BIOS Config Lock Enabled
GbE Config Lock Enabled
Get flash master region access status…done
Host Read Access to ME Enabled
Host Write Access to ME Enabled
Get EC region access status…done
Host Read Access to EC Enabled
Host Write Access to EC Enabled
Protected Range Register Base #0 0x0
Protected Range Register Limit #0 0x0
Protected Range Register Base #1 0x0
Protected Range Register Limit #1 0x0
Protected Range Register Base #2 0x0
Protected Range Register Limit #2 0x0
Protected Range Register Base #3 0x0
Protected Range Register Limit #3 0x0
Protected Range Register Base #4 0x0
Protected Range Register Limit #4 0x0
SPI Flash ID 1 C22018
SPI Flash ID 2 Not Available
BIOS boot State Post Boot
OEM ID 00000000-0000-0000-0000-000000000000
Capability Licensing Service Enabled
OEM Tag 0x00000000
Slot 1 Board Manufacturer 0x00000000
Slot 2 System Assembler 0x00000000
Slot 3 Reserved 0x00000000
M3 Autotest Disabled
C-link Status Disabled
EPID Group ID 0x28AF
Keybox Not Provisioned
Intel(R) PTT Supported Yes
Intel(R) PTT initial power-up state Enabled
PAVP Supported Yes
Integrated Sensor Hub Initial Power State Disabled
End of Manufacturing Enable No
Post Manufacturing NVAR Config Enabled Yes
Minimum Allowed Anti Rollback SVN 1
Image Anti Rollback SVN 4
Trusted Computing Base SVN 1
ACM SVN FPF 0x00
KM SVN FPF 0x00
BSMM SVN FPF 0x00
OEM Public Key Hash FPF Not set
OEM Public Key Hash UEP F731B3F589D6527AF409187D6E4E4D05BBF98E3DD05164E25F0B61EEFF41D7E6
OEM Public Key Hash ME FW F731B3F589D6527AF409187D6E4E4D05BBF98E3DD05164E25F0B61EEFF41D7E6
HW Binding Enabled


FPF UEP ME FW
*In Use
— — -----
Key Manifest ID Not set 0x01 0x01
PTT Not set Enabled Enabled
SPI Boot Source Not set Enabled Enabled
Enforcement Policy Not set 0x00 0x00
OEM ID Not set 0x00 0x00
TXT Supported Disabled Disabled Disabled
OEM Key Manifest Present Not Present Present Present
OEM Platform ID Not set 0x00 0x00
SOC Config Lock Not set Not Done Not Done
Persistent PRTC Backup Power Enabled Enabled Enabled
EK Revoke State Not Revoked Not Revoked Not Revoked
CPU Debugging Not set Enabled Enabled
BSP Initialization Not set Enabled Enabled
Measured Boot Not set Disabled Disabled
Verified Boot Not set Disabled Disabled
Protect BIOS Environment Not set Disabled Disabled


SPI verbose (There was no error during analysis)

FW Status Register1: 0xA0000255
FW Status Register2: 0x3B850106
FW Status Register3: 0x00000020
FW Status Register4: 0x00004000
FW Status Register5: 0x00000000
FW Status Register6: 0x00400000

Initializing SPI utilities
Reading HSFSTS register… Flash Descriptor: Valid

Region Limits as programmed into the SPI Registers
FREG0 - DESC Region:Base Address: 0x000000 Limit : 0x000FFF
FREG1 - BIOS Region:Base Address: 0x800000 Limit : 0xFFFFFF
FREG2 - CSME Region:Base Address: 0x001000 Limit : 0x7FFFFF
FREG3 - GbE Region:Base Address: 0x7FFF000 Limit : 0x000FFF
FREG4 - PDR Region:Base Address: 0x7FFF000 Limit : 0x000FFF
FREG5 - Region:Base Address: 0x7FFF000 Limit : 0x000FFF
FREG6 - Region:Base Address: 0x7FFF000 Limit : 0x000FFF
FREG7 - Region:Base Address: 0x7FFF000 Limit : 0x000FFF
FREG8 - EC Region:Base Address: 0x7FFF000 Limit : 0x000FFF
FREG9 - Region:Base Address: 0x7FFF000 Limit : 0x000FFF
FREG10 - Region:Base Address: 0x7FFF000 Limit : 0x000FFF
FREG11 - Region:Base Address: 0x7FFF000 Limit : 0x000FFF
FREG12 - Region:Base Address: 0x7FFF000 Limit : 0x000FFF
FREG13 - Region:Base Address: 0x7FFF000 Limit : 0x000FFF
FREG14 - Region:Base Address: 0x7FFF000 Limit : 0x000FFF
FREG15 - Region:Base Address: 0x7FFF000 Limit : 0x000FFF
Address Limit 0x1000000 Maximum Memory 16384kB


— Flash Devices Found —
MX25L12875F ID:0xC22018 Size: 16384KB (131072Kb)

Using hardware sequencing.
Reading region information from flash descriptor.
Base: 0x00000000, Limit: 0x00000FFF
Base: 0x00800000, Limit: 0x00FFFFFF
Base: 0x00001000, Limit: 0x007FFFFF
DumpFlashToFile (spi.bin, 0x0, 0x0)…

- Reading Flash [0x0000040] 0KB of 16384KB - 0 percent complete.
- Reading Flash [0x0028F80] 163KB of 16384KB - 1 percent complete.
- Reading Flash [0x0051EC0] 327KB of 16384KB - 2 percent complete.
- Reading Flash [0x007AE40] 491KB of 16384KB - 3 percent complete.
- Reading Flash [0x00A3D80] 655KB of 16384KB - 4 percent complete.
- Reading Flash [0x00CCD00] 819KB of 16384KB - 5 percent complete.
- Reading Flash [0x00F5C40] 983KB of 16384KB - 6 percent complete.
- Reading Flash [0x011EBC0] 1146KB of 16384KB - 7 percent complete.
- Reading Flash [0x0147B00] 1310KB of 16384KB - 8 percent complete.
- Reading Flash [0x0170A40] 1474KB of 16384KB - 9 percent complete.
- Reading Flash [0x01999C0] 1638KB of 16384KB - 10 percent complete.
- Reading Flash [0x01C2900] 1802KB of 16384KB - 11 percent complete.
- Reading Flash [0x01EB880] 1966KB of 16384KB - 12 percent complete.
- Reading Flash [0x02147C0] 2129KB of 16384KB - 13 percent complete.
- Reading Flash [0x023D740] 2293KB of 16384KB - 14 percent complete.
- Reading Flash [0x0266680] 2457KB of 16384KB - 15 percent complete.
- Reading Flash [0x028F600] 2621KB of 16384KB - 16 percent complete.
- Reading Flash [0x02B8540] 2785KB of 16384KB - 17 percent complete.
- Reading Flash [0x02E1480] 2949KB of 16384KB - 18 percent complete.
- Reading Flash [0x030A400] 3113KB of 16384KB - 19 percent complete.
- Reading Flash [0x0333340] 3276KB of 16384KB - 20 percent complete.
- Reading Flash [0x035C2C0] 3440KB of 16384KB - 21 percent complete.
- Reading Flash [0x0385200] 3604KB of 16384KB - 22 percent complete.
- Reading Flash [0x03AE180] 3768KB of 16384KB - 23 percent complete.
- Reading Flash [0x03D70C0] 3932KB of 16384KB - 24 percent complete.
- Reading Flash [0x0400000] 4096KB of 16384KB - 25 percent complete.
- Reading Flash [0x0428F80] 4259KB of 16384KB - 26 percent complete.
- Reading Flash [0x0451EC0] 4423KB of 16384KB - 27 percent complete.
- Reading Flash [0x047AE40] 4587KB of 16384KB - 28 percent complete.
- Reading Flash [0x04A3D80] 4751KB of 16384KB - 29 percent complete.
- Reading Flash [0x04CCD00] 4915KB of 16384KB - 30 percent complete.
- Reading Flash [0x04F5C40] 5079KB of 16384KB - 31 percent complete.
- Reading Flash [0x051EBC0] 5242KB of 16384KB - 32 percent complete.
- Reading Flash [0x0547B00] 5406KB of 16384KB - 33 percent complete.
- Reading Flash [0x0570A40] 5570KB of 16384KB - 34 percent complete.
- Reading Flash [0x05999C0] 5734KB of 16384KB - 35 percent complete.
- Reading Flash [0x05C2900] 5898KB of 16384KB - 36 percent complete.
- Reading Flash [0x05EB880] 6062KB of 16384KB - 37 percent complete.
- Reading Flash [0x06147C0] 6225KB of 16384KB - 38 percent complete.
- Reading Flash [0x063D740] 6389KB of 16384KB - 39 percent complete.
- Reading Flash [0x0666680] 6553KB of 16384KB - 40 percent complete.
- Reading Flash [0x068F600] 6717KB of 16384KB - 41 percent complete.
- Reading Flash [0x06B8540] 6881KB of 16384KB - 42 percent complete.
- Reading Flash [0x06E1480] 7045KB of 16384KB - 43 percent complete.
- Reading Flash [0x070A400] 7209KB of 16384KB - 44 percent complete.
- Reading Flash [0x0733340] 7372KB of 16384KB - 45 percent complete.
- Reading Flash [0x075C2C0] 7536KB of 16384KB - 46 percent complete.
- Reading Flash [0x0785200] 7700KB of 16384KB - 47 percent complete.
- Reading Flash [0x07AE180] 7864KB of 16384KB - 48 percent complete.
- Reading Flash [0x07D70C0] 8028KB of 16384KB - 49 percent complete.
- Reading Flash [0x0800000] 8192KB of 16384KB - 50 percent complete.
- Reading Flash [0x0828F80] 8355KB of 16384KB - 51 percent complete.
- Reading Flash [0x0851EC0] 8519KB of 16384KB - 52 percent complete.
- Reading Flash [0x087AE40] 8683KB of 16384KB - 53 percent complete.
- Reading Flash [0x08A3D80] 8847KB of 16384KB - 54 percent complete.
- Reading Flash [0x08CCD00] 9011KB of 16384KB - 55 percent complete.
- Reading Flash [0x08F5C40] 9175KB of 16384KB - 56 percent complete.
- Reading Flash [0x091EBC0] 9338KB of 16384KB - 57 percent complete.
- Reading Flash [0x0947B00] 9502KB of 16384KB - 58 percent complete.
- Reading Flash [0x0970A40] 9666KB of 16384KB - 59 percent complete.
- Reading Flash [0x09999C0] 9830KB of 16384KB - 60 percent complete.
- Reading Flash [0x09C2900] 9994KB of 16384KB - 61 percent complete.
- Reading Flash [0x09EB880] 10158KB of 16384KB - 62 percent complete.
- Reading Flash [0x0A147C0] 10321KB of 16384KB - 63 percent complete.
- Reading Flash [0x0A3D740] 10485KB of 16384KB - 64 percent complete.
- Reading Flash [0x0A66680] 10649KB of 16384KB - 65 percent complete.
- Reading Flash [0x0A8F600] 10813KB of 16384KB - 66 percent complete.
- Reading Flash [0x0AB8540] 10977KB of 16384KB - 67 percent complete.
- Reading Flash [0x0AE1480] 11141KB of 16384KB - 68 percent complete.
- Reading Flash [0x0B0A400] 11305KB of 16384KB - 69 percent complete.
- Reading Flash [0x0B33340] 11468KB of 16384KB - 70 percent complete.
- Reading Flash [0x0B5C2C0] 11632KB of 16384KB - 71 percent complete.
- Reading Flash [0x0B85200] 11796KB of 16384KB - 72 percent complete.
- Reading Flash [0x0BAE180] 11960KB of 16384KB - 73 percent complete.
- Reading Flash [0x0BD70C0] 12124KB of 16384KB - 74 percent complete.
- Reading Flash [0x0C00000] 12288KB of 16384KB - 75 percent complete.
- Reading Flash [0x0C28F80] 12451KB of 16384KB - 76 percent complete.
- Reading Flash [0x0C51EC0] 12615KB of 16384KB - 77 percent complete.
- Reading Flash [0x0C7AE40] 12779KB of 16384KB - 78 percent complete.
- Reading Flash [0x0CA3D80] 12943KB of 16384KB - 79 percent complete.
- Reading Flash [0x0CCCD00] 13107KB of 16384KB - 80 percent complete.
- Reading Flash [0x0CF5C40] 13271KB of 16384KB - 81 percent complete.
- Reading Flash [0x0D1EBC0] 13434KB of 16384KB - 82 percent complete.
- Reading Flash [0x0D47B00] 13598KB of 16384KB - 83 percent complete.
- Reading Flash [0x0D70A40] 13762KB of 16384KB - 84 percent complete.
- Reading Flash [0x0D999C0] 13926KB of 16384KB - 85 percent complete.
- Reading Flash [0x0DC2900] 14090KB of 16384KB - 86 percent complete.
- Reading Flash [0x0DEB880] 14254KB of 16384KB - 87 percent complete.
- Reading Flash [0x0E147C0] 14417KB of 16384KB - 88 percent complete.
- Reading Flash [0x0E3D740] 14581KB of 16384KB - 89 percent complete.
- Reading Flash [0x0E66680] 14745KB of 16384KB - 90 percent complete.
- Reading Flash [0x0E8F600] 14909KB of 16384KB - 91 percent complete.
- Reading Flash [0x0EB8540] 15073KB of 16384KB - 92 percent complete.
- Reading Flash [0x0EE1480] 15237KB of 16384KB - 93 percent complete.
- Reading Flash [0x0F0A400] 15401KB of 16384KB - 94 percent complete.
- Reading Flash [0x0F33340] 15564KB of 16384KB - 95 percent complete.
- Reading Flash [0x0F5C2C0] 15728KB of 16384KB - 96 percent complete.
- Reading Flash [0x0F85200] 15892KB of 16384KB - 97 percent complete.
- Reading Flash [0x0FAE180] 16056KB of 16384KB - 98 percent complete.
- Reading Flash [0x0FD70C0] 16220KB of 16384KB - 99 percent complete.
- Reading Flash [0x1000000] 16384KB of 16384KB - 100 percent complete.

Writing flash contents to file “spi.bin”…

Memory Dump Complete
FPT Operation Successful.

Ok, good news. You have read/write access to the SPI/BIOS chip so you can certainly fix the problem. Thing is, I don’t understand what the problem is. As shown in MEInfo, the CSME & PMC firmware are both updated and working as expected. Maybe it’s the BIOS which now has corrupted settings (NVRAM) for some reason. Did you try restoring BIOS defaults by any chance? Anyway, I have prepared the following SPI/BIOS image which is based on Gigabyte’s X5V810.B04 but with the latest CSME & PMC firmware. It can be flashed by Flash Image Tool via “fptw -f outimage.bin” followed by “fptw -greset”.

outimage.rar (4.94 MB)

Yes I had the most recent bios installed (B04 the one you posted) and when I had access to windows I reinstalled it with the Oem application but it did not solve the problem so I downgrade it to B02 but the problam was still here. I will try with your solution, but when i installed the bios through the program on windows it was updating 2 files at the same time, the bios and another file called EC (EC v F004 for B04 bios). Will not it be a problem if I update the bios in B04 with the EC file on the old version?

Thank you

[EDIT] I try the update with fpt but when I put the command “fptw -f…” it says “Bad command or filename” so I try with “fpt -f…” the command is correct but I have the error below ;(

FW Status Register1: 0xA0000255
FW Status Register2: 0x30850106
FW Status Register3: 0x00000020
FW Status Register4: 0x00004000
FW Status Register5: 0x00000000
FW Status Register6: 0x00400000

Initializing SPI utilities
Reading HSFSTS register… Flash Descriptor: Valid

Region Limits as programmed into the SPI Registers
FREG0 - DESC Region:Base Address: 0x000000 Limit : 0x000FFF
FREG1 - BIOS Region:Base Address: 0x800000 Limit : 0xFFFFFF
FREG2 - CSME Region:Base Address: 0x001000 Limit : 0x7FFFFF
FREG3 - GbE Region:Base Address: 0x7FFF000 Limit : 0x000FFF
FREG4 - PDR Region:Base Address: 0x7FFF000 Limit : 0x000FFF
FREG5 - Region:Base Address: 0x7FFF000 Limit : 0x000FFF
FREG6 - Region:Base Address: 0x7FFF000 Limit : 0x000FFF
FREG7 - Region:Base Address: 0x7FFF000 Limit : 0x000FFF
FREG8 - EC Region:Base Address: 0x7FFF000 Limit : 0x000FFF
FREG9 - Region:Base Address: 0x7FFF000 Limit : 0x000FFF
FREG10 - Region:Base Address: 0x7FFF000 Limit : 0x000FFF
FREG11 - Region:Base Address: 0x7FFF000 Limit : 0x000FFF
FREG12 - Region:Base Address: 0x7FFF000 Limit : 0x000FFF
FREG13 - Region:Base Address: 0x7FFF000 Limit : 0x000FFF
FREG14 - Region:Base Address: 0x7FFF000 Limit : 0x000FFF
FREG15 - Region:Base Address: 0x7FFF000 Limit : 0x000FFF
Address Limit 0x1000000 Maximum Memory 16384kB


— Flash Devices Found —
MX25L12875F ID:0xC22018 Size: 16384KB (131072Kb)

Using hardware sequencing.
Reading region information from flash descriptor.
Base: 0x00000000, Limit: 0x00000FFF
Base: 0x00800000, Limit: 0x00FFFFFF
Base: 0x00001000, Limit: 0x007FFFFF
WriteStartAddress : 0x00000000
WriteEndAddress : 0xFFFFFFFF
BiosStartAddress : 0x00800000
BiosEndAddress : 0x00FFFFFF
Need to disable BIOS Write Protection based on Address overlap …
FPRval 0x00000000
BIOS Guard Lock Enable is set

Error 301: Protected Range Registers are currently set by BIOS, preventing flash access.
Please contact the target system BIOS vendor for an option to disable Protected Range Registers.
FPT Operation Failed.

Make sure you have the latest BIOS from Gigabyte installed. Afterwards, run “fpt -me -f outimage_cse.bin” followed by “fpt -greset”.

outimage_cse.rar (1.61 MB)

Okay, but I have one more question :), generally I updated the BIOS directly on Windows with the update program from Aorus and it was updating BIOS and EEC but now I can’t have acces to Windows.
So I extracted the *.exe but there are many files. For BIOS update, I think I have to copy in my bootable usb key the bios file and afudos.exe present in DOS folder, but for EC update I don’t know how and what files I need (only EC.bin or flash2.bin too) and do I need afudos.exe to update or it’s another program in the extracted files ? Do you have an idea ?

Thank you for your help

[EDIT] I tried to update the BIOS but I can’t arrive to do. I don’t know what files I have to copy in my usb key to do the update, afudos.exe (in DOS folder of extracted files) doesn’t work.

The EC has its own chip. For now, lets restore the BIOS chip firmware. Once you boot into Windows, you can run the latest BIOS update from Gigabyte to update the EC as well (in case you downgraded that as well). We’ll flash the stock SPI/BIOS as provided by Gigabyte, via DOS. Download the attachment, copy the three files into a bootable USB stick with DOS and run “flash.bat”.

X5V810_B04.rar (5.01 MB)

Thank you but I think I’m out of luck :frowning:
I’ve created a bootable usb with DOS on rufus but when I run “flash.bat” nothing happens except the blinking cursor and I don’t write a command anymore. I have to reboot for exit DOS.
Is there a particular DOS version to install ?

You can create a bootable USB with FreeDOS via Rufus. You can enter the command manually afterwards if the automatic batch file does not work for some reason:

AFUDOS X5V810.B04 /p /b /n /s /r /q /oemcmd:1 /k /shutdown %1 %2 %3

OkayIt’s exactly what I did, a bootable USB with FreeDOS via Rufus and run the batch file.
Also I didn’t specify but I had tried directly with this command

and there is the same result…

Well ok, that makes no sense. Try removing those “%1 %2 %3” in the end.

Otherwise, are you able to boot info an EFI environment (you should)? If yes, download the attachment and just copy the “efi” folder & two files (“AfuEfix64.efi”, “X5V810.B04”) at the root of the USB drive, nothing else is needed. Boot from the USB drive and it should show you a map/list of partitions. Choose the one corresponding to your flash drive, usually command “fs0:”. Afterwards, enter the command:

AfuEfix64.efi X5V810.B04 /p /b /n /s /r /q /oemcmd:1 /k /shutdown

X5V810_B04.rar (5.24 MB)

Hey :), I finally was able to update BIOS in EFI with your files and run the fpt commands in your #6 post. There was no error for the first fpt command, green message at the end of verification so I ran the second command and the laptop restarted several times before to show the oem logo.
Now I have the bios updated to latest version but there are always other problems present (sata detection, m2 disk detection, etc…) except the number of memory slot has returned to 2 instead of 4, that’s a good point :smiley:
Do you think I could find all the features of the BIOS again as originally ?
Do I also have to do what you told me in #4 post in addition to the one I already made in #6 post ?

[EDIT] Apparently windows starts (on M.2 disk, not always but it’s better than nothing) and my computer is charging again (not stable) but after disconnecting the charging plug, Windows crashed with blue screen and reboot. I have the impression that when Windows gets started it’s only when the computer is plugged in. My other HDD sata is still not detected in BIOS.

Ah finally. Maybe it was some kind of FreeDOS incompatibility or similar. Doesn’t matter as long as you can now use both EFI and Windows.

The goal now is to make your system 100% operational, just like before the update attempt. First, make sure you have the latest BIOS/EC installed by running the Gigabyte installer via Windows. If that’s done, check with MEInfo if your CSME & PMC firmware versions are the old or new ones. If they are the new ones, we’ll downgrade them via FPT, which should be possible because you have read/write access to the SPI/BIOS chip.

Download the attachment and run Flash Programming Tool with command “fptw -me -f X5V810.B04_cse.bin” followed by “fptw -greset”.

X5V810.B04_cse.rar (1.53 MB)

I do what you told me and currently I write from my laptop currently that apparently works normally again :smiley: so thank you so much for your help, you’re the best :wink:
But I wondered out of curiosity and to understant, did you have an idea of what could have caused this problem exactly ?
I did the update directly with CMD on Windows, do you think if I made it on EFI environement (for example) it will be more safe ?
And in case I redo the an update, just to be sure, what type of firmware corresponding to my system should I install (EXRGN, RGN, FWU) ?


Honestly, no. Maybe the issues you were facing were PMC related as it does stand for Power Management Controller. But if so, I don’t know why. The new firmware was certainly compatible and it requires no configuration. MEInfo was also reporting everything as working fine. To maybe narrow it down, was the issue solved immediately after flashing “X5V810.B04_cse.bin”? Meaning, did the problem remain and then re-flashing the latest BIOS/EC fixed it? I’m trying to figure out if the culprit was the CSME+PMC update or the BIOS/EC.


As long as you don’t have other programs/services running in the background at Windows, it should be fine. The only advantage of using DOS/EFI is that you automatically rule out other OS stuff interfering with the important update process.


Doing tests to figure out what went wrong would be great for me and the rest of the community. However, I don’t recommend it in your case because you’re using a laptop and recovery is usually very-very difficult in these systems. You were actually very lucky that your system has read/write access to the SPI/BIOS firmware as that should not be the case for security reasons. As for what to use when updating, make sure to read “Firmware Regions (RGN/EXTR)” and “Notice about CSME 12 FWUpdate Tool” at Section B of the (CS)ME thread. Basically, for FWUpdate use, you can take either RGN or EXTR and merge it with the correct PMC via Flash Image Tool, just like you did initially correctly.



In the order of how it happened :
1. From de latest bios (FB04) and original CSME firmware (12.0.0.1062) , I first made the update to the latest CSME+PMC version (merged file 12.0.6.112 + 300.2.11.1014)
2. Issues appears from here, no bios detection of sata drive and M.2 (where windows installed) but sometimes windows started and when the laptop was plugged when I was on windows, the charge icon notified “plugged in, not charging” and if I disconneted it, sometimes windows crashed (bluescreen)
3. From here, I wanted to reinstall again latest bios thinking the old firmware overwrite the new one but the new was still installed
4. So I downgrade to the first bios version (FB02) and more issue appears from here, no more detection of M.2 so impossiblity to start windows, 4 memory slots appears instead of 2 ( (2 with ram and 2 empty).
5. When I managed to update to the latest firmware again (FB04), the new issues above disappears and I went back to the problems mentioned in point 2.
6. And when I managed to downgrade to the old CSME and PMC firmware everything was working again.

However, I noticed that a sometimes times at fisrt start, windows loading was longer than usual, maybe 5-10 max before, against ~20 sec now. It’s a detail but it always started very quickly before.

Thank you for the detailed answer. Well, it seems that there were 2 issues. First, the CSME+PMC update caused some sort of non-obvious issue (maybe BIOS incompatibility?). Then, the BIOS downgrade caused even more issues. I don’t even see that version at Gigabyte’s website, maybe it was problematic. Anyway, now you have a working system again. I could provide tests to see what went wrong but for now leave the laptop as it is and update to future official Gigabyte SPI/BIOS only, at least until we have more info from systems which can be recovered more easily in case of problems. CSME 12 updating is new so I haven’t had the chance to find people who are trying to update yet so that we figure out the workflow exactly.

By the way, you mentioned earlier that MEA was crashing at your dumped SPI image. It turns out there was a bug in MEA. I will consider that a report so thank you for that. It has now been fixed at the latest version.

Hi @SabriLLe

Another laptop user with a very similar system had the same issue as you and, from what I can tell, the problem was that PMC 300.2.11.1014 was problematic whereas the new 300.2.11.1015 fixes those issues. If you are interested in trying again (no problem at all if you don’t), you can find instructions here.

Ah great thank you, I will try to install the new PMC update asap. I’ll let you know the result