macOS 11 Big Sur on Unsupported Macs Thread

[kuoshen]

Hi,

A big thank you to @Barry K. Nathan, @jackluke, @ASentientBot, @highvoltage12v , @testheit, @parrotgeek1 and @Ausdauersportler. My iMac 2011 with nVidia K2100M patched with Barry's micropatcher to run Big Sur 11.1 with OpenCore 0.6.3 (I have not upgraded yet to 0.6.4). Clean installed Big Sur 11.1 on new APFS volume. Migrated from 11.0.1 - macOS Setup Assistant copied all my files across to my new install of Big Sur 11.1 in about 15 mins.

Worked on the second try. Messed up on the first try, when I ran the patch-kexts.sh script too early, before macOS Setup Assistant started. Thought I had to patch-kexts before macOS Setup Assistant starts. Patched-kexts was successful (with the --useOC option) but when rebooted it went into an endless boot-loop with black screen.

On the second try, I waited until I got into macOS Setup Assistant. At the point it completed the migration (copying my files across from Big Sur 11.0.1 install), it rebooted. That's when I held down the Option key to boot back into "Install macOS Big Sur" and ran patch-kexts.sh script (with --useOC). When completed, I shutdown and restarted by booting into OpenCore 0.6.3 then my Big Sur 11.1 volume. Worked like a charm!

On my desktop, there is a "Relocated Items.nosync" folder. https://www.macrumors.com/guide/relocated-items/

 

[naylom11]

Hello there, I wonder if there is anyone ran into the same problem as mine.
I upgraded to 11.0.1 from Catalina following the steps of the micro patcher, everything been great.
However when I tried the very same process for the 11.1 update, my late 2012 MacBook Pro would boot into recovery instead of reinstall the OS, and it will ask me for the password for decryption, and my password wouldn't be correct. I also tried the GUI version Patcher Sur, same problem. I did tried boot into EFI boot first then the installer.
Appreciate any help, thanks!

Sounds like a FileVault issue. I know the micropatcher/BigSur in general has had issues with it

 

[bcdc13]

Hey guys, I need a little bit of help here. I'm trying to upgrade from 11.0.1 to 11.1 on my mid 2010 iMac. I'm attempting to use @Ausdauersportler fork of Barry's Micropatcher, but I'm getting held up. Steps I've taken so far:

1) create the installer media
2) run Micropatcher.sh
3) run install-setvars.sh
4) mount EFI partition of the install media and copy over the OC 0.6.4 boot and OC folders

Issue I'm having is that I can boot into what looks like a recovery install environment - grey screen with a mouse cursor I can move around - but I never get a menu bar or the recovery options window. Thoughts? Am I missing a step someplace? Thanks in advance

 

[antifocus]

Hmm, sounds like a FileVault issue. If I'm not mistaken, the MicroPatcher doesn't play well with it. Make sure its off. If that's not an option, my advice would be do a Time Machine backup of your current 11.01 install. Erase and do a fresh install following the same instructions

Hey thanks for the input, when I upgraded from Catalina Firevault was on so I didn't give it much thought, I'll disable it and see how it goes.

Edit: Can't seem to disable it, I guess TM back up then erase is the way to go, damn...

 

[TheSkywalker77]

So to "update" to 11.1 I just need to go through the same process I did to upgrade from Catalina to Big Sur with the micropatcher??

 

[kuoshen]

Hey guys, I need a little bit of help here. I'm trying to upgrade from 11.0.1 to 11.1 on my mid 2010 iMac. I'm attempting to use @Ausdauersportler fork of Barry's Micropatcher, but I'm getting held up. Steps I've taken so far:

1) create the installer media
2) run Micropatcher.sh
3) run install-setvars.sh
4) mount EFI partition of the install media and copy over the OC 0.6.4 boot and OC folders

Issue I'm having is that I can boot into what looks like a recovery install environment - grey screen with a mouse cursor I can move around - but I never get a menu bar or the recovery options window. Thoughts? Am I missing a step someplace? Thanks in advance

This is what worked for me. Do not boot into OpenCore until macOS Setup Assistant is almost complete and restarts the iMac. My iMac 2011 restarted 5 times, and I only boot into Opencore on the fifth and final time with macOS Setup Assistant to complete my migration from 11.0.1 to 11.1. In the meantime, I did not have brightness control and my iMac and LCD were getting very hot (probably 65 degrees C or higher). Hope this helps.

 

[jackyu]

help ,this version seem has security issue;
after install Big Sur on a early 2011 mbp;
it always prompt this screen, click cancel won't work:

 

[bcdc13]

This is what worked for me. Do not boot into OpenCore until macOS Setup Assistant is almost complete and restarts the iMac. My iMac 2011 restarted 5 times, and I only boot into Opencore on the fifth and final time with macOS Setup Assistant to complete my migration from 11.0.1 to 11.1. In the meantime, I did not have brightness control and my iMac and LCD were getting very hot (probably 65 degrees C or higher). Hope this helps.

Ok so maybe that’s my problem? I actually have OC 0.6.3 installed on my internal ssd so it’s booted by default every time. Maybe I need to find a way to remove that for the time being?

 

[kuoshen]

Ok so maybe that’s my problem? I actually have OC 0.6.3 installed on my internal ssd so it’s booted by default every time. Maybe I need to find a way to remove that for the time being?

When you hear the chime, hold down "Option" key and use the boot picker to select "macOS Installer".

My Opencore is also on a HFS+ partition on my SSD. I had enough of hitting my head on a table lamp going to the back to plug in an Opencore USB drive.

 

[tnsbgs]

I refer to the readme by online docs for micropatcher 0.5.1 (last section) "Modifying the System volume yourself"
1. remount-sysvol.sh
2. zap-snapshots.sh

Could someone explain how correctly run this command, because the command has beta mentioned.
/Volumes/Install\ macOS\ Big\ Sur\ Beta/remount-sysvol.sh

 

[mwidjaya]

/Volumes/Install\ macOS\ Big\ Sur\ Beta/remount-sysvol.sh

That just full path to script.

Drop the \ Beta, because your USB installer volume's name should be without Beta (assuming you are installing public release 11.1).

 

[mwidjaya]

Currently benchmarking 11.1 Opencore and MicroPatcher installs on my Mid 2012.

Now, this is interesting.

I have only used micropatcher so far.

Would love to hear what are the benefits of OpenCore and if it is worthwhile switching to this.

 

[tnsbgs]

That just full path to script.

Drop the \ Beta, because your USB installer volume's name should be without Beta (assuming you are installing public release 11.1).

it's not work, I get message: no such file or directory
I tried:
/Volumes/Install\ macOS\ Big\ Sur\ remount-sysvol.sh
/Volumes/Install\ macOS\ Big\ Sur /remount-sysvol.sh
/Volumes/Install\ macOS\ Big\ Sur remount-sysvol.sh
what is correct one?

 

[mwidjaya]

what is correct one?

OMG...

What do you get when you drop "\ Beta"?

/Volumes/Install\ macOS\ Big\ Sur/remount-sysvol.sh

 

[Objectivist-C]

My non-OpenCore 5,1 won’t show the 11.1 update when I boot my Big Sur install through VMWare and it doesn’t look like there’s a downloadable installer for it either. :/

 

[tnsbgs]

OMG...

What do you get when you drop "\ Beta"?

/Volumes/Install\ macOS\ Big\ Sur/remount-sysvol.sh

I get:
-bash-3.2# /Volumes/Install\ macOS\ Big\ Sur/remount-sysvol.sh
-bash: /Volumes/Install macOS Big Sur/remount-sysvol.sh: No such file or directory

 

[mwidjaya]

-bash: /Volumes/Install macOS Big Sur/remount-sysvol.sh: No such file or directory

Is the USB installer plugged in and mounted? What is the volume name? Can you see it in finder?

-----------------
Actually, if you are struggling with this, I think you better stop.

That section of micropatcher is not for noobs.

 

[tnsbgs]

Is the USB installer plugged in and mounted? What is the volume name? Can you see it in finder?

-----------------
Actually, if you are struggling with this, I think you better stop.

That section of micropatcher is not for noobs.

yeah sure, the USB name is: Install macOS Big Sur as usual and of course I can see all the files in the finder.

I start via this USB installation and go to the Terminal (same as in Recovery mode) and then I run the commands.
Maybe I do something wrong?

 

[mwidjaya]

I do something wrong?

Those instructions are specific, each line means something.

For now, remount-sysvol.sh should be run from the patched installer USB (but after booting from your Big Sur installation).

You did not follow this line above. Boot from your internal Big Sur disk, have USB installer plugged in, use terminal to run script off the USB stick.

Sounds to me like you boot up from USB installer....

As I said, unless you know what you are doing, please stop.

 

[akki_nd]

I did a fresh install on MBP Mid 2012 Build 20C69 now I am getting "Battery Service Recommended" error. Battery is actually working fine and giving me good backup. Another bug is now Volume icon is not changing even after plugging in the Headphones, I have already tried resetting SMC / PRAM but no change... Last build was better I guess. Anyone else noticed anything like this?

 

[tnsbgs]

Those instructions are specific, each line means something.

For now, remount-sysvol.sh should be run from the patched installer USB (but after booting from your Big Sur installation).

You did not follow this line above. Boot from your internal Big Sur disk, have USB installer plugged in, use terminal to run script off the USB stick.

Sounds to me like you boot up from USB installer....

As I said, unless you know what you are doing, please stop.

I have just reinstalled again USB drive and now it went smoothly with remount-sysvol.sh

only the part about removing snapshot using: zap-snapshots.sh I can't understand how to do it correctly:

"You may also run /Volumes/Install\ macOS\ Big\ Sur\ Beta/zap-snapshots.sh to delete all APFS system snapshots except for the most recent (this script must be run inside the subshell)."

 

[Ausdauersportler]

I have just reinstalled again USB drive and now it went smoothly with remount-sysvol.sh

only the part about removing snapshot using: zap-snapshots.sh I can't understand how to do it correctly:

"You may also run /Volumes/Install\ macOS\ Big\ Sur\ Beta/zap-snapshots.sh to delete all APFS system snapshots except for the most recent (this script must be run inside the subshell)."

You may re-read the online docs to get an idea how to work on the command line with path names (tab completion is you friend) and please tell me why you want to delete the snap shots. There is absolutely no need to do this (I never even though about it, because I normally have only one new).

Instead you can read the man pages of apfs to get an idea how snap shots are working. man pages??? Just enter man man within a terminal or search the web for Apple online docs. More easy to read...

 

[tnsbgs]

You may re-read the online docs to get an idea how to work on the command line with path names (tab completion is you friend) and please tell me why you want to delete the snap shots. There is absolutely no need to do this (I never even though about it, because I normally have only one new).

You are right and I also would't like to do this, but what if sometimes it's necessary to put some files in the system?
I wonder if there is the way to do it without deleting/re-creating snapshot?
for example, I need to put some file into this folder: /System/Library/Displays/Contents/Resources/Overrides/DisplayVendorID-10ac
how can I do this?

 

[vosadrian]

A USB SSD is a great idea. It's generally recommended to have a partition or SSD for the supported OS and another one for the unsupported OS so you can boot both.

I had a SSD I put in a USB drive case that actually works pretty well. I installed Big Sur 11.1 on that using micropatch on my iMac 2013. It seems to work really well with comparible performance to the internal SSD running Catalina. The only issue I have had does not seem to be a Big Sur issue but an issue with my iMac refusing to acknowledge the SSD as a startup disk unless I use the option key without it connected and then connect it once it gets to the startup manager (I had to do the same to use the install USB key). It made the install a bit tedious with all the reboots, but I don't think it has anything to do with the patch.

So Wifi works fine and everything is nice and snappy. I did notice some pixelated edges that I have seen others have mentioned, but only because I went looking for it.

So this was a test before upgrading the internal drive and everything seems to work great. Anything else I should check before I commit the internal drive to "umsupported Big Sur"? My wife uses this iMac for her work when she wants a bigger screen than her MBA which already has Big Sur (supported), So I thought I would upgrade it so she has the same functionality on each... but don't want that to backfire on me!

 

[Dilli]

Updated from 11.0.1 to 11.1 using Patched Sur method

To try something different I updated my MacBook Air mid 2011 patcher earlier with Barry's patcher 11.0.1 with Patch Sur this time and succeeded updating to version 11.1 of BigSur.
However had issue post installation of applying kexts.sh patch. The app Patched Sur just wouldn't open even though I clicked on open anyway in the system preference Privacy. It gave error reopen window but would just not open.

So I opened terminal and dragged the patch-kexts.sh script from the installer to the terminal and rebooted and got the wifi back. However still don't have Airdrop, Hands-off /continuity as it need patching and Siri lightening indicator missing.

My pointing out this is to just let Bensova know why this happened when everything was done as planned.