Jump to content
KGP-iMacPro

iMac Pro X99 - live the future now with macOS 10.14 Mojave [Successful Build/Successful Guide]

107 posts in this topic

Recommended Posts

Advertisement

Hi KGP,

 

a quick question: I'm on 10.14.2 at the moment with your EFI 10.14.2 folder and the truncated 15-port XHC USB kext (I also use a Asus x99-A II). See Screenshot. I'm using the newest Lilu and WhateverGreen.kext, as well as my own Vega56 ssdt setup (what works awesome).

22425215_Bildschirmfoto2019-02-09um11_11_23.png.c7f6bb0e41d2e5efd1ecfaeb807fa137.png

 

When I download your EFI folder, it is missing the XHCI 15port kext in your folder as well as tscadjustreset and whatevergreen. I guess because it is the basic EFI Folder for the first usb installer boot procedure etc.?

 

Question for my update routine to 10.14.3:

Should I first update to 10.14.3,

or first update clover, edit my config to replace the performance_patch, reboot and after that update to 10.14.3?

 

In addition: I used your CPU Type solution provided on page 3 to replace the cpu information in the system environment stating "3.3 GHz unknown" but it does not solve the issue:

465552477_Bildschirmfoto2019-02-09um11_23_55.thumb.png.4c36bd63da75dc0866225d8bfc553c6d.png

 

Edited by Multisaft

Share this post


Link to post
Share on other sites
9 minutes ago, Multisaft said:

Hi KGP,

 

a quick question: I'm on 10.14.2 at the moment with your EFI 10.14.2 folder and the truncated 15-port XHC USB kext (I also use a Asus x99-A II). See Screenshot. I'm using the newest Lilu and WhateverGreen.kext, as well as my own Vega56 ssdt setup (what works awesome).

22425215_Bildschirmfoto2019-02-09um11_11_23.png.c7f6bb0e41d2e5efd1ecfaeb807fa137.png

 

When I download your EFI folder, it is missing the XHCI 15port kext in your folder as well as tscadjustreset and whatevergreen. I guess because it is the basic EFI Folder for the first usb installer boot procedure etc.?

 

Question for my update routine to 10.14.3:

Should I first update to 10.14.3,

or first update clover, edit my config to replace the performance_patch, reboot and after that update to 10.14.3?

 

In addition: I used your CPU Type solution provided on page 3 to replace the cpu information in the system environment stating "3.3 GHz unknown" but it does not solve the issue:

465552477_Bildschirmfoto2019-02-09um11_23_55.thumb.png.4c36bd63da75dc0866225d8bfc553c6d.png

 

 

Yes it is just a basic EFI-folder for maximim compability and flexibility. The rest needs to be implemented following my guidelines. If you use the truncated 15-port kext you just need to update Clover and the kext and kernel patches in the config.plist. You can also directly use my 10.14.3 EFI-Folder and add what is missing from your current 10.13.6 EFI-Folder or what still needs to be implemented by following my guidelines. 

On X299, as Skylake-X is implemented natively, the resultung EFI-Folder is fully vanilla and works with all macOS versions, always provided that one uses the 15-port kext and one therefore does not need  respective USB port limit patches, which are still macOS dependent. 

Share this post


Link to post
Share on other sites
12 minutes ago, KGP-iMacPro said:

 

Yes it is just a basic EFI-folder for maximim compability and flexibility. The rest needs to be implemented following my guidelines. If you use the truncated 15-port kext you just need to update Clover and the kext and kernel patches in the config.plist. You can also directly use my 10.14.3 EFI-Folder and add what is missing from your current 10.13.6 EFI-Folder or what still needs to be implemented by following my guidelines. 

On X299, as Skylake-X is implemented natively, the resultung EFI-Folder is fully vanilla and works with all macOS versions, always provided that one uses the 15-port kext and one therefore does not need  respective USB port limit patches, which are still macOS dependent

 

Ok,

so I need to find out what files I need to update in my EFI Folder to replace the old clover with the new version, can you give me a hint? I don't want to replace mine with your 10.14.3 because I like it more to go through each step on my own so not to miss anything. Must I use the clover installer to update the respective efi partition, or is it just for example some files in the clover path?

After Clover update, I will just update my Lilu ones more and add the respective performance patch. thanks!

 

 

Share this post


Link to post
Share on other sites
19 minutes ago, Multisaft said:

 

Ok,

so I need to find out what files I need to update in my EFI Folder to replace the old clover with the new version, can you give me a hint? I don't want to replace mine with your 10.14.3 because I like it more to go through each step on my own so not to miss anything. Must I use the clover installer to update the respective efi partition, or is it just for example some files in the clover path?

After Clover update, I will just update my Lilu ones more and add the respective performance patch. thanks!

 

 

 

Just replace EFI/BOOT/BootX64.efi, /EFI/CLOVER/CLOVERX64.efi and /EFI/CLOVER/driver64UEFI in your EFI-Folder with does files and directories implemented in my default 10.14.3 EFi-Folder distribution. By this you will implement Clover_v2.4k_r4870. 

Alternatively you can simply automatically update the receptive files and directories by simply running the Clover_v2.4k_r4870 installer, although also carefully select in the Clover installation process only does efi-drivers, which are actually also implemented under /EFI/CLOVER/driver64UEFI/ in my original 10.14.3 EFi-Folder distribution. 

Share this post


Link to post
Share on other sites

Hey!

 

First up: Thanks for building this X99 Guide. My System(Mojave) was running like charm with everything working from the beginning! (Rampage 5 extreme; 6850k, Vega 64). I just received my Fenvi T919 WiFi/BT Card that should be fully functional OOB. I installed the card, booted the system Up and experiencing PCI Configuration end + a prohibited sign and when i use USB injectall + disabling the 4g encoding it proceeds till USB sound assertion and gets stuck there + prohibited sign. . The BIOS settings are the same as you pointed in the guide.

 

Things I tried :

  • Removed the card which lets me boot normally. Once booted i plug in the fenvi card while the system is running and I can see the adapter getting recognized. The system is not booting only when the adapter is installed during the boot phase.
  • Tried Enabling/Disabling FixAirport, FixLan which doesn't seem to help.
  • Switched different PCI lanes and doesn't seem to help.

CLOVER.zip

Share this post


Link to post
Share on other sites

Hi KGP,

 

Thanks for your encyclopedic effort with this and other guides. 

 

I've run into a roadblock modifying the BIOS file for my Asus x99 Deluxe. The microcode update appeared to go smoothly, inasmuch, as my outputs match your screenshots. However, when I tried to run UEFIPatch, I get the following error message:

 

Unsupported 16-bit Application

The program or feature "[...] UEFIPatch.exe" cannot start or run due to incompatibility with 64-bit versions of Windows. Please contact the software vendor to ask if a 64-bit  Windows compatible version is available.

 

FYI, I tried loading the BIOS file created by MMTool directly from a USB flash drive with the computer off but the update didn't go through. The LED just flashed four times and then stayed solid. I also tried via the UEFI at startup but got an error message.

 

Any thoughts on how to proceed?

 

Thanks for your help.

 

Max

Share this post


Link to post
Share on other sites
28 minutes ago, maxneko said:

Hi KGP,

 

Thanks for your encyclopedic effort with this and other guides. 

 

I've run into a roadblock modifying the BIOS file for my Asus x99 Deluxe. The microcode update appeared to go smoothly, inasmuch, as my outputs match your screenshots. However, when I tried to run UEFIPatch, I get the following error message:

 

Unsupported 16-bit Application

The program or feature "[...] UEFIPatch.exe" cannot start or run due to incompatibility with 64-bit versions of Windows. Please contact the software vendor to ask if a 64-bit  Windows compatible version is available.

 

FYI, I tried loading the BIOS file created by MMTool directly from a USB flash drive with the computer off but the update didn't go through. The LED just flashed four times and then stayed solid. I also tried via the UEFI at startup but got an error message.

 

Any thoughts on how to proceed?

 

Thanks for your help.

 

Max

 

UEFIpatch is meant to be executed within a terminal under macOS! 

Share this post


Link to post
Share on other sites
1 hour ago, KGP-iMacPro said:

 

UEFIpatch is meant to be executed within a terminal under macOS! 

Ouch! Sorry...

So I went back to the X99D.CAP file generated in the UBU folder and ran it through UEFIPatch on my MBP. I got the text you mention in the guide that is harmless. The difference was that, in my case, it ended with "Function called with invalid parameter". No patched .CAP file was generated.

Share this post


Link to post
Share on other sites
32 minutes ago, maxneko said:

Ouch! Sorry...

So I went back to the X99D.CAP file generated in the UBU folder and ran it through UEFIPatch on my MBP. I got the text you mention in the guide that is harmless. The difference was that, in my case, it ended with "Function called with invalid parameter". No patched .CAP file was generated.

 

Well I don’t know what exactly you did now and why you got the error in consequence. 

 

What was exactly your command line? 

Share this post


Link to post
Share on other sites
35 minutes ago, KGP-iMacPro said:

 

Well I don’t know what exactly you did now and why you got the error in consequence. 

 

What was exactly your command line? 

Last login: Fri Mar  8 16:08:46 on console

MacBook-Pro:~ maxneko$ cd /Users/maxneko/Desktop/UEFIPatch_0.3.9_osx 

MacBook-Pro:UEFIPatch_0.3.9_osx maxneko$ /Users/maxneko/Desktop/UEFIPatch_0.3.9_osx/UEFIPatch /Users/maxneko/Desktop/UEFIPatch_0.3.9_osx/X99D.CAP 

parseImageFile: Aptio capsule signature may become invalid after image modifications

parseSection: section with unknown type 52h

parseFile: non-empty pad-file contents will be destroyed after volume modifications

parseSection: section with unknown type 52h

parseFile: non-empty pad-file contents will be destroyed after volume modifications

Function called with invalid parameter

MacBook-Pro:UEFIPatch_0.3.9_osx maxneko$

Share this post


Link to post
Share on other sites
Posted (edited)
33 minutes ago, maxneko said:

Last login: Fri Mar  8 16:08:46 on console

MacBook-Pro:~ maxneko$ cd /Users/maxneko/Desktop/UEFIPatch_0.3.9_osx 

MacBook-Pro:UEFIPatch_0.3.9_osx maxneko$ /Users/maxneko/Desktop/UEFIPatch_0.3.9_osx/UEFIPatch /Users/maxneko/Desktop/UEFIPatch_0.3.9_osx/X99D.CAP 

parseImageFile: Aptio capsule signature may become invalid after image modifications

parseSection: section with unknown type 52h

parseFile: non-empty pad-file contents will be destroyed after volume modifications

parseSection: section with unknown type 52h

parseFile: non-empty pad-file contents will be destroyed after volume modifications

Function called with invalid parameter

MacBook-Pro:UEFIPatch_0.3.9_osx maxneko$

 

Well in principle the terminal commands are in fact as easy as: 

 

cd ~/Desktop/UEFIPatch_0.3.9_osx/

and

./UEFIPatch X99D.CAP

If this does not work, try to patch the original ASUS BIOS firmware directly after download and subsequently modify CPU microcode under Windows. This should really work. There is not other solution.

 

Note that the directory ~/Desktop/UEFIPatch_0.3.9_osx/ must contain "UEFIPatch", "patches.txt" and the "BIOS firmware to be patched"!   

 

Good luck,

 

KGP 

 

 

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites
2 minutes ago, KGP-iMacPro said:

 

Well in principle the terminal commands are in fact as easy as: 

 


cd ~/Desktop/UEFIPatch_0.3.9_osx/

and


./UEFIPatch X99D.CAP

If this does not work, try to patch the original ASUS BIOS after download and subsequently  modify CPU microcode under Windows. This should really work. There is not other solution.

 

Good luck,

 

KGP 

 

 

Thanks, KGP. I actually tried the short version after changing directories and I got "-bash: UEFIPatch: command not found". I assumed that I needed to edit my bash file.

 

I located another version of UEFIPatch here: <<https://github.com/LongSoft/UEFITool/releases/download/0.26.0/UEFIPatch_0.26.0_mac.zip>> and ran the command successfully, inasmuch as a new .CAP file was created. Unfortunately, the flashback failed. I'll now try your suggestion above.

 

Thanks again,

 

Max

Share this post


Link to post
Share on other sites
34 minutes ago, maxneko said:

Thanks, KGP. I actually tried the short version after changing directories and I got "-bash: UEFIPatch: command not found". I assumed that I needed to edit my bash file.

 

I located another version of UEFIPatch here: <<https://github.com/LongSoft/UEFITool/releases/download/0.26.0/UEFIPatch_0.26.0_mac.zip>> and ran the command successfully, inasmuch as a new .CAP file was created. Unfortunately, the flashback failed. I'll now try your suggestion above.

 

Thanks again,

 

Max

 

The command is also not 

 

UEFIPatch

 

but 

 

./UEFIPatch 

 

If a new cap file was created, the patch was sucessful. 

 

Hower, for EZ-Flashback, the new cap file must again be renaimed to x99D.CAP! 

 

Also verify that your USB flash drive is really plugged to the EZ Flashback USB connector! 

 

Good luck,

 

KGP

 

Share this post


Link to post
Share on other sites
On 3/8/2019 at 5:35 PM, KGP-iMacPro said:

 

The command is also not 

 

UEFIPatch

 

but 

 

./UEFIPatch 

 

If a new cap file was created, the patch was sucessful. 

 

Hower, for EZ-Flashback, the new cap file must again be renaimed to x99D.CAP! 

 

Also verify that your USB flash drive is really plugged to the EZ Flashback USB connector! 

 

Good luck,

 

KGP

 

Thanks, KGP, I appreciate you really spelling things out. I've made progress but am not quite there yet.

  • updated the microcodes in the Asus stock BIOS in Windows, using mmtool.
  • unlocked the msr register using UEFIPatch (no error messages and patched BIOS file created)
  • as suggested, I ran UEFIPatch first and then updated the microcodes in Windows
  • am using a PNY USB 2.0 8GB flash drive, formatted FAT32, with the patched BIOS renamed to X99D.CAP in the correct port (the one with the green rectangle around it
  • I turned on the power and held down the flashback button until the first blink of the blue LED (about two seconds). I released it whereupon it blinked three more times and then turned solid. It stayed solid indefinitely.
  • I tried the above using an unpatched Asus BIOS file with the same result (encouraging, in a way).
  • I successfully reflashed the Asus BIOS from within the UEFI using the same unpatched Asus file.
  • I tried reflashing with the patched BIOS from within the UEFI. I got an error along the lines of "This is not a proper BIOS." (I believe this expected?)

My guess is that I either have a hardware issue with my motherboard or else that there is something blindingly obvious (except to me) that I'm doing wrong with the USB flashback. Does it matter what devices are connected to the motherboard? Could the CMOS backup battery come into play? Is there a command that resets the board to its out of the box state?

 

 

 

 

 

 

Share this post


Link to post
Share on other sites
Posted (edited)
16 minutes ago, maxneko said:

Thanks, KGP, I appreciate you really spelling things out. I've made progress but am not quite there yet.

  • updated the microcodes in the Asus stock BIOS in Windows, using mmtool.
  • unlocked the msr register using UEFIPatch (no error messages and patched BIOS file created)
  • as suggested, I ran UEFIPatch first and then updated the microcodes in Windows
  • am using a PNY USB 2.0 8GB flash drive, formatted FAT32, with the patched BIOS renamed to X99D.CAP in the correct port (the one with the green rectangle around it
  • I turned on the power and held down the flashback button until the first blink of the blue LED (about two seconds). I released it whereupon it blinked three more times and then turned solid. It stayed solid indefinitely.
  • I tried the above using an unpatched Asus BIOS file with the same result (encouraging, in a way).
  • I successfully reflashed the Asus BIOS from within the UEFI using the same unpatched Asus file.
  • I tried reflashing with the patched BIOS from within the UEFI. I got an error along the lines of "This is not a proper BIOS." (I believe this expected?)

My guess is that I either have a hardware issue with my motherboard or else that there is something blindingly obvious (except to me) that I'm doing wrong with the USB flashback. Does it matter what devices are connected to the motherboard? Could the CMOS backup battery come into play? Is there a command that resets the board to its out of the box state?

 

 

 

 

 

 

 

Yes something goes definitely wrong with EZ Flashback at your side (it is definitely not a faulty motherboard though)

 

1.) NEVER BUT NEVER flash a patched BIOS firmware from within the BIOS! Flash any patched firmware with EZ Flashback only! 

 

2.) Always consider the correct ASUS EZ flashback filename convention for your respective motherboard. For the X99 Deluxe any firmware to be flashed (if original or patched) must be named X99D.CAP to make the EZ Flashback work at all. 

 

3.) For EZ Flashback, the USB Flash drive with the X99D.CAP file must be connected to the EZ Flashback USB port on your motherboard (there is just one port on each ASUS motherboard clearly denoted such)!  

 

4.) Although in my case the EZ Flashback also works with a 32GB USB3.0 Flash drive formatted with FAT32, you could also try USB2.0 or USB3.0 USB flash drives <8GB formatted with FAT32.

 

Considering 1.) to 4.)  MUST solve your issue. 

 

Good luck,

 

KGP  

 

 

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites
On 3/8/2019 at 6:46 PM, maxneko said:

 

 

FYI, I tried loading the BIOS file created by MMTool directly from a USB flash drive with the computer off but the update didn't go through. The LED just flashed four times and then stayed solid. I also tried via the UEFI at startup but got an error message.

 

Any thoughts on how to proceed?

 

Thanks for your help.

 

Max

Hi Max

This is a well known behaviour with some Bios release (asus X99 deluxe I and II and also with asus x99 rampage V and 10)

If you are sure that your bios is good (original from Asus surely is) and also your USB is working well (formatted as required from asus EZ flash specs)

try this

clear motherboard cmos with button you have on motherboard

this will put in default condition your BIOS USB settings

then try again to flash with EZ flash procedure.

You should be able now to complete your task...

let me know

 

Share this post


Link to post
Share on other sites
On 3/10/2019 at 2:12 PM, fabiosun said:

Hi Max

This is a well known behaviour with some Bios release (asus X99 deluxe I and II and also with asus x99 rampage V and 10)

If you are sure that your bios is good (original from Asus surely is) and also your USB is working well (formatted as required from asus EZ flash specs)

try this

clear motherboard cmos with button you have on motherboard

this will put in default condition your BIOS USB settings

then try again to flash with EZ flash procedure.

You should be able now to complete your task...

let me know

 

Thanks, @fabiosun. I've been trying for the last day or two, off and on but still without success. 

  • With the power supply switch on but the computer not yet turned on, I pressed the red button that clears CMOS. The computer would wake up and start trying to boot. I then turned the power off and back on. I then tried the flashback but no different result. I would hold down the flashback for about two seconds until the LED started to blink. The LED would blink a total of three times and on the fourth remain lit for however long the power supply was left on. When I'd restart the computer, my CMOS settings had been cleared but the BIOS was the same.
  • The latest BIOS, 3902, is designated as a beta, although it's been out for nearly a year. I downgraded to 3802 via the UEFI and then tried to upgrade to 3902 via USB flashback. That, too, didn't work.
  • I tried patching 3802 but no better luck when it came to the USB flashback.
  • I haven't yet tried removing the CMOS battery, although I'm not quite sure why it would make a difference.
  • I tried disconnecting everything connected to the motherboard except the CPU. Still no luck.

This has been object lesson to me in leaving well-enough alone. A few months ago, I had a fully functioning Hackintosh in High Sierra. But I had always been annoyed by my failure to get both GPU's working. For some reason, my Hackintosh was only happy when it had a Thunderbolt card that I never used in the fifth slot. I decided to ditch the adapter and go with just the two GPU's and RAID controller. As I was taking things apart, it occurred to me not to get greedy. I then couldn't get it to reboot in High Sierra and finally decided to take the opportunity to update to Mojave. Since then, I've had to do my photo editing in Windows which isn't impossible but generally sucks. I have 10GB of data on an HFS-formatted RAID that Windows can read thanks to software from Paragon. I'm concerned that this isn't a resilient setup, particularly because while I have the usual arsenal of Mac troubleshooting software, I have nothing equivalent in Windows and wouldn't know how to use it if I did.

 

While it's more elegant to proceed with a patched BIOS, I assume that it's not a dealbreaker. Is it time to move on?

Share this post


Link to post
Share on other sites
Posted (edited)
20 minutes ago, maxneko said:

Thanks, @fabiosun. I've been trying for the last day or two, off and on but still without success. 

  • With the power supply switch on but the computer not yet turned on, I pressed the red button that clears CMOS. The computer would wake up and start trying to boot. I then turned the power off and back on. I then tried the flashback but no different result. I would hold down the flashback for about two seconds until the LED started to blink. The LED would blink a total of three times and on the fourth remain lit for however long the power supply was left on. When I'd restart the computer, my CMOS settings had been cleared but the BIOS was the same.
  • The latest BIOS, 3902, is designated as a beta, although it's been out for nearly a year. I downgraded to 3802 via the UEFI and then tried to upgrade to 3902 via USB flashback. That, too, didn't work.
  • I tried patching 3802 but no better luck when it came to the USB flashback.
  • I haven't yet tried removing the CMOS battery, although I'm not quite sure why it would make a difference.
  • I tried disconnecting everything connected to the motherboard except the CPU. Still no luck.

This has been object lesson to me in leaving well-enough alone. A few months ago, I had a fully functioning Hackintosh in High Sierra. But I had always been annoyed by my failure to get both GPU's working. For some reason, my Hackintosh was only happy when it had a Thunderbolt card that I never used in the fifth slot. I decided to ditch the adapter and go with just the two GPU's and RAID controller. As I was taking things apart, it occurred to me not to get greedy. I then couldn't get it to reboot in High Sierra and finally decided to take the opportunity to update to Mojave. Since then, I've had to do my photo editing in Windows which isn't impossible but generally sucks. I have 10GB of data on an HFS-formatted RAID that Windows can read thanks to software from Paragon. I'm concerned that this isn't a resilient setup, particularly because while I have the usual arsenal of Mac troubleshooting software, I have nothing equivalent in Windows and wouldn't know how to use it if I did.

 

While it's more elegant to proceed with a patched BIOS, I assume that it's not a dealbreaker. Is it time to move on?

 

Did you consider what I outlined in post 

 

 

I am convinced that your problem is the USB stick. Also note that X99D.CAP cannot be in any subdirectory on the stick. Which USB stick are you using? Is it formatted with FAT32? To which USB port do you connect the USB stick?   

 

The blinking you describe is typical when EZ Flashback does not find any X99D.CAP to be flashed. BTW.. Are your sure that you have a X99 Deluxe and not a X99 Deluxe II?  

 

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites
Posted (edited)
On 3/10/2019 at 1:59 PM, KGP-iMacPro said:

4.) Although in my case the EZ Flashback also works with a 32GB USB3.0 Flash drive formatted with FAT32, you could also try USB2.0 or USB3.0 USB flash drives <8GB formatted with FAT32.

 

Yes!!! I just tried with a 16GB USB3 flash drive and it worked! (I tried with the 32GB version of the same flash drive, but didn't have any luck yesterday.) My PNY 8GB USB2 flash drive is quite old. I wonder whether there are firmware updates for it.

 

Thanks so much.

 

EDIT (Update): I checked the three USB flash drives that I had been using. While they were all formatted with FAT32, two of them had GUID Partition Maps. I must have formatted them on my MBP without first selecting Show All Devices. Had I done so, I would have seen the partition map option which otherwise doesn't appear. Even though these devices were accessible through the UEFI, this might explain why the USB flashback wasn't working. This was an expensive lesson from a time standpoint. I built my Hackintosh back in late 2014 because Apple wasn't making the computer that I wanted. I need to remind myself of this because if I place any value on the time I've put in over the years, this turns out to be vastly more expensive than the trashcan Mac Pro of 2014. At the end of the day, you have to enjoy the process.

Edited by maxneko
Update

Share this post


Link to post
Share on other sites

I was able to install Mojave, however, the boot hangs at:

 

IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0

 

I've been trying to install Mojave for months (various guides) and this is the error that always defeats me. I've come across posts suggesting that it's related to my GPU. Do I need a framebuffer patch? I'm using dual ASUS Radeon R9280X-DC2T-3GD5 GPU's. I believe that this is the same card as the AMD HD7970 which has been natively supported until now. Before I try this, I'm wondering whether @KGP-iMacPro or anyone else sees something that is fixable in my config.plist or choice of drivers and kexts.

 

Thanks for your help.

 

Max

config.plist

CLOVER.zip

IMG_5473.jpg

Share this post


Link to post
Share on other sites
Posted (edited)

Guide update to 10.14.4 (18E226) completed

 

X99-10_14.4.thumb.png.e8f58c9df3b1c7da3d6cd2cdb2393bc4.png

 

129079807_Screenshot2019-03-26at00_31_14.thumb.png.17539506d5784e729b5725af0ba03cf0.png

 

New 10.14.4 EFI-Folder distribution EFI-X99-10.14.4-Release-iMacPro1,1-250319.zip in the X99 EFI-Folder Github repository. Clover_v2.4k_r4903 and new 10.14.4 USB port limit patch implementation. Updated FakeSMC and HWSensor distribution. Implementation of latest Lilu.kext and AppleALC.kext distributions. One should also add latest Whatevergreen.kext distribution.

Still no native vanilla Radeon VII macOS implementation (still no default Radeon VII device-ID 0x66AF1002 in the vanilla AMDRadeonX5000.kext).

 

Also note new Xcode 10.2 and Xcode 10.2 Command Line distributions. 

Enjoy and have fun,

 

kgp.png.6c52bb0ab65586ffe2c2ca3591273fdc.png

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites

MacOS 10.14.4 (18E2034) - special build 

This afternoon @DSM2  advised me that yesterday Apple seems to have added a second special build of MacOS 10.14.4 (18E2034) on swcdn.apple.com, likely for new devices.

 

819183963_Screenshot2019-03-26at23_53_16.png.9c4eea00b53d63e0142f750e3921b2de.png

 

376835768_Screenshot2019-03-26at23_54_11.png.c001b918a96d217e083ef1758b3f025b.png

 

1813992324_Screenshot2019-03-26at23_19_50.thumb.png.a7742a3fd8f76a859bf5e60d21b25d2b.png

 

And here is the script for the respective Install MacOS.app creation: createInstaller-10.14.4-SB.sh.zip.

EFI-X99-10.14.4-Release-iMacPro1,1-250319.zip is also fully valid in this case. 

No native vanilla implementation of the Radeon VII also with this macOS build yet. 

Enjoy and have fun,
 

 

kgp.png.cf91b2097c0c9ee8d72dbc7f53ae03e2.png

Share this post


Link to post
Share on other sites

Native Radeon VII support with MacOS 10.14.5 public beta 1

 

See respective IM thread.

 

Unfortunately I am not able to confirm this by myself as I cannot implement the air flow Radeon VII in my water blocked X299 system and my X99 system with the air flow Radeon VII does not boot with 10.14.5 beta 1 as the XCPM_pkg_scope kernel patch (not required for X299) seems broken with 10.14.5 beta 1. I was not able to reach @PMheart for the necessary XCPM_core_scope kernel patch update and in 4 hours I have to leave to the airport and will not have any access to my computers for 6 days.

 

Thus, all X299 guys, enjoy Radeon VII with 10.14.5 beta 1. All necessary kext and kernel patches implemented in EFI-X299-10.14.4-Release-iMacPro1,1-250319.zip are working. I already updated to 10.14.5 beta 1 on X299 and everything is fine and working. 

 

All X99 guys should wait with the update to 10.14.5 beta 1 until an updated XCPM_pkg_scope kernel patch is available. All other kext and kernel patches implemented in EFI-X99-10.14.4-Release-iMacPro1,1-250319.zip should continue working also under 10.14.5 beta 1.

 

There are Radeon VII SSDTs in the X99 (Slot-1, ASUS X99-A II) and X299 (Slot-1, ASUS Prime X299 Deluxe; Slot-5 ASUS WS X299 Sage 10G) SSDT Github directories, which yet need to be verified and hopefully will also work with the native Radeon VII implementation after a likely necessary ACPI path and ACPI replacement adaptation depending on your motherboard and Radeon VII PCIe slot population.  

 

Also it is recommended to use the latest versions of Lilu.kext (1.3.5), AppleALC.kext (1.3.6) and Whatevergreen.kext (1.2.7). 

 

Good luck and see you in one week from now.

 

KGP

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By fusion71au
      Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VMware Workstation on a Windows Host
       
      I wanted to make a simple guide on how to create a vanilla OS X El Capitan virtual machine running on a Windows host.  The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh.
       
      There are many guides and videos on the net about running OS X on Windows machines using pre-made VMWare disk images but you can never guarantee what else is in there….
       
      I’ve gathered info for this guide from various threads in the Multibooting and Virtualisation section of this forum eg
       
      Workstation 11/12, Player 7/12, Fusion 7/8 and ESXi 6 Mac OS X Unlocker 2 by @Donk How to Install OS X 10.x from Snow Leopard to El Capitan in VMware Workstation 10/12, Player 6/8 or ESXi 5/6 by @MSOK HOW TO: Create a bootable El Capitan ISO for VMware Credit and thanks to @Donk, @Albert Nietsnie and @MSOK for all their hard work in creating and testing the VMware Unlocker program.
       
      Requirements
      Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X) 4GB or more RAM (2GB or more will be needed for OS X) Hard Disk with at least 40GB free for Virtual Machine VMware Workstation 12 or later VMware Unlocker 2.0.7 or later Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#41 16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC Prepare Installation ISO on your Mac or Hack
      1.  On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder.
      2.  Unmount any attached install image/InstallESD.dmg (if currently mounted) by rebooting the system or running the hdiutil unmount command in terminal eg
       
      3.  Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes….
       
       
       
      4.  Open OS X terminal, then run the following commands to execute the script:
      cd downloads chmod +x CECI.tool ./CECI.tool 5.  At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later.
       
      Updates:
      @shela has created an ISO generating script compatible with OS X 10.6-10.12: create_osx_iso post #362.
      See post#30 for macOS_iso_cim.tool script to create ISO for macOS 10.13+ using Apple's createinstallmedia utility.
       
      Install and Patch VMware Workstation 12 on your PC
      1.  Download and install VMWare Workstation Player 12 or later
      2.  Download and extract Unlocker 2.0.7 or later to your USB stick…
      3.  Run the win-install.cmd as administrator by right clicking the file in Windows explorer or run it from an Administrative Command Prompt.
       



       
      Create an El Capitan Virtual Machine
      1.  Double click on the VMware Workstation 12 Player icon on your desktop and click “Create a New Virtual Machine”.  Choose “I will install the operating system later” at the How will you install screen….
       

      2.  Select Apple Mac OS X as the Guest operating system and OS X 10.11 as the version.  By default, an OS X 10.11 folder will be created in your Documents\Virtual Machines folder.
       


      3.  Under Specify Disk Capacity, you can leave the default 40GB or set a larger value.  I personally store the virtual disk as a single file.  Click Finish and you will see OS X 10.11 on the Main Screen of Workstation 12.
       


      4.  Next, we need to edit the virtual machine settings to map the virtual SATA CD/DVD drive to the El Capitan installation iso we created earlier.
       


       
      5.  To prevent the virtual machine from crashing in Windows, the virtualHW.version set in the vmx configuration file needs to be changed from 12 to 10 (alternatively, the line smc.version = "0" can be added to the file).  The OS X 10.11.vmx file can be edited with the WordPad program (navigate to the OS X 10.11 virtual machine folder with Windows Explorer and right click on the file to open in WordPad).
       


       
      6.  For HW10, set USB compatibility to USB 2.0, otherwise your mouse and keyboard might not work in the virtual machine.
       

      7.  Finally click “Play virtual machine”
       

      Installation of El Capitan
      Installation should be relatively straight forward, just following the prompts of the OS X installer:
      1.  Select language, agree to legal terms
       

      2.  Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended.  I’ve named the drive Macintosh HD but you can enter whatever you like eg El_Capitan.
       



      3.  Quit DU and choose Macintosh HD to install El Capitan on.
       

      4.  After 20-30 min (depending on how fast your system is), the installation will complete and the VM will automatically reboot…
       

      5.  At the welcome screen, choose your country and keyboard layout.  You can skip transfer information, location services and logging in with your Apple ID if you wish…
       


      6.  Create a User Account and select your Time Zone.  You can skip sending diagnostics and usage data to Apple….
       


      7.  Finally, you will arrive at the El Capitan Desktop.  You should eject the Installation iso now by right clicking and selecting “Eject OS X Base System”.  This will allow you to install VMware Tools….
       



      8.  After rebooting, the VM can now be resized or run at full screen resolution.  Audio and network/internet should also work OOB.
       

       
      SMBIOS Customization and iMessage Vars
      To make the Virtual Machine more "Mac like", you can edit the vmx file to add unique identifiers from a real Mac's SMBIOS -
      eg for an iMac 11,3 SMBIOS, you can enter the following lines....
      smbios.reflectHost = "FALSE" board-id.reflectHost = "FALSE" board-id = "Mac-F2238BAE" hw.model.reflectHost = "FALSE" hw.model = "iMac11,3" serialNumber.reflectHost = "FALSE" serialNumber = "W80#######6" Refer How to spoof real Mac in VMware - Multi-booting and Virtualisation.
       
      The critical variables for iMessage/Facetime activation are MLB & ROM.  By default, VMware "reflects" the host's MLB and ROM since it assumes you are running the OSX guest on a real Mac host - see post#42 by @Donk.
       
      If the host is a Windows PC, the following lines need to be added to the vmx file (requires virtualHW.version 12 and smc.version = "0")....
      efi.nvram.var.ROM.reflectHost = "FALSE" efi.nvram.var.MLB.reflectHost = "FALSE" system-id.enable = "TRUE" and the MLB, ROM and optionally system-id entered manually eg
      efi.nvram.var.MLB = "W80######BA1A" (MLB can be 13 or 17 characters long, alphanumeric string) efi.nvram.var.ROM = "<=>?@A" (ROM is entered here as a 6 character ASCII string) uuid.bios = "## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##" <---Optional (if you want to inject a given system-id hexadecimal value) Note the output for ROM from imessage_debug is a 12 character hexadecimal that needs to be entered here as a 6 character ASCII string eg using an Hex to ASCII converter we find that "3c3d3e3f4041" hex is equivalent to   "<=>?@A".
       
      Vanilla Mavericks and Yosemite
      The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite .  Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware.
       
      With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie
       
      To create a Mavericks ISO on your desktop
      cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop
      cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5...
       

       
      Enjoy
       
      Update for macOS 10.12 Sierra
      The above settings still work for macOS Sierra after upgrading to VMware Workstation 12.5 and unlocker 2.0.8 - see post #13.
       
      Update for macOS 10.13 High Sierra and 10.14 Mojave
      See post#30 for macOS_iso_cim.tool script to create ISO for macOS using Apple's createinstallmedia utility.
      Post#41 describes how to build "Install macOS ******.app" on the fly from installer files downloaded beforehand in /SharedSupport folder.
       
      Update for macOS 10.15beta Catalina
      See post Update for macOS Catalina 10.15beta
       
      CECI.zip
      CYI.tool.zip
      CMI.tool.zip
    • By crazybirdy
      Patched OSInstaller.framework to allow macOS 10.14 installation on MBR HFS+ partition.
       
      To use those patched files you must follow HowTo to create an USB installer. You can't just run the app downloaded from Mac App Store.
      The patch is made base on 落下爱@pcbeta 10.10.x MBR patch method, and more patch for 10.14 HFS Firmware check by crazybirdy.
       
      What is this patched OSInstaller doing?
      1. Patch the MBR check, allow macOS 10.14 installation on MBR partition.
      2. Patch the Firmware check, bypass the error of "An error occurred while verifying firmware".
      3. Patch to stop auto-convert to APFS , "ConvertToAPFS=false" is no longer worked with 10.14.
      4. This patched MBR OSInstaller will never convert to APFS, and will always install as HFS+ partition.
      5. This patched MBR OSInstaller method works with both MBR HFS+ and GPT HFS+ partition (GPT+recovery).
      No longer need to set new SMbiosversion, FirmwareFeatures, and FirmwareFeaturesMask with this MBR-patch.
       
      What's the difference between createinstallmedia method, MBR-Manual-Method, and MBR-Automatic-Method?
      As the following....
      1. createinstallmedia method,
          needs stage 1, stage 2 installation process, which is worked with GUID partition only, always convert to APFS format.
      2. MBR-Manual-Method (same as 10.12),
          install via stage 2 manually, which is worked with both MBR and GUID, HFS+ and APFS, will never convert the partition format.
          We can manually format as MBR or GPT, HFS+ or APFS on installation screen like as 10.12.
          We can manually select MBR HFS+ partition to install 10.13 and 10.14 on installation screen now.
          Needn't to update the MBR-Manual-Method files, it will still work on 10.13, and 10.14 future versions, I think so.
          It can be installed as Fresh installation on formated blank partition only, but can't be installed as update from previous version.
      3. MBR-Automatic-Method (new for 10.13+),
          install via stage 2 automatically, which is worked with both MBR and GUID, HFS+ and APFS, will never convert the partition format.
          It can be installed as Fresh installation on formated blank partition, and can be installed as update from previous version.

      How to make 10.14 installer for MBR (MBR-Manual-Method)?
      Just use EasyMBR-InstallerMaker to make installer, it works with both MBR and GPT.
      Read HowTo inside the dmg first, same as 10.12.
      Read HowTo Q/A Q5. How to patch to work with CPU SSE4.1 only for Mojave?
      Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      Read HowTo Q/A Q7. How to update 10.14.x combo-update to MBR and GPT with installScript directly?
       
      How to make 10.14 installer for MBR (MBR-Automatic-Method)?
      Just use 14MBRinstallerMaker to make installer, it works with both MBR and GPT.
      Read HowTo inside the dmg first, same as 10.13.
      Read HowTo Q/A Q5. How to patch to work with CPU SSE4.1 only for Mojave?
      Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      Read HowTo Q/A Q7. How to update 10.14.x combo-update to MBR and GPT with installScript directly?
       
      And, need a SMBIOS supported with /System/Library/CoreServices/PlatformSupport.plist.
       


       
      Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      A6. Some people download installer app from App Store, and get only 18 MB size, not the complete installer app (5.68 GB). You should boot to 10.12, or 10.13 to download it again from App Store, or use script Q6-DownloadFullApp/installScript_1014fullapp to download the full installer app via swscan.apple.com.
       

       
    • By fusion71au
      Patch Catalina or Mojave macOS Installer App for Unsupported Machines
       
      Often for economic reasons, Apple prevents the Installer.app for its latest macOS from installing on older machines perfectly capable of running it eg macOS 10.14 Mojave on Unsupported Macs Thread.
       

       
      In Mojave 10.14, @ASentientBot posted a method to patch the distribution file in OSInstall.mpkg to enable the Mojave installer to install on unsupported machines (with or without graphics card metal support). 
       
      In Catalina 10.15beta, the above method no longer works since Apple is checking OSInstall.mpkg for its file signature and the mandatory requirement in Catalina to install to 2 separate apfs volumes necessitates using the original Catalina macOS Base System Installer.  Fortunately, it is still possible to substitute High Sierra’s Apple Signed OSInstall.mpkg inside the Catalina or Mojave InstallESD.dmg by making it R/W.
       
      The procedure below will allow Macs or Hacks able to install High Sierra to also install Catalina or Mojave (eg SMBIOS MacPro5,1, iMac11,3, MacBook Pro7,1 which have been unsupported in macOS 10.14.x and 10.15beta) -credit to @ASentientBot's post.
       
      Prerequisites
      1. Mac or Hack capable of and running High Sierra 10.13.x
      2. An original, untouched copy of OSInstall.mpkg from High Serra InstallESD.dmg - attached OSInstall_10.13.6.mpkg.zip save to your ~/Downloads folder
      3. macOS Installer App eg for Catalina beta or Mojave downloaded to /Applications
      4. Add NVRAM boot arg (or Clover config.plist boot arg on a hack) -no_compat_check to enable system to boot to final completed Mojave or Catalina install.
       
      Procedure
      1. Open Terminal and type the following
       
      open /Applications/Install*/Contents/SharedSupport/InstallESD.dmg (assuming the Catalina or Mojave Installer App is in /Applications)  
      2. Open Disk Utility, click File|New Image|Image from ‘InstallESD”
      3. Save as read/write image, no encryption in /Applications
      4. Unmount InstallESD in DU by clicking the "eject" icon next to it
       
       
      5. Open the R/W InstallSD.dmg in /Applications and replace Catalina’s/Mojave's OSInstall.mpkg with High Sierra’s version by typing in terminal
       
      open /Applications/InstallESD.dmg cp ~/Downloads/OSInstall_10.13.6.mpkg /Volumes/InstallESD/Packages/OSInstall.mpkg  
      6. Unmount InstallESD in DU by clicking the "eject" icon next to it
      7. Replace original Catalina/Mojave InstallESD.dmg with our patched one, making a backup of the original.  In terminal, type
       
      sudo mv /Applications/Install*/Contents/SharedSupport/InstallESD.dmg /Applications/InstallESD_orig.dmg sudo mv /Applications/InstallESD.dmg /Applications/Install*/Contents/SharedSupport/  
      8.  Test the newly patched installer!…

    • By mfkk
      I install Mojave by following RehabMan Guide. After install I copy the Intel HD4000 7 series Config.plist from RehabMan. In my system configuration shows 1536MB graphics but I don't get the graphics performance . I have graphics related problems and lags issues. dock don't have transperancy, browsers have black shade and don't see fonts etc. I try many config files but I can't fix the issue still now. When I try some config file it will be fix until restart or shutdown. After that I have still graphics problem. Over a month I try to fix this I didn't get any result still now. Please help me to fix this . I'm first time in Hackintosh and I don't have knowledge about it.
       
      Intel HD4000 Graphics with 1366x786 (8086/0166)
      i3 processor
      6gb ram
      123gb ssd 

    • By Cyberdevs
      Please read me:
      Ever since macOS Mojave came out (I mean the first DP) Apple removed the support for Atheros based WiFi Adapters from the IO80211Family.kext, so to fix it we need to add the AirPortAtheros40.kext to the Extensions manually.
      After each clean install the AirPortAtheros40.kext needs to be installed and after clean installing Mojave DPs after few times I decides to create this app to save some time.
       
      How to use it:
      This application will install the missing AirPortAtheros40.kext into /System/Library/Extensions and after the installation is done and once you reboot your computer the Atheros based WiFi adapters will be enabled.
      The installation is the first step of the process and it is fast but the next steps which are repairing the permission on /System/Library/Extensions and rebuilding the system caches might take a while so please wait until you were asked to reboot your computer.
       
      I'm using a TP-Link WDN4800 with an Atheros chipset and it works on other similar hardware.

       


       
×