macOS 11 Big Sur on Unsupported Macs Thread

[tennisproha]

Firmware in your mini says 9999.xxxx (maxed out) because of earlier OCLP spoofing method of faking to a newer mini (let's say 2014 mini) so that later macOS can be installed/ran.

To prevent Big Sur from updating the firmware on 2012 mini incorrectly, the version is maxed out to block any update.

By updating to current OCLP version, it uses spoof-less (hiding behind VM install), can present as true 2012 mini so no need to set firmware version to 9999.xxxx.

- update to OCLP 0.4.2
- run SilentKnight again to check firmware version (it should show true version instead of 9999.xxxx)
- may not need to reinstall Big Sur over the top but do that if macOS not working well

Catalina still gets Security Updates once in a long while. If there is a firmware update, it is bundled in there. Applying the security updates will also apply the firmware update.

- prepare a Catalina USB installer
- prepare a partition (50GB) to install it to
- reboot, hit spacebar at show picker, reset NVRAM (bypass OCLP)
- option reboot to select Catalina USB installer
- install Catalina, boot into it, run all software updates
- run SilentKnight to confirm firmware updated

- option reboot, select OCLP EFI boot
- CTRL select Big Sur to boot back into OCLP Big Sur


Need root patching (post install) to use HD4000 graphics acceleration. Breaks SSV and SIP but it is not really a big concern if you do it. Keeping SIP enabled is overrated.

Thanks for this breakdown. That makes sense. I thought I saved the firmware info somewhere but can't find it now. I don't have time to do this now but I'll try to do it by next weekend and report back. Only do this stuff once in a blue moon so I always forget the steps; and then it takes me a while!

 

[K two]

Firmware in your mini says 9999.xxxx (maxed out) because of earlier OCLP spoofing method of faking to a newer mini (let's say 2014 mini) so that later macOS can be installed/ran.

To prevent Big Sur from updating the firmware on 2012 mini incorrectly, the version is maxed out to block any update.

By updating to current OCLP version, it uses spoof-less (hiding behind VM install), can present as true 2012 mini so no need to set firmware version to 9999.xxxx.

- update to OCLP 0.4.2
- run SilentKnight again to check firmware version (it should show true version instead of 9999.xxxx)
- may not need to reinstall Big Sur over the top but do that if macOS not working well

Catalina still gets Security Updates once in a long while. If there is a firmware update, it is bundled in there. Applying the security updates will also apply the firmware update.

- prepare a Catalina USB installer
- prepare a partition (50GB) to install it to
- reboot, hit spacebar at show picker, reset NVRAM (bypass OCLP)
- option reboot to select Catalina USB installer
- install Catalina, boot into it, run all software updates
- run SilentKnight to confirm firmware updated

- option reboot, select OCLP EFI boot
- CTRL select Big Sur to boot back into OCLP Big Sur


Need root patching (post install) to use HD4000 graphics acceleration. Breaks SSV and SIP but it is not really a big concern if you do it. Keeping SIP enabled is overrated.

No offence but wouldn't this info be more relevent on the Catalina on Unsupported Macs thread, also Dortania does not yet endorse doing this in writing and will get a terse reply from the founders if questioned. There are some bugs which should be mentioned, as well. And as usual, Metal works best. https://github.com/dortania/OpenCore-Legacy-Patcher#readme see -

"Note 2: Currently OpenCore Legacy Patcher officially supports patching to run macOS Big Sur and Monterey installs. For older OSes, OpenCore may function however support is currently not provided from Dortania.

• For macOS Mojave and Catalina support, we recommend the use of dosdude1's patchers "
• OCLP boots dosdude1 MacOS installs, perfectly, btw.

 

[mwidjaya]

No offence but wouldn't this info be more relevent on the Catalina on Unsupported Macs thread

It is the method applicable to Big Sur on unsupported Mac, for updating firmware. So it belongs here.


PS: Swap some OS names out, it is also applicable method to Monterey on unsupported Mac.

 

[TimothyR734]

Successfully installed macOS Big Sur 11.6.6 RC1 didn't need to reapply the root-volume patches

 

[Lady Titan]

Hi all! help install big sur, on imac 2011 with a gtx880m video chip, is there a step-by-step instruction or video instruction on how to do this easily and not forcibly?

I am currently using catalina.

 

[makra]

Just a little hint...

 

[MBAir2010]

Hi all! help install big sur, on imac 2011 with a gtx880m video chip, is there a step-by-step instruction or video instruction on how to do this easily and not forcibly?

I am currently using catalina.

this link helped me from page 479 on this thread

then i chickened out or could not find BigSur to download.
there is a great video on that youtube thing that explained in detail how to install monterry
i might do that then install Mojave along with that

on our Mojave thread, someone advised using this link as well.

i know the way to install Mojave an catalina was much easier and used terms we understand.

good luck and let us know how this proceeded.

 

[makra]

Hi all! help install big sur, on imac 2011 with a gtx880m video chip, is there a step-by-step instruction or video instruction on how to do this easily and not forcibly?

I am currently using catalina.

Really: Read the first post thoroughly. That will get you to the OpenCore Legacy Patcher site. There's a step by step introduction. The software is great, but you need to understand the concept, that differs very much from Catalina Patcher.

 

[mogaleksej]

Mac OS 11.6.5 OCLP 0.4.3 it takes about 20 seconds from turning on to the appearance of the Apple logo ! Tell me what I configured incorrectly in OCLP ...

 

[K two]

This lowly Apple refurb unsupported 13 year-old Mini3,1 is the daily driver at this location w/OCLP_044N. Within the limits imposed by non-Metal hardware overall performance is truly impressive far better than expected.

 

[hvds]

This lowly Apple refurb unsupported 13 year-old Mini3,1 is the daily driver at this location w/OCLP_044N. Within the limits imposed by non-Metal hardware overall performance is truly impressive far better than expected.

View attachment 1987651

Very true! Also here on MBP5,2 (mid 2009) 11.6.6RC, with OCLP 0.4.4n, runs very well.

Installed it on an external testing SSD. Connected to a USB3 port on expresscard, not noticeably slower than the internal SATA SSD.

 

[TimothyR734]

This little tool could be handy https://github.com/mikebeaton/BootHelperPkg

 

[madvinegar]

In an iMac 2011 I updated the Cpu to i7-2600s and the Gpu to Nvidia K2100m.
Then used OCLP to update the system to Big Sur.

I install intel power gadget, it installs fine but when I open it, the terminal opens instead, showing an error.

Does this have anything to do that I updated the cpu to i7 2600s?
Or that I updated the gpu to k2100m?
Or is there any setting in opencore that I should change...?

 

[A4orce84]

Hey Everyone,

I have a 2012 Mac Mini that I patched using DosDude1's patch early on to Big Sur 11.1. I recently plugged the mac mini back in and fired it up and was curious what is the process for me to update to the latest Big Sur release that came out before MacOS Monterey?

I just want to make sure I'm using the latest MacOS (Big Sur) on my machine since I'm planning on using it semi-regularly again.

Any help would be greatly appreciated. Thanks!

 

[TimothyR734]

Hey Everyone,

I have a 2012 Mac Mini that I patched using DosDude1's patch early on to Big Sur 11.1. I recently plugged the mac mini back in and fired it up and was curious what is the process for me to update to the latest Big Sur release that came out before MacOS Monterey?

I just want to make sure I'm using the latest MacOS (Big Sur) on my machine since I'm planning on using it semi-regularly again.

Any help would be greatly appreciated. Thanks!

Go to the first page of this thread and scroll down to OpenCoreLegacy Patcher you will need a GitHub account to download the Patcher just follow the instructions and you should be fine !

 

[mogaleksej]

After installing the OC LP , the iMac loads 20 seconds before the Apple logo ... tell me where to look for the reason!

 

[makra]

Non-metal and catalyst: I've tried 0.4.4N on two machines (MPB 6,2 and 8,1). No issues and the 1200s-crash has disappeared. 👏

 

[makra]

After installing the OC LP , the iMac loads 20 seconds before the Apple logo ... tell me where to look for the reason!

Set the OC EFI Boot as default boot entry:

Booting OpenCore and macOS | OpenCore Legacy Patcher

 

[mogaleksej]

Set the OC EFI Boot as default boot entry:

Booting OpenCore and macOS | OpenCore Legacy Patcher

Thanks for the advice! But that 's what I always do ... but the result is the same

 

[madvinegar]

In an iMac 2011 I updated the Cpu to i7-2600s and the Gpu to Nvidia K2100m.
Then used OCLP to update the system to Big Sur.

I install intel power gadget, it installs fine but when I open it, the terminal opens instead, showing an error.

Does this have anything to do that I updated the cpu to i7 2600s?
Or that I updated the gpu to k2100m?
Or is there any setting in opencore that I should change...?

Any ideas on this? Is intel power gadget working in your unsupported macs updated to big sur?

 

[Bmju]

Any ideas on this? Is intel power gadget working in your unsupported macs updated to big sur?

Intel Power Gadget works on my unsupported MBP10,2 running Big Sur. It should just work. (It should definitely cope with an upgraded processor.) Maybe post the error here?

 

[madvinegar]

Intel Power Gadget works on my unsupported MBP10,2 running Big Sur. It should just work. (It should definitely cope with an upgraded processor.) Maybe post the error here?

Thank you for your reply.
Here you go:

 

[Bmju]

Thank you for your reply.
Here you go:

Hmm. It's news to me. This is from starting the app normally (double-click in Applications folder), right?

I definitely believe the app should work fine on your machine. As I'm sure you've already tried too, Google doesn't seem to throw up much. Apart from the obvious (remove app, clean reinstall) I don't have much more to offer, sorry. :-(

 

[madvinegar]

Hmm. It's news to me. This is from starting the app normally (double-click in Applications folder), right?

I definitely believe the app should work fine on your machine. As I'm sure you've already tried too, Google doesn't seem to throw up much. Apart from the obvious (remove app, clean reinstall) I don't have much more to offer, sorry. :-(

It was working fine in high sierra i.e. before I upgraded to Big Sur using OCLP. This is why I suspect that there must be a setting in opencore that is causing this.

 

[Bmju]

It was working fine in high sierra i.e. before I upgraded to Big Sur using OCLP. This is why I suspect that there must be a setting in opencore that is causing this.

I think your machine can run Big Sur without OpenCore. If I'm reading this post by @Ausdauersportler correctly, it would be without sound or ethernet, but still running.

To boot without OC you need to boot into Recovery, run sudo nvram boot-args="-no_compat_check" from the Terminal, then reboot your Mac, hold down ALT during boot to get the native Apple bootpicker, and select macOS directly. This will boot into macOS without OC, to let you check the theory. (I'm still pretty sure the theory is wrong, OC doesn't change anything relevant to this.)

To get back to booting via OpenCore, probably your machine will do so automatically when you reboot again, but if it does not, simply reboot your Mac again, hold down ALT to get the native Apple bootpicker, and then select OpenCore while CTRL is held down to make it the persistent default boot option.