Beiträge von Jamie

Von Veemyu und statt Vmware Fusion virtualbox because AMD

VMware fusion is required or if you know of any other method to get a fully installed big sur installation onto your Harddrive that's also fine.

E.g Simple KVM

The problem with Big sur is that Opencore can't inject Kexts properly into the installer / Recovery so we need a fully installed Big sur installation first.

Either using KVM VMware(this guide) or from a real mac with an external ssd

1. Open VMware Fusion and create a new custom virtual machine choose Apple --> mac OS 10.15

Leave the Disk Settings at the default of 40GB and if possible don't split files and press continue

2. Customize the VM Settings to feature an additional virtual harddisk with at least 64GB also without split files

6-8GB of RAM should be minimum for the VM (speed)

3.Close VMWare fusion as we now have our 2 VMDKs created

4. Install Paragon VMDK Mounter

Disclaimer:

This isn't a crack. This software is just deprecated and the licensing has been shut down. You need a license but it was always free (you basically signed up with your email and got a free serial directly from paragon so this is nothing illegal)

http://dl.paragon-software.com/free/VMDK_MOUNTER_2014.dmg

PRODUCT KEY: VMDK-MOUNTER-2014-434979472

SERIAL NUMBER: 51537-43450-1B2D9-8213A

5. Go to your Home Folder then -- > Virtual Machines -- > where you'll find your 10.15 Virtual Machine. Right click and open it with VMDK mounter then it'll ask you what Virtual Disk you want to mount choose the 40GB one that you created. It will mount a Macintosh HD. If it says unknown Disk eg. Needs to be intitialised redo Step 1.

Go to disk utility and re-format the Macintosh HD as Mac OS Extended Journaled eg. HFS+ DO NOT FORMAT THE DEVICE just format the single partition.

6. Go into terminal and create your macOS Beta installer

sudo /Applications/Install\ macOS\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/40GBVMDK

And then it'll transfer all the install files onto the 40GB VMDK

When it's finished, unmount the VMDK Disk with Disk Utility.

The whole Disk needs to be ejected so right click the VMDK Mounter Device and click eject there mustn't be any trace of it inside of Disk Utility if there's still a VMDK Mounter Device visible inside of Disk Utility please restart your PC.

Start up your VM. Which should boot into the Big Sur installer because the VM has the VMDK in it which we transferred the Install Data to.

Open the Big Sur Disk Utility in the VM and format the second Hard Disk with GUID APFS.

Tap on View --> Show all Devices

We now need to format the whole VMware Device so we'll create a GUID Partition Table.

We'll then quit Disk Utility and install Big sur onto our freshly formatted 64GB+ APFS Volume

If the installer initiates a reboot and it always boots into the installer or recovery instead of the second stage of installing Bug Sur.

Just remove the 40GB installer Virtual Disk from the Virtual Machine.

Installation should then continue as normal.

Setup Big sur and put in your user info. We need Big Sur set up right up to the normal Desktop or else it won't boot on your Hackintosh.

7. When you're booted to the Desktop in the VM shut it down.

8. Open the Big Sur VMDK from Home Folder --> Virtual Machines 10.15 and choose the 64GB+ VMDK

9. You now need to clone the installation to a Bootable disk.

10. Open Disk Utility and create a new APFS Container Partition (DO NOT ADD A VOLUME TO AN EXISTING APFS CONTAINER, YOUR EXISTING INSTALLATION WILL BREAK) on an internal Disk that you can boot from and then unmount that partition.

Unmount the single partitions of the VMDK mount not the VMDK Mount itself we just need it unmounted so we can clone the VMDK to our Internal Disk

Click on your Internal Disk's new APFS partition (not the device ) and restore it with the Big Sur (The normal Partition, not the Data partition that get's copied over automatically) and don't worry about the Update partition we don't need it.

It should copy over normally .

NVRAM > Add > 7C436110-AB2A-4BBB-A880-FE41995C9F82 > booter-fileset-kernel - type Data - value 00

NVRAM > Delete > 7C436110-AB2A-4BBB-A880-FE41995C9F82 > type String - value booter-fileset-kernel

AvoidRuntimeDefrag no longer needs to be off with OC from the latest master build.

You will need to bypass Stage 2 somehow, see above.

11. Open your config.plist and change:

Booter --> Quirks --> AvoidRuntimeDefrag to FALSE (NO) otherwise you can't boot at all

This is fixed with the latest OpenCore Build as of July 26th 2020

NVRAM > Add > 7C436110-AB2A-4BBB-A880-FE41995C9F82 > booter-fileset-kernel - type Data - value 00

And also

NVRAM --> Delete --> 7C436110-AB2A-4BBB-A880-FE41995C9F82

create a new String with value "booter-fileset-kernel"

IGPU users need -disablegfxfirmware to boot

That's about it

And use a freshly compiled version of OpenCore 6.0.0

Just install XCODE and then "git clone --recursive --depth=1 github.com/acidanthera/OpenCorePkg" the OpenCorePKG Repository and ./oc_buidtool to build opencore and then update opencore as normal

And also compile Lilu and VirtualSMC and it's plugins from source compile Lilu first with Xcode and then copy Lilu.kext into the VirtualSMC build Folder or use the goldfish repo