Jump to content

Creare il file di configurazione "config.plist"

1 post in this topic

Recommended Posts

Utilizzando Clover come bootloader al suo interno troviamo il file di configurazione detto config.plist

Il config.plist deve essere messo in EFI/Clover/

Il file di configurazione è scritto in XML, ma può essere utile per vederlo come file di testo.
Può essere modificato da semplici editor di testo o editor plist.

In alternativa agli editor si può utilizzare questa app Clover Configurator semplice e bella dalla grafica.


Aprite Clover Configurator e vi chiederà di montare la partizione EFI cliccate Mount EFI partition


Mettiamo la password


Troviamo la EFI sulla scrivania


Cicchiamo Open Partition




File/Import Configuration/EFI/Clover/config.plist


Il config.plist è caricato adesso possiamo fare le modifiche al file di configurazione.


Download : http://mackie100.webwacemaster.altervista.org/#

Struttura del config.plist : http://clover-wiki.zetam.org/Configuration


Share this post

Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By fusion71au
      Create Custom Entries to Hide Preboot and Recovery APFS Volumes with Clover Configurator
        With the release of High Sierra and the APFS file system, Clover users now have "extra" entries appearing in their Main Menu - Preboot and Recovery APFS volumes.  While they are harmless and actually useful in certain circumstances (eg need Preboot to boot if using File Vault encryption, need Recovery to fix some file system problems), most users will likely want to hide them in day to day use.    
      Note:  This guide is tailored to those users who want to understand how to create custom APFS entries and the "nuts and bolts" of how Clover parses the file system looking for efi loader entries.   If all you want to do is hide entries, the easiest way is through the GUI/Hide section of the config.plist.  This won't allow you to rename custom entries, nor unhide them with the <F3> key (at least not till Clover r4247).   Pre-requisites macOS High Sierra installed on APFS SSD or HDD Clover r4097+ with apfs.efi installed in /EFI/CLOVER/drivers64UEFI or /EFI/CLOVER/drivers64 Clover Configurator v or later   Procedure 1.  Record output of "diskutil list" and "diskutil apfs list" to determine the layout of the actual physical disk(s) and the synthesized APFS container.   In my example, the High Sierra Volume is named macOS_HS and is installed in physical disk partition disk3s4.   fusion71aus-iMac:~ fusion71au$ diskutil list /dev/disk3 (internal, physical):    #:                       TYPE NAME                    SIZE       IDENTIFIER    0:      GUID_partition_scheme                        *1.0 TB     disk3    1:                        EFI EFI                     209.7 MB   disk3s1    2:       Microsoft Basic Data DATA                    935.6 GB   disk3s2    3:         Microsoft Reserved                         134.2 MB   disk3s3    4:                 Apple_APFS Container disk4         63.6 GB    disk3s4    5:       Apple_KernelCoreDump                         655.4 MB   disk3s5 /dev/disk4 (synthesized):    #:                       TYPE NAME                    SIZE       IDENTIFIER    0:      APFS Container Scheme -                      +63.6 GB    disk4                                  Physical Store disk3s4    1:                APFS Volume macOS_HS                34.3 GB    disk4s1    2:                APFS Volume Preboot                 20.9 MB    disk4s2    3:                APFS Volume Recovery                519.6 MB   disk4s3    4:                APFS Volume VM                      20.5 KB    disk4s4         2.  Generate Clover Boot Log with terminal bdmesg > ~/Documents/bootlog.txt Note: for easier analysis of boot log, please remove all Custom/Hidden Entries from config.plist/GUI first (leaving only Clover auto scanning) before generating it.   3.  Open bootlog.txt with a text editor and under the [ ScanLoader ] section, note the volume numbers corresponding to the Preboot, High Sierra and Recovery APFS volumes...
        Preboot Volume ---> 24 High Sierra Volume ---> 25 Recovery Volume ---> 26   4.  Under [ ScanVolumes ] section, record the UUIDs of the above 3 Volumes In this example   Vol 24 = Preboot: E38C70C3-C1C1-4096-B2DE-2EE2660FCE41,0x6CF46800,0x7687D88)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,050BA2A72D1D0E4D8ABDE9B99632868E Partition UUID = E38C70C3-C1C1-4096-B2DE-2EE2660FCE41 Vol UUID = 050BA2A72D1D0E4D8ABDE9B99632868E (little endian format)   Vol 25 = macOS_HS: E38C70C3-C1C1-4096-B2DE-2EE2660FCE41,0x6CF46800,0x7687D88)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,67B6FC62811C594E819DACAE2F90240D Partition UUID = E38C70C3-C1C1-4096-B2DE-2EE2660FCE41 Vol UUID = 67B6FC62-811C-594E-819D-ACAE2F90240D (little endian format), 62FCB667-1C81-4E59-819D-ACAE2F90240D (big endian format)   Vol 26 = Recovery: E38C70C3-C1C1-4096-B2DE-2EE2660FCE41,0x6CF46800,0x7687D88)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,F3D73FFF25C8334DAF3C183BC35433DF Partition UUID = E38C70C3-C1C1-4096-B2DE-2EE2660FCE41 Vol UUID = F3D73FFF25C8334DAF3C183BC35433DF (little endian format)   Note the partition UUIDs for all the APFS volumes are the same because they are all formed from the same physical disk partition disk3s4 = E38C70C3-C1C1-4096-B2DE-2EE2660FCE41   5.  Mount the APFS Volumes to determine the "path" to boot.efi for the Preboot and Recovery Volumes.   In terminal: fusion71aus-iMac:~ fusion71au$ diskutil mount disk4s2 Volume Preboot on disk4s2 mounted fusion71aus-iMac:~ fusion71au$ diskutil mount disk4s3 Volume Recovery on disk4s3 mounted fusion71aus-iMac:~ fusion71au$ open /Volumes   In Finder, the hidden folder /Volumes will open (or use "ShowAllFiles.app" attached)... Record the "path to boot.efi" by expanding the directory tree of Preboot and Recovery (hint: drag the icon of boot.efi to a terminal window for full path):     So for Preboot Volume, path = /Volumes/Preboot/62FCB667-1C81-4E59-819D-ACAE2F90240D/System/Library/CoreServices/boot.efi --> record as \62FCB667-1C81-4E59-819D-ACAE2F90240D\System\Library\CoreServices\boot.efi   and for Recovery Volume, path = /Volumes/Recovery/62FCB667-1C81-4E59-819D-ACAE2F90240D/boot.efi ---> record as \62FCB667-1C81-4E59-819D-ACAE2F90240D\boot.efi   Notes Need backslashes in the path, including the leading \ The UUID in the paths to boot.efi, for both the Preboot and Recovery APFS volumes, is the same = Vol UUID of the High Sierra Volume in big endian format...  
      6.  Open Clover Configurator, mount EFI System Partition to edit /Volumes/EFI/EFI/CLOVER/config.plist 7.  Click GUI section on LHS and the + sign under Custom Entries to create New Custom Entry     8.  Create Preboot High Sierra Custom Entry   In Volume, copy and paste Vol UUID of Preboot Volume from step 4 In Path, copy and paste path to boot.efi from step 5, including the leading \ Click Title/FullTitle and enter the display name you want eg "Preboot High Sierra"  Set Injectkexts and Hidden attributes to Yes Set Entry type to OSX Leave VolumeType blank   9.  Create APFS Recovery Custom Entry   In Volume, copy and paste Vol UUID of Recovery APFS Volume from step 4 In Path, copy and paste path to boot.efi from step 5, including the leading \ Click Title/FullTitle and enter the display name you want eg "APFS Recovery"  Set Injectkexts and Hidden attributes to Yes Set Entry type to OSXRecovery Leave VolumeType blank   10.  Save config.plist and reboot the system.  At the main Clover Menu, you should see something like this ...     To unhide the custom APFS entries, press the F3 key  
      Update: New "macOS Install Prebooter" Entry with Clover r4225+
      Clover r4225+ has added new code to detect OS X installer data on the Preboot Volume ---> causes an extra entry at the Clover Main Menu: "Boot macOS Install Prebooter from Preboot"... 

      If you mount your Preboot volume, you will see ...

      Method for hiding the new entry would be similar to hiding the Preboot Entry discussed above:
      In Volume, copy and paste Vol UUID of Preboot Volume from step 4 In Path, copy and paste path to boot.efi from step 5, including the leading \ (eg \UUID\com.apple.installer\boot.efi ) Click Title/FullTitle and enter the display name you want eg "High Sierra Install Prebooter"  Set Injectkexts and Hidden attributes to Yes Set Entry type to OSXInstaller Leave VolumeType blank Custom Entry for Fusion Drive Installation of Sierra or High Sierra - post#22.
    • By Micky1979
      A web-based Clover's config.plist editor, wrapper for kylon's CCE (Clover Cloud Editor).
      Info about CCE:
      Info about this app:
      Clover flying editor is a web browser based on WebKit (code comes from Pandora's Box), Clover Cloud Editor is a PHP project © 2016 kylon, so this app is just a wrapper, in fact you can simply load it in Safari/Opera/Firefox/IE etc. by click here .
      The app works on Lion~Sierra.
      The purpose is to promote and help kylon's project.
      Adding a download Manager for compressed file extensions (.zip, .tar.bz2 etc).
    • By miliuco
      Cómo habilitar Mensajes en el Hackintosh con El Capitán
      NOTA1: texto basado en el excelente artículo de grantfitz “Simple iMessage Guide for Yosemite and El Capitan” del que es prácticamente una traducción con algunas aportaciones propias.
        NOTA2: requiere el uso de Clover Configurator de mackie100projects.   Interfaz de red con el nombre BSD En0   Como paso previo, es imprescindible que la interfaz de red que usamos para conectar a Internet, cable o wifi, sea En0 en Perfil de Sistema. Si no es así, hay que borrar los archivos NetworkInterfaces.plist and preferences.plist de la carpeta /Library/Preferences/SystemConfiguration y reiniciar el ordenador antes de continuar.   SMBIOS Copia al Escritorio el archivo /EFI/CLOVER/config.plist para poder modificarlo. Abre config.plist desde Clover Configurator. En la pestaña SMBIOS pulsa en el icono de la varita mágica. Elige el modelo de Mac que vas a tener en tu Perfil del Sistema. En mi caso elijo iMac14,2. Hasta ahora he funcionado bien con el perfil MacPro3,1 pero recientemente Apple ha declarado obsoleto el modelo de Mac al que hace referencia por lo que conviene cambiar a otro modelo más reciente y en mi Hackintosh el iMac14,2 parece funcionar bien. A ello hay que añadir que con el perfil MacPro3,1 o MacPro5,1 no es posible ni siquiera descargar Mac OS Sierra precisamente por corresponderse con modelos obsoletos para la nueva versión del sistema operativo. Pulsa los botones Shake varias veces para que asigne semana de fabricación y número de unidad, de ambos  depende el número de serie que tendrá el sistema. Visita la página de Apple que permite comprobar los números de serie https://checkcoverage.apple.com. Comprueba el tuyo, si avisa de error por número de serie no válido, sigue adelante. En caso contrario significa que se ha generado un número de serie que se corresponde con el de un Mac real por lo que has de elegir otro número de serie pulsando los botones en Clover Configurator. En la casilla Board Serial Number has de escribir el número de serie seguido de 5 caracteres hexadecimales (números y letras), aquí tienes algunos ejemplos que puedes utilizar: W9YLL / K73PA / P1YF5 / CK217 / 2K73P / AF8JC. Abre Terminal, escribe uuidgen y pulsa INTRO. Copia el valor obtenido y pégalo en la casilla SmUUID de Clover Configurator. Guarda los cambios del archivo config.plist desde Clover Configurator. Este archivo has de copiarlo a 2 lugares reemplazando al existente:
      /Volumes/EFI/EFI/CLOVER/config.plist (para poder copiarlo aquí primero has de montar la partición EFI que por defecto está oculta, se puede hacer desde Clover Configurator que tiene esa opción, entre otras, en la pestaña de la izquierda). Eliminar configuraciones previas   Abre Terminal, pega este texto y pulsa INTRO. Puedes recibir mensajes de que alguno de los archivos no existe:   cd ~/Library/Caches/ rm -R com.apple.Messages* rm -R com.apple.imfoundation* cd ~/Library/Preferences/ rm com.apple.iChat* rm com.apple.imagent* rm com.apple.imessage* rm com.apple.imservice* rm -R ~/Library/Messages/   Reinicia el ordenador.   Aplicación Mensajes   Si todo ha ido bien, la aplicación Mensajes debería funcionar correctamente. Primero configuras la cuenta de iCloud. Y después pruebas a enviar algo desde la aplicación.   AVISO: las instrucciones y propuestas de esta página se proporcionan sin garantía de ningún tipo a la hora de llevarlas a la práctica. Lo que ha funcionado bien en mi caso pudiera no hacerlo en el tuyo.
    • By L0g4n
      Hi guys,
      wanted to install OS X El Capitan on my desktop PC using the Clover bootloader.
      That worked with a slightly modified standard config.plist from TonyMacx86 guide for Yosemite with Clover.
      Just for your information, my hardware components:
      The used config.plist is appended.
      The installation worked, but when I come to my desktop after a short period of time always the screen turns black (not when I am in safe mode, but I can not mount partitions in this mode, etc.).
      Well, obviously this seems to be a GPU related problem so I tried already different things to solve this issue:
       1. In Clover configurator I added the Fake ID "0x67B01002" under devices in "ATI".
       2. Under "Graphics" I enabled "LoadVBios" and pasted my .ROM (I exported that for my video card approx. 1 week ago with GPU-Z under windows) under EFI/CLOVER/ROM in the right format (in my case 1002_67B0.rom) (also attached).
      Unfortunately, all of this measures could not solve my issue.
      Would appreciate your help, thanks!
      EDIT: I could solve that issue. For my GPU it was necessary to insert under "Graphics" in "FBName" "kBaladi" and now it works.
    • By TheIvanovization
      Hola a todos.
      Soy relativamente nuevo en esto de la configuración del clover, y es que aunque ya tengo 1 año con una OSx86 apenas hace 6 meses comencé a usar Clover y apenas estoy aprendiendo.
      El motivo de mi post es saber si existe una forma de "restaurar" o regresar al default el config.plist con el fin de iniciar desde 0 o limpiar las configuraciones del clover sin tener que reinstalar. ¿Por qué alguien querría hacer eso? Pues porque (en mi caso) le he picado a muchos botones y he activado muchas cosas con el fin de solucionar errores pero siguen sin repararse.
      Gracias por leer y si eres o no experto en el tema te agradezco que hayas entrado.
      Felices fiestas.