Jump to content
ErmaC

Clover General discussion

18,354 posts in this topic

Recommended Posts

Posted (edited)

Updated to latest release on source forge and now clover takes much longer to start.

 

Here's an extract from bdmesg:

3:241  0:000  === [ ScanLoader ] ========================================
3:241  0:000  - [02]: 'EFI'
3:264  0:022          AddLoaderEntry for Volume Name=EFI
3:264  0:000          skipped because entry is hidden
3:264  0:000  - [05]: 'Data HFS'
3:277  0:013  - [06]: 'Shared'
15:904  12:626  - [07]: 'Preboot'
15:907  0:003          AddLoaderEntry for Volume Name=Preboot
15:911  0:004      Check if volume Is Hibernated:

"Shared" is an exfat partition. I don't have exfat efi drivers. Booting CloverEFI. Not sure why it's taking that long. Disk activity light stays on during that delay.

 

Also, when entering a boot arg in Clover GUI, the GUI freezes and disk activity light comes on for a few seconds. 

 

Edit: Downgrading to 4458 fixes the problem.

Edited by Dr. Hurt

Share this post


Link to post
Share on other sites
Advertisement
On 5/25/2018 at 4:24 PM, chris1111 said:

Hi MR Slice

The most recent I've found and that works for old mac in (Legacy ESP) is Clover r4452

Hope you can find where is the solution

4452.thumb.png.edbaa122d85b63d6b4625bfb244d2636.png

Hi Chris,

Is it true that the problem arises only with your compilation and no problem with official binaries?

Share this post


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

Hi Chris,

Is it true that the problem arises only with your compilation and no problem with official binaries?

I wil try now SF Package and report

Share this post


Link to post
Share on other sites
Posted (edited)

Slice You are right it is my compilation because SF Package works 

edit ***

the last SF package I just used r4497 is it compile with UDK2018?
or else EDK2?

Edited by chris1111

Share this post


Link to post
Share on other sites

UDK2018 but with patches defferent from those propesed by Zenith432 which is included into svn.

So I am not sure if they are good.

Share this post


Link to post
Share on other sites
Posted (edited)
On 5/27/2018 at 11:04 AM, Slice said:

UDK2018 but with patches defferent from those propesed by Zenith432 which is included into svn.

So I am not sure if they are good.

Ok thank you Slice for your time

Edit**

My compile issue about ESP and old macOS is resolved

 

Edited by chris1111

Share this post


Link to post
Share on other sites
Posted (edited)

Hi,

 

Strange issue. I update Clover to r4506 (UDK2018 compile). But it display r4495 on start screen :worried_anim: Clover_Install_Log.txt attached

Clover_Install_Log.txt

 

Edit: (EDK2 compile) no issue

Edited by Matgen84

Share this post


Link to post
Share on other sites

Since Clover REV 4502 "all drivers must be optional and available for UEFI only boot".

Does this mean that we can't have XhciDxe-64 for USB3 cards to work in clover gui in legacy mode?

 

Share this post


Link to post
Share on other sites
Posted (edited)
On 5/25/2018 at 5:51 AM, Slice said:

I will make the change in Clover sources today evening.

And I think the problem is

<key>Inject</key>

<string>19</string>

 

but no problem with

<key>Inject</key>

<integer>19</integer>

This change disables audio for the Clover installed base.

Until 4497,

<key>Inject</key>

<string>19</string>

supported 19, Detect, No, 883, 0x373, 1, etc. 

 

Why did 4497/Devices/Audio/Inject/Type=String stop working?

 

Clean 4497 installed config.plist (attached) shows 

<key>Inject</key>

<string>0x0887</string>

4497-config.plist.zip

 

Edited by toleda

Share this post


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

This change disables audio for the Clover installed base.

Until 4497,

<key>Inject</key>

<string>19</string>

supported 19, Detect, No, 883, 0x373, 1, etc. 

 

Why did 4497/Devices/Audio/Inject/Type=String stop working?

 

Clean 4497 installed config.plist (attached) shows 

<key>Inject</key>

<string>0x0887</string>

4497-config.plist.zip

 

Rev 4500

enable HDA injection if codecID set as string

Share this post


Link to post
Share on other sites
Posted (edited)
15 hours ago, Mr MagOO said:

Since Clover REV 4502 "all drivers must be optional and available for UEFI only boot".

Does this mean that we can't have XhciDxe-64 for USB3 cards to work in clover gui in legacy mode?

 

Good question... are all drivers now embedded in legacy hence its only for UEFI only?

Edited by ellaosx

Share this post


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

Rev 4500

enable HDA injection if codecID set as string

So we can use

<key>Audio</key>
        <dict>
            <key>Inject</key>
            <integer>28</integer>
        </dict>

 

or

<key>Audio</key>
        <dict>
            <key>Inject</key>
            <string>563</string>
        </dict>

 

am i reading correctly?

 

Info.plist.zip

Share this post


Link to post
Share on other sites

Hello Slice
VBoxHfs-64.efi is suppose to be a Mandatory Drivers, why is it in the list of Drivers to choose?

have a nice day thanks

Share this post


Link to post
Share on other sites
Posted (edited)
10 minutes ago, Allan said:

AFAIK is not mandatory.

There's some differences between HFSPlus and VBox: https://clover-wiki.zetam.org/What-is-what#efi-drivers

Yes it is mandatory before the change commit 4502

if HFSPlus is present the package remove VBoxHfs-64.efi 

Edited by chris1111

Share this post


Link to post
Share on other sites
Posted (edited)

Well, yesterday I've built Clover 4508 from source, just for fun, and everything was ok on my Haswell rig, even with no FixHDA and stuff. Today I upgraded to 4509 (latest official release) and also no more sound issues.

 

@Slice many, many thanks. :)

 

I'm also curious as to why are there so many Drivers now with the newer Clover builds.... I'm still using only one of those, cause that's pretty much all I need to get my computer going, but I was curious why are there so many now?

 

Also, many of them are similar, just different versions. For example OsXAptioFixDrv/OsXAptioFix2Drv/OsXAptioFix3Drv... Do we need all of those? I mean, it's good to have options when you need them. But...question is, DO we need them? And do we need them ALL? Does anyone still need OsXAptioFixDrv instead of OsXAptioFix3Drv for example? And when i say need, I really mean NEED, as in the sense that it doesn't work otherwise?

 

Cause, if not....I would suggest only keeping the latest version (or best version). And when I say "best", I mean the one with the broader spectrum of compatibility. If they are backwards compatible, then, in theory, all you need is the last one, right?

 

I don't know... To me, and you probably already know this, cause I said it before, options are good. But too many options are not. Cause they tend to create confusion.

 

Also, one thing I would recommend, in case it's possible... Let's group those drivers based on their use.

 

For example:


Drivers64UEFI

     Mouse and keyboard (expand/collapse, just like the Drivers64UEFI section itself)

          UsbMouseDxe

          UsbKbDxe

     

     NVRAM emulators

          EmuVariableUefi (not needed if you have hardware NVRAM or OsXAptioFix3Drv in place). Hope I'm not wrong...

 

Anyway, you got the point.

 

Maybe this will also bring some clarity on what each driver is doing. Especially since some of them seem to be missing their description.

 

Also, I guess we could group them into Mandatory and Non-Mandatory. But then again, what's "mandatory" for my system might not be mandatory for yours, due to hardware differences. So... I don't think that's gonna be very accurate.

Edited by arsradu

Share this post


Link to post
Share on other sites

Now that some drivers have become optional have they been removed from the system?, i've been experiencing slower boot times recently would any of these drivers contribute to that? if so which one? clover 4510 laptop specs below.

Share this post


Link to post
Share on other sites
Posted (edited)
40 minutes ago, SavageAUS said:

Now that some drivers have become optional have they been removed from the system?, i've been experiencing slower boot times recently would any of these drivers contribute to that? if so which one? clover 4510 laptop specs below.

Hmm... no such issues on my side. But also, I've got a different system here.

 

On a first glance, I'd say they shouldn't be removed.... I think they just became accessible in the UI. I mean, I had OSXAptioFix3Drv enabled from previous builds. And it's still checked for upgrade/installation in the installer UI. If there was something else I had installed, I would think it should have also been marked as checked for upgrade... Personally I'm not sure this is a driver issue.

 

But...I guess we can test this theory by simply reinstalling an older build and comparing the results between the old and the new one...? See which drivers you have with the old one and which ones you have with the new one. Compare the lists, see which one is added/removed and where. It's just an idea, of course.

Edited by arsradu

Share this post


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

Hmm... no such issues on my side. But also, I've got a different system here.

 

On a first glance, I'd say they shouldn't be removed.... I think they just became accessible in the UI. I mean, I had OSXAptioFix3Drv enabled from previous builds. And it's still checked for upgrade/installation in the installer UI. If there was something else I had installed, I would think it should have also been marked as checked for upgrade... Personally I'm not sure this is a driver issue.

 

But...I guess we can test this theory by simply reinstalling an older build and comparing the results between the old and the new one...? See which drivers you have with the old one and which ones you have with the new one. Compare the lists, see which one is added/removed and where. It's just an idea, of course.

Do you happen to know the clover version number when it changed?

Share this post


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

Do you happen to know the clover version number when it changed?

I think it was 4497

So anything older than that (I'm talking official builds, not third party builds) should be fine for this test.

Share this post


Link to post
Share on other sites
Posted (edited)
8 hours ago, arsradu said:

I'm also curious as to why are there so many Drivers now with the newer Clover builds.... I'm still using only one of those, cause that's pretty much all I need to get my computer going, but I was curious why are there so many now?

 

Also, many of them are similar, just different versions. For example OsXAptioFixDrv/OsXAptioFix2Drv/OsXAptioFix3Drv... Do we need all of those? I mean, it's good to have options when you need them. But...question is, DO we need them? And do we need them ALL? Does anyone still need OsXAptioFixDrv instead of OsXAptioFix3Drv for example? And when i say need, I really mean NEED, as in the sense that it doesn't work otherwise?

 

Cause, if not....I would suggest only keeping the latest version (or best version). And when I say "best", I mean the one with the broader spectrum of compatibility. If they are backwards compatible, then, in theory, all you need is the last one, right?

 

Because they work differently. AptioFix3/AptioMemoryFix is the best as it preserves (for the most part) all runtime but has broken hibernation/wake, AptioFix2 only works for some people and provides native NVRAM usually, AptioFix1 is the original and is basically the only one that will almost always work - however, it will most likely break NVRAM and you will need EmuVar.

 

8 hours ago, arsradu said:

I don't know... To me, and you probably already know this, cause I said it before, options are good. But too many options are not. Cause they tend to create confusion.

 

Also, one thing I would recommend, in case it's possible... Let's group those drivers based on their use.

 

For example:


Drivers64UEFI

     Mouse and keyboard (expand/collapse, just like the Drivers64UEFI section itself)

          UsbMouseDxe

          UsbKbDxe

     

     NVRAM emulators

          EmuVariableUefi (not needed if you have hardware NVRAM or OsXAptioFix3Drv in place). Hope I'm not wrong...

 

Anyway, you got the point.

 

Maybe this will also bring some clarity on what each driver is doing. Especially since some of them seem to be missing their description.

 

Also, I guess we could group them into Mandatory and Non-Mandatory. But then again, what's "mandatory" for my system might not be mandatory for yours, due to hardware differences. So... I don't think that's gonna be very accurate.

 

Yeah, there's no way to do mandatory and non-mandatory because each system has different requirements for what needs fixed/implemented. The grouping and better descriptions is probably a good idea but the package itself is a terrible mess. There aren't many who can understand it and change it to be better, it's a lot of work. I'm pretty sure that the package is just a modified version of the package from chameleon, and that's as old as hackintoshing.

 

EDIT: Spelling.

 

5 hours ago, SavageAUS said:

Now that some drivers have become optional have they been removed from the system?, i've been experiencing slower boot times recently would any of these drivers contribute to that? if so which one? clover 4510 laptop specs below.

 

Which drivers did you have before? Just put them back and see....?

 

5 hours ago, SavageAUS said:

Now that some drivers have become optional have they been removed from the system?, i've been experiencing slower boot times recently would any of these drivers contribute to that? if so which one? clover 4510 laptop specs below.

 

It was 4502: https://sourceforge.net/p/cloverefiboot/code/4502/

 

4 hours ago, arsradu said:

Hmm... no such issues on my side. But also, I've got a different system here.

 

On a first glance, I'd say they shouldn't be removed.... I think they just became accessible in the UI. I mean, I had OSXAptioFix3Drv enabled from previous builds. And it's still checked for upgrade/installation in the installer UI. If there was something else I had installed, I would think it should have also been marked as checked for upgrade... Personally I'm not sure this is a driver issue.

 

But...I guess we can test this theory by simply reinstalling an older build and comparing the results between the old and the new one...? See which drivers you have with the old one and which ones you have with the new one. Compare the lists, see which one is added/removed and where. It's just an idea, of course.

 

When you install, a ticket is created for each item installed. If you start the installer again, the ticket will be found and the box will be auto ticked to upgrade. This prevents mismatched versions, also anything unchecked will be removed if it was checked before.

 

4 hours ago, SavageAUS said:

Do you happen to know the clover version number when it changed?

 

r4502. You can look at the history of commits on sf.net: https://sourceforge.net/p/cloverefiboot/code/HEAD/log/?path=

 

4 hours ago, arsradu said:

I think it was 4497

So anything older than that (I'm talking official builds, not third party builds) should be fine for this test.

 

r4497 should be the last official release that doesn't have this mandatory/non-mandatory change. However, looking at 4497, there were a ton of changes to injection, so maybe you need to adjust some of your settings to deal with that.

Edited by apianti

Share this post


Link to post
Share on other sites

Fwiw, 4509 fixed the slow clover startup / scan loaders phase.

Share this post


Link to post
Share on other sites
Posted (edited)

Maybe if anyone wants to take a look and see if anything is wrong, ive provided files.

 

Edited by SavageAUS

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 fusion71au
      Clover r4799 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.14 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4799 for VMware.zip". Mount Clover-v2.4k-4799-X64 by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
    • By sonicthehedgehog2
      Apologies for the lack of information (and for posting in the wrong place), but I can't even boot into Clover so screenshots of verbose mode aren't even possible. I've been running the beta of 10.14.2 for sometime (-using this excellent guide 
      ) without any issues. When I tried to apply the new update for 10.14.2, my pc downloaded the update, shutdown but applied some updates then rebooted into a blank screen. I've tried several things since then. Specifically:
       
      * Booting from the installation USB created using the above guide - same blank screen
      * Booting from an external HDD - successful launch of OS. From here I have tried different versions of Clover including the one on my HDD r4644 (all have been unsuccessful). I have also tried different memory management options osxaptiofix (1, 2 & 3)
       
      The only other information I can provide is in the screenshots below (including a brief of my drive configuration)
       
      Please let me know if and how I can get more information to help resolve the issue, or if I have to rebuild from scratch.
       
      Many thanks in advance
       
       


    • By Teress
      To build a Hackintosh never was easier. If you want cheap Hackintosh and have it quickly and 100% working and without any knowledge how to tweak things, this video is right for you.
       
    • By superdooper71
      Hi all,
      I hope someone can help me as I am struggling with this bloody installation.
      I am running on several problems that I can't face : (
       
      First of all my config:
      Mobo: ASROCK H81M-DGS R2
      CPU: Intel Xeon E3-1220 v3 @3.10ghz
      RAM: 16gb DDR3 1600Mhz
      SSD: Crucial BX100 120Gb SSD
      Monitor: Hp 27w Hdmi
       
      POST Installation CLOVER
       
      Current Issues:
      • System will not boot (clover boot loader do not shows up) from SSD
         - System boot only with USB stick
      • Screen Resolution is only 1024x768
      • Monitor recognised as 17" instead of 24"
      • Monitor identified as secondary
      • Grafic Card Geforce GT710 shows 0 Mb
      • System info do not match Config.plistin Clover
       
      I attach screenshot of System Info, Kext in Clover, Resolution etc etc.
       
      Please can someonhelp me?
       
      Please can you tell me what is the Clover Parameter to activate when installing Clover  (Clover_v2.4k_r4722) into Boot Disk?
       
      I hope someone can help me out of this little troble: )
       
      Cheers
      Franco
       
      system info.tiff
      kext.tiff
      resolution.tiff
      system.tiff
      config.plist
    • 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  selezionate OsxAptioFixDrv-64
                             *  :Se nel vostro sistema è presente una scheda grafica (discreta) della serie 9xx nVidia selezionate OsxAptioFix2Drv-64 al posto di  OsxAptioFixDrv-64 *
      ** OsxAptioFix2Drv :E' necessario per poter impostare CsrActiveConfig= 0x3 **
      ***OsxAptioFix3Drv oppure AptioMemory --> (consigliato) devono essere usati su hardware Skylake o successivi perché permettono alla nvram di lavorare correttamente
           (mi raccomando o uno o l'altro)
      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






×