Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Installing the 19H2 patched CoreBrightness.framework breaks Safari on my iMac. While the NightShift is working nicely with the Framework installed I cannot use the Safari to browse any longer :) This is a really nice one.
I installed the patched CoreBrightness on my MBP 8,2 external drive and I haven't any issue with Safari, while the NightShift works OK.
 
App Store

macOS Big Sur 11.0.1 beta (20B5012d)

 

In a way, this is a strong indication that the work on version 11.0 has already been completed and that we should see the long-awaited launch of Big Sur happening in the coming days.

Whoever is in the beta program, it is good to leave, as the Big Sur 11.0 installer will not appear if you continue in the beta, you will go to the 11.0.1 beta.
 
In a way, this is a strong indication that the work on version 11.0 has already been completed and that we should see the long-awaited launch of Big Sur happening in the coming days.

Whoever is in the beta program, it is good to leave, as the Big Sur 11.0 installer will not appear if you continue in the beta, you will go to the 11.0.1 beta.
Not in the coming days, more like 2 weeks to go if not a bit more.
 
disagree with you, I believe we will see him later this week. There's no reason to launch an 11.0.1 if you don't release 11.0
You can disagree with me all you want, thing is, 11.0 will be for the to be released new macs with likely references to unreleased macs, now...Apple don't want people to know that just yet.

Apple also always releases GM candidates first at least a week before, we haven't seen a GM just yet.
There's also the letter g in the last beta, should be a or something to be close to release.

And, there will be an event, there hasn't been a date released yet by Apple just yet, some say it will be the 17th. of November.

I will eat my shoes if Apple releases macOS 11 this week.
 
You can disagree with me all you want, thing is, 11.0 will be for the to be released new macs with likely references to unreleased macs, now...Apple don't want people to know that just yet.

Apple also always releases GM candidates first at least a week before, we haven't seen a GM just yet.
There's also the letter g in the last beta, should be a or something to be close to release.

And, there will be an event, there hasn't been a date released yet by Apple just yet, some say it will be the 17th. of November.

I will eat my shoes if Apple releases macOS 11 this week.

You're right, but she did this quite recently with iOS, first releasing the 14.1 and 14.2 beta.
We will not lose faith.

It got lost on release dates, including betas versions this year.

We have already launched every day of the week. There is no longer a pattern.
 
  • Like
Reactions: TimothyR734
You're right, but she did this quite recently with iOS, first releasing the 14.1 and 14.2 beta.
We will not lose faith.

It got lost on release dates, including betas versions this year.

We have already launched every day of the week. There is no longer a pattern.
Just a few more weeks, they'll be behind you before you know it.
I am actually really looking forward to the new Apple silicon Macs, I want/need a new Mac, preferably a new Mac Mini, mine is from 2012, a capable Mini but I am a bit tired of not being able to Update the regular supported way.
I was really thinking macOS Big Sur could be supported on my 2012 MBP, it was sold until October 2016, so not even 4 years ago and they dropped support, WTF Apple.
 
Here is a fetched full OTA Installer for 11.0.1 beta:
http://updates-http.cdn-apple.com/2020SummerSeed/patches/001-58875/...4110f12785f6cad55.zip

Note this is not a full InstallAssistant.pkg for createinstallmedia , but instead you should use USBOpenCore spoofing to OTA update, otherwise complete a stage1 BigSur Installer from any USB BigSur Installer, then reboot to another macOS and after unzipped this zip package, through ASentientBot method replace on the BigSur /macOS Install Data/UpdateBundle/ the content of the AssetData (unzipped from that link), then reboot to apple startup manager and select the "macOS Installer" stage2 to continue the installation with updated packages.
 
I made some searching and noticed that Disassembler can understand till ARMv7 and ARM64 (that is ARMv8) while any recent iOS hardware device and Apple Silicon Mac should use ARMv8.4-A .
Yes, thank you - now I see that when opening a file, the disassembler offers the option AArch64 instead of intel. I‘ll look closer but need to understand the ARM RISC instructions better first.
Wasn‘t there mention earlier in this thread that some functionality dropped from BS in intel implementation, does exist for ARM?
EDIT: found it, here: #5,064 , by antony34.
 
Last edited:
Yes, thank you - now I see that when opening a file, the disassembler offers the option AArch64 instead of intel. I‘ll look closer but need to understand the ARM RISC instructions better first.
Wasn‘t there mention earlier in this thread that some functionality dropped from BS in intel implementation, does exist for ARM?
So with BigSur seems apple (after Catalina) double sized almost all of their system core binaries exec to include both AArch64 and x86_64 coding, I guess more than rewrite many core binaries, they simply used those from their iOS that were already ARM64 , just to say, even the System Update packing is similar to iOS .
 
My guess the URL will be this...


Question will be, what will the XX/XX stand for. 🤔
Sadly, there are quite a few possibilities, like in 100 X100= 10.000.
Except, the first XX won't be lower than the last beta, that number was 59, so 40 X 100= 4000 possibilities remaining.
Actually, one number was higher.¯\_(ツ)_/¯

A few of the last betas were
/59/23/
/53/17/
/49/42/
/10/06/
/60/31/
 
So with BigSur seems apple (after Catalina) double sized almost all of their system core binaries exec to include both AArch64 and x86_64 coding, I guess more than rewrite many core binaries, they simply used those from their iOS that were already ARM64 , just to say, even the System Update packing is similar to iOS .
The move from Mojave to drop X86 unity binaries was precisely for this reason.
 
  • Like
Reactions: TimothyR734
I have downloaded update and go to first reboot on Mac mini 2012 by spoofing Mac - and as a result I can’t boot nothing(((((( even recovery or with Alt key. Any help suggestions?
 
11.0.1 install and patch success, had some bumps in the way (machine wouldn't post, the indicator light would flash with no sound) but a disassembly, removal and reinstallation of SSD and RAM fixed it and the machine was able to post and it greeted me with no entry sign ( I had the OpenCore EFI and boot file blessed so I could boot into macOS and get the ota and install the update without any problem) I just selected EFI, machine restarted then selected preboot and machine took a lot longer but it restarted then selected macOS and It took like 2 or 3 minutes but it booted, I booted normally to Big Sur and remove everything OpenCore related to it and patched with barryKN's micro patcher v.0.4.4 and after the reboot I got a fully functional install
Screen Shot 2020-10-28 at 6.16.10 PM.png
 
So a weird issue.. I had beta 10 installed on my late 2013 iMac and had everything working, including Apple Watch unlock. I've now upgrade my phone to a new iphone12, and a start of that process, I had to unpair-repair watch with the phone.

I now can now longer activate Apple Watch to unlock the iMac, with an error message that its unable to contact watch and ensure its on your wrist and unlocked and your phone is unlocked

Any ideas?
 
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.