Jump to content
ErmaC

Clover General discussion

20,012 posts in this topic

Recommended Posts

11 minutes ago, Slice said:

svn up

 

That brings the version to 4537 indeed. BUT I apparently run into some conflicts.

 

   A Drivers/UsbBusDxe/UsbBusDxeExtra.uni
   A Drivers/UsbBusDxe/UsbBus.h
   A Drivers/UsbBusDxe/UsbUtility.h
   A Conf/Tpl/MSFT/config.template
   A gptsync/gptsync.inf
   A gptsync/gptsync.h
   A Certificates/Default/Signing.key
 U   .
Updated to revision 4537.
Summary of conflicts:
  Tree conflicts: 145
Tree conflict on 'BuildTools'
   > local dir unversioned, incoming dir add upon update
Select: (r) mark resolved, (p) postpone, (q) quit resolution, (h) help:

Uhm...help? :)) Or is that intended?

I'm guessing this happened because the initial source was not downloaded via svn? So..it's "unversioned" because of this?

And when I did the svn up it added whatever was different from my local source, but also, couldn't compare versions?

 

I exited the Terminal and went back. Now it says only

imac-2:Clover jimmy$ svn up
Updating '.':
At revision 4537.

 

Edited by arsradu

Share this post


Link to post
Share on other sites
Advertisement
19 minutes ago, chris1111 said:

No issue here light mode :rofl:



 

882741836_Capturedcranle2018-06-1212_03_22.png.a8e186db8621956f0d8d2b8fbc9cb20a.png

 

Oh, I see.. now I just realize that it happened to another package installer too.. a bug with DarkMode, I think.

Spoiler

What a great idea from Apple to make our eyes blind, then they'll release a new device named "iGlass" #LoL

 

Nvidia-Light-Dark.png

Share this post


Link to post
Share on other sites
Delete manually this folder and try again

Yep. Works fine with a fresh environment. Which means that most likely it is/was the fact that I “injected” the Clover sources into the environment instead of downloading them from svn that caused the issues.

 

Thank you so much for your feedback.

By the way, I’m not sure who should I be thanking for this, but building Clover using UDK2018 method is a LOT faster. It is probably also faster because it doesn’t build 32 bit versions anymore. But I don’t know, it just seems really, really fast now.

Well done!

 

Share this post


Link to post
Share on other sites

Guys, a new issue when building the package in Mojave. I'm pretty sure it's something related to the setup. I'm using Xcode 10, obviously. But...the error says Xcode version too old. Which makes no sense.

 

192-168-0-116:CloverPackage jimmy$ ./makepkg

========= Translating Resources ========
/Users/jimmy/src/UDK2018/Clover/CloverPackage/package/../../../../opt/local
XCode version too old. Not extracting locale strings from source XIB file
XCode version too old. Not extracting locale strings from source XIB file
XCode version too old. Don't extracting locale strings from source files

Building CloverUpdater application...
[XCODE]
Building CloverPrefpane preference...
** BUILD FAILED **

make: *** [CloverPrefpane] Error 65
192-168-0-116:CloverPackage jimmy$ 

Did anyone succeed to build Clover in Xcode 10 with this method?

Share this post


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

Guys, a new issue when building the package in Mojave. I'm pretty sure it's something related to the setup. I'm using Xcode 10, obviously. But...the error says Xcode version too old. Which makes no sense.

 


192-168-0-116:CloverPackage jimmy$ ./makepkg

========= Translating Resources ========
/Users/jimmy/src/UDK2018/Clover/CloverPackage/package/../../../../opt/local
XCode version too old. Not extracting locale strings from source XIB file
XCode version too old. Not extracting locale strings from source XIB file
XCode version too old. Don't extracting locale strings from source files

Building CloverUpdater application...
[XCODE]
Building CloverPrefpane preference...
** BUILD FAILED **

make: *** [CloverPrefpane] Error 65
192-168-0-116:CloverPackage jimmy$ 

Did anyone succeed to build Clover in Xcode 10 with this method?

Show, please, output

xcodebuild -version | sed -nE 's/^Xcode ([0-9]).*/\1/p'

Share this post


Link to post
Share on other sites
Just now, Slice said:

Show, please, output

xcodebuild -version | sed -nE 's/^Xcode ([0-9]).*/\1/p'

 

Seems to be 1.

192-168-0-116:~ jimmy$ xcodebuild -version | sed -nE 's/^Xcode ([0-9]).*/\1/p'
1
192-168-0-116:~ jimmy$ 

 

Share this post


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

 

Seems to be 1.


192-168-0-116:~ jimmy$ xcodebuild -version | sed -nE 's/^Xcode ([0-9]).*/\1/p'
1
192-168-0-116:~ jimmy$ 

 

I excluded Xcode version check in 4538. It was needed for Xcode 3 and 4. Now I think xcode is always >=5.

If anyone want old versions then welcome with your proposition how to do better way.

6 hours ago, arsradu said:

 

Seems to be 1.


192-168-0-116:~ jimmy$ xcodebuild -version | sed -nE 's/^Xcode ([0-9]).*/\1/p'
1
192-168-0-116:~ jimmy$ 

 

Check, please

xcodebuild -version | sed -nE 's/^Xcode ([0-9]+).*/\1/p'

Share this post


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

fdisk440 should be revised or just excluded. It is compiled to 32bit which is no more supported.

There is a better way to install mbr0 sector sizeof 440


dd if=/dev/disk0 count=1 bs=512 of=origMBR
cp origMBR newMBR
dd if=boot0 of=newMBR bs=1 count=440 conv=notrunc
dd if=newMBR of=/dev/disk0 count=1 bs=512

Someone can implement this into Clover Package? And completely exclude fdisk440.

 

EDITED.

Or /dev/rdisk0 ?

I'll do that tonight. Did you want to backup original boot sectors?

Share this post


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

I'll do that tonight. Did you want to backup original boot sectors?

I don't. See no reason to restore it.

See please all fdisk440 usage in the package.

Share this post


Link to post
Share on other sites
15 minutes ago, Slice said:

I don't. See no reason to restore it.

See please all fdisk440 usage in the package.

Ok, I think that fdisk (shipped with the OS) will works just fine activating partitions

Share this post


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

I excluded Xcode version check in 4538. It was needed for Xcode 3 and 4. Now I think xcode is always >=5.

If anyone want old versions then welcome with your proposition how to do better way.

Check, please

xcodebuild -version | sed -nE 's/^Xcode ([0-9]+).*/\1/p'

 

After updating sources, now it says "10".

192-168-0-116:Clover jimmy$ xcodebuild -version | sed -nE 's/^Xcode ([0-9]+).*/\1/p'
10
192-168-0-116:Clover jimmy$ 

Now, it says "updating 'en' strings"... But still fails in the same place:

========= Translating Resources ========
/Users/jimmy/src/UDK2018/Clover/CloverPackage/package/../../../../opt/local
Updating 'en' strings file for CloverUpdater... done
Updating 'en' strings file for Clover Preference Panel... done
Updating strings file for Clover Preference Panel... done

Building CloverUpdater application...
[XCODE]
Building CloverPrefpane preference...
** BUILD FAILED **

make: *** [CloverPrefpane] Error 65
192-168-0-116:CloverPackage jimmy$ 

 

Edited by arsradu

Share this post


Link to post
Share on other sites

@Slice

Sorry, seems like I've missed important changes few months back.

What u mean with --Automatic choose "yourtheme" or "yourtheme@2x" if monitor is 2k or larger.--?

In my case, if there're "Lightness" and "Lightness256" themes on the repo already; do I need to rename Lightness256 to Lightness@2x (is exact naming)..?

"The criteria is ScreenHight > 1100", is this new value on theme.plist or u mean "DesignHeight" and Width will follow? Thanks.

Screenshot 31.png

Edited by Badruzeus

Share this post


Link to post
Share on other sites
4 minutes ago, blackosx said:

Yeah. Slice posted a link to an example theme. I've not had time to look yet.

OK, just curious with "ScreenHeigh" and I have no bigger screen than 768 to test.

A question, can we use similar method to speed up CloverThemeManager sync process when updating just like this? Thanks.

Share this post


Link to post
Share on other sites

@Slice

 

sorry yet another issue under 10.14, while the clover package builds totally fine under 10.13.5.

 

Warning!  Building 4538 can now cause a KP under 10.14 and can make your system totally irresponsive.  

 

1289625263_Screenshot2018-06-13at09_07_13.thumb.png.920e579df01eaf5679c23d250efc99b1.png

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites
14 minutes ago, KGP-iMacPro said:

@Slice

 

sorry yet another issue under 10.14, while the clover package builds totally fine under 10.13.5.

 

Warning!  Building 4538 can now cause a KP under 10.14 and can make your system totally irresponsive.  

...

Where's the proof that your KP issue under 10.14 is caused by "Building 4538"..???

Share this post


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

 

Oh, I see.. now I just realize that it happened to another package installer too.. a bug with DarkMode, I think.

  Reveal hidden contents

What a great idea from Apple to make our eyes blind, then they'll release a new device named "iGlass" #LoL

 

Nvidia-Light-Dark.png

 

Hmm...where did you get this driver? :D

1 hour ago, KGP-iMacPro said:

@Slice

 

sorry yet another issue under 10.14, while the clover package builds totally fine under 10.13.5.

 

Warning!  Building 4538 can now cause a KP under 10.14 and can make your system totally irresponsive.  

 

1289625263_Screenshot2018-06-13at09_07_13.thumb.png.920e579df01eaf5679c23d250efc99b1.png

 

Have you tried building with UDK2018? I see you're still using edk2.

Also, no issues booting Mojave using Clover 4538. So...I'm guessing it might be something specific either to your config...or to your Clover build. It's just an idea. I could be wrong. But...as I said, doesn't happen to me.

If you want, you can give it a try.

Clover_v2.4k_r4538.pkg

Edited by arsradu

Share this post


Link to post
Share on other sites
2 hours ago, Badruzeus said:

Where's the proof that your KP issue under 10.14 is caused by "Building 4538"..???

 

I got a KP while building 4538. It was the first and only one since one year. What else you want yo be proven? You should know yourself that it is impossible to provide proof and reason for a KP once the PC is totally frozen. 

 

Anyway, you can also just ignore my advice. Fine with me. 

Share this post


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

 

Hmm...where did you get this driver? :D

 

Have you tried building with UDK2018? I see you're still using edk2.

Also, no issues booting Mojave using Clover 4538. So...I'm guessing it might be something specific either to your config...or to your Clover build. It's just an idea. I could be wrong. But...as I said, doesn't happen to me.

If you want, you can give it a try.

Clover_v2.4k_r4538.pkg

 

I did not say that I had problems in booting Mojave with 4538. I did say that I witnessed a KP and another error while building 4538 on X299 under Mojave. 

 

I guess one should be able to use the Build_Clover.Command, isn’t it? If the latter requires some update to use UDK2018 instead of edk2, I hope somebody can implement it. 

 

All my previous replies about remaining errors have been valid and kindly removed/fixed by @Slice

 

I don't think that now the remaining error is at my side.. 

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites

The only issue I had building Clover in Mojave is the one I posted above. That’s why I thought I would suggest using UDK2018 method.

 

As for build_clover.command, while an awesome script, it uses SF svn. Which...has been really bad for me recently. Very unstable. By the way, even with VPN.

I don’t know by which miracle it worked last night when downloading Clover sources. But otherwise...man, that was garbage. So...if it works fine for you, that’s great. But an unstable connection like that can create issues building anything. Since you can’t be 100% you got all the sources and nothing is corrupted.

Edited by arsradu

Share this post


Link to post
Share on other sites
23 minutes ago, KGP-iMacPro said:

 

I got a KP while building 4538. It was the first and only one since one year. What else you want yo be proven? You should know yourself that it is impossible to provide proof and reason for a KP once the PC is totally frozen. 

 

Anyway, you can also just ignore my advice. Fine with me. 

Well said, you could troubleshoot your self what caused KP with terminal command like this:

Good luck :)

 

Spoiler

cat /private/var/log/system.log | grep "whatever"

 

Screenshot 35.png

Edited by Badruzeus

Share this post


Link to post
Share on other sites
12 minutes ago, Badruzeus said:

Well said, you could troubleshoot your self what caused KP with terminal command like this:

Good luck :)

 

  Reveal hidden contents

cat /private/var/log/system.log | grep "whatever"

 

Screenshot 35.png

 

Well.. I see no reason for doing that, sorry.. I usually don't face any KP issues on my system... Thanks for your kind advise anyway... 

 

Also my previous post you originally quoted was addressed to @Slice and I guess he knows quite well that I am talking about.. 

 

The main problem is also not the one single KP I observed while compiling 4538 on X299 under Mojave, but another compiling/buiding error/issue in addition to all others I previously reported and which already have been kindly removed/fixed by others.  

 

Cheers,

 

KGP

Edited by KGP-iMacPro

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

  • Similar Content

    • 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 fusion71au
      Clover r5050 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_r5050 for VMware.zip". Mount Clover-v2.5k-5050-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
    • By MaLd0n
      ---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
       
      ---DSDT patch requests is here---
       
      https://olarila.com/forum/viewtopic.php?f=19&t=1131
       
      ---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 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
       
       
       
       
       
       
       
       
       
       
       
       
       
×