<![CDATA[Bios Mods - The Best BIOS Update and Modification Source - Tutorials]]> https://www.bios-mods.com/forum/ Thu, 07 May 2026 12:14:40 +0000 MyBB <![CDATA[[Guide] ASUS K56CB BIOS Unlock (Advanced/Power/Chipset) using Linux/Flashrom]]> https://www.bios-mods.com/forum/Thread-Guide-ASUS-K56CB-BIOS-Unlock-Advanced-Power-Chipset-using-Linux-Flashrom Mon, 12 Jan 2026 16:40:12 -0500 Nikilite]]> https://www.bios-mods.com/forum/Thread-Guide-ASUS-K56CB-BIOS-Unlock-Advanced-Power-Chipset-using-Linux-Flashrom I successfully unlocked all hidden menus (Advanced, Chipset, Power, Thermal Configuration, etc.) on my ASUS K56CB (HM76 chipset) without using an external hardware programmer. I did this entirely from a Linux environment (Void Linux), avoiding the need for DOS boot sticks or risky Windows flashers.
Since sharing my modded BIOS file would clone my specific UUID/Serial numbers to your machine, I am sharing the exact method so you can unlock your own BIOS safely while keeping your DMI data intact.
Target: ASUS K56CB (Aptio IV BIOS)
Tools used: Flashrom (Linux), AMIBCP 4.55 (via Wine/Windows)
DISCLAIMER: Flashing the BIOS involves risk. I am not responsible for bricked devices. Ensure your battery is charged and the AC adapter is plugged in.
Step 1: Kernel Preparation
To access the internal flasher on Linux, you must boot with relaxed memory protections.
  1. Edit /etc/default/grub.
  2. Add iomem=relaxed to GRUB_CMDLINE_LINUX_DEFAULT.
    (e.g.,
    Code:
    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash iomem=relaxed"
    )
  3. Update GRUB and reboot.
Step 2: Dump the Current BIOS
The K56CB has a locked Intel ME region, so we need a layout file to tell flashrom to only touch the BIOS region.
  1. Create a file named layout.txt:

    Code:
    0x00000000:0x00000fff fd
    0x00001000:0x00002fff gbe
    0x00003000:0x001fffff me
    0x00200000:0x007fffff bios
  2. Dump your current BIOS:

    Code:
    sudo flashrom -p internal -r bios_original.bin --layout layout.txt --include bios
    KEEP A BACKUP OF THIS FILE!
Step 3: Modify with AMIBCP
  1. Open bios_original.bin in AMIBCP 4.55.
  2. Navigate to the Setup Configuration tab.
  3. Change the "Access/Use" column from 'Default/Suppressed' to USER for the menus you want (I recommend unlocking Advanced, Chipset, Power, and Thermal).
  4. Save as bios_mod.bin.
Step 4: Flash the Modded BIOS
Back in Linux, write the modified region to the chip:

Code:
sudo flashrom -p internal -w bios_mod.bin --layout layout.txt --include bios --noverify-all
Note: The --noverify-all flag is required because we are ignoring the locked ME regions.
Wait for the "VERIFIED" message.
Step 5: Post-Flash
  1. Reboot.
  2. Enter BIOS (F2).
  3. Important: Load Optimized Defaults (F9) -> Save & Exit (F10).
Results:
I now have access to:
  • cTDP Configuration (Level 1/2/3 Up/Down)
  • Fan Control / Active Trip Points (ACPI) [doesn't seem to really work]
  • DVMT Pre-Allocated memory (Graphics)
  • C-States and CFG Lock (Disabled for Undervolting on Linux)
Hope this helps anyone trying to revive this old machine]]> I successfully unlocked all hidden menus (Advanced, Chipset, Power, Thermal Configuration, etc.) on my ASUS K56CB (HM76 chipset) without using an external hardware programmer. I did this entirely from a Linux environment (Void Linux), avoiding the need for DOS boot sticks or risky Windows flashers.
Since sharing my modded BIOS file would clone my specific UUID/Serial numbers to your machine, I am sharing the exact method so you can unlock your own BIOS safely while keeping your DMI data intact.
Target: ASUS K56CB (Aptio IV BIOS)
Tools used: Flashrom (Linux), AMIBCP 4.55 (via Wine/Windows)
DISCLAIMER: Flashing the BIOS involves risk. I am not responsible for bricked devices. Ensure your battery is charged and the AC adapter is plugged in.
Step 1: Kernel Preparation
To access the internal flasher on Linux, you must boot with relaxed memory protections.
  1. Edit /etc/default/grub.
  2. Add iomem=relaxed to GRUB_CMDLINE_LINUX_DEFAULT.
    (e.g.,
    Code:
    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash iomem=relaxed"
    )
  3. Update GRUB and reboot.
Step 2: Dump the Current BIOS
The K56CB has a locked Intel ME region, so we need a layout file to tell flashrom to only touch the BIOS region.
  1. Create a file named layout.txt:

    Code:
    0x00000000:0x00000fff fd
    0x00001000:0x00002fff gbe
    0x00003000:0x001fffff me
    0x00200000:0x007fffff bios
  2. Dump your current BIOS:

    Code:
    sudo flashrom -p internal -r bios_original.bin --layout layout.txt --include bios
    KEEP A BACKUP OF THIS FILE!
Step 3: Modify with AMIBCP
  1. Open bios_original.bin in AMIBCP 4.55.
  2. Navigate to the Setup Configuration tab.
  3. Change the "Access/Use" column from 'Default/Suppressed' to USER for the menus you want (I recommend unlocking Advanced, Chipset, Power, and Thermal).
  4. Save as bios_mod.bin.
Step 4: Flash the Modded BIOS
Back in Linux, write the modified region to the chip:

Code:
sudo flashrom -p internal -w bios_mod.bin --layout layout.txt --include bios --noverify-all
Note: The --noverify-all flag is required because we are ignoring the locked ME regions.
Wait for the "VERIFIED" message.
Step 5: Post-Flash
  1. Reboot.
  2. Enter BIOS (F2).
  3. Important: Load Optimized Defaults (F9) -> Save & Exit (F10).
Results:
I now have access to:
  • cTDP Configuration (Level 1/2/3 Up/Down)
  • Fan Control / Active Trip Points (ACPI) [doesn't seem to really work]
  • DVMT Pre-Allocated memory (Graphics)
  • C-States and CFG Lock (Disabled for Undervolting on Linux)
Hope this helps anyone trying to revive this old machine]]> <![CDATA[How to Unlock Advanced BIOS Settings in InsydeH2O BIOS for 320-14IKB, 320-14ISK, 320-]]> https://www.bios-mods.com/forum/Thread-How-to-Unlock-Advanced-BIOS-Settings-in-InsydeH2O-BIOS-for-320-14IKB-320-14ISK-320 Sun, 25 Jun 2023 07:05:32 -0400 Minionguyjpro]]> https://www.bios-mods.com/forum/Thread-How-to-Unlock-Advanced-BIOS-Settings-in-InsydeH2O-BIOS-for-320-14IKB-320-14ISK-320 How to Unlock Advanced BIOS Settings in InsydeH2O BIOS for 320-14IKB, 320-14ISK, 320-15IKB (Type 80XL, Type 80YE), 320 Touch-15IKB (Type 80XN), 320-15ISK, 320-17IKB (Type 80XM), 320-17ISK, 520-15IKB (Type 80YL), Lenovo V320-17ISK, V320-17IKB (Type 80AH), B320-14IKB
This is a guide on how to unlock the advanced BIOS settings in the Lenovo laptops listed above. It is super easy and done very fast!
Downloading and Running LenovoH2O-Unlocker
  1. Download the LenovoH2O-Unlocker application from here, source is from GitHub.
  2. Open Windows Explorer.
  3. Go to the Downloads folder or to the folder where you downloaded it to.
  4. Right-click the 'Unlocker.exe' file and click 'Run as Administrator'. Without administrator rights, it is guaranteed that it fails.
  5. Let it run. If it succeeded it should say 'success'.
Booting Into the BIOS
  1. Power off your Lenovo laptop.
  2. Power on, but after you press the power button immediately keep pressing the F2 button until the BIOS appears, saying 'InsydeH2O Setup Utility'.
  3. Congratulations! There should be three new tabs: 'Main', 'Advanced' and 'Power' with many new options. You can change many settings in the BIOS now. They will stay even after you boot into the BIOS again. But also be careful, as some settings might make your system not to function properly anymore. If that is the case, you can go to 'Exit' > 'Load OS Optimized Defaults' to reset all settings to the defaults.

Long live the Lenovo IdeaPad series Big Grin !
]]> How to Unlock Advanced BIOS Settings in InsydeH2O BIOS for 320-14IKB, 320-14ISK, 320-15IKB (Type 80XL, Type 80YE), 320 Touch-15IKB (Type 80XN), 320-15ISK, 320-17IKB (Type 80XM), 320-17ISK, 520-15IKB (Type 80YL), Lenovo V320-17ISK, V320-17IKB (Type 80AH), B320-14IKB
This is a guide on how to unlock the advanced BIOS settings in the Lenovo laptops listed above. It is super easy and done very fast!
Downloading and Running LenovoH2O-Unlocker
  1. Download the LenovoH2O-Unlocker application from here, source is from GitHub.
  2. Open Windows Explorer.
  3. Go to the Downloads folder or to the folder where you downloaded it to.
  4. Right-click the 'Unlocker.exe' file and click 'Run as Administrator'. Without administrator rights, it is guaranteed that it fails.
  5. Let it run. If it succeeded it should say 'success'.
Booting Into the BIOS
  1. Power off your Lenovo laptop.
  2. Power on, but after you press the power button immediately keep pressing the F2 button until the BIOS appears, saying 'InsydeH2O Setup Utility'.
  3. Congratulations! There should be three new tabs: 'Main', 'Advanced' and 'Power' with many new options. You can change many settings in the BIOS now. They will stay even after you boot into the BIOS again. But also be careful, as some settings might make your system not to function properly anymore. If that is the case, you can go to 'Exit' > 'Load OS Optimized Defaults' to reset all settings to the defaults.

Long live the Lenovo IdeaPad series Big Grin !
]]> <![CDATA[[GUIDE]How to unlock AMI Aptio 4 BIOS with mono-GUID tabs.]]> https://www.bios-mods.com/forum/Thread-GUIDE-How-to-unlock-AMI-Aptio-4-BIOS-with-mono-GUID-tabs Wed, 08 Dec 2021 10:52:17 -0500 Maxinator500]]> https://www.bios-mods.com/forum/Thread-GUIDE-How-to-unlock-AMI-Aptio-4-BIOS-with-mono-GUID-tabs How to unlock AMI Aptio 4 BIOS with mono-GUID tabs.
Old Sony Vaio and Clevo primarily.

1. Markers in BIOS indicating success of applying such method.
The same GUID for every Formset.
[Image: marker1.png]
Data array.
[Image: marker2.png]

2. Main part.
Some background and patching.
How it was done.
It is known that changing the beforementioned sequence of bytes array allows you to unlock settings for some bios, and for some it is not. So if it exists in all Aptio 4, why even if it is filled with bytes-ones, the menus are still not available? I do not have an exact answer to this question, but I can tell you how it can be fixed!
While looking for a general difference between Sony BIOS and any others in which changing the sequence of bytes gives visible changes, I determined which patches needed to be applied.
Patching.
To reproduce that legacy logic of work of bytes array, please follow next examples.
Place 1:
[Image: 899407-D7-99-FE-43-D8-9-A21-79-EC328-CAC21.png]
Place 2:
[Image: Freeform-of-Setup.png]
Place 3:
[Image: FE612-B72-203-C-47-B1-8560-A66-D946-EB371.png]

3. Results.
Before and after.
[Image: bf.png]
If any of the tabs is empty, then you either did something wrong, or you need to set the access level in AMIBCP program.

List of utilities and programs required for patching:
1. UEFITool;
2. Universal IFR Extractor;
3. HxD.]]> How to unlock AMI Aptio 4 BIOS with mono-GUID tabs.
Old Sony Vaio and Clevo primarily.

1. Markers in BIOS indicating success of applying such method.
The same GUID for every Formset.
[Image: marker1.png]
Data array.
[Image: marker2.png]

2. Main part.
Some background and patching.
How it was done.
It is known that changing the beforementioned sequence of bytes array allows you to unlock settings for some bios, and for some it is not. So if it exists in all Aptio 4, why even if it is filled with bytes-ones, the menus are still not available? I do not have an exact answer to this question, but I can tell you how it can be fixed!
While looking for a general difference between Sony BIOS and any others in which changing the sequence of bytes gives visible changes, I determined which patches needed to be applied.
Patching.
To reproduce that legacy logic of work of bytes array, please follow next examples.
Place 1:
[Image: 899407-D7-99-FE-43-D8-9-A21-79-EC328-CAC21.png]
Place 2:
[Image: Freeform-of-Setup.png]
Place 3:
[Image: FE612-B72-203-C-47-B1-8560-A66-D946-EB371.png]

3. Results.
Before and after.
[Image: bf.png]
If any of the tabs is empty, then you either did something wrong, or you need to set the access level in AMIBCP program.

List of utilities and programs required for patching:
1. UEFITool;
2. Universal IFR Extractor;
3. HxD.]]> <![CDATA[Change BIOS Splash Screen on Aptio 3.x and 4.x (American Megatrends Inc.)]]> https://www.bios-mods.com/forum/Thread-Change-BIOS-Splash-Screen-on-Aptio-3-x-and-4-x-American-Megatrends-Inc Mon, 05 Apr 2021 06:14:27 -0400 joveaaron]]> https://www.bios-mods.com/forum/Thread-Change-BIOS-Splash-Screen-on-Aptio-3-x-and-4-x-American-Megatrends-Inc Hello! If you don't like your BIOS' splash screen, you can change it with the method I'll show you today! Take note that if you do something wrong, I won't be responsible. (sorry if my English isn't very good) First, download the ZIP file I attached. Then, read the instructions in "Instructions.rtf". In the instructions, I show you how to get your image resolution, but I showed you how to do it in Windows 10 (I'm not sure if its the same way on other versions of Windows) but if it's not, open the BMP file in MS Paint and press Ctrl + W and click on Pixels. In there you will see your image's resolution.  Thank you. (A video tutorial is coming soon)

⚠THIS TUTORIAL WILL ONLY WORK IN 64-BIT MACHINES UNLESS YOU REPLACE THE AFU FILES IN THE PROVIDED ZIP FILE⚠

If there's something wrong with the tutorial please let me know and I'll change it!

REMEMBER TO DISABLE YOUR ANTIVIRUS BEFORE DOING ANYTHING! OR ELSE FILES MIGHT GET DELETED.

.zip   BIOS SPLASH MODIFYING TOOLS.zip (Size: 1.15 MB / Downloads: 875) ]]> Hello! If you don't like your BIOS' splash screen, you can change it with the method I'll show you today! Take note that if you do something wrong, I won't be responsible. (sorry if my English isn't very good) First, download the ZIP file I attached. Then, read the instructions in "Instructions.rtf". In the instructions, I show you how to get your image resolution, but I showed you how to do it in Windows 10 (I'm not sure if its the same way on other versions of Windows) but if it's not, open the BMP file in MS Paint and press Ctrl + W and click on Pixels. In there you will see your image's resolution.  Thank you. (A video tutorial is coming soon)

⚠THIS TUTORIAL WILL ONLY WORK IN 64-BIT MACHINES UNLESS YOU REPLACE THE AFU FILES IN THE PROVIDED ZIP FILE⚠

If there's something wrong with the tutorial please let me know and I'll change it!

REMEMBER TO DISABLE YOUR ANTIVIRUS BEFORE DOING ANYTHING! OR ELSE FILES MIGHT GET DELETED.

.zip   BIOS SPLASH MODIFYING TOOLS.zip (Size: 1.15 MB / Downloads: 875) ]]> <![CDATA[[Onward Guide] How get unlocked MORE hidden tabs for old laptops with Insyde H2O]]> https://www.bios-mods.com/forum/Thread-Onward-Guide-How-get-unlocked-MORE-hidden-tabs-for-old-laptops-with-Insyde-H2O Sat, 30 Jan 2021 16:45:52 -0500 Maxinator500]]> https://www.bios-mods.com/forum/Thread-Onward-Guide-How-get-unlocked-MORE-hidden-tabs-for-old-laptops-with-Insyde-H2O This may help Insyde BIOS modders get modified SetupUtility modules with such adv. menu unlocking pattern:
Standart
[Image: N4nkz2I.png]
Just a one-byte patch somewhere at offset 0x1800006XX. Yeah? Usually opens only one or two tabs, but if you'll look at the setup utlity screenshoot from "Len_Z460_NIWEx215_x32_UlkMenus_ByCamiloml.exe" you see that BIOS no longer able to stop adding new tabs (jumping over functions after a specific stage).
More menus
[Image: Qt0tyku.png]
]]> This may help Insyde BIOS modders get modified SetupUtility modules with such adv. menu unlocking pattern:
Standart
[Image: N4nkz2I.png]
Just a one-byte patch somewhere at offset 0x1800006XX. Yeah? Usually opens only one or two tabs, but if you'll look at the setup utlity screenshoot from "Len_Z460_NIWEx215_x32_UlkMenus_ByCamiloml.exe" you see that BIOS no longer able to stop adding new tabs (jumping over functions after a specific stage).
More menus
[Image: Qt0tyku.png]
]]> <![CDATA[[Guide] How to extract binary BIOS flash chip content out of an Insyde .fd file and d]]> https://www.bios-mods.com/forum/Thread-Guide-How-to-extract-binary-BIOS-flash-chip-content-out-of-an-Insyde-fd-file-and-d Sat, 09 Jan 2021 16:42:29 -0500 manolo_number_two]]> https://www.bios-mods.com/forum/Thread-Guide-How-to-extract-binary-BIOS-flash-chip-content-out-of-an-Insyde-fd-file-and-d
The Problem came due to a stuck BIOS upgrade from version 1.10 to 1.40. The BIOS of this model is from Insyde.
To be honest, this Laptop is pretty old, but I never had such a case on my desk and there was no risk to break it even more - it was broken already. The only thing that could happen was that I'd get this PC running again, so I decided to give it a try.

First, I tried to restart the Flashin process as indicated on diverse pages, as also here: extracting the .fd file from the BIOS update on a USB-Stick and pressing special keys (Win+B, Fn+B,....) during Power-on. It was visible on the Stick's LED that the PC somehow did something on it. But I could never get to the point that the PC would beep or do anything else than switching off after a minute. I also tried the same with a similar CD in the drive, as the drive sounded as if it would do something. I tried every possible combination of keys - nothing.
All this did not work, so I needed another solution.

I stumbled across this page: https://www.rototron.info/recover-bricke...pberry-pi/
This guy is explaining very clearly how I could reprogram the Flash chip using a Raspberry Pi.
I still had a Raspberry Pi 3 in the drawer, so why not give it a try?
In his example, he had the Macronix MX25L8005 Flash IC, where in contrast, my PC used a Winbond W25Q64F. But that should be handled by the flashrom tool used on the Raspberry Pi.

I decided to solder the chip out, as I currently don't own such a clamp for contacting the SOIC8 in-circuit. Plus, several guys out there reported that due to other circuits on the board, signal level and power supply might be insufficient, if just supplied by the Pi.

There are a lot of working descriptions on how to connect this Winbond Flash IC to the Raspberry Pi, but I found this one to be fine and it worked as well: https://github.com/nopnop2002/Raspberry-W25Q64
I am not aware of the software this guy has on the page. But I used his Fritzing wiring plan.

As I had the IC soldered-out and wired to the Raspberry Pi, I just followed the instructions from the rototron page above:
Code:
flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=2000 -V

And after some other beginner-faults, flashrom showed me the result I were looking for: 
Code:
Found Flash chip "W25Q64".
- Okay, let's go.

I took a dump of the bricked Flash using
Code:
flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=2000 -V -r bricked.bin
in order to be safe if anything would happen.

Then, I were ready to flash the new content. - But which one?

I read in several comments that the .fd file in the installer .exe is the BIOS content and that it can be used the same way as a .bin file is used. So, I extracted the .fd file from the 1.40 Update and tried to flash it to the device:
Code:
flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=2000 -V -w DM10S140.FD

Unfortunately, that failed!
And the error message was really confusing:   
Code:
Error: Image size (9056560 B) doesn't match the flash chip's size (8388608 B)!

Does that mean, I can't use this file? - It seems like!

But what would I use then?
An internet search did not reveal anything new about .fd and .bin files, so I had to find the solution by myself.

Assumption was that the right content must be contained in this file.

When I open this file in 7-Zip, it turns out that it has different sections. One of them ".text" - the by far largest one - is 9054304 Bytes long. Highly probable that this further contains the content I need, plus some overhead I don't need.

What could I do in order to find that out?

Well, just out of pure luck, I also had the brick.bin flash dump. So, maybe I could find some hints in that file?
So, I openend that file using HxD:


.png   2021-01-08_20h24_42.png (Size: 10.88 KB / Downloads: 64)

So, the brick.bin file starts with one line of 0xFFs and the second line starts with "5A A5 F0 0F".
The .text file beginning is completely different. So, let's see it we can find the upper sequence in the .text file...  Tada!


.png   2021-01-08_20h28_06.png (Size: 30.37 KB / Downloads: 80)
The beginning sequence of the brick.bin is stored at offset 0x0430! Seems to work. And in the line above, there is a text saying "IFLASH_BIOSIMG". So, it really looks like there is a section marked, which contains the flash binary I need.
I erased the part before offset 0x0430 and saved the file under a new name "DM10S140.BIN".

So, let's do the same with the end of my brick.bin:


.png   2021-01-08_20h42_13.png (Size: 26.76 KB / Downloads: 43)

Interestingly, the brick.bin file size is exactly 8388608 Bytes (= 0x800000 Bytes), just as the chip size.

The file concludes with a line "0F 09 E9 1B...". Let's seek that in the .text file...

And: BAM! - That's it!


.png   2021-01-08_20h49_47.png (Size: 39.25 KB / Downloads: 51)


So, the End of the brick.bin file, Offset 0x7FFFFF is stored in the now shortened .text file at Offset 0x7FFFFF!

It seems pretty clear that everything between is my flash content and below is some text overhead I can just cut off...

Did that, and saved the file. The new "DM10S140.BIN" file now had exactly the same size as the "brick.bin" file, which made perfect sense.

I prayed once that it would work and flashed it on the device:

Code:
flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=2000 -V -w DM10S140.BIN

After some time (and many pages of output due to the -V switch :-), flashrom concluded its process:

Code:
Erase/write done.
Verifying flash... VERIFIED

Seemed like the flash had worked. Now, there was no other way than the re-assembly of the Laptop in order to get the proof.

Unsoldered the chip from the wires, soldered it back to the mainboard and assembled the PC.
And...  It is fixed and running! --> SDG


Most of this surely is not new to the readers of this forum. But I have not found anything about how to extract the .bin file from the fd file.
Maybe, some other tools do this automatically. But flashrom - or at least the implementation I were using - was not able to do so.

I believe, I am not the only person ever facing this problem, so hopefully, this will help anyone else...


In order to help others not having the necessary files, I also attach the now running Insyde BIOS 1.40 .bin file for the Toshiba Satellite C50-A-1M0 ready for flashing.

.bin   DM10S140.BIN (Size: 8 MB / Downloads: 1) ]]>
The Problem came due to a stuck BIOS upgrade from version 1.10 to 1.40. The BIOS of this model is from Insyde.
To be honest, this Laptop is pretty old, but I never had such a case on my desk and there was no risk to break it even more - it was broken already. The only thing that could happen was that I'd get this PC running again, so I decided to give it a try.

First, I tried to restart the Flashin process as indicated on diverse pages, as also here: extracting the .fd file from the BIOS update on a USB-Stick and pressing special keys (Win+B, Fn+B,....) during Power-on. It was visible on the Stick's LED that the PC somehow did something on it. But I could never get to the point that the PC would beep or do anything else than switching off after a minute. I also tried the same with a similar CD in the drive, as the drive sounded as if it would do something. I tried every possible combination of keys - nothing.
All this did not work, so I needed another solution.

I stumbled across this page: https://www.rototron.info/recover-bricke...pberry-pi/
This guy is explaining very clearly how I could reprogram the Flash chip using a Raspberry Pi.
I still had a Raspberry Pi 3 in the drawer, so why not give it a try?
In his example, he had the Macronix MX25L8005 Flash IC, where in contrast, my PC used a Winbond W25Q64F. But that should be handled by the flashrom tool used on the Raspberry Pi.

I decided to solder the chip out, as I currently don't own such a clamp for contacting the SOIC8 in-circuit. Plus, several guys out there reported that due to other circuits on the board, signal level and power supply might be insufficient, if just supplied by the Pi.

There are a lot of working descriptions on how to connect this Winbond Flash IC to the Raspberry Pi, but I found this one to be fine and it worked as well: https://github.com/nopnop2002/Raspberry-W25Q64
I am not aware of the software this guy has on the page. But I used his Fritzing wiring plan.

As I had the IC soldered-out and wired to the Raspberry Pi, I just followed the instructions from the rototron page above:
Code:
flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=2000 -V

And after some other beginner-faults, flashrom showed me the result I were looking for: 
Code:
Found Flash chip "W25Q64".
- Okay, let's go.

I took a dump of the bricked Flash using
Code:
flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=2000 -V -r bricked.bin
in order to be safe if anything would happen.

Then, I were ready to flash the new content. - But which one?

I read in several comments that the .fd file in the installer .exe is the BIOS content and that it can be used the same way as a .bin file is used. So, I extracted the .fd file from the 1.40 Update and tried to flash it to the device:
Code:
flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=2000 -V -w DM10S140.FD

Unfortunately, that failed!
And the error message was really confusing:   
Code:
Error: Image size (9056560 B) doesn't match the flash chip's size (8388608 B)!

Does that mean, I can't use this file? - It seems like!

But what would I use then?
An internet search did not reveal anything new about .fd and .bin files, so I had to find the solution by myself.

Assumption was that the right content must be contained in this file.

When I open this file in 7-Zip, it turns out that it has different sections. One of them ".text" - the by far largest one - is 9054304 Bytes long. Highly probable that this further contains the content I need, plus some overhead I don't need.

What could I do in order to find that out?

Well, just out of pure luck, I also had the brick.bin flash dump. So, maybe I could find some hints in that file?
So, I openend that file using HxD:


.png   2021-01-08_20h24_42.png (Size: 10.88 KB / Downloads: 64)

So, the brick.bin file starts with one line of 0xFFs and the second line starts with "5A A5 F0 0F".
The .text file beginning is completely different. So, let's see it we can find the upper sequence in the .text file...  Tada!


.png   2021-01-08_20h28_06.png (Size: 30.37 KB / Downloads: 80)
The beginning sequence of the brick.bin is stored at offset 0x0430! Seems to work. And in the line above, there is a text saying "IFLASH_BIOSIMG". So, it really looks like there is a section marked, which contains the flash binary I need.
I erased the part before offset 0x0430 and saved the file under a new name "DM10S140.BIN".

So, let's do the same with the end of my brick.bin:


.png   2021-01-08_20h42_13.png (Size: 26.76 KB / Downloads: 43)

Interestingly, the brick.bin file size is exactly 8388608 Bytes (= 0x800000 Bytes), just as the chip size.

The file concludes with a line "0F 09 E9 1B...". Let's seek that in the .text file...

And: BAM! - That's it!


.png   2021-01-08_20h49_47.png (Size: 39.25 KB / Downloads: 51)


So, the End of the brick.bin file, Offset 0x7FFFFF is stored in the now shortened .text file at Offset 0x7FFFFF!

It seems pretty clear that everything between is my flash content and below is some text overhead I can just cut off...

Did that, and saved the file. The new "DM10S140.BIN" file now had exactly the same size as the "brick.bin" file, which made perfect sense.

I prayed once that it would work and flashed it on the device:

Code:
flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=2000 -V -w DM10S140.BIN

After some time (and many pages of output due to the -V switch :-), flashrom concluded its process:

Code:
Erase/write done.
Verifying flash... VERIFIED

Seemed like the flash had worked. Now, there was no other way than the re-assembly of the Laptop in order to get the proof.

Unsoldered the chip from the wires, soldered it back to the mainboard and assembled the PC.
And...  It is fixed and running! --> SDG


Most of this surely is not new to the readers of this forum. But I have not found anything about how to extract the .bin file from the fd file.
Maybe, some other tools do this automatically. But flashrom - or at least the implementation I were using - was not able to do so.

I believe, I am not the only person ever facing this problem, so hopefully, this will help anyone else...


In order to help others not having the necessary files, I also attach the now running Insyde BIOS 1.40 .bin file for the Toshiba Satellite C50-A-1M0 ready for flashing.

.bin   DM10S140.BIN (Size: 8 MB / Downloads: 1) ]]> <![CDATA[BIOS Update for lenovo laptop]]> https://www.bios-mods.com/forum/Thread-BIOS-Update-for-lenovo-laptop Thu, 22 Oct 2020 18:46:27 -0400 iamdman]]> https://www.bios-mods.com/forum/Thread-BIOS-Update-for-lenovo-laptop BIOS Update for lenovo laptop
My painful experience detailed a bit further to hopefully help others

Summary of problem:
Not able to update BIOS using Lenovo BIOS Update Utility for Windows in Windows 10.  I have an older laptop e420 and new Lenovo BIOS update Utility for Windows 10 is not compatible.  With tool I get a blue screen warning.  Laptop reboots and BIOS is not updated.  Lenovo bios ISO file is in El Torito format which most Windows Apps cannot extract and Rufus tool cannot create a bootable USB from this ISO due to this format.

General idea is to create a bootable USB with your BIOS update files on this USB stick.

1) Download and install ISO Buster
https://www.isobuster.com/install.php
2) Download and install PowerIso
https://www.poweriso.com/download.php
3) Download you ISO file which is typically created in LINUX El Torito format.  For me I went here https://support.lenovo.com/do/en/downloads/ds014969 and downloaded 8huj17us.iso  (You will need to search for your specific Lenovo BIOS files but process should be similar to steps below)
4) Use IsoBuster to open 8huj17us.iso file.  Look under Bootable Disc folder you should see a file with extenstion .img for me the file was named NERO BURNING ROM.img
5) Extract the .img file to your desktop and rename it to BIOS.img to make it more obvious
6) Find your BIOS file that you want to flash to.  For me I used a modded BIOS file to remove the white list.  You may however simply be trying to update your BIOS from Lenovo BIOS file on Lenovo site.  For me my original BIOS is here: https://download.lenovo.com/ibmdl/pub/pc...uj03us.exe which I downloaded for back up purposes incase the modded BIOS had issues (highly recommended if you are flashing a modded BIOS).  My modded BIOS was here: https://www.bios-mods.com/BIOS/index.php?dir=Whitelists%2F&download=8huj04us_NWL_ByCamiloml.exe.  These both work for BIOS ID = 8HET34WW.  Again you would need to find the BIOS version from Lenovo that works for your Lenovo laptop.
7) Open BIOS.img with PowerISO tool.  PowerISO lets you add files to the .IMG file.
8) Extract your Lenovo BIOS file (and Modded BIOS file if you have it), typically they get extracted to: C:\DRIVERS\FLASH
9) Using Windows Explorer and since my BIOS ID is I then find the 8HET34WW folder under C:\DRIVERS\FLASH\8huj04us and C:\DRIVERS\FLASH\8huj03us folders, the former be my modded BIOS and the later being the Lenovo original backup BIOS.  I drag and drop each of these 8HET34WW folders to the FLASH folder in PowerISO.  If you have a modded BIOS as you drop each folder rename it right after (e.g. for me when I dropped my modded folder 8HET34WW I renamed it to 04_8HET34WW, then when dropped the original BIOS folder with the same name 8HET34WW I renamed it to 03_8HET34WW.  After each dropped I have to click SAVE in PowerISO otherwise it would crash some times.
10) Now extract .IMG file to a windows Temp Folder
11) Download Rufus https://rufus.ie/downloads/.  This tool will allow us to create a bootable USB called FreeDOS
12) Insert a spare USB Key 1G is best but can go higher if that is all you have.  Use RUFUS to create FreeDOS bootable USB.
13) When done open USB in Windows Explorer and navigate to Drivers folder
14) Create a folder called FLASH
15) Inside of FLASH folder copy all the files you extracted in step 10.  For me my 03_8HET34WW is now located at \Drivers\FLASH\03_8HET34WW
16) Your bootable USB is now ready, reboot and for me my BIOS is already set to check for USB key on boot and load it.  I think hitting F12 on startup will also do this for most people, if not google is your friend.
17) Now time to flash bios, execute the following from the FLASH folder:

PFLASH /sv /sd ./[BIOS_FILE_FOLDER]/[BIOS_FILE]

note for me this was the command:

PFLASH /sv /sd ./04_8HET34WW/$0A8H000.FL1

Heard some beeps and once DOS progressbar hit 100% was all done.

Hopefully some or all of this is useful to others.]]> BIOS Update for lenovo laptop
My painful experience detailed a bit further to hopefully help others

Summary of problem:
Not able to update BIOS using Lenovo BIOS Update Utility for Windows in Windows 10.  I have an older laptop e420 and new Lenovo BIOS update Utility for Windows 10 is not compatible.  With tool I get a blue screen warning.  Laptop reboots and BIOS is not updated.  Lenovo bios ISO file is in El Torito format which most Windows Apps cannot extract and Rufus tool cannot create a bootable USB from this ISO due to this format.

General idea is to create a bootable USB with your BIOS update files on this USB stick.

1) Download and install ISO Buster
https://www.isobuster.com/install.php
2) Download and install PowerIso
https://www.poweriso.com/download.php
3) Download you ISO file which is typically created in LINUX El Torito format.  For me I went here https://support.lenovo.com/do/en/downloads/ds014969 and downloaded 8huj17us.iso  (You will need to search for your specific Lenovo BIOS files but process should be similar to steps below)
4) Use IsoBuster to open 8huj17us.iso file.  Look under Bootable Disc folder you should see a file with extenstion .img for me the file was named NERO BURNING ROM.img
5) Extract the .img file to your desktop and rename it to BIOS.img to make it more obvious
6) Find your BIOS file that you want to flash to.  For me I used a modded BIOS file to remove the white list.  You may however simply be trying to update your BIOS from Lenovo BIOS file on Lenovo site.  For me my original BIOS is here: https://download.lenovo.com/ibmdl/pub/pc...uj03us.exe which I downloaded for back up purposes incase the modded BIOS had issues (highly recommended if you are flashing a modded BIOS).  My modded BIOS was here: https://www.bios-mods.com/BIOS/index.php?dir=Whitelists%2F&download=8huj04us_NWL_ByCamiloml.exe.  These both work for BIOS ID = 8HET34WW.  Again you would need to find the BIOS version from Lenovo that works for your Lenovo laptop.
7) Open BIOS.img with PowerISO tool.  PowerISO lets you add files to the .IMG file.
8) Extract your Lenovo BIOS file (and Modded BIOS file if you have it), typically they get extracted to: C:\DRIVERS\FLASH
9) Using Windows Explorer and since my BIOS ID is I then find the 8HET34WW folder under C:\DRIVERS\FLASH\8huj04us and C:\DRIVERS\FLASH\8huj03us folders, the former be my modded BIOS and the later being the Lenovo original backup BIOS.  I drag and drop each of these 8HET34WW folders to the FLASH folder in PowerISO.  If you have a modded BIOS as you drop each folder rename it right after (e.g. for me when I dropped my modded folder 8HET34WW I renamed it to 04_8HET34WW, then when dropped the original BIOS folder with the same name 8HET34WW I renamed it to 03_8HET34WW.  After each dropped I have to click SAVE in PowerISO otherwise it would crash some times.
10) Now extract .IMG file to a windows Temp Folder
11) Download Rufus https://rufus.ie/downloads/.  This tool will allow us to create a bootable USB called FreeDOS
12) Insert a spare USB Key 1G is best but can go higher if that is all you have.  Use RUFUS to create FreeDOS bootable USB.
13) When done open USB in Windows Explorer and navigate to Drivers folder
14) Create a folder called FLASH
15) Inside of FLASH folder copy all the files you extracted in step 10.  For me my 03_8HET34WW is now located at \Drivers\FLASH\03_8HET34WW
16) Your bootable USB is now ready, reboot and for me my BIOS is already set to check for USB key on boot and load it.  I think hitting F12 on startup will also do this for most people, if not google is your friend.
17) Now time to flash bios, execute the following from the FLASH folder:

PFLASH /sv /sd ./[BIOS_FILE_FOLDER]/[BIOS_FILE]

note for me this was the command:

PFLASH /sv /sd ./04_8HET34WW/$0A8H000.FL1

Heard some beeps and once DOS progressbar hit 100% was all done.

Hopefully some or all of this is useful to others.]]> <![CDATA[MSI 990XA GD55 BIOS mode for PCI-e M.2 Nvme SSD support (applicable to others)]]> https://www.bios-mods.com/forum/Thread-MSI-990XA-GD55-BIOS-mode-for-PCI-e-M-2-Nvme-SSD-support-applicable-to-others Fri, 26 Jun 2020 12:42:14 -0400 ilkerzeki]]> https://www.bios-mods.com/forum/Thread-MSI-990XA-GD55-BIOS-mode-for-PCI-e-M-2-Nvme-SSD-support-applicable-to-others If you experience, an old bios not supporting  Nvme ssd in the PCI-e data way then this can be usefull..

My hardware: msi 990xa gd55 motherboard, samsung evo 970 plus 500 GB M.2-nvme and Msi nvme-pci card adapter.

The way is simple, if your motherboard brand has a nvme support in the newer version as the same chipset of your old motherboard, then the nvme drivers in the bios dxe can be pull out and inserted to your old motherboards bios ...

requirements
1-Copy of your old motherboard bios
2-Nvme supporting new bios copy
3-An old flash usb disk
4-Lastest ver of UEFI tool program
5-AFUDE238 for flashing your moded bios back (can be changed acording to your brand)
6-Rufus for to prepare a bootable usb


The work:

1-Enter into bios and copy your existing ROM: as the MSI bios has a bios flash tool and have the option of bios backup, just insert a FAT32 formatted usb with just one primary patition and boot into bios, choose utilities option and get a copy of your orginal bios.

2-Exit bios and enter your OS, download UEFI tool prog

3-For MSI, 990xa dg55 board have the same chipset with 990fxa but while fxa has the nvme support xa do not.  so the goal is to extract nvme support from 990fxa and just implement to 990xa

4-Open the new bios file of 990fxa and old one of yours side to side in two seperate UEFI tool prog and compare them by opening the file tree. There are DXE driver type entries for the system drives in the subtype colum. The newer one has Nvme, NVMEINT13 and NvmeSmm drivers in this dxe section but 990xa-old one do not...

5-Choose the drivers one by one Nvme, NVMEINT13 and NvmeSmm, and right click, choose extract as is option and save the files as .ffs format

6-In your old bios file, where is the last dxe entry, there must be pad file.

.... DO NOT TRY TO INSERT FILE TO ANOTHER PLACE.....

choose the last DXE entry, rightclik, and choose insert after. Insert three of the extracted files one by one as to be the same order with orginal bios. Action colon will hold ''insert''. After then just save as a new file and exit UEFI toolkit.

The total file sizes must be exact the same before and after insertion of the drives. If not it means samething go wrong and just make it again....

----------------
IMPORTANT : If your motherboard do not have same chipset nvme support or u can not find bios file, there are avaible Nvme support drivers in the form of bios insertable *.ffs files. But the drives you find may not be compatable with your system and you have to try more than one to find the suitable one....

https://onedrive.live.com/?authkey=%21ABsFwc0otsoLx3k&id=5014229B9E752333%2128813&cid=5014229B9E752333
------------------

7-With rufus prepare a bootable FAT32  free dos based usb, then copy new modded bios file and afude238.exe

8-insert the usb and boot, .....DO NOT USE THE INTEGRATED FLASH UPDATE UTILITY IN THE BIOS... When booted  usb must get the control and Dos enviroment will come...

9-flash the bios from the command prompt of dos and reboot

10-Boot into bios and make sata option AHCI or raid (it may change acording to pci card type or Nvme ssd i do not know but i have a raid system sata raid works for me) as M.2 Nvme  ssd will be an UEFI system with GPT if u plan to install Win 10, raid rom must not be legacy, menu differs along motherboards...

11-For win 7 you must load the needed nvme and sata ahci raid drivers during win install, but win 10 do not need.
 

thats all....]]> If you experience, an old bios not supporting  Nvme ssd in the PCI-e data way then this can be usefull..

My hardware: msi 990xa gd55 motherboard, samsung evo 970 plus 500 GB M.2-nvme and Msi nvme-pci card adapter.

The way is simple, if your motherboard brand has a nvme support in the newer version as the same chipset of your old motherboard, then the nvme drivers in the bios dxe can be pull out and inserted to your old motherboards bios ...

requirements
1-Copy of your old motherboard bios
2-Nvme supporting new bios copy
3-An old flash usb disk
4-Lastest ver of UEFI tool program
5-AFUDE238 for flashing your moded bios back (can be changed acording to your brand)
6-Rufus for to prepare a bootable usb


The work:

1-Enter into bios and copy your existing ROM: as the MSI bios has a bios flash tool and have the option of bios backup, just insert a FAT32 formatted usb with just one primary patition and boot into bios, choose utilities option and get a copy of your orginal bios.

2-Exit bios and enter your OS, download UEFI tool prog

3-For MSI, 990xa dg55 board have the same chipset with 990fxa but while fxa has the nvme support xa do not.  so the goal is to extract nvme support from 990fxa and just implement to 990xa

4-Open the new bios file of 990fxa and old one of yours side to side in two seperate UEFI tool prog and compare them by opening the file tree. There are DXE driver type entries for the system drives in the subtype colum. The newer one has Nvme, NVMEINT13 and NvmeSmm drivers in this dxe section but 990xa-old one do not...

5-Choose the drivers one by one Nvme, NVMEINT13 and NvmeSmm, and right click, choose extract as is option and save the files as .ffs format

6-In your old bios file, where is the last dxe entry, there must be pad file.

.... DO NOT TRY TO INSERT FILE TO ANOTHER PLACE.....

choose the last DXE entry, rightclik, and choose insert after. Insert three of the extracted files one by one as to be the same order with orginal bios. Action colon will hold ''insert''. After then just save as a new file and exit UEFI toolkit.

The total file sizes must be exact the same before and after insertion of the drives. If not it means samething go wrong and just make it again....

----------------
IMPORTANT : If your motherboard do not have same chipset nvme support or u can not find bios file, there are avaible Nvme support drivers in the form of bios insertable *.ffs files. But the drives you find may not be compatable with your system and you have to try more than one to find the suitable one....

https://onedrive.live.com/?authkey=%21ABsFwc0otsoLx3k&id=5014229B9E752333%2128813&cid=5014229B9E752333
------------------

7-With rufus prepare a bootable FAT32  free dos based usb, then copy new modded bios file and afude238.exe

8-insert the usb and boot, .....DO NOT USE THE INTEGRATED FLASH UPDATE UTILITY IN THE BIOS... When booted  usb must get the control and Dos enviroment will come...

9-flash the bios from the command prompt of dos and reboot

10-Boot into bios and make sata option AHCI or raid (it may change acording to pci card type or Nvme ssd i do not know but i have a raid system sata raid works for me) as M.2 Nvme  ssd will be an UEFI system with GPT if u plan to install Win 10, raid rom must not be legacy, menu differs along motherboards...

11-For win 7 you must load the needed nvme and sata ahci raid drivers during win install, but win 10 do not need.
 

thats all....]]> <![CDATA[guide for mod bios hp insyde on my experience]]> https://www.bios-mods.com/forum/Thread-guide-for-mod-bios-hp-insyde-on-my-experience Sat, 16 May 2020 06:14:04 -0400 leolift]]> https://www.bios-mods.com/forum/Thread-guide-for-mod-bios-hp-insyde-on-my-experience after about 1 month, my request to unlock my HP Insyde BIOS was ignored, so I tried to study independently via this forum or other forums on the web.
I have come to good results to unlock several hidden BIOS features.
I would like to list the various notions learned in order to facilitate the lives of other interested parties.

i am working on a hp 630 with bios insyde.

the bios insyde seems to be one of the most difficult to unlock besides the fact that many of these bios have an RSA signature which makes changes impossible ...
in my case they managed to find in the bios network for my pc RSA and so I have worked on this.

HP 630

HP Compaq 630 - Mini 430 - Compaq Presario CQ43-414TU BDMaster
HP Mini 430 - Compaq 630 - Compaq Presario CQ43-414TU BDMaster

Versione Data Dimensione SoftPaq
F.39 12-2013 sp64612.exe RSA
F.38 03-2013 sp60723.exe RSA
F.37 11-2012 sp59757.exe RSA
F.33 01-2012 sp55626.exe RSA
F.32 11-2011 sp55356.exe RSA
F.24 10-2011 sp54776.exe RSA
F.23 09-2011 sp54697.exe RSA
F.22 08-2011 sp54181.exe RSA
F.19 07-2011 sp53673.exe possiamo bios mod
F.18 06-2011 sp53593.exe possiamo bios mod
F.17 06-2011 sp53383.exe possiamo bios mod
F.16 05-2011 sp53108.exe possiamo bios mod
F.02 03-2011 sp52301.exe possiamo bios mod

so I worked on sp53673.exe (no rsa)
this .exe is multi Fd. (fd is the unit of the bios proper and in my case within the executable of qull there are 3 different models, mine is 03676.fd)
to eject this exe file just open it with win rar or 7zip.
I learned several tricks to unlock hidden functions, but I really had to be a web astronaut.
with the "fd" file we have to try to extract it with what in the network is called "Andy tool" is a tool that opens the fd file, dumps and can therefore cook the updated fd file with the changes made by us.

link image: https://ibb.co/TKsgDg0

press ok, in the root directory of the FD file there will be new files and folders.
DUMP inside there will be many files ... to unlock the hidden functions when we are interested and almost always a file ending in FE...670_ (Module) and then with numbers (Checksums)
in my case it's called like this:

FE3542FE-C1D3-4EF8-657C-8048606FF670_649.ROM (SetupUtility)

of these, there may be more than one, but we must identify the larger one.
Ok now with a new tool called Universal IFR Extractor.exe created by Mr. Donovan6k we should read the identified ROM file.
The Universal IFR Extractor converts the code into human-readable data so that we can include the variables that condition the functions of our BIOS.
Now we will have a .txt file with what we will have to understand in our functions:

I have shortened the text file for space reasons, I just want to show an example of the system configuration field.

Code:
                               EFI Protocol Detected
--------------------------------------------------------------------------------

                               String Packages
--------------------------------------------------------------------------------
Offset:        Language:
--------------------------------------------------------------------------------
0xF080        eng
0x1BA68        fra
0x2941A        chn
0x31DEE        jpn
0x3E33C        ita
0x4B3B8        spa
0x59222        ger
0x66758        por

                                  Form Sets
--------------------------------------------------------------------------------
Offset:        Title:
--------------------------------------------------------------------------------
0x73450        Main (0xE9)
0x735D0        Exit (0x365)
0x73700        System Configuration (0x5B)
0x73DD0        Power (0x2E5)
0x746D0        Security (0x36)
0x747C0        Advanced (0xFB)
0x77B10        Main (0x4)
0x77DD0        Diagnostics (0x42)

                        Internal Forms Representation
--------------------------------------------------------------------------------
Offset:        Instruction:
--------------------------------------------------------------------------------

0x73706 Form Set: System Configuration {0E 24 F4 27 4A A0 00 DF 42 4D B5 52 39 51 13 02 11 3D 5B 00 DA 00 00 00 00 00 00 00 00 00 01 00 00 00 BC 02}
0x7372A     Form: System Configuration, Form ID: 0x1 {01 06 01 00 5B 00}
0x73730         Subtitle:   {02 04 DA 00}
0x73734         Suppress If: {0A 03 00}
0x73737         true {27 02}
0x73739             Setting: UEFI Boot, Variable: 0x7E[1] {05 09 7E 00 01 D6 00 D7 00}
0x73742                 Option: Enabled, Value: 0x0 {09 09 DC 00 00 00 01 00 00}
0x7374B                 Option: Disabled, Value: 0x1 {09 09 DB 00 01 00 00 00 00}
0x73754             End of Options {10 02}
0x73756             Setting: Quick Boot, Variable: 0x72[1] {05 09 72 00 01 48 03 49 03}
0x7375F                 Option: Enabled, Value: 0x1 {09 09 DC 00 01 00 01 00 00}
0x73768                 Option: Disabled, Value: 0x0 {09 09 DB 00 00 00 00 00 00}
0x73771             End of Options {10 02}
0x73773             Setting: Quiet Boot, Variable: 0x73[1] {05 09 73 00 01 4A 03 4B 03}
0x7377C                 Option: Enabled, Value: 0x1 {09 09 DC 00 01 00 01 00 00}
0x73785                 Option: Disabled, Value: 0x0 {09 09 DB 00 00 00 00 00 00}
0x7378E             End of Options {10 02}
0x73790             Setting: PXE Boot to LAN, Variable: 0x74[1] {05 09 74 00 01 4C 03 4D 03}
0x73799                 Option: Disabled, Value: 0x0 {09 09 DB 00 00 00 01 00 00}
0x737A2                 Option: Enabled, Value: 0x1 {09 09 DC 00 01 00 00 00 00}
0x737AB             End of Options {10 02}
0x737AD         End If {18 02}

Method 1

if you want to try to take risks that I don't feel responsible for the damage you can do to your PC, and it would be a good thing to make sure that the BIOS is reset with a keyboard,
or even to have a terminal with a programmer to repair the bios in case something goes wrong.
In my case, for example, in the System Configuration tab, the startup function of Eufi is not visible and to unlock it and make it appear we have to make the variable false:
 
0x73706 Module set: System configuration {0E 24 F4 27 4A A0 00 DF 42 4D B5 52 39 51 13 02 11 3D 5B 00 FROM 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 01 00 00 00 BC 02}

0x7372A Module: System configuration, Module ID: 0x1 {01 06 01 00 5B 00}
0x73730 Subtitles: {02 04 DA 00}
0x73734 Suppress if: {0A 03 00}
0x73737 true {27 02} <--------- we must make it false by changing 28 instead of 27

so now with a hexadecimal software like hxd, i have to change this value ...

I open the file (in my case) FE3542FE-C1D3-4EF8-657C-8048606FF670_649.ROM
identified at the beginning and we open it in HxD, we go to offset 0x73737 (always in my case) and change the value from 27 to 28. and save.

we make a copy of this file, on the desktop, let's go back to Andy's tool and select these parameters :

link image1: https://ibb.co/V2MWHLX

linnk iimage2: https://ibb.co/QNmLX4N

link image3: https://ibb.co/FzcYpQZ

After the informational message, not replaced ok, you have to go to the directory of the "fd" file in the dump folder and replace the installed "rom" file and only now do ok.
Now in the folder we have several files, one of which with the name 03676_SLIC.fd, we rename it by deleting _slic and we insert this file in the original folder for the flash.
Now we can flash the new BIOS, I found a patch that allows me to do it ... it would be a change to be made to the iscflash.dll file

Method 2

There are functions, however, that cannot be unlocked with this method because they have another function that blocks them ...
for example, the Vurtualization technology in my case is blocked by this formula:

0x73800 Label: 0x1001 {1D 04 01 10}
0x73804 Suppress if: {0A 03 00}
0x73807 Variable 0x225 [1] equal to 0x0 {12 07 25 02 01 00 00} <--------------------- change change this variable
0x7380E Setting: virtualization technology, variable: 0x1B0 [1] {05 09 B0 01 01 5C 00 5D 00}
0x73817 Option: enabled, value: 0x1 {09 09 83 00 01 00 04 45 00}
0x73820 Option: disabled, value: 0x0 {09 09 84 00 00 00 05 45 00}
0x73829 End of options {10 02}
0x7382B End If {18 02}

In my case the number 45 will have to be changed to FF, so open Hxd change the value in the offset and repeat the procedure as above with the useful tool.

Method 3

these changes can also be made in other ways, without flashing the BIOS, but modifying the one already present, the shell method exists, in my case it didn't work,
so you can use the H2Ouve.exe software:

iimage link: https://ibb.co/25tMhrm

We always work on virtualization technology that the default on my laptop is disabled.
We have seen above that the variable is:

0x73807 Variable 0x225

and if deactivated the value is 00 if activated the value is 01
so to understand where to modify this variable on H2Ouve we have to take the variable 0x225 and go to the column in 220 and to the row number 5 and insert the value 01

link image: https://ibb.co/Q8TnXnn

in this case you just have to save and the setting will be saved in the BIOS.
It's not permanent if we wanted to delete it, just reset to reset the settings from the BIOS or by disconnecting the cmos battery.

unlock advanced and power boards

The methods described above do not unlock the functions of the hidden tabs as often happens (Advanced and power) but unlocking are the hidden functions of the active tabs.
To unlock the hidden cards I was still helped by Mr. Donovan with his guide even if generic and therefore they did not work for my laptop but they are close (at least I hope),
but there are neighbors (at least I hope), for this we need another softwrae called ida.exe.
It does nothing but disassemble and show us the various sequences using flowcharts to make us understand how the logic of our BIOS works.

link image: https://ibb.co/ygm5Lgb

in my case the 1800747C0 is the offset of the tabs advanced variable

link image: https://ibb.co/xzbbfp5 in this image the call is shown

In theory with this method you would need JZ (conditional jumps) and in a certain sense bypass them. I have not found them in mine, and here I ask the help of someone more experienced.

link image: https://ibb.co/BLY4DXB

I don't know how to proceed, but I feel I am very close to the solution ...

The Solution :

Code:
Bios v.F.16 Model 03672 Menu Tabs Unlock Mod :

                                   Form Sets
--------------------------------------------------------------------------------
Offset:        Name:
--------------------------------------------------------------------------------
0x12300        Exit (0x158)
0x12430        System Configuration (0x5B)
0x12B10        Power (0x38E)
0x133D0        Diagnostics (0x42)
0x13440        Security (0x36)
0x13530        Advanced (0x182)
0x17730        Main (0xD0)
0x17890        Main (0x4)

065D : 74 5B  to  74 00               jz      short loc_1800006BA  to  jz  $+2
0668 : 74 50  to  74 00               jz      short loc_1800006BA  to  jz  $+2
0673 : 74 45  to  74 00               jz      short loc_1800006BA  to  jz  $+2


Code:
Bios v.F.16 Model 03674 Menu Tabs Unlock Mod :

                                   Form Sets
--------------------------------------------------------------------------------
Offset:        Name:
--------------------------------------------------------------------------------
0x80400        Main (0xE8)
0x806C0        Exit (0x384)
0x807D0        System Configuration (0x5B)
0x80E90        Power (0x301)
0x813D0        Security (0x36)
0x814C0        Advanced (0xF5)
0x85350        Diagnostics (0x42)

0651 : 74 50  to  74 00     jz      short loc_1800006A3  to  jz $+2
065C : 74 45  to  74 00     jz      short loc_1800006A3  to  jz $+2


Code:
Bios v.F.16 Model 03676 Menu Tabs Unlock Mod :

                                   Form Sets
--------------------------------------------------------------------------------
Offset:        Name:
--------------------------------------------------------------------------------
0x73450        Main (0xE9)
0x735D0        Exit (0x365)
0x73700        System Configuration (0x5B)
0x73DD0        Power (0x2E5)
0x746D0        Security (0x36)
0x747C0        Advanced (0xFB)
0x77B10        Main (0x4)
0x77DD0        Diagnostics (0x42)

067B : 74 55  to  74 00               jz      short loc_1800006D2  to  jz $+2
0685 : 74 4B  to  74 00               jz      short loc_1800006D2  to  jz $+2
068F : 74 41  to  74 00               jz      short loc_1800006D2  to  jz $+2


It will helps many users !
Regards]]> after about 1 month, my request to unlock my HP Insyde BIOS was ignored, so I tried to study independently via this forum or other forums on the web.
I have come to good results to unlock several hidden BIOS features.
I would like to list the various notions learned in order to facilitate the lives of other interested parties.

i am working on a hp 630 with bios insyde.

the bios insyde seems to be one of the most difficult to unlock besides the fact that many of these bios have an RSA signature which makes changes impossible ...
in my case they managed to find in the bios network for my pc RSA and so I have worked on this.

HP 630

HP Compaq 630 - Mini 430 - Compaq Presario CQ43-414TU BDMaster
HP Mini 430 - Compaq 630 - Compaq Presario CQ43-414TU BDMaster

Versione Data Dimensione SoftPaq
F.39 12-2013 sp64612.exe RSA
F.38 03-2013 sp60723.exe RSA
F.37 11-2012 sp59757.exe RSA
F.33 01-2012 sp55626.exe RSA
F.32 11-2011 sp55356.exe RSA
F.24 10-2011 sp54776.exe RSA
F.23 09-2011 sp54697.exe RSA
F.22 08-2011 sp54181.exe RSA
F.19 07-2011 sp53673.exe possiamo bios mod
F.18 06-2011 sp53593.exe possiamo bios mod
F.17 06-2011 sp53383.exe possiamo bios mod
F.16 05-2011 sp53108.exe possiamo bios mod
F.02 03-2011 sp52301.exe possiamo bios mod

so I worked on sp53673.exe (no rsa)
this .exe is multi Fd. (fd is the unit of the bios proper and in my case within the executable of qull there are 3 different models, mine is 03676.fd)
to eject this exe file just open it with win rar or 7zip.
I learned several tricks to unlock hidden functions, but I really had to be a web astronaut.
with the "fd" file we have to try to extract it with what in the network is called "Andy tool" is a tool that opens the fd file, dumps and can therefore cook the updated fd file with the changes made by us.

link image: https://ibb.co/TKsgDg0

press ok, in the root directory of the FD file there will be new files and folders.
DUMP inside there will be many files ... to unlock the hidden functions when we are interested and almost always a file ending in FE...670_ (Module) and then with numbers (Checksums)
in my case it's called like this:

FE3542FE-C1D3-4EF8-657C-8048606FF670_649.ROM (SetupUtility)

of these, there may be more than one, but we must identify the larger one.
Ok now with a new tool called Universal IFR Extractor.exe created by Mr. Donovan6k we should read the identified ROM file.
The Universal IFR Extractor converts the code into human-readable data so that we can include the variables that condition the functions of our BIOS.
Now we will have a .txt file with what we will have to understand in our functions:

I have shortened the text file for space reasons, I just want to show an example of the system configuration field.

Code:
                               EFI Protocol Detected
--------------------------------------------------------------------------------

                               String Packages
--------------------------------------------------------------------------------
Offset:        Language:
--------------------------------------------------------------------------------
0xF080        eng
0x1BA68        fra
0x2941A        chn
0x31DEE        jpn
0x3E33C        ita
0x4B3B8        spa
0x59222        ger
0x66758        por

                                  Form Sets
--------------------------------------------------------------------------------
Offset:        Title:
--------------------------------------------------------------------------------
0x73450        Main (0xE9)
0x735D0        Exit (0x365)
0x73700        System Configuration (0x5B)
0x73DD0        Power (0x2E5)
0x746D0        Security (0x36)
0x747C0        Advanced (0xFB)
0x77B10        Main (0x4)
0x77DD0        Diagnostics (0x42)

                        Internal Forms Representation
--------------------------------------------------------------------------------
Offset:        Instruction:
--------------------------------------------------------------------------------

0x73706 Form Set: System Configuration {0E 24 F4 27 4A A0 00 DF 42 4D B5 52 39 51 13 02 11 3D 5B 00 DA 00 00 00 00 00 00 00 00 00 01 00 00 00 BC 02}
0x7372A     Form: System Configuration, Form ID: 0x1 {01 06 01 00 5B 00}
0x73730         Subtitle:   {02 04 DA 00}
0x73734         Suppress If: {0A 03 00}
0x73737         true {27 02}
0x73739             Setting: UEFI Boot, Variable: 0x7E[1] {05 09 7E 00 01 D6 00 D7 00}
0x73742                 Option: Enabled, Value: 0x0 {09 09 DC 00 00 00 01 00 00}
0x7374B                 Option: Disabled, Value: 0x1 {09 09 DB 00 01 00 00 00 00}
0x73754             End of Options {10 02}
0x73756             Setting: Quick Boot, Variable: 0x72[1] {05 09 72 00 01 48 03 49 03}
0x7375F                 Option: Enabled, Value: 0x1 {09 09 DC 00 01 00 01 00 00}
0x73768                 Option: Disabled, Value: 0x0 {09 09 DB 00 00 00 00 00 00}
0x73771             End of Options {10 02}
0x73773             Setting: Quiet Boot, Variable: 0x73[1] {05 09 73 00 01 4A 03 4B 03}
0x7377C                 Option: Enabled, Value: 0x1 {09 09 DC 00 01 00 01 00 00}
0x73785                 Option: Disabled, Value: 0x0 {09 09 DB 00 00 00 00 00 00}
0x7378E             End of Options {10 02}
0x73790             Setting: PXE Boot to LAN, Variable: 0x74[1] {05 09 74 00 01 4C 03 4D 03}
0x73799                 Option: Disabled, Value: 0x0 {09 09 DB 00 00 00 01 00 00}
0x737A2                 Option: Enabled, Value: 0x1 {09 09 DC 00 01 00 00 00 00}
0x737AB             End of Options {10 02}
0x737AD         End If {18 02}

Method 1

if you want to try to take risks that I don't feel responsible for the damage you can do to your PC, and it would be a good thing to make sure that the BIOS is reset with a keyboard,
or even to have a terminal with a programmer to repair the bios in case something goes wrong.
In my case, for example, in the System Configuration tab, the startup function of Eufi is not visible and to unlock it and make it appear we have to make the variable false:
 
0x73706 Module set: System configuration {0E 24 F4 27 4A A0 00 DF 42 4D B5 52 39 51 13 02 11 3D 5B 00 FROM 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 01 00 00 00 BC 02}

0x7372A Module: System configuration, Module ID: 0x1 {01 06 01 00 5B 00}
0x73730 Subtitles: {02 04 DA 00}
0x73734 Suppress if: {0A 03 00}
0x73737 true {27 02} <--------- we must make it false by changing 28 instead of 27

so now with a hexadecimal software like hxd, i have to change this value ...

I open the file (in my case) FE3542FE-C1D3-4EF8-657C-8048606FF670_649.ROM
identified at the beginning and we open it in HxD, we go to offset 0x73737 (always in my case) and change the value from 27 to 28. and save.

we make a copy of this file, on the desktop, let's go back to Andy's tool and select these parameters :

link image1: https://ibb.co/V2MWHLX

linnk iimage2: https://ibb.co/QNmLX4N

link image3: https://ibb.co/FzcYpQZ

After the informational message, not replaced ok, you have to go to the directory of the "fd" file in the dump folder and replace the installed "rom" file and only now do ok.
Now in the folder we have several files, one of which with the name 03676_SLIC.fd, we rename it by deleting _slic and we insert this file in the original folder for the flash.
Now we can flash the new BIOS, I found a patch that allows me to do it ... it would be a change to be made to the iscflash.dll file

Method 2

There are functions, however, that cannot be unlocked with this method because they have another function that blocks them ...
for example, the Vurtualization technology in my case is blocked by this formula:

0x73800 Label: 0x1001 {1D 04 01 10}
0x73804 Suppress if: {0A 03 00}
0x73807 Variable 0x225 [1] equal to 0x0 {12 07 25 02 01 00 00} <--------------------- change change this variable
0x7380E Setting: virtualization technology, variable: 0x1B0 [1] {05 09 B0 01 01 5C 00 5D 00}
0x73817 Option: enabled, value: 0x1 {09 09 83 00 01 00 04 45 00}
0x73820 Option: disabled, value: 0x0 {09 09 84 00 00 00 05 45 00}
0x73829 End of options {10 02}
0x7382B End If {18 02}

In my case the number 45 will have to be changed to FF, so open Hxd change the value in the offset and repeat the procedure as above with the useful tool.

Method 3

these changes can also be made in other ways, without flashing the BIOS, but modifying the one already present, the shell method exists, in my case it didn't work,
so you can use the H2Ouve.exe software:

iimage link: https://ibb.co/25tMhrm

We always work on virtualization technology that the default on my laptop is disabled.
We have seen above that the variable is:

0x73807 Variable 0x225

and if deactivated the value is 00 if activated the value is 01
so to understand where to modify this variable on H2Ouve we have to take the variable 0x225 and go to the column in 220 and to the row number 5 and insert the value 01

link image: https://ibb.co/Q8TnXnn

in this case you just have to save and the setting will be saved in the BIOS.
It's not permanent if we wanted to delete it, just reset to reset the settings from the BIOS or by disconnecting the cmos battery.

unlock advanced and power boards

The methods described above do not unlock the functions of the hidden tabs as often happens (Advanced and power) but unlocking are the hidden functions of the active tabs.
To unlock the hidden cards I was still helped by Mr. Donovan with his guide even if generic and therefore they did not work for my laptop but they are close (at least I hope),
but there are neighbors (at least I hope), for this we need another softwrae called ida.exe.
It does nothing but disassemble and show us the various sequences using flowcharts to make us understand how the logic of our BIOS works.

link image: https://ibb.co/ygm5Lgb

in my case the 1800747C0 is the offset of the tabs advanced variable

link image: https://ibb.co/xzbbfp5 in this image the call is shown

In theory with this method you would need JZ (conditional jumps) and in a certain sense bypass them. I have not found them in mine, and here I ask the help of someone more experienced.

link image: https://ibb.co/BLY4DXB

I don't know how to proceed, but I feel I am very close to the solution ...

The Solution :

Code:
Bios v.F.16 Model 03672 Menu Tabs Unlock Mod :

                                   Form Sets
--------------------------------------------------------------------------------
Offset:        Name:
--------------------------------------------------------------------------------
0x12300        Exit (0x158)
0x12430        System Configuration (0x5B)
0x12B10        Power (0x38E)
0x133D0        Diagnostics (0x42)
0x13440        Security (0x36)
0x13530        Advanced (0x182)
0x17730        Main (0xD0)
0x17890        Main (0x4)

065D : 74 5B  to  74 00               jz      short loc_1800006BA  to  jz  $+2
0668 : 74 50  to  74 00               jz      short loc_1800006BA  to  jz  $+2
0673 : 74 45  to  74 00               jz      short loc_1800006BA  to  jz  $+2


Code:
Bios v.F.16 Model 03674 Menu Tabs Unlock Mod :

                                   Form Sets
--------------------------------------------------------------------------------
Offset:        Name:
--------------------------------------------------------------------------------
0x80400        Main (0xE8)
0x806C0        Exit (0x384)
0x807D0        System Configuration (0x5B)
0x80E90        Power (0x301)
0x813D0        Security (0x36)
0x814C0        Advanced (0xF5)
0x85350        Diagnostics (0x42)

0651 : 74 50  to  74 00     jz      short loc_1800006A3  to  jz $+2
065C : 74 45  to  74 00     jz      short loc_1800006A3  to  jz $+2


Code:
Bios v.F.16 Model 03676 Menu Tabs Unlock Mod :

                                   Form Sets
--------------------------------------------------------------------------------
Offset:        Name:
--------------------------------------------------------------------------------
0x73450        Main (0xE9)
0x735D0        Exit (0x365)
0x73700        System Configuration (0x5B)
0x73DD0        Power (0x2E5)
0x746D0        Security (0x36)
0x747C0        Advanced (0xFB)
0x77B10        Main (0x4)
0x77DD0        Diagnostics (0x42)

067B : 74 55  to  74 00               jz      short loc_1800006D2  to  jz $+2
0685 : 74 4B  to  74 00               jz      short loc_1800006D2  to  jz $+2
068F : 74 41  to  74 00               jz      short loc_1800006D2  to  jz $+2


It will helps many users !
Regards]]> <![CDATA[[GUIDE] Removing Wi-Fi/WWAN whitelist on Lenovo (Insyde) BIOS]]> https://www.bios-mods.com/forum/Thread-GUIDE-Removing-Wi-Fi-WWAN-whitelist-on-Lenovo-Insyde-BIOS Sun, 10 Feb 2019 10:47:54 -0500 p0358]]> https://www.bios-mods.com/forum/Thread-GUIDE-Removing-Wi-Fi-WWAN-whitelist-on-Lenovo-Insyde-BIOS As I haven't personally found any good or recent guide on this, I decided to give it a go and write my own.

Here's a link to the article:
https://medium.com/@p0358/removing-wlan-...033a5a5e5a

It is based on Lenovo G510 (where all mods are personal), and involves using SPI programmer + SOIC8 clip, since BIOS on this model is write-protected, so it is the only way to modify it.
Hope it's useful.]]> As I haven't personally found any good or recent guide on this, I decided to give it a go and write my own.

Here's a link to the article:
https://medium.com/@p0358/removing-wlan-...033a5a5e5a

It is based on Lenovo G510 (where all mods are personal), and involves using SPI programmer + SOIC8 clip, since BIOS on this model is write-protected, so it is the only way to modify it.
Hope it's useful.]]> <![CDATA[Instructions for BIOS WL removal on ALL X201 models]]> https://www.bios-mods.com/forum/Thread-Instructions-for-BIOS-WL-removal-on-ALL-X201-models Tue, 05 Feb 2019 10:27:15 -0500 MagicFab]]> https://www.bios-mods.com/forum/Thread-Instructions-for-BIOS-WL-removal-on-ALL-X201-models
http://richbits.rbarnes.org/installing-t...-x201.html

This should work on *ANY* X201. I tested on mine with Windows 7 with a number of different Atheros cards, all worked.

Also note you may hear 6 short beeps at boot time, possibly indicating the BIOS has been modified and ading some delay to boot time but it worked for me.]]>
http://richbits.rbarnes.org/installing-t...-x201.html

This should work on *ANY* X201. I tested on mine with Windows 7 with a number of different Atheros cards, all worked.

Also note you may hear 6 short beeps at boot time, possibly indicating the BIOS has been modified and ading some delay to boot time but it worked for me.]]> <![CDATA[[GUIDE] Flash BIOS with CH341A programmer]]> https://www.bios-mods.com/forum/Thread-GUIDE-Flash-BIOS-with-CH341A-programmer Mon, 19 Nov 2018 07:25:24 -0500 junjo]]> https://www.bios-mods.com/forum/Thread-GUIDE-Flash-BIOS-with-CH341A-programmer PART 1
CH341A details

This guide is based on the winbond 25Q64 bios chip.

Special thanks to Lost_N_BIOS for your help.


CH341A programmer:

[Image: yjqgDTv.png]




PINs details:

[Image: hH2Ap6c.png]

[Image: juDxcVx.png]

[Image: AT2ZMUA.png]  [Image: 2wXHVDF.png]

1.8V Adapter:

[Image: vQU7dQM.png]

[Image: cwMs82I.png]

[Image: HNfIuW8.png]


PIN 1 on the BIOS chip:

[Image: NAW7f3Z.png]

[Image: 8jvCZv3.png]

[Image: MmQfDLC.png]

If you receive this error(s) with the CH341A programmer connected to bios chip:


[Image: TarZn3y.png]

[Image: jnZbfp0.png]

This error(s) is caused by the bad connection of the clip or by the wrong software version.

Try the following steps:

Exit form C341A software.
Disconnect ch341a programmer from USB.
Disconnect the test clip from the bios chip.

Connect the test clip to bios chip.
Connect ch341a programmer to USB.
Run C341A software.
Press detect button.

OR

Please try another software version.
]]> PART 1
CH341A details

This guide is based on the winbond 25Q64 bios chip.

Special thanks to Lost_N_BIOS for your help.


CH341A programmer:

[Image: yjqgDTv.png]




PINs details:

[Image: hH2Ap6c.png]

[Image: juDxcVx.png]

[Image: AT2ZMUA.png]  [Image: 2wXHVDF.png]

1.8V Adapter:

[Image: vQU7dQM.png]

[Image: cwMs82I.png]

[Image: HNfIuW8.png]


PIN 1 on the BIOS chip:

[Image: NAW7f3Z.png]

[Image: 8jvCZv3.png]

[Image: MmQfDLC.png]

If you receive this error(s) with the CH341A programmer connected to bios chip:


[Image: TarZn3y.png]

[Image: jnZbfp0.png]

This error(s) is caused by the bad connection of the clip or by the wrong software version.

Try the following steps:

Exit form C341A software.
Disconnect ch341a programmer from USB.
Disconnect the test clip from the bios chip.

Connect the test clip to bios chip.
Connect ch341a programmer to USB.
Run C341A software.
Press detect button.

OR

Please try another software version.
]]> <![CDATA[Help for unlock bios Sony Vaio VGN-NR11S]]> https://www.bios-mods.com/forum/Thread-Help-for-unlock-bios-Sony-Vaio-VGN-NR11S Thu, 12 Oct 2017 14:51:07 -0400 diogofvh]]> https://www.bios-mods.com/forum/Thread-Help-for-unlock-bios-Sony-Vaio-VGN-NR11S
I need to unlock bios for Sony Vaio VGN-NR11S to install windows 10.
I discover that link https://www.bios-mods.com/forum/archive/...15895.html but i don's know how it's apply.

someone can help me or send me a tutorial step by step.

Thank you.]]>
I need to unlock bios for Sony Vaio VGN-NR11S to install windows 10.
I discover that link https://www.bios-mods.com/forum/archive/...15895.html but i don's know how it's apply.

someone can help me or send me a tutorial step by step.

Thank you.]]> <![CDATA[[request] BIOS Modding]]> https://www.bios-mods.com/forum/Thread-request-BIOS-Modding Tue, 10 Oct 2017 18:15:25 -0400 jinxowemeasoda]]> https://www.bios-mods.com/forum/Thread-request-BIOS-Modding , I am new to the subject of bios modding/updating Confused and would appreciate if some of you guys could guide me in the right direction. I have an Acer Aspire  17 (E5-721-46M4) that I am trying to install a modded or unlocked bios on for the purpose of overclocking. is there a modded or unlocked bios rom somewhere that i could download for my computer? if not, is there a way that the stock bios can be reverse engineered and modified?. thanks in advance to anyone who provides some me with some help. Big Grin

specs
Motherboard: EA70_BE
Vendor: Acer (www.acer.com)

Current BIOS
Vendor:Insyde Corp.
version: v1.06

processor: AMD Quad-Core A4-6210 (1.8 GHz) with Radeon R3 Graphics

apologeez if this is the wrong category ...]]> , I am new to the subject of bios modding/updating Confused and would appreciate if some of you guys could guide me in the right direction. I have an Acer Aspire  17 (E5-721-46M4) that I am trying to install a modded or unlocked bios on for the purpose of overclocking. is there a modded or unlocked bios rom somewhere that i could download for my computer? if not, is there a way that the stock bios can be reverse engineered and modified?. thanks in advance to anyone who provides some me with some help. Big Grin

specs
Motherboard: EA70_BE
Vendor: Acer (www.acer.com)

Current BIOS
Vendor:Insyde Corp.
version: v1.06

processor: AMD Quad-Core A4-6210 (1.8 GHz) with Radeon R3 Graphics

apologeez if this is the wrong category ...]]> <![CDATA[There a HOW-TO or DIY guide for Modding a BIOS? related to Lenovo and Phoenix Bios]]> https://www.bios-mods.com/forum/Thread-There-a-HOW-TO-or-DIY-guide-for-Modding-a-BIOS-related-to-Lenovo-and-Phoenix-Bios Mon, 10 Jul 2017 19:49:03 -0400 mos65xx@gmail.com]]> https://www.bios-mods.com/forum/Thread-There-a-HOW-TO-or-DIY-guide-for-Modding-a-BIOS-related-to-Lenovo-and-Phoenix-Bios