I have dumped my bios with fptw64. I successfully removed the msr lock with uefipatch and flashed it back with the same program.
Now I'd like to unhide chipset and memory settings. I have an XMP memory module and I can't set that in the bios as there is no memory settings menu, yet I can see the bios have xmp profiles in strings.
Can anyone help to unhide it? How can I do it myself?
Here's link to the rom, it's an AMI bios of course.
x301a 211 ami bios
By looking at the menu with amibcp the chipset settings is set to show still it doesn't appear.
[
attachment=7830]
[
attachment=7831]
[
attachment=7832]
here's what I did:
I followed the guide to enable chipset menu in x301a 211 bios.
I extracted the setup module uncompressed and found the 010100010101 string, modified it to 010101010101.
Then at 011h I changed F3 to F2 ( result of F3 -1 ). (checksum)
I then reinserted the module with mmtool and no error was shown.
I saved my bios image, now the report for setup (made with mmtool) shows:
before mod:
|139|Setup |899407D7-99FE-43D8-9A21-79EC328CAC21|002608A8|00F8FA|DRVR|
after mod:
|139|Setup |899407D7-99FE-43D8-9A21-79EC328CAC21|002608A8|043CF8|DRVR|
so the size of the setup module is now 043CF8 and was 00F8FA , meaning the new size is bigger by 343fe.
Is this normal? I mean is it because I extracted uncompressed and then reinserted uncompressed while in the original file the module is compressed?
I don't see any option to insert the module compressed.
I tried to instead delete the setup module and insert the modified one as compressed but then mmtool locates it at another address 01 A3 instead of 01 8B where it originally was.
|163|Setup |899407D7-99FE-43D8-9A21-79EC328CAC21|002BC198|00F8FD|DRVR|
this time the size is 00F8FD
now I did like this, I deleted the setup from the image and inserted the modded setup module compressed. Then I extracted it as is (compressed). Then I reloaded the original bios image and replaced the extracted setup module.
Now everything seems fine as it's at 01 8B, however the size of the extracted compressed module differs from the one inserted, 00F8FD while the new is 00F8F9...
|139|Setup |899407D7-99FE-43D8-9A21-79EC328CAC21|002608A8|00F8F9|DRVR|
the rest is unchanged. the module is bigger by 3 from the original.
I still need to flash it, what do you think of this procedure? anyone?
You have not used Google !!!
I posted many times same things :
Hi friend,
Here is the last AMIBCP version 4.55 :
http://rghost.net/59893020
Here is a Tutorial to modify AMI Aptio Bios :
http://forums.mydigitallife.info/threads...MSR-unlock!
Follow CodeRush Suggestions :
It's certanly not so easy for BIOSes with another menu setup, but the whole idea is the same.
I could also recommend trying AMIBCP to modify menu entries vilibility from "Default" to "USER",
if your menu setup is more complex then a setup above.
I have to flash my image on the administrator commandline using afuwinx64 bios_mod.rom /GAN . . .
Otherwise it gives me a security error (Thanks again CodeRush)
Let me know
Regards
https://www.bios-mods.com/forum/Thread-G...ios-Unlock
Try this way is simplest and sure !
Ok got it, thanks! Anyway I didn't use afu /gan as someone in another forum reported this method bricked his laptop. I used fptw64 both for dump and reflash the msr unlocked rom. Now I used uefitool to unlock the chipset menu and will flash the rom later.
UEFITool don't unlock anything It needs to extract and repack UEFI Bioses !
You extracted a Module, modified It and repacked by UEFITool (BIG CODERUSH) !!!
The MSR Patch is done by UEFIPatch (Always Coderush) !
FPT - W - W64 is an Intel Utility so You are lucky as not have an AMD CPU otherwise
AFUDOS "necesse est" !
Regards
(02-08-2015, 05:45 PM)BDMaster Wrote: [ -> ]UEFITool don't unlock anything It needs to extract and repack UEFI Bioses !
You extracted a Module, modified It and repacked by UEFITool (BIG CODERUSH) !!!
The MSR Patch is done by UEFIPatch (Always Coderush) !
FPT - W - W64 is an Intel Utility so You are lucky as not have an AMD CPU otherwise
AFUDOS "necesse est" !
Regards
Yes I used UEFIPatch, I wrote wrong.