macOS 11 Big Sur on Unsupported Macs Thread

[jackluke]

@jackluke it seems to me that your prelinked kernel fix for Beta 3 doesn't work anymore on beta 5 (Mac Mini 2010) ... Could you check and update it, if obsolete? (And it would be nice if it could also be launched from Catalina). Thank you!

Starting from BigSur beta 5 "patched prelinkedkernel" no longer works, I get "namespace kernel panic" so can't reproduce a prelinkedkernel fix for legacy USB penryn and ivy bridge mac.

Anyway BootKernelExtensions.kc still works for recent USB Mac and any kext patches (telemetry plugin, wifi, sound), so use this: https://github.com/barrykn/big-sur-micropatcher

to remove the prelinkedkernel fix use this: BigSur generic BKE.command.zip

 

[Alex-Microsmeta]

Starting from BigSur beta 5 "patched prelinkedkernel" no longer works, I get "namespace kernel panic" so can't reproduce a prelinkedkernel fix for legacy USB penryn and ivy bridge mac.

Anyway BootKernelExtensions.kc still works for recent USB Mac and any kext patches (telemetry plugin, wifi, sound), so use this: https://github.com/barrykn/big-sur-micropatcher

to remove the prelinkedkernel fix use this: BigSur generic BKE.command.zip

Thank you! I have managed to boot using hax3 + OpenCoreLoader4, but no wifi, usb, ethernet, internal audio and acceleration. Next time I try micropatcher.

 

[EdGlassgow]

In case it's somehow CPU related, it might be worth posting the CPU model. Run this command:
sysctl -n machdep.cpu.brand_string
then copy-and-paste the ENTIRE output of that command (it should be 1 line of text), and post it here.

Edit: In case it wasn't clear, this is directed at everyone with a MacPro5,1 or flashed 4,1. Maybe some pattern will show up in the data... maybe. This is currently my best stab-in-the-dark for trying to figure out what might be going on here.

Here is mine....

Intel(R) Xeon(R) CPU X5690 @ 3.47GHz

I am having the bootloop issue

I have installed a previous version of Big Sur using a previous version of MicroPatcher on this machine, just so you know

 

[thatsmeonlyme]

Starting from BigSur beta 5 "patched prelinkedkernel" no longer works, I get "namespace kernel panic" so can't reproduce a prelinkedkernel fix for legacy USB penryn and ivy bridge mac.

Anyway BootKernelExtensions.kc still works for recent USB Mac and any kext patches (telemetry plugin, wifi, sound), so use this: https://github.com/barrykn/big-sur-micropatcher

to remove the prelinkedkernel fix use this: BigSur generic BKE.command.zip

So I think my MID 2012 MBP will not be upgraded to DP5. With your prelinkedkernel Kernel, all is working fine, better then under Catalina.

 

[jackluke]

Thank you! I have managed to boot using hax3 + OpenCoreLoader4, but no wifi, usb, ethernet, internal audio and acceleration. Next time I try micropatcher.

Right, because with USBOpenCoreAPFSloader4 I forced to use BootKernelExtensions.kc rather than prelinkedkernel, also legacy USB Mac could boot with CMD+S and "exit", anyway to get Wifi, Sound and other features you need the micropatcher because it installs the kext through making a new snapshot, otherwise if you could use "sudo mount -uw /" kext replacing is much more easier, I updated previous beta 4 using the skipping of stage3 installer and it worked to disable "snapshot booting".

So I think my MID 2012 MBP will not be upgraded to DP5. With your prelinkedkernel Kernel, all is working fine, better then under Catalina.

Currently can't get it to work on beta 5 , I also encountered issues in making a beta 4 prelinkedkernel, that's why I used a beta 3 fix.

You can use micropatcher for that machine.

 

[nandor690]

In case it's somehow CPU related, it might be worth posting the CPU model. Run this command:
sysctl -n machdep.cpu.brand_string
then copy-and-paste the ENTIRE output of that command (it should be 1 line of text), and post it here.

Edit: In case it wasn't clear, this is directed at everyone with a MacPro5,1 or flashed 4,1. Maybe some pattern will show up in the data... maybe. This is currently my best stab-in-the-dark for trying to figure out what might be going on here.

I’m using a W3690 in a 2009 Mac Pro. Beta 1 would get in a boot loop sometimes. But beta 2 and 3 installed multiple times just fine. Beta 4 did install, but after trying to reinstall again it will get stuck in a boot loop after the first restart while trying to install. Haven’t been able to fix it. I tried older micropatchers too.
if I boot verbose it seems like it does everything it suppose too. And then switches to the Apple logo screen. The bar will load for a second and just when it’s about to start the install again and give you a “time remaining” is when it will restart.
i haven’t messed with it all week. I’ll see if I can get the Install partition to mount in Catalina to get logs off of it. That was another problem I was having.

 

[RITAMA]

Work Ok !!
TQ @Barry K Nathan
i'm using your Micropatcher 0.10
on MBP mid 2012 13" to install BS DP5

 

[IbrahimFmc]

DP5 Not shown as ota update on mid 2012 Mac OS Big Sur (20A5343i), is it require manual update ?

 

[Fran Frin]

@Barry K. Nathan

Successfully clean installed beta5 on MacBook 2010 White with big-sur-micropachter version 0.10. Great! only a little sluggish since no acceleration.

View attachment 945892

I have MacBook Pro mid 2009, very similar to this, step do you do to install?? Thanks

 

[startergo]

So for some reason Barry's micropatcher's Install USB was just rebooting and it would not proceed. After resetting the NVRAM it worked. I had SIP disabled before so that could have prevented the USB from running.

 

[thatsmeonlyme]

Work Ok !!
TQ @Barry K Nathan
i'm using your Micropatcher 0.10
on MBP mid 2012 13" to install BS DP5

what about Airdrop / Handoff? Working ?

 

[Joonyv]

MacBook Air 2012 successfully installed with Barry's micropatcher's.
One question, this machine supports Continuity on Catalina. Now that WiFi is working with that patch, why isn’t continuity supported unde a Big Sur. Thanks

 

[Barry K. Nathan]

So for some reason Barry's micropatcher's Install USB was just rebooting and it would not proceed. After resetting the NVRAM it worked. I had SIP disabled before so that could have prevented the USB from running.

Disabling SIP sure doesn't do that on other Mac models!

Are you saying that the install USB itself was rebooting before it could finish booting normally (and then was able to boot after resetting NVRAM), or are you saying that it would get stuck in a boot loop during the installation process? The latter is what most of the MacPro4,1/5,1 issues have been, but if it's the former, that's really weird and I'll need to think about the possible implications.

 

[startergo]

or are you saying that it would get stuck in a boot loop during the installation process? The latter is what most of the MacPro4,1/5,1 issues have been

Well it is a reboot loop but it starts right after the USB is selected followed by a black screen and a reboot. it is on cMP5,1 and I could only proceed after NVRAM reset.

 

[Barry K. Nathan]

MacBook Air 2012 successfully installed with Barry's micropatcher's.
One question, this machine supports Continuity on Catalina. Now that WiFi is working with that patch, why isn’t continuity supported unde a Big Sur. Thanks

Which version of the micropatcher did you use? And which Continuity feature(s) failed? (For a list of Continuity features, you can look at this Apple support article.)

 

[startergo]

@Barry K. Nathan I left it alone during installation and when I came back the system was shut down. I restarted, but it now stops at the forbidden sign of the installer.

 

[Barry K. Nathan]

@Barry K. Nathan I left it alone during installation and when I came back the system was shut down. I restarted, but it now stops at the forbidden sign of the installer.

Start up from the installer USB, run set-vars.sh, then reboot and see if installation is able to proceed further.

 

[scans]

I have a Macbook Pro 2009 13" (5,5, Core 2 Duo) with 8GB RAM and a 480GB SSD running Catalina beautifully using DosDude's patcher (although the CPU runs hot requiring iStat to run the fans to cool it). Have also put Catalina on many other older machines the same way, without any issues.

However, I have been trying unsuccessfully to get Big Sur on my machine, trying Barry's micropatcher on each release, each BS beta release, and even following some of the others who have reported success.

I've hit many roadblocks. I figure it is something simple I am not doing, but maybe someone can confirm.

1) Should I make a new APFS container or partition? Or should I use a new internal SSD?
2) The machine already uses APFS patched ROM to boot that came with DosDude's patcher. Is that a problem? I can't see any other APFS bootable volume in the System Setting panel. Booting with option held down often only shows the EFI volume, and not any other container or partition.
3) When I have tried booting from a USB installer (Barry's item #4) (holding OPTION at boot and selecting) the apple logo shows, there's some flashing of the LED on the USB drive, then nothing for 20 seconds, and eventually, a big grey circle with a line through it ("forbidden" - the firmware telling me there is no compatible system on the drive). Same thing with using a Samsung T5 SSD USB.
4) When I use the Hax3 patcher (so that it will allow me to install the unmodified BS beta on any drive) to install to another partition/container or on the T5 SSD (figuring I can apply the kexts later), it will spend 10 minutes copying files, and then prompt to reboot. But if I reboot, it goes back into my Catalina EFI boot. If I hold OPTION, I do not see the new volume (which is now APFS).

I have read through dozens of posts, but maybe I missed something about installing on top of a machine already using the patched ROM by DosDude?

I appreciate any suggestions by anyone who was successful on the MacBookPro 5,x models.

 

[Joonyv]

Which version of the micropatcher did you use? And which Continuity feature(s) failed? (For a list of Continuity features, you can look at this Apple support article.)

Handoff says not supported under Bluetooth details. Used the latest version of the patcher.

 

[thatsmeonlyme]

DP5 Not shown as ota update on mid 2012 Mac OS Big Sur (20A5343i), is it require manual update ?

as you are working on an unsupported machine SW update will everytime show you to be up to date

 

[Bruno Berchielli]

Is it possible to update an Beta 4 install to Beta 5 via USB?
Or is a clean install mandatory?

rMBP 15 mid-2012 with upgraded wifi card

 

[IbrahimFmc]

as you are working on an unsupported machine SW update will everytime show you to be up to date

Thank you very much for your kindly reply

 

[startergo]

Start up from the installer USB, run set-vars.sh, then reboot and see if installation is able to proceed further.

So I started the installation from scratch and I saw it rebooting around 12th minute remaining. It stopped at the forbidden sign and shut down. Then I rebooted to the installer and re-executed the set-vars.sh script, but it still stops at the forbidden sign. Then I continued the installation through OC.

 

[lowercaseman]

Then I continued the installation through OC.

Forgive me but what does "OC" mean?

 

[startergo]

Forgive me but what does "OC" mean?

OpenCore boot loader