macOS 11 Big Sur on Unsupported Macs Thread

[jackluke]

One more time you did it, thank you Jackluke.
Your Penryn command did the trick and i was able to complete the installation.

Didn't need to use the reducetransparency fix.
Not working yet : Wireless, sound, the imac 21,5" is reported as 30,5" Monitor in system informations, and transparency.

Thank you for your support!

If you can use "sudo mount -uw /" from BigSur terminal then you can easily fix those kext, otherwise you should use the method of making a new snapshot, about my prelinkedkernel fix at least ethernet should work, instead for your Wifi issue I guess your iMac has an Atheros Wifi card, while I only included Broadcom Wifi cards kext.

Since you have an ATI non-metal GPU could you make this other test, because I am not sure if the "light mode" fix is related to a video framebuffer loaded or simply apple fixed it with BigSur beta 3: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28706998

 

[TimothyR734]

Hi to all,

After more or less successfully installed Beta 1 with your help, I tried to install Beta 3 using the same approach, Install from catalina, etc.. The problem that i'm facing now is that i complete fase 2(29 minutes that last almost 60m), and after the next reboot the installation continuous to reboot at the fase (i'm guessing) the graphics change mode to present the chosse language screen or close to that and never passes that stage. I tried another installation and after fase 2, press the option button, but i only have a disk named "Efi boot" choose that and the installation reboots the same way above.

I already tried to patch the installation from catalina with the peryn_patch.command but no go.

My system is Imac 10,1 Late 2009, C2D, 12 Gb RAM, ATI Radeon 4670 256Mb.

Any thoughts are welcome.
Thanks.

When you have installed Big Sur that is normal to see EFI boot that is what I saw so I clicked on it and Big Sur runs fine

 

[TimothyR734]

Would a Late 2008 MacBook work as an "install to this machine" / upgrade from Catalina using this method? These machines are very similar in specifications.

NO you need to make a patched Big Sur usb installer

 

[ykokosh]

macOS Big Sur Patcher Is No Longer Available

parrotgeek.com

does it works for beta 3?

 

[joevt]

Big Sur kext question:
I installed Lilu and WhateverGreen just by using kmutil load -p ~/Downloads/____.kext (sip is disabled) and then enabling them both in the Security preferences panel (not currently using OpenCore or Clover kext injection).

How do I uninstall a kext that I installed that way? I installed the release version of Whatevergreen but I want to replace that with the debug version. Do I have to boot into Recovery and use kmutil trigger-panic-medic?

 

[TimothyR734]

does it works for beta 3?

Yes follow the instructions on parrot geek's site then after run this script in the terminal then reboot into your Big Sir usb installer open the terminal type in csrutil status if it says enabled csrutil disable reboot back into you Big Sur usb installer then open the terminal again type in nvram boot-args="-no_compat_check" close the terminal then install Big Sur Beta

 

[PBiscaia]

If you can use "sudo mount -uw /" from BigSur terminal then you can easily fix those kext, otherwise you should use the method of making a new snapshot, about my prelinkedkernel fix at least ethernet should work, instead for your Wifi issue I guess your iMac has an Atheros Wifi card, while I only included Broadcom Wifi cards kext.

Since you have an ATI non-metal GPU could you make this other test, because I am not sure if the "light mode" fix is related to a video framebuffer loaded or simply apple fixed it with BigSur beta 3: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28706998

JackLuke,
The terminal command fix for "light mode" worked. All icons show now, before they didn't show but clicking in the toolbar didn't logout as used to do in beta 1. Regarding the sudo mount it failed with 66 permission denied.
And yes the wifi card is the original Atheros. I don't know exactly how to do a snapshot, probably using kext from catalina.

Thanks,

 

[thielsa]

I have included the full instructions on how I updated from Beta 2 to Beta 3 the other day in case it is helpful for anyone with a MacPro 5.1. Here is what I did:

* Make sure you have a recent TimeMachine backup on a separate drive. This is key to avoid having to set everything up again from scratch.
* Download the full installer for Beta 3. I found a link earlier in this thread.
* I formatted a USB Stick as an APFS bootable disk using Disk Utility.
* I followed the instructions 4-10 on https://parrotgeek.com/bigsur/
* I shutdown the MacPro.... I put in my original graphics card.
* I restarted the MacPro holding the option key to get to a boot select.
* I booted from the USB.
* I erased and formatted as APFS the drive I wanted to install Big Sur onto.
* I started the Big Sur install.
* On my MacPro there were 2-3 restarts where a cancel sign appeared. When this happened I powered down the computer and restarted.
* Eventually you will get to the Big Sur setup. I shutdown the MacPro and installed my normal graphics card.
* When you go through setup select restore from a TimeMachine backup. It gave me back everything exactly as it was in Beta 2.

Hope this helps. I am not running anything other than the installed iOS (no OpenCore). The performance in Geekbench is better than what I was able to achieve in Catalina.

 

[Barry K. Nathan]

When I have parrot geek's method I always get you need internet access, If I uses yours I get dll.domain error's so I create my patcher using the parrotgeek's method then run your micro patcher and install Big Sur no error's at all been doing this since beta 2 but the only time I have issues is if I need to reinstall it will say error preparing for installation

That is really strange. (With my patcher, make sure you always do step 6 before step 7, and make sure not to reboot between steps 6 and 7. If you boot from a USB stick that has my patch, then try to do step 7 without doing step 6 first, that could cause the kinds of errors you're having. I can't think of anything else... By the way, earlier versions of my patcher would display a misleading message after step 6 that could make it sound like a reboot was necessary before step 7, but I fixed that in v0.0.11.)

 

[jackluke]

JackLuke,
The terminal command fix for "light mode" worked. All icons show now, before they didn't show but clicking in the toolbar didn't logout as used to do in beta 1. Regarding the sudo mount it failed with 66 permission denied.
And yes the wifi card is the original Atheros. I don't know exactly how to do a snapshot, probably using kext from catalina.

Thanks,

You need kext from "Catalina" (but they are from HighSierra and Mojave), the snapshot method I wrote as also others a little guide from BigSur normal booting: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28657337

I guess to make that snapshot method work is sufficient csrutil disable .

 

[jackluke]

Big Sur kext question:
I installed Lilu and WhateverGreen just by using kmutil load -p ~/Downloads/____.kext (sip is disabled) and then enabling them both in the Security preferences panel (not currently using OpenCore or Clover kext injection).

How do I uninstall a kext that I installed that way? I installed the release version of Whatevergreen but I want to replace that with the debug version. Do I have to boot into Recovery and use kmutil trigger-panic-medic?

If you have a sealed system with snapshot booting to uninstall those kext I guess you should remove this file, but I am not really sure:
/Volumes/BigSur Data Volume/Library/KernelCollections/AuxiliaryKernelExtensions.kc

 

[joevt]

If you have a sealed system with snapshot booting to uninstall those kext I guess you should remove this file, but I am not really sure:
/Volumes/BigSur Data Volume/Library/KernelCollections/AuxiliaryKernelExtensions.kc

kmutil load -p works if I change the version of the kexts each time (still need to authorize in preferences pane and restart though). It's inconvenient. There should be a better way.

 

[GermanyUSER02]

Thanks GDMSR for answaring ;-)

That:

there's no guarantee of a patcher... but here's hoping

is exaktly what i mean.

We have OLD Computers, that was our own Problem (... we have wait to long to change to a newer one because "its still working"...).

And Apple has (from Time to Time) no other choice as let some Models down (especaly if INTEL gives no longer Securitypatches for the CPU´s).

Thats why i said its makes me a little angry that people came here to force a result for there old Computer (there is not a right to) ... I will be thankfull -if- the Community here find a way ... but if not .. so be it (than have i to change every my Computers at once -or from Time to Time-

But, its still time ... - to hope for a miracle )

Again, a big THANKS for all of you that make us these Miracles since a longe time

 

[Alex-Microsmeta]

@jackluke Hi dear, actually I have sounds (in & out) but using USB webcam mic and Bluetooth speakers. How to fix in BS Beta 3 AppleHDA.kext on Core 2 Duo Penryn Macmini 4.1 to have also internal sounds enabled? I fear to retry ~Snapshot method that has crashed BS Beta 2 (very probably due to my mistake)
[automerge]1595758906[/automerge]
How can I easily rename with a Terminal script on Catalina the original Apple boot pickups (not openCoreLoader3b) labels and add 512x512 pixels logos (Eg: "Windows 10" instead of "EFI boot" avoiding the risk of breaking original EFI APFS startup menu? Thank you!

 

[jackluke]

@jackluke Hi dear, actually I have sound (in & out) but using USB webcam mic and Bluetooth speakers. How to fix in BS Beta 3 AppleHDA.kext on Core 2 Duo Penryn Macmini 4.1 to have also internal sounds enabled? I fear to retry ~Snapshot method that has crashed BS Beta 2 (very probably due to my mistake)
[automerge]1595758906[/automerge]
How can I easily rename with a Terminal script on Catalina the original Apple boot pickups (not openCoreLoader3b) labels and add 512x512 pixels logos (Eg: "Windows 10" instead of "EFI boot" avoiding the risk of breaking original EFI APFS startup menu? Thank you!

To rename the "EFI Boot" I made earlier a simple app: EFI.Boot.renamer.app.zip

for fixing AppleHDA with prelinkedkernel you need to use this method: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28657337

 

[hvds]

When you have installed Big Sur that is normal to see EFI boot that is what I saw so I clicked on it and Big Sur runs fine

You mean, in the opt/alt boot selector? That I also have since installing beta3, for my BS SSD on USB. In OpenCore it is labelled Preboot. On the desktop the volume is labelled correctly.

 

[jackluke]

You mean, in the opt/alt boot selector? That I also have since installing beta3, for my BS SSD on USB. In OpenCore it is labeled Preboot. On the desktop the volume is labeled correctly.

I have an explanation for this, non-APFS (or APFS patched) or legacy USB Mac can't rename the "EFI Boot" labels for apple startup manager (it's a firmware limitation), while current opencore version can only detect the BigSur Preboot volume.

To try renaming the BigSur Preboot for opencore, open a BigSur normal booting terminal:

sudo bless --folder /System/Volumes/Preboot/*/System/Library/CoreServices --label "BigSur"

 

[David dongfox]

I did a full update to from Beta 2 to Beta 3 using the Parrotgeek instructions on my MacPro 5.1 . Used my timemachime backup to restore. Worked really well.

me too, everything work only wifi. in my mac mini late 2012.

 

[Alex-Microsmeta]

To rename the "EFI Boot" I made earlier a simple app: EFI.Boot.renamer.app.zip

for fixing AppleHDA with prelinkedkernel you need to use this method: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28657337

Tried with WinToUSB WINTOUSB partitions of Windows 10 USB 64 GB Pendrive from Catalina (Apple label EFI Boot), but it give me an error:

 

[jackluke]

Tried with WinToUSB WINTOUSB partitions of Windows 10 USB 64 GB Pendrive from Catalina (Apple label EFI Boot), but it give me an error:

Try to select the "Windows_FAT_32" as EFI Boot to rename .

 

[hvds]

I have an explanation for this, non-APFS (or APFS patched) or legacy USB Mac can't rename the "EFI Boot" labels for apple startup manager (it's a firmware limitation), while current opencore version can only detect the BigSur Preboot volume.

To try renaming the BigSur Preboot for opencore, open a BigSur normal booting terminal:

sudo bless --folder /System/Volumes/Preboot/*/System/Library/CoreServices --label "BigSur"

Thanks - it is BigSur now in apple boot selector.

 

[PBiscaia]

You need kext from "Catalina" (but they are from HighSierra and Mojave), the snapshot method I wrote as also others a little guide from BigSur normal booting: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28657337

I guess to make that snapshot method work is sufficient csrutil disable .

Hi Jackluke,

I tried to make the snapshot using the instructions provided, every commands worked without any errors, but now can't boot from bigSur the slashed circle immediately appears. Even in recovery mode I can't put SIP disable it's in "unknown" state.

Any clues?

Thanks.

 

[jackluke]

Hi Jackluke,

I tried to make the snapshot using the instructions provided, every commands worked without any errors, but now can't boot from bigSur the slashed circle immediately appears. Even in recovery mode I can't put SIP disable it's in "unknown" state.

Any clues?

Thanks.

Try reapplying from Catalina: BigSur Penryn beta3 prelinkedkernel fix.command.zip

If still don't work from a macOS Recovery open terminal and type: nvram boot-args="-no_compat_check"

otherwise use this: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28675922

or for non-APFS firmware snapshot booting try this from Catalina (or Mojave): BigSur snapshot fix.command.zip

 

[Barry K. Nathan]

Bonjour,

I'm sorry if it has already been said, but it gets lost quickly, to my great surprise since beta 3 my ethernet card is no longer recognized.

Have a nice day.

This is also happening on my MacBookPro8,1. I don't think it's a general "Ethernet no longer works in beta 3" problem, because nvenet still works on my MacBook6,1 in beta 3.

I'll look into this and see if I can find a fix or workaround.

 

[civotit]

I just made another installation of BigSur beta 3 on external drive, and as some already mentioned this "weird method" to allow "sudo mount -uw /", I confirm it worked, but the main condition is don't lose sight of "macOS Installer" progress install bar (on some disks can take more than 29 minutes up to one hour):

The BigSur installer has 3 main stages:

stage 1 : the BigSur logo enough quick loading bar "3 minutes remaining"
stage 2 : the apple logo that is the slow loading bar "29 minutes remaining"
stage 3 : the apple logo that is system sealing and snapshot booting

the gimmick is to skip the stage 3 , to do that you need to wait for the "29 minutes remaining" part, then after the auto reboot quickly hold alt-option key and don't select "macOS Installer" but select instead the "BigSur Data" , this should boot directly to desktop from where you can use "sudo mount -uw /" .

If after reboot you were distracted and stage 3 begins, you can force a power-off there, then power-on holding alt-option key and select "BigSur Data".

Since the "macOS Installer" is still in nvram, to avoid that after any reboot it could attempt to seal system (and snapshot booting of it), you have to select from System Preferences Startup Disk any other disk, so that "macOS Installer" is removed from list (maybe also a PRAM reset should work).

I tried this approach on a Late 2012 Mac Mini but pressing Alt/Option during the boot chime (after the second stage), there was no "Big Sur - Data" to select, only "mac OS Installer." Ended up with a sealed volume. On Beta 3, my install try showed "14 minutes remaining" on the initial stage.