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.
I'm idly looking at doing this for my 2008 3,1 mac pro. I've patched it up to Catalina and have a natively supported GTX680 graphics card but its probably prudent to go up to BS as I want to keep it running until I can afford an ARM mac mini- or wait until like gen 2 or 3 versions come out.

I've found a couple of tutorials and resources for big sur patchers but I'm not an expert so use at ur own risk.

If I do try one and It works I'll post it here.

https://github.com/StarPlayrX/bigmac (mac pro patcher- needs a boot screen or a workaround if you don't have a supported GPU, probably not an issue if your machine isn't a hacked freak of a machine like mine)


Apologies if any of you have seen these bfore but I thought I'd share :) If people know better patchers and such then drop me a reply or a DM xx
 
i have a problem, my graphics are not running
i have installed an intel hd3000, and my sound and wifi are not working.
is there a patch for the macbook air4,1 that works again?

lg
 

Attachments

  • Bildschirmfoto 2020-11-24 um 04.16.22.png
    Bildschirmfoto 2020-11-24 um 04.16.22.png
    1.1 MB · Views: 514
  • Like
Reactions: TimothyR734
i have a problem, my graphics are not running
i have installed an intel hd3000, and my sound and wifi are not working.
is there a patch for the macbook air4,1 that works again?

lg

Nobody has figured out " yet " full graphics acceleration on Intel HD 3000.

So for now you can install Big Sur, but it won't have graphics acceleration.
 
I got another warning on my 2012 Mac Mini, the second one, first was about a month ago, it said I have problems with my computer, in the Dialog window (Which I sadly clicked away before making a screenshot) I had the option to view the log/file.
See screenshot, seems like Efi problems.

Screenshot 2020-11-24 at 18.46.51.png
 
Last edited:
Hello to all,

Reporting a successful installation of Big Sur 11.1 on late 2012 iMac 13,2 equipped with Fusion HDrive, and installation of Big Sur 11.0.1 on Mid 2009 MacBook Pro 5,2 with a Samsung EVO 860 SSD.

—iMac installation process:

I used createinstallmedia process, and Barry K. Nathan’s micropatcher 0.5.1. to prepare USB thumb drive for installation of Big Sur 11.1 (installer 16.2.01) onto its own partition. Necessary steps for successful installation are well delineated on BKN’s GitHub page.

All system functions, including WiFi, operate without discernible faults.

—MacBook Pro 5,2 installation process:

Utilized creatinstallmedia process and @jackluke’s BigSurBaseSystemFix1 and BigSurBaseSystemFix2 to place and patch, respectively, Big Sur installer onto a USB-thumb drive.

Direct Link to juckluke’s BigSurBaseSystem fix zip: https://forums.macrumors.com/attachments/bigsur-basesystem-legacy-usb-fix-zip.1169210/

Direct link to juckluke’s PDF doc containing instructions: https://forums.macrumors.com/attachments/bigsurbasesystemfix-pdf.1666289/

Above items are on page 228 of this thread, in a post # 5692 by jackluke

I followed instructions deleniated in jackluke’s PDF document (referenced above); read instructions carefully, notably, the directive to unplug USB thumb-drive from the USB port after applying fix1, and plugging USB thumb-drive back into computer’s USB port before applying Fix#2.

Once USB stick is prepared, boot from it, by using the option Key on restart, and choosing said USB stick from the displayed selection of drives.

At end of boot from USB Drive a window will open, and display multiple items for selection.

Install jackluke’s modified open-core on the internal drive — open-core allows for booting when computer is stuck for any reason. It’s a great tool.

Then continue by selecting Hex3.app to allow BigSur installation on internal drive. (Note that other drives can be chosen, but process is different - read juckluke’s PDF instructions.)

Subsequently, choose install BugSur application icon. Wait for the installation to finish and follow instructions to create an account , etc.

Reboot to USB stick again, and apply three more modules, (all available from the displayed menu.)

1. BigSurFixes snapshot booting
2. BigSurFixes legacy USB
3. BigSurFixes graphical framebuffer (this module restores brightness control and allows sleep function to activate, among other interface improvements)
4. I disabled animation using free TinkerTool ( no affiliation with the program)

After applying above listed modules I did have an issue booting back into the Big Sur installation. That’s when open-core was invaluable; I booted from open-core, (selection of open-core is available when booting with option-key pressed). Then, I used ope-core generated interface to choose startup from Big Sur partition. Thereafter, I did not need open-core to boot into Big Sur.

There is no graphic acceleration, as expected, but system is usable for basic tasks; the range of tasks that may be usable may depend on CPU and memory configuration. Wifi and Ethernet were functional as well.

This is an abbreviated descriptive of installation process on Penryn C2D MacBook Pro 5,2.

Hope this post may be of help.

Thank you to all the developers and participants whose work and contributions gift the "old" Macs with a viable "existance."
Very helpful post indeed, thanks!
I am also installing 11.1 on an MBP5,2, using jackluke's BigSurBaseSystemFix patching of the installer.
While it was always fine upto 11.0.1, I am still busy with setting up 11.1 installation.
My USB installer won't boot right away. Two observations I wanted to share now, before I have success:
- seems that the installer for 11.1 beta needs English language setup, as was the case for earlier 11.0 betas (delete the language entries from nvram with sudo nvram -d prev-lang:kbd and sudo nvram -d prev-lang-diags:kbd, unless it indicates English already)
- the file name of macOS Big Sur Beta installieren.app looks as if there were two blanks in the string "macOS Big Sur "while there is in fact two times the sequence hex C2 A0, maybe only in the file name generated in my German setup
- in a private communication jackluke suggested to plug the 11.1 installer.app into a USB installer prepared with 11.0.1. Trying that now.

EDIT: not quite there yet. I get to the language selection screen, but even when choosing English, I get a grey screen (mouse present and moving) instead of the recovery screen with jackluke's extras.
@RogueB , on which system did you perform the createinstallmedia and patching, and what was your language setup? I used Catalina 10.15.7, so far German, now will try in English.
 

Attachments

  • Bildschirmfoto 2020-11-24 um 18.02.10.png
    Bildschirmfoto 2020-11-24 um 18.02.10.png
    67.7 KB · Views: 125
Last edited:
  • Like
Reactions: TimothyR734
I'm idly looking at doing this for my 2008 3,1 mac pro. I've patched it up to Catalina and have a natively supported GTX680 graphics card but its probably prudent to go up to BS as I want to keep it running until I can afford an ARM mac mini- or wait until like gen 2 or 3 versions come out.

I've found a couple of tutorials and resources for big sur patchers but I'm not an expert so use at ur own risk.

If I do try one and It works I'll post it here.

https://github.com/StarPlayrX/bigmac (mac pro patcher- needs a boot screen or a workaround if you don't have a supported GPU, probably not an issue if your machine isn't a hacked freak of a machine like mine)


Apologies if any of you have seen these bfore but I thought I'd share :) If people know better patchers and such then drop me a reply or a DM xx
You may just pay a visit to the first post of this thread :)
 
  • Like
Reactions: TimothyR734
Very helpful post indeed, thanks!
I am also installing 11.1 on an MBP5,2, using jackluke's BigSurBaseSystemFix patching of the installer.
While it was always fine upto 11.0.1, I am still busy with setting up 11.1 installation.
My USB installer won't boot right away. Two observations I wanted to share now, before I have success:
- seems that the installer for 11.1 beta needs English language setup, as was the case for earlier 11.0 betas (delete the language entries from nvram with sudo nvram -d prev-lang:kbd and sudo nvram -d prev-lang-diags:kbd, unless it indicates English already)
- the file name of macOS Big Sur Beta installieren.app looks as if there were two blanks in the string "macOS Big Sur "while there is in fact two times the sequence hex C2 A0, maybe only in the file name generated in my German setup
- in a private communication jackluke suggested to plug the 11.1 installer.app into a USB installer prepared with 11.0.1. Trying that now.

I haven't tested yet 11.1 beta for some reasons , maybe apple changed their Install app name as "Install macOS Big Sur 11.1 Beta 11.1" , so in this case even if BaseSystem fix works can't find from ramdisk the correct app folder.

But from my earlier test you could use a previous BaseSystem.dmg to load in ramdisk any recent "Install macOS BigSur Beta.app" , it is possible that installer language doesn't work properly so selecting English should easily work, anyway you could try also this to make a patched installer, just use any previous BaseSystemfix Installer, then replace only in this path: /Install macOS Big Sur*.app/Contents/SharedSupport/SharedSupport.dmg

also when replacing that file don't rename "Install macOS Big Sur Beta.app" or "Install macOS Big Sur.app", I mean apple macOS has some their routines that automatically rename those aliases installer app to the main non English system language, when this happens don't rename it to English otherwise that app is no more valid, you should use the name that macOS automatically chosen and renamed that alias .app folder , if you rename again to English that folder the installer will show grey screen.

So I guess replacing only the updated "SharedSupport.dmg" should work with any patched BigSurBaseSystemfix.dmg and any language selected:
Code:
cp /Applications/*.app/Contents/SharedSupport/SharedSupport.dmg /Volumes/Install macOS Big Sur*/*.app/Contents/SharedSupport/
 
Last edited:
Hi all

Has anyone noticed freezes with any apple apps? I got them with contacts and messages so far.

Cheers
Ok, I found a solution but I cannot tell whether it is permanent or not: disconnecting contacts from icloud, launching it, quitting it and then reconnecting it did the trick. Hope it sticks

Edit: Spoke to soon... Back to square one.
 
Last edited:
I'm still trying to get my Mac Pro 3,1 going but it's rough sledding. In today's adventures in Big Sur patching, i finally got the BigMac patch to get to the installer screen where I could launch Terminal....until I realized that USB is so jacked up that it wouldn't recognize the old USB keyboard plugged into the front port. And it wouldn't recognize it once I plugged it into the USB 3 hub. (And Bluetooth isn't working). And it seems that once you've booted from the USB installer once, it may not boot again properly. So I'm starting from scratch with two USB wired keyboards...one plugged into the built in ports to control the boot process, the other plugged directly into the USB 3 card, bypassing the hub.

We'll see if this is more successful. Right now, I'm rebuilding the boot USB disk all over again.
 
  • Like
Reactions: AlexSakha67
I haven't tested yet 11.1 beta for some reasons , maybe apple changed their Install app name as "Install macOS Big Sur 11.1 Beta 11.1" , so in this case even if BaseSystem fix works can't find from ramdisk the correct app folder.

But from my earlier test you could use a previous BaseSystem.dmg to load in ramdisk any recent "Install macOS BigSur Beta.app" , it is possible that installer language doesn't work properly so selecting English should easily work, anyway you could try also this to make a patched installer, just use any previous BaseSystemfix Installer, then replace only in this path: /Install macOS Big Sur*.app/Contents/SharedSupport/SharedSupport.dmg

also when replacing that file don't rename "Install macOS Big Sur Beta.app" or "Install macOS Big Sur.app", I mean apple macOS has some their routines that automatically rename those aliases installer app to the main non English system language, when this happens don't rename it to English otherwise that app is no more valid, you should use the name that macOS automatically chosen and renamed that alias .app folder , if you rename again to English that folder the installer will show grey screen.

So I guess replacing only the updated "SharedSupport.dmg" should work with any patched BigSurBaseSystemfix.dmg and any language selected:
Code:
cp /Applications/*.app/Contents/SharedSupport/SharedSupport.dmg /Volumes/Install macOS Big Sur*/*.app/Contents/SharedSupport/
Thank you jackluke, that worked.
Now MBP5,2 is running 11.1beta on a USB disk.

I made a new USB installer medium with createinstallmedia of 11.0.1 (20B50), applied your BigSur BaseSystem legacy usb fix/fix2, then replaced on the USB medium the SharedSupport.dmg with the one from 11.1beta I have on my Catalina disk. Installer booted and installation fine, applied legacy USB fix for post-install.

I think for future betas I'll use the method again, it is a fast way to update the USB installer.
 

Attachments

  • Bildschirmfoto 2020-11-25 um 00.15.33.png
    Bildschirmfoto 2020-11-25 um 00.15.33.png
    66.7 KB · Views: 126
  • Like
Reactions: macinfo
I am SOOOO close. I managed to get the installer USB drive to boot properly in BigMac patcher. And for the life of me, I cannot get a wired keyboard to work. I have an ancient iMac one (and puck mouse) from iMac G3 days I use for stuff like this plugged into one of the built in ports. And I have a more recent wired USB keyboard and mouse plugged into the USB 3 card. Both mice work. A trackpad plugged into the USB port works. Neither keyboard is alive.

Update: in a fit of desperation, I tried my newest keyboard, a modern Magic Keyboard connected via lightning/USB. That one is working. Go figure. Onward!
 
Last edited:
I am SOOOO close. I managed to get the installer USB drive to boot properly in BigMac patcher. And for the life of me, I cannot get a wired keyboard to work. I have an ancient iMac one (and puck mouse) from iMac G3 days I use for stuff like this plugged into one of the built in ports. And I have a more recent wired USB keyboard and mouse plugged into the USB 3 card. Both mice work. A trackpad plugged into the USB port works. Neither keyboard is alive.

Update: in a fit of desperation, I tried my newest keyboard, a modern Magic Keyboard connected via lightning/USB. That one is working. Go figure. Onward!
I am SOOOO close. I managed to get the installer USB drive to boot properly in BigMac patcher. And for the life of me, I cannot get a wired keyboard to work. I have an ancient iMac one (and puck mouse) from iMac G3 days I use for stuff like this plugged into one of the built in ports. And I have a more recent wired USB keyboard and mouse plugged into the USB 3 card. Both mice work. A trackpad plugged into the USB port works. Neither keyboard is alive.

Update: in a fit of desperation, I tried my newest keyboard, a modern Magic Keyboard connected via lightning/USB. That one is working. Go figure. Onward!
You are doing better than me on the install. I followed Big Sur macOS 11 Mac Pro patcher to the Tee. I get the install to work in Mac OS terminal before the first boot. Then when it does the reboot it start loading, then constant reboot at the same spot. The progress bar goes for about 5 seconds then reboots in the same spot. I have tried 4 different SSDs. I need a break. Will start back in one hour.
 
OK, after trying the install twice, I keep getting the following error while trying to do the postinstall script:

Warning: com.apple.driver.KextExcludeList was not found!

At this point other errors happen that seem to be related to it.

While I can get the main installer to run, I don't seem to have any luck with it doing the reboot steps after it. I'm thinking it ends up defaulting to the main boot drive (which is internal, an SSD) which means I'll probably have to disconnect it in order for all this to work.

it almost seems like it would be easier to install BigSur on a machine that is able to actually run BigSur, then take that drive, run the postinstall.sh program and voila!
 
  • Like
Reactions: AlexSakha67
OK, after trying the install twice, I keep getting the following error while trying to do the postinstall script:

Warning: com.apple.driver.KextExcludeList was not found!

At this point other errors happen that seem to be related to it.

While I can get the main installer to run, I don't seem to have any luck with it doing the reboot steps after it. I'm thinking it ends up defaulting to the main boot drive (which is internal, an SSD) which means I'll probably have to disconnect it in order for all this to work.

it almost seems like it would be easier to install BigSur on a machine that is able to actually run BigSur, then take that drive, run the postinstall.sh program and voila!
I tried that with no luck, installed Big Sur on my 2015 Mac Book Pro. I had the same reboot problem as before rebooting.
 
You are doing better than me on the install. I followed Big Sur macOS 11 Mac Pro patcher to the Tee. I get the install to work in Mac OS terminal before the first boot. Then when it does the reboot it start loading, then constant reboot at the same spot. The progress bar goes for about 5 seconds then reboots in the same spot. I have tried 4 different SSDs. I need a break. Will start back in one hour.

In the end, the exact same thing happened to me. So I've giving up for the evening. This may work on the 4,1 and 5,1 Mac Pros but the 3,1 is still a big problem.
 
Very helpful post indeed, thanks!
I am also installing 11.1 on an MBP5,2, using jackluke's BigSurBaseSystemFix patching of the installer.
While it was always fine upto 11.0.1, I am still busy with setting up 11.1 installation.
My USB installer won't boot right away. Two observations I wanted to share now, before I have success:
- seems that the installer for 11.1 beta needs English language setup, as was the case for earlier 11.0 betas (delete the language entries from nvram with sudo nvram -d prev-lang:kbd and sudo nvram -d prev-lang-diags:kbd, unless it indicates English already)
- the file name of macOS Big Sur Beta installieren.app looks as if there were two blanks in the string "macOS Big Sur "while there is in fact two times the sequence hex C2 A0, maybe only in the file name generated in my German setup
- in a private communication jackluke suggested to plug the 11.1 installer.app into a USB installer prepared with 11.0.1. Trying that now.

EDIT: not quite there yet. I get to the language selection screen, but even when choosing English, I get a grey screen (mouse present and moving) instead of the recovery screen with jackluke's extras.
@RogueB , on which system did you perform the createinstallmedia and patching, and what was your language setup? I used Catalina 10.15.7, so far German, now will try in English.
Hello hvds,

I had the same problem, with USB installer failing to boot, however, since I am located on the west coast of USA, the default language (English) was not the issue. BigSur 11.1 USB stick would not boot from either open-core nor apple boot selector. Given the encountered problems I opted to reinstall Big Sur 11.0.1 (official release) back onto the USB stick (using creatinstallmedia), then use Catalina 10.15.7 installation to install Big Sur 11.1 directly onto second partition.

Just for clarity, SSD in my computer has two partitions; one partition holds Mojave and Catalina systems (in two separate containers, titled Macintosh SSD and Catalina OS); the second partition holds container for BigSurBeta.

While booted from Catalina 10.15.7, I used Asentientbot's Hex3.app to initiate installation of Big Sur onto its own partition. The system installation involved several self-reboots, and I let it proceed until it entered a boot-loop ( same progress bar progression and time to reboot). Then, I pressed the Option Key to boot into the apple drive selector, and chose USB Big Sur 11.0.1 installer as my target.

The USB drive booted without a problem and I was able to apply jackluke's patches as described in my post above.
While I couldn't boot into Big Sur SSD partition from apple boot drive selector ( reboot ensued), I was able to boot successfully into Big Sur Beta 11.1 via open-core.

I am typing this post from Big Sur 11.1 installation. Internal speakers, microphone, brightness control and WiFi are fully operational, trim is enabled; the only thing missing is the graphics acceleration.

Hope this may be of help.

Screen Shot 2020-11-24 at 21.31.09.png

Screen Shot 2020-11-24 at 21.31.09 1.png
B
 
Last edited:
i have a problem, my graphics are not running
i have installed an intel hd3000, and my sound and wifi are not working.
is there a patch for the macbook air4,1 that works again?

lg
You need to try opencore @jackluke bigsur fixes. You should be able to get it on the forum.
 
Hi all,

I'm trying to install Big Sur on my Mac Pro 3,1.
I have created an external USB Disk using BigMac 🍔
Code:
sudo ./preinstall.sh
After that I have executed the Big Sur Installation from my Catalina 10.15.7.
The Big Sur Installation tool complete the first part and ask me to reboot.
When I reboot the Mac Pro reboot every time with a:

Panic Stackshot Succeded ** Bytes Traced...

What I miss? I'm unable to find suggestions to this problem.

Thanks
 
Hi all,

I'm trying to install Big Sur on my Mac Pro 3,1.
I have created an external USB Disk using BigMac 🍔
Code:
sudo ./preinstall.sh
After that I have executed the Big Sur Installation from my Catalina 10.15.7.
The Big Sur Installation tool complete the first part and ask me to reboot.
When I reboot the Mac Pro reboot every time with a:

Panic Stackshot Succeded ** Bytes Traced...

What I miss? I'm unable to find suggestions to this problem.

Thanks

In my case, was panic bootloop because of old bluetooth adapter. When i removed it, all work fine.
 
  • Wow
Reactions: freqrider
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.