Hello, dear readers of the site site! My name is Roman Nahvat and I present to your attention the third and final part of the article on recovering a damaged BIOS firmware (using the Acer Aspire E1-532 laptop as an example). Before reading this part of the article, it is recommended that you familiarize yourself with and in which we disassembled the Acer Aspire E1-532 laptop, removed the motherboard from it, connected the CH341A programmer to the BIOS chip and saved the damaged BIOS firmware to a separate file. Let's continue our work by preparing a new BIOS firmware file and then write it to the BIOS chip.
Let's go to the Acer website to the Acer Aspire E1-532 laptop support page.
And we will download all available BIOS firmware.
For example, let's open the folder with firmware version 2.10.
In this folder, we see a regular exe file, let's run it.
After running the V5WE2210.exe file, we get this error window, which says that this BIOS firmware is not suitable for this laptop or computer. We do not press the OK button yet, since we need to extract the BIOS firmware file for our Acer Aspire E1-532 laptop from the V5WE2210.exe file.
Go to section C: along the way
C:\Users\Username\AppData\Local\Temp (the username can be anything, depending on the name the account was created with). In the Temp folder, we see the temporary folder 7zS2C4E.tmp, which appeared after the launch of the V5WE2210.exe file.
Let's open the 7zS2C4E.tmp folder and see the isflash.bin file in it, which is the BIOS chip firmware file. Copy this file to a flash drive.
The isflash.bin file copied to the flash drive.
The size of this BIOS firmware file is 9.45 MB.
When trying to open this firmware file in the CH341A-USB program, we get a message that the file size is larger than necessary, that is, this firmware file is too large to be used to flash the Winbond W25Q64FV chip (namely, this chip is installed on the Acer laptop motherboard Aspire E1-532).
Microcircuits can be of different volumes, let's consider this using the example of Winbond microcircuits. As can be seen from the table, the volume of the microcircuit can be 512, 256, 128, 64, 32 Mbit and so on.
The W25Q64FV chip has a capacity of 64 Mbit (or 8 MB).
Since our BIOS firmware isflash.bin file, extracted from the exe file above, weighs 9.45 MB, and the size of the BIOS chip on the Acer Aspire E1-532 laptop motherboard is 8 MB, in order to successfully restore the BIOS firmware, we need to reduce the isflash.bin file from 9.45 MB to 8 MB. For these purposes, we will use a hex editor, for example HxD. We go to the address
https://mh-nexus.de/en/downloads.php?product=HxD20
and download the installation file hex editor HxD
Click on the downloaded file and start the installation.
Install.
Installation completed.
Click on the hex shortcut of the HxD editor and run it.
Main window HxD.
We click on File-Open.
Select the isflash.bin file and click "Open"
We get the following.
In the same way, open the file of the damaged BIOS firmware isflash01.bin (which we saved in the second part of the article).
Consider carefully the structure of the isflash01.bin file. As you can see, the isflash01.bin firmware file starts with FF values (line 00000000), and in line 00000010 there are values 5A A5 F0 0F.
Now consider the structure of the isflash.bin file. We see that this firmware file starts with the values 4D 5A 00 00 (line 00000000). We need to make sure that the isflash.bin file starts exactly the same as the isflash01.bin file, that is, that the isflash.bin file starts with the values FF (line 00000000).
In the open isflash.bin file, click Search-Find.
And we search for the value 5A A5 F0 0F.
We see that the value 5A A5 F0 0F in the isflash.bin file is in line 0001F340, we also see FF values in line 0001F330 above.
Select the range of lines 00000000-0001F320 in the isflash.bin file. To do this, select Edit-Select block.
Specify the start (00000000) and end (1F320) lines of the selected range.
The selected string range is 00000000-1F320.
Delete the selected range of lines from the isflash.bin file by clicking Delete.
As you can see, after deleting the selected lines, the isflash.bin firmware file now starts exactly the same as the isflash01.bin file, namely, line 00000000 contains the values FF, and line 00000010 contains the values 5A A5 F0 0F.
Let's go back to the isflash01.bin firmware file. Scroll to the end and see that it ends with the line 007FFFF0.
If you scroll to the end of the isflash.bin file, we see that it ends with the line 009548F0.
Let's remove all lines from the isflash.bin file that are in the range 00800000-9548F0, that is, we will make the isflash.bin file end with the line 007FFFF0. Click Edit-Select block.
Specify the range of selected rows.
Selected string range 00800000-9548F0.
Delete the selected range 00800000-9548F0 by clicking Delete.
As you can see, now the isflash.bin firmware file ends with the line 007FFFF0.
Save the BIOS firmware file under a new name by selecting Save as...
Specify a name, for example isflash_new and click Save.
The new BIOS firmware file isflash_new.bin.
It should be noted that the isflash_new.bin file weighs the same as the isflash01.bin file that we saved in the second part, namely 8 MB.
Since the W25Q64FV chip, as mentioned above, has a capacity of 64 Mbit (or 8 MB), and our edited isflash_new.bin firmware file weighs 8 MB, we can start flashing. We connect the CH341A programmer to the BIOS chip in the same way as we did in the second part of the article.
We launch the CH341A-USB program. We indicate the manufacturer and model of the microcircuit and delete the old BIOS firmware by clicking "Erase".
Actually, the original method, equipment and microcodes can be found (directly instructions for AMI), and in most cases, using this method does not cause any problems and has no pitfalls, but in my practice I regularly encountered such a problem:
Those. there was a banal lack of free space inside the image. When you modify the BIOS for yourself for a specific processor, you can ignore this, because. You can always load just one microcode specifically for your processor, or delete some old microcode to free up space, but when you modify it with a stream, you need to look for another solution, a compromise.
As a compromise, I chose the following solution - we take the latest versions of microcodes for all CORE generation processors in all constructs (Celeron E, Pentium E, Core 2 Duo, Core 2 Quad, Xeon *3xxx / *5xxx) and replace them with everything that was before . The set of microcodes is as follows:
The volume of this set is only 76 kilobytes. This file was obtained by combining these files:
cpu00010676_plat00000001_ver0000060f_date20100929.bin
cpu00010676_plat00000004_ver0000060f_date20100929.bin
cpu00010676_plat00000010_ver0000060f_date20100929.bin
cpu00010676_plat00000040_ver0000060f_date20100929.bin
cpu00010677_plat00000010_ver0000070a_date20100929.bin
cpu0001067a_plat00000011_ver00000a0b_date20100928.bin
cpu0001067a_plat00000044_ver00000a0b_date20100928.bin
cpu000006f2_plat00000001_ver0000005d_date20101002.bin
cpu000006f6_plat00000001_ver000000d0_date20100930.bin
cpu000006f6_plat00000004_ver000000d2_date20101001.bin
cpu000006f7_plat00000010_ver0000006a_date20101002.bin
cpu000006f7_plat00000040_ver0000006b_date20101002.bin
cpu000006fb_plat00000001_ver000000ba_date20101003.bin
cpu000006fb_plat00000004_ver000000bc_date20101003.bin
cpu000006fb_plat00000010_ver000000ba_date20101003.bin
cpu000006fb_plat00000040_ver000000bc_date20101003.bin
cpu000006fd_plat00000001_ver000000a4_date20101002.bin
The modification procedure itself has also changed a bit and has become, if not easier, then faster:
Step 1- open the BIOS image in the MMTool program: 
Step 2- to check, go to the last tab (CPU PATCH) and look at the number of microcodes. Here they are, for example, 31 pieces: 
Step 3- go to the Replace tab and look for the “P6 Micro Code” item on it: 
Step 4- having selected the item “P6 Micro Code”, press the Ikshtsyu button, select the ncpucode.bin file described above and replace it with the Replace button: 
Step 5- to check, go to the last tab (CPU PATCH) and look at the number of microcodes. After changing the microcodes, 17 remained, the latest version: 
There is no fundamental difference with the modification order described on delidded.com. In most cases, the output is of course not the same, but the processor receives the desired microcode. Of the subjective positive points, I would only like to draw attention to the fact that the microcodes for all current processors are guaranteed to be updated, whether they are “civilian” or “server”, and there is practically no risk of receiving a message about lack of space. Although, in my practice, even for such a set of microcodes there was not enough space a couple of times, it was with the BIOS for ECS P4M900T-M and ECS P4M900T-M2 boards, which are generally compatible with the Xeon E5450.
By tradition, I publish a link to the archive with tools - (zip, 234KB). The archive contains an executable file MMTOL.exe(version 3.22 BKMOD), firmware file for all 45/65nm core/xeon processors ncpucode.bin, as well as two files 45nm.bin And 65nm.bin with microcodes only for 45nm processors and only for 65nm. The use of these files can be useful in cases where it is necessary to free up additional space in the BIOS, for example, for new firmware of some controller, network, disk, etc.
!NB: Neither the ncpucode.bin file nor the 45nm.bin/65nm.bin files support Pentium 4, Celeron (without letter indexes), Pentium D, Celeron D and Xeon W processors (Xeon 5080 for example). These are NetBrust generation processors.
Probably, today there are no users who have not heard about the BIOS. Novice users (some of them are in the state of beginners all their lives) are afraid of this very BIOS like fire and do not even know how to enter it, let alone configure it. Well, experienced users or, as they are commonly called, computer enthusiasts, not only set up the BIOS system, but also reflash it. It should be noted that the procedure for flashing the BIOS even among specialists causes a surge of adrenaline, since it is by no means safe and often poses a threat to life. However, the BIOS flashing procedure is still flowers. Far more extreme is the modding, or editing, BIOS, which will be discussed in this article.
Before starting a story about how to edit the BIOS, let's briefly recall what the BIOS is, what opportunities it provides to the user, and why update it, let alone edit it.
BIOS (Basic Input/Output System) is a basic input/output system. More precisely, the BIOS is a system for configuring and managing memory, a processor, a chipset, controllers integrated on the board, and devices connected to the board. Unlike most other programs, the BIOS is not located on the hard drive, but on a special self-powered chip on the motherboard.
A lot depends on the BIOS in a computer. In fact, the BIOS determines the system setting, which determines the functionality and performance of the PC. Often the first BIOS versions with which motherboards appear are replete with "bugs" that disappear only in subsequent versions.
The BIOS is included on every motherboard (excluding Apple motherboards), whether it's for a desktop PC or a laptop. However, it has traditionally happened that the BIOS for a laptop has a minimum of settings and is more of an informational nature. As for the BIOS of the motherboard for a desktop PC, it allows you to make a fairly large number of settings that affect both the performance of the system and its functionality. In particular, the traditional overclocking of the system, which implies an increase in the processor clock frequency, a change in the processor supply voltage, a change in the clock frequency, timings and memory supply voltage, is performed precisely in the BIOS settings. In addition, in some cases, the BIOS allows you to configure the speed of the fan installed in the processor cooler and additional fans installed in the system, configure the RAID array of hard drives if this array is based on a controller integrated into the chipset, as well as perform a host of other fine-tuning of the computer.
The BIOS is located in a ROM-memory chip (Read Only Memory), which ensures that the BIOS is always available regardless of the performance of components external to the motherboard (for example, boot disks). Because RAM (Random Access Memory) is much faster to access than ROM, many manufacturers provide automatic copying of the BIOS from ROM to RAM at power on. The area of RAM involved in this is called Shadow ROM.
Currently, most modern motherboards are equipped with Flash BIOS chips, the code in which can be rewritten using a special program. This approach provides the ability to update (firmware new version) BIOS.
There are not so many BIOS kernel manufacturers. The most common BIOSes are from AMI (American Megatrends, Inc.), AWARD, and Phoenics Technologies. Other BIOSes (from FirmWorks, Micro Firmware, etc.) are much less common. AMI BIOS currently dominates the market, so in the future we will focus on ways to flash and modify it.
Naturally, each manufacturer makes its own changes to the basic BIOS version, and, of course, one or another BIOS version is designed only for a specific product (computer or laptop) and is incompatible with other solutions.
Finally, note that BIOS chips currently use two interfaces to connect to the motherboard: either the LPC (Low Pin Connection) bus or the new SPI (Serial Peripheral Interface) bus.
All manufacturers of motherboards and laptops strongly do not recommend flashing the BIOS unless it is absolutely necessary. Moreover, representatives of service centers constantly turn to motherboard manufacturers with a request to completely block the possibility of flashing the BIOS for the user. Of course, this idea is absurd and this will never happen, but we emphasize once again that the BIOS flashing operation is not safe and can be life-threatening. If the board or laptop is working fine, then there is no point in updating the BIOS.
At the same time, situations often arise when a BIOS update is necessary. For example, you purchased a motherboard with a processor and found out that they are incompatible with each other. Most likely, the problem is that your motherboard is flashed with an old BIOS version that does not support the new processor. The only option in this case is to find the old processor and update the BIOS on the board.
In addition, each new BIOS version fixes bugs that were made in previous versions, so the BIOS update procedure is very useful.
The most secure in terms of the BIOS flashing procedure are boards from Gigabyte, ASUS and MSI, which implement protection against unsuccessful BIOS flashing. Gigabyte boards have two BIOS chips installed (DualBIOS technology), and if the BIOS is flashed incorrectly and the system cannot start, then the BIOS emergency recovery procedure from the backup chip automatically starts.
On new ASUS boards, the BIOS emergency recovery technology is called ASUS CrashFree BIOS 3. The essence of this technology is that in the event of a BIOS crash or a checksum mismatch after an unsuccessful firmware, a program is automatically launched that looks for the BIOS on a CD / DVD disk, floppy disk or flash drive (with FAT/FAT32 file system). If a file is found on some media, the recovery procedure starts automatically.
A similar technology, dubbed M-Flash, is found on MSI boards. The only difference is that the BIOS file must be on the flash drive.
All motherboard manufacturers, along with new BIOS versions, also post utilities for flashing them, as well as detailed instructions on how to flash the BIOS. Alas, there is simply no universal toolkit for flashing the BIOS. In general, there are three ways to flash the BIOS: from under DOS, from under the Windows operating system, and directly from under the BIOS.
Actually, there is not much to tell about the methods of flashing the BIOS from under the BIOS and using a proprietary utility from under the Windows operating system. Everything is simple and clear here. Moreover, flashing the BIOS from under the BIOS is the easiest and safest way, but, alas, not all manufacturers support this feature. The only exceptions are ASUS and Gigabyte.
Moreover, not all manufacturers provide their boards with utilities for flashing the BIOS from under Windows, and in some cases flashing from under DOS is the only possible way.
The method of flashing the BIOS from under DOS can be called classic, but also the most inconvenient. The fact is that, in addition to having the appropriate DOS utility, this flashing method involves booting the computer not from the hard drive, but from external media. Previously, conventional 3.5-inch boot diskettes with DOS were used for this, and along with the operating system, the BIOS file itself and the DOS utility for flashing it were written to this diskette. However, at present, 3.5-inch floppy disks, like the flop drives themselves, can be considered obsolete devices. Many modern motherboards do not even have a connector for connecting a floppy drive, and laptops with 3.5-inch floppy drives have not been produced for a long time. However, the problem of this method of flashing the BIOS is not even that. In the end, you can find a 3.5-inch floppy drive with a USB interface, but this is unlikely to solve the problem. The fact is that a modern BIOS can be several megabytes in size and simply does not fit on a floppy disk.
In principle, you can try to solve this problem by using a bootable flash drive with a DOS kernel instead of a boot floppy. But even in this case there are complications. First of all, you need to find a utility that will allow you to make the flash drive bootable, and the system files of the DOS operating system. You can find several utilities on the Internet that allow you to make bootable DOS flash drives, the most famous of which are the HP USB Disk Storage Format Tool and BootFlashDOS, which are freely available on the Web.
The HP USB Disk Storage Format Tool allows you to create bootable flash drives if you have DOS system files, which means it also requires the files themselves. However, on torrent resources you can find assemblies that include DOS system files.
If you use flash drives with a capacity of less than 4 GB, when formatting and creating a bootable flash drive using the HP USB Disk Storage Format Tool (Fig. 1), you can use the FAT or FAT32 file system, but if you use a flash drive with a capacity of more than 4 GB, then you need a file system FAT32.
Rice. 1. Create a bootable flash drive with DOS
using the HP USB Disk Storage Format Tool
The BootFlashDOS utility allows you to create bootable DOS flash drives with just one click, since all the necessary system files are already included in the utility itself (Fig. 2).
Rice. 2. Creating a bootable DOS flash drive using the BootFlashDOS utility
In principle, if a bootable flash drive with DOS is created, then there will be no problems with flashing the BIOS. It is enough to copy the DOS utility for flashing the BIOS and the BIOS file to the bootable flash drive and boot the computer from the flash drive. To boot a computer from a flash drive, you need to insert it into the PC, restart or simply turn on the computer and enter the BIOS at the boot stage to set boot from the USB Flash Drive in the settings. Further, having saved the settings, we restart the computer and, having loaded DOS, we execute the necessary command on the command line in accordance with the BIOS manufacturer's instructions.
We will give examples of executing such a command a little later, but for now we will consider another way to flash the BIOS from under DOS. It lies in the fact that instead of a bootable flash drive, a bootable CD / DVD is used. It's hardly worth reinventing the wheel here - it's better to use the ready-made Hiren`s BootCD (current version 10.4), the image of which can be downloaded from www.hirensbootcd.net. If you use Hiren`s BootCD, you will additionally need a flash drive (with the FAT or FAT32 file structure), on which the DOS utility for flashing the BIOS, and the BIOS file itself should be written.
Now let's look at the procedure for flashing the BIOS from under DOS using the example of an MSI GX640 laptop with AMI BIOS. On MSI laptops, there is only one way to flash the BIOS from under DOS using the proprietary DOS utility that comes with the BIOS file itself. Actually, all that is needed to flash the BIOS is to create a bootable flash drive, download the archive with all the necessary files from the MSI website, which includes the BIOS file, the flashing utility and the flash.bat executable file with the prescribed sequence of all actions. After that, you should unzip this archive to a bootable flash drive and, after booting from the flash drive, run the flash.bat file for execution. The main thing is that all unzipped files are in the same folder (you can unzip them to the root directory of the flash drive).
In general, it should be noted that for each type of BIOS (AMI, Award) for flashing, there are specialized utilities from AMI and Award companies. For example, from the AMI website, you can download the amiflash package, which includes the afudos and afuwin utilities that allow you to flash the AMI BIOS from DOS and from Windows, respectively. However, keep in mind that the AMI BIOS can be either a classic AMI BIOS or an AMI Aptio BIOS. Aptio is a variant of AMI BIOS, but the main thing is that different afudos and afuwin utilities are used for AMI BIOS and Aptio AMI BIOS.
In addition, many motherboard manufacturers make such significant changes to the BIOS for their products that the universal AMI or Award utilities simply do not recognize them, and therefore cannot reflash them. In particular, in the previously discussed example with the AMI BIOS of the MSI GT640 laptop, the afudos and afuwin utilities do not recognize it as an AMI BIOS and, of course, cannot reflash.
In general, the situation when it comes to modified versions of the AMI BIOS, which are defined as AMI BIOS by the AMI utilities themselves, is quite common. These are many MSI boards, and many Gigabyte boards. So far, only ASUS boards, the BIOS on which can be reflashed with utilities from AMI (although, of course, utilities supplied by ASUS itself, are better suited) have not been seen in such a "show off".
So, we have considered the main ways to flash the BIOS, and now we will discuss how to modify it. Naturally, the question arises: why modify the BIOS at all? On this occasion, one can argue ad infinitum, as well as about whether it is necessary to overclock the computer. Actually, if the BIOS modding procedure is possible in principle, there will always be enthusiasts who will do it.
A few years ago, few people thought about the possibility of self-editing the BIOS. However, this procedure has recently become popular, and you can find quite a few resources on the Internet dedicated to BIOS modding. The interest in this issue can be explained by the fact that recently many users have begun to flash the SLIC table in their BIOS, and this is one of the options for modding, or editing, the BIOS. By itself, the procedure for flashing a SLIC table into the BIOS is quite legal, but what it is done for, of course, is already illegal - this explains the popularity of this procedure.
Briefly explain what we are talking about. Flashing the SLIC table in the BIOS is used to implement the mechanism for OEM activation of the Windows 7 operating system in the same way that Microsoft OEM partners do to activate pre-installed copies of Windows without Microsoft checking. This method allows you to activate the system under three conditions: the use of a special OEM key and an OEM certificate, as well as the presence of a SLIC table in the computer's BIOS.
Windows 7 requires SLIC tables version 2.1 in the BIOS, and there is no hard binding of the OEM key to the SLIC table and certificate. The key is bound only to the Windows edition and allows you to activate both x86 and x64 versions of the OS. The filecertificate and SLIC tables are interconnected, and for successful activation, both components must be from the same OEM partner.
We will not tell you how to illegally activate Windows 7, but we will focus on the procedure for inserting a SLIC table into the BIOS. We note right away that this is far from always possible and not all BIOSes can be edited in any way.
On the Internet, you can find a package of software tools (AMITool) containing both the SLIC tables themselves and a utility (AMI SLIC Mod) for flashing them into the AMI BIOS. However, this requires that you use the AMI BIOS on your board, but even in this case there is no guarantee that the procedure for flashing the SLIC table in the BIOS will be possible. As we have already noted, many manufacturers modify the BIOS for their products in such a way that the AMI SLIC Mod utility simply does not recognize it as an AMI BIOS, and therefore cannot modify it.
However, even in this case, do not despair and run to the store for another motherboard. Before trying to flash the SLIC table in the BIOS, you should check that it is not in the BIOS. If you recently bought a motherboard or laptop, it may well turn out that the version of the SLIC table you need (version 2.1) is already in the BIOS.
You can view the version of the SLIC table in the BIOS using the specialized utility RW - Read & Write Utility (current version 1.4.7), which can be downloaded from http://rweverything.phpnet.us. Another name for this utility is RW-Everything.
After installing this utility, run it and in the main window of the program on the toolbar, click on the button labeled ACPI. In the ACPI Table window that opens, click on the SLIC tab. Next, you need to view the table in hexadecimal format and find in it a line starting with bytes 53 20. If the next four bytes are 00 00 00 00, then the SLIC table version 2.0 is flashed in the BIOS, and if it is 01 00 02 00, then the SLIC is flashed version 2.1 table (Fig. 3).
Rice. 3. Determining the version of the BIOS SLIC table
Of course, inserting a SLIC table into the BIOS is far from the only possible modding option. Another modding method is unlocking some BIOS features. Indeed, motherboard manufacturers often deliberately block some BIOS functionality in order to simplify the Setup BIOS setup procedure. They also disable those functions that are not available in a particular motherboard, but can be used in the following modifications.
Using specialized utilities, you can try to unlock all disabled features and options in the BIOS. In addition, you can change the logos (some motherboard manufacturers, such as ASUS, even supply special utilities to change the BIOS logo), as well as some names so that, for example, when booting, it does not display the real name of the processor, but something like “AMD Core i9 -995".
Another example of BIOS modding can be given. Some craftsmen manage to unlock the possibility of using the SLI mode for NVIDIA video cards on those motherboards where this mode is not provided through the BIOS. Actually, if the board officially supports the SLI mode, then its BIOS contains the corresponding key from NVIDIA. The idea of modding is to cut this key from the BIOS of the motherboard on which the SLI mode is officially supported, and paste it into the BIOS for the board on which the SLI mode is not supported (that is, in the BIOS without the NVIDIA key). In particular, there are examples of how, due to such modding, the SLI mode was activated on boards based on the Intel P45 Express chipset.
However, let's move from theory to practice and discuss BIOS editing, in particular AMI BIOS editing as the most common.
To edit a BIOS with an AMI kernel, you will need the AMIBCP utility, which, by the way, is released by AMI itself. This utility can be downloaded both separately and as part of the AMI BIOS ROM Utilities package. It should be noted that since, as we have repeatedly emphasized, motherboard and laptop manufacturers make changes to the AMI BIOS for their products, there is no guarantee that the AMIBCP utility will recognize the BIOS. Alas, not every BIOS can be modified. As practice shows, the BIOS of ASUS and ECS boards can be edited without problems, but the AMIBCP utility is powerless with respect to Gigabyte and MSI boards.
So, back to the consideration of editing the BIOS in the event that it is possible. The AMIBCP utility (version 3.x) runs under the Windows operating system, but it should be noted that there are versions of the same utility for DOS.
After downloading the utilities, you need to open the BIOS file. In our example, we will consider editing the AMI BIOS for the ASUS P6X58D-E motherboard using the AMIBCP v.3.37 utility. We will edit the P6X58DE.ROM file.
So, in the main window of the program, we load the BIOS file, which we will modify (Fig. 4).
Rice. 4. The main window of the AMIBCP v.3.37 utility
First of all, the Setup Configuration tab is interesting, in which, in fact, the BIOS settings are modified. The main BIOS settings menu is displayed in the left window of this tab. If you uncheck any menu item, it will not be displayed in the BIOS menu. In the considered example (see Fig. 4), we unchecked the Ai Tweaker and Advanced checkboxes, thus blocking all possibilities for overclocking the system. That is, the BIOS menu items, in which you can view information about the processor and memory, as well as change frequencies, supply voltage, etc., will simply be absent in the modified version of the BIOS.
The situation is similar when opening the tree structure of each item of the BIOS setup menu: if you uncheck any sub-item, it will not be displayed in the BIOS menu. For example, if we do not want the Intel PPM Configuration item to be displayed in the Advanced settings menu, we just need to uncheck the corresponding item (Fig. 5).
In order to block any option of the BIOS setup menu, it is enough to set the value No in the Show column for the corresponding item. Such blocked elements will (after saving the changes) be highlighted with a green bar.
For example, if our system does not have additional fans installed in the case and we do not want their settings to be displayed in the BIOS, then we enter the Power menu, then open the Hardware Monitor menu and for the options Chassis Fan 1 Speed, Chassis Fan 2 Speed, Chassis Fan 3 Speed, Chassis Q-Fan Profile and Power Fan Speed set the value to No in the Show column (Fig. 6).
Rice. 6. Blocking BIOS display of various setup menu options
It should be noted that the BIOS P6X58DE.ROM for the ASUS P6X58D-E board does not allow any improvements using the AMIBCP v.3.37 utility. All options in it are unlocked, so the maximum that can be done is to block what is not needed (however, it is not clear why this should be done).
You can also try to change some labels, but keep in mind that labels in Russian will not be displayed. For example, if we want the line ComputerPress P6X58D-E BIOS Edition to be displayed instead of the line ASUS P6X58D-E ACPI BIOS Revision 0106 during boot, then it is enough to find the line ASUS P6X58D-E ACPI BIOS Revision 0106 on the BIOS Strings tab and change it to the specified .
It remains for us to consider one more type of BIOS modding - changing the background image (logo) of the BIOS. At the same time, ASUS even bundles its boards with a special utility that allows you to implement this feature. Of course, for ASUS boards, it is easiest to use this particular utility. However, for AMI BIOS, you can also use the AMI OEM LOGO utility (Fig. 7).
Rice. 7. Changing the BIOS logo using the OEM LOGO utility
The interface of this utility is very simple and does not require comments. It is enough to load the BIOS and specify the path to the file with the new logo. The only limitation is that the drawing must be of a certain resolution and format.
A universal program for removing firmware and BIOS backups from any models of laptops and personal computers.
A dump should always be done when we want to make a firmware update, update, or BIOS rollback. Sometimes they ask to make a copy of the BIOS of a laptop or a personal computer motherboard in order to repair similar equipment.
And what is BIOS and how does this abbreviation stand for.
BIOS is an abbreviation for the English words Base_Input_Output_System and it translates as basic_input_output_system
Making a BIOS dump of laptops and computers using this program is very easy and simple.
Brief instructions on how to use the Universal BIOS utility Backup ToolKit 2.0 to create a bios damp, and in Russian a backup copy.
Video instructions for working with this program.
Many antiviruses detect this program as a virus, but it is not.
After downloading, you can check this archive on the website www.virustotal.com, which will say that half of the antiviruses will find various viruses in it, and the second half will not.
My AVG defines it the same as a virus. And on the beech Casper says that everything is fine.
After checking this file, see if your antivirus finds a virus in it. If so, disable it while the program is running.
Then we unpack the archive and run the resulting file with the name Universal BIOS Backup ToolKit 2.0.exe
If your system says that administrator rights are required. Then we right-click on this file and click on the item run as administrator.
After that, the program window opens, in which we see information about the type, version, size, manufacturer and date of your BIOS.
After that, press the Read button and wait until the BIOS reading process is completed.
After that, a sign will appear with the inscription that the BIOS reading was completed successfully.
We press OK. Then click the Backup button.
We are offered to choose a place where we save the BIOS dump. Select the desired folder and click the save button.
We all made a BIOS backup, you can update the version, flash a new or old stable version of the BIOS.
