Install Macos 11 Big Sur On Unsupported Macs

Update V11 5 1 Install Macos Big Sur On Unsupported Macs Full Tutorial Macbook Imac Macpro, Which is the best-Notch Music Download Internet websites? There are numerous web pages where by you can get on the net music without the need of spending, although other web pages present the most effective music streaming products and services. And, higher than talked about Internet sites permits you to hit music totally free download. Update V11 5 1 Install Macos Big Sur On Unsupported Macs Full Tutorial Macbook Imac Macpro

UPDATED TUTORIAL FOR 11.5.1: How to install the brand new Apple MacOS 'Big Sur' on older, officially unsupported Apple Hardware like the still very powerful...

However, there are ways to install macOS Big Sur at least on some of the unsupported Macs like the mid-2012 or the early-2013 MacBook Pro. MacOS Big Sur Supported Models Apple MacBook 2015 and later.

All you guys asking if this works on you machine - please check the compatibility lists at Barry‘s guide first: ...

Big-sur-micropatcher (Version 0.5.1) A primitive USB patcher for installing macOS Big Sur on unsupported Macs. By the way, if you have a Mac Pro, Big Mac by StarPlayrX is another patcher worth considering. Attempting to install Catalina on an unsupported Mac is in no way supported by Apple, and you are doing so at your own risk. MacRumors cannot be held liable for any data loss or damage as a result. Dec 10, 2020 How to install macOS Big Sur on an old unsupported Mac. Luckily there's a patcher for installing macOS Big Sur on older Macs available - the big-sur-micropatcher can be downloaded from GitHub.

Today I will show you how to Install macOS 11 Big Sur on an Unsupported Mac.To be clear this guide shows you how to install Mac OS Big Sur, it is up to...

Do you want to install macOS Big Sur on your 2012 or 2013 Mac? I will show you the easiest way to do it! This video is a step-by-step tutorial on how to use...

FULL TUTORIAL: How to install the brand new Apple macOS 12 'Monterey' (Beta) or macOS 11 'Big Sur' on older, officially UNSUPPORTED Apple hardware! With...

How To Install Macos Big Sur On Unsupported Mac

With this method, you won't need to create a bootable USB flash drive for every macOS Big Sur update! Once you've installed it once, you will be able to...

In this video, I am going to show you how to install the final version of macOS Big Sur on an Unsupported Mac (2008-2013)Useful links:The patcher's site...

Patched Sur Version 0.1.1 is LIVE! You can now install macOS Updates automatically from the Patched Sur App!!!! If you just used Patched Sur or...

So you just used Patched Sur or Big-Sur-Micropatcher to upgrade your unsupported Mac to Big Sur but how do you update? This video is a step-by-step tutorial...

How To Install Latest Big Sur Version on Unsupported Mac The Simple Way!! IN ONE CLICK!!!2012 MacBook Pro: ebay.us/5HmC6u2011 MacBook Pro: ...

FULL GUIDE: How to update macOS on unsupported Mac hardware with a patched installer, how to update OpenCore Bootloader to it's newest version and test it...

Install macOS Big Sur on your 2008-2013 Unsupported Mac? OpenCore Legacy Patcher supports beta graphics acceleration for 2008-2011 Macs!!!! 2012-2013 Macs...

FULL GUIDE: How to set up OpenCore via its configuration file 'config.plist'! Remove compatibility checks, spoof (fake) different hardware to receive updates...

Link To BenSova's Patcher: github.com/BenSova/Patched-SurHello guys in this video I will be showing you how to install macOS Big Sur on an unsupported...

In this video, I will upgrade a classic Mac Pro 4,1 all the way up to Big Sur. From hardware perspective, I will upgrade the memory, CPU, GPU and install a...

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.

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:

Install
  • 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:

# 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)

# 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:

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.

Mac Mini 2012 Big Sur

# Some kexts may not be compatible with Big Sur yet

Install Macos 11 Big Sur On Unsupported Macs Operating System

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

Install Macos 11 Big Sur On Unsupported Macs 7

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.

How To Install Big Sur On Unsupported Mac

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.

Install Macos 11 Big Sur On Unsupported Macs Version

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:

Comments are closed.