Jump to content
ErmaC

Clover General discussion

18,552 posts in this topic

Recommended Posts

Dear Pike,

 

I don't get very much information about it. Could you possibly take a look at the new el capitan injection method of clover? Does it correspond with your newly found exploit? If not, could you please help me or show me some way to implement it (in pseudo code). I most possible can take it from there. I don't want to discuss the needs of security here, but I want to have it most secure as possible.

Up until now, I did "read" all the source codes and compiled everything from that, if I wanted to install anything on my systems.

 

Thanks in advance.

I'm not aware of any new method to inject kexts, but there are a couple of ways to let the old method work. One of them is already being used by the kernel patcher. This was also one of the ways I found earlier, but I did not stop there. A real injection is on its way. It's a matter of time, but time is not on my side because I am busy with other stuff as well.

Share this post


Link to post
Share on other sites
Advertisement

Hi, can anyone give some explanation of what the booterconfig flag is for? It is always included, and always has the value 0x28. I know it is needed but how is it different from csractiveconfig and what other values are possible apart from 0x28? Thanks.

 

 

You must be confused. You looked at boot_args->flags instead of boot_args->csrCapabilities These are not the same ;)

He asked about  boot_args->flags. The answer is correct.

Share this post


Link to post
Share on other sites

As Slice said, he asked for bootercfg and that is ->flags... what has changed is that PendingConfig was renamed and InstallUi added.

Also, there is no new way of injection but only a kernel patch that jumps past the check for the kext-management entitlement.

Share this post


Link to post
Share on other sites

So what are the safest BooterConfig and CsrActiveConfig entries that still allow kext injection and normal booting?  :rolleyes: Can I switch to 0x2 or something like that to improve security? 

 

Mine are standard 0x28 and 0x67

 

I have enabled rootless after rebuilding kext caches. 

Share this post


Link to post
Share on other sites

So what are the safest BooterConfig and CsrActiveConfig entries that still allow kext injection and normal booting?  :rolleyes: Can I switch to 0x2 or something like that to improve security? 

 

Mine are standard 0x28 and 0x67

 

I have enabled rootless after rebuilding kext caches. 

 

iRipper

 

It just depends on what you need to make your system work. Personally I only require 0x28 and 0x1 so that I can inject a couple kexts with Clover and Install a few unsigned kexts after the OS X install process.

 

Good luck,

 

-Robert

Share this post


Link to post
Share on other sites

He asked about boot_args->flags. The answer is correct.

No. Flags didn't change. Only one item was renamed since Yosemite, but the checks in the code are still the same as in Yosemite. What actually did change was boot_args->csrCapabilities There you'll find items that were first introduced in El Capitan.

Share this post


Link to post
Share on other sites

csrCapabilities is a bitmask with all available bits set. So, afaik it just gets set to CSR_VALID_FLAGS. Also, yes there is something new in boot_args.flags which is kBootArgsInstallUi.

Share this post


Link to post
Share on other sites

is it just me? .... tried to build 3262 and got this error:

 

Processing meta-data .

 

build.py...

/Extra/Clover_Install/CloverGrowerPro/edk2/Clover/Clover.dsc(...): error 4000: Instance of library class [VarCheckLib] is not found

in [/Extra/Clover_Install/CloverGrowerPro/edk2/MdeModulePkg/Universal/Variable/RuntimeDxe/VariableRuntimeDxe.inf] [X64]

consumed by module [/Extra/Clover_Install/CloverGrowerPro/edk2/MdeModulePkg/Universal/Variable/RuntimeDxe/VariableRuntimeDxe.inf]

Share this post


Link to post
Share on other sites

is it just me? .... tried to build 3262 and got this error:

 

Processing meta-data .

 

build.py...

/Extra/Clover_Install/CloverGrowerPro/edk2/Clover/Clover.dsc(...): error 4000: Instance of library class [VarCheckLib] is not found

in [/Extra/Clover_Install/CloverGrowerPro/edk2/MdeModulePkg/Universal/Variable/RuntimeDxe/VariableRuntimeDxe.inf] [X64]

consumed by module [/Extra/Clover_Install/CloverGrowerPro/edk2/MdeModulePkg/Universal/Variable/RuntimeDxe/VariableRuntimeDxe.inf]

 

I'm getting the same error.

Share this post


Link to post
Share on other sites

For general info, here are the SIP values set by each option of Apple's csrutil utility from recovery partition with DP7:

                                    hex     n/a    nvram  dtrace intern debug  pid    fs     kexts  nvram csr-active-config
csrutil enabled --no-internal       00      0      0      0      0      0      0      0      0      %00%00%00%00
csrutil enabled                     10      0      0      0      1      0      0      0      0      %10%00%00%00
csrutil enable —-without kext       11      0      0      0      1      0      0      0      1      %11%00%00%00
csrutil enable —-without fs         12      0      0      0      1      0      0      1      0      %12%00%00%00
csrutil enable —-without debug      14      0      0      0      1      0      1      0      0      %14%00%00%00
csrutil enable —-without dtrace     30      0      0      1      1      0      0      0      0      0%00%00%00
csrutil enable —-without nvram      50      0      1      0      1      0      0      0      0      P%00%00%00
csrutil disabled                    77      0      1      1      1      0      1      1      1      w%00%00%00

Other settings
disabled (no internal)              67      0      1      1      0      0      1      1      1      g%00%00%00

Of course you are free to use any other value that you want for your hack, for example 0x01, 0x03.

Share this post


Link to post
Share on other sites

clover hot key option in custom entry woking on legacy bios system???

Here is custom entry and i cannot use hotkey option

key>GUI</key>
<dict>
<key>Custom</key>
<dict>
<key>Entries</key>
<array>
<dict>
<key>Disabled</key>
<false/>
<key>FullTitle</key>
<string>Windows</string>
<key>Hidden</key>
<false/>
<key>Ignore</key>
<false/>
<key>Path</key>
<string>\EFI\Microsoft\Boot\bootmgfw.efi</string>
<key>Type</key>
<string>Windows</string>
<key>Volume</key>
<string>EFI</string>
<key>VolumeType</key>
<string>Internal</string>
</dict>
<dict>
<key>Disabled</key>
<false/>
<key>FullTitle</key>
<string>OSX Yosemite</string>
<key>Hidden</key>
<false/>
<key>Ignore</key>
<false/>
<key>InjectKexts</key>
<string>Detect</string>
<key>NoCaches</key>
<false/>
<key>Type</key>
<string>OSX</string>
<key>VolumeType</key>
<string>Internal</string>
</dict>
<dict>
<key>Disabled</key>
<false/>
<key>Hidden</key>
<true/>
<key>Hotkey</key>
<string>o</string>
<key>Ignore</key>
<false/>
<key>InjectKexts</key>
<true/>
<key>NoCaches</key>
<false/>
<key>Title</key>
<string>OSX Recovery</string>
<key>Type</key>
<string>OSXRecovery</string>
<key>VolumeType</key>
<string>Internal</string>
</dict>
<dict>
<key>Disabled</key>
<false/>
<key>Ignore</key>
<false/>
<key>Path</key>
<string>\EFI\ubuntu\grubx64.efi</string>
<key>Title</key>
<string>Linux</string>
<key>Type</key>
<string>Linux</string>
<key>Volume</key>
<string>EFI</string>
<key>VolumeType</key>
<string>Internal</string>
</dict>
<dict>
<key>Disabled</key>
<false/>
<key>Hidden</key>
<true/>
<key>Hotkey</key>
<string>m</string>
<key>Ignore</key>
<false/>
<key>Path</key>
<string>\EFI\Aomei\AomeiBoot.efi</string>
<key>Title</key>
<string>AOMEI Recovery Partition</string>
<key>Type</key>
<string>Windows</string>
<key>Volume</key>
<string>EFI</string>
<key>VolumeType</key>
<string>Internal</string>
</dict>
</array>
</dict>

Share this post


Link to post
Share on other sites

Guys, do we need to manually specify a certain C-state (Clover Configurator)? Or is it enough to check the box for "Generate Cstates" and Clover will pick one automatically? And if so, which one will it pick?

 

I was trying to debug some sleep issues that I'm having with El Capitan (but not with any other operating system) and I started reading about this on the internet. So I was just wondering if the user has to select a specific C-state for this case, or if it makes any difference whatsoever if he doesn't.

Share this post


Link to post
Share on other sites

What's your Sleep issue, my El Capitan install panics every time I try and wake it from sleep since installing PB5?

Well, mine doesn't go to sleep in the first place. I don't have kp anymore.  I suddenly had one since I installed PB5 again (fresh install), with no apparent reason whatsoever, and I solved it easily by clearing my kernel cache.

 

About the sleep issue itself, it turns off most of my components, but the CPU and the video card are still on. So basically half of my computer is still on (I can't interact with it though). This does not occur with Yosemite. And previous issues I had with Yosemite, were caused by the graphics card. Now, I know the latest Nvidia graphics card driver is in Beta, so...I'm waiting for an update on that, in case this might have anything to do with the driver. Anyway, it does the same thing with or without the driver installed. So, that's why I was starting debugging other causes for lack of sleep. But I'm not sure the lack of C-states is one of them. Still I was curious to know if we need to add a specific state manually or if it makes any difference if we don't.

Share this post


Link to post
Share on other sites

For general info, here are the SIP values set by each option of Apple's csrutil utility from recovery partition with DP7:

                                    hex     n/a    nvram  dtrace intern debug  pid    fs     kexts  nvram csr-active-config
csrutil enabled --no-internal       00      0      0      0      0      0      0      0      0      %00%00%00%00
csrutil enabled                     10      0      0      0      1      0      0      0      0      %10%00%00%00
csrutil enable —-without kext       11      0      0      0      1      0      0      0      1      %11%00%00%00
csrutil enable —-without fs         12      0      0      0      1      0      0      1      0      %12%00%00%00
csrutil enable —-without debug      14      0      0      0      1      0      1      0      0      %14%00%00%00
csrutil enable —-without dtrace     30      0      0      1      1      0      0      0      0      0%00%00%00
csrutil enable —-without nvram      50      0      1      0      1      0      0      0      0      P%00%00%00
csrutil disabled                    77      0      1      1      1      0      1      1      1      w%00%00%00

Other settings
disabled (no internal)              67      0      1      1      0      0      1      1      1      g%00%00%00

Of course you are free to use any other value that you want for your hack, for example 0x01, 0x03.

 

 

So what are the safest BooterConfig and CsrActiveConfig entries that still allow kext injection and normal booting?  :rolleyes: Can I switch to 0x2 or something like that to improve security? 

 

Mine are standard 0x28 and 0x67

 

I have enabled rootless after rebuilding kext caches. 

 

@iRipper

 

Since Blackosx's post i've been using the following settings with same results, only the SIP status messages are now correct and assume will continue to work with future OS X El Capitan updates.

 

CsrActiveConfig=0x11

BooterConfig=0x28

System Integrity Protection status: enabled (Custom Configuration).

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

This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.

Good luck!

Share this post


Link to post
Share on other sites

Ok so after finally getting my dual boot going with Clover.... It is now hiding my "Microsoft Reserved" partition which I was using to boot Win7.

 

The change that caused this? I switched out my storage drives. Yup that's it. It was working fine immediately before. What gives? Is there something I can do to force it to show it? 

 

Edit:

Something I did under OS X made my windows unbootable. This has never happened before in any install I've done, ever. Or maybe I did something under Windows... Ugh I hate windows. Nevertheless a reinstall got me going.

Share this post


Link to post
Share on other sites

What's your Sleep issue, my El Capitan install panics every time I try and wake it from sleep since installing PB5?

Is it  correct you are still loading changed or non apple signed kexts in S/L/E when likely you should be looking at other ways to get your o/b audio working. Further more have you done a clean install and tested El Capit without any additional apps loaded?

One has to appreciate that El Cap is a work in progress, but you would be well advised to respect the integrity of S/L/E beit security or otherwise one needs to read up on the changes announced at WDC - they are well documented

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 gengik84
      Ciro82==>>Thanks
      Uno dei tre Requisiti:
      Hack funzionante Mac vero Macchina virtuale Impostazioni Bios per il boot:
      Cercate una voce  del tipo “Sata Mode”e settatela  in AHCI
      Secure Boot: disabilitare o altri sistemi operativi
      CSM: UEFI o LEGACY, oppure a secondo del tipo di installazione
      VT-x / VT-d disable
      *Nota: Secure boot e csm valido solo per bios UEFI
      Materiale Occorrente 
      "OS X (Versione App.Store)”
      USB 8GB  *nota: nel caso di usb superiori dovrà essere partizionata, in modo da avere una partizione su cui "lavoreremo,di questa dimensione
      ShowAllfiles 
      kext Wizard 
      Bootloader Clover_2.3k_r xxx:                   http: //sourceforge.n.../cloverefiboot/
      Clover Configurator:                                    http: //mackie100proj...a.org/download/
      FakeSmc.kext:                                            https://github.com/kozlek/HWSensors/releases
      In allegato,a fondo pagina troverete un "pacchetto" contenente : ShowAllfiles, Kext Wizard, FakeSmc.kext: 
      App alternative:
      ESP Mounter Pro: per montare la partizione EFI
      Vi illustrerò tre metodi per creare la usb, ma sono ben distinti… quindi usatene soltanto uno
      Metodo 1: “Install Mac_OS_X.command” Metodo 2: “Create Install Media di Apple” Metodo 3:  Metodo Manuale Alla fine delle preparazione dell’installer, tutti i metodi necessitano l’installazione del Bootloader Clover sulla a vostra USB.
      “CONDIZIONI OBBLIGATORIE”
      PUNTO 1: che la vostra usb sia stata preventivamente nominata USB (caratteri maiuscoli) Tabella di partizione GUID e la formattazione in  Mac esteso Journaled.
      PUNTO 2: che l’installer di OSX si trovi in Applicazioni
      Utility Disco 
      Selezionate la pendrive, andate su “partizione”, selezionate “1 partizione”, impostate Mac OS esteso journaled e date il nome USB, poi in basso cliccate su opzioni e scegliete Tabella partizione (GUID), poi “applica”.
      Immagine 
      Riporto nuovamente l’operazione sopra citata adoperando dal nuovo Utility Disco introdotto su El Capitan.
      Rimane ovviamente invariato nome della usb in ==>> USB (maiuscolo), la formattazione in Mac esteso Journaled e sia la mappa partizione in GUID
      Da utility disco selezionate la usb, cliccate su inizializza.
      dal menù a tendina scegliete la relative impostazioni
      Immagine  
      Procedura effettua da High Sierra è la stessa della precedente, l'unica attenzione e operazione da aggiungere in primis  è cliccare nel menù a tendina in alto sulla sinistra di utility disco e selezionare "mostra tutti i dispositivi"
      Immagine 
       
      =====================
        METODO 1: "Install_Mac_OS_X.Command" Lo script che trovate allegato in fondo alla guida permette la creazione dell’installer in maniera automatica
      Include la possibilità di scelta di tre versioni di osx
      Yosemite El Capitan Sierra Il risultato finale è come quello del metodo "manuale" descritto nella guida, per cui l'installazione avverrà in un solo passaggio, non in due come con il metodo createinstallmedia. 
      Offre inoltre la possibilità di inserire un kernel patchato, utile, per esempio, per chi usa AMD.
      Rimane invariato il nome dato alla usb in USB, mappa partizione e tipo di formattazione
      Se la vostra usb non sarà rinominata nel modo corretto, verrete avvisati dal terminale, quindi non dovrete far altro che apportare la relativa modifica e rilanciare nuovamente lo script
      Esempio
      ===========================
      Metodo 2 
      L'intento è quello di usare la procedura fornitaci direttamente da Apple, "createinstallmedia", introdotta  con Mavericks. 
      Tale metodo prevede l’uso del terminale che via via se ne sta perdendo il “valore e l’uso”
      Inizialmente per i neofiti potrà sembrare problematico ma alla fine non è così.
      Durante il post installazione alcune operazioni ne richiedono l’ uso.
      Perciò mi sono chiesto perchè, qualora uno volesse, non far conoscere da subito un po’ questo “strumento”???
      Per favorirvi vi ho allegato i comandi già  “pronti”, i quali li potrete copiare ed incollare sul terminale.
      A questo punto aprite il terminale, copiate ed incollate il comando sottostante e premete invio, digitate la vostra password e premete nuovamente invio.
      Comando per creare USB con Yosemite:
      sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --nointeraction  
      Comando per creare USB con El Capitan
      sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app --nointeraction Comando per creare USB con Sierra 
      sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ Sierra.app/ --nointeraction Per creare USB con Hight Sierra o Mojave usate --> C_I_M (aggiornato per 10.14)
       
      Funziona con il drag & drop sul terminale, in questo caso non vi è necessità che la usb sia nominata in un determinato modo ed essendo basato su create install media ovviamente funziona da 10.9 a 10.14.... 
      BENE…IL PROCESSO DI CREAZIONE E’ INIZIATO…
      AVREMO CIRCA 20/30 MINUTI DI TEMPO LIBERO A CUI DEDICARSI A CIO’ CHE VOGLIAMO………………………………………..  
      COLGO L’OCCASIONE PER FARVI NOTARE LA VELOCITA’ E LA SICUREZZA DI QUESTO METODO
      CONFRONTATE QUESTO CON IL TERZO METODO E NOTERETE CHE CON UN SOLO PASSAGGIO, OSSIA IL COMANDO DATO AL TERMINALE, FACCIAMO IN UNA SINGOLA OPERAZIONE TUTTI I VARI STEP DESCRITTI SULL’ ALTRO METODO.
      DETTO QUESTO, MOLTO IMPORTANTE E’ SOTTOLINEARE CHE COSI’ FACENDO EVITEREMO ERRORI  DI DISTRAZIONE RIGUARDO AI PASSAGGI O FRAINTENDIMENTI.
      Immagine 
      Potete adesso passare ad installare il bootloader Clover sulla vostra usb.
      *NOTA*:
      Avendo usato questo metodo l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      =========================
      METODO "MANUALE"....  (lascio per futura memoria-Compatibile fino a 10.12)
      ==========================
      Bootloader
      **Nota:** Installazione in UEFI  dipenderà dalla scheda madre in vostro possesso, quindi se non supporta tale opzione , il bootloader dovrà essere installato in  modalità Legacy.
       Vi invito, qualora non sapeste questa informazione, a recarvi nel sito ufficiale del produttore e controllare le informazioni a riguardo
      Fatto questo dobbiamo installare  Clover sulla usb.
      A seconda del tipo di Bios o al tipo di installazione che vogliamo fare UEFI o Legacy avremo ovviamente configurazioni diverse in questa fase.
      Lanciate il pkg.
      Immagine 

       
      Cambiate la destinazione di installazione ad USB oppure Install Mac_OS_X (a secondo del tipo di creazione eseguita)
      Successivamente clicchiamo su "Ad Hoc"
      Per Installazione UEFI
      Mettete i flag   : Installazione solo per avvio UEFI
                               : installare Clover nella ESP
                               : Driver64UEFI  AptioMemory --> (consigliato) 
                               : Driver64UEFI  ApfsDriverLoader --> (consigliato) --> sostituisce l'uso del driver apfs.efi
                               : Selezionate l'altri driver come da successiva immagine,
       
      *Nota: Altri driver che si possono usare  al suo posto  sono:
       informazioni 
       
      Proseguite con l’installazione.
      Immagine 
      ** Ricordate che avrete accesso a questa cartella dopo aver montato la partizione EFI**
      ===========================
      Per installazione Legacy
      Immagine 
      ===========================
      Impostazione per config.plist:
      Con clover configurator “montate” la partizione EFI della usb.
      1) Per fare questo nel menù di sinistra, cliccate su “Mount EFI”
      2) individuate la partizione relativa alla vostra usb, a questo punto montiamo la relativa partizione EFI  selezionando l’apposito pulsante “Mount Partition”
      Immagine 
      3) Successivamente cliccate su “Open Partition”.. recatevi in EFI/Clover ed aprite il config.plist
      4) Sezione ACPI: Disabilitate tutti i fix sia del menù 1 che del menù 2
      Immagine 
      5) Sezione BOOT: Sole se si sta installando Yosemite mettete il flag su kext-dev-mode=1
      Immagine 
      6) Sezione RT Variables: Se si sta installando El Capitan oppure Sierra, aggiungere i valori: BooterConfig= 0x28, CsrActiveConfig= 0x67
      Immagine 
      7) Sezione System Parameters: Su inject kext mettete YES
      Immagine 
      ===========================
      Nota: Su El Capitan, è stato introdotto SIP (System Integrity Protection)
      Info:
      ===========================
      Recatevi in EFI/Clover/kext/10.x 
      X= alla versione di osx che state installando. Per esempio se installerete Yosemite dovrete recarvi nella cartella 10.10, con El Capitan in 10.11….ecc
      Se non ci fosse tale cartella, createla e nominatela voi a “modo”.
      Copiatevi all’interno FakeSmc.kext
      *Nota se venite già da altre vostre configurazioni, oltre kext sopra citato ,potete mettere gli altri necessari per il vostro hardware
      Stessa cosa se avete DSDT e/o SSDT potete copiarli in EFI/Clover/Acpi/Patched
      Immagine 
      
      Per High Sierra:
      Scaricare il driver apfs.efi a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
       
      Per chi volesse continuare ad usare HFS vi rimando a questo post:
        Come installare High Sierra in HFS direttamente dalla usb  
      Utenti Laptop:  Nel 99% è obbligatorio disattivare la grafica discreta Nvidia/Amd per installare questo nuovo osx
                                     Quindi aggiungete --> SSDT-Disable_DGPU.aml.zip
                                     in EFI/Clover/acpi/Patched della usb
      --------------------------------------------------------------------
      Per Mojave:
      Scaricare il driver apfs.efi per 10.14 a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
      Versione di clover non antecedente a V_4015
      Volete usare HFS?
      E' possibile fare un installazione diretta su altro disco o partizione, nel caso può essere usato anche per effettuare aggiornamenti...
      nel caso guardate...
       Mojave in HFS 
       Oppure direttamente da usb  
       
      Fatto questo avrete la vostra USB bootable per installare OSX.
      ………Non scordatevi Fakesmc.kext da mettere nella relativa cartella…. senza il quale non farete mai il Boot......
      *NOTA: se usato il terminale per la creazione della usb, l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      **NOTA** Se avete processori Broadwell,Skylake o Kabylake...usate FakeSmc.kext e relativi sensors che trovate all'interno del secondo pacchetto.. (potete usarlo anche sui precedenti senza problemi, essendo una versione più aggiornata ha ulteriore supporto per le cpu più recenti)
      Update: Fakesmc e sensors versione 6.26
      Post installazione... post #2           
       Buon Hack….. 
      Aggiornamento:Install_Mac_OS_X.command.zip (compatibile da 10.10 a 10.12)
      le info le trovate a questo post
      Ringrazio @Ciro82 che mi ha aiutato nel preparare questa guida.
      Pacchetto.zip
      Pacchetto-2.zip
      apfs.efi-10.13-NoLog.zip
      Pacchetto-Fake+Sensors 6.26.1440.zip
      apfs.efi-10.13.1-No_LOG.zip
      apfs.efi-10.13.2_No_Log.zip
      apfs.efi-10.13.3-No_Log.zip
      apfs.efi-10.13.4-No_Log.zip
      apfs.efi-10.13.5_No_Log.zip
      C_I_M.zip
       
      apfs.efi-10.14-beta1_No_Log.zip






    • By tbianco
      Ho comprato da poco un Acer Aspire 5750G e girando su internet ho trovato la cartella efi che garantiva quasi tutto funzionante perfino il wifi (https://github.com/zipippino/HighSierraAspire5750G).
      Allora felicissimo installo macOS e a parte incappare in errori stupidi, riesco a fare tutto, ma quando sono riuscito ad installare clover Legacy e sostituendo la roba con la 'mia' efi clover si avvia ma macOS no, semplicemente non carica (si nota anche pk la spia dell'hdd che dice se è in attivitá è spenta.
      Qualcuno può aiutarmi?
    • By RougeOne
      Budget Workstation MacOS 10.14.1 build: z370 AORUS Gaming 5 - i5-8600K - RX 580 - UHD 630
      flawless iGPU/dGPU integration, fast FCPX editing/rendering, great overall performance for ~$1200 / ~£1000
       
      I'm gonna come straight out and admit it - I used newb tools which are considered taboo on InsanelyMac, and so this isn't so much an installation guide as it is a green flag to anyone considering the same hardware. My first and previous Hackintosh project was just over ten years ago and this site was massively helpful, so this is my (very small) way of giving back.
       
      EFI DIRECTORY
      http://s000.tinyupload.com/index.php?file_id=97606131925137056003
       
      HARDWARE
      CPU: Intel i5-8600K 3.6GHz hexacore (contains UHD 630 iGPU)
      CPU Cooler: be quiet! Pure Rock Slim (no paste needed, and fan facing front)
      Mobo: GIGABYTE z370 AORUS Gaming 5 (WIFI)
      RAM: 1x 8GB CORSAIR Vengeance LPX C16 2666MHz (in first slot)
      GFX Card: Sapphire RX 580 NITRO+ SE
      SATA: used ports 0, 1, 3, 5 (HDD problems when connected to port 4)
      HDD: generic
      DVD Drive: generic
      PSU: EVGA 500W Semi Modular (but you should get 650W!)
      Case: CoolerMaster CM590 III
      Fans: 2x stock case fans (one sucky on front, one blowy on back), 3x be quiet! BL046 120mm fans (two blowy on top, one sucky on front). Airflow near-perfectly balanced.
       
      ADVICE
      With the Clover configuration, you want to pay close attention to all things relating to graphics. There are some specific settings for ACPI, Boot, Devices and Graphics which should be copied exactly in order to get the iGPU and dGPU to work in perfect harmony. For instance, make sure you use ig-platform-id 59120003 rather than 59120000 if you want FCPX to be usable. With the right settings, FCPX will not only run, but run flawlessly.
       
      I was not able to figure out how to make NVRAM/PRAM behave itself, and I got errors when I tried to issue relevant commands. As a result, I could not get iMessage to work properly. It worked precisely once, on my first installation attempt. This Clover configuration therefore has no consideration whatsoever toward iMessage reliability - if you can get NVRAM/PRAM working properly on this hardware, please do edit the config as you see fit.
       
      Onboard WiFi does not work. There is no driver for it. I'm using wired ethernet to a bridge router as it was cheaper than getting a compatible PCI card.
       
      Audio is working well after I installed the z370 audio patch, then the ALC1220 codecs, then AppleALC.
       
      With kexts for generic 3rd party SATA and generic 3rd party eSATA, my HDDs and DVD drive work perfectly well.
       
      Sleep/Wake functions run perfectly. iCloud functions run perfectly. Shutdown leaves the mobo LEDs on, annoyingly.
       
      Overall, this system appears to run about as well under MacOS 10.14 Mojave as it does under Windows 7. I would solidly recommend this build to anyone looking to build a computer for workstation purposes, on a budget.
    • By JLMOX
      I think, at this point converting to hfs+ is out of the question, Apple has been pushing the apfs file policy very aggressively, so does anybody solved the missing "Boot macOS from Mojave " (this last word may be different). I have installed the latest clover in HDD and USB, but I can only see 3 Mac Os related tabs but not the one for actually loading the Mojabe mac OS. I updated high sierra to Mojave and everything went fine. My laptop (Dell E6530) booted up normally, Mojave system loaded up, I finished the setup and spent sometime exploring. I updated clover to the latest version and turned of machine. When I restarted, I noticed Clover did not have an option for booting into the system like High sierra had it. I tried adding the apfs.efi or the ApfsDriverLoader-64.efi driver to the clover efi folder in the HDD and also tried with a USB clover installation and the result is the same: No boot option for the Mojave OS. I used the recovery option and I was able to explore the partion where the system is located but that´s as far as I could go. Does anybody has an idea of what happened?

    • By Allan
      That's unbelievable awesome

       
      Link: https://www.macupdate.com/app/mac/61068/clover-theme-manager
×