Have you tried looking at Apple's troubleshooting suggestions? (Sorry I don't have any better suggestions at the moment, but this might be better than nothing.)
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
Thanks @Barry K. Nathan
Eventually found an article about fixing the issue.. Linked below incase anyone else gets the same issue
discussions.apple.com
Eventually found an article about fixing the issue.. Linked below incase anyone else gets the same issue
Your Mac was unable to communicate with y… - Apple Community
That is a real kick in the teeth. I have a Mac Pro 4,1-flashed-to-5,1 that dosdude1 has easily kept relevant with only light patching needed for Catalina to work. I feel like moving up to Big Sur without his level of detail would be a risk. It's a shame, but life goes on.
Now I'll have to decide what kind of Mac I'll actually want - probably an Apple Silicon-based at this point.
Keep in mind that Mojave will continue to receive security updates until roughly one year from now, and Catalina until roughly two years from now. You can stick with Catalina for now and take your time when deciding what to do for the future.
link is broken can you fix download link to InstallAssistant.pkg
Hello,
sorry I have read all the steps but I did not understand how to install the update to version 10.
Do you think it will be so much missing from the final release?
sorry I have read all the steps but I did not understand how to install the update to version 10.
Do you think it will be so much missing from the final release?
You can tell from the silence. Also look at this forum. The "issue" has been solved for the greater part.
The link to IntallAssistant.pkg in there is http://swcdn.apple.com/content/down...ff81a690twrhri7k2vlmpkti/InstallAssistant.pkg
and the app made from the downloaded pkg has 16.0.22 as version in its info.plist: looks like beta10, and has same size 12.24GB as beta10.
11.0.1 Beta (20B5012d) . This is a GM candidate for non-Silicon macs, how do I deduce this? Well, they fixed the bug in the Recovery languages and also if you change the wallpaper and have a password to start, you will see that now it keeps the wallpaper on the welcome screen at login.
Attachments
About BigSur 11.0.1 all newer core binaries have been compiled by apple on 25 October , Penryn Core2Duo can still boot the updated kernel 20.1.0 , but I noticed that apple changed the
boot.efi stock size now is 724 KB (maybe they added some additional ARM64 code) while previous one was 642 KB (even if @ASentientBot often rightly wrote that a previous patched Catalina 0xfff boot.efi can still boot a BigSur environment).Attachments
11.0.1 Beta (20B5012d) - I had Beta 10 running without any patches needed on Mac Pro 5,1 with Metal GPU. I accomplished this by installing Beta 10 on my 2015 Macbook Pro and then putting the drive in my Mac Pro 5,1.
On the Mac Pro 5,1 I am enrolled in the Apple Developers Program but software update would not show 11.0.1 Beta (20B5012d) update as available.
So again I used my 2015 Macbook Pro to install 11.0.1 Beta (20B5012d) over Beta 10 on the drive. The Install/upgrade was 3.6gig downloaded. Before i installed the upograde i searched the drive for what was downloaded but could not find it. The install/upgrade took a long time but worked on the 2015 Macbook pro. It keep my installed apps, wallpaper and Login info.
When I put the drive back into the Mac Pro 5,1 it cannot boot from it. The drive is not seen by holding option at boot but Beta 10 was.
11.0.1 Beta and Beta 10 do not have a boot.efi file that I can find?
They both have a Boot folder with many boot.efi.Jxxxap.im4m example boot.efi.j132ap.im4m which is 4k in size
11.0.1 Beta has 32
Beta 10 has 16
What say you guys?
On the Mac Pro 5,1 I am enrolled in the Apple Developers Program but software update would not show 11.0.1 Beta (20B5012d) update as available.
So again I used my 2015 Macbook Pro to install 11.0.1 Beta (20B5012d) over Beta 10 on the drive. The Install/upgrade was 3.6gig downloaded. Before i installed the upograde i searched the drive for what was downloaded but could not find it. The install/upgrade took a long time but worked on the 2015 Macbook pro. It keep my installed apps, wallpaper and Login info.
When I put the drive back into the Mac Pro 5,1 it cannot boot from it. The drive is not seen by holding option at boot but Beta 10 was.
11.0.1 Beta and Beta 10 do not have a boot.efi file that I can find?
They both have a Boot folder with many boot.efi.Jxxxap.im4m example boot.efi.j132ap.im4m which is 4k in size
11.0.1 Beta has 32
Beta 10 has 16
What say you guys?
Last edited:
This is still the Beta 10 link - if all of you just use notepad and save the (old) links you can compare all the time in advance before downloading the very same package again and again...
There is no!So which is the working link to 11.0.1 full installAssistant.pkg?
macOS Big Sur 11.0.1 Beta Release Notes
Note: For today's macOS Big Sur seed, a full installer is not available. If you are starting from macOS Catalina or an earlier version of macOS, you will need to install Beta 10 prior to updating to 20B5012d.
This is what I got from the feedback assistant installed after joining the public beta program. You will have to do the boot and replace method @jackluke already described in detail several times...
Edit:
Look at this post on the Catalina thread..possibly we could do something similar with the Beta 10 full installer?
Last edited:
Unfortunately, no, at least not at this time. Look at the first half of this post by @ASentientBot, particularly the "pkgdmg" thing.
I might be able to add a script or two to the patcher to make ASentientBot's installation method for these zip files a little easier. I don't know if I'll have a chance today or if it'll have to wait for the weekend. (Also, if Apple sticks to the same schedule they used for beta 9 and 10, it's possible they might release a full installer later today.)
I've looked at OpenCore. Several times. I meet the requirements but I'm not clear on if this makes it as easy as using dosdude1's patcher, or if it's easier.
You could even make a copied "macOS Install Data" (already filled with its structure but AssetData) on "BigSur Data Volume", then to make it bootable after stage1 installer some part of that folder "Locked Files" is copied also on the BigSur Preboot UUID at this path
com.apple.installer , this copied path should be tagged with its "Locked Files" boot.efi (BKE , com.apple.Boot.plist and UpdateOptions.plist) in order for "macOS Installer" (stage2 ramdisk) to show at apple startup manager, but you should also add the BigSur Data UUID on example com.apple.Boot.plist .I edited it as generic
BigSurDataUUID that is your APFS Data Volume UUID (different for any machines):diskutil info diskXs1 | grep UUID or ls /System/Volumes/Preboot from BigSur.
Last edited:
Use TimeMachine to revert, or read up on what to do, I did the same last time, wasn't able to boot but I fixed it, I don't know though if your situation is the same, I got it installed and after patching the wifi Kext and deleting a snapshot I wasn't able to boot the OS.
For people with questions.
Always read the last few pages first, many times we see questions here that have an answer in the last few pages.
And please read carefully, I for instance had to posts which people didn't read careful, if they did they wouldn't need to post a followup.
Always read the last few pages first, many times we see questions here that have an answer in the last few pages.
And please read carefully, I for instance had to posts which people didn't read careful, if they did they wouldn't need to post a followup.
You are forgetting to enable TRIM again.
Terminal: sudo trimforce enable
password
YES
YES
Reboot
Safari bug on Beta 10 enable Developer Menu > disable VP9 decoder (Features Experimentals) or update to 11.0.1 beta (fix bugs).
Big Sur is only an exercise on Core 2 Duo Pernyn. Catalina 10.15.7 does surprising well on my Mac mini 2010, I have only to use some tricks to lower my "default" CPU usage from 30% at boot to 4%, to get all the power
