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
      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.

       


       
    • By ludufre
      Installing macOS Mojave 10.14.5 on Gigabyte Z370N WIFI + i7 8700K + UHD 630



      Changelog:
       
      06/10/2019 00:44h GMT-0
      - Completely rewritten.
       
      10/17/2018 08:12h GMT-0
      - Fix Kexts permissions commands adjusted.
      - Removed FrameBuffer patch that is not needed.
      - Added audio solution and HDMI.
      - Unfortunately DisplayPort does not work.
      - Replaced Wifi/BT with DW1560 (BCM94352Z)
       
      10/11/2018 04:15h GMT-0
      - Added USB 3.0 patch.
      - Adjusted some steps.
      - Changed text formatting.
       
      10/11/2018 03:42h GMT-0
      - Added missing UEFI configuration.
       
      10/07/2018 00:36h GMT-0
      - First version.
       
      What works and what does not
       
      - Processor: Intel Core i7-8700K ->  Work. All SpeedStep stages.
      - Video Card: Intel UHD 630 ->  Work. QE/CI and Metal.
      - Chipset: Intel Z370 ->  Work.
      - HDMI 2.0 (1st) ->  Work.
      - HDMI (2nd) ->  Work.
      - DP ->  Not tested yet.
      - Audio: ALC1220 ->  Work.
      - HDMI Audio ->  Work.
      - WiFi/Bluetooth ->  Not work. Replaced with BCM94360CS2.
      - Ethernet (1st) ->  Work.
      - Ethernet (2nd) ->  Work.
      - USB3.0 ->  Work.
      - Sleep ->  Work.
      - Airdrop, Handoff, Instant Hotspot and Continuity ->  Work after replaced wireless.
       
       
      Todo
       
      - Make audio work.
      - Make HDMI audio work.
      - Test DisplayPort.
      - Make second ethernet work.
      - Replace Wifi/Bluetooth.
      - Test DP.
       
      What you need to install

      - Running install of macOS
      - One USB flash drive of 8GB or bigger
      - macOS Mojave install app
      - Clover Configurator
      - Clover EFI
      - Clover Configurator
      - Some KEXTs and SSDT patches


      How create create the install flash drive
       
      Prepare install flash drive

      Format the flash drive with GUID partition mapping and name it "Install".

      - Open Disk Utility.
      - Click in View, then "Show All Devices".
      - Select the destination flash drive, then Erase.
      - Name: Install, Format: Mac OS Extended (Journaled) and Scheme: GUID Partition Map
       
      Create install flash drive

      Open terminal and run this command:
      sudo /Applications/Install\ macOS\ .app/Contents/Resources/createinstallmedia --volume /Volumes/Install--nointeraction This will take about 30 minutes.
       
       

      Install bootloader

      Download the CloverEFI (used 4953, from Automated Clover Builds) and install with this options on "Install macOS Mojave":
       
      - Install for UEFI booting only
      - Install Clover in the ESP
      - UEFI Drivers - ApfsDriverLoader-64
      - UEFI Drivers - AptioMemoryFix-64
      - UEFI Drivers - HFSPlus
      - UEFI Drivers - NvmExpressDxe-64 (I have an NVME SSD)
      - FileVault 2 UEFI Drivers (I strongly recommend enable FileVault)


       
       
      Make things works
       
      We'll make a full working flash drive, so follow these instructions:
       
      Will be mounted the EFI partition of the flash drive.
       
      Open the the /Volumes/EFI/CLOVER/config.plist inside this new partition with Clover Configurator (used 5.4.4.0)
       
      Important modifications
       
      config.plist

      BOOT Page
       
      - Add: Arguments - darkwake=2
      - Uncheck: NeverDoRecovery
      - Check: Legacy - XMPDetection=Yes
       
      KERNEL AND KEXT PATCHES Page
       
      - Check: KernelPm
       
      RT VARIABLES Page
       
      - Change: CsrActiveConfig - 0x3
       
      SMBIOS Page
       
      - Change: Macmini8,1 - Mac mini (Late 2018) | Intel Core i7-8700B @ 3.20 GHz

       
      - Click: Generate New (few times in the two buttons)

       
       
      Need some Kexts in the folder /EFI/CLOVER/kexts/Other/
       
      - Download the HWSensors 3 from here. I used the FakeSMC.kext, ACPIMonitor.kext and IntelCPUMonitor.kext inside of DMG version r196.
      - Download the Lilu.kext from here. I used the version 1.3.6.

       
      Intel UHD 630
       
      ACPI Page
      - Uncheck: Fixes - AddHDMI
      - Uncheck: Fixes - FixDisplay
      - Uncheck: Fixes - FixHDA
       
      GUI Page
      - Change: Screen Resolution - 3840x2160 (My monitor is 4K)

      Need a Kext in the folder /EFI/CLOVER/kexts/Other/
       
      - Download the WhateverGreen.kext from here. I used the version 1.2.9.

       
      Audio ALC 1220 and HDMI audio

      BOOT Page
      - Add: Arguments - alcid=11

      DEVICES Page
      - Change: Audio - Inject - 11
      - Uncheck: Audio - AFGLowPowerState
      - Uncheck: Audio - ResetHDA

      Need a Kext in the folder /EFI/CLOVER/kexts/Other/
       
      - Download the AppleALC.kext from here. I used the version 1.3.8.

       
      All USBs (2.0, 3.0, Type-C, internal)
       
      KERNEL AND KEXT PATCHES Page - KextsToPatch
       
      - Name*: com.apple.iokit.IOUSBHostFamily
      - Find* [HEX]: 83FB0F0F
      - Replace* [HEX]: 83FB3F0F
      - Comment: USB Port Limit Patch 1 PMHeart/DalianSky
      - MatchOS: 10.14.x
       
      - Name*: com.apple.iokit.IOUSBHostFamily
      - Find* [HEX]: 83FB0F0F
      - Replace* [HEX]: 83FB3F0F
      - Comment: USB Port Limit Patch 2 PMHeart/DalianSky
      - MatchOS: 10.14.x
       
      - Name*: com.apple.driver.usb.AppleUSBXHCI
      - Find* [HEX]: 83FB0F0F
      - Replace* [HEX]: 83FB3F0F
      - Comment: USB Port Limit Patch 3 PMHeart/DalianSky
      - MatchOS: 10.14.x
       
      - Name*: com.apple.driver.usb.AppleUSBXHCI
      - Find* [HEX]: 83FF0F0F
      - Replace* [HEX]: 83FF3F0F
      - Comment: USB Port Limit Patch 4 PMHeart/DalianSky
      - MatchOS: 10.14.x
       
      Need a Kext in the folder /EFI/CLOVER/kexts/Other/
       
      - Download the USBInjectAll.kext from here. I used the version 2018-1108.
       
      Need SSDT patch in the folder /EFI/CLOVER/ACPI/patched/
       
      - Download the SSDT-EC.aml, SSDT-UIAC.aml and SSDT-USBX attached bellow.
       
      Wifi and Bluetooth (BCM94360CS)
       
      Works out of box (plug 'n' play).
       
       
      LAN Cards
       
      Need a Kext for feach card in the folder /EFI/CLOVER/kexts/Other/
       
      - Download the IntelMausiEthrenet.kext from here. I used the version 2018-1031.
      - Download the SmallTreeIntel82576.kext attached bellow. I do not remember where I found it.

       
      Now you can start the instalation without problem (I guess).
       
       
      How install
       
      UEFI Setup Configuration and Installation

      UEFI configuration
       
      - Shutdown and insert the flash.
      - Power on with DEL pressed to enter BIOS setup.
      - Change value: Periphelrals - Initial Display to IGP
      - Change value: Periphelrals - USB Configuration - XHCI Hand-off to ENABLE
      - Change value: Chipset - VT-d to DISABLE
      - Change value: Chipset - Internal Graphics to ENABLE
      - Change value: Chipset - DVMT Pre-Allocated to 128M
      - Save & Exit Setup
       
      - Now, hold the F12
      - In the list, select your flash drive.
      - It will show twice. One with UEFI prefix and another without.
      - Select with UEFI prefix. Ie.: "UEFI: Sandisk Cruzer"
       
      The installer will start. 
      
      Format destination disk

      Format the disk with GUID partition mapping and name it "HD".

      - Select Disk Utility in the list, then press Continue.
      - Click in View, then "Show All Devices".
      - Select the destination Disk, then Erase.
      - Name: HD, Format: APFS and Scheme: GUID Partition Map

      Close Disk Utility.
      
      Select "Install macOS", then Continue.
      Follow instructions in screen.

      After install

      After first part install the system will reboot.
      
      The second part of the installation will begin. This will take 16 minutes.
       

      Post installation

      Install bootloader
       
      When the second part of install finish, the system will reboot again.

      After performing the user initial setup and go to the desktop, you need to install Clover on internal disk.

      Open the Clover installer inside flash drive that you copied before.

      Use same options above but choose the system partition this time.

      Now you need to replace the EFI folder inside your destination disk EFI parittion, with EFI folder inside flash card EFI partition.

      If the flash drive EFI partition of your destination disk or flash drive is unmounted:
      Mount with terminal "sudo diskutil mount /dev/rdiskXs1". To know what X is, use "diskutil list", most likely is 0 for destination disk and 1 for flash drive.
       
      Then, eject the flash drive.
       
      Last step
       
      Move all Kexts from EFI partition to /Library/Extensions, with those commands in Terminal:
      sudo mv -R /Volumes/EFI/EFI/CLOVER/kexts/10.14/* /Library/Extensions/ sudo chmod -R 755 /Library/Extensions sudo chown -R root:wheel /Library/Extensions sudo kextcache -i / Restart the system.
       
       
      It's done!

       
      And last but not least
       
      I would like to thank the following community members, by making these dream possible:
      @crushers, @snatch, @apianti, @blackosx, @blusseau, @dmazar, @slice2009, @autumnrain, @phpdev32, @EMlyDinEsH, @RehabMan, @Scellow, @mitch_de, @Shailua, @Andy Vandijck, @maxfierke, @ArturXXX, @LexHimself, @brumas and all others members involved directly or indirectly.
       
       
       
       
       
       
       
      Z370N-WIFI.zip
    • By ludufre
      Installing macOS Mojave on Lenovo ThinkPad L440

       
      There are two version of this laptop:
      - 20AS = Chipset QM87, without Express Card (mine).
      - 20AT = Chipset HM86, with Express Card.
      I strong believe is the same thing...
       

      Changelog:
       
      06/09/2019 14:16h GMT-0
      - Added missing parts in the post-install step. 
       
      06/04/2019 17:19h GMT-0
      - Updated Clover link. 
       
      06/02/2019 18:08h GMT-0
      - Added info about update 10.14.5. 
       
      03/13/2019 13:15h GMT-0
      - Updated info about touchpad replacement and CPU and 4G LTE modem.
       
      02/05/2019 18:47h GMT-0
      - Updated info about CPU replacement and 4G LTE modem.
       
      02/04/2019 15:24h GMT-0
      - Sometimes the VoodooHDA.kext doesn't work.
      - Added AppleHDADisabler.kext to fix that (attached bellow).
       
      01/24/2019 14:42h GMT-0
      - Added more adjustments to use of VoodooHDA.
      - Updated VoodooHDA links to 2.9.1 official (without installer).
      - Changed PCM volume from 90 to 180 in Info.plist (attached modified VoodooHDA.kext bellow)
      - Updated SSDT-L440.aml (Removed HDEF and HDAU, not needed).
      - Updated config.plist (Changed to user Audio layout to 1).
       
      01/22/2019 20:47h GMT-0
      - I gave up on the AppleALC.
      - Headset does not work.
      - Now with VoodooHDA is perfect and the sound even louder.
       
      01/22/2019 14:37h GMT-0
      - Added info about update 10.14.3. 
       
      01/22/2019 13:46h GMT-0
      - Added link to BIOS reassing guide.
       
      01/20/2019 11:49h GMT-0
      - First version.
       
      What works and what does not
       
      - Processor: Intel Core i5-4300M ->  Work. All SpeedStep stages.
      - Video Card: Intel HD4600 ->  Work. QE/CI and Metal.
      - Chipset: Intel QM87 ->  Work.
      - Mini DisplayPort ->  Work. But no audio, yet.
      - VGA ->  Not work. Normal.
      - Audio: ALC292 ->  Work.
      - WiFi/Bluetooth: Intel AC 7260 ->  Not work. Replaced with DW1560 (need whitelist removal).
      - Ethernet: Intel I217-LM ->  Work.
      - Card Reader: Realtek RTS5227 ->  Not work.
      - Keyboard and Touchpad ->  Work.
      - Webcam ->  Work.
      - Fingerprint Reader ->  Not work. Normal.
      - USB3.0 ->  Work.
      - Sleep ->  Work.
      - Airdrop, Handoff, Instant Hotspot and Continuity ->  Work after replaced wireless.
       
       
      Extras
       
      - FullHD 1920x1080 display upgrade: 
      Replaced with AU Optronics B140HAN01.1 30pin eDP (B140HAN01.2 and B140HAN01.3 also compatible).
      Apparently same screen as Dell Latitude E6440, E7440, Lenovo Ideapad U430 and E129.
       
      - CPU upgrade:
      Replaced the stock Intel Core i5 4300M 2.6Ghz (3.3Ghz turbo) 6M cache with Intel Core i7 4700MQ 2.4Ghz (3.4Ghz turbo) 6MB.
      I initially had problems with overheating. The processor ran at full load above 90 degrees.
      After using a quality thermal paste I can work between 70 and 80 degrees.
      Acceptable taking into consideration that the new processor has 47TDP versus 37TDP which is recommended.
      I also had no problem consuming the battery while charging. The original 65W source seems to have figured out.
       
      - Touchpad upgrade:
      Replaced the stock with T460 touchpad.
      This is serious: you have to do it! It should be stock. Touchpad with precision and absurd quality!
      Just do it!
       
      - RAM upgrade:
      No mistery here. Just upgade.
       
       
      Todo
       
      - Make DP audio work.
      - Make Card Reader work.
      - Upgrade CPU to i7-4712MQ (Ordered. It's on the way) Done, but received i7-4700MQ (47w TDP, with good paste I have no overheating)
      - Replace touchpad with T460 model (Ordered. It's on the way) Done. Sensitivity and perception of quality much better. I recommend 100%!
      - Sierra Gobi5000 4G LTE modem EM7355 (Ordered. It's on the way. I hope works. ) Done, but not work. Recognize but not connect. I already gave up...
      - Upgrade to 16GB RAM Done
      - Make trackpad appear in System Preferences
       
       
      What you need to install

      - Running install of macOS
      - One USB flash drive of 8GB or bigger
      - macOS Mojave install app
      - Clover EFI
      - Clover Configurator
      - Some KEXTs and SSDT patches


      How create create the install flash drive
       
      Prepare install flash drive

      Format the flash drive with GUID partition mapping and name it "Install".

      - Open Disk Utility.
      - Click in View, then "Show All Devices".
      - Select the destination flash drive, then Erase.
      - Name: Install, Format: Mac OS Extended (Journaled) and Scheme: GUID Partition Map
       
      Create install flash drive

      Open terminal and run this command:
      sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/Install --nointeraction This will take about 30 minutes.
       


      Install bootloader

      Download the CloverEFI from SourceForge (used 4934) and install with this options on "Install macOS Mojave":
       
      - Install for UEFI booting only
      - Install Clover in the ESP
      - UEFI Drivers - ApfsDriverLoader-64
      - UEFI Drivers - AptioMemoryFix-64


       
       
      Make things works

      Will be created a partition named EFI and mounted in Desktop.
      - Replace the /Volumes/EFI/CLOVER/config.plist with mine attached below
                    If you have modded BIOS with Advanced Menu and enabled 128MB DRAM-prealloc use 128MB_DRAM-prealloc_config.plist.zip
                    If no, then use 32MB_DRAM-prealloc_config.plist.zip
      - Put SSDT-L440.aml attached below in /Volumes/EFI/CLOVER/ACPI/patched/
       
      Generate your Serial, MLB and SmUUID
       
      - Open the replaced config.plist with Clover Configurator (used 5.3.2.0)
      - Go to SMBIOS, click few times in "Generate New" in Serial Number and SmUUID.
       
      Download those Kexts and put in /EFI/CLOVER/kexts/Other/
       
      - Download the HWSensors 3 from here. I used the FakeSMC.kext, ACPIMonitor.kext and IntelCPUMonitor.kext inside of DMG version r196.
      - Download the VoodooPS2Controller.kext from here. I used version 2018-1008.
      - Download the IntelMausiEthernet.kext from here. I used the version 2018-1031.
      - Download the Lilu.kext from here. I used the version 1.3.6.
      - Download the VoodooHDA from here. I used the version 2.9.1 and patched the sound volume (attached below).
      - Download the WhateverGreen.kext from here. I used the version 1.2.9.
      - Download the AppleBacklightFixup.kext from here. I used the version 2018-1013.
      - Download the USBInjectAll.kext from here. I used the version 2018-1108.
      - Download the ACPIBatteryManager.kext from here. I used the version 2018-1005.
       
      - Download the VirtualSMC.kext from here. I used version 1.0.2. Replaced with FakeSMC of the HWSensors 3 r196 package.
      - Download the FakeSMC.kext from here. I used the version 2018-0915. Replaced with VirtualSMC.kext due 10.14.4 issues on update.
      - Download the AppleALC.kext from here. I used the version 1.3.4. Replaced with VoodooHDA.kext due mic not working.
       
       
      Wifi and Bluetooth (DW1560 / BCM94352Z)
       
      Unfortunately, some notebook manufacturers are currently blocking the replacement of wireless cards. They want you to only use the models sold by them. And of course, none of them from Lenovo for this notebook model is compatible with MacOS.
       
      If you try to start with an unauthorized wifi card for them, you will receive a screen error:
      1802: Unauthorized network card is plugged in - Power off and remove the network card. Since this check is done directly in the BIOS, the only solution is to modify it.
      But since nothing is easy in this life, there is one small big problem:
      - The BIOS update procedure does not allow you to use modded files as it used to be.
      - You will need to physically reach your BIOS on the motherboard and make use of a USB BIOS reader/writer.
       
      So what you need to do:
      1. Disassembly your laptop;
      2. Dump your BIOS with an USB BIOS reader with SOIC8 clip (to not desolder from the motherboard);
      3. Patch it (In addition to removing the whitelist, add the advanced menu);
      4. Fix RSA signature;
      5. Reflash BIOS;
      6. Replace wireless card;
      7. Remount your laptop;
      8. Done.
       
      Soon, I'll provide step by step in this process. Probably until end of this week.
      In the meantime, if you need to, send me your dump that I do steps 3 and 4 for you.
      I also add the Advanced Menu so you can increase to 128MB the DRAM-prealloc.
       
      To fix a Modded BIOS to remove the 5 beeps on boot, you need this guide: https://www.insanelymac.com/forum/topic/337333-guide-fix-insyde-h2o-bios-signature-5-beeps-on-lenovo (traduzido: pt-BR)
       
       
      After replaced the wireless card. Download those Kexts and put in /EFI/CLOVER/kexts/Other/
       
      - Download the AirportBrcmFixup.kext from here. I used the version 2.0.0.
      - Download the BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext from here. I used the version 2018-0505.
      - Download the BT4LEContinuityFixup.kext from here. I used the version 1.1.2.
       
       
      Now you can start the instalation without problem (I guess).
       
       
      How install
       
      UEFI Setup Configuration and Installation

      UEFI configuration
       
      My BIOS is the latest: 1.93 (J4ET93WW) 

      - Shutdown and insert the flash drive.
      - Power on with F1 pressed to enter BIOS setup.
      - Change value: Config - Intel(R) AMT - Intel(R) AMT Control to DISABLED
      - Change value: Security - Security Chip to DISABLED
      - Change value: Security - Anti-Theft - Intel(R) AT Module Activation to DISABLED
      - Change value: Security - Anti-Theft - Computrace to DISABLED
      - Change value: Security - Secure Boot to DISABLED
      - Change value: Startup - UEFI/Legacy Boot to BOTH, Legacy First and CSM Support = Yes
      - Save & Exit Setup (F10)
       
      - Now, hold the F12
      - In the list, select your flash drive.
       
      The installer will start. 
      
      Format destination disk

      Format the disk with GUID partition mapping and name it "Macintosh".

      - Select Disk Utility in the list, then press Continue.
      - Click in View, then "Show All Devices".
      - Select the destination Disk, then Erase.
      - Name: HD, Format: APFS and Scheme: GUID Partition Map

      Close Disk Utility.
      
      Select "Install macOS", then Continue.
      Follow instructions in screen.

      After install

      After first part install the system will reboot. Maybe you have to press F12 again and select the flash drive.
      
      The second part of the installation will begin. This will take 16 minutes.
       

      Post installation

      Install bootloader
       
      When the second part of install finish, the system will reboot again.

      After performing the user initial setup and go to the desktop, you need to install Clover on internal disk.

      Open the Clover installer inside flash drive that you copied before.

      Use same options above but choose the system partition this time.

      Now you need to replace the EFI folder inside your destination disk EFI parittion, with EFI folder inside flash card EFI partition.

      If the flash drive EFI partition of your destination disk or flash drive is unmounted:
      Mount with terminal "sudo diskutil mount /dev/rdiskXs1". To know what X is, use "diskutil list", most likely is 0 for destination disk and 1 for flash drive.
       
      Then, eject the flash drive.
       
      Last step
       
      Move all Kexts from EFI partition to /Library/Extensions, with those commands in Terminal:
      sudo mv -R /Volumes/EFI/EFI/CLOVER/kexts/Other/* /Library/Extensions/ sudo chmod -R 755 /Library/Extensions sudo chown -R root:wheel /Library/Extensions sudo kextcache -i / Restart the system.
       
       
      It's done!
       
       
      Updates
       
      System update 10.14.3
       
      - Updated with success;
      - Everything works perfectly after reboot;
       

       
       
      System update 10.14.4
       
      - Updated Clover to 4910.
      - Updated Lilu.kext to 1.3.5 and WhateverGreen to 1.2.7.
      - After first reboot the update progress stoped with:
      GTrace synchronization point 4 Unsupported CPU Unsupported PCH hmm.. mismatch sizes: 3100 vs 20 It was still possible to start the previous installation, selecting "Macintosh" as opposed to "macOS Install" in Clover.
      So I created a flash drive with Clover 4910 and put only my config.xml, SSDT-L440.aml, the updated Lilu.kext and WhateverGreen.kext. And I decided to test VirtualSMC instead of FakeSMC.kext.
      With this I was able to install update 10.14.4. After installation I can boot normally, even with FakeSMC.kext that already in /Library/Extensions.
      I do not know what exactly happened, but now works everything like was previously.
       


       
       
      System update 10.14.5
       
      - Updated Clover to 4934.
      - Updated Lilu.kext to 1.3.6 and WhateverGreen to 1.2.9.
      - After first reboot the update progress stoped again (like 10.14.4 update) with:
      GTrace synchronization point 4 Unsupported CPU Unsupported PCH hmm.. mismatch sizes: 3100 vs 20 It was still possible to start the previous installation, selecting "Macintosh" as opposed to "macOS Install" in Clover.
      I decided to rollback to FakeSMC.kext but this time with the version of HWSensors 3. Link above.
      With this I was able to install update 10.14.5. After installation I can boot normally.
       

       
       

      And last but not least
       
      I would like to thank the following community members, by making these dream possible:
      @crushers, @snatch, @apianti, @blackosx, @blusseau, @dmazar, @slice2009, @autumnrain, @phpdev32, @EMlyDinEsH, @RehabMan, @Scellow, @mitch_de, @Shailua, @Andy Vandijck, @maxfierke, @ArturXXX, @LexHimself, @brumas, @Shiki and all others members involved directly or indirectly.
       
       
       
       
       
       
      32MB_DRAM-prealloc_config.plist.zip
      128MB_DRAM-prealloc_config.plist.zip
      SSDT-L440.aml
      VoodooHDA.kext.zip
      AppleHDADisabler.kext.zip
×