macOS 11 Big Sur on Unsupported Macs Thread

[justperry]

These cards are wifi n, not wifi ac. What is the difference with the original card of the MBP mid 2012 ?

The second one does have AC.
It's supported, the original is not.

https://www.amazon.com/Broadcom-Bcm94360cs-Bcm94360csax-Bluetooth-Wireless/dp/B00PDN4H9E

 

[Apple-is-Cool]

I just installed Beta 6 on my MacPro5,1 and updated to Beta 8 w/OpenCore 0.6.1. Previously running Catalina 10.15.7. Apple Watch unlocking is working too to my surprise. The only thing that is broken right now is DRM for tv shows/movies.

 

[Alex-Microsmeta]

About Penryn Core2Duo Legacy USB and non-APFS Mac, I patched a beta 8 BaseSystem.dmg and it still works with my BaseSystem Legacy USB fix (so this eventually could be used as BigSur Recovery for non-APFS Mac), but to continue the staged installer is required USBopencore and a replacement of patched BKE on these paths:

/APFS Data Volume/macOS Install Data/Locked Files/BootKernelExtensions.kc
/APFS Data Volume/boot/BootKernelExtensions.kc
/APFS Preboot/UUIDBigSur/boot/System/Library/KernelCollections/BootKernelExtensions.kc

Thanks to @ASentientBot method downgrading the beta 6 kernel and an updated version of usbopencore I was able to boot with CMD+S and exit on a non-APFS Mac (legacy USB) the beta 8 through an external USB SSD installation .

I uploaded the patched BKE that embeds beta 8 extensions and beta 6 kernel here: https://github.com/jacklukem/BigSurfixes/tree/master/penryn c2d bigsur beta6

because a beta 6 kernel is required to boot BigSur with Penryn Core2Duo.

Meanwhile I attach the updated usbopencore that is not for spoofing or OTA updates, but mainly to inject some legacy kext on the BootKernelExtensions.kc still experimental and legacy USB booting works only with CMD+S and exit (stock Recovery 11.0 beta 6 also works, I'd advise to keep a beta 6 BaseSystem.dmg copy).

To use the bootloader simply copy the EFI folder to any FAT32 formatted volume, then reboot with alt-option key and select EFI Boot.

Thank you! Very interesting as always

 

[sinbad21]

The second one does have AC.
It's supported, the original is not.

Thank you. Unfortunately none of the two cards are supported by the MBP mid 2012. I have read your post too fast.

 

[telepati]

BTW using different csr-config giving a different error number. Does anyone realize that?

In general, we are getting 66 but when I try to 67000000 then I got 77. is that mean if we can find the correct csr we can pass the disk read/write?

Note: I know this is a stupid idea. ?

 

[Ausdauersportler]

I just installed Beta 6 on my MacPro5,1 and updated to Beta 8 w/OpenCore 0.6.1. Previously running Catalina 10.15.7. Apple Watch unlocking is working too to my surprise. The only thing that is broken right now is DRM for tv shows/movies.

View attachment 960677

DRM broke with beta 6 on my iMac with RX560...spoofing iMacPro 1,1 etc...before it worked. Guess we have to check the modifications at the usual suspects

 

[startergo]

BTW using different csr-config giving a different error number. Does anyone realize that?

In general, we are getting 66 but when I try to 67000000 then I got 77. is that mean if we can find the correct csr we can pass the disk read/write?

Note: I know this is a stupid idea. ?

SIP codes:

OpenCorePkg/Include/Apple/IndustryStandard/AppleCsrConfig.h at 42c7e8a69f792e8fef2ad5da843d1406eed8d536 · acidanthera/OpenCorePkg

OpenCore bootloader. Contribute to acidanthera/OpenCorePkg development by creating an account on GitHub.

github.com

GitHub - corpnewt/CsrDecode: Small py script to show what different CsrActiveConfig values enable/disable

Small py script to show what different CsrActiveConfig values enable/disable - corpnewt/CsrDecode

github.com

 

[startergo]

DRM broke with beta 6 on my iMac with RX560...spoofing iMacPro 1,1 etc...before it worked. Guess we have to check the modifications at the usual suspects

OpenCore and macOS 11: Big Sur | OpenCore Install Guide

With Big Sur, quite a bit broke. Mainly the following:

• Lilu
  • Mainly user-space patching ( dyld_shared_cache ) has severely broke, meaning certain patches like DRM don't work

 

[buckrock]

Thank you. Unfortunately none of the two cards are supported by the MBP mid 2012. I have read your post too fast.

Just to clarify, the MacBook Pro (10,1) mid-2012 Retina is the A1398. It certainly supports the Broadcom bcm4360 card (802.11ac). That is the card in my MBP right now!

 

[eminemmm]

The patched boot.efi possibility occurred to me after my last post, and in retrospect I should've asked about it.

However, I had RAM problems of a similar magnitude on my own MacBookPro8,1 and MacBook7,1 last year, so I know that it would not "result in a non-booting system for sure". I only got weird stuff like this happening once every 2 months or less, and I never seemed to have any filesystem corruption (at least not to the point that Disk Utility/fsck could detect on APFS). Nonetheless, Apple Hardware Test and memtest86+ would both consistently fail the RAM; swapping in different RAM modules fixed it, and Crucial replaced the defective RAM under warranty. I have seen similar RAM problems on many Macs and PCs over the years (including at a past job where I was an admin of 200+ systems, so not just personal systems). I've seen the effects of bad RAM bit flips too many times on too many almost-but-not-quite-100%-working computers over too long a period of time to not believe it is the most likely possibility (at least aside from a patched boot.efi).

Having said that, now that I've slept and am thinking more clearly, "most likely possibility" (which I could still be mistaken about, for that matter) doesn't come anywhere near proving it, and I absolutely overreacted. I did make a leap that went too far. (And there is also a flaw in patch-kexts.sh which I should try to fix at some point.)

@eminemmm So did you install a patched boot.efi? Either way, for now I'll proceed assuming the RAM is good -- ASentientBot is right that it's likely and I shouldn't dismiss it out of hand. At some point it would still be good to run memtest86+ and see whether it finds anything wrong. (In my case I usually run it by booting up an old Ubuntu Linux DVD, but later today I'll figure out again how to do it without an old Linux DVD lying around and I'll provide brief instructions.)

Still here waiting to try new solutions.
i don’t know if I’m using custom boot.efi because I don’t I’m understand how can I do that. Tell me please if you want me to try anything , I really want to use my MacBook Pro 8.1 again

 

[Caeed]

I just installed Beta 6 on my MacPro5,1 and updated to Beta 8 w/OpenCore 0.6.1. Previously running Catalina 10.15.7. Apple Watch unlocking is working too to my surprise. The only thing that is broken right now is DRM for tv shows/movies.

View attachment 960677

Hello
I have a question
How to install Beta 8 on this MacBook
I have 2011
But I do not find the beta 8 link everywhere I look
And I can not do a direct update and it gives an error
Thank you for your help

 

[Barry K. Nathan]

Hello
I have a question
How to install Beta 8 on this MacBook
I have 2011
But I do not find the beta 8 link everywhere I look
And I can not do a direct update and it gives an error
Thank you for your help

I just did it on my own Early 2011 13" MacBook Pro. Basically, I did the following:

• If you used patch-kexts.sh, reinstall beta 6 and avoid patch-kexts.sh until after beta 8 is installed. (I avoided patch-kexts.sh from the beginning for this Big Sur installation.)
• Since without patch-kexts.sh neither built-in Ethernet nor WiFi will function, you will need a USB Ethernet adapter. Plug it in now.
• Boot up using @jackluke's USBopencore (hopefully that's the right name) thing (it spoofs the model ID so Software Update thinks you have a supported Mac).
• Run sudo softwareupdate -da in Terminal to download the update (it also does at least some of the filesystem verification at the same time). This will take a while.
• Once it's done, go to System Preferences->Software Update, let it check for updates (it won't take long), then click "Update Now" or whatever the button says. In a few seconds, a notification will pop up saying that the computer will restart in 60 seconds (it counts down). Go ahead and click the Restart button in the notification.
• The computer will restart several times during the update. Stay with the computer the whole time, and with each reboot, make sure to hold down the Option key and choose the USBopencore USB stick, then: If there is a "macOS Installer" volume, boot from that, otherwise boot from Preboot.
• Eventually the computer will display time remaining (maybe something like "30 minutes remaining"). At that point, it will not reboot again, so you can leave the computer alone and do other stuff. At least if you have an SSD, it will complete in well under 30 minutes at that point. Once it is done, the Mac will be at the login prompt. Log in and Setup Assistant will start up, and eventually crash because Siri needs a Metal GPU (but you can just log in a second time and then things will work).
• I guess now you can boot from the EFI Boot partition of the patched installer USB (EDIT: Seriously, you will get a prohibited/no-entry sign if you don't do that!), then boot from the other partition of the patched installer USB (or boot like normal), and run patch-kexts.sh. I have not personally tested this last part yet.

I think it is likely that another beta will be released soon, so it would be easiest to just wait. However, if you really want to try the new beta, this is how I did it. (Also, I installed using my patcher as normal, so this was with an unsealed volume. So it looks like it's not necessary for the volume to be sealed in order for the delta update installation to succeed.)

By the way, my attempts to make (un)patch-kexts.sh work better failed. I ended up with an unpatch-kexts.sh which is able to satisfy Apple's filesystem verification but which somehow causes the Installer to (as far as I can tell) massively corrupt the filesystem. And this has happened on 2 out of 2 attempts so far -- it seems like I can do it at will. Edit: I actually managed to fix the corruption problem, so I now have implementations of patch-kexts.sh and unpatch-kexts.sh where running unpatch-kexts.sh before a delta updater is sufficient, no need to do the full installer first! I'll probably release it in the next day or so.

 

[Caeed]

I just did it on my own Early 2011 13" MacBook Pro. Basically, I did the following:

• If you used patch-kexts.sh, reinstall beta 6 and avoid patch-kexts.sh until after beta 8 is installed. (I avoided patch-kexts.sh from the beginning for this Big Sur installation.)
• Since without patch-kexts.sh neither built-in Ethernet nor WiFi will function, you will need a USB Ethernet adapter. Plug it in now.
• Boot up using @jackluke's USBopencore (hopefully that's the right name) thing (it spoofs the model ID so Software Update thinks you have a supported Mac).
• Run sudo softwareupdate -da in Terminal to download the update (it also does at least some of the filesystem verification at the same time). This will take a while.
• Once it's done, go to System Preferences->Software Update, let it check for updates (it won't take long), then click "Update Now" or whatever the button says. In a few seconds, a notification will pop up saying that the computer will restart in 60 seconds (it counts down). Go ahead and click the Restart button in the notification.
• The computer will restart several times during the update. Stay with the computer the whole time, and with each reboot, make sure to hold down the Option key and choose the USBopencore USB stick, then: If there is a "macOS Installer" volume, boot from that, otherwise boot from Preboot.
• Eventually the computer will display time remaining (maybe something like "30 minutes remaining"). At that point, it will not reboot again, so you can leave the computer alone and do other stuff. At least if you have an SSD, it will complete in well under 30 minutes at that point. Once it is done, the Mac will be at the login prompt. Log in and Setup Assistant will start up, and eventually crash because Siri needs a Metal GPU (but you can just log in a second time and then things will work).
• I guess now you can boot from the EFI Boot partition of the patched installer USB, then boot from the other partition of the patched installer USB (or boot like normal), and run patch-kexts.sh. I have not personally tested this last part yet.

I think it is likely that another beta will be released soon, so it would be easiest to just wait. However, if you really want to try the new beta, this is how I did it. (Also, I installed using my patcher as normal, so this was with an unsealed volume. So it looks like it's not necessary for the volume to be sealed in order for the delta update installation to succeed.)

By the way, my attempts to make (un)patch-kexts.sh work better failed. I ended up with an unpatch-kexts.sh which is able to satisfy Apple's filesystem verification but which somehow causes the Installer to (as far as I can tell) massively corrupt the filesystem. And this has happened on 2 out of 2 attempts so far -- it seems like I can do it at will.

I do not know how to forge my Mac series
Can you share the full tutorial?

 

[Caeed]

I uploaded my opencore EFI folder (also updated to 0.6.1) to spoof a supported BigSur Mac in order to detect OTA updates: USBOpencore4s1

to make it working simply copy the EFI folder to any FAT32 formatted volume, at reboot hold alt-option key to select it from the apple startup manager.

But as I wrote a snapshot booting (and sealed system) is required to complete the OTA update properly.

I did that
But I get this error again

 

[Barry K. Nathan]

I do not know how to forge my Mac series
Can you share the full tutorial?

This post might help.

If that's not enough information for you to figure it out, then just wait for the next beta (which will hopefully have a full installer).

 

[Barry K. Nathan]

Still here waiting to try new solutions.
i don’t know if I’m using custom boot.efi because I don’t I’m understand how can I do that. Tell me please if you want me to try anything , I really want to use my MacBook Pro 8.1 again

I'll get to this as soon as I can, but it might not be for a couple more days. Other things are taking me longer than I had hoped. Sorry -- I'm trying.

 

[Husseinabd40]

Try this:
https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28948321

I have tried to follow the instructions. When I am executing kmutil install --update-all , it shows that it failed to build release collection, as shown

When I boot with USBopencore, I stuck with apple logo

kindly, any suggestion ?

 

[Caeed]

This post might help.

If that's not enough information for you to figure it out, then just wait for the next beta (which will hopefully have a full installer).

If it was a joke, it would not be funny
The operating system crashed after doing so
And a cross replaced the Apple logo when it arrived
Whatever I did, the problem was not solved and
All data and operating system were deleted
I reinstalled and tried again, it was the same problem again

 

[eikic1]

how to update Bigsure on MacPro5,1 2012
i try but error, i try with bootable disk, successfully update but not detect on Open Core
thanks b4

 

[olad]

If it was a joke, it would not be funny
The operating system crashed after doing so
And a cross replaced the Apple logo when it arrived
Whatever I did, the problem was not solved and
All data and operating system were deleted
I reinstalled and tried again, it was the same problem again

I reckon you are new here. Which might explain why you come across as being a little less humble. Mr Nathan does what he does because - well - he does, freely, without recompense. He owes nobody anything, so if he points you in a certain direction and you are unable to find your way, you are not entitled to any explanations beyond what he gave. Kindly wait patiently until problems are solved. Nobody on this thread/forum has any obligations to you.

 

[thatsmeonlyme]

I reckon you are new here. Which might explain why you come across as being a little less humble. Mr Nathan does what he does because - well - he does, freely, without recompense. He owes nobody anything, so if he points you in a certain direction and you are unable to find your way, you are not entitled to any explanations beyond what he gave. Kindly wait patiently until problems are solved. Nobody on this thread/forum has any obligations to you.

@Caeed
all we are doing here is on our own responsibility. And if you have look at the first post and also to other ones you´ll see that there are warnings exactly to the possibility of such crashes. If @Barry K. Nathan gave you a hint or a link he is not joking. It is at you to work with try and error as anyone else does here. Have a ,look what you are doing wrong.

 

[jackluke]

I have tried to follow the instructions. When I am executing kmutil install --update-all , it shows that it failed to build release collection, as shown
View attachment 960835

When I boot with USBopencore, I stuck with apple logo
View attachment 960839

kindly, any suggestion ?

Regardless of that error, do you typed also kcditto before reboot to opencore ?

If you did and stuck there, then try this updated USBopencore: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28952250

 

[jackluke]

If it was a joke, it would not be funny
The operating system crashed after doing so
And a cross replaced the Apple logo when it arrived
Whatever I did, the problem was not solved and
All data and operating system were deleted
I reinstalled and tried again, it was the same problem again

You simply needed to set nvram boot-args="-no_compat_check" , or to use Barry Micropatcher current release booting from EFI Boot.

Anyway about deleted Data (that I doubt it has been really deleted), apple in their beta release notes stated clearly that installing BigSur should be done on a volume that you are prepared to erase any time, also they advise to use a separate APFS disk container.

In this beta with BigSur they changed many things, so it's very useful to keep at least Mojave or Catalina as bootable internal or external macOS .

Moreover I read that also many BigSur supported Mac had issues during installation or OTA updates, maybe because apple focused more on ARM than Intel cpu.

 

[Caeed]

@Caeed
all we are doing here is on our own responsibility. And if you have look at the first post and also to other ones you´ll see that there are warnings exactly to the possibility of such crashes. If @Barry K. Nathan gave you a hint or a link he is not joking. It is at you to work with try and error as anyone else does here. Have a ,look what you are doing wrong.

Big Sur was not my only operating system
And my information in Big Sur was not important
I'm upset about that
Maybe it was done as a joke
You are right and I went fast
And by the way, I used the micropatcher and I am very satisfied
But I do not know why I got into trouble here
But if I upset you, I apologize
[automerge]1601367335[/automerge]

You simply needed to set nvram boot-args="-no_compat_check" , or to use Barry Micropatcher current release booting from EFI Boot.

Anyway about deleted Data (that I doubt it has been really deleted), apple in their beta release notes stated clearly that installing BigSur should be done on a volume that you are prepared to erase any time, also they advise to use a separate APFS disk container.

In this beta with BigSur they changed many things, so it's very useful to keep at least Mojave or Catalina as bootable internal or external macOS .

Moreover I read that also many BigSur supported Mac had issues during installation or OTA updates, maybe because apple focused more on ARM than Intel cpu.

Big Sur was not my only operating system
And my information in Big Sur was not important
I'm upset about that
Maybe it was done as a joke
You are right and I went fast
And by the way, I used the micropatcher and I am very satisfied
But I do not know why I got into trouble here
But if I upset you, I apologize

 

[jackluke]

[automerge]1601367335[/automerge]
Big Sur was not my only operating system
And my information in Big Sur was not important
I'm upset about that
Maybe it was done as a joke
You are right and I went fast
And by the way, I used the micropatcher and I am very satisfied
But I do not know why I got into trouble here
But if I upset you, I apologize

No upset, even with a sealed system you can read and write BigSur Data Volume from another macOS, but my USBopencore setup might not be compatible for all machines, so better waiting for a full Big Sur beta installer.