dortania / opencore-legacy-patcher Goto Github PK

When I start open core patcher I get this error
/Users/francesco/Downloads/Opencore-Legacy-Patcher-0.0.7/OpenCore-Patcher.command ; exit; francesco@Francescos-MacBook-Pro ~ % /Users/francesco/Downloads/Opencore-Legacy-Patcher-0.0.7/OpenCore-Patcher.command ; exit; NVRAM: Error getting variable - '4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:oem-product': (iokit/common) data was not found No OpenCore detected Current Model: MacBookPro10,2

and then it continues to the normal prompt to select one of the options.
I never managed to install Big Sur with open core, so I am wondering now if it might be because this error,
I am on a MacBookpro 10,2 with upgraded wifi card.
All is working well with BenSova patcher, but I really want to use this patcher because superior on many things.
Any help??

Ok when I booted from the USB and installed Big Sur of course it reboots I go back to the USB and pick macOS Installer, but it gets the apple logo and then reboots every time.

Edit: Just going to say I know the performance wont be great but I'll mostly use it for Spotify and some general browsing and probably tweak it a bit myself.

<dict>
				<key>Arch</key>
				<string>x86_64</string>
				<key>BundlePath</key>
				<string>USB-Map-MacPro5,1.kext</string>
				<key>Comment</key>
				<string>USB Map</string>
				<key>Enabled</key>
				<false/>
				<key>ExecutablePath</key>
				<string></string>
				<key>MaxKernel</key>
				<string></string>
				<key>MinKernel</key>
				<string></string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>

Check syntax. Should be:

"<false/><!--USBmap-->",
"<true/><!--USBmap-->"

instead of:

"<<false/><!--USBmap-->",
"<true/><!--USBmap-->"

Thunderbolt display showing nothing even can see from system report
OTA 11.1 from 11.01 bricked iMac14.2 as well as 11.1 installer. Chime but dark screen. Had to use programmer to flash the EFI ROM chip to revived it. I compared the intel ME version between currupted one and clean one in the dump files, the currupted is 9.0.6.1492 while clean one is 9.0.5.1367, so the update/installation did flash the ROM firmware.

!--OpenCore 0.6.4 config--

plist shows the above ....i have generated 0.6.6 OC with MacPro 5.1 and MAcBookPro9.2 ...same time ...same ""

now i confused, if the plist-file contains the 0.6.6 code ....

MacBookPro9,1, NVIDIA GeForce GT 650M boots to black screen with Big Sur 11.0.1 installer. After verbose boot it shows mouse cursor for a second, the blackscreen and backlight disables

NVRAM is cleared before trying to boot

generated config for MacBookPro9,2:

LauncherOption = Default
LauncherPath=Full

LauncherOption = Default - Invalid LauncherOption
Manual:
"Failsafe: Disabled
Description: Register launcher option in firmware preferences for persistence. Valid values:
XXXXXXXXXXXX
• Disabled — do nothing.
• Full — create or update top-priority boot option in UEFI variable storage at bootloader startup. For this option to work RequestBootVarRouting is required to be enabled.
• Short — create a short boot option instead of a complete one. This variant is useful for some older firmwares, Insyde in particular, but possibly others, which cannot handle full device paths.

This option provides integration with third-party operating system installation and upgrade at the times they overwrite \EFI\BOOT\BOOTx64.efi file. By creating a custom option in this file path becomes no longer used for bootstrapping OpenCore. The path used for bootstrapping is specified in LauncherPath option.

Note 1: Some types of firmware may have faulty NVRAM, no boot option support, or other incompatibilities. While unlikely, the use of this option may even cause boot failures. This option should be used without any warranty exclusively on the boards known to be compatible. Check acidanthera/bugtracker#1222 for some known issues with Haswell and other boards.
Note 2: Be aware that while NVRAM reset executed from OpenCore should not erase the boot option created in Bootstrap, executing NVRAM reset prior to loading OpenCore will remove it. For significant implementation updates (e.g. in OpenCore 0.6.4) make sure to perform NVRAM reset with Bootstrap disabled before reenabling."

LauncherPath = Full - Invalid Launcher Option
Failsafe: Default
Description: Launch path for LauncherOption.
Default stays for launched OpenCore.efi, any other path, e.g. \EFI\Launcher.efi, can be used to provide custom loaders, which are supposed to load OpenCore.efi themselves.

Correct:
LauncherOption = Full
LauncherPath = Default

The following is my output:

Created Build Folder

• Adding OpenCore v0.6.4
• Adding config.plist v0.6.4
• Adding Lilu 1.4.9
• Adding WhateverGreen 1.4.4
• Adding AppleMCEReporterDisabler v1.0.0
• Adding AAAMouSSE v0.93
  Traceback (most recent call last):
  File "/Users/josephkramer/Downloads/Opencore-Legacy-Patcher-0.0.4/OpenCore-Patcher.command", line 92, in
  BuildOpenCore.BuildEFI()
  File "/Users/josephkramer/Downloads/Opencore-Legacy-Patcher-0.0.4/Resources/BuildOpenCore.py", line 74, in BuildEFI
  copy(Versions.mousse_version, Versions.kext_path_build)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/shutil.py", line 139, in copy
  copyfile(src, dst)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/shutil.py", line 96, in copyfile
  with open(src, 'rb') as fsrc:
  IOError: [Errno 2] No such file or directory: '0.93'

@Bustycat found some interesting discussion about bumping the BIOSVersion to prevent firmware updates. If it works, this seems like a reasonable way to stop the bricking issues if other solutions aren't working.

Saw a workaround on Mac Rumors as injecting BIOSVersion to 999.0.0.0.0. Would the patcher developers test further and consider it?
Originally posted by @Bustycat in #15 (comment)

While the instructions posted in that thread don't work, the idea seems sound. I went ahead and tried it on my MacBookPro10,1 (which is affected according to #15). The updated version shows up both in the EFI shell (smbiosview -t 0) and within macOS 11.0.1, and doesn't appear to cause any issues.

I had some difficulty finding the correct way to set the version using config.plist, and after chasing through the OpenCore source for longer than I care to admit I ended up mounting the EFI partition and hand-editing the OpenCore.efi file to make the change.

I want to understand Apple's update process a little more before I pull the trigger and do an OTA update on my machine, but this seems like a promising fix to the bricking.

Hi,

I installed opencore 0.6.4 using the script on a Mac Mini 6,1 (late 2012 - Ivy Bridge machine).
As is commonly documented, the installer rebooted and the machine failed to POST (blinking front lights).
However, power-cycling as well as disconnecting the machine for several hours did not help, unlike the success I've had with my laptop.
While I assume/hope that when I remove the PRAM battery the machine will function correctly, perhaps it is better to blacklist those models as well since this is not a trivial recovery process.

macmini 3,1 (2009 model) trying to boot into big sur installer

I am able to boot into the Big Sur installer via my USB drive and install onto any internal sata based drive on the internal bus, as well as start the install on my PCI nvme drive, however when installing onto the pci nvme, the installer gets to the point where it reboots and the picker is unable to see the pci based nvme drive as a boot option to continue the install. Are there any Kext or plist options to enable this?

After installing OpenCore, my 2012 rMBP 15" would crash if sleeping long enough to enter standby
(AKA hibernate, determined by pmset -a standbydelay)

config.plist needs to support hibernation.
Under Misc/Boot/:

			<key>HibernateMode</key>
			<string>Auto</string>

The bare minimum config.plist that will boot this machine into Big Sur (identifying info removed):

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<!--OpenCore 0.6.4 config-->
<dict>
	<key>Misc</key>
	<dict>
		<key>Boot</key>
		<dict>
			<key>HibernateMode</key>
			<string>Auto</string>
			<key>PickerMode</key>
			<string>Apple</string>
			<key>PollAppleHotKeys</key>
			<true/>
			<key>TakeoffDelay</key>
			<integer>0</integer>
			<key>Timeout</key>
			<integer>5</integer>
		</dict>
		<key>Security</key>
		<dict>
			<key>AllowNvramReset</key>
			<true/>
			<key>AllowSetDefault</key>
			<true/>
			<key>ApECID</key>
			<integer>0</integer>
			<key>AuthRestart</key>
			<false/>
			<key>BootProtect</key>
			<string>Bootstrap</string>
			<key>BlacklistAppleUpdate</key>
			<false/>
			<key>DmgLoading</key>
			<string>Signed</string>
			<key>EnablePassword</key>
			<false/>
			<key>ExposeSensitiveData</key>
			<integer>6</integer>
			<key>HaltLevel</key>
			<integer>2147483648</integer>
			<key>PasswordHash</key>
			<data></data>
			<key>PasswordSalt</key>
			<data></data>
			<key>ScanPolicy</key>
			<integer>0</integer>
			<key>SecureBootModel</key>
			<string>x86legacy</string>
			<key>Vault</key>
			<string>Optional</string>
		</dict>
		<key>Tools</key>
		<array>
			<dict>
				<key>Arguments</key>
				<string></string>
				<key>Auxiliary</key>
				<false/>
				<key>Name</key>
				<string>OpenShell.efi</string>
				<key>Comment</key>
				<string>OpenShell.efi</string>
				<key>Enabled</key>
				<true/>
				<key>Path</key>
				<string>OpenShell.efi</string>
				<key>RealPath</key>
				<false/>
				<key>TextMode</key>
				<false/>
			</dict>
		</array>
	</dict>
	<key>NVRAM</key>
	<dict>
		<key>Add</key>
		<dict>
			<key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
			<dict>
				<key>DefaultBackgroundColor</key>
				<data>AAAAAA==</data>
				<key>UIScale</key>
				<data>Ag==</data>
			</dict>
			<key>4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102</key>
			<dict>
				<key>rtc-blacklist</key>
				<data></data>
			</dict>
			<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
			<dict>
				<key>boot-args</key>
				<string></string>
				<key>run-efi-updater</key>
				<string>No</string>
				<key>csr-active-config</key>
				<data>AAAAAA==</data>
			</dict>
		</dict>
		<key>Delete</key>
		<dict>
			<key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
			<array>
				<string>UIScale</string>
				<string>DefaultBackgroundColor</string>
			</array>
			<key>4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102</key>
			<array>
				<string>rtc-blacklist</string>
			</array>
			<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
			<array>
				<string>boot-args</string>
			</array>
		</dict>
		<key>WriteFlash</key>
		<true/>
	</dict>
	<key>PlatformInfo</key>
	<dict>
		<key>Automatic</key>
		<true/>
		<key>CustomMemory</key>
		<false/>
		<key>Generic</key>
		<dict>
			<key>AdviseWindows</key>
			<false/>
			<key>SystemMemoryStatus</key>
			<string>Auto</string>
			<key>MLB</key>
			<string>...</string>
			<key>ProcessorType</key>
			<integer>0</integer>
			<key>ROM</key>
			<data>ESIzRFVm</data>
			<key>SpoofVendor</key>
			<true/>
			<key>SystemProductName</key>
			<string>MacBookPro11,2</string>
			<key>SystemSerialNumber</key>
			<string>...</string>
			<key>SystemUUID</key>
			<string>...</string>
		</dict>
		<key>UpdateDataHub</key>
		<true/>
		<key>UpdateNVRAM</key>
		<true/>
		<key>UpdateSMBIOS</key>
		<true/>
		<key>UpdateSMBIOSMode</key>
		<string>Create</string>
	</dict>
</dict>
</plist>

It appears that the patcher currently assumes that the selected disk is mounted to /Volumes/EFI. If you already have something mounted to /Volumes/EFI (such as the host system you're creating the USB from), it can install to the wrong EFI.

Propose either checking the mount point after mounting to get where the system put it (likely /Volumes/EFI\ 1) or just forcing a mount point like /Volumes/OCP-EFI.

I was able to successfully create and patch my USB. Once the MacPro is booted, I choose the EFI and it presents me with the picker, where I choose external Install Big Sur. The boot process starts at which time I see the verbose, then it panics. I will upload the panic log, for reference. Thanks
panic-2020-12-04-205029.txt

Hello,

I tried the new Version of the patcher, but I can not run the OpenCore-Patcher.command. I get a failure that the Opencore-Legacy-Patcher-0.0.4 is corrupted. With 0.0.3 it works.

Regards

I'm trying to update aforementioned laptop to Mac OS 11 Big Sur.

I downloaded the OC LP main repo (as I was not able to run it when I downloaded just the 0.0.9 release), ran the open core[something].command file, had it build a new OpenCore setup, transferred the newly built thing to my systems (Mac OS Catalina v10.15.7, BTW) EFI folder (replacing all the old contents of the EFI folder), then used bless ...... -setBoot to make the system boot from the OpenCore partition. But instead it gives these errors, crashes, and then boots to the Catalina recovery partition:

[EB| 'LD:LF] FIO: 0, DIR:1, P: , DP:1
[EB|'B:SBS] SZ: 6211112
[EB|#B:SHA] f4031e1840ae80899574cd5a1feedc6b106d0f87
[EB|'WL:pWLFNV] Err(0xE) @ GV wake-failure
[EB|#WL:DT] 0xCB 0x3C 184 0xCA
[EB|'FS:AGSVH] Err(0xE) @ 'AGU.0
[EB|'LD:LKC] SB -> (System\Library\PrelinkedKernels\immutablekernel)
[EB|'LD:LKC] BPDK -> (System\Library\PrelinkedKernels\immutablekernel.development)
[EB|'LD:LF] FIO: 0, DIR:1, P: System\Library\PrelinkedKernels\immutablekernel.development, DP:0
[EB|'LD:OFS] Err(0xE) @ OPEN (System\Library\PrelinkedKernels\immutablekernel.development)
[EB|'LD:LKC] BPDK, !R -> (System\Library\PrelinkedKernels\immutablekernel)
[EB|'LD:LF] FIO: 0, DIR:1, P: System\Library\PrelinkedKernels\immutablekernel, DP:0

So what have I done wrong? What's an immutablekernel? Also I did not add any prelinkedkernel patches, so why the related errors? Do I need to modify the config.plist configuration created by the OpenCore Legacy Patcher, or exclude some kexts? Tried searching the internet for this error to no avail. Kinda stumped.

I should probably add that the machine that the Legacy Patcher decided to spoof to is a MacBook Pro 11,1.

Thanks in advance.

Early 2013 MacBook Pro 15" with an upgraded BCM94360CSAX WiFi/BT card. WiFi doesn't work at all when booted via Opencore from USB. "Wi-Fi" does not even appear as a network device in System Preferences or under "Wi-Fi" in System Information. BT seems to work normally. EFI was built, with Opencore Legacy Patcher, to a blank, GUID formatted USB 2.0 drive.

I have several hard drives running the patcher. I was able to update the os on one using 004, now with 007 I am not. I can go through the install process but it still says version 11.01 and is presenting me with the update. Is this by design?

I can't know for sure what are the steps to test as I don't have Big Sur since long.
Though, I sometimes get a random reboot after I put my macbook to sleep (closing the lid).
I'm not sure if regular Sleep or Safe sleep is the issue, as well as on battery or plugged.

I'll report if I can gather informations

Tried to run your patcher on my iMac 2010 with an AMD RX480 GPU. To enable 4K HEVC and 4K H.264 we used (as the MacPro users) OpenCore to spoof the iMacPro1,1 ID.

Without this you could only get 4K H.264 by patching AppleGVA.framework - which does not work currently with Big Sur either.

Any plans to add this?

I have managed to install Big Sur on my iMac14,2 (Late 2013, i5) using the patcher, installed just fine, but then I updated to 11.1.
After the reboot, nothing would work. Startup chime is there whenever I try to turn it on, but the screen remains black - pitch black, not even the dim black when the screen is on. SMC / PRAM reset didn't work.
I have used the main branch to create the EFI.

I have used Dosdudes install for Catalina on a Kepler Card Nvidia GT720 on a MacPro 3,1. It has always worked (once it loads the metal drivers) but I am getting no video with it or with the old stock gt 120 card.

At least with the GT 120 I can get to the OpenCore picker, but then it starts booting and then goes black and stays that way. Any idea? Is this do to the patcher, or Something else?

With v0.0.1, our patcher currently has the following limitations:

• Cannot format USBs or create macOS installers
• Missing Legacy Audio Patches
  • Currently looking into AppleALC patching
  • Temporary solution would be to install VoodooHDA
• Missing Legacy GPU Patches
• Missing Airdrop support on pre-2012 models
• Missing BCM4328 and BCM4321 chipset patches
• Missing more user friendly GUI

I keep getting OpenCore-Legacy-Patcher is damaged error and it makes me trash the program. Any thoughts?

Using v0.0.7 in an attempt to install Catalina 10.15.7 to MacBook Air 4,2, booting into picker starts OC (0.6.3) and then reboots into what appears to be the installer, only to give the option to reinstall OS has High Sierra, rather then Catalina?

Build Folder attached for reference.
Build-Folder.zip

Hi.

Just a quick thought, wouldn't be better to report MacBookPro10,1 (Retina mid-2012) as a late-2013 model? The mid-2014 is reporting as has a different GPU in it (AMD vs Nvidia) and that might interfere with power management on the GPU.

thx

Hello. My install using 0.0.3, 0.04, and 0.0.5 all get to the installation screen for my drive but do not allow me to use a keyboard or mouse because there is no USB support. I am attaching a photo of the installation screen. I am hoping that you will fix this issue with Mac Pro 3,1 machines. Please assist.

Hi,
I used this patcher to patch the EFI partition of a USB installer but now the USB flash drive is corrupted and I can't even erase it.
On a Linux laptop, it shows up as connected through lsusb but it isn't even attributed a corresponding device in /dev.
Any idea how to reuse this drive now?

When I try to open parted by calling the disk by id, it says no medium found

With the recent commit to both this patcher and OpenCorePkg, I added a new quirk to OpenCore that will max out the BIOSVersion property. We've had several reports that this works however we'd still like to have a thread to consolidate things, as we had too many issues to keep track of.

Issues recently closed:

• #43
• #42
• #40
• #38
• #32
• #15

For users with machines that have been bricked, we recommend following this thread

iMac 14.2 model is not compatible with Big Sur officially. During the process of installation of 11.01/11.1, iMac was bricked and then was revived by programming EFI ROM chip, then resuming installation of 11.01/11.1. After that Big Sur can run natively even opencore is not active.

This has happened twice now, so I can confirm it is the 11.1 beta 2 update causing it:

Mid-2012 Retina MBP 15" (MacBookPro10,1). Erased and installed Big Sur 11.0.1 GM using OpenCore.

I received the macOS 11.1 beta 2 update and installed it. During the update process, an Apple logo with a progress bar appears. At about 25% the MacBook shuts down and will not start back up. Pressing the power key causes fan spin but I get no chime or backlight. It will power off if I hold the power key, but the machine will not POST.

I tried NVRAM clear, SMC reset, and SMC bypass, no good. The only way I could get it out of this state was to take the bottom off and disconnect the battery. Seems like the 11.1 beta 2 sees the SMBIOS reporting MacBookPro11,2 and tries something it should not do. My guess would be attempting a firmware update or perhaps an RTC issue as disconnecting the battery clears it up. Once it boots, it completes the update and runs 11.1 beta 2 fine.... but if you don't have the proper pentalobe bit, you are in trouble.

I previously upgraded from 11.0.1 to 11.1 beta 1 using OpenCore and did not encounter this problem.

Hi everyone

I bricked my two iMacs installing BigSur 11.1 Update! It worked well with first release of BigSur, then troubles happened after updating process. I bricked the first one, though it was an hardware issue, tried the second one and did twice the same mistake :-(((

CHIME SOUND, BLACK SCREEN AND NOTHING ELSE...If only I new a simple software could damage my iMacs this way I wouldn't have used this patch!

I've already tried all the standard procedures (pram, power, nvram, etc.) and nothing works.
Please tell me I won't have to open the machine to fix it ?!! Because I won't be able to...

I read about corrupted EFI Rom and it might be my case...I can't believe I broke two iMacs in less than one hour, I feel so stupid now!

Will Apple Genius fix it? Will they charge for it?

Best regards from Switzerland
Mateo

After installing Big Sur everything was ok, so I started to update to 11.1, after a few minutes, my imac won't turn on (completely black screen) Any suggestion? Model: iMac 27" 2012.

The instalation tryed to upgrade the firmware (so bad)
I'd open the macbook and disconnected battery and ssd to solve the boot.
Everything was working fine , even OTA to macOS BS 11.2 beta (20D5029f)

use opencore 0.6.5 files to solve firmware version and all is working fine
Opencore 0.6.5 was find is this link
https://bitbucket.org/profdrluigi/opencorepkg-beta/downloads/

Could you please update the patcher ?

Seems like no matter what I do, I'm met with immutable kernel, followed by a restart. Tried different installers (High Sierra and Catalina). Have not attempted to use Big Sur yet.

I also have a K4100M flashed to work on macOS, not sure if that would be the issue but I read that some kepler GPUs still work under BigSur.

Edit: Forgot to mention, used latest version of patcher 0.0.7 at the time of writing.

Hello, i have the same issue like in #7 I used version 0.0.7 and when my MacBook 10.1 is to long in in standby, i think more than 24 hour it crashes.

`Sleep Wake failure in EFI

Failure code:: 0x00000000 0x0000001f

Please IGNORE the below stackshot

================================================================
Date/Time: 2020-12-10 06:16:09.275 +0100
OS Version: ??? ??? (Build ???)
Architecture: x86_64
Report Version: 32

Data Source: Stackshots
Shared Cache: EDB59884-BECA-35C6-A628-15DA943D22A5 slid base address 0x7fff200ba000, slide 0xba000

Event: Sleep Wake Failure
Duration: 0.00s
Steps: 1

Boot args: -v keepsyms=1 debug=0x100 agdpmod=pikera chunklist-security-epoch=0 -chunklist-no-rev2-dev

Time Awake Since Boot: 43s

Process: swd [299]
Architecture: x86_64
Footprint: 376 KB
Time Since Fork: 0s
Num samples: 1 (1)

Thread 0x8ae 1 sample (1) priority 4 (base 4)
<thread QoS background (requested background), thread darwinbg, process darwinbg, IO tier 2>
1 start + 1 (libdyld.dylib + 87601) [0x7fff203e3631] 1
1 ??? [0x10ddf7454] 1
1 ??? [0x10ddf71e8] 1
1 __stack_snapshot_with_config + 10 (libsystem_kernel.dylib + 143386) [0x7fff203b601a] 1
*1 ??? [0xffffff80002621f6] 1
*1 ??? [0xffffff8000969ceb] 1
*1 ??? [0xffffff8000873d11] 1
*1 ??? [0xffffff80002851c9] 1
*1 ??? [0xffffff80002bbf0d] (running) 1

Binary Images:
0x7fff20393000 - 0x7fff203c1fff libsystem_kernel.dylib (7195.50.7) <41068F5C-74E3-3C98-9256-6A18364FB5BA> /usr/lib/system/libsystem_kernel.dylib
0x7fff203ce000 - 0x7fff20408fff libdyld.dylib (832.7.1) <0C66AB9F-E22C-3286-B76B-DA4008698CD2> /usr/lib/system/libdyld.dylib
Model: MacBookPro11,2, BootROM 427.0.0.0.0, 4 processors, Quad-Core Intel Core i7, 2,7 GHz, 16 GB, SMC 2.3f36
Graphics: kHW_IntelHD4000Item, Intel HD Graphics 4000, spdisplays_builtin
Graphics: kHW_NVidiaGeForceGT650MItem, NVIDIA GeForce GT 650M, spdisplays_pcie_device, 1 GB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x112), Broadcom BCM43xx 1.0 (7.77.111.1 AirPortDriverBrcmNIC-1669)
Bluetooth: Version 8.0.1f5, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SD512E, 500,28 GB
USB Device: USB 3.0 Bus
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: Hub
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: FaceTime HD Camera (Built-in)
Thunderbolt Bus: MacBook Pro, Apple Inc., 23.4`

Hi,
I am a little bit worried about BlacklistAppleUpdate not set in your generated config files, injecting iMac15,1 ID on iMacs 2010,2011. Don't you think an unwanted firmware update could occurs on Big Sur?

OpenCore.efi inside OpenCore generated by Legacy Patcher is slightly smaller than the one of OpenCore’s release package. I tried to replace it with the release one, yet a warning message for not properly shutting down would pop up after every booting. Does it mean that we could update OpenCore.efi only via Legacy Patcher in the future?

I realized that using python 3.8.5 creates more errors than even native python 2.7. See here:
#23 (comment)
Using python 2.7.16 I was able to run the application by navigating to

/Users/<user>/Downloads/Opencore-Legacy-Patcher-main/App/OpenCore-Patcher.app/Contents/MacOS/OpenCore-Patcher.command

and running the command directly. But when installing to an EFI on USB. I get these errors:

Coping OpenCore onto Volumes/EFI
Cleaning EFI folder
Traceback (most recent call last):
  File "/Users/<user>/Downloads/Opencore-Legacy-Patcher-main/App/OpenCore-Patcher.app/Contents/MacOS/OpenCore-Patcher.command", line 160, in <module>
    BuildOpenCore.MoveOpenCore()
  File "/Users/<user>/Downloads/Opencore-Legacy-Patcher-main/App/OpenCore-Patcher.app/Contents/MacOS/Resources/BuildOpenCore.py", line 376, in MoveOpenCore
    rmtree("/Volumes/EFI/EFI")
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/shutil.py", line 270, in rmtree
    rmtree(fullname, ignore_errors, onerror)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/shutil.py", line 275, in rmtree
    onerror(os.remove, fullname, sys.exc_info())
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/shutil.py", line 273, in rmtree
    os.remove(fullname)
OSError: [Errno 2] No such file or directory: '/Volumes/EFI/EFI/BOOT/._.disk_label'
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

There is also a syntax error in the beginning "coping" should be "copying"

https://github.com/dortania/Opencore-Legacy-Patcher/blob/bafff664171f54d969b4745e2e74820b5d50dc83/OpenCore-Patcher.command#L200

I am not sure about if OpenCanopy.efi should work with OpenCore generated by Legacy Patcher as the driver is included, but it does not work for my MacBookPro9,2. I followed the guide but the OpenCore boot screen is still not graphical.

Are there any plans for a patch that can enable the legacy Intel IDE controller used in 2008 model Mac Pro 3,1 systems? I have such a system, and the IDE bus was working in Catalina (two DVD drives are connected to it) but in Big Sur installed with the OpenCore Legacy Patcher nothing connected to the IDE controller gets detected. Thanks in advance

A UIScale of Ag== (02) fits better with the default behavior than AQ== (01) on rMBP Mid-2012 (MacBookPro10,1) when booting with FileVault.

With 02, there is no change in resolution when it switches from pre-boot to boot and looks more smooth.

So with 0.0.8 I was finally able to install Big Sur. The installation was incredibly slow, expected, but still felt off. During the Big Sur setup screen it was very laggy. It would freeze for about 10 seconds and then be choppy for a few seconds while letting me move the mouse and then freeze again.

What's broken:
Wifi
Bluetooth
Sound
Brightness

The computer also idles very hot.

Hello @khronokernel, since through your OC Legacy Patcher for enabling OTA updates you are spoofing to iMac15,1 that is an Haswell architecture BigSur supported Mac, for fixing dualGPUs blank screen (after the apple stage2 loading bar) you might need the pikeralpha's AppleGraphicsDevicePolicy fix that is adding in OC config.plist boot-args: agdpmod=pikera

I also advise to add -no_compat_check because even if you spoof a supported board id, in some circumstances this is ignored using anyway the stock BigSur PlatformSupport.plist that of course doesn't contain the unsupported legacy Mac board id.

My example on how I'd modify the AppleNVRAM key:

			<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
			<dict>
				<key>boot-args</key>
				<string>keepsyms=1 debug=0x100 -no_compat_check agdpmod=pikera</string>

I have a MacBook Pro 7,1 and version 0.0.6 is spoofing it as 11,1. When trying to boot the EFI to install Big Sur it tells me this Mac is not supported. I don't know what I'm doing wrong.

I was playing around with trying to get non-macserial-generated ids (i.e. my machine's orginal ids) when booting through OpenCore. (And latterly pestering the OC developers with some issues, and one very minor accepted codefix, related to looking into this!)

It seems (at least to me) a good idea not to 'burn through' faked ids, and not to require users (at least, users who don't know how to manually change their config!) to fake more than is necessary.

However the current OCLP config does use macserial-generated system ids.

Of course, most OC documentation also assumes macserial. The reason I understood it was even possible to use the original machine's ids is that @jacklukem's OpenCoreAPFSLoader is already set up to do this; i.e. OC already supported this. I have been using @jacklukem's OC config (latterly with some minor updates) to pass through my machine ids, with only the product name (e.g. Mac15,1) and matching board id (i.e.Mac-XXXXXXX) faked, all through the Big Sur beta process, with no problems at all. (Well, not NO problems, but the firmware flashing problem is completely unrelated to this and now fixed!)

After playing around with @jacklukem's config and also looking at how this part of OC works, then on OC 0.6.6 the following <PlatformInfo> config section (EDIT#1 edited to reflect the comments by @vit9696 below) achieves this (I'm including this for the record, and to reflect my understanding that it wouldn't be that hard to do; also, in case anybody else wants to modify their config based off this section for now):

        <key>PlatformInfo</key>
        <dict>
            <key>Automatic</key>
            <true/>
            <key>CustomMemory</key>
            <false/>
            <key>Generic</key>
            <dict>
                <key>AdviseWindows</key>
                <false/>
                <key>MaxBIOSVersion</key>
                <true/>
                <key>MLB</key>
                <string></string>
                <key>ProcessorType</key>
                <integer>0</integer>
                <key>ROM</key>
                <data></data>
                <key>SpoofVendor</key>
                <false/>
                <key>SystemMemoryStatus</key>
                <string>Auto</string>
                <key>SystemProductName</key>
                <string>iMac15,1</string>
                <key>SystemSerialNumber</key>
                <string></string>
                <key>SystemUUID</key>
                <string></string>
            </dict>
            <key>UpdateDataHub</key>
            <false/>
            <key>UpdateNVRAM</key>
            <false/>
            <key>UpdateSMBIOS</key>
            <true/>
            <key>UpdateSMBIOSMode</key>
            <string>Create</string>
        </dict>

@bensova @vit9696 @khronokernel

Hi,
I have run BS on iMac11.3 with Opencore-Legacy-Patcher 0.0.9 and probably the CatalinaBCM5701Ethernet.kext is not loaded correctly because in the System Report Ethernet Card does not exist. I have checked the config.plist and the kext is enabled.

In other things the sound with VoodoHD.kext is terrible, is it possible to install AppleHDA.kext using OC?

Thanks for Your support.

Hi there,

Not able to get this patcher to work on the Mac Pro 4,1 > 5,1.

• Fresh install of Mojave
• Downloaded this Patcher
• Ran using "option 1"
• Used Opencore Configurator to mount EFI partition
• Rebooted into Recovery Mode
• Blessed the EFI partition for booting
• Boot screen loaded with OS selector, however no OS will boot
• Shows message "This version of Mac OS X is not supported on this platform."

It's possible that I've done something wrong, but considering there are no instructions, this was my best attempt.

Mac Pro (Early 2009) flashed to 5,1.
ATI Radeon RX580
3.46 GHz 6-Core Intel Xeon

Any fix / suggestions?