Phoenix Bios Editor Pro V2 2 1 3.rar
Donald
I think I have just worked out why by manually editing the SMBios element of my Asus P5E3 Premium wifi@n bios does not effect what is shown in Geekbench. The settings are actually stored elsewhere on the motherboard and override what is actually in the bios itself. Even though I have edited the motherboard DMI, if I save the bios, the settings contained therein, are the original settings. This has the benefit of if you upgrade the bios, the modified settings remain and are independent of the bios itself. None of the manual edits I have tried with this particular bios are seen or change what has been changed by DMICFG.exe. So in simple terms, by using DMICFG.exe, I can get Geekbench to report all changes apart from the bios vendor id. Maybe that info can be saved and manually edited, I will look into that. This is what Geekbench currently reports:
The structure of the bios seems slightly different too and this may explain why AMCBCP.exe crashes when you try to open up this bios, as it finds that some elements are not in the exact place it is expecting.
You can set the Bios not to show the "Press Delete" message but there is No way of removing the "Press Tab" message. You will either have to hide it with a white border or try and make the writing black in DMICFG.exe. I'm not bothered so I'm not trying!
Even though you can use DMICFG.exe to change what is reported, which DOES effect what is seen by Geekbench, it does not change what is written to the bios. I have checked that by making changes with DMICFG, saving the bios then opening it up with MMTool and the SMBios part of the bios remains unchanged. Also, reflashing the bios with the standard Asus bios leaves my modified settings unchanged.
This is my understanding as well, DMI is independent. Which is good, as you dont have to change your DMI everytime you load a new BIOS. Thats why I was bold enough to try changing it. I tried to change the info on SMBIOS module but my I had some freezing during boot post.
First things first.... I have removed the intel logo successfully as per SticMan's instruction. Just remove the F0 module in MMtool. One thing to note is to use the MMTool ver 3.19Mod21fix. Version below this does not allow you to delete, add/insert or replace modules.
Now for some help. Would anyone care to try applying the suggestions on -bin/ul...c;f=52;t=000132 on adding New Item and New Labels in the BIOS. Most of us can't open our BIOS in AMIBCP so this would be the long way of doing it.
Adding the module FA to the bios doesn't make it play the sound! We will have to look into adding the BIOS options for enabling the sound as in the F3Jv rom. I would like to but I'm busy, the Wife just slapped a Acer Aspire One 150 on my desk and said: " Here, see if you can make this work"
I want to replace the OEM Logo of my MSI Neo2-FR P35. I thought I could remove the Intel Logo and take a BMP with a white background. But I am not sure wether if it works with my BIOS or not. I have an already modified BIOS to use multicore.
I moded the boot screen and took out the "Press tab to display BIOS POST message" from the multilanguage module. Also I removed the 'Intel' logo (module F0). all with MMtool. I tryed the OEMLOGO.exe to replace the screen but the modded BIOS will allways show CMOS setup error at boot. With MMTool theres no problem at all.
I changed the DMI information as well, to match a MacPro1,1 with DMIFCG. The info didnt show right on the program itself (showed some wierd characters instead) but all was there when I checked with CrystalDMI. Unfortunately vanilla SMBIOS doesnt pick the info by itself so I still need to use an injector. Geekbench picks all without problem thou...
Whats brand is your MB? Extract your original logo using OEMLOGO.EXE. In photoshop(if you dont have one just download GIMP) and compare the properties/attributes of the image ie. color, size, etc. and make your new image the same.
Hello, i'm trying to remove the intel logo from this bios (see attached file) and also to customize the fullscreen logo (splash image). I was unable to find any BIOS editor wich works with this BIOS, can anybody help me?
Many thanks for replying Jedric, i've tried all versions of MMTool in the page that you have suggested but all of them gives me the same error. Have you tried opening my attached file? I've readed this complete thread and followed the instructions but no luck...
I looked at the attached file and I cant open that either, how did you save that file? what model is you motherboard? best way is to get a new BIOS from the manufacturer and edit that and replace the one on your mb.
Good Evening everyone,
After hours of following old guides, and installing odd software, I believe I have found the easiest and most universal way to fully unlock Haswell-M class CPUs that utilize turbo bins.
I will do my best to explain everything, but I must warn you all that everything listed below is what I have figured out, and I am still learning. This means that this process might not work for some people. (Step 10 of the Insyde portion goes into more depth.) I am hoping I can get some input and have some people test out my method on different computers. I really want to test and ensure this method works for all Haswell mobile BIOSes, but I don't have all of the resources and knowledge to do that. I would really appreciate any help/assistance that I can get on this journey ?
Let me know if my way of explaining this is too confusing/convoluted. I struggle a bit with putting my mind into words, so I might not go fully in depth into some things that don't seem complicated to me. This post will probably be edited multiple times to make things more clear and to fix spelling errors as this is quite a lengthy post ?
Anyways, let's get started!
What is the Haswell Microcode "Bug"?
The Haswell Microcode "Bug" as it is called isn't really a bug at all, but more so an oversight that managed to slip through the cracks and end up available for us, the general consumer.
Haswell CPUs, like all other CPUs, have a few different Microcode versions as seen in the list below. Think of the Microcode as a set of very basic, but important instructions that are implemented on a higher level than other instructions that a CPU utilizes. One of the Microcode versions (306C2, better known as C20603) has a very special attribute. It allows for certain Haswell based CPUs to have a fully unlocked multiplier up to x80. I personally don't know why it is this way. It is either because this microcode was used for pre-production testing and somehow made its way to the public, or because it was a simple bug that went unnoticed until it was too late. Either way, Intel quickly realized the problem, and pushed out a newer microcode version that patched this "bug".
A few years later, people realized that this old microcode version would allow them to further push their MQ CPUs. A guide was posted over various websites, but it seems that the guide is only really intended for AMI/Phoenix BIOSes, and some of the tools listed in the original guide have been lost to time.
Despite these roadblocks, I have found a way to implement the older "bugged" microcode into both AMI/Phoenix BIOSes and Insyde BIOSes (the latter being a bit more difficult, but still possible.)
I am not entirely sure if this works for desktop CPUs (If someone could test this, I would be glad to credit you!), but I can attest that this does work for all Haswell CPUs with the MQ moniker. I plan on testing a 4210M that I have, and will update this post once I get results from using that.
There are some programs that you will need in order to perform this mod, below is a a list of the programs needed:
UEFI BIOS Updater (UBU) -guide-news-uefi-bios-updater-ubu/30357 This will be used for obtaining the "bugged" microcode version. It can also be used to obtain any other microcode versions you may want.
HxD - Freeware Hex Editor: -nexus.de/en/hxd/ This will be used for viewing and editing the BIOS and microcode files if you are modifying an Insyde BIOS.
Throttlestop version 8.70: -throttlestop/41599/download/ This older version of TS is necessary for changing the speed of the CPU as the multiplier behaves in a very odd way. Any TS version 8.x should work, but 8.7 was the newest version I could find that worked.
AMI MMTool v5.0.0.7 This tool is only needed if you are modifying an AMI/Phoenix BIOS. I cannot provide a download link here for various reasons, but just look up "MMTool Aptio 5.00.0007" and download that.
Step 1: Download or dump the BIOS you plan on modifying. For this portion, it is the E1763IMS.11D BIOS that can be found on MSI's website.
Step 2: With UBU open, put your BIOS file and AMI MMTool v5.0.0.7 into the folder with all of the other files. (Your folder may look a bit different then mine)
Step 3: Rename mmtool_v5 to "mmtool_a4" and make sure that it's a .exe file.
Step 4: Run the UBU .bat file, and go through until you get to the "Main Menu"
Step 5: Choose the number that says CPU MicroCode next to it. (For me it's usually 5)
Step 6: You should be on a prompt below. (Yours may look different then mine depending on what BIOS you are modifying, this is okay) Press V to open the list of microcode's supported through the program.
Step 7: Scroll down in the text file until you find #LGA1150 like in the picture below. Delete all of the strings besides the 306C2 string as that's the "bugged" microcode we want to keep. Save the text file when you are done.
From this:
To this:
Step 8: Go back to the UBU tab, and press F to replace the microcode in the BIOS with the the "bugged" C20603 microcode. You should be on a prompt that only has the CPUID of 306C2:
Step 9: Press R to start the replacement. Wait for it to finish, press any key to exit and then you can close out of UBU.
Step 10: To double check that the "bugged" microcode was implemented, rename the bios.bin to bios.rom and open the mmtool_a4 file we added earlier.
Step 11: Click "Load Image" and select the bios.rom that is in the UBU folder. Now go to the "CPU Patch" tab and make sure the only CPU ID is 06C2. If it is the only one, then you are good to go.
Step 12: Flash the newly modified BIOS onto the desired computer.
What we just did was replacing the newer microcode with the older "bugged" microcode in the BIOS file by using the UBU tool. This means that once you flash the BIOS, it should utilize the old "bugged" microcode.