Jump to content
ErmaC

Clover General discussion

19,245 posts in this topic

Recommended Posts

hey! i got two questions:

 

1:

 

here in post #10 slice talks about the possibility to set different settings for different cards but i don't quiet get it get it how i should alter my config.plist to use this?

 

i run three GPUs in my machine of which two need injection. right now i have do do the settings manually in clover at boot.

 

2:

 

clover is also able to boot linux which is great. but is there any way the pass more arguments to the kernel (aka bootflags?)

 

 

Cheers

Share this post


Link to post
Share on other sites
Advertisement

Just downloading the final version of El capitan after patiently waiting out the beta period.

 

I just wanted to check the key things I need to change from upgrading from a working Yosemite install:

 

I'm on clover version 3259 and my config.plist currently has only: `<key>RtVariables</key> <dict> <key>MLB</key> <string>C07039601ANDD17DV</string> <key>ROM</key> <string>78ca392e 3bb0</string> </dict>

I take it I need to add in the two additional keys  - booterconfig with string as 0x28 and csractiveconfig with the string as either 0x67 or 0x77. (but if I pick one of those values for csractiveconfig I'll still get some SIP error messages - is that right?) However if I make it 0x11 will those SIP messages disappear? Is the issue with going with 0x11 is that  it isn't advisable to copy kexts to /Library/extensions (does that makes things unstable?)

I only have a few kexts in EFI/Clover/kexts/10.10. AppleIntelE1000e.kext FakeSMC.kext NullCPUPowerManagement.kext realtekALC.kext (I take it these need to be copied to the 10.11 folder?)

I can see FakeSMC.kext in /System/Library/extensions - but none of the others (are these not being injected?)

Do I also need to turn off kext-dv-mode=1 boot option (or is it just ignored now? Any other things to be wary off?

Thanks.

 

Setup is

Intel core i5 4570

Gigabyte Z87m-D3h

Nvidia 780 ti

Share this post


Link to post
Share on other sites

Just downloading the final version of El capitan after patiently waiting out the beta period.

 

I just wanted to check the key things I need to change from upgrading from a working Yosemite install:

 

I'm on clover version 3259 and my config.plist currently has only: `<key>RtVariables</key> <dict> <key>MLB</key> <string>C07039601ANDD17DV</string> <key>ROM</key> <string>78ca392e 3bb0</string> </dict>

I take it I need to add in the two additional keys  - booterconfig with string as 0x28 and csractiveconfig with the string as either 0x67 or 0x77. (but if I pick one of those values for csractiveconfig I'll still get some SIP error messages - is that right?) However if I make it 0x11 will those SIP messages disappear? Is the issue with going with 0x11 is that  it isn't advisable to copy kexts to /Library/extensions (does that makes things unstable?)

I only have a few kexts in EFI/Clover/kexts/10.10. AppleIntelE1000e.kext FakeSMC.kext NullCPUPowerManagement.kext realtekALC.kext (I take it these need to be copied to the 10.11 folder?)

I can see FakeSMC.kext in /System/Library/extensions - but none of the others (are these not being injected?)

Do I also need to turn off kext-dv-mode=1 boot option (or is it just ignored now? Any other things to be wary off?

Thanks.

 

Setup is

Intel core i5 4570

Gigabyte Z87m-D3h

Nvidia 780 ti

 

You've got green light to update.

 

1. Move your kexts from Clover/kexts/10.10 to 10.11 (as you suspected). Or copy them if you're planning on keeping Yosemite and installing El Capitan on a different partition, but on the same HDD/SSD.

2. You don't need to add RT Variables. I think Clover will add them anyway on new installations. However, if you want to add them manually, yes 0x28 for BooterConfig and 0x67 for CsrActiveConfig will disable SIP enough to give access to pretty much everything. You can tweak that later on, don't worry about it. You can boot just as well with 0x28 and 0x1. So..yeah, just go ahead and update.

3. kext-dev-mode=1 is not needed in El Capitan (it's got SIP now). So if you're not planning on getting back to Yosemite, you can remove that with no problem.

4. you don't need copy anything to S/L/E. It's not needed. Clover injection works beautifully from EFI. Also, you should not have custom kexts in both places (S/L/E and Clover/kexts/10.x)

 

You can use Clover Configurator for a more user-friendly editing interface for your config.plist. Just make sure it's the latest version (I think 4.24 is the latest one.)

Share this post


Link to post
Share on other sites

You've got green light to update.

 

1. Move your kexts from Clover/kexts/10.10 to 10.11 (as you suspected). Or copy them if you're planning on keeping Yosemite and installing El Capitan on a different partition, but on the same HDD/SSD.

2. You don't need to add RT Variables. I think Clover will add them anyway on new installations. However, if you want to add them manually, yes 0x28 for BooterConfig and 0x67 for CsrActiveConfig will disable SIP enough to give access to pretty much everything. You can tweak that later on, don't worry about it. You can boot just as well with 0x28 and 0x1. So..yeah, just go ahead and update.

3. kext-dev-mode=1 is not needed in El Capitan (it's got SIP now). So if you're not planning on getting back to Yosemite, you can remove that with no problem.

4. you don't need copy anything to S/L/E. It's not needed. Clover injection works beautifully from EFI. Also, you should not have custom kexts in both places (S/L/E and Clover/kexts/10.x)

 

You can use Clover Configurator for a more user-friendly editing interface for your config.plist. Just make sure it's the latest version (I think 4.24 is the latest one.)

 

Friend and the flag: "Rootless = 1", you will be required in the El Capitan yet?

Share this post


Link to post
Share on other sites

Friend and the flag: "Rootless = 1", you will be required in the El Capitan yet?

No. If you set Rt Variables, "rootless=1" is not required. Also, I'm pretty sure it's already obsolete.

Share this post


Link to post
Share on other sites

Brilliant thanks

 

- from your comment - "you should not have custom kexts in both places"  - Does that mean I should remove the FakeSMC.kext which is is /S/L/E and also in clover/kexts/10.x?

 

Yup I use clover configurator - it's handy. I'm on the 4.24 version but it doesn't seem to have an option (in boot?) for RT Variables -> BooterConfig and CsrActiveConfig.  Not a big deal as I can edit config.plist manually.

Share this post


Link to post
Share on other sites

- from your comment - "you should not have custom kexts in both places"  - Does that mean I should remove the FakeSMC.kext which is is /S/L/E and also in clover/kexts/10.x?

 

No, just keep your custom kexts in one place: Clover/kexts/10.x.  Not in Clover and also in S/L/E. But in one place only. And I would recommend that place to be in Clover's kexts folder.

 

Clover Configurator has a dedicated RtVariables section (separate from Boot). That's where you need to add those values.

Share this post


Link to post
Share on other sites

Upgraded all seems ok apart from the nvidia web driver is saying it's not compatible and there is no update? The version is: 346.02.03f01.

Anyone else got it working? 

 

(using 780ti)

Share this post


Link to post
Share on other sites

 

@Slice:

 

I've noticed after updating to the newest r3277 (from r3228), that if one doesn't set the property CsrActiveConfig , clover will then set it to 0x67, which disables the entire SIP.

I think it is a security vulnerability. 

 

Wouldn't it be better to document the feature in the wiki and let the end user decide, if they want to disable SIP or not?

 
Sorry, if it has been already discussed...

 

I agree, I think Clover should only automatically allow unsigned kexts by default (0x11 IIRC) only if the NVRAM variable csr-active-config doesn't exist (not the Clover CsrActiveConfig property).

Share this post


Link to post
Share on other sites

Upgraded all seems ok apart from the nvidia web driver is saying it's not compatible and there is no update? The version is: 346.02.03f01.

Anyone else got it working? 

 

(using 780ti)

You need the newest Beta driver. Currently version 346.03.01b07.

 

Here you go.

Share this post


Link to post
Share on other sites

I agree, I think Clover should only automatically allow unsigned kexts by default (0x11 IIRC) only if the NVRAM variable csr-active-config doesn't exist (not the Clover CsrActiveConfig property).

No, not that even. Just have the feature and let the user decide what to do, would be more secure way.

 

I'm aware, that it might be difficult for many users, but the security should be more important, than anyone, who can't read wiki's...

Share this post


Link to post
Share on other sites

Its possible to add a folder, where i can put all my kexts in, for every OS ?

I mean, i need to put 6Kexts into 10.11 folder and the same 6 in 10.10 folder... useless space consumption...

 

It works if i delete 10.10 & 10.11 folder and put them all in Others folder, but if i update clover, 10.10 and 10.11 folder is back and they are empty and it doesn't inject... so i need to delete them again after update...

 

Cheers :-)

Share this post


Link to post
Share on other sites

Its possible to add a folder, where i can put all my kexts in, for every OS ?

I mean, i need to put 6Kexts into 10.11 folder and the same 6 in 10.10 folder... useless space consumption...

 

It works if i delete 10.10 & 10.11 folder and put them all in Others folder, but if i update clover, 10.10 and 10.11 folder is back and they are empty and it doesn't inject... so i need to delete them again after update...

 

Cheers :-)

This is very old disscussion what is more convenient. One think that second think other.

For my mind, for my kexts from signature, a kext for 10.6 will work in 10.11.

Bright exception is AppleHDA that I don't use. It is always system specific.

So I think it will be good to support a folder "Common" with system independent kexts. But this is a problem to keep two different pathes where Clover should  take kexts Only one folder.  :(

Discuss?

Share this post


Link to post
Share on other sites

This is very old disscussion what is more convenient. One think that second think other.

For my mind, for my kexts from signature, a kext for 10.6 will work in 10.11.

Bright exception is AppleHDA that I don't use. It is always system specific.

So I think it will be good to support a folder "Common" with system independent kexts. But this is a problem to keep two different pathes where Clover should  take kexts Only one folder.  :(

Discuss?

 

Can we check if a folder is empty (or check for files with extension *.kext under those folders)? Also, can we check OS version before looking for kexts in Clover/kexts/10.x ? If so, can we do something like this?

 

1. Check OS version.

2. Check for kexts in the corresponding folder for that version

3. If the folder is empty or doesn't have any *.kext files, move on to the Others folders and look under there.

4. If that one is empty as well, tough luck. :)

 

But I'm just saying, if we can check if a folder is empty, or doesn't have any kexts in it (you can put txt in it, but that won't help you boot :)) ), then let's check if those folders have what they need to perform a boot. If not, check under Others. Don't check if the folder exists, but rather, if the folder contains the stuff the system needs to boot.

 

Second variant (but I don't know how efficient would that be) is to look for kexts under any of those folders. And try to boot using the kexts from wherever you can find them. That would kinda cancel the reason for having multiple folders in the first place.

 

I don't know. Just a few ideas off the top of my head. 

Share this post


Link to post
Share on other sites

Hmm I may have spoken too soon about an easy upgrade to El capitan.  It appears the sound is broken.   In the system report-> Audio I can see Intel High Definition Audio.  But under the sound options in preferences there is nothing to choose under "Selected sound output device".

 

The kext in EFI/clover/kext/10.11 is realtekALC.kext  (my motherboard is Gigabyte z87-d3h (which uses realktek ALC892)

(clover congiruator has audio set to 1 - unchanged from my yosemite install)

 

It did work previously under Yosemite.  (the only other thing is I can hear the speakers pop when I boot up).

 

Any ideas what may be the issue?

Thanks. 

 

My config.plist http://txt.do/a2hrg

Share this post


Link to post
Share on other sites

Hmm I may have spoken too soon about an easy upgrade to El capitan.  It appears the sound is broken.   In the system report-> Audio I can see Intel High Definition Audio.  But under the sound options in preferences there is nothing to choose under "Selected sound output device".

 

The kext in EFI/clover/kext/10.11 is realtekALC.kext  (my motherboard is Gigabyte z87-d3h (which uses realktek ALC892)

(clover congiruator has audio set to 1 - unchanged from my yosemite install)

 

It did work previously under Yosemite.  (the only other thing is I can hear the speakers pop when I boot up).

 

Any ideas what may be the issue?

Thanks. 

 

My config.plist http://txt.do/a2hrg

Yes, patch your sound again.

 

If you're using Toleda's patching script, good job! Just make sure it's the latest version (last time I checked it was version "e" or something like that).

 

Also, according to your config, you need to allow the system to load unsigned kexts. In RtVariables, add BooterConfig 0x28 and CsrActiveConfig 0x67. FYI, 0x67 will allow access to a lot more than just unsigned kexts. But just to reduce the number of variables in this equation, allowing access to pretty much everything, for now, is a good place to start. You can diminish the access level afterwards, depending on your needs/preference

Share this post


Link to post
Share on other sites

I'm not sure if it's the same with Yosemite, but coming from Mavericks I had to add an additional binpatch for ALC898 (zeroing out ADI1983) to get it working again.

 

Also, I'm booting with CsrActiveConfig set to 0x03 but I haven't set/changed BooterConfig from whatever Clover defaults it to.

 

For the kext folders, I think arsradu's way works. Having a common kexts folder means not having to create a 10.xx folder for every required system version. For my X79, I use the same kexts for all systems so all the 10.xx folders are identical.

 

Slice, did you see my post here about my HDEF injection problem? It looks like a bug.

Share this post


Link to post
Share on other sites

Hmm I may have spoken too soon about an easy upgrade to El capitan.  It appears the sound is broken.   In the system report-> Audio I can see Intel High Definition Audio.  But under the sound options in preferences there is nothing to choose under "Selected sound output device".

 

The kext in EFI/clover/kext/10.11 is realtekALC.kext  (my motherboard is Gigabyte z87-d3h (which uses realktek ALC892)

(clover congiruator has audio set to 1 - unchanged from my yosemite install)

 

It did work previously under Yosemite.  (the only other thing is I can hear the speakers pop when I boot up).

 

Any ideas what may be the issue?

Thanks. 

 

My config.plist http://txt.do/a2hrg

1. Repatch AppleHDA, like asradu said,

2. On 10.11, applehda (or dummy) injection doesn't work anymore, since Resources folder can't be injected, so use it in SLE or LE.

 

 

This is very old disscussion what is more convenient. One think that second think other.

For my mind, for my kexts from signature, a kext for 10.6 will work in 10.11.

Bright exception is AppleHDA that I don't use. It is always system specific.

So I think it will be good to support a folder "Common" with system independent kexts. But this is a problem to keep two different pathes where Clover should  take kexts Only one folder.  :(

Discuss?

Common folder is a very good idea, or the Others way, like asradu said is a good idea too...

 

i have a qustion, which folder uses the single user mode? (i use the Others folder for this) & which folder uses the installer, the normal (10.11) one?

and how i can check the limit of injection, i mean i haven't unlimited free space in the cache... or how this works?

 

And other question xD i know its discussed very much...

But if i going to patch applehda with clover,

1. i need to patch info.plist (that is possible already)

2. i need to inject Layout and Platform (.xml or .zml) into resources folder ( but there is no way atm on 10.11, right? )

 

Cheers :-)

Share this post


Link to post
Share on other sites
And other question xD i know its discussed very much...

But if i going to patch applehda with clover,

1. i need to patch info.plist (that is possible already)

2. i need to inject Layout and Platform (.xml or .zml) into resources folder ( but there is no way atm on 10.11, right? )

 

Cheers :-)

 

I would strongly recommend using toleda's script to patch audio. It's an awesome script. And it does everything for you. Oh, yes, and it works perfectly with 10.11.

Share this post


Link to post
Share on other sites

Why threre is no respons about my comment :(

What's wrong?

 

We don't like your nose. :P

 

Joking, of course. There are not many people who have the newer Skylake processors yet. So not many can confirm that or work on a fix for that. I'm sure the guys here will take a look at that and fix it, if indeed is a real issue, if it's a Clover issue, and if it's not just a simple layout/cosmetic issue. :) Either way, a bit of patience would be nice.

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 vit9696
      OpenCorePkg / Documentation / Configuration Template / Bugtracker   Discussion and installation should be done in a separate thread! This thread is for development only!
      Current status as of April 2019: Support for UEFI and DuetPkg (legacy) booting APFS and HFS+ compatibility ACPI patcher (adding, dropping, binary patching, relocation) Apple-compatible bless implementation DeviceProperties injection DataHub and SMBIOS generation Symbolic kext and kernel patcher Direct kext injection/patching/blocking within prelinkedkernel Installation/Recovery/FileVault 2 support  Configuration in config.plist with open documentation Simple boot picker for quick launch Direct boot from dmg images  
      Known defects live here.  
      For those, who are not familiar with the history, OpenCore is a project initially born in HermitCrabs Lab that unfortunately almost died before its birth. This release is both a rebirth and a complete rewrite of OpenCore, which brings a number of new ideas, and tries to preserve the smart moves incorporated by iNDi and his team. Other than that, I wish to express my deepest words of gratitude to Acidanthera and WWHC members: your participation was and remains the key for project success, and you are simply the best.
    • By fusion71au
      Clover r4961 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_r4961 for VMware.zip". Mount Clover-v2.4k-4961-X64.iso 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 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
      Pacchetto-Fake+Sensors 6.26.1440.zip
      C_I_M.zip
       
      apfs.efi-10.14-beta1_No_Log.zip





       

×