macOS 11 Big Sur on Unsupported Macs Thread

[Fangio]

Updated from DP3 to DP4 on a 2012 15" MBP 9,1 using Barrys micropatcher v0.0.18. No issues, WiFi and AirDrop are fine.

I have just released v0.0.18 of my patcher. [...] The big change is that patch-kexts.sh no longer requires rebooting into the installer USB. Furthermore, if you run it under your macOS Big Sur installation instead of the installer USB, you do not need to specify the volume name on the command line -- it will automatically default to the volume that you booted from.

Can also confirm this, running /Volumes/Image\ Volume/patch-kexts.sh in a Big Sur terminal works very well. Thanks Barry.

 

[jackluke]

Could someone upload the /Applications/Safari.app from BigSur beta 4 (20A5343i) ?

The app is enough small zipped.

edit:
copied from beta4 BaseSystem.dmg (877 MB) the /macOS Base System/Applications/Safari.app
and now is working also on my beta4 installation , for some reason the app hasn't been updated and was still the version from beta3, probably because I skipped the stage3 installer .

I have also an explanation for this, apple core apps on a dual APFS macOS (Catalina and BigSur) are stored on this folder:

/APFS System Volume/System/Applications/

instead Safari.app is stored here:

/APFS Data Volume/Applications/

(or /System/Volumes/Data/Applications/ )

 

[alexanderguad]

Trying to create the install media

sudo /Applications/Install\ macOS\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/USB

And I just get Command not found in return. Not sure what I'm doing wrong?

EDIT: Got it working.

 

[shadowapple]

hello, any easy toturial to install big sur beta 4 and that if possible work the wifi?

Thanks.

 

[eikic1]

hello brother, i try to bigsurotafix but error, anyone know what this error?

 

[jackluke]

hello brother, i try to bigsurotafix but error, anyone know what this error?

Move the app on the desktop or downloads folder and open from there, anyway to fix software update "amfi disabled" is required because it's a dylib insert, but maybe use the direct link 12,3 gb to download, the app doesn't work properly yet .

 

[nandor690]

I have just released v0.0.18 of my patcher. Quoting from the release notes:


The big change is that patch-kexts.sh no longer requires rebooting into the installer USB. Furthermore, if you run it under your macOS Big Sur installation instead of the installer USB, you do not need to specify the volume name on the command line -- it will automatically default to the volume that you booted from.

@pfandung @guerrabadboy with this version of the patcher you should now be able to run /Volumes/Install\ macOS\ Big\ Sur\ Beta/patch-kexts.sh and you should get working WiFi, without having to boot from the patched installer USB. (@TimothyR734 in the near future, after you install beta 4 or the public beta, you might also want to give this a try and see if it sidesteps the problems you had in the past.)

Alongside the improved patch-kexts.sh, I had also wanted to release remount-sysvol.sh and rebuild-kc.sh, for mounting the underlying volume as read-write to a temporary mount point and for easily rebuilding the kernel/kext collections -- this would allow people to easily add/remove/replace kexts themselves. However, that has been taking longer than I expected and I didn't want to hold up the rest of this release, so it's postponed until the next release (probably later this week, but it could slip to next week).

GitHub - barrykn/big-sur-micropatcher: A primitive USB patcher for installing macOS Big Sur on unsupported Macs

A primitive USB patcher for installing macOS Big Sur on unsupported Macs - barrykn/big-sur-micropatcher

github.com

Here’s a dumb thing I did for you to laugh at. I was messing around and ran the set-vars.sh but directed it toward my ssd that has Big Sur on it. I think I lost it for good 😂. It obviously doesn’t boot from bi sur any more. If I try to use disk utility in recover mode or in Catalina it causes the system to crash. If I try to manually erase it from terminal it won’t allow me because of permissions. And I can’t change the permissions.
[automerge]1596646653[/automerge]

hello brother, i try to bigsurotafix but error, anyone know what this error?

I get the same thing.

 

[jackluke]

I get the same thing.

Use this: http://swcdn.apple.com/content/down...m7ounuabziajlktg8nhoptis/InstallAssistant.pkg

OTA updates still don't work on unsupported Mac, unless you spoof to supported BigSur Mac through opencore .

 

[eikic1]

Move the app on the desktop or downloads folder and open from there, anyway to fix software update "amfi disabled" is required because it's a dylib insert, but maybe use the direct link 12,3 gb to download, the app doesn't work properly yet .

already bro, but still error
[automerge]1596647073[/automerge]

Use this: http://swcdn.apple.com/content/down...m7ounuabziajlktg8nhoptis/InstallAssistant.pkg

OTA updates still don't work on unsupported Mac, unless you spoof to supported BigSur Mac through opencore .

from beta 1 i can ota download bro

 

[Barry K. Nathan]

Hi Barry. Sorry to bother you. When trying to create the USBboot in order to update to beta 4 from beta 3, creatmedia reports the following:

objc[1001]: Class IASNightInstallSupport is implemented in both /System/Library/PrivateFrameworks/IASUtilities.framework/Versions/A/IASUtilities (0x7fff8a37cd78) 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 (0x10c295ac0). One of the two will be used. Which one is undefined.
objc[1001]: Class IASSystemInformation is implemented in both /System/Library/PrivateFrameworks/IASUtilities.framework/Versions/A/IASUtilities (0x7fff8a37ceb8) 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 (0x10c295bd8). One of the two will be used. Which one is undefined.
Ready to start.

It is not the first time I am using createinstallmedia but it's the first time I see something like this. Any thoughts?

Thank you sir and sorry again...

For what it's worth, "Class X is implemented in both Y and Z. One of the two will be used. Which one is undefined." warnings have been triggered by the Big Sur installer since beta 1 (and I just verified that beta 4 is still doing it), but 99+% of the time they just get silently logged and you don't ever see it. createinstallmedia showing similar warnings is new in beta 4, but it doesn't seem to have any other effects, so I would just ignore it.

 

[webg3]

Could you attach these files:

/System/Library/CoreServices/SystemVersion.plist
/System/Library/CoreServices/SystemVersionCompact.plist
/Applications/Safari.app/Contents/Info.plist

(I don't know why post merging is not working)

 

[furdi]

For what it's worth, "Class X is implemented in both Y and Z. One of the two will be used. Which one is undefined." warnings have been triggered by the Big Sur installer since beta 1 (and I just verified that beta 4 is still doing it), but 99+% of the time they just get silently logged and you don't ever see it. createinstallmedia showing similar warnings is new in beta 4, but it doesn't seem to have any other effects, so I would just ignore it.

Thank you very much for your reply. Much appreciated. I have installed the beta 4 through the usb boot using your 0.0.19 patcher and at the end I just want to run the patch-hexts.sh and I want to make sure that I am doing it right:
after restart, I just run the terminal and just run the command, or I have to start the installer and from there I open the terminal? I have tried opening the terminal and it tells me that no such directory is found... Thank you!

Edit: So in regards to my experience with the upgrade from beta 3 to beta 4 this is how it went: used creatmedia for the USBboot and used the last patcher from @Barry K. Nathan (HUGE THANKS!). All perfect installed, but at the end no wifi... Tried running the patch-hexts.sh from terminal within Big Sur, no such directory... Rebooted from the USBboot, run terminal with the full sintax (including the target volume) and after rebbot to Big Sur and after 5 to 7 minutes of searching and searching, I got Wifi!!!
All good and working now!

 

[nandor690]

Anyone else having issues of handoff not working after a fresh install?

 

[Barry K. Nathan]

Here’s a dumb thing I did for you to laugh at. I was messing around and ran the set-vars.sh but directed it toward my ssd that has Big Sur on it. I think I lost it for good 😂. It obviously doesn’t boot from bi sur any more. If I try to use disk utility in recover mode or in Catalina it causes the system to crash. If I try to manually erase it from terminal it won’t allow me because of permissions. And I can’t change the permissions.

Wait, set-vars.sh or patch-kexts.sh? I'm not sure how set-vars.sh could destroy any data. patch-kexts.sh could, yes, and I'll see if I can improve that script's error checking to further reduce the chance of data loss (although I would expect it to destroy installer USBs and not full macOS installations).
...
You know what set-vars could (in some sense) destroy? The boot-args nvram variable. But running set-vars.sh again (properly) should fix that, or if things somehow got too messed up to do that, then doing a "PRAM reset" (nvram reset, really) should recover things to the point that set-vars.sh can run again.

 

[Barry K. Nathan]

Thank you very much for your reply. Much appreciated. I have installed the beta 4 through the usb boot using your 0.0.19 patcher and at the end I just want to run the patch-hexts.sh and I want to make sure that I am doing it right:
after restart, I just run the terminal and just run the command, or I have to start the installer and from there I open the terminal? I have tried opening the terminal and it tells me that no such directory is found... Thank you!

Edit: So in regards to my experience with the upgrade from beta 3 to beta 4 this is how it went: used creatmedia for the USBboot and used the last patcher from @Barry K. Nathan (HUGE THANKS!). All perfect installed, but at the end no wifi... Tried running the patch-hexts.sh from terminal within Big Sur, no such directory... Rebooted from the USBboot, run terminal with the full sintax (including the target volume) and after rebbot to Big Sur and after 5 to 7 minutes of searching and searching, I got Wifi!!!
All good and working now!

It's /Volumes/Image\ Volume/patch-kexts.sh if you're booting from the installer USB, /Volumes/Install\ macOS\ Big\ Sur\ Beta/patch-kexts.sh if you're just opening up Terminal and running it without rebooting from the installer USB first.

 

[nandor690]

Wait, set-vars.sh or patch-kexts.sh? I'm not sure how set-vars.sh could destroy any data. patch-kexts.sh could, yes, and I'll see if I can improve that script's error checking to further reduce the chance of data loss (although I would expect it to destroy installer USBs and not full macOS installations).
...
You know what set-vars could (in some sense) destroy? The boot-args nvram variable. But running set-vars.sh again (properly) should fix that, or if things somehow got too messed up to do that, then doing a "PRAM reset" (nvram reset, really) should recover things to the point that set-vars.sh can run again.

It was the set-vars.sh. All my other drives boot besides that one. And literally anything I try to do to that drive causes the computer to crash. It’s not that big of a deal tho. It’s an old ssd. But I’ll try the pram reset and running the command again.
The command I ran was
/Volumes/Image\ Volume/set-vars.sh /Volume/BS

I was just messing around to see what it would do lol

 

[nandor690]

And it also seems like Safari crashes a lot on macOS Big Sur beta 4

 

[nandor690]

Wait, set-vars.sh or patch-kexts.sh? I'm not sure how set-vars.sh could destroy any data. patch-kexts.sh could, yes, and I'll see if I can improve that script's error checking to further reduce the chance of data loss (although I would expect it to destroy installer USBs and not full macOS installations).
...
You know what set-vars could (in some sense) destroy? The boot-args nvram variable. But running set-vars.sh again (properly) should fix that, or if things somehow got too messed up to do that, then doing a "PRAM reset" (nvram reset, really) should recover things to the point that set-vars.sh can run again.

So it kind of worked itself out. After multiple reboots of trying to get other things working, the partitions on that other ssd that I screwed up just started disappearing on their own until only the container was left. At that point disk utility let me reformat it without crashing. Go figure lol. Thanks for the reply’s tho.

 

[Ronald Steven]

Installed BS4 in my MBP 13" mid 2012 whit @Barry K. Nathan patcher and all works, only a bug at the button to turn off/on any wifi network, not works, the wifi continues working, it has to disable from main wifi bottom directly to turn off/on. thanks for all people that make a great effort @Barry K. Nathan @jackluke @ASentientBot thanks guys! 👏

 

[nandor690]

Does anyone see what I'm doing wrong here. I ran set-vars.sh from recovery. I checked in terminal and csrutil authenticated-root status is disabled and csrutil is disabled. but I can't get this to work without getting failed because of read-only file system.
thanks for anyone that sees my mistake

 

[Barry K. Nathan]

Does anyone see what I'm doing wrong here. I ran set-vars.sh from recovery. I checked in terminal and csrutil authenticated-root status is disabled and csrutil is disabled. but I can't get this to work without getting failed because of read-only file system.
thanks for anyone that sees my mistake

diskutil mount probably mounted the filesystem at /Volumes/bs\ 1. Use ls -l /Volumes after diskutil mount to check for sure.

 

[nandor690]

diskutil mount probably mounted the filesystem at /Volumes/bs\ 1. Use ls -l /Volumes after diskutil mount to check for sure.

Iv tried both. ...../Volumes/bs\ 1 will say it doesn’t exist. And the same drive name without the 1 will say failed read only

 

[furdi]

It's /Volumes/Image\ Volume/patch-kexts.sh if you're booting from the installer USB, /Volumes/Install\ macOS\ Big\ Sur\ Beta/patch-kexts.sh if you're just opening up Terminal and running it without rebooting from the installer USB first.

Thank you sir! Much obliged... Have an amazing day and thank you for all your hard work on this!

 

[DerMario]

Use this: http://swcdn.apple.com/content/down...m7ounuabziajlktg8nhoptis/InstallAssistant.pkg

OTA updates still don't work on unsupported Mac, unless you spoof to supported BigSur Mac through opencore .

How does this work? Is there any Tutorial?

 

[RogueB]

Successful installation of Big Sur Beta4 on two machines, a late 2012 iMac and MacBook Pro 5,2 (C2D Penryn)

iMac installation:

Download Big Sur Beta4 (to download folder), and launch installassistant.pkg; an actual Big Sur Beta4 Installation program will be placed in the Application folder.

Created a USB installer, using the “sudo /Applications/Install\ macOS\ Big\ Sur\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/MyVolume”” command (“MyVolume” would be name of the USB thumb drive.)

Then, utilized Barry K. Nathan’s micro-patcher v 0.0.19 to “prepare” Big Sur Beta4 USB stick for installation (follow directions on Barry’s GitHub site)

Boot into USB thumb drive, and launch the installer; Big Sur B4 installed without problems, other than (expected) lack of WiFi connectivity.

I run jackluke’s “BigSur IvyBridge beta3 prelinkedkernel fix.command.zip” , from Big Sur desktop, rebooted, and had a fully functional Big Sur beta4 installation, including WiFi.

Not sure, whether it was Beta 4 improvement or just fresh install, but I had no problems installing applications or utilities, while previous Beta 3 caused some crashes (?)



MacBook Pro 5,2 (C2D Penryn), installation.

Note, that I used fully functional Catalina installation, present on one partition, to install Big Sur Beta 4 onto same SATA internal disk, but on separate partition. I did not use USB installer.

Download Big Sur Beta4 to Catalina partition. Launch installation.assistant.pkg (should be in download folder), which will place actual Big Sur Installation program into Application folder.

Further installation steps assume, that SIP and “authenticated-root “ are disabled, with nvram set to ‘boot-args=“_no compat_check amfi get_out_of_my_way=1”’

From Catalina desktop, launch Asentientbot’s Hax3.app to initiate installation of Big Sur Beta4 onto separate partition. Let the installer proceed until it is caught in boot-loop, then (on self-reboot) press option key to boot into “drive selection window,” and choose Catalina as your startup disk.

Execute juckluke’s BigSur Penryn beta3 prelinkedkernel fix.command.zip from Catalina desktop, to allow direct-boot back into Big Sur, activate wifi ,and Framebuffer (?)

See post #2529 on page 102 for some further details, and cross-references, on the method used to activate sound ,and a functional “display“ panel. However, to the set of extensions list copied from Catalina, add two extension supplied by jackluke , i.e. AppleHDA.kext and IO80211Family.kext (though I did not actually copy the latter kext to Big Sur)

This post does not have complete details, but I assumed that most people would have installed one of the other Big Sur betas, and would have some familiarity with the process.

Great thank you to all involved in this "holy grail" of computing. If I did not credit someone, it is completely an inadvertent omission.

If someone would like specific details, let me know.

Hope this may be of help.

Just noted jackluke's post #2871; seems my approach is somewhat behind times, if functional.