Jump to content
ErmaC

Clover General discussion

20,008 posts in this topic

Recommended Posts

I have some questions about DSDT (*.aml) loading in Clover. I've posted in a few places and haven't gotten definitive answers.
 
Say I have 2 (or more) .aml files within EFI/CLOVER/ACPI/patched -- say dsdt1.aml and dsdt2.aml.
I want to compare how they affect my machine; as well as NOT loading either of them.
So in config.plist I tried 'DSDT Name' set to null, i.e., there is no key/value.
But checking bdmesg it shows:

Inserting dsdt1.aml from EFI\CLOVER\ACPI\patched ... Success
Inserting dsdt2.aml from EFI\CLOVER\ACPI\patched ... Success

My questions:

  • Does "Inserting" mean they were both loaded? Or just recognized?
  • Do they have to be called DSDT or can they be called anything?
  • In Clover options /Acpi Patching, if I want to specify which to load, do I include .aml, or just dsdt1?
  • Can I specify a folder in Clover options or does the AML have to reside within /ACPI/patched?
  • If I want to NOT load ANY aml ... Do I need to actually remove them from ACPI/patched?
  • Can I create just an empty file called none.aml and use that in Clover options in order to not load any AML?
  • Is there any definitive way in MacOS to check which (if any) AML has been loaded? (I tried extracting DSDT with "MaciASL.app" but it did not match either of my AML files.)

I don't want to remove them from ACPI/patched, because, if for some reason, I can't boot MacOS, then it will be a pain trying to putt them back.
 
Thanks!

Share this post


Link to post
Share on other sites
Advertisement

I have some questions about DSDT (*.aml) loading in Clover. I've posted in a few places and haven't gotten definitive answers.

 

Say I have 2 (or more) .aml files within EFI/CLOVER/ACPI/patched -- say dsdt1.aml and dsdt2.aml.

I want to compare how they affect my machine; as well as NOT loading either of them.

So in config.plist I tried 'DSDT Name' set to null, i.e., there is no key/value.

But checking bdmesg it shows:

 

Inserting dsdt1.aml from EFI\CLOVER\ACPI\patched ... Success
Inserting dsdt2.aml from EFI\CLOVER\ACPI\patched ... Success
My questions:

  • Does "Inserting" mean they were both loaded? Or just recognized?
  • Do they have to be called DSDT or can they be called anything?
  • In Clover options /Acpi Patching, if I want to specify which to load, do I include .aml, or just dsdt1?
  • Can I specify a folder in Clover options or does the AML have to reside within /ACPI/patched?
  • If I want to NOT load ANY aml ... Do I need to actually remove them from ACPI/patched?
  • Can I create just an empty file called none.aml and use that in Clover options in order to not load any AML?
  • Is there any definitive way in MacOS to check which (if any) AML has been loaded? (I tried extracting DSDT with "MaciASL.app" but it did not match either of my AML files.)
I don't want to remove them from ACPI/patched, because, if for some reason, I can't boot MacOS, then it will be a pain trying to putt them back.

 

Thanks!

In your config.plist, set the name of an .aml file that doesn't exist, like dsdt456.aml. That way clover won't use any of the .aml files in ACPI/Patched.

 

If your system doesn't boot, you can change the .aml file name on Clover GUI for one file that does exists and works.

Share this post


Link to post
Share on other sites

In your config.plist, set the name of an .aml file that doesn't exist, like dsdt456.aml. That way clover won't use any of the .aml files in ACPI/Patched.

 

If your system doesn't boot, you can change the .aml file name on Clover GUI for one file that does exists and works.

 

 

I tried that ... but it didn't work.

 

In `config.plist` I have:

 

<key>ACPI</key>...
  <key>DSDT</key>...
   <key>Name</key>
   <string>DSDT.aml</string>

 

In ACPI/patched I have:

 

    dsdt1.aml
    dsdt2.aml

 

Clover options shows ACPI DSDT name: `DSDT.aml` -- I left it as is.

 

And yet `bdmesg` *still* shows:

 

    Inserting dsdt1.aml from EFI\CLOVER\ACPI\patched ... Success
    Inserting dsdt2.aml from EFI\CLOVER\ACPI\patched ... Success

Share this post


Link to post
Share on other sites

I have some questions about DSDT (*.aml) loading in Clover. I've posted in a few places and haven't gotten definitive answers.

 

Say I have 2 (or more) .aml files within EFI/CLOVER/ACPI/patched -- say dsdt1.aml and dsdt2.aml.

I want to compare how they affect my machine; as well as NOT loading either of them.

So in config.plist I tried 'DSDT Name' set to null, i.e., there is no key/value.

But checking bdmesg it shows:

Inserting dsdt1.aml from EFI\CLOVER\ACPI\patched ... Success
Inserting dsdt2.aml from EFI\CLOVER\ACPI\patched ... Success

My questions:

  • Does "Inserting" mean they were both loaded? Or just recognized?
  • Do they have to be called DSDT or can they be called anything?
  • In Clover options /Acpi Patching, if I want to specify which to load, do I include .aml, or just dsdt1?
  • Can I specify a folder in Clover options or does the AML have to reside within /ACPI/patched?
  • If I want to NOT load ANY aml ... Do I need to actually remove them from ACPI/patched?
  • Can I create just an empty file called none.aml and use that in Clover options in order to not load any AML?
  • Is there any definitive way in MacOS to check which (if any) AML has been loaded? (I tried extracting DSDT with "MaciASL.app" but it did not match either of my AML files.)

I don't want to remove them from ACPI/patched, because, if for some reason, I can't boot MacOS, then it will be a pain trying to putt them back.

 

Thanks!

It looks like you have case-sensitive file system.

Clover intended to exclude all files with name DSDT* but it did not.

It is Clover bug and will be fixes asap.

Share this post


Link to post
Share on other sites

So I'm running the latest version of Clover, and it's working great except for one minor niggle; before Clover displays any icons, I get a bunch of what looks like debug/log text to my screen about all the different EFI entries it finds.

 

Now this would be fine if I were debugging, but booting is working just fine so I'd rather not see this, but I can't find any option anywhere in config.plist to disable it, as far as I can see I've turned off all log and all debug options.

 

To clarify; the entries I'm getting are specifically about EFI volumes that Clover finds, and occurs before I select a volume to boot up from, so this isn't anything to do with the -verbose flag for actual macOS booting (though I also have this disabled).

 

Is there some other option somewhere that I can disable?

Share this post


Link to post
Share on other sites

So I'm running the latest version of Clover, and it's working great except for one minor niggle; before Clover displays any icons, I get a bunch of what looks like debug/log text to my screen about all the different EFI entries it finds.

 

Now this would be fine if I were debugging, but booting is working just fine so I'd rather not see this, but I can't find any option anywhere in config.plist to disable it, as far as I can see I've turned off all log and all debug options.

 

To clarify; the entries I'm getting are specifically about EFI volumes that Clover finds, and occurs before I select a volume to boot up from, so this isn't anything to do with the -verbose flag for actual macOS booting (though I also have this disabled).

 

Is there some other option somewhere that I can disable?

Follow this  http://www.insanelymac.com/forum/topic/327584-apfsefi-without-verbose-boot/?hl=%20apfsefi

Share this post


Link to post
Share on other sites

Clover rev 4380

2 config.plist named config.plist and config-1.plist with inside different ACPI/DSDT/patches

I choose config-1.plist then check in ACPI/DSDT custom patches and I see patches of previous config.plist

in this condition on clover boot men I press return to go to the main boot menu then again I select ACPI/DSDT/custom patches and I see correct ones patches

Share this post


Link to post
Share on other sites

Clover rev 4380

2 config.plist named config.plist and config-1.plist with inside different ACPI/DSDT/patches

I choose config-1.plist then check in ACPI/DSDT custom patches and I see patches of previous config.plist

in this condition on clover boot men I press return to go to the main boot menu then again I select ACPI/DSDT/custom patches and I see correct ones patches

config-1.plist will be taken into account after return to main menu.

Share this post


Link to post
Share on other sites

I have some questions about DSDT (*.aml) loading in Clover. I've posted in a few places and haven't gotten definitive answers.

 

Say I have 2 (or more) .aml files within EFI/CLOVER/ACPI/patched -- say dsdt1.aml and dsdt2.aml.

I want to compare how they affect my machine; as well as NOT loading either of them.

So in config.plist I tried 'DSDT Name' set to null, i.e., there is no key/value.

But checking bdmesg it shows:

Inserting dsdt1.aml from EFI\CLOVER\ACPI\patched ... Success
Inserting dsdt2.aml from EFI\CLOVER\ACPI\patched ... Success

My questions:

  • Does "Inserting" mean they were both loaded? Or just recognized?
  • Do they have to be called DSDT or can they be called anything?
  • In Clover options /Acpi Patching, if I want to specify which to load, do I include .aml, or just dsdt1?
  • Can I specify a folder in Clover options or does the AML have to reside within /ACPI/patched?
  • If I want to NOT load ANY aml ... Do I need to actually remove them from ACPI/patched?
  • Can I create just an empty file called none.aml and use that in Clover options in order to not load any AML?
  • Is there any definitive way in MacOS to check which (if any) AML has been loaded? (I tried extracting DSDT with "MaciASL.app" but it did not match either of my AML files.)

I don't want to remove them from ACPI/patched, because, if for some reason, I can't boot MacOS, then it will be a pain trying to putt them back.

 

Thanks!

The bug is fixed in 4391.

Anyway it is better to name files DSDT*.aml

Share this post


Link to post
Share on other sites

Guys, I just want to clarify one thing, since it's a bit confusing to me. Starting with the addition of OsxAptioFix3Drv (which supports NVRAM), do we still need EmuVariableUefi for non-hardware NVRAM motherboards, such as series 100, in order to have the Nvidia Driver working?

 

They seem to work very well in parallel. But I was just wondering if this particular piece of software (the Nvidia driver) will still work without the EmuVariable driver (considering I'm using OsxAptioFix3 instead). Has anyone tried that so far?

Share this post


Link to post
Share on other sites

Guys, I just want to clarify one thing, since it's a bit confusing to me. Starting with the addition of OsxAptioFix3Drv (which supports NVRAM), do we still need EmuVariableUefi for non-hardware NVRAM motherboards, such as series 100, in order to have the Nvidia Driver working?

 

They seem to work very well in parallel. But I was just wondering if this particular piece of software (the Nvidia driver) will still work without the EmuVariable driver (considering I'm using OsxAptioFix3 instead). Has anyone tried that so far?

Yes we no longer need EmuVariableUefi for Nvidia.

 

Sent from my SM-G930F using Tapatalk

Since rev980 Clover has enough functions to make iMessage working.

You have to set correct UUID, sn, ROM, MLB and register Apple services official way agree with all Apple's claim.

No matter what I try I cannot get iMessage to work. Do you have any guides to get it working?

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

Guys, I just want to clarify one thing, since it's a bit confusing to me. Starting with the addition of OsxAptioFix3Drv (which supports NVRAM), do we still need EmuVariableUefi for non-hardware NVRAM motherboards, such as series 100, in order to have the Nvidia Driver working?

 

They seem to work very well in parallel. But I was just wondering if this particular piece of software (the Nvidia driver) will still work without the EmuVariable driver (considering I'm using OsxAptioFix3 instead). Has anyone tried that so far?

Series 100 and up is exactly what AF3 fixes...

Share this post


Link to post
Share on other sites

Yes we no longer need EmuVariableUefi for Nvidia.

 

Sent from my SM-G930F using Tapatalk

No matter what I try I cannot get iMessage to work. Do you have any guides to get it working?

 

Sent from my SM-G930F using Tapatalk

 

Series 100 and up is exactly what AF3 fixes...

 

Got it. Thank you both very much for your feedback! :) So far so good.

 

SavageAUS, I personally haven't gotten any issues with iMessage... So if the serials are right, so you can successfully authenticate on Apple's servers, I think...it should work...?

 

Do you get the generic message to contact Apple when you try to login? Or something else?

Share this post


Link to post
Share on other sites

Yes we no longer need EmuVariableUefi for Nvidia.

 

Sent from my SM-G930F using Tapatalk

No matter what I try I cannot get iMessage to work. Do you have any guides to get it working?

 

Sent from my SM-G930F using Tapatalk

You need to dump some real MBL and MAC

 

Sent from my Nexus 4 using Tapatalk

Share this post


Link to post
Share on other sites

Got it. Thank you both very much for your feedback! :) So far so good.

 

SavageAUS, I personally haven't gotten any issues with iMessage... So if the serials are right, so you can successfully authenticate on Apple's servers, I think...it should work...?

 

Do you get the generic message to contact Apple when you try to login? Or something else?

Something like "an error occurred during authentication please try again".

 

I have working nvram.

My serial number is invalid according to apple.

My serial number matches to the right mac on everymac.

Ethernet is builtin and en0.

Have followed numerous guides.

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

Something like "an error occurred during authentication please try again".

 

Sent from my SM-G930F using Tapatalk

Hmm... Did it work before? What changed in the meantime?

 

Also, are you using automatic time zone set to ON? If not, maybe you can switch it on... Some people say it could be a server issue here, caused by the wrong date and time. I could be very wrong though. I'm still trying to find a probable cause here. But...you can try. Maybe it helps.

Share this post


Link to post
Share on other sites

Hmm... Did it work before? What changed in the meantime?

 

Also, are you using automatic time zone set to ON? If not, maybe you can switch it on... Some people say it could be a server issue here, caused by the wrong date and time. I could be very wrong though. I'm still trying to find a probable cause here. But...you can try. Maybe it helps.

No I've never ever had working iMessage.

I'll check time zone settings.

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

No I've never ever had working iMessage.

I'll check time zone settings.

 

 

share your config plist to take a look. I have several config.plist with iMessage and Facetime ok.

Share this post


Link to post
Share on other sites

No I've never ever had working iMessage.

I'll check time zone settings.

 

Sent from my SM-G930F using Tapatalk

I suggest you remove your device from iCloud, create a new config.plist and then reconfigure your new config as same as the old one, after choosing the SMBIOS generate several serial numbers then in system parameters create a new custom UUID and then go to Rt Variables and generate a new ROM then save the config and reboot.

 

Just copy the existing EFI folder on a USB disk just in case if anything goes wrong then try with the new settings and sign in iCloud and iMessage.

Share this post


Link to post
Share on other sites

I suggest you remove your device from iCloud, create a new config.plist and then reconfigure your new config as same as the old one, after choosing the SMBIOS generate several serial numbers then in system parameters create a new custom UUID and then go to Rt Variables and generate a new ROM then save the config and reboot.

 

Just copy the existing EFI folder on a USB disk just in case if anything goes wrong then try with the new settings and sign in iCloud and iMessage.

Yeah I've tried that and didn't work unfortunately. Could it be because I don't have an iPhone? And have never setup iMessage on a real mac?

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

Yeah I've tried that and didn't work unfortunately. Could it be because I don't have an iPhone? And have never setup iMessage on a real mac?

 

Sent from my SM-G930F using Tapatalk

That would be interesting, I would imagine you could still use Messages without ever owning a phone but would only be able to send messages to Apple ID members only. Not sure if it would even be possible to activate Messages without activating the service on a iPhone first. 

Share this post


Link to post
Share on other sites

That would be interesting, I would imagine you could still use Messages without ever owning a phone but would only be able to send messages to Apple ID members only. Not sure if it would even be possible to activate Messages without activating the service on a iPhone first.

I don't suppose anyone has a spare iMessage account that works that I could test? You can change the password before allowing me to use it and change it again after.

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

Yeah I've tried that and didn't work unfortunately. Could it be because I don't have an iPhone? And have never setup iMessage on a real mac?

 

Sent from my SM-G930F using Tapatalk

Yeah that will explain it

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