Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,068
I am managing to install "Big Sur", these are the installer stages involved :

stage 1 - automatic unzip of "Install macOS Beta.app" to a temporary APFS "macOS Install Data" volume, followed by auto reboot (this takes about 5 minutes on SSD)

stage 2 - automatic booting (or alt-option key manually booting the "macOS beta installer") to apple white logo on grey wallpaper with loading bar "time remaining", probably a volume check, followed by auto reboot (this takes about 5 minutes)

stage 3 - Booting apple white logo on black wallpaper without "time remaining" and filling the loading bar (probably an attempt to EFI firmware update ?) followed by another auto reboot (this takes about 5 minutes)

stage 4 - "Big Sur" installer on APFS volume showing simply an apple logo on black wallpaper, loading bar and "time remaining" (this going to take about one hour and 15 minutes)

The stages installer GUI style is similar to Mojave, rather than Catalina (that had a GUI logo with a circle wallpaper).

now I am just installing, needs to wait to complete.
 
Last edited:

h9826790

macrumors P6
Apr 3, 2014
16,656
8,587
Hong Kong
I have a 2010 Mac Pro 5,1 with an 8gb Sapphire RX580 gpu with metal support currently running Mojave. It should be able to run Catalina by simply installing a patcher. At that point, would it be possible to upgrade to Big Sur via patcher, assuming one can be made?

It's so stupid that Apple has cut support on these machines especially since they are significantly more powerful and capable than the majority of the 2013 computers they are continuing to support. Apple should cut support on macs like they do on iPhones. Support should only be cut when the device no longer has the hardware needed to run the operating system. I should not have to downgrade to a less capable but newer mac just to get the latest operating system Apple has to offer.

Anyway, if anyone has any idea if a Big Sur patcher is possible for a Mac Pro 5,1, let me know. And if not, any suggestions on what to upgrade to would be helpful aswell.
Oh, I only posted my test in the Mac Pro forum. I should also post to here as well.

Anyway, it's fairly straight forward to install and run Big Sur on Mac Pro 5,1 (via OpenCore).
Screenshot 2020-06-23 at 5.32.41 AM.png

Screenshot 2020-06-23 at 5.42.48 AM.png


No patcher required. The OS can be downloaded and run "natively". The trick is to spoof the SMBIOS as iMac Pro 1,1 before you launch the installer (otherwise you will see that BIErrorDomain error 3).
Screenshot 2020-06-23 at 5.54.06 AM.png


Once the installation is finished, you can switch back to the 5,1 SMBIOS. Of course, we can still inject the iMac Pro board ID to activate HWAccel.
macOS 11 5,1.png
 
Last edited:

Darkdes

macrumors member
Jun 22, 2020
35
39
I am managing to install "Big Sur", these are the installer stages involved :

stage 1 - automatic unzip of "Install macOS Beta.app" to a temporary APFS "macOS Install Data" volume, followed by auto reboot (this takes about 5 minutes on SSD)

stage 2 - automatic booting (or alt-option key manually booting the "macOS beta installer") to apple white logo on grey wallpaper with loading bar "time remaining", probably a volume check, followed by auto reboot (this takes about 5 minutes)

stage 3 - Booting apple white logo on black wallpaper without "time remaining" and filling the loading bar (probably an attempt to EFI firmware update ?) followed by another auto reboot (this takes about 5 minutes)

stage 4 - "Big Sur" installer on APFS volume showing simply an apple logo on black wallpaper, loading bar and "time remaining" (this going to take about one hour)

The stages installer GUI style is similar to Mojave, rather than Catalina (that had a GUI logo with a circle wallpaper).

now I am just installing, needs to wait to complete.

I have made a flash drive from the package file. I don’t know what to do next I can boot it but I get the domain error even after a hard disk erase. I am really confused on why it’s still doing this and what I can do to make it work. I am reinstalling Catalina on the Mac right now through internet recovery. What could be causing this
 
  • Like
Reactions: TimothyR734

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,068
I have made a flash drive from the package file. I don’t know what to do next I can boot it but I get the domain error even after a hard disk erase. I am really confused on why it’s still doing this and what I can do to make it work. I am reinstalling Catalina on the Mac right now through internet recovery. What could be causing this

You should re-download from Mojave or Catalina a full "Big Sur beta" installer using my CatalinaOTAswufix and apply the OTA swu fix during the downloading, in this way the OTA installer post-scripts make automatically a distribution pre-patched "Install macOS beta.app", otherwise as @h9826790 just wrote you should use opencore and spoof to a supported machine.

I have not yet tried "opencore spoofing to install" because don't know the behaviour of how firmware update packages are handled on "Big Sur", but it should work too, I mean EFI firmware update should fail the checksum when detect a different EEPROM, and the installer should continue anyway.
 
Last edited:

MultiFinder17

macrumors 68030
Jan 8, 2008
2,740
2,088
Tampa, Florida
I have made a flash drive from the package file. I don’t know what to do next I can boot it but I get the domain error even after a hard disk erase. I am really confused on why it’s still doing this and what I can do to make it work. I am reinstalling Catalina on the Mac right now through internet recovery. What could be causing this
Besides the fact that it’s a day-old first developer beta of a new OS? ;)

I got a domain error after installing on my supported machine. Twice in a row the install locked up. I rebooted it a few times and then it caught and installed smoothly.
 

Darkdes

macrumors member
Jun 22, 2020
35
39
You should re-download from Mojave or Catalina a full "Big Sur beta" installer using my CatalinaOTAswufix and apply the OTA swu fix, in this way the OTA installer post-scripts make a distribution pre-patched "Install macOS beta.app", otherwise as @h9826790 just wrote you should use opencore and spoof to a supported machine.

I have not yet tried this because don't know yet the behaviour of how firmware update packages are handled on "Big Sur", but it should work too, I mean EFI firmware update should fail the checksum when detect a different EEPROM, and the installer should continue anyway.

I can’t get catalinaOTAswufix to work and cannot find the download anymore. Could you help me by guiding me on how I am supposed to use it and provide a download link for it
[automerge]1592905375[/automerge]
I have looked on this forum and can’t find the catalinaOTAswufix. I have a functioning copy of Catalina installed now and set up what could my macro point of action be
 
Last edited:
  • Like
Reactions: TimothyR734

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,068
I can’t get catalinaOTAswufix to work and cannot find the download anymore. Could you help me by guiding me on how I am supposed to use it and provide a download link for it

Which machine do you have ?

I ask because currently I don't know how to add the USBLegacyInjector.kext to "Big Sur", but only natively APFS supported HighSierra can boot easily using the stock BigSur IOUSB kext .
 
  • Like
Reactions: iMac-iPad

Darkdes

macrumors member
Jun 22, 2020
35
39
Which machine do you have ?

I ask because currently I don't know how to add the USBLegacyInjector.kext to "Big Sur", but only natively APFS supported HighSierra can boot easily using the stock BigSur IOUSB kext .

I am using a mid 2012 unibody mbp
 
  • Like
Reactions: TimothyR734

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,068
Stuck on "This version of Mac OS X is not supported on this platform" in singleuser mode, how can I remove telemetry otherwise?

Provided that you add in nvram boot-args at least "-no_compat_check", holding CMD+S after power-on, from the "Big Sur" command shell type:
Code:
mount -uw /
cd /System/Library/UserEventPlugins/
mv com.apple.telemetry.plugin com.apple.telemetry.plugin2
exit
now you should get the "Big Sur" desktop but currently without Wifi .
[automerge]1592907040[/automerge]
I can’t get catalinaOTAswufix to work and cannot find the download anymore. Could you help me by guiding me on how I am supposed to use it and provide a download link for it
[automerge]1592905375[/automerge]
I have looked on this forum and can’t find the catalinaOTAswufix. I have a functioning copy of Catalina installed now and set up what could my macro point of action be

Try this: https://forums.macrumors.com/threads/macos-10-15-catalina-on-unsupported-macs.2183772/post-28320558

Launch it from Catalina desktop or downloads folder, click first "Software Update fix" button, then start to download the 10.16 macOS beta OTA installer, during downloading re-launch catalinaotaswufix and click the "OTA update fix" button.

This should make a pre-patched distribution "Install macOS beta.app" that you can run directly from Catalina desktop.
 
Last edited:

Darkdes

macrumors member
Jun 22, 2020
35
39
Holding CMD+S after power-on, from the "Big Sur" command shell type:
Code:
mount -uw /
cd /System/Library/UserEventPlugins/
mv com.apple.telemetry.plugin com.apple.telemetry.plugin2
exit
now you should get the "Big Sur" desktop but currently without Wifi .
[automerge]1592907040[/automerge]


Try this: https://forums.macrumors.com/threads/macos-10-15-catalina-on-unsupported-macs.2183772/post-28320558

Launch it from Catalina desktop or downloads folder, click first "Software Update fix" button, then start to download the 10.16 macOS beta OTA installer, during downloading re-launch catalinaotaswufix and click the "OTA swu fix" button.



I have a mid 2012 unibody could that be a problem
 
Last edited:
  • Like
Reactions: TimothyR734

FlorisVN

macrumors 6502a
Nov 8, 2013
979
380
The late 2013 21.5 iMac literally has a more powerful haswell cpu than the 2014 21.5. This is completely arbitrary.

Maybe apple
No, it's Metal GPU Mac, and many already tested that "Big Sur" worked except the Wifi .

HD4000 is also working then.. ?
besides the Nvidia kepler card.. ?

maybe this wifi upgrade can be a solution for Uniboy mpb users.. ? :
 

Darkdes

macrumors member
Jun 22, 2020
35
39
No, it's Metal GPU Mac, and many already tested that "Big Sur" worked except the Wifi .

Ok so the Mac is not the problem. I would try CatalinaOTAswufix but I don't know how to use it or where to get it. if you could help me in using catalinaOTAswufix I would use it
 

brandonsierra

macrumors member
Jun 10, 2017
40
74

toru173

macrumors 6502
Apr 5, 2007
332
154
stage 2 - automatic booting (or alt-option key manually booting the "macOS beta installer") to apple white logo on grey wallpaper with loading bar "time remaining", probably a volume check, followed by auto reboot (this takes about 5 minutes)
I can fill in this blank, at least. At this point it's extracted and booted to the BaseSystem.dmg, and is running EnsureRecoveryBooter from the diskmanagement framework. See https://derflounder.wordpress.com/2...lume-or-partition-with-create_macos_recovery/ for some more info. This always happens before a new OS install/update these days!
 

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,068
And after three hours I also got "Big Sur" desktop loaded on core2duo, I followed a different path from ASentientBot, I used CatalinaOTAswufix.app , anyway I'd advise to use his method is safer, because after my "OTA update" I found a weird "Big Sur" label "Update" (a new APFS volume for firmware updates?) with many Firmware files, probably the installer attempted a firmware update on unsupported machine, but no issues.

The current 0.59 opencore version can't inject any patched kext on the prelinkedkernel, even if it is still there, I mean they changed the "kextcache" method but the prelinkedkernel is still used (kcditto to put it in its "Big Sur" Library and Users Data APFS volume).

Of course: no wifi, no sound, no video acceleration, the challenge has just begun.

About Wifi bad news, apple has dropped also AirPortBrcm4360 driver (the one I patched for AirDrop that spoofed to a supported Catalina Wifi), now seems they only like the AirPortBrcmNIC.kext .

I guess rather than for Metal GPU, apple dropped the 2012 Mac because of their Wifi card.
 

Attachments

  • BigSur on core2duo with catalinaotaswufix.png
    BigSur on core2duo with catalinaotaswufix.png
    727.8 KB · Views: 529
  • Big Sur new APFS Update volume.png
    Big Sur new APFS Update volume.png
    113.9 KB · Views: 480
  • Big Sur Wifi dropped driver.png
    Big Sur Wifi dropped driver.png
    30 KB · Views: 442
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.