Toggle sidebar Toggle sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

macOS 11 Big Sur on Unsupported Macs Thread

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Mac_tech said:
Do you know if 11.1 works using the micropatcher or patched sur?
Click to expand...
Will update when installed.

Don't see a reason why it wouldn't though. I'm on 11.1 beta build 20C5061b which installed w/o any issues on both macs in my sig, using Barrys micropatcher 0.5.1 .
 
Ausdauersportler said:
I cite @jackluke :

"Anyway I advise to don't use more on BigSur any spoofing opencore setup for OTA updates, because apple especially with ARM might change the EFI SMC "FirmwareUpdate.pkg post script", their "firmware dictionary keys" or csr-active-config or "nvram firmware boot-args" or "plist kernel flags" or Firmware.scap file to crossflash your unsupported BigSur Mac EFI SMC firmware regardless of how much safe is the opencore config.plist made."

Could you please share your config.plist from your OC to check if spoofing is used? I cannot believe you get OTA upgrades without cloaking under an supported board-id.
Click to expand...
Watching a bit from the sideline. Thanks for your well justified words of caution.

I was using @khronokernel 's OpenCore Legacy Patcher 0.0.3 (post #7,336 ) and it spoofed the MBP5,2 to MBP11,2.
In this case the spoofing choice is made programmatically, not static in config.plist. See screenshots.

It found the OTA update but I didn't dare yet to start it.
Will do eventually on my own risk, as this OC patcher is done so well and worth exercising.
 

Attachments

  • Bildschirmfoto 2020-12-14 um 20.01.33.png
    Bildschirmfoto 2020-12-14 um 20.01.33.png
    210.7 KB · Views: 132
  • Bildschirmfoto 2020-12-14 um 20.01.45.png
    Bildschirmfoto 2020-12-14 um 20.01.45.png
    110.4 KB · Views: 133
  • Bildschirmfoto 2020-12-14 um 20.01.56.png
    Bildschirmfoto 2020-12-14 um 20.01.56.png
    131.9 KB · Views: 128
  • Bildschirmfoto 2020-12-14 um 20.03.17.png
    Bildschirmfoto 2020-12-14 um 20.03.17.png
    88.8 KB · Views: 134
Last edited:
  • Like
Reactions: macinfo, webg3 and iMac-iPad
For patcher users I would wait for a bit. This is general advice even for supported Mac users! This is just to make sure no major issues pop up.

Big Sur Micropatcher, BigMac & Patched Sur users - will have to download the full installer and perform an upgrade in place update via usb installer.

OpenCore users - can update using software update at any time.

All the info you will need on the update.
mrmacintosh.com

What’s New in the macOS Big Sur 11.1 Update 20C69? - Mr. Macintosh

What’s New in macOS Big Sur 11.1 (20C6) Update? The update includes new features & fixes + support for AirPods Max headphones & more!
mrmacintosh.com mrmacintosh.com
 
  • Like
Reactions: jazo97, macinfo, Dilli and 5 others
Ausdauersportler said:
I cite @jackluke :

"Anyway I advise to don't use more on BigSur any spoofing opencore setup for OTA updates, because apple especially with ARM might change the EFI SMC "FirmwareUpdate.pkg post script", their "firmware dictionary keys" or csr-active-config or "nvram firmware boot-args" or "plist kernel flags" or Firmware.scap file to crossflash your unsupported BigSur Mac EFI SMC firmware regardless of how much safe is the opencore config.plist made."

Could you please share your config.plist from your OC to check if spoofing is used? I cannot believe you get OTA upgrades without cloaking under an supported board-id.
Click to expand...
Yes I use two config.plist files one with spoofing and one without, both made available by jakeluke right here in this thead.

what I do is to raise the system in the spoff and have the system updated, I follow from the beginning, and when it asks to restart, then I use the micropatcher pendrive, to be able to change the NVRAM.

I follow the update, and after restarting, I change config.plist back to the version without spoof.

Something very simple.


OpenCore is configured to start first, because on the primary partition, it is the first path it reads.
 
hvds said:
Watching a bit from the sideline.
I was using OpenCore Legacy Patcher 0.0.3 (post ) and it spoofed the MBP5,2 to MBP11,2.
In this case the spoofing choice is made programmatically, not static in config.plist. See screenshots.
It found the OTA update but I didn't dare yet to start it.
Click to expand...
Backup your firmware using @dosdude1 romtool and make sure you can flash it using a clip if things going south.

Use at least OC 0.6.4 and configure it as described in the latest Open Core Patcher version 0.0.7

And even then you might enter rough water ...
 
  • Like
Reactions: macinfo, Dilli and hvds
webg3 said:
Yes I use two config.plist files one with spoofing and one without, both made available by jakeluke right here in this thead.

what I do is to raise the system in the spoff and have the system updated, I follow from the beginning, and when it asks to restart, then I use the micropatcher pendrive, to be able to change the NVRAM.

I follow the update, and after restarting, I change config.plist back to the version without spoof.

Something very simple.


OpenCore is configured to start first, because on the primary partition, it is the first path it reads.
Click to expand...
Even this is only working if the download does not try to do nasty things before restarting the Mac the first time.
Has anybody fully analyzed the first stage as of now?

I know the method you are using will work, but I cannot predict the costs coming with it. A simple single success is no proof.
 
  • Like
Reactions: Dilli, webg3 and hvds
Ausdauersportler said:
Backup your firmware using @dosdude1 romtool and make sure you can flash it using a clip if things going south.

Use at least OC 0.6.4 and configure it as described in the latest Open Core Patcher version 0.0.7

And even then you might enter rough water ...
Click to expand...
Thanks, I'll put the precautions in place, but first take time to understand more, before an OTA update with OC.
 
Last edited:
Ausdauersportler said:
Even this is only working if the download does not try to do nasty things before restarting the Mac the first time.
Has anybody fully analyzed the first stage as of now?

I know the method you are using will work, but I cannot predict the costs coming with it. A simple single success is no proof.
Click to expand...
Hm... In science, the saying goes like this:
A single black swan proves the existence of black swans. (Of course, others have to verify it).
;-)
 
  • Like
Reactions: macinfo and Ausdauersportler
Larsvonhier said:
Hm... In science, the saying goes like this:
A single black swan proves the existence of black swans. (Of course, others have to verify it).
;-)
Click to expand...
That is wrong. If you see a single black swan then only this is true:

There exists at least one swan which is black from at least one side.

I just warn people to jump onto that train without having a recovery plan in place.
 
  • Haha
Reactions: Dilli and Larsvonhier
Jack Neill said:
I have tried this on supported Macs, and have found that a clean install, at least with 11.0.1 seemed to work better
Click to expand...
Ok, thanks! I will update Catalina 2020-001 then and do a Time Machine backup and - just to be sure - an additional CCC backup. Then fingers crossed for the clean install and backup restore afterwards. A clean installation of 11.0 worked fine on an external SSD, so I think there will be no problems.
But first I'll wait for a patcher update, heard that Barry's 0.5.2 patcher is on the way?
 
Ausdauersportler said:
Even this is only working if the download does not try to do nasty things before restarting the Mac the first time.
Has anybody fully analyzed the first stage as of now?

I know the method you are using will work, but I cannot predict the costs coming with it. A simple single success is no proof.
Click to expand...

I've been doing this since Beta 8.

If you are not familiar with Terminal, I do not recommend doing some things, we are all here, at least the vast majority, because we know how to use and we are not afraid of the Terminal.
 
  • Like
Reactions: Dilli
hvds said:
Right - webg3 has proven that it can work, others have proven that it can brick...
Click to expand...
Yes, of course. An while you are waiting for a counter proof others brick their macs. Smart move. The only thing we know for sure is it worked for webg3. If this fulfills your need of a proof you better never do math again.
 
  • Like
Reactions: Dilli
ClassicII said:
For patcher users I would wait for a bit. This is general advice even for supported Mac users! This is just to make sure no major issues pop up.

Big Sur Micropatcher, BigMac & Patched Sur users - will have to download the full installer and perform an upgrade in place update via usb installer.

OpenCore users - can update using software update at any time.

All the info you will need on the update.
mrmacintosh.com

What’s New in the macOS Big Sur 11.1 Update 20C69? - Mr. Macintosh

What’s New in macOS Big Sur 11.1 (20C6) Update? The update includes new features & fixes + support for AirPods Max headphones & more!
mrmacintosh.com mrmacintosh.com
Click to expand...

Does this mean that the update will no longer brick the logic board for 2014 MBP 13"?
 
  • Like
Reactions: MrMacintoshBlog and Ausdauersportler
Pri-est said:
My second Bild of old Big Sur installation on Mac Pro 2008.

Mac Pro 3,1 (early 2008)
2xE5462 (QC 2.8)
4x4GB DDR2 5300F
NoNamed SSD 64GB
GTX 680 2GB (Flashed Mac EFI)

Installed by create partition on Hard Drive and creating install media, patching by Micropatcher and Jacklukem USB fixes 1 and 2.
After installation process, perform BigMac postinstall from MacOS Catalina and USB legacy patch from BigSurFixes Menu from Recovery mode (install media).
All work good!
Not opencored.
P.S. Old 2005 Bluetooth card should be removed.
Click to expand...
Hi, if I understand correctly, you used two different tutorials for the installation, the first step with Micropatcher and the second step with BigMac postinstall, right?
Thanks for your help
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back