[UEFIPatch] UEFI patching utility

[TimeWalker75a]

Why would you rename it? You just have to specify the actual input file and the name of the output file which will be created if the patching has been done successfully. There shouldn't be an output file of that name unless the program produces a valid output and you can tell it has done so when you see a "Output file generated." message.

[magnifico]

Why would you rename it? You just have to specify the actual input file and the name of the output file which will be created if the patching has been done successfully. There shouldn't be an output file of that name unless the program produces a valid output and you can tell it has done so when you see a "Output file generated." message.

so put two times Rampage-IV-Extreme-ASUS-4206.CAP in terminal ?

[TimeWalker75a]

PMPatch [existing_bios_file_as_input_file] [non-existing_bios_file_as_output_file]

 

Example:

PMPatch  Rampage-IV-Extreme-ASUS-4206.CAP patched_bios.CAP

[tonydickinson]

@ magnifico

 

Trying to help you is a waste of time and effort, and you responded by saying you were not happy using USB flashback. Gringo and others went to great lengths to help you with the input and output filenames last time. Yet now you are asking the same questions again.

 

On 1st Aug I said to you by direct email.

 

 

Carmine,

Did you see there is a new BIOS for your motherboard 4206?

I have downloaded and modded it with PMPATCH the file is named R4E.CAP - believe that is correct or your MB.

 

This just needs loading as it is  - using USB flashback.

 

File was attached...

[magnifico]

@ magnifico

 

Trying to help you is a waste of time and effort, and you responded by saying you were not happy using USB flashback. Gringo and others went to great lengths to help you with the input and output filenames last time. Yet now you are asking the same questions again.

 

On 1st Aug I said to you by direct email.

 

 

Carmine,[/size]Did you see there is a new BIOS for your motherboard 4206?[/size]I have downloaded and modded it with PMPATCH the file is named R4E.CAP - believe that is correct or your MB.[/size]

 

This just needs loading as it is  - using USB flashback.[/size]

 

File was attached...

 

Tony no, no .... I have not tried your patched bios, because I think it still is not 'the time to do this, there are still problems on x79, I read news from around are quite vague about the future of x79 ... for now I do not flash the bios, but I your buck up, even though I figured out how to patch the original bios are always very helpful .... thanks

 

Ps : maybe when exit maverics or 10.8.5 all working for PM

[DislikeYou]

Hi CodeRush, I have ASUS GRYPHON Z87 and in Clover I set:

 

<key>AsusAICPUPM</key>
<false/>

 

and OSX boots fine, I don't have a patched bios.

 

Can you explain this, it must mean that the region is not locked on this bios???

Edit: Other user with Asus Z87-DELUXE-DUAL board confirmed that he had same results.

 

So it means that the region is really unlocked. Great news! 

[Cobra03]

 

Hi CodeRush, I have ASUS GRYPHON Z87 and in Clover I set:

 

<key>AsusAICPUPM</key>
<false/>

 

and OSX boots fine, I don't have a patched bios.

 

Can you explain this, it must mean that the region is not locked on this bios???

Edit: Other user with Asus Z87-DELUXE-DUAL board confirmed that he had same results.

 

So it means that the region is really unlocked. Great news! 

 

Do you have AICPUPM loaded?

[thunderbug]

Hi there,

 

First I want to say thank you CodeRush for creating such a cool tool.

 

I have an ASUS Z87-Pro mainboard. The bios patch worked but the flashback doesn't. The green led stops blinking after 5 seconds. I used a 4gb uab stick fat32 formatted. I think it's because I've used a wrong filename for the bios file. I tried "Z87PRO.CAP" but it didn't work. I also tried to find the filename on the internet+ in the mainboard manual without success

So does anyone know the correct bios filename for my mainboard? (or did I do something else wrong?)

thanks

[CodeRush]

Try using another USB flash, thre are some incompatible ones. You can use ASUS BRenamer utility to rename your BIOS file correctly.

[bcc9]

Write protection for BIOS region on P8Z77-V LK introduced with 1103.

Note that you can rollback to older bios, patch the newer protected bios with pmpatch, and flash to it.

I just did that on my p8h77-m system which is in the same situation. (1301 bios adds the protection, older bioses don't). But the newer bios has better CSM graphics support so I wanted to switch in spite of the extra hassle.

[k3nny]

Note that you can rollback to older bios, patch the newer protected bios with pmpatch, and flash to it...

Thanks for the hint, I noticed it during my experiments. Sadly you can't use this option with new boards.

 

Could you write more about the better CSM graphics support, please? Currently I use the older unprotected version because I didn't see any visible advantage yet. There have been many changes under the hood but Asus seems rather lazy when writing the changelog.

[magnifico]

Thanks for the hint, I noticed it during my experiments. Sadly you can't use this option with new boards.

 

Could you write more about the better CSM graphics support, please? Currently I use the older unprotected version because I didn't see any visible advantage yet. There have been many changes under the hood but Asus seems rather lazy when writing the changelog.

i have a gigabyte nd 660 oc and for me it is a good

Sorry for oT

[bcc9]

Thanks for the hint, I noticed it during my experiments. Sadly you can't use this option with new boards.

Yes, I don't know about everyone else, but I'll be sure not to buy or recommend any more asus systems anytime soon due to these shenanigans. Crazy to make the bios actively prevent the system's owner from managing the system. What do they think this is a subsidized iphone?

Could you write more about the better CSM graphics support, please? Currently I use the older unprotected version because I didn't see any visible advantage yet. There have been many changes under the hood but Asus seems rather lazy when writing the changelog.

There was no mention in the changelog, I just noticed it. Briefly, since it's off topic, looks like they now make use of the higher resolutions found in a monitor's EDID, in the details timings section. This fixes black screen situations on monitors that can't scale the hard-coded low resolution 1024x768 that the EFI CSM driver really wants to use. I posted a bunch of details on this over at projectosx.

[DislikeYou]

Do you have AICPUPM loaded?

Thanks for asking that, you remembered me to check kextstat, and it shows.

Index Refs Address            Size       Wired      Name (Version) <Linked Against>
    1   59 0xffffff7f807d1000 0x8d80     0x8d80     com.apple.kpi.bsd (13.0.0)
    2    6 0xffffff7f80867000 0x28c0     0x28c0     com.apple.kpi.dsep (13.0.0)
    3   74 0xffffff7f807b3000 0x1dfb0    0x1dfb0    com.apple.kpi.iokit (13.0.0)
    4   81 0xffffff7f807a4000 0xbf40     0xbf40     com.apple.kpi.libkern (13.0.0)
    5   72 0xffffff7f807b0000 0x2d10     0x2d10     com.apple.kpi.mach (13.0.0)
    6   34 0xffffff7f8081c000 0x7d40     0x7d40     com.apple.kpi.private (13.0.0)
    7   52 0xffffff7f80824000 0x48e0     0x48e0     com.apple.kpi.unsupported (13.0.0)
    8    0 0xffffff7f80904000 0xb000     0xb000     com.apple.kec.pthread (1) <7 6 5 4 1>
    9    2 0xffffff7f80fea000 0x47000    0x47000    com.apple.kec.corecrypto (1.0) <7 6 5 4 3 1>
   10   14 0xffffff7f812d3000 0x9000     0x9000     com.apple.iokit.IOACPIFamily (1.4) <7 6 4 3>
   11   20 0xffffff7f80829000 0x2d000    0x2d000    com.apple.iokit.IOPCIFamily (2.8) <7 6 5 4 3>
   12    1 0xffffff7f81fe6000 0x5f000    0x5f000    com.apple.driver.AppleACPIPlatform (3.0) <11 10 7 6 5 4 3 1>
   13    1 0xffffff7f81031000 0xb000     0xb000     com.apple.driver.AppleFDEKeyStore (28.30) <9 7 6 5 4 3 1>
   14    1 0xffffff7f812c2000 0x11000    0x11000    com.apple.iokit.IOReportFamily (21) <5 4 3>
   15    8 0xffffff7f8086d000 0x2d000    0x2d000    com.apple.iokit.IOStorageFamily (1.9) <7 6 5 4 3 1>
   16    0 0xffffff7f81322000 0x1e000    0x1e000    com.apple.driver.DiskImages (370) <15 7 6 5 4 3 1>
   17    0 0xffffff7f81d86000 0x14000    0x14000    com.apple.driver.AppleKeyStore (2) <9 7 6 5 4 3 1>
   18    2 0xffffff7f816bf000 0x14000    0x14000    org.netkas.driver.FakeSMC (755) <10 7 5 4 3 1>
   19    0 0xffffff7f8170f000 0x4000     0x4000     org.hwsensors.driver.CPUSensors (755) <18 7 5 4 3>
   20    0 0xffffff7f8086a000 0x3000     0x3000     com.apple.security.TMSafetyNet (7) <7 6 5 4 2 1>
   21    2 0xffffff7f808e3000 0x5000     0x5000     com.apple.kext.AppleMatch (1.0.0d1) <4 1>
   22    1 0xffffff7f808e8000 0x14000    0x14000    com.apple.security.sandbox (278.6) <21 7 6 5 4 3 2 1>
   23    0 0xffffff7f808fc000 0x7000     0x7000     com.apple.security.quarantine (3) <22 21 7 6 5 4 2 1>
   24    0 0xffffff7f82056000 0x8000     0x8000     com.apple.nke.applicationfirewall (153) <7 6 5 4 3 1>
   25    0 0xffffff7f81fba000 0x3000     0x3000     com.apple.driver.AppleAPIC (1.7) <4 3>
   26    0 0xffffff7f81cac000 0x4000     0x4000     com.apple.driver.AppleSMBIOS (2.0) <7 4 3>
   27    0 0xffffff7f81f28000 0x3000     0x3000     com.apple.driver.AppleHPET (1.8) <10 7 5 4 3>
   28    0 0xffffff7f81cd8000 0x7000     0x7000     com.apple.driver.AppleRTC (2.0) <10 5 4 3 1>
   29    2 0xffffff7f8103c000 0x85000    0x85000    com.apple.iokit.IOHIDFamily (2.0.0) <13 7 6 5 4 3 2 1>
   30    0 0xffffff7f8204f000 0x4000     0x4000     com.apple.driver.AppleACPIButtons (3.0) <29 12 10 7 6 5 4 3 1>
   31    1 0xffffff7f81f95000 0x5000     0x5000     com.apple.driver.AppleEFIRuntime (2.0) <7 6 5 4 3>
   32    0 0xffffff7f81f9a000 0xa000     0xa000     com.apple.driver.AppleEFINVRAM (2.0) <31 7 6 5 4 3>
   33    8 0xffffff7f80f68000 0x6b000    0x6b000    com.apple.iokit.IOUSBFamily (650.4.1) <11 7 5 4 3 1>
   34    0 0xffffff7f810d1000 0x1d000    0x1d000    com.apple.driver.AppleUSBXHCI (650.4.1) <33 11 7 5 4 3 1>
   35    0 0xffffff7f8114d000 0x18000    0x18000    com.apple.driver.AppleUSBEHCI (650.4.1) <33 11 7 5 4 3 1>
   36    3 0xffffff7f814b3000 0x19000    0x19000    com.apple.iokit.IOAHCIFamily (2.6.0) <5 4 3 1>
   37    0 0xffffff7f81fbf000 0x1a000    0x1a000    com.apple.driver.AppleAHCIPort (2.9.0) <36 11 5 4 3 1>
   38    2 0xffffff7f80f27000 0x34000    0x34000    com.apple.iokit.IONetworkingFamily (3.2) <7 6 5 4 3 1>
   39    0 0xffffff7f81ea7000 0x18000    0x18000    com.insanelymac.driver.AppleIntelE1000e (2.3.2) <38 11 5 4 3 1>
   41    0 0xffffff7f816e9000 0x15000    0x15000    org.hwsensors.driver.GPUSensors (755) <18 11 10 7 5 4 3>
   42    0 0xffffff7f80fe7000 0x3000     0x3000     com.apple.iokit.IOUSBUserClient (650.4.0) <33 7 5 4 3 1>
   43    0 0xffffff7f8112f000 0x17000    0x17000    com.apple.driver.AppleUSBHub (650.4.1) <33 5 4 3 1>
   44    0 0xffffff7f814d9000 0x17000    0x17000    com.apple.iokit.IOAHCIBlockStorage (2.4.0) <36 15 6 5 4 3 1>
   45    3 0xffffff7f807da000 0x31000    0x31000    com.apple.iokit.IOSCSIArchitectureModelFamily (3.6.0) <5 4 3 1>
   46    0 0xffffff7f814cc000 0xd000     0xd000     com.apple.iokit.IOAHCISerialATAPI (2.6.0) <45 36 5 4 3 1>
   47    0 0xffffff7f81afe000 0x3000     0x3000     com.apple.driver.XsanFilter (404) <15 5 4 3 1>
   48    0 0xffffff7f8180d000 0x9000     0x9000     com.apple.BootCache (35) <7 6 5 4 3 1>
   49    0 0xffffff7f81f86000 0x4000     0x4000     com.apple.AppleFSCompression.AppleFSCompressionTypeZlib (1.0.0d1) <6 4 3 2 1>
   50    0 0xffffff7f81f8c000 0x3000     0x3000     com.apple.AppleFSCompression.AppleFSCompressionTypeDataless (1.0.0d1) <7 6 4 3 2 1>
   52    0 0xffffff7f8126e000 0x7000     0x7000     com.apple.iokit.SCSITaskUserClient (3.6.0) <45 15 5 4 3 1>
   53    3 0xffffff7f81279000 0x11000    0x11000    com.apple.iokit.IOCDStorageFamily (1.7.1) <15 5 4 3 1>
   54    2 0xffffff7f8128a000 0xe000     0xe000     com.apple.iokit.IODVDStorageFamily (1.7.1) <53 15 5 4 3 1>
   55    1 0xffffff7f81298000 0xc000     0xc000     com.apple.iokit.IOBDStorageFamily (1.7) <54 53 15 5 4 3 1>
   56    0 0xffffff7f812a4000 0x1e000    0x1e000    com.apple.iokit.IOSCSIMultimediaCommandsDevice (3.6.0) <55 54 53 45 15 5 4 3 1>
   57    0 0xffffff7f810ca000 0x7000     0x7000     com.apple.driver.AppleUSBComposite (650.4.0) <33 4 3 1>
   58    0 0xffffff7f810c1000 0x9000     0x9000     com.apple.iokit.IOUSBHIDDriver (650.4.1) <33 29 5 4 3 1>
   60    8 0xffffff7f80925000 0x43000    0x43000    com.apple.iokit.IOGraphicsFamily (2.3.6) <11 7 5 4 3 1>
   61    2 0xffffff7f80968000 0x10000    0x10000    com.apple.iokit.IONDRVSupport (2.3.6) <60 11 7 5 4 3>
   62    3 0xffffff7f812dc000 0xa000     0xa000     com.apple.driver.IOPlatformPluginFamily (5.5.1d21) <10 7 6 5 4 3>
   63    0 0xffffff7f81d7e000 0x3000     0x3000     com.apple.driver.AppleLPC (1.7.0) <62 11 5 4 3>
   65    1 0xffffff7f812e6000 0x14000    0x14000    com.apple.driver.IOPlatformPluginLegacy (1.0.0) <62 10 7 6 5 4 3>
   66    2 0xffffff7f812fa000 0x11000    0x11000    com.apple.driver.AppleSMC (3.1.6d1) <10 7 5 4 3>
   67    0 0xffffff7f8130b000 0x10000    0x10000    com.apple.driver.ACPI_SMC_PlatformPlugin (1.0.0) <66 65 62 11 10 7 6 5 4 3>
   68    1 0xffffff7f81828000 0x11000    0x11000    com.apple.kext.OSvKernDSPLib (1.14) <5 4>
   69    1 0xffffff7f81839000 0x37000    0x37000    com.apple.iokit.IOAudioFamily (1.9.4fc3) <68 5 4 3 1>
   70    0 0xffffff7f81b53000 0x51000    0x51000    com.apple.driver.AppleUSBAudio (2.9.3f15) <69 33 5 4 3>
   71    1 0xffffff7f81dc7000 0x6000     0x6000     com.apple.AppleGraphicsDeviceControl (3.4.12) <7 6 5 4 3 1>
   72    1 0xffffff7f81dcd000 0x72000    0x72000    com.apple.iokit.IOAcceleratorFamily2 (98.6) <60 11 7 6 5 4 3 1>
   73    0 0xffffff7f81e3f000 0x51000    0x51000    com.apple.driver.AppleIntelFramebufferAzul (8.1.8) <72 71 60 11 10 7 6 5 4 3 1>
   74    2 0xffffff7f80978000 0x274000   0x274000   com.apple.nvidia.driver.NVDAResman (8.1.8) <61 60 11 5 4 3 1>
   75    0 0xffffff7f80bec000 0x1c4000   0x1c4000   com.apple.nvidia.driver.NVDAGK100Hal (8.1.8) <74 11 4 3>
   76    0 0xffffff7f81f04000 0x3000     0x3000     com.apple.driver.AppleHWAccess (1) <7 5 4 3>
   77    0 0xffffff7f81716000 0x5000     0x5000     com.apple.Dont_Steal_Mac_OS_X (7.0.0) <66 7 4 3 1>
   80    1 0xffffff7f81594000 0x64000    0x64000    com.apple.iokit.IOAcceleratorFamily (98.6) <60 11 7 6 5 4 3 1>
   81    0 0xffffff7f815f8000 0x8f000    0x8f000    com.apple.GeForce (8.1.8) <80 74 61 60 11 7 5 4 3 1>
   82    1 0xffffff7f81265000 0x4000     0x4000     com.apple.iokit.IOSMBusFamily (1.1) <5 4 3>
   83    1 0xffffff7f81d35000 0x11000    0x11000    com.apple.driver.AppleSMBusController (1.0.11d1) <82 11 10 5 4 3>
   84    0 0xffffff7f81d46000 0xd000     0xd000     com.apple.driver.AppleMCCSControl (1.1.12) <83 60 11 10 7 5 4 3 1>
   85    0 0xffffff7f813d3000 0xac000    0xac000    com.apple.iokit.IOBluetoothFamily (4.2.0b20) <33 14 7 5 4 3 1>
   86    0 0xffffff7f81251000 0x14000    0x14000    com.apple.iokit.IOSurface (91) <7 5 4 3 1>
   87    0 0xffffff7f80f5b000 0x7000     0x7000     com.apple.iokit.IOUserEthernet (1.0.0d1) <38 6 5 4 3 1>
   88    0 0xffffff7f81ba4000 0x5000     0x5000     com.apple.driver.AppleUpstreamUserClient (3.5.13) <60 11 10 7 5 4 3 1>
   91    1 0xffffff7f813ae000 0x11000    0x11000    com.apple.iokit.IOSerialFamily (10.0.7) <7 6 5 4 3 1>
   92    0 0xffffff7f813bf000 0xa000     0xa000     com.apple.iokit.IOBluetoothSerialManager (4.2.0b20) <91 7 5 4 3 1>
   93    2 0xffffff7f80db0000 0x56000    0x56000    com.apple.filesystems.ntfs (3.11) <7 6 5 4 1>
   94    1 0xffffff7f81818000 0x5000     0x5000     com.apple.kext.triggers (1.0) <7 6 5 4 3 1>
   95    0 0xffffff7f8181d000 0x9000     0x9000     com.apple.filesystems.autofs (3.0) <94 7 6 5 4 3 1>
   96    1 0xffffff7f80e0a000 0xe000     0xe000     com.apple.filesystems.msdosfs (1.9) <7 5 4 1>

AppleIntelCPUPowerManagement and AppleGraphicsPowerManagement is not loaded, so thats why we can boot OSX without patched BIOS and <key>AsusAICPUPM</key> <true/>.

 

Apparently those kexts are not loaded on 10.9 (and 10.8.5???) on Haswell systems.

 

??????

 

Edit: Some more users confirmed to me that on their Z87 and H87 systems, those kext are not loaded at all. But everything seems to be working, speedstep works, temp is normal etc. I don't know what Apple did.

[thunderbug]

Try using another USB flash, thre are some incompatible ones. You can use ASUS BRenamer utility to rename your BIOS file correctly.

Thank you so much! I used that bios rename tool and it worked. :

Also the Mavericks installation etc. worked... 

[kermit1219]

Can someone help me with my Dell Inspiron 14z? The bios states it is an AMI / Aptio bios.

 

I tried using PMPatch on the bios 5423A13.exe file, and got this:

 

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 modules not found.

 

then I dug a little deeper and extracted the bios rom from the 5423A13.exe by using the /writeromfile command, when I ran PMPatch on the .rom I got this:

 

PMPatch 0.5.13

PowerManagement module at 00333758 patched.

PowerMgmtDxe/PowerManagement2.efi modules not found.

AMI nest modules not found.

Phoenix nest modules not found.

CpuPei module at 0077B570 not patched: Patch pattern not found.

 

That tells me that PMPatch was able to patch the file, just not via the EXE, now am not able to flash just the rom as dell has security preventing that. (I have tried using afudos and get the error "18 Error Unable to start a secure flash session" 

 

Please help!

[AsusFreak]

No. It was 100h, AFAIR. ASUS Z87 boards have that stupid BIOS region protection, that prevents modified BIOSes from flashing. This has nothing in comman with that 100h removal.

Can this be verified again please. I'm running Stock Bios 1206 (not flashed) on a Asus Gryphon with no issue at all.  PM working fine on 10.8.5 and DP5

 

Thanx

[yehia2amer]

Machine Model: HP Pavilion dv6-2170ee

Bios Orginal Image: Insyde F.1C A ( sp48953 )

This Bios is already unlocked by Camiloml to add more options and remove whitelist: sp48953_AHCI_VT_MoreOptions_ByCamiloml.exe

I Tried the Patch with no luck

any help will be appreciated

[kermit1219]

Can someone help me with my Dell Inspiron 14z? The bios states it is an AMI / Aptio bios.

 

I tried using PMPatch on the bios 5423A13.exe file, and got this:

 

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 modules not found.

 

then I dug a little deeper and extracted the bios rom from the 5423A13.exe by using the /writeromfile command, when I ran PMPatch on the .rom I got this:

 

PMPatch 0.5.13

PowerManagement module at 00333758 patched.

PowerMgmtDxe/PowerManagement2.efi modules not found.

AMI nest modules not found.

Phoenix nest modules not found.

CpuPei module at 0077B570 not patched: Patch pattern not found.

 

That tells me that PMPatch was able to patch the file, just not via the EXE, now am not able to flash just the rom as dell has security preventing that. (I have tried using afudos and get the error "18 Error Unable to start a secure flash session" 

 

Please help!

turns out all I needed to do was install patched applepowermanagement.kext as there is no actual way to flash a modded bios to this system. 

[cmwilliams72]

Hi Code Rush,

 

Asus came out with a couple new updates for the Z87-Deluxe/Dual and I'm wondering if you could help me patch the new file (Z87-DELUXE/DUAL BIOS 1305).  I'd do it myself but I cannot get the mac version of pmpatch to work properly.

 

Thanks in advance,

 

CW

[AsusFreak]

Hi Code Rush,

 

Asus came out with a couple new updates for the Z87-Deluxe/Dual and I'm wondering if you could help me patch the new file (Z87-DELUXE/DUAL BIOS 1305).  I'd do it myself but I cannot get the mac version of pmpatch to work properly.

 

Thanks in advance,

 

CW,

Just for giggles, why not flash 1305 from bios (Not Flashback) and see if it works. I don't believe that it's locked as many of us are using the stock bios and all is well. If you end up with an issue then just USB Flash back to the previous bios, no harm done. I have a friend with that board purchased 2 days ago and all if fine without patch...

[cmwilliams72]

Just for giggles, why not flash 1305 from bios (Not Flashback) and see if it works. I don't believe that it's locked as many of us are using the stock bios and all is well. If you end up with an issue then just USB Flash back to the previous bios, no harm done. I have a friend with that board purchased 2 days ago and all if fine without patch...

Oh I have   but to no resolve.  I will say I can't guarantee it's the flashing, but I could not force partition my Hackintosh HD into MBR format so it's a GUID partition scheme and ASUS will not recognize (or even load it).

 

I have no patience hence the reason I tried. 

[AsusFreak]

Oh I have   but to no resolve.  I will say I can't guarantee it's the flashing, but I could not force partition my Hackintosh HD into MBR format so it's a GUID partition scheme and ASUS will not recognize (or even load it).

 

I have no patience hence the reason I tried. 

I don't understand this, I and friends all running GUID partitions... The Asus problem with GUID was only with the first bios release, was quickly solved with the next bios. Don't know why you have a question if your flashing worked or not.  Put the new bios on a usb drive, boot to bios and run flash utility... It will tell you if it fails.

[cmwilliams72]

Let me start again, I've never been able to get Mac OSX Maverick to work using Asus Bios version 1008 (and then a patched version from Code Rush).  Neither of the latter worked.  Then, I've used myHack installer; this resulted in an internal error at the end of installation and could never boot into OSX using my Hackintosh HD (note: I can get into the installer using flags -v cpus=1 PCIRootUID=0). 

 

Before flashing, I used Christ111's installer, and the flags above and was able to install OSX without any errors.  So, hoping the issue was Asus' GUID issue, I successfully flashed my Z87-Deluxe/Dual to 1305, and still have not been able to boot to my Hackintosh HD.

 

Any recommendations would really help.

[AsusFreak]

Let me start again, I've never been able to get Mac OSX Maverick to work using Asus Bios version 1008 (and then a patched version from Code Rush).  Neither of the latter worked.  Then, I've used myHack installer; this resulted in an internal error at the end of installation and could never boot into OSX using my Hackintosh HD (note: I can get into the installer using flags -v cpus=1 PCIRootUID=0). 

 

Before flashing, I used Christ111's installer, and the flags above and was able to install OSX without any errors.  So, hoping the issue was Asus' GUID issue, I successfully flashed my Z87-Deluxe/Dual to 1305, and still have not been able to boot to my Hackintosh HD.

 

Any recommendations would really help.

My original reply to you was regarding 1305 with you stating you couldn't get pmpatch to work.  Nothing in that post suggested that you hadn't achieved a successful install yet.  I'd suggest that re-read the guides, format your drive and start over...  I've used the myHack guide and it works, there are better methods such as creating a Clover installer, but you are better off following the myHack guide so you can get help here if necessary...