Jump to content
ErmaC

Clover General discussion

20,008 posts in this topic

Recommended Posts

Posted (edited)
7 hours ago, fusion71au said:

 

@arsradu,

 

I noticed the makeiso script formats the iso with -eltorito-boot, to allow for legacy BIOS booting, and it also uses boot6 instead of boot7 (BiosBlockIO) which works on your system.  I'm guessing the presence of the legacy BIOS code is what makes the CD-DVD-ROM "invisible" to your firmware when it is set to boot to "UEFI only".

 

Try the following modified makeiso files (place in ~/src/edk2/Clover/CloverPackage) to generate the Clover ISO instead of the default one...

makeiso_boot7.zip ---> uses boot 7 instead of boot 6 for legacy boot

makeiso_uefi_only.zip ---> removed -eltorito-boot formatting so only UEFI booting possible

 

PS BiosBlockIO is still available in the latest Clover Pkg installer r4995.  If the boot7/BosBlockIO installed by r4995 doesn't work, then simply replace it with the boot7 "boot" file from Clover r3911 (keep the rest of the files from Clover r4995, including CLOVERX64.efi, BOOTX64.efi and the new drivers folder file structure)...

 

BiosBlockIO.png.b2405cfea903cbfcee7b388de9265433.png1770777261_Bootfile.png.a70ac1b6f2c7150185c4c4e99ea329a9.png

 

Good Luck!

Clover_v2.4k_r4995.pkg.zip

 

Hi there! :) 

 

So, let's see.

 

1. I'm guessing you're building Clover with a custom script or something, cause I couldn't get mine to add BiosBlockIO. :P Also, I see yours also has a few third party drivers and other wonders.

 

This is what I get with regular compiling.

743490089_Screenshot2019-07-13at08_37_37.thumb.png.6b7bcfb96c4a29f506f970492100c6ca.png

 

However, even with your 4995 pkg, I still can't boot. But the behaviour is a little different than before.

 

I get the cursor on the top-left corner, the "not found" thing, but no red screen anymore. It's just stuck at "not found".

 

Replacing boot from 3911 into the 4995 USB also doesn't do anything. Same exact behaviour as above (stuck at "not found").

 

2. makeiso_boot7 - same as above. Stuck at "not found".

 

I've got the exact same behavior when nothing was written on the CD and trying to boot from it (stupid mistake on my side, I erased the disk, but forgot to put something back on it). Still, it was interesting to me that I got the exact same behaviour. So, no difference with or without content, that's what I'm trying to say.

 

3. makeiso_UEFI_only - still not visible in boot menu.

 

Also, not sure that's intended (but I've got the same issue with the regular makeiso), but I've got no themes (at all) in the /themes folder on the iso...although the themes are present in CloverV2/themespkg. But they don't seem to make their way into the actual iso file.

 

I don't think my inability to boot has anything to do with the themes, since I have the same issue with your 4995 pkg, and I do have themes on the USB drive, so it can't be that. But I'm just mentioning it in case they should be there (which I'm guessing they should).

 

 

Edited by arsradu

Share this post


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

1. I'm guessing you're building Clover with a custom script or something, cause I couldn't get mine to add BiosBlockIO.

you forgot to add -mc to ebuild.sh?

./ebuild.sh -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8

 

Share this post


Link to post
Share on other sites
Posted (edited)
2 minutes ago, vector sigma said:

you forgot to add -mc to ebuild.sh?


./ebuild.sh -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8

 

Can't forget something I never knew I needed. :))) But yeah, that part was missing. Thank you!

Edited by arsradu

Share this post


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

Replacing boot from 3911 into the 4995 USB also doesn't do anything. Same exact behaviour as above (stuck at "not found").

 

There might be a bit of confusion here.  Legacy boot should work now that you proved it does with r3911 :P.

  1. Install latest Clover r4996 with pkg installer in legacy mode targeting your USB drive (custom option: install in EFI etc)
  2. Make sure all your needed efi drivers are in EFI/CLOVER/drivers/BIOS, normal kexts, config.plist present in their respective folders etc
  3. Delete the file named "boot" at the root folder, / , of your USB drive's EFI partition (this is actually boot6=CloverEFI 64 bits SATA, renamed as "boot")
  4. Replace with boot7 = CloverEFI 64 bits BiosBlockIO (which I extracted from official Clover r3911 ISO on Sourceforge) on the root of the USB drive, renamed as "boot"

 

Try legacy boot again to your USB...

 

46 minutes ago, arsradu said:

Can't forget something I never knew I needed. :))) But yeah, that part was missing. Thank you!

Make sure you put the working boot7 from Clover r3911 in ~/src/edk2/Clover/CloverPackage/CloverV2/Bootloaders/x64 before running makeiso_boot7 from your ~/src/edk2/Clover/CloverPackage folder.  Otherwise it also won't be present in your Clover ISO :lol:.

 

Also regarding the missing embedded theme in your ISO:  Did you copy the embedded theme folder from ~/src/edk2/Clover/CloverPackage/CloverV2/EFI/CLOVER/themes to ~/src/edk2/Clover/CloverPackage/CloverV2/themespkg before running makeiso?

 

 

 

2 hours ago, XLNC said:

is aptiomemfix removed from clover ? 

 

Yes, this is an acidanthera project now. 

 

If you build Clover with Build_Clover.command and specify XCODE5 toolchain, you will still find it compiled in the ~/src/edk2/Build/AptioFixPkg/RELEASE_XCODE5/X64 folder  ---> manually copy it to your ~/src/edk2/Clover/CloverPackage/CloverV2/EFI/CLOVER/drivers/off/UEFI/MemoryFix folder.  Then cd to ~/src/edk2/Clover/CloverPackage and run ./makepkg to create the Clover installer.

 

Edited by fusion71au

Share this post


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

I made this change because of what? 

It was initially VOID*, but it is not compatible with VS2013 (error C2036).

Well that explain why. C standard treat void as an incomplete type while the gnu one consider it to be size 1. 

Share this post


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

There might be a bit of confusion here.  Legacy boot should work now that you proved it does with r3911 :P.

 

  1. Install latest Clover r4996 with pkg installer in legacy mode targeting your USB drive (custom option: install in EFI etc)
  2. Make sure all your needed efi drivers are in EFI/CLOVER/drivers/BIOS, normal kexts, config.plist present in their respective folders etc
  3. Delete the file named "boot" at the root folder, / , of your USB drive's EFI partition (this is actually boot6=CloverEFI 64 bits SATA, renamed as "boot")
  4. Replace with boot7 = CloverEFI 64 bits BiosBlockIO (which I extracted from official Clover r3911 ISO on Sourceforge) on the root of the USB drive, renamed as "boot"

 

Try legacy boot again to your USB...

 

 

 

 

Yeah, I guess I mixed some drivers...cause now IT WORKS!

 

I already replaced that boot file, as you mentioned. But I guess the problem was somewhere else....?

 

So, right now, I managed to get 4997 to boot (all the way into the OS) in Legacy mode.

But here's how:

1. on my existing USB drive with 3991, I replaced BOOTX64.efi in /BOOT and CLOVERX64.efi in /CLOVER with the ones I compiled for myself (version 4997) from my SSD's EFI folder. Call it "manual upgrade"...? :))

2. I copy-pasted drivers from drivers64 to drivers/BIOS and from drivers64UEFI to drivers/UEFI. The new /drivers folder was already there from my previous installations of 49xx versions. So I just copy-pasted from the old folder structure to the new one.

 

So maybe the reason why I couldn't boot with BiosBlockIO (getting stuck at Not Found) was the driver, not the boot file itself. That...or I was doing something else wrong. But I think that was it.

 

Update: confirmed.

 

SATA doesn't work (red screen).

BiosBlockIO DOES work (including from 4997, which now I can compile on my own, thanks to Vector Sigma's feedback).
 

BUT

 

The drivers need to be rewritten. Otherwise I get stuck with BiosBlockIO. As I said, the behaviour is a little different. With BiosBlockIO and wrong drivers, I get stuck at "Not Found". No red screen in this case. Just stuck.

With BiosBlockIO and correct drivers, all fine, I can boot Mojave with no problems.

 

With the default drivers in 4997, I can't boot. I have to look more into it, but not right now

 

However, with drivers copy-pasted from drivers64 and drivers64UEFI (from 3911, with some additions) into the new folder structure, it does boot.


2064342132_Screenshot2019-07-13at11_30_07.thumb.png.a48243a0aaa7ec032162fea2049368b4.png

 

*ApfsDriverLoader has been added by me, the rest of the drivers are from original 3911 installation.

482672959_Screenshot2019-07-13at11_30_22.thumb.png.f43b53c1f77369596cee67d819063ad8.png

 

*ApfsDriverLoader adn OsXAptioFix3Drv have been added by me. The rest of them are from the original 3911 installation.

drivers.zip

Edited by arsradu

Share this post


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

If you build Clover with Build_Clover.command and specify XCODE5 toolchain, you will still find it compiled in the ~/src/edk2/Build/AptioFixPkg/RELEASE_XCODE5/X64 folder  ---> manually copy it to your

Guys, isn't more easy to go at github/acidanthera/AptioMemoryFix/release and just download it?:whistle:

 

if you want it in the package, just copy it in

../CloverPackage/CloverV2/EFI/CLOVER/drivers/off/UEFI/MemoryFix/

just before call 'make pkg'

Edited by vector sigma

Share this post


Link to post
Share on other sites
Posted (edited)
29 minutes ago, vector sigma said:

Guys, isn't more easy to go at github/acidanthera/AptioMemoryFix/release and just download it?:whistle:

 

if you want it in the package, just copy it in


../CloverPackage/CloverV2/EFI/CLOVER/drivers/off/UEFI/MemoryFix/

just before call 'make pkg'

 

At the moment, the Build_Clover.command script has not been updated to take into account the new /Drivers folder structure that you introduced.  Before, AptioMemoryFix was automatically compiled and included in the final installer.pkg presented to the end user.

 

btw, I found another typo in the makeiso.script...for latest r5000, boot? should be boot6 I assume...attached fixed makeiso.fixed typo.zip OK, it copies both boot6 and boot7 :P

 

1879256035_typobootinmakeiso.png.15cde83f1d95db2955e07c99bd5fd5c4.png

 

Edited by fusion71au

Share this post


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

 

At the moment, the Build_Clover.command script has not been updated to take into account the new /Drivers folder structure that you introduced.  Before, AptioMemoryFix was automatically compiled and included in the final installer.pkg presented to the end user.

 

btw, I found another typo in the makeiso.script...for latest r5000, boot? should be boot6 I assume...attached fixed makeiso.fixed typo.zip

 

1879256035_typobootinmakeiso.png.15cde83f1d95db2955e07c99bd5fd5c4.png

 

Isn't a typo, it's correct. It just copy both boot6 and boot7 or whatever starts with boot

Edited by vector sigma

Share this post


Link to post
Share on other sites
Posted (edited)
44 minutes ago, vector sigma said:

@arsradu can you kindly try the attached iso if works in pure UEFI?

Clover-v2.4k-5000-X64.iso.zip

 

Sadly...nope... BIOS is set to see both Legacy and UEFI drives. For all my other UEFI drives (such as my HDD and SSD), it does show something like "UEFI OS:". For the DVD ROM. It doesn't. Which makes me think it's not UEFI (yet).

 

Also, selecting that DVD ROM (the legacy mode entry), I get this message (old, classical "nope, that's not it" kind of message).

 

The message is most likely intended. But...yeah, no UEFI yet.

 

IMG_0008.thumb.jpeg.2c7d159a24ebc772ed5f3444cc79f533.jpeg

Edited by arsradu

Share this post


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

 

Sadly...nope... BIOS is set to see both Legacy and UEFI drives. For all my other UEFI drives (such as my HDD and SSD), it does show something like "UEFI OS:". For the DVD ROM. It doesn't. Which makes me think it's not UEFI (yet).

 

Also, selecting that DVD ROM (the legacy mode entry), I get this message (old, classical "nope, that's not it" kind of message).

 

The message is most likely intended. But...yeah, no UEFI yet.

 

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

Share this post


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

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

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. :) 

Share this post


Link to post
Share on other sites
Posted (edited)

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.

Edited by Badruzeus

Share this post


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

osascript read-write or whatever it's name. I believe HFS+ has no r/o limitation under Catalina. Thanks.

I'll fix it, but is this a hack or it's normally allowed?

Share this post


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

I'll fix it, but is this a hack or it's normally allowed?

absolutely a hack, Apple has given warning back in Sierra time that HFS was being replaced with APFS. It's just some want to stay with old methods.

Share this post


Link to post
Share on other sites
6 hours ago, fusion71au said:

 

There might be a bit of confusion here.  Legacy boot should work now that you proved it does with r3911 :P.

  1. Install latest Clover r4996 with pkg installer in legacy mode targeting your USB drive (custom option: install in EFI etc)
  2. Make sure all your needed efi drivers are in EFI/CLOVER/drivers/BIOS, normal kexts, config.plist present in their respective folders etc
  3. Delete the file named "boot" at the root folder, / , of your USB drive's EFI partition (this is actually boot6=CloverEFI 64 bits SATA, renamed as "boot")
  4. Replace with boot7 = CloverEFI 64 bits BiosBlockIO (which I extracted from official Clover r3911 ISO on Sourceforge) on the root of the USB drive, renamed as "boot"

 

Try legacy boot again to your USB...

 

Can't forget something I never knew I needed. :))) But yeah, that part was missing. Thank you!

Make sure you put the working boot7 from Clover r3911 in ~/src/edk2/Clover/CloverPackage/CloverV2/Bootloaders/x64 before running makeiso_boot7 from your ~/src/edk2/Clover/CloverPackage folder.  Otherwise it also won't be present in your Clover ISO :lol:.

 

Also regarding the missing embedded theme in your ISO:  Did you copy the embedded theme folder from ~/src/edk2/Clover/CloverPackage/CloverV2/EFI/CLOVER/themes to ~/src/edk2/Clover/CloverPackage/CloverV2/themespkg before running makeiso?

 

 

 

 

Yes, this is an acidanthera project now. 

 

If you build Clover with Build_Clover.command and specify XCODE5 toolchain, you will still find it compiled in the ~/src/edk2/Build/AptioFixPkg/RELEASE_XCODE5/X64 folder  ---> manually copy it to your ~/src/edk2/Clover/CloverPackage/CloverV2/EFI/CLOVER/drivers/off/UEFI/MemoryFix folder.  Then cd to ~/src/edk2/Clover/CloverPackage and run ./makepkg to create the Clover installer.

 

And sorry for noob question: if I use the Acidanthera one, I must put it in the memory fix folder?

Share this post


Link to post
Share on other sites
34 minutes ago, brousseau6933 said:

And sorry for noob question: if I use the Acidanthera one, I must put it in the memory fix folder?

Found myself: just added it in Drivers/UEFI...

Share this post


Link to post
Share on other sites

Guys, please don't mad to me;

 

What are the differences between VBoxHfs and the HFSPlus? Both say "EFI filesystem driver for HFS+" is that so, what are the differences?

 

Share this post


Link to post
Share on other sites

 

7 minutes ago, telepati said:

What are the differences between VBoxHfs and the HFSPlus? Both say "EFI filesystem driver for HFS+" is that so, what are the differences?

VBoxHfs = open source driver that works really good, read only.

HFSPlus = extracted from Apple's firmware. Someone says you need it for RAID configurations. Otherwise VBoxHfs it's enough.

Share this post


Link to post
Share on other sites
Posted (edited)

@vector sigma or @fusion71au

 

Any idea which part of the makeiso script formats the resulting iso image as Apple Partition Map? I can't figure it out.

 

1370411295_Screenshot2019-07-13at20_40_33.thumb.png.fd8606b922be406b2da9d34bd1924114.png

 

Edit:

 

apparently this part:

hdiutil makehybrid...

 

Edited by arsradu

Share this post


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

Guys I think is better to commit all translatioons tomorrow and give times to any other is doing this. @Slice, why not opening a Topic for translations only?

OK, done!

All post about translations splitted into new topic Clover Localizations

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
       
       
       
       
       
       
       
       
       
       
       
       
       
×