Jump to content
ErmaC

Clover General discussion

20,006 posts in this topic

Recommended Posts

21 hours ago, Sherlocks said:

@Slice

long time no see.

can we consider smcverision 1/2/3? smcversion3 doesn't have REV/EPCI/RBR. 

FakeSMC force inject REV value right? can we just control datahub part to not relate FakeSMC rev?

Hi,

May be you are right but older computers need REV. Can you propose a way to distinct when used or not?

I just can propose that injecting redundant value does not influence at all.

 

Share this post


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

Hi,

May be you are right but older computers need REV. Can you propose a way to distinct when used or not?

I just can propose that injecting redundant value does not influence at all.

 

 

here is smc version 3

 

no key list 
MacBookPro15,1 : REV rBR EPCI
MacBookPro15,2 : REV rBR EPCI
MacBookAir8,1  : REV rBR EPCI
Macmini8,1     : REV rBR EPCI
iMacPro1,1     : REV rBR EPCI

2 hours ago, telepati said:

 

Does Clover affect the processor type under the About This Mac? If it is, that's why all 9900K users seeing own processor type as an i7 then.

 

try this cputype "0x1009"

Share this post


Link to post
Share on other sites
1 hour ago, telepati said:

 

Thank you. But correct value is 0x1005. This is from real iMac 19,1.

 

Hi

Where I can find cputype for core i7 9700k? What smbios is recommanded: Imac19,1! Thanks

 

I've to build a new hackintosh next week (Asus Prime z390-A, Core i7 9700K, MSI Radeon RX580)

Share this post


Link to post
Share on other sites
52 minutes ago, Matgen84 said:

 

Hi

Where I can find cputype for core i7 9700k? What smbios is recommanded: Imac19,1! Thanks

 

I've to build a new hackintosh next week (Asus Prime z390-A, Core i7 9700K, MSI Radeon RX580)

 

Since it's an i7, I'm guessing (and this is just me guessing, based on what I read online so far): 0x0705 (?)

 

Also, I think maybe iMac19,2 might be closer...? The iMac19,2 seems to be an i7 8700k. iMac19,1 seems to be an i9. So..since this is an i7, I'm guessing iMac19,2 might be closer.

 

However, Clover is already pretty good at getting the correct value for your CPU, so you might not need to enter anything there. And it's only cosmetic anyway.

 

 

Share this post


Link to post
Share on other sites
2 hours ago, telepati said:

 

Thank you. But correct value is 0x1005. This is from real iMac 19,1.

I looked to dumps of real iMac19,1 and found cpu type = 0x0709

Share this post


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

I looked to dumps of real iMac19,1 and found cpu type = 0x0709

 

This also dumps from real iMac19,1. You probably know better than me :wink_anim:

 

ioreg.png.a84d620305fcc28cbd5f2d57bd6ca914.png

 

Credits; DexterOX

 

6 hours ago, Matgen84 said:

 

Hi

Where I can find cputype for core i7 9700k? What smbios is recommanded: Imac19,1! Thanks

 

I've to build a new hackintosh next week (Asus Prime z390-A, Core i7 9700K, MSI Radeon RX580)

4

 

I think i7 9700K will be recognized by automatically in 10.14.5.

Edited by telepati

Share this post


Link to post
Share on other sites
5 hours ago, telepati said:

 

This also dumps from real iMac19,1. You probably know better than me :wink_anim:

 

 

 

Credits; DexterOX

 

 

I think i7 9700K will be recognized by automatically in 10.14.5.

We should tell about CPU not MacModel.

I saw iMac19,1 with i7-8700.

Share this post


Link to post
Share on other sites
6 hours ago, telepati said:

 

This also dumps from real iMac19,1. You probably know better than me :wink_anim:

 

ioreg.png.a84d620305fcc28cbd5f2d57bd6ca914.png

 

Credits; DexterOX

 

 

I think i7 9700K will be recognized by automatically in 10.14.5.

 

Thanks.

 

As @Slice, I saw Imac19,2 with i7-8700 in everyman.com site. But there is also IMac19,1 for i5-9600K. So what SMBIOS is good for i7-9700K in config.plist?

https://everymac.com/systems/apple/imac/specs/imac-core-i7-3.2-21-inch-aluminum-retina-4k-early-2019-specs.html

 

Everymac.com:

"The iMac "Core i9" 3.6 27-Inch Aluminum (Retina 5K, 2019/Coffee Lake) technically is a "configure-to-order" configuration of the iMac "Core i5" 3.1 27-Inch (5K, 2019) or iMac "Core i5" 3.7 27-Inch (5K, 2019)"

 

Share this post


Link to post
Share on other sites

I need to see DMI dumps from models with other CPU

iMac "Core i3" 3.6 21.5-Inch (4K, Early 2019) or iMac "Core i5" 3.0 21.5-Inch (4K, Early 2019), 

 

Share this post


Link to post
Share on other sites
On 4/23/2019 at 10:03 AM, Badruzeus said:

Well, I have few questions:

1. Why after writing boot1f32 my EFI partition (/dev/disk0s1) becomes "Unknown"..?

 

Screenshot 7.png

 

 

Which software is this?

Share this post


Link to post
Share on other sites
On 5/11/2019 at 7:45 AM, apianti said:

Siiiiiiiiiiiiiiiiiiiiiiiiiiiiigggggggggggggggggghhhhhhhhhhhhhhhh...................... You missed my point, it is not reading the EFI entries. It is reading the BCD from the registry, which was populated with firmware entries by bootmgfw.efi on boot. If I go into the registry and look at the BCD I have firmware entries there, yet none of them are displayed in bcdedit /enum all. Also as I said it can create one entry {bootmgr}, I'm pretty sure what you describe in the other topic is a bug (just like the enumeration one I am saying there is) not to mention that yes it includes the option data which can cause undefined behavior in whatever you created when launched... If it was able to create actual entries then you would be able to add an entry that is simply a firmware application, you cannot do this. The only way to edit EFI entries is to use the windows API. Windows applications and drivers can't even read or write nvram variables without a special certificate from microsoft (that you must request and provide reasons why you need to use nvram), and additionally being signed, having two special attributes, being run as an administrator or the system and that user has to have a special privilege. What you have described is actually an easy way for a rootkit to be installed, which completely defeats the purpose of all their restrictions on nvram access.

I use EasyBCD to edit/add/reorder Windows boot entries and EasyEFI to edit/add/reorder NVRAM boot entries. I try not to mess with the windows boot entry because either the firmware or Windows wants it to exist a certain way but I can change the order of the entries at least.

 

Share this post


Link to post
Share on other sites
22 hours ago, Funky frank said:

 

Which software is this?

That image is from DarwinDumper.

 

And to answer Badruzeus' question, DarwinDumper adds the name of the Loader to the dump by identifying known bytes in the MBR. If you see Unknown then that just simply means the code is not known by DarwinDumper rather than there being anything necessarily wrong with your MBR. 

 

DarwinDumper is old now and mostly out of date, better to see newer program's like headkaze's Hackintool and the Acidanthera repo for newer code for various tools

Share this post


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

That image is from DarwinDumper.

 

Which is also your "baby". :)

 

Quote

DarwinDumper is old now and mostly out of date

 

It's also one of the best tools I've ever used. You should be proud of it. :) 

Edited by arsradu

Share this post


Link to post
Share on other sites
Posted (edited)

smc v3.

i have to remove rev and commented rev key in datahub.

fakesmc write rev key and clover overwrite rev key from platformdata.

136462451_2019-05-319_55_09.png.71ee36629b5dac174afcfa522f501ecf.png

 

we need to think idea.. i think if we can control with non-touched fakesmc, will be better

Edited by Sherlocks

Share this post


Link to post
Share on other sites

REV key is model specific. As we can change model in Clover then Clover should set the key and override previous defined key.

Share this post


Link to post
Share on other sites
REV key is model specific. As we can change model in Clover then Clover should set the key and override previous defined key.

yes. can clover remove previous defined rev key if i use mbp15,1?

we just disable rev in datahub, still alive rev. because fakesmc write rev 1.33f?.

so we override disable key or remove 1.33f?

 

나의 SM-N960N 의 Tapatalk에서 보냄

 

 

 

Share this post


Link to post
Share on other sites

On clover boot screen I am pressing F4 and boot screen freezes. I can't make a boot, I must force reset from the case. I am using v4934. Does anybody know why this happening?  

 

 

Share this post


Link to post
Share on other sites

Hi

 

I can't restart or shutdown on my new Hack (Asus Prime Z390-A, i7 9700K) with Clover r4937. Does anybody know why?

 

Sorry if this issue is Off-Topic

Share this post


Link to post
Share on other sites
17 hours ago, Sherlocks said:

yes. can clover remove previous defined rev key if i use mbp15,1?

we just disable rev in datahub, still alive rev. because fakesmc write rev 1.33f?.

so we override disable key or remove 1.33f?

 

나의 SM-N960N 의 Tapatalk에서 보냄

 

 

 

We should erase the key from FakeSMC. Let it be always from Clover present or not to be depend on Model.

 

14 hours ago, telepati said:

On clover boot screen I am pressing F4 and boot screen freezes. I can't make a boot, I must force reset from the case. I am using v4934. Does anybody know why this happening?  

 

 

Looks like your ACPI has some difficulties for Clover. Provide, please, debug.log to see the moment of the stop.

 

11 minutes ago, Matgen84 said:

Hi

 

I can't restart or shutdown on my new Hack (Asus Prime Z390-A, i7 9700K) with Clover r4937. Does anybody know why?

 

Sorry if this issue is Off-Topic

It is surely on-topic.

There was several changes in Clover concerning CoffeeLake CPU. You should search what is the key.

First I will propose to set manually

CPU->Type = 0x0705

Share this post


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

On clover boot screen I am pressing F4 and boot screen freezes. I can't make a boot, I must force reset from the case. I am using v4934. Does anybody know why this happening?

Running 4934 here. Aaand..no issues getting the ACPI tables on my side. So, as Slice mentioned, it's most likely something specific for your case. :)

 

Just wanted to share my own results, so you don't think it's a general issue with this version. Cause it doesn't look like it.

Edited by arsradu

Share this post


Link to post
Share on other sites
Posted (edited)
1 hour ago, Slice said:

We should erase the key from FakeSMC. Let it be always from Clover present or not to be depend on Model.

 

Looks like your ACPI has some difficulties for Clover. Provide, please, debug.log to see the moment of the stop.

 

It is surely on-topic.

There was several changes in Clover concerning CoffeeLake CPU. You should search what is the key.

First I will propose to set manually

CPU->Type = 0x0705

 

Thanks @Slice

 

Where should I set CPU>Type in config.plist

 

PS: I remove kexts one by one, and now I can reboot or shutdown correctly. If issue remains again, I post debug.log

Edited by Matgen84

Share this post


Link to post
Share on other sites
2 hours ago, Matgen84 said:

Hi

 

I can't restart or shutdown on my new Hack (Asus Prime Z390-A, i7 9700K) with Clover r4937. Does anybody know why?

 

Sorry if this issue is Off-Topic

It's all about broken NVRAM on Z390. Add EmuVariableUefi.efi in Drivers64UEFI and restart/shutdown will work.

EmuVariableUefi-64.efi.zip 

Share this post


Link to post
Share on other sites
4 hours ago, vandroiy2012 said:

It's all about broken NVRAM on Z390. Add EmuVariableUefi.efi in Drivers64UEFI and restart/shutdown will work.

EmuVariableUefi-64.efi.zip 

 

Thanks :)

 

I actually use AptioMemoryFix. Also I've to change for OSXAptioFix_Drv-64, Right or Not?

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 shinho73
      Hello everyone. I managed to install AMD Sierra V5(10.12.6) on my old AMD A8 7600 PC(Mother Board-A58M-E, GPU- Palit Geforce GT730 DDR3). Everything is working except the GPU. The GT730 DDR3 GF108 is natively supported on Sierra, but for some reason, it is not working. On Clover Config, "Inject Nvidia" is selected, no Nvidia Web, and nv_disable=1. On "About This Mac" it just says " NVIDIA Chip Model 3 MB".
      I have attached config.plist. Can someone look at it please? Any help will be greatly appreciated. Thank you. 





      config.plist
    • By fusion71au
      Clover r5050 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r5050 for VMware.zip". Mount Clover-v2.5k-5050-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 MaLd0n
      ---TUTORIAL---

      https://olarila.com/forum/viewtopic.php?f=50&t=8685
       
      --Original Post--
       
      https://olarila.com/forum/viewtopic.php?f=97&t=11237
       
      --Bios/UEFI Settings--
       
      *Update bios/uefi to F7+*
      1- Go to M.I.T./Advanced Frequency Settings tab
       
      Extreme Memory Profile (X.M.P.) - Profile 1
       
      2- Go to BIOS tab
       
      CSM Support - Disabled
       
      3- Go to Peripherals/Thunderbolt(TM) Configuration tab
       
      Security Level - No Security
      Thunderbolt USB Support - Enabled
      GPIO3 Force Pwr - Enabled
       
      4- Go to Chipset tab
       
      Internal Graphics - Enable
       
      ---CLOVER FOLDER---
      *Use this folder with FULL DSDT PATCHED
      EFI CLOVER Z390 DESIGNARE.zip
       
      ---OPENCORE FOLDER---
      *Use this folder with FULL DSDT PATCHED
      EFI OPENCORE Z390 DESIGNARE.zip
       
      ---DSDT patch requests is here---
       
      https://olarila.com/forum/viewtopic.php?f=19&t=1131
       
      ---HARDWARE---
       
      --MOBO

      GIGABYTE Z390 DESIGNARE
      -Link
      https://www.amazon.com/Z390-DESIGNARE-Gigabyte-Thunderbolt-Motherboard/dp/B07K8RJZRG/ref=sr_1_1?keywords=Z390+DESIGNARE&qid=1565492390&s=electronics&sr=1-1

      --PROCESSOR

      Intel Core i9-9900K
      -Link
      https://www.amazon.com/Intel-i9-9900K-Desktop-Processor-Unlocked/dp/B005404P9I/ref=sr_1_1_sspa?keywords=Intel+Core+i9-9900K&qid=1553358099&s=gateway&sr=8-1-spons&psc=1

      --COOLER

      CORSAIR H100i RGB PLATINUM AIO Liquid CPU Cooler
      -Link
      https://www.amazon.com/CORSAIR-H100i-PLATINUM-Liquid-Cooler/dp/B07JWB5BSN/ref=sr_1_4?keywords=WATER+COOLER+CPU&qid=1565492509&s=gateway&sr=8-4

      --MEMORY

      Corsair CMW32GX4M2C3200C16 Vengeance RGB PRO 32GB (2x16GB) DDR4 3200 (PC4-25600)
      -Link
      https://www.amazon.com/Corsair-CMW32GX4M2C3200C16-Vengeance-PC4-25600-Desktop/dp/B07GTG2T7L/ref=sr_1_15?keywords=memory+ddr4+32&qid=1553358238&s=gateway&sr=8-15

      --GPU

      MSI RX Vega 64 AIR Boost 8G OC
      -Link
      https://www.amazon.com/MSI-RX-64-AIR-8G/dp/B07DH7S1X1/ref=sr_1_2?keywords=vega+64+gigabyte&qid=1565492819&s=electronics&sr=1-2

      --SSD

      Samsung 970 EVO 1TB SSD (MZ-V7E1T0BW) NVMe M.2 V-NAND
      -Link
      https://www.amazon.com/Samsung-970-EVO-1TB-MZ-V7E1T0BW/dp/B07BN217QG/ref=sr_1_1?keywords=s+samsung+970+evo+1tb&qid=1565493002&s=electronics&sr=1-1

      --POWER SUPPLY

      EVGA Supernova 1000 P2 80+ Platinum, 1000W ECO Mode Fully Modular 
      -Link
      https://www.amazon.com/EVGA-Supernova-Platinum-Crossfire-220-P2-1000-XR/dp/B00EKJQM5E/ref=sr_1_3?keywords=power+supply+1000w&qid=1565493196&s=gateway&sr=8-3

      --WIRELESS

      TP-Link Archer T9E
      -Link
      https://www.amazon.com/TP-Link-Archer-T9E-Beamforming-Technology/dp/B00TQEX7AQ/ref=sr_1_1?keywords=TP-Link+Archer+T9E&qid=1553358397&s=gateway&sr=8-1

      --CASE

      Thermaltake Core P5 Tempered Glass Black Edition ATX Open Frame Panoramic Viewing
      -Link
      https://www.amazon.com/Thermaltake-Tempered-Panoramic-Certified-CA-1E7-00M1WN-03/dp/B01N4IGVSC/ref=sr_1_2?keywords=Thermaltake+Core+P5&qid=1565493567&s=gateway&sr=8-2

      --DSDT Patches--
      -FIX ACPI ERRORS -FIX OEM SSDTs to AVOID ERRORS AND WARNINGS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA -DMAC -REMOVE PROBLEMATIC AND UNUSED DEVICES -FIX K.P in REBOOT -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -FWHD -USBX -PMCR -PPMC -XSPI -CNVW -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES ---SCREENSHOTs---




















      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Thanks to KGP for SSDT Thunderbolt
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
      We're all here to have fun and learn from each other!
    • By kylon
      Cloud Clover Editor is an open source application that allows you to manage various Hackintosh Bootloaders configs everywhere.

      Open Cloud Clover Editor
       
      Cloud Clover Editor Wiki
      Cloud Clover Editor Sources
       
       
      Features
      Supports Clover EFI, Ozmosis, Chameleon, OpenCore GUI and Text Editor Mode CCE Bank Mobile friendly  
      Officially supported browsers
      Chrome 42+ Microsoft Edge 14+ Firefox 39+ Safari 10+ Opera 29+ Opera Mobile 12+ Chrome for Android 75+ Firefox for Android 67+  
       
      Credits
      mackie100 - took some ideas from his app Clover EFI dev team Eric Slivka - new serial number Virtual1 - new serial number cecekpawon - PHP 5.3.3 patch, , help with the ACPI Loader Mode flag and more Micky1979 - Clover flying editor  (Discontinued) crusher. - Help with the ACPI Loader Mode flag Download-Fritz - Help with the ACPI Loader Mode flag Pavo - Ozmosis fields and values stehor - Ozmosis fields and values Sherlocks - General help and support gujiangjiang - General help and support  
      Please let me know if i forgot you!
    • 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) ->  Link download
       Può essere solo aggiunto manualmente scaricando dal link sopra e collocandolo nella rispettiva cartella
       NOTA: in questo caso non selezionare nessun OsxAptioFixDRV durante l'installazione di clover oppure rimuovetelo                        successivamente. 
                               : 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
       
       
       
       
       
       
       
       
       
       
       
       
       
×