Yes, you confirmed my doubt about selecting the right source. I will retry with a smaller volume.
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
You probably meant a bigger target disk.
Edit: You need to copy disk0 with all its partitions.
Does anyone have a recommendation of a Wifi/BT card that I can upgrade/swap to on my non-retina 2012 MBP that would worth with Big Sur?
Excuse me for butting into a thread I haven't been following—does this mean you can actually make live changes to the system volume without rebooting? I would very much like a way to do that in general, on supported Macs.
this worked for my MBP2012
Some people were talking about turning off your mac at stage 3 of the installer to prevent the installer from sealing your APFS volume, allowing it to boot from the live volume instead. I just tested this on my 2012 Mac mini and it does indeed work. I can now just mount -uw / without issues.
So basically when you start the installation of Big Sur it copies over the data to the APFS Volume (stage 1), then reboots and installs macOS (stage 2). Then it reboots again but this time you'll hold cmd+v to enter verbose mode and let it run until you see a line saying something like
Code:
executing /System/Library/Filesystems/apfs.fs/Contents/Resources/apfs_sealvolumeOn which point you'll turn off your mac. Then turn your mac back on holding the option/alt key to get into the boot menu and select your Big Sur volume.
this worked for my MBP2012
A query. Why do you want to change the WiFi card in a 2012 MBP does not retina? It works perfectly for me in both beta 1 and beta 2 thanks to the help of @jackluke
How to even install beta 1? I have the same model as yours
Neat, thanks! I do hope there's eventually a better way to do this than interrupting the installer, that feels quite tenuous!
Last edited:
There are some other ways, this one for instance but none of them worked for me.
Edit: haha I just realized you've already seen that method
Any one know why when entering sudo mount -uw / why I get an error saying volume could not be mounted: Operation not permitted and failed with 77? This is also for a mid 2012 non retina macbook pro.
Yes—that would be because you are using the root snapshot thingamajig and would need to go through a big rigamarrole in order to edit the snapshot. If you want to just boot from the root volume instead, see posts above.
ddrescue is even better (but only really necessary if the disk has a bad block).
Hello everybody, I'm with Catalina 15.5 on Macmini 5.1 (mi-2011)
Could please someone help me to install Big sur .
I did read the posts but i can't find the good solution ?
Thanks a lot.
Could please someone help me to install Big sur .
I did read the posts but i can't find the good solution ?
Thanks a lot.
This turned out to be the secret to getting LegacyUSBInjector.kext to work! (I have not yet gotten around to trying to change the BaseSystem.dmg yet -- this is in the context of a Big Sur installation on an external USB SSD, where I'm installing Big Sur, LegacyUSBInjector.kext, other kext patches, removing the telemetry plugin on a MacBookPro8,1 then booting the drive on my MacBook6,1.)
But, the weird thing is that now my MacBookPro8,1 and MacBook6,1 are booting from different APFS snapshots on the same disk. The MacBookPro8,1 is booting from the APFS snapshot that it's supposed to, but the MacBook6,1 is booting from the snapshot that the Big Sur installer created, not any of the newer snapshots. I discovered this because the MacBook6,1 was having the usual kernel panic from the telemetry plugin, and I could see in single-user mode that the plugin was still there, but when I booted the same disk in single-user mode on the MBP8,1 I saw that the plugin was renamed as I had intended -- and both Macs were booting from snapshots! (It's not a case of one Mac booting from a snapshot and the other Mac booting straight from the APFS volume.) But it turns out they're booting from snapshots with different xids (this is visible in the boot messages). This is with beta 2, by the way.
I just finished making a dd clone of the external SSD where this is happening (I've been using dd to clone macOS betas since High Sierra). I'll investigate the situation a bit more, but I just wanted to alert everyone that this is possible. (Has anyone else had this happen yet?)
macOS 10.15.6 doesn't fix Disk Utility about BS partitions ? Now, even worse, after most cloning trials, instead of Update partition + Big Sur - Data, on Internal SSD, toghether with Catalina it shows only 1 ASR container that cannot be fixed. Luckily BS beta 2 still loads flawlessy ? I'll wait beta 3 to reinstall BS in a working container.
No, a smaller dev source, because with my vintage Mac mini 2010, Big Sur gold master will be out before finished cloning 500 GB SSD with dd ?
It's not a secret, you just need to use the prelinkedkernel (also the apple stock one if you prefer) as main Preboot BigSur kernelcache: com.apple.Boot.plist
this "prelinkedkernel method" is mandatory if you want to build a legacy USB prelinkedkernel, otherwise
kextcache delegates its tasks to kmutil that rebuild only the BootKernelExtensions (that I can't make work with LegacyUSBInjector).To make LegacyUSBInjector.kext to work with prelinkedkernel you need to add it to BigSur SLE (you need an unsealed system with no snapshot), but using only this will boot legacy USB but with "CMD+S" and "exit".
I instead discovered that prelinking it together with this (that should provide also SSE4.2 and AVX emulation):
https://forums.macrumors.com/thread...emulation-to-enable-amd-metal-driver.2206682/
allows that "BigSur single user mode booting delay" I needed to detect correctly
HID: Legacy Shim 2 for any non-APFS or legacy USB Penryn Core2Duo mac .I haven't made yet a new "beta2 prelinkedkernel" because BigSur kernel is still version 20.0.0 and I assume all the prelinked kext are also almost identical to the beta1 .
Happy to know that @dosdude1 was in pause for 15 days (hoping for holidays) . He really misses here. Catalina Patcher 1.4.4 still working perfectly with 10.15.6 (updated directly on Cat SSD) is a software masterpiece ?
Last edited:
Let me rephrase it: What testheit posted was, for me, the secret to getting kmutil to build a BootKernelExtensions.kc with a working LegacyUSBInjector.
Actually, there are two other catches, I remember now:
1. kmutil can build both the BootKernelExtensions.kc and the SystemKernelExtensions.kc in one command, but if you do that, LegacyUSBInjector won't work. You have to build the two of them with two different commands.
2. You have to use a chroot. I ran into some weird error with kmutil that magically disappeared once I started using a chroot.
The code that I have that does it is something like this ("$VOLUME" is the path to the Big Sur system volume):
Code:
chroot "$VOLUME" kmutil create -n boot \
--kernel /System/Library/Kernels/kernel \
--volume-root / \
--bundle-path /System/Library/Extensions/LegacyUSBInjector.kext \
--boot-path /System/Library/KernelCollections/BootKernelExtensions.kc
chroot "$VOLUME" kmutil create -n sys \
--kernel /System/Library/Kernels/kernel \
--volume-root / \
--system-path /System/Library/KernelCollections/SystemKernelExtensions.kc \
--boot-path /System/Library/KernelCollections/BootKernelExtensions.kc
"$VOLUME/usr/sbin/kcditto"
bless --folder "$VOLUME"/System/Library/CoreServices --bootefi --create-snapshotBy the way, you can run
strings on the generated BootKernelExtensions.kc and look for "com.parrotgeek" and see that the LegacyUSBInjector is there (or see that it's not there if something went wrong).This should happen also if you have SIP enabled, disable it.