OK, but I'll wait the installer.pkg B10 if available or GM to update from beta 9, then I'll apply the last micropatcher 0.4.x fixes by @Barry K. Nathan
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
OK, but I'll wait the installer.pkg B10 if available or GM to update from beta 9, then I'll apply the last micropatcher 0.4.x fixes by @Barry K. Nathan
Anyone using OpenCore (USBOpenCoreAPFSloader4s) to update macOS Big Sur Beta 10, it is necessary to change
<key>csr-active-config</key>
<data>00000000</data>
<key>csr-active-config</key>
<data>00000000</data>
You meant SIP enabled
AAAAAA== ? Maybe, for staged installer is sufficient -no_compat_check, but as I wrote a sealed system and stock snapshot booting (without kext patches) is required to complete the OTA update when spoofing, I also noticed that if someone used a public beta 9 from Software update is delivered a beta10 package of 11,36 GB, while from a dev beta 9 install a smaller beta10 3,8 GB package.
Last edited:
Hello , is there installer for beta 10 ? Or how is the way to update from beta 9 to 10 and how it will be with next update for Big Sur unsupported Mac in future ?
Following the short recipe @justperry posted on the last page I could update my beta 9 iMac 2011 to b10 successfully.
Only the latest 0.4.1 micro patcher threw this error message:
which I healed by applying manually before rebooting this command
After reboot I figured out that the AMD hardware acceleration is back with B10, you get 4K H.264 and 4K HEVC, used VideoProc to check this.
System: iMac 2011, AMD WX4170, BCM943602CDP WIFI/BT, Big Sur Beta 10, Lilu and Whatevergreen via OpenCore
Only the latest 0.4.1 micro patcher threw this error message:
me@iMac ~ % /Volumes/Install\ macOS\ Big\ Sur\ Beta/patch-kexts.sh --2011 --iMac --no-wifi
Password:
Using --2011 mode.
Enabling 2011 iMac patch (--iMac command line option)
Disabling WiFi patch (--no-wifi command line option)
Installing kexts to:
/
Volume appears to have a Big Sur installation (build 20A5395g). Continuing.
Volume is mounted from device: /dev/disk1s5s1
Mounted device is a snapshot. Will now mount underlying volume
from device /dev/disk1s5 at temporary mountpoint:
/System/Volumes/Update/mnt1
Checking for KernelCollections backup...
Backup not found. Performing backup now. This may take a few minutes.
Backing up original KernelCollections to:
/System/Volumes/Update/mnt1/System/Library/KernelCollections/KernelCollections-20A5395g.tar.lz4
a BootKernelExtensions.kc
a SystemKernelExtensions.kc
Installing High Sierra AppleHDA.kext
Installing High Sierra Intel HD 3000 kexts
Installing LegacyUSBInjector.kext
Installing Catalina AppleBCM5701Ethernet.kext
Installing highvoltage12v patched iMac-2011-family.kext
AMD Polaris Card found
Using iMacPro1,1 enabled version of AppleIntelSNBGraphicsFB.kext
Using Big Sur AppleBacklight.kext
Using kmutil to rebuild boot collection...
Using kmutil to rebuild system collection...
Copying deferred prelinked kernels in /System/Volumes/Update/mnt1...
/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/kext_tools/kext_tools-692.40.7/kc_staging.m.279: Encountered error while inspecting path: Error Domain=NSCocoaErrorDomain Code=260 "The folder “PrelinkedKernels” doesn’t exist." UserInfo={NSFilePath=/System/Volumes/Update/mnt1/Library/Apple/System/Library/PrelinkedKernels, NSUserStringVariant=(
Folder
), NSUnderlyingError=0x7f805d40c5b0 {Error Domain=NSOSStatusErrorDomain Code=-43 "fnfErr: File not found"}}
/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/kext_tools/kext_tools-692.40.7/kc_staging.m.279: Encountered error while inspecting path: Error Domain=NSCocoaErrorDomain Code=260 "The folder “PrelinkedKernels” doesn’t exist." UserInfo={NSFilePath=/System/Volumes/Update/mnt1/Library/Apple/System/Library/PrelinkedKernels, NSUserStringVariant=(
Folder
), NSUnderlyingError=0x7f805d508570 {Error Domain=NSOSStatusErrorDomain Code=-43 "fnfErr: File not found"}}
Copying KCs in /System/Volumes/Update/mnt1...
System Volume UUID: 6CEB13E1-3AAA-4470-8D8A-E13FE6F116EF
Volume Group UUID: 76E5F318-CD7C-4F8B-B63C-4FB913D53356
Preboot disk: /dev/disk1s2
Preboot volume: /System/Volumes/Preboot
Copying: /System/Volumes/Update/mnt1/System/Library/KernelCollections/BootKernelExtensions.kc.elides -> /System/Volumes/Preboot/76E5F318-CD7C-4F8B-B63C-4FB913D53356/boot/System/Library/KernelCollections
Copying: /System/Volumes/Update/mnt1/System/Library/KernelCollections/BootKernelExtensions.kc -> /System/Volumes/Preboot/76E5F318-CD7C-4F8B-B63C-4FB913D53356/boot/System/Library/KernelCollections
Creating new root snapshot.
Can't use last-sealed-snapshot or create-snapshot without --bootefi.
Attempting to unmount underlying volume (don't worry if this fails).
This may take a minute or two.
umount(/System/Volumes/Update/mnt1): Resource busy -- try 'diskutil unmount'
Volume BSB10 on disk1s5 failed to unmount: dissented by PID 0 (kernel_task)
Installed patch kexts successfully.
me@iMac ~ %
Password:
Using --2011 mode.
Enabling 2011 iMac patch (--iMac command line option)
Disabling WiFi patch (--no-wifi command line option)
Installing kexts to:
/
Volume appears to have a Big Sur installation (build 20A5395g). Continuing.
Volume is mounted from device: /dev/disk1s5s1
Mounted device is a snapshot. Will now mount underlying volume
from device /dev/disk1s5 at temporary mountpoint:
/System/Volumes/Update/mnt1
Checking for KernelCollections backup...
Backup not found. Performing backup now. This may take a few minutes.
Backing up original KernelCollections to:
/System/Volumes/Update/mnt1/System/Library/KernelCollections/KernelCollections-20A5395g.tar.lz4
a BootKernelExtensions.kc
a SystemKernelExtensions.kc
Installing High Sierra AppleHDA.kext
Installing High Sierra Intel HD 3000 kexts
Installing LegacyUSBInjector.kext
Installing Catalina AppleBCM5701Ethernet.kext
Installing highvoltage12v patched iMac-2011-family.kext
AMD Polaris Card found
Using iMacPro1,1 enabled version of AppleIntelSNBGraphicsFB.kext
Using Big Sur AppleBacklight.kext
Using kmutil to rebuild boot collection...
Using kmutil to rebuild system collection...
Copying deferred prelinked kernels in /System/Volumes/Update/mnt1...
/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/kext_tools/kext_tools-692.40.7/kc_staging.m.279: Encountered error while inspecting path: Error Domain=NSCocoaErrorDomain Code=260 "The folder “PrelinkedKernels” doesn’t exist." UserInfo={NSFilePath=/System/Volumes/Update/mnt1/Library/Apple/System/Library/PrelinkedKernels, NSUserStringVariant=(
Folder
), NSUnderlyingError=0x7f805d40c5b0 {Error Domain=NSOSStatusErrorDomain Code=-43 "fnfErr: File not found"}}
/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/kext_tools/kext_tools-692.40.7/kc_staging.m.279: Encountered error while inspecting path: Error Domain=NSCocoaErrorDomain Code=260 "The folder “PrelinkedKernels” doesn’t exist." UserInfo={NSFilePath=/System/Volumes/Update/mnt1/Library/Apple/System/Library/PrelinkedKernels, NSUserStringVariant=(
Folder
), NSUnderlyingError=0x7f805d508570 {Error Domain=NSOSStatusErrorDomain Code=-43 "fnfErr: File not found"}}
Copying KCs in /System/Volumes/Update/mnt1...
System Volume UUID: 6CEB13E1-3AAA-4470-8D8A-E13FE6F116EF
Volume Group UUID: 76E5F318-CD7C-4F8B-B63C-4FB913D53356
Preboot disk: /dev/disk1s2
Preboot volume: /System/Volumes/Preboot
Copying: /System/Volumes/Update/mnt1/System/Library/KernelCollections/BootKernelExtensions.kc.elides -> /System/Volumes/Preboot/76E5F318-CD7C-4F8B-B63C-4FB913D53356/boot/System/Library/KernelCollections
Copying: /System/Volumes/Update/mnt1/System/Library/KernelCollections/BootKernelExtensions.kc -> /System/Volumes/Preboot/76E5F318-CD7C-4F8B-B63C-4FB913D53356/boot/System/Library/KernelCollections
Creating new root snapshot.
Can't use last-sealed-snapshot or create-snapshot without --bootefi.
Attempting to unmount underlying volume (don't worry if this fails).
This may take a minute or two.
umount(/System/Volumes/Update/mnt1): Resource busy -- try 'diskutil unmount'
Volume BSB10 on disk1s5 failed to unmount: dissented by PID 0 (kernel_task)
Installed patch kexts successfully.
me@iMac ~ %
Code:
Creating new root snapshot.
Can't use last-sealed-snapshot or create-snapshot without --bootefi.which I healed by applying manually before rebooting this command
Code:
me@iMac ~ % sudo bless --folder /System/Volumes/Update/mnt1/System/Library/CoreServices --bootefi --create-snapshot
Password:
me@iMac ~ % sudo rebootAfter reboot I figured out that the AMD hardware acceleration is back with B10, you get 4K H.264 and 4K HEVC, used VideoProc to check this.
System: iMac 2011, AMD WX4170, BCM943602CDP WIFI/BT, Big Sur Beta 10, Lilu and Whatevergreen via OpenCore
Attachments
Last edited:
Since the beta 10 update, I'm not able to boot into recovery mode anymore (Command (⌘) and R) in French. Am I the one? I think it's a bug... (Edit : works quite well in English)
Last edited:
Thanks for filing a GitHub issue about this problem. Quoting from my response on that issue (which I edited a couple times):
Is my issue to do with this? - with b10 I can't delete the remaining snapshot from Recovery. Even with the BS System volume mounted and R/W, I get 'Error -69863: Insufficient privileges'. I've managed to delete all snapshots manually up to/incl b9.
After I updated b9 to b10, the usual 'com.apple.update...' sort of snapshot was listed - but with 'Purgeable: No' this time around. I added a newer snapshot and zapped the Apple one with Barry's script. The remaining one I added stated 'Purgeable: Yes' but it still just won't delete.
Any thoughts anyone?
EDIT: I just reapplied the full Beta10 Installer over the injected-into-b9 delta b10 update and I 'can' now delete the initial update snapshot from recovery, leaving none (even though it was flagged as 'Purgeable: No').
Last edited:
I used the default, but that's right SIP and authenticated-root enabled
I did not have to change this to successfully get beta 10 OTA (3.82GB) using OpenCoreAPFSloader4s1
I have installed Big Sur beta 9 onto a Samsung EVO 860 SSD drive via a stat to USB cable using my 2015 Macbook Pro.
I then installed the SSD into my Mac Pro 5,1 with a Metal Capable Graphics card and it boots without any additional drivers or hacks. Runs well. Its pretty speedy actually.
Yesterday after beta 10 was announced, the SSD drive in the Mac Pro 5,1 would not update to Big Sur beta 10 via the app store - stating "No available updates - you are up to date".
I removed the SSD and re-connected it to my 2015 Macbook Pro and I did an in place app store upgrade download and install to beta 10 - which took a long time. I put the upgraded SSD drive back in the Mac Pro 5,1 and all is working.
Tried to use Carbon Copy Cloner v5.1.22-b5.6073 to clone the drive in my Mac Pro 5,1 and although Carbon Copy Cloner reported that the drive cloned successfully, the cloned drive would not boot - so work has to be done there. I haven't tried using Carbon Copy Cloner v5.1.22-b5.6073 with the drive booted up on the 2015 Macbook Pro - so maybe the results are could be different?
We will see what happens when and if the next beta version has a proper installer or with the GM release.
Other observations -
Some older applications still don't work will need to be upgraded by their developers and some were fixed with beta 10.
It you have a multi-drive / multi boot system and you use system properties - startup disk in either High Sierra, Catalina or Mojave and try to and restart and boot from Big Sur - The drive is not listed there - even though you can see the drive on your desktop if you have Finder preferences to show all hard drives. So you have to do restart and hold option.
Big Sur beta 10 does have alternate Desktop images to choose from if the circus color scheme of Big Sur doesn't float your boat.
I then installed the SSD into my Mac Pro 5,1 with a Metal Capable Graphics card and it boots without any additional drivers or hacks. Runs well. Its pretty speedy actually.
Yesterday after beta 10 was announced, the SSD drive in the Mac Pro 5,1 would not update to Big Sur beta 10 via the app store - stating "No available updates - you are up to date".
I removed the SSD and re-connected it to my 2015 Macbook Pro and I did an in place app store upgrade download and install to beta 10 - which took a long time. I put the upgraded SSD drive back in the Mac Pro 5,1 and all is working.
Tried to use Carbon Copy Cloner v5.1.22-b5.6073 to clone the drive in my Mac Pro 5,1 and although Carbon Copy Cloner reported that the drive cloned successfully, the cloned drive would not boot - so work has to be done there. I haven't tried using Carbon Copy Cloner v5.1.22-b5.6073 with the drive booted up on the 2015 Macbook Pro - so maybe the results are could be different?
We will see what happens when and if the next beta version has a proper installer or with the GM release.
Other observations -
Some older applications still don't work will need to be upgraded by their developers and some were fixed with beta 10.
It you have a multi-drive / multi boot system and you use system properties - startup disk in either High Sierra, Catalina or Mojave and try to and restart and boot from Big Sur - The drive is not listed there - even though you can see the drive on your desktop if you have Finder preferences to show all hard drives. So you have to do restart and hold option.
Big Sur beta 10 does have alternate Desktop images to choose from if the circus color scheme of Big Sur doesn't float your boat.
Pls read the release notes. CCC is currently unable to do a full clone of Big Sur due to Apple's changes. The cloning fallback creates a full data backup. You install the new Big Sur from scratch and migrate from that backup.
(pipped at the post by another member, regarding CCC)
Question does anyone here know how long it will be until Dos dude makes a patcher if he does?
I would say, just be patient.
If he will make a patch, I would expect when GM or final release is there..
Alright Im just wondering hopefully he will be able to get the late 2012 iMac working
Waiting for the Beta 10 full installer.pkg, I have finally updated iMac 2013 (iMac14,1) Big Sur from beta 3 to beta 9 on my main external SSD Samsung T5, with @Barry K. Nathan micropatcher patched USB pendrive, without using set-vars.sh and patch-kexts.sh on USB Stick, OVER the previous installation, keeping all apps already installed, in only 45 minutes. All works fine without kext patches. Apple has simply choosen to not support it anymore for marketing, but is still perfectly compatible and FAST. You need only an external USB 3.0 SSD (or internal, if you know how to replace it) for optimized performance, but also with the slow original hard disk is usable exactly like the "supported" Catalina. Bye bye iMac Silicon at least until 2022.
Attachments
Correct, they just added it: http://swcdn.apple.com/content/down...ff81a690twrhri7k2vlmpkti/InstallAssistant.pkg
Just Updated, twas a breeze, after every reboot I held the option key, then choose Opencore, after first start I choose reboot, after that just open core and my SSD where my normal working OS reside, after several reboots it worked.
The only thing I still have to do is fix my wifi on my 2012 Mac Mini, that shouldn't take long nor too much time.
Oh FF sake.
I checked before I updated with Opencore, wasn't there before, but then again, Update went smoothly with Opencore.
Is there any timestamp on the page, as in, when/at what time was it updated, like to know because I did check it before updating with Opencore just about 1 hour ago.
Edit: There is
But that brings me to another question, what time is this, can't be the time where Apple is located, too early for that time.
And I am pretty sure I checked later than that time here in Mainland Europe.
Greenwich Time???
Automatically set to Western Europe time???
Last edited:
Hi, the Link is
[automerge]1602791216[/automerge]
Hi, the Link is
julian-fairfax/macos-patcher
Command line tool for running macOS on unsupported Macs - End of support/development - julian-fairfax/macos-patchergithub.com
I feel exactly the same. Mac mini 2012 I want to wait Apple Silicon butwhen I got install Big Sur I felt that I won 1 or 2 years for the change
I’m interesting if you could explain better this words “without using set-vars.sh and patch-kexts.sh on USB Stick”. Now I’m in b9 and I’d wait till b10 installer or GM but I want to clarify which steps of tutorial could I avoid when update the system