Jump to content
ErmaC

Clover General discussion

20,006 posts in this topic

Recommended Posts

Posted (edited)

Hi guys,

 

So...apparently UEFI DVDs do work on my machine. I've got an older Ubuntu 15.04 around, so I was curious if that one shows up in boot menu.

 

And it does! With no extra changes in BIOS settings. Right now, my BIOS is set to LEGACY + UEFI. That's why it shows the DVD ROM as both UEFI and Legacy.

 

IMG_0010.thumb.jpeg.3d5ea7f4f194a8f09d5ee1e0bec41742.jpeg

 

So I think it should be (at least in theory) possible to make a bootable DVD with Clover on it.

 

In Disk Utility, DVD ROM shows up as Apple Partition Map (intended...I guess...?)

1016512514_Screenshot2019-07-13at23_35_23.thumb.png.380da6af0b619284169674f652480373.png

 

And the partition itself is a FAT12.

 

5288702_Screenshot2019-07-13at23_36_51.thumb.png.cf9b2787e14ae57eac28b46f0a098db8.png

 

But I guess that can't be all. Since the installer can't be only 2.3MB in size. :)) I know linux partitions can't be mounted by default with Disk Utility. So I didn't really bother to mount it.

Edited by arsradu

Share this post


Link to post
Share on other sites
Advertisement

Hi @arsradu,

I have to inform you that BiosBlockIO will not work with DVD because legacy BIOS (as well as CSM) operate with block size 512 bytes while DVD has block size 2048 bytes. Clover SATA (boot6) is only way to make cdboot.

 

Share this post


Link to post
Share on other sites
Posted (edited)
4 minutes ago, Slice said:

Hi @arsradu,

I have to inform you that BiosBlockIO will not work with DVD because legacy BIOS (as well as CSM) operate with block size 512 bytes while DVD has block size 2048 bytes. Clover SATA (boot6) is only way to make cdboot.

 

Hi Slice! :) 

 

Thank you very much for the info.

 

But...I'm not trying to make a bootable DVD for Legacy mode. That one already works (if you manually replace boot6 with boot7 before making the iso). However, I'm trying to make a bootable DVD for UEFI mode. THAT one doesn't work yet. :) 

 

But if you already know how to make that work...please, let me know. Cause I spent almost the entire day trying to figure that out.

Edited by arsradu

Share this post


Link to post
Share on other sites
Posted (edited)
1 hour ago, arsradu said:

 

Hi Slice! :) 

 

Thank you very much for the info.

 

But...I'm not trying to make a bootable DVD for Legacy mode. That one already works (if you manually replace boot6 with boot7 before making the iso). However, I'm trying to make a bootable DVD for UEFI mode. THAT one doesn't work yet. :) 

 

But if you already know how to make that work...please, let me know. Cause I spent almost the entire day trying to figure that out.

Clover DVD STOP at Sierra 10.12 because Apple change the rule , Remember that on High Sierra it is impossible to use Base System USB Installer High Sierra only installs in Create Install Media oficially. I'm not testing the Dosdude1 Patch on a DVD but I have to stop doing DVD programs after Sierra

 

See MacOS X Install DVD Creator

Test here 10.9 10.10, 10.11, 10.12

Edited by chris1111

Share this post


Link to post
Share on other sites
Posted (edited)

I see... but I'm not trying to make an installer. Just to boot Clover in UEFI mode, off of a CD/DVD.

 

And...with the help of fusion71au's script (and ./ebuild.sh -mc, so I don't have to manually replace boot6 with boot7 from Clover3911 anymore), I managed to create an iso for booting with BiosBlockIO. So, that part is covered. You can take a look at the script, and the resulting ISO. I can boot that no problem, from CD.

Now I just want to be able to create a CD/DVD for booting Clover (just Clover) in UEFI mode. I'm not interested in making a MacOS Installer.

 

How is is possible for that Ubuntu DVD to show up as UEFI boot item in Boot Menu? Wouldn't be able to do the same for Clover?

Clover-v2.5k-5005-X64.iso

makeiso_boot7

Edited by arsradu

Share this post


Link to post
Share on other sites
3 minutes ago, arsradu said:

I see... but I'm not trying to make an installer. Just to boot Clover in UEFI mode, off of a CD/DVD.

 

And...with the help of fusion71au's script (and ebuild.sh -mc), I managed to create an iso for booting with BiosBlockIO. So, that part is covered. You can take a look at the script, and the resulting ISO. I can boot that no problem, from CD.

Now I just want to be able to create a CD/DVD for booting Clover (just Clover) in UEFI mode. I'm not interested in making a MacOS Installer.

 

How is is possible for that Ubuntu DVD to show up as UEFI boot item in Boot Menu? Wouldn't be able to do the same for Clover?

Clover-v2.5k-5005-X64.iso

makeiso_boot7

The problem is DVD use cdboot

cdboot boot from Legacy clover not EFI partition

I don't know if that is possible ?????????

Share this post


Link to post
Share on other sites
Posted (edited)

I know what you're saying. I'm definitely not an expert. But I did test that iso. And it does work. :) How...? Ask someone with more experience. :))) I can only tell you that it works. If that's not Legacy (since, in theory, I shouldn't be able to boot like that), then it's definitely not UEFI either (cause it doesn't show up as UEFI: in Boot Menu).

 

This is from Clover, booting from CD.

 

IMG_0013.thumb.jpg.a292c66d305e07602e46706f6e40aaf9.jpg

 

Edited by arsradu

Share this post


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

I know what you're saying. I'm definitely not an expert. But I did test that iso. And it does work. :) How...? Ask someone with more experience. :))) I can only tell you that it works. If that's not Legacy (since, in theory, I shouldn't be able to boot like that), then it's definitely not UEFI either.

 

This is from Clover, booting from CD.

 

 

 

cdboot in /usr/standalone/i386 use EFI on the root DVD or CD not in the EFI Partition

908835083_Capturedcranle2019-07-1318_24_46.png.9b3419f577394993ba36425a80e4846b.png

Share this post


Link to post
Share on other sites
Posted (edited)
6 minutes ago, chris1111 said:

cdboot in /usr/standalone/i386 use EFI on the root DVD or CD not in the EFI Partition

I know that. There is no EFI partition on a CD/DVD. :)

 

Still, the questions remain:

1. how does this trick work then? Cause it does work.

2. how can I make it work in UEFI mode (like that Ubuntu DVD I mentioned above)?

Edited by arsradu

Share this post


Link to post
Share on other sites
Posted (edited)
30 minutes ago, arsradu said:

I know that. There is no EFI partition on a CD/DVD. :)

 

Still, the questions remain:

1. how does this trick work then? Cause it does work.

2. how can I make it work in UEFI mode (like that Ubuntu DVD I mentioned above)?

Ubuntu  use EFI folder on root 

I don't think You can using EFI partition with cdboot;  it use only EFI on root

Maybe its possible but I don't know how to ??

Edited by chris1111

Share this post


Link to post
Share on other sites

But, but...Chris, the iso I posted above also has an EFI folder on root... But I guess that's not used in the same way as a real UEFI boot.

 

And....if cdboot is only for Legacy booting...I'm not interested in using it for UEFI. As I said, for Legacy, somehow it works already. :))) No need to focus on that anymore.

Now I just wanna focus on booting that CD in UEFI mode (maybe similar to how Ubuntu is doing it with that DVD).

 

I also don't know how... But...it seems to be possible...somehow. :))

 

Thank you so much for your feedback, Chris! Always nice talking to you. :) 

Share this post


Link to post
Share on other sites
Posted (edited)
11 hours ago, Badruzeus said:

Hi @fusion71au did you also install 10.15 in HFS+..? On my case am no longer able to proceed Clover installation since r4999. It just got stuck at osascript read-write or whatever it's name. I believe HFS+ has no r/o limitation under Catalina. And it does nothing with $ sudo mount -uw / either. Thanks.

 

No, I only installed hfs Catalina on a VMware virtual machine.  For my physical machines, 10.15 is installed on apfs formatted HDs.

 

Maybe your issue is SIP? Did you set CsrActiveConfig to 0x3E7, CSR_ALLOW_UNAPPROVED_KEXTS?  What is the output of csrutil status in Catalina?  Tried booting to Recovery HD and setting csrutil disable?

 

I also use @ASentientBot's launch daemon - copy CatalinaAutoMountWritable.plist into /Library/LaunchDaemons which auto mounts the root volume as R/W at every login (sudo mount -uw /).

 

 

 

4 hours ago, arsradu said:

Hi guys,

 

So...apparently UEFI DVDs do work on my machine. I've got an older Ubuntu 15.04 around, so I was curious if that one shows up in boot menu.

 

And it does! With no extra changes in BIOS settings. Right now, my BIOS is set to LEGACY + UEFI. That's why it shows the DVD ROM as both UEFI and Legacy.

 

 

 

So I think it should be (at least in theory) possible to make a bootable DVD with Clover on it.

 

In Disk Utility, DVD ROM shows up as Apple Partition Map (intended...I guess...?)

 

 

And the partition itself is a FAT12.

 

 

 

But I guess that can't be all. Since the installer can't be only 2.3MB in size. :)) I know linux partitions can't be mounted by default with Disk Utility. So I didn't really bother to mount it.

 

That looks interesting and promising.  If you can find out how the Ubuntu ISO is prepared and burnt to disk in linux, it should in theory be easy to do that for the Clover ISO as well.  Somehow it has a FAT partition (like a FAT32 EFI?).  Note Clover can also be compiled in Linux Mint/Ubuntu with the Build_Clover.command script.

Edit: This post and the subsequent wiki link maybe relevant on how to create a UEFI bootable ISO in ubuntu...:)

 

In addition, see if you can manually add an extra UEFI BIOS entry for the Clover CD/DVD (linking to CLOVERX64.efi) in linux with efibootmgr, or with bcfg in UEFI shell.

 

On macOS, have a look at man for hdiutil makehybrid.  Maybe -udf format will allow the Clover CD/DVD to be recognised when BIOS set to UEFI Only?

 

Finally, if you multi boot with UEFI Windows, then maybe you can manually create a UEFI-CloverCD/DVD entry with the EasyUEFI program.  Link to my guide for adding a Clover entry in UEFI Windows here and @GhostRaider's how to for MSI H81 boards (should be similar or the same BIOS settings to your system). <--- only works with GUID HDs that have EFI partitions

 

13 hours ago, vector sigma said:

Thanks anyway. I need a rw cd, or a UEFI virtual machine to do some tests..

 

13 hours ago, arsradu said:

Sure, no worries. Fusion71au seems to have made some progress with VM (if I got this right).

 

If you need any more tests on "real hardware", meaning a real CD, I can help you with that. :) 

 

 

The Clover ISO at least is able to EFI boot into macOS Catalina with VMware EFI firmware (also boot7 in your case which is Clover's EFI DUET firmware)...Note Clover's boot log

"Starting Clover Revision ... on VMware. Inc. EFI"

1664840985_CloverISOUEFIboot.thumb.png.48d6dc5c99374269caecf420559c48c7.png

 

The issue is getting the MSI UEFI Bios to recognise the Clover ISO burnt to CD/DVD as a UEFI bootable entry...

 

Edited by fusion71au
Link to linux xorriso -isohybrid-gpt-basdat option

Share this post


Link to post
Share on other sites

After 4992 there are no more error "Not found"?

Don't replace boot6 with boot7. boot7 is BiosBlockIo, it will not work with DVD.

And about UEFI DVD I think it is impossible because there is no EFI partition.

Share this post


Link to post
Share on other sites
Posted (edited)

The Not Found errors are there if:

1. I boot with SATA (boot6) instead of BiosBlockIO (boot7).

2. If I have missing drivers for boot. I'm still not sure which drivers created issues for me...that's why I uploaded above the exact ones that worked for me, but yeah, same error for both cases.

 

The only difference is that:

1. For case Nr 1, after the Not Found error, if I press Enter, I get that x64 Exception Type 000000000000006.

2. For case Nr2, I get stuck at Not Found and nothing happens if I press Enter.

 

I don't know why I can't boot with boot6, but I can't.

 

I'll try the newest commit 5006 with boot6 to confirm the "not found" error.

 

About UEFI DVD...it's not impossible, since Ubuntu does it already. :) But....after some brainstorming with fusion71au, it seems to be doing it by creating a mini EFI with efi.img within /boot/grub folder. So yeah, there is no EFI partition on a CD/DVD, but they managed to "emulate it" in some way that it it seems to work.

 

If you wanna take a look, I attached the boot files from Ubuntu 18.04.

Ubuntu ISO boot files.zip

 

Update: Build 5006 (and later) can't boot with default boot6. Not Found error + x64 Exception (red text screen).

Edited by arsradu

Share this post


Link to post
Share on other sites
31 minutes ago, arsradu said:

I don't know why I can't boot with boot6, but I can't.

This depend by a lack of your bios, why a variant that uses the bios block io was done.

Share this post


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

This depend by a lack of your bios, why a variant that uses the bios block io was done.

 

Most likely yes. I know it's a weird issue, and with my previous Gigabyte board, I think I used to use SATA (boot6). But that was like years ago, before even knowing I can boot UEFI. So yeah, it's most likely a particularity of this motherboard.

Share this post


Link to post
Share on other sites
Posted (edited)

@vector sigma Can you please, tell me if this is normal for building clover with ebuild.sh -mc?

 

 

426948517_Screenshot2019-07-14at14_01_24.thumb.png.8c18cc661ed79ad7bc8935be8af9af02.png

254094728_Screenshot2019-07-14at14_01_34.thumb.png.843bd1b43813f69c9afdba7ffbea0bef.png

 

Also, when writing Clover (pkg variant) to an USB drive, formatted GPT, shouldn't we remove boot6/boot7 file (named just "boot") from EFI partition root directory, when the user switches from Legacy booting to UEFI only?

 

Cause that doesn't seem to happen right now.

Edited by arsradu

Share this post


Link to post
Share on other sites
10 minutes ago, arsradu said:

Also, when writing Clover (pkg variant) to an USB drive, formatted GPT, shouldn't we remove boot6/boot7 file (named just "boot") from EFI partition root directory, when the user switches from Legacy booting to UEFI only?

 

Cause that doesn't seem to happen right now.

that is done automatically, if you can see boot6 or boot7 is because you selected alt boot?

Share this post


Link to post
Share on other sites
Posted (edited)
20 minutes ago, arsradu said:

@vector sigma Can you please, tell me if this is normal for building clover with ebuild.sh -mc?

It is ok, for others looks at off folder ;)

Anyway suppose you have a fresh Clover, I guess you want boot6 as well right? so a secondary pass without -mc is needed.

Edited by vector sigma

Share this post


Link to post
Share on other sites
1 minute ago, vector sigma said:

It is ok, for others looks at off folder ;)

Anyway suppose you have a fresh Clover, I guess you want boot6 as well right? so a secondary pass without -mc is needed.

 

Yeah...I've noticed. Well, I don't really want boot6. :)) That's the problematic one. I can't boot with it.

 

And...it's built by default. So..if I want boot7 (which allows me to boot), I need to do another pass with -mc.

 

About the boot file at the root of the EFI partition, it doesn't seem to be removed when reinstalling in UEFI mode only... Meaning I get this before and after installing Clover in UEFI only mode. Does it work ok for you?

 

913296905_Screenshot2019-07-14at14_55_37.thumb.png.6d18683c99d83fc272698b4b17cd053c.png

 

Share this post


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

About the boot file at the root of the EFI partition, it doesn't seem to be removed when reinstalling in UEFI mode only... Meaning I get this before and after installing Clover in UEFI only mode. Does it work ok for you?

Sorry but no one want to remove a boot file! Can be another bootloader , i.e. not Clover. Anyway if you remove the boot file... what do you want to do with your boot sectors Lol?

Share this post


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

Sorry but no one want to remove a boot file! Can be another bootloader , i.e. not Clover. Anyway if you remove the boot file... what do you want to do with your boot sectors Lol?

For UEFI-only booting, that boot file is not necessary, for as far as I know. Is it...?

Share this post


Link to post
Share on other sites
Posted (edited)
7 minutes ago, arsradu said:

For UEFI-only booting, that boot file is not necessary, for as far as I know. Is it...?

Yes your image is ESP Installation not UEFI only!

 

EDIT ***

Or you have install previously on ESP and after you have made a UEFI install on the same EFI partition but Clover will not remove previous ESP choice

if you are select UEFI only is only change the Clover LOG and the Drivers

Edited by chris1111

Share this post


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

For UEFI-only booting, that boot file is not necessary, for as far as I know. Is it...?

No but, boot, isn't there for your will? Isn't installed by case. Once you selected a legacy installation, also your master boot record and the partition boot record of your disk are modified (boot0->boot1->boot). Removing the bootloader file didn't change mutch. As I said this is unsafe, the world didn't start nor ends with Clover. What you ask cannot be done, sorry.

Share this post


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

Yes your image is ESP Installation not UEFI only!

 

This is the setup.

 

1099865737_Screenshot2019-07-14at15_14_27.thumb.png.37c43844b47f2eaa2618030d61a61304.png

 

And you've already seen the outcome. :))

2 minutes ago, vector sigma said:

No but, boot, isn't there for your will? Isn't installed by case. Once you selected a legacy installation, also your master boot record and the partition boot record of your disk are modified (boot0->boot1->boot). Removing the bootloader file didn't change mutch. As I said this is unsafe, the world didn't start nor ends with Clover. What you ask cannot be done, sorry.

 

Sure, no problem. :) I just thought that's a bug. Since we do add that boot file for Legacy installations, I thought it makes sense to remove it for UEFI-only installations.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By MaLd0n
      ---TUTORIAL---

      https://olarila.com/forum/viewtopic.php?f=50&t=8685
       
      --Original Post--
       
      https://olarila.com/forum/viewtopic.php?f=97&t=11237
       
      --Bios/UEFI Settings--
       
      *Update bios/uefi to F7+*
      1- Go to M.I.T./Advanced Frequency Settings tab
       
      Extreme Memory Profile (X.M.P.) - Profile 1
       
      2- Go to BIOS tab
       
      CSM Support - Disabled
       
      3- Go to Peripherals/Thunderbolt(TM) Configuration tab
       
      Security Level - No Security
      Thunderbolt USB Support - Enabled
      GPIO3 Force Pwr - Enabled
       
      4- Go to Chipset tab
       
      Internal Graphics - Enable
       
      ---CLOVER FOLDER---
      *Use this folder with FULL DSDT PATCHED
      EFI CLOVER Z390 DESIGNARE.zip
       
      ---OPENCORE FOLDER---
      *Use this folder with FULL DSDT PATCHED
      EFI OPENCORE Z390 DESIGNARE.zip
       
      ---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
       
       
       
       
       
       
       
       
       
       
       
       
       
    • By Alesss
      Good morning,
       
      I've the following pieces of hardware:
      - i7 6700K
      - GTX 1080
      - Asus Z170 Deluxe
      - NVME hard drives
       
      Yesterday I've successfully completed a High Sierra installation (I can't migrate to Mojave due to missing NVIDIA web drivers) but the system (even though it works correctly) seems to show a kernel panic at every shutdown/reboot.
       
      Please find the RunMe.app report attached.
       
      A couple of notes:
      - I've installed the audio kexts through the acidanthera AppleALC procedure
      - I've generated the SSDT with pikessdt script
      - Nvidia web drivers have been installed with the vulgo/webdriver.sh script that requires the WhateverGreen and the ngfxcompat=1 boot argument
      - AirportBrcmFixup.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext have been used to unlock the full potential of the integrated Wi-Fi card
      - I've tried to clean nvram and motherboard CMOS with no avail
      - I've tried to update Clover to the latest version but it always results in an unbootable system
       
      It's a pity because everything seems to work correctly (USB ports, graphics, Wifi card, Continuity and so on. I haven't tried sleep but I don't use it anyway ) but this crash is fairly annoying.
       
      Thank you very much,
      Alesss
       
      Send me Ales-iMac.zip
    • By Pentothal.Z
      Hello all,
      I have a working hackintosh....ok.....but it takes a lot to boot and according to the boot.log there are a few problems.
      One of them is a black screen that stays on for a long time.
      I would like to ask anyone in this community some help to fine tune my machine.
      Boot.log and config.plist attached


      Any help would be appreciated.
      bootlog.txt
      config.plist
×