Mac Os Big Sur On Unsupported

admin

Aug 13, 2021 Once you have taken a backup follow the instructions below to install macOS Big Sur on your unsupported Mac. Step 1: First you need to download two files from the links below to complete the macOS 11 Big Sur installation on your unsupported Mac. MacOS Big Sur PKG installer: https://developer.apple.com/macos/. Big Sur Micropatcher ⭐ 1,055. A primitive USB patcher for installing macOS Big Sur on unsupported Macs. Patched Sur ⭐ 940. A simple but powerful patcher for macOS Big Sur. Automator For Barrykn Micropatcher ⭐ 24. Automator for the BarryKN Micropatcher. 1 - 3 of 3 projects. Advertising 📦 9. To install macOS Big Sur on an unsupported Mac we must do it on a disk partition and from macOS Catalina. This way if something goes wrong, we can always continue using our Mac as if nothing else. To make a partition follow these steps: Click on the magnifying glass and look for the app Disk utility. Up click on Create partition. If you’re an advanced user who is comfortable with running unsupported system software on unsupported hardware, and you’re feeling adventurous, there are some solutions to install and run macOS Big Sur on unsupported Macs, but it’s nowhere near as straight forward or simple as installing Big Sur on an officially supported Mac is.

  1. Big Sur Unsupported Patch
  2. Mac Os Big Sur Download
  3. Mac Os Catalina
  4. Mac Os Big Sur Unsupported Mac Github
  5. Download Mac Os Big Sur On Unsupported Imac

It's that time of year again and with it, and a new macOS beta has been dropped. Here's all the info you need to get started.

Reminder that Dortania and any tools mentioned in this guide are neither responsible for any corruption, data loss, or other ill effects that may arise from this guide, including ones caused by typos. You, the end user, must understand this is beta software on unsupported machines so do not pester developers for fixes. Dortania will not be accepting issues regarding this mini-guide except for typos and/or errors.

Once done, reboot your Mac. Install future macOS Big Sur updates on unsupported Macs. Whenever there is an update for macOS Big Sur, instead of updating using Software Update in System Preferences.

This guide expects you to have a basic understanding of hackintoshing. If you are not familiar with it, we highly recommend you to wait until there is an easier and more straight-forward solution available.

# Backstory

More a mini-explainer as to why this release is a bit more painful than average macOS releases, the main culprits are as follows:

# AvoidRuntimeDefrag

With macOS Big Sur, the AvoidRuntimeDefrag Booter quirk in OpenCore broke. Because of this, the macOS kernel will fall flat when trying to boot. Reason for this is due to cpu_count_enabled_logical_processors requiring the MADT (APIC) table, and so OpenCore will now ensure this table is made accessible to the kernel. Users will however need a build of OpenCore 0.6.0 with commit bb12f5f or newer to resolve this issue.

# Kernel Collections vs prelinkedkernel

Since 10.7, the prelinkedkernel has been the default way for real macs to boot. This contained a very minimal amount of kexts to get a mac booted. This same bundle is what OpenCore uses to inject kexts, and was hoped to last quite some time. With macOS Big Sur, a huge change happened in where Apple no longer makes it the default form of booting.

Due to the hard work of @acidanthera, OpenCore gained experimental support for this new format in roughly 2 weeks, and we can now attempt to boot Big Sur on our hackintoshes without a Mac or VM - although you will likely run into some issues along the way.

# Prerequisites

Before we can jump head first into installing Big Sur, we need to go over a few things:

# A supported SMBIOS

Big Sur dropped a few Ivy Bridge and Haswell based SMBIOS from macOS, so see below that yours wasn't dropped:

  • iMac14,3 and older
    • Note iMac14,4 is still supported
  • MacPro5,1 and older
  • MacMini6,x and older
  • MacBook7,1 and older
  • MacBookAir5,x and older
  • MacBookPro10,x and older

If your SMBIOS was supported in Catalina and isn't included above, you're good to go!

For those wanting a simple translation for their Ivy and Haswell Machines:

  • iMac13,2, iMac14,2 and iMac14,3 should transition over to using iMac15,1
  • iMac14,1 should transition over to iMac14,4

# Supported hardware

Not much hardware has been dropped, though the few that have:

  • Official Ivy Bridge U, H and S CPUs.
    • These CPUs will still boot without much issue, but note that no Macs are supported with consumer Ivy Bridge in Big Sur.
    • Ivy Bridge-E CPUs are still supported thanks to being in MacPro6,1
  • Ivy Bridge iGPUs.
    • HD 4000 and HD 2500, initial developer beta forgot to remove drivers but more than likely to be removed in later updates.
  • BCM94331CD based Wifi cards.
    • See Wireless Buyers guide for potential cards to upgrade to.
  • Certain SATA controllers dropped
    • For some reason, Apple removed the AppleIntelPchSeriesAHCI class from AppleAHCIPort.kext. Due to the outright removal of the class, trying to spoof to another ID (generally done by SATA-unsupported.kext) can fail for many and create instability for others.
    • A partial fix is to block Big Sur's AppleAHCIPort.kext and inject Catalina's version with any conflicting symbols being patched. You can find a sample kext here: Catalina's patched AppleAHCIPort.kext
    • This will work in both Catalina and Big Sur so you can remove SATA-unsupported if you want.

Also note that AMD OSX has updated their patches, but they are experimental and unsupported and you will not obtain support for them:

And a special note for MSI Navi users, you no longer require the ATY,rom/-wegnoegpu patch to boot the installer!

# Up-to-date kexts, bootloader and config.plist

Ensure you've updated to the latest builds (not releases) of OpenCore and all your kexts, as to avoid any odd incompatibility issues. You can find the latest builds of kexts and OpenCore here:

  • Driver Repo (contains OpenCore builds too).

You will also need to ensure you have a few NVRAM variables set:

  • NVRAM -> Add -> 7C436110-AB2A-4BBB-A880-FE41995C9F82:
    • boot-args:
      • -lilubetaall
        • Newest builds of Lilu(v1.4.6+) and most plugins do not require this boot-arg
      • vsmcgen=1
        • Newest builds of Lilu(v1.4.6+) and VirtualSMC(v1.1.5+) don't need this boot-arg
      • -disablegfxfirmware
        • Newer builds of WhateverGreen(v1.4.1+) resolves this

If you're unsure what version of OpenCore you're using, you can run the following in terminal:

  • Note: The about command will require you to include bit 0x2 in Misc -> Security -> ExposeSensitiveData, recommended values for ExposeSensitiveData is 0x6 which includes bits 0x2 and 0x4.

# Known issues

With Big Sur, quite a bit broke. Mainly the following:

  • Lilu
    • Mainly user-space patching has severely broke, meaning certain patches like DRM don't work
    • Kernel-space should be working correctly with v1.4.6, but plugins may require updates due to a complete rewrite of the patcher for Kernel Collection support.
  • VirtualSMC
    • Some users may notice that even with vsmcgen=1 in boot-args, you'll still have VirtualSMC failing. To work around this, you may need to use FakeSMC till vSMC and Lilu issues are resolved.
    • Resolved with v1.1.5+
  • Battery status
    • Currently RehabMan's ACPIBatteryManager is the only working kext for battery status.
    • Resolved with VirtualSMC v1.1.5+
  • AirportBrcmFixup
    • Forcing a specific driver to load with brcmfx-driver= may help
    • BCM94352Z users for example may need brcmfx-driver=2 in boot-args to resolve this, other chipsets will need other variables.
  • Intel HEDT hackintoshes failing to boot
    • This is due to Asus and many other OEMs excluding certain regions from your RTC device, to resolve this we can create a new RTC device with the proper regions.
    • OpenCorePkg includes a sample SSDT that goes in-depth: SSDT-RTC0-RANGE.dsl

And while not an issue, SIP has now gained a new bit so to properly disable SIP you need to set csr-active-config to FF0F0000. See here for more info: Disabling SIP

# Installation

For the installation, you'll need a few things:

  • macOS Big Sur installer
  • 12GB+ USB drive
  • A Mac, hack, or pre-existing VM to download the installer and create install media
  • Latest builds of OpenCore and kexts (see above)

# Grabbing the installer

To grab the Big Sur installer, download the beta profile from Apple's developer portal, then check for updates in System Preferences. If you don't have a developer account, you can use gibMacOS to download it:

Download gibMacOS and open gibMacOS.command:

Press M to change the Max OS, then enter 10.16 to switch the (update) catalog to the Big Sur one.

Press C to change the catalog, then select the number for the developer catalog.

Select the number for the Big Sur beta to start downloading it.

Once finished, open the InstallAssistant.pkg that was downloaded - it will be located in the gibMacOS/macOS Downloads/developer/XXX-XXXXX - Install macOS Beta folder. This package from Apple will create Install macOS Big Sur Beta.app in your /Applications folder.

Run the InstallAssistant.pkg and point this to whichever drive you're booting off of, this is where the Install.app will be dropped:

Once done, you should find it located in your Applications folder:

Apps

# Creating the installer

To create the USB is quite simple, grab your USB drive and open Disk Utility in macOS. Next format as follows:

  • Name: MyVolume
  • Format: macOS Journaled
  • Scheme: GUID Partition Map

Once this is done, run the following command:

This will take some time so you may want to grab a coffee, once done your USB should be good to boot!(Assuming you updated OpenCore and co earlier)

Big Sur Unsupported Patch

# Installing

Installing macOS 11: Big Sur on a Hackintosh is fairly similar to how previous version of macOS were installed, with the main issues being:

  • KernelCollections over prelinkedkernel (discussed above)
  • Installation being much longer
    • This is due to the new snapshot feature of the OS
  • Certain kexts breaking
    • Mainly Lilu and plugins, though quite obvious when they break

For the last one, if you get a kernel panic with Lilu we highly recommend you to update to the latest version with links we provided above. If errors are still not resolved, you may need to disable Lilu outright.

# Troubleshooting

# Stuck at Forcing CS_RUNTIME for entitlement

This is actually the part at where macOS will seal the system volume, and where it may seem that macOS has gotten stuck. DO NOT RESTART thinking you're stuck, this will take quite some time to complete.

# Stuck at PCI Configuration Begins for Intel's HEDT boards

As previously mentioned, Intel HEDT motherboards may have some issues revolving around their RTC device in ACPI. To resolve, you'll need to look at your RTC device and see which regions are missing. For more information, see here: SSDT-RTC0-RANGE.dsl

# Stuck on ramrod(^^^^^^^^^^^^^)

If you get stuck around the ramrod section (specifically, it boots, hits this error, and reboots again back into this, causing a loop), this hints that your SMC emulator is broken. To fix this, you have 2 options:

  • Ensure you're using the latest builds of VirtualSMC and Lilu, with the vsmcgen=1 boot-arg
  • Switch over to Rehabman's FakeSMC (you can use the MinKernel/MaxKernel trick mentioned above to restrict FakeSMC to Big Sur and up

And when switching kexts, ensure you don't have both FakeSMC and VirtualSMC enabled in your config.plist, as this will cause a conflict.

# DeviceProperties injection failing

With Big Sur, macOS has become much pickier with devices being present in ACPI. Especially if you're injecting important properties for WhateverGreen or AppleALC, you may find they're no longer applying. To verify whether your ACPI defines your hardware, check for the acpi-path property in IORegistryExplorer:

Mac Os Big Sur Download

If no property is found, you'll need to create an SSDT that provides the full pathing as you likely have a PCI Bridge that is not documented in your ACPI tables. An example of this can be found here: SSDT-BRG0

  • Note: This issue may also pop up in older versions of macOS, however Big Sur is most likely to have issues.

# Some kexts may not be compatible with Big Sur yet

There are a lot of kexts out there, and Big Sur is still pretty new. Not all kexts are working yet, so if you're experiencing a weird kernel panic, one thing you can try is booting with only the essential kexts (Lilu, VirtualSMC/FakeSMC, WhateverGreen) and seeing if it works. If so, you can enable kexts one by one to try to narrow down the issue.

# Virtual Machine Route

If you're still facing issues, or if with a new beta things break, you can try the virtual machine route to install on a disk and then transfer it over to your hack. Follow the following instructions to build install media and then install in a hypervisor.

Note: If you have an AMD CPU, this method isn't going to work.

# Building the Installation Media

Requirements:

  • A computer or VM running macOS
  • The desired macOS installation software installed to /Applications

Once you have the installation software installed to /Applications you will need to create a VDI of the installation media that will be used to install macOS in your VM. The instructions below are intended to be cut and pasted without editing unless specified.

First, set the IMAGE variable to the name of the installation you are installing. The example defines the image for Big Sur.

Next, create an empty 16GB image to host the media.

Verify that you have a 16GB file named 'Install macOS Beta.img' before continuing. After that, attach it to your macOS system as a virtual disk using the variable you created earlier.

Run diskutil list and verify that you have a disk attached that is type 'disk image'.

Now that the image is mounted, format it to Journaled HFS+.

Once the image is formatted, create the installation media.

Now detach or eject the virtual disk.

You now have a raw image of the installer. Follow the appropriate page for the hypervisor you'll be choosing:

Big Sur on unsupported Mac

Installing Big Sur on an unsupported Mac can’t be done the regular way through System Preferences > Software update. However, if the machine’s not too old, there’s still a way to install Big Sur on an unsupported Mac using a specially developed patcher tool.

Big Sur Workaround

At first glance, it may seem impossible to install macOS Bug Sur on a machine that’s not supported. If you are using a Mac that’s too old and go to its Software Update section, you will see that you are simply not allowed to install the Big Sur upgrade. If, however, you are determined to get Big Sur on your Mac, it may still be done in a roundabout way, by using a specially-developed patcher that you can download from here.

Depending on how old your Mac is, the patcher may or may not enable you to install Big Sur – some Macs are just too old, and even the patcher cannot make it possible for the latest macOS to be installed on them.

On the linked page (from where you can download the patcher), you can find notes that show for which Mac models (and hardware compositions) the patcher is most likely to work and for which it’s not recommended to try it. Carefully look through those notes and if it turns out that your Mac doesn’t have the necessary prerequisites, it’s best if you don’t try the patcher as it will probably not work and may cause unnecessary complications that could be difficult to fix. There is a reason why the latest macOS isn’t supported on older Mac models. The system requirements of Big Sur are higher than what most of the older models can effectively handle and so, unless you are certain that your Mac can run on Big Sur (check the notes in the link), it would probably be best if you kept its current macOS, that it can run stably.

Important Note

Also, it is important that you back up your important data – even if your Mac model and hardware composition are compatible with the patcher according to the notes, you should still make sure that any important data you don’t want to lose is safely backed up.

Another thing to mention is that, if you are using FireVault, you need to have it turned off, or else the patcher will probably not work.

The last precaution before you start with the Big Sur installation is to download the current macOS that you have on your Mac/MacBook onto a USB stick so that, should there be a problem with the Big Sur installation, you can always install the older macOS onto the machine using the USB stick.

With all that out of the way, here’s how you can use the Big Sur patcher to upgrade your unsupported Mac to the latest macOS.

How to install Big Sur on unsupported Mac

To install Big Sur on an unsupported Mac, you must first create a bootable USB drive using a special patcher app. Then you need to use the USB drive to install Big Sur on the unsupported Mac, and, lastly, you must install the needed patches.

Creating a bootable USB stick using the Big Sur patcher.

The first phase of the process involves creating a bootable USB drive with the help of a special patcher, so here’s how to do that:

  1. Start by getting an empty USB stick with enough space on it – it is recommended the stick has at least 16 GB free storage space (the more, the better).
  2. Plug the empty USB stick into your Mac, go to Spotlight (the magnifying glass icon in the top-right), type Disk Utility, and hit Enter.
  3. Select the View icon in the top-left and select Show All Devices.
  4. Click on the USB drive from the left panel, and select Erase.
  5. In the Erase window, make sure that the format is set to Mac OS Extended and click on Erase.
  6. After the USB drive is erased, close the Disk Utility, open your browser, and go to the page where the patcher is (here is the link to it again). DO NOT remove the USB stick from your Mac – it must stay plugged into the computer during the next steps.
  7. Look at the right side of the page, where it says Releases (you may have to scroll down a bit), and select Latest.
  8. You will see the latest available patch and down below, under assets, you will see the download link/links for it. Click on the first link and download the file on your Desktop.
  9. Next, close the browser, open the patcher, and when a window pops up on your screen, double-click on the Patched Sur icon.
  10. When macOS asks you if you are sure you want to open the app, select Open and select Start from the newly-opened window.
  11. Next, the patcher will automatically detect what Mac model you are using and show you what Big Sur features will work on it and what features won’t be available – select Continue in that window.
  12. If you want, read the guide that appears on your screen and click Continue again.
  13. On the next page, make sure that the “Release” option is selected, and click on Continue.
  14. In the next screen, select Update, and then click Continue.
  15. Wait until the download finishes and then click on Download macOS 11.0.1 (or whatever macOS version is shown).
  16. Wait for the loading process to complete (it’s likely going to take quite a lot of time, so be patient), provide your Mac password, and click on Continue.
  17. Next, select the name of the empty USB stick and then select Continue, and Continue again on the next page.
  18. The following process could take quite some time, so be patient, wait for everything to be finished, and then close the window. Once the process is complete, macOS Big Sur will be downloaded onto the empty USB stick and will be ready to be installed on your Mac. To close the window, click on Patched Sur in the top-left and select Quit Patched Sur.

Installing macOS Big Sur

Once you have the bootable USB stick ready, it’s time to install Big Sur on your Mac.

  1. Shut down your Mac and when it powers down completely, start it back up, and immediately after pressing the power button, press and hold the left Option (Alt) key.
  2. Once you get a screen with three different options, select the one labeled Install macOS Big Sur. If you don’t get that screen and your Mac starts normally, repeat the previous step until you get the screen with the three options.
  3. When your Mac loads to a screen with four different options, do the following if the current macOS on the computer isn’t Catalina but one that is older. If your current macOS is Catalina, skip steps 4 to 7 and go directly to step 8.
  4. Select Disk Utility and then click on Continue.
  5. Click on the View icon from the top and select Show All Devices (like you did in one of the earlier steps).
  6. In the left panel, select the drive on which the current macOS is installed (should be the one shown at the top).
  7. Next, click on Erase, make sure that the format is set to APFS, and select Erase.
    • Important!: this action will erase everything on the selected hard drive, so it is important to have previously backed up data you wouldn’t want to lose. If you haven’t done that, restart your Mac, back up your data, and then erase the drive.
  8. Once the drive is erased, go back to the screen with four options, select Install macOS Big Sur, and click Continue, and then Continue again.
  9. Agree to the Terms and Conditions, on the next page, select the drive on which you’d like Big Sur to be installed, and select Continue. This will begin the installation of Big Sur and, again, depending on a number of factors, this process could anywhere between 45 minutes to 3 hours (or more).

Mac Os Catalina

Patiently wait for the installation to complete and once your Mac starts again, you will have Big Sur installed onto it. If you have performed a fresh install of Big Sur (if you’ve first erased your previous OS, you will have to go through several normal setup steps that are very easy to complete).

Installing Necessary Patches

Mac Os Big Sur Unsupported Mac Github

The last phase of the Big Sur installation is to install several important patches to make your Mac function properly.

Download Mac Os Big Sur On Unsupported Imac

  1. Once the computer starts after the Big Sur installation, and you complete any required setup steps (in case you’ve performed a fresh install of the OS), open the icon of the bootable USB drive.
  2. Open the Patched Sur app and select the Patch Kexts.
  3. Click Continue, enter your password and click on Continue again.
  4. Once the patches are installed, the app will ask you to restart your Mac, so click on the Restart to Finish option and wait for the computer to restart.
  5. If your Mac is a very old one, one thing that could help it run smoother is to go back to the Patcher, select Settings, and click on the Disable Animations option. We also recommend selecting the Clean Leftovers button to get rid of any unnecessary files and free up some space on the computer.

Once this is finished, your Mac will be ready for use with the macOS Big Sur installed on it. If you have any questions, do not hesitate to ask them in the comments section below.