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:
Wait, wait, wait!

UEFI installation (in contrary to the legacy BIOS installation) used on iMac 2011 models and some other machines does not recognize the installed hardware correctly and so sound is broken.

To fix this you can use an DSDT patch injected through OpenCore. So OpenCore does not cause the sound problems but can be used to fix them. This is slightly off topic, too. There will be surely a "Windows 10 on Macs" thread...
Click to expand...
Not sure if it is UEFI or legacy installation.

Code: 
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI ⁨EFI⁩                     209.7 MB   disk0s1
   2:                 Apple_APFS ⁨Container disk1⁩         200.0 GB   disk0s2
   3:       Microsoft Basic Data ⁨BOOTCAMP⁩                299.9 GB   disk0s3

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +200.0 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume ⁨macOS - 資料⁩            74.3 GB    disk1s1
   2:                APFS Volume ⁨Preboot⁩                 296.3 MB   disk1s2
   3:                APFS Volume ⁨Recovery⁩                613.6 MB   disk1s3
   4:                APFS Volume ⁨VM⁩                      1.1 GB     disk1s4
   5:                APFS Volume ⁨macOS⁩                   15.0 GB    disk1s5
   6:              APFS Snapshot ⁨com.apple.os.update-...⁩ 15.0 GB    disk1s5s1
 
Well,
Ausdauersportler said:
This is absolute ...

@KennyW just wrote down what every company (small or big) is doing if they have a roll our plan for new software. This thread is exactly the foundation to detect and fix errors in the deployment process, find workarounds for things Apple dropped on their own way to new and more modern macOS releases. Using unsupported Macs we cannot rely on the results Apple is producing for their set of supported machines - and even there bugs exist.

Currently there are only a few reasons to migrate from Catalina to Big Sur for people using it as a productive platform, the reasons have been written down.

For my particular family of iMac systems there is the loss of DRM with Big Sur. So I opted to have two systems, one running with latest stable Catalina and Big Sur release, another with the latest beta upgrades included. Before I touch the stable releases I do some manual checks. Real IT companies have compute farms with highly automated test cases running on each new build. We have some technical interested users doing it manually when the developers roll out a new version of the patchers....

Why I do have the latest Beta installed? I just want to know if the deployment process needs some adaptions making sure the patcher will work.
Click to expand...
After all this time reading about how to do it, I tried in my mbp9,2 and really it's better than Catalina. Even the machine its more cooler! That impress me a lot, since always was hot and when I was working in 3D, the fan goes like crazy.

I just made a partition with Catalina (without initalizate... even) and then the Big Sur... "I went with all", like we said in my country... without fear. It's my main machine and everything is working really good. I will going to test some rendering in VRAY.

I tried in the mini5,2 but yeah, even mine has the graphic card but was very laggy, so I left in High Sierra. I will sell that machine in any case.
 
  • Like
Reactions: webg3 and Ausdauersportler
Bustycat said:
Not sure if it is UEFI or legacy installation.

Code: 
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI ⁨EFI⁩                     209.7 MB   disk0s1
   2:                 Apple_APFS ⁨Container disk1⁩         200.0 GB   disk0s2
   3:       Microsoft Basic Data ⁨BOOTCAMP⁩                299.9 GB   disk0s3
Click to expand...

To check for legacy BIOS installation:
Code: 
# look at MBR, does it have more than one partition?
sudo fdisk /dev/disk0

# look at GPT, does it show MBR or PBR (protected boot record which means the GPT disk is not a hybrid GPT/MBR disk)?
sudo gpt -r show -l /dev/disk0

# look at contents of MBR. Does it have lots of non-zero bytes which indicate boot code?
sudo dd if=/dev/disk0 count=1 2> /dev/null | xxd

# look at the contents of the PBR. Does it have lots of non-zero bytes which indicate boot code? Does it mention BOOTMGR which indicates that it wants to load the BOOTMGR file?
sudo dd if=/dev/disk0s3 count=1 2> /dev/null | xxd

# does the BOOTCAMP disk have the legacy boot loader BOOTMGR? This command searches all the mounted disks:
ls -l /Volumes/*/bootmgr
 
vinaypundith said:
I have a Mac Pro 3,1 as well, with the APFS BootROM patch, an EFI flashed GTX 680, an upgraded BCM94360CD wireless card, a PCI Express USB 3.0 card (in case the built in USB won't work with Big Sur) and a Gigabyte Titan Ridge Thunderbolt 3 card. Would love to run Big Sur on it.

- Can you give a brief explanation of how you installed OpenCore on the computer, please? I spent hours searching the Internet but cannot find anything definitive on how to install OpenCore on anything other than a 2010/2012 model Mac Pro 5,1.

- How did you get the installer for Big Sur? I can't seem to find a download anywhere. Can we do an update from Catalina after using OpenCore to spoof the model?

Lastly, does anyone here have any experience with the Gigabyte GC-TITAN-RIDGE Thunderbolt add in card in Mac OS Big Sur?

Thanks in advance.
Click to expand...
Have you tried the 1st page of this thread. It has all the answers. There are some videos too on youtube. May not be fir your model but the guide is similar mostly. You also need to read thee last few 10-12 pages. cheers
 
Dilli said:
Have you tried the 1st page of this thread. It has all the answers. There are some videos too on youtube. May not be fir your model but the guide is similar mostly. You also need to read thee last few 10-12 pages. cheers
Click to expand...

I read through the first page. I'm interested in using OpenCore because I like that it allows for OTA updates without having to keep patching each update. Having OpenCore can also help because I have a Gigabyte Thunderbolt card.

I can find plenty of guides installing OpenCore on a 2010 model Mac Pro 5,1 (more like 2009-2012) but absolutely nothing, nothing else. I was able to successfully install OpenCore using the download and guide at https://create.pro/opencore-catalina-install-guide/ but it is version 0.6.0 or something.

I edited the config.plist file to show BootROM version 999.0.0.0.0 as was shown on page 325 of this thread, to avoid my computer getting screwed up by firmware updates. My computer was running a dosdude patcher modified version of Catalina 10.15.5, and after opencore-ing it I was able to OTA download the Big Sur 11.1 installer but when I tried to run the installer it said "Your Mac needs a firmware update to install to this volume. Please select a volume formatted to Mac OS Extended (Journaled) instead.". My Mac Pro has the APFS BootROM patch from dosdude installed, and it was working great to run Catalina, so what is causing this error?

I tried to update OpenCore to 0.6.5 thinking it might help, but apparently did it wrong and now Catalina won't boot at all. I'm gonna be reinstalling Catalina tomorrow, and will opencore it again, hopefully properly.

How do I install OpenCore 0.6.5 on the Mac Pro 3,1? I downloaded the .release zip file from github and tried replacing the EFI partition contents with the EFI folder from the zip file. That did not work, presumably because it lacked a config.plist file. How do I create it?

Thanks.
 
vinaypundith said:
I read through the first page. I'm interested in using OpenCore because I like that it allows for OTA updates without having to keep patching each update. Having OpenCore can also help because I have a Gigabyte Thunderbolt card.

I can find plenty of guides installing OpenCore on a 2010 model Mac Pro 5,1 (more like 2009-2012) but absolutely nothing, nothing else. I was able to successfully install OpenCore using the download and guide at https://create.pro/opencore-catalina-install-guide/ but it is version 0.6.0 or something.

I edited the config.plist file to show BootROM version 999.0.0.0.0 as was shown on page 325 of this thread, to avoid my computer getting screwed up by firmware updates. My computer was running a dosdude patcher modified version of Catalina 10.15.5, and after opencore-ing it I was able to OTA download the Big Sur 11.1 installer but when I tried to run the installer it said "Your Mac needs a firmware update to install to this volume. Please select a volume formatted to Mac OS Extended (Journaled) instead.". My Mac Pro has the APFS BootROM patch from dosdude installed, and it was working great to run Catalina, so what is causing this error?

I tried to update OpenCore to 0.6.5 thinking it might help, but apparently did it wrong and now Catalina won't boot at all. I'm gonna be reinstalling Catalina tomorrow, and will opencore it again, hopefully properly.

How do I install OpenCore 0.6.5 on the Mac Pro 3,1? I downloaded the .release zip file from github and tried replacing the EFI partition contents with the EFI folder from the zip file. That did not work, presumably because it lacked a config.plist file. How do I create it?

Thanks.
Click to expand...
First read this post about the OLP !

You need a patcher from page #1 to install Big Sur.

You may use OLP to create a shell of a OpenCore installation or you read the OpenCore docs on GitHub and do it yourself.

Because if my first line comment I would strongly advice against using OC for OTA unless your are able to restore a broken firmware on your Mac yourself.
 
Ausdauersportler said:
First read this post about the OLP !

You need a patcher from page #1 to install Big Sur.

You may use OLP to create a shell of a OpenCore installation or you read the OpenCore docs on GitHub and do it yourself.

Because if my first line comment I would strongly advice against using OC for OTA unless your are able to restore a broken firmware on your Mac yourself.
Click to expand...
A possible workaround is generating files by OpenCore Legacy Patcher and then replacing all except config.plist and USB mapping kext with OpenCore 0.6.5. Hence, the patcher can be only used for generating config.plist and a mapping kext now.
 
Bustycat said:
Not sure if it is UEFI or legacy installation.

Code: 
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI ⁨EFI⁩                     209.7 MB   disk0s1
   2:                 Apple_APFS ⁨Container disk1⁩         200.0 GB   disk0s2
   3:       Microsoft Basic Data ⁨BOOTCAMP⁩                299.9 GB   disk0s3

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +200.0 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume ⁨macOS - 資料⁩            74.3 GB    disk1s1
   2:                APFS Volume ⁨Preboot⁩                 296.3 MB   disk1s2
   3:                APFS Volume ⁨Recovery⁩                613.6 MB   disk1s3
   4:                APFS Volume ⁨VM⁩                      1.1 GB     disk1s4
   5:                APFS Volume ⁨macOS⁩                   15.0 GB    disk1s5
   6:              APFS Snapshot ⁨com.apple.os.update-...⁩ 15.0 GB    disk1s5s1
Click to expand...
Opencore legacy installation

But at windows no sound , I don't now how to solve yet
 

Attachments

  • Diskutil.jpg
    Diskutil.jpg
    118.8 KB · Views: 88
  • EFI.jpg
    EFI.jpg
    175 KB · Views: 110
buckrock said:
First, my bluetooth firmware is v150 c9319 on a 15in rMBP mid-2012 running BS 11.1(20C69) with an upgraded 802.11ac Broadcom card installed.

Second, if you migrated preferences back from Big Sur to Catalina there may be some conflicts. I'd recommend creating a new pristine admin-level user and checking how your bluetooth devices work. In fact, this is a great troubleshooting tool and should be part of everyone's arsenal!

Third, you could run Bluetooth Setup Assistant again. There are some settings in Preferences-->Bluetooth-->Advanced... to check. Or perhaps just uncheck/uninstall your Bluetooth devices and rediscover them???
Click to expand...
Hi there

thanks for your reply.

I did a clean install with formatting the new drive.
buckrock said:
No, I don't know how to flash BT firmware. There are lots of folks on this thread who may be able to help.

Since your MBA is supported for 10.15.7, I'd try a reinstall using this Combo Updater for 10.15.7. Combo Updaters are wonderful for removing small glitches and you shouldn't lose any settings.
Click to expand...

Hi,
As a follow up on my bluetooth issue with Magic Keyboard and Magic Mouse on a MBA Mid 2012 updated to BigSur then rolled back to catalina.
The mouse connection is laggy and not usable.
The keyboard connection is unreliable.

I have rolled back to older MacOS version and the issue is present in all version from Lion to Catalina on this MBA.
I also have a MBP 2015 on BigSur where both devices work perfectly fine.

The strangest thing that I noticed is: When doing a clean install (formatting the main drive) and resetting the PRAM both devices remain present in the new OS as soon as it opens even when both devices are OFF at all time.

This means that the bluetooth connectivity is kept in memory somewhere not in the RAM nor on the main drive.

I also noticed a strange error when booting in Diagnostic mode :
Error: 0x8000...3, cannot load EFI/Drivers/TestSupport.efi

It seems that it is not a hardware problem but that installing Big Sur and/or using micro patcher has changed something that even a new OS installation can't recover.

Any hint would be appreciated.
 
haralds said:
Look up in how to completely reset your BlueTooth system. It means you have to pair your devices again.
BlueTooth configuration is global, another account should not make a difference.
Click to expand...
That's right bluetooth is global across accounts.

The strangest thing that I noticed is when doing a clean install (formatting the main drive) and resetting the PRAM both devices remain present in the new OS as soon as it opens even when both devices are OFF at all time.

This means that the bluetooth connectivity is kept in memory somewhere not in the RAM nor on the main drive and this is kept even when a new OS is freshly installed.
 
vinaypundith said:
I have a Mac Pro 3,1 as well, with the APFS BootROM patch, an EFI flashed GTX 680, an upgraded BCM94360CD wireless card, a PCI Express USB 3.0 card (in case the built in USB won't work with Big Sur) and a Gigabyte Titan Ridge Thunderbolt 3 card. Would love to run Big Sur on it.

- Can you give a brief explanation of how you installed OpenCore on the computer, please? I spent hours searching the Internet but cannot find anything definitive on how to install OpenCore on anything other than a 2010/2012 model Mac Pro 5,1.

- How did you get the installer for Big Sur? I can't seem to find a download anywhere. Can we do an update from Catalina after using OpenCore to spoof the model?

Lastly, does anyone here have any experience with the Gigabyte GC-TITAN-RIDGE Thunderbolt add in card in Mac OS Big Sur?

Thanks in advance.
Click to expand...
hi! Problem with internal USB solves by apply Jaclucke's Legacy Usb fix.

(brief (RU) how to perform postinstall on Mac Pro 3.1 on this video)

OpenCore on MacPro 3.1 you can install by perform Open Core Legacy USB Patch Link
 
  • Like
Reactions: AlexSakha67
Hi guys

I'm reading through this thread...but is it worth it to upgrade a mid-2009 13" MBP to Big Sur? I read it takes 23 seconds just to minimize a window - is that right?

Thanks
 
jvaska said:
Hi guys

I'm reading through this thread...but is it worth it to upgrade a mid-2009 13" MBP to Big Sur? I read it takes 23 seconds just to minimize a window - is that right?

Thanks
Click to expand...
Yours is a machine with non-Metal GPU. No solution has been found to achieve graphics acceleration for those in Big Sur, and yes, it is as slow as you read.
If you install, it will be merely an installation exercise - which works well with jackluke‘s method in my case (similar MBP with 17“). But the resulting system is so slow that it is only good for testing.
Have a closer look to 1st page if this thread.
 
  • Like
Reactions: ASentientBot, macinfo and Ausdauersportler
jvaska said:
Hi guys

I'm reading through this thread...but is it worth it to upgrade a mid-2009 13" MBP to Big Sur? I read it takes 23 seconds just to minimize a window - is that right?

Thanks
Click to expand...
It is not worth it! Without any graphics acceleration you can use it as a headless server....

BTW:
Why you do doubt the docs made by the patch developers? This line was put there to stop endless discussions, I am sure of.
 
  • Like
Reactions: macinfo
2008 Mac Pro 3,1 OpenCore Legacy Patcher Big Sur installation SUCCESS - sort of.

First off - thanks @Ausdauersportler for reminding me about OpenCore Legacy Patcher. Also super thanks to its developers.

Second off, to clarify the question I had earlier but could get no answers for - OC Legacy Patcher functions exactly the same as regular OpenCore itself, by applying patches to the EFI bootloader instead of the operating system itself. OCLP is just a tool that configures the OpenCore bootloader to allow for running unsupported Mac OS versions on old hardware.

I know this isn't the right way to install Big Sur, but here is how I did it, in case anyone wants to know. I had tried to avoid using the OCLP at first due to not understanding how it works and fear of firmware destruction, instead preferring to configure OpenCore myself, but that proved to be a massive waste of time (see 3rd bullet point).
- Installed and confiured OpenCore via the guide at: https://dortania.github.io/OpenCore-For-Legacy-Macs/prerequisites.html
- Download Big Sur 11.1 full installer OTA from Catalina through Software Update, which got enabled after following the above guide
- Used that installer to install Big Sur on to a 2nd hard drive in the Mac Pro; this installed successfully but the keyboard and mouse input was not working at all at the "Select your Country or Region" setup screen.

- Booting back into Catalina, ran the OC Legacy Patcher, following instructions at: https://github.com/dortania/Opencore-Legacy-Patcher
- Replaced the contents of the EFI bootloader partition created by the old OpenCore install with what was generated by the OCLP

- Rebooted to the Big Sur drive, and all seems to be working (aside from audio but that seems to be a well known issue). Currently writing this from the Pro 3,1 running Big Sur 11.1.

So a few concerns:
- I did not actually install Big Sur with the OCLP generated bootloader; the installation was done with my self-configured one. So I can say nothing about the safety of running the installer with the OCLP generated bootloader with regards to harmful firmware updates. I'll figure this out more when the 11.2 update comes out, as to how to safely OTA update.
@h9826790 and everyone else who used the method of spoofing a BootROM version higher than what was in the f/w update package as an added protection from f/w update damage - what supported Mac had you spoofed your config to? My OCLP default config spoofed to Mac Pro 7,1 and a BootROM version of 1554.50.3.0.0, higher than the 999.0.0.0.0 that you used. Would putting something even higher like 9999.99.99.99.99 do the trick? Obviously this isn't the only protection I'll use to block f/w updates - but I would like to use it in addition to BlacklistAppleUpdate and run-efi-updater=no.
- Audio does not work, nothing new. But would it be possible to take the audio kexts used by the BarryKN Micropatcher, Big Mac or whatever other operating system level (as against bootloader level) patch tools that do have audio working on the Mac Pro 3,1 and add them to OpenCore to inject at bootup? If so, which kext is it?

- I see absolutely nothing in the Big Sur installation related to DVD drives, even though my Mac Pro has two! Are DVD drives not supported at all in Big Sur or is it just missing the driver for my IDE optical drives (one original Apple SuperDrive and another PC one)? The Disc Burning section of System Report says "No disc burning device was found. If the device is external, make sure it’s connected and turned on." The ATA devices section also says "This computer does not contain any ATA devices". Is there an ATA / IDE support kext that I can add? Can someone who installed Big Sur on a MP3,1 with any other method see if DVD drives work? If DVD drives don't work I really will have to stick with Catalina.

- What is the best model supported Mac to spoof to? OCLP defaulted to Mac Pro 7,1, but that results in a memory config error / warning message because my 32GB total DDR2 on two risers doesn't match what an MP7,1 would use. Also, what is the bare minimum spoofing that I can do to get updates to work? Can I leave the model name and leave the serial number as original, or vice versa?
 

Attachments

  • Screen Shot 2021-01-10 at 4.58.08 PM.png
    Screen Shot 2021-01-10 at 4.58.08 PM.png
    1.2 MB · Views: 682
I should add that my Mac Pro 3,1 has dosdude's APFS BootROM patch installed, an EFI flashed Metal supported NVidia GTX 680 and an upgraded BCM94360CD WiFi card, if that helped things work
 
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