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.

LuisN

macrumors 6502a
Mar 30, 2013
737
688
Torres Vedras, Portugal
Wow your Retina 2012 still lasts 6 hours?

I swaped my battery at Apple last week, before they ended the repairs for this machine and the battery only lasts 3h30. Will call them about this.

Tks
Bought it 2 months ago from Duracell Direct. I was lucky with this one, the manufacturer date was less than one month before the date of purchase. I hope I'm not wrong but your site maybe this one? https://www.duracelldirect.it/porta...673-batteria-alimentatore-caricabatterie.html that's the easy 2013 battery with is the same that the 2012 retina uses
 
Last edited:
  • Like
Reactions: Bruno Berchielli

jhowarth

macrumors 65816
Jan 13, 2017
1,122
1,500
None of my Macs are supported machines. (I was expecting that Apple would wait another year before dropping the 2012s.) I've been doing these steps on my (2011) MacBookPro8,1 which comes closer to being supported than my MacBook6,1, so it's still an interesting question.

However, my next step (after my next patcher release -- not sure if it'll be tonight, tomorrow, or Saturday) will probably be to look into actually modifying BaseSystem, so that the installer can actually boot with functioning keyboard and trackpad on my MacBook6,1.

Do you have any idea how to use kmutil to rebuild the SystemKernelCollection.kc? I am seeing the same weird behavior that I saw before with chroot when I build either the LegacyUSBInjector.kext or a patched IOUSBHostFamily.kext into BootKernelCollection.kc. The usb external hard drive attached to my MacPro 3,1 seems to fully boot into Big Sur but produces the Bluetooth keyboard dialog saying it can't find a usb keyboard. The fact that it can boot from a usb external seems to contradict this. Also, the same kernels always allow 'cmd+s' and 'exit' to boot into a fully functional Big Sur. It makes me wonder if the OS ever looks at SystemKernelCollection.kc and the fact that it lacks either a LegacyUSBInjector.kext or a patched IOUSBHostFamily.kext could be a problem?

ps Also do you know if it matters that the .elides files in KernelCollections never get regenerated in the produce of rebuilding the kc's?
 

TimothyR734

macrumors 68030
Apr 10, 2018
2,723
2,753
Logsden Oregon
Do you have any idea how to use kmutil to rebuild the SystemKernelCollection.kc? I am seeing the same weird behavior that I saw before with chroot when I build either the LegacyUSBInjector.kext or a patched IOUSBHostFamily.kext into BootKernelCollection.kc. The usb external hard drive attached to my MacPro 3,1 seems to fully boot into Big Sur but produces the Bluetooth keyboard dialog saying it can't find a usb keyboard. The fact that it can boot from a usb external seems to contradict this. Also, the same kernels always allow 'cmd+s' and 'exit' to boot into a fully functional Big Sur. It makes me wonder if the OS ever looks at SystemKernelCollection.kc and the fact that it lacks either a LegacyUSBInjector.kext or a patched IOUSBHostFamily.kext could be a problem?

ps Also do you know if it matters that the .elides files in KernelCollections never get regenerated in the produce of rebuilding the kc's?
If you are placing the LegacyUSBInjector and IOUSBHostFamily kexts in /System/Library/Extensions I wonder if the would help sudo touch /System/Library/Extensions && sudo kextcache -u /
[automerge]1595125242[/automerge]
Totally random question
Is there going to be an easy to use patcher like there has been in the past from @dosdude1 for macOS Big Sur whenever it comes out to the public?
dosdude is working on it no word as to when it will be available
 

Barry K. Nathan

macrumors 6502
Jul 6, 2018
387
1,145
Irvine, CA, USA
If you get a chance, try patching IOUSBHostFamily.kext/Contents/Info.plist and IOUSBHostFamily.kext.orig/Contents/PlugIns/AppleUSBHostPlatformProperties.kext/Contents/Info.plist instead of including LegacyUSBInjector.kext to see if that also produced a bootable kc on unsupported machines that require Legacy USB.
Patching IOUSBHostFamily.kext/Contents/Info.plist alone is sufficient to produce a bootable kc for an unsupported machine that requires Legacy USB. (I tested that earlier.) However, since I have LegacyUSBInjector working now, I think I'm going to stick with that, as long as it seems to work. (In the event that LegacyUSBInjector only works intermittently for people after I add it to my patcher, I'll revisit Info.plist patching.)
[automerge]1595128376[/automerge]
One other question. I have been trying to avoid setting "amfi_get_out_of_my_way=1" in nvram in case it fouls up my patched Catalina drive booting. Have you tried using a com.apple.Boot.plist in /Volumes/Preboot/*/System/Library/CoreServices/ with something like...

Code:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
        <key>Kernel Cache</key>
        <string>System\Library\KernelCollections\BootKernelExtensions.kc</string>
        <key>Kernel Flags</key>
        <string>-no_compat_check amfi_get_out_of_my_way=1</string>
</dict>
</plist>

to pass 'amfi_get_out_of_my_way=1'? I am unclear if the com.apple.Boot.plist works for kc's as well as prelinked kernels and if 'Kernel Cache' should be pointing at BootKernelExtensions.kc or SystemKernelExtensions.kc?
I haven't tried this yet... but it's a good suggestion, and I'll see if I can try it soon. Edit: Yes, com.apple.Boot.plist works for kc's as well. I don't remember now which kernel cache you put the path for, or if you simply omit the "Kernel Cache" part of the file and just do "Kernel Flags".
 
Last edited:

Barry K. Nathan

macrumors 6502
Jul 6, 2018
387
1,145
Irvine, CA, USA
Do you have any idea how to use kmutil to rebuild the SystemKernelCollection.kc? I am seeing the same weird behavior that I saw before with chroot when I build either the LegacyUSBInjector.kext or a patched IOUSBHostFamily.kext into BootKernelCollection.kc. The usb external hard drive attached to my MacPro 3,1 seems to fully boot into Big Sur but produces the Bluetooth keyboard dialog saying it can't find a usb keyboard. The fact that it can boot from a usb external seems to contradict this. Also, the same kernels always allow 'cmd+s' and 'exit' to boot into a fully functional Big Sur. It makes me wonder if the OS ever looks at SystemKernelCollection.kc and the fact that it lacks either a LegacyUSBInjector.kext or a patched IOUSBHostFamily.kext could be a problem?

ps Also do you know if it matters that the .elides files in KernelCollections never get regenerated in the produce of rebuilding the kc's?
Going back to this post, the first chrooted kmutil command builds the BootKernelExtensions.kc and the second one builds the SystemKernelExtensions.kc. The BootKernelExtensions.kc must be built first -- kmutil uses it in the process of building the SystemKernelExtensions.kc.

I'll see later whether LegacyUSBInjector is getting included in SystemKernelExtensions.kc -- but on my MacBook6,1 it seems to work as long as it's included in the BootKernelExtensions.kc, both for booting to single-user mode and for booting straight into full macOS.

It doesn't seem to matter that the .elides are never getting regenerated. (If it later turns out that the elides matter, then that may require using different command line options with kmutil, to let it know what it needs to elide.)
 

Barry K. Nathan

macrumors 6502
Jul 6, 2018
387
1,145
Irvine, CA, USA
If you are placing the LegacyUSBInjector and IOUSBHostFamily kexts in /System/Library/Extensions I wonder if the would help sudo touch /System/Library/Extensions && sudo kextcache -u /
For prelinkedkernels, possibly. For KCs, no. With KCs, kextcache can't do anything on its own and tries to invoke kmutil to do something equivalent -- but we need to invoke kmutil in our own special way for LegacyUSBInjector to work. So kextcache won't be able to do any good and might do some harm.

This may seem like an argument for patching IOUSBHostFamily instead of using LegacyUSBInjector, until you think about it more and realize that any situation where Big Sur is going to automatically rebuild the boot and system KCs is also a situation where some installer or other is going to remove any kexts we add to /System/Library/Extensions anyway, or at least overwrite IOUSBHostFamily. (I just checked IOUSBHostFamily on my High Sierra system and in fact it was updated by the security update a few days ago.)

(And if we put LegacyUSBInjector in /Library/Extensions, it'll go into the auxillary KC, so I think it'll end up loading too late, if it loads at all. Maybe I'll test this at some point.)
 
  • Like
Reactions: TimothyR734

TimothyR734

macrumors 68030
Apr 10, 2018
2,723
2,753
Logsden Oregon
For prelinkedkernels, possibly. For KCs, no. With KCs, kextcache can't do anything on its own and tries to invoke kmutil to do something equivalent -- but we need to invoke kmutil in our own special way for LegacyUSBInjector to work. So kextcache won't be able to do any good and might do some harm.

This may seem like an argument for patching IOUSBHostFamily instead of using LegacyUSBInjector, until you think about it more and realize that any situation where Big Sur is going to automatically rebuild the boot and system KCs is also a situation where some installer or other is going to remove any kexts we add to /System/Library/Extensions anyway, or at least overwrite IOUSBHostFamily. (I just checked IOUSBHostFamily on my High Sierra system and in fact it was updated by the security update a few days ago.)

(And if we put LegacyUSBInjector in /Library/Extensions, it'll go into the auxillary KC, so I think it'll end up loading too late, if it loads at all. Maybe I'll test this at some point.)
sudo mount -uw / ; killall Finder

open /System/Library/Extensions/

replace from Finder in that path the IO80211Family.kext

sudo -s

chmod -R 755 /System/Library/Extensions/

chown -R 0:0 /System/Library/Extensions/

sudo touch /System/Library/Extensions && sudo kextcache -u /

kextcache -i /

kmutil install --update-all

kcditto

reboot
[automerge]1595168704[/automerge]
This is what I used when I replaced IO80211Familykext to get my Wifi working
 

Alex-Microsmeta

macrumors 6502
Jul 14, 2018
376
630
Rome
Interesting posts about METAL APIs and unsupported Mac: https://appleinsider.com/articles/18/06/28/why-macos-mojave-requires-metal----and-deprecates-opengl

https://cdm.link/2018/06/apple-to-open-source-cross-platform-gpu-tech-drop-dead/ @ASentientBot and running Molten over Metal?


Molten DEMO
 
Last edited:

MacPeet

macrumors member
Jul 26, 2018
57
115
germany
Unfortunately I don't understand the many hints and instructions regarding Snaphot / PrelinkedKernel and Kext installation, sorry.
Here the BigSur system was killed several times.

But now with:

sudo touch / System / Library / Extensions && sudo kextcache -u /
kmutil install --update-all
kcditto

... I have sound on the MacPro3.1

MacPro3_1_with_Audio.png

LegacyUSBInjector.kext will probably need an update.
LegacyUSBInjector.kext does not work yet.
Still via CMD + S and exit.
 

Alex-Microsmeta

macrumors 6502
Jul 14, 2018
376
630
Rome
Unfortunately I don't understand the many hints and instructions regarding Snaphot / PrelinkedKernel and Kext installation, sorry.
Here the BigSur system was killed several times.

But now with:

sudo touch / System / Library / Extensions && sudo kextcache -u /
kmutil install --update-all
kcditto

... I have sound on the MacPro3.1

View attachment 935316

LegacyUSBInjector.kext will probably need an update.
LegacyUSBInjector.kext does not work yet.
Still via CMD + S and exit.

You must update also your signature with macOS 11 instead of 10.16 :)
 

TimothyR734

macrumors 68030
Apr 10, 2018
2,723
2,753
Logsden Oregon
Interesting posts about METAL APIs and unsupported Mac: https://appleinsider.com/articles/18/06/28/why-macos-mojave-requires-metal----and-deprecates-opengl

https://cdm.link/2018/06/apple-to-open-source-cross-platform-gpu-tech-drop-dead/ @ASentientBot and running Molten over Metal?


Molten DEMO
I share this with Asentientbot a month ago on discord said he would look into it on Vulkan
 

jhowarth

macrumors 65816
Jan 13, 2017
1,122
1,500
Going back to this post, the first chrooted kmutil command builds the BootKernelExtensions.kc and the second one builds the SystemKernelExtensions.kc. The BootKernelExtensions.kc must be built first -- kmutil uses it in the process of building the SystemKernelExtensions.kc.

I'll see later whether LegacyUSBInjector is getting included in SystemKernelExtensions.kc -- but on my MacBook6,1 it seems to work as long as it's included in the BootKernelExtensions.kc, both for booting to single-user mode and for booting straight into full macOS.

It doesn't seem to matter that the .elides are never getting regenerated. (If it later turns out that the elides matter, then that may require using different command line options with kmutil, to let it know what it needs to elide.)

When I tried the following from a snapshot mounted at /Users/howarth/mntpoint...

Code:
sudo mount -o nobrowse -t apfs /dev/disk7s5 /Volumes/BigSur/Users/howarth/mntpoint
sudo chroot /Volumes/BigSur/Users/howarth/mntpoint kmutil create -n boot \
    --kernel /System/Library/Kernels/kernel \
    --volume-root / \
    --bundle-path /System/Library/Extensions/LegacyUSBInjector.kext \
    --bundle-path /System/Library/Extensions/telemetrap.kext \
    --boot-path /System/Library/KernelCollections/BootKernelExtensions.kc

sudo chroot /Volumes/BigSur/Users/howarth/mntpoint 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
sudo bless --folder /Volumes/BigSur/System/Library/CoreServices --bootefi --create-snapshot

Only BootKernelExtensions.kc showed parrotgeek using grep. As I mentioned before, the resulting BootKernelExtensions.kc can boot into the Big Sur graphical interface from a usb external drive (proving that it has legacy usb support for the boot) but then produces the Bluetooth keyboard dialog indicating that the usb keyboard can't be found. This seems to indicate that the boot process switches over from BootKernelExtensions.kc to SystemKernelExtensions.kc which is missing the LegacyUSBInjector.kext
 

William Rogers

macrumors newbie
Jun 22, 2020
3
5
When the full and finished patcher is going, you shouldn’t need to use a USB although it is usually recommended- if it’s anything like last time it is almost completely automated thanks to everyone here! It’s not ready yet though so just keep checking back here and there will be a message saying the Patcher is ready

Hi guys anyone can anyone make a guide on how to install this on a early 2011 13" Macbook Pro just on the mac itself without a usb drive as my usb ports dont work
 
  • Like
Reactions: TimothyR734

timmykm721

macrumors newbie
Feb 17, 2020
9
5
On my BigSur beta 2 (sealed snapshot), I tried to use this @ASentientBot method to delete the annoying BigSur snapshots (the purpose is to use "sudo mount -uw /" in normal booting)

csrutil authenticated-root already disabled , tried either from a BigSur recovery or normal booting:

Code:
cd /S*/L*/F*/apfs.fs/C*/R*/

./apfs_systemsnapshot -v "/Volumes/mountpoint/BigSur/" -r ""

-r "" should tag no snapshots booting directly the unsealed BigSur System

But I can't tag it, system says:

Attempting tagging of snapshot on volume: /Volumes/BigSur
fs_snapshot_root: Operation not permitted
fs_snapshot_root failed with /Volumes/BigSur

While from BigSur beta 1 (I can use "sudo mount -uw /"), I am able to remove snapshots in this way:
Code:
tmutil listlocalsnapshots /Volumes/BigSur/

tmutil deleteLocalSnapshots /Volumes/BigSur/ snapshotdatetime
If I opt for DoNotSeal Yes. I also get operation not permitted. But, if the system volume is sealed, no issue tagging and deleting snapshot.
 

Arnomacmini

macrumors newbie
Oct 19, 2019
28
26
In few words to skip the "non-metal GPU" BigSur Finder login crash you need to replace this file: BigSur com.apple.universalaccess.plist.zip
in this path: /Volumes/BigSur Data/Users/yourusername/Library/Preferences/

Try this attached from Catalina or another macOS with APFS support, it should work.

@RogueB you need the same fix for non-Metal GPU and also try this:
https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28643133

Thanks it works , i succeed log in
But no sound ( HDMI sound doesn’t appear)
no Wifi
Lot of Lag and much noise of cooler

any idea ?
thank you very much for your Help !
 
Last edited:

Dave1423

macrumors member
Jul 19, 2020
93
32
would i be able to install this on a late 2008 15” macbook pro and how well does this run on 4GB of ram without a ssd and does anyone have a guide for this or can make one
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.