Hello everyone,
I recently bought a laptop motherboard from ebay (lenovo edge e330 motherboard (with hm77 intel chipset)and CPU i5-3210m) to be used as a computer to connect to with RDP or other remote access apps (for browsing etc).
I would also like to connect to it remotely with using Intel ME to assess any problems (power up, access change bios settings, etc)
I mention I didn’t previously use intel ME or configured but I read recently about it and would like to use it.
But the problem is I cannot access it from anywhere.
I guess the motherboard is a bit odd because in BIOS system board serial number is INVALID; system unit serial number is OK and I can check it on lenovo site (1 year warranty laptop bought in 2012)
(no msdm table is present in smbios acpi)
Intel AMT is Enabled but Not Activated.
At first I had the CTRL-P configure option present in boot menu. But then after a few windows boots its not present anymore.
Bios is latest version
no devices, drivers appear in Device Manager (related to intel ME, AMT etc).
As I said I don’t know much about Intel ME , so I am just asking:
- could it be set up already by the previous owner (of the motherboard) and block any local client trying to access its settings
in other words could a local client be cut out (some opt out or something) to be able to access ME settings and set up to call home
should i be worried or am I to paranoid about this possibility.
- what could I do regain access to it and configure it (and be able to access the computer from WAN)
Thanks.
HM77 chipset doesn’t offer intel vPro, that would be QM77. if this chipset comes with a 5 MB ME firmware it can maybe offer Intel SBA.
It wouldn’t be a good idea to present a ME 8.x vPro interface to the internet (WAN?) anyway. This version is discontinued, has several unfixed security bugs, and can’t be updated to a higher version.
Thanks for you answer, but that doesn’t answer any of my questions
Lenovo e330 (intel hm77 chipset) has Intel ME support because there are drivers for this on it’s support lenovo page.
(the drivers to manage it for windows, even an update to MBEX v8.1 (i didn’ try it yet. I don’t want to overwrite any data if AMT is configured already)
In short what I was asking is how can I access Intel AMT , MEBx and configure it because I can’t.
Could this be because (access to the Intel AMT) is cut off by a previous ME configuration data (in bios chip)
and can the motherboard be configured to call home (IP from internet, wan)
There was CTRL+P option until I connected to internet, and booted a couple of times in windows
@corexlim Intel AMT = vPro
- HM77 Chipset doesn’t have AMT = vPro (See Intel Mobile Intel® HM77 Express Chipset)
- all Intel Ivy Bridge PCs do have an Intel ME
- you can update all versions of Intel ME firmware to the latest version of same revision
- you can always install a driver for Intel ME in Windows
- Intel ME of these generations comes with different sizes: 1.5MB ‘consumer’- ME just for system start, and 5 MB ‘corporate’, in different versions with different abilities
- AMT always requires processor, chipset, network card to be ready for AMT
Download Intel ME System Tools v8 r3, run MEinfo and check the output for Intel(R) Active Management Technology or Intel(R) Small Business Technology
Examples for ME 9.1
Copyright(C) 2005 - 2017, Intel Corporation. All rights reserved.
Intel(R) Manageability and Security Application code versions:
BIOS Version: 3602
MEBx Version: 9.0.0.0028
Gbe Version: 1.3
VendorID: 8086
PCH Version: 5
FW Version: 9.1.43.3004 H
LMS Version: Not Available
MEI Driver Version: 11.7.0.1057
Wireless Hardware Version: Not Available
Wireless Driver Version: Not Available
FW Capabilities: 0x0DFE5967
Intel(R) Active Management Technology - PRESENT/ENABLED
Intel(R) Anti-Theft Technology - PRESENT/ENABLED
Intel(R) Capability Licensing Service - PRESENT/ENABLED
Protect Audio Video Path - PRESENT/ENABLED
Intel(R) Dynamic Application Loader - PRESENT/ENABLED
Intel(R) AMT State: Enabled
TLS: Enabled
Last ME reset reason: Power up
…
Intel(R) MEInfo Version: 9.1.45.3000
Copyright(C) 2005 - 2017, Intel Corporation. All rights reserved.
GBE Region does not exist.
Intel(R) Manageability and Security Application code versions:
BIOS Version: V2.11
MEBx Version: 10.0.0.0004
Gbe Version: Unknown
VendorID: 8086
PCH Version: 0
FW Version: 9.1.45.3000 H
LMS Version: 11.7.0.1060
MEI Driver Version: 11.7.0.1057
FW Capabilities: 0x1930194C
Intel(R) Small Business Technology - PRESENT/ENABLED
Intel(R) Capability Licensing Service - PRESENT/ENABLED
Protect Audio Video Path - PRESENT/ENABLED
Intel(R) Dynamic Application Loader - PRESENT/ENABLED
TLS: Enabled
Last ME reset reason: Power up…
As I said I don’t know that much about Intel AMT , ME etc. I could easily mix terms meaning etc.
And now from what you wrote and looking more carefully at the side descriptions in BIOS I reckon I confused Intel AT Module Activation with Intel AMT. Intel AT Module is enabled.
But there is a “CTRL-P to enter the Management Engine setup screen” option
When I first tried to enter this all I got was Entering MEBx … and windows loads.
And on lenovo support page for this laptop (I used the serial so I am not mistaken; it’s a Edge E330 (ThinkPad) - Type 3354) at Chipset Drivers there are:
Intel Management Engine Interface Driver for Windows 10 (32-bit, 64-bit), 8 (64-bit) - Notebook
This package installs the software (Intel Active Management Technology (AMT) Management Engine Interface Driver) to enable the following device. - Intel Management Engine Interface
Intel Management Engine 8.1 Firmware for Windows 8.1 (64-bit), 8 (64-bit), 7 (32-bit, 64-bit), XP (32-bit, 64-bit) - ThinkPad E330
Intel Chipset Support for Windows 10 (32-bit, 64-bit), 8.1 (64-bit), 8 (64-bit) - Notebook
This package installs the software (Intel Chipset driver) to enablethe following device. - Intel(R) 7 Series Chipset
Now, in Windows 10 in device manager there are no devices related to the Intel ME, Intel AMT, etc present.
If I try installing Intel Management Interface Drivers i get "this computer does not meet the minimum requirements for installing the software"
Chipset drivers is ok, it installs.
Firmware upgrade I didn’t try it because I don’t want to mess up BIOS ME data (I think it should be present) , but I guess it won’t work even if I tried.
From MeInfoWin64.exe i get:
Error 9458: Communication error between application and Intel ME module (FW Update client)
Error 9459: Internal error (could not determine FW features information)
So what should I make of all this ?
It has to have Intel ME this board. Why can’t I access it , configure it.
Intel ME then (and not Intel AMT) I ask you, can it be configured to not be able to access settings somehow, and the board to call home (WAN not LAN), remote control ? I mean by the previous owner). Or is this paranoic?
BIOS is latest version H3ET79WW v1.16
Thanks
------------------------------
I downloaded the pack you said
>cctWin.exe gl
HECI INITIALIZATION FAILED
>FPTW64.exe -I Intel (R) Flash Programming Tool. Version: 8.1.60.1561 Copyright (c) 2007 - 2014, Intel Corporation. All rights reserved. Platform: Intel(R) HM77 Express Chipset
Reading HSFSTS register… Flash Descriptor: Valid
— Flash Devices Found —
MX25L6405D ID:0xC22017 Size: 8192KB (65536Kb)
W25Q32BV ID:0xEF4016 Size: 4096KB (32768Kb)
Error 104: The 2 SPI flash devices do not have compatible command sets.
>MEInfoWin64.exe
the 2 errors I mentioned in my previous post
----------------------
Lenovo Thinkpad EDGE E330 Intel® 2500 MHz 4096 MB Portable HD Graphics 4000
www.amazon.co.uk/Lenovo-Thinkpad-Intel&r…s/dp/B00CSJ5MCM
Intel Small Business Advantage (SBA): Yes
so it should have Intel AMT SBA
…
also found later this
Lenovo Solutions for Small Business Powered by Intel Small Business Advantage for Windows 7 - Laptop and Desktop
Supported SystemsLaptops:
Lenovo B480, B580
Lenovo V480, V480c, V480u, V480s, V580
ThinkPad Edge E130, E330, E430, E530, S230u, S430
ThinkPad T430, T430i, T430s, T530
ThinkPad W530
ThinkPad X230, X230i, X230 tablet
Desktops:
ThinkCentre Edge 92, Edge 92z
NotesChipset requirement - The computer must be running one of the following chipsets:
Intel Q77 desktop chipset
Intel B75 desktop chipset
Intel QM77 notebook chipset
Intel HM77 notebook chipset
Intel QS77 notebook chipset
CPU requirement - The computer must be running one of the following CPUs:
Intel Core i7 processor with vPro
Intel Core i5 processor with vPro
Intel Core i7 processor without vPro - B75, QM77, HM77 chipsets only
Intel Core i5 processor without vPro - B75, QM77, HM77 chipsets only
Intel Core i3 processor - B75, QM77, HM77 chipsets only
(2nd and 3rd generation processors supported)
Exceptions - The following CPUs are not supported: i3-2308M, i3-2328M,
i3-2348M, i3-2368M, i3-2355M, i3-2365M, i3-2375M
/+ I have Core i3-3110M
Firmware requirement - The computer must support the Intel Management Engine with Small Business Technology (SBT). To check for SBT support:
Click START → Intel → Intel Management and Security Status ->Intel Management and Security Status.
Check for a tab called “Intel SBT”.
Software requirement - The following software must be installed beforeLenovo Solutions for Small Business.
Microsoft .NET Framework 3.5 or later.
Intel Management Engine Interface driver (also called Intel AMT software)
But as I said I have no Intel MEI devices. and it gives me the error message I posted previously when I try and install it.
- This software is available on Lenovo’s support site.
- The Intel Management Engine Interface driver will install the following components required by Lenovo Solutions for Small Business:
MEI driver
Intel Management and Security Status
Intel LMS
Intel UNS
This install package will install the prerequiste “Intel Small Business Advantage”.
There is no AMT SBA, it’s either SBA or AMT- and your notebook has SBA as I wrote in my 1.st post.
Intel SBA was discontinued some years ago. For your system you find software here, latest version was 4.1.42, found 4.1.36 from Lenovo here.
And I did recommended to run meinfo from the system 8.x tools, not the flash utility (fptw). For Windows you’d need a driver for meinfo to be able to communicate with the ME. You find information which driver to chose for your system in this thread as well as the driver downloads. As you did’n t write your Windows version but got problems with the drivers offered for Windows 10 I assume Intel MEI Drivers & Software Corporate v11.0.6.1194 (ME 7-8) would be the correct choice.
Sorry, I ment the laptop should have Intel ME with SBA (not AMT with SBA)
I know my replys are a bit lenghty but please try and read them even if you skim. I wrote about what you asked to write in my 3rd post:
"Now, in Windows 10 in device manager there are no devices related to the Intel ME, Intel AMT, etc present.
/I am using Window 10 thus
If I try installing Intel Management Interface Drivers i get "this computer does not meet the minimum requirements for installing the software"
Chipset drivers is ok, it installs.
From MeInfoWin64.exe i get:
Error 9458: Communication error between application and Intel ME module (FW Update client)
Error 9459: Internal error (could not determine FW features information)
/it loads the driver smxdrv.sys, and launch it as Admin (i know pretty much about windows and computers, I don’t know much about Intel ME tough; that’s what I am trying to get better in)
Firmware upgrade I didn’t try it because I don’t want to mess up BIOS ME data (I think it should be present) , but I guess it won’t work even if I tried.
"
You don’t seem to understand the problem I have. (Do not take it in a negative way)
I know who to find the software and drivers fot Intel ME (with SBA) , or other needed software. Thanks anyway.
But I CANNOT USE IT
I cannot access Intel ME before windows
I cannot set a password in Intel ME MEBx settings.
I remember I had and worked on a Lenovo e330 5-10years ago and I know for sure I could access Intel MEBx config before loading OS. (That is why I wanted to buy this type of board again)
I set a password for it (diffrent from ‘admin’ the one with the requeirements)
I could access Intel ME settings etc (in the text GUI); but at that time it didn’t interest me to access it with Intel ME
On this board I can’t, and I am trying to find out why I can’t
and if this settings access can be cut of from previous configuration
if you know about Intel ME and configuration please tell me this:
If it can be configured to call home in WAN, and deny access to settings
or is some other thing with this board
Intel ME corruption , problems in BIOS
Indeed SBA != AMT. Other than that, run MEInfo -fwsts and show us the result because the ME firmware is probably corrupted.
Interesting, I did not think any of other MEinfo command line options would work.
It’s a step forward I guess in finding what is wrong with this motherboard.
Here is the output:
>MEInfoWin64.exe -fwsts
Intel(R) MEInfo Version: 8.1.56.1541
Copyright(C) 2005 - 2014, Intel Corporation. All rights reserved.
FW Status Register1: 0x00304181
FW Status Register2: 0x153B0100
CurrentState: Init
ManufacturingMode: Disabled
FlashPartition: Valid
OperationalState: Bring Up
InitComplete: Initializing
BUPLoadState: Success
ErrorCode: Debug Error
ModeOfOperation: Normal
ICC: No valid OEM data, ICC not programmed
PhaseStatus: UNKNOWN
-------------------------------
And this is the output for (maybe it helps)
>MEInfoWin64.exe -verbose
Intel(R) MEInfo Version: 8.1.56.1541
Copyright(C) 2005 - 2014, Intel Corporation. All rights reserved.
FW Status Register1: 0x00304181
FW Status Register2: 0x153B0100
CurrentState: Init
ManufacturingMode: Disabled
FlashPartition: Valid
OperationalState: Bring Up
InitComplete: Initializing
BUPLoadState: Success
ErrorCode: Debug Error
ModeOfOperation: Normal
ICC: No valid OEM data, ICC not programmed
PhaseStatus: UNKNOWN
HECI device is found to be disabled.
Windows OS Version : 6.2.9200 ""
OS BIOS Support : UEFI
Table Type 134 ( 0x 86 ) found, size of 16 (0x 10 ) bytes
Table Type 4 ( 0x 04 ) found, size of 42 (0x 2A ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 16 ( 0x 10 ) found, size of 23 (0x 17 ) bytes
Table Type 17 ( 0x 11 ) found, size of 34 (0x 22 ) bytes
Table Type 17 ( 0x 11 ) found, size of 34 (0x 22 ) bytes
Table Type 19 ( 0x 13 ) found, size of 31 (0x 1F ) bytes
Table Type 134 ( 0x 86 ) found, size of 13 (0x 0D ) bytes
Table Type 0 ( 0x 00 ) found, size of 24 (0x 18 ) bytes
Windows OS Version : 6.2.9200 ""
OS BIOS Support : UEFI
Table Type 134 ( 0x 86 ) found, size of 16 (0x 10 ) bytes
Table Type 4 ( 0x 04 ) found, size of 42 (0x 2A ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 16 ( 0x 10 ) found, size of 23 (0x 17 ) bytes
Table Type 17 ( 0x 11 ) found, size of 34 (0x 22 ) bytes
Table Type 17 ( 0x 11 ) found, size of 34 (0x 22 ) bytes
Table Type 19 ( 0x 13 ) found, size of 31 (0x 1F ) bytes
Table Type 134 ( 0x 86 ) found, size of 13 (0x 0D ) bytes
Table Type 0 ( 0x 00 ) found, size of 24 (0x 18 ) bytes
Table Type 1 ( 0x 01 ) found, size of 27 (0x 1B ) bytes
Table Type 2 ( 0x 02 ) found, size of 15 (0x 0F ) bytes
Table Type 3 ( 0x 03 ) found, size of 22 (0x 16 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 126 ( 0x 7E ) found, size of 17 (0x 11 ) bytes
Table Type 10 ( 0x 0A ) found, size of 6 (0x 06 ) bytes
Table Type 12 ( 0x 0C ) found, size of 5 (0x 05 ) bytes
Table Type 13 ( 0x 0D ) found, size of 22 (0x 16 ) bytes
Table Type 22 ( 0x 16 ) found, size of 26 (0x 1A ) bytes
Table Type 22 ( 0x 16 ) found, size of 26 (0x 1A ) bytes
Table Type 18 ( 0x 12 ) found, size of 23 (0x 17 ) bytes
Table Type 21 ( 0x 15 ) found, size of 7 (0x 07 ) bytes
Table Type 21 ( 0x 15 ) found, size of 7 (0x 07 ) bytes
Table Type 131 ( 0x 83 ) found, size of 22 (0x 16 ) bytes
Table Type 136 ( 0x 88 ) found, size of 6 (0x 06 ) bytes
Table Type 135 ( 0x 87 ) found, size of 74 (0x 4A ) bytes
Table Type 135 ( 0x 87 ) found, size of 10 (0x 0A ) bytes
Table Type 15 ( 0x 0F ) found, size of 81 (0x 51 ) bytes
Table Type 140 ( 0x 8C ) found, size of 67 (0x 43 ) bytes
Table Type 140 ( 0x 8C ) found, size of 47 (0x 2F ) bytes
Table Type 140 ( 0x 8C ) found, size of 63 (0x 3F ) bytes
Table Type 140 ( 0x 8C ) found, size of 17 (0x 11 ) bytes
Table Type 140 ( 0x 8C ) found, size of 19 (0x 13 ) bytes
Table Type 24 ( 0x 18 ) found, size of 5 (0x 05 ) bytes
Table Type 132 ( 0x 84 ) found, size of 7 (0x 07 ) bytes
Table Type 135 ( 0x 87 ) found, size of 18 (0x 12 ) bytes
Table Type 140 ( 0x 8C ) found, size of 15 (0x 0F ) bytes
Table Type 127 ( 0x 7F ) found, size of 4 (0x 04 ) bytes
Error 9458: Communication error between application and Intel(R) ME module (FW Update client)
Error 9459: Internal error (Could not determine FW features information)
Yes, the ME and/or BIOS firmware are corrupted. You need to repair the corruption and for that you need read/write access to the SPI/BIOS chip. Check if the Flash Descriptor is unlocked, otherwise unlock it by following [Guide] Unlock Intel Flash Descriptor Read/Write Access Permissions for SPI Servicing. Once you have unlocked the FD, you’ll re-flash the ME firmware first to see if that’s the only corrupted part. I tracked down a SPI/BIOS dump from another E330 online, followed [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization on it so now the ME firmware it has is repaired and can be flashed on your system. Download the attachment and use Flash Programming Tool via “fptw -me -f Lenovo_ThinkPad_Edge_E330_Clean_ME.bin” followed by “fptw -greset”. A hard reboot will occur and afterwards, you should have a working ME firmware. Check with “MEInfo -fwsts” again. The hardest part is usually unlocking the FD.
Lenovo_ThinkPad_Edge_E330_Clean.rar (4.26 MB)
Thank you very much for your help. Hope I can unlock the FD by software. If it doesn’t I am able to reflash (with a programmer) the eeproms(I’ve done it in the past with other motherboards)
Do you know/think in this boards MEBx can be configured to be accessed remotly from internet (remote control, screen view, change bios settings)?
Don’t forget to make a complete dump / a complete backup of your bios before you try to flash the ME! As you already have a programmer this would possibly be the prefereed mode. Reading the chips with fpt(w[64]) shouldn’t be a problem, too, but you’d possibly have to change fparts.txt. (Link to similar 2 chip configuration)
Don’t forget to make a complete dump / a complete backup of your bios before you try to flash the ME! As you already have a programmer this would possibly be the prefereed mode. Reading the chips with fpt(w[64]) shouldn’t be a problem, too, but you’d possibly have to change fparts.txt. (Link to similar 2 chip configuration)
Thanks, I will try that too.
The FD is locked (CPU cannot access error)
So, I might try the pin method if I properly find what pins on my motherboard to shortcut (I managed to find a boardview)
The archive you attached for me has 2 files
Lenovo_ThinkPad_Edge_E330_Clean.bin 12MB
i guess this is the whole bios (EC firmware, and with Intel ME, and BIOS)
Lenovo_ThinkPad_Edge_E330_Clean_ME.bin 8MB
this is without ME part?
If I will be writing with FPT.exe its not a problem, i reckon.
But the problem is if I end up writing with the programmer.
On my motherboard there are two chips
one is 4MB and from what I have read containes the Embedded Controller firmware (just a part of the 4mb or the whole is the EC FW?)
one is 8MB
How shoud I write (the first or the second .bin to those two chips)
where should I split etc?
FPT* won’t let you program here, since the two chips have different programming parameteres.
It seems that the 12 MB file is the complete bios, which is distributed among these 2 chips. Look at the 12 MB file with uefitool_NE, bios starts at 8MB, so this suggests that the 4 MB Chip would house the bios region, the 8MB chip Descriptor and ME. Safest way to find out: Look at the two backup files you hopefully made, put them together in a hex editor and compare the structure…
Lenovo_ThinkPad_Edge_E330_Clean.bin → Full 12MB (0xC00000) SPI image for "FPT -f" use
Lenovo_ThinkPad_Edge_E330_Clean_ME.bin → ME Region only (0x7FF000 < 0x800000 = 8MB) for "FPT -me -f" use
The 12MB SPI image consists of 2 Flash Components: 8MB = 0x800000 (FD + ME) and 4MB = 0x400000 (EC + BIOS). You need to split them for SPI Programmer use.
I rould really like to try the pin method and flash with FPT (I found a GPIO33 pin in schematic pdf that is for Flash Descriptor unlock; but I will get back to that)
Wouldn’t it sufice to change the command sets in fparts.txt for the two chips to coincide, and make the command sets compatible?
If it’s not complatible you can’t flash the whole .bin to those chips with FPT?
W25Q32BV, 0xEF4016, 0x2000000, 0x1000, 0x20, 64, 0, 0xc7, 80000
MX25L6405D, 0xC22017, 0x4000000, 0x1000, 0x20, 64, 0, 0x60, 80000
>fptw64.exe -i
Intel (R) Flash Programming Tool. Version: 8.1.60.1561
Copyright (c) 2007 - 2014, Intel Corporation. All rights reserved. Platform: Intel(R) HM77 Express Chipset
Reading HSFSTS register… Flash Descriptor: Valid
— Flash Devices Found —
MX25L6405D ID:0xC22017 Size: 8192KB (65536Kb)
W25Q32BV ID:0xEF4016 Size: 4096KB (32768Kb)
— Flash Image Information –
Signature: VALID
Number of Flash Components: 2
Component 1 - 8192KB (65536Kb)
Component 2 - 4096KB (32768Kb)
Regions:
Descriptor - Base: 0x000000, Limit: 0x000FFF
BIOS - Base: 0x800000, Limit: 0xBFFFFF
ME - Base: 0x001000, Limit: 0x7FFFFF
GbE - Not present
PDR - Not present
Master Region Access:
CPU/BIOS - ID: 0x0000, Read: 0x0B, Write: 0x0A
ME - ID: 0x0000, Read: 0x0D, Write: 0x0C
GbE - ID: 0x0118, Read: 0x08, Write: 0x08
Total Accessable SPI Memory: 12288KB,
Total Installed SPI Memory : 12288KB
Change W25Q32BV from 0xC7 to 0x60 for FPT use, both are the same:
So, after I change the command set and hopefully unlock the descriptor with pin method (gpio33 to gnd; as I said will get back to this with some info request; but this is the way the schematic pdf sais it unlocks)
then use FPT -f "full 12mb .bin" and it should work?
If the 12MB file plutomaniac created for you isn’t based on your own bios- backup, you could lose som information that was specific for your notebook (possibly serial, network address…) when overwriting the bios region.