Jump to content
AudioGod

AudioGod's Aorus Z390 Pro Patched DSDT Mini Guide and Discussion

2,247 posts in this topic

Recommended Posts

2 hours ago, WizeMan said:

 

So unfortunately after a week or so, my Time Machine USB drive started being force ejected again.

I have updated my initial message a couple of pages back. I did not have this issue for about a week using no darkwake value (thus the kernel setting the default 3) but the morning of the day before yesterday I came to my office, woke up my hack and saw several force eject messages. Then came back yesterday morning, the same. Last night I resorted back to darkwake = 0 and this morning no force eject messages. Will definitely further check it as it seems super random.


@WizeMan Give jettison a try bro,

https://www.stclairsoft.com/Jettison/


Or do what I did ages ago and forgot about it and it’s why my usb never ejects i believe.


To fix "disk did not eject properly" message use  fixUSB.sh  install open terminal:

1- Copy and paste :

// command will download the latest fixUSB.sh ( if link does not work, then follow alternative instructions at bottom)

git clone https://github.com/syscl/Fix-usb-sleep

Enter

 

2- Copy and paste:

chmod +x ~/Fix-usb-sleep/fixUSB.sh

Enter

 

3- Copy and paste:


cd ./Fix-usb-sleep
./fixusb.sh  

Enter

Edited by AudioGod

Share this post


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


@WizeMan Give jettison a try bro,

https://www.stclairsoft.com/Jettison/


Or do what I did ages ago and forgot about it and it’s why my usb never ejects i believe.


To fix "disk did not eject properly" message use  fixUSB.sh  install open terminal:

1- Copy and paste :

// command will download the latest fixUSB.sh ( if link does not work, then follow alternative instructions at bottom)


git clone https://github.com/syscl/Fix-usb-sleep

Enter

 

2- Copy and paste:


chmod +x ~/Fix-usb-sleep/fixUSB.sh

Enter

 

3- Copy and paste:



cd ./Fix-usb-sleep
./fixusb.sh  

Enter

 

Thanks mate! I'll keep experimenting with darkwake=0 which doesn't seem to bring any force ejection issues up until now. In case I see that the problem persists I 'll use fixUSB script.

Share this post


Link to post
Share on other sites
4 minutes ago, WizeMan said:

 

Thanks mate! I'll keep experimenting with darkwake=0 which doesn't seem to bring any force ejection issues up until now. In case I see that the problem persists I 'll use fixUSB script.

 

I use darkwake=0 plus the fixUSb script and I haven’t had a single force eject problem ever and I just forgot about it. That was like 6 months ago or something like that. Used darkwake=8 for a while and moved back to zero but again I have never ever had the force eject issue so I would recommend it personally. :thumbsup_anim:

Share this post


Link to post
Share on other sites

@Wizeman 

The eject problem exists on some real Mac's as well . It's the power definition which can be done via USBX , the current level for sleep is the relevant part.

With my "SSDT only OC" version it should be fixed. Since then, I could remove Jettison.

 

Share this post


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

@Wizeman 

The eject problem exists on some real Mac's as well . It's the power definition which can be done via USBX , the current level for sleep is the relevant part.

With my "SSDT only OC" version it should be fixed. Since then, I could remove Jettison.

 

Problem with USBX is it can leave your external usb rgb lights on once sleep hits as happens to me a lot with my Corsair keyboard or mouse but your right it does cure eject too. 

Edited by AudioGod

Share this post


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

 

Thanks mate! I'll keep experimenting with darkwake=0 which doesn't seem to bring any force ejection issues up until now. In case I see that the problem persists I 'll use fixUSB script.

Love to know if it works for you. It didn’t for me.

 

I tried Jettison and it was nice, but I think you have to eject the drive manually and sleep. I didn’t see it work automatically. Maybe I'll try again. It might be darkwake depend as well.

2 hours ago, texem said:

@Wizeman 

The eject problem exists on some real Mac's as well . It's the power definition which can be done via USBX , the current level for sleep is the relevant part.

With my "SSDT only OC" version it should be fixed. Since then, I could remove Jettison.

 

What and/or where is this "SSDT only OC" I'm a bit confused about USBX?

Share this post


Link to post
Share on other sites
17 minutes ago, pkdesign said:

What and/or where is this "SSDT only OC" I'm a bit confused about USBX?

 

Its not posted or released by any of us yet and is a work in progress so too speak.

It might go live when 0.5.6 is officially released and if it can pass the @larabee test under 19,1. ATM its only reliable on a Z390 Pro with the igpu disabled.

You can request a copy from @texem as I only have a working copy for the Z390 Master that works perfectly under 19,1 with igpu enabled but that's a whole different bios and story and thread. :hysterical:

 

 

Edited by AudioGod

Share this post


Link to post
Share on other sites
39 minutes ago, pkdesign said:

I tried Jettison and it was nice, but I think you have to eject the drive manually and sleep. I didn’t see it work automatically.

 

it's fully automatic, you can configure what to eject and remount on sleep/wake.

 

Share this post


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

CLOVER DRIVER UPDATE 26/02/20

 

OcQuirks Revision 16 & FwRunTimeServices Latest Versions.

 

OcQuirks R16.zip

Are we using the plist file with our setup? Or do we just delete it.

Share this post


Link to post
Share on other sites
20 hours ago, AudioGod said:

Please don’t post an Efi of yours and mark it like it’s one of mine.

you have made many strange changes that are incorrect so I would be grateful if you could remove it please from your post.
thank you

No problems, done.

Thanks anyway.

 

Edited by Olion

Share this post


Link to post
Share on other sites
36 minutes ago, pkdesign said:

Are we using the plist file with our setup? Or do we just delete it.

I don’t use it with the master or the pro setups but it’s been reported on here that it helps so I left it in there. If your having troubles now and again using 19,1 then add the plist and see if it helps.

if it does then just let me know. :thumbsup_anim:
 

50 minutes ago, Tiem said:

1725746116_ScreenShot2020-02-26at11_06_37AM.thumb.png.2097a4abae0153edc23169381561d443.png

Latest beta running on Clover. All good.

Any sign of any performance improvements with your 5700xt using the latest beta?  

Edited by AudioGod

Share this post


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

RTCMemoryFixup.kext is used for CMOS debugging. USBInjectAll.kext is a temporary extension used to aid in mapping USB ports.

But, without USBInjectAll.kext my USB ports don't work.

Share this post


Link to post
Share on other sites
14 minutes ago, Olion said:

But, without USBInjectAll.kext my USB ports don't work.

Did you remove the dsdt and or ssdt from my original Efi when you tried to use it?
or did you add any additional usb info in any way shape or form when you first tried to use it?
 

34 minutes ago, Tiem said:

@AudioGod Nope. They are definitely working on the drivers but it's still falling well short of what the card is capable of doing.

I hope so, the only reason it doesn’t crash for us is because we use smbios 19,1.. Try using a 5700xt under macpro1,1 or better yet with a real Mac of any description and put the gpu under heavy load for a prolonged amount of time and watch what happens...lol...it’s not good at all.

on a hack under 19,1 with the igpu enabled fixes it but it’s not really fixed it’s just hiding the problem.

oh well at least it works for us I guess.

fingers crossed they sort it out soon as I would like to go back to smbios 1,1 for myself and disable my igpu. (Maybe one day) :) 

Edited by AudioGod

Share this post


Link to post
Share on other sites
16 hours ago, Pieroman said:

Have you tried with the quirks DevirtualiseMmio set to true and ForceExitBootServices to false ? This made it working for me (so far !) with the iGPU and 19,1. But I'm on Clover (since we are using OCquirks the same options should be there in OC)...

Hey bud, yeah i had the mmio one enabled with few others under 0.5.5, i have since reset much of what was enabled back to the default if it was off / false to see what occurs .. so far i cant tell that i miss anything.  Ill wait until 0.5.6 is released proper and see what occurs with it when i enable stuff again.

 

Cheers

 

EDIT : Tried Clover again, your right, seems to work out the box with iGPU enabled and using 19,1.  Do you have enabled a qcquirks.plist that sets this DevirtualiseMmio ?  I do not have one and as far as i can tell from here https://github.com/ReddestDream/OcQuirks, its not enabled out the box.  Matters not thus far though as im booted OK.  Doubt ill remain here for long, but its fun to checkout for now :)

 

EDIT2: Just noticed v16 of the OCQuirks that AG posted recently, has a qcquirks.plist file included.. does not enable DevirtualiseMmio though..  Not sure at this point i need it. 

 

Thanks Again.

Edited by Cass67

Share this post


Link to post
Share on other sites

Love reading the discussion on this thread.

I am still on bios f11 with Pro Wifi(disabled from bios from the start as i dont need it).Tried to boot this afternoon with 19.1 it worked fine so far. Forbidden signal when i selected osx.( Had my fw audio card turned on). Turned of the card, again cold boot, same thing so probably  its not the card. Reverted to 1.1 efi and bios settings, all good. Hmmm.. so far cold boot worked, restart from windows worked too. I see 19.1 still not working as good as 1.1 for many. I will stay on 1.1 as i have no issues.

8700k oc 4.7 locked all powersavings off

32gb gskill rgb 3000

Adata 8200 nvme

Strix vega 64

Fw400 pci

Gc Titan Ridge TB3. 

OSX 10.14.6

Thnx 4 all the info guys!

Share this post


Link to post
Share on other sites
8 minutes ago, dsynos80 said:

Love reading the discussion on this thread.

I am still on bios f11 with Pro Wifi(disabled from bios from the start as i dont need it).Tried to boot this afternoon with 19.1 it worked fine so far. Forbidden signal when i selected osx.( Had my fw audio card turned on). Turned of the card, again cold boot, same thing so probably  its not the card. Reverted to 1.1 efi and bios settings, all good. Hmmm.. so far cold boot worked, restart from windows worked too. I see 19.1 still not working as good as 1.1 for many. I will stay on 1.1 as i have no issues.

8700k oc 4.7 locked all powersavings off

32gb gskill rgb 3000

Adata 8200 nvme

Strix vega 64

Fw400 pci

Gc Titan Ridge TB3. 

OSX 10.14.6

Thnx 4 all the info guys!

you need to fully reset the bios by removing all power and then pull the battery from the motherboard for a few mins, put it all back and load your bios settings back with igpu enabled using the 19,1 EFI and away you go.

vital that is to clear out all traces from the memory.  

Share this post


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

Did you remove the dsdt and or ssdt from my original Efi when you tried to use it?
or did you add any additional usb info in any way shape or form when you first tried to use it?

No, 3 days I couldn't find the reason and asked here on the forum for help why USB doesn't work.
Used the "HD 630 Z390 ProF12 dEFI 140220" without any changes. When I change the settings manually described above - usb start working.

Share this post


Link to post
Share on other sites
57 minutes ago, Olion said:

No, 3 days I couldn't find the reason and asked here on the forum for help why USB doesn't work.
Used the "HD 630 Z390 ProF12 dEFI 140220" without any changes. When I change the settings manually described above - usb start working.

 

@Olion Here I made this just for you,

I tested it on my test bench before sending it to you and its works for me.

ive also made random details for you to use.

let me know if it woks for you but If it dont then switch the smbios iMac18,1 and try again

 

Olion EFI igpu only.zip

 

Note - If you have a Nvidia Or any other discrete gpu that your not using in MacOS installed then add -wegnoegpu to the boot arguments in the clover config to disable it in MacOS. Other then that don’t make any other changes to the EFI or upgrade or over install clover just drop this into your EFI partition on your usb install key or hard drive and try and boot up.

sign out of iCloud if your signed into it as this has different details setup for you already.

good luck!

Edited by AudioGod

Share this post


Link to post
Share on other sites
On 2/16/2020 at 11:57 AM, AudioGod said:

 

the one I have never got to work is unlock the lock screen with my watch. Something about where I live and the noise around me that makes it just not work.

ive tried to get it going on various setups including my own and different cards including your one but have never succeeded to get it to unlock my hack. It can everything else it’s meant to like approve installs but not that. It’s very annoying and I gave up a while ago now or I would of gone crazy...lol

 

Just coming back to unlock with apple watch, using the latest clover EFI you provide on here (upgraded clover version to 5104 since) i notice that while apple watch unlock works, when i lock the screen and raise watch to unlock, the screen goes black and seems to go to sleep, have to hit enter to get logged in... This is one difference on Clover that i have experienced with OC, i get no black screen on OC, just opens the desktop right away..  Just thought id note this here since im back on Clover for a bit.

Share this post


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

I hope so, the only reason it doesn’t crash for us is because we use smbios 19,1.. Try using a 5700xt under macpro1,1 or better yet with a real Mac of any description and put the gpu under heavy load for a prolonged amount of time and watch what happens...lol...it’s not good at all.

on a hack under 19,1 with the igpu enabled fixes it but it’s not really fixed it’s just hiding the problem.

oh well at least it works for us I guess.

fingers crossed they sort it out soon as I would like to go back to smbios 1,1 for myself and disable my igpu. (Maybe one day) :) 

I'd be happy if they just fixed the bugs. Since beta 2, the dock is mirrored on shutdown/logout to where it doubles up. Still there this beta. But the 5600/5700 are the first of the Navi chips, so here's hoping they keep refining.

 

So far tho, still the same as before.

Share this post


Link to post
Share on other sites
8 hours ago, AudioGod said:

you need to fully reset the bios by removing all power and then pull the battery from the motherboard for a few mins, put it all back and load your bios settings back with igpu enabled using the 19,1 EFI and away you go.

vital that is to clear out all traces from the memory.  

Hehe yes boss i know the drill! Of course i did that. With 1 monitor it works ok. With 2 i get the error. Maybe its a thing from the vega? I have my 1st mon on DP and the 2nd on Hdmi. The hdmi mon used to open first after entering osx, but the latest lilu+weg fixed that.

Share this post


Link to post
Share on other sites

Aorus Z390 pro , i7 9700K , 32GB , Sapphire RX5700 XT Nitro+ , F11

 

Got random reboots :(

Screenshot 2020-02-27 at 16.53.45.png

Zrzut ekranu 2020-02-27 o 16.50.58.png

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

  • Similar Content

    • By AudioGod
      I have put together this simple little guide for anybody wanting to use a Patched DSDT EFI with the same configuration as me.
      This is also a thread to discuss everything Z390 Master and try and help where we can and maybe make things a little better for you. 
       
      A huge massive thank you to @glasgood @MaLd0n @larabee These three guys have helped me and talked me so much and are as helpful as you could ever get, Without them I wouldn't have a perfect working build like I do or be putting up this Guide & Discussion Thread sharing the hard work and countless hours that we have all put in to this.   
       
       
      This EFI and Patched DSDT have been created to work with a Gigabyte Aorus Z390 Master using bios revision F11c, 9900k with a 5700 XT but has also been tested and verified fully working with the following Hardware
       
      CPU's
      8600K, 8700, 8700K, 9600K, 9700K, 9900K, 9900KS
       
      GPU's
      RX 560, 570, 580, 590, Vega 56, Vega 64, Radion VII, 5700, 5700 XT
      (If you have success with any different CPU or GPU's then please do let me know)
       
       
       @glasgood Has kindly put together a new simple Catalina install guide so Just Follow He's Guide For a Perfect Install. (glasgood put the guide together for the Z390 Pro but the two boards are so alike that you can follow this guide with no problems at all using the Z390 Master)
       
       
      HARDWARE USED
      • Intel I9 9900k @5.2Ghz
      • Gigabyte AORUS Z390 MASTER
      • Sapphire Reference RX 5700 XT ( connected to monitor with DisplayPort )
      • Corsair Vengeance Pro RGB 32GB @3600mhz (2 x 16GB)
      • Corsair RM850x 80 Plus Gold Power Supply Unit
      • EK Custom Liquid Cooling Loop
      • Samsung 970 EVO 1TB NVMe SSD macOS Catalina 10.15.3
      • Samsung 860 EVO 1TB SSD (2.5) Windows 10 Pro
      • ABWB BCM943602CS 802.11AC WI-FI With Bluetooth 4.0 PCI-Express (PCI-E)   
      • Lian Li PC-O11DW Dynamic ATX Case
       

       

       

       
      WORKING
      • Sound 
      • Ethernet Port
      • WiFi
      • SSD Trim
      • USB 3.0 & 2.0 (All ports Open Natively)
      • AirDrop
      • iCloud
      • Hardware Acceleration
      • iMessages
      • Facetime
      • Sleep & Wake
      • Sleep and Shutdown via the Power Button
      • Handoff
      • Netflix on Safari browser
      • Continuity
      • Sidecar (only works using the iMac19,1 EFI and with your igpu Enabled)

       
      EFI FOLDERS  
      please note - You must flash your Z390 MASTER bios to revision F11c to use any of these EFI's, The DSDT is not designed for any other Bios revision
      mb_bios_z390-aorus-master_f11c.zip - Aorus Z390 Master Bios F11c 
       
      Current EFIs 
      Updated 26/03/2020
      PLEASE NOTE - You MUST update to the latest Clover EFI before updating to 10.15.4 or you may find your unable to update.
       
      Clover EFI Updated 26/03/20 - Use with Bios revision F11c Only or Replace with the older F10 DSDT if you don't want to update the bios
      Clover Z390 Master Vega Navi EFI 260320.zip - Vega, Navi (5700, 5700XT), Radeon VII DSDT EFI
      Clover Z390 Master Polaris EFI 260320.zip - R5XX Polaris DSDT EFI
       
       
      CFG Unlock (MSR) F11c BIOS Profile - The Easy Way 
      Highly recommended if your using a Vega 56/64, Radeon VII or Navi GPU
       
       
      ADDITIONAL DSDT's & Older EFI’s (A big thanks to @MaLd0n for compiling these DSDT's)
       
       
      Alternative EFI - OpenCore No DSDT and Done the way OpenCore intended it (03/03/2020)
       

      Alternative EFI 2 - N-D-K Fork of OpenCore (03/03/2020)
       
       
      To Create Your Own Patched DSDT Message @MaLd0n using the link bellow
      https://www.olarila.com/forum/17-dsdt-patch-requests/
      (If you want a perfect setup then getting your own patched DSDT made would be the best thing to do, Mine will work perfectly fine but different hardware no matter how small a change it is can tend to have some sort of effect on the DSDT and your setup)
       
       
      If Your Not Using File Vault Then Please Disable Hibernate
      disablehibernate.command
       
       
      ADDITONAL DOWNLOADS
      mb_bios_z390-aorus-master_f10
      Clover
      Clover Configurator
      Kext Updater
      RepairPermissions
       
       
      OPTIONAL DOWNLOADS
      BroadcomFix.zip   (Use these kexts if your Broadcom bluetooth/Wifi isn't working properly)
      Hackintool
      IORegistryExplorer
      Native Display Brightness with MonitorControl
       
       
      BIOS SETTINGS (Bios Revision F11C)
       
      • Enter BIOS → Press Delete → Enter Setup
      • Save & Exit → Load Optimized Defaults
       
      • Boot -> Windows 8/10 Features -> Win 8/10WHQL
      • Boot -> CSM Support -> Disabled (Can be set to Enabled if need be but try to have it set to Disabled first)
      • Favourites -> Extreme Memory Profile (X.M.P.) -> Profile1
      • Favourites -> VT-d -> Disabled (Can be set to Enabled or Disabled, Your choice)
      • Settings -> IO Ports -> Internal Display Output -> PCIe 1 Slot
      • Settings -> IO Ports -> Internal Graphics -> Enabled
      • Settings -> IO Ports -> DVMT Pre-Allocated -> 64M
      • Settings -> IO Ports -> DVMT Total GFX0-Allocated -> 256M
      • Settings -> IO Ports -> Aperture Size -> 256MB
      • Settings -> IO Ports -> Wifi -> Disabled
      • Settings -> IO Ports -> Audio Controller -> Enabled
      • Settings -> IO Ports -> Above 4G Decoding -> Enabled
      • Settings -> IO Ports -> USB Configuration -> Legacy USB Support -> Disabled
      • Settings -> IO Ports -> USB Configuration -> XHCI Hands-off -> Enabled
      • Settings -> Miscellaneous -> Software Guard Extensions (SGX) -> Disabled
      • Settings -> Platform Power -> Platform Power Management -> Enabled
      • Settings -> Platform Power -> ErP -> Enabled
      • Settings -> Platform Power -> RC6(Render Standby) -> Enabled
       
      • Save & Exit → Save & Exit Setup
       
       
      SCREENSHOTS

       
       

       

       

       

       

       

       

    • By Rohan20
      Opencore is running really really slow on Catalina 10.15.4. So It was running perfectly before I put the ssdt-pnlf for enabling Brightness control. it is running really slow and I verified my config with the sanity checker and its all correct. can someone please help. I am attaching my oc folder.

       
      https://www.dropbox.com/s/drkek0eaz19ina5/OC.zip?dl=0
       
    • By tlefko
      Description
      This esentially an ultra-simplistic version that is stable without the use of a deploy or complicated file installations and copies. Highly recommend using DW1560 wifi card, killer wifi isn't supported. This does include a copy of Clover, which of course I take no credit for. I am only responsible for minor changes in files and plists, as well as placement and instructions throughout the guide (as well as the work used from previous projects). Many files and ideas are sourced from @maz-1, @syscl, and my previous guides Granted, many files are similar or the same but there is significantly less of them and/or they are predeployed into spots where they will work just as well, even if not as efficient on bootup. Esentially, this guide is designed to provide a perfectly working setup with little knowledge of the topic and without optimization (because often they can break things). Most patches on the main plist use patches implemented by him as well. ****This guide does work excellently however and will provide you with a near perfect setup for Catalina for your XPS 9350, and is currently my daily driver as I struggled using the referenced users files as well.
      Styling
      This guide is designed to be literally as thorough as possible to appeal to those who really don't understand many of the things in @maz-1's guide or some of the other users as they assume you would already understand this information. It does not cover complex topics like undervolting etc etc Notes
      Never tested USB C except for charging, works great no issues with sleep, wakeup. power management is defaulted as I found with @maz-1 it had issues when on battery switching from AC USB devices eject on sleep (not really an issue) Haven't implemented a Bluetooth solution into this yet, as I don't really use it -- will be added ASAP (I believe KILLER WIFI will NOT work, must use one of the supported chipsets (DW1560 is excellent) BIOS Setup
      Set all SATA operation as AHCI Disable Secure Boot, Fast Boot For Coil Whine improvement disable C-States Enable UEFI Booting Recommended: Clean Install (Preinstall steps)
      Format a USB (16GB) as Journaled and then proceed to download the latest Catalina Installer Patcher Application Download the latest Catalina installer from within the Patcher App, and select to download a new copy and install to your USB device Download the clover configurator application and mount the EFI of the USB partition, then copy the contents of the Files linked above to the EFI Folder within the EFI partition. ** This is because the App Store installers will often not download a full installer, just an truncated version that downloads the installer files from the interent while installing. Thus, they're not bootable from a USB as they're not complete. That is why you should use this method to make sure the installer is usable for bootable media.
      Install Steps
      Simply use F12 to boot from the USB device, and select the USB Device and then boot from the Install mac OS partition. I have defaulted the installer to boot into verbose mode so I can easily see the errors you guys are seeing if you encounter them. If everything goes well, you can disable these from the boot arguments selection of Clover Configurator Boot into the USB Device, and follow the steps to format your SSD from the installer to install Mac OS Catalina. NOTE THE TRACKPAD WILL NOT FUNCTION AT THIS POINT, BUT THE TOUCHSCREEN WILL. This is caused by the way the installer handles Kext loading but because the touchscreen is being loaded via usb and the keyboard in a different method (which I can explain in detail if you'd like, the install will be possible. Do not be alarmed if the installer takes a long time to boot into, this is expected Once you have done this step, use F12 to select the USB and boot into the installer from the SSD in the options menu. (you cannot boot natively yet as the EFI isn't copied into the SSD yet. Setup computer as normal, touchpad, brightness, etc, should all be functioning at this point. Same with wifi. Then, you should using Clover configurator copy the contents of the USB EFI into the EFI folder of your SSD EFI partition (in the folder) Now we will add this as a native boot option. Setup computer as normal, touchpad, brightness, etc, should all be functioning at this point. Same with wifi. Then, you should using Clover configurator copy the contents of the USB EFI into the EFI folder of your SSD EFI partition (in the folder) Now will we add this as a boot entry so you can always boot from this natively without the USB. Boot Entry Setup
      Boot into the BIOS of the computer, then navigate to the Boot setup (or entries (not sure what it is called exactly, but it will be a list of the options your computer selects to boot) Click add new, and make sure the USB isn't plugged in. Select the only option that is avaiable, and in FS0 navigate to Boot/BOOTx64. Add this as an entry, then select this as whatever priority you would like. Credits
      Credit Hackintosher.com for basic patches (although @syscl) covered some Credit to @Rehabman Credit to @syscl Kexts, and his contributers (@maz-1) Messages and Facetime
      Using Clover Configuator generate your own Serials, Board Numbers, MLB There are various guides online to do this and as default they're set to essentially Null (Fakeserial) This is fairly straightforward and there is lots of documentation, just don't open these apps until you've done this properly. Finished!
      Congratulations, there really aren't any more steps that are required. Feel free to contact me with any questions. Files can be downloaded here, and issues and help requests can be said here or opened into the GitHub page. Please @ me for a faster response on this page, as I am not that attentive, also, feel free to PM me.  Github: https://github.com/tlefko/XPS13-9350-Catalina Thanks for reading! Files.zip
    • By Teress
      I built the world’s fastest, most powerful, ultimate Hackintosh in 2020! 2019 Mac Pro cannot compete with my build!  Real 2019 Mac Pro killer! Real Monster. Watch here
      https://youtu.be/A-1aFfToXzk
×