macOS 11 Big Sur on Unsupported Macs Thread

[IbrahimFmc]

How Can I fix this

install setvars can't continue

usb stick already formatted as extended journaled

 

[webg3]

How Can I fix this

install setvars can't continue

usb stick already formatted as extended journaled
View attachment 978048

View attachment 978047

You must first choose between MBR or GPT.
Choose GPT and then you can format the unit.

 

[hvds]

I have just released Big Sur Micropatcher v0.5.0. Release notes:

Unfortunately, there is some stuff going on in my life right now that is absolutely nuts -- nothing really bad per se, but certainly introducing tremendous uncertainty into scheduling/time management matters. (And not related at all to the US election, by the way.) As a result, I may not be able to work on the patcher again (or catch up on posts in this forum thread) until late in the week or the upcoming weekend. I realize this is bad timing, with the Apple event and probably the Big Sur release early-mid next week, but this is beyond my control. Sorry.

GitHub - barrykn/big-sur-micropatcher: A primitive USB patcher for installing macOS Big Sur on unsupported Macs

A primitive USB patcher for installing macOS Big Sur on unsupported Macs - barrykn/big-sur-micropatcher

github.com

Thanks a lot for the new micropatcher version, Barry! Nice streamlining of the options.

Just applied successfully patch-kexts.sh as post-install patching to 11.0.1beta on my MBP5,2 (SSD on USB).

(For NightShift, and USB mouse/keyboard without CMD+S/exit, I've put the changes made earlier into 0.5.0. This time hiding them behind an extra command line option --extra, and having the patched CoreBrightness framework and the related libraryvalidation plist in kexts for simplicity, instead of in additional folders. Also patched IOHIDFamily is there. In case anyone is interested, a zip with the three files for kexts/ and the changed patch-kexts.sh is appended; they replace the ones in payloads/.)

 

[m3rih]

Hey everyone,

I would like to try Big Sur on my MacBook Pro Mid 2012. However, I don't understand coding etc. Is there automized intsaller package just like dosdude?

 

[IbrahimFmc]

You must first choose between MBR or GPT.
Choose GPT and then you can format the unit.

Thank you for your reply , but where i can choose , format option is to select extended journaled , etc

 

[BeatCrazy]

Delete for now... trying one more thing...

 

[IbrahimFmc]

You must first choose between MBR or GPT.
Choose GPT and then you can format the unit.

i got it thank you

 

[BeatCrazy]

I have just released Big Sur Micropatcher v0.5.0. Release notes:

Unfortunately, there is some stuff going on in my life right now that is absolutely nuts -- nothing really bad per se, but certainly introducing tremendous uncertainty into scheduling/time management matters. (And not related at all to the US election, by the way.) As a result, I may not be able to work on the patcher again (or catch up on posts in this forum thread) until late in the week or the upcoming weekend. I realize this is bad timing, with the Apple event and probably the Big Sur release early-mid next week, but this is beyond my control. Sorry.

GitHub - barrykn/big-sur-micropatcher: A primitive USB patcher for installing macOS Big Sur on unsupported Macs

A primitive USB patcher for installing macOS Big Sur on unsupported Macs - barrykn/big-sur-micropatcher

github.com

I am making good progress, but have a question for anyone.

I made a fresh Big Sur installer on USB, ran the micropatcher.sh and install-setvars.sh from micropatcher 0.5.0. Based on the Terminal output, I think those worked.

Since I'm running OC 0.6.0 (only stable version for me) on my iMac 11,1 (Late 2009 27" with K2100M), I rebooted with Option, picked my OpenCore booter, then I get my OC picker choice, where I choose Install macOS Big Sur.

For one hour now, I just have a white screen with gray Apple logo, no progress bar. Fortunately, it's not the "Prohibited" sign 🙂

Is this supposed to take 1+ hours? Am I at step #14 "wait an hour or so"?

 

[BeatCrazy]

How Can I fix this

install setvars can't continue

usb stick already formatted as extended journaled
View attachment 978048

View attachment 978047

I had this exact same problem earlier today. I erased my USB via Disk Utility, reformatted it, then downloaded/ran the installer package again. It worked for me after that.

 

[iMac-Oldschool]

Hey everyone,

I would like to try Big Sur on my MacBook Pro Mid 2012. However, I don't understand coding etc. Is there automized intsaller package just like dosdude?

First of all, take a look at Barry K Nathan's post 5621. The official release of Big Sur is expected next week and you would be well advised to wait for that. The installation procedure is unlikely to change very much, but if you are not very familiar with "coding etc." there's not a lot of point in trying to run two installations within a short period of time.
In the meantime, you can check whether your MBP supports Metal graphics. Click on the Apple symbol in the top left hand corner of the screen and go to About This Mac, System Support, Graphics/Displays. If it is supported, you will see a line like: Metal: Supported, feature set macOS GPUFamily1 v3. The details are not important, Metal: Supported is what matters. Your MBP probably has Intel HD Graphics 4000, but it's a good idea to check. Metal support is essential to get acceptable graphics performance under Big Sur.
The best way to install Big Sur is to follow Barry's procedure under https://github.com/barrykn/big-sur-micropatcher, which is updated regularly. The entire process may take 2 or 3 hours, after which your MBP should boot in Big Sur. If the system is running, but WiFi is not working, follow the procedure given by Ausdauersportler in post 5171.

 

[Fcus88]

good evening, help with advice) the system got up with a Bang on no blur effect(

 

[SmOgER]

good evening, help with advice) the system got up with a Bang on no blur effect(

Honestly that machine is probably better off without it. It's more snappy without blur. I even disabled that on my 2013 MBA. It can handle it but I see no reason to slow it down as it looks good and modern with reduced transparency too.

 

[Fcus88]

Honestly that machine is probably better off without it. It's more snappy without blur. I even disabled that on my 2013 MBA. It can handle it but I see no reason to slow it down as it looks good and modern with reduced transparency too.

I understand that he is already an old man, I just torture him with interest, at 10.14 he just flies.in fact, the matter is no longer in the top for a little bit it will be hard for him, but with which command this function is turned on, because when installing a clean system it was no longer there ...

 

[SmOgER]

I understand that he is already an old man, I just torture him with interest, at 10.14 he just flies.in fact, the matter is no longer in the top for a little bit it will be hard for him, but with which command this function is turned on, because when installing a clean system it was no longer there ...

Sorry can't help you there mate. MBA 2013 is officially supported, I just popped in here briefly out of curiosity. 😉

 

[Fcus88]

Sorry can't help you there mate. MBA 2013 is officially supported, I just popped in here briefly out of curiosity. 😉

lol went to see how the people are suffering?)

 

[SmOgER]

lol went to see how the people are suffering?)

haha no, just curious how is it going for people installing it the unofficial way. 😛

 

[Fcus88]

haha no, just curious how is it going for people installing it the unofficial way. 😛

💪🏻

 

[480951]

How well do you suppose this will run on a Mid-2010 MBP that has a 2.4ghz Core 2 Duo processor if I’ve upgraded to an SSD and it has 16GB of RAM? I’m still running High Sierra and don’t use a lot of intensive applications,

 

[tokyogentleman]

How well do you suppose this will run on a Mid-2010 MBP that has a 2.4ghz Core 2 Duo processor if I’ve upgraded to an SSD and it has 16GB of RAM? I’m still running High Sierra and don’t use a lot of intensive application

It runs pretty good on my MBP5,3 just the video isn't as smooth as MBA5,2. I swapped out dvd drive for SSD and made a RAID0 on Catalina. Now it makes a nice remote desktop server. Without video acceleration its a bit painful to watch. So I stick with Catalina RAID0. Read speed is 2x compared to 1 drive. around 500MB/s which is similar to MBA5,4. Good luck!

 

[jackluke]

So it wasn't my USBOpenCore4s1 setup fault , where there was "run-efi-updater No" but on BigSur installer something changed recently, so those who encountered those "EFI firmware issues" after using any OpenCore spoofing setup on BigSur 11.0.1 here is the reason:

run-efi-updater flag no longer works in macOS 11, Big Sur · Issue #1255 · acidanthera/bugtracker

With macOS Big Sur, it seems that even though the NVRAM variable is set macOS will still bless the firmware update during both install and update processes: 15:835 00:005 OCB: Perform boot EFI to d...

github.com

OcBootManagementLib: Added `BlacklistAppleUpdate` to fix update optout · acidanthera/OpenCorePkg@3998399

closes acidanthera/bugtraker#1255

github.com

khronokernel and vit9696 are two experts opencore developers.

Ironically on my earlier Catalina spoofing setup: USBOpenCoreAPFSloader3 (and for BigSur also here: USBOpenCoreAPFSloader3b) I used that BlacklistAppleUpdate (then removed to add "run-efi-updater"), 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.

 

[CuchoM]

in my experience on MBP5,3 and MBA5,2 the serial number and wifi/bt (pcie card) information was saved in the firmware.

its a good idea to remove the drive to get past the white (or black) screen of death and waiting for the folder mark to show up on the screen.

it does seem like opencore could cause a crossflash problem. good to have backup rom file just for safety anyways.

sudo bless -mount / -firmware <PATH>/MBP91_00D7_B00.scap --verbose --recovery

Find the .scap file on shared.dmg to into install copy to your USB boot and use the command to restore firmware

 

[CuchoM]

sudo bless -mount / -firmware <PATH>/MBP91_00D7_B00.scap --verbose --recovery

Find the .scap file on shared.dmg to into install copy to your USB boot and use the command to restore firmware

.scap or fd of your MAC

 

[BeatCrazy]

Sorry delete, double post.

 

[BeatCrazy]

So it wasn't my USBOpenCore4s1 setup fault , where there was "run-efi-updater No" but on BigSur installer something changed recently, so those who encountered those "EFI firmware issues" after using any OpenCore spoofing setup on BigSur 11.0.1 here is the reason:

run-efi-updater flag no longer works in macOS 11, Big Sur · Issue #1255 · acidanthera/bugtracker

With macOS Big Sur, it seems that even though the NVRAM variable is set macOS will still bless the firmware update during both install and update processes: 15:835 00:005 OCB: Perform boot EFI to d...

github.com

OcBootManagementLib: Added `BlacklistAppleUpdate` to fix update optout · acidanthera/OpenCorePkg@3998399

closes acidanthera/bugtraker#1255

github.com

khronokernel and vit9696 are two experts opencore developers.

Ironically on my earlier Catalina spoofing setup: USBOpenCoreAPFSloader3 (and for BigSur also here: USBOpenCoreAPFSloader3b) I used that BlacklistAppleUpdate (then removed to add "run-efi-updater"), 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.

I am mostly following along. Can I assume that the above analysis is responsible for my issue below?

 

[Pascal Baillargeau]

I just want to share a success booting Big Sur latest beta on an iMac 2010 using SSDT-CPBG.
Thanks for all the work done.