macOS 11 Big Sur on Unsupported Macs Thread

[tchek]

Hi all,
😎

Everything was done quickly and very simply.

I have upgraded my iMac 21' Late 2012 and Mac Mini Late 2012 with "Patched Sur"
(V 0.2.1, thanks to Ben,👍🏻 this is a great work), patched the kexts for wifi,
and everything rolles perfectly.

On my 27' Late 2013 everything is ok too, and no need to patch the Kexts.

 

[Dilli]

I appreciate the response, but I still don't think it's "easy" :-/

Just to be 100% clear (and I think updating the guidance doc would help), if you want to go from 11.3 to 11.4 (for example), you will need to manually find/download the official InstallerPackage from Apple, and run it from that "Install macOS Big Sur" application. Not from the the "Software Update" tool.

Using terms like "delta updates" and "OTA updates" can be confusing, especially for non-native English speakers, and considering Apple doesn't/rarely describes updates using those terms.

OCLP allows OTA updates but full installers on non metal graphic macs like my MacBook Air mid 2011. I had 11.3.1 and I just used software update in Preference pane and the mac started downloading 11.4. Thereafter had few boots, black screen had to manually press option key to get to the installer to complete and it was done. I do admit it was not smooth at all. Thereafter re -installed volume legacy patch for non metal graphic card acceleration. All runs ok but my particular model still has issues with graphic acceleration as its not listed in the OCLP docs as success but I have hope that developers will get a solution. I suggest keep the OCLP docs file as your guide on your desktop.Cheers

 

[Dilli]

Ok friends, I got the "big beast" up and running 11.4 thanks to OCLP 1.5!

This beast is my newish (free-to-me) Mid-2010 17" MacBook Pro 6,1 A1297. It has the 2.66GHz dual core i7, with the Nvidia GeForce GT 330M 512MB GPU, 8GB of 1067MHz DDR3, and the optional matte screen (1920x1200).

Performance seems pretty good so far. I occasionally notice some graphical glitches around the cursor leaving "trails" on background images. And I did run into the (documented) bug of inability to click "Continue" on Maps, etc. Had to use the Tab + Spacebar workaround.

Overall I'm really impressed! Thanks to all that made this possible.

I have similar issue of cursor leaving trails.

 

[Dilli]

Is the process trustd running amok? Go to the directory /private/var/protected/trustd/ Delete the valid.sqlite3 files. When rebooting with a network connection Apple will rebuild the .sqlite files, trustd will peak briefly, then CPU activity will return to normal for good. 😎

Yes I too am having my CPU over loaded on my MacBook air with "trustd" running amok. I will follow your steps. Thanks

 

[NetRocker]

Both methods will work. Please check the installation instructions within the official OCLP docs linked in on the first post of this thread.

Thanks,

 

[woefi]

Is the process trustd running amok? Go to the directory /private/var/protected/trustd/ Delete the valid.sqlite3 files. When rebooting with a network connection Apple will rebuild the .sqlite files, trustd will peak briefly, then CPU activity will return to normal for good.

Thank You! This bugged me the last week on several machines (BigSur and Mojave alike...)
also this Link explains a little more and how to remove them also in Mojave:
https://lapcatsoftware.com/articles/trustd.html

 

[mwidjaya]

Quick update on my 2012 macmini6,1.

Did the OTA to 11.4 today. Went perfectly.

Also updated OCLP to latest release 0.1.5 just before triggering the OTA. All good.

 

[xanderon]

and paniced/crashed again…

fresh 11.4 with OCLP 0.1.5 without Fusion Drive, clean install with time machine restore to just one 1tb ssd
13 ram tests memtest86 booted from usb went through without errors,
metalbench and yes terminal stress test on CPU and GPU were also stable.

its very random

panic(cpu 2 caller 0xffffff800f69f846): [ipc kmsgs]: element modified after free (off:136, val:0x0000080000000000, sz:256, ptr:0xffffff86cfc82e00, prot:zero)
  136: 0x0000080000000000
Backtrace (CPU 2), Frame : Return Address
0xffffffa08e8035f0 : 0xffffff800ee8e0dd mach_kernel : _handle_debugger_trap + 0x3fd
0xffffffa08e803640 : 0xffffff800efd4f33 mach_kernel : _kdp_i386_trap + 0x143
0xffffffa08e803680 : 0xffffff800efc552a mach_kernel : _kernel_trap + 0x55a
0xffffffa08e8036d0 : 0xffffff800ee32a2f mach_kernel : _return_from_trap + 0xff
0xffffffa08e8036f0 : 0xffffff800ee8d8fd mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffa08e803810 : 0xffffff800ee8dbf3 mach_kernel : _panic_trap_to_debugger + 0x273
0xffffffa08e803880 : 0xffffff800f69d81a mach_kernel : _panic + 0x54
0xffffffa08e8038f0 : 0xffffff800f69f846 mach_kernel : _kheap_temp_leak_panic + 0x1b7c
0xffffffa08e803d70 : 0xffffff800eeecad6 mach_kernel : _work_interval_port_type_render_server + 0x4446
0xffffffa08e803de0 : 0xffffff800ee697f7 mach_kernel : _ipc_kmsg_get + 0x187
0xffffffa08e803e60 : 0xffffff800ee81224 mach_kernel : _mach_msg_overwrite_trap + 0x1e4
0xffffffa08e803ef0 : 0xffffff800efa982d mach_kernel : _mach_call_munger64 + 0x29d
0xffffffa08e803fa0 : 0xffffff800ee33216 mach_kernel : _hndl_mach_scall64 + 0x16

Process name corresponding to current thread: WindowServer
Boot args: keepsyms=1 debug=0x100 chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
20F71

Kernel version:
Darwin Kernel Version 20.5.0: Sat May  8 05:10:33 PDT 2021; root:xnu-7195.121.3~9/RELEASE_X86_64
Kernel UUID: 52A1E876-863E-38E3-AC80-09BBAB13B752
KernelCache slide: 0x000000000ec00000
KernelCache base:  0xffffff800ee00000
Kernel slide:      0x000000000ec10000
Kernel text base:  0xffffff800ee10000
__HIB  text base: 0xffffff800ed00000
System model name: iMac12,2 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 8987354653729
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x0000082c8814ecf3
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x0000001da4d132da 0x0000000000000000

 

[Orange24]

Hi there,

first of all, thank you very much for the great opportunity to install Big Sur 11.4 on my MBP 6,2.

You are doing a really great job!

Today I have upgraded my 15' Mid 2010 MBP with OCLP 0.1.5. So far, so good.

But unfortunately the Graphics Acceleration Patch does not work because the error message (Fig. 1 - 3) always appears. The shown link also doesn't work.

Could someone help me please? Many Thanks in advance

 

[massimodl]

Hi Folks, I hope you can help me. I have an early 2013 MacBook Pro 15 Retina. I have even "upgraded" the internal wi-fi card with one compatible with Big Sur. I have installed Big Sur without any issues. I simply avoided to run the post install process since I actually don't need it, my Wi-Fi works just fine. Yesterday I have done the upgrade to the latest version of Big Sur using the "Run update" procedures of "Patched Sur" and I am afraid that this time the "Patch kexts" procedure has been executed automatically. In fact I have some minor glitches with the bluetooth that I didn't have previously. The bt keyboard and headset get disconnected very often. Also the bt mouse sometimes seems freezing for few seconds.
So my question is: is there a way to check if the patched kexts have been installed and, if so, is there a way to remove them safely?

Thanks a lot

Massimo

 

[Ausdauersportler]

Hi there,

first of all, thank you very much for the great opportunity to install Big Sur 11.4 on my MBP 6,2.

You are doing a really great job!

Today I have upgraded my 15' Mid 2010 MBP with OCLP 0.1.5. So far, so good.

But unfortunately the Graphics Acceleration Patch does not work because the error message (Fig. 1 - 3) always appears. The shown link also doesn't work.

Could someone help me please? Many Thanks in advance

You possibly have to move to the most recent development version.

Nightly builds can be found here courteous of nightly.link: Nightly OpenCore-Patcher.app
The current payload version seems to be 0.0.8 not 0.0.7.

 

[Ausdauersportler]

Hi Folks, I hope you can help me. I have an early 2013 MacBook Pro 15 Retina. I have even "upgraded" the internal wi-fi card with one compatible with Big Sur. I have installed Big Sur without any issues. I simply avoided to run the post install process since I actually don't need it, my Wi-Fi works just fine. Yesterday I have done the upgrade to the latest version of Big Sur using the "Run update" procedures of "Patched Sur" and I am afraid that this time the "Patch kexts" procedure has been executed automatically. In fact I have some minor glitches with the bluetooth that I didn't have previously. The bt keyboard and headset get disconnected very often. Also the bt mouse sometimes seems freezing for few seconds.
So my question is: is there a way to check if the patched kexts have been installed and, if so, is there a way to remove them safely?

Thanks a lot

Massimo

Good luck! We had and have barely users of Patched Sur here. You should move to Ben‘s Discord channel. There you possible find help faster.

From my work on the micropatcher I would say it is better to reinstall the latest version of Big Sur on top of your current one to get a clean installation again.

 

[Orange24]

Good luck! We had and have barely users of Patched Sur here. You should move to Ben‘s Discord channel. There you possible find help faster.

From my work on the micropatcher I would say it is better to reinstall the latest version of Big Sur on top of your current one to get a clean installation again.

 

[Orange24]

You possibly have to move to the most recent development version.

Nightly builds can be found here courteous of nightly.link: Nightly OpenCore-Patcher.app
The current payload version seems to be 0.0.8 not 0.0.7.

Many thanks for the quick response. That's exactly what I've already tried, but unfortunately with the same result. Is there possibly a terminal command that could be executed. Or can the Apple Binaries be installed manually via the terminal?

 

[massimodl]

Good luck! We had and have barely users of Patched Sur here. You should move to Ben‘s Discord channel. There you possible find help faster.

From my work on the micropatcher I would say it is better to reinstall the latest version of Big Sur on top of your current one to get a clean installation again.

I see, honestly I had lost latest news about Big Sur patchers. I read about the Patched Sur updates only recently. Do you suggest to go with OpenCore Legacy Patcher or there is other solution that would allow to manage "natively" OS updtes? (Also in my case I shouldn't need any patches, so I hope the procedure would allow me to choose to do it).

 

[StuBFrost]

Hi. Apologies if this has been posted before but I did a quick thread search but couldn't find anything.

I have a MacBook 5,1 and I have installed Big Sur 11.4 on an external SSD using OCLP and everthing seems fine except when I load maps and click search it will crash unless I quickly type a letter to limit the seatch. It seems to be if it fills the whole column of the search it crashes every time.

Stu

 

[Ausdauersportler]

I see, honestly I had lost latest news about Big Sur patchers. I read about the Patched Sur updates only recently. Do you suggest to go with OpenCore Legacy Patcher or there is other solution that would allow to manage "natively" OS updtes? (Also in my case I shouldn't need any patches, so I hope the procedure would allow me to choose to do it).

We had this discussion a while ago. Your type of system is a special case. Using the installation methods of micropatcher/Patched Sur you can use the unpatched image the Apple installer creates and live with it unless you want to install the next minor release. But installing this works only with the so called full installers when provided by Apple. The problem is that Apple stopped delivering those for Catalina with 10.7 last summer. The same will likely happen with Big Sur this Summer and the update story of Patched Sur ends (same will happen with micropatcher).

Using OCLP your system gets a new identity (of a still supported Mac) and your can install and update using the normal Apple software update process. On the other hand some corrections have to be made because the new identity does not exactly fit with your older system.

All this works so well and the advantage of doing software updates and installations the same way as before made a lot of users give up other patcher solutions during the last 3 month.

Of course there a (Apple) bugs still visible even with OCLP - but honestly IMHO we have never had a better supported patcher.

OLCP is the only solution offering native OC updates unless you want do develop and maintain your own OpenCore based solution. I gave up following this approach half a year ago So I am not really objective when it comes to this question.

 

[Ausdauersportler]

Hi. Apologies if this has been posted before but I did a quick thread search but couldn't find anything.

I have a MacBook 5,1 and I have installed Big Sur 11.4 on an external SSD using OCLP and everthing seems fine except when I load maps and click search it will crash unless I quickly type a letter to limit the seatch. It seems to be if it fills the whole column of the search it crashes every time.

Stu

Known issue. Search back this thread with keyword Maps.

 

[massimodl]

We had this discussion a while ago. Your type of system is a special case. Using the installation methods of micropatcher/Patched Sur you can use the unpatched image the Apple installer creates and live with it unless you want to install the next minor release. But installing this works only with the so called full installers when provided by Apple. The problem is that Apple stopped delivering those for Catalina with 10.7 last summer. The same will likely happen with Big Sur this Summer and the update story of Patched Sur ends (same will happen with micropatcher).

Using OCLP your system gets a new identity (of a still supported Mac) and your can install and update using the normal Apple software update process. On the other hand some corrections have to be made because the new identity does not exactly fit with your older system.

All this works so well and the advantage of doing software updates and installations the same way as before made a lot of users give up other patcher solutions during the last 3 month.

Of course there a (Apple) bugs still visible even with OCLP - but honestly IMHO we have never had a better supported patcher.

OLCP is the only solution offering native OC updates unless you want do develop and maintain your own OpenCore based solution. I gave up following this approach half a year ago So I am not really objective when it comes to this question.

Thanks for your reply. Kinda helpful, I will try to install again Big Sur on top of this installation with the OLCP (it's on an external drive, I still have Mojave on the internal disk... I will switch once the procedure will allow me to be safe).

Thanks again!

 

[StuBFrost]

Known issue. Search back this thread with keyword Maps.

I did do a search but didn’t see that post for some reason. Thanks for the link.

 

[Ausdauersportler]

I did do a search but didn’t see that post for some reason. Thanks for the link.

The search engine used is not as sophisticated as the one we know from the big net. You have most success with single keyword searches.

 

[marcel151]

Hi, I got problems while patching kexts on my MBP 2012 with PatchedSur v0.2.1, tried to patch kext from Install Media, same issue.

-bash-3.2# /Volumes/Image\ Volume/patch-kexts.sh /Volumes/Macintosh\ SSD
No WiFi option specified on command line, so checking for 802.11ac...
No 802.11ac WiFi card detected, so installing mojave-hybrid WiFi patch.
No patch mode specified on command line. Detecting Mac model...
(Use --2010, --2011, or --2012 command line option to override.)
Detected model: MacBookPro9,1
Detected a 2012-2013 Mac. Using --2012 patch mode.
Installing kexts to:
/Volumes/Macintosh SSD

Volume appears to have a Big Sur installation (build 20F71). Continuing.
Volume is mounted from device:  /dev/disk1s5
Mounted device is an actual volume, not a snapshot. Proceeding.
System Integrity Protection is off.
Restart the machine for the changes to take effect.
Successfully disabled authenticated root.
Restart the machine for the changes to take effect.
Remounting volume as read-write...
Checking for KernelCollections backup...
Backup not found. Performing backup now. This may take a few minutes.
Backing up original KernelCollections to:
/Volumes/Macintosh SSD/System/Library/KernelCollections/KernelCollections-20F71.tar.lz4
a BootKernelExtensions.kc
a SystemKernelExtensions.kc
Beginning patched IO80211Family.kext installation
Installing mojave-hybrid WiFi patch
Using kmutil to rebuild boot collection...
Error returned: <dictionary: 0x7fff870535d0> { count = 1, transaction: 0, voucher = 0x0, contents =
    "XPCErrorDescription" => <string: 0x7fff87053738> { length = 18, contents = "Connection invalid" }
}
Error returned: <dictionary: 0x7fff870535d0> { count = 1, transaction: 0, voucher = 0x0, contents =
    "XPCErrorDescription" => <string: 0x7fff87053738> { length = 18, contents = "Connection invalid" }
}
Error returned: <dictionary: 0x7fff870535d0> { count = 1, transaction: 0, voucher = 0x0, contents =
    "XPCErrorDescription" => <string: 0x7fff87053738> { length = 18, contents = "Connection invalid" }
}
Using kmutil to rebuild system collection...
Error returned: <dictionary: 0x7fff870535d0> { count = 1, transaction: 0, voucher = 0x0, contents =
    "XPCErrorDescription" => <string: 0x7fff87053738> { length = 18, contents = "Connection invalid" }
}
Error returned: <dictionary: 0x7fff870535d0> { count = 1, transaction: 0, voucher = 0x0, contents =
    "XPCErrorDescription" => <string: 0x7fff87053738> { length = 18, contents = "Connection invalid" }
}
Error returned: <dictionary: 0x7fff870535d0> { count = 1, transaction: 0, voucher = 0x0, contents =
    "XPCErrorDescription" => <string: 0x7fff87053738> { length = 18, contents = "Connection invalid" }
}
Error Domain=KMErrorDomain Code=71 "Unable to resolve dependencies: 'com.apple.driver.AppleIntelFramebufferAzul' names a dependency on 'com.apple.AppleGraphicsDeviceControl', which was not found." UserInfo={NSLocalizedDescription=Unable to resolve dependencies: 'com.apple.driver.AppleIntelFramebufferAzul' names a dependency on 'com.apple.AppleGraphicsDeviceControl', which was not found.}
kmutil failed. See above output for more information.
patch-kexts.sh cannot continue.

Any suggestions?

 

[Ausdauersportler]

Many thanks for the quick response. That's exactly what I've already tried, but unfortunately with the same result. Is there possibly a terminal command that could be executed. Or can the Apple Binaries be installed manually via the terminal?

Open an issue on the OCLP GitHub page. One can (could in the past) manually set the download path which has been regularly published on Discord (in the past).

 

[KennyW]

Updating my iMac11,3 with AMD RX480 and BCM943602CDP to 11.4 via software update was quite a journey. Needed several forced reboots to get id done.

View attachment 1781207

OCLP 0.1.5, minimal spoofing

Edit: Same with Late 2009, WX4150, stock BT. A single forced reboot necessary after this screen came up.

View attachment 1781234

Got my iMac 2010 with RX480 updated from BS 11.2.3 directly to 11.4.



A bumpy road.
The BS 11.2.3 was installed with help of OCLP 0.1.2 on an SD card, which was later updated to OCLP 0.1.5.
With OCLP 0.1.5, I created an USB BS Installer of 11.3.1 initially and later 11.4, but both cannot upgrade my BS due to hanging in middle of 2nd stage of installation (running the mac OS Installer). Despite multiple reboot, it just couldn't pass thru the second stage.
Finally, to see what is causing the problem, I enabled the verbose mode of OCLP 0.1.5. Surprisingly, as the texts flew thru on screen, I could see the 2nd stage installation with an Apple icon above a display of time to finish (~27 minutes) with count down which was absent in prior reboots. However, it finished with a stop sign and messing up the text display on screen.



I thought it failed and swapped out the SD card of OCLP 0.1.5 with verbose mode ON to one with OC 0.6.8 from the older days of using iMac Micropatcher to install Big Sur 11.1. I got my second surprise that the system booted smoothly to 11.4 ! I then rebuilt the OCLP 0.1.5 (AMD with minimal SMBIOS patch and full SIP & SecureBoot) with verbose OFF and exchanged with the OC 0.6.8. Everything still works fine. What a puzzle ....

 

[K two]

Should the OpenCore Patcher be granted Full Disk Access in the Security&Privacy CP? Nothing found re-reading extensive docs. 🧐