No, honestly I do not know!
Please try to figure out if this is probably a problem seen on supported systems, too. Big Sur will have a lot of bugs and most likely we will see them on the unsupported systems as well. We will not fix such bugs...
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
Please try to figure out if this is probably a problem seen on supported systems, too. Big Sur will have a lot of bugs and most likely we will see them on the unsupported systems as well. We will not fix such bugs...
Use option 'C' to change catalog from 'publicrelease' to 'developer' (option 4). Use option U to show Catalog url.
You have all the information to apply the plist patch yourself. Go ahead! This whole story cannot be a success if everybody is just waiting. And please report the results back...
With a little bit of help, I can try and test it.
Do I? Which informations?
Which plist?
Did you read my answer to @dilly or did you just answer to it?
Sure! You created a pull request to fix something with continuity and change something with bluetooth.
Should I just run the commands written in the pull request?
@Ausdauersportler
I run the commands and got
Set: Entry, ":Mac-FC02E91DDD3FA6A4:ContinuitySupport", Does Not Exist
For me, nothing changed.
I run the commands and got
Set: Entry, ":Mac-FC02E91DDD3FA6A4:ContinuitySupport", Does Not Exist
For me, nothing changed.
Turns out it was an issue with disk encryption. I was unable to turn that off (System preferences just ignored the request to do so), so I ended up doing a fresh install and following the instructions on the patcher website. This time I was able to get through step 15 and successfully install Big Sur. I hope this helps someone else!
Hello,
Does anyone know of a patch to enable Mojave under System Preferences - Startup Disk to see a Big Sur as a Boot drive?
On a dual boot Mac Pro with Mojave and Big Sur - Big Sur can see Mojave and Catalina on System Preferences - Startup Disk but not the other way around. Of course one can always hold Option after the chime at boot but was curious if there was another way around this without Opencore Boot Picker installed?
Does anyone know of a patch to enable Mojave under System Preferences - Startup Disk to see a Big Sur as a Boot drive?
On a dual boot Mac Pro with Mojave and Big Sur - Big Sur can see Mojave and Catalina on System Preferences - Startup Disk but not the other way around. Of course one can always hold Option after the chime at boot but was curious if there was another way around this without Opencore Boot Picker installed?
Can I use update macOS normally through system preferences with the update prompts after installing the patcher?
That really remains to seen , someone said no a new patch will be used for updates , but I just ran the updater and it checked for updates and then showed that my mac is up to date with 11.0.1 , it all looks normal , and I hear the beta is out of a developer download , so maybe when another official release that is not in beta is released for updating then will find out if it will update as normal
Someone did say they downloaded the beta 11.1 ver and used this same patcher and it worked , they showed pic as well
Last edited:
I had exactly the same problem. When I installed big sur under system preferences both disks were present and after start Mojave back up as startup disk big sur was no longer available
Updated from 20B50 to 11.1 build 20C5048l linked by @jackluke, on a cMP no issues at all with micropatcher v0.5.1. Same goes for my 2012 MB1 9,1. Have WiFi working on both.
I've checked briefly, most important feature request woul be a Softwareupdate fix for delta updates ofc. I remember with Catalina Patcher a fix came up after a few .xx point releases, still hope thats feasible. Also I'm missing Night Shift on the cMP but not the MBP. Just FYI @Barry K. Nathan, thanks for all you've done so far.
Attachments
your steps are much easier to follow than the barrykns. get it installed on my MBP 2012 + WiFi fix.
I came across this on YouTube. The processes described here, in this forum are over my head. I was fine with dosdude's patches through Catalina. Big Sur, not so much. This video makes things seem simpler, at least for me. Will probably attempt in the next few days. Perhaps it can help others.
You can enable Night Shift and OTA upgrades yourself by searching this thread for posts made by @jackluke. We had a longer public conversation about OTA upgrades and the danger of getting unwanted firmware updates on this way.
This is ridiculous, the steps are the same, but you do not have to read all the warnings @Barry K. Nathan made before about using file vault, etc and can happily jump directly into the deepest possible hole this upgrade may offer.
Dude I've been following this thread from day one, loong before you joined it and I'm aware of the BigSurOTAswufix.
@jackluke you said that there is still work to be done, would love to hear about some progress in case I missed it. As for the integration of both into the micropatcher, Barry has mentioned he was looking into it also, and I'd think many would appreciate to see that coming with the kext payload folder. Thanks
Since the betas of 11.0 Flurry works flawlessly, Drift not at all. Even sleep doesn't work, unluckily...
Dude I've been following this thread from day one, loong before you joined it and I'm aware of the BigSurOTAswufix.
@jackluke you said that there is still work to be done, would love to hear about some progress in case I missed it. As for the integration of both into the micropatcher, Barry has mentioned he was looking into it also, and I'd think many would love to see that coming with the kext payload folder. Thanks
The first sentence you claim to know everything from day one on and in the second you ask for more information in case you missed something - could not be better.
Progress could be made here if experienced users like you start to test such installations on their own before a patcher includes it and it may potentially cause more headache than good.
Finally this is just another request for a better patcher, there was a note on the first page about such requests. But you already know this, you have been following the thread from day one.