What method did you use to installBeta4 Everything Ok, with MacPro 2012
For Now,
thanks all brother for tech me until success install
Thank you!You need an already installed BigSur and upgrade (or reinstall) that installation from an USB BigSur Installer to select the "BigSur Data", otherwise only "macOS Installer" is showed.
For BigSur beta4 these still works:
BigSur IvyBridge beta3 prelinkedkernel fix.command.zip
BigSur Penryn beta3 prelinkedkernel fix.command.zip
BigSur beta3 Nvidia Tesla fix.command.zip
step for macPro withWhat method did you use to install
All my Macpro does is boot loop after the files have been put on my ssd via initial install screen
6. close terminal and install macos big sur/Volumes/Image\ Volume/set-vars.sh
10. Done.../Volumes/Image\ Volume/patch-kexts.sh /Volume/NAME OF DISK INSTALLED BIG SUR
Many thanks for the install instruction will try later and report back???step for macPro with
1. Isntall Opencore
2. Creating Bootable DISK with Bigsur Beta 1
3. patch with big-sur-micropatcher-0.0.17 (dont use 0.0.19)
4. Go to system preferences>startup and choose bottable disk instaler big sur
5. on recovery instaler big sur, open terminal and write this
6. close terminal and install macos big sur
7. after finish and boot with big sur, and step choose country , shutdown macpro
8. booting with installer
9. open terminal and patch with this script
10. Done...
.
.
and for update to beta 4, i just download big sur beta 4 and install normal, and after done, just patch again wifi, done
.
.
.
it my step by step
.
CMIW
I wonder, is the update package the same for all machines ? If you simulate another machine with opencore, don't you risk to have a wrong package ?Use this: http://swcdn.apple.com/content/down...m7ounuabziajlktg8nhoptis/InstallAssistant.pkg
OTA updates still don't work on unsupported Mac, unless you spoof to supported BigSur Mac through opencore .
Beta 4 successfully installed on my MBP mid 2012 (MacBookPro9,1) with micropatcher version 0.0.18, WiFi works.
I wonder, is the update package the same for all machines ? If you simulate another machine with opencore, don't you risk to have a wrong package ?
No, I spoke about OTA updates, with softwareupdate panel.This is a 12.3 GB installer package. Looks like all included.
No, I spoke about OTA updates, with softwareupdate panel.
Thank you. So I understand that incremental updates on unsupported machines via opencore are not recommended.For OTA or incremental update they could change a bit, but for full beta installer they are all the same.
Drivers are loaded, you can look in IOreg and kextstat -l, but the system programs also need to use acceleration through Tesla, but perhaps Apple has already removed this feature from the system. However, the latest version of Mojave work fine, and there is still 32-bit support, so we can stop at this system. Catalina works worse, I often see a spinner in it, and sometimes it wakes up in a black screen, I have to do a rough shutdown. I ditched Catalina, so maybe Mojave is the last good system for MacBooks that don't have Metal support, that makes sense to stay on. Alas.Are you sure that Tesla acceleration works? I don't see trasparencies on dock and menu bar... My Mac mini 2010 graphic board Nvidia Geforce 320M is similar (newer) to your Geforce 9400M and we have both a Core 2 Duo... I still not have acceleration.
Thank you. So I understand that incremental updates on unsupported machines via opencore are not recommended.
I have a working beta 1, would a patched beta 4 usb upgrade my existing beta 1. Or would it wipe it and install a fresh copyNot yet, but they already work, for now is advisable using the ASentientBot Hax3 or HaxLib methods and upgrade a previous BigSur installation using the createinstallmedia USB BigSur Installer with https://github.com/barrykn/big-sur-micropatcher .
In few words applying the HaxLib from an USB BigSur Installer environment allows to upgrade a previous BigSur installation, from Catalina desktop you can only install a clean BigSur, probably because of sealed system and snapshot booting, instead both are absent from an USB BigSur Installer booting where you have an unsealed system without snapshot diskXsYs1 volume.
I don’t know what the hell I’m doing wrong but for the last 3-4 days Iv been trying to get sudo mount -uw / to work. None of the patches or methods all me to delete snapshots with ASentientBot method. I check and csrutil and csrutil authentication-root are disabled according to terminal. In the second terminal window I have open it appears it’s mounted as /bs\ 1 but if I run the command it says it failed because it’s read only. And running the command with just /bs says it doesn’t exist.For Penryn Core2Duo Mac non-APFS or legacy USB , I confirm that this method:
BigSur BaseSystem legacy USB fix
still works for a patched USB BigSur beta4 installer and allows to boot, install and upgrade BigSur on legacy USB Mac on internal SATA disk.
(for external USB disk installation to continue stage2 installer use in addition this: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28743252)
Also I add that you can combine the @Barry K. Nathan patches with my fixes, I mean they are compatible, moreover adding this: https://github.com/barrykn/big-sur-micropatcher
to an USB BigSur Installer (BaseSystem legacy USB fixed) allows to use correctly his post install script as for example installing kext making a new snapshot or delete snapshots (so you can install kext with "sudo mount -uw /").
The only difference is that I use prelinkedkernel (kextcache) as default kernelcache booting, while @Barry K. Nathan uses kmutil and BootKernelExtensions.kc .
I'm not sure what's going on then, sorry.Iv tried both. ...../Volumes/bs\ 1 will say it doesn’t exist. And the same drive name without the 1 will say failed read only
Hi jackluke,
One question about your USBOpenCoreAPFSloader4: Do I need any additional kexts/patches to install Mojave/Catalina? I tried to install Mojave off of a bootable USB through the OpenCore loader and when I go to the window to choose the install disk it says "This version 10.14.6 cannot be installed on this computer" or somethingorother.
None of the patches or methods all me to delete snapshots with ASentientBot method. I check and csrutil and csrutil authentication-root are disabled according to terminal.
sudo mount -uw /Volumes/bs