blowntaha

Could you pls walk me through what I should change to test if your theory works with HM76? Link for the original bios here.

Theory is an overstatement; changing the ICC boot profile to be selected by BIOS instead of the default "soft strap" enabled BCLK access via XTU on an HM77 chipset. I just figured since it was the only additional change necessary to enable it on that specific HM77 mobo, and that this is something I have not tried on HM76 then it might be what's preventing XTU access/capability to change BCLK.

Step by step, explain-it-to-me-like-im-seven:

1. Click and drag your ME FW onto FITC.exe
   
2. Under the subsection Descriptor Map, change Number of Flash Component to zero so that only your ME FW is built/compiled
   
3. Under the subsection PCH Straps -> PCH Strap 10, change the third parameter from the bottom ICC Boot Profile Selected [...] from true to false
   
4. Done.
   

Or, you can just flash this, which I already modded. I used your stock BIOS, added the changes from the OP, and then did ^. End result is your full BIOS image.

I opened up your firmware you linked and it is not in a flash image format. You need to dump the firmware off of your system for a full image.

Hey,

I was trying to figure out Nando's post, where he quoted you (here). Looking at the already modified ME9 FW in FITC (linked on Nando's post), and comparing it to mine in ME10 FITC, I couldn't deduce which setting enabled all of registers after EOP. Could you tell me specifically what I would have to change to enable all the clocks, thus allowing me to slightly increase BCLK via XTU?

Here's two quick FITC side by side comparisons, with mine on the left (ME10), and ME9 FITC on the right,

So should I try this on my ASUS UX32VD with HM76 chipset? Could it cause something bad?

Worst case scenario you may have to bios recovery.

Ok. But I don't understand, why you wrote about HM76?

I wrote,

If you are interested, I think I know of a way to get BCLK control on HM76, PM or reply if interested.

Interested, but I don't understand, it works for HM77 or for HM76, or for both? You changed only this one setting in Descriptor region? I ask because for unlock BCLK, i always changed other setting, in ME region, and all works fine, of course only for HM77.

I don't know if this works for HM76 (don't have one anymore, to test on), but for my particular case (person who had requested me to mod), he had HM77, did only the steps listed in OP, and XTU did not have BCLK control, even after reinstallation. I did notice that he had 2 ICC profiles, by default. So, maybe this is why the extra change (soft strap to false) was necessary. After trying various things, and then eventually trying this, the BCLK option was unlocked in XTU.

Also, after he did a BIOS flash, the ME FW was flashed back to the original unmodified one, so he lost settings. Then, when I changed only the ICC registers from the ones in the OP, and setting the soft strap to false, he regained the ability to increase BCLK in XTU.

Thanks! Yea then I'm not even interested in changing BCLK, I know in the past when I've tried increasing FSB on other computers with PCI-E SATA harddrives, it would lock up very very fast. If I could unlock the multipliers, that'd be great. Were you able to do that?

If you are interested, I think I know of a way to get BCLK control on HM76, PM or reply if interested.

To anyone who is having trouble getting this to work, it might be be required to change ICC Boot Profile Selected By Soft Strap from true to false; this is located under PCH Straps->PCH Straps 10. I don't know why this works, but when I was helping someone with HM77 chipset and the instructions from OP didn't work, I tried that change and voila, it worked.

All the values are as they should be to enable BCLK control. If they aren't, then if I were you, I'd move on to try and get turbo multi control. Grab Andy's tool (aka phoenix tool), select your image, manufacturer -> structire -> look for DXE core -> Setup Utility. Check the decompress box and extract. Drag and drop that file onto this universal IFR Extractor tool credits to donovon). Open the .txt file and CTRL-F turbo and sift through to see if anything comes up that related to the multis (excluding TDP). Once/if you find the setting for the turbo multipliers, you want to write down/remember the variable name.

Ex.

Here's a small chunk of what you'd might in the txt file

Setting: DMA Channel, Variable: 0x13 {05 91 27 02 1F 01 11 00 34 12 13 00 00 10 01 03 00}

0x66834 Option: DMA 1, Value: 0x1 {09 07 28 02 00 00 01}

0x6683B Option: DMA 2, Value: 0x2 {09 07 29 02 00 00 02}

0x66842 Option: DMA 3, Value: 0x3 (default) {09 07 2A 02 10 00 03}

the Variable is 0x13. If you wanted to change it from its default value of 0x03 to 0x01. You'd boot to EFI shell. If you dont know how, heres a quick TUT

grab a usb, create folder in root dir named, EFI and inside that make another folder named Boot. Inside that, you would place

this file (after extracting). FYI, there are many other EFI shells you can boot to if this one doesn't work for you.

Once you have booted to EFI shell, you would use the setup_var command

setup_var <variable> ;this is to check if it is a valid variable with a valid value, if this checks out then,

setup_var <variable> <value>

example:

setup_var 0x13

<some output="">

setup_var 0x13 0x01

Once you change all the vars you wanted to, type exit and boot. Alternatively you can look at the much nicer and more detailed guide by Khenglish. && no, I was not able to get turbo multi control. </some></value></variable></variable>

Interesting, I opened up the ME region only .bin I posted earlier and you are correct, the changed bits aren't there (I guess the "Int" folder is no good). However, they are if I open up the full image, which I flashed. I also re-dumped the current FW and opened the image in fitc and the bits are changed. Here is my newly dumped .bin after the changes: http://s000.tinyupload.com/?file_id=61252391357967251527

I'm really just doing this to see if it's possible, not so much out of need, this is an Ultrabook after all. I would love to unlock the multipliers. The BCLK would also overclock other components right?

Yes. BCLK will also increase RAM/PCI/etc clocks as well; that being said, unless you can change ram multipliers, you probably wont be able to increase BCLK by a whole lot without being able to maintain stability. You'd most likely get more gain by changing turbo multis, with a lot less effort and risk. If you make a mistake changing a certain nvar you can just reset its value by changing or removing the part (corresponding to the nvar) for one boot.

I will take a look at your zip later as i do t have access to a pc atm

Well I built and flashed the entire FW (8mB). I figured it wasn't necessary to change the number of flash devices if I did that? I did indeed do the flashing in Windows.

Just try what i said but allow me to save you the headache and dont try too hard (unless youre confident), because you will end up with a brick like i did. IMO perf gain in actual world applications just. By increasing BCLK without ability to increase volts isnt worth the effort. And since bottlenecking isnt an issue for gpu/cpu relationship, you're better off trying to buff your gpu

Seriously!? The modified one I pulled from the "Int" (Intermediate) build folder. It creates these when building the full .bin image which I flashed.

Make sure you set "number of flash devices" to zero so thay only the ME portion is created, do all flashing and dumping in DOS. If it still doesnt work you can try extracting an IFR structure.txt file and then looking for any vars that you might want to change. Probably wont get BCLK control, but you might be able to change turbo multis

Yea I guess so. Here's my original and modified ME regions (in .zip). I just realized the modified one is much larger. I took these from the files FITC first created for the original, and from the Int folder for the new one.

Is the modified ME Region an ME dump after flashing or an exact copy of one created in FITC? Because neither image has the necessary bits set.

So I flashed my modified firmware (just built and flashed the full thing), nothing additional unlocked in XTU or ThrottleStop that I can tell. In fact, I could have sworn that in XTU, I previously could see "Reference clock - 100Mhz" greyed out but now I can't see it at all.

I tried attaching my original and modified ME regions here but it says invalid file. Tried both .bin and .rar.

If the changes that you actually made was in fact:

Clock Source Select: from 0x00011A33 to 0x00011A34

SRC Source Select: from 0x00033733 to 0x00133744

PLL Reference Clock Select: from 0x00088CBF to 0x000A8CBE

Divider Enable: from 0x000005EB to 0x000005FF

SSC Control: from 0x00010000 to 0x00000000

then you are probably SOL.

I am pretty sure that enabling BCLK OCing is either downright impossible on HM76 chipset or it requires much deeper modification (which I attempted, failed, and gave up on). Good luck on whatever you choose to do. If by chance you are worried about any possible bottlenecking then rest assured that a 3610QM did not bottleneck my GTX 970 eGPU setup.

Alright this is where I'm at with my Asus UX32VD, please help me proceed.

I've made the FW dump with fptw64.exe.

I opened it up in FITC. It's detected as "Intel 7 Series Chipset / Intel HM76 - Mobile". Someone on the previous page was having issues with a HM76 chipset?

I changed the following bits as I think this is all you changed, and this is what I saw recommended in the Intel PDF regarding overclocking in the ME section of the firmware.

ICC Data\ICC Profile 0\FCIM/BTM Specific ICC Registers:

Clock Source Select: from 0x00011A33 to 0x00011A34

SRC Source Select: from 0x00033733 to 0x00133744

PLL Reference Clock Select: from 0x00088CBF to 0x000A8CBE

Divider Enable: from 0x000005EB to 0x000005FF

SSC Control: from 0x00010000 to 0x00000000

ICC Data\ICC Profile 0\ICC Registers:

PI12BiasParms: from 0x08880888 to 0x00000888

Can you please verify this is correct? I really don't wanna brick this laptop. Also, how do I build just this portion?

I'm thinking: Build, build settings, check "build compact image". Any other settings I need to change?

Those look identical to the changes I had to make when I first stumbled upon this thread. You are good to go with those values. Just make sure you set number of flash devices to 0 at the top so that when you build your image, it will be simplified, and equal sized output image (this is how you "build just this portion").

@Tech Inferno Fan or @Khenglish

I got my flash descriptor unlocked, and I dumped my ME image in DOS using FPT, but when I was trying to copy the settings needed from the ocme.bin in the OP..... I can't tell which bits correspond to each other between ME10 and ME8. Could one of you please point me in the right direction or if you have time, modify it for me? Here is my ME dump. Thanks!

blown_ME10.zip

Wow that's pretty unlucky! Well I'll give it a shot and see if it really is our chipset that's the problem. The OP hasn't said exactly which lines to change. I opened his modded ME in fitc and the lines I changed (posted above) seem to be the only ones he changed, but I'm not sure. Could you verify?

I won't get to it until tomorrow. It's fairly straight forward, just open both your ME dump and the one Khenglish uploaded in FITC, side by side, and just copy everything in the extended ICC tabs, along with changing "number of flash devices" to zero (this will cause only the ME FW to be built instead of a bunch of different ones); it's located in one of the top sections. As long as you do just that, and assuming there is no PEBKAC and no problems with flashing, I don't see any risk unless your specific laptop model is prone to problems.. Worst case scenario, you will have to perform BIOS recovery, but I doubt it'd come to that just by making the changes I've stated. Just out of curiosity, what laptop model?

Reason I am so confident is because I have been in many soft brick scenarios, mostly with my y580, but have had experience with others as well, and I was almost always able to recover via bios recovery. Every laptop is different, proceed with the information I have provided at your own risk.

Flyview said:

Damn, yea I noticed that you were having problems. Would it hurt for me to try? Are the changes I have made sufficient? Were you trying something else when you bricked it?

Brick happened because of something stupid I did. I was trying to see if I could un-greyout some of the settings under Advanced->Extended ICC in my BIOS; all in effort to do what I couldn't do with ME FW. Basically I ungreyed some bits that were supposedly undefined, followed by a bad flash. Could have been recoverable but thunderstorm caused a temporary blackout and I forgot to put battery in. GG WP cyal8r mobo

Wouldn't hurt to try. Just do exactly was the OP says and change only things under ICC subsection along with the other one or two settings outside of that. Pretty sure chances of bricking are slim to none, assuming you only change what is stated in the post. Don't take my word for it though, I am only saying that based on what I have experienced with one motherboard, along with reading a lot of different threads on a lot of different forums ( techinferno, etc).

Alright this is where I'm at with my Asus UX32VD, please help me proceed.

I've made the FW dump with fptw64.exe.

I opened it up in FITC. It's detected as "Intel 7 Series Chipset / Intel HM76 - Mobile". Someone on the previous page was having issues with a HM76 chipset?

I changed the following bits as I think this is all you changed, and this is what I saw recommended in the Intel PDF regarding overclocking in the ME section of the firmware.

ICC Data\ICC Profile 0\FCIM/BTM Specific ICC Registers:

Clock Source Select: from 0x00011A33 to 0x00011A34

SRC Source Select: from 0x00033733 to 0x00133744

PLL Reference Clock Select: from 0x00088CBF to 0x000A8CBE

Divider Enable: from 0x000005EB to 0x000005FF

SSC Control: from 0x00010000 to 0x00000000

ICC Data\ICC Profile 0\ICC Registers:

PI12BiasParms: from 0x08880888 to 0x00000888

Can you please verify this is correct? I really don't wanna brick this laptop. Also, how do I build just this portion?

I'm thinking: Build, build settings, check "build compact image". Any other settings I need to change?

I have (or had, bricked but not beyond recovery) a y580 which is also HM76. I have spent hours and hours trying to get it to work and later learned that it is impossible to enable any sort of extended ICC control on chipsets (that Intel has labeled) which do not support overclocking. There is a chart in one of the PDFs from the IMEI system tools .zip file. I had a 3920XM in my HM76 board (it's an unlocked cpu !!) and had no more OCing capabilities than I did with my 3610QM, which is a locked cpu. Both before, and after flashing a modified ME FW, while also checking that the ICC registers were the correct values via cct.exe (from IMEI tools, and they were correct), ressulted in the same limited control in XTU/throttlestop/setFSB/etc.

I even went as far as to contact Intel and was told that it is a hardware limitation, despite the fact that firmware is supposed to control hardware, but I can't fully understand that concept so I might be wrong. You can look at my previous posts to view my progress and things I tried.

Just my two cents.

Hello, I'm hoping someone has been in a similar situation and was able to overcome it

I have an HP 15 Notebook (r210dx), with a 5200U cpu. When I boot to EFI and try to change most variables, I get an error stating the variable cannot be changed in an EFI environment; so that's a no go. I dumped my BIOS, and extracted it via hex editor; but the problem I'm having is according to the ME FW dump when viewed in FITC, the flash descriptor is already 0xFF for all of them; but according to MEinfo, they're locked && can't dump/flash via FPT either, so MEinfo should be more accurate. I also can't find the corresponding bits in hex edit either. Unless ME 10.x has different values for LOCKED (e.g. 0A 0B, 0C 0D, 08 08).

Can someone mod my ME FW or tell me what I'm doing wrong? I've attached my ME dump. Thanks in advance.

Oops, forgot to mention, WIN+left+right doesn't work for me, have tried mashing, as well as holding those keys.

me.zip

Sorry to advise that I had no luck in either trying to get UEFI vars to mod on my HP Elitebook 2570P/8470P tinkerings, nor can those BIOS be modified and flashed without it bricking the system on bootup. The BIOS is RSA protected.

The best I was able to accomplish was to unlock BCLK overclocking via a modifed MW firmware (courtesy of @Khenglish ). Dell Latitudes have far more options to modify UEFI vars.

One other thing that may help you. There is a HP utility called 'biosconfigutility'. You can run it to get a dump of the bios settings in a text file. Sometimes there are some hidden settings in the file. Then you just apply your modified text file back to biosconfigutility and reboot.

I was trying to mod my ME, but the WIN+LEFT+RIGHT isn't working for me. I have the proper BIOS dump w/ ME FW courtesy of HP's BIOS manager; problem is when I look at the ME FW in FITC, the descriptor settings arealready 0xFF. & when I open it in a hex editor and compare my dump with another FW (built in FITC, with descriptor set to LOCKED), the only differences I see are ones that are either bugged/incorrect/irrelevant. In other words, I can't find the flash descriptor bits anywhere; I remember in ME 8.x, there'd be a 0B 0A -- miscellaneous FF/00 -- 0D 0C --...

Am I looking for the wrong values? Because from what I gather, the flash descriptor bits should be in the very beginning, and should be 0B 0A, 0D 0C (or the reverse).

Here is the ME FW dump I extracted from my full BIOS dump (which was obtained from HP's BIOS management tool, so it's correct and accurate).

EDIT: I was able to dump, modify, and reflash the descriptor region, so I have read/write access to ME FW. I've attached my ME dump if someone could modify it for extended CPU control. I'd (prefer) do it myself but, but after looking at the ME10 dump in FITC, the ICC section seems very different. I'm actually working up to getting x2 link for my eGPU functional, but I figured I'd start with light CPU mods first unless someone here can tell me straight how to do it.

Thanks

blown_me.zip

Just for kicks, I'd like to try this on an old old Dell Inspiron 9300. It has a Pentium-M 1.86Ghz 533MHz FSB. I tried installing XTU but it says hardware not supported. What would I use to actually change the CPU BCLK once I unlock the bios? I don't want to change the FSB only as that quickly becomes unstable due to other components.

You could try a different version of XTU. I have a 5200U and XTU v5.x gives me hardware unsupported error, but any other version it works fine. That is, assuming you already did the ME FW step.

is Alienware included? able to volunteer...

I'd try to answer your question but you're very vague on what you're asking Alienware is included in?

@Khenglish, @Tech Inferno Fan

Do you know of a way on how to modify UEFI vars on newer HP laptops? After bricking my lenovo y580, im now on an "HP 15 notebook - r210dx" (5200U CPU, ME 10.x 1.5mb) and when I boot to grub EFI shell, and then try to change any vars, I get an error saying something along the lines of "unable to change variables in EFI environment"

Tried various combinations of disabling enabling/disabling boot, enabling/disabling legacy boot, and different USB ports but same thing. I modded a BIOS based on my dump from FPT but seeing as I'm unable to find a single BIOS update/file/ANYTHING for 'r210dx' or 'HP 15 notebook', I'm not quite sure how to flash it other than using FPT -F but using FPT to flash the whole BIOS image is scary, at least to me it is but maybe I am just inexperienced..

I don't even care for turbo multi unlocking, my main goal is to just set primary display from SG to auto & TDP MSR Lock from on to off.

I have an Acer v3-571, well actually I only have its motherboard (long story). Anyways, I was getting ready to unlock its BIOS using a good old fashioned hex editor when I came across a Russian forum where someone had already done so. The instructions for flashing it require entering BIOS recovery via special key combination upon powering on (Fn + Esc). My only problem is since I only have the motherboard and no onboard keyboard. I have already tried holding Fn+Esc with a usb keyboard, but all that seems to happen is the laptop freezing up.

That aside, I tried replacing the .rom/.bin file in the default BIOS's .exe, but when I extract it there is no .bin or .rom file for me to replace.. So, I saw

My question is, would I be able to take the unlocked BIOS, use it to replace the one in the temp folder, and then proceed to flash as normal by running insydeflash.exe without an increased chance/risk of brick? I know, I know, there is always a risk involved with these things, I just want to minimize the risk although eliminating it would be nice

Normally. It can be a different F# but normally it F5 on Dells.

it didnt work.. i think ill just try to flash an unlocked bios then go from there

Tried using the fn + f5 and so on?

What does Fn + F5 do, is that a shortcut for switching displays?

Hello,

I know this probably belongs in the Acer subforum but I'm sure other non-Acer laptops function the same way.

Background:

I had a Y580 and I bricked it, so I bought a motherboard for the v3-571 because it has an HM77 chipset (versus y580's hm76) and ability to OC cpu. I modified the DC cable from my Y580 to make it fit in the v3-571, attached a powered USB hub since it only has only one USB port, and I am using an external mouse and keyboard since I only have the mobo. I can turn it on by shorting some pins in the slot where the power button's ribbon cable would normally go.

Problem:

When I turn it on with an SSD, keyboard, mouse, and bootable USB formatted with a windows 7 installer ready to go as well as an external display connected via VGA (I tried HDMI as well). When I turn it on, the external display shows no image or any connectivity/signal. I know it is successfully booting because when I hit alt-ctrl-del, it restarts as expected and this also tells me it's still in the pre-boot stage where it didn't yet boot to OS/USB. It will also restart if I hit F9 - enter (restore defaults) - F10 - enter (save & exit). I have also tried attaching my PE4C & PE4L eGPU as a display but to no avail.

Request:

Can someone upload somewhere a picture of each BIOS tab for the v3-571's default BIOS == AND / OR == an ISO image with bare drivers installed (chipset/intel hd/etc) of either Windows 7/8/8.1; it does not matter if it is activated (I prefer unactivated) because I have my own activation keys to use.

Note:

I'm talking about Acer Aspire v3-571 NOT v3-571g. I don't know if they have different BIOS but the one I have does not have a mobile nvidia dGPU.

-Thanks

Hello,

Background:

I had a Y580 and I bricked it, so I bought a motherboard for the v3-571 because it has an HM77 chipset (versus y580's hm76) and ability to OC cpu. I modified the DC cable from my Y580 to make it fit in the v3-571, attached a powered USB hub since it only has only one USB port, and I am using an external mouse and keyboard since I only have the mobo. I can turn it on by shorting some pins in the slot where the power button's ribbon cable would normally go.

Problem:

When I turn it on with an SSD, keyboard, mouse, and bootable USB formatted with a windows 7 installer ready to go as well as an external display connected via VGA (I tried HDMI as well). When I turn it on, the external display shows no image or any connectivity/signal. I know it is successfully booting because when I hit alt-ctrl-del, it restarts as expected and this also tells me it's still in the pre-boot stage where it didn't yet boot to OS/USB. It will also restart if I hit F9 - enter (restore defaults) - F10 - enter (save & exit). I have also tried attaching my PE4C & PE4L eGPU as a display but to no avail.

Request:

Can someone upload somewhere a picture of each BIOS tab for the v3-571's default BIOS == AND / OR == an ISO image with bare drivers installed (chipset/intel hd/etc) of either Windows 7/8/8.1; it does not matter if it is activated (I prefer unactivated) because I have my own activation keys to use.

Note:

I'm talking about Acer Aspire v3-571 NOT v3-571g. I don't know if they have different BIOS but the one I have does not have a mobile nvidia dGPU.

-Thanks