macOS 11 Big Sur on Unsupported Macs Thread

[kraca]

I hope somebody comes up with one patch that will let my end 2012 iMac update to Big Sur. I'm not that into terminal

Just wait for dosdude and his expert friends to bring the magic

 

[quaccOS]

"root-dmg" is only used for ramdisk not for Preboot, so edit your 4 (that is the one used from APFS BigSur Preboot) as this:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Kernel Cache</key>
    <string>boot\System\Library\KernelCollections\BootKernelExtensions.kc</string>
    <key>Kernel Flags</key>
    <string>-no_compat_check amfi_get_out_of_my_way=1</string>
</dict>
</plist>

and it should boot to the loginUI, if still can't boot, otherwise you might try to edit this other way:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Kernel Cache</key>
    <string>System\Library\PrelinkedKernels\prelinkedkernel</string>
    <key>Kernel Flags</key>
    <string>-no_compat_check amfi_get_out_of_my_way=1</string>
</dict>
</plist>

I reached the Welcome (Choose Language) screen again this time, but it crashed after 10 seconds while changing language.

I edited /Volumes/Preboot/UUID-BigSurData/Library/SystemConfiguration/com.apple.Boot.plist and
/Volumes/Preboot/UUID-BigSurData/Library/Preferences/SystemConfiguration/com.apple.Boot.plist to match below.
I added the plist to /Volumes/Preboot/UUID-BigSurData/System/Library/CoreServices/ as it wasn't there.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Kernel Cache</key>
    <string>boot\System\Library\KernelCollections\BootKernelExtensions.kc</string>
    <key>Kernel Flags</key>
    <string>-no_compat_check amfi_get_out_of_my_way=1</string>
</dict>
</plist>

Removing boot\ caused it to crash before the Welcome screen, so I kept it.


For Big Sur USB /Volumes/USBInstallerBigSur/Library/Preferences/SystemConfiguration/com.apple.Boot.plist, it had to be this to boot:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Kernel Flags</key>
    <string>root-dmg=file:///BaseSystem/BaseSystem.dmg -no_compat_check cs_enforcement_disable=1 cs_debug=1 amfi_allow_any_signature=1 amfi_get_out_of_my_way=1</string>
</dict>
</plist>

Big Sur USB Recovery Terminal also said SIP & Authenticated Root were both enabled. I tried csrutil disable & csrutil authenticated-root disable but it would still be enabled after reboot.

If it can boot to the Welcome screen, but then crash…there must be something that is causing kernel panic, or is disrupting the startup process. I can't figure it out. If anyone is on MacBook Pro 7,1, let me know.

 

[rezzo]

Great work guys!

 

[jackluke]

I reached the Welcome (Choose Language) screen again this time, but it crashed after 10 seconds while changing language.

Then I guess it's the telemetry.plugin still copied or re-used from some "BigSur snapshot booting", for another test try this other method:
https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28611501

using usbopencoreloader contains telemetrap.kext that prevents telemetry.plugin from kernel loading, but you have to edit the BigSur Preboot com.apple.Boot.plist

changing this <string>boot\System\Library\KernelCollections\BootKernelExtensions.kc</string>

to this <string>System\Library\PrelinkedKernels\prelinkedkernel</string>

that string change is required otherwise usbopencore can't use the telemetrap.kext to block dinamically the telemetry plugin.

 

[FlorisVN]

I hope somebody comes up with one patch that will let my end 2012 iMac update to Big Sur. I'm not that into terminal

Just be patient..
We are still at beta 1 not even a gm is out.

 

[jhumroo]

So I installed Big Sur on my Mac Mini Late 2012 early this morning. I went about it differently. I first made a Time Machine backup of my Catalina install, then I reinstalled Catalina so I could start from scratch. Instead of installing Big Sur on it's own partition, I installed it as an Update to Catalina. I used the Hax.dylib file and some other stuff to make it boot. As of right now, Big Sur boots every time I restart my Mac. I then followed that guide on Medium to get my wifi working, and now everything just works just as good as Catalina did. I even have all my clock settings. Then I just opened up Time Machine and put all my programs back on my Mac.

Edit: I know this is working better than the last time I installed Big Sur(separate partition) because once I installed Homebrew it doesn't take forever to install stuff with it and I'm not getting any build errors.
View attachment 927948

I have the same machine and config. When you reinstalled Catalina, did you basically wipe-out your HD, install Catalina, and then update to Big Sur? Thanks

 

[quaccOS]

And now through my method to use the prelinkedkernel (instead of BootKernelExtensions) , using my opencore customized setup for non-APFS (or APFS rom patched) "Unsupported HighSierra Mac" or "El Capitan Supported Mac" is possible to use the @parrotgeek1 USBLegacyInjector.kext and @Syncretic telemetrap.kext (they are already included in my opencore setup), just make an external USB opencore bootloader with this:

USBOpenCoreAPFSloader3.app.zip

For "Unsupported HighSierra Mac" with working "Legacy IOUSB" you can boot (and use) a BigSur installation (while the USB BigSur installer still has unresponsive usb input output devices), to install BigSur on "Unsupported HighSierra Mac" just use the @ASentientBot method:
https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28589245

if you have a non-APFS machine you should pick from opencore the "macOS Installer" (or "macOS Install Data") to continue the BigSur installation, after is completed to use prelinkedkernel you should replace the file attached in the path as explained here: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28610988

Then power on holding alt-option key and select the usbopencore to load its simple text menu, easily to identify any bootable volumes, it's totally harmless and safe for any mac.

changing this <string>boot\System\Library\KernelCollections\BootKernelExtensions.kc</string>

to this <string>System\Library\PrelinkedKernels\prelinkedkernel</string>

I changed that string in all three com.boot.Apple.plist files in the Preboot volume that Big Sur uses.

I opened USBOpenCoreAPFSloader3, and I chose a 4 GB partition I made on my external HDD. It erased the entire drive. I didn't have anything important on it – only Cat & BS recoveries but that was disappointing.
I inserted a real 4 GB USB stick, and now I'm getting strange errors.

I checked UserEventPlugins a few times in BS Recovery before, and Telemetry plugin was removed. Understanding Big Sur's APFS system is very difficult…

 

[brandonsierra]

Its getting late for me. Its 10:26pm GMT or 11:26pm BST in the UK

 

[jackluke]

I changed that string in all three com.boot.Apple.plist files in the Preboot volume that Big Sur uses.

View attachment 928170 I opened USBOpenCoreAPFSloader3, and I chose a 4 GB partition I made on my external HDD. It erased the entire drive. I didn't have anything important on it – only Cat & BS recoveries but that was disappointing.
I inserted a real 4 GB USB stick, and now I'm getting strange errors.

I checked UserEventPlugins a few times in BS Recovery before, and Telemetry plugin was removed. Understanding Big Sur's APFS system is very difficult…

When you select a partition on an external HDD you should select to install opencore "Near an USB device without erasing" , while instead "On an empty USB device" (as usb drive not partition) means that the whole drive is used (there also some warnings before using the second option).

To fix the "mkdir" error, open /private/tmp/ and delete the "USBOpenCoreAPFSloader3" temporary folder, then retry to remake an usb opencore bootloader, after you made, reboot holding alt-option key and select it from apple startup manager.

This method is useful because makes an external USB EFI volume, without interfering with internal EFI or internal disks.

 

[jhowarth]

And now through my method to use the prelinkedkernel (instead of BootKernelExtensions) , using my opencore customized setup for non-APFS (or APFS rom patched) "Unsupported HighSierra Mac" or "El Capitan Supported Mac" is possible to use the @parrotgeek1 USBLegacyInjector.kext and @Syncretic telemetrap.kext (they are already included in my opencore setup), just make an external USB opencore bootloader with this:

USBOpenCoreAPFSloader3.app.zip

For "Unsupported HighSierra Mac" with working "Legacy IOUSB" you can boot (and use) a BigSur installation (while the USB BigSur installer still has unresponsive usb input output devices), to install BigSur on "Unsupported HighSierra Mac" just use the @ASentientBot method:
https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28589245

if you have a non-APFS machine you should pick from opencore the "macOS Installer" (or "macOS Install Data") to continue the BigSur installation, after is completed to use prelinkedkernel you should replace the file attached in the path as explained here: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28610988

Then power on holding alt-option key and select the usbopencore to load its simple text menu, easily to identify any bootable volumes, it's totally harmless and safe for any mac.

edit:
The Arrandale cpu mac still can't boot BigSur even using the prelinkedkernel.

I tested and it worked for "Unsupported HighSierra Mac" (non-APFS firmware Penryn Core2Duo, MacPro3,1 included), but easiest way is if you use an external USB BigSur installation, or clone a BigSur installation, but even with installation from Catalina (using ASentientBot Hax.dylib method) following the previous steps you will have a working IOUSB legacy BigSur .

For "Unsupported HighSierra Mac", currently no wifi, but you could use ethernet or an USB wifi dongle with this driver:
https://github.com/chris1111/Wireless-USB-Big-Sur-Adapter

On my MacPro 3,1 with GTX680, BCM94360CD and APFS ROM patch, I tried the steps of...

cd ~/"really simple installer hack"
launchctl setenv DYLD_INSERT_LIBRARIES $PWD/Hax.dylib

however when I launch the 'Install macOS Beta' and select an external USB hard drive, freshly erased as an empty APFS volume, I get an error that 'Your Mac needs a firmware update in order to install on this volume. Please select a Mac OS Extended (Journaled) volume instead'.

 

[jackluke]

On my MacPro 3,1 with GTX680, BCM94360CD and APFS ROM patch, I tried the steps of...

cd ~/"really simple installer hack"
launchctl setenv DYLD_INSERT_LIBRARIES $PWD/Hax.dylib

however when I launch the 'Install macOS Beta' and select an external USB hard drive, freshly erased as an empty APFS volume, I get an error that 'Your Mac needs a firmware update in order to install on this volume. Please select a Mac OS Extended (Journaled) volume instead'.

To insert properly the Hax.dylib you should copy it to the ~/ (home folder root as ~/Hax.dylib) and then run from terminal: launchctl setenv DYLD_INSERT_LIBRARIES $PWD/Hax.dylib

but first you should set in nvram boot-args="-no_compat_check amfi_get_out_of_my_way=1" from a recovery environment or USB Catalina patcher and "csrutil disable".

 

[jhowarth]

To insert properly the Hax.dylib you should copy it to the ~/ (home folder root as ~/Hax.dylib) and then run from terminal: launchctl setenv DYLD_INSERT_LIBRARIES $PWD/Hax.dylib

but first you should set in nvram boot-args="-no_compat_check amfi_get_out_of_my_way=1" from a recovery environment or USB Catalina patcher and "csrutil disable".

Is the 'amfi_get_out_of_my_way=1' critical to getting the disk to select? I am launching the installer under patched Catalina which has the plist hack to disable amfi. I haven't seen anyone actually report an installation on a APFS ROM patched machine as opposed to one that has official Apple APFS rom support.

 

[theANY]

Just fyi: I have got the absolutely same prob with a Mid 2009 MBP, with a patched ROM so it does boot Catalina from APFS natively. Hope somebody can figure out how to patch that.

 

[quaccOS]

When you select a partition on an external HDD you should select to install opencore "Near an USB device without erasing" , while instead "On an empty USB device" (as usb drive not partition) means that the whole drive is used (there also some warnings before using the second option).

To fix the "mkdir" error, open /private/tmp/ and delete the "USBOpenCoreAPFSloader3" temporary folder, then retry to remake an usb opencore bootloader, after you made, reboot holding alt-option key and select it from apple startup manager.

This method is useful because makes an external USB EFI volume, without interfering with internal EFI or internal disks.

@jackluke This is a beautiful moment. You must witness it. Behold…the Big Sur!
This is insane — to have macOS 11 running on a 10 year old machine.
No graphics acceleration, WiFi, speakers & microphone…but it booted!

 

[rjohnstone]

Late 2013 21" iMac.
Everything works... WiFi, my third party SSD (Samsung Evo 860) and no issues with HW acceleration for the graphics.

 

[Lars B.]

@jackluke This is a beautiful moment. You must witness it. Behold…the Big Sur!
This is insane — to have macOS 11 running on a 10 year old machine.
No graphics acceleration, WiFi, speakers & microphone…but it booted!

I don't want to ruin your joy, but to be honest, it's not really that impressive. The most recent version of Windows 10 runs great on that machine, including full graphics acceleration, WiFi, speakers & microphone.

 

[quaccOS]

I don't want to ruin your joy, but to be honest, it's not really that impressive. The most recent version of Windows 10 runs great on that machine, including full graphics acceleration, WiFi, speakers & microphone.

Windows 10 is only good for playing GTA on a Mac. After that, it's toilet paper. It's not made by people who care about the end-user. It's a terrible experience to use Windows as a primary OS.

Emphasis on experience, because that's what has made macOS the best desktop OS in the world. Windows fails to be an OS that is easy to use & control. Their one-size-fits-all approach to having to develop Windows for endless amounts of different hardware probably hampers Microsoft's ability to make it nicer. Same with Android…

The power in Apple's OS is you can give it to a child…and they'll figure it out in seconds. I could elaborate on that all day.

 

[timidpimpin]

I hope somebody comes up with one patch that will let my end 2012 iMac update to Big Sur. I'm not that into terminal

Let me see if I understand... you want someone to make a patcher specifically for you?

Here's a thought... maybe try to advance your computing ability a little, and stop expecting to be spoon-fed things. Your lack of ability, and clear desire to not evolve, are your problem.

 

[antony34]

@jackluke This is a beautiful moment. You must witness it. Behold…the Big Sur!
This is insane — to have macOS 11 running on a 10 year old machine.
No graphics acceleration, WiFi, speakers & microphone…but it booted!

View attachment 928182
View attachment 928183

Oh....seems iMac 2009 still can install Big Sur.....(still long road we needed to test)
Maybe we can save some money to wait ARM iMac out?

 

[quaccOS]

Let me see if I understand... you want someone to make a patcher specifically for you?

Here's a thought... maybe try to advance your computing ability a little, and stop expecting to be spoon-fed things. Your lack of ability, and clear desire to not evolve, are your problem.

Programming isn't for everyone, but besides that – people evolve to take-on different priorities, and those priorities aren't always concerned with the advancement of the human race. Most will take the path of least resistance to adapt to the environment, hopefully achieving the comfort of emotion. Many are hit with numbness, and no desire to advance. There is in fact nothing to advance to except the next feeling. The tangible structures we build along the way can distract us from that until we pass…

TLDR: Lol. Philosophy. sudo sleep -t 480 *swish*

 

[timidpimpin]

Programming isn't for everyone, but besides that – people evolve to take-on different priorities, and those priorities aren't always concerned with the advancement of the human race. Most will take the path of least resistance to adapt to the environment, hopefully achieving the comfort of emotion. Many are hit with numbness, and no desire to advance. There is in fact nothing to advance to except the next feeling. The tangible structures we build along the way can distract us from that until we pass…

TLDR: Lol. Philosophy. sudo sleep -t 480 *swish*

The point is that they desire something, but are not willing to contribute anything, even to the point of copy/pasting terminal commands. This type of thinking lacks humanity.

 

[quaccOS]

The point is that they desire something, but are not willing to contribute anything, even to the point of copy/pasting terminal commands. This type of thinking lacks humanity.

Yeah…I don’t disagree with you. I just think it’s not worth ‘fixing‘ people. I always got frustrated with people, especially those with potential who chose to waste it. But that person’s attitude also reflects a lot of people - how are you going to change so many people’s perspective? It’s a lot of effort for no reward, so I tend to just ignore it…

That being said, maybe you can change people. But I feel hardwired to “ignore”. Unlike every other problem, ‘underthinking’ people turns out to be much more rewarding.

 

[aussieacorn]

I hope somebody comes up with one patch that will let my end 2012 iMac update to Big Sur. I'm not that into terminal

Just so you know, the last part of your comment ("I'm not that into terminal") can't be gone lazier than anything.

 

[Jose C. Salazar]

The point is that they desire something, but are not willing to contribute anything, even to the point of copy/pasting terminal commands. This type of thinking lacks humanity.

Sorry the spam but... if you desire a Ferrari.... you should learn about car construction and contribute to the car building industry? he is not saying he want a patch only for his machine, he is waiting for a massive public release...

 

[timidpimpin]

Sorry the spam but... if you desire a Ferrari.... you should learn about car construction and contribute to the car building industry?

What a ridiculous argument. If you like Ferarri's, and can afford one, then you're contributing your money to the Ferrari market. The person in question isn't even willing to use spoon-fed instructions.