Hey everyone, I recently got a BIOS and FD unlock from Lost N Bios, wich works great! Now, today I came across an old thread at techinferno about how to unlock BCLK alterations by flashing a ME region edited with FITC, all was done on a FIT v.8.
I’m wondering if this is possible on a ME v.11 system… I opened a ME DUMP on FIT v.11 but could not find the same options as in FIT v.8.
Also, is there any way to give BIOS BCLK and multiplier control over a CPU that doesn’t allow those alterations by nature?
To summarize, my goal is to change BCLK or multiplier of an I5 7200U beyond the current limit, and my question is if this is possible.
thanks in advance, guys
@fairestmeat - FITc v8 info applies to ME FW V8, none of that is relevant or possible in V11 ME FW, sorry 
Almost all CPU you can Bclk edit, as long as BIOS provides it, but most modern CPU this is tied to PCI/PCIE/SATA clocks to system messes up much past 103, and Intel has hard locked some CPU’s or chipsets etc to only allow 102/103 max anyway
So really just a waste of time to even consider anymore, Bclk/FSB overclocking has been officially killed now thanks to Intel.
@Lost_N_BIOS
I see… That’s a bummer! But thanks for clarifying.
Same thing about multiplier, I guess? I mean, no way to bypass the x31 limit of my cpu
CPU multi is always hard locked to max turbo multi amount by Intel’s evil laser
@Lost_N_BIOS
Daaamn intel!!
Also, there is something i’m curious about…there is an option in BIOS, that says “disable ME” the description is worthless, so i dont get what this actually does, i think is under ME config tab
@fairestmeat - This is why they now sell X, K, KF CPU’s.
ME Re-Flash? If yes, that is for disabling me temp for one reboot so you can fix ME FW if corrupted.
Careful messing with ME FW or you will corrupt it if you do something wrong, then that can mess up your fans, memory speed/timings, and even downclock CPU sometimes too.
If you want to update ME FW, this setting is not needed, grab whatever V11 ME FW RGN/EXTR, and grab ME System Tools V11 and in the FWUpdate folder use ME FW update tool via >> FWUpdLcl.exe -f update_file_name.bin
Please pay close attention to the warnings here for V11 - Intel Management Engine: Drivers, Firmware & System Tools
Specifically - All systems which initially come with CSME v11.0, v11.5, v11.6 or v11.7 are upgradable to v11.8 firmware.
All systems which initially come with CSME v11.10 or v11.11 are upgradable to v11.12 firmware. All systems which initially come with CSME v11.20 or v11.21 are upgradable to v11.22 firmware.
@Lost_N_BIOS
No, its something called ME state, under pch config, the description says that If disabled ME FW Will be temporarily disabled, I just don’t get why is this for, and how would affect the system.
Also, what could I get from ME update? Bug correction, optimized settings, etc, is that It?
Yes, that is the exact setting I mean, located at >> PCH-FW Configuration >> Firmware Update Configuration - It’s exact name is >> Me FW Image Re-Flash
I explained above what it’s for 
ME FW update can fix bugs, but more importantly it adds latest security fixes (ie block certain virus attacks)
@Lost_N_BIOS
Actually, the setting I’m talking about is one menu before firmware update… It says: ME state and the description is exactly: “when disabled ME will be put into ME Temporarily disbled mode” (I’m sending a pic of it).
I’m just curious about this disabled ME FW, how (if) the system would work without a ME, and the purpose of it. I imagine it’s not really a ME disable, just a strange choice of words…
Ohh, sorry, I thought you were in the submenu down below that. Yes, looks like that is a direct ME FW disable option too, that may remain until you set it back, unlike the one I mentioned (it only stays for one reboot, then resets itself, or at least should )
ME FW usually helps run a lot of things, so best to leave enabled (sometimes >> fan speeds, memory speed or timings, CPU functions, sensor reports etc)
I tried setting that exact setting to Disabled and it stuck for multiple reboots but made my boot times go up to 30 seconds + and disabled my sound completely … there must be a better way to remove this backdoor?