How to disable library validation: https://forums.macrumors.com/threads/macos-10-15-catalina-on-unsupported-macs.2183772/post-28257563
Ok i have ran the command and can now boot the flash drive but i still get the error 3 warning and cant install
really ? how do you think ? ?it's likely that they will re-add support for the late 2013 iMacs
Must be the Haswell CPU requirement. Fwiw it also supports the late-2013 Retina which also had GT650M graphics
Anyone know the best way of contacting Apple to ask for this?it's likely that they will re-add support for the late 2013 iMacs
Fixed with Wiping whole drive in DU a new APFS drive.Im at this stage too with my 15" Mid-2012 2.6 Retina MacBook Pro 10,1
Speaking as someone who’s owned two ARM desktop computers (Acorn Archimedes and RiscPC) I see no reason why they shouldn’t outperform the competition now, just like they did back then.I distaste ARM computing in all its forms, I hope we shall not see desktop or laptop computers on ARM becoming the norm too soon. But perhaps we shall adapt.
I created a basic patch which seems to get a copy of the OS installed.
View attachment 926159
My steps (briefly) were:
- Disable Library Validation and SIP
-launchctl setenv DYLD_INSERT_LIBRARIES $PWD/Hax.dylib
- Open and click through the installer app
This is all that's necessary for an "install to this machine" outcome. However, it currently does not boot... will report back if I figure anything out.
For anyone else who only has an unsupported machine and wants to test, here are the files! There are definitely alternatives like using OpenCore, cloning from a supported machine, etc. But thought I'd share this anyways.
Edit: Also, it needs over 50 gigs to do a clean install. I'm assuming it extracts the .zip to a temp location (~10gb), builds an installer package from the pbzx compressed payload (~10gb) then actually executes the staged installer (~10gb), which puts the files on disk (~20gb). So at the moment it looks like a hybrid macOS/iOS installer. The boot process for basesystem.dmg is completely different too - they've hardened and signed rc.cdrom, and it no longer creates ramdisks
There's no full secure boot chain though, so worst case scenario we have to patchboot.efi
or something.
Arghhh, it's pretty unfair and unreasonable they left iMac Late 2013 out!
Hope it can be made to work, because Big Sur sure looks great.
You should erase from DiskUtilty first an empty volume as an APFS container, because currently it's not easy to upgrade a previous Catalina installation, even removing the SystemVersion.plist from /System/Library/CoreServices/
otherwise you could try my opencore setup (my included configuration doesn't spoof to any supported "Big Sur" machine so it's totally safe at least to boot):
macOS 10.15 Catalina on Unsupported Macs
Hello everyone, I just updated the USBOpenCoreAPFSloader, even if previous version still works, this is based on the latest opencore binaries (current version 0.5.9) , that added a new function BlacklistAppleUpdate to block the apple EFI firmware update, as I call it the "big apple logo with big...forums.macrumors.com
Since it's an EFI external you can install it near a "Big Sur" USB Installer, regardless now it's a containerised APFS installer.
Apple silicon - just call it PowerPC v.2 ARM Macs. Silicon sounds lame. Think different 2 !
Im at this stage too with my 15" Mid-2012 2.6 Retina MacBook Pro 10,1
[automerge]1592900000[/automerge]
Fixed with Wiping whole drive in DU a new APFS drive.
No stuck on needing an internet connection to continue. but my wifi isn't showing up and I don't have an ethernet adapter... /cry
Seems like 2012 Macs are dropped, and I believe many are still using those. Ka-ching?
This is why I dislike Apple computers. Arbitrary dropping off from OS support despite the device itself is still perfectly capable. In contrast, Windows 10 is able to be installed even on old machines.
Downside of switching to ARM, now there's no Windows option to extend the life of these older Macs (unless Microsoft announced Windows 10 ARM will support Apple silicon). Just like an iPhone, when Apple dropped your computer from support, that's it. It seems acceptable for phones, but for laptops and desktops, seems unreasonable. Most people don't need the latest performance, with even 10 year old computers still sufficient for many.
I've been thinking about whether the 2013 Mac Pro's Ivy Bridge CPU might be different from the others in some way... and it turns out, it is! CVE-2020-0543 (SRBDS) affects most Ivy Bridge CPUs, but not the Xeon E5 series used by the 2013 Mac Pro. For this CVE, Intel provided microcode updates for Haswell and later, but not Ivy Bridge.
Perhaps Apple doesn't want to officially support Macs that have Intel CPU flaws which (more or less) cannot be mitigated. For all I know (since I'm not a lawyer), this could be some legally driven thing. By the way, this would also explain why Apple decided not to officially support Catalina on the 2012 Mac Pro. In that case, the vulnerability was Microarchitectural Data Sampling (MDS).
This still doesn't explain the Late 2013 iMacs, but with that one exception, Apple's choice of models they're supporting in Big Sur now appears to me to be logically consistent and not arbitrary. The goal seems to me to be: avoid supporting Mac models with known unmitigated Intel CPU flaws in any new macOS release. (I almost wrote "support all Macs without known unmitigated Intel CPU flaws as of the OS's release date" but in reality it's probably a little more complicated than that, even if that is basically the result in the end.)
Ok. I have tried 2 different ways of installing with the same domain error 3 occurring. What could this be. I have erased the drive and still have had no luck
If you used CatalinaOTAswufix to download the "Install macOS Beta.app" have you applied also the OTA swu fix ?
Because you have to whitelist the unsupported machine and the board-id, my OTA swu fix simply puts "return true;" on the distribution file, that should be suffice at least to install "Big Sur" on unsupported machines without any unwanted EFI firmware update.
No. I couldn’t get that way of downloading the app to work. I had a friend with a supported Mac download the app and send it to me on google drive
I doubt it will work then (unless you use opencore to spoof the machine), because apple deliver a customised signature "Big Sur" installer, I mean very restricted to target machines that probably they indicate as "Domains".
Try this InstallAssistant.pkg : https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28586298
What should I do after using this package