Jump to content
ErmaC

Clover General discussion

20,013 posts in this topic

Recommended Posts

I cant see "kext inject management" bug fixes in (specific to) r4244, if so your problem could be randomly happen.. again :)

 

i just can't see "++++++++++++++++++" with failed boot on r4244. this problem happen

and i can't use kext inject management on 4243. because always failed after kext inject management.

i'm not sure other kext inject management issue. i tested basic feature.

 

my test

1. only used 10.13 folder with kexts. emtpy Others folder. injectkexts=detect. not tested usb installer. only installed HS disk.

2. in gui, select 10.13 installed HS disk with space bar, go kext inject management, enter 10.13, check kexts list, exit 10.13, enter other folder, check empty list, exit other folder, exit kext inject management. then boot without -v.

 

my test is failed boot with "++++++++++++++++++" line and apple logo on r4243

my test passed on r4244

 

sorry for my bad english

Share this post


Link to post
Share on other sites
Advertisement

In contrary, boot.efi seems preferred to read NVRAM "boot-args" instead of LoadOptions. So storing LoadOptions to loaded boot.efi get ignored because its too late?

 

Just guessing:

 

(1) You have "-v" NVRAM "boot-args".

(2) Switch off "-v" from GUI.

(3) Boot.efi will read your NVRAM "boot-args" with "-v" (still), but Clover already switching to graphic mode. So resulting in black screen.

Share this post


Link to post
Share on other sites

@Slice: how about using the XCLANG compiler profile? It's present in tools_def.txt as a profile for building edk2 for OS X/macOS. AFAIK, clang/llvm can be found in two places:

1. /usr/bin

2. /Library/Developer/CommandLineTools/usr/bin

The second path requires the Xcode command line tools to be installed with xcode-select --install, but think about it, that's more than enough for the ordinary user and no 7GB Xcode download would be needed. I wonder why nobody has seen that part of that file yet, except maybe Micky1979, that's his idea.

 

In order the XCLANG profile to be used, the following paths should be changed:

#
# Change to the location clang was built
#
#DEFINE CLANG_BIN = /usr/bin/
#DEFINE CLANG_BIN = /opt/local/libexec/llvm-3.6/bin/

DEFINE LLVM_BIN = ENV(HOME)/src/llvm-build/Release/bin/
DEFINE CLANG_BIN = ENV(HOME)/src/llvm-build/Release/bin/

to something like

# clang and llvm are in the clt directory

DEFINE LLVM_BIN = /Library/Developer/CommandLineTools/usr/bin/
DEFINE CLANG_BIN = /Library/Developer/CommandLineTools/usr/bin/

or even configurable with variable:

# clang and llvm can be anywhere, just set the env var

DEFINE LLVM_BIN = ENV(LLVM_PREFIX)/
DEFINE CLANG_BIN = ENV(CLANG_PREFIX)/

Share this post


Link to post
Share on other sites

@Philip Petev

I can't debug the problem because I always have Xcode installed.

I also didn't use llvm-clang because Xcode one is good enough producing working codes due to work of Zenith432. Tested on Xcode4.4.1, 7.3.1, 8.3.3, 9.0.

If I will change something in  tools_def.txt it will happen only if it doesn't violate my working compilation.

Share this post


Link to post
Share on other sites

@Philip Petev

I can't debug the problem because I always have Xcode installed.

I also didn't use llvm-clang because Xcode one is good enough producing working codes due to work of Zenith432. Tested on Xcode4.4.1, 7.3.1, 8.3.3, 9.0.

If I will change something in  tools_def.txt it will happen only if it doesn't violate my working compilation.

There is no difference between the llvm-clang that comes with the Command line tools and the one, included in Xcode AFAIK.

Share this post


Link to post
Share on other sites

@fabiosun,

 

Once you get to the prompt you are the root user, type this to mount the root filesystem read/write:

fsck –fy
mount –uw /

Then you can run any commands like you would in the terminal, such as removing or fixing kexts. You can't use things like diskutil though, and you are already root so don't use sudo.

Grazie!

Share this post


Link to post
Share on other sites

Just guessing:

 

(1) You have "-v" NVRAM "boot-args".

(2) Switch off "-v" from GUI.

(3) Boot.efi will read your NVRAM "boot-args" with "-v" (still), but Clover already switching to graphic mode. So resulting in black screen.

No. AFAIK Clover destroys NVRAM "boot-args" before boot.efi starts.

There is no difference between the llvm-clang that comes with the Command line tools and the one, included in Xcode AFAIK.

llvm-clang assumed is custom compiled from llvm sources.

Xcode has "clang".

Share this post


Link to post
Share on other sites
llvm-clang assumed is custom compiled from llvm sources.

Xcode has "clang".

Well, according to this, the Command line Tools are basically Xcode without the GUI. Both the compiler tools (clang etc.) and the macOS SDK are included. Xcode is actually a frontend for those tools and I really doubt someone would take the time and effort to compile two different sets of such tools.

Share this post


Link to post
Share on other sites

 

@Slice: how about using the XCLANG compiler profile? It's present in tools_def.txt as a profile for building edk2 for OS X/macOS. AFAIK, clang/llvm can be found in two places:

1. /usr/bin

2. /Library/Developer/CommandLineTools/usr/bin

The second path requires the Xcode command line tools to be installed with xcode-select --install, but think about it, that's more than enough for the ordinary user and no 7GB Xcode download would be needed. I wonder why nobody has seen that part of that file yet, except maybe Micky1979, that's his idea.


cvad as seen this since long time, Clover Builder.app tools do not need Xcodes

Edit***

Not sure ??

Share this post


Link to post
Share on other sites
# clang and llvm can be anywhere, just set the env var

DEFINE LLVM_BIN = ENV(LLVM_PREFIX)/
DEFINE CLANG_BIN = ENV(CLANG_PREFIX)/

good, just tested with success! I have clang in /usr/bin/, also I have the command line tools and exporting those paths made working binaries.

Initially I receive a "bad nasm" message, so I just exported its path as well. Mine It's a tiny partition with os x installed and no place for Xcode, thanks!

cvad as seen this since long time, Clover Builder.app tools do not need Xcodes

Edit***

Not sure ??

Can't be without making on-the-fly changes to the source so I searched for that app and as expected  needs both xcode and an old version of gcc to be compiled, very different story. I think xcode is needed only to compile obj-c stuff, but the above is really better.

Edited by vector sigma

Share this post


Link to post
Share on other sites

good, just tested with success! I have clang in /usr/bin/, also I have the command line tools and exporting those paths made working binaries.

Initially I receive a "bad nasm" message, so I just exported its path as well. Mine It's a tiny partition with os x installed and no place for Xcode, thanks!

Can't be without making on-the-fly changes to the source so I searched for that app and as expected  needs both xcode and an old version of gcc to be compiled, very different story. I think xcode is needed only to compile obj-c stuff, but the above is really better.

Be sure you have NASM 2.13.01 else codes will be broken.

For little changes in sources you just use ./ebuild.sh. Big scripts or apps needed for first time compilation.

No. AFAIK Clover destroys NVRAM "boot-args" before boot.efi starts.

 

Oops!

This line is commented out

//    DeleteNvramVariable(L"boot-args", &gEfiAppleBootGuid);

This is a big question.

Share this post


Link to post
Share on other sites

Question:

I use older 4222 and see  (using -v) that always uses an boot arg slide=0 is used. But all working.

That slide=0 is not in set as boot arg in config.plist. (And is not  listet in nvram after boot)

Where does this boot arg slide=0 come from? Does Clover add this for boottime and then delete it from nvram?

Share this post


Link to post
Share on other sites

Question:

I use older 4222 and see  (using -v) that always uses an boot arg slide=0 is used. But all working.

That slide=0 is not in set as boot arg in config.plist. (And is not  listet in nvram after boot)

Where does this boot arg slide=0 come from? Does Clover add this for boottime and then delete it from nvram?

Clover calculates the obligatoriness of this arg and added it. But I am not sure as arg or also in NVRAM.

Share this post


Link to post
Share on other sites

@slice so now clover enables it also if it is not selected by user?

 

I just wondered, I thought it was obsolete  :angel:


also this automatic mandatory injection is possible to override for some parts?

 

I mean automatic choice of a fakecpuid or some kernel patches in case of unsupported CPU?

Clover calculates the obligatoriness of this arg and added it. But I am not sure as arg or also in NVRAM.

Share this post


Link to post
Share on other sites

I just wondered, I thought it was obsolete  :angel:

Since Clover do it automatically.

 

@slice so now clover enables it also if it is not selected by user?

 

also this automatic mandatory injection is possible to override for some parts?

 

I mean automatic choice of a fakecpuid or some kernel patches in case of unsupported CPU?

some kernel patches yes.

fakecpuid no.

Share this post


Link to post
Share on other sites

Thank you for clarification

 

so my cpu needs of 0x40674 fakecpuid

clover detects it and choose right kernel patches after or if this fakecpuid is detected?

 

So it is behave in similar way if ie I have a i7 6950x or a E5 - 2696 v4 (xeon)

 

I am asking because with some clover version I had after login a reboot I ever  have had not before with ie clover 4081 release or 4049...whit this I have had a set of kernel fix or only a kext fix like brumbaer 5960x patch which produce a near perfect system (in daily use no reboots @all)

It is difficult to debug because clover changes, system changes (from Sierra to high) and this behavior happens very rarely in my rig

so excluding some automatic patching or to have a old clover release working with High Sierra could help

 

 

Since Clover do it automatically.

 

some kernel patches yes.

fakecpuid no.

Share this post


Link to post
Share on other sites

Thank you for clarification

 

so my cpu needs of 0x40674 fakecpuid

clover detects it and choose right kernel patches after or if this fakecpuid is detected?

 

So it is behave in similar way if ie I have a i7 6950x or a E5 - 2696 v4 (xeon)

 

I am asking because with some clover version I had after login a reboot I ever have had not before with ie clover 4081 release or 4049...whit this I have had a set of kernel fix or only a kext fix like brumbaer 5960x patch which produce a near perfect system (in daily use no reboots @all)

It is difficult to debug because clover changes, system changes (from Sierra to high) and this behavior happens very rarely in my rig

so excluding some automatic patching or to have a old clover release working with High Sierra could help

I would second that - we need a way to disable automatic patching for Broadwell-E, because it is not perfect. If I had the time I would propose fixes for inclusion in the code but right now I can't so am being forced to stick to older versions or build my own suitably modified which is not ideal. It seems there are multiple users who have same need.

 

 

Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites

I would second that - we need a way to disable automatic patching for Broadwell-E, because it is not perfect. If I had the time I would propose fixes for inclusion in the code but right now I can't so am being forced to stick to older versions or build my own suitably modified which is not ideal. It seems there are multiple users who have same need.

 

 

Sent from my iPhone using Tapatalk

		<key>KernelPm</key>
		<false/>

Will it help you?

 

@Sherlocks

Is the any Broadwell patch that can't be switched off from config?

Share this post


Link to post
Share on other sites

 

<key>KernelPm</key>		<false/>
Will it help you?

 

@Sherlocks

Is the any Broadwell patch that can't be switched off from config?

Yes. I mentioned this problem before when auto patch start r4134 over build.

 

Now, we have no choice to disable autopatch. Also user can't debug system problem correctly.

Broadwell and other xcpm patch "not perfect". Consider various facts(bios setting, msr on each motherboard) for stable system. This is not cover all system. Users check each patch for their system. I mentioned this status long time ago to apianti and syscl. But not accept it.

 

At least, need oppertunity to use fakecpuid feature and kernel patch on pure kernel for unsupport cpu's user. But now clover doesnt have.

 

So now fabiosun,alfaSZ reported oppertunity that i mentioned above.

 

My opinion, at least, autopatch disable option.

 

Thanks

 

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

@Sherlocks Grazie! :-)

 

Could it be possible to use a your commits (I think 4081) with high Sierra?

For simple user as I am often it is difficult to explain problem to help coder in they efforts..but ie in this thread:

http://www.insanelymac.com/forum/topic/316516-macos-sierrahigh-sierra-on-broadwell-eep-not-a-guide-but-maybe-a-working-in-progress/page-1

with previous clover without auto patch functionality I can try all that solution..which were fully working for different people

with auto patch simple user do not know which patches are on or less..

The only problem was to find exact new kernel location if OSX kernel changed.

 

Thank you

Share this post


Link to post
Share on other sites

@Sherlocks Grazie! :-)

 

Could it be possible to use a your commits (I think 4081) with high Sierra?

For simple user as I am often it is difficult to explain problem to help coder in they efforts..but ie in this thread:

http://www.insanelymac.com/forum/topic/316516-macos-sierrahigh-sierra-on-broadwell-eep-not-a-guide-but-maybe-a-working-in-progress/page-1

with previous clover without auto patch functionality I can try all that solution..which were fully working for different people

with auto patch simple user do not know which patches are on or less..

The only problem was to find exact new kernel location if OSX kernel changed.

 

Thank you

i prefer to use manual patch for kernel. Now, sorry i can't. Already suggested it before. But not accepted autopatch disable option. I don't have permission above. Reason that i mentioned. Maybe Slice can.

 

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

i prefer to use manual patch for kernel. Now, sorry i can't. Already suggested it before. But not accepted autopatch disable option. I don't have permission above. Reason that i mentioned. Maybe Slice can.

 

나의 LG-F800S 의 Tapatalk에서 보냄

 

Maybe you missed an old post where apianti said to a my request to ask @sys and@Sherlocks if I find I repost it

in my case was perfect 4081 release with previous OSX but it seems to have problem with High Sierra.I will try again

thank you again 

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 MaLd0n
      ---TUTORIAL---

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

      https://www.youtube.com/watch?v=k9wmIfGLe3A
       
      ---HARDWARE---
       
      --MOBO

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

      --PROCESSOR

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

      --COOLER

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

      --MEMORY

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

      --GPU

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

      --SSD

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

      --POWER SUPPLY

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

      --WIRELESS

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

      --CASE

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

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




















      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Thanks to KGP for SSDT Thunderbolt
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
      We're all here to have fun and learn from each other!
    • By fusion71au
      Clover r5051 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r5051 for VMware.zip". Mount Clover-v2.5k-5051-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 shinho73
      Hello everyone. I managed to install AMD Sierra V5(10.12.6) on my old AMD A8 7600 PC(Mother Board-A58M-E, GPU- Palit Geforce GT730 DDR3). Everything is working except the GPU. The GT730 DDR3 GF108 is natively supported on Sierra, but for some reason, it is not working. On Clover Config, "Inject Nvidia" is selected, no Nvidia Web, and nv_disable=1. On "About This Mac" it just says " NVIDIA Chip Model 3 MB".
      I have attached config.plist. Can someone look at it please? Any help will be greatly appreciated. Thank you. 





      config.plist
    • By kylon
      Cloud Clover Editor is an open source application that allows you to manage various Hackintosh Bootloaders configs everywhere.

      Open Cloud Clover Editor
       
      Cloud Clover Editor Wiki
      Cloud Clover Editor Sources
       
       
      Features
      Supports Clover EFI, Ozmosis, Chameleon, OpenCore GUI and Text Editor Mode CCE Bank Mobile friendly  
      Officially supported browsers
      Chrome 42+ Microsoft Edge 14+ Firefox 39+ Safari 10+ Opera 29+ Opera Mobile 12+ Chrome for Android 75+ Firefox for Android 67+  
       
      Credits
      mackie100 - took some ideas from his app Clover EFI dev team Eric Slivka - new serial number Virtual1 - new serial number cecekpawon - PHP 5.3.3 patch, , help with the ACPI Loader Mode flag and more Micky1979 - Clover flying editor  (Discontinued) crusher. - Help with the ACPI Loader Mode flag Download-Fritz - Help with the ACPI Loader Mode flag Pavo - Ozmosis fields and values stehor - Ozmosis fields and values Sherlocks - General help and support gujiangjiang - General help and support  
      Please let me know if i forgot you!
    • By gengik84
      Ciro82==>>Thanks
      Uno dei tre Requisiti:
      Hack funzionante Mac vero Macchina virtuale Impostazioni Bios per il boot:
      Cercate una voce  del tipo “Sata Mode”e settatela  in AHCI
      Secure Boot: disabilitare o altri sistemi operativi
      CSM: UEFI o LEGACY, oppure a secondo del tipo di installazione
      VT-x / VT-d disable
      *Nota: Secure boot e csm valido solo per bios UEFI
      Materiale Occorrente 
      "OS X (Versione App.Store)”
      USB 8GB  *nota: nel caso di usb superiori dovrà essere partizionata, in modo da avere una partizione su cui "lavoreremo,di questa dimensione
      ShowAllfiles 
      kext Wizard 
      Bootloader Clover_2.3k_r xxx:                   http: //sourceforge.n.../cloverefiboot/
      Clover Configurator:                                    http: //mackie100proj...a.org/download/
      FakeSmc.kext:                                            https://github.com/kozlek/HWSensors/releases
      In allegato,a fondo pagina troverete un "pacchetto" contenente : ShowAllfiles, Kext Wizard, FakeSmc.kext: 
      App alternative:
      ESP Mounter Pro: per montare la partizione EFI
      Vi illustrerò tre metodi per creare la usb, ma sono ben distinti… quindi usatene soltanto uno
      Metodo 1: “Install Mac_OS_X.command” Metodo 2: “Create Install Media di Apple” Metodo 3:  Metodo Manuale Alla fine delle preparazione dell’installer, tutti i metodi necessitano l’installazione del Bootloader Clover sulla a vostra USB.
      “CONDIZIONI OBBLIGATORIE”
      PUNTO 1: che la vostra usb sia stata preventivamente nominata USB (caratteri maiuscoli) Tabella di partizione GUID e la formattazione in  Mac esteso Journaled.
      PUNTO 2: che l’installer di OSX si trovi in Applicazioni
      Utility Disco 
      Selezionate la pendrive, andate su “partizione”, selezionate “1 partizione”, impostate Mac OS esteso journaled e date il nome USB, poi in basso cliccate su opzioni e scegliete Tabella partizione (GUID), poi “applica”.
      Immagine 
      Riporto nuovamente l’operazione sopra citata adoperando dal nuovo Utility Disco introdotto su El Capitan.
      Rimane ovviamente invariato nome della usb in ==>> USB (maiuscolo), la formattazione in Mac esteso Journaled e sia la mappa partizione in GUID
      Da utility disco selezionate la usb, cliccate su inizializza.
      dal menù a tendina scegliete la relative impostazioni
      Immagine  
      Procedura effettua da High Sierra è la stessa della precedente, l'unica attenzione e operazione da aggiungere in primis  è cliccare nel menù a tendina in alto sulla sinistra di utility disco e selezionare "mostra tutti i dispositivi"
      Immagine 
       
      =====================
        METODO 1: "Install_Mac_OS_X.Command" Lo script che trovate allegato in fondo alla guida permette la creazione dell’installer in maniera automatica
      Include la possibilità di scelta di tre versioni di osx
      Yosemite El Capitan Sierra Il risultato finale è come quello del metodo "manuale" descritto nella guida, per cui l'installazione avverrà in un solo passaggio, non in due come con il metodo createinstallmedia. 
      Offre inoltre la possibilità di inserire un kernel patchato, utile, per esempio, per chi usa AMD.
      Rimane invariato il nome dato alla usb in USB, mappa partizione e tipo di formattazione
      Se la vostra usb non sarà rinominata nel modo corretto, verrete avvisati dal terminale, quindi non dovrete far altro che apportare la relativa modifica e rilanciare nuovamente lo script
      Esempio
      ===========================
      Metodo 2 
      L'intento è quello di usare la procedura fornitaci direttamente da Apple, "createinstallmedia", introdotta  con Mavericks. 
      Tale metodo prevede l’uso del terminale che via via se ne sta perdendo il “valore e l’uso”
      Inizialmente per i neofiti potrà sembrare problematico ma alla fine non è così.
      Durante il post installazione alcune operazioni ne richiedono l’ uso.
      Perciò mi sono chiesto perchè, qualora uno volesse, non far conoscere da subito un po’ questo “strumento”???
      Per favorirvi vi ho allegato i comandi già  “pronti”, i quali li potrete copiare ed incollare sul terminale.
      A questo punto aprite il terminale, copiate ed incollate il comando sottostante e premete invio, digitate la vostra password e premete nuovamente invio.
      Comando per creare USB con Yosemite:
      sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --nointeraction  
      Comando per creare USB con El Capitan
      sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app --nointeraction Comando per creare USB con Sierra 
      sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ Sierra.app/ --nointeraction Per creare USB con Hight Sierra o Mojave usate --> C_I_M (aggiornato per 10.14)
       
      Funziona con il drag & drop sul terminale, in questo caso non vi è necessità che la usb sia nominata in un determinato modo ed essendo basato su create install media ovviamente funziona da 10.9 a 10.14.... 
      BENE…IL PROCESSO DI CREAZIONE E’ INIZIATO…
      AVREMO CIRCA 20/30 MINUTI DI TEMPO LIBERO A CUI DEDICARSI A CIO’ CHE VOGLIAMO………………………………………..  
      COLGO L’OCCASIONE PER FARVI NOTARE LA VELOCITA’ E LA SICUREZZA DI QUESTO METODO
      CONFRONTATE QUESTO CON IL TERZO METODO E NOTERETE CHE CON UN SOLO PASSAGGIO, OSSIA IL COMANDO DATO AL TERMINALE, FACCIAMO IN UNA SINGOLA OPERAZIONE TUTTI I VARI STEP DESCRITTI SULL’ ALTRO METODO.
      DETTO QUESTO, MOLTO IMPORTANTE E’ SOTTOLINEARE CHE COSI’ FACENDO EVITEREMO ERRORI  DI DISTRAZIONE RIGUARDO AI PASSAGGI O FRAINTENDIMENTI.
      Immagine 
      Potete adesso passare ad installare il bootloader Clover sulla vostra usb.
      *NOTA*:
      Avendo usato questo metodo l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      =========================
      METODO "MANUALE"....  (lascio per futura memoria-Compatibile fino a 10.12)
      ==========================
      Bootloader
      **Nota:** Installazione in UEFI  dipenderà dalla scheda madre in vostro possesso, quindi se non supporta tale opzione , il bootloader dovrà essere installato in  modalità Legacy.
       Vi invito, qualora non sapeste questa informazione, a recarvi nel sito ufficiale del produttore e controllare le informazioni a riguardo
      Fatto questo dobbiamo installare  Clover sulla usb.
      A seconda del tipo di Bios o al tipo di installazione che vogliamo fare UEFI o Legacy avremo ovviamente configurazioni diverse in questa fase.
      Lanciate il pkg.
      Immagine 

       
      Cambiate la destinazione di installazione ad USB oppure Install Mac_OS_X (a secondo del tipo di creazione eseguita)
      Successivamente clicchiamo su "Ad Hoc"
      Per Installazione UEFI
      Mettete i flag   : Installazione solo per avvio UEFI
                               : installare Clover nella ESP
                               : Driver64UEFI  AptioMemory --> (consigliato) ->  Link download
       Può essere solo aggiunto manualmente scaricando dal link sopra e collocandolo nella rispettiva cartella
       NOTA: in questo caso non selezionare nessun OsxAptioFixDRV durante l'installazione di clover oppure rimuovetelo                        successivamente. 
                               : Driver64UEFI  ApfsDriverLoader --> (consigliato) --> sostituisce l'uso del driver apfs.efi
                               : Selezionate l'altri driver come da successiva immagine,
       
      *Nota: Altri driver che si possono usare  al suo posto  sono:
       informazioni 
       
      Proseguite con l’installazione.
      Immagine 
      ** Ricordate che avrete accesso a questa cartella dopo aver montato la partizione EFI**
      ===========================
      Per installazione Legacy
      Immagine 
      ===========================
      Impostazione per config.plist:
      Con clover configurator “montate” la partizione EFI della usb.
      1) Per fare questo nel menù di sinistra, cliccate su “Mount EFI”
      2) individuate la partizione relativa alla vostra usb, a questo punto montiamo la relativa partizione EFI  selezionando l’apposito pulsante “Mount Partition”
      Immagine 
      3) Successivamente cliccate su “Open Partition”.. recatevi in EFI/Clover ed aprite il config.plist
      4) Sezione ACPI: Disabilitate tutti i fix sia del menù 1 che del menù 2
      Immagine 
      5) Sezione BOOT: Sole se si sta installando Yosemite mettete il flag su kext-dev-mode=1
      Immagine 
      6) Sezione RT Variables: Se si sta installando El Capitan oppure Sierra, aggiungere i valori: BooterConfig= 0x28, CsrActiveConfig= 0x67
      Immagine 
      7) Sezione System Parameters: Su inject kext mettete YES
      Immagine 
      ===========================
      Nota: Su El Capitan, è stato introdotto SIP (System Integrity Protection)
      Info:
      ===========================
      Recatevi in EFI/Clover/kext/10.x 
      X= alla versione di osx che state installando. Per esempio se installerete Yosemite dovrete recarvi nella cartella 10.10, con El Capitan in 10.11….ecc
      Se non ci fosse tale cartella, createla e nominatela voi a “modo”.
      Copiatevi all’interno FakeSmc.kext
      *Nota se venite già da altre vostre configurazioni, oltre kext sopra citato ,potete mettere gli altri necessari per il vostro hardware
      Stessa cosa se avete DSDT e/o SSDT potete copiarli in EFI/Clover/Acpi/Patched
      Immagine 
      
      Per High Sierra:
      Scaricare il driver apfs.efi a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
       
      Per chi volesse continuare ad usare HFS vi rimando a questo post:
        Come installare High Sierra in HFS direttamente dalla usb  
      Utenti Laptop:  Nel 99% è obbligatorio disattivare la grafica discreta Nvidia/Amd per installare questo nuovo osx
                                     Quindi aggiungete --> SSDT-Disable_DGPU.aml.zip
                                     in EFI/Clover/acpi/Patched della usb
      --------------------------------------------------------------------
      Per Mojave:
      Scaricare il driver apfs.efi per 10.14 a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
      Versione di clover non antecedente a V_4015
      Volete usare HFS?
      E' possibile fare un installazione diretta su altro disco o partizione, nel caso può essere usato anche per effettuare aggiornamenti...
      nel caso guardate...
       Mojave in HFS 
       Oppure direttamente da usb  
       
      Fatto questo avrete la vostra USB bootable per installare OSX.
      ………Non scordatevi Fakesmc.kext da mettere nella relativa cartella…. senza il quale non farete mai il Boot......
      *NOTA: se usato il terminale per la creazione della usb, l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      **NOTA** Se avete processori Broadwell,Skylake o Kabylake...usate FakeSmc.kext e relativi sensors che trovate all'interno del secondo pacchetto.. (potete usarlo anche sui precedenti senza problemi, essendo una versione più aggiornata ha ulteriore supporto per le cpu più recenti)
      Update: Fakesmc e sensors versione 6.26
      Post installazione... post #2           
       Buon Hack….. 
      Aggiornamento:Install_Mac_OS_X.command.zip (compatibile da 10.10 a 10.12)
      le info le trovate a questo post
      Ringrazio @Ciro82 che mi ha aiutato nel preparare questa guida.
      Pacchetto.zip
      Pacchetto-2.zip
      Pacchetto-Fake+Sensors 6.26.1440.zip
      C_I_M.zip
       
       
       
       
       
       
       
       
       
       
       
       
       
×