Jump to content
ErmaC

Clover General discussion

20,012 posts in this topic

Recommended Posts

It works without activating on iPhone, or maybe I am just lucky) use MBL and ROM from real Mac!

 

Sent from my Nexus 4 using Tapatalk

Share this post


Link to post
Share on other sites
Advertisement

You need to dump some real MBL and MAC

 

Sent from my Nexus 4 using Tapatalk

I have own MLB and MAC, non-Apple. And I registered AppleID before I bought iPhone. All works!

I have to remind that you should have a payable account (VISA or something else).

Share this post


Link to post
Share on other sites

I have own MLB and MAC, non-Apple. And I registered AppleID before I bought iPhone. All works!

I have to remind that you should have a payable account (VISA or something else).

I do have my visa card attached to my apple id.

 

Unless a sure fire way is described I'll wait a few months when I switch from android to apple.

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

I have own MLB and MAC, non-Apple. And I registered AppleID before I bought iPhone. All works!

I have to remind that you should have a payable account (VISA or something else).

No Visa non payable account.

 

Sent from my Nexus 4 using Tapatalk

Share this post


Link to post
Share on other sites

Why my PC install Clover 4380 - 4387 - 4391 to HDD  bios UEFI - GPT boot into macOS 10.13.2 & 10.13.3 verry slow 15 minute ?

 

 

Install for UEFI booting only

Install Clover in the ESP

 

OsxAptioFix2Drv + EmuVariableUefi-64.efi

 

HELP ME ? THANK

 

 

ScreenShot2018-01-24at2.15.25AM.png

 

ScreenShot2018-01-24at2.16.33AM.png

Share this post


Link to post
Share on other sites

hello

 

maybe u don't need

 

EmuVariableUefi-64.efi

 

try without it and use 

 

OsxAptioFix3Drv.efi

 

good hackI install Cliver 4391 on HDD

 

 

I insstall Clover 4391 on HDD bios UEFI- GPT

 

- Install for UEFI booting - only

- Install Clover in the ESP

- OsxAptioFix2Drv + EmuVariableUefi-64.efi

 

ScreenShot2018-01-24at2.15.25AM.png

 

ScreenShot2018-01-24at2.16.33AM.png

 

 

I download FakeSMC unzip & copy 6 file to my Clover 4391 on HDD path EFI\Clover\Kexts\other

 

https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek/downloads/

 

ScreenShot2018-01-24at3.45.36AM.png

 

 

ScreenShot2018-01-24at3.46.46AM.png

 

 

Boot to login green verry fast 1minute

 

Thank

Share this post


Link to post
Share on other sites

I insstall Clover 4391 on HDD bios UEFI- GPT

 

- Install for UEFI booting - only

- Install Clover in the ESP

- OsxAptioFix2Drv + EmuVariableUefi-64.efi

 

 

 

 

 

 

I download FakeSMC unzip & copy 6 file to my Clover 4391 on HDD path EFI\Clover\Kexts\other

 

https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek/downloads/

 

 

 

 

 

 

 

Boot to login green verry fast 1minute

 

Thank

HWMonitor is an app, there's no need to have it on CLOVER/Kexts/Other, Lol. Put that in /Applications.

 

Like people said, use OsxAptioFix3 without Emuvariable. Make a backup USB first in case it doesn't boot.

 

You can also try with AptioMemoryFix instead of OsxAptio.

Share this post


Link to post
Share on other sites

Also, @el_charllie, if I may, I think you don't need RC scripts anymore...if you're using OsxAptioFix3Drv. Someone, please, correct me if I'm wrong, but I didn't have any issues so far without that.

 

Now, I know Clover is meant to be as customisable as possible, so people can use whatever they need, if they need it, and it's been an amazing tool for me for YEARS, but for the sake of usability, do you guys think it would be maybe better to allow users to select only drivers which are not mutually exclusive?

 

For example, if you select OsxAptioFix3Drv, automatically deselect EmuVariableUefi since you don't need it anymore? This way, it's clear for everyone that they are doing the same thing, and they're not needed (or not supposed to work) together. In this particular case, having them both won't create any issues (at least as far as I'm concerned), but there could be cases where you're not supposed to mix two drivers, because that WILL create issues. And, especially for those cases, such a feature would be nice to have.

 

I know this is like a minor "issue" (if you can call it an issue in the first place). I don't know... It's just an idea. :)

 

Also, I know that someone will probably come back and say something like "Clover is not meant for stupid people" :)). Still, I think it would be a good idea for newcomers. Clover has a pretty steep learning curve, in my opinion. And I personally found a lot of things to be confusing at the beginning (especially coming from Chameleon).

 

Point I'm trying to make is this: I know it's not for "stupid people". Still, I don't think that's a reason not to make it a bit more user friendly, if that helps to avoid confusion (and possible issues) for newcomers.

Share this post


Link to post
Share on other sites

Also, @el_charllie, if I may, I think you don't need RC scripts anymore...if you're using OsxAptioFix3Drv. Someone, please, correct me if I'm wrong, but I didn't have any issues so far without that.

 

Now, I know Clover is meant to be as customisable as possible, so people can use whatever they need, if they need it, and it's been an amazing tool for me for YEARS, but for the sake of usability, do you guys think it would be maybe better to allow users to select only drivers which are not mutually exclusive?

 

For example, if you select OsxAptioFix3Drv, automatically deselect EmuVariableUefi since you don't need it anymore? This way, it's clear for everyone that they are doing the same thing, and they're not needed together. I know this is like a minor "issue" (if you can call it an issue in the first place). I don't know... It's just an idea. :)

 

I know that someone will probably come back and say something like "Clover is not meant for stupid people" :)). Still, I think it would be a good idea for newcomers. Clover has a pretty steep learning curve, in my opinion. And I personally found a lot of things to be confusing at the beginning (especially coming from Chameleon).

 

Point I'm trying to make is this: I know it's not for "stupid people". Still, I don't think that's a reason not to make it a bit more user friendly, if that helps to avoid confusion for newcomers.

 

Well, I have the RC scripts on my laptop hack because I was booting on legacy before. Should I delete them??

 

I think they deal with EmuVariable to write on the nvram.plist when there's no native NVRAM but IDK if it's safe to delete them.

 

I have rc.boot.d , rc.shutdown.d, rc.clover.lib and other RC but IDK if they're from Clover: rc.common, rc.common˜previous and rc.netboot.

Share this post


Link to post
Share on other sites

Well, I have the RC scripts on my laptop hack because I was booting on legacy before. Should I delete them??

 

I think they deal with EmuVariable to write on the nvram.plist when there's no native NVRAM but IDK if it's safe to delete them.

 

I have rc.boot.d , rc.shutdown.d, rc.clover.lib and other RC but IDK if they're from Clover: rc.common, rc.common˜previous and rc.netboot.

 

 

Hmm, I'm not sure about legacy boot... I haven't used that in years (didn't need to). But if you're on UEFI boot now, I don't think you need them anymore. It won't harm you to keep them. And in my personal experience, I haven't gotten any issues without them. But...you can wait for someone else's opinion, if you're not sure. As I said, it won't harm you to keep them both. It's just a matter of "should you remove them, if they're not needed anymore?"

Share this post


Link to post
Share on other sites

Hmm, I'm not sure about legacy boot... I haven't used that in years (didn't need to). But if you're on UEFI boot now, I don't think you need them anymore. It won't harm you to keep them. And in my personal experience, I haven't gotten any issues without them. But...you can wait for someone else's opinion, if you're not sure. As I said, it won't harm you to keep them both. It's just a matter of "should you remove them, if they're not needed anymore?"

 

Yeah, I had them because I didn't know I could boot in UEFI and had native NVRAM (I have hardware nvram without OsxAptio3), so I think I can delete them safely but I'll wait for some confirmation.

Share this post


Link to post
Share on other sites

Yeah, I had them because I didn't know I could boot in UEFI and had native NVRAM (I have hardware nvram without OsxAptio3), so I think I can delete them safely but I'll wait for some confirmation.

 

See, this was exactly my case. At the begging, I was using Clover in Legacy mode, although I had an UEFI enabled motherboard. Simply because Chameleon was a legacy bootloader (I think it still is, if anyone is still using it) and I didn't know that I don't actually need to use Legacy mode if I have an UEFI motherboard.

 

Also, if you have hardware NVRAM (meaning a motherboard under series 100, like my Z97S from MSI, for example), you don't need the scripts, EmuVariable or OsxAptioFix3Drv (basically you can use any OsxAptioFix, not necessarily "v3"), for sure. It's already tested. 

 

You can still use OsxAptioFix3Drv, no problem. It's just that, in your particular case, the NVRAM fix won't make any difference, since you already have hardware NVRAM.

Share this post


Link to post
Share on other sites

HWMonitor is an app, there's no need to have it on CLOVER/Kexts/Other, Lol. Put that in /Applications.

 

Like people said, use OsxAptioFix3 without Emuvariable. Make a backup USB first in case it doesn't boot.

 

You can also try with AptioMemoryFix instead of OsxAptio.

You are installing this way Clover 4391 ?

 

ScreenShot2018-01-24at6.23.16AM.png

Share this post


Link to post
Share on other sites

You are installing this way Clover 4391 ?

 

ScreenShot2018-01-24at6.23.16AM.png

 

No, don't use AptioMemoryFix and OsxAptio3, use one or another. Try with AptioMemory first as recommended by Slice, then give OsxAptio3.

 

Make sure you have a CLover USB backup to boot in case it desn't work.

 

IDK if you need Partition-Dxe, I can boot fine without it. It's best to use the less drivers. But as I said, make a Clover USB backup with the current configuration you have and test you can boot from it in case something goes wrong.

Share this post


Link to post
Share on other sites

No, don't use AptioMemoryFix and OsxAptio3, use one or another. Try with AptioMemory first as recommended by Slice, then give OsxAptio3.

 

Make sure you have a CLover USB backup to boot in case it desn't work.

 

IDK if you need Partition-Dxe, I can boot fine without it. It's best to use the less drivers. But as I said, make a Clover USB backup with the current configuration you have and test you can boot from it in case something goes wrong.

 

PartitionDxe is not necessary if you're not doing anything crazy with your partition maps.

 

Quoting from the driver's description: [PartitionDxe-64] is a "64bit driver to support non-usual partition maps such as: hybrid GPT/MBR or Apple Partition Map."

 

So, if you're not using any of that, you shouldn't be needing this driver either.

Share this post


Link to post
Share on other sites

I do have my visa card attached to my apple id.

 

Unless a sure fire way is described I'll wait a few months when I switch from android to apple.

 

Sent from my SM-G930F using Tapatalk

I created a new Apple ID to use on my hackintoshes, just to be safe. However, I indeed couldn't activate FaceTime and iMessage. I did not add any payment information though.

My actual Apple ID however, which I created when I got the iPhone 4s back in the days, does work with FaceTime and iMessage and back then my creditcard was linked (however, not anymore and iMessage et cetera still works, even after switching MLB and ROM).

Share this post


Link to post
Share on other sites

I created a new Apple ID to use on my hackintoshes, just to be safe. However, I indeed couldn't activate FaceTime and iMessage. I did not add any payment information though.

My actual Apple ID however, which I created when I got the iPhone 4s back in the days, does work with FaceTime and iMessage and back then my creditcard was linked (however, not anymore and iMessage et cetera still works, even after switching MLB and ROM).

Yeah I think I'll just wait for my current contract to finish then switch to apple then hopefully it will all work.

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

 

PartitionDxe is not necessary if you're not doing anything crazy with your partition maps.

 

Quoting from the driver's description: [PartitionDxe-64] is a "64bit driver to support non-usual partition maps such as: hybrid GPT/MBR or Apple Partition Map."

 

So, if you're not using any of that, you shouldn't be needing this driver either.

my problem is the card vga ASUS Geforce 210 1Gb DDR3  it not Clover problem

 

install Wed Driver Ndivia for macos 10.13.2  boot verry slow

 

I use Easykext Utility install VoodooHDA.kext for Geforce 210 boot HDD verry fast 1 minute into Login green

 

https://drive.google.com/open?id=1tzqWWQScXldll3jgU0EQv7OL9gQH0VZw

 

ScreenShot2018-01-24at6.20.55PM.png

Thank for Help

Share this post


Link to post
Share on other sites

Then why are you commenting in a Clover discussion thread ?

Because when i install old Clover 4297 - 4369 no problem

 

When I install Clover 4380 -4387 -4391 problem boot verry slow 15 minute

Share this post


Link to post
Share on other sites

Well, I have the RC scripts on my laptop hack because I was booting on legacy before. Should I delete them??

 

I think they deal with EmuVariable to write on the nvram.plist when there's no native NVRAM but IDK if it's safe to delete them.

 

I have rc.boot.d , rc.shutdown.d, rc.clover.lib and other RC but IDK if they're from Clover: rc.common, rc.common˜previous and rc.netboot.

 

 

the rc scripts have a variety of specific startup and shutdown functions such as save clover boot logs as well as nvram set up and save. if you are not using EmuVariable the rc shutdown will be a no-op in terms of writing the nvram.plist file. meaning it checks for it.

 

so bottom line you can leave or remove the pair of scripts if EmuVar is out of the picture

 

rc.boot.d/20.mount_ESP.local

rc.shutdown.d/80.save_nvram_plist.local

Share this post


Link to post
Share on other sites

the rc scripts have a variety of specific startup and shutdown functions such as save clover boot logs as well as nvram set up and save. if you are not using EmuVariable the rc shutdown will be a no-op in terms of writing the nvram.plist file. meaning it checks for it.

 

so bottom line you can leave or remove the pair of scripts if EmuVar is out of the picture

 

rc.boot.d/20.mount_ESP.local

rc.shutdown.d/80.save_nvram_plist.local

Other than the scripts you already mentioned, I also have

10.save_and_rotate_boot_log.local 
70.disable_sleep_proxy_client.local.disable

under /etc/rc.boot.d/, can I remove them safely?

Share this post


Link to post
Share on other sites

Try to do anything to narrow the problem:

- reduce a number of injected kexts

- reduce number of patches

- change AptioFix ion

- build Clover with Debug messages

and so on

if (drvPtr == 0 || infoPtr == 0 || extraPtr == 0 || drvPtr > infoPtr || drvPtr > extraPtr || infoPtr > extraPtr) {		Print(L"\nInvalid device tree for kext injection\n");    gBS->Stall(5000000);		return EFI_INVALID_PARAMETER;	}

Hello slice.

 

I have test these case.

 

1.AptioV1 Works fine.

 

2.AptioV2 works fine with slide value.

 

3.AptioV3 sometimes can’t boot and show Invalid device tree for kext injection.

 

4.AptioMemFix same with AptioV3 but more show more frequently.

 

I find AptioV3 and AptioMemFix have changed something with nvram so I think it maybe related with this?

 

PS: My laptop can use native nvram with V1V2V3 and AptioMemFix.

 

从我的 iPhone 发送,使用 Tapatalk

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
       
       
       
       
       
       
       
       
       
       
       
       
       
×