macOS 11 Big Sur on Unsupported Macs Thread

[justperry]

Somewhat related to this topic, the below screenshots confuses me, I unlock the preferencePane, there's a button called allow, so I suppose that's what it does but then have to tick or untick a box to allow the extensions.
Should I tick the box to allow or untick. /confused

*They were ticked, but the text above says they were blocked from loading.

 

[Larsvonhier]

Strange but may be promising - which express card do you use?

This one, will have to check the chipset used (I think it was NEC but I have to look it up tomorrow).

edit:
See vendor/product ID screenshot. It is supported out of the box, no further kexts or plist mods required.

 

[Allan Fox]

Also how is the bootable usb method supposed to work I’m currently trying that and it instantly boots into the big sur recovery but cannot install Big Sur in any drive
[automerge]1593456499[/automerge]

 

[hvds]

Now that you have "my BigSur prelinkedkernel fix", you can also swap this disk and boot from external USB Big Sur installation, currently (skip a normal booting or CMD+V) use from opencore CMD+S , select BigSur Volume (in your case Samsung840 - Data Label) and then type "exit" this will boot BigSur with IOUSB legacy and telemetry fixed all the times.

Instead if you don't use single user mode (for non-APFS BigSur install), randomly you might get unresponsive IOUSB legacy as for 10.16 Recovery (dmg) , that's because @parrotgeek1 should update the LegacyUSBInjector.kext to align with the BigSur IOUSBHostFamily.kext/Plugins/AppleUSBHostMergeProperties.kext

Meanwhile I asked to @Syncretic (because his AAAMouSSE and telemetrap have correctly assigned a kernel cache ID on BigSur and both work with kextstat) to upgrade that "USB Legacy injector" to allow it to prelink to BigSur (SDK and IOKit), but it's not easy to make it work with BootKernelExtensions.kc .

Also to show to others that you succeeded to boot BigSur from a non-APFS mac use these commands from a BigSur terminal:

system_profiler SPHardwareDataType | grep "Model Identifier"

ioreg -l | grep -i board-id

sysctl machdep.cpu.brand_string

sysctl machdep.cpu.features

system_profiler SPUSBDataType | grep Host

Sorry for replying late - the hardware info is in the attached screenshot.

Yes, I think the installed BS SSD would work on USB. For now I think I leave it as internal disk, to be able to repeat an installation.
Thank you for already contacting parrotgeek1 and Syncretic. In the longer BS run those upgrades/adaptations would be great.

I'll now work on the WIFI fix. Neither this nor Ethernet cable are working at the moment.

(MBP5,2 17" mid 2009, 2.8GHz Penryn T9600, Nvidia 9600M GT, 8GB, APFS ROM patch applied. APFS SSD Samsung 860 EVO for production / 840 for testing, with Catalina 10.15.5.02 / Big Sur 10.16.0 DB1, resp.)

 

[justperry]

Also how is the bootable usb method supposed to work I’m currently trying that and it instantly boots into the big sur recovery but cannot install Big Sur in any drive

View attachment 929128

Answers are there If you read one of the last few pages, just open a former page, Command-F (Search) for the error you have, you'll find it.

 

[Allan Fox]

I’ll try to make an external one first then if it works I’ll upgrade the internal HDD

 

[bontempi]

I've installed Big Sur fine on my macbook pro 2012 non retina... Now i'm trying to follow these instructions

macOS 11 Big Sur on Unsupported Macs Thread

For enabling Wifi 802.11n on any 2012 Mac or any other unsupported Big Sur but supported Catalina Mac (in few words those who use the AirPortBrcm4360 driver), this will work: https://forums.macrumors.com/threads/macos-11-big-sur-on-unsupported-macs-thread.2242172/post-28595200 To install it...

forums.macrumors.com

when i type the sudo mount -uw / killall thing, i get :
"mount_apfs volume could not be mounted : permission denied
mount failed with 66"

I can't copy the wifi kext file to my macbooks extension folder ...

any help ?

Still looking for help... thanks

 

[Allan Fox]

trying
[automerge]1593458100[/automerge]

Still looking for help... thanks

there is a link somewhere on the forum fixing your problem. I saw it an hour ago

 

[hvds]

Looks like you guys already got this sorted, but it was a simple fix for the "Hax.dylib" thing if anybody with a non-APFS Mac would like to test this. Please report your results if anyone uses it!

Thank you for the Hax3.app!

I tried it on my present setup (10.15.5.02 on USB, 10.16.0 DB1 internal on SATA (the Samsung840)). It seems the Big Sur disk isn't seen by the Installer after starting it via Hax3.

Maybe due to Catalina not recognising properly the Big Sur disk structure (white terminal window), which seems intact as BS is working, and from inside BS it looks fine (black one).

But that doesn't matter. I think I'll soon clone Catalina to the Samsung840, and repeat installation. Then the Installer will see it. But for now I'll continue playing with the existing BS installation...

 

[David403]

View attachment 929146
trying
[automerge]1593458100[/automerge]

there is a link somewhere on the forum fixing your problem. I saw it an hour ago

If you've read all the pages (yes I do mean all 47) - as you should have done!!! the question has been answered several times - Just wait! it can take a long, long time - well over an hour!

 

[Allan Fox]

If you've read all the pages (yes I do mean all 47) - as you should have done!!! the question has been answered several times - Just wait! it can take a long, long time - well over an hour!

Yeah mate currently waiting for the install to finish, it’s on an external drive so I don’t care that much now

 

[bontempi]

If you've read all the pages (yes I do mean all 47) - as you should have done!!! the question has been answered several times - Just wait! it can take a long, long time - well over an hour!

Is this page the only way to fix this error 66 ?

Making WiFi work on Big Sur unsupported Macs with “failed with 66” error

How to make wifi work on unsupported macs running Big Sur, if you have “failed with 66” error

medium.com

Can anyone confirm it actually worked for them ?
Or is it better to wait for a simpler fix ?

Another question : will the kext still work after every Big Sur upgrade ? Wouldn't it be better to upgrade the broadcom card instead ?

Thanks

 

[Allan Fox]

I think

 

[Alex-Microsmeta]

The ≈25.7 MB prelinkedkernel file exists in the ./UUID/System/Library/PrelinkedKernels directory of Big Sur's Preboot volume.
diskutil apfs list revealed that the UUID shown in /Volumes/Preboot/2B9C924F-9B05-4337-9383-0C2057994587 was in fact the UUID of the Big Sur - Data volume (disk1s2) — not the Preboot volume (disk1s1) as I would've expected.

Editing the default com.apple.Boot.plist files seem to be vital in making Big Sur boot up.
The other tasks in order were:
disabling SIP & Library Validation; injecting Hax.dylib; installing macOS Beta with app; adding the NVRAM boot args; making a bootable Big Sur installer; deleting/renaming Telemetry plugin — so the last task seems to be editing Boot plist files.

There seem to be 4 different Boot plists in question.
1st is in the Big Sur USB Installer, 2nd & 3rd in the two SystemConfig folders in Big Sur's Preboot volume, and the 4th is the one I copied to the CoreServices directory because a Boot plist did not exist there

1/Volumes/USBInstallerBigSur/Library/Preferences/SystemConfiguration/com.apple.Boot.plist
2/Volumes/Preboot/UUID-BigSurData/Library/SystemConfiguration/com.apple.Boot.plist
3/Volumes/Preboot/UUID-BigSurData/Library/Preferences/SystemConfiguration/com.apple.Boot.plist
4/Volumes/Preboot/UUID-BigSurData/System/Library/CoreServices/com.apple.Boot.plist

Hi @jackluke ! Thank you again. I have finally added on Big Sur Preboot volume: com.apple.Boot.plist in /CoreServices/ and /SystemConfiguration/ (there wasn't here) but my Macmini 2010 Core 2 Duo continues to crash after switching from black to white screen, never reaching Language Configuration.
I'll wait your plist injected in next Bug Sur patcher

 

[Allan Fox]

Progress though this is what happened the first time then prohibitory sign
[automerge]1593460735[/automerge]
When I tried the internal drive

 

[hvds]

Here is my question is it possible to install Big Sur to external SSD on iMac 9,1(an Unsupported Catalina installed)?

Cause I create a normal USB installer with createinstall method and try to boot with Opt key and I got Probihited Sign never reach the installer screen.

@jackluke I also tried with your USBOpenCoreAPFSloader to reach Big Sur installer screen but I always getting Probihited Sign.

I tried to start installer inside Catalina this time I got this machine not have APFS Fireware error try to HFS+ I tried HFS+ and this time got BIError Domain error 3.

So is it possible how?

Note: I don't want to make a boot in this machine I just want to install to the external drive and when I reach the language setup screen remove it.

I also made an USB installer with createinstall à la jackluke post #215.
It behaves the same as yours - prohibited sign in the end.

In my case I guess it has to do with USB access from within the installer (my machine is a mid 2009 MBP5,2). I'll try further.

ASentientBot has made a fix for using the BS installer from within Catalina (Hax3.app from his post #1091) which avoids the "firmware..." message. It provides an extry dylib to the installer. Works fine for me.

 

[Allan Fox]

Ok so now the external drive showed efi boot

 

[telepati]

I also made an USB installer with createinstall à la jackluke post #215.
It behaves the same as yours - prohibited sign in the end.

In my case I guess it has to do with USB access from within the installer (my machine is a mid 2009 MBP5,2). I'll try further.

ASentientBot has made a fix for using the BS installer from within Catalina (Hax3.app from his post #1091) which avoids the "firmware..." message. It provides an extry dylib to the installer. Works fine for me.

Do you mean If I install Hax3.app on Catalina, can I install BS beta to external drive by launching BS beta from Catalina?

 

[ASentientBot]

Thank you for the Hax3.app!

I tried it on my present setup (10.15.5.02 on USB, 10.16.0 DB1 internal on SATA (the Samsung840)). It seems the Big Sur disk isn't seen by the Installer after starting it via Hax3.

Maybe due to Catalina not recognising properly the Big Sur disk structure (white terminal window), which seems intact as BS is working, and from inside BS it looks fine (black one).

But that doesn't matter. I think I'll soon clone Catalina to the Samsung840, and repeat installation. Then the Installer will see it. But for now I'll continue playing with the existing BS installation...

That's weird... the inability to mount a BS disk on Cat comes from the volume sealing feature, which my installer hack is supposed to disable.

 

[quaccOS]

Hi @jackluke ! Thank you again. I have finally added on Big Sur Preboot volume: com.apple.Boot.plist in /CoreServices/ and /SystemConfiguration/ (there wasn't here) but my Macmini 2010 Core 2 Duo continues to crash after switching from black to white screen, never reaching Language Configuration.
I'll wait your plist injected in next Bug Sur patcher

You probably seen the correct plists, but check these against yours.

/Volumes/USBInstallerBigSur/Library/Preferences/SystemConfiguration/com.apple.Boot.plist ⬇︎

<?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>

/Volumes/Preboot/UUID-BigSurData/Library/SystemConfiguration/com.apple.Boot.plist /Volumes/Preboot/UUID-BigSurData/Library/Preferences/SystemConfiguration/com.apple.Boot.plist /Volumes/Preboot/UUID-BigSurData/System/Library/CoreServices/com.apple.Boot.plist ⬇︎

<?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>

Even if you delete the Telemetry plugin which is causes problems for Core 2 Duo CPUs, the plugin is still getting re-used or copied from some strange Big Sur snapshot booting…

You'll need to use the USB OpenCoreAPFSloader3 to. It will dynamically block the plugin by loading the telemetrap.kext — but you need this string in your plists <string>System\Library\PrelinkedKernels\prelinkedkernel</string>.
See more here:

https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28612815

You may have already seen this though.

 

[Bravo2zero]

I got it on my 2012 Mac mini now and works well once it’s in the OS environment.

Every start up of the machine gives not closed down properly pop up but this seems to be a BS issue.

You can’t no matter how you try clone your HDD once BS is installed. I have 2 SSD hyperX savage and hyper X s3 and I cloned 10.15 to the slower of the 2 ( S3 ) then did a system upgrade keeping Catalina on the faster drive.

Once satisfied all was good I wanted to clone BS over the Cat SSD and wipe the S3.

BS can’t be cloned with anything ! Carbon clone , disk utility, I even got a SSD external installed 10.15 on that used CCC & disk Utility and nothing worked. Just wouldn’t start just spat out file format errors so looks like I’m stuck on the slower disk till I do a full reinstall on to the savage drive.

 

[Allan Fox]

ok so something weird happened while booting of the hard disk it placed the apple logo and the loading bar then the new loading screen and it shut off any ideas why? My Mac as shown in previous posts is a mid 2012 MacBook Pro

 

[quaccOS]

Yes please, dear @ASentientBot could you show us the terminal script to remove telemetry from Big Sur volume, and from where? It seems to me to have correctly completed the installation and I have 2 volumes: "Big Sur - Dati" and "Update" but I cannot enter Big Sur recovery because It crashes after screen changing from black to white, while from Catalina Recovery I don''t find volume Big Sur's path /System/Library/UserEventPlugins/ to delete com.apple.telemetry.plugin. With It, macmini4,1 crashes before reaching first Language configuration.

Thank you! Alex

You can't delete Telemetry plugin from Catalina or earlier. You will need to make a Big Sur bootable installer with the createinstallmedia command, and use the recovery Terminal there. Earlier macOS versions don't understand Big Sur's system volume, so you have to be on some kind of Big Sur — recovery is the way.
sudo /Applications/Install\ macOS\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/MyVolume

In recovery Terminal:
mount -uw "/Volumes/Big Sur" cd /Volumes/Big\ Sur/System/Library/UserEventPlugins/; ls rm -r com.apple.telemetry.plugin

 

[Allan Fox]

Finally after making a separate partition and restoring the external hard disk to it I finally made it work

 

[MacHacJac]

I see a lot of different options for installing BS and can't decide what works, what's reliable, and what I would use. What would you suggest as a reliable method (preferably with a WiFi possibility) for a 2011 MBP?