Jump to content
ErmaC

Clover General discussion

18,272 posts in this topic

Recommended Posts

Well, with

<key>KernelXCPM</key>
<false/> 
stuck in PCI configuration begin

 

You can add more PCI configuration logging by adding pci=1 to boot arguments in Clover config.plist. Maybe it will show what device is causing the problem? The pci= flags are listed at https://opensource.apple.com/source/IOPCIFamily/IOPCIFamily-320.1.1/IOKit/pci/IOPCIConfigurator.h.auto.html

PCI logging might be useful to get Thunderbolt probe (for hot plug) in the future.

Share this post


Link to post
Share on other sites
Advertisement

You can add more PCI configuration logging by adding pci=1 to boot arguments in Clover config.plist. Maybe it will show what device is causing the problem? The pci= flags are listed at https://opensource.apple.com/source/IOPCIFamily/IOPCIFamily-320.1.1/IOKit/pci/IOPCIConfigurator.h.auto.html

PCI logging might be useful to get Thunderbolt probe (for hot plug) in the future.

Thanks. I will try

Share this post


Link to post
Share on other sites

Ok, and how to deal with it? If you know, what is changed over from 4233 to 4297 that's not loading fakesmc.

 

Maybe your custom High Sierra Entry is interfering with os ver detection in Clover r4297 but not r4233.

 

With Clover r4233, your boot.log under [ AddCustomEntries ] shows Clover is detecting your High Sierra custom entry as 10.13.1...

8:223  0:008  Custom settings: <null string>.plist will  be applied
8:223  0:000  chosen os 10.13.1
8:256  0:032      Checking volume "Recovery" (PciRoot(0x0)\Pci(0x1,0x1)\Pci(0x0,0x0)\NVMe(0x1,00-00-00-00-00-00-00-00)\HD(2,GPT,

but with r4297, the line "chosen os 10.13.1" is missing...

8:418  0:008  Custom settings: <null string>.plist will  be applied
8:422  0:004      Checking volume "Recovery" (PciRoot(0x0)\Pci(0x1,0x1)\Pci(0x0,0x0)\NVMe(0x1,00-00-00-00-00-00-00-00)\HD(2,GPT,72F936FF-2F5E-46B0-99B4-04CFAE5FB052,0x64800,0xEED0800)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,C75337538ACA8B4784FF587E39EFE541)) ... skipped

Suggestions

  • Remove the custom entry for High Sierra and see if booting the auto scanned HS entry makes a difference
  • Make sure FakeSMC is in /CLOVER/kexts/Other (or temporarily install in SLE/LE so we can get full boot.log from Clover r4297)

Share this post


Link to post
Share on other sites

 

 

Maybe your custom High Sierra Entry is interfering with os ver detection in Clover r4297 but not r4233.

 

With Clover r4233, your boot.log shows Clover is detecting your High Sierra custom entry as 10.13.1...

8:223  0:008  Custom settings: <null string>.plist will  be applied
8:223  0:000  chosen os 10.13.1
8:256  0:032	  Checking volume "Recovery" (PciRoot(0x0)\Pci(0x1,0x1)\Pci(0x0,0x0)\NVMe(0x1,00-00-00-00-00-00-00-00)\HD(2,GPT,
but with r4297, the line "chosen os 10.13.1" is missing...
8:418  0:008  Custom settings: <null string>.plist will  be applied
8:422  0:004      Checking volume "Recovery" (PciRoot(0x0)\Pci(0x1,0x1)\Pci(0x0,0x0)\NVMe(0x1,00-00-00-00-00-00-00-00)\HD(2,GPT,72F936FF-2F5E-46B0-99B4-04CFAE5FB052,0x64800,0xEED0800)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,C75337538ACA8B4784FF587E39EFE541)) ... skipped
Suggestions
  • Remove the custom entry for High Sierra and see if booting the auto scanned HS entry makes a difference
  • Make sure FakeSMC is in /CLOVER/kexts/Other (or temporarily install in SLE/LE so we can get full boot.log from Clover r4297)

FakeSMC? When i question about the differences between 4233 and 4297 I think it's logic that I don't alter and change anything in EFI... Will test and report your idea about entries. Thanks

Share this post


Link to post
Share on other sites

Hi all,

 

in the latest versions of Clover more options about hibernation have come out. Particularly (as from Clover configurator):

 

  • StrictHibernate
  • NeverHibernate
  • HibernationFixUp
  • SkipHibernateTimeout

does anyone know what they mean and how/when we should use them? ... TIA :) 

 

I'm still facing problems with hibernation on my rig... 

Share this post


Link to post
Share on other sites

Hi all,

 

in the latest versions of Clover more options about hibernation have come out. Particularly (as from Clover configurator):

 

  • StrictHibernate
  • NeverHibernate
  • HibernationFixUp
  • SkipHibernateTimeout

does anyone know what they mean and how/when we should use them? ... TIA :)

 

I'm still facing problems with hibernation on my rig... 

About StrictHibernate   #43 

NeverHibernate - as it named

HibernationFixUp - for use with Lilu+HibernationFixup plugin

SkipHibernateTimeout - as it named, if your config contains Timeout=5second then during hibernate wake the timeout will be zero to speedup the process.

 

Anyway hibernation may not work for different reason.

Share this post


Link to post
Share on other sites

That's quite weird! I don't even need "HibernationFixUp" (in config.plist) at all. All I need are "StrictHibernate" + IOPCIFamily patch (alternatively, Lilu + HibernationFixup). I have fv2 enabled.

Share this post


Link to post
Share on other sites

Ok, and how to deal with it? If you know, what is changed over from 4233 to 4297 that's not loading fakesmc.

 

I thought I posted this but I don't see it so maybe I didn't or it got deleted or something. You have no FakeSMC. I can see from your log that it is in kexts\Other and prepared for injection. So either injection is failing or you disabled the kext from being injected.

Share this post


Link to post
Share on other sites

 

FakeSMC failing to load?

 

 

 

The installer path to boot.efi on the "Boot OS X" partition for Fusion Drives changed from /System/Library/CoreServices/boot.efi (in El Capitan) to /com.apple.boot.R/boot.efi (in Sierra & High Sierra)...

 

El Capitan

attachicon.gifBoot OS X and com.apple.boot.S for El Capitan install.png

 

vs Sierra & High Sierra

attachicon.gifBoot OS X and com.apple.boot.R for HSierra install.png

 

 

please test for fusion drive

fusion test.zip

Share this post


Link to post
Share on other sites

Hi, maybe a noob questions :)

 

clover add some nvram keys which aren't present with other bootloaders

can you explain (briefly) about them?

 

security-mode=none

flagstate=0

efi-boot-device=UUID of macOS partition (is it because of LastBootedVolume?)

EFILoginHiDPI=0

efi-boot-device-data

specialbootdevice (same key as efi-boot-device-data)

Thanks.

Share this post


Link to post
Share on other sites

sorry for late

i don't correctly know your system.

your config.plist has some wrong parts and not cleanup. try this.

Hello. Will try, feedback on the way)

Share this post


Link to post
Share on other sites

Upload your preboot.log and did you see DSMOS arrived message above verbose log?

 

나의 LG-F800S 의 Tapatalk에서 보냄for 

for now I could just confirm that your config.plist working just well with clover 4233... 

 

not so well) no so good on CPU... so

Share this post


Link to post
Share on other sites

for now I could just confirm that your config.plist working just well with clover 4233...

 

not so well) no so good on CPU... so

Try r4268 pkg on sf.

 

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

Hi, maybe a noob questions :)

 

clover add some nvram keys which aren't present with other bootloaders

can you explain (briefly) about them?

 

security-mode=none

flagstate=0

efi-boot-device=UUID of macOS partition (is it because of LastBootedVolume?)

EFILoginHiDPI=0

efi-boot-device-data

specialbootdevice (same key as efi-boot-device-data)

Thanks.

 

These are all keys from different SMBIOS of different macs. Some don't have certain ones, but there's nothing wrong with setting them in that case. The efi-boot-device(-data) and specialbootdevice keys are set because that's the startup disk.

Share this post


Link to post
Share on other sites

please test for fusion drive

 

Thanks Sherlocks.

 

It now correctly detects /com.apple.boot.R/boot.efi from "Boot OS X" as macOS install  :).  

 

At the moment, it is not parsing /com.apple.boot.R/SystemVersion.plist so os ver is not set to 10.13.x ---> will need FakeSMC in /CLOVER/kexts/Other as /10.13 won't be used...

 

 

post-846696-0-78536600-1510603603_thumb.png

post-846696-0-07708100-1510603630_thumb.png

post-846696-0-68121500-1510603648_thumb.png

 

Share this post


Link to post
Share on other sites

Thanks Sherlocks.

 

It now correctly detects /com.apple.boot.R/boot.efi from "Boot OS X" as macOS install  :).  

 

At the moment, it is not parsing /com.apple.boot.R/SystemVersion.plist so os ver is not set to 10.13.x ---> will need FakeSMC in /CLOVER/kexts/Other as /10.13 won't be used...

 

 

 

maybe this is last test. please test and report

 

also still if null, can't read other folder. this is strange.

for now I could just confirm that your config.plist working just well with clover 4233... 

 

not so well) no so good on CPU... so

 

you need to find solution yourself. your system has simliar fabiosun's system. maybe he can help you.

fusion test2.zip

Share this post


Link to post
Share on other sites

@Sherlocks,

 

test2.zip gets same result as original test.zip ---> os ver not set to 10.13.x.

 

It was a similar situation before with "/macOS Install Data/Locked Files/Boot Files/SystemVersion.plist" before @Slice fixed version detection from that folder in Clover r4293.

Share this post


Link to post
Share on other sites

Try r4268 pkg on sf.

 

나의 LG-F800S 의 Tapatalk에서 보냄

preboot from 4297

Share this post


Link to post
Share on other sites

@Sherlocks,

 

test2.zip gets same result as original test.zip ---> os ver not set to 10.13.x.

 

It was a similar situation before with "/macOS Install Data/Locked Files/Boot Files/SystemVersion.plist" before @Slice fixed version detection from that folder in Clover r4293.

 

already. i did mistake build. here is file

can you upload systemversion.plist?

 

com.apple.boot.R/SystemVersion.plist

macOS Install Data/Locked Files/Boot Files/SystemVersion.plist

 

it will help cleanup code.

preboot from 4297

why add 0:138  0:000   - [04]: 10.13 Installer/Updater essential :: MatchOS: 10.13.x :: data len: 11?

already its same xcpm_pkg_scope_msrs © Pike R. Alpha. your preboot was cut. not full log. strange.

fusion3.zip

Share this post


Link to post
Share on other sites

already. i did mistake build. here is file

can you upload systemversion.plist?

 

com.apple.boot.R/SystemVersion.plist

macOS Install Data/Locked Files/Boot Files/SystemVersion.plist

 

it will help cleanup code.

why add 0:138  0:000   - [04]: 10.13 Installer/Updater essential :: MatchOS: 10.13.x :: data len: 11?

already its same xcpm_pkg_scope_msrs © Pike R. Alpha. your preboot was cut. not full log. strange.

Installer/Updater essential - its disabled, also other patch have to edit to make cpu run properly. tomorrow will test another version clover) thanks

Share this post


Link to post
Share on other sites

already. i did mistake build. here is file

can you upload systemversion.plist?

 

com.apple.boot.R/SystemVersion.plist

macOS Install Data/Locked Files/Boot Files/SystemVersion.plist

 

it will help cleanup code.

 

fusion3.zip works perfectly  :thumbsup_anim: ...

 

 

 

post-846696-0-55685000-1510608759_thumb.png

post-846696-0-02069400-1510608806_thumb.png

post-846696-0-77744200-1510608828_thumb.png

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>ProductBuildVersion</key>
	<string>17B48</string>
	<key>ProductCopyright</key>
	<string>1983-2017 Apple Inc.</string>
	<key>ProductName</key>
	<string>Mac OS X</string>
	<key>ProductUserVisibleVersion</key>
	<string>10.13.1</string>
	<key>ProductVersion</key>
	<string>10.13.1</string>
</dict>
</plist>

 

 

 

Attached is com.apple.boot.R.zip with SystemVersion.plist.

 

 

 

FakeSMC? When i question about the differences between 4233 and 4297 I think it's logic that I don't alter and change anything in EFI... Will test and report your idea about entries. Thanks

 

I think you might be misunderstanding me.  We need a full boot.log from Clover r4297 to diagnose the problem, which means you temporarily install essential kexts needed for booting into /S/L/E (like FakeSMC), so the boot can go to completion.

 

At the moment, your preboot.log from r4297 ends shortly after reaching the Clover GUI (because you are booting into Linux with r4297, instead of High Sierra??)...

2:534  0:058  GUI ready
7:271  4:736  BootVariable of the entry is empty
7:271  0:000  === [ StartLoader ] =======================================
7:271  0:000  Finally: ExternalClock=25MHz BusSpeed=100000kHz CPUFreq=3400MHz PIS: hw.busfrequency=100000000Hz
7:271  0:000  Loading grubx64.efi  status=Success

and is missing the crucial part we are interested in wrt kext injection eg

 

 

 

does GetOSversion detect 10.13.x correctly?

10:834  0:000  Loading boot.efi  status=Success
10:845  0:010  GetOSVersion: 10.13.1 (17B48)

and what happens with kext injection

FSInjectionInstall ...
- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: 58D6B298
10:939  0:005  Use origin smbios table type 1 guid.
10:942  0:002  Preparing kexts injection for arch=x86_64 from EFI\\CLOVER\\kexts\\Other
10:942  0:000  Extra kext: EFI\\CLOVER\\kexts\\Other\\X99_Injector USB 3.kext
10:947  0:005  Extra kext: EFI\\CLOVER\\kexts\\Other\\VoodooTSCSync.kext
10:956  0:008  Extra kext: EFI\\CLOVER\\kexts\\Other\\USBInjectAll.kext
11:030  0:074  Extra kext: EFI\\CLOVER\\kexts\\Other\\Lilu.kext
11:041  0:010  Extra kext: EFI\\CLOVER\\kexts\\Other\\IntelMausiEthernet.kext
11:053  0:011  Extra kext: EFI\\CLOVER\\kexts\\Other\\FakeSMC.kext
11:067  0:013    |-- PlugIn kext: EFI\\CLOVER\\kexts\\Other\\FakeSMC.kext\\Contents\\PlugIns\\LPCSensors.kext
11:112  0:045    |-- PlugIn kext: EFI\\CLOVER\\kexts\\Other\\FakeSMC.kext\\Contents\\PlugIns\\GPUSensors.kext
11:126  0:013    |-- PlugIn kext: EFI\\CLOVER\\kexts\\Other\\FakeSMC.kext\\Contents\\PlugIns\\CPUSensors.kext
11:136  0:010  Extra kext: EFI\\CLOVER\\kexts\\Other\\Shiki.kext\
11:147  0:010  Extra kext: EFI\\CLOVER\\kexts\\Other\\AtherosE2200Ethernet.kext
11:157  0:010  Extra kext: EFI\\CLOVER\\kexts\\Other\\AppleALC.kext
11:173  0:016    |-- PlugIn kext: EFI\\CLOVER\\kexts\\Other\\AppleALC.kext\\Contents\\PlugIns\\PinConfigs.kext 

 

 

 

We can extrapolate whether kext injection is working from /CLOVER/kexts/Other by seeing if the other, non essential kexts (besides FakeSMC, like your AppleALC.kext), are loaded after a successful boot into your system with Clover r4297 and FakeSMC in /S/L/E.

com.apple.boot.R.zip

macOS Install Data.zip

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 r4747 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_r4747 for VMware.zip". Mount Clover-v2.4k-4747-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 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






    • By marianopela
      Hi, I'm an Hackintosh user on my HP ProDesk and I'd like to try getting Mojave on my HP 250 G6
      Could anybody help me with the EFI folder?
       
      Thanks in advance
    • By Donk
      Here is a new utility to patch the EFI firmware in VMware Workstation and Fusion to allow the non-server versions of Mac OS X 10.5 (Leopard) and 10.6 (Snow Leopard) to run. Yoiu will need macOS unlocker 3 if you are using Workstation on non-Apple hardware. I still have to find a way to do this on ESXi as the UEFIPatch utility will not run in the ESXi console.
      This currently supports:
       
      Workstation 11/12/14/15 on Windows and Linux Workstation Player 7/12/14/15 on Windows and Linux Fusion 10/11 on macOS  
      https://github.com/DrDonk/efi-unlocker/releases/download/1.0.0/efi-unlocker100.zip
      https://github.com/DrDonk/efi-unlocker
       
      Please read the readme.txt file for details.
      readme.txt
×