Jump to content
CodeRush

[UEFIPatch] UEFI patching utility

1,989 posts in this topic

Recommended Posts

Can you confirm this correct patched

Last login: Wed Oct  2 06:28:49 on console

manoranjans-MacBook-Pro-2:~ manoranjan$ /Users/manoranjan/Desktop/PMPatch /Users/manoranjan/Desktop/P8Z77-V-PRO-ASUS-2104.CAP /Users/manoranjan/Desktop/P8Z77-V-PRO-ASUS-2104 PATCHED.CAP

PMPatch 0.5.11

PowerManagement module at 00422C90 patched.

AMI nest modules not found.

Phoenix nest modules not found.

CpuPei module at 00792020 not patched: Patch pattern not found.

CpuPei module at 007D2020 not patched: Patch pattern not found.

Output file generated.

manoranjans-MacBook-Pro-2:~ manoranjan$

Share this post


Link to post
Share on other sites
Advertisement

Can you confirm this correct patched

Last login: Wed Oct  2 06:28:49 on console

manoranjans-MacBook-Pro-2:~ manoranjan$ /Users/manoranjan/Desktop/PMPatch /Users/manoranjan/Desktop/P8Z77-V-PRO-ASUS-2104.CAP /Users/manoranjan/Desktop/P8Z77-V-PRO-ASUS-2104 PATCHED.CAP

PMPatch 0.5.11

PowerManagement module at 00422C90 patched.

AMI nest modules not found.

Phoenix nest modules not found.

CpuPei module at 00792020 not patched: Patch pattern not found.

CpuPei module at 007D2020 not patched: Patch pattern not found.

Output file generated.

manoranjans-MacBook-Pro-2:~ manoranjan$

Yes it is correct

Share this post


Link to post
Share on other sites

Asus Sabertooth P67 B3.

Successfully patched 3602 ROM to allow sleep in Mac OSX 10.8.5. Sleep now works. 

Thank you very much Coderush!!!

 

Any help with getting audio going on this board on a mac? Looks like going down from 3XXX bios to 2XXX is not possible?

Share this post


Link to post
Share on other sites

Normal AppleHDA patching for specific HDA chip will work on this board. And it has unlocked flash descriptor, so BIOS downgrade is possible, but only with non-vendor BIOS flasher.

Please stay on 3xxx, if there is no big deal.

Share this post


Link to post
Share on other sites

Coderush, your just awesome for all the hard work you put in for us all. I did try the ALC892 patch from [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] and it did not work. Then when I tried  adding voodoo on top of that my system KPed.

 

Thank you!

 

Peter

Share this post


Link to post
Share on other sites

There are many people here that are good with AppleHDA patching, I think. Asking in another topic may help. :)

Now I personally have nothing to do with OSX, and all my knowledge of it is very limited.

Share this post


Link to post
Share on other sites

no, it's a dos executable, you can get a dos bootstick image at bootdisk.com or created one as explained here chip.de

Hi Fix It Felix Jr.,

I made a DOS bootable disk and executed the modded bios. After reboot it says "Secure Flash Check Fail". Is there anything I am missing? 

 

Thanks.

Share this post


Link to post
Share on other sites

Is it possible for you to lead me to a link to get my 3XXX bios downgraded to 2XXX on my Sabertooth P67 B3 motherboard? Apparently there is an issue with the 3XXX bios that will not allow my ACL892 audio to work with it on a Mac. It needs to be a 2XXX bios. I have no bios flashback option.

 

Thank you

Share this post


Link to post
Share on other sites

Is it possible for you to lead me to a link to get my 3XXX bios downgraded to 2XXX on my Sabertooth P67 B3 motherboard? Apparently there is an issue with the 3XXX bios that will not allow my ACL892 audio to work with it on a Mac. It needs to be a 2XXX bios. I have no bios flashback option.

 

Thank you

If you call the bios flash program in cmd, you can get the option keys. There should be one for ignoring the version. You can look in bios mod forums for that.

 

Have fun.

Share this post


Link to post
Share on other sites

If you call the bios flash program in cmd, you can get the option keys. There should be one for ignoring the version. You can look in bios mod forums for that.

 

Have fun.

No luck there. Thank you for trying though.

Share this post


Link to post
Share on other sites

Hi guys

I am looking patched bios and DSDT for ASUS p8z77-v pro

IF you have upload for us.

Thank you.

This is ori bios 2104 ple unlock for me.

ori.zip

Share this post


Link to post
Share on other sites

Hi..

sorry the dummy question..

this file you send is the full patched bios..

that is it..?

I only have to change the original one to this one..like a flash update..?

thank you...

"this is not my beach"

c.frio

Share this post


Link to post
Share on other sites

Hi..

sorry the dummy question..

this file you send is the full patched bios..

that is it..?

I only have to change the original one to this one..like a flash update..?

thank you...

"this is not my beach"

c.frio

yes, just change the filename and flash.

Share this post


Link to post
Share on other sites

yes, just change the filename and flash.

sorry again..change to which name..? I never played with bios...

c.frio

Share this post


Link to post
Share on other sites

Hi guys

I am looking patched bios and DSDT for ASUS p8z77-v pro

IF you have upload for us.

Thank you.

This is ori bios 2104 ple unlock for me.

Hi All

Can you fixed bios file ple

Share this post


Link to post
Share on other sites

All Credits to Fix It Felix Jr.

 

With his help I could pmpatch my bios. Here is the steps:

 

Motherboard: ASRock Z87 Extreme4

Bios version: 2.30

 

1. Install the latest factory bios using Instant Flash tool

2. Download amiflash tool from ami support site. I used afudos from aptio folder.

3. run afudos bios.bin /o

4. You will have bios.bin which now needs to be patched using pmpatch tool

5. after pmpatching you will have pmpatched.bin (patched bios)

6. run afudos pmpatched.bin /gan

7. This will rewrite the patched bios

 

To test patching actually worked, run steps #3 and #4 again and see if pmpatch actually finds anything patchable. If none found, the first attempt worked.

 

Thanks again Fix It Felix Jr.

 

 

Share this post


Link to post
Share on other sites

Hi Felix

just one more and last question about......this bios is the  LAST ONE (patched) for the  AsrockH87M pro4..that is it?

taking courage...

c.frio

Share this post


Link to post
Share on other sites

C.Frio,

 

On Z87 board I can recommend the method as explained by Mainul. There will be no capsule issues.

It's easier to apply and it works ; )

The patched ROM from you has 8.196 KB which is 4KB overhead. I'd not mess with it.

 

Better use afudos /gan method instead.

 

You can even do it all from windows as pmpatch is provided as windows executable,

steps:

  1. backup: afuwinx64 bios.bin /o
  2. patch: pmpatch bios.bin bios-pmpatched.bin
  3. apply: afuwinx64 bios-pmpatched.bin /gan

verification after reboot:

  1. backup: afuwinx64 bios.bin /o
  2. test: pmpatch bios.bin bios-pmpatched.bin

will report there's nothing left to patch.

Voila, you have a pmpatched UEFI now.

 

Most important: don't use a different bios version, it potentially causes bricks. Work only with the created backup bios.

 

The AFU for APTIO /GAN switch appears to serve the same purpose as /SANTA on AFU for regular BIOS.

Share this post


Link to post
Share on other sites

hi

so you recommend to make another one?instead that one you send to me...?

or I can use the one you send?

 

can I use de "instant flash" from MB -it is recommended?

I do not have windows installed..

c.frio

 

it is like a snow ball for me...

Share this post


Link to post
Share on other sites

The vendor will recommend his own tools, but all the vendor tools have their traps, especially with mods.

My last post explains how you can do it the right way, if you have windows installed.

Create a fresh one on your own, it's as easy as described ;)

With this method you'll keep all your SMBIOS and NVRAM entries as is.

Share this post


Link to post
Share on other sites

hi..

 

tks...

c.frio :thumbsup_anim:

 

Should I expect they fix this "need to be patched to work" with a "module" or bootloader..as Chameleon and so on...?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Majed DH
      Hi everyone. 
      I have HP 15-da0xxx series laptop. i got macos mojave installed on it. but I was trying to get my intel graphics working but i couldn't change dmvt preallocation. 
      So I updated the bios (unfortunately). And since then i could not boot any version of clover. 
      I tried two versions that were working and even an installer that worked before is not working:
       
      I searched alot about the error and found nothing relared to macos or hackintosh..  would it be solved by patching the dsdt? 

      Any suggestions people ? 
    • By SoThOr
      This was spurred on from a discussion in the Clover General thread. Where there was a debate on bcdedit being able create/read/edit (U)EFI Boot entries. I didn't think it appropriate to post all this information there and somebody may want to make use of this and its likely to get lost in that massive thread.
       
      Out of curiosity I decided to see if I could create an EFI entry using bcdedit. What can I say I like a challenge.  Whilst is not a documented method by Microsoft, as it turns out in a round about way it IS possible to create an EFI entry using bcdedit and these are the steps I went through to add UEFI Shell located on a USB stick to the EFI entries. 
       
      Third party software is available that can create and edit UEFI entries from Windows with better support and more features. I'm just making this information available in case those options are unavailable. 
       
      DISCLAIMER - This is not a supported method. Use at your own risk. I recommend backing up your BCD/Firmware variables/settings beforehand.
       
      1) Copy {bootmgr} entry.
      C:\Windows\System32>bcdedit /copy {bootmgr} /d "UEFI Shell" The entry was successfully copied to {34e8383c-73a7-11e9-9cb0-94de8078a7b5}. 2) Edit the new entry using the new GUID bcdedit generated in the copy step.
        a) Set the device and path for UEFI shell on my USB stick.
      bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} device partition=G: bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} path \EFI\SHELL\SHELLX64.efi   b) Clean up some of the stuff that was copied from {bootmgr} (optional as far as I can tell, just makes things tidier in bcdedit)
      3) Put the new EFI entry first in boot order. (optional)
       
      After completing the steps above, here is what "bcdedit /enum firmware" shows:
       
      I shutdown my computer and when I turned my computer back on it booted up into UEFI Shell. After exiting the shell my PC went on to boot Windows.
      Here is the resulting dump using "bcfg boot dump -v" from that shell:
       
      You may notice that the shell shows as "Windows Boot Manager" in the bcdedit output. This I believe is because of the "WINDOWS" at the beginning of the option data that bcdedit added to the EFI Boot entry. I also believe this why bcdedit shows my Windows 8 installation as "Firmware Application" because it has no option data. I don't know how to remove this data using bcdedit nor do I know how the option data, that bcdedit adds, will affect other EFI applications.

      There might be a way to create the EFI entry without copying the Windows entry but if there is I'm unable to find any documentation on how one would do so. If you use the create command then it just puts it in the BCD and I'm unaware of a way to tell it to create it in EFI instead, other than by doing the above.
    • By d2a
      So I'm finally joining the grown-ups and trying to set up a new(ish) hack. In the past I've used legacy Clover with my old Gigabyte board and thought I knew what I was doing. But I've been trying to get a UEFI Clover-based install to work and it's going nowhere.
       
      My new system (listed as SysB in sig) is a Gigabyte Z97X-UD3H-BK rev1.1 with firmware F6, an i7 4790K CPU and 4x4GB Corsair 1866MHz. I have the firmware settings set as per various guides and thought this should be a pretty painless transition...
       
      I have successfully run the installer for El Cap several times, but can't get the machine to boot reliably - it seems to change behaviour each boot. Sometimes boot hangs at the Gigabyte logo after choosing boot volume via F12, sometimes it boots to clover but displays no bootable drives, sometimes displays ElCap SSD in Clover but wont boot from it with kernel cache error, and occasionally it will boot all the way.
       
      What I'd like to know is:
       
      Should I update the mobo firmware to the latest version? This board has two more recent Bios software downloads, but they wont allow me to drop back to the version currently installed. I'm nervous to update unless this is likely to be the culprit. Is this just a UEFI issue? If the simple answer is just go legacy mode, maybe I should just avoid the issue... FInally, does anyone else have a working clover install on this board they could share with me? I think I've got it set up as it should be but the strange inconsistent boot behaviour makes me wonder... Thanks
×