Fair enough.My Mac was supported before Apple blocked the update due to some mbp late 2013 logic board damage and I used Patched Sur to install 11.1 beta 2.
My bad.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 11 Big Sur on Unsupported Macs Thread
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
-
- Tags
- 10.16 macos unsupported
- Sort by reaction score
- Status
My bad.
I have a late 2013 iMac running Big Sur 11.0.1. With the up coming 11.1 release , wondering what development has been going on for OTA upgrades or will it be another USB stick install with the Micropatcher ??
Yes, it looks like 11.1 Final will hit on Monday. I say Monday because that's when Fitness+ goes live and you need 11.1.
I still do not see a full installer for 11.1 RC, if one drops I will post the direct link. I also do not think Apple was able to fix the 2013 & 2014 13" MBPro Bricking issue, so I worry about those users trying to patch until Apple figures this out.
I posted my first video using Ben's Patched Sur. I was thinking about turning this into a series.
Any thoughts?
Ideas =
#1. Catalina > Big Sur using - Ben's Patched Sur = DONE
#2. High Sierra, Mojave > Big Sur using - Barry's Micro Patcher = Working on now
#3. High Sierra, Mojave > Big Sur using - moosethegoose2213 automator = thinking
#4. OpenCore Patcher?
#5. Mac Pro Big Sur Patcher using StarPlayrX bigmac = Not sure if I have enough interest
#6 Patched Big Sur Installed on a 2nd internal partition for testing before main upgrade = Not Sure
#7 Patched Big Sur Installed on External Hard drive for testing before main upgrade = Not Sure
#8 Patched Big Sur Install on Unsupported 2010 & 2011 Macs (Testing only do not recommend) = Not Sure
Any thoughts?
Ideas =
#1. Catalina > Big Sur using - Ben's Patched Sur = DONE
#2. High Sierra, Mojave > Big Sur using - Barry's Micro Patcher = Working on now
#3. High Sierra, Mojave > Big Sur using - moosethegoose2213 automator = thinking
#4. OpenCore Patcher?
#5. Mac Pro Big Sur Patcher using StarPlayrX bigmac = Not sure if I have enough interest
#6 Patched Big Sur Installed on a 2nd internal partition for testing before main upgrade = Not Sure
#7 Patched Big Sur Installed on External Hard drive for testing before main upgrade = Not Sure
#8 Patched Big Sur Install on Unsupported 2010 & 2011 Macs (Testing only do not recommend) = Not Sure
Last edited:
Any help, sharing, demonstration and walk thru to facilitate the installation of Big Sur in unsupported Macs would be welcomed by us newbies
And thanks for your effort.
A suggestion for the Big Sur series.
Maybe cover the safer approach of clean install instead of in-place upgrade, since there are lots of changes, up and down, in Big Sur.
Maybe cover backup strategy (TM?), erase disk, clean install, migration/setup as new.
#5 BMO2ac_wifi download is the ABSOLUTE easiest for MacPro 3,1 owners with the BT4/WiFiac hardware upgrade once you have the 11 or so GB file downloaded. Literally 2 steps and 10 minutes of work. Thanks Todd.
Yes Apple has fixed the problem with the late 2013 MBP and my firmware was updated to 429.0.0.0.0 too but my update was 11.27 GB and not a full installer as it started the update by itself.
I used your video to update my Mac Pro 5,1. Very helpful.
@jackluke @ASentientBot @Barry K. Nathan my perfectly Big Sur running iMac 2013 is dead... Suddenly switching off more times, then it was impossible to power on it again. Tried to press ON button for 10 seconds: no beep, no fan rumors, nothing. I think it's the power supply (I had strange behaviors on USB ports) . Now technicians are trying to fix it on a not-Apple Service. Only to say that I'm not disappeared ...In the meanwhile I have just ordered a Mac mini M1 from Amazon, but I'll back here soon, at least for my Mac mini 2010, to continue to test your wonderful patches.
...In the meanwhile I have just ordered a Mac mini M1 from Amazon, but I'll back here soon, at least for my Mac mini 2010, to continue to test your wonderful patches.
Last edited:
Hey Everyone,
So when 11.1 releases officially, those of us who used the patcher (Barry's micro-patcher) to upgrade, will we have to do any extra steps when we want to upgrade to MacOS 11.1? Or can we just click the "update" button and be good?
Thanks in advance to everyone for your time and help, it is greatly appreciated!
So when 11.1 releases officially, those of us who used the patcher (Barry's micro-patcher) to upgrade, will we have to do any extra steps when we want to upgrade to MacOS 11.1? Or can we just click the "update" button and be good?
Thanks in advance to everyone for your time and help, it is greatly appreciated!
Same here.
Concern with this for me is that the ReadMe files (presumably these are the instructions) gets about a dozen changes per day on GitHub. Tried to get clarification from the developer but he misinterpreted my intentions and got upset.
Wonder whether anyone knows what the deal is with the abnormal rate of changes to the ReadMe.
I also own an iMac 27'' Late 2013 and I solved the slowness problems by deciding to eliminate the Fusion Drive, open the iMac and replace the mechanical Hard Disk with a 2TB Crucial MX500 SSD.
Now the iMac flies, turns on and login in a matter of seconds and has never gone so well from Maverick to Catalina!
Keep in mind that with Micropatcher 0.51 I had first installed Big Sur 11.0.1 on the externally connected SSD and it then worked immediately as soon as I replaced the internal Hard Disk and turned the iMac back on.
Now that the 128GB Apple SSD belonging to the Fusion Drive is indipendent (note: I called it Macintosh SD
), I have run some Benchmark and in fact Apple has done well to exclude these iMacs 14,2 from Big Sur, due to the numerous models purchased with Fusion Drive. In fact, the read of Apple internal 128GB SSD is 700MB/sec and the Write 300MB/sec. That's fine as long as the Data does not exceed 128GB; after that, since the Fusion Drive does nothing but move the most used data from the HD to the SSD, everything slows down, ESPECIALLY the Parallels Desktop or the VMWare Fusion Virtual Machines.Now, however, especially since I put the Parallels Desktop VM with Windows 10 Pro in the Apple internal SSD 128GB, Winzozz startup almost instantaneous while before it took minutes as the Fusion Drive wasted time transferring 25GB of VM to the SSD but NEEDING TO FREE THE SPACE FIRST...
The SSDs and the PCI-Nvme Controller used by iMacs from 2015 onwards, on the other hand, are much more performing.
From the FAQ on the first post written by a guy named himself @dosdude1:I also own an iMac 27'' Late 2013 and I solved the slowness problems by deciding to eliminate the Fusion Drive, open the iMac and replace the mechanical Hard Disk with a 2TB Crucial MX500 SSD.
Now the iMac flies, turns on and login in a matter of seconds and has never gone so well from Maverick to Catalina!
Keep in mind that with Micropatcher 0.51 I had first installed Big Sur 11.0.1 on the externally connected SSD and it then worked immediately as soon as I replaced the internal Hard Disk and turned the iMac back on.
Now that the 128GB Apple SSD belonging to the Fusion Drive is indipendent (note: I called it Macintosh SD
Now, however, especially since I put the Parallels Desktop VM with Windows 10 Pro in the Apple internal SSD 128GB, Winzozz startup almost instantaneous while before it took minutes as the Fusion Drive wasted time transferring 25GB of VM to the SSD but NEEDING TO FREE THE SPACE FIRST...
The SSDs and the PCI-Nvme Controller used by iMacs from 2015 onwards, on the other hand, are much more performing.
Also, terrible Fusion Drive performance under Big Sur on Late 2013 iMacs may be the reason Apple dropped support for that model.
Hello everybody! Thanks to all of you, my iMac 27'' late 2013 working perfectly with Big Sur that I installed as soon as the official version 11.0.1 came out.
As a "Nerd", however, I'm very sorry and bothered that OTA updates don't work...
I've seen that maybe can make the macOS recognise my iMac 14.2 as if it were an iMac 15.1 or even 19.1.
I understood that maybe I could do it with OpenCore, but I didn't understand how.
Can I do it easily, without having to initialise the Disk and reinstall everything from scratch, but just starting a simple Patch?
I can't find very simple and straightforward instructions like I did with Micropatcher 0.51 which allowed me to quickly and easily create an installation USB key.
It would be useful to understand even if, in the meantime, I can use some tricks only to install a Patch that allows the above without having to install the entire system as well.,
Once this is done, can you tell me if starting the update to 11.1 from macOS System Preferences it will continue as if reading an hardware Firmware 15.1 or 19.1, without crashing?...
Thank you so much.
As a "Nerd", however, I'm very sorry and bothered that OTA updates don't work...
I've seen that maybe can make the macOS recognise my iMac 14.2 as if it were an iMac 15.1 or even 19.1.
I understood that maybe I could do it with OpenCore, but I didn't understand how.
Can I do it easily, without having to initialise the Disk and reinstall everything from scratch, but just starting a simple Patch?
I can't find very simple and straightforward instructions like I did with Micropatcher 0.51 which allowed me to quickly and easily create an installation USB key.
It would be useful to understand even if, in the meantime, I can use some tricks only to install a Patch that allows the above without having to install the entire system as well.,
Once this is done, can you tell me if starting the update to 11.1 from macOS System Preferences it will continue as if reading an hardware Firmware 15.1 or 19.1, without crashing?...
Thank you so much.
So, to summarize, you are upset about developers (who do this for us for nothing) updating their ReadMe files?
Also, I'm not sure which GitHub files/developers you are referring to since you left that part out.
I just checked BarryKN's latest micropatcher v 0.5.1 ReadMe; it was last updated 27 days ago. The update was a warning about third party antivirus. Perhaps you are patronizing the wrong developer?
Not sure where you read me saying that I was upset or how you otherwise came to that conclusion.
I just wanted to know whether the tool was stable since what I assume are the usage instructions seemed to be changing multiple times a day. Don't sure why this query is considered offensive.