Jump to content
wmchris

[GUIDE] Dell XPS 15 (9550) Mojave 10.14 / 10.15 Quick Installation

1,493 posts in this topic

Recommended Posts

FYI, unsigned kext messages are normal.  It's a hackintosh it's going to have non-official kexts loading.

 

 

I’m on 10.13.3 now. I still can get my brightness controls to work.
Even after rebuilding the kernel caches.

I’m getting some complains about invalid signatures what appears to say it was allowed.

I did the commands from the guide to flush the kernel cache.
Any ideas on how to fix?

 

 

EDIT: I have  no idea what i've done. After a few flushes, the brightness control is working  again. I tried to allow unsigned code again through that spctl command. And after the last flush it seems to have fixed it. I'm not really sure.

 

Are there any advantages in going to the new Clover, also the github repo seems to have been updated with a few new things, something about nvram and aptio v3..... should i move to those?

Share this post


Link to post
Share on other sites
Advertisement

Hi Folks, seeking your advice if you will?

 

System: 9550, i7, 16gb, 4k screen, Toshiba SSD.   Install as per the GitHub repo, switching the SSD to 4k sectors, and following up with a Win10 dual-boot for games, though most of my work will be in OSX.

 

Audio - I left it 'as is', everything is fine through speakers, but I get corruption when using headphones plugged into the laptop (as expected).   None of the other options seemed particularly enticing (would rather audio disruption than kernel panics), but thought 'never mind, I'll use Bluetooth headphones'.

 

Having acquired a serviceable pair, which work perfectly with my phone, I think evening paired them with the laptop.  However, the end result isn't great (wired with corrpution is better).   They regularly (between 2 and 5 mins) disconnect, and when connected, more often than not, the sound is garbled.  When is is playing properly, it sounds great.

 

Any tips on what I should change?  System stability is priority number one, but after that, bluetooth audio trumps speaker audio if it's a trade off.

 

Many thanks.

 

Gavin.

Share this post


Link to post
Share on other sites

Hmm, they're fine on my phone and, having checked, in Win10 on the same machine, so seems to be specific to the headphone/OSX combination.

Anything I should try? or SOL?  I can't pick up a £300 pair of headphones on the off-chance it'll work ;-)

Share this post


Link to post
Share on other sites

Solved my issue:  It seems that, when connecting to a 2.4Ghz Wifi connection in OSX (not in Windows 10), my audio gets corrupted.  As soon as I switched over to a 5Ghz connection, everything was absolutely fine, so, I guess something in the card/driver is conflicting with itself.

Share this post


Link to post
Share on other sites

its not a conflict... this is normal behaviour with some bt hardware...

wifi and bt are interfering with each other. both are using 2,4ghz for transmission. it depends on quality of your used devices (router, headphones,...) and their transmission settings if the interference will be a mild side effect or a absolute non working disaster.

Share this post


Link to post
Share on other sites

So, my post was deleted due to the forum's recent changes...

Anyway, here is what you need to enable VoodooI2C on our machine (Better touchpad and touchscreen)

More info about VoodooI2C here (thanks @alexandred for the great work)

Add these two entries to Clover's config.plist at `ACPI > DSDT > Patches`:

<dict>
	<key>Comment</key>
	<string>change GPI0 device _STA to XSTA</string>
	<key>Disabled</key>
	<false/>
	<key>Find</key>
	<data>X1NUQQCgCZNTQlJHAA==</data>
	<key>Replace</key>
	<data>WFNUQQCgCZNTQlJHAA==</data>
</dict>
<dict>
	<key>Comment</key>
	<string>change I2C devices _CRS to XCRS</string>
	<key>Disabled</key>
	<false/>
	<key>Find</key>
	<data>X0NSUwCgDg==</data>
	<key>Replace</key>
	<data>WENSUwCgDg==</data>
</dict>

Copy the SSDT-I2CX.aml and SSDT-XOSI.aml(thanks @goodwin_c) files inside the attached zip to `CLOVER > ACPI > patched`

Download the latest VoodooI2C.kext release (link) and copy both VoodooI2C.kext and VoodooI2CHID.kext files to Clover's kexts folder . The other files are not needed. (more info about them here)

Reboot and that's it.

Personally I think the performance of our's laptop touchpad is better using VoodooI2C.kext than with VoodooPS2Controller.kext. And the added gestures to the Touchscreen are a nice bonus.

P.S: Don't delete VoodooPS2Controller.kext, as it is still necessary for the keyboard to function and it is compatible with VoodooI2C.

P.S.S: Inside the attached zip I included a beta version of VoodooI2C.kext (10.13 only, based on this changes) that enable native gestures and settings for our touchpad (Just like Apple's Magic Trackpad). However this version is in current development and those willing to test should expect bugs. (Removed per author's request, if you want to know more about this version go here)

 

I2C.zip

Edited by hvolkoff
Changed attachment, removed VoodooI2C beta binary and added missing SSDT-XOSI.aml file

Share this post


Link to post
Share on other sites
15 hours ago, hvolkoff said:

So, my post was deleted due to the forum's recent changes...

Anyway, here is what you need to enable VoodooI2C on our machine (Better touchpad and touchscreen)

More info about VoodooI2C here (thanks @alexandred for the great work)

Add these two entries to Clover's config.plist at `ACPI > DSDT > Patches`:


<dict>
	<key>Comment</key>
	<string>change GPI0 device _STA to XSTA</string>
	<key>Disabled</key>
	<false/>
	<key>Find</key>
	<data>X1NUQQCgCZNTQlJHAA==</data>
	<key>Replace</key>
	<data>WFNUQQCgCZNTQlJHAA==</data>
</dict>
<dict>
	<key>Comment</key>
	<string>change I2C devices _CRS to XCRS</string>
	<key>Disabled</key>
	<false/>
	<key>Find</key>
	<data>X0NSUwCgDg==</data>
	<key>Replace</key>
	<data>WENSUwCgDg==</data>
</dict>

Copy the SSDT-I2CX.aml file inside the attached zip to `CLOVER > ACPI > patched`

Download the latest VoodooI2C.kext release (link) and copy both VoodooI2C.kext and VoodooI2CHID.kext files to Clover's kexts folder . The other files are not needed. (more info about them here)

Reboot and that's it.

Personally I think the performance of our's laptop touchpad is better using VoodooI2C.kext than with VoodooPS2Controller.kext. And the added gestures to the Touchscreen are a nice bonus.

P.S: Don't delete VoodooPS2Controller.kext, as it is still necessary for the keyboard to function and it is compatible with VoodooI2C.

P.S.S: Inside the attached zip I included a beta version of VoodooI2C.kext (10.13 only, based on this changes) that enable native gestures and settings for our touchpad (Just like Apple's Magic Trackpad). However this version is in current development and those willing to test should expect bugs. 

I2C.zip

Could you share your IOReg with VoodooI2C working?

Share this post


Link to post
Share on other sites
19 hours ago, hvolkoff said:

So, my post was deleted due to the forum's recent changes...

Anyway, here is what you need to enable VoodooI2C on our machine (Better touchpad and touchscreen)

More info about VoodooI2C here (thanks @alexandred for the great work)

Add these two entries to Clover's config.plist at `ACPI > DSDT > Patches`:


<dict>
	<key>Comment</key>
	<string>change GPI0 device _STA to XSTA</string>
	<key>Disabled</key>
	<false/>
	<key>Find</key>
	<data>X1NUQQCgCZNTQlJHAA==</data>
	<key>Replace</key>
	<data>WFNUQQCgCZNTQlJHAA==</data>
</dict>
<dict>
	<key>Comment</key>
	<string>change I2C devices _CRS to XCRS</string>
	<key>Disabled</key>
	<false/>
	<key>Find</key>
	<data>X0NSUwCgDg==</data>
	<key>Replace</key>
	<data>WENSUwCgDg==</data>
</dict>

Copy the SSDT-I2CX.aml file inside the attached zip to `CLOVER > ACPI > patched`

Download the latest VoodooI2C.kext release (link) and copy both VoodooI2C.kext and VoodooI2CHID.kext files to Clover's kexts folder . The other files are not needed. (more info about them here)

Reboot and that's it.

Personally I think the performance of our's laptop touchpad is better using VoodooI2C.kext than with VoodooPS2Controller.kext. And the added gestures to the Touchscreen are a nice bonus.

P.S: Don't delete VoodooPS2Controller.kext, as it is still necessary for the keyboard to function and it is compatible with VoodooI2C.

P.S.S: Inside the attached zip I included a beta version of VoodooI2C.kext (10.13 only, based on this changes) that enable native gestures and settings for our touchpad (Just like Apple's Magic Trackpad). However this version is in current development and those willing to test should expect bugs. 

I2C.zip

Very nice, thank you for this! Do you happen to know if the pinning for the 9560 is the same?

Share this post


Link to post
Share on other sites
4 hours ago, goodwin_c said:

Thanks. That is what i was thinking - on my machine it didn't catch TPD1 device. Even, i don't see TPD1 in IOReg. Will try to debug ACPI to find out what is going on.

same here, TPD* missing.

to be honest i'm a lil bit confused... i'm pretty sure the ELAN Touchscreen is connected with USB, not I2C...

Share this post


Link to post
Share on other sites
3 hours ago, wmchris said:

same here, TPD* missing.

to be honest i'm a lil bit confused... i'm pretty sure the ELAN Touchscreen is connected with USB, not I2C...

Try to replace your SSDT-XOSI with next code:

DefinitionBlock ("", "SSDT", 2, "hack", "XOSI", 0x00000000)
{
    External (_SB.TBFP, MethodObj)
    External (USTP, UnknownObj)
    Name (CNT1, Zero)
    Method (XOSI, 1, NotSerialized)
    {
        CNT1++
        IF (CNT1 == 0x1)
        {
          \_SB.TBFP (One)
          USTP = One
        }
        Local0 = Package (0x0A)
            {
                "Windows",
                "Windows 2001",
                "Windows 2001 SP2",
                "Windows 2006",
                "Windows 2006 SP1",
                "Windows 2006.1",
                "Windows 2009",
                "Windows 2012",
                "Windows 2013",
                "Windows 2015"
            }
        Return ((Ones != Match (Local0, MEQ, Arg0, MTR, Zero, Zero)))
    }
}

This will:

- permanently enable TB controller (USB-C works like a charm :) )

- should make VoodooI2C attaching to TPD acpi device

Share this post


Link to post
Share on other sites

works well. thank you.

btw usb-c worked well before ;-)

@hvolkoff
does the voodooi2c native branch kext also mess up with your left click (not tap)?
most physical clicks are not recognized anymore on my system, but drag and drop works ... but sometimes doesnt register the clickUP event. dunno if configured something wrong or this is just a bug

Edited by wmchris

Share this post


Link to post
Share on other sites
7 hours ago, lebish said:

Very nice, thank you for this! Do you happen to know if the pinning for the 9560 is the same?

Hi, I don't know cause I don't have a 9560 and also don't have access to one's DSDT. But it may work, considering that some of my config is derived from @KNNSpeed's files, and I made very few changes to make them compatible with 9550.

5 hours ago, wmchris said:

same here, TPD* missing.

to be honest i'm a lil bit confused... i'm pretty sure the ELAN Touchscreen is connected with USB, not I2C...

Well... I got say that I don't understand much of how that works as well, hahaha. But, from our device DSDT you can see that in the _SB.PCI0.I2C1 bus there are two devices declared:

Scope (_SB.PCI0.I2C1) {
        Device (TPD1) {
            Name (HID2, Zero)
            Name (SBFB, ResourceTemplate () {
                I2cSerialBusV2 (0x002C, ControllerInitiated, 0x00061A80,
                    AddressingMode7Bit, "\\_SB.PCI0.I2C1",
                    0x00, ResourceConsumer, , Exclusive,
                )
            })
			
            ...
        }

        Device (TPL1) {
            Name (HID2, Zero)
            Name (SBFB, ResourceTemplate () {
                I2cSerialBusV2 (0x004C, ControllerInitiated, 0x00061A80,
                    AddressingMode7Bit, "\\_SB.PCI0.I2C1",
                    0x00, ResourceConsumer, _Y29, Exclusive,
                )
            })
	
            ...
		}

    ...
}

TPD1 is the touchpad
TPL1 should be the touchscreen

However if you check IOReg with VoodooI2C enabled:

image.thumb.png.629a57ee91bc478c75c6cabed74f3fa4.png

You can see that under I2C1 there is only TPD1 (touchpad), and on the USB controller there are some I2C nodes for the Touchscreen. So, maybe, the TPL1 device is acting as some kind of bridge between the two interfaces or something. But that is just me guessing based on my currently limited knowledge of I2C.
 

1 hour ago, wmchris said:

works well. thank you.

btw usb-c worked well before ;-)

@hvolkoff
does the voodooi2c native branch kext also mess up with your left click (not tap)?
most physical clicks are not recognized anymore on my system, but drag and drop works ... but sometimes doesnt register the clickUP event. dunno if configured something wrong or this is just a bug

Yeah physical clicks are acting weird for me too on Native and I am experience some random crashes on startup.

Share this post


Link to post
Share on other sites
2 hours ago, goodwin_c said:

Try to replace your SSDT-XOSI with next code:


DefinitionBlock ("", "SSDT", 2, "hack", "XOSI", 0x00000000)
{
    External (_SB.TBFP, MethodObj)
    External (USTP, UnknownObj)
    Name (CNT1, Zero)
    Method (XOSI, 1, NotSerialized)
    {
        CNT1++
        IF (CNT1 == 0x1)
        {
          \_SB.TBFP (One)
          USTP = One
        }
        Local0 = Package (0x0A)
            {
                "Windows",
                "Windows 2001",
                "Windows 2001 SP2",
                "Windows 2006",
                "Windows 2006 SP1",
                "Windows 2006.1",
                "Windows 2009",
                "Windows 2012",
                "Windows 2013",
                "Windows 2015"
            }
        Return ((Ones != Match (Local0, MEQ, Arg0, MTR, Zero, Zero)))
    }
}

This will:

- permanently enable TB controller (USB-C works like a charm :) )

- should make VoodooI2C attaching to TPD acpi device

Damn, thanks man. I totally forgot about adding that to the post... I too did have to make changes in SSDT-XOSI, but I only had to add the newer "windows" identifiers to it. Do you mind explaining what the CNT1 bit is about?

Share this post


Link to post
Share on other sites
3 minutes ago, hvolkoff said:

Damn, thanks man. I totally forgot about adding that to the post... I too did have to make changes in SSDT-XOSI, but I only had to add the newer "windows" identifiers to it. Do you mind explaining what the CNT1 bit is about?

afaik its for triggering power to the TB device on bootup.

Edited by wmchris

Share this post


Link to post
Share on other sites
7 hours ago, wmchris said:

afaik its for triggering power to the TB device on bootup.

Yes, it is done to be sure that part inside of "if" will be triggered only once (on first call of XOSI function), as XOSI function is used few times in original DSDT.

Share this post


Link to post
Share on other sites

I have also installed the I2C Kexts but the Touchpad doesn't work for me with this Kext. Installed also the SSDT-XOSI and the Device TPD1 is also there according to IOReg. Did I something wrong or is this a Bug? The Keyboard works normal. With the ApplePS2SmartTouchPad.kext I have no problems with my Touchpad.

Share this post


Link to post
Share on other sites

My XPS 15 9550 will not boot after install.

I followed the GitHub guide, except I used [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] and Clover from tonymac. I have installed 10.13.2 onto APFS (SSD disk only)  and it boots via Clover on the USB, but will not boot on its own. No diagnostic, just a Dell blue screen comes up saying the disk won't boot.

My BIOS is 1.4.0.

Any suggestions on what to try?

Share this post


Link to post
Share on other sites
On 3/13/2018 at 10:22 PM, hitman478 said:

I have also installed the I2C Kexts but the Touchpad doesn't work for me with this Kext. Installed also the SSDT-XOSI and the Device TPD1 is also there according to IOReg. Did I something wrong or is this a Bug? The Keyboard works normal. With the ApplePS2SmartTouchPad.kext I have no problems with my Touchpad.

Same for me. Even though removing the I2C kexts it does not work. It may be due to the SSDT-XOSI or voodooPS2daemon?

I have only tried the SSDT-XOSI as @goodwin_c suggested, not using the previous one with enabling later windows as @hvolkoff stated.

I have tried both I2C 2.0.1 and the "10.13 beta" as included in zip file of original post by @hvolkoff .

The ControllerInterrupt first two hex are "10" looking at IOReg.

I've noticed that in some cases the mouse works just fine during the login screen, but shortly after logging in it stops moving, hard to do mouse clicks, essentially unusable except for scrolling. The touchscreen, however, works perfectly.

Share this post


Link to post
Share on other sites

Hey gang, did we ever get Thunderbolt working? Specifically I'm interested in the Elgato TB3 Dock and curious if anyone has had success TB3 yet.

Share this post


Link to post
Share on other sites
13 hours ago, pourhaus said:

My XPS 15 9550 will not boot after install.

I followed the GitHub guide, except I used ##### and Clover from tonymac. I have installed 10.13.2 onto APFS (SSD disk only)  and it boots via Clover on the USB, but will not boot on its own. No diagnostic, just a Dell blue screen comes up saying the disk won't boot.

My BIOS is 1.4.0.

Any suggestions on what to try?

OK, that was a quick post where I was hoping someone may have hit a similar problem.

Let me expand. As mentioned, I used U-n-i-B-e-a-s-t and Clover from t-m-86 to install _just_ the USB. That works from F12 boot menu, and is able to boot the High Sierra it installed from the SSD. I used the Clover, EFI and instructions from the GitHub repo to update/configure the High Sierra on the SSD itself (post-boot). Boot direct from the SSD does not work. I get _no_ text from the OS, it goes from BIOS boot menu to black screen for 5-10 seconds, then to Dell blue can't-boot screen.

Share this post


Link to post
Share on other sites

Just wanted to say thank you for providing the package and this tutorial for the XPS 15 9550, I found it very quick and easy to get up and running thanks to you! I ran in to 2 problems during the process which I thought I'd highlight as these were the only ones I encountered and in case anybody else is trying to do the same:

 

1) "does printf work??" - this was caused by the incorrect default "slide=0" value when using "OsxAptioFix3Drv-64.efi". Calculating the slide manually as per this tutorial fixed this for me.

 

2) "Unable to find driver for this platform" - this happened when I was using Pandora's Box to create my EFI boot USB. Manually erasing the USB to GUID structure, using the Clover installer provided in the Github package to create it and then manually installing the High Sierra installer on to the USB worked for me.

Quick question, has anybody upgraded their 10.13.3 install with the new "10.13.3 Supplemental Update" and if so, how did it go?

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 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. Had to change the tubing around 
                                                                            Best regards 
                                                                                             Baldy
       












    • 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. 
       
       
      AMD Vega card's  will work with this guide, but If you plan to use a Sapphire Pulse Vega 56 then please read @AudioGod ==>post  regarding the Sapphire Pulse 56.
       
       
       
      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 → Disabled
      • 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
       
       
      • MIT → Advanced Memory Settings  → Extreme Memory Profile (X.M.P) → 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
       
       
    • By ThatsMatt
      Salve, sono nuovo nel forum e mi serviva una mano nell'installazione dell' ultima versione di MacOs sul mio notebook HP Pavilion 15-ak112nl.
      Specifiche Tecniche: 
      CPU: Intel Core i7-6700HQ (2.60 / 3.50 GHz, 4 core, 6 MB CACHE L3). 
      Scheda Grafica: Intel HD Graphics 530 + NVIDIA GeForce GTX 950M 4 GB DDR3.
      Hard Disk: 1 TB SATA 5400 rpm.
      Ram: 8 GB DDR3L-1600.
      Audio: altoparlanti stereo Bang & Olufsen PLAY. 
      Rete: LAN 10/100, WLAN 802.11b/g/n, bluetooth 4.0 (Miracast).
      Grazie in Anticipo a chi mi risponderà
    • 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.




×