Jump to content
ErmaC

Clover General discussion

18,272 posts in this topic

Recommended Posts

HFS+ (Journaled) with GPT partition scheme setup on a real Mac with Disk Utility. I always do OS X installation on real Macs as it makes things much easier.

 

Mieze

Check in the drive uses UEFI Bios is represented as EFI boot boot!!

 

If not possiver!
Riding EFI system partition and check if anything wrong in Clover installed in this unit, check also if RC scripts were installed on that partition!

Share this post


Link to post
Share on other sites
Advertisement

 

Check in the drive uses UEFI Bios is represented as EFI boot boot!!

 

If not possiver!
Riding EFI system partition and check if anything wrong in Clover installed in this unit, check also if RC scripts were installed on that partition!

 

 

Yes, I checked the Clover installation and UEFI setup several times and found no error but the issue remains:

 

connected via USB: UEFI recognizes the drive as bootable and Clover successfully boots OS X.

 

connected via SATA: UEFI doesn't recognize any boot device (the drive is the only one in the system).

 

Secure boot is disabled (tried both settings) and CSM enabled (also tried both) but those settings doesn't seem to have any influence.

 

Mieze 

Share this post


Link to post
Share on other sites

Yes, I checked the Clover installation and UEFI setup several times and found no error but the issue remains:

 

connected via USB: UEFI recognizes the drive as bootable and Clover successfully boots OS X.

 

connected via SATA: UEFI doesn't recognize any boot device (the drive is the only one in the system).

 

Secure boot is disabled (tried both settings) and CSM enabled (also tried both) but those settings doesn't seem to have any influence.

 

Mieze 

Doing so:
Initialize a pendriver with Clover;
go to Boot Options Clover;
add the UEFI Boot options

post-814746-0-62716600-1388344364_thumb.png

post-814746-0-09713400-1388344391_thumb.png

Share this post


Link to post
Share on other sites

Yes, I checked the Clover installation and UEFI setup several times and found no error but the issue remains:

 

connected via USB: UEFI recognizes the drive as bootable and Clover successfully boots OS X.

 

connected via SATA: UEFI doesn't recognize any boot device (the drive is the only one in the system).

 

Secure boot is disabled (tried both settings) and CSM enabled (also tried both) but those settings doesn't seem to have any influence.

 

Mieze 

 

Maybe your BIOS is searching for BOOTX64.efi on an internal disk???

 

Did you already tried to create an /EFI/BOOT folder at your EFI partition, make a copy of CLOVERX64.efi on it and

rename it to BOOTX64.efi???

Share this post


Link to post
Share on other sites

I had a very stressful experience a few minutes ago. I installed the 2427 version that is in the link a few posts ago and it lost all my hdds in the boot menu Clover. There appeared no boot option on any HDD, even making boot from the USB drive. It was quite disturbing because I have one year of my work on my main system and I thought there was the possibility that, for whatever reason, anything could have erased all my hdds. I climbed my pen drive installation and could return to calm when I saw the terminal that hdds were intact, thank God! So I plugged my main hd on our other computer and reinstalled Clover, now in version 2428 and all is well again, thank God! Uf!

Share this post


Link to post
Share on other sites

I had a very stressful experience a few minutes ago. I installed the 2427 version that is in the link a few posts ago and it lost all my hdds in the boot menu Clover. There appeared no boot option on any HDD, even making boot from the USB drive. It was quite disturbing because I have one year of my work on my main system and I thought there was the possibility that, for whatever reason, anything could have erased all my hdds. I climbed my pen drive installation and could return to calm when I saw the terminal that hdds were intact, thank God! So I plugged my main hd on our other computer and reinstalled Clover, now in version 2428 and all is well again, thank God! Uf!

Here I have a micro sd with Clover old version;
For HD tests and do sometimes have to connect and disconnect them;
And every time I need micro sd with clover to clover boot options to enable the partitions with clover with UEFI boot, they live up losing it!

Share this post


Link to post
Share on other sites

can someone help me  configure quadro 600 in clover? i don't know  I'm experiencing lag i have done over thousand installations and sleekness nights


I'm using maverick also 

Share this post


Link to post
Share on other sites

can someone help me  configure quadro 600 in clover? i don't know  I'm experiencing lag i have done over thousand installations and sleekness nights

I'm using maverick also 

What is your specs ?

Share this post


Link to post
Share on other sites

I've exactly the same problem like toleda mentioned here in this post
http://www.insanelym...71#entry1909778

my clover boot log also says exactly this 


0:318 0:000 SetScreenResolution: 1920x1080 - not found!
0:318 0:000 SetMaxResolution: found best mode 0: 1024x768 - set

I've intelHD3000 on GA-Z86X rev1.3 i7-2600K

On login screen and inside the system my graphics card is working at good resolution. But at clover gui and apple legacy logo its not.

Thanks
 


Hi there ios9! Sadly the only thing I can tell you is to try adding the CSMVideoDxe driver (if it's UEFI boot) and to enable PatchVBios, but I'm not sure that works with the Intel graphics. Besides that, there's not much you can do. In fact I have the same resolution issue on my board while booting UEFI, which doesn't happen in legacy mode.
 
At most you may try looking for the highest resolution possible (which in my case is 1280x1024) by pressing PgUp and PgDown on Clover's GUI, and then add that resolution to your plist to force it at load.
 
Good luck!

 

Thank you very much for your help solved my problem by loading CSMVIDEODXEDRIVER into my EFI partition and patched vbios.Patch was successfull n running good at 1080p reso.
 
I tried this patchvbios without that driver for million times and confirmed myself as noob. :D
 
Thanks again.

Edited by ios9

Share this post


Link to post
Share on other sites

What is your specs ?

Here are the specs:
i7 3930K
Intel DX79SI
Bios SIX910J.86A.0525.2012.0709.1221
32 GB DDR3 667MHz
NVIDIA Quadro 600

Share this post


Link to post
Share on other sites

and also my cpu info in about this mac is showing as unknown and how to fix this 

Share this post


Link to post
Share on other sites

 

Doing so:
Initialize a pendriver with Clover;
go to Boot Options Clover;
add the UEFI Boot options

 

 

Hello Bruxo,

 

that worked and resolved the issue. Now I can even disable CSM. Obrigada!

 

Mieze

Share this post


Link to post
Share on other sites

Hello Bruxo,

 

that worked and resolved the issue. Now I can even disable CSM. Obrigada!

 

Mieze

enjoy!

Share this post


Link to post
Share on other sites

@fusion71au: may I ask you something, your BIOS doesn't have UEFI support, right? If so, that explains the differences between you and me. I'm running my system in Hybrid UEFI mode (with CSM) with Clover, installed in the EFI partition and Windows 7, installed the UEFI way. The SLIC Dump Toolkit is known to be non-working on GPT drives and UEFI BIOSes (it actually works on such BIOSes, but only in Legacy boot mode), unlike RW Everything and AIDA64 (Business and Engineer Edition, Extreme Edition has no APCI Tool), as they seem to have no problem with that. I've used both of them to determine the ACPI tables and all OEM IDs seems to be correct (and equal) according to both.

Share this post


Link to post
Share on other sites

Hi,

 

So I installed mavericks on my laptop (Asus X54C) with clover bootloader and everything went well until the first boot from the hard drive. First boot took quite long time so I booted again with -v to see whats wrong. Boot stops at IOBluetoothHCI.. and I know this is not related to bluetooth but the next step after that: graphics. I know this has been asked before but no proper solution has been posted and after trying to add fakesmc.kext, nullcpupowermanagement.kext, deleting kexts and booting with different settings I havent been able to solve this.

 

Boot with -v: https://www.dropbox.com/s/tqd9r5dijoa1m2e/Foto%2029.12.13%2021%2039%2050.jpg

 

My graphics card is Intel HD Graphics 3000 and again, Im using clover not chimera or chameleon.

 

Thanks smile.png

Share this post


Link to post
Share on other sites

@philip_petev,

 

Yes you are indeed correct, my machine uses old style BIOS.  I don't think I recall any UEFI/EFI PCs back in 2008 when I bought my XPSm1530 (besides Apple of course :) ).

 

From the Clover wiki:

BIOS--->MBR--->PBR--->boot--->CLOVERX64.efi--->OSLoader

 

That being said, the XPSm1530 is one of the most compatible laptops for OSX and is able to run any OSX from Leopard to Mavericks very well.  I boot Clover in non-uefi mode (see post by BatcOuntrY) on a pure GPT drive with protective mbr.  UEFI Windows 7_X64 is also installed and booted by Clover-EFI - see this very insightful post by Pene.

 

The SLIC Dump Toolkit incompatibility is more likely due to UEFI BIOS than disk partitioning I suspect.

Share this post


Link to post
Share on other sites

Unfortunately, my problem remains, and I don't seem to find a person here who is able to actually help me. I have to admit this is slowly become very frustrating. I am not a person who is crying for help with any little problem I encounter, but only if I really don't know what to do, and after having tried so solve everything for myself. And I still think the probs I have are - at least partly - at fault of clover, not mine.

 

Maybe related to my newer CPU and X79 rev, but nobody seems to be really interested in helping me find out. So it seems clover is not supporting 4930K or newer X79 revs at all? Or do I just ask in the wrong forum? Is there any place where you can actually get some help with clover? Maybe a place where I can talk to some devs? Shall I open some tickets?

Share this post


Link to post
Share on other sites

Newest revisions should fix issues with fourth generation cpus, and also dropping existing SLIC when injecting new one, so please upgrade to newest revision. You may need to build it since I don't think there is a package up on source forge yet.

Share this post


Link to post
Share on other sites

I built a new Clover UEFI system with following specs:

  • i7-4770k
  • Asus Maximus VI Gene C2
  • Nvidia GTX780

The bios is standard MSR unlocked and I think NVRAM is working too.

Sleep isn't working and I can't use the Eject button on my Apple keyboard (it's in the menubar).

 

I used PJALM's all-in-one patch for the DSDT, combined with Toleda's patches for audio ALC1150 and HDMI audio. The discrete graphics patch does not work, as it enters a new PEGP device and it doesn't exist resulting in an error.

I also use a SSDT for power management (kernelpm not needed) and added a MacPro5,1 Board-ID plist in X86PlatformPlugin, copied from an iMac14,2 Board-ID plist.

 

1. Power management seems to be working, I get a lot of turbo states but this likely seems to be Mavericks kernel power management.

2. How can I test if NVRAM is really working? I don't need EmuVariable64.efi and "nvram -p" shows Clover traces.

 

I'll also add my config.plist, did I forget something to get sleep to work? (without DSDT it does work)

<?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>ACPI</key>
	<dict>
		<key>DSDT</key>
		<dict>
			<key>Name</key>
			<string>DSDT.aml</string>
		</dict>
		<key>SSDT</key>
		<dict>
			<key>DropOem</key>
			<true/>
		</dict>
	</dict>
	<key>Boot</key>
	<dict>
		<key>Timeout</key>
		<integer>5</integer>
		<key>Arguments</key>
		<string></string>
	</dict>
	<key>Devices</key>
	<dict>
		<key>USB</key>
		<dict>
			<key>Inject</key>
			<false/>
			<key>FixOwnership</key>
			<false/>
			<key>AddClockID</key>
			<false/>
		</dict>
	</dict>
	<key>GUI</key>
	<dict>
		<key>Scan</key>
		<dict>
			<key>Tool</key>
			<true/>
			<key>Entries</key>
			<true/>
			<key>Legacy</key>
			<false/>
		</dict>
		<key>Hide</key>
		<array>
			<string>HD(1,GPT,031A7308-A953-448D-AC13-DF16C772C478)</string>
			<string>HD(2,GPT,D35FB078-F5FB-43C3-A6EE-856EF6C96C07)</string>
		</array>
		<key>Custom</key>
		<dict>
			<key>Entries</key>
			<array>
				<dict>
					<key>Volume</key>
					<string>0F3582E4-D5F4-42BA-8FA7-013996A0475C</string>
					<key>Path</key>
					<string>\EFI\BOOT\BOOTX64.efi</string>
					<key>Disabled</key>
					<true/>
					<key>Hidden</key>
					<true/>
				</dict>
				<dict>
					<key>Volume</key>
					<string>DAE6FD8B-3D41-4529-B1FE-006E50933417</string>
					<key>Hidden</key>
					<true/>
					<key>Disabled</key>
					<false/>
					<key>FullTitle</key>
					<string>Recovery</string>
					<key>Type</key>
					<string>OSXRecovery</string>
				</dict>
				<dict>
					<key>Volume</key>
					<string>9748EF3F-6433-45BA-80F7-F6D9FDA3EFE5</string>
					<key>FullTitle</key>
					<string>Mac</string>
					<key>Type</key>
					<string>OSX</string>
				</dict>
				<dict>
					<key>Volume</key>
					<string>896874EF-2639-4D21-9624-BC84A00130CD</string>
					<key>Path</key>
					<string>\EFI\Microsoft\Boot\bootmgfw-orig.efi</string>
					<key>FullTitle</key>
					<string>Windows 8</string>
					<key>Type</key>
					<string>Windows</string>
					<key>InjectKexts</key>
					<false/>
					<key>AddArguments</key>
					<string></string>
				</dict>
			</array>
		</dict>
		<key>Theme</key>
		<string>mlcamp</string>
		<key>DebugLog</key>
		<true/>
		<key>Mouse</key>
		<dict>
			<key>Enabled</key>
			<true/>
			<key>Speed</key>
			<integer>2</integer>
			<key>DoubleClick</key>
			<integer>500</integer>
			<key>Mirror</key>
			<false/>
		</dict>
	</dict>
	<key>Graphics</key>
	<dict>
		<key>Inject</key>
		<dict>
			<key>Intel</key>
			<true/>
		</dict>
	</dict>
	<key>KernelAndKextPatches</key>
	<dict>
		<key>AppleRTC</key>
		<false/>
		<key>AsusAICPUPM</key>
		<true/>
		<key>Debug</key>
		<false/>
		<key>KernelCpu</key>
		<false/>
		<key>KextsToPatch</key>
		<array>
			<dict>
				<key>Name</key>
				<string>IOAHCIBlockStorage</string>
				<key>Find</key>
				<data>QVBQTEUgU1NEAA==</data>
				<key>Replace</key>
				<data>AAAAAAAAAAAAAA==</data>
			</dict>
			<dict>
				<key>Name</key>
				<string>AppleTyMCEDriver</string>
				<key>Find</key>
				<data>cgoATWFjUHJvNCwxAE1hY1BybzUsMQBY</data>
				<key>Replace</key>
				<data>cgoAAAAAAAAAAAAAAAAAAAAAAAAAAABY</data>
			</dict>
		</array>
	</dict>
	<key>RtVariables</key>
	<dict>
		<key>LogEveryBoot</key>
		<string>Yes</string>
		<key>LogLineCount</key>
		<integer>3000</integer>
		<key>MountEFI</key>
		<false/>
	</dict>
	<key>SMBIOS</key>
	<dict>
		<key>ProductName</key>
		<string>MacPro5,1</string>
		<key>SerialNumber</key>
		<string>XXX</string>
		<key>SmUUID</key>
		<string>XXX</string>
	</dict>
	<key>SystemParameters</key>
	<dict>
		<key>CustomUUID</key>
		<string>XXX</string>
		<key>InjectSystemID</key>
		<false/>
		<key>InjectKexts</key>
		<true/>
		<key>XMPDetection</key>
		<true/>
	</dict>
</dict>
</plist>

Share this post


Link to post
Share on other sites

Newest revisions should fix issues with fourth generation cpus, and also dropping existing SLIC when injecting new one, so please upgrade to newest revision. You may need to build it since I don't think there is a package up on source forge yet.

 

I am at 2428 already. So there is a newer revision that may fix the problem and that I need to build on my own?

Sleep isn't working

 

Welcome to the club.

 

2. How can I test if NVRAM is really working? I don't need EmuVariable64.efi and "nvram -p" shows Clover traces.

 

You can test it by setting a bogus variable, like this: (in terminal)

sudo nvram test="test"

Then reboot and print out the NVRAM contents to see if the value survived a restart:

nvram -p

Even if you see clover related stuff in the output, that does not necessarily mean that these vars are actually persistent.

Share this post


Link to post
Share on other sites

Ok, dropping of original SLIC if new SLIC is injected is in Clover rev 2427.

@dmazar can you explain to me what happens if we drop the slic in windows folder ? I'm confused 

Share this post


Link to post
Share on other sites

It appears there is still problem with kernel power management then since that's what the fourth generation cpus now use in os x. So messing with the other stuff is probably not really doing anything useful. As for the SLIC, you can place SLIC.aml in \EFI\CLOVER\acpi\Windows\ and it will inject it. Previously it only injected the SLIC placed in this folder without checking for or dropping the previous SLIC which it should now do, removing any conflict that occured.


Although I see there appears to be a few more changes for haswell, if you can build 2431, there is no official package though.

Share this post


Link to post
Share on other sites

You'll need to know your VESA modes for your graphics card. If it doesn't support it, you can patch your VBIOS on the fly in config.plist for nvidia cards.

 

I did this for my GTX 560Ti:

 

<key>PatchVBiosBytes</key>
			 <dict>
					 <key>0</key>
					 <dict>
							 <key>Find</key>
							 <data>NC0nKJAroL+cj5a5jh8AAAA=</data>
							 <key>Replace</key>
							 <data>Fg7vn4/9AmM7N8/rQADBJAI=</data>
					 </dict>
					 <key>1</key>
					 <dict>
							 <key>Find</key>
							 <data>KAAZACgYCAgF</data>
							 <key>Replace</key>
							 <data>gAc4BPBCEAcF</data>
					 </dict>
					 <key>2</key>
					 <dict>
							 <key>Find</key>
							 <data>gg8DAQAACAQUAAAIFw==</data>
							 <key>Replace</key>
							 <data>TQEDTQEIASDAA///IA==</data>
					 </dict>
					 <key>3</key>
					 <dict>
							 <key>Find</key>
							 <data>QAa6sAQ=</data>
							 <key>Replace</key>
							 <data>gAe6OAQ=</data>
					 </dict>
			 </dict>
That added 1920x1080 in four matrices of the Video Bios. More info at ProjectOSX forums.

 

If you have an UEFI motherboard, you'll need a driver called CsmVideoDxe-64.efi.

 

Cheers!

 

PS: I forgot, the setting of the resolution is in the refit.conf file.

 

can i use this in chameleon ?

Share this post


Link to post
Share on other sites

Nope it doesn't have kext patching, you can however locate the original perl scripts that are around and use it to patch the binary directly in the kext in /s/l/e.

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 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
×