Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 11 Big Sur on Unsupported Macs Thread
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
-
- Tags
- 10.16 macos unsupported
- Sort by reaction score
- Status
Could somebody help me get started with Big Sur Public Beta (or Dev Beta 4) on a MacBookPro4,1 (early 2008)? BootROM APFS-patched already, Mojave and Catalina running nicely, thanks to @dosdude1’s various patchers.
Most probably LegacyUSB patch is needed there, and big-sur-micropatcher (at v0.0.20) has no support for these machines yet, right?
Also a big Thank You! to all contributors here.
Most probably LegacyUSB patch is needed there, and big-sur-micropatcher (at v0.0.20) has no support for these machines yet, right?
Also a big Thank You! to all contributors here.
Last edited:
Just came across this. Not sure if it's it was created by, or of any use to developers here: https://github.com/barrykn/big-sur-micropatcher. Not a developer but, would be willing to help out. I have a MacBook Pro 8,2 running Catalina thanks to DosDude1.
I seem to be having a problem with this install method. I downloaded the InstallAssistant.pkg file. When I click on it, it starts the installer. I chose an external 250GB USB drive I have plugged called 'Untitled'. It installs the 'Install macOS Big Sur Beta.app' into the /Applications directory of 'Untitled'. This process fails; says it can't find what it needs from the Interwebz. I even tried command line with the standard command:
sudo /Applications/Install\ macOS\ Big\ Sur\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled
What I get is this:
Class IASNightInstallSupport is implemented in both /System/Library/PrivateFrameworks/IASUtilities.framework/Versions/A/IASUtilities (0x7fff91cf80b0) and /Applications/Install macOS Big Sur Beta.app/Contents/Frameworks/OSInstallerSetup.framework/Versions/A/Frameworks/IAESD.framework/Versions/A/Frameworks/IAInstallerUtilities.framework/Versions/A/IAInstallerUtilities (0x107f23ac0). One of the two will be used. Which one is undefined.
objc[79848]: Class IASSystemInformation is implemented in both /System/Library/PrivateFrameworks/IASUtilities.framework/Versions/A/IASUtilities (0x7fff91cf81f0) and /Applications/Install macOS Big Sur Beta.app/Contents/Frameworks/OSInstallerSetup.framework/Versions/A/Frameworks/IAESD.framework/Versions/A/Frameworks/IAInstallerUtilities.framework/Versions/A/IAInstallerUtilities (0x107f23bd8). One of the two will be used. Which one is undefined.
/Applications/Install macOS Big Sur Beta.app does not appear to be a valid OS installer application.
So, I can't even create an install yet to even execute the micropatcher.sh script.
Any ideas? Can you help?
sudo /Applications/Install\ macOS\ Big\ Sur\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled
What I get is this:
Class IASNightInstallSupport is implemented in both /System/Library/PrivateFrameworks/IASUtilities.framework/Versions/A/IASUtilities (0x7fff91cf80b0) and /Applications/Install macOS Big Sur Beta.app/Contents/Frameworks/OSInstallerSetup.framework/Versions/A/Frameworks/IAESD.framework/Versions/A/Frameworks/IAInstallerUtilities.framework/Versions/A/IAInstallerUtilities (0x107f23ac0). One of the two will be used. Which one is undefined.
objc[79848]: Class IASSystemInformation is implemented in both /System/Library/PrivateFrameworks/IASUtilities.framework/Versions/A/IASUtilities (0x7fff91cf81f0) and /Applications/Install macOS Big Sur Beta.app/Contents/Frameworks/OSInstallerSetup.framework/Versions/A/Frameworks/IAESD.framework/Versions/A/Frameworks/IAInstallerUtilities.framework/Versions/A/IAInstallerUtilities (0x107f23bd8). One of the two will be used. Which one is undefined.
/Applications/Install macOS Big Sur Beta.app does not appear to be a valid OS installer application.
So, I can't even create an install yet to even execute the micropatcher.sh script.
Any ideas? Can you help?
Yes! The macOS Big Sur Beta.app is in Applications directory on the external USB drive.
While installing InstallAssistant.pkg I'll get:
Then when running the Install macOS Big Sur Beta.app from external drive /Applications dir I'll get:
By the way, I'm running all this on a late 2012 iMac.
Please try create the USB installer again as format below.
Name: Untitled
Format: Mac OS Extended (Journaled)
Scheme: GUID Partition Map
Same exact problem. I erased my USB drive with the parameters above. I then ran InstallAssistant.pkg - failed with the same error message I showed. The .app was again placed in an /Applications directory. I copied that .app into my main /Applications dir and ran the createinstallmedia from CLI and it still gave the same error:
sudo /Applications/Install\ macOS\ Big\ Sur\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled
objc[88196]: Class IASNightInstallSupport is implemented in both /System/Library/PrivateFrameworks/IASUtilities.framework/Versions/A/IASUtilities (0x7fff91cf80b0) and /Applications/Install macOS Big Sur Beta.app/Contents/Frameworks/OSInstallerSetup.framework/Versions/A/Frameworks/IAESD.framework/Versions/A/Frameworks/IAInstallerUtilities.framework/Versions/A/IAInstallerUtilities (0x10b60cac0). One of the two will be used. Which one is undefined.
objc[88196]: Class IASSystemInformation is implemented in both /System/Library/PrivateFrameworks/IASUtilities.framework/Versions/A/IASUtilities (0x7fff91cf81f0) and /Applications/Install macOS Big Sur Beta.app/Contents/Frameworks/OSInstallerSetup.framework/Versions/A/Frameworks/IAESD.framework/Versions/A/Frameworks/IAInstallerUtilities.framework/Versions/A/IAInstallerUtilities (0x10b60cbd8). One of the two will be used. Which one is undefined.
/Applications/Install macOS Big Sur Beta.app does not appear to be a valid OS installer application.
Thank you! Team @barrykn - big-sur-micropatcher
Works like a dream ... took about an hour to install (using USB2 thumb drive and slow mo HDD)
but I got there! BS also updated my Canon printer drivers and I find no issues, so far. I owe you guys
lunch or something!
Regards.
Works like a dream ... took about an hour to install (using USB2 thumb drive and slow mo HDD)
but I got there! BS also updated my Canon printer drivers and I find no issues, so far. I owe you guys
lunch or something!
Regards.
Attachments
Using @Barry K. Nathan's patcher 0.0.20 I created a series of snapshots during my patching. Is there an easy way to revert back to the original state before applying the first patches, i.e. to the stock installation state? Cannot find a suitable doc how to handle these snapshots...
So I had BigSur beta 4 installed and booted through Opencore. Then I decided to boot it without OpenCore. No patches except SIP disabled (through rEFInd):
And I found the Preboot volume's path and I did:
Then I added the following, saved the file and I booted straight to BigSur from rEFInd!
Code:
nvram csr-active-config
csr-active-config w%08%00%00
Code:
sudo -s
sudo nano /System/Volumes/Preboot/4E2EE6EB-C9EA-3217-813B-33C40F31AB8C/System/Library/CoreServices/PlatformSupport.plistDownload the InstallAssistant.pkg at post 2982 and try it again.
It seems like you're new here. Yes, that is probably the BEST place to go as of right now. It's developed by Barry K. Nathan and is really awesome and as stable as it gets.
I downloaded the InstallAssistant from 2982, I had all the same exact problems.
sudo /Applications/Install\ macOS\ Big\ Sur\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes//Untitled/
objc[1139]: Class IASNightInstallSupport is implemented in both /System/Library/PrivateFrameworks/IASUtilities.framework/Versions/A/IASUtilities (0x7fff8aad70b0) and /Applications/Install macOS Big Sur Beta.app/Contents/Frameworks/OSInstallerSetup.framework/Versions/A/Frameworks/IAESD.framework/Versions/A/Frameworks/IAInstallerUtilities.framework/Versions/A/IAInstallerUtilities (0x10fb18ac0). One of the two will be used. Which one is undefined.
objc[1139]: Class IASSystemInformation is implemented in both /System/Library/PrivateFrameworks/IASUtilities.framework/Versions/A/IASUtilities (0x7fff8aad71f0) and /Applications/Install macOS Big Sur Beta.app/Contents/Frameworks/OSInstallerSetup.framework/Versions/A/Frameworks/IAESD.framework/Versions/A/Frameworks/IAInstallerUtilities.framework/Versions/A/IAInstallerUtilities (0x10fb18bd8). One of the two will be used. Which one is undefined.
/Applications/Install macOS Big Sur Beta.app does not appear to be a valid OS installer application.
Anyone got it (Public Beta) working on MacBook5,1 (13-inch, Aluminum, Late 2008, upgraded with 8GB RAM and SSD)? Please share your experience and steps. Mine is running macOS Catalina 10.15.6 (thanks to dosdude1).
[/QUOTE]
I'm formatting my USB 32 GB and downloading the InstallAssistant.pkg at post 2982. I'll format my Big Sur SSD and reinstall the Public beta. I'll post the info later.
I reinstalled the Big Sur Public beta no problem with Barry instruction step 1 to 8 for my cMP 5,1 mid 2012
Did you open a Terminal window, drag and drop micropatcher.sh into the Terminal window, drag and drop the USB macOS into the Terminal window?
Follow Barry Quick instructions for use and you will install Big Sur without problem.
Quick instructions for use:
1. Obtain a copy of the macOS Big Sur Developer Preview and use `createinstallmedia` as usual to create a bootable USB stick with the installer and recovery environment, as you would on a supported Mac. This patcher is easier to use if the installer USB stick is not renamed after `createinstallmedia` is used, but it can still work if the USB stick has been renamed (see next step).
2. Download this micropatcher, then run `micropatcher.sh` to patch the USB stick. (If you are viewing this on GitHub, and you probably are, then click "Clone" then "Download ZIP".) If the USB stick has been renamed or micropatcher.sh is otherwise unable to find the USB stick, then try specifying the pathname of the USB stick to micropatcher.sh. The easiest way to do that is to open a Terminal window, drag and drop micropatcher.sh into the Terminal window, go back to Finder, choose Computer from the Go menu, drag and drop the USB stick into the Terminal window, then press Return.
3. Since Disk Utility in Big Sur may have new bugs, this may be a good time to use Disk Utility in High Sierra/Mojave/Catalina to do any partitioning or formatting you may need.
4. Boot from the USB stick.
5. If you need to do any partitioning or formatting with Disk Utility, and you didn't do it in step 5, it's best to do it now.
6. Open Terminal (in the Utilities menu), then run `/Volumes/Image\ Volume/set-vars.sh`. This script will change boot-args and csrutil settings as needed, and also set things up so the Installer will run properly. Don't forget that tab completion is your friend! You can type `/V<tab>/I<tab>/se<tab>` at the command prompt -- that's much less typing! (Run `/Volumes/Image\ Volume/set-vars.sh -v` instead if you want verbose boot, which can be very useful for troubleshooting.)
7. Quit Terminal then start the Installer as you would on a supported Mac.
8. Come back in an hour or two and you should be at the macOS setup region prompt! (If you actually watch the installation process, don't be surprised if it seems to get stuck at "Less than a minute remaining..." for a long time. Allow it well over half an hour. It should eventually reboot on its own and keep going.)
9. If you're on a Late 2013 iMac, or you've replaced the 802.11n card in your 2012/2013 Mac with an 802.11ac card, you're done. Otherwise, press Command-Q and wait a few seconds, then the Setup Assistant should let you shut down. After you shut down, start up again and boot from the patched installer USB again, then open Terminal again. This time, run `/Volumes/Image\ Volume/patch-kexts.sh /Volumes/<name of Big Sur volume>`, for example `/Volumes/Image\ Volume/patch-kexts.sh /Volumes/Macintosh\ HD`. It needs to be the name of the *system* volume. This will patch your Big Sur installation to add working Wi-Fi. (On 2011 MacBook Pro 13" and 2011 MacBook Air, add a "--2011" option after the ".sh" and before the volume name, for example `/Volumes/Image\ Volume/patch-kexts.sh --2011 /Volumes/Macintosh\ HD`, to fix sound, brightness control, and sleep as well as Wi-Fi. If you're going to use the installation on a 2010 or older Mac, add a "--all" option likewise.) As of patcher v0.0.18, it is now possible to do this step without booting from the patched installer USB -- just open Terminal and run `/Volumes/Install\ macOS\ Big\ Sur\ Beta/patch-kexts.sh` with any command line options if needed (such as `/Volumes/Install\ macOS\ Big\ Sur\ Beta/patch-kexts.sh --2011`), but do not specify a volume name and patch-kexts.sh will automatically default to the boot drive.
10. If you will be using the Big Sur installation on a different Mac (for instance, installing on a 2011 or later Mac and using it on a 2009 or 2010 Mac), it is possible that the other Mac (the one not used for installation) may try to boot off the wrong APFS snapshot. To prevent this, run zap-snapshots.sh on your System volume, to remove all but the most recent snapshot. For instance, `/Volumes/Image Volume/zap-snapshots.sh /Volumes/Macintosh\ HD`. (Or you can also do this if you are running low on disk space.) This is basically the same as step 9, but with `zap-snapshots` instead of `patch-kexts`, and without any command line options like `--2011` or `--all`.
11. After step 9 (and 10 if necessary), reboot into your Big Sur installation.
12. On 2011 and older Macs, once you have installed Big Sur, make sure to enable Reduce Transparency to eliminate many seemingly random crashes, and if icons on the right-hand side of the menu bar are invisible afterward, try Dark mode. (If you will be using the installation on a 2009/2010 Mac, it would be a good idea to finish the Setup Assistant on a 2011 or later Mac and enable Reduce Transparency before moving the installation over.)
13. (only for 2008 Mac Pros & 2010 or earlier models of other Macs) Before you move the installation over from a newer Mac, you need to set nvram variables. Normally this would be done by the set-vars.sh script in step 6, but you ran that script on a different Mac because the patched installer USB either will not boot on your Mac or will not provide a functioning keyboard/mouse/trackpad on your Mac. To set the nvram variables on the older Mac, first boot into the installer USB or DVD for OS X Mavericks (10.9.5) or older. Yosemite (10.10) and later will not work! Then open Terminal and run the following commands (pay attention to zero vs. 8 -- it's 'w%08%00%00'):
nvram csr-active-config='w%08%00%00'
nvram boot-args="-no_compat_check"
I'm formatting my USB 32 GB and downloading the InstallAssistant.pkg at post 2982. I'll format my Big Sur SSD and reinstall the Public beta. I'll post the info later.
I reinstalled the Big Sur Public beta no problem with Barry instruction step 1 to 8 for my cMP 5,1 mid 2012
Did you open a Terminal window, drag and drop micropatcher.sh into the Terminal window, drag and drop the USB macOS into the Terminal window?
Follow Barry Quick instructions for use and you will install Big Sur without problem.
Quick instructions for use:
1. Obtain a copy of the macOS Big Sur Developer Preview and use `createinstallmedia` as usual to create a bootable USB stick with the installer and recovery environment, as you would on a supported Mac. This patcher is easier to use if the installer USB stick is not renamed after `createinstallmedia` is used, but it can still work if the USB stick has been renamed (see next step).
2. Download this micropatcher, then run `micropatcher.sh` to patch the USB stick. (If you are viewing this on GitHub, and you probably are, then click "Clone" then "Download ZIP".) If the USB stick has been renamed or micropatcher.sh is otherwise unable to find the USB stick, then try specifying the pathname of the USB stick to micropatcher.sh. The easiest way to do that is to open a Terminal window, drag and drop micropatcher.sh into the Terminal window, go back to Finder, choose Computer from the Go menu, drag and drop the USB stick into the Terminal window, then press Return.
3. Since Disk Utility in Big Sur may have new bugs, this may be a good time to use Disk Utility in High Sierra/Mojave/Catalina to do any partitioning or formatting you may need.
4. Boot from the USB stick.
5. If you need to do any partitioning or formatting with Disk Utility, and you didn't do it in step 5, it's best to do it now.
6. Open Terminal (in the Utilities menu), then run `/Volumes/Image\ Volume/set-vars.sh`. This script will change boot-args and csrutil settings as needed, and also set things up so the Installer will run properly. Don't forget that tab completion is your friend! You can type `/V<tab>/I<tab>/se<tab>` at the command prompt -- that's much less typing! (Run `/Volumes/Image\ Volume/set-vars.sh -v` instead if you want verbose boot, which can be very useful for troubleshooting.)
7. Quit Terminal then start the Installer as you would on a supported Mac.
8. Come back in an hour or two and you should be at the macOS setup region prompt! (If you actually watch the installation process, don't be surprised if it seems to get stuck at "Less than a minute remaining..." for a long time. Allow it well over half an hour. It should eventually reboot on its own and keep going.)
9. If you're on a Late 2013 iMac, or you've replaced the 802.11n card in your 2012/2013 Mac with an 802.11ac card, you're done. Otherwise, press Command-Q and wait a few seconds, then the Setup Assistant should let you shut down. After you shut down, start up again and boot from the patched installer USB again, then open Terminal again. This time, run `/Volumes/Image\ Volume/patch-kexts.sh /Volumes/<name of Big Sur volume>`, for example `/Volumes/Image\ Volume/patch-kexts.sh /Volumes/Macintosh\ HD`. It needs to be the name of the *system* volume. This will patch your Big Sur installation to add working Wi-Fi. (On 2011 MacBook Pro 13" and 2011 MacBook Air, add a "--2011" option after the ".sh" and before the volume name, for example `/Volumes/Image\ Volume/patch-kexts.sh --2011 /Volumes/Macintosh\ HD`, to fix sound, brightness control, and sleep as well as Wi-Fi. If you're going to use the installation on a 2010 or older Mac, add a "--all" option likewise.) As of patcher v0.0.18, it is now possible to do this step without booting from the patched installer USB -- just open Terminal and run `/Volumes/Install\ macOS\ Big\ Sur\ Beta/patch-kexts.sh` with any command line options if needed (such as `/Volumes/Install\ macOS\ Big\ Sur\ Beta/patch-kexts.sh --2011`), but do not specify a volume name and patch-kexts.sh will automatically default to the boot drive.
10. If you will be using the Big Sur installation on a different Mac (for instance, installing on a 2011 or later Mac and using it on a 2009 or 2010 Mac), it is possible that the other Mac (the one not used for installation) may try to boot off the wrong APFS snapshot. To prevent this, run zap-snapshots.sh on your System volume, to remove all but the most recent snapshot. For instance, `/Volumes/Image Volume/zap-snapshots.sh /Volumes/Macintosh\ HD`. (Or you can also do this if you are running low on disk space.) This is basically the same as step 9, but with `zap-snapshots` instead of `patch-kexts`, and without any command line options like `--2011` or `--all`.
11. After step 9 (and 10 if necessary), reboot into your Big Sur installation.
12. On 2011 and older Macs, once you have installed Big Sur, make sure to enable Reduce Transparency to eliminate many seemingly random crashes, and if icons on the right-hand side of the menu bar are invisible afterward, try Dark mode. (If you will be using the installation on a 2009/2010 Mac, it would be a good idea to finish the Setup Assistant on a 2011 or later Mac and enable Reduce Transparency before moving the installation over.)
13. (only for 2008 Mac Pros & 2010 or earlier models of other Macs) Before you move the installation over from a newer Mac, you need to set nvram variables. Normally this would be done by the set-vars.sh script in step 6, but you ran that script on a different Mac because the patched installer USB either will not boot on your Mac or will not provide a functioning keyboard/mouse/trackpad on your Mac. To set the nvram variables on the older Mac, first boot into the installer USB or DVD for OS X Mavericks (10.9.5) or older. Yosemite (10.10) and later will not work! Then open Terminal and run the following commands (pay attention to zero vs. 8 -- it's 'w%08%00%00'):
nvram csr-active-config='w%08%00%00'
nvram boot-args="-no_compat_check"
Attachments
Last edited:
One of my friend achieved so somehow, however it isn't really good for now mate... His one is now having sound & Wi-Fi malfunction with lack of hardware acceleration. It could be something wrong from his side, or perhaps didn't apply the updated techniques those may be solutions for the issues, but that is pretty much I can say about it for now.
Just updated my Mac Pro 4,1 (upgraded to 5,1) using the same patcher and installation method. Worked like a charm. Now running developer beta 4 smoothly (upgraded from Catalina 10.15.6). Interestingly enough my model year (2009) shows up in my "About This Mac" page.
is there a way to add this to a USB Installer to aid installation on a macpro 4.1/5.1
This happened to me. I ran the InstallAssistant from the Public Beta and the resultant Installer in Applications was invalid and had the slashed circle through its icon, even though the app installer gave up a success message. I trashed that 12.3gb BS installer and tried again with the same downloaded file (didn’t DL it again). This time the BS installer was valid and worked fine to create a USB to then patch.
Just successfully updated my iMac late 2013 to Big Sur Developer beta 4. This time the only difference from previous post #2,707 was I didn't have to boot into Catalina at all.
I downloaded the beta from the link on this thread http://swcdn.apple.com/content/down...m7ounuabziajlktg8nhoptis/InstallAssistant.pkg and ran the installer on Big Sur. It placed Install Big Sur Beta in Big Sur's applications folder. I then ran createinstallmedia again in Big Sur Terminal to create my usb thumb drive. Ran Barry's micropatcher also from Big Sur Terminal. From there everything was the same as before - boot with the usb thumb drive, run terminal commands and update install to Big Sur drive.
I downloaded the beta from the link on this thread http://swcdn.apple.com/content/down...m7ounuabziajlktg8nhoptis/InstallAssistant.pkg and ran the installer on Big Sur. It placed Install Big Sur Beta in Big Sur's applications folder. I then ran createinstallmedia again in Big Sur Terminal to create my usb thumb drive. Ran Barry's micropatcher also from Big Sur Terminal. From there everything was the same as before - boot with the usb thumb drive, run terminal commands and update install to Big Sur drive.
Here is one to create a bootable Big Sur usb installer just ignore the open core choose usb creation then after apple BarryKn's mircorpatch https://github.com/chris1111/Install-Media-BS-OC
I can’t have the hardware acceleration function of the Microsoft Remote Desktop work on my iMac 27” 2013 with the latest big sur beta 4 installed. It will crash when i attempt to connect to the Remote Desktop.
Does anyone having the same issue regarding the hardware acceleration? Any solution?
I have tried to run it on my MBP 2017 with also big sur beta 4 and the hardware acceleration function work properly, which I can eliminate the reason of running the app on unsupported macOS
Does anyone having the same issue regarding the hardware acceleration? Any solution?
I have tried to run it on my MBP 2017 with also big sur beta 4 and the hardware acceleration function work properly, which I can eliminate the reason of running the app on unsupported macOS