Jump to content
ErmaC

Clover General discussion

19,245 posts in this topic

Recommended Posts

I still struggling with this question. What are these third-party kexts? @RehabMan always saying after installation moves all kexts to L/E. But some people saying keep your kexts in the Clover/Others.

 

For instance, I am using these kexts and which one are in the third-party kext?

 

AppleALC.kext

EFICheckDisabler.kext

FakeSMC.kext

IntelMausiEthernet.kext

Lilu.kext

USBInjectAll.kext

 

Should I keep these kexts inside of the Clover/Others or which kexts should I move to L/E?

Share this post


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

I still struggling with this question. What are these third-party kexts? @RehabMan always saying after installation moves all kexts to L/E. But some people saying keep your kexts in the Clover/Others.

 

For instance, I am using these kexts and which one are in the third-party kext?

 

AppleALC.kext

EFICheckDisabler.kext

FakeSMC.kext

IntelMausiEthernet.kext

Lilu.kext

USBInjectAll.kext

 

Should I keep these kexts inside of the Clover/Others or which kexts should I move to L/E?

 

Your kexts are no problem.

I recommend Bluetooth Kexts files(Rehabman BT or Dinesh BT) in L/E or S/L/E if you have problem about bt gone when wakeup from sleep.

Share this post


Link to post
Share on other sites
2018-05-04 06:06:12.840511+0800 0x140      Error       0x0                  0      0    kernel: (IOHIDFamily)  is not entitled for IOHIDLibUserClient keyboard access
2018-05-04 14:06:31.126427+0800 0x3cb      Error       0x0                  0      0    kernel: (AppleSystemPolicy) Setting mach port for daemon
2018-05-04 06:06:05.450599+0800 0x7e3      Error       0x0                  0      0    kernel: (Sandbox) Sandbox: identityservices(281) System Policy: deny(1) system-privilege 12010

 

Share this post


Link to post
Share on other sites

Hi

 

Currently, I manually update kexts in EFI/Clover/Kext/others or 10.13.  Do you know a drag & drop app to do the job?

 

Thanks

Share this post


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

Hi

 

Currently, I manually update kexts in EFI/Clover/Kext/others or 10.13.  Do you know a drag & drop app to do the job?

 

Thanks

I'm using Clover Configurator Pro.app from Mikey1979 that can easily find the boot partition and mount the right ESP (automatically or not). No kexts installation but is easy and fast.

Share this post


Link to post
Share on other sites
29 minutes ago, vector sigma said:

I'm using Clover Configurator Pro.app from Mikey1979 that can easily find the boot partition and mount the right ESP (automatically or not). No kexts installation but is easy and fast.

Thanks. I use ESP Mounter Pro from Micky1979, installed in menu bar (Insanelymac.com,  download section). But search apps to update EFI/Clover/Kexts similar to famous Kext Utility app.

Share this post


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

Thanks. I use ESP Mounter Pro from Micky1979, installed in menu bar (Insanelymac.com,  download section). But search apps to update EFI/Clover/Kexts similar to famous Kext Utility app.

Sorry for my ignorance..what is kext utility?  can I take a look?

Share this post


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

For instance, I am using these kexts and which one are in the third-party kext?

Looking at Clover's source you should (IMO) avoid kexts that needs resources on the file system (like AppleHDA) because if a kext is inside your ESP the kext's bundle is not reachable. More the "kext path" in Clover use Windows separator ("\" instead of "/" used in Unix) so that this is a limit even for injected kexts on a mounted filesystem. After that looks like there's a limit in making spaces in the memory map (I don't think you can do that as you wish).... so that /library/Extensions is really a good place. Just my opinion.

 

edit

about making space in the mem-map you should consider that this job is done by boot.efi, and Clover arrives after that (i.e. not after loading it, but after this job is done?). If not I'm wrong, otherwise correct me :)

Edited by vector sigma

Share this post


Link to post
Share on other sites
57 minutes ago, vector sigma said:

Sorry for my ignorance..what is kext utility?  can I take a look?

Kext Utility is for S\L\E and L\E installation. Here  I think KCPM Utility Pro 6 is better: Here

Share this post


Link to post
Share on other sites
On ‎5‎/‎4‎/‎2018 at 2:48 AM, tluck said:

 

IMO (and experience)

 

/Library/Extensions (vs SLE ) tends to be the better option for 3rd party (for things not macOS installed) - that is if you need to put them in the OS (vs ESP with clover injection) - as some kexts seem to only work this way.

Otherwise if you have no version dependent kexts - which is common if are booting recent OS such as Sierra and High Sierra, then EFI/CLOVER/kexts/Other keeps it simple.

 

 

if you were installing FakeSMC, NullPowerManagemet and other kexts like Intel gigabit drivers, would you be installing them in /Library/Extensions?

Share this post


Link to post
Share on other sites
On 5/3/2018 at 3:27 AM, mrjayviper said:

Hi everyone. 

 

Where the best place to put 3rd party/party kexts?

 

From within clover alone there's

 

1.EFI/CLOVER/kexts/Others

2.EFI/CLOVER/kexts/10.xx

 

When should I use SLE?

 

Thanks so much!

 

It depends, kexts in Other will be injected for all versions, kexts in 10.xx folders will be injected only for that version. You should not use \S\L\E anymore unless there is an official driver installer like Nvidia web drivers. Use \L\E, but only when you do not need the kext to boot., i.e. bluetooth or network kexts.

 

On 5/3/2018 at 4:52 AM, eugene28 said:

It depends how many versions of OSX you want to use. If only one than 1st option. If you happy with your install and everything tested and works good you can transfer kexts to SLE. Some kexts needs to be installed to SLE only, like bluetooth kexts.

 

Apple now recommends only installing user kexts in /L/E not /S/L/E ever since kext signing was enforced.

 

On 5/4/2018 at 12:28 AM, Slice said:

Installing into LE or SLE requires keeping root:wheel permissions.

Clover's folder do not. It is more simple to install and modify kexts here. But in this case you can't use other bootloaders.

 

Agreed, but you should try to inject as many as possible but as few as possible too. I know that sounds strange but the more kexts you inject the more problems with memory you are likely to have. On the other hand, you want to inject as many kexts as possible so you don't have to do any work to get upgrades, installers, etc, working without much effort after doing once. The equilibrium I find is just injecting only what I absolutely need to boot, and install everything else in the OS.

 

On 5/4/2018 at 8:10 PM, telepati said:

I still struggling with this question. What are these third-party kexts? @RehabMan always saying after installation moves all kexts to L/E. But some people saying keep your kexts in the Clover/Others.

 

For instance, I am using these kexts and which one are in the third-party kext?

 

AppleALC.kext

EFICheckDisabler.kext

FakeSMC.kext

IntelMausiEthernet.kext

Lilu.kext

USBInjectAll.kext

 

Should I keep these kexts inside of the Clover/Others or which kexts should I move to L/E?

 

This is a pretty easy answer, they are all third party kexts and  keep injecting them. Third party means made by an organization not directly affiliated with the first party, in this case Apple, second party is like Intel, NVIDIA, or AMD that create components and drivers. If you install them in /L/E or /S/L/E then whenever anything happens like an upgrade or such you probably won't get working boot since it will use a different cache not built from your system (the one that is already prebuilt for the upgrade/installer). Though, you could not inject AppleALC and IntelMausiEthernet, and install those since they are not needed for booting.

 

On 5/4/2018 at 8:14 PM, Sherlocks said:

I recommend Bluetooth Kexts files(Rehabman BT or Dinesh BT) in L/E or S/L/E if you have problem about bt gone when wakeup from sleep.

 

Yeah, this is probably a must.

 

22 hours ago, maoyeye said:

2018-05-04 06:06:12.840511+0800 0x140      Error       0x0                  0      0    kernel: (IOHIDFamily)  is not entitled for IOHIDLibUserClient keyboard access
2018-05-04 14:06:31.126427+0800 0x3cb      Error       0x0                  0      0    kernel: (AppleSystemPolicy) Setting mach port for daemon
2018-05-04 06:06:05.450599+0800 0x7e3      Error       0x0                  0      0    kernel: (Sandbox) Sandbox: identityservices(281) System Policy: deny(1) system-privilege 12010

 

 

Not enough information...?

 

17 hours ago, Matgen84 said:

Hi

 

Currently, I manually update kexts in EFI/Clover/Kext/others or 10.13.  Do you know a drag & drop app to do the job?

 

Thanks

 

What else would you do, you only need to put the kexts (which are folders containing binaries, configurations, and other resources) in the folder. Just replacing them is drag and drop, is it not?

 

12 hours ago, Matgen84 said:

Thanks. I use ESP Mounter Pro from Micky1979, installed in menu bar (Insanelymac.com,  download section). But search apps to update EFI/Clover/Kexts similar to famous Kext Utility app.

 

I'm confused, you just need to copy the files to the injection folder. The only difference is that kext utility repairs permissions for the files and with injection the file permissions do not matter.

 

12 hours ago, vector sigma said:

Looking at Clover's source you should (IMO) avoid kexts that needs resources on the file system (like AppleHDA) because if a kext is inside your ESP the kext's bundle is not reachable. More the "kext path" in Clover use Windows separator ("\" instead of "/" used in Unix) so that this is a limit even for injected kexts on a mounted filesystem. After that looks like there's a limit in making spaces in the memory map (I don't think you can do that as you wish).... so that /library/Extensions is really a good place. Just my opinion.

 

edit

about making space in the mem-map you should consider that this job is done by boot.efi, and Clover arrives after that (i.e. not after loading it, but after this job is done?). If not I'm wrong, otherwise correct me :)

 

You are not correct. Clover injects kexts through the data hub before launching boot.efi, then some other corrections happen to the device tree at exit boot services. You can't inject a kext that is already present in the kernelcache, the kernel will ignore duplicate identifiers. A lot of kexts are placed in the cache regardless of whether they are used/attached to a device because of dependencies and the category of driver, i.e. core, safe, network, etc. I can't remember the actual grouping, but it's not nearly that precise so most kexts in the OS can't be injected because they are already in the cache. You can absolutely access the ESP to inject kexts when they are actually loaded, however other resources that will eventually be loaded (like the audio driver port layouts) will not be accessible from the ESP after exit boot services. These resources will then be loaded from where the identifier of the kext exists (in /S/L/E or /L/E) because that's where the kernel expects the resources to be.

 

2 minutes ago, mrjayviper said:

 

if you were installing FakeSMC, NullPowerManagemet and other kexts like Intel gigabit drivers, would you be installing them in /Library/Extensions?

 

You should always inject FakeSMC, you should never ever ever use NullPowerManagement, and any network drivers are pretty much the ones that can absolutely be installed instead of injected since they don't need to be present to boot.

Share this post


Link to post
Share on other sites
11 minutes ago, apianti said:

 

You should always inject FakeSMC, you should never ever ever use NullPowerManagement, and any network drivers are pretty much the ones that can absolutely be installed instead of injected since they don't need to be present to boot.

 

inject = must be present before OSX starts booting? seems to me only FakeSMC needs to be used then if this is the case and all device drivers can go to /Library/Extensions?

 

In my case, I've patched the DSDT in my last hackintosh (x58 build) instead of using a several kexts.

Share this post


Link to post
Share on other sites
3 hours ago, apianti said:

 

What else would you do, you only need to put the kexts (which are folders containing binaries, configurations, and other resources) in the folder. Just replacing them is drag and drop, is it not?

 

Actually, I manually update my Source HDD, Clone HDD, Test HDD and USB Installer each time. So, if a app exist to install in EFI/Clover/Kexts, it would be more practical :)

Share this post


Link to post
Share on other sites
9 hours ago, mrjayviper said:

inject = must be present before OSX starts booting? seems to me only FakeSMC needs to be used then if this is the case and all device drivers can go to /Library/Extensions?

In my case, I've patched the DSDT in my last hackintosh (x58 build) instead of using a several kexts.

 

There's many things you can do depending. Your most useful situation is injecting everything you need to boot and not much more, that includes patched ACPI tables and kexts. Install kexts that you don't need to access the installer (or as Slice pointed out, the recovery).

 

5 hours ago, Matgen84 said:

Actually, I manually update my Source HDD, Clone HDD, Test HDD and USB Installer each time. So, if a app exist to install in EFI/Clover/Kexts, it would be more practical :)

 

Why don't you just write a simple shell script to automate the process? That would be the most practical.

 

5 hours ago, Slice said:

It will be better to keep FakeSMC and LAN kexts in Other folder because they needed for Recovery too.

 

Yes, if you need internet recovery, otherwise there is no need, but FakeSMC you should absolutely be injecting all the time, at the minimum.

Share this post


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

Why don't you just write a simple shell script to automate the process? That would be the most practical.

Thanks. Because I don't know how to do it. But I will look how to get there.

Share this post


Link to post
Share on other sites
12 hours ago, apianti said:

You are not correct. Clover injects kexts through the data hub before launching boot.efi, then some other corrections happen to the device tree at exit boot services. You can't inject a kext that is already present in the kernelcache, the kernel will ignore duplicate identifiers. A lot of kexts are placed in the cache regardless of whether they are used/attached to a device because of dependencies and the category of driver, i.e. core, safe, network, etc. I can't remember the actual grouping, but it's not nearly that precise so most kexts in the OS can't be injected because they are already in the cache. You can absolutely access the ESP to inject kexts when they are actually loaded, however other resources that will eventually be loaded (like the audio driver port layouts) will not be accessible from the ESP after exit boot services. These resources will then be loaded from where the identifier of the kext exists (in /S/L/E or /L/E) because that's where the kernel expects the resources to be.

 

Sure that I'm not totally correct, but my point was not boot.efi (in fact my was a question about that, there is a question mark in my last post since I didnt read the entire source Lol). I was referring to functions like OSKextRequestResource(). You can't access the returned path of a kext and it is not a UNIX path  ( in the event kext is injected by Clover and so already loaded).

 

TestKext.kext (1.0.0) net.vectorsigma.kext.TestKext EFI\CLOVER\kexts\10.13\TestKext.kext\Contents\Resources

How access EFI\CLOVER\kexts\10.13\TestKext.kext\Contents\Resources/firmware.bin

or

\System\Library\Extensions\TestKext.kext\Contents\Resources/firmware.bin

if forced loaded by Clover?

 

Edited by vector sigma

Share this post


Link to post
Share on other sites
9 hours ago, Slice said:

It will be better to keep FakeSMC and LAN kexts in Other folder because they needed for Recovery too.

 

So you mean to say 10.x folder dont get loaded in recovery?

 

Also, in Fusion Drive, would it be possible to have the drive's volume name recognized by clover menu automatically, just like the non-fusion drive? Currently, im renaming it in config's custom key.

Edited by ellaosx

Share this post


Link to post
Share on other sites

Hello everyone, I've been looking for a while Sierra on a PC and turn it into a hackintosh so unfortunately after a while and several attempts I decided to postpone this operation or until a CPU had arrived a some more powerful and that seems to be more compatible with a hackintosh.

the CPu came to me and was mounted correctly but the error that gave me before the replacement of the CPU is given to me even after the upgrade of the same.

I do not know how to enable the debugging of clover otherwise I would send that file ... you meanwhile from the image posted you could tell me what possibly depends on this error and how to solve it?

 

Thanks for allreloc_block.thumb.jpg.87f9c10420a6449bb3ec90c361dda40f.jpg.

Share this post


Link to post
Share on other sites
17 minutes ago, daltanious78 said:

Hello everyone, I've been looking for a while Sierra on a PC and turn it into a hackintosh so unfortunately after a while and several attempts I decided to postpone this operation or until a CPU had arrived a some more powerful and that seems to be more compatible with a hackintosh.

the CPu came to me and was mounted correctly but the error that gave me before the replacement of the CPU is given to me even after the upgrade of the same.

I do not know how to enable the debugging of clover otherwise I would send that file ... you meanwhile from the image posted you could tell me what possibly depends on this error and how to solve it?

 

Thanks for allreloc_block.thumb.jpg.87f9c10420a6449bb3ec90c361dda40f.jpg.

Try to replace OsxAptioFix2Drv.efi by  OsxAptioFixDrv.efi in CLOVER/EFI/Drivers64UEFI

If you have select both in Clover package installer, remove  OsxAptioFix2Drv.efi

OsxAptioFixDrv-64.efi.zip

Edited by chris1111

Share this post


Link to post
Share on other sites
15 hours ago, apianti said:

This is a pretty easy answer, they are all third party kexts and  keep injecting them. Third party means made by an organization not directly affiliated with the first party, in this case Apple, second party is like Intel, NVIDIA, or AMD that create components and drivers. If you install them in /L/E or /S/L/E then whenever anything happens like an upgrade or such you probably won't get working boot since it will use a different cache not built from your system (the one that is already prebuilt for the upgrade/installer). Though, you could not inject AppleALC and IntelMausiEthernet, and install those since they are not needed for booting. 

5

 

Thanks, @apianti for this good informative explanation. I know now where should I keep my kexts.

Share this post


Link to post
Share on other sites
3 hours ago, ellaosx said:

So you mean to say 10.x folder dont get loaded in recovery?

  

Also, in Fusion Drive, would it be possible to have the drive's volume name recognized by clover menu automatically, just like the non-fusion drive? Currently, im renaming it in config's custom key.

I'm using FileVault2, so it's based on Core storage like fusion drive.

 

It's set like this here:

<key>DefaultVolume</key>
		<string>HD(2,GPT,159588F2-432D-4C37-A81C-5B788C3AA48A,0x64028,0xDF30B60)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,2C597282D9D1154385E5FBD28A73FDF0)</string>

 

Share this post


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

Thanks. Because I don't know how to do it. But I will look how to get there.

 

Yeah. There is like a million resources for learning shell script on the internet,  just write a bash shell script, it's just like using the terminal but in a text file with a special starting line and the executable attribute

 

8 hours ago, vector sigma said:

Sure that I'm not totally correct, but my point was not boot.efi (in fact my was a question about that, there is a question mark in my last post since I didnt read the entire source Lol). I was referring to functions like OSKextRequestResource(). You can't access the returned path of a kext and it is not a UNIX path  ( in the event kext is injected by Clover and so already loaded).

 


TestKext.kext (1.0.0) net.vectorsigma.kext.TestKext EFI\CLOVER\kexts\10.13\TestKext.kext\Contents\Resources

How access EFI\CLOVER\kexts\10.13\TestKext.kext\Contents\Resources/firmware.bin

or

\System\Library\Extensions\TestKext.kext\Contents\Resources/firmware.bin

if forced loaded by Clover?

 

 

You should look at the code more then, lol. I answered this already, but he's a more precise answer. If you have file system Injection (FSInject.efi, which you should) then yes this resource will be resolved if it's loaded at kext initialization as this happens when the kext is loaded as a booter extension when injected. If the kext loads files later, like the audio port layouts, then no the file cannot be loaded from anything but the root filesystem. However, I think I just thought of a solution, a kext that is injected that mounts the ESP and allows other kext resources' paths to be resolved.

 

7 hours ago, ellaosx said:

So you mean to say 10.x folder dont get loaded in recovery?

 

Also, in Fusion Drive, would it be possible to have the drive's volume name recognized by clover menu automatically, just like the non-fusion drive? Currently, im renaming it in config's custom key.

 

No, they do. He was talking about using internet recovery - you need network kexts to boot in that situation, but not otherwise. Software RAID core storage volumes are not created yet, so no, the Preboot or Boot partitions are used depending on which filesystem is being used.

Share this post


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

Hello everyone, I've been looking for a while Sierra on a PC and turn it into a hackintosh so unfortunately after a while and several attempts I decided to postpone this operation or until a CPU had arrived a some more powerful and that seems to be more compatible with a hackintosh.

the CPu came to me and was mounted correctly but the error that gave me before the replacement of the CPU is given to me even after the upgrade of the same.

I do not know how to enable the debugging of clover otherwise I would send that file ... you meanwhile from the image posted you could tell me what possibly depends on this error and how to solve it?

 

Thanks for allreloc_block.thumb.jpg.87f9c10420a6449bb3ec90c361dda40f.jpg.

 

You need power management or ACPI tables patched. Also use AptioMemoryFix.efi, OsxAptioFix 1 and 2 are obsolete.

 

5 hours ago, chris1111 said:

Try to replace OsxAptioFix2Drv.efi by  OsxAptioFixDrv.efi in CLOVER/EFI/Drivers64UEFI

If you have select both in Clover package installer, remove  OsxAptioFix2Drv.efi

OsxAptioFixDrv-64.efi.zip

 

Just use AptioMemoryFix from the clover installer. Also that's the original one that works even less.

 

4 hours ago, smolderas said:

I'm using FileVault2, so it's based on Core storage like fusion drive.

 

It's set like this here:


<key>DefaultVolume</key>
		<string>HD(2,GPT,159588F2-432D-4C37-A81C-5B788C3AA48A,0x64028,0xDF30B60)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,2C597282D9D1154385E5FBD28A73FDF0)</string>

 

 

That does not give you the name of the core storage volume as that is not even created yet from the separate partitions, that looks most likely the preboot from an APFS container.

Share this post


Link to post
Share on other sites

@everyone,

 

I'm sorry, I'm still working on v3. I'm just really sidetracked with my health, the treatment I was getting didn't have long term response so I may have to go into a clinical trial that lasts about a month, though unsure when that will be, if ever. I'm having really bad tremors so its getting hard to type and staring into a screen reading is not doing anything helpful either. Hopefully, I can get v3 to a point where it at least is stable enough to start getting others testing. Again, I'm sorry. I also haven't forgotten anyone who has donated, I have a donor list to remember... lol

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 vit9696
      OpenCorePkg / Documentation / Configuration Template / Bugtracker   Discussion and installation should be done in a separate thread! This thread is for development only!
      Current status as of April 2019: Support for UEFI and DuetPkg (legacy) booting APFS and HFS+ compatibility ACPI patcher (adding, dropping, binary patching, relocation) Apple-compatible bless implementation DeviceProperties injection DataHub and SMBIOS generation Symbolic kext and kernel patcher Direct kext injection/patching/blocking within prelinkedkernel Installation/Recovery/FileVault 2 support  Configuration in config.plist with open documentation Simple boot picker for quick launch Direct boot from dmg images  
      Known defects live here.  
      For those, who are not familiar with the history, OpenCore is a project initially born in HermitCrabs Lab that unfortunately almost died before its birth. This release is both a rebirth and a complete rewrite of OpenCore, which brings a number of new ideas, and tries to preserve the smart moves incorporated by iNDi and his team. Other than that, I wish to express my deepest words of gratitude to Acidanthera and WWHC members: your participation was and remains the key for project success, and you are simply the best.
    • By fusion71au
      Clover r4961 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_r4961 for VMware.zip". Mount Clover-v2.4k-4961-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 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) 
                               : 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
       
      apfs.efi-10.14-beta1_No_Log.zip





       

×