Jump to content
ErmaC

Clover General discussion

17,629 posts in this topic

Recommended Posts

Slice is glad to present a new EFI bootloader.
CLOVER
Now version 2 rEFIt based.


It is open source based on different projects: Chameleon, rEFIt, XNU, VirtualBox. The main is EDK2 latest revision.
I also want to thank all who help Slice with the development. Credits and copyrights remain in the sources.
http://cloverefiboot.sourceforge.net/

Main features:

 

  • Boot into 10.4 - 10.8 OSX, Windows EFI and Linux EFI
  • Boot into LegacyOS (WindowsXP, Linux, DOS) by their bootsectors
  • This is EFI bootloader so it provides RuntimeServices for OS that impossible for Legacy Bootloaders
  • Mostly Clover do automatic detection of hardware and set all properties by default. But user can change them by config.plist
  • with Clover you may restart into other OS from Startup Disk prefPane
  • Config autodetect by OEM product name
  • UUID written into config.plist will be the same as in OS
  • Autopatch OemDSDT for working OSX
  • SMBIOS will be corrected to standard 2.6
  • ACPI will be corrected to standard 4.0. Custom DSDT will be loaded from booted partition or from EFI folder
  • MADT table may be corrected to resolve problem with NMI on some hardware
  • ACPI tables loading (SSDT-xx, APIC, BOOT, SLIC, SLIT, SRAT, UEFI...)
  • Correctly set PowerProfile for laptops (notebooks), desktops, workstations
  • Customizable RestartFix
  • sleep/wake fixes
  • PCIRootUID value (0,1) for device-injection for those who can't edit DSDT
  • Graphics Properties Injector for ATI, NVidia and Intel for wide range of supported cards. Also customizable.
  • Custom EDID for non-DDC monitors
  • USB fix (LegacyOff, Ownership, Builtin, clock-id) up to USB 3.0
  • HDA injector, HDMI fix.
  • Ethernet builtin injector
  • CPU turbo
  • P- and C-states generator
  • PLimitDict and UnderVoltage for CPU Speedstep
  • patch kernel on the fly for unsupported CPU like Atom and Ivy Bridge
  • patch kexts inside kernelcache for unsupported hardware
  • Extra kexts loading
  • Security mode for FireWire
  • Default boot after timeout
  • Customizable GUI: themes support, own icons, fonts.
  • There is a possibility to implement national languages and fonts. F1 - multilingual help
  • Saving boot.log in OS and preboot.log from GUI by typing F2
  • Save original (OEM) ACPI tables by pressing F4
  • Test DSDT patching with F5
  • Save videoBIOS into EFI/misc by pressing F6
  • Saving screenshots from GUI typing F10
  • CD/DVD eject by F12 and refresh menu after CD insertion

 



If you have a question please provide outputs from DarwinDumper (formed from Trauma tool). Thanks Trauma!
Continued by blackosx and STLVNUB.

-----------------

Edited by Slice
new update / references added

Share this post


Link to post
Share on other sites
Advertisement

To begin with, congratulations to all of you, this project is fantastic!!!!!

 

Last night I tried the installer on my Lappy, but I can only see at boot "GPT, boot0, boot0, DONE", or something like that.

 

For those who have already installed the bootloader (Chameleon) there are specific warnings?

 

My partions on GPT disk:

 

Efi

osx 10.8.1

osx 10.8.0

 

 

Another curiosity, we can change now the APIC.aml table, for override the original, to surpass the Local Apic error for Insyde BIOSes? Is possible with this bootloader?

 

 

As soon as I can, experiment on USB key, and report results!

Share this post


Link to post
Share on other sites

Excellent job on the setting up this topic Fabio & Slice.

 

Clover has grown and expanded incredibly this year and it now supports a wealth of options, many of which I don't use either because my hardware doesn't require them, or my setup already had the required patches applied. Because of that, and also the pace of development, I've missed out on the learning, experimenting and understanding of some of Clovers options and with the previous available documentation being either the Russian PDF at AppleLife, or one of the hundreds of posts at projectosx your opening posts here make a welcome resource.

 

Keep up the great work :)

Share this post


Link to post
Share on other sites

Hi people, and thank you for your efforts !

I followed this tutorial :

How to install InstallESD.dmg to GPT. since r480.

 

First, you need to Restore InstallESD.dmg to disk by using Disk Utility.

Then, follow the stage 1 and stage 2 to install 10.7.x or 10.8.x to GPT, and auto-create the Recovery HD used for iCloud.

 

Stage 1

 

1.Remove kernelcache in InstallESD.dmg/Library/Preferences/SystemConfiguration/com.apple.Boot.plist.

<key>Kernel Cache</key> remove this line.

<string>xxxxxxxxxxxxx</string> remove this line.

2.Copy BaseSystem.dmg/System/Library/Extensions to partition of InstallESD.dmg and add other kexts (FakeSMC.kext).

3.Clover select to "Boot Mac OS X with extra kexts (skips cache)", and follow the installation with restart first time.

 

Stage 2

 

1.Remove kernelcache in target partition's /OS X Install Data/com.apple.Boot.plist.

<key>Kernel Cache</key> remove this line.

<string>xxxxxxxxxxxxx</string> remove this line.

( 10.7.x is /Mac OS X Install Data/com.apple.Boot.plist )

2.Copy InstallESD.dmg/System/Library/CoreServices and /mach_kernel to target partition's / .

3.Copy BaseSystem.dmg/System/Library/Extensions to target partition's / and add other kexts (FakeSMC.kext).

4.Boot to "OS X Install" with "Boot Mac OS X with extra kexts (skips cache)" and finish the installation.

(10.7.x is "Mac OS X Install")

 

I completed stage 1 (the installation), after restart i can't seem to detect my HFS+ drive on clover unless i change AHCI to IDE in my bios sata configuration. Once it is detected, it is stuck at [PCI Configuration Begin].

Tried FixDsdtMask = 0x0000 = Fail

npci=0x3000 PCIRootUID=0 GraphicsEnabler=Yes = fail

I did not change the smbios or anything else except doing a clean installation and following the above steps. So for stage 2, do i perform all these steps from the shell or any other way (like from windows partition for instance)?

I have an Asus G53JW-A1 with nvidia 460m GTX 1.5 Gb memory, and its working pretty well with Chameleon, but was just hoping to get something more Vanilla with your masterpiece and achieve better ACPI integration (Battery, Brightness control,...).

Please let me know .

Share this post


Link to post
Share on other sites

@slayer2333 see at post #9, under AHCI timeout by bcc9,

 

kext editing (or use an injector), not dsdt fix

 

 

EDIT

 

or something like this?

 

<key>0</key>
  <dict>
    <key>Name</key>
    <string>IOAHCIBlockStorage</string>
    <key>Find</key>
    <string>example in bcc9 script</string>
    <key>Replace</key>
    <string>example in bcc9 script</string>
  </dict>

 

???? :|

Share this post


Link to post
Share on other sites

Hi Slice.

I have absolutely no experience with ATI card (I don't have one).

 

One question related to Ati injector...

I see in the source only the "generic" Device ID like this:

{ 0x688D, 0x00000000, CHIP_FAMILY_CYPRESS,"AMD FireStream 9350",kZonalis},

 

Any reason for not add the specific SubId?

I have a lot of it... if you wont also add it...

 

Fabio

Share this post


Link to post
Share on other sites

I tried the last versione of Clover and i found this problem.

 

Boot Clover .

Press "O" .

Enable "Turbo" .

 

When i want to exit from menu and try to boot Clover Freeze. I'm alone?

Share this post


Link to post
Share on other sites

Hi Fabio,

It works without any knowledge about specific SubsystemID.

Dunno about NVidia but sure about ATI algorithm. It works also for Mobile Radeons.

 

I tried the last versione of Clover and i found this problem.

 

 

 

When i want to exit from menu and try to boot Clover Freeze. I'm alone?

I think the "Turbo" is a dangerous characteristic but I can't make a proof if it is allowed.

Share this post


Link to post
Share on other sites

hello

 

@slice

 

the customedid key for me don't work, clover loads the key, but result in nothing if don't apply the fix in file

 

/System/Library/Displays/Overrides/DisplayVendorID-756e6b6e/DisplayProductID-717

 

i don't have graphics at all, only black screen.

 

good hack

Share this post


Link to post
Share on other sites

hello

 

@slice

 

the customedid key for me don't work, clover loads the key, but result in nothing if don't apply the fix in file

 

/System/Library/Displays/Overrides/DisplayVendorID-756e6b6e/DisplayProductID-717

 

i don't have graphics at all, only black screen.

 

good hack

This is something that I don't know.

Share this post


Link to post
Share on other sites

Slice, I've set SMBios to Mac Pro 5,1, but after booting from Clover, it is always become iMac12,1.

What can I do if I want to force it to identify the system as MacPro5,1?

 

This is the config.plist which I'm using now.

 

.
.
<key>SMBIOS </key>
<dict>
<key>BiosReleaseDate</key>
<string>03/21/12</string>
<key>BiosVendor</key>
.
.

 

-Problem Solved-

Share this post


Link to post
Share on other sites

See if removing that space after SMBIOS helps.

 

<key>SMBIOS </key>

Thank you very much. Problem solved... :)

 

It's hard to notice the space in Xcode....

Share this post


Link to post
Share on other sites

Can anyone give me an example about how to hide partition in Clover?

I don't understand what the introduction means.

 

What should I key for "VolumeString" and "String or it's part from boot.log?"

 

Is VolumeString the name of partition or something like disk2s1 or the UUID of the partition?

Share this post


Link to post
Share on other sites

hello

 

@slice

 

the customedid key for me don't work, clover loads the key, but result in nothing if don't apply the fix in file

 

/System/Library/Displays/Overrides/DisplayVendorID-756e6b6e/DisplayProductID-717

 

i don't have graphics at all, only black screen.

 

good hack

if you have a Laptop must work, but I doubt if you are using an external monitor, their EDID are published by their EEPROM, so, attention if your Display product/vendor ID already exists in your Overrides folder.

ProductID-717 indicate a generic files generated by Osx visible in ioreg (not a real product ID), and video acceleration is really required for override the EDID, your display must be attached to the framebuffer, without, injection does not work!

 

 

search mmod, for real Product/Vendor ID

myedid.png

 

Micky

Share this post


Link to post
Share on other sites

Hi all, this is a very great job , but i dont unterstound , i have two answer , wich is config.plist of edited?

http://www.mediafire...4jiib4fupsd4n3d

 

The first or second in OEM folder

 

and why is slow between the boot done to get to the screen shots of the theme?

the first from the left work!

 

/EFI/config.plist

Share this post


Link to post
Share on other sites

Can anyone give me an example about how to hide partition in Clover?

I use the volume GUID. So for example, here's mine:

<key>Volumes</key>
<dict>
<key>HideAllLegacy</key>
<string>Yes</string>
<key>HideVolumes</key>
<dict>
<key>0</key>
<dict>
<key>VolumeString</key>
<string>F55D9AC4-08A8-4269-9A8E-396DBE7C7943</string>
</dict>
<key>1</key>
<dict>
<key>VolumeString</key>
<string>43EB9A16-6572-4B7F-A537-6303895DAE0A</string>
</dict>
</dict>
</dict>

You can get the GUID of each volume by checking your Clover bootlog.

Or easier still, run DarwinDumper and select the Disk Volume UUID & GUID option.

Share this post


Link to post
Share on other sites

if you have a Laptop must work, but I doubt if you are using an external monitor, their EDID are published by their EEPROM, so, attention if your Display product/vendor ID already exists in your Overrides folder.

ProductID-717 indicate a generic files generated by Osx visible in ioreg (not a real product ID), and video acceleration is really required for override the EDID, your display must be attached to the framebuffer, without, injection does not work!

 

 

hello

 

i use the lcd note

 

and the customedid is loaded by the key and string, is show in boot.log

 

but no works

 

only work with the edid in file

 

Captura de ecrã 2012-09-23, Ã s 22.02.28.png

 

good hack

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   1 member

  • Similar Content

    • By fusion71au
      Clover r4542 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 14 running OSX 10.9 -->10.14 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4542 for VMware.zip". Mount Clover-v2.4k-4542-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
      First... If you need DSDT edits for SkyLake, KabyLake or CoffeeLake... -Post your full Clover folder with original tables in Origin folder(Extract with F4 in Clover boot screen) -Run it, post files generated in your desktop RunMe.app  Installation   --Create a bootable copy of macOS Sierra Check out the link http://www.insanelymac.com/forum/files/file/559-flash-drive-maker/   --Create a bootable copy of macOS HighSierra Check out the link http://diskmakerx.com/   --Install Clover in USB stick https://sourceforge.net/projects/cloverefiboot/files/Installer/   --Replace with my Clover folder  CLOVER.zip   --Install Sierra/High Sierra and boot into system!   Post Installation   --Install Clover in HDD/SSD and replace with my folder CLOVER.zip   --Reboot and activate video!   -Nvidia WebDriver Sierra http://www.insanelymac.com/forum/topic/312525-nvidia-web-driver-updates-for-macos-sierra-update-07212017/ -Nvidia WebDriver High Sierra http://www.insanelymac.com/forum/topic/324195-nvidia-web-driver-updates-for-macos-high-sierra-update-10162017/ -Cuda http://www.insanelymac.com/forum/topic/302795-cuda-90214-is-out-update-10162017/   --DSDT My DSDT with patches for Skylake DSDT.MaLd0n ASUS Z170M PLUS.zip   Patches -FIX ERRORS AND WARNINGS -HPET -SATA -SLPB -DMAC -DARWIN -LPC -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -RTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -USBX -PMCR -EC -IMEI -PNLF -HDMI --FakeSMC
      http://www.hwsensors.com/releases   --Audio https://github.com/vit9696/AppleALC   --USB https://bitbucket.org/RehabMan/os-x-usb-inject-all/downloads   --LAN https://github.com/Mieze/IntelMausiEthernet   -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!   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 and many, many, many others!   We're all here to have fun and learn from each other!   ENJOY!
    • By zebity
      Hi Hypervisors,
       
      EDITED - 9 JUNE 2018 - as all other issues resolved but am now stuck with QEMU Error: "PFLASH: Possible BUG - Write Block Confirm" details on testing lower in thread (to follow).
       
      I have been working to move my Late 2009 Xserve MacOS Server onto Ubuntu 18.04 LTS QEMU/KVM based virtual machine using OVMF and Clover.
       
      After much effort and testing based on the following information from: Kraxel's, Kholia, Gordon Turner and Clover site:
      https://www.kraxel.org/blog/2017/09/running-macos-as-guest-in-kvm/
      https://github.com/kholia/OSX-KVM
      https://gist.github.com/gordonturner/2a2e5ecde5e7860b52e2
      https://clover-wiki.zetam.org/Home
       
      I have now managed to get OVMF/Clover boot and install of MacOS Sierra.
       
      I started with Ubuntu 16.04 initially but this required download and compile of QEMU to get update of machines to: pc-q35-2.9 or better, so I moved to Ubuntu 18.04, which has pc-q35.2.11 available as standard.
       
      So I am now working with standard Ubuntu 18.04 LTS based systems with following packages: kvm/qemu/libvirt/bridge-utils/ovmf/virt-manager
       
      As I want to use PCIe Passthrough for a number of PCIe card currently installed in the server (SmallTree 10GbE & Areca ARC-1883 SAS RAID) I set up my machine with linux kernel boot configuration (/etc/default/grub) of: 
      GRUB_CMDLINE_LINUX_DEFAULT="iommu=1 intel_iommu=on" (as my machine is intel VT-d based HW virtualisation)
       
      This resulted in creation of a number of iommu groups (see /sys/kernel/iommu_group directory for this and this posting for information: https://forum.level1techs.com/t/ubuntu-17-04-vfio-pcie-passthrough-kernel-update-4-14-rc1/119639 , noting that Ubuntu 18.04 LTS has kernel version: 4.15.0-22-generic so there is no need to do kernel update for iommu to work).
       
      Using bare minimal Clover config.plist:
       
       
      And following Clover UEFI drivers:
       
      I can boot MacOS, but it is very very slow... it sits on the apple boot logo for over a minutes before finally moving onto the progress bar.
      The other problem I have is that no PCI or Network devices appear in the "About This Mac" System Information Report and I cannot get any network connectivity from bridged E1000 network device.
       
      Here is my virtlib.xml dump for the virtual machine:
       

      Can any one advise of whether I need to update the CLOVER config.plist to add extra items in to allow network and PCI Passthrough to work.
       
      Thank you.
       
      Regards,
       
      Zebity
       
    • 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.13.... 
      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
       
       
       
      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 Trung_Nguyen
      Hello, I have been a long time with the DSDT.aml and an old BIOS so I decided to go to full hotpatch in order that I could update my BIOS flawlessly
      Most things works now(Audio,Brightness slider,...)except the Bluetooth and the Brightness key(IOWMIFamily)
      The Bluetooth is located on an USB hub and now it said Bluetooth: Not Available and not found in Sysinfo BT sub-page.
      I tried to patch the _Q66 into XQ66 to add the code the notify the driver but it doesn't seem to work. The brightness key no longer work on it own(as I have patch the _OSI). So the last thing to do is patch the _Q66 to receive the signal.
      Thanks all
      Archive.zip
×