Jump to content
wmchris

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

1,493 posts in this topic

Recommended Posts

57 minutes ago, pourhaus said:

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.

as i said... you didnt install clover properly and/or forgot to configure the boot priority. both is explained in the tutorial.
also i will not give support for any tool by TM - see the FIRST text in the tutorial for the reason.

32 minutes ago, Rajveer86 said:

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?

works. :-)

Edited by wmchris

Share this post


Link to post
Share on other sites
Advertisement
On 2018/3/13 at 6:17 AM, goodwin_c said:

This will:

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

- should make VoodooI2C attaching to TPD acpi device

Hello goodwinc

Does it means it dont need macOS-IOElectrify.kext anymore to enable TypeC?

Share this post


Link to post
Share on other sites
9 hours ago, gujiangjiang said:

Hello goodwinc

Does it means it dont need macOS-IOElectrify.kext anymore to enable TypeC?

never required any of these and i used usb-c on a regular base. :-/

Share this post


Link to post
Share on other sites
never required any of these and i used usb-c on a regular base. :-/



SSDT-TYPEC.aml?
SSDT-TB.aml?
SSDT-XHC.aml?

May you share your acpi/parched to me to see what happened.

Thansk


从我的 iPhone 发送,使用 Tapatalk

Share this post


Link to post
Share on other sites

I test again my xps couldn't recognize typec in hotplug and i must plug it before power on.

I use SSDT-TB.aml SSDT-TYPEC.aml SSDT-TBON.aml SSDT-XHC.aml SSDT-USBX.aml.

 

I try to delete some of them but with no use.

 

How can fix TypeC hotplug.

Share this post


Link to post
Share on other sites

I test again my xps couldn't recognize typec in hotplug and i must plug it before power on.

I use SSDT-TB.aml SSDT-TYPEC.aml SSDT-TBON.aml SSDT-XHC.aml SSDT-USBX.aml.

 

I try to delete some of them but with no use.

 

How can fix TypeC hotplug.

 

Update:

And i get back to AppleSmartPS2 kext and delete voodooI2C because when i change to VoodooI2C it may reboot when wake up and come out some ERROR message when boot into macOS.

Share this post


Link to post
Share on other sites

Sorry to ask something that seems so obvious, however I'm looking to change my SMBIOS to MacbookPro13,3 and have read in this (and other) guides that I will need to change the fake ethernet to en0. The confusion arises from darkhandz's guide (https://github.com/darkhandz/XPS15-9550-High-Sierra#网卡顺序修正) where he doesn't have the fake ethernet installed and instead has the wifi as en0. Is this because this guide defaults to using an iMac setup whereas his defaults to MacbookPro13,3?

Share this post


Link to post
Share on other sites

Hello guys, 

This is a little bit out of topic but i had to ask. My dell decided not to give any signs of life at all. Pressing the power button does nothing and status LED is not lightning up also. It seems like its completelly dead. 

I tried removing ssd, ram modules and turning it on, but even then it doesnt give error codes (amber and white lights) on front LED. 

The only time it responds is if I hold CTRL + ESC and insert the power adapter. But according to the manuals something should be displayed on the screen but its not. 

The laptop is missing the battery and this happened when i pulled the cable out because it was stuck on the dell logo for a while and it didnt respond to the power button.

Any kind of help is appreciated. Thanks!

Share this post


Link to post
Share on other sites
50 minutes ago, th3_v0ice said:

Hello guys, 

This is a little bit out of topic but i had to ask. My dell decided not to give any signs of life at all. Pressing the power button does nothing and status LED is not lightning up also. It seems like its completelly dead. 

I tried removing ssd, ram modules and turning it on, but even then it doesnt give error codes (amber and white lights) on front LED. 

The only time it responds is if I hold CTRL + ESC and insert the power adapter. But according to the manuals something should be displayed on the screen but its not. 

The laptop is missing the battery and this happened when i pulled the cable out because it was stuck on the dell logo for a while and it didnt respond to the power button.

Any kind of help is appreciated. Thanks!

Actually, CTRL+ESC is starting Dell Bios Recovery 2. And it is tricky - it is starting only when it can find recovery file. If file is not found - it will just start and shutdown in few seconds, and even without showing anything on screen.

To start Bios Recovery properly, do next steps:

 - Download bios update file from Dell site (it will be .exe file)

- Rename this file to BIOS_IMG.rcv (yes, from exe to rcv. file name should have perfect match)

- Take some not-too-big USB flash drive, format it in FAT32 fs

- Copy BIOS_IMG.rcv to the root of flash drive

- Insert flash drive to left USB port on laptop (shouldn't be difference in which port, but from my personal experience left one is better :) )

- Start laptop with CTRL+ESC. If flash drive has activity led - it should blink at least few times. If machine is not physically damaged - it will run bios recovery with options to reset BIOS settings and re-flash BIOS image

Share this post


Link to post
Share on other sites
On 3/15/2018 at 1:06 PM, pourhaus said:

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.

I have now re-installed, following the entire guide here as closely as I can, using Pandora's Box and not U-n-i-B-e-a-s-t. I have also upgraded my firmware to 1.5.1 as I found a YouTube video where that was being used and worked.

I am still not able to boot directly from SSD (which is partitioned using APFS by the way), but can boot from the USB.

Any suggestions?

Share this post


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

I have now re-installed, following the entire guide here as closely as I can, using Pandora's Box and not U-n-i-B-e-a-s-t. I have also upgraded my firmware to 1.5.1 as I found a YouTube video where that was being used and worked.

I am still not able to boot directly from SSD (which is partitioned using APFS by the way), but can boot from the USB.

Any suggestions?

For the last time: read the TUTORIAL! https://github.com/wmchris/DellXPS15-9550-OSX/blob/10.13/Tutorial_10.13_Step7.md#clover-doesnt-boot-or-model-name-error

 

Edited by wmchris

Share this post


Link to post
Share on other sites

OK, so I added an entry to the BIOS for CLOVERX64.efi.

It still does not boot from SSD.

BTW, a suggestion - how about you add a note to the guide in Step 3, near where it says "Your system should be bootable by itself", that if it can not, refer to "clover doesnt boot OR Model Name Error" in "Step 7: Fixes / Enhancements / Alternative Solutions / Bugs".

Share this post


Link to post
Share on other sites
OK, so I added an entry to the BIOS for CLOVERX64.efi.
It still does not boot from SSD.
BTW, a suggestion - how about you add a note to the guide in Step 3, near where it says "Your system should be bootable by itself", that if it can not, refer to "clover doesnt boot OR Model Name Error" in "Step 7: Fixes / Enhancements / Alternative Solutions / Bugs".
You are obviously not reading. Why don't you create an USB with create install using Rehaab man tutorial. Pandorabox never work for me. [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] is only for desktop set ups.

Sent from my Pixel XL using Tapatalk

Share this post


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

OK, so I added an entry to the BIOS for CLOVERX64.efi.

It still does not boot from SSD.

BTW, a suggestion - how about you add a note to the guide in Step 3, near where it says "Your system should be bootable by itself", that if it can not, refer to "clover doesnt boot OR Model Name Error" in "Step 7: Fixes / Enhancements / Alternative Solutions / Bugs".

because i wrote in the tutorial - at the very beginning:
 

Quote

please read the whole document before reporting an issue to prevent multiple questions. Also check Step7 and do a google search.

i dont include jump statements in a 3 page document for people who mistake a tutorial for a bash script.

also i want to hint to:

Quote

But it is NOT suited for people with no or only few knowledge in Hackintosh Systems. If you only know how to copy commands in your shell and you dont know what they're doing, then stop the tutorial and revert to windows or buy a real mac. Even if you get it running: this system is not failsafe and will be broken multiple times in its usage time, where you have to fix it without a step by step tutorial.

your issue is not even a specific issue for this computer. You cant get Clover to boot. This is pre- driver and pre- configuration. It's like: "i cant get my nuclear reactor to work. need help with how to open the front door". We know it's not a clover issue, because the preconfigured stick works. So if you cant configure the EFI to boot from your internal SSD, how will you fix the real issues?

 

Edited by wmchris

Share this post


Link to post
Share on other sites
On 17.3.2018 at 9:36 PM, Rajveer86 said:

Sorry to ask something that seems so obvious, however I'm looking to change my SMBIOS to MacbookPro13,3 and have read in this (and other) guides that I will need to change the fake ethernet to en0. The confusion arises from darkhandz's guide (https://github.com/darkhandz/XPS15-9550-High-Sierra#网卡顺序修正) where he doesn't have the fake ethernet installed and instead has the wifi as en0. Is this because this guide defaults to using an iMac setup whereas his defaults to MacbookPro13,3?

Some Mac-Services identify itself by the Mac(-Address) The wifi driver has been reported as unstable in the past, which resulted in en0 been absent - so no mac address.

obviously it will boot without fake ethernet, but you can run into issues with the AppStore.

So it's just more failsafe to use fake ethernet.

Edited by wmchris

Share this post


Link to post
Share on other sites
On 3/20/2018 at 9:05 AM, wmchris said:

It's like: "i cant get my nuclear reactor to work. need help with how to open the front door".

1

Best thing I've read all day hahahaha :)

Share this post


Link to post
Share on other sites
On 11/03/2018 at 9:59 PM, 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

I did not give you permission to upload a compiled version of the native branch. Kindly remove it. I said multiple times that it was not for public use and the source code is online strictly for development purposes.

 

I will take down the source code for the native branch if people continue to abuse this.

Share this post


Link to post
Share on other sites
48 minutes ago, alex.daoud said:

I did not give you permission to upload a compiled version of the native branch. Kindly remove it. I said multiple times that it was not for public use and the source code is online strictly for development purposes.

 

I will take down the source code for the native branch if people continue to abuse this.

Done, already removed it from the attachment. Sorry if it caused any troubles, wasn't my intention. However, I do have to point out that you actually gave permission to your software distribution when you released it under GNU GPL3, as per section 6.d. Maybe you want to revise the license?

Share this post


Link to post
Share on other sites
On 15/03/2018 at 7:53 AM, Lockzi said:

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.

Hun? That is weird. I don't think neither SSDT-XOSI nor voodooPS2daemon should cause any incompatibilities with I2C. Could you plz provide you system IOReg and logs?

Edited by hvolkoff

Share this post


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

Done, already removed it from the attachment. Sorry if it caused any troubles, wasn't my intention. However, I do have to point out that you actually gave permission to your software distribution when you released it under GNU GPL3, as per section 6.d. Maybe you want to revise the license?

i was in contact with the original author @alex.daoud before, and it was quite the opposite of a friendly chitchat. i think his problem is, that he doesnt like to fiddle with any bug reports (quote: "i know all existing bugs") and this binary triggers the usage by people without much knowledge.

but this is the opposite of an open development, which is very sad.

i fixed some of the (what the original autor told me as "very hard to fix") bugs like the physical click errors, but i was unable to fix the random crashes. The native and the master branch kexts should be considered as highly unstable and i suggest everyone to stick to VoodooPS2 for now.

Before someone asks: I didnt push my changes back to the repo, because of the hostile enviroment...  still, if someone is interested in the changes, contact me.

Edited by wmchris

Share this post


Link to post
Share on other sites
1 hour ago, wmchris said:

i was in contact with the original author @alex.daoud before, and it was quite the opposite of a friendly chitchat. i think his problem is, that he doesnt like to fiddle with any bug reports (quote: "i know all existing bugs") and this binary triggers the usage by people without much knowledge.

but this is the opposite of an open development, which is very sad.

i fixed some of the (what the original autor told me as "very hard to fix") bugs like the physical click errors, but i was unable to fix the random crashes. The native and the master branch kexts should be considered as highly unstable and i suggest everyone to stick to VoodooPS2 for now.

Before someone asks: I didnt push my changes back to the repo, because of the hostile enviroment...  still, if someone is interested in the changes, contact me.

Just my opinion:

To be fair, @alex.daoud faces the same redundant questions being asked on Gitter (mostly from newbies) and most of the questions are quite easy to understand from reading the documentation. It gets quite frustrating after a while. However, I also understand where you are coming from.

I am pretty sure @alex.daoud is all for open-source community driven development. So why don't we all get along and get those pull-requests going shall we?

Back to the native branch:

A lot of the work on the native branch was *a lot* of guess work. I can provide more details on the multitouch protocol and the simulator. Feel free to PM here on InsanelyMac if you want to clarify on why certain parts of the code (i.e. magic constants) are set up that way.

Share this post


Link to post
Share on other sites
On 3/20/2018 at 8:30 AM, wmchris said:

Some Mac-Services identify itself by the Mac(-Address) The wifi driver has been reported as unstable in the past, which resulted in en0 been absent - so no mac address.

obviously it will boot without fake ethernet, but you can run into issues with the AppStore.

So it's just more failsafe to use fake ethernet.

Thank you for the help, I've gone ahead with making the fake ethernet en0 and everything seems to be working fine with my Apple ID :)

Share this post


Link to post
Share on other sites
1 hour ago, 68x said:

To be fair, @alex.daoud faces the same redundant questions being asked on Gitter (mostly from newbies) and most of the questions are quite easy to understand from reading the documentation. It gets quite frustrating after a while. However, I also understand where you are coming from.

ofc, thats why most people dont offer chat support and use either bug reports or add a readme with common bugs or a big warning, but if you dont add anything, people can be missleaded. for ex. the current readme file for the NATIVE branch contains:

Quote

Current Status

The following Intel I2C controllers are fully supported:

  1. INT33C2 and INT33C3 - Haswell era
  2. INT3432 and INT3433 - Broadwell era
  3. pci8086,9d60, pci8086,9d61, pci8086,a160 and pci8086,a161 - Skylake/Kabylake era

The following device classes are fully supported:

  1. I2C-HID devices
  2. ELAN devices

how should anyone know that these are highly unstable pre-alpha debug code with major system compromising and os crashing flaws without reading +100 pages of chatlogs?
so i cant understand why @alex.daoud got so upset from the release of the compiled files by @hvolkoff

however this is highly off-topic, but VoodooI2C itself is not.

VoodooI2C has high potential, but it's not ready yet. Whenever i see a (semi-)stable release, i'll consider adding it to this tutorial. till then i can just repeat: VoodooPS2 has its flaws, too, but its much more stable and feature rich right now

 

--- Report of March, 21st 2018 ---

Pro of VoodooI2C:

  • Much smoother scrolling
  • faster reaction time

Con of VoodooI2C:

  • no palm detection/rejection
  • very VERY sensitive to touch, accidental clicks every time
  • random crashes on bootup (with automatic reboot)
  • random crashes after sleep (with automatic reboot)
  • unable to customize
  • is only compatible with the touchpad, NOT the touchscreen of the Dell XPS 15

 

Report of Native, last commit from early March: https://github.com/alexandred/VoodooI2C/commit/3be7546fd95693330dc84aa3feb7da11d7c3621c

Pro of VoodooI2C Native:

  • Native Multitouch
  • Configurable like an original Apple Magic Trackpad 2
  • Everything from the Pro of the non native version

Con of VoodooI2C Native:

  • Physical Clicks are buggy - nearly impossible to use
  • Random Freezes
  • Random Kernel Panics
  • Random Crashes on Shutdown / unable to shutdown
  • Most touch gestures dont work as they should - if at all
  • hypersensitive
  • Non working drag and drop
  • Everything from the Con of the non native version
  • and many more

 

 

Edited by wmchris

Share this post


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

Done, already removed it from the attachment. Sorry if it caused any troubles, wasn't my intention. However, I do have to point out that you actually gave permission to your software distribution when you released it under GNU GPL3, as per section 6.d. Maybe you want to revise the license?

Thank you. The license acts as a deterrent for companies like touch-base from appropriating code from VoodooI2C. Legally speaking, however, Apple's EULA nullifies any open source license that is applied to kernel level software developed for OS X. The license is merely the illusion of rights applied.

That being said I have always and will always be 100% committed to the open-source development of VoodooI2C. However, it is typically well-recognised that OSS that does not start as a form of collaboration between many people (i.e that was only really started and worked on for a large amount of time by one or two people) will develop a group of people that is known as the "benevolent dictator for life"(https://en.wikipedia.org/wiki/Benevolent_dictator_for_life). Linux is a famous example of this whereby Linus Torvalds effectively has the final say as to what is merged into the master branch of the Linux kernel. Currently myself and @coolstar exercise our rights to this kind of control over the project due to the vast amount of man-hours we have put into it. We have recently (within the last year and a half or so) seen new people eagerly contributing and helping out and, gradually, they will also be able to exercise the same rights over the project.

 

One day I will officially leave this project fully to the community (and cease development myself) but that day cannot come until people realise that this whole idea of making some small changes, bundling them up in a new buggy kext and spreading these kexts around the internet severely undermines the hackintosh community as a whole. This is why the hackintosh community is so unpolished as compared to the iOS jailbreak community. There is very little attention to quality control and what is appropriate to be released as a "beta". This is also why we get so many of the same boring old questions over and over again - its because the internet is full of old junk kexts which people continue to download then complain about when they don't work. You can see this easily with VoodooI2C. We had someone called macforceone create a fork with a certain fix for Elan1200 back in the days of v1.0.0. It was a buggy fix and has long since been superseded - yet I still get questions about why this kext isn't working for people and whether its better to use than v2. The existence of these things undermines the very goal of this project: to provide super fluid (someday native) input on I2C devices. I spent 3 long months working very hard full-time to rewrite VoodooI2C from the ground up officially finishing it in September 2017. I held off on releasing until January 2018 after months of extensive private and then public beta testing. As a result, something that was written in 3 months is almost up to scratch to (and even often outperforms) VoodooPS2 which has been around (and not been rewritten since) in various iterations for close to 13 years. I remember using the predecessor to VoodooPS2 back in 2005 when I first started hackintoshing and the performance has not drastically improved since then.

 

It is for this reason that I do not approve of anything that isn't on the Release page being posted anywhere. It really is for the good of the development of VoodooI2C.

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 metaphysician
      hi folks! i'm just checking for opinions here on a Clover based install of High Sierra. currently i can't boot directly from the internal drive on my hackbook, an ASUS ROG GL502-VS laptop (with the replaced WiFi card), though i can boot from the USB bootloader/installer

      i installed 10.13.6 fine using a prepared vanilla installer on HFS+ (not APFS), but my configuration is somewhat unusual. i have two drives. the first SSD has the Windows system, the second has two partitions with the 2nd partition holding the macOS system. when i ran Clover installer i could not use the UEFI option to copy to the EFI partition because it couldn't find one on that drive. so it installed the EFI folder on the root of the macOS partition instead.
       
      however, after a bit of tinkering around, i found out that there is an existing EFI partition on the primary drive called SYSTEM. it has a EFI folder and underneath that is a Windows folder, a Boot folder, and one called APPLE. i can mount this partition with Clover Configurator and copy files to it, but i don't know if this is a good or risky solution. i was thinking i would manually copy the CLOVER folder and the uefi64.boot file to this partition , making sure not to overwrite anything existing. using the UEFI setup, i can create a boot path from the SYSTEM partition to the Clover boot file, but i'm just curious if this is a useful solution or not, and i don't want to ruin the existing Windows 10 installation for sure. any advice appreciated!
    • 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?
×