cmwilliams72 Posted August 17, 2013 Share Posted August 17, 2013 Thanks! I'll give myHack a retry today. Link to comment Share on other sites More sharing options...
cmwilliams72 Posted August 18, 2013 Share Posted August 18, 2013 Okay major update so here it goes: I've tried almost everything to get Mac OSX Maverick on my Asus Z87 Deluxe/Dual and I don't know where to go from here. I followed the following manuals to the letter...yes I've done that many installs and re-installs: Gus's manual for his Z87 Deluxe, Rockiron's vanilla install instructions (see insanelymac guides), and I've installed via myHack and I cannot get any of the installs to boot with my HDD; even after following all of the post-install recommendations. I know my biggest issue is that during all of the above installs, I do not have the option to choose MBR as a format option. OSX Installer ONLY allows me to continue my install with a GUID partition (no matter what option above). Based on various recommendations, I even went to the great length of continuing to install on my Hackintosh with a GUID partition and using my MacBook Pro to format a separate hard drive as MBR and copy all of the files from the prior install on the MBR drive...again to no avail. I'm not sure how individual's are getting past the MBR issue or how they got their systems working, but if someone could spare some time to help that would be great. Best, CW Link to comment Share on other sites More sharing options...
pavolajco Posted August 18, 2013 Share Posted August 18, 2013 Hi CodeRush, can you patch this uefi Bios? Speedstep isn't working. It's for older Gigabyte board. http://download.gigabyte.eu/FileList/Bios/mb_bios_ga-p67a-ud3-b3_u1d.exe Link to comment Share on other sites More sharing options...
TimeWalker75a Posted August 18, 2013 Share Posted August 18, 2013 Hi CodeRush, can you patch this uefi Bios? Speedstep isn't working. It's for older Gigabyte board. http://download.gigabyte.eu/FileList/Bios/mb_bios_ga-p67a-ud3-b3_u1d.exe Gigabyte never locked down the MSR register, so It's up to you to get it to work.. Link to comment Share on other sites More sharing options...
partypoison1993 Posted August 18, 2013 Share Posted August 18, 2013 Hey guys please help me. i always get error when flashing modded bios that was patched with pmpatch tool. in asus ezflash 2 utility, when trying to update with the modded bios, a security related error is popping. so i tried with ftk under both windows and dos mode, but got error, there too. this is the error im getting. " error 280 :failed to disable write protection for the bios space". Please help guys, im friggin exhausted, i i've spend one whole day to make this possible but no luck so far. Please Help. Please ! Some info about my Mobo :- Mobo- Asus p8h77 vle Latest Bios update - 1103 (.CAP File) Vendor - American Megatrends Inc Current version of Bios -1103 (original / un-modified ) OS:- Windows 7 Ultimate 64 bit. Help! Thanks !. Link to comment Share on other sites More sharing options...
k3nny Posted August 18, 2013 Share Posted August 18, 2013 Hey guys please help me. i always get error when flashing modded bios that was patched with pmpatch tool. ... Mobo- Asus p8h77 vle Latest Bios update - 1103 (.CAP File) ... Asus recently introduced a new protection and it seems the P8Z77-V LE is affected, too. You have three possibilities: 1) Patch and flash an older unprotected BIOS 2) Roll back to an older unprotected BIOS, patch and flash the current BIOS 3) Patch AppleIntelCPUPowerManagement.kext to avoid messing with BIOS at all 1 Link to comment Share on other sites More sharing options...
schot Posted August 18, 2013 Share Posted August 18, 2013 does not work for MSI H87-G41 PC Mate have it patched and starting BIOS from a USB stick works... nay can't get the patched bios flashed on the computer Link to comment Share on other sites More sharing options...
k3nny Posted August 18, 2013 Share Posted August 18, 2013 does not work for MSI H87-G41 PC Mate it broke my motherboard!!! WARNING! That's bad but it would be good if you explain what the single steps and results in more detail so others won't have the same problem. Link to comment Share on other sites More sharing options...
schot Posted August 18, 2013 Share Posted August 18, 2013 That's bad but it would be good if you explain what the single steps and results in more detail so others won't have the same problem. it looks now like the pact worked.... only there is no tool for windows to flash the BIOS so i have to pad the BIOS from a USB stick. Still my OSx won't work but now it does not reboot anymore... now other problems bt for another topic.... Link to comment Share on other sites More sharing options...
partypoison1993 Posted August 19, 2013 Share Posted August 19, 2013 is there a way to do it another way..? like using AMITool or MMtool etc..? Please Help.? Link to comment Share on other sites More sharing options...
AsusFreak Posted August 19, 2013 Share Posted August 19, 2013 This has already been answered: http://www.insanelymac.com/forum/topic/285444-pmpatch-uefi-patching-utility/?p=1939730 Link to comment Share on other sites More sharing options...
buoo Posted August 20, 2013 Share Posted August 20, 2013 Are the new gigabyte Z87/H87 boards looked? Are Asrock and MSI using the the protection of BIOS region too? Link to comment Share on other sites More sharing options...
CodeRush Posted August 20, 2013 Author Share Posted August 20, 2013 buoo, I have no idea now. For the first question - try using latest version of PMPatch on BIOS file from new GB board. If it works and produces output file - they are indeed locked. If not - post the log and the file here, so we may look at it. I still have no access to my primary PC now, but I will be ready for action in about 2 weeks. For the second - download the BIOS file, open it with hex editor and look at 0x60 offset, if there are 00 00 FF FF 00 00 FF FF 18 01 FF FF - regions are unlocked, if something else - something else. That year was very hard for me and I need a proper vacation to get rid of it. 2 Link to comment Share on other sites More sharing options...
CodeRush Posted August 20, 2013 Author Share Posted August 20, 2013 yehia Amer, I have disassembled PowerManagement2 module from your BIOS and see no signs of locking code there, but maybe I'm just blind now. Will look deeper a bit later. It looks like new GB boards are locked too, and I can't figure out the locking code from my netbook again. Can anyone with GB Z87 board confirm if bit 15 of 0xE2 MSR is set, or post MSRDumper report here? 1 Link to comment Share on other sites More sharing options...
Cobra03 Posted August 20, 2013 Share Posted August 20, 2013 yehia Amer, I have disassembled PowerManagement2 module from your BIOS and see no signs of locking code there, but maybe I'm just blind now. Will look deeper a bit later. It looks like new GB boards are locked too, and I can't figure out the locking code from my netbook again. Can anyone with GB Z87 board confirm if bit 15 of 0xE2 MSR is set, or post MSRDumper report here? Here is info from AICPUPMinfo.kext I use from PikeAlpha Revoboot. I haven't used MSRDumper.kext so I'm not sure if they are the same info you need. If not I will get MSRDumper.kext and use that. Just let me know if you need me too. Latest PMPatch make no output file. 8/20/13 8:09:17.000 AM kernel[0]: MSR_CORE_THREAD_COUNT......(0x35) : 0x40008 8/20/13 8:09:17.000 AM kernel[0]: MSR_PLATFORM_INFO..........(0xCE) : 0x80838F3012300 8/20/13 8:09:17.000 AM kernel[0]: MSR_PMG_IO_CAPTURE_BASE....(0xE4) : 0x1814 8/20/13 8:09:17.000 AM kernel[0]: IA32_MPERF.................(0xE7) : 0x18B0347B0D 8/20/13 8:09:17.000 AM kernel[0]: IA32_APERF.................(0xE8) : 0x17D6E1717A 8/20/13 8:09:17.000 AM kernel[0]: MSR_IA32_PERF_STATUS.......(0x198) : 0x16B000000800 8/20/13 8:09:17.000 AM kernel[0]: MSR_IA32_PERF_CONTROL......(0x199) : 0x800 8/20/13 8:09:17.000 AM kernel[0]: IA32_CLOCK_MODULATION......(0x19A) : 0x0 8/20/13 8:09:17.000 AM kernel[0]: IA32_THERM_STATUS..........(0x19C) : 0x88460000 8/20/13 8:09:17.000 AM kernel[0]: IA32_MISC_ENABLES..........(0x1A0) : 0x850089 8/20/13 8:09:17.000 AM kernel[0]: MSR_MISC_PWR_MGMT..........(0x1AA) : 0x1 8/20/13 8:09:17.000 AM kernel[0]: MSR_TURBO_RATIO_LIMIT......(0x1AD) : 0x27272727 8/20/13 8:09:17.000 AM kernel[0]: IA32_ENERGY_PERF_BIAS......(0x1B0) : 0x5 8/20/13 8:09:17.000 AM kernel[0]: MSR_POWER_CTL..............(0x1FC) : 0x4005F 8/20/13 8:09:17.000 AM kernel[0]: MSR_RAPL_POWER_UNIT........(0x606) : 0xA0E03 8/20/13 8:09:17.000 AM kernel[0]: MSR_PKG_POWER_LIMIT........(0x610) : 0xFFD00000EA82 8/20/13 8:09:17.000 AM kernel[0]: MSR_PKG_ENERGY_STATUS......(0x611) : 0xEC971E 8/20/13 8:09:17.000 AM kernel[0]: MSR_PP0_CURRENT_CONFIG.....(0x601) : 0x1F40 8/20/13 8:09:17.000 AM kernel[0]: MSR_PP0_POWER_LIMIT........(0x638) : 0xFFD0 8/20/13 8:09:17.000 AM kernel[0]: MSR_PP0_ENERGY_STATUS......(0x639) : 0x8B1CFF 8/20/13 8:09:17.000 AM kernel[0]: MSR_PP0_POLICY.............(0x63a) : 0x0 8/20/13 8:09:17.000 AM kernel[0]: MSR_CONFIG_TDP_NOMINAL.....(0x648) : 0x23 8/20/13 8:09:17.000 AM kernel[0]: MSR_CONFIG_TDP_LEVEL1......(0x649) : 0x0 8/20/13 8:09:17.000 AM kernel[0]: MSR_CONFIG_TDP_LEVEL2......(0x64a) : 0x0 8/20/13 8:09:17.000 AM kernel[0]: MSR_CONFIG_TDP_CONTROL.....(0x64b) : 0x80000000 8/20/13 8:09:17.000 AM kernel[0]: MSR_TURBO_ACTIVATION_RATIO.(0x64c) : 0x0 8/20/13 8:09:17.000 AM kernel[0]: MSR_PKG_C3_RESIDENCY.......(0x3f8) : 0x0 8/20/13 8:09:17.000 AM kernel[0]: MSR_PKG_C6_RESIDENCY.......(0x3f9) : 0x0 8/20/13 8:09:17.000 AM kernel[0]: MSR_PKG_C7_RESIDENCY.......(0x3fa) : 0x0 8/20/13 8:09:17.000 AM kernel[0]: AICPUPMI: Low Frequency Mode : 800 MHz 8/20/13 8:09:17.000 AM kernel[0]: AICPUPMI: Clock Speed : 3500 MHz 8/20/13 8:09:17.000 AM kernel[0]: AICPUPMI: Max Turbo Frequency: 3900 MHz 8/20/13 8:09:17.000 AM kernel[0]: waitForSystemMapper 8/20/13 8:09:17.000 AM kernel[0]: Backtrace 0xffffff80006b6919 0xffffff80006b63fd 0xffffff7f81b7e4b5 0xffffff80006920cf 0xffffff8000691c8f 0xffffff800068d869 0xffffff80006927e3 8/20/13 8:09:17.000 AM kernel[0]: Kernel Extensions in backtrace: 0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 16: 5A A5 F0 0F 03 00 04 03 06 02 10 15 20 01 21 1B 32: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 48: 45 00 90 64 00 00 00 00 00 00 00 00 FF FF FF FF 64: 00 00 00 00 00 00 FF 0F 03 00 FF 01 01 00 02 00 80: FF 7F 00 00 FF 7F 00 00 FF 7F 00 00 FF FF FF FF 96: 00 00 FF FF 00 00 FF FF 18 01 FF FF FF FF FF FF <see here ^Bios F7 Ga-z87x-ud3h Link to comment Share on other sites More sharing options...
CodeRush Posted August 20, 2013 Author Share Posted August 20, 2013 Cobra03, BIOS appears unlocked for writing with Intel FPT, but I can say nothing about the lock: 0xE2 register is not reported in your quote. I also think there are a bit different mechanisms on 10.8.5 and 10.9 DP, and AppleIntelCPUPowerManagement.kext isn't loaded anymore, making the patch unneeded too. I have no access to normal x64 disassembler or OS X now, so for now I can say nothing more. 1 Link to comment Share on other sites More sharing options...
Cobra03 Posted August 20, 2013 Share Posted August 20, 2013 Cobra03, BIOS appears unlocked for writing with Intel FPT, but I can say nothing about the lock: 0xE2 register is not reported in your quote. I also think there are a bit different mechanisms on 10.8.5 and 10.9 DP, and AppleIntelCPUPowerManagement.kext isn't loaded anymore, making the patch unneeded too. I have no access to normal x64 disassembler or OS X now, so for now I can say nothing more. Moded Bios can be written without issue I have confirmed that. And yes New MacBookAir6,1/6,2 do not load AICPUPM either. So I believe you are correct that even if patch is needed its useless do to lack of .kext loading. If you need any other info I can get it for you................. Did you get the files I sent your way? I know you are on vacation so this is no big deal, Just curious....... Link to comment Share on other sites More sharing options...
Cobra03 Posted August 20, 2013 Share Posted August 20, 2013 Aug 20 01:33:02 localhost kernel[0]: MSR_CORE_THREAD_COUNT......(0x35) : 0x40008 Aug 20 01:33:02 localhost kernel[0]: MSR_PLATFORM_INFO..........(0xCE) : 0x80838F3012300 Aug 20 01:33:02 localhost kernel[0]: MSR_PMG_IO_CAPTURE_BASE....(0xE4) : 0x1814 Aug 20 01:33:02 localhost kernel[0]: MSR_IA32_PERF_STATUS.......(0x198) : 0x168800000800 Aug 20 01:33:02 localhost kernel[0]: MSR_IA32_PERF_CONTROL......(0x199) : 0x800 Aug 20 01:33:02 localhost kernel[0]: MSR_MISC_PWR_MGMT..........(0x1AA) : 0x1 Aug 20 01:33:02 localhost kernel[0]: MSR_TURBO_RATIO_LIMIT......(0x1AD) : 0x27272727 Aug 20 01:33:02 localhost kernel[0]: MSR_POWER_CTL..............(0x1FC) : 0x4005F Aug 20 01:33:02 localhost kernel[0]: MSR_RAPL_POWER_UNIT........(0x606) : 0xA0E03 Aug 20 01:33:02 localhost kernel[0]: MSR_PKG_POWER_LIMIT........(0x610) : 0xFFD00000EA82 Aug 20 01:33:02 localhost kernel[0]: MSR_PKG_ENERGY_STATUS......(0x611) : 0xBEADDC Aug 20 01:33:02 localhost kernel[0]: MSR_PP0_CURRENT_CONFIG.....(0x601) : 0x1F40 Aug 20 01:33:02 localhost kernel[0]: MSR_PP0_POWER_LIMIT........(0x638) : 0xFFD0 Aug 20 01:33:02 localhost kernel[0]: MSR_PP0_ENERGY_STATUS......(0x639) : 0x73B5CF Aug 20 01:33:02 localhost kernel[0]: MSR_PP0_POLICY.............(0x63a) : 0x0 Aug 20 01:33:02 localhost kernel[0]: MSR_CONFIG_TDP_NOMINAL.....(0x648) : 0x23 Aug 20 01:33:02 localhost kernel[0]: MSR_CONFIG_TDP_LEVEL1......(0x649) : 0x0 Aug 20 01:33:02 localhost kernel[0]: MSR_CONFIG_TDP_LEVEL2......(0x64a) : 0x0 Aug 20 01:33:02 localhost kernel[0]: MSR_CONFIG_TDP_CONTROL.....(0x64b) : 0x80000000 Aug 20 01:33:02 localhost kernel[0]: MSR_TURBO_ACTIVATION_RATIO.(0x64c) : 0x0 Aug 20 01:33:02 localhost kernel[0]: MSR_PKG_C3_RESIDENCY.......(0x3f8) : 0x0 Aug 20 01:33:02 localhost kernel[0]: MSR_PKG_C6_RESIDENCY.......(0x3f9) : 0x0 Aug 20 01:33:02 localhost kernel[0]: MSR_PKG_C7_RESIDENCY.......(0x3fa) : 0x0 Aug 20 02:01:24 localhost shutdown[412]: reboot by _cvmsroot: Aug 20 02:03:20 localhost kernel[0]: MSR_CORE_THREAD_COUNT......(0x35) : 0x40008 Aug 20 02:03:20 localhost kernel[0]: MSR_PLATFORM_INFO..........(0xCE) : 0x80838F3012300 Aug 20 02:03:20 localhost kernel[0]: MSR_PMG_IO_CAPTURE_BASE....(0xE4) : 0x1814 Aug 20 02:03:20 localhost kernel[0]: MSR_IA32_PERF_STATUS.......(0x198) : 0x168800000800 Aug 20 02:03:20 localhost kernel[0]: MSR_IA32_PERF_CONTROL......(0x199) : 0x800 Aug 20 02:03:20 localhost kernel[0]: MSR_MISC_PWR_MGMT..........(0x1AA) : 0x1 Aug 20 02:03:20 localhost kernel[0]: MSR_TURBO_RATIO_LIMIT......(0x1AD) : 0x27272727 Aug 20 02:03:20 localhost kernel[0]: MSR_POWER_CTL..............(0x1FC) : 0x4005F Aug 20 02:03:20 localhost kernel[0]: MSR_RAPL_POWER_UNIT........(0x606) : 0xA0E03 Aug 20 02:03:20 localhost kernel[0]: MSR_PKG_POWER_LIMIT........(0x610) : 0xFFD00000EA82 Aug 20 02:03:20 localhost kernel[0]: MSR_PKG_ENERGY_STATUS......(0x611) : 0x8D689B Aug 20 02:03:20 localhost kernel[0]: MSR_PP0_CURRENT_CONFIG.....(0x601) : 0x1F40 Aug 20 02:03:20 localhost kernel[0]: MSR_PP0_POWER_LIMIT........(0x638) : 0xFFD0 Aug 20 02:03:20 localhost kernel[0]: MSR_PP0_ENERGY_STATUS......(0x639) : 0x57245E Aug 20 02:03:20 localhost kernel[0]: MSR_PP0_POLICY.............(0x63a) : 0x0 Aug 20 02:03:20 localhost kernel[0]: MSR_CONFIG_TDP_NOMINAL.....(0x648) : 0x23 Aug 20 02:03:20 localhost kernel[0]: MSR_CONFIG_TDP_LEVEL1......(0x649) : 0x0 Aug 20 02:03:20 localhost kernel[0]: MSR_CONFIG_TDP_LEVEL2......(0x64a) : 0x0 Aug 20 02:03:20 localhost kernel[0]: MSR_CONFIG_TDP_CONTROL.....(0x64b) : 0x80000000 Aug 20 02:03:20 localhost kernel[0]: MSR_TURBO_ACTIVATION_RATIO.(0x64c) : 0x0 Aug 20 02:03:20 localhost kernel[0]: MSR_PKG_C3_RESIDENCY.......(0x3f8) : 0x0 Aug 20 02:03:20 localhost kernel[0]: MSR_PKG_C6_RESIDENCY.......(0x3f9) : 0x0 Aug 20 02:03:20 localhost kernel[0]: MSR_PKG_C7_RESIDENCY.......(0x3fa) : 0x0 Aug 20 08:09:17 localhost kernel[0]: MSR_CORE_THREAD_COUNT......(0x35) : 0x40008 Aug 20 08:09:17 localhost kernel[0]: MSR_PLATFORM_INFO..........(0xCE) : 0x80838F3012300 Aug 20 08:09:17 localhost kernel[0]: MSR_PMG_IO_CAPTURE_BASE....(0xE4) : 0x1814 Aug 20 08:09:17 localhost kernel[0]: MSR_IA32_PERF_STATUS.......(0x198) : 0x16B000000800 Aug 20 08:09:17 localhost kernel[0]: MSR_IA32_PERF_CONTROL......(0x199) : 0x800 Aug 20 08:09:17 localhost kernel[0]: MSR_MISC_PWR_MGMT..........(0x1AA) : 0x1 Aug 20 08:09:17 localhost kernel[0]: MSR_TURBO_RATIO_LIMIT......(0x1AD) : 0x27272727 Aug 20 08:09:17 localhost kernel[0]: MSR_POWER_CTL..............(0x1FC) : 0x4005F Aug 20 08:09:17 localhost kernel[0]: MSR_RAPL_POWER_UNIT........(0x606) : 0xA0E03 Aug 20 08:09:17 localhost kernel[0]: MSR_PKG_POWER_LIMIT........(0x610) : 0xFFD00000EA82 Aug 20 08:09:17 localhost kernel[0]: MSR_PKG_ENERGY_STATUS......(0x611) : 0xEC971E Aug 20 08:09:17 localhost kernel[0]: MSR_PP0_CURRENT_CONFIG.....(0x601) : 0x1F40 Aug 20 08:09:17 localhost kernel[0]: MSR_PP0_POWER_LIMIT........(0x638) : 0xFFD0 Aug 20 08:09:17 localhost kernel[0]: MSR_PP0_ENERGY_STATUS......(0x639) : 0x8B1CFF Aug 20 08:09:17 localhost kernel[0]: MSR_PP0_POLICY.............(0x63a) : 0x0 Aug 20 08:09:17 localhost kernel[0]: MSR_CONFIG_TDP_NOMINAL.....(0x648) : 0x23 Aug 20 08:09:17 localhost kernel[0]: MSR_CONFIG_TDP_LEVEL1......(0x649) : 0x0 Aug 20 08:09:17 localhost kernel[0]: MSR_CONFIG_TDP_LEVEL2......(0x64a) : 0x0 Aug 20 08:09:17 localhost kernel[0]: MSR_CONFIG_TDP_CONTROL.....(0x64b) : 0x80000000 Aug 20 08:09:17 localhost kernel[0]: MSR_TURBO_ACTIVATION_RATIO.(0x64c) : 0x0 Aug 20 08:09:17 localhost kernel[0]: MSR_PKG_C3_RESIDENCY.......(0x3f8) : 0x0 Aug 20 08:09:17 localhost kernel[0]: MSR_PKG_C6_RESIDENCY.......(0x3f9) : 0x0 Aug 20 08:09:17 localhost kernel[0]: MSR_PKG_C7_RESIDENCY.......(0x3fa) : 0x0 This is actual MSRDumper.kext log. Aug 20 13:07:42 localhost kernel[0]: MSRDumper PStatesReached: 8 35 37 38 39 Link to comment Share on other sites More sharing options...
Menno Posted August 22, 2013 Share Posted August 22, 2013 C:\Users\Menno\Downloads\Rampage-IV-Extreme-ASUS-4206>PMPatch.exe Rampa ge-IV-Extreme-ASUS-4206.CAP Rampage-IV-Extreme-ASUS-4206-PM.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 0079EEC8 patched. CpuPei module at 007DEEC8 patched. Output file generated. Is this correct? Link to comment Share on other sites More sharing options...
CodeRush Posted August 22, 2013 Author Share Posted August 22, 2013 Yes, but on X79 you still need a modified kext even with patched BIOS. Link to comment Share on other sites More sharing options...
partypoison1993 Posted August 22, 2013 Share Posted August 22, 2013 hey, if i go with patching apple power management kext, the only thing is that , i should repatch these kexts after each update right.? can someone confirm this..? Thanks. Link to comment Share on other sites More sharing options...
TimeWalker75a Posted August 22, 2013 Share Posted August 22, 2013 Yes you do, unless the kext is not updated with a certain update.. which is obvious. Link to comment Share on other sites More sharing options...
partypoison1993 Posted August 23, 2013 Share Posted August 23, 2013 Thanks mate. Link to comment Share on other sites More sharing options...
CodeRush Posted August 23, 2013 Author Share Posted August 23, 2013 Hi, read Tito's post at MDL regarding OA30 - I wasn't even aware about the fact, that Phoenix Tools has the signing key included ; ) so it's possible to re-sign & flash an ASUS UEFI with help of PT. best regards That is great, if works. Can anyone confirm that BIOS for ASUS Z77 board, that was patched with PMPatch and then modified that way can be flashed with EZ Flash? 1 Link to comment Share on other sites More sharing options...
ham4ever Posted August 26, 2013 Share Posted August 26, 2013 does it work for haswell and GA Z87 HD3 ?? thanks for this great tool Link to comment Share on other sites More sharing options...
Recommended Posts