Jump to content
wmchris

[GUIDE] Dell XPS 15 (9550) Mojave 10.14.x Quick Installation

1,478 posts in this topic

Recommended Posts

@Lockzi My setup is running without HWPEnabler.kext in S/L/E with hibernate mode set to 0. I remember that goodwin_c mentioned at the previous thread that we do not need the kext since we can enable it at clover configurator and it is supported by Clover EFI (38XX ver and higher supports HWP if I am not wrong, have to check it at changelogs). So far I haven't encounter data corruption.

You do need the kext if you want to be able to control/change the power setting.

And exactly, if you do not use HWPEnabler.kext, but have HWPEnabled = true in config.plist that would mean that you enable HWPEnable before kernel loads which if my theory is correct - would not result in corruption.

 

 

 

So if data corruption occurs. The system becomes useless? Or are you guys checking for data corruption?

 

Sent from my Pixel XL using Tapatalk

 

 

You will not be able to boot anymore if this occurs to your machine.

 

It's a "you can't miss it" situation :)

Share this post


Link to post
Share on other sites
Advertisement

According to wmchris post here

either the clover option, or the kext. no need for both.

There is no need to have both. Also I didn't found the kext to be attached at the repo of this tutorial, so I skipped it and so far my machine work with intel speed shift enabled via clover without corrupting my file system or data.
Maybe the corruptions only occurs when you use both at the same time? Don't really know.

Share this post


Link to post
Share on other sites
Thanks everybody for reporting about (possible) NVMe data corruption. 

 

i list my "setup" here if it helps. i have no problems until now:

 

As i closely followed the instructions of this thread i think

- i don't have HWPEnabler.kext installed (i cant find it in system EFI)

- My config.plist says HWPEnabled = true

- i did pmset -a hibernatemode 0

 

sleep and wake up is fine

 

do you guys keep a clone (clonezilla?) of your system for the case of data corruption? 

i also have a windows10 partition. will it also be affected?

 

thanks!

 

EDIT:

 

My SSD: THNSN5512GPUK NVMe TOSHIBA 512GB

Share this post


Link to post
Share on other sites

Hi, is anyone working on the SD card Reader? I'm a photographer, it would be really useful for me.

 

At This point (and probably ever) there is no known way to make the SD card reader working.

 

 

According to wmchris post here

There is no need to have both. Also I didn't found the kext to be attached at the repo of this tutorial, so I skipped it and so far my machine work with intel speed shift enabled via clover without corrupting my file system or data.

Maybe the corruptions only occurs when you use both at the same time? Don't really know.

 

Thanks for giving out your setup.

 

To clarify, the reason for using both is that you would be able to alternate your HWP configuration (Power Saver/Maximum Performance).

 

From my information in addition with:

 

Thanks everybody for reporting about (possible) NVMe data corruption. 
 
i list my "setup" here if it helps. i have no problems until now:
 
As i closely followed the instructions of this thread i think
- i don't have HWPEnabler.kext installed (i cant find it in system EFI)
- My config.plist says HWPEnabled = true
- i did pmset -a hibernatemode 0
 
sleep and wake up is fine
 
do you guys keep a clone (clonezilla?) of your system for the case of data corruption? 
i also have a windows10 partition. will it also be affected?
 
thanks!

 

 

In mind, my theory (as long as my system is not corrupted) is correct:

1. pmset hibernatemode 0

2. HWPEnabler (by only kext) causes corruption. (Would like more experience except only mine to confirm this.)

3. If you still want to have HWP, then you need to enable it through Clover (bootloader(before kernel loads)).

4. And if you enable it through Clover, you can as well enable the KEXT (as long as my system doesn't corrupt anytime soon, then I would have to eat my words).

Share this post


Link to post
Share on other sites

Hi, is anyone working on the SD card Reader? I'm a photographer, it would be really useful for me.

You can only use sd card reader via usb 3.1 Type C hub like this.

 

At This point (and probably ever) there is no known way to make the SD card reader working.

 

 

 

Thanks for giving out your setup.

 

To clarify, the reason for using both is that you would be able to alternate your HWP configuration (Power Saver/Maximum Performance).

 

From my information in addition with:

 

In mind, my theory (as long as my system is not corrupted) is correct:

1. pmset hibernatemode 0

2. HWPEnabler (by only kext) causes corruption. (Would like more experience except only mine to confirm this.)

3. If you still want to have HWP, then you need to enable it through Clover (bootloader(before kernel loads)).

4. And if you enable it through Clover, you can as well enable the KEXT (as long as my system doesn't corrupt anytime soon, then I would have to eat my words).

Is possible to be related to type/manufacturer of the NVMe drive? In your signature I see that you have Toshiba SSD, I have Samsung PM961 (Polaris) 512 NVMe Drive and so far nothing happen to my system. I will backup my system today, install the kext and then if something happen I will share it here.

Share this post


Link to post
Share on other sites

I have THNSN5512GPUK NVMe TOSHIBA 512GB too... ¿Maybe it's a problem with this nvme?

 

Another question... ¿it's possible to install into a external drive via usb 3 instead internal nvme?

Share this post


Link to post
Share on other sites

I have THNSN5512GPUK NVMe TOSHIBA 512GB too... ¿Maybe it's a problem with this nvme?

 

Another question... ¿it's possible to install into a external drive via usb 3 instead internal nvme?

ssd works and yes you can install on external drive.

Share this post


Link to post
Share on other sites

Hi guys, I thought I'd chime in here as I'm trying to get my dell e5470 latitude working with sierra and have run into the same issues with HWP, SSDTprgen and the latest MacBook Pro smbios. I have an intel 6820hq cpu and MacBook Pro 13,2 is the only smbios that matches my CPU so naturally I'd like to get that working. I also get a KP with macbook 9,1 and many other smbios definitions. Like others I get a KP when booting with an ssdt generated by SSDTprgen using MacBook 13,2 smbios. I switched to HWPEnabler kext which seemed to work well at first but I got data corruption that reset my user account after a couple boots. This with was a fully patched DSDT/SSDT and hibernate mode off. I have a Samsung 850 pro ssd so the problem is not NVMe related.

 

Questions:

- is HWP retained after sleep if only using HWPEnable=true in clover (no kext). I could live without power profiles if the setting is definitely retained. How would I check this in AppleIntelInfo.kext?

- what is the exact cause of the KP when using a generated SSDT? Is it an smbios serial number problem?

Share this post


Link to post
Share on other sites

ssd works and yes you can install on external drive.

 

I know that the ssd works, but maybe one nvme has more chances of corruption than others... We need to limit the problem from the base.

Share this post


Link to post
Share on other sites

I know that the ssd works, but maybe one nvme has more chances of corruption than others... We need to limit the problem from the base

 

think i said before i'm using the toshiba and never had one corruption so far. So i doubt it has something to do with the SSD itself.

 

Hi guys, I thought I'd chime in here as I'm trying to get my dell e5470 latitude working with sierra and have run into the same issues with HWP, SSDTprgen and the latest MacBook Pro smbios. I have an intel 6820hq cpu and MacBook Pro 13,2 is the only smbios that matches my CPU so naturally I'd like to get that working. I also get a KP with macbook 9,1 and many other smbios definitions. Like others I get a KP when booting with an ssdt generated by SSDTprgen using MacBook 13,2 smbios. I switched to HWPEnabler kext which seemed to work well at first but I got data corruption that reset my user account after a couple boots. This with was a fully patched DSDT/SSDT and hibernate mode off. I have a Samsung 850 pro ssd so the problem is not NVMe related.

 

Questions:

- is HWP retained after sleep if only using HWPEnable=true in clover (no kext). I could live without power profiles if the setting is definitely retained. How would I check this in AppleIntelInfo.kext?

- what is the exact cause of the KP when using a generated SSDT? Is it an smbios serial number problem?

 

i used the HWP kext for months in the past with ElCap and had no corruption at all. Additionally i dont think that this simple command in the kext is able to make the SSD corrupt. If you want to use the kext see gymnaes 10.11 tutorial for the 9550. He has published a script for reloading HWP after sleep. I personally suggest using the clover flag -> much easier and from the same developer.

 

they're are two different KP. 1. if you use a different SMBIOS you should always be sure to set it correctly and 2. if you use a skylake smbios (which provides cpu informations) you should not provide additional CPU informations as ssdt

Share this post


Link to post
Share on other sites

think i said before i'm using the toshiba and never had one corruption so far. So i doubt it has something to do with the SSD itself.

 

 

i used the HWP kext for months in the past with ElCap and had no corruption at all. Additionally i dont think that this simple command in the kext is able to make the SSD corrupt. If you want to use the kext see gymnaes 10.11 tutorial for the 9550. He has published a script for reloading HWP after sleep. I personally suggest using the clover flag -> much easier and from the same developer.

When you used the HWP kext for months in ElCap, did you also have the Clover HWPEnabler = true? I believe it was a release in november of Clover that got the HWPEnabled feature introduced.

Share this post


Link to post
Share on other sites

When you used the HWP kext for months in ElCap, did you also have the Clover HWPEnabler = true? I believe it was a release in november of Clover that got the HWPEnabled feature introduced.

 

This option in Clover was added by me as well. And it makes same basic thing as my kext. So if you have one of them, or both - there is zero difference. But kext can additionally specify performance profile - if you want to set something different from default one.

Share this post


Link to post
Share on other sites

This option in Clover was added by me as well. And it makes same basic thing as my kext. So if you have one of them, or both - there is zero difference. But kext can additionally specify performance profile - if you want to set something different from default one.

 

Hello Goodwin_c!

Nice to see you here as well, and thanks for your work for the community!

 

Do you have any input to my theory below, that it has to be enabled before kernel loads to avoid risk of corruption?

 

Sorry to hear that @mikolatero.

 

We really need to find a permanent fix for these NVMe corruptions...
 

I have had the same experience, although this latest install has been running for 2 weeks without a problem.

 

sudo pmset -a hibernatemode 0 is a must.

Previous guides has been saying that it can be set to 3 (darkhandz), but I've had corruptions with that setting.

 

I initially "blamed" goodwin_c's HWPEnabler.kext, which I am certain has something to do with it, but on this installation I have both HWPEnabled = true in EFI/CLOVER/config.plist as well as the HWPEnabler.kext in L/E.

 

My thoughts are that we can't be enabling HWP as late as KEXT loads, it needs to be before the kernel loads, i.e. in clover bootloader.

 

To sum up my experience:

 

Corruption 1:

No change to pmset hibernatemode

HWPEnabler.kext in L/E

 

Corruption 2:

pmset hibernatemode 3

HWPEnabler.kext in L/E

 

Corruption 3:

pmset hibernatemode 0

HWPEnabler.kext in L/E

 

Current (2 weeks running setup without corruption (yet?) ):

pmset hibernatemode 0

HWPEnabler.kext in L/E

HWPEnabled = true in config.plist

 

What was your setup regarding HWPEnabler?

The more information we have, the more likely we can find a solution.

Share this post


Link to post
Share on other sites

Hello Goodwin_c!

Nice to see you here as well, and thanks for your work for the community!

 

Do you have any input to my theory below, that it has to be enabled before kernel loads to avoid risk of corruption?

 

No, it can't affect anything - after enabling HWP - normal kernel power management will stop woking. But stop working means - that if kernel will try to change frequency directly though Speed Step - then CPU will just ignore this request. No errors, no segfaults, no side effects. Just CPU will be doing own job and ignoring all Speed Step requests from OS.

Share this post


Link to post
Share on other sites

No, it can't affect anything - after enabling HWP - normal kernel power management will stop woking. But stop working means - that if kernel will try to change frequency directly though Speed Step - then CPU will just ignore this request. No errors, no segfaults, no side effects. Just CPU will be doing own job and ignoring all Speed Step requests from OS.

Interesting!

 

Do you have any input regarding NVMe corruption if we forget HWP for a moment?

Share this post


Link to post
Share on other sites

I'm using HWP starting from time when i created this kext. Dual boot, sometimes using Win10 (not very often), mostly MacOS. Always latest betas, a lot of reboots (development of system things needs a lot of them). A lot of freezes while experimenting with other things - this means a lot of unconditional reboots using 5-second-pressed power button. And still my data partition is ok, no corruption. And yes - i have one of highest configurations with 512Gb Toshiba SSD, 4K and i7. So far so good. So from my example you can see that there is no relation with HWP ;)

Share this post


Link to post
Share on other sites

What is a good replacement for the Killer 1535 Wi-Fi adapter?

 

hey, i had the same question here in this thread. see answer of wmchris. i'm also looking for a replacement. in the meantime i use this: "D-Link DWA-131 - Revision E" external USB-Wifi. D-Link provides official 10.12 drivers which work very well.                          

Share this post


Link to post
Share on other sites

Hi wmchris,

 

I just want to inform you that no devices work when plugged to TB3 port even after your latest config.plist, kexts and patched ACPI updates.

Share this post


Link to post
Share on other sites

Interesting note: when changing SMBIOS (both in Clover and kext) to MBP13,3, onboard HDMI and HDMI via the USB-C adapter stop working entirely.

 

I can leave the kext alone (still MBP13,3) but change the Clover config back to MB9,1 and both ports start working again.

Share this post


Link to post
Share on other sites

Hi wmchris,

 

I just want to inform you that no devices work when plugged to TB3 port even after your latest config.plist, kexts and patched ACPI updates.

these are not intended as final fixes. sys_cl told me TB3 would work by manually generating the SSDT/DSDT files with the correct refs.txt file in hand while deassembling. So maybe someone wants to give it a try. Tutorial is available in the ElCapitan Guide for the XPS15 from Gymnae.

Interesting!

 

Do you have any input regarding NVMe corruption if we forget HWP for a moment?

it seems like the corruption occurs because of SSDT/DSDT differences on each device. Seems like on some setups its entering sleep state before writing is completed. Other setups are immune to this. possible solutions would be to modify the SSDT/DSDT to give it a lil bit more time or to force a flush on sleep/deep-sleep. so it has nothing to do with HWP.

 

 

regarding the hynix devices: it seems like it's not really the device itself. i already gave a possible patch to one of my testers, i really hope i get a positive feedback :-)

UPDATE: it works! HYNIX SSDs ARE NOW SUPPORTED! Tutorial is updated

http://www.insanelymac.com/forum/topic/319929-pikeralphas-nvme-patch-with-hynix-m2-ssds/?do=findComment&comment=2354906

Share this post


Link to post
Share on other sites

these are not intended as final fixes. sys_cl told me TB3 would work by manually generating the SSDT/DSDT files with the correct refs.txt file in hand while deassembling. So maybe someone wants to give it a try. Tutorial is available in the ElCapitan Guide for the XPS15 from Gymnae.

 

 

The only tutorial I found online is at github by Gymnae and he mentions that tb3 is solved in 10.1 2, is there a link to his guide. I am willing to try. 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

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

Create an account

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

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By glasgood
      GLASGOOD'S
       
      MOJAVE HACKINTOSH GUIDE 
       

       
       
       
      **FOR**  GIGABYTE Z390 AORUS PRO
       
       
       
       
      CREDITS & THANKS
       
      @MaLd0n
      His help with EFI configuration and DSDT
       
      CLOVER  TEAM
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, rehabman, Download-Fritz, Zenit432, cecekpawon Et al
       
      APPLEALC
      Acidanthera, vit9696
       
      VOODOOHDA
      autumnrain, slice2009, zenith432
       
      ESP PRO MOUNTER
      @Micky1979 
       
      HACKINTOOL
      @headkaze
       
      CLOVER CONFIGURATOR
      Mackie100
       
      THEME ENGINE
      Alex Zielenski
       
      INSANELYMAC
      OLARILA
       
      Hackintool Tutorial
      daliansky
       
      Hackintosh Vanilla Desktop Guide
      /r/Hackintosh - corpnewt
       
       
      MONITORCONTROL
      JoniVR & theOneyouseek
       
       
       
      ------------------------------------------------------------------------------------------------------------------------------------------------------------
       
      UPDATES
       
       
      ------------------------------------------------------------------------------------------------------------------------------------------------------------
       
       
      PART LIST
       
      • Intel I7 8700 
      • Gigabyte Z390 AORUS PRO
      • Gigabyte AORUS RADEON RX 580 8GB ( connected to monitor with DisplayPort )
       
      • Corsair Vengeance LPX 16GB ( 2 x 8GB ) 2666MHz – CMK16GX4M2A2666C16  In this build, both memory modules are installed in memory slots DDR4_A1  and DDR4_B1 
       
      • Corsair RM650x 80 Plus Gold Power Supply Unit
      • Corsair H100i V2 AIO Hydro/Water RGB LED CPU Cooler
      • Samsung EVO 500GB SSD (2.5) macOS Mojave
      • Samsung EVO 250 GB SSD (2.5) Windows 10 Pro
      • NZXT H500 Mid Tower ATX Case
       
      • RECOMMENDED WIFI CARD → ABWB 802.11AC WI-FI With Bluetooth 4.0 PCI-Express (PCI-E) BCM943602CS  
      OR
      • WIFI and Bluetooth with BCM94331CD with PCI-e adapter (but will require AirportBrcmFixup.kext for AirDrop.. )
       
      ** Avoid Samsung EVO 970 PLUS as Hackintosh has problem with that device **
       
       
      WORKING
       
      • Sound 
      • HDMI Port on AMD RX580 / 590 ( Ensure you disable BIOS CSM if using HDMI on RX580 / RX590 )
      • HDMI Port on Aorus Z390 Motherboard ( Ensure you have correct BIOS settings as per this guide for Intel only)
      • Ethernet Port
      • WiFi
      • SSD Trim
      • USB 3.0 & 2.0 
      • AirDrop
      • iCloud
      • Hardware Acceleration
      • iMessages
      • Facetime
      • Handoff
      • Continuity
       

       

       
       
       

       
       
       
       
       
      PREAMBLE - BEFORE YOU START 
       
      Here detailed, is all the  steps towards building a successful and stable Aorus Pro Z390 Hackintosh, if you are a first time Hackintosher, this guide will have you quickly up and running with the Aorus Pro Z390 Hackintosh. To rule out any problems from the go,
      only have the disc that you plan to install macOS Mojave connected to the Aorus Pro, disconnect any other Windows / Linux or data drives, external drives from your Aorus Pro. Windows / Linux and data drives can be connected after successful installation of macOS Mojave
      If you have more than 16 GB of memory, then install macOS Mojave with just 16GB, you can later add any additional memory. Install memory modules in slots DDR4_A1  and DDR4_B1. This build has the Wi-Fi combo PCI-e card installed in slot PCIEX1_3
      with its 9 pin USB cable attached to motherboard header F_USB2. 
       
      If using the Corsair H100i v2 AIO cooler with USB cable connected to motherboard header F_USB1, you will need to enable hot-patch ( explained in guide ) in config.plist for working sleep, wake from sleep will only work by pressing Power Button.
      However, If not using the Corsair H100i v2  USB cable, then you have wake from sleep using Keyboard / Mouse or Power Button.
      The Corsair USB cable is only required if using Corsair Link software in Windows for custom Fan or LED settings.
       
      Install macOS Mojave on its own physical drive, so do not try and install macOS Mojave onto a free partition on a disc that contains Windows.
      Remove any Thunderbolt cards, Thunderbolt card can be reinserted after installation.  Double check your BIOS settings are the same as this guide. 
       
      Following are unsupported / problematic
       
      • Intel Optane ( if you have this, remove it before installation of macOS Mojave )
       
      • Samsung EVO Plus drives ( firmware problem with macOS )
       
      • XFX Radeon RX 580
       
      • NVIDIA GTX / RTX not supported in macOS Mojave
       
      • Fenvi T919 Wireless Card, it seems Bluetooth is not working out of box for some users ( Maybe the USB port attached to Fenvi bluetooth is wrongly configured, or the SSDT-UIAC.aml port connector was not configured as Internal, or maybe some other reason )
         Save yourself a headache --->  RECOMMENDED WIFI CARD WORKING OUT OF BOX (OOB)  is ---> ABWB 802.11AC WI-FI With Bluetooth 4.0 PCI-Express (PCI-E) BCM943602CS 
       
       
       
      Q - WILL THIS GUIDE WORK WITH MY NON AORUS Z390 PRO MOTHERBOARD ?
      A - Possibly may work with other Z390 chipset motherboards. See very bottom of page for PRE & POST - INSTALL AORUS X 390 EFI's ( will require USB SSDT fix  )
       
      Q - I notice you have the Aorus Pro Z390 version, will this guide work with Aorus Pro Z390 WiFi version ?
      A - Yes, but onboard Intel / Intel CNVi WIFII /Bluetooth will not work with macOS and you will have to disable HS14 for Bluetooth to function properly on BCM943602CS or BCM94331CD WiFi/Bluetooth Combo cards ( more info at bottom of guide) .
       
       
       
       
       
       
      PART 1 - DOWNLOAD 
       
       
      Download the following:
       
      • CLOVER
       
      • PRE-INSTALL Aorus Pro Z390 EFI - RX580.zip
       
      •  POST-INSTALL Aorus Pro Z390 EFI - RX580.zip
       
       
      //OPENCORE EXPERIMENTAL EFI FOR RX580==> EFI.zip
       
       
       
       
       
       
      // INTEL UHD 630 EFI  Aorus Pro Z390 EFI's below. For those who do not have a Graphics Card Installed in PCIe Slot, requires Initial Display Output BIOS setting to be changed to IGFX  spoiler below!
       
      •  PRE-INSTALL Aorus Pro Z390 EFI - Intel UHD630.zip
       
      •  POST-INSTALL Aorus Pro Z390 EFI - Intel UHD630.zip
       
       
       
       
       
       
      • ESP MOUNTER PRO v1.9
       
      • macOS MOJAVE 
       
      • CLOVER CONFIGURATOR
       
      • EmuVariableUefi-64.efi  ( Used only to initialise iMessages. It then must be removed from Clover drivers64UEFI folder as will cause intermittent memory allocation errors on boot, explained in guide)
       
       
      OPTIONAL DOWNLOADS
       
      • Native Display Brightness with MonitorControl
       
      • VoodooHDA.kext.zip 

      • ThemeEngine 
       
      • Assets.car 
       
       
      // Not really needed but IF no sound on Wake from Sleep then use SSDT-ALC1220 and CodecCommander
      • SSDT-ALC1220.aml  ( Resolves Audio Sound on Wake, place in Clover / ACPI / Patched )
       
      • CodecCommander.kext.zip ( Resolves Audio Sound on Wake, place in Clover / Kexts / Other )
       
       
       
       
      PART 2 - BIOS SETTINGS (version F9 )
       
       
      Here is a list of the BIOS settings that I have used ( Screenshots in spoiler below )
       
      • Enter BIOS → Press F12 → Enter Setup
      • Save & Exit → Load Optimized Defaults
       
      • BIOS → Windows 8/10 Features → Other OS
      • BIOS → CSM Support → Enabled
       
      • Peripherals → Initial Display Output → PCIe 1 Slot
      • Peripherals → Trusted Computing → Security Device Support →  Disable
      • Peripherals → Intel(R)Bios Guard → Intel BIOS Guard Support →  Disable
      • Peripherals → USB Configuration → Legacy USB Support →  Enabled
      • Peripherals → USB Configuration → XHCI Hand-off →  Enabled
      • Peripherals → Network Stack Configuration → Network Stack →  Disabled
      • Peripherals → SATA And RST Configuration → SATA Mode Selection →  AHCI
       
      • Chipset → Vt-d → Enabled
      • Chipset → Internal Graphics → Enabled
      • Chipset → DVMT Pre-Allocated → 256M
      • Chipset → DVMT Total Gfx Mem → MAX 
      • Chipset → Audio Controller → Enabled
      • Chipset → Above 4G Decoding → Disabled 
       
      • Power → Platform Power Management → Disabled ( Change to enabled after macOS is installed )
      • Power → ErP → Disabled  ( Can be enabled if you have RGB lighting that you want to power off when shutting down Hackintosh. Thanks @AudioGod for flagging this up)
      • Power → RC6 (Render Standby) → Disabled
       
      // IF USING  CORSAIR H100i V2 AIO CPU WATER COOLER 
      • MIT → Smart Fan 5 Settings → CPU Fan Control mode → PWM 
       
      • Save & Exit → Save & Exit Setup
       
      SCREEN DUMP SPOILERS
       
       
       
       
       
      PART 3 – CREATE A MOJAVE USB FLASH INSTALLER
       
      Prepare USB Installer for Mojave ( Video below )
       
      • Insert USB drive
      • Launch /Applications/Utilities/Disk Utility
      • Disk Utility → View → Show All Devices
      • On Left-hand panel → External →(Identify your USB device in left hand panel)
      • Click and highlight your USB device in the left-hand panel.
      • Click erase button.
      • Name: USB
      • Format: Mac OS Extended (Journaled )
      • Scheme: GUID Partition Map
      • Click Erase button.
       
      • Place the downloaded MacOS Mojave app into Applications folder.
      • Open Terminal copy and paste:
       
      sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --nointeraction && say Mojave Drive Created  • Enter
       
       
       
       
       
       
       
       
       
       
       
      PART 4 – INSTALL CLOVER ON THE MOJAVE USB INSTALLER 
       
      Make Mojave USB flash drive installer bootable.( Video below )
       
      • Launch Clover application, double click.
      • Click Continue → Continue → Continue 
      • Click Change Install Location button.
      • Click Install macOSMojave USB installer → Continue
      • Click Customise button
      • Choose:
      Clover for UEFI booting only Install Clover in the ESP Themes UEFI Drivers • Click Install button
      • Installation Complete!
       
      Video:
       
       
       
       
       
       
      PART 5 – CUSTOMIZE MOJAVE USB INSTALLER FOR AORUS Z390 PRO
       
      Replace Clover EFI folder with PRE-INSTALL Aorus Pro Z390 EFI - RX580.zip  OR  if NO graphics card installed in PCIe slot, then use PRE-INSTALL Aorus Pro Z390 EFI - Intel UHD630.zip( Video below ) 
       
      • Install ESP Mounter Pro v1.9
      • Using ESP Mounter Pro, Mount ESP on disk2s1 ( Your disk name may be different )
       

       

       
       
       
      • Open mounted EFI partition found on desktop
      • Copy all the contents from Aorus 390 Pro EFI folder
      • Replace USB EFI folder with all the contents inside the Aorus 390 Pro EFI folder.
       
       

       
       
       
       
       
       
       
      PART 6 – INSTALL MAC OS MOJAVE ON INTERNAL DRIVE
       
      INSTALL NOTE
       
      ENSURE BIOS: Above 4G Decoding is set to Disabled 
      if Above 4G decoding is set to enabled then macOS Mojave install will freeze at 2 mins remaining and will not shut down properly!!!!
       
      Please be patient during install, so when install gets to 2 or 3 mins remaining then it may take extra time. Be ready to boot from UEFI USB installer by pressing F12 when install initiates restarts. 

      • INSERT USB INSTALLER INTO THE USB 2.0 PORT  
       
       
       Here is a walkthrough of the full process using the macOS Mojave USB Installer on the Aorus Z390 Pro. 
       
       
       
       
      • Power on PC and press F12• Choose bootable USB drive from boot menu.
       
       
       
      • Install macOS Mojave to internal solid state or hard drive.
       
       
       
      When system returns to the Clover boot menu choose:
       
      • Boot macOS Install from Macintosh
       
       
       
      At next restart, press F12 and boot from external UEFI USB device and choose:
       
      • Boot macOS Install from Macintosh
       
       
       
      Proceed with macOS Mojave install
       
       
      macOS Mojave is now installed, but it can only boot at this moment thanks to FakeSMC and Clover on the Mojave USB flash drive installer.
       

       
       
       
       
       
       
      PART 7 – MAKE AORUS Z390 PRO INTERNAL DRIVE BOOTABLE
       
      Make internal drive bootable ( Video below )
       
      So far, the Aorus Pro can only boot the internal system drive with the aid of the Mojave USB Installer.
      To boot from the internal system drive without the installer: 
       
      Download and install Clover with RC Scripts on target volume.  
      If your Aorus Pro Z390 has AMD RX 580 then copy the EFI folder from inside POST-INSTALL Aorus Pro Z390 EFI - RX580.zip  folder and paste it inside the the System Drive EFI partition.          OR
      If your Aorus Pro Z390 has no graphics card installed in PCIe slot, then copy the EFI folder from inside POST-INSTALL Aorus Pro Z390 EFI - Intel UHD630.zip  folder and paste it inside the the System Drive EFI partition.   
       

       
       
       
      • Remove USB Mojave installer and shut down and restart.
       
      Aorus Hackintosh should now be able to boot to macOS Mojave, Done, well almost ! 
       
       
       
       
       
      PART 8 – ENABLE IMESSAGES & FACETIME 
       
       
      // UPDATE 21st MAY 2019
       
      Possibly Clover Configurator now automatically populates correct values for working iMessages when you select an SMBIOS.  
       

       
      After selecting SMBIOS, example iMac19,1 for Aorus Pro with RX580 ( image above ) then go to Apple and ensure you have the "serial number is not valid " message. Done!
       
      If you still have problems connecting to iMessage, test and ensure that AirDrop is working, then follow instructions inside spoiler. 

       
       
      • Mount internal drive EFI/ESP partition
      • Go to folder CLOVER → drivers64UEFI 
      • Place both EMUVariableUefi-64.efi inside → drivers64UEFI
       
       
      Using Clover Configurator, add the following argument to config.plist using Clover Configurator.
       
      • Slide = 0
       

       
       
      Shutdown and then press power on button on PC.
       
      • You should now be able to Log into iCloud, iMessages and FaceTime
       
       
       
      • NOW delete EMUVariableUefi-64.efi from CLOVER → drivers64UEFI Folder 
      • Shutdown and restart Aorus Pro hackintosh. iMessages etc is now operational without EMUVariableUefi-64.efi ( EMUVariableUefi-64.efi only needed to initialise iMessages )
       
       
      // UPDATE 22nd May 2019 
       
      • It seems that there are no "Couldn't allocate runtime area"  errors when continuing to use EMUVariableUefi-64.efi since updating to macOS Mojave 10.14.5 and using Clover version r4920. 
      • It is important to delete EMUVariableUefi-64.efi, this will avoid very intermittent boot errors such as: “Couldn’t allocate runtime area”  post errors.
       
       
       
       
      PART 9 – ENABLE TRIM for Solid State Flash Drives
       
      Open Terminal and enter the following command:
      sudo trimforce enable  
       
       
       
       
      DEFAULT SSDT –  USB PORTS FIX CONFIGURATION WITH FRONT USB-C - SSDT USBPorts.kext ALREADY INSIDE AORUS Z390 EFI FOLDER  – Provided by @AudioGod  
       
       

       

       
      If you have USBC on Computer Chassis / Case, then SS01 and SS02 is mapped to that USB C port 
       

       
       
       
       
       
       
      ------------    GUIDE FINISHED YOU SHOULD NOW HAVE WORKING AORUS Z390 PRO HACKINTOSH  WITH SSDT USB FIX   ------------
       
       
       
      OPTIONAL: Set Wi-Fi Country Code
       
       
       
       
       
       
      OPTIONAL: System Information - PCI
       
       
       
       
       
       
       
      External USB Storage:  Fix "disk did not eject properly" message upon wake from sleep
       
       
       
       
       
       
       
      OPTIONAL:  Native Display Brightness - with MonitorControl

       
       
       
       
       
       
      OPTIONAL:  Dual Boot macOS Mojave & Windows 10 
       
       
       
       
       
       
       
       
      OPTIONAL:  Replace the default "About This Mac" Apple Logo with RED AORUS APPLE
       
       

       
       
       
       
      OPTIONAL - ALTERNATIVE SSDT 1 –  SSDT Ports configuration below - replace SSDT inside Clover /ACPI/PATCHED folder 
       
       
       
       
       

      OPTIONAL - ALTERNATIVE SSDT 2 -  SSDT Ports configuration below - replace SSDT inside Clover /ACPI/PATCHED folder 
       
       
       
       
       

      OPTIONAL - ALTERNATIVE SSDT 3 – Create your own SSDT
       
       
       
       
       
      FRAMEBUFFER PATCHING  – For working Intel UHD 630 Graphics, working HDMI Port, working HDMI Audio on Aorus Z390 Pro
       


       
       
       
       
       
       
      FINAL CUT PRO  – Configuration for AMD RX5xx 
       
       
       
       
      AORUS PRO Z390 WIFI version with Intel CNVi  – Disable Bluetooth on HS14
       
      Resolve bluetooth issue  reported by @eSaF 
       
       
       
       
       
       
      CLOVER  – Updating / Upgrade Clover boot loader 
       
       
       
       
       
       
      SLEEP  – Sleep and Automatic Sleep

       
       
       
       
       
       
       
       
      SLEEP  – Resolving Instant Wake ( Corsair H100i v2 AIO )
       
       
       
       
       
       
       
       
      WIFI  – Clover Hotpatch PXSX to ARPT
       
       
       
       
       
       
       
       
       
       
      RECOMMENDED READING  – Excellent Hackintosh Vanilla guide created by CorpNewt with in depth tutorial on Clover.  
       
      https://hackintosh.gitbook.io/-r-hackintosh-vanilla-desktop-guide/config.plist-per-hardware/coffee-lake
       
       
       
       
       
       
       
       
       
      AORUS Z390 MOTHERBOARD X  – EFI WITH NO USB SSDT, WITH PORTS LIMIT PATCH, WITH SSDT-GPRW SLEEP / WAKE FIX
       
      Q - I notice you have the Aorus Pro Z390 version, will this guide work with other Gigabyte Aorus Z390  motherboards ?
      A - Possibly, but it is not guaranteed that these EFI folders below may work. 
       
       
      PRE-INSTALL Aorus X Z390 EFI - RX580.zip
      POST-INSTALL Aorus X Z390 EFI - RX580.zip
       
      PRE-INSTALL Aorus X Z390 EFI - Intel UHD630.zip
      POST-INSTALL Aorus X Z390 EFI - Intel UHD630.zip
       
       
       
       
       
       
       
       
       
       
       
       

       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
      SSDT-UIAC.aml.zip
      SSDT-UIAC.dsl.zip
       
      CodecCommander.kext.zip
      SSDT-ALC1220.aml.zip
       
      POST-INSTALL Aorus Pro Z390 EFI - RX580 2.zip
    • By Technology & more
      Can Someone make a guide to install macOS Mojave on the Surface Pro 1?
    • By MardukPVP
      Hello guys,

      recently I have tried to install macOS mojave on my Mi Notebook pro (i5 - 8250u model) but have faced one big problem.
      My guide was from Razorkey (https://www.tonymacx86.com/threads/guide-xiaomi-mi-notebook-pro-high-sierra-10-13-6.242724/). As a newbie I have almost no experience in installing macOS on a PC / Laptop... so I hope you can help me .

      But first things first I configurated the BIOS settings on my Mi - Notebook Pro. Therein I just disabled secure boot (because there are quite few options to tick).

      After that I headed over to my secondary Windows - PC and installed a High Sierra virtual machine (thanks to this tutorial: https://techsviewer.com/install-macos-high-sierra-vmware-windows-pc/). At that point everything worked fine.

      Then I downloaded the Mojave patcher and downloaded the full 6GB macOS Installer, put it into applications and formatet my 16GB USB Stick into the journaled + GUID with the name USB meanwhile.
      Next I typed 
      sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/USB 
      into the terminal and at that point everything looked like it would work pretty fine. I downloaded Clover Config, mountet the EFI partition and pushed the EFI folder from this site: https://github.com/daliansky/XiaoMi-Pro to the EFI partition on my 16GB USB drive.

      In the folloing I restarted my Notebook, selected the MacOS installer and it bootet into the MacOS installer. By doing that I only noticed that the progress bar turned green at a certain time (attatchment). Even though everything bootet pretty fine, i formattet my only ssd (Samsung) into APFS + GUID and startet the installation.
      At the point of two minutes my notebook suddenly rebootet and it brang me into the same clover selection menue as before (with only one method [macOS Installation]). Unfortunately there was no further installation method.

      When I was trying to reboot the laptop into the installer i got a error [your computer restarted because of a problem...] and i would have to do everything again.


      I hope someone can help me fixing this problem  . Thanks in advance.




    • By BALDY_MAN
      I've just got my hack. to were I'm happy with it.
      its been a long road. and up to this point was always evolving. and from the software side. id Like to thank EVERYONE that as given there time help and support  in my Hackintosh adventure.
      the hardware side. as at times been a bit of a challenge (learning to bent stainless tubing) I got the powder coating done by a local company
      Please comment
                                                                            Best regards 
                                                                                             Baldy
       







    • By Theapc06
      Hi I Just Bought A Hp Elite 8300 I3 3200 Desktop Computer And I Was Wondering If The Intel HD Graphics Were Going To Be Supported When I iNSTALL Mojave Or High Sierra Thanks -ALEX
       
       
      PS: What Is The Better OS To Go For On This Desktop PC : MacOS High Sierra -10.13 Or MacOS Mojave -10.14
       
                                                   Thanks Again -Alex
       
×