How Can I fix this
install setvars can't continue
usb stick already formatted as extended journaled
install setvars can't continue
usb stick already formatted as extended journaled
Got a tip for us?
Let us know
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
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
-
- Tags
- 10.16 macos unsupported
- Sort by reaction score
- Status
You must first choose between MBR or GPT.
Choose GPT and then you can format the unit.
Thanks a lot for the new micropatcher version, Barry! Nice streamlining of the options.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-micropatchergithub.com
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/.)
Attachments
Last edited:
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?
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?
Thank you for your reply , but where i can choose , format option is to select extended journaled , etc
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
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"?
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.
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.
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 ...
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?)Sorry can't help you there mate. MBA 2013 is officially supported, I just popped in here briefly out of curiosity.
haha no, just curious how is it going for people installing it the unofficial way.
💪🏻haha no, just curious how is it going for people installing it the unofficial way.
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,
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:
github.com
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
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.
Last edited:
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
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...
OcBootManagementLib: Added `BlacklistAppleUpdate` to fix update optout · acidanthera/OpenCorePkg@3998399
closes acidanthera/bugtraker#1255
khronokernel and vit9696 are two experts opencore developers.
Ironically on my earlier Catalina spoofing setup: USBOpenCoreAPFSloader3 (and for BigSur also here: USBOpenCoreAPFSloader3b) I used thatBlacklistAppleUpdate(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?
