macOS 11 Big Sur on Unsupported Macs Thread

[mrbubzie1993]

folks I have upgraded four out of five of my machines to Big Sur and two of them are unsupported......White MacBook Mid 2010, and Mac Pro 5,1. Im writing this as sort of a warning. I WOULD NOT suggest upgrading any machine to Big Sur unless you have metal compatible graphics. My Mac Pro runs beautifully under Big Sur because of a graphics upgrade but as an experiment I installed on the white MacBook....and all I can say is its not even worth it....YouTube stutters because its relying on software acceleration and not taping into the hardware. Its extremely jittery and none responsive at times and its just overall a horrible experience. Save yourself the time and stick to Catalina which will have a few more years of support. Installing Big Sur on none metal graphics is futile.. .Only reason I'm saying all this is theres been a common occurrence of people not going through the forums and reading.....installing and wondering why the lousy performance. Please read through the forums and have an expectation if you move forward your machine is probably not going to be useable. And on a side note thank you all developers for making this possible. Im grateful to you guys this thanksgiving and will be raising a beer in your name. Happy thanksgiving to my favorite community

 

[BenSova]

Patched-Sur by Ben Sova is GUI frontend, not patcher. The patching is based on the first real patching option listed here, the @Barry K. Nathan patcher. The GUI makes it more comfortable to use the process but it hides also all obstacles and potential problems and it hides the docs. One should use a GUI if and only if the logic behind is mature and well known.

Yes, it uses a lot of code and references from the micropatcher, and I'm trying to eliminate as much as that as I can. In fact, the original plans for Patched Sur remove all of the code references completely. From my understanding, this message is silently asking for transparency which I will give in time. I hold the title "Beta" for a reason. I'm not done, and I won't be for a while. I can assure you, there might be several source breaking changes before Patched Sur comes out, and rewriting the documentation each time does not sound like something I want to do.

Here's the plan for Patched Sur as I see it (add all of the bug fixes in between):

1. Finish working on updating with startosinstall and clean installs by modifying the BaseSystem to have Patched Sur as an app.
2. Rewrite patch-kexts.sh to support whatever kexts the user wants to use whether this be their own fork, or not to use the WiFi kexts for some reason.
3. Fork the kexts so then I can control what the base kexts that Patched Sur ships with are (the user can still use BarryKN's if they want, but I want to make it easy for other users who haven't dived into this nearly as much as most people have, aka not you guys), and I no longer rely on BarryKN's micropatcher.
4. Finish the How It Works and Mac Compatibility sections in Patched Sur.
5. Work on in-depth documentation of everything Patched Sur does.
6. Finalize the app and bring it into something that gives the user the freedom to customize their Mac's kexts and similar while still making it easy for the people that just want Big Sur and don't really care to change up their kexts or what's on the installer USB.
7. Keep on going, until macOS 12 comes out which I will try to make a seamless update from macOS 11, and keep on going from there.

If there's any other transparency or customization you want, just ask, I'm not doing this to get it done, I'm doing this to let people extend their Mac's life their way. Whether they want to do it with a GUI or Terminal is their choice, whether they want to do it with premade kexts or their own kexts is their choice, I'm not here to limit, I'm here to show more people how much longer their Mac can survive. My audience is not the people who will see this message, my audience is the person who just realized that their Mac is no longer supported, and especially those who don't want to do crazy things to try to restore it, but I'll keep code there for those who do see this message and want to restore their Mac their way.

 

[jackluke]

I just uploaded a BigSurBaseSystemfix disk, updated for any generic BigSur 11.x beta (also non beta should work), simply restore through DiskUtility this DMG :

BigSurBaseSystemfix.dmg

Shared with Dropbox

www.dropbox.com

- minimum requirement 1 GB USB drive for an external modified recovery patcher (with BigSurFixes included)

to add an updated BigSur Installer app:

- an already downloaded InstallAssistant.pkg and unpacked to Applications folder
- 16 GB USB drive to add also the updated SharedSupport.dmg (typically size is 12.3 GB)

after restored the patched BigSurBaseSystemfix, you can use the same disk for any next beta releases, simply use this attached script I wrote for copying the updated SharedSupport.dmg to the target BigSurBaseSystemfix disk.

 

[mcpro2008]

I confirm it work also for me.
I have removed the old bluetooth adapter and installed a new WiFi + Bluetooth (Broadcom).

My steps to install Bug Sur on my Mac Pro with BigMac 🍔 tool from my macOS Catalina 10.15.7:

1. Download the BigMac script
2. From macOS Catalina, open a terminal and type:

cd ~/Downloads/bigmac-master (choose your correct location)
sudo ./preinstall.sh

When the script finish, execute the macOS Big Sur Installer clicking on its icon.
I suggest you to install into a SSD drive
After near 15 min, the installer finish and ask you to reboot, click restart.
Wait near 1h to let macOS Big Sur to complete the installation. It reboot 4 or 5 times.
When it finish the installation, the Mac Pro go into a loop, the macOS start and reboot, start and reboot (like with the dosdude1 patch when you install macOS Catalina.
Press the option key and boot again into Catalina.
Open a terminal and type:


cd ~/Downloads/bigmac-master (choose your correct location)
sudo ./postinstall.sh

When the script complete, reboot into macOS Big Sur

Finish

Thanks for the reply!

I tried doing that, applied post install patches as well, but I’m still getting the reboot loop. Any idea how to fix it?

 

[hvds]

I am patching 11.0.1 (20B50). Do you think I should try to fool around with SharedSupport.dmg? I don't have access to a 11.1 beta, and I do prefer English.

If it is for 11.0.1, no.

From the symptoms described I thought it must be for 11.1, where RogueB and myself have observed similar behaviour.

Had no problems with several USB installers made from 11.0.1 with jackluke BigSurBaseSystemfix/fix2.

 

[BeatCrazy]

I just uploaded a BigSurBaseSystemfix disk, updated for any generic BigSur 11.x beta (also non beta should work), simply restore through DiskUtility this DMG :

BigSurBaseSystemfix.dmg

Shared with Dropbox

www.dropbox.com

- minimum requirement 1 GB USB drive for an external modified recovery patcher (with BigSurFixes included)

to add an updated BigSur Installer app:

- an already downloaded InstallAssistant.pkg and unpacked to Applications folder
- 16 GB USB drive to add also the updated SharedSupport.dmg (typically size is 12.3 GB)

after restored the patched BigSurBaseSystemfix, you can use the same disk for any next beta releases, simply use this attached script I wrote for copying the updated SharedSupport.dmg to the target BigSurBaseSystemfix disk.

I must be missing a step

I am trying to create a new/repeatable Big Sur installer, while doing all of the below steps on a patched/working iMac 11,1 with Big Sur. I do have 11.0.1 (20B50) "Install macOS Big Sur" in my Applications folder and the InstallAssistant.pkg.

After following your instructions, I now have a 1GB USB with BigSurBaseSystemfix mounted and available as a bootable USB. I also have a patched (includes your fix 1+2) Install macOS Big Sur USB bootable USB. I also ran the the BigSurSharedSupportfix.command and that seemed successful.

After I boot from Catalina Loader, choosing either of the above boot options I choose from the picker menu still gives me a gray screen with the briefly-flashed Language Chooser menu, which disappears and I'm left with a light gray screen.

Thanks in advance for any guidance.

 

[jackluke]

I must be missing a step

I am trying to create a new/repeatable Big Sur installer, while doing all of the below steps on a patched/working iMac 11,1 with Big Sur. I do have 11.0.1 (20B50) "Install macOS Big Sur" in my Applications folder and the InstallAssistant.pkg.

After following your instructions, I now have a 1GB USB with BigSurBaseSystemfix mounted and available as a bootable USB. I also have a patched (includes your fix 1+2) Install macOS Big Sur USB bootable USB. I also ran the the BigSurSharedSupportfix.command and that seemed successful.

After I boot from Catalina Loader, choosing either of the above boot options I choose from the picker menu still gives me a gray screen with the briefly-flashed Language Chooser menu, which disappears and I'm left with a light gray screen.

Thanks in advance for any guidance.

I guess I should rephrase that previous post, restoring to 1 GB USB will make simply an external BigSur patched recovery, while instead to make an updated BigSurBaseSystemfix full Installer for any 11.x beta :

- restore the BigSurBaseSystemfix.dmg to a 16 GB USB empty drive
- download the 11.x beta InstallAssistant.pkg and after run it to make the unpackaged apple "Install app" in the default macOS (HighSierra, Mojave, Catalina, BigSur) Applications folder
- launch the "BigSurSharedSupportfix" that should automatically copy the updated SharedSupport.dmg (that is where the stage2 installer is stored) to the 16 GB USB drive (that acts as an updated BaseSystemfix Installer)
- at reboot from apple startup manager or any bootloader it should work to boot "BigSurBaseSystemfix" with an updated "stage2 macOS Installer", I'd say the stage1 installer is common to any BigSur Installer so it doesn't require an updated package.

 

[macguru8]

Thanks for the reply!

I tried doing that, applied post install patches as well, but I’m still getting the reboot loop. Any idea how to fix it?

I just did the same here, still reboot loop

 

[mcpro2008]

I just did the same here, still reboot loop

Trying to update my Catalina drive (was trying to clean install before), will update on how it goes.

 

[macguru8]

Trying to update my Catalina drive (was trying to clean install before), will update on how it goes.

Standing by, hope you have luck

 

[mcpro2008]

Standing by, hope you have luck

No luck - installer finished and when I tried booting into the now updated drive I got the prohibited sign. Ran the bigmac post install and I’m back to Catalina somehow.

 

[BeatCrazy]

I guess I should rephrase that previous post, restoring to 1 GB USB will make simply an external BigSur patched recovery, while instead to make an updated BigSurBaseSystemfix full Installer for any 11.x beta :

- restore the BigSurBaseSystemfix.dmg to a 16 GB USB empty drive
- download the 11.x beta InstallAssistant.pkg and after run it to make the unpackaged apple "Install app" in the default macOS (HighSierra, Mojave, Catalina, BigSur) Applications folder
- launch the "BigSurSharedSupportfix" that should automatically copy the updated SharedSupport.dmg (that is where the stage2 installer is stored) to the 16 GB USB drive (that acts as an updated BaseSystemfix Installer)
- at reboot from apple startup manager or any bootloader it should work to boot "BigSurBaseSystemfix" with an updated "stage2 macOS Installer", I'd say the stage1 installer is common to any BigSur Installer so it doesn't require an updated package.

That makes more sense So I followed the above instructions, and it helps to reboot after running the BigSurSharedSupportfix. I'm pretty sure I was successful in creating the BigSurBaseSystemfix, as the script ran fine, took about 10 minutes.

But when I choose BigSureBaseSystemfix (external) from my CatalinaLoader OC picker, I still get the Apple icon/progress bar, then the quick "Language Picker" header, but then a solid gray screen with cursor, unable to proceed.

Seems strange, since this booter/patched installer is 100% fresh and new, and your instructions have been followed exactly.

I can't boot/pick directly from the BigSureBaseSystemfix USB (without CatalinaLoader), as I just get the Apple logo, no progress bar.

 

[hvds]

...

But when I choose BigSureBaseSystemfix (external) from my CatalinaLoader OC picker, I still get the Apple icon/progress bar, then the quick "Language Picker" header, but then a solid gray screen with cursor, unable to proceed.

...

Strange, because you said your system is English anyway.
If your nvram contains language entries, you could still try to remove them, like in the attached screenshot.

 

[jorrrrrje]

Hi people.

I'm trying to install Big Sur on my mac with the hax.dylib patch but when i click on my SSD on the install, it shows a message saying that it wasn't possible to update.

What should I do?

 

[hvds]

I just uploaded a BigSurBaseSystemfix disk, updated for any generic BigSur 11.x beta (also non beta should work), simply restore through DiskUtility this DMG :

BigSurBaseSystemfix.dmg

Shared with Dropbox

www.dropbox.com

- minimum requirement 1 GB USB drive for an external modified recovery patcher (with BigSurFixes included)

to add an updated BigSur Installer app:

- an already downloaded InstallAssistant.pkg and unpacked to Applications folder
- 16 GB USB drive to add also the updated SharedSupport.dmg (typically size is 12.3 GB)

after restored the patched BigSurBaseSystemfix, you can use the same disk for any next beta releases, simply use this attached script I wrote for copying the updated SharedSupport.dmg to the target BigSurBaseSystemfix disk.

Thank you jackluke, and congratulations. You have devised a very convenient procedure to make an installer which is updateable for a whole series of betas, and applicable to the very old legacy USB machines.

I just successfully used it to create a new USB installer for 11.1 beta, and used the result to install successfully.

Used these steps to make the installer (maybe too detailed for many - sorry):
1) downloaded your BigSurSharedSupportfix.zip, unzip to get the BigSurSharedSupportfix.command
2) downloaded your BigSurBaseSystemfix.dmg
3) plug in the USB medium to be used as the USB installer (formatted Mac OS extended (journaled)) and start Disk Utility
4) select Restore in Disk Utility, to the USB medium, with BigSurBaseSystemfix.dmg as the Image to be restored to the USB medium (photos 1+2).

These four steps are needed once, and new versions (betas or releases) can be included in the USB medium as they appear, as follows:

5) have the USB medium plugged in
6) have the installer app you want to install from, in /Applications. It gets there by downloading and running a full installer's InstallAssistant.app
7) open a terminal and run BigSurSharedSupportfix.command in it, e.g. by drag/drop from a Finder window (photos 3+4), or run the command by simply double-clicking it. This may take some 10-15 minutes as it has to transfer the largest part of the system, i.e. SharedSupport.dmg. The contents of the resulting USB installer is in photo 5.

These three steps can be executed again with the same USB medium when a new version arrives.

The installer should boot fine and can be used as the ones made with previous jackluke procedures, i.e. BigSur BaseSystem legacy usb fix/fix2.command.

To recall this installation procedure:
a) boot the USB installer (photo 6)
b) run Hax3 installer fix from main window and confirm it (photos 7+8)
c) start the installer, select the target disk, and its stage 1 should proceed (photo 9).

Depending on the location of your target disk (internal SATA, external USB) and whether your machine is a legacy USB or more modern one, the process will proceed to the end or will require rebooting to the USB installer to apply stage 2 installer fix and Legacy USB patches (an alternative to stage 3 installer fix). Choose them from the Utilities pulldown menu.

BigSur should be able to boot now. Anyway in the end boot again the USB installer to apply post-install patches like graphics framebuffer, Framework, etc., from the Utilities pulldown menu (photo 10).

@jackluke, I hope it got it right...

 

[TA 455SD]

Hi people.

I'm trying to install Big Sur on my mac with the hax.dylib patch but when i click on my SSD on the install, it shows a message saying that it wasn't possible to update.

View attachment 1680580

What should I do?

From my understanding to install Big Sur the usb must be at least 16GB and formatted as GUID , also it would be best to post what machine you have , the year and model and any changes you have made if any

 

[haralds]

Started running into stuttering USB 3 performance with video and audio on my cMP 5,1. This worked fine a few days ago with no changes. Does anybody have any ideas?
Catalina works great.

 

[jorrrrrje]

From my understanding to install Big Sur the usb must be at least 16GB and formatted as GUID , also it would be best to post what machine you have , the year and model and any changes you have made if any

But i could update

I just patched correctly and it worked.

I'm using MacBook Pro 15" Early-2013.

BUT i'm having issues with wi-fi and i'm trying to mount -uw bus it's appearing that it failed 'with' 66.

 

[TA 455SD]

But i could update

I just patched correctly and it worked.

I'm using MacBook Pro 15" Early-2013.

BUT i'm having issues with wi-fi and i'm trying to mount -uw bus it's appearing that it failed 'with' 66.

There is a fix for the wifi , but I don't recall what it was as I did not have problem with it , but I have seen several people speak of it and for a 2013 the fix was rather simple , look through the past 20 pages and I am sure you will come across it , or use the search bar that may make it easier

 

[jorrrrrje]

There is a fix for the wifi , but I don't recall what it was as I did not have problem with it , but I have seen several people speak of it and for a 2013 the fix was rather simple , look through the past 20 pages and I am sure you will come across it , or use the search bar that may make it easier

ok, i'll find it, thanks a lot.

 

[BeatCrazy]

Strange, because you said your system is English anyway.
If your nvram contains language entries, you could still try to remove them, like in the attached screenshot.

Thanks. I'm a bit hesitant to mess with the languages via Terminal. I'm in the USA, with a USA iMac, and only an English speaker. Installing Big Sur has worked fine before, so although the Language Chooser is where I get stuck, it seems like something else is really my problem.

 

[KennyW]

Yes, it uses a lot of code and references from the micropatcher, and I'm trying to eliminate as much as that as I can. In fact, the original plans for Patched Sur remove all of the code references completely. From my understanding, this message is silently asking for transparency which I will give in time. I hold the title "Beta" for a reason. I'm not done, and I won't be for a while. I can assure you, there might be several source breaking changes before Patched Sur comes out, and rewriting the documentation each time does not sound like something I want to do.

Here's the plan for Patched Sur as I see it (add all of the bug fixes in between):

1. Finish working on updating with startosinstall and clean installs by modifying the BaseSystem to have Patched Sur as an app.
2. Rewrite patch-kexts.sh to support whatever kexts the user wants to use whether this be their own fork, or not to use the WiFi kexts for some reason.
3. Fork the kexts so then I can control what the base kexts that Patched Sur ships with are (the user can still use BarryKN's if they want, but I want to make it easy for other users who haven't dived into this nearly as much as most people have, aka not you guys), and I no longer rely on BarryKN's micropatcher.
4. Finish the How It Works and Mac Compatibility sections in Patched Sur.
5. Work on in-depth documentation of everything Patched Sur does.
6. Finalize the app and bring it into something that gives the user the freedom to customize their Mac's kexts and similar while still making it easy for the people that just want Big Sur and don't really care to change up their kexts or what's on the installer USB.
7. Keep on going, until macOS 12 comes out which I will try to make a seamless update from macOS 11, and keep on going from there.

If there's any other transparency or customization you want, just ask, I'm not doing this to get it done, I'm doing this to let people extend their Mac's life their way. Whether they want to do it with a GUI or Terminal is their choice, whether they want to do it with premade kexts or their own kexts is their choice, I'm not here to limit, I'm here to show more people how much longer their Mac can survive. My audience is not the people who will see this message, my audience is the person who just realized that their Mac is no longer supported, and especially those who don't want to do crazy things to try to restore it, but I'll keep code there for those who do see this message and want to restore their Mac their way.

Thanks for your effort, Ben.

Is there an uninstall option for specific patches ? Sometimes when some hardwares are changed for better compatibility with the OSX, those patches might not be needed and would in fact contribute to system instability or non-function.

An option to roll back these patches would be welcomed if feasible.

At present, say for the great DosDude1 Catalina Patcher, without the uninstall option, I have to install the whole system again if the legacy video patch or USB or wifi/BT patch is unnecessarily applied, although there are instructions to revert manually which are a bit troublesome.

Just a suggestion to consider.

Cheer.

 

[BenSova]

Thanks for your effort, Ben.

Is there an uninstall option for specific patches ? Sometimes when some hardwares are changed for better compatibility with the OSX, those patches might not be needed and would in fact contribute to system instability or non-function.

An option to roll back these patches would be welcomed if feasible.

At present, say for the great DosDude1 Catalina Patcher, without the uninstall option, I have to install the whole system again if the legacy video patch or USB or wifi/BT patch is unnecessarily applied, although there are instructions to revert manually which are a bit troublesome.

Just a suggestion to consider.

Cheer.

Yes, there will be once I work on the custom implementation of patch-kext.sh.

 

[jorrrrrje]

I'm having issues to connect using wifi network because it doesn't show nothing when finds.

And i'm trying to boot on recovery mode but when i try it...the mojave's recovery appears and not the big sur. so i don't know what i should do.

 

[jorrrrrje]

About the micro patcher: it means i should reinstall the whole system?