@Fabulist - Yes that is what I'm wanting to see, show me image of that from bottom of report, it's still not clear to me in text format

Thanks for test report back on FPT flash, seems something is still locked or whatever is causing the ME Disabled message is causing this as well. Were you given any error once it was done writing?
Before you recover, one more test, if you don't mind, try this and see if outcome is same >> FPTw.exe -rewrite -f SPI.BIN

Once Plutomaniac gets back in hopefully he will see what's causing that, I'm helping another user with same message on his BIOS too, unsure if this is some ME message to be ignored, or some compatibility issue with FPT version or what

To recover, yes, program back in last known working BIOS. To avoid this issue, since ME FW will already be updated, and so you can put system back together, any further BIOS mods can be flashed via FPTw.exe -bios anyway, since that has been tested and confirmed OK

On RAID RST, I don't know what is compatible, this is not my area, you must read all the info on both threads I linked you to and decide and then let me know (For both EFI and orom).
If you want same version for both, and that is available for both, let me know both = same/same version

Nothing I can do to help with UBU, I've made him aware of this issue for a year or so, a few different times we've discussed it.

As I mentioned, probably TPM wasn't visible to you before due to either older BIOS version and it was hidden in that version, or due to the ME FW was messed up before, causing it to be hidden due to non-functionality and now ME FW is correct so it's visible again.

Do nothing after you recover, wait for plutomaniac to check the ME FW on the other thread once he gets back and then we'll see if we can get to the bottom of the cause of this.

I could not run the test you wanted me to, I had to recover because I could not boot. No I received no errors, otherwise I would have let you know.

OK, so I run a test since I had to open the laptop again, I updated all modules possible via UBU on your BIOS, including microcodes, but not the vBIOS (it gives an option about it?), and flashed it. I also figured out the RAID RST ROM/EFI I should use.

It actually worked, so it seems there is a problem with Intel's Flash Programming Tool instead of UBU? The only problem I have had, maybe because of the D4 microcode, I lost control of MSI's power/OC settings in the Dragon Center (reinstalling it did not change anything). There are options such as "Sport" that OC the CPU to about 3,3GHz for example, but in order for it to work, Intel Speedstep and the C states need to be enabled into BIOS.

The CPU was stuck at around 2,6Ghz, and the "Sport" option was not selectable, as if I had Intel Speedstep disabled into BIOS. I do not know what the problem is.

I will wait for the ME, however, I did update it in the past and it was working properly as far as I can tell, the TPM was not avaialble from when I purchased the computer (and even after multiple MSI BIOS), long before I updated ME.

Thanks!

Yes, sorry, I didn't think of that, you'd have to recover first no matter what to then test the -rewrite method.

Did you use the same older version of UBU this time, that you used before? If not, then it's not a valid test. I doubt it's anything to do with FPT, and same FPT version should have been used both times anyway (If you meant you flashed via FPT)
Send me this mod BIOS You made and I will check it, then we'll know if this padding this is an issue for your BIOS or not, or if it was only done with previous UBU edit but not this latest one you just made.

On ME, as mentioned, go ahead and update it via FW Update tool, then reboot and see if you still get same ME Disabled messages on FPT flash attempts.

TPM must have been hidden previous BIOS then,

Ah, you are right, my test is not comparable as the UBU version is not identical.

OK so, two things:

1) ME firmware was updated and is reported in the BIOS as such, everything in the system seems OK. I used v11.8.70.3626 as it seems, according to plutomaniac's thread to be the maximum version compatible with the system.

2) I created a second modded BIOS via UBU (uploaded here), on which I updated the Network and RAID modules, but not the microcodes. MSI's power\OC settings were restored and I can set the CPU to "Sport" mode again. This means that for some reason when updating the microcode, via UBU at least, I lose OC control and the CPU runs on minimum speed (it never clocks up at all).

The FPTw.exe -d SPI.BIN >> FPTw.exe -f SPI.BIN says "Unable to detect ME disabled", I did not accept the operation.

EDIT: Also, really cool I can use TPM now!

Thanks!

Upload both of those current UBU mods so I can see if this padding is removed in either, if it is then we know this is not a problem on this board/BIOS and some other thing I didn't notice causes the brick.
Sounds like current/latest UBU edit you mention is removing this padding too, thus the issues you describe above with microcode edit, and loosing OC control. But at least its not bricking.
Check current microcode shown in HWInfo64 with this situation and see if microcode shown is version you expected (or none) - You can see it here, in either place


Or you can see current micocodes in any BIOS by drag/dropping it onto ME Extractor, or with UBU scan if you want to wait for that each time, downloads are in the "releases" tab at top/middle
https://github.com/platomav/MCExtractor

Thanks, so ME FW update did not get rid of the message, we found the same in other thread where we're seeing this, I updated his ME FW manually there too.
Maybe some bug in FPT version or something, causing this message, we know it's not disabled so the message is false, but we'll have to wait and see what's causing it.

OK, I uploaded the version with and without the updated microcodes as well (misclicked on the previous post) here: https://www.mediafire.com/file/d63f7yvgp...U_BIOS.rar/file

HWINFO reports "C6" on μCU.

If I can help you figure out the problem with the ME for your other thread as well, I am available to run any test you prefer.

Thanks!

On ME, nothing we can do until plutomanic is back and has time to look into this and let us know, he's the ME FW guru
I tried for 15 minutes, can you upload that to another host, mediafire is crap for me this week
Never mind, finally got it, please wait while I check.

* Edit @Fabulist - padding file issue I mentioned is only present in the microcode edited version. So this means only UBU edit on that BIOS causes this, and in this case it does not brick the BIOS but does seem to mess up your CPU functionality (probably due to non-load of microcodes).
This is due to broken/non microcode load and the C6 is loaded from the OS files (windows microcodes), as C6 version is not in any of these BIOS (Stock contains C2 and 2C, and your mod/updated version contains D4 and 2E)

Oh OK, I did upload them on win-raid as attachments though (previous post, just now).

It's OK, refresh and see my edits above. Have to run for now, will be back tonight

Got it, thanks! Let me know if you find the time to proceed with the CPU microcode/VBIOS update on the BIOS since you figured out the problem, so we can try a final flash with these too.

I will be available in case I can help with something regarding the ME issue.

Good day!

@Fabulist - Here is update (Built on your pre-updated non-uCode BIOS) with updated uCodes + FIT Fixed & GOP, VBT, vBIOS all updated. If this fails to display, it may be due to GOP or VBT update, not always so simple on a laptop.
If this happens, we'll have to try GOP by itself, then vBIOS by itself, then both, then if OK add VBT (Which may need tested in various with/without GOP/vBIOS scenarios as well)
Additionally included is a microcode only update, so you can use with that by itself, in case there is issues with the vBIOS/GOP/VBT updates at first
http://s000.tinyupload.com/index.php?fil...162112674324504

All flashes can be done in windows with FPT, using command below, unless you need to recover from the vBIOS/GOP/VBT BIOS above

FPTw.exe -bios -f filename.bin

Send me some images of your BIOS, I need to see main "Settings" page at root level so I can see all visible submenus showing there. And one of inside of Advanced page, scroll up/down so I can see all visible setting/submenus directly at root of inside advanced too.

Thank you for this!!

OK so, the vBIOS mod gives me no boot, but the microcode BIOS works perfectly, the system's CPU also works properly and can OC via the Dragon Center's "OC" mode! If anything you were absolutely right, UBU was making a faulty CPU microcode update.

I uploaded the pictures here: https://imgur.com/a/hGpSuOL

Thanks!

You're welcome, and thanks for quick testing. Yes, I knew that was what's going on with the ucodes, at least it doesn't brick your system (many it does)

Here, please test GOP/vBIOS update only, if this doesn't fail, we know the VBT was the issue and either it can't be updated to that high of a version, or some other issue.
If this fails, then similar, GOP may not be able to be updated to that high of a version, and or at least not without some VBT update as well (They go together). This includes the ucode updates as well
If this works, then I will make you a few others with updated VBT too, using interim versions. if this fails, then next set I will send GOP update and vBIOS update as separate tests.
http://s000.tinyupload.com/index.php?fil...399988290447600

Thanks for the images, I will work on this in the background, some quick test on simple pre-mod changes may be required as I work through the mod
Ohh! Great! You have normal AMI type BIOS, not the usual MSI stuff, that will hopefully make these edits easier, some MSI BIOS menus are a pain in my rear
Please add "Save and Exit" page image too, thanks

I see, thank you for all this information.

OK, so this BIOS = no boot, first try huh! I would also like to note that ME got downgraded with the previous update (microcode BIOS or the vBIOS BIOS before it).

Yeah, MSI certainly went cheap with both the BIOS menu (there are multiple issues with it, system does not function properly without C states and Speedstep being enabledA) and cutting support really fast for a system that was really expensive at its time :) :) :)

This frustration is also the reason I am so inclined to update it. I love the old girl!

Thanks!

@Fabulist Sorry about the ME, I forgot you or I updated that and was only using the UBU mod BIOS you sent me as base, I will update it in next set and make that my new base.
Whatever you recover with programmer will overwrite the ME, so that may be what happened, if you used some older known working BIOS to recover with, that had older ME. After putting in new ME you have to do the 1+ minute no power thing, or issue this command from windows >> FPTw.exe -greset

Here, try GOP UPD only + vBIOS only. Hopefully only one fails, then well know more what's going on here. See, I told you vBIOS updating wasn't so easy on a laptop
If it's vBIOS causing the boot failure, it may simply need to be an older version than one I used
http://s000.tinyupload.com/index.php?fil...053776587488334

What do you mean about the System doesn't function right if C-State and or Speedstep is disabled? What happens if either is disabled?