Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
It works.....!!!, I mod config.plist to use SMBIOS Info instead of Generic Data, reinstalled 11.1 and bypass correctly the EFI Update at MBP Mid 2012.
@Arnoldso
coupld you screenshot that section of config.plist (SMBIOS/Generic)? I tried but did not work for me so I might miss something.
thanks
 
Last edited:
Is Big Sur 11.1 update safe to install on Mac Pro 5,1 and on MacBook Pro 9,1 (both with OpenCore)?
 
  • Like
Reactions: MacHacJac
We got an old 2012 27” iMac that isn’t officially supported. I have to open it up again to install a bigger SSD. I was wondering if anyone can recommend a WiFi card that would work from the latest iMacs? I’m assuming since some people only have wifi issues with their 2012 if I upgrade it to the latest it could support it would fix that problem right? It would also just work if it came from a newer iMac ? I’ve tried researching but I can only find the same models or possibly the 2013 version? Thank you.
 
@Arnoldso
coupld you screenshot that section of config.plist (SMBIOS/Generic)? I tried but did not work for me so I might miss something.
thanks
Here are the Section.....

<key>PlatformInfo</key>
<dict>
<key>Automatic</key>
<false/>
<key>CustomMemory</key>
<false/>
<key>SMBIOS</key>
<dict>
<key>BIOSReleaseDate</key>
<string>12/02/2020</string>
<key>BIOSVendor</key>
<string></string>
<key>BIOSVersion</key>
<string>999.0.0.0.0</string>
<key>BoardAssetTag</key>
<string>Base Board Asset Tag</string>
<key>BoardLocationInChassis</key>
<string>Part Component</string>
<key>BoardManufacturer</key>
<string></string>
<key>BoardProduct</key>
<string>Mac-189A3D4F975D5FFC</string>
<key>BoardSerialNumber</key>
<string>C02314902J9FH31FB</string>
<key>BoardType</key>
<integer>10</integer>
<key>BoardVersion</key>
<string>MacBookPro11,1</string>
<key>ChassisAssetTag</key>
<string>Asset Tag#</string>
<key>ChassisManufacturer</key>
<string></string>
<key>ChassisSerialNumber</key>
<string>C02JN5U8DTY7</string>
<key>ChassisType</key>
<integer>10</integer>
<key>ChassisVersion</key>
<string>Mac-189A3D4F975D5FFC</string>
<key>FirmwareFeatures</key>
<data>d/UP6wAAAAA=</data>
<key>FirmwareFeaturesMask</key>
<data>f/8f/wAAAAA=</data>
<key>PlatformFeature</key>
<integer>2</integer>
<key>ProcessorType</key>
<integer>1541</integer>
<key>SmcVersion</key>
<data></data>
<key>SystemFamily</key>
<string>MacBook Pro</string>
<key>SystemManufacturer</key>
<string></string>
<key>SystemProductName</key>
<string>MacBookPro11,1</string>
<key>SystemSKUNumber</key>
<string>System SKU#</string>
<key>SystemSerialNumber</key>
<string>C02JN5U8DTY7</string>
<key>SystemUUID</key>
<string>C63A2F62-CB18-4033-B4A8-DD3C597FC9FF</string>
<key>SystemVersion</key>
<string>1.0</string>
</dict>
<key>UpdateDataHub</key>
<true/>
<key>UpdateNVRAM</key>
<true/>
<key>UpdateSMBIOS</key>
<true/>
<key>UpdateSMBIOSMode</key>
<string>Create</string>
</dict>


Automatic must be "false" to Use SMBIOS Info.

<key>Automatic</key>
<false/>
 
Last edited:
  • Like
Reactions: hvds and paul.zhu
Is Big Sur 11.1 update safe to install on Mac Pro 5,1 and on MacBook Pro 9,1 (both with OpenCore)?
my experience, Mac Pro with opencore is perfect, refer below for more information:
while other Macs with opencore could be troublesome, i bricked my iMac.
 
  • Like
Reactions: webg3
Here are the Section.....

<key>PlatformInfo</key>
<dict>
<key>Automatic</key>
<false/>
<key>CustomMemory</key>
<false/>
<key>SMBIOS</key>
<dict>
<key>BIOSReleaseDate</key>
<string>12/02/2020</string>
<key>BIOSVendor</key>
<string></string>
<key>BIOSVersion</key>
<string>999.0.0.0.0</string>
<key>BoardAssetTag</key>
<string>Base Board Asset Tag</string>
<key>BoardLocationInChassis</key>
<string>Part Component</string>
<key>BoardManufacturer</key>
<string></string>
<key>BoardProduct</key>
<string>Mac-189A3D4F975D5FFC</string>
<key>BoardSerialNumber</key>
<string>C02314902J9FH31FB</string>
<key>BoardType</key>
<integer>10</integer>
<key>BoardVersion</key>
<string>MacBookPro11,1</string>
<key>ChassisAssetTag</key>
<string>Asset Tag#</string>
<key>ChassisManufacturer</key>
<string></string>
<key>ChassisSerialNumber</key>
<string>C02JN5U8DTY3</string>
<key>ChassisType</key>
<integer>10</integer>
<key>ChassisVersion</key>
<string>Mac-189A3D4F975D5FFC</string>
<key>FirmwareFeatures</key>
<data>d/UP6wAAAAA=</data>
<key>FirmwareFeaturesMask</key>
<data>f/8f/wAAAAA=</data>
<key>PlatformFeature</key>
<integer>2</integer>
<key>ProcessorType</key>
<integer>1541</integer>
<key>SmcVersion</key>
<data></data>
<key>SystemFamily</key>
<string>MacBook Pro</string>
<key>SystemManufacturer</key>
<string></string>
<key>SystemProductName</key>
<string>MacBookPro11,1</string>
<key>SystemSKUNumber</key>
<string>System SKU#</string>
<key>SystemSerialNumber</key>
<string>C02JN5U8DTY3</string>
<key>SystemUUID</key>
<string>C63A2F62-CB18-4033-B4A8-DD3C597FC9FF</string>
<key>SystemVersion</key>
<string>1.0</string>
</dict>
<key>UpdateDataHub</key>
<true/>
<key>UpdateNVRAM</key>
<true/>
<key>UpdateSMBIOS</key>
<true/>
<key>UpdateSMBIOSMode</key>
<string>Create</string>
</dict>


Automatic must be "false" to Use SMBIOS Info.

<key>Automatic</key>
<false/>
For others, please gen your own serial number and UUID when use the above code.

Hundreds of people using the same serial number to login to iCloud may cause unexpected issues.

Even using your original serial number (which not belongs to this Mac model) still better than using this published number.
 
Using micropatcher?

If so, that is correct behaviour.

Step 9...Start up from "EFI Boot". Within a few seconds, although most likely in under a second, the Mac will suddenly power down. This indicates that the setvars EFI utility has finished ....

Step 10 Turn the Mac back on (or reboot it if you skipped step 9), with the Option key down again, to use the Startup Selector again. This time, boot from "Install macOS Big Sur Beta" (or similar)...
Yeah, micropatcher....
Not getting up «install macOS Big Sur», just efi boot... hmmm I’m not using beta, I’ll try that instead. Thanks
 
  • Like
Reactions: webg3
Here are the Section.....

<key>PlatformInfo</key>
<dict>
<key>Automatic</key>
<false/>
<key>CustomMemory</key>
<false/>
<key>SMBIOS</key>
<dict>
<key>BIOSReleaseDate</key>
<string>12/02/2020</string>
<key>BIOSVendor</key>
<string></string>
<key>BIOSVersion</key>
<string>999.0.0.0.0</string>
<key>BoardAssetTag</key>
<string>Base Board Asset Tag</string>
<key>BoardLocationInChassis</key>
<string>Part Component</string>
<key>BoardManufacturer</key>
<string></string>
<key>BoardProduct</key>
<string>Mac-189A3D4F975D5FFC</string>
<key>BoardSerialNumber</key>
<string>C02314902J9FH31FB</string>
<key>BoardType</key>
<integer>10</integer>
<key>BoardVersion</key>
<string>MacBookPro11,1</string>
<key>ChassisAssetTag</key>
<string>Asset Tag#</string>
<key>ChassisManufacturer</key>
<string></string>
<key>ChassisSerialNumber</key>
<string>C02JN5U8DTY3</string>
<key>ChassisType</key>
<integer>10</integer>
<key>ChassisVersion</key>
<string>Mac-189A3D4F975D5FFC</string>
<key>FirmwareFeatures</key>
<data>d/UP6wAAAAA=</data>
<key>FirmwareFeaturesMask</key>
<data>f/8f/wAAAAA=</data>
<key>PlatformFeature</key>
<integer>2</integer>
<key>ProcessorType</key>
<integer>1541</integer>
<key>SmcVersion</key>
<data></data>
<key>SystemFamily</key>
<string>MacBook Pro</string>
<key>SystemManufacturer</key>
<string></string>
<key>SystemProductName</key>
<string>MacBookPro11,1</string>
<key>SystemSKUNumber</key>
<string>System SKU#</string>
<key>SystemSerialNumber</key>
<string>C02JN5U8DTY3</string>
<key>SystemUUID</key>
<string>C63A2F62-CB18-4033-B4A8-DD3C597FC9FF</string>
<key>SystemVersion</key>
<string>1.0</string>
</dict>
<key>UpdateDataHub</key>
<true/>
<key>UpdateNVRAM</key>
<true/>
<key>UpdateSMBIOS</key>
<true/>
<key>UpdateSMBIOSMode</key>
<string>Create</string>
</dict>


Automatic must be "false" to Use SMBIOS Info.

<key>Automatic</key>
<false/>
Posting your S/N publicly is a bit dangerous... For codes you could apply the “code” function.
 
Yes it is safe , look at this post
#8,081 I am using that with no problem

Once again, stop saying a method is all around safe. Your case is your case, but its not the rule. The simple answer is no. The fact is OpenCore is bricking a certain percentage of machines, particularly MBP's, MBA's, and iMacs from 2012-2014. Until the firmware issue is remedied with a standardized and repeatable solution, saying anything to the contrary is dangerous. Those coming to the forum asking for information and help will be met with only half truths, and that's setting them up for failure.

Is Big Sur 11.1 update safe to install on Mac Pro 5,1 and on MacBook Pro 9,1 (both with OpenCore)?

And the full answer is it entirely depends on how you want to go about updating. For the Mac Pro I would say its relatively safe, even doing an OTA update. Theres little risk of a firmware issue. For the MacBook Pro I would be more cautious. My advice would be create a full USB installer for the time being and install that way. It may be worth considering the Micropatcher. Avoid OTA's for that machine entirely until the firmware issues get worked out.
 
Last edited:
Yeah, micropatcher....
Not getting up «install macOS Big Sur», just efi boot... hmmm I’m not using beta, I’ll try that instead. Thanks
Format the USB drive, and set up the install again. It sounds like an issue with either the USB drive or createinstallmedia didn't complete. It will not matter whether its a Beta or Official release. Just do it again following the instructions closely. Heres a quick Reference Guide for the MicroPatcher:

1. Run Create Install Media
2. Run micropatcher.sh
3. Run install-setvars.sh
4. Shut down and select "EFI Boot" (the system will shut down)
5. Reboot, then select "Install Mac OS Big Sur"
6. Kext Patching (if you need it)
 
Dosdude1 patcher has example code using NSTask and NSPipe.
Ok, but how would I make that visible in the GUI? Here is an example of my running a script:
Code:
        if(scriptPath){


            NSArray* theArguments = [NSArray arrayWithObjects: @"/bin/sh", scriptPath, @"micropatcher.sh", nil];

            NSTask* scriptTask = [[NSTask alloc] init];

            NSPipe *pipe;

            pipe = [NSPipe pipe];

            [scriptTask setStandardOutput: pipe];

            [scriptTask setStandardError: pipe];

            NSFileHandle *file;

            file = [pipe fileHandleForReading];

            [scriptTask setLaunchPath: [theArguments objectAtIndex:0]];

            [scriptTask setArguments: [theArguments subarrayWithRange: NSMakeRange (1, ([theArguments count] - 1))]];

            [scriptTask launch];

            NSData *data;

            data = [file readDataToEndOfFile];

            NSString *string;

            string = [[NSString alloc] initWithData: data encoding: NSUTF8StringEncoding];

            NSLog (@"got\n%@", string);

            NSLog(@"It works!!!");


        } else {

            NSLog(@"This script doesn't exist");

        }
 
Last edited:
  • Like
Reactions: Ausdauersportler
Probably because your MacPro3,1 it's a non-APFS firmware (with Legacy USB), to skip this reboot to Catalina, you should use my OpenCoreAPFSloader4b setup to detect the hidden stage2 installer "macOS Installer", then installation proceeds through "29 minutes remaining", after there are some some reboot and loop with apple logo that is the stage3 installer.

Since you have a GPU flashed for MacPro , almost surely you have a bootscreen for verbose booting or apple logo, so you can use this as bootloader to detect your hidden APFS volumes: USBOpenCoreAPFSloader4b

Then try to make a "BaseSystem fix" installer, with this: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-29170178

after installation (and bootloop) you should apply "BigSurFixes Legacy USB patches".

For "BaseSystem fix" target USB createinstallmedia must be used HFS+ (not APFS).

While for target BigSur installation disk I'd advise instead of erasing as HFS+ , use directly an APFS container.
Hi Jackluke, have you been able to run BigSur on your old Macbook Air mid 2011? (MacBookAir4,2).
 
I tried resetting 'energy saver' panel, and no more network problems.

Big Sur works incredible (I have 16 MBP and 2013 late iMac), the only 'bug' I have is volume icon in taskbar showed headphone icon in 11.0.1, and it doesn't show it anymore in 11.1. That's it.
iMac with Fusion Drive?
 
The USB installer, prep correctly, would show up with 2 things on Option Power up.

(a) "EFI Boot"
(b) "Install macOS Big Sur"
I will screenshot the process, it used to do so - when creating boot volumes before, but didn't this time.... will get back to you after xmas :) - and happy hollidays everyone :)
 
Format the USB drive, and set up the install again. It sounds like an issue with either the USB drive or createinstallmedia didn't complete. It will not matter whether its a Beta or Official release. Just do it again following the instructions closely. Heres a quick Reference Guide for the MicroPatcher:

1. Run Create Install Media
2. Run micropatcher.sh
3. Run install-setvars.sh
4. Shut down and select "EFI Boot" (the system will shut down)
5. Reboot, then select "Install Mac OS Big Sur"
6. Kext Patching (if you need it)
yeah what I did,,, but will document the process after xmas :) maybe you guys will spot where I go wrong. :) Anyway, happy juletide :)
 
Happy Holidays @dosdude1 @jackluke @ASentientBot @Barry K. Nathan @parrotgeek1 Thank you for your valuable support as ethical hackers of Big Sur! My perfectly working iMac 2013 with masterfully patched Big Sur logic board is dead, ONLY due to a killer USB 3.0 7 ports Cinese Hub (according to Apple Store support, a damage of 600€!) so I have bought a Mac mini M1 that's incredibly fast and surprisingly compatible with Mac x86 and Windows 10 ARM x64 Insider Preview apps thanks to Rosetta 2, Parallels Desktop M1 16.3 preview and some very useful tricks that I have learned IN THIS FORUM :)

But I will continue to follow this trend hoping that one day my Mac mini 2010 Core 2 Duo Penryn will have accelerated graphic on Intel Big Sur.

MacMiniM1-8-256.gif
 
Last edited:
Can someone send me a list of all the Big Sur patches/kexts and for what Macs each are? I would really appreciate it. Merry Christmas to all who celebrate it!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.