@Lost_N_BIOS Thanks,

snakeman

@snakeman @Lost_N_BIOS I have tried to Mod the F12 Version for the Gigabyte Z370N WiFi but i wasn't successfull. I used the original DOwnloaded BIOS and changed the ME Version to 11.6.27.3264 as I did for my old BIOS and Change the SKU to Intel KBH H Series Chipsent and Emulation to Intel B250 Desktop. I have flased the modded BIOS then via the SPI Flasher and when I start it, it runs for around 30 seconds and turns itself of. WHen I restart it then it utrns it off immediality. I will upload both BIOS to check what I have done wrong. I have uploaded the BIOS to https://mega.nz/#!XFkwSK4S!D2mXzSF6MFfte...pYOsIXAsQLBacn8 The Password for the ZIP is hitman20

This is the Picture of the ME Analyzer.

@hitman20 @Lost_N_BIOS Why the Emulation to Intel B250 Desktop? I will do some more reading.

@hitman20 - I didn't check your BIOS, due to Mega is a pain for me to download from, but did you add in 906E9 microcode? Use MMTool on this one, or padding above ucode is removed. If yes, did you fix FIT table after that, if needed? This was not needed when I edited with MMTool, so should be OK
And, you really shouldn't FPT or flash programmer stock BIOS, this will loose your serial, UUID and LAN MAC ID, as well as a complete NVRAM volume and 95% of your other main NVRAM volume.
If you want to use FPT, or programmer, dump your BIOS (originally on there, it would need programmed back in now, first), then modify that, then FPT or program back. Preferably if you use FPT, only use that, if you use programmer only use that.
To start over, you will need to put back some original BIOS dump you have, from the programmer, unless you FPT flashed stock BIOS before that, then all NVRAM would be lost. Serial/UUID irrelevant here, and LAN MAC ID can be fixed anytime via FPT if needed.

If you are using stock BIOS as base source, just Qflash the BIOS, no need to FPT or program anyway, and as mentioned above it's not suggested for stock BIOS anyway due to all mentioned.
If, in Qflash, you are not offered quick or full, then you may need to DOS or windows FPT flash FD and ME Regions one by one (by themselves, follow ME region flash with -greset) This would need done with known compatible CPU installed still.

@snakeman - please test this F12 before I make the other older one you wanted. Leave in older/compatible CPU until you are done.
Flash via Qflash, if you are not asked in Qflash if you want Full or Quick (Choose Full if asked), then you will need to follow up with FPT flashes as noted below (use included files as source = filename.bin, these are extracted from the whole BIOS = same/same, just safer to feed FPT this way)

FPTw.exe -desc -f FD.bin
FPTw.exe -me -f ME.bin
FPTw.exe -greset

To ANYONE considering using this BIOS, this BIOS is STOCK modified BIOS, do not flash this with FPT or flash programmer, flash it only via Qflash (FPT or programmer flash of FD or ME is OK)
http://s000.tinyupload.com/index.php?fil...325382903565570

B250 SKU is used to make it Kaby Compatible, Z170 SKU may be possible to use too, I'm not 100% sure, only going on what @dsanke told us to use back first time we did this mod

@Lost_N_BIOS Downloading now........... I had two choices Quick or Intact! I choose Intact, flashing now.
@hitman20 here are my results with F12 provided by Lost_N_BIOS

Installed i5 7500 booted up fine
Windows10: booted fine ME drivers are loaded
Ubuntu 18.04.x: slow booting acting weird but I knew this with F12
Hackxxxxxh: did not boot also not surprised


meinfowin64 results:

Intel(R) ME code versions:

BIOS Version F12
MEBx Version 0.0.0.0000
GbE Version 0.2
Vendor ID 8086
PCH Version 0
FW Version 11.6.27.3264 H
Security Version (SVN) 1
LMS Version Not Available
MEI Driver Version 11.7.0.1040
Wireless Hardware Version Not Available
Wireless Driver Version Not Available

FW Capabilities 0x31101140

Intel(R) Capability Licensing Service - PRESENT/ENABLED
Protect Audio Video Path - PRESENT/ENABLED
Intel(R) Dynamic Application Loader - PRESENT/ENABLED
Intel(R) Platform Trust Technology - PRESENT/DISABLED

Re-key needed False
Platform is re-key capable True
TLS Disabled
Last ME reset reason Global system reset
Local FWUpdate Enabled
BIOS Config Lock Enabled
GbE Config Lock Enabled
Host Read Access to ME Enabled
Host Write Access to ME Enabled
Host Read Access to EC Enabled
Host Write Access to EC Enabled
SPI Flash ID 1 C22018
SPI Flash ID 2 Unknown
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
Independent Firmware Recovery Disabled
EPID Group ID 0x1033
LSPCON Ports None
5K Ports None
OEM Public Key Hash FPF Not set
OEM Public Key Hash ME 0000000000000000000000000000000000000000000000000000000000000000
ACM SVN FPF 0x0
KM SVN FPF 0x0
BSMM SVN FPF 0x0
GuC Encryption Key FPF Not set
GuC Encryption Key ME 0000000000000000000000000000000000000000000000000000000000000000

FPF ME
--- --
Force Boot Guard ACM Not set Disabled
Protect BIOS Environment Not set Disabled
CPU Debugging Not set Enabled
BSP Initialization Not set Enabled
Measured Boot Not set Disabled
Verified Boot Not set Disabled
Key Manifest ID Not set 0x0
Enforcement Policy Not set 0x0
PTT Not set Enabled
EK Revoke State Not Revoked
PTT RTC Clear Detection FPF Not set

@snakeman - If you need hackintosh mod I can do that too, sorry I didn't know you needed that done or I would have done already. Thanks for quick testing and report back [check] Now, we know this ME FW region is good, it can be extracted and use in F5 too now.

Good you had "Intact" option, that would be same as "Full", some BIOS don't have it, and some models never offer it. Like maybe F5 wont have it, it's OK in those cases though, just do as I mentioned with FPT if you run into that kind of situation

So, you now need F5 = same as above (+ new F12) both with CFG-Lock >> Disable << This is the main issue with hackintosh I believe, always Enabled by default
This may take an edit or two, before I know which method your BIOS is using to pull setting from. Please pick some obvious setting you know you can tell if it's enabled or disabled no matter what the BIOS option looks to be set on.
Then I will send you two BIOS to test this changed from default. Default can be enabled or disabled, doesn't matter, I will just change this in two ways and both may be visible changes in BIOS, but only one way may actually perform the change (and that is key, so make it some setting you can tell enabled or disabled, without touching the setting)
Maybe LED's, change from default static to something else like Pulse or OFF? << Lets do this one, to Off, if that OK as a test for you?

You know XD/NX//Execute Bit Disable (Set enabled), and VT-d, Secure Boot and possible others needs disabled correct for Hackinstosh. I assume you know, but mention in case maybe you forgot one of those

@Lost_N_BIOS Yes, I sometimes use Hack looks like the F12 bios supports the 9th Generation processors such as i9 9900k activates RTC which s not important to my i5 7500 processor sorry for the confusion. I found this information in a forum. https://www.tonymacx86.com/threads/succe...51#post-1934546 POST #507

Are talking the same thing here as CFG-LOCK?

@snakeman - please see my edits above, I was editing as you replied. CPU Gen means nothing to me, you must mention some model, and then a question about it. Sorry, I don't know what you are asking or saying there in regards to CPU.

Yes, what you linked is the standard mod I mentioned above CFG Lock, needs disabled for Hackintosh.
As for the other one, I've never heard of that needing changed, nor ever heard it mentioned by anyone in regards to anything, but if that is something you need changed we can change that too.
He's changing it from Default >> ACPI Time and Alarm Device >> To >> Legacy RTC

@Lost_N_Bios sorry for the confusion. If it can be done in the bios that would be great. "changing it from Default >> ACPI Time and Alarm Device >> To >> Legacy RTC".

Thanks for all the help.


snakeman

Sorry, I don't know what RTC is, if this is some BIOS setting then I can probably enable that for you too (on any BIOS) Unless you mean Real Time Clock?
If yes, that's probably same thing as discussed above, this wouldn't be something that changes due to CPU or CPU gen, it's just a BIOS setting

Yes, OK, I will make you new F12 with CFG Lock disabled and Legacy RTC set & F5 same way.

You're welcome!

But, first, we need to do as I mentioned above, with some single setting, so I can see which area the BIOS is using settings from. Are you OK with the test I mentioned, does that sound like an ideal way for us to test what I need to know I mean?
I send you two BIOS to test, both with LED's, change from default static to OFF? Then, you tell me which BIOS I sent you has the LED's OFF. Then I know where to change these two settings we need to change default of for Hackinstosh.
This is required on my end because the BIOS settings are stored in 3 locations, and only one is used by BIOS as a main setting source, but it's different for every BIOS what this main default source is (Setup, AMITSE/SetupData (What AMIBCP Changes), or NVRAM)
I will be making two BIOS for this test, one with setup change, other with what AMIBCP Changes, NVRAM isn't usually the source for this kind of setting change but it will get auto-updated with a copy of the used setting values as they change every time you change something.

I have to leave now though, so I will make these BIOS for you tonight and we'll proceed from there once I get report back from you on which disables the LED.
Then two BIOS will be made without further testing needed, all will be done.

@Lost_N_BIOS I could now get the Kabylake CPU to work with the Latest F12 BIOS. I flashed my F4 BIOS again and booted with the Coffee Lake Processor and Updated it to F12. Then I dumped the BIOS with the SPI Flahser, changed the ME Version to 11.6.27.3264 and changed the SKU to Intel KBP H Series Chipset, Ubtek B250 Desktop. Then I added the Micro Code for Kabylake with the MMTool and updated the ROM Versions with the UBU Tool. After this I have flased the BIOS again with the Programmer and it has booted sucessfully now.

Edit: I tried to make the RTC Lock visible in the BIOS with AMIBCP but it crashed while saving. I tried it with Version 5.01 and 5.02. I tried it to find something with the UEFI Tool but I don't know where to start there.

Edit2: I have now found the in the UEFI Tool the Path for the Variables of the Menu and extracted it with the IFR Universal Extractor. I tried via the UEFI Shell to modify the Addresses with setup_var 0x9BD 0x01 but it didn't work to make it visible.

Thanks.

@Lost_N_BIOS I used the technique from the link above and I'm booting hack again.
@hitman20 Do our boards support vpro? We have the intel ethernet cards. But does the Motherboard support Intel AMT? Looks like no according to intel only the Q370/Q270/Q170 My "optiplex 5040" supports it.

That would be a cool mod.



snakeman

@snakeman In the BIOS File are Settings for a AMT Configuration but I think the Board and the CPU doesn't support it. For example the Dell Poweredge T20 has Intel AMT and it only works there with Xeon CPU's and not with non Xeon CPU. I think it doesn't work there since it it also an non Server Mainboard.

@hitman20 - changing the variables via shell may not work, you need to use grub and setup_var instead (or wait until I am done here). Making the setting visible is unrelated to any of this, that's a totally different thing. That I can do for you guys too.
Also RTC Lock (0x9BD) is not the setting mentioned above, what you wanted is called System Time and Alarm Source, VarStoreInfo (VarOffset/VarName): 0x507

@snakeman - I am not sure what you are asking, "No settings thus far"??? I am waiting on you to reply to my question, then I was going to make test BIOS, to figure out which area on you guys BIOS I need to change to make these changes by default.
Yes, it's possible to do as you linked, any time, for all the settings. My goal for you was to make it a default thing in BIOS. And or, after that, I can make settings visible to you guys if you wanted.

VPRO is controlled by CPU, and BIOS/ME FW settings, this can be enabled or disabled too. For use of this, you'd really want a fully unlocked BIOS first though, so you could see/access all the in BIOS ME/AMT setting options.

* Edit @snakeman - Please test each of these BIOS, let me know which one disables the onboard RGB Fusion LED's by default (what it shows at the BIOS setting default doesn't matter to me for this).
Base BIOS used here is the F12 I modified above, all warnings mentioned there apply here, flash with Qflash but since your ME is already old version you can do with current CPU installed now.
Once I have your report back from this test, I can then make those changes you wanted by default. If you guys want unlocked BIOS, I need images of all your BIOS pages, everything you can see on all pages/submenus etc (F12 to USB, then 7zip please)
http://s000.tinyupload.com/index.php?fil...858854371762974

@Lost_N_BIOS I haven't tested because my clip does not work on my programmer. I had to order a new one today.
Wait this board is supposed to be dual bios, off to do some testing!





snakeman