I used AMIBCP to modify the BIOS file, navigating through the desired folders, subfolders, and options, and changed them from ‘default’ to ‘user’. After saving the file (without creating a new one), I received a warning that the BIOS was not signed. I noticed that the size of the backup file created by AFUWIN is smaller than the saved file.
When I tried flashing using AFUWIN, an error occurred indicating that the file size was not as expected, so I decided not to proceed. What would be the best procedure in this case?
Information:
Version: 310
System: Windows Hirenboot
Edit by Fernando: Thread title shortened and customized
I am trying to unlock certain menus, sections, and submenus in the BIOS of the ASUS X510URR model but have been unsuccessful. The sections I want to unlock are shown in the attached image. I do not need the CPU VR options.
I would like to keep the area responsible for booting unchanged when flashing the BIOS to ensure a recovery option in case something goes wrong. I plan to follow this guide for the process: AMI AptioV UEFI Editor & FPT Flash Method Guide
If any additional information is needed, I am happy to provide it.
Thanks in advance for your time and help!
I used System Tools v11 r46.
It seems to me that there are no blocks…
MEInfoWin64.exe -verbose
Intel(R) MEInfo Version: 11.8.92.4189
Copyright(C) 2005 - 2020, Intel Corporation. All rights reserved.
Windows OS Version : 10.0
FW Status Register1: 0x90000245
FW Status Register2: 0x060B0506
FW Status Register3: 0x00000020
FW Status Register4: 0x00084000
FW Status Register5: 0x00000000
FW Status Register6: 0x40000000
CurrentState: Normal
ManufacturingMode: Disabled
FlashPartition: Valid
OperationalState: CM0 with UMA
InitComplete: Complete
BUPLoadState: Success
ErrorCode: No Error
ModeOfOperation: Normal
SPI Flash Log: Not Present
FPF HW Source value: Not Applicable
ME FPF Fusing Patch Status: ME FPF Fusing patch NOT applicable
Phase: ROM/Preboot
ICC: Valid OEM data, ICC programmed
ME File System Corrupted: No
PhaseStatus: CALL_NEXT_MODULE
FPF and ME Config Status: Match
FW Capabilities value is 0x31111240
Feature enablement is 0x31111240
Platform type is 0x41130321
The only information that appeared was what I previously sent. Perhaps the Intel ME is outdated (I will check), or the BIOS is restricting access to this information. Additionally, RW Everything might be useful for displaying these details.
@karfel
Here.
Secure Boot and TPM are disabled, I’m using CSM (region.bin and dump.bin may have these settings) If necessary I put the default values. region.zip (4.4 MB)
It should be fine. I think even if it doesn’t work, the device can still boot to Windows. It just can’t access the setup menu BIOS. If that happens, reflash it again with the original region.
note:
This BIOS is a little different in how hidden values are set in AMITE PE32, unlike other devices, so the result is unknown.
I’m sure that all users seeking bios mod files have in mind that they can break their system and make post/boot a blank/black picture… do you know how to recover a death system?
Some users seeking bios mods, hope that they are safe and nothing will fail…wrong assumption.
It’s just a little reminder… the asset is yours and your decision only.