To get 4K HEVC with your RX580 you need OpenCore as described in this post.
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
For booting BigSur on newer opencore from 0.6.0 version try this in config.plist :
<key>SecureBootModel</key>
<string>Disabled</string>
then from opencore currently Lilu.kext doesn't work on BigSur, so you can't inject any graphics kext, instead you can manually install them with kmutil in /System/Library/Extensions/ , but with snapshot booting is not so easy, so if you used my "basesystem fix", then reboot to the USB Installer and try to use from Utilities menu
BigSurFixes disable snapshot or delete snapshot (that includes also a script to rebuild kernelcollection from normal booting) , so at next reboot, from BigSur normal booting you could use sudo mount -uw / to allow any system modification, then simply replace @Ausdauersportler kext for your iMac with upgraded Metal GPU, open terminal and type sudo -s ; /kc.shAt next reboot Brightness control should work.
Last edited:
so fast this is one of very clear and easy to understand step by step instructions to install big sir on unsupported mac.
good work. Thanks.
Although kext-patch works and fix Wifi card in Mac mini 2012 (late) I got this error during the process
I don't know if they are relevant
Can someone clarify me, thanks
I don't know if they are relevant
Can someone clarify me, thanks
Code:
Copying deferred prelinked kernels in /System/Volumes/Update/mnt1...
/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/kext_tools/kext_tools-692.40.7/kc_staging.m.279: Encountered error while inspecting path: Error Domain=NSCocoaErrorDomain Code=260 "The folder “PrelinkedKernels” doesn’t exist." UserInfo={NSFilePath=/System/Volumes/Update/mnt1/Library/Apple/System/Library/PrelinkedKernels, NSUserStringVariant=(
Folder
), NSUnderlyingError=0x7fee2bc0c5d0 {Error Domain=NSOSStatusErrorDomain Code=-43 "fnfErr: File not found"}}
/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/kext_tools/kext_tools-692.40.7/kc_staging.m.279: Encountered error while inspecting path: Error Domain=NSCocoaErrorDomain Code=260 "The folder “PrelinkedKernels” doesn’t exist." UserInfo={NSFilePath=/System/Volumes/Update/mnt1/Library/Apple/System/Library/PrelinkedKernels, NSUserStringVariant=(
Folder
), NSUnderlyingError=0x7fee2bc131b0 {Error Domain=NSOSStatusErrorDomain Code=-43 "fnfErr: File not found"}}I had the same for each beta version I installed with micropatcher on my mini 2011.
However the installation worked well, with wifi and all. I took that as warnings instead of errors
Great experience with Big Sur and Mac mini 2012
I am thinking update my Catalina partition and star working with Big Sur
- Installation process seems absolutely stable, update process is not so heavy to deal. Permanent USB/SD sticker and booting take 30 minutes in my SSD and patch Wifi is just use terminal and reboot. Even I take care that my "auto_smb" file in /etc/ is intact after OS update (with Catalina OTA update the file change and I need to copy each time)
- The system works great, stable and smooth. No difference with Catalina, even better
-Catalyst system apps like Photos, Music or iMessage works better for me (placebo sensation?)
What do you think? Could I update with USB installer Big Sur 11.0.1 RC over Catalina without risk? (in this moment I have 2 partition, one with Catalina and other with Big Sur 11.0.1 RC)
I am thinking update my Catalina partition and star working with Big Sur
- Installation process seems absolutely stable, update process is not so heavy to deal. Permanent USB/SD sticker and booting take 30 minutes in my SSD and patch Wifi is just use terminal and reboot. Even I take care that my "auto_smb" file in /etc/ is intact after OS update (with Catalina OTA update the file change and I need to copy each time)
- The system works great, stable and smooth. No difference with Catalina, even better
-Catalyst system apps like Photos, Music or iMessage works better for me (placebo sensation?)
What do you think? Could I update with USB installer Big Sur 11.0.1 RC over Catalina without risk? (in this moment I have 2 partition, one with Catalina and other with Big Sur 11.0.1 RC)
You don’t need to change anything for WIFI, your hardware supported.
After created the USB installer with Barry’s micropatcher.sh.
Boot from USB installer.
In Recovery Terminal just type:
/Volumes/Image\ Volume/set-vars.sh
Install macOS.
Wait for it...
Btw, set-vars.sh is decrypted since Big Sur broke nvram commands a while ago. You should be using install-setvars.sh to create an EFI partition on your drive that will set the boot-args and SIP statuses on boot. The trampoline app in the micropatcher takes care of insert-hax.sh.
You may don't have cMP mid 2012 with all hardwares supported such as GPU, BT 4.2.
I never have had any issue with install Big Sur from day one with Jackluke or Barry's micropatchers.
Just wanted to post about my iMac11,2. Got everything up and running with a flashed K1100M, using barryk's micropatcher and khronokernel's OpenCore fix. Only things that don't work are brightness and sleep.. this is my first run with upgrading and flashing a GPU for one of these computers--so I might be totally oblivious on a fix for brightness/sleep. Regardless, I'm glad to have Big Sur on this machine. Big thanks to the devs for making this possible.
I've followed this guide and it worked flawlessly for Mid 2012 Macbook Pro 13, Thanks.
Attachments
Some additional notes about my BigSur installer BaseSystem fix :
- To install or upgrade BigSur on unsupported Mac use from Utilities menu the ASentientBot Hax3 installer quick fix or from main menu Hax3 fix clicking on the upper right finder menu
- During the stage1 installer if you don't notice the progress bar, just click any point on the background window or simply open the installer log with CMD+L
- When I write "Arrandale MacBookPro" it includes all its derived architectures (Lynnfield and Clarksdale iMac, Nehalem and Westmere MacPro and others), for these machines to boot the BigSur kernel and Installer you need first any Opencore with khronokernel SSDT ACPI fix applied or you could use my external OpenCore4b1:
https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-29138842
- Ethernet driver is not included in Utilities patches (even if it's in kext folder), because I had issues when adding it with kmutil and using opencore, but without opencore it works so you can install it
- iSight fix is only required for Mac with Nvidia non-Metal GPU, for dualGPUs Mac use instead "BigSurFixes graphics framebuffer"
- In kext folder I used naming as kext1 or kext2 for backup or patching so don't rename these, you can even add your custom kext to that folder and they are kmutil installed through "BigSurFixes snapshot booting" or "BigSurFixes disabled snapshot"
- CoreBrightness patched for Night Shift even if still works is not included (and also the AMFI disable library validation), for now I preferred to keep the stock BigSur framework
- LegacyUSBInjector is merged with IOUSBHostFamily in order to use the stock current BigSur 11.0.1 kmutil and kcditto
- Installing on internal SATA disk there are no issues for automatic stage2 and stage3 installer phases but if you are installing non-APFS Mac on external USB target disk then you need to boot through opencore the stage2 "macOS Installer", reboot the Installer and apply the "BigSur stage2 installer fix" (after installation you can skip stage3 and apply "BigSur stage3 installer fix"), non-APFS Mac after the "BigSurFixes Legacy USB patches" can boot also without opencore, while for "Arrandale Mac" after any patch you need to apply the "BigSurFixes opencore preboot"
- To install or upgrade BigSur on unsupported Mac use from Utilities menu the ASentientBot Hax3 installer quick fix or from main menu Hax3 fix clicking on the upper right finder menu
- During the stage1 installer if you don't notice the progress bar, just click any point on the background window or simply open the installer log with CMD+L
- When I write "Arrandale MacBookPro" it includes all its derived architectures (Lynnfield and Clarksdale iMac, Nehalem and Westmere MacPro and others), for these machines to boot the BigSur kernel and Installer you need first any Opencore with khronokernel SSDT ACPI fix applied or you could use my external OpenCore4b1:
https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-29138842
- Ethernet driver is not included in Utilities patches (even if it's in kext folder), because I had issues when adding it with kmutil and using opencore, but without opencore it works so you can install it
- iSight fix is only required for Mac with Nvidia non-Metal GPU, for dualGPUs Mac use instead "BigSurFixes graphics framebuffer"
- In kext folder I used naming as kext1 or kext2 for backup or patching so don't rename these, you can even add your custom kext to that folder and they are kmutil installed through "BigSurFixes snapshot booting" or "BigSurFixes disabled snapshot"
- CoreBrightness patched for Night Shift even if still works is not included (and also the AMFI disable library validation), for now I preferred to keep the stock BigSur framework
- LegacyUSBInjector is merged with IOUSBHostFamily in order to use the stock current BigSur 11.0.1 kmutil and kcditto
- Installing on internal SATA disk there are no issues for automatic stage2 and stage3 installer phases but if you are installing non-APFS Mac on external USB target disk then you need to boot through opencore the stage2 "macOS Installer", reboot the Installer and apply the "BigSur stage2 installer fix" (after installation you can skip stage3 and apply "BigSur stage3 installer fix"), non-APFS Mac after the "BigSurFixes Legacy USB patches" can boot also without opencore, while for "Arrandale Mac" after any patch you need to apply the "BigSurFixes opencore preboot"
Last edited:
I've come up with a way to make completely unpatched Big Sur on an unsupported Mac keep booting after an NVRAM reset or after using @jackluke's sideloader to fetch updates. Using the sideloader this way is no longer a recommended way to run Big Sur, but I'm still playing around with it.
The trick is to have a boot file in the system boot partition which sets
The trick is to have a boot file in the system boot partition which sets
boot-args="-no_compat_check" and then exits, not restarts. Because it exits it drops through to the default OS.- Before starting, use Disk Utility to confirm that Big Sur is on the first partition on your hard drive; if it's not, this won't work
- Mount the Mac boot partition
- If there is anything other than the
Applefolder in/Volumes/efi/EFIthen you need to move those files out of the way first, into a new small FAT partition which you can create e.g. at the end of your hard drive; 50MB is enough to move the/EFI/Bootand/EFI/Microsoftboot-loader files for Windows; 20MB is enough for the/EFI/BOOTand/EFI/ubuntufiles for Ubuntu - The boot partition should now only contain
/EFI/Apple. If so, add a new/EFI/BOOTdirectory, and copy the single filebootx64.efifrom this zip file into there - Optionally run
sudo bless --folder /Volumes/efi/EFI/BOOT --label 'Restart Big Sur'
- Reboot and clear NVRAM (reboot holding Option, Command, P and R and wait for the second chime). Big Sur should just start.
- Reboot and start Big Sur via OpenCore. Restart and allow to reboot. Big Sur should just start.
Last edited:
How can the Install Big Sur Beta app be modified to allow install on a cMP 5,1 without the need of the micropatcher?
I mean no dis-respect to Barry K Nathan's great work
Is there a plist file that can be either deleted or modified inside the app package?
I can confirm that the un-patched Install Big Sur Beta app can be run from a booted Mojave or High Sierra install on a supported Mac and then installed on a external SSD using a SSD to usb adapter.
I have done this on my supported 2015 Macbook Pro and then when I put that SSD inside my cMP 5,1 it boots and runs without any patches needed or problems.
I mean no dis-respect to Barry K Nathan's great work
Is there a plist file that can be either deleted or modified inside the app package?
I can confirm that the un-patched Install Big Sur Beta app can be run from a booted Mojave or High Sierra install on a supported Mac and then installed on a external SSD using a SSD to usb adapter.
I have done this on my supported 2015 Macbook Pro and then when I put that SSD inside my cMP 5,1 it boots and runs without any patches needed or problems.
If you want another patcher for your Mac Pro got back to the download site of the micro patcher and read the first page.
You could find this:
GitHub - SuperBox64/bigmac: Big Mac, macOS 11 Big Sur and macOS Monterey disk installer and back up tool for Intel based Macs
Big Mac, macOS 11 Big Sur and macOS Monterey disk installer and back up tool for Intel based Macs - SuperBox64/bigmac
github.com
Please don't get me wrong, because I don't want to press or annoy anyone - Basically, I really appreciate the great activities so far and the helpful and very clear communication here.
But is there currently a realistic chance that all of this will eventually result in a patcher that is as easy, elegant and effective to use as @dosdude1 's patcher for Catalina? Maybe it's not just my opinion that this should actually and ultimately be the main goal. Because most of us should be typical Mac users (and not Terminal wizards) who still believe in the ideal of WYSIWYG and easy handling of complex processes. Personally, I am still very surprised and delighted that Macs that are no longer officially supported can still be patched for free. Nevertheless, I would also be willing to pay the price of a shareware program, for example, in order to provide my Mac with a current OS.
How do you see it?
But is there currently a realistic chance that all of this will eventually result in a patcher that is as easy, elegant and effective to use as @dosdude1 's patcher for Catalina? Maybe it's not just my opinion that this should actually and ultimately be the main goal. Because most of us should be typical Mac users (and not Terminal wizards) who still believe in the ideal of WYSIWYG and easy handling of complex processes. Personally, I am still very surprised and delighted that Macs that are no longer officially supported can still be patched for free. Nevertheless, I would also be willing to pay the price of a shareware program, for example, in order to provide my Mac with a current OS.
How do you see it?
Hi @jackluke I'm patching Mac mini 2010 (Macmini4,1) . Patcher #1 sholud patches the BS 11.0.1 RC USB Installer? Because it starts executing script without specifying the USB pendrive as I do with micropatcher. Patcher #2 closes immediately. I have 2 working installations: "BigSur EXT" (external usb 3.0 harddisk partition) and "BigSur SSD" (internal) . On both USB mouse and keyboard still not working without cmd +S , so I presume they aren't be patched. Now I launch the USB installer, but patch #2 has not been executed also if it was the target.
Last edited:
BaseSystem is not the BigSur installation, but it's a name that apple uses for the macOS Recovery or Installer environment, so my BaseSystem fix is for the Installer and booting from the patched Installer you can apply patches to the BigSur installation.
The BigSur BaseSystem fix is made of two scripts and both are required to patch the USB BigSur Installer, "legacy USB fix1" detects any stock USB BigSur Installer plugged and patch its BaseSystem to add my custom bash apps, after fix1 is completed, you have to unplug and plug again the USB Installer, then launch "legacy USB fix2" , once both fixes are applied to the USB BigSur Installer, you should boot from apple startup manager with alt-option key the Installer, from there you can apply the fixes to your BigSur installation.
In your case without using opencore is sufficient to apply from Utilities menu "BigSurFixes Legacy USB patches", just a minimal interaction is required, you should type your Preboot diskXs2 (showed in patching list) and the BigSur System Label you want to patch (without "quotes") for example:
BigSur Preboot: disk5s2 (if your BigSur System is on disk5s5)
BigSur Label: BigSur EXT (type without quotes because they are already added in my fixes)
Thank you!! Yes, I have read but forgot to unplug the USB key before applying fix #2.. Now I re-apply patch #2 from Catalina and retry to patch both installations from Usb installer Utliities
@jackluke to clone BigSur working installations, instead of the still limited Carbon Copy Cloner 5.20, I would like to try Windows 10's imageUSB (a forensic tool that works fine to clone 1.1 WIN2USB installation with 2 partitions bootable on Mac on a MD5 image) to have a simple restore of final BigSur. In your opinion, before wasting time, could it work in alternative to the dangerous dd command?
Currently cloning BigSur is troubled mainly due to its sealed snapshot booting and UUID Preboot, also when cloning keeping the same Preboot UUID I guess is not advisable, so I'd use clean install where apple installer assigns a new Preboot UUID and Migration Assistant (that should detect the Data Volume even if the BigSur is unbootable), you're right dd would work but it's dangerous, @jowaju on other threads used Clonezilla and I guess could work on BigSur too.