Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.

Mystere65

macrumors member
Nov 2, 2015
78
46
Firenze (Italy)
So, a question slightly related......if I've installed Big Sur beta on an unsupported iMac, will I be able to get future beta updates through software update within there, or do I need to download the beta when its available (by looking on this thread) and put on a USB installer as I did the first time? I'm not clear on this myself, hence why I ask.

Yes, that's it for now
 
  • Like
Reactions: TimothyR734

Dilli

macrumors 6502a
Oct 21, 2019
581
544
Update Big Sur on iMac 2011 with a metal GPU:

Installation of the Beta 6 on my iMac 2011 / 780M / BCM94360CD with a modified @Barry K. Nathan micro patcher done....again.

Lilu, Whatevergreen got updates two days ago, the AppleGraphicsControl has been taken from this current Beta 6 (20A5364e) and modified and these three files have been added to the zip file attached. Both the old and new zip will give you a working Big Sur. At least I got it running including sleep, AirDrop, Handoff etc using a BCM94360CD card.

After patching the USB installer put in the into the kexts folder on the patched USB installer and unzip the new and put it at the same spot where you find the patch-kexts.sh provided by @Barry K. Nathan (version 0.1.0).

Follow exactly the guide @Barry K. Nathan created, just call the new patch-kexts-iMac-2011.sh instead of the stock patch-kexts.sh. Call the script while booted into Big Sur on your iMac. The new script needs a working OS to check the card type (NVIDIA Kepler or AMD Polaris).

Have fun! You may also check my first post about this mods and the command line arguments to be used.

P.S.:
Currently it is not entirely clear if we really new the modified AppleGraphicsControl to avoid a black screen on boot. No such experience with the few installations of Big Sur so far.

Copying over an installation to an iMac using an AMD Polaris card works with this version, too. You have to change the AppleIntelSNBGraphicsFB extension and delete the AppleBacklightFixup then, of course. Better you copy an unpatched version of an installation and use the special patch-kexts-iMac-2011.sh later from the micro patched USB installer you need to create the installation first hand (iMac 2011, AMD WX4170, BCM943602CPD).
You are really good at this. A suggestion make a video on youtube would really help audio visually. Cheers ✌️
 

Ausdauersportler

macrumors 603
Nov 25, 2019
5,007
5,826
You are really good at this. A suggestion make a video on youtube would really help audio visually. Cheers ✌
Thanks, I am not a native speaker and I am the visual learner by reading :) So I never understood why wasting time in front of a 15 min video when I am able to gather the same information within seconds of reading. This is just entering some lines of commands and doing 10 steps in the way @Barry K. Nathan documented it already.

But I promise to create a more complete documentation of the things we (@highvoltage12v and me) are doing here later. Right now I just want to make sure that the patcher developers add the patched extensions we provide here to the Big Sur patcher or they may offer an interface within the @dosdude1 patcher to integrate new hardware configurations. In this case I could add the patch sets for the part of the community owning a hardware modded iMac 2011 with a metal GPU - just writing from my 2011/GTX 780M/BCM94360CD using Big Sur.

The message I can send right now is:

Replace the GPU and the WIFI/BT card and you will get most likely a Big Sur compatible platform. This config is close to the 2013 iMac models and may have ever a better GPU (AMD Polaris). And if runs really perfectly with Catalina as of now.

But Apple may find a way to lock us out in the last moment. Who knows..
 

chrishatch

macrumors newbie
Jul 26, 2013
9
4
I have a 2013 Mac Pro and an unsupported 2012 Mac Mini. Is it possible to install Big Sur on an external SSD using the Mac Pro, then boot from the external SSD using the Mac Mini?
 
  • Like
Reactions: TimothyR734

Starmina

macrumors member
Jul 7, 2020
46
14
Hi Everyone,

I searched the thread for the terms `BIErrorDomain error 2` and couldn't find any information about my problem.
I recently upgraded my MacBook Pro 10,2 (Late 2012) from Catalina to Big Sur and it was a success.

I then tried to upgrade from what i remember was beta 2 to beta 3 or 4 and that's where issues started. I can't remember what exactly i did wrong, but each time i tried to boot i would get a forbidden sign.
I did some research and I fortunately could restore my system to Catalina by downloading restore tools (Option+CMD+R) from Apple server.
Installation worked perfectly, and i could use my mbp again.

Of course : I want Big Sur and not Catalina. But before i try again to upgrade, i create a new APFS container to have a Big Sur 'partition' and a Catalina one (just in case).

I then proceed to download Beta 6 > createinstallmedia > ran micropatcher.sh from barrykn > Boot from USB > set-vars.sh > Try to install Big Sur to disk.

From there i can't go further. I can't upgrade Catalina to Big Sur, i can't install it to the 'Big Sur' apfs container and i can't even install it to an USB APFS Partition i made (I knew it would be slow but it should at least work).
All disk are greyed out, with error 'Operation couldn't be completed (BIErrorDomain error 2).

I tried
everything i could, to re-create disk, create a 'real partition' (instead of APFS Container) : nothing work since i had the forbidden sign problem.

Hope someone knows the answer to this.

Thanks a lot guys.
 
Last edited:
  • Like
Reactions: TimothyR734

mikentosh

macrumors newbie
Oct 19, 2002
27
19
Earth
Hi Everyone,

I searched the thread for the terms `BIErrorDomain error 2` and couldn't find any information about my problem.
I recently upgraded my MacBook Pro 10,2 (Late 2012) from Catalina to Big Sur and it was a success.

I then tried to upgrade from what i remember was beta 2 to beta 3 or 4 and that's where issues started. I can't remember what exactly i did wrong, but each time i tried to boot i would get a forbidden sign.
I did some research and I fortunately could restore my system to Catalina by downloading restore tools (Option+CMD+R) from Apple server.
Installation worked perfectly, and i could use my mbp again.

Of course : I want Big Sur and not Catalina. But before i try again to upgrade, i create a new APFS container to have a Big Sur 'partition' and a Catalina one (just in case).

I then proceed to download Beta 6 > createinstallmedia > ran micropatcher.sh from barrykn > Boot from USB > set-vars.sh > Try to install Big Sur to disk.

From there i can't go further. I can't upgrade Catalina to Big Sur, i can't install it to the 'Big Sur' apfs container and i can't even install it to an USB APFS Partition i made (I knew it would be slow but it should at least work).
All disk are greyed out, with error 'Operation couldn't be completed (BIErrorDomain error 2).

I tried
everything i could, to re-create disk, create a 'real partition' (instead of APFS Container) : nothing work since i had the forbidden sign problem.

Hope someone knows the answer to this.

Thanks a lot guys.

I have a Late 2013 27-inch iMac and I ran into a similar problem when I tried to upgrade from Big Sur Beta 4 to Beta 6. I had successfully upgraded from Catalina to Big Sur Beta 1 to 2 to 3 to 4 with no problem. When trying to go from 4 to 6, I too kept getting the BIErrorDomain error 2. The only thing that ended up working for me was formatting my iMac HD and doing a fresh install of Beta 6 (then restoring). I thought it was an issue with running the set-vars.sh at first, but I know I did that part correctly (eventually). Since you have a partition, I would think it would work the same as a disk format. Are you positive the set-vars.sh are working? I had a path issue once booted into the installer, so I had to type:

/bin/bash /Volumes/Image\ Volume/set-vars.sh
 
  • Like
Reactions: TimothyR734

Starmina

macrumors member
Jul 7, 2020
46
14
I have a Late 2013 27-inch iMac and I ran into a similar problem when I tried to upgrade from Big Sur Beta 4 to Beta 6. I had successfully upgraded from Catalina to Big Sur Beta 1 to 2 to 3 to 4 with no problem. When trying to go from 4 to 6, I too kept getting the BIErrorDomain error 2. The only thing that ended up working for me was formatting my iMac HD and doing a fresh install of Beta 6 (then restoring). I thought it was an issue with running the set-vars.sh at first, but I know I did that part correctly (eventually). Since you have a partition, I would think it would work the same as a disk format. Are you positive the set-vars.sh are working? I had a path issue once booted into the installer, so I had to type:

/bin/bash /Volumes/Image\ Volume/set-vars.sh

I'm positive the command works as it shows messages to the screen confirming that nvram / csrutil commands were run successfully. Anyway, I added the -v parameter, and then, booting Catalina indeed shows boot logs so i think the command is working correctly

I tried your command (adding the /bin/bash at the start) but it's unfortunately the same :/
Thanks for your answer

EDIT : So actually running /Volumes/Image\ Volume/reset-vars.sh, rebooting, then set-vars.sh fixed the problems ! Never tought it would work. Honestly tought re-running set-vars.sh each time was enough.

EDIT 2 : So i tought it was good. Even though i can actually launch the Big Sur installation, after the first reboot it nows shows a forbidden sign instead of continuing the Big Sur installation... damn.. Tried the installation on two different disk and got the same issue
 
Last edited:
  • Like
Reactions: TimothyR734

LuisN

macrumors 6502a
Mar 30, 2013
738
688
Torres Vedras, Portugal
@Maclinux:

Same machine 500/100 ISP speed
WIFI:
Captura de ecrã 2020-09-11, às 15.14.32.png

WIRED:
Captura de ecrã 2020-09-11, às 15.15.28.png
 
Last edited:

buckrock

macrumors 6502
Jul 24, 2020
297
424
Fresno, California
Is there a place where I can find all of the links to all of the betas, 1-6? I would like to test them all one by one on my 2011 MBP to see what to use on my patcher before the real thing comes out.

Funny you should ask. I wanted to organize a list and maybe have that as a sticky. Didn't finish, but I do have the first 5 and the post they are mentioned in.

note: the beta1 through 4 links are expired (buckrock edit)

beta 1 post #40 id number 18401
beta 2 post #1599 id number 23553
beta 3 post #2215 id number 26097
beta 4 post #2898 id number 35028
beta 5 post #3339 id number 36806
beta 6 post #3888 id number 43966

Sorry, I didn't put beta 6 on my rough list. FYI, the id number is a number unique in the link for the beta's InstallAssistant.pkg

Edited by Buckrock
 
Last edited:
  • Like
Reactions: hvds

justperry

macrumors G5
Aug 10, 2007
12,627
9,933
I'm a rolling stone.
I'm positive the command works as it shows messages to the screen confirming that nvram / csrutil commands were run successfully. Anyway, I added the -v parameter, and then, booting Catalina indeed shows boot logs so i think the command is working correctly

I tried your command (adding the /bin/bash at the start) but it's unfortunately the same :/
Thanks for your answer

EDIT : So actually running /Volumes/Image\ Volume/reset-vars.sh, rebooting, then set-vars.sh fixed the problems ! Never tought it would work. Honestly tought re-running set-vars.sh each time was enough.

EDIT 2 : So i tought it was good. Even though i can actually launch the Big Sur installation, after the first reboot it nows shows a forbidden sign instead of continuing the Big Sur installation... damn.. Tried the installation on two different disk and got the same issue

It's most likely due to the no compat check, try to run that command in recovery.
You'll might have to start all over again though, but try before.

Run

sudo nvram boot-args="-no_compat_check"

in Terminal in recovery mode.
 
  • Like
Reactions: Starmina

treee111

macrumors member
Apr 17, 2020
39
38
I was able to install macOS Big Sur using the micropatcher v0.1.0 on a external SSD connected to my macBookPro 2011 8,1 and got it running!
WIFI, sound, FN-keys (volume, brightness etc.) working! :)

It took me around 3/4 hours from scratch and I used mainly the receipe on github and some comments in this thread.

You done a amazing job @Barry K. Nathan !!!
Let's get further and further --> I need another partition on my internal SSD for Big Sur ;)
 

Starmina

macrumors member
Jul 7, 2020
46
14
It's most likely due to the no compat check, try to run that command in recovery.
You'll might have to start all over again though, but try before.

Run

sudo nvram boot-args="-no_compat_check"

in Terminal in recovery mode.

Hi, thanks for your answer, booting with Cmd + R and Typing the command indeed work ! Finally running Big Sur again !
Additionnal info : 'sudo' doesn't exist in Recovery mode, but the command work without sudo
 
  • Like
Reactions: justperry

Armere Caruso

macrumors newbie
Jul 7, 2020
20
19
Can I delete the Big Sur volume called install Mac OS beta and have bug sur still work Bc i portioned half and half and I want the rest of the room for Big Sur
 

bige12

macrumors 65816
Apr 6, 2009
1,473
847
Vienna, VA
I took my USB external hard drive that has Mac OS Big Sur Beta 6 on and booted up on on a mid 2011 MacBook Air and it booted just fine the only thing is the background of the dock is black but dose not look too bad, I just wanted to see if it would boot and it did really did not spend much time testing it
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.