Sorry. Dell 9020 mt with i7 4770 and another similar with i5 and rx 560. I was clone the sata ssd to pcie nvme ssd with filezilla. On the boot opencore have only one big sur selection.
Sorry. Dell 9020 mt with i7 4770 and another similar with i5 and rx 560. I was clone the sata ssd to pcie nvme ssd with filezilla. On the boot opencore have only one big sur selection.
These are the Mac models that will let you download Big Sur and create your USB installer. Whether you use a hackintosh or a Mac your SMBIOS needs to meet these minimum specs to be eligible.
When your Mac is ineligible to download Catalina or Newer macOS versions If your Intel Mac is from approximately 2011/12 or older (see post #2) you won't be able to download Catalina from the Mac App Store. Follow the instructions in these videos to enable the download of Catalina or newer...
www.tonymacx86.com
2. Create the USB Installer
As with Catalina, you'll need a minimum of a 16GB USB flash drive if you're going to use macOS to make your Big Sur installer. 32GB USBs also work. Anything larger, make a small partition of at least 16GB but less than 32 for building the installer. Big Sur should be in Applications.
You'll need to use createinstallmedia method after you've formatted the USB as Mac OS Extended (Journaled) and GUID partition table via Disk Utility. You can name the drive simply USB. Now open up Terminal and then copy/paste the following there and press return. Enter your password and return again.
Once you've installed Big Sur to the USB, the next task is to create the custom OpenCore EFI folder and then copy/paste that to the EFI partition of the USB after completing all edits. This is where you'll need to use a sample config.plist and modify it specifically for your hardware.
OpenCore Bootloader and the Dortania Guide
1. Download the standalone OpenCore Bootloader package installer from the official downloads section.
2. Apply necessary kexts, SSDTs and make the required edits (Haswell specific) to the config.plist using ProperTree.
Alternative Method
For those that want a Multibeast Like GUI to create their EFI folder, there is a handy app called OC Gen-X created by Pavo that you can use. https://github.com/Pavo-IM/OC-Gen-X/releases
1. Open OC Gen-X and select System Type -> Intel Consumer -> Haswell
2. Select the Kext tab and leave the two default choices as they are
3. Under VirtualSMC Plugins select the SMCProcessor kext
4. Under Graphics select the Whatevergreen kext
5. Select AppleALC for Audio
6. For your Ethernet kext select IntelMausi
7. Firmware Drivers - leave the defaults checked
8. SMBIOS - iMac15,1 (Serials and SMUUID will be entered later)
9. BootArgs - Enter -v to boot verbose keepsyms=1 and debug=0x100
10. Generate your EFI folder
Your brand new OC EFI folder will appear on your desktop. Leave it there for now.
11. Copy and paste the ACPI files (attached below) into the newly created ACPI folder in the OC folder.
12. Copy and paste the 2 extra kexts into the kexts folder. Also attached below.
13. If you have a MT 7020/9020 you can use the kext attached below which enables the internal USB 2.0 port HS13. It's called Dell MT.USBPorts.kext. I have HS13 set to internal for those that will connect a Wifi/BT card. I've attached a pic below of the MT board so you can see where the internal USB 2.0 header resides.
SFF and USFF owners should use the USBports kext in the "2 extra kexts" folder below. Those have no HS13.
14. Add modGRUBShell.efi to the tools folder
4. Adding patches and setting Quirks in the newly created Config.plist
Next is the config.plist editing. Use the PlistEditPro app and the free trial or you can use ProperTree if you prefer but I find it much easier to do this by using PlistEditPro app.
Add the three specialized ACPI patches for the HPET, RTC and TIMR to the ACPI -> Patch section. They are included in the example config.plist so you can transfer those into your config.plist you've created. The example config.plist is attached below. See the video above for instructions of how to copy them to the new config.plist.
Refer to the above OC EFI video to see all the changes to make in the .plist.
Once everything is set then it's time for the OC snapshot. Demonstrated in the video also.
1. Now open up your new config.plist with ProperTree (attached below)
(right click on ProperTree.command and open it up with terminal)
2. Click on the File menu in the menu bar then OC Snapshot (Cmd +R).
Once all your config.plist edits are done copy the finished OpenCore Custom EFI folder to the EFI partition of the USB installer you just created with Big Sur. You'll have to mount the hidden EFI partition of the USB first. I use EFI Agent app by the creator of Hackintool. https://github.com/headkaze/EFI-Agent/releases
OpenCore Basics
ACPI
SSDT-EC.aml - Fix for EC (Embedded Controller) on Catalina and above
SSDT-PLUG.aml - Allows for native CPU power management
@trs96 Thanks for your efforts! Your YouTube guided me following you fresh install my Big Sur on a new ssd driver.
However, I would like you to address few things/issues:
1) when I boot into OS, how can I enter directly into apple progress bar instead of the OC menu following the entries scanning? I really don't like the entries scanning that I don't understand each line of them.
2) Few softwares I installed on Catalina worked great but not on this Big Sur, e.g.: Ring (from App Store, when I clicked a camera, it is just green ), amcrest surveillance pro (open a camera just blink), and Minecraft can't be opened....I searched online tried to figure out if these softwares have similar issues on Big Sur, but couldn't find any related, so I think I missed something when installed it. Thank you !
when I boot into OS, how can I enter directly into apple progress bar instead of the OC menu following the entries scanning? I really don't like the entries scanning that I don't understand each line of them.
Edit the config.plist and remove -v which shows the verbose info at boot up. I mentioned it in the guide. You can delete all of the boot-args if you'd like.
Few softwares I installed on Catalina worked great but not on this Big Sur, e.g.: Ring (from App Store, when I clicked a camera, it is just green ), amcrest surveillance pro (open a camera just blink)
In post #1 of the guide I did say that it's a little too early to fully migrate to Big Sur. Some things like specific apps will not work properly. You can go back to Catalina and keep using OC if you want to.
Edit the config.plist and remove -v which shows the verbose info at boot up. I mentioned it in the guide. You can delete all of the boot-args if you'd like. View attachment 508066
In post #1 of the guide I did say that it's a little too early to fully migrate to Big Sur. Some things like specific apps will not work properly. You can go back to Catalina and keep using OC if you want to.
Thanks quick reply!
1) removed -v and skipped the verbose scanning, works great!
2) I am so unlucky that few app are not working on Big Sur. How can I return Catalina? Just simply copy my OC's EFI to Clover's EFI or need anything else?
There is not nvmefix.kext file in this link. I found in another site the nvmefix.kext file but not working. The opencore menu shows only one big sur installation.
There is not nvmefix.kext file in this link. I found in another site the nvmefix.kext file but not working. The opencore menu shows only one big sur installation.
Do you have the NvmExpressDxe.efi driver in your drivers folder ? It must also be enabled in the config.plist. Try taking another OC snapshot with ProperTree.
I tried something that might indicate the software compatibility issues occur on Big Sur with OC boot:
As I couldn't use Minecraft and Ring (from Apple Store) on Big Sur, I return to Catalina with OC instead of Clover I used before, I found I still couldn't use them on Catalina/OC, but they are normally displayed on Catalina/Clover. That addressed there are something missed in my OC setting. Please advise and see attached pics! Thank you!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
github.com
