Jump to content
JRevenge

Post install Asus X550JX DM217T [Mojave dev 11]

93 posts in this topic

Recommended Posts

Ciao ragazzi, 

volevo anticipatamente nuovamente ringraziare gengik84 per avermi realizzato il medesimo portatile su High Sierra perfettamente funzionante, che fino ad oggi non mi ha mai dato nessun problema.

 

Ho deciso di installare la developer 11 o se meglio vogliamo chiamarla "DG" che dovrebbe essere l'anticipazione della stabile, tutto funziona correttamente tranne le seguenti cose:

 

- WiFi non funzionante (prima andava senza problemi, addirittura la 5Ghz)

- Bug grafici (che ad es. disattivato l'accelerazione hardware da Chrome, non da più problemi)

- Se non avvio Clover in -v, non parte

 

Avreste modo di aiutarmi?

Per il resto, touchpad, tastiera, audio, batteria, ethernet e quant'altro vanno senza problemi.

 

Grazie anticipatamente e allego la EFI

EFI.zip

Share this post


Link to post
Share on other sites
Advertisement

Niente, non funziona proprio. Anche se devo essere sincero, anche dalla chiavetta non si avvia più (mi esce la scritta veloce in verbose e si riavvia il Portatile). @gengik84 hai qualche consiglio? te che ci hai messo mano sul portatile? Grazie ad entrambi nel frattempo

Share this post


Link to post
Share on other sites
2 minutes ago, gengik84 said:

Ciao che wifi hai?

 

Wi-Fi Atheros AR9462 AR5B22

5 minutes ago, gengik84 said:

Ciao che wifi hai?

Atheros...

AppleHa rimosso i kext quindi rimosso il supporto a tali wifi...

 

Che brutta notizia che mi dai!

A questo punto mi consigli qualche altra scheda funzionante (così da rimuovere questa, come ho fatto inizialmente con quella originale che non era 5Ghz) o rimango su High Sierra?

 

Grazie anticipatamente

Share this post


Link to post
Share on other sites

non ricordo il modello esatto che monti adesso

 

comunque si può provare ma non ti prometto nulla perchè tocca andare a installare kext di 10.13

 

riguardo ai wifi la miglior cosa è andare su broadcom

a secondo se mini pci-e o m2 ci sono alcuni modelli compatibili 

Share this post


Link to post
Share on other sites
2 minutes ago, gengik84 said:

non ricordo il modello esatto che monti adesso

 

comunque si può provare ma non ti prometto nulla perchè tocca andare a installare kext di 10.13

 

riguardo ai wifi la miglior cosa è andare su broadcom

a secondo se mini pci-e o m2 ci sono alcuni modelli compatibili 

 

E' una mini pci-e, esattamente questa: https://www.amazon.com/Bluetooth-PCI-Express-Half-Size-Atheros-chipset/dp/B012JQVUX8

 

EDIT: Questa nello screenshot esattamente

 

Schermata 2018-09-14 alle 12.47.53.png

Edited by onlyJRevenge

Share this post


Link to post
Share on other sites

EDIT: non avevo letto... ti faccio fare una prova...

è una mini pci-e

 quindi in caso devi acquistare una BCM4352 che ha BT 4.0

Share this post


Link to post
Share on other sites
1 minute ago, gengik84 said:

EDIT: non avevo letto... ti faccio fare una prova...

 

Dai un occhiata nello screenshot, non vorrei fossero diverse le due che ho mandate.

Share this post


Link to post
Share on other sites

in un primo momento avevi scritto che andava tutto :D togli i sensor dalla EFI e inserisci il fake ID  0x12345678 in devices intel GFX oppure direttamente dalla GUI di clover

 

In caso di riavvii o blocchi servirebbe foto o video per capire quale potrebbe essere il problema

Share this post


Link to post
Share on other sites
Just now, iCanaro said:

in un primo momento avevi scritto che andava tutto :D togli i sensor dalla EFI e inserisci il fake ID  0x12345678 in devices intel GFX oppure direttamente dalla GUI di clover

 

In caso di riavvii o blocchi servirebbe foto o video per capire quale potrebbe essere il problema

 

Allora all'inizio post-installazione andava tutto, tranne:

 

- Bug grafici (ma rimuovendo l'accelerazione hardware a tipo Chrome, non lo dava, ovviamente solo su Chrome)

- Si avvia solo in -v, senza -v non parte

- Il WiFi non funzionante, ma abbiamo capito dove sta il problema.

 

Dopo che ho provato a mettere dei comandi nel boot arg, ha iniziato a dare anche altri problemi.

Nel caso, uso il tuo config e la rimozione del kext che mi hai detto, o uso la mia che funziona e faccio questa prova?

Just now, gengik84 said:

perchè togli i sensors? e usa il fakeID?

ha detto che ha solo glitch...

 

Esattamente mi va anche la % della batteria. I sensori funzionano. Ho solamente quel problema che me lo fece anche su High Sierra e poi mi sistemasti te, e quell'avvio solamente in -v con verbose

Share this post


Link to post
Share on other sites

@gengik84 io non ci stò capendo niente allora, prima ha detto che ha solo i glitch, poi ora ha scritto che non gli parte più nemmeno con la USB...sono un po' confuso :o

Share this post


Link to post
Share on other sites

@onlyJRevenge

Fai questa prova, sostituisci la cartella clover

poi trovi due kext sempre allegati, installali direttamente in S/L/E riavvia e controlla il wifi

Per installarli usa https://www.insanelymac.com/forum/applications/core/interface/file/attachment.php?id=187043

trasportali dentro l'app, fa tutto da se, quando ha finito devi solo riavviare

 

per il wifi se vuoi sostituirlo ti confermo quello sopra citato

Share this post


Link to post
Share on other sites

se il problema sono i glitch, azhul con mojave non serve una cippa, e nel config che ho messo ci stà la relativa patch 9Mb cursor per risolvere il problema

Share this post


Link to post
Share on other sites
2 minutes ago, iCanaro said:

@gengik84 io non ci stò capendo niente allora, prima ha detto che ha solo i glitch, poi ora ha scritto che non gli parte più nemmeno con la USB...sono un po' confuso :o

 

Sì, ma infatti ora neanche parte con la USB, ma probabilmente perchè ho combinato casini io. Adesso reinstallo tutto da zero, con la mia EFI e poi provo la guida suggerita da @gengik84

Just now, gengik84 said:

EDIT:Aspetta ho visto ora che hai un po di confusione anche nei driver..

 

Confido in voi allora! Attendo e se volete, faccio l'installazione da zero con la vostra EFI sistemata

 

Share this post


Link to post
Share on other sites

nella tua EFI ti ribadisco che azhul lo devi togliere

nel tuo config è sbagliato il SIP hai inserito solo 3, occorre almeno 0x67

Share this post


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

nella tua EFI ti ribadisco che azhul lo devi togliere

nel tuo config è sbagliato il SIP hai inserito solo 3, occorre almeno 0x67

 

Se è sbagliato, provvedo a corregerlo. Avendo utilizzato su High Sierra senza problemi, non l'ho mai toccato per questo motivo.

Edited by onlyJRevenge

Share this post


Link to post
Share on other sites

Ho un'hack simile al tuo e ho avuto gli stessi problemi quando installai la prima beta di mojave... poi grazie a gengik ho risolto :)

azhul non serve e si usa una patch che trovi nel config che ti ho messo

 

chiaro che 0x67 non è obbligatorio ;) 

Edited by iCanaro

Share this post


Link to post
Share on other sites

@iCanaro 

Dalla mia guida per usb, info riguardo a SIP

configurazione 0x3

       Apple Internal: disabled
       Kext Signing: disabled
       Filesystem Protections: disabled
       Debugging Restrictions: enabled
       DTrace Restrictions: enabled
       NVRAM Protections: enabled
       BaseSystem Verification: enabled

 

Share this post


Link to post
Share on other sites
2 minutes ago, gengik84 said:

@onlyJRevenge

sostituisci e segui le info del post precedente

Archivio.zip

@iCanaro andrebbe bene solo che doveva mettere 0x3 e non 3

non è obbligo 0x67

 

Grazie mille ad entrambi. Posso procedere con la mia EFI all'installazione (che sto facendo) e so che mi porta a termine tutto e successivamente, una volta avviato, provvedo con la vostra EFI e consigli? così almeno riesco a muovervi all'interno di Mojave, senza quel casino che ho creato precedentemente.

Share this post


Link to post
Share on other sites
1 minute ago, onlyJRevenge said:

 

Grazie mille ad entrambi. Posso procedere con la mia EFI all'installazione (che sto facendo) e so che mi porta a termine tutto e successivamente, una volta avviato, provvedo con la vostra EFI e consigli? così almeno riesco a muovervi all'interno di Mojave, senza quel casino che ho creato precedentemente.

Non so a quale confusioni ti riferisci... non posso sapere quella sul sistema...io per ora ho visto solo quella nella EFI

quindi se reinstalli con quella non cambia gran che.. 

Poi se hai anche "pacioccato" il sistema ...allora altro discorso

Share this post


Link to post
Share on other sites
5 minutes ago, gengik84 said:

Non so a quale confusioni ti riferisci... non posso sapere quella sul sistema...io per ora ho visto solo quella nella EFI

quindi se reinstalli con quella non cambia gran che.. 

Poi se hai anche "pacioccato" il sistema ...allora altro discorso

 

Sì, infatti procedo ad installare da zero con la mia EFI, appena finisce, la sostituisco con la tua e installo i due kext tramite Utility che mi hai inviato. Riavvio e vi faccio sapere. Il problema con l'avvio solamente in -v me lo dava anche all'inizio, nella prima installazione, secondo voi, come mai? l'SSD lo formatto in APFS - Guid (se può essere quello il problema)

 

EDIT: Ecco, dopo il primo avvio dell'installazione da chiavetta (con il metodo Vanilla), passo per selezionare l'SSD per procedere nell'installazione e non va. Se faccio partire con -v continua l'installazione e la porta a termine.

Edited by onlyJRevenge

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 headkaze
      Framebuffer patching in Mojave
      Binary patching framebuffers using KextsToPatch in Clover is no longer a viable method in Mojave for Skylake and above. Now you need to use Lilu + WhateverGreen.
       
      Not just for Mojave
      This method of framebuffer patching is not only required for Mojave we recommend it for all previous and future releases of macOS.
       
      Coffee Lake Users
      Please note that the new WhateverGreen will not work with fake Kaby Lake platform-id's. You will need to have either macOS 10.14 Beta 4 (18A336e) or macOS High Sierra 10.13.6 (17G2112). The latter is a special build only available to MacBookPro15,1 or MacBookPro15,2 board id's. You can create a macOS High Sierra 10.13.6 (17G2112) installer by running installinstallmacos.py. (Update: vit9696 added back ability to fake Kaby Lake platform-id's)
       
      Lilu + WhateverGreen
      WhateverGreen is going to replace all the other video patching plugins for Lilu (it currently has merged WhateverGreen, IntelGraphicsFixup, NvidiaGraphicsFixup, Shiki and CoreDisplayFixup). Others will likely follow (such as AppleALC, HibernationFixup and IntelGraphicsDVMTFixup). This is aiming to be the all-in-one solution for video.
       
      Beta Warning
      Please note that it is currently in a "beta" state so use it at your own risk. I am just documenting this here for those of you who want to get framebuffer patching now.
       
      Preliminary
      1. Remove:
      - FakePCIID_Intel_HD_Graphics
      - IntelGraphicsFixup
      - NvidiaGraphicsFixup
      - CoreDisplayFixup
      - Shiki
      2. Turn off all graphics injections in Clover:
      - config.plist/Graphics/Inject/ATI=NO
      - config.plist/Graphics/Inject/Intel=NO
      - config.plist/Graphics/Inject/NVidia=NO
      - config.plist/Graphics/ig-platform-id=
      - config.plist/Devices/FakeID/IntelGFX=

      3. Disable DSDT Clover fixes:
      - AddHDMI
      - FixDisplay
      - FixIntelGfx
      - AddIMEI
      4. Disable UseIntelHDMI
      5. Remove boot argument: -disablegfxfirmware
      6. Remove any IGPU and HDMI entries from:
      - config.plist/Devices/Arbitrary
      - config.plist/Devices/Properties
      - config.plist/Devices/AddProperties
      7. Remove any IGPU and HDMI related SSDT and DSDT from:
      - CLOVER/ACPI/patched
      8. Renaming GFX0 -> IGPU
      - WhateverGreen will do this automatically (see caveat below)
      - Be aware that WhateverGreen does not rename all instances of GFX0 -> IGPU but should be okay in most cases
      - You may need to include Clover GFX0 -> IGPU rename for other kexts or ACPI patching that require it
       
      Compile Lilu + WhateverGreen
      Download WhateverGreen. Make sure you place the debug version of Lilu into the root of WhateverGreen before you compile. Install Lilu and WhateverGreen kext's into the usual place. Compile WhateverGreen as debug if you want to view debug output.
       
      Having trouble compiling?
      If you're having trouble compiling you can wait for the official binaries or download my (unsupported) build_lilu.sh shell script and run it in a folder to download and build Lilu + WhateverGreen using Xcode automatically. I recommend you try the debug versions first (place them into Clover's EFI/Clover/kexts/Other folder).
       
      Get the device path of your IGPU:
      Download and use the gfxutil tool like so:
      $ ./gfxutil -f IGPU DevicePath = PciRoot(0x0)/Pci(0x2,0x0) ig-platform-id
      For the AAPL,ig-platform-id (AAPL,snb-platform-id for Sandy Bridge) entry Clover requires this value to be in Data format so you need to reverse the bytes. So if you want your platform-id to be 0x3EA50009 first reverse the bytes (0900A53E) then use Xcode's plist editor to add the values to Clover's config.plist.

       
      What ig-platform-id should I use for my system?
      You should choose one that is the closest match to your system. I recommend you do some research on this before choosing one. See post #2 for available options. More info can be found here.
       
      You can determine the generation of your CPU by the first digit after the hyphen.
      Examples:
      - Intel(R) Core(TM) i5-2760QM (Gen 2)
      - Intel(R) Core(TM) i7-5257U CPU @ 2.70GHz (Gen 5)
      - Intel(R) Core(TM) m3-6Y30 (Gen 6)
      - Intel(R) Core(TM) i5-8350U (Gen 8)
       
      Here are some recommended frames:
       
      Gen 2: Sandy Bridge (Intel HD Graphics 2000/3000)
      - Support started with OS X 10.7.x and ended with macOS 10.13.6
      - Metal support is not available
      - Desktop: 0x00030010 (default)
      - Laptop: 0x00010000 (default)
       
      Gen 3: Ivy Bridge (Intel HD Graphics 2500/4000)
      - Support started with OS X 10.8.x
      - Desktop: 0x0166000A (default), 0x01620005
      - Laptop: 0x01660003 (default), 0x01660009, 0x01660004
       
      Gen 4: Haswell (Intel HD Graphics 4200-5200)
      - Support started with OS X 10.9.x
      - Desktop: 0x0D220003 (default)
      - Laptop: 0x0A160000 (default), 0x0A260005 (recommended)
       
      Gen 5: Broadwell (Intel HD Graphics 5300-6300)
      - Support started with OS X 10.10.2
      - Desktop: 0x16220007 (default)
      - Laptop: 0x16260006 (default)
       
      Gen 6: Skylake (Intel HD Graphics 510-580)
      - Support started with OS X 10.11.4
      - Desktop: 0x19120000 (default)
      - Laptop: 0x19160000 (default)
       
      Gen 7: Kaby Lake (Intel HD Graphics 610-650)
      - Support started with macOS 10.12.6
      - Desktop: 0x59160000 (default)
      - Laptop: 0x591B0000 (default)
       
      Gen 8: Coffee Lake (Intel UHD Graphics 630)
      - Support started with macOS 10.13.6 (17G2112) / 10.14 beta 4 (18A336e)
      - Desktop: 0x3EA50000 (default), 0x3E9B0007 (recommended)
      - Laptop: 0x3EA50009 (default)
       
      Framebuffer Patching
      WhateverGreen does most of the work automatically for you and in most cases you do not need any extra Framebuffer Patching. At the minimum though you should choose an ig-platform-id suitable for your system and place it in config.plist/Devices/Properties like this:

      Here are some reasons why you might need extra Framebuffer Patching:
      - Setting DVMT for those who can't set it above 32 MB in BIOS (framebuffer-stolenmem / framebuffer-fbmem)
      - Setting higher VRAM (framebuffer-unifiedmem)
      - Disabling eGPU (disable-external-gpu)
      - Enable pixel clock patch for 4K support (enable-hdmi20)
      - Disabling connectors to enable sleep (framebuffer-pipecount / framebuffer-portcount / framebuffer-conX-type=-1)
      - Removing CNConnectorAlwaysConnected flag for eDP laptop screens on < 10.13.6 (framebuffer-con0-flags=0x00000090)
      - Changing connector types to match your systems ports (framebuffer-conX-type)
       
      Framebuffer Patching Types
      We have three different types of patches:
       
      1. Arbitrary (Recommended)
      framebuffer-patch-enable (required to enable below) framebuffer-framebufferid (optional; defaults to current platform-id) (all below are optional) framebuffer-mobile framebuffer-pipecount framebuffer-portcount framebuffer-memorycount framebuffer-stolenmem framebuffer-fbmem framebuffer-unifiedmem framebuffer-cursormem (Haswell only) framebuffer-conX-enable (required to enable below) framebuffer-conX-index framebuffer-conX-busid framebuffer-conX-pipe framebuffer-conX-type framebuffer-conX-flags 2. All Data
      framebuffer-conX-enable (required to enable below) framebuffer-conX-alldata 3. Find / Replace
      framebuffer-patchX-enable (required to enable below) framebuffer-patchX-framebufferid (optional; defaults to current platform-id) framebuffer-patchX-find framebuffer-patchX-replace framebuffer-patchX-count (optional; defaults to 1) You should place your patches in config.plist/Devices/Properties in Clover config.plist.
       
      Here are some example patches:
      - 32MB BIOS, 19MB stolen (framebuffer) 9MB fbmem (cursor) 2048MB unifiedmem (vram)

       
      - Pipe / Port Count 3 to 2
      - Connector 1 DP to HDMI
      - Connector 2 Disable

       
      Here is an example of the All Data method:

       
      Here is an example of the Find / Replace method:

       
      Framebuffer Dumps
      There are two ways to dump your framebuffer data (both require WhateverGreen + Lilu debug versions):
       
      1. Using -igfxdump boot flag to dump IGPU framebuffer kext to /AppleIntelFramebuffer_X_Y (root of your boot drive)
       
      There are several ways of reading this dump:
      - Using 010 Editor along with the IntelFramebuffer.bt template
      - Using Intel FB-Patcher File->Open menu
       
      2. Using -igfxfbdump boot flag to dump native and patched framebuffer table to ioreg at IOService:/IOResources/WhateverGreen
       
      There are several ways of reading this dump:
      - Using dump_platformlist.sh shell script
      - Using Intel FB-Patcher File->Import->IOReg Dump menu
       
      Debug Output
      To get debug output from Lilu use the -liludbgall flag and for WhateverGreen use the -wegdbg boot flag. You will need to compile Lilu and WhateverGreen as debug for both of these flags to work.
       
      To view debug paste the following into Terminal (weglog.txt will output to your home directory):
      log show --predicate 'process == "kernel" AND (eventMessage CONTAINS "WhateverGreen" OR eventMessage CONTAINS "Lilu")' --style syslog --source --last boot >weglog.txt
      Credits
      - vit9696 and lvs1974 for WhateverGreen (Full Credits) and Lilu (Full Credits)
      - Andrey1970 for his guide on applelife.ru
      - RehabMan for all data patching method, ioreg framebuffer dump and other contributions
       


    • By Luan Eduardo
      Installing macOS Mojave 10.14 on Gigabyte Z370N WIFI + i7 8700K + UHD 630



      Changelog:
       
      10/17/2018 08:12h GMT-0
      - Fix Kexts permissions commands adjusted.
      - Removed FrameBuffer patch that is not needed.
      - Added audio solution and HDMI.
      - Unfortunately DisplayPort does not work.
      - Replaced Wifi/BT with DW1560 (BCM94352Z)
       
      10/11/2018 04:15h GMT-0
      - Added USB 3.0 patch.
      - Adjusted some steps.
      - Changed text formatting.
       
      10/11/2018 03:42h GMT-0
      - Added missing UEFI configuration.
       
      10/07/2018 00:36h GMT-0
      - First version.
       
      What works and what does not
       
      - Processor ->  Work. All SpeedStep stages.
      - Video Card ->  Work. QE/CI and Metal.
      - Chipset ->  Work.
      - HDMI (1st) ->  Work.
      - HDMI (2nd) ->  Work.
      - DP ->  Not work.
      - Audio ->  Work.
      - HDMI Audio ->  Work.
      - WiFi/Bluetooth ->  Work. Replaced.
      - Ethernet (1st) ->  Work.
      - Ethernet (2nd) ->  Not work.
      - USB3.0 ->  Work.
      - Sleep ->  Work.
       
       
      Todo
       
      - Make audio work.
      - Make HDMI audio work.
      - Test DisplayPort.
      - Make second ethernet work.
      - Replace Wifi/Bluetooth.
       
       
      What you need to install

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


      How create create the install flash drive
       
      Prepare install flash drive

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

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

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


      Install bootloader

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


       
       
      Make things works

      Will be created a partition named EFI and mounted in Desktop. Edit the /Volumes/EFI/CLOVER/config.plist inside this new partition, open with Clover Configurator (used 5.2.1.0)
       
      Full UHD630 Acceleration
       
      config.plist (Clover Configurator): 
       
      - Uncheck: Acpi - Fixes - FixDisplay
      - Uncheck: Acpi - Fixes - AddHDMI
       
      - Change value: Gui - Screen Resolution to 3840x2160 (Your screen resolution, mine is 4k)
      - Change value: Rt Variables - CsrActiveConfig to 0x3
      - Select value: SMBIOS - Up/Down arrows - iMac18,1 - Intel Core i5-7360U @ 2.30Ghz (I know, it's not our processor, but is that option)
       
       
      Download those Kexts and put in /EFI/CLOVER/kexts/10.14/
       
      - Download the Lilu.kext from here. I used the version 1.2.7.
      - Download the WhateverGreen.kext. I used the version 1.2.3.RELEASE.
       
       
      All USBs (2.0, 3.0, Type-C, internal)
       
      config.plist (Clover Configurator): 
       
      - Add value: Kernel and Kext Patches - KextsToPatch:
                       Name*: com.apple.driver.usb.AppleUSBXHCI
                       Find* [HEX]: 83FB0F0F 83030500 00
                       Replace* [HEX]: 83FB0F90 90909090 90
                       Comment: disable port limit in XHCI kext (credit PMHeart)
                       MathOS: 10.14.x

       
       
      Sleep/Wake
       
      config.plist (Clover Configurator): 
       
      - Check: Boot - Arguments - dart=0
       
       
      Audio onboard and HDMI
       
      config.plist (Clover Configurator): 
       
      - Change: Device - Audio Injection - layout-id to 7
       
      Download those Kexts and put in /EFI/CLOVER/kexts/10.14/
       
      - Download the Lilu.kext from here. I used the version 1.2.7. (already installed above)
      - Download the AppleALC.kext from here. I used the version 1.3.2.
       
       
      Wifi and Bluetooth (DW1560 / BCM94352Z)
       
      Download those Kexts and put in /EFI/CLOVER/kexts/10.14/
       
      - Download the FakePCIID.kext and FakePCIID_Broadcom_WiFi.kext from here. I used the version 2018-1014.
      - Download the BrcmFirmwareRepo.kext, BrcmPatchRAM.kext and BrcmNonPatchRAM.kext from here. I used the version 2018-0505.
       
       
      Mandatory Kexts
       
      Download those Kexts and put in /EFI/CLOVER/kexts/10.14/
       
      - Download the FakeSMC.kext from here. I used the version 2018-0915.
      - Download the IntelMausiEthernet.kext from here. I used the version 2018-0424.
       
       
      Put the Clover installer on the flash drive too.
       
      Now you can start the instalation without problem (I guess).
       
       
      How install
       
      UEFI Setup Configuration and Installation

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

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

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

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

      After install

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

      Post installation

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

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

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

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

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

      The flash drive EFI partition is unmounted. Mount with terminal "sudo diskutil mount /dev/rdiskXs1". To know what X is, use "diskutil list", most likely is 1.
       
      Last step
       
      Copy all Kexts from flash drive to /Library/Extensions, with those commands in Terminal:
      sudo cp -R /Volumes/EFI/EFI/CLOVER/kexts/10.14/* /Library/Extensions/ sudo chmod -R 755 /Library/Extensions sudo chown -R root:wheel /Library/Extensions sudo kextcache -system-prelinked-kernel sudo kextcache -system-caches Restart the system.
       
       
      It's done!

       
      And last but not least
       
      I would like to thank the following community members, by making these dream possible:
      @crushers, @snatch, @apianti, @blackosx, @blusseau, @dmazar, @slice2009, @autumnrain, @phpdev32, @EMlyDinEsH, @RehabMan, @Scellow, @mitch_de, @Shailua, @Andy Vandijck, @maxfierke, @ArturXXX, @LexHimself, @brumas and all others members involved directly or indirectly.
       
    • By am_yvr
      Asus Prime B360M-A or Asus Prime H310M-E :

      Which of these two motherboards would give less hassle in a Hackintosh build - requiring fewer after install fixes/updates to get everything working in Mojave or High Sierra?
       
      These are the only two Asus models that I can afford, fit the form factor in my build, and already have had a BIOS upgrade by Asus to 9th-generation - if I want to replace the CPU with an i9 in the future (for now I'll be using i7-8700 or even i3-8350k but I want to future proof a bit)
       
      Thanks guys!
    • By thomazella
      Hi guys. Just wanted to say this is my new favorite forum for mac hacks

      I'm trying to get mojave to work, and using the guide's (moderator made, on the front page) clover folder I ALMOST got it! T.T

      There's something still wrong tho. lol.

      - Install to a HDD formated as case-sensitive APFS goes black at 2 minutes remaining. Is it supposed to fill the progress bar 100%? If so then I have a problem.
      - Assuming the install went well, I tried to boot to "MacOS Prebooter" from clover screen and got that error.

      I have a Z170m ASUS, awesome board. I'm sure it can be done. With Intel 6700k.
      Latest clover. Guide's clover config!!

      What do you guys think?
      - mobo config problem
      - other hardware thing (I have many harddrives connected?)
      - clover config
      - need some driver/kext
      - something else

      THANK YOU!

      PS: I've tried upgrading with the App store download on a Sierra system to arrive in the same screen, with the same error.
      I'll also spend some time today searching the forums. Just busy atm, and thanks for any help or tips!!

    • By JoeMaya
      Hi. I'm currently on AppleALC.kext with layout ID 3. Clover's a boot argument contains alcid=3. 

      Problem:
       
      Case: Happens only in case of earphones.
      Problem description: The sound is somewhat like an echo where I'm hardly able to hear the vocals of a song. And the music sounds as if it's being playing under water. I later went to audio devices and tried checking the checkbox shown in the image below. I did improve the sound and I was finally able to hear vocals of a song in a much better way, however, it still doesn't sound like a proper sound. Is there any more configuration that I need to make? 

      The reason I'm able to differentiate the bad and the good sound output is because on High Sierra, using AppleHDA patch, the sound worked fine using AppleHDA patcher.

       

×