Jump to content

[UEFIPatch] UEFI patching utility

BIOS patch power management UEFI

  • Please log in to reply
1643 replies to this topic

#481
magnifico

magnifico

    InsanelyMac Deity

  • Donators
  • 2,451 posts
  • Gender:Male

It's pretty straightforward. Download the attachment and read the readme.
http://www.insanelym...lity/?p=1929505
 
Of course your motherboard must support USB BIOS flashback. You didn't say what motherboard you have.


Gringo have R4e ....the special one...

#482
Gringo Vermelho

Gringo Vermelho

    The Jan Bird fix

  • Supervisors
  • 6,112 posts
  • Gender:Male
  • Location:Brazil

Go back and read my post again, I made an edit



#483
magnifico

magnifico

    InsanelyMac Deity

  • Donators
  • 2,451 posts
  • Gender:Male

No need to use BIOS renamer, just name the patched file R4E.CAP and you're good to go.
Dude, you could have found this information yourself with google in 5 seconds.
If you google ASUS BIOS flashback the very first hit has this information.



I'm sorry, but if I take the bios.cap and dragged him into the utilty coderush 0.5.13, this automatically creates me a patched bios for native speed step, why do I need usb flash back? just take the modified bios and flash with EZFlash bios or not?



#484
Gringo Vermelho

Gringo Vermelho

    The Jan Bird fix

  • Supervisors
  • 6,112 posts
  • Gender:Male
  • Location:Brazil

Because the only way to flash a modified, non-factory BIOS is with USB BIOS flashback, which as you know by now, require the file to be named in a certain way in order to work.



#485
magnifico

magnifico

    InsanelyMac Deity

  • Donators
  • 2,451 posts
  • Gender:Male

Because the only way to flash a modified, non-factory BIOS is with USB BIOS flashback, which as you know by now, require the file to be named in a certain way in order to work.


So put bios mod inside pen drive ( format fat 32 ) and use usb flash back mode ?
But first use usb flash back ( bios original on another pen drive ) buck up if something is not right...or magnifico dont unterstand nothing ?

.

#486
Gringo Vermelho

Gringo Vermelho

    The Jan Bird fix

  • Supervisors
  • 6,112 posts
  • Gender:Male
  • Location:Brazil

Please stop, this is getting silly. Or create a new topic if you must.

 

How to use USB BIOS flashback is explained in detail in your motherboard manual, now is a good time to read it.



#487
magnifico

magnifico

    InsanelyMac Deity

  • Donators
  • 2,451 posts
  • Gender:Male

Please stop, this is getting silly. Or create a new topic if you must.
 
How to use USB BIOS flashback is explained in detail in your motherboard manual, now is a good time to read it.



listen to me and not 'stupid, and I know what and' a manual and how to use usbflashback, maybe my English is not 'played well ... end of story

If this is a off topic ...delete my post ...i am not stupid man ...

#488
magnifico

magnifico

    InsanelyMac Deity

  • Donators
  • 2,451 posts
  • Gender:Male
;)
and this a message error
so for me i need rename file.but dont work also i rename i
localhost:~ carmine$ /Users/carmine/Desktop/NewBios/PMPatchPMPatch 0.5.13This program patches UEFI BIOS filesto be compatible with Mac OS X SpeedStep implementationUsage: PMPatch INFILE OUTFILElocalhost:~ carmine$ /Users/carmine/Desktop/NewBios/Rampage-IV-Extreme-ASUS-4102.CAP-bash: /Users/carmine/Desktop/NewBios/Rampage-IV-Extreme-ASUS-4102.CAP: cannot execute binary filelocalhost:~ carmine$


#489
magnifico

magnifico

    InsanelyMac Deity

  • Donators
  • 2,451 posts
  • Gender:Male

@ Gringo

I reasoned with my brain, and I realized that I had to rename the file as BRenamer (works only for windows OS) once you have the file R4E.cap I used the utility of PMPatch 0.5.13 coderush, I opened the Terminal and I entered the PMPatch file, so it's not like you say, you have to rename the file.

You write this : No need to use BIOS renamer, just name the patched file R4E.CAP and you're good to go.

 

So It's not like you say ,
 
and this is the result, you can see by the path in the Terminal

 

localhost:~ carmine$ /Users/carmine/Desktop/NewBios/PMPatch /Users/carmine/Desktop/NewBios/Rampage-IV-Extreme-ASUS-4102.CAP /Users/carmine/Desktop/NewBios/R4E.CAP
PMPatch 0.5.13
PowerManagement modules not found.
PowerMgmtDxe/PowerManagement2.efi modules not found.
AMI nest modules not found.
Phoenix nest modules not found.
CpuPei module at 0079CAC8 patched.
CpuPei module at 007DCAC8 patched.
Output file generated.
localhost:~ carmine$

 

Perhaps, as regards USB FLASH BACK, meant that the right way to Flash was just this, because Asus EZ Flash cannot read mod file because it has a broken safety control
 
End of story
and I don't want to make unnecessary controversy, thanks for your help
 
:wink_anim:


#490
bdv

bdv

    InsanelyMac Protégé

  • Donators
  • 64 posts
  • Gender:Male
  • Location:France, Near Bordeaux
  • Interests:Italian motorcycles riding and fixing, computers, cats, pre-print design.

 

;)

and this a message error

so for me i need rename file...in .rom , but dont work also i rename in.rom

localhost:~ carmine$ /Users/carmine/Desktop/NewBios/PMPatch
PMPatch 0.5.13
This program patches UEFI BIOS files
to be compatible with Mac OS X SpeedStep implementation

Usage: PMPatch INFILE OUTFILE

localhost:~ carmine$ /Users/carmine/Desktop/NewBios/Rampage-IV-Extreme-ASUS-4102.CAP
-bash: /Users/carmine/Desktop/NewBios/Rampage-IV-Extreme-ASUS-4102.CAP: cannot execute binary file
localhost:~ carmine$

You got this error message because you do not type the correct command line:

 

Usage: PMPatch INFILE OUTFILE

 

so you should type, for instance:

 

PMPatch  Rampage-IV-Extreme-ASUS-4102.CAP  NEW_Rampage-IV-Extreme-ASUS-4102.CAP

 

But you use only Rampage-IV-Extreme-ASUS-4102.CAP as a command line, without the program and the output file...



#491
fwood

fwood

    InsanelyMac Deity

  • Members
  • PipPipPipPipPipPipPipPipPipPip
  • 2,170 posts
  • Gender:Male
  • Interests:Music producer

Hi guys...i'll almost to buy exactly the same motherboard of Magnifico (Rampage-IV-Extreme). I cannot understand 2 things:

1/  after modding process of bios...in the future i'll have to use always the PM.kext, or  i'll be fine just with bios ?

2/ If i'll need always the powermanagement kext ....it must be a  patched kext , or also an original untouched powermanagement kext will work?

Thank you very much in advance!



#492
CodeRush

CodeRush

    InsanelyMac Sage

  • Developers
  • 401 posts
  • Gender:Male
  • Location:Deggendorf, Germany

I was contacted by Jose Philips today via Skype, he has found a BIOS file, that can't be patched by PMPatch. It's normal to find one, but this file is definitely special and worth telling it's story.

Behold, a new version 2209 of Intel UEFI BIOS for old Intel DP67BG board. Looks like normal UEFI BIOS, behaves like normal UEFI BIOS, what's special about it?

First, it can't be patched by any current patch included in PMPatch, I'm OK with that, next.

Second, it can be opened by PhoenixTool 2.14, big thanks go to AndyP, it's cool, next.

Third and finally, this file is an Intel's tribute to Inception movie, because it has modules with 12 (twelwe!) levels of inclusion (EFI Capsule->Firmware Volume->File->File->...->File). 

The module with locking code has only 9 levels of inclusion, which is a kid level for this UEFI BIOS.

Intel has also removed all UI sections from their modules, so we can name one a "PowerManagement module" or something. There are only GUIDs, they are for real men.

The module with 0xE2 locking code has 62D171CB-78CD-4480-8678-C6A2A797A8DE GUID and there are 2 copies of this module in that BIOS.

The locking code itself is nothing special:

  0000000000005E4E: B9 E2 00 00 00     mov         ecx,0E2h                ; copy 0xE2 MSR number to ECX
  0000000000005E53: E8 EA AE 00 00     call        0000000000010D42        ; rdmsr inside  
  0000000000005E58: 48 89 44 24 28     mov         qword ptr [rsp+28h],rax ; copy read value of 0xE2 from RAX to some memory address
  0000000000005E5D: 48 8B 44 24 28     mov         rax,qword ptr [rsp+28h] ; copy the same value back to RAX (not sure if too smart or just stupid)
  0000000000005E62: 48 25 00 80 00 00  and         rax,8000h               ; set all bits of RAX except 15 (LOCK) to 0
  0000000000005E68: 48 85 C0           test        rax,rax                 ; test if lock bit is already set
  0000000000005E6B: 75 31              jne         0000000000005E9E        ; if so, jump over the next 10 lines 
  0000000000005E6D: B9 E2 00 00 00     mov         ecx,0E2h                ; if not, copy 0xE2 MSR number to ECX again
  0000000000005E72: E8 CB AE 00 00     call        0000000000010D42        ; rdmsr inside
  0000000000005E77: 48 89 44 24 28     mov         qword ptr [rsp+28h],rax ; RAX to memory
  0000000000005E7C: 48 8B 44 24 28     mov         rax,qword ptr [rsp+28h] ; memory to RAX (I like to move it, move it ...)
  0000000000005E81: 48 0D 00 80 00 00  or          rax,8000h               ; set bit 15 (LOCK) of RAX to 1 
  0000000000005E87: 48 89 44 24 28     mov         qword ptr [rsp+28h],rax ; RAX to memory
  0000000000005E8C: 48 8B 44 24 28     mov         rax,qword ptr [rsp+28h] ; memory to RAX (You like to move it, move it ...)
  0000000000005E91: 48 8B D0           mov         rdx,rax                 ; copy RAX to RDX
  0000000000005E94: B9 E2 00 00 00     mov         ecx,0E2h                ; copy 0xE2 MSR number to ECX
  0000000000005E99: E8 62 4D 00 00     call        000000000000AC00        ; wrmsr inside
  0000000000005E9E: E8 79 AB 00 00     call        0000000000010A1C        ; execution continues here

The patch itself is 73 31 to EB 31, which disables WRMSR part of this code. Can be done with PhoenixTool now.

I have no plans for integrating this patch to PMPatch, because will be really a chalenge to implement 9 levels of inclusion traversal without any traversal code. Will be done some day, I hope. 

Modified BIOS file is attached.

Attached Files



#493
bdv

bdv

    InsanelyMac Protégé

  • Donators
  • 64 posts
  • Gender:Male
  • Location:France, Near Bordeaux
  • Interests:Italian motorcycles riding and fixing, computers, cats, pre-print design.

Hi guys...i'll almost to buy exactly the same motherboard of Magnifico (Rampage-IV-Extreme). I cannot understand 2 things:

1/  after modding process of bios...in the future i'll have to use always the PM.kext, or  i'll be fine just with bios ?

2/ If i'll need always the powermanagement kext ....it must be a  patched kext , or also an original untouched powermanagement kext will work?

Thank you very much in advance!

 

To run OSX with Apple PowerManagement, you have 3 solutions:

1) use a motherboard with a bios that permits it (mainly Gigabyte  boards)

2) use a patched AICPUPM kext

3) use a patched bios that will make your "locked" bios to behave like case #1 (Asus, Asrock and a lot of other brands).

 

Once you patched your bios using PMPatch or PhoenixTools or other methods, you can install and run with vanilla PM.

It is the whole point of patching your bios: you do not have to use patched kext anymore for PM.



#494
fwood

fwood

    InsanelyMac Deity

  • Members
  • PipPipPipPipPipPipPipPipPipPip
  • 2,170 posts
  • Gender:Male
  • Interests:Music producer

To run OSX with Apple PowerManagement, you have 3 solutions:

1) use a motherboard with a bios that permits it (mainly Gigabyte  boards)

2) use a patched AICPUPM kext

3) use a patched bios that will make your "locked" bios to behave like case #1 (Asus, Asrock and a lot of other brands).

 

Once you patched your bios using PMPatch or PhoenixTools or other methods, you can install and run with vanilla PM.

It is the whole point of patching your bios: you do not have to use patched kext anymore for PM.

Thanks mate...now it's clear!



#495
meatlover

meatlover

    InsanelyMac Protégé

  • Members
  • Pip
  • 4 posts

I have an Asus UX32VD laptop which has UEFI installed on. But recently I just switched it to SSD and now if I look into the Windows/Panther directory in one of the file. I dont see UEFI anymore only BIOS. Can I fix this problem before marching on with OSX86 installation



#496
Gringo Vermelho

Gringo Vermelho

    The Jan Bird fix

  • Supervisors
  • 6,112 posts
  • Gender:Male
  • Location:Brazil

You can just leave it as it is and install OS X.  As far as I know there are no real benefits to using UEFI mode over legacy mode, it seems to me to be mostly in the "because I can" department.

 

Someone correct me if I'm wrong.



#497
TimeWalker75a

TimeWalker75a

    InsanelyMac Legend

  • Gurus
  • 1,065 posts
  • Gender:Male
You use real NVRAM and thus can use bootcamp to restart from Windows to OSX from Startup Disk. Thats the obky pro I can think of...

#498
meatlover

meatlover

    InsanelyMac Protégé

  • Members
  • Pip
  • 4 posts

I've tried using vmware but this program detects that i have unavailable uefi, installation cannot be continued



#499
Gringo Vermelho

Gringo Vermelho

    The Jan Bird fix

  • Supervisors
  • 6,112 posts
  • Gender:Male
  • Location:Brazil

Please don't derail this thead any further. If you want to talk about installing OS X on a virtual machine then go here:

http://www.insanelym...virtualisation/



#500
STLVNUB

STLVNUB

    InsanelyMac Legend

  • Coders
  • 1,127 posts
  • Gender:Male

This tool should be developed further, like PhoenixTool for OS X







Also tagged with one or more of these keywords: BIOS, patch, power management, UEFI


3 user(s) are reading this topic

0 members, 3 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy