macOS 11 Big Sur on Unsupported Macs Thread

[Underbeat88]

Hello,
I have installed the big sur on an iMAC late 2010. Everithing works except the ethernet LAN Card. The BCM5701 driver, so i guess, is not right installed. So far usualy is this firmware in the AppleBCM5701Ethernet.kext somewhere in the /S/L/E folder... But this folder is write protected now. So my question is, is it possible to inect this driver with the opencore bootloader, too? Or is it necessary to install the System new?

I also did not find a way to install kexts, I have already tried all the options, but nothing helps ((( remount-sysvol.sh did not help either, maybe I missed something, but I did not succeed.

 

[Bustycat]

For those who are using OpenCore to spoof the Mac's indent in order to get Big Sur support.

I have a suggestion to avoid unintentional BootROM update (if both run-efi-updater=No and BlacklistAppleUpdate=true failed).

Rather than use actual BootROM version, manually inject 999.0.0.0.0 in the config plist.

This won't do anything damaging to your Mac. Your Mac still use the current (and actual) BootROM.

However, once booted to macOS, macOS will "believe" that the Mac already has BootROM version 999.0.0.0.0.

So, let's say, Big Sur 11.2 official release contain a BootROM update for the Mac ident that you are spoofing (e.g. version number 430.0.0.0.0).

Since 999.0.0.0.0 is already higher than 430.0.0.0.0. Therefore, the installer / updater will automatically skip the BootROM update. Therefore, even both run-efi-updater=No and BlacklistAppleUpdate=true failed, your Mac should be still protected.

If you have tried and it worked well, you should report this article to the authors of OpenCore Legacy Patcher. It is not easy for people to add the string of BIOSVersion as it is not included by default.

 

[Bustycat]

Hello,
I have installed the big sur on an iMAC late 2010. Everithing works except the ethernet LAN Card. The BCM5701 driver, so i guess, is not right installed. So far usualy is this firmware in the AppleBCM5701Ethernet.kext somewhere in the /S/L/E folder... But this folder is write protected now. So my question is, is it possible to inect this driver with the opencore bootloader, too? Or is it necessary to install the System new?

For OpenCore you have to place kexts into /EFI/OC/Kexts and add them to your config.plist, but I don’t know if those kexts would work with OpenCore. Besides, OpenCore provides another kext for your ethernet:

Fixing Ethernet | OpenCore For Legacy Macs

 

[chrisx78]

I have it dry to mount the EFI with the opencore cofigurator and add the kexts in the Folder but it will not work. Is the a possibility to debug the initial run of opencore?

 

[Bustycat]

I have it dry to mount the EFI with the opencore cofigurator and add the kexts in the Folder but it will not work. Is the a possibility to debug the initial run of opencore?

You have to mention kexts in config.plist too. You should also try CatalinaBCM5701Ethernet that the link mentions.

 

[h9826790]

If you have tried and it worked well, you should report this article to the authors of OpenCore Legacy Patcher. It is not easy for people to add the string of BIOSVersion as it is not included by default.

I am not a Macbook user, but a Mac Pro 5,1 user (the very first batch users that using OpenCore to bypass some Apple's artificial lock). Therefore, I don't need to use OpenCore Legacy Patcher.

I also use OpenCore on my Hackintosh.

Therefore, I don't have any Macbook to test if this can work.

However, I really can't see why this won't work. The BootROM update logic is really very straight forward. It only proceed if the current BootROM version is older than the one that contain in the installer / updater.

Also, as mentioned, this won't do any harm. It won't really affect the Mac's BootROM, but just make macOS believe (and display) the injected BootROM version. At least, there is no risk of bricking the Mac.

Anyway, it's very easy to add BootROM version.

1) Mount the EFI partition

2) locate the config.plist inside EFI/EFI/OC

3) Open it by TextEdit

4) Serach <key>SMBIOS</key>

5) add the following code below <dict>

<key>BIOSVersion</key>
<string>999.0.0.0.0</string>

It should looks like this after the mod

6) save changes and reboot

 

[Bustycat]

I am not a Macbook user, but a Mac Pro 5,1 user (the very first batch users that using OpenCore to bypass some Apple's artificial lock). Therefore, I don't need to use OpenCore Legacy Patcher.

I also use OpenCore on my Hackintosh.

Therefore, I don't have any Macbook to test if this can work.

However, I really can't see why this won't work. The BootROM update logic is really very straight forward. It only proceed if the current BootROM version is older than the one that contain in the installer / updater.

Also, as mentioned, this won't do any harm. It won't really affect the Mac's BootROM, but just make macOS believe (and display) the injected BootROM version. At least, there is no risk of bricking the Mac.

Anyway, it's very easy to add BootROM version.

1) Mount the EFI partition

2) locate the config.plist inside EFI/EFI/OC

3) Open it by TextEdit

4) Serach <key>SMBIOS</key>

5) add the following code below <dict>

<key>BIOSVersion</key>
<string>999.0.0.0.0</string>

It should looks like this after the mod
View attachment 1699268
6) save changes and reboot

So OpenCore Legacy Patcher has to add the section of SMBIOS too. config.plist generated by it uses Generic only.

 

[Ausdauersportler]

Hello,
I have installed the big sur on an iMAC late 2010. Everithing works except the ethernet LAN Card. The BCM5701 driver, so i guess, is not right installed. So far usualy is this firmware in the AppleBCM5701Ethernet.kext somewhere in the /S/L/E folder... But this folder is write protected now. So my question is, is it possible to inect this driver with the opencore bootloader, too? Or is it necessary to install the System new?

For exactly this reason I still recommend my iMac fork of the micro patcher for iMac Late 2009 to Mid 2011.

 

[Khadam]

Hello!

I have a problem while installing Big Sur using micropatcher on my iMac Mid 2011 21,5. No, I am not talking about metal related issues because I have upgraded it's video card, with custom vBios, the thing worked with Catalina no problem. The issue I'm having is...weird. While installing macOS BigSur with patched bootable USB, after some time there is that part of installation in which iMac reboots couple of times to finish doing it's stuff. But, after iMac reboots, the screen is dead black but iMac is still running, doing it's thing. At one point reboots stop, the fans are still spining (i have SSD so no thermal sensor for me) but iMac is cool to the touch but no image whatsoever. Nothing changes after turning iMac off and on, only blackness.

B U T

If I hold option key and boot to boot menu and then choose Macintosh HD drive (the one with BigSur) eveything works fine. Screen is bright, colors are vibrant it's just perfect. But after rebooting again (without option key) - blackness again. Pulling out Bootable USB? Doesn't work. Installing kexts form modified BigSur USB? Nothing. Reseting Nvram, SNC, praying to late Steve Jobs, dancing?
N O T H I N G

What the heck is going on?

 

[slim0287]

I used the micropatcher to upgrade my late 2013 iMac 14,2 to macOS Big Sur 11.1 recently. It worked great but I have odd behavior with Spotlight. I use Spotlight to search for something and I get no results. Then I click on the desktop to make Spotlight go away, I click on the Spotlight icon again, and boom- the Spotlight search window re-appears with all the results. So, Spotlight still works, but it has this strange and annoying behavior of essentially not operating "in real time."

I have re-indexed Spotlight just in case that would help and it didn't change the behavior.

This is the only issue I've had with the upgrade. Anyone have insight either with it being a known problem or how to address it?

Thanks

 

[MacHacJac]

Yes!

 

[h9826790]

I used the micropatcher to upgrade my late 2013 iMac 14,2 to macOS Big Sur 11.1 recently. It worked great but I have odd behavior with Spotlight. I use Spotlight to search for something and I get no results. Then I click on the desktop to make Spotlight go away, I click on the Spotlight icon again, and boom- the Spotlight search window re-appears with all the results. So, Spotlight still works, but it has this strange and annoying behavior of essentially not operating "in real time."

I have re-indexed Spotlight just in case that would help and it didn't change the behavior.

This is the only issue I've had with the upgrade. Anyone have insight either with it being a known problem or how to address it?

Thanks

This should be Big Sur issue, not patcher, or Mac model related.

 

[MrMacintoshBlog]

I am not a Macbook user, but a Mac Pro 5,1 user (the very first batch users that using OpenCore to bypass some Apple's artificial lock). Therefore, I don't need to use OpenCore Legacy Patcher.

I also use OpenCore on my Hackintosh.

Therefore, I don't have any Macbook to test if this can work.

However, I really can't see why this won't work. The BootROM update logic is really very straight forward. It only proceed if the current BootROM version is older than the one that contain in the installer / updater.

Also, as mentioned, this won't do any harm. It won't really affect the Mac's BootROM, but just make macOS believe (and display) the injected BootROM version. At least, there is no risk of bricking the Mac.

Anyway, it's very easy to add BootROM version.

1) Mount the EFI partition

2) locate the config.plist inside EFI/EFI/OC

3) Open it by TextEdit

4) Serach <key>SMBIOS</key>

5) add the following code below <dict>

<key>BIOSVersion</key>
<string>999.0.0.0.0</string>

It should looks like this after the mod
View attachment 1699268
6) save changes and reboot

Again this is great, but please submit to https://github.com/dortania/Opencore-Legacy-Patcher/pulls or https://github.com/dortania/Opencore-Legacy-Patcher/issues so this could be evaluated.

 

[MacHacJac]

One more question:
how can I display string outputs of shell scripts within my obj-c app? I have them showing up in the log, but that's it.

 

[Rob1n]

Hi!
I'm a bit lost with all these different options for getting Big Sur installed on an unsupported machine.
Does anyone know what the simplest and most stable option is?
Patched Sur seems great but I don't know if it is stable enough.
I have a MacBook Pro 15 inch 2011 with the dedicated gpu disabled and a Mac Pro 2008 with a metal (flashed to apple rom) gpu installed.
Thanks in advance!

 

[bcdc13]

Can anyone offer suggestions on getting BS 11.1 installed on a 2010 upgraded iMac. I've followed the directions to use the micropatcher fork customized for these systems, but once I have it booted up the installer screen never appears. I just stall out with a grey screen and a mouse pointer. Ideas?

 

[MacHacJac]

Hi!
I'm a bit lost with all these different options for getting Big Sur installed on an unsupported machine.
Does anyone know what the simplest and most stable option is?
Patched Sur seems great but I don't know if it is stable enough.
I have a MacBook Pro 15 inch 2011 with the dedicated gpu disabled and a Mac Pro 2008 with a metal (flashed to apple rom) gpu installed.
Thanks in advance!

Patched Sur is best unless you know terminal well. If so, BarryKN patcher.

 

[MacHacJac]

One more question:
how can I display string outputs of shell scripts within my obj-c app? I have them showing up in the log, but that's it.

Any solutions?

 

[fshortt]

Hi guys,
Having issues with the EFI boot... when I try to boot from it and install Big Sur, Screen goes black and machine is turned off.... can't figure out why...

I followed all the steps, to the letter, so not sure why this is happening should I try without "install-setvars.sh"?

I am on:
iMac (27-inch, Late 2012)
Processor 3.4 GHz Quad-Core Intel Core i7
Memory 16 GB 1600 MHz DDR3
Graphics NVIDIA GeForce GTX 680MX 2 GB

Running latest Catalina 10.15.7

Any suggestions? Thanks in advance!

fshortt

 

[mwidjaya]

I followed all the steps, to the letter

Using micropatcher?

If so, that is correct behaviour.

Step 9...Start up from "EFI Boot". Within a few seconds, although most likely in under a second, the Mac will suddenly power down. This indicates that the setvars EFI utility has finished ....

Step 10 Turn the Mac back on (or reboot it if you skipped step 9), with the Option key down again, to use the Startup Selector again. This time, boot from "Install macOS Big Sur Beta" (or similar)...

 

[zorropapa31]

EDIT: I wanted to edit this and mention that I am using a compatible Bluetooth/wifi card.

Hello everyone! Iv got a question. On my Mac Pro 4,1 flashed to 5,1, ever since high Sierra I would have to run this in order for handoff and continuity and unlock with Apple Watch to work right.
sudo mount -uw /

sudo /usr/libexec/PlistBuddy -c "Set:Mac-F221BEC8:ContinuitySupport true" "/System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist"

sudo -E perl -pi -e "s/\Mac-00BE6ED71E35EB86/\Mac-F221BEC8\0\0\0\0\0\0\0\0/" /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext/Contents/MacOS/AirPortBrcm4360

sudo touch /Library/Extensions

sudo kextcache -i /

But I can't run those commands on Big Sur. Mainly because it says the plugin for the airportbrcm4360 doesn't exist.

So, what iv been doing is installing Catalina first. Then running those commands to get handoff and everything working and then just updated to a version of Big Sur.

I ran into a new problem. The latest version of Big Sur breaks this.

My question is is how is everyone else with a Mac Pro 4,1 or 5,1 getting this to work.

THANK YOU for any help it is much appreciated

Any news or solution? Catalina's IO80211Family.kext has AirPortBrcm4360.kext i copied to plugins folder, mount -uw / command doesn't work:

mount_apfs: volume could not be mounted: Permission denied

mount: / failed with 66

 

[Ausdauersportler]

Any news or solution? Catalina's IO80211Family.kext has AirPortBrcm4360.kext i copied to plugins folder, mount -uw / command doesn't work:

mount_apfs: volume could not be mounted: Permission denied

mount: / failed with 66

Read the first post and the three lines of text about the first patcher option.

 

[leventozler]

Thanks for your information. I also have a late 2013 27-inch iMac with Big Sur 11.0.1 that works great, looking like a new Mac whit M1 CPU... and I'd like to ask if it's worth upgrading to Big Sur 11.1. What has improved 11.1 version to the point that it is worth updating? Or do you think that since I haven't updated and I still have 11.0.1 it's better to wait for 11.2? Thanks! I think an answer will serve many others.

I tried resetting 'energy saver' panel, and no more network problems.

Big Sur works incredible (I have 16 MBP and 2013 late iMac), the only 'bug' I have is volume icon in taskbar showed headphone icon in 11.0.1, and it doesn't show it anymore in 11.1. That's it.

 

[zorropapa31]

Read the first post and the three lines of text about the first patcher option.

Finally done, I copied AirportBrcm4360.kext to IO80211Family.kext's Contents/PlugIns folder, but now no wifi... i rebuilded kc. Anybody has working handoff with Big Sur 5,1 cMP?

 

[Arnoldso]

For those who are using OpenCore to spoof the Mac's indent in order to get Big Sur support.

I have a suggestion to avoid unintentional BootROM update (if both run-efi-updater=No and BlacklistAppleUpdate=true failed).

Rather than use actual BootROM version, manually inject 999.0.0.0.0 in the config plist.

This won't do anything damaging to your Mac. Your Mac still use the current (and actual) BootROM.

However, once booted to macOS, macOS will "believe" that the Mac already has BootROM version 999.0.0.0.0.

So, let's say, Big Sur 11.2 official release contain a BootROM update for the Mac ident that you are spoofing (e.g. version number 430.0.0.0.0).

Since 999.0.0.0.0 is already higher than 430.0.0.0.0. Therefore, the installer / updater will automatically skip the BootROM update. Therefore, even both run-efi-updater=No and BlacklistAppleUpdate=true failed, your Mac should be still protected.

It works.....!!!, I mod config.plist to use SMBIOS Info instead of Generic Data, reinstalled 11.1 and bypass correctly the EFI Update at MBP Mid 2012.