In Disk Util go to the top and 'View > All Devices" then format from the top option not the driveI have erased the drive but still receive the error. I don’t know what I’m doing wrong. Here is the error
In Disk Util go to the top and 'View > All Devices" then format from the top option not the driveI have erased the drive but still receive the error. I don’t know what I’m doing wrong. Here is the error
In Disk Util go to the top and 'View > All Devices" then format from the top option not the drive
Oh, I only posted my test in the Mac Pro forum. I should also post to here as well.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.
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
Besides the fact that it’s a day-old first developer beta of a new OS?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, 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
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 .
Stuck on "This version of Mac OS X is not supported on this platform" in singleuser mode, how can I remove telemetry otherwise?
mount -uw /
cd /System/Library/UserEventPlugins/
mv com.apple.telemetry.plugin com.apple.telemetry.plugin2
exit
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
Holding CMD+S after power-on, from the "Big Sur" command shell type:
now you should get the "Big Sur" desktop but currently without Wifi .Code:mount -uw / cd /System/Library/UserEventPlugins/ mv com.apple.telemetry.plugin com.apple.telemetry.plugin2 exit
[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
The late 2013 21.5 iMac literally has a more powerful haswell cpu than the 2014 21.5. This is completely arbitrary.
No, it's Metal GPU Mac, and many already tested that "Big Sur" worked except the Wifi .
No, it's Metal GPU Mac, and many already tested that "Big Sur" worked except the Wifi .
im not gonna do this patch until wifi is workingBeen able to run to the desktop on my Mac Mini Late 2012. Wifi not working, gfx working, bluetooth working.
Here's summary of my steps: https://medium.com/@andv/how-to-install-big-sur-to-mac-mini-late-2012-9d674b563174
[automerge]1592908081[/automerge]
Also, have not deleted telemetry, just sudo nvram boot-args="-no_compat_check"
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!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)
Currently trying to figure out why it doesn't workim not gonna do this patch until wifi is working
really ? how do you think ? ?