355 replies to this topic

[CodeRush]

EDIT:
I'm removing PMAP from public access because it's too dangerous and easy to brick your PC by using it. Sorry.

[maximus]

PMPatch 0.5.10
PowerManagement module at 00302920 not patched: Patch pattern not found.
AMI nest modules not found.
Phoenix nest modules not found.
CpuPei module at 0057D5A8 not patched: Patch pattern not found.

Bios version 2.9

[CodeRush]

maximus, on 02 February 2013 - 01:42 AM, said:

PMPatch 0.5.10
PowerManagement module at 00302920 not patched: Patch pattern not found.
AMI nest modules not found.
Phoenix nest modules not found.
CpuPei module at 0057D5A8 not patched: Patch pattern not found.

Bios version 2.9

Looks like already patched BIOS.
Is it definitely incompatible with original kext? If so, we need to find new patch pattern to perform. Thank you for report.

[Charan Cherry Patnaik]

what the hell you done ? you are awesome man thanks a lot working pretty awesome on H61M-DS2 v2.2 bios-F8 with i5 3450 ivy bridge, thanks a lot man you done magic..

[BALDY_MAN]

HI i tryed  to batch my sabertooth x79 bios
what i did was down load latest bios to usb and patched in terminal and renamed to bois file after patching
the bios loaded ok put i couldnt boot up after removing null cpu management kext
i had to reload the kext file and i could boot up
but my overclock was unstable so i replaced with standard bios
i hope the info helps with your development

[CodeRush]

I have seen some issues with x79 boards, but I really don't know why OC can become unstable after the patch.
Repacking BEOS and becoming issues from it is only a sign of weak BIOS programming, which is common for ASUS boards.
Thank you for report but I don't know how to fix that.

[maximus]

CodeRush, on 02 February 2013 - 01:49 AM, said:

Looks like already patched BIOS.
Is it definitely incompatible with original kext? If so, we need to find new patch pattern to perform. Thank you for report.

Yes I think its incompatible as I get a kernel panic if I dont use NullCPUPowerManagement.kext. Tried on bioses 2.10, 2.9 and beta 2.94 for my board in sig.

[paashaas2]

I tested the latest windows version on a MSI GT60 Laptop with the latest bios version. The result is in the picture (attechment)

Attached Files

•  PMPatch.JPG   145.95K   98 downloads

[LoLL]

Anybody have tested it with Sony Vaio S ?

[oolll]

Here is the result

CodeRush, on 01 February 2013 - 09:58 PM, said:

I wrote a batch file and prepared a set of tools (now for Windows and Intel-based machines only) to make all things from my previous post automatically.
For anyone who has unpatched BIOS and want to test this automatic Dump->Patch->Flash solution - you are welcome.
It works on ASUS Maximus IV Gene-Z and it will not work on Intel boards, but I hope it will work on any non-Intel board, including laptop ones.
PowerManagement AutoPatcher aka PMAP v0.1 for Windows
Download it, unpack and run PMAP.bat as Administrator. Thank you in advance and please report your results here.

Not working on hp 4530s

PowerManagement Autopatcher v0.1
This program will dump your BIOS region,
patch it with PMPatch and flash the resulting file back to BIOS chip.
WARNING: BIOS flashing is dangerous and requires exclusive access to SPI chip.
Please disable any antivirus software,
virtualisation or sandboxing tools before running this batch file.
Press any key to continue if you are ready.
Press any key to continue . . .
Reading BIOS dump to dump.bin file.
Intel (R) Flash Programming Tool. Version: 8.1.10.1286
Copyright (c) 2007 - 2012, Intel Corporation. All rights reserved.
Platform: Intel(R) HM65 Express Chipset
Reading HSFSTS register... Flash Descriptor: Valid
--- Flash Devices Found ---
MX25L3205D ID:0xC22016 Size: 4096KB (32768Kb)

- Reading Flash [0x400000] 2560KB of 2560KB - 100% complete.
Writing flash contents to file "dump.bin"...
Memory Dump Complete
FPT Operation Passed
Patching dump.bin with PMPatch
PMPatch 0.5.10
PowerManagement modules not found.
AMI nest modules not found.
Trying to apply patch #1
Nested PowerManagement2.efi module at 01689340 patched.
Phoenix nest module at 00030048 patched.
CpuPei modules not found.
Output file generated.
Flashing modified BIOS dump to BIOS chip
Intel (R) Flash Programming Tool. Version: 8.1.10.1286
Copyright (c) 2007 - 2012, Intel Corporation. All rights reserved.
Platform: Intel(R) HM65 Express Chipset
Reading HSFSTS register... Flash Descriptor: Valid
--- Flash Devices Found ---
MX25L3205D ID:0xC22016 Size: 4096KB (32768Kb)

Error 280: Failed to disable write protection for the BIOS space!
Flashing modified BIOS failed. Please report in PMPatch topic on InsanelyMac.com
forum. Exiting.
Press any key to continue . . .

[oSxFr33k]

@CodeRush,


osxfr33ks-Mac-Pro-2:G74sx osxfr33k$ ./PMPatch G74SxAS.203 G74SxAS.203_patch
PMPatch 0.5.10
PowerManagement modules not found.
Trying to apply patch #1
Nested PowerManagement module at 00F900AC patched.
AMI nest module at 000B7720 patched.
Phoenix nest modules not found.
CpuPei module at 0027C2C0 not patched: Patch pattern not found.
Output file generated.


I have an Asus Gamers Laptop G74SX that I have to use the speedstep patching from that thread.  Did your patch work on this particular UEFI bios and will I be able to update the bios on the notebook?

Asus Laptops use Asus brand boards not Intel as far as I know.  Of course they are intel chipsets.


EDITED:

I attached both the original files from Asus and patched file.

Attached Files

•  G74SxAS203.zip   1.04MB   3 downloads
•  G74SxAS.203_patch.zip   1.04MB   2 downloads

[TimeWalker75a]

oolll, on 02 February 2013 - 05:45 PM, said:

Here is the result

Not working on hp 4530s

PowerManagement Autopatcher v0.1
This program will dump your BIOS region,
patch it with PMPatch and flash the resulting file back to BIOS chip.
WARNING: BIOS flashing is dangerous and requires exclusive access to SPI chip.
Please disable any antivirus software,
virtualisation or sandboxing tools before running this batch file.
Press any key to continue if you are ready.
Press any key to continue . . .
Reading BIOS dump to dump.bin file.
Intel (R) Flash Programming Tool. Version: 8.1.10.1286
Copyright (c) 2007 - 2012, Intel Corporation. All rights reserved.
Platform: Intel(R) HM65 Express Chipset
Reading HSFSTS register... Flash Descriptor: Valid
--- Flash Devices Found ---
MX25L3205D ID:0xC22016 Size: 4096KB (32768Kb)

- Reading Flash [0x400000] 2560KB of 2560KB - 100% complete.
Writing flash contents to file "dump.bin"...
Memory Dump Complete
FPT Operation Passed
Patching dump.bin with PMPatch
PMPatch 0.5.10
PowerManagement modules not found.
AMI nest modules not found.
Trying to apply patch #1
Nested PowerManagement2.efi module at 01689340 patched.
Phoenix nest module at 00030048 patched.
CpuPei modules not found.
Output file generated.
Flashing modified BIOS dump to BIOS chip
Intel (R) Flash Programming Tool. Version: 8.1.10.1286
Copyright (c) 2007 - 2012, Intel Corporation. All rights reserved.
Platform: Intel(R) HM65 Express Chipset
Reading HSFSTS register... Flash Descriptor: Valid
--- Flash Devices Found ---
MX25L3205D ID:0xC22016 Size: 4096KB (32768Kb)

Error 280: Failed to disable write protection for the BIOS space!
Flashing modified BIOS failed. Please report in PMPatch topic on InsanelyMac.com
forum. Exiting.
Press any key to continue . . .

Try booting tour laptop by holding down: win+left atrow+right arrow when you hit the power button.

[CodeRush]

maximus, on 02 February 2013 - 12:27 PM, said:

Yes I think its incompatible as I get a kernel panic if I dont use NullCPUPowerManagement.kext. Tried on bioses 2.10, 2.9 and beta 2.94 for my board in sig.

Will look at it then. X79 boards are hard to patch, and I don't know if they can be patched at all, but not trying is not an option.

paashaas2, on 02 February 2013 - 04:37 PM, said:

I tested the latest windows version on a MSI GT60 Laptop with the latest bios version. The result is in the picture (attechment)

Thanks for report, there is an example of normal PMAP log with all things gone right.

oolll, on 02 February 2013 - 05:45 PM, said:

Not working on hp 4530s

BIOS write protection kicks in. Intel boards behave similar.
Read a manual to your laptop for instructions on disabling write protection. Try TimeWalker's method too.
Patch a normal BIOS file with PMPatch and try flashing it with HP flashing tools.
Report your results.

oSxFr33k, on 02 February 2013 - 05:50 PM, said:

I have an Asus Gamers Laptop G74SX that I have to use the speedstep patching from that thread.  
Did your patch work on this particular UEFI bios and will I be able to update the bios on the notebook?

If it patches and generates patched file then this patched file must be working. I can't guarantee it, but there was no corrupted image produced since version 0.5.3, and thre is only report of having isssues with OC stability after flashing patched BIOS.
Try PMAP first, if it works, you don't need anything else. If not - report and I will try to guide you further.

[CodeRush]

BALDY_MAN, on 02 February 2013 - 03:04 AM, said:

ASUS Sabertooth x79

Can you also try flashing patched BIOS with biosrefl.bat from FTK? Can you try not latest BIOS version but a one ore two previous ones? You can flash any version you want with FTK.
I think I know why this OC issues may be present, but I need more testing before I can fully explain it.

[BALDY_MAN]

@codeRush.
                    sorry i didnt use your tool correctly in my first post my mistake was only puting bios file in terminal once. but i hve just but bios file in twice. and genarated a patched file.
this is my read out from terminal.


Desktop/SABERTOOTH-X79-ASUS-3305.CAP\ 2
PMPatch 0.5.10
PowerManagement modules not found.
AMI nest modules not found.
Phoenix nest modules not found.
CpuPei module at 0079A518 patched.
CpuPei module at 007DA518 patched.
Output file generated.

Now the motherboard will not read the patched file from the usb stick

[CodeRush]

BALDY_MAN, on 02 February 2013 - 08:04 PM, said:

Now the motherboard will not read the patched file from the usb stick

It's normal. Use FTK toolset linked above to flash this patched BIOS.
Download FTK for Windows, unpack it, rename your patched BIOS file to bios.bin, copy it to FTK/Win32 or FTK/Win64 folder and run biosrefl.bat as Administrator. Then run poweroff.bat as Administrator.

[beta992]

Thanks for this.

Going to test with an ASUS P8H67-M Pro B3.

[CodeRush]

beta992, on 02 February 2013 - 08:35 PM, said:

Going to test with an ASUS P8H67-M Pro B3.

There is no reason for patch not to work on this board. I'm waiting for your report.

[oSxFr33k]

@CodeRush,

Tried and looks like the flashing failed:

Platform: Intel(R) HM65 Express Chipset
Reading HSFSTS register... Flash Descriptor: Valid
	--- Flash Devices Found ---
	W25Q32BV	ID:0xEF4016	Size: 4096KB (32768Kb)
PDR Region does not exist.
GBE Region does not exist.
- Erasing Flash Block [0x200000] -  20% complete.
Error 7: Hardware sequencing failed. Make sure that you have access to target fl
ash area!
Trying to erase the same block (iteration: 2)
Error 7: Hardware sequencing failed. Make sure that you have access to target fl
ash area!
Trying to erase the same block (iteration: 3)
Error 7: Hardware sequencing failed. Make sure that you have access to target fl
ash area!
Failed to erase this block 3 times!!
Flashing modified BIOS failed. Please report in PMPatch topic on InsanelyMac.com
forum. Exiting.
Press any key to continue . . .
PowerManagement Autopatcher v0.1
This program will dump your BIOS region,
patch it with PMPatch and flash the resulting file back to BIOS chip.
WARNING: BIOS flashing is dangerous and requires exclusive access to SPI chip.
Please disable any antivirus software,
virtualisation or sandboxing tools before running this batch file.
Press any key to continue if you are ready.
Press any key to continue . . .
Reading BIOS dump to dump.bin file.
Intel (R) Flash Programming Tool. Version:  8.1.10.1286
Copyright (c) 2007 - 2012, Intel Corporation. All rights reserved.
Platform: Intel(R) HM65 Express Chipset
Reading HSFSTS register... Flash Descriptor: Valid
	--- Flash Devices Found ---
	W25Q32BV	ID:0xEF4016	Size: 4096KB (32768Kb)

- Reading Flash [0x400000] 2560KB of 2560KB - 100% complete.
Writing flash contents to file "dump.bin"...
Memory Dump Complete
FPT Operation Passed
Patching dump.bin with PMPatch
PMPatch 0.5.10
PowerManagement modules not found.
Trying to apply patch #1
Nested PowerManagement module at 00A480EC patched.
AMI nest module at 000B7720 patched.
Phoenix nest modules not found.
CpuPei module at 0027C2C0 not patched: Patch pattern not found.
Output file generated.
Flashing modified BIOS dump to BIOS chip
Intel (R) Flash Programming Tool. Version:  8.1.10.1286
Copyright (c) 2007 - 2012, Intel Corporation. All rights reserved.
Platform: Intel(R) HM65 Express Chipset
Reading HSFSTS register... Flash Descriptor: Valid
	--- Flash Devices Found ---
	W25Q32BV	ID:0xEF4016	Size: 4096KB (32768Kb)
PDR Region does not exist.
GBE Region does not exist.
- Erasing Flash Block [0x200000] -  20% complete.
Error 7: Hardware sequencing failed. Make sure that you have access to target fl
ash area!
Trying to erase the same block (iteration: 2)
Error 7: Hardware sequencing failed. Make sure that you have access to target fl
ash area!
Trying to erase the same block (iteration: 3)
Error 7: Hardware sequencing failed. Make sure that you have access to target fl
ash area!
Failed to erase this block 3 times!!
Flashing modified BIOS failed. Please report in PMPatch topic on InsanelyMac.com
forum. Exiting.
Press any key to continue . . .

[oSxFr33k]

It was too late and I lucked in.  It booted fine.  I tried to use winflash from ASus website and it would not let me install a stock rom because of the differences of the rom and file.

So I booted into the Bios and used EASY FLASH and installed the stock rom.

I went one step further and used EASY FLASH to update to the patched rom and it works!!!

I can boot now without a speedstep patched AICPM kext.

Thanks so much!!

What exactly will the procedure you mentioned do?

EDITED:

Could I still be in danger or I am past that stage?  In other words if I take out the battery and let all the Caps discharge could I run into an issue or am I safe now?

Did you still want to remote in and check it out?