Hello everyone!

As I am still a beginner in the area of ​​maintenance of laptop's and PC's, some things I'm still 'catching' ...

for example: I have the motherboard "qcl40 la8221p" from Asus' laptop "a45a" and its problem was doesn't turn on. After cleaning [and draining possible static energy] I managed to turn on the equipment and it gave a video; but for getting excited [beginner's thing ...], I didn't even back up the original BIOS and I've been trying to update the BIOS (using the update file downloaded from the website) through the machine's SETUP, since its HDD was not being recognized.

Conclusion: at the end of the process there was a verification error, which I interpret as a checksum error [image below]



==================================================

So I started my research on editing bios and now, that I found this forum and interlaced myself with fitc.exe, I made about 15 BIOS versions between fitc.exe, several versions of ME and other means of BIOS edits that I learned. So far I've tested 5; three of them did not show an increase in current, but the remaining two showed similar results as follows:

I press the 'power', the led lights up and stays on for about 6 seconds and goes off; I try again, and as I try, the amperage in the bench-top source increases, for example: in the first one it gives 20 milliamps; on the 2nd, 30 ... and so on until it reaches something around '0.070 A' and then drops to '0.000 A'. But now, the increasing of amperage only happens if I drain all the motherboard energy and repeat the process.

I'll continue trying, but if this information already indicates something [that is really a BIOS or motherboard problem] to someone with more experience and can give me a 'tip', I will certainly already take a good step forward in completing my service.

Obviously, after I fix it I post the details here.

Thank you.

ytsoc - how did you solve this question? for easy cleaning CSME 12c - it is necessary to unite the region with PMC or not? Thanks

sorry, i do not have a solution

@plutomaniac - Can you explain, or update the guide, how we should use EXTR to clean/update ME FW manually, on our end to be fixed for other users to then flash in via FW Update tool.
I thought you told me before it's OK with V12+ to use EXTR for this process, but I just tested and I see original settings are not same in before/after XML, thus stuff from the EXTR is being carried over during the process.
Thanks

Well I already updated ME to latest RGN + latest PMC already for user, but wanted to now send him clean updated latest EXTR ME FW version that he could program in with FW Update tool.
But, I can't, due to EXTR by itself says no FW Update possible, and if I want to merge PMC with this to make it FW update possible, then incorrect settings are transferred over during this process.
So, is it not possible to do what I wanted? Or, is the Y/N the answer here? * Edit - I guess that does not apply, target goal = 12.0.70.1652_CON_H_BA_PRD_EXTR

@Lost_N_BIOS Doesn't your FIT v12 write FWupdate files, too? If I merge Intel CSME Firmware v12.0.71.1681 (CON H BA) with Intel PMC CNP Firmware v300.2.11.1025 (H B) just as an example, flash components "0", build, I get:

"FW update image written: ..../Intel CSME System Tools v12 r28/Flash Image Tool/WIN32/cse_image_FWU_Base.bin
FW update image written: ./Intel CSME System Tools v12 r28/Flash Image Tool/WIN32/cse_image_FWU_Full.bin"



As far as I understood FWUpdate doesn't transfer any settings, so it doesn't really matter which configuration might be stored in the image?

OK, let me explain. I took full already clean/UPD ME FW (older) complete BIOS image, tried to update to 12.0.70.1652_CON_H_BA_PRD_EXTR, after compare before/after outimage and settings do not match.
I prefer to use full BIOS image when doing anything ME FW, on my end. Then I planned to extract ME FW to give to user to flash via FW UPD tool.
Yes, thank you both, I did forget that ME FW Update tool will not transfer in incorrect settings, but still, I should not be seeing them, thus my questions.

Latest PMC already integrated in previous BIOS w/ latest RGN clean UPD, already flashed in and tested.
I was simply trying to make a file so user could update to the latest version (EXTR) with FW Update tool, since I could not update to EXTR while clean/UPD on my end.

As for the mis-matched settings on before/after, here is an example area, and now I noticed it's just this area


If I were to send him cse_image_FWU_Base.bin, but until I found why the reason for above, I would not trust this file.

I see what I intended is not possible (extract UPD ME from BIOS = FW Update = NO)
So I will have to use cse_image_FWU_Base.bin anyway, but I now see latest NO, with the latest version, so as usual, I'm a mess and lost with ME FW I used to only have to fight X79 ME FW

Why do we use Base over Full, both are identical?

@Lost_N_BIOS This time it's really not too easy to understand what you mean/ did...

Zitat von Lost_N_BIOS im Beitrag #324

---

OK, let me explain. I took full already clean/UPD ME FW (older) complete BIOS image, tried to update to 12.0.70.1652_CON_H_BA_PRD_EXTR, after compare before/after outimage and settings do not match.

---

Zitat von Lost_N_BIOS im Beitrag #324

---

......Then I planned to extract ME FW to give to user to flash via FW UPD tool.
Yes, thank you both, I did forget that ME FW Update tool will not transfer in incorrect settings, but still, I should not be seeing them, thus my questions.

Latest PMC already integrated in previous BIOS w/ latest RGN clean UPD, already flashed in and tested.
I was simply trying to make a file so user could update to the latest version (EXTR) with FW Update tool, since I could not update to EXTR while clean/UPD on my end.

---

Zitat von plutomaniac im Beitrag Intel Management Engine: Drivers, Firmware & System Tools

---

How to use CSME v12 FWUpdate Tool: At CSME 12, Intel FWUpdate tool does not work with bare RGN or EXTR CSE firmware as it requires that they are first combined/stitched with the equivalent Power Management Controller (PMC) firmware, which is updated alongside the main CSE firmware. The CSME v12 archives below always include bare RGN or EXTR CSE firmware images so you must always stitch the equivalent PMC firmware first, via Flash Image Tool (FIT), before using Intel FWUpdate tool. To check if a CSE RGN/EXTR firmware region is already FWUpdate compatible, input it at ME Analyzer tool and make sure that "FWUpdate Support" is reported as "Yes". To generate the correct FWUpdate compatible CSME + PMC firmware combination for your system via FIT, you must first know your system's Chipset Platform (H, LP), Chipset Type (Consumer, Corporate, Slim) and Chipset Stepping/Revision (A, B, C etc).

• Download the latest Intel CSME System Tools (Section C) as well as ME Analyzer tool.
• From Intel CSME System Tools, run MEInfo command line tool and under "Intel(R) ME code versions" > "FW Version" you will find your system's Chipset Platform as well as Type (i.e. H Consumer etc). Under "PCH Information" > "PCH Step Data" you will find your system's Chipset Stepping which starts with a letter (Ax, Bx, Cx etc).
• Alternatively, only if you cannot use MEInfo, drag & drop your system's SPI/BIOS image at ME Analyzer tool and find "SKU" field which shows your system's Chipset Type and Platform (i.e. Consumer H). Next, find "Chipset Stepping" field which lists one or more supported Chipset Steppings in the form of letters (A, B, C etc).
• Based on your system's Chipset Platform, Type and Stepping, choose the correct CSME and PMC firmware (Section B).
• Input the chosen CSME firmware into ME Analyzer tool and make sure that "FWUpdate Support" is not reported as "Impossible".
• From Intel CSME System Tools, go to Flash Image Tool folder and make sure that only two (2) files exist: fit.exe and vsccommn.bin. Otherwise, delete the rest.
• Run Flash Image Tool (FIT) and adjust the Chipset Platform drop-down menu at the top to either "H Series Chipset" or "LP Series Chipset" based on your system's Chipset Platform. For the purposes of FWUpdate, there is no need to further adjust the Chipset SKU.
• Load/drop the chosen CSME firmware image and then input the chosen PMC firmware at "Flash Layout" > "Ifwi: Intel(R) Me and Pmc Region" > "PMC Binary File".
• Adjust "Flash Settings" > "Flash Components" > "Number of Flash Components" to "0".
• Adjust "Integrated Sensor Hub" > "Integrated Sensor Hub" > "Integrated Sensor Hub Supported" to "No".
• Build the image and a "cse_image_FWU_Base.bin" file will be generated.
• Input "cse_image_FWU_Base.bin" file into ME Analyzer tool and make sure that "FWUpdate Support" is reported as "Yes".
• Use FWUpdate tool to flash the "cse_image_FWU_Base.bin" image.

---

@lfb6 - What I meant, tried to explain, was I attempted to clean/UPD ME FW like you normally would, as I've done a million times without issue.
The problem here is me trying to figure out how to hand user proper file to use for ME FW update tool I guess, without the issues I'm seeing being a part of that file I pass to him.

I never work with ME FW update tool, or ME FW by itself, always entire BIOS and FPT.
So I'm sure some of my concerns here may be due to that, however, I don't see how/why I should not be concerned.

This is what was done already, flashed in and user is using as we speak >> BIOS Fixed, Unlocked, ME FW Updated to latest RGN/PMC (As we normally do, mentioned above)
However, due to latest actual ME FW version was not RGN, I used older one that was last RGN version. So, now, I want to give him file to use to update to latest actual version, and there is where problems begin.
PMC is already latest, but I can re-integrate that without issue, but I don't see how to give him safe file to use, provided what I showed in the image above
That the update ME via FIT with latest EXTR proves out changes that should not be, thus I don't see how cse_image_FWU_Base.bin would not also contain these same incorrect changes that should not be happening

I know you both want to help, but when I get lost on a ME FW issue, I usually can't absorb how to get around it.
I still avoid ANY X79 ME FW update for this reason, for anyone, and only direct them how to use ME FW Update tool and latest provided file.

Yes, some of your points/questions, I have the same concerns, thus my question here.
I have since noticed you can't use extracted ME FW, even cut to size, for ME FW Update tool, so I got that now

Maybe you could help the user? If yes, do you need me to link you to the last BIOS I gave him, with latest RGN ME + Latest PMC, or can you help him directly with none of that?

I have read the guide, but it and what you quoted is not at all related to anything I am asking (really this).
I know how to make proper ME files, it's just not happening here in a way that I trust, due to changes in before/after comparisons that should not be there.

Meaning >> I would not give this BIOS with updated ME FW (From EXTR) to user to put on with unlocked FD and FPT, or a flash programmer either, there is a problem.
The oddities I mentioned above (previous post/image) with cse_image_FWU_Base.bin and or Before/After XML on actual BIOS image.
I don't trust those incorrect things in the BIOS image before/after are not also going to be flashed in during a ME FW update using cse_image_FWU_Base.bin created at same time as outimage with incorrect settings as shown in the image above.

Quicker summary >> If I use EXTR via FIT and make BIOS/ME, before/after XML does not match properly.
How am I to know/trust cse_image_FWU_Base.bin generated right then too, is not also going to contain the same incorrect changes? << This sums up my questions and concern perfectly, nice and brief too

Zitat von Lost_N_BIOS im Beitrag #326

---

...Quicker summary >> If I use EXTR via FIT and make BIOS/ME, before/after XML does not match properly. ....

---

@lfb6 - Soon I will have to stop answering anything ME FW related
Here is the thread, last BIOS I made is in this post has the BIOS he programmed in, this has latest RGN and latest PMC already, just need to update ME side to latest EXTR
@ #622 - OverPowered TONGFANG CyberPower Machrevo MACHENIKE - Unlocked BIOS Guide W/ Files (42)

Yes, that was part of my summary and main question! How can I confirm, or be sure those incorrect changes I see, are or are not part of the cse_image_FWU_Base.bin update file.
I gave comparison image above, you can't compare what I'm asking about any other way, unless you know how to show settings contained within cse_image_FWU_Base.bin are NOT the same as contained withing outimage generated at same time.

If you can show him the way to update that ME FW further via ME FW update, while also at same time knowing FOR SURE those incorrect changes do not also get get transferred in the update file, then please do, thanks

Zitat von Lost_N_BIOS im Beitrag #328

---

@lfb6 - Soon I will have to stop answering anything ME FW related

---