Jump to content

[UEFIPatch] UEFI patching utility


CodeRush
1,981 posts in this topic

Recommended Posts

  • 3 weeks later...

Hi Coderush/Gurus,

I really admire your work and all the contribution towards the utilities which made life of many novice people like me to be able to think of bios-modding.

I am approaching you for a thing which may be a simple thought and will take days to figure out for me.

 

I am writing the modded BIOS to chips by CH341A programmer every time and am desperately trying since a week to be able to perform BIOS modifications through FPT.

 

I have removed the Descriptor lock by using FITC.

 

Next, I did two changes to PchBiosWriteProtect suggested by Coderush Changing 0xFE to 0xFF and Changing 0x20 to 0x00. But, no luck still getting the error "Error 28: Protected Range Registers are currently set by BIOS, preventing flash access. Please contact the target system BIOS vendor for an option to disable Protected Range Registers." when I try to execute 1. fptw64 -d dump.bin 2. fptw64 -f dump.bin.

 

Next, I did replace the test statements with 4831C0 in PCHinitDXE at two places at BPL register comparision 40 84 28 -> 48 31 C0 and at BiosLock comparision F6 00 10 -> 48 31 C0. But, still no Luck.

 

Please let me know if you want the bios dump to be sent you if you want to have a look at. I even removed CMOS battery and reset NVRAM.

 

System BIOS version : A14

System Model : Inspiron 15R N5520

Chipset :- HM77 Mobile

CPU: i7-3632Qm

 

Can you please tell me if I am doing something wrong.

 

Thanks in Adavance for your suggestions/inputs.

 

Pavan.

Link to comment
Share on other sites

  • 4 weeks later...

Strange, I have Gigabyte Z170X-UD5 and 0xE2 is not locke

 

 

Seems unlocked

UEFIPatch.exe Z170XD.F21
parseFile: non-empty pad-file contents will be destroyed after volume modifications
No patches can be applied to input file

 

Hmm...it won't boot without KernelPm checked in Clover and put it to sleep would crashed the system. I think it said MSR 0xe2 is locked in the boot log.

 

But, anyway, I returned and exchange 6700K and Gigabyte GA-Z170-designare for 7700K and Asus TUF Z270-Mark 1. I got everything working except for Intel 219V Nic and sleep. Somehow, IntelMausiEthernet driver work in Designare but it won't work on Mark 1. The strange thing is that both are Intel 219V. Sleep doesn't work but at least it doesn't crashed the whole system like Designare and it boot without KernelPm checked.

Link to comment
Share on other sites

You think or you see?

I saw that line and few other lines related to it.

 

I finally got fully working Hackintosh with working Speedstep and Sleep with 7700K CPU and Asus TUF Z270-Mark 1 motherboard. The latest bios v0701 fixed Intel 219V, now, it's working with IntelMausiEthernet v2.20 driver. But my 2nd Nic port with Intel 211 using AppleIGB.kext loses connection after waking up from Sleep.

Link to comment
Share on other sites

  • 3 weeks later...

MSR 0xe2 is locked on new Gigabyte Bios F21.

0:107  0:000  CPU Vendor = 756E6547 Model=506E3
0:107  0:000   The CPU supported SSE4.1
0:107  0:000  got cores from CPUID_1 = 0
0:107  0:000  The CPU supported turbo
0:107  0:000  BrandString = Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
0:107  0:000   TSC/CCC Information Leaf:
0:107  0:000    numerator     : 334
0:107  0:000    denominator   : 2
0:107  0:000   Calibrated ARTFrequency: 24003236
0:107  0:000  MSR 0xE2 before patch 00008000
0:107  0:000  MSR 0xE2 is locked, PM patches will be turned on
0:107  0:000  MSR 0xE4              00000000
0:107  0:000  MSR 0xCE              00080838_F1012800
0:107  0:000  non-usable FLEX_RATIO = F0000
0:107  0:000  corrected FLEX_RATIO = E0000
0:107  0:000  FSBFrequency=100MHz DMIvalue=100000kHz
0:107  0:000  Corrected FSBFrequency=100MHz
0:107  0:000  Vendor/Model/Stepping: 0x756E6547/0x5E/0x3
0:107  0:000  Family/ExtFamily: 0x6/0x0
0:107  0:000  MaxDiv/MinDiv: 40.0/8
0:107  0:000  Turbo: 40/40/40/42
0:107  0:000  Features: 0xBFEBFBFF
0:107  0:000  Threads: 8
0:107  0:000  Cores: 4
0:107  0:000  FSB: 100 MHz
0:107  0:000  CPU: 4000 MHz
0:107  0:000  TSC: 4000 MHz
0:107  0:000  PIS: 400 MHz
Link to comment
Share on other sites

 

MSR 0xe2 is locked on new Gigabyte Bios F21.

0:107  0:000  CPU Vendor = 756E6547 Model=506E3
0:107  0:000   The CPU supported SSE4.1
0:107  0:000  got cores from CPUID_1 = 0
0:107  0:000  The CPU supported turbo
0:107  0:000  BrandString = Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
0:107  0:000   TSC/CCC Information Leaf:
0:107  0:000    numerator     : 334
0:107  0:000    denominator   : 2
0:107  0:000   Calibrated ARTFrequency: 24003236
0:107  0:000  MSR 0xE2 before patch 00008000
0:107  0:000  MSR 0xE2 is locked, PM patches will be turned on
0:107  0:000  MSR 0xE4              00000000
0:107  0:000  MSR 0xCE              00080838_F1012800
0:107  0:000  non-usable FLEX_RATIO = F0000
0:107  0:000  corrected FLEX_RATIO = E0000
0:107  0:000  FSBFrequency=100MHz DMIvalue=100000kHz
0:107  0:000  Corrected FSBFrequency=100MHz
0:107  0:000  Vendor/Model/Stepping: 0x756E6547/0x5E/0x3
0:107  0:000  Family/ExtFamily: 0x6/0x0
0:107  0:000  MaxDiv/MinDiv: 40.0/8
0:107  0:000  Turbo: 40/40/40/42
0:107  0:000  Features: 0xBFEBFBFF
0:107  0:000  Threads: 8
0:107  0:000  Cores: 4
0:107  0:000  FSB: 100 MHz
0:107  0:000  CPU: 4000 MHz
0:107  0:000  TSC: 4000 MHz
0:107  0:000  PIS: 400 MHz

This is very bad news. 

Anyway I decided to stay with F5. It is much better then F20.

Link to comment
Share on other sites

  • 3 weeks later...

Hi Rushcode.

I'm trying flashing the bios on my P8Z77-V LK but i get this message:

Error 280: Failed to disable write protection for the BIOS space!

It says that my bios are locked.
There are any possibility to unlock it to flash one bios with PM ?
Like:https://github.com/danielstuart14/ASUS_BIOS_REPO

Some help is very apreciated
Best Regards, Nuno

Link to comment
Share on other sites

  • 4 weeks later...

verify it then push flashback button till led starts to blink

then wait patiently

I have Asus x99 Deluxe II BIOS 1401 I believe you have the same board and BIOIS would you be able to share your patched BIOS ?

Thanks 

Link to comment
Share on other sites

  • 1 month later...

I have the Asus X99-A ll Motherboard and just tried to patch the bios but it did not work...

 

At first I have downgraded my Bios from 1401 to Version 801. Then I patched version 1401 with the UefiPatch.

I renamed the patched 1401 Version to X99A2.CAP and have already tried two different USB Sticks (2.0 and 3.0) for the flashing process.

The LED starts to blink and after 3 or 4 times blinking it stops and remains on.

 

I have also tried patching and flashing the newest Version of my motherboard, which is 1504, but I got the same problems.

And when I try to update my bios directly in the bios menu, it says: "the file selected is not a proper bios"

 

Is there anyone who has an idea what the problem could be?

 

 

 

Link to comment
Share on other sites

  • 1 month later...

Hi.

First sorry for my bad english.

 

I have a problem with motherboard asus z87-deluxe.

 

My motherboard not save bios setting.

 

When i press f10 save changes and exit its shutdown.

 

And its loop on " new cpu installed press f1"

I modified bios with amicbp v4 and i changed wait for f1 to disabled.

 

But i couldnt flash modified bios afuwin says " unble to start secure flash session"

 

And i tried usb flashback with modded bios and nothing.

Its not work, led flash for 3-4 times then stop flashing.

 

Please help me to fix this.

Tnx

Link to comment
Share on other sites

  • 1 month later...

If anyone could patch the BIOS for the z77 M Power and post it here I would be eternally grateful. I had no idea it needed patched and have been struggling for a week

It's patched correctly.

Coderush I hate to ask favors but is there any way you could patch the bios for the MSI Z77 M Power and post it ? I would be eternally grateful

Link to comment
Share on other sites

  • 1 month later...

Hey guys I have this message when I try to patch the ROM of ASUS-X99-A with bios version:3701

 

parseImageFile: Aptio capsule signature may become invalid after image modifications
parseSection: section with unknown type 52h
parseFile: non-empty pad-file contents will be destroyed after volume modifications
parseSection: section with unknown type 52h
parseFile: non-empty pad-file contents will be destroyed after volume modifications
No patches can be applied to input file

 

This mean that it's already unlocked, or the patches won't be applied because of the UEFI Image Security (But at liest the patches must be applied and only the image file won't be working ) or I don't know.

Link to comment
Share on other sites

Hey guys I have this message when I try to patch the ROM of ASUS-X99-A with bios version:3701

 

parseImageFile: Aptio capsule signature may become invalid after image modifications

parseSection: section with unknown type 52h

parseFile: non-empty pad-file contents will be destroyed after volume modifications

parseSection: section with unknown type 52h

parseFile: non-empty pad-file contents will be destroyed after volume modifications

No patches can be applied to input file

 

This mean that it's already unlocked, or the patches won't be applied because of the UEFI Image Security (But at liest the patches must be applied and only the image file won't be working ) or I don't know.

 

use this file https://github.com/LongSoft/UEFITool/blob/master/UEFIPatch/patches.txt

  • Like 1
Link to comment
Share on other sites

×
×
  • Create New...