Administrators Gengik84 Posted April 29, 2019 Administrators Share Posted April 29, 2019 Hi people.. I will show some basic informations to start configuring OpenCore bootloader. This is EFI's structure EFI ├── BOOT │ └── BOOTx64.efi └── OC ├── ACPI │ └── Custom ├── Drivers ├── Kexts ├── OpenCore.efi └── Config.plist As you can see inside EFI folder we have two nested folders BOOT and OC ... This is a structure very similar to Clover bootloader one, inside BOOT we have BOOTx64.efi, this file is mandatory to have a working boot. Inside OC we have all necessary folders like ACPI,Drivers,Kexts inside ACPI we cand find Custom folder, this will be the place where we have to put our patched ACPI if our hack needs them. In Drivers folder we have to put all drivers we need to boot. Important NOTE:No x64 extension is needed for them You DO NOT use Clover's drivers , in OpenCore they are different (vBox is an exception alternative to HFS.plus Main Drivers are: AptioMemoryFix ApfsDriverLoader (mandatory if you have a disk in apfs format, otherwise you do not need of it HFS.plus or vBox Kexts: Obviously , here we will put extra kexts Open config.plist with a PlistEditor or with Xcode if installed in your system for good English translation. 1 Link to comment Share on other sites More sharing options...
Administrators Gengik84 Posted April 29, 2019 Author Administrators Share Posted April 29, 2019 ACPI first step If you have to use patched ACPI it is mandatory to put them inside this folder: EFI/OC/ACPI/Custom Then you have to define and enabled it as pictures below Next we have to define and enable to load it Successivamente definite e abilitate per il caricamento Esempio nome convertito.png You can drop also in other way, you can use table OEM "name" Open it with maciasl app and check it strTohex.zip strTohex.zip strTohex.zip Link to comment Share on other sites More sharing options...
Administrators Gengik84 Posted April 29, 2019 Author Administrators Share Posted April 29, 2019 Device Properties 59[/color]120000 and FakeID 0x59128086 First of all we have to invert numbers order two by two. You do not have to consider first 0x so, ig-platform-id with Properties is: AAPL,ig-platform-id 00 00 12 59 instead for FakeID value you have to omit 0x and also 8086 will be transformed to 0000 so we will have: device-id 00 00 12 59 GFX0/IGPU[/b] PciRoot(0x0)/Pci(0x2,0x0) HDEF/HDAS PciRoot(0x0)/Pci(0x1b,0x0) IE when we set layout to 1 in our config you will have this: Link to comment Share on other sites More sharing options...
Administrators Gengik84 Posted April 29, 2019 Author Administrators Share Posted April 29, 2019 Kernel ADD: In this section we have to declare all kext we use in EFI folder BundlePatch[/b]: "name".kext Enabled: YES or NO option to load it or not ExecutablePatch: it shows path for executable file MatchKernel: this is usefull to declare OSX in use or better to declare optimal OSX for kext, in clover we have different folders (10.12,10.13 and so on) where we put relative kext useful for installed OSX How to know which value we have to use in it? 18 value is for Mojave.. previous version have 17 or 16 IE inserting 18 our kext will be loaded on all Mojave release (from 10.14 to 10.14.6 if it exists) We have also the chance to define a specific OSX version in this way. today latest Mojave beta is 10.14.5 If we would like to choose a more precise OSX version? Well. today latest Mojave beta is 10.14.5 that is 18.6 How to achieve this task? Open a terminal windows and type: [code]uname -r [/code] [/b]info.plist path which is pretty surely (about 99% of situation)the same path Block Quirks[/color] Qui troviamo alcune patch Link to comment Share on other sites More sharing options...
Administrators Gengik84 Posted April 29, 2019 Author Administrators Share Posted April 29, 2019 Post riservato Misc Link to comment Share on other sites More sharing options...
Administrators Gengik84 Posted April 29, 2019 Author Administrators Share Posted April 29, 2019 Pst riservato PlatformInfo Link to comment Share on other sites More sharing options...
Administrators Gengik84 Posted April 29, 2019 Author Administrators Share Posted April 29, 2019 NVRAM Link to comment Share on other sites More sharing options...
Administrators Gengik84 Posted April 29, 2019 Author Administrators Share Posted April 29, 2019 UEFI In this section we will declare efi drivers we use In this picture we show basic one driver If you have defined some drivers in your config but they are not present in Drivers folder, your system will hang on boot. To solve you have to remove or disable relative option in config.plist, or you can copy in Drivers folder that driver Note: If you use FV2 you have to add some drivers to have a working FV2 Link to comment Share on other sites More sharing options...
Supervisor fabiosun Posted May 2, 2019 Supervisor Share Posted May 2, 2019 Thank you @Gengik84 for helping us in many task to have a working and updated hack Now we can also try this new shining bootloader 🙂 Link to comment Share on other sites More sharing options...
Recommended Posts