Sidebar 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.
Ausdauersportler said:
You can do my a favour and post back the result of this command from the terminal on your stock iMac 12,1:

Code: 
/usr/sbin/system_profiler SPDisplaysDataType | fgrep "Device ID" | awk '{print $3}
Click to expand...
On a base 21" mid-2011 iMac 12,1 with stock configuration other than double the RAM running latest High Sierra stock when I run that command in the terminal I get the output:
Code: 
0x6741

Screen Shot 2020-12-14 at 8.58.58 am.png


Hope this helps (yes, I am still using a background on this machine from an older version of Mac OS X).
 
Last edited:
  • Like
Reactions: Ausdauersportler
Hello friends

I just looked at the Big Sur Patcher 0.0.4 (is 22 days old) from Mr. Macintosh (also the Youtube video from Mr. Macintosh his Big Sur Patcher 0.0.4) and compared it with the Micropatcher 0.5.1 from Barry K.

What do you mean, which one is better now?

The Big Sur Patcher 0.0.4 from Mr. Macintosh works without recovery mode and you don't need to go into the terminal, everything is done from the graphical interface in Big Sur (I mean the subsequent kexte patching).

Is this Big Sur Patcher 0.0.4 now also compatible for RC and other Big Sur builds? I like that you don't have to boot into recovery mode to go to the terminal
to patch the texts.

The result is the same for both Big Sur patchers. Big Sur also runs unsupported Macs, which is the goal.
 
Pinarek said:
Hello friends

I just looked at the Big Sur Patcher 0.0.4 (is 22 days old) from Mr. Macintosh (also the Youtube video from Mr. Macintosh his Big Sur Patcher 0.0.4) and compared it with the Micropatcher 0.5.1 from Barry K.

What do you mean, which one is better now?

The Big Sur Patcher 0.0.4 from Mr. Macintosh works without recovery mode and you don't need to go into the terminal, everything is done from the graphical interface in Big Sur (I mean the subsequent kexte patching).

Is this Big Sur Patcher 0.0.4 now also compatible for RC and other Big Sur builds? I like that you don't have to boot into recovery mode to go to the terminal
to patch the texts.

The result is the same for both Big Sur patchers. Big Sur also runs unsupported Macs, which is the goal.
Click to expand...
Just to be clear, Big Sur Patcher 0.0.4 is BenSova's work, not Mr. Macintosh (who did the YouTube video). Ben's patcher is a graphical interface that currently uses Barry KN's micropatcher 0.5.1, but will use 0.5.2 when Barry publishes it. Both methods (BenSova and BarryKN) get you to the same installation.

Also, Ben's Big Sur Patcher has the same constraints we all have on needing to use a released form of Big Sur -- duh! So, currently, it cannot install Big Sur 11.1 (20C69). Let us hope that changes real soon!
 
  • Like
Reactions: macinfo, Quackers and Pinarek
Thanks for the explanation of the patcher manufacturer.
I assumed that Mr. Macintosh did it, but it doesn't matter as long as it works.
Do you mean if Micropatcher 0.5.2 comes with a graphical GUI? that would be good.

As I have read everywhere on the net, there will be no full installer for RC 20C69. Do we have to wait for the next update and hope that there will be a full installer. With my Hackintosh it's not a problem because the updates come when you activate SIP then just load the update and install it over it and you're done.
 
Pinarek said:
Thanks for the explanation of the patcher manufacturer.
I assumed that Mr. Macintosh did it, but it doesn't matter as long as it works.
Do you mean if Micropatcher 0.5.2 comes with a graphical GUI? that would be good.

As I have read everywhere on the net, there will be no full installer for RC 20C69. Do we have to wait for the next update and hope that there will be a full installer. With my Hackintosh it's not a problem because the updates come when you activate SIP then just load the update and install it over it and you're done.
Click to expand...
No, Barry's Micropatchers have always been shell scripts that you run via Terminal. AFAIK, he has no plans to put them into a GUI. However, BenSova uses Barry's micropatcher so in a way they will be applied via Ben's GUI.

Regarding 0.5.2, BenSova explains in his description of v 0.0.4: "Patched Sur now uses a dynamic micropatcher version, so I can tell it to use v0.5.2 instead of v0.5.1 when it comes out without having to publish a new release of Patched Sur."

As you correctly said above, many are predicting "there will be no full installer for final release 20C69," or beyond for that matter. Let us hope they are wrong.
 
  • Like
Reactions: Fangio, olad, hvds and 3 others
Anyone got the Open Core Legacy Patcher working on a MBP 9,2? I got it working perfectly on my MBA 5,2 but it can't get the SMBIOS to spoof to 11,1 correctly because it either always boots to internet recovery or says its on a not supported platform.
 
  • Like
Reactions: naylom11 and WT_
Hello, guys! I have some problem. After installation big sur micropatcher by Barrykn (ver. 0.5.1) I loose possibility to boot windows from Alt menu. It helps me reset NVRAM to boot windows as default, but it for time, not long, I think. Also Windows starts only from 3-4 time (till recovery windows menu after 2 hard switch off by power button of my mac). It happens only when windows default, without Alt menu with choosing boot partition (efi)
Ok, no more words and complaints, I atteched video with my issue. Thanks all who helps!

 
  • Like
Reactions: macinfo
buckrock said:
Some think the final candidate release date will be Monday, Dec 14, 2020 to coincide with the release of Fitness+ which requires BS 11.1. Others have predicted that Apple is moving away from installassistant.pkg favoring OTA updates, so we'll just need to wait ... and enjoy 11.0.1!
Click to expand...
could someone provide direct download Link to latest update, seems the full installer 11.26GB is there, so I see it on my developer software update, but unfortunately I can't update it:(


 
Last edited:
tnsbgs said:
could someone provide direct download Link to latest update, seems the full installer 11.26GB is there, so I see it on my developer software update, but unfortunately I can't update it:(


Click to expand...
First of all OTA updates will not work for unsupported macs. So please wait for the pkg download link to be posted .
 
  • Like
Reactions: macinfo
Jack Neill said:
Anyone got the Open Core Legacy Patcher working on a MBP 9,2? I got it working perfectly on my MBA 5,2 but it can't get the SMBIOS to spoof to 11,1 correctly because it either always boots to internet recovery or says its on a not supported platform.
Click to expand...
Same here, I believe it has to do with platform spoofing an 11,1 MBP. Which (and I could be mistaken) is one of the models Apple blocked with the 20B50 update... Curious if anyone else has run into this problem or knows a good workaround?

I'm currently using bkn's micropatcher on 20B29, and works great. But I'm experimenting with OpenCore for newer versions
 
Last edited:
  • Like
Reactions: macinfo
naylom11 said:
Same here, I believe it has to do with the platform spoofing an 11,1 MBP. Which (and I could be mistaken) is one of the models Apple blocked with the 20B50 update... Curious if anyone else has run into this problem or knows a good workaround?

I'm currently using bkn's micropatcher on 20B29, and works great. But I'm experimenting with OpenCore for newer versions
Click to expand...
I hadnt thought of that! The open core patcher seems like the way to go if you want OTA's. The MBA 5,2 I spoofed to a 6,2 has been working fantastic.
 
  • Like
Reactions: webg3, macinfo and naylom11
I just installed and removed the BigSurBaseSystemFixes of Jackluke but the apfs boot picker of bigsur fixes has not been deleted. Is there a way to remove it completely because i am running dosdude's catalina patcher.
 
  • Like
Reactions: macinfo
naylom11 said:
Same here, I believe it has to do with platform spoofing an 11,1 MBP. Which (and I could be mistaken) is one of the models Apple blocked with the 20B50 update... Curious if anyone else has run into this problem or knows a good workaround?

I'm currently using bkn's micropatcher on 20B29, and works great. But I'm experimenting with OpenCore for newer versions
Click to expand...
I can confirm. This is exactly the problem. The two workarounds are either installing OC on a 20B29 install, or spoofing a different MBP
 
webg3 said:
It works, you need to configure OpenCore 6.3 on the main system's EFI partition.
Click to expand...
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.
 
  • Like
Reactions: Dilli
Using gibMacOS-master, I saw that InstallAssistant.pkg for 001-86606 - 11.1 macOS Big Sur (20C69) is available now. I'm downloading it now. It's 12.20 GB.

Sorry, I don't know how to link directly to the InstallAssistant.pkg
 
  • Like
Reactions: macinfo
OKonnel said:
I also own an iMac 27'' Late 2013 and I solved the slowness problems by deciding to eliminate the Fusion Drive, open the iMac and replace the mechanical Hard Disk with a 2TB Crucial MX500 SSD.
Now the iMac flies, turns on and login in a matter of seconds and has never gone so well from Maverick to Catalina! :)

Keep in mind that with Micropatcher 0.51 I had first installed Big Sur 11.0.1 on the externally connected SSD and it then worked immediately as soon as I replaced the internal Hard Disk and turned the iMac back on.

Now that the 128GB Apple SSD belonging to the Fusion Drive is indipendent (note: I called it Macintosh SD ;)), I have run some Benchmark and in fact Apple has done well to exclude these iMacs 14,2 from Big Sur, due to the numerous models purchased with Fusion Drive. In fact, the read of Apple internal 128GB SSD is 700MB/sec and the Write 300MB/sec. That's fine as long as the Data does not exceed 128GB; after that, since the Fusion Drive does nothing but move the most used data from the HD to the SSD, everything slows down, ESPECIALLY the Parallels Desktop or the VMWare Fusion Virtual Machines.
Now, however, especially since I put the Parallels Desktop VM with Windows 10 Pro in the Apple internal SSD 128GB, Winzozz startup almost instantaneous while before it took minutes as the Fusion Drive wasted time transferring 25GB of VM to the SSD but NEEDING TO FREE THE SPACE FIRST...
The SSDs and the PCI-Nvme Controller used by iMacs from 2015 onwards, on the other hand, are much more performing.
Click to expand...
Thanks for getting back to me, this is helpful. I passed this on to the person I'm helping on Reddit.
 
Last edited:
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