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.

Payne Mononymous Bachman

macrumors member
Jun 22, 2020
97
181
Sounds good.
[automerge]1593297233[/automerge]
I wonder since Apple is switching to their own processors if they will be starting to ditch AMD Graphics in their Mac Pros ,iMacs and their laptops?
[automerge]1593297339[/automerge]
Still runs well, I also have a nMBP from the same year, It was available for purchase until November 2016, I actually thought it would still be supported at least for one more year, guess I was wrong.
I also just got a mid 2012 Macbook pro and 2013 iMac. I also thought that they would at least be supported a few more years. It a shame that they are being not supported anymore since they are still capable machines.
 

Payne Mononymous Bachman

macrumors member
Jun 22, 2020
97
181
[automerge]1593297339[/automerge]

I also just got a mid 2012 Macbook pro and 2013 iMac. I also thought that they would at least be supported a few more years. It a shame that they are being not supported anymore since they are still capable machines.

Also I find it interesting that they still sold the 2012 while the 2015 was being sold. So in my mind the 2012 should get the same type of support that a 2015 should get.
 

vobele

macrumors newbie
Jun 27, 2020
9
15
THANK YOU ALL, this thread is so awesome! By following the instructions here I managed to not only install Big Sur on my (unsupported:mad:) Early 2013 MacBook Pro Retina 15, but also getting WiFi working. I can confirm Big Sur is working absolutely flawless on this machine :p
Bildschirmfoto 2020-06-28 um 00.23.17.png
 

justperry

macrumors G5
Aug 10, 2007
12,631
9,967
I'm a rolling stone.
[automerge]1593297339[/automerge]

I also just got a mid 2012 Macbook pro and 2013 iMac. I also thought that they would at least be supported a few more years. It a shame that they are being not supported anymore since they are still capable machines.

Well, I will be Ok with this "hack" to install BS, that at least takes me forward to not buying another Intel Mac before the transition to arm, I will be buying a new one as soon as there's an arm proc inside.

And then this, no big deal but you quoted your own post, you might take the time to edit it. :)

Also I find it interesting that they still sold the 2012 while the 2015 was being sold. So in my mind the 2012 should get the same type of support that a 2015 should get.

You quoted your own post again. ;)



THANK YOU ALL, this thread is so awesome! By following the instructions here I managed to not only install Big Sur on my (unsupported:mad:) Early 2013 MacBook Pro Retina 15, but also getting WiFi working. I can confirm Big Sur is working absolutely flawless on this machine :p
View attachment 928527

How did you manage to get Wifi working?
 

Barry K. Nathan

macrumors 6502
Jul 6, 2018
387
1,145
Irvine, CA, USA
All right, hey everyone, I tried using the Hax dylib method on my 2012 13" rMBP which is supported but not officially.
I get the following error:

The operation couldn’t be completed. (BIErrorDomain error 3.)

Can anyone help me figure this one out? I'm pretty sure I did all of the steps okay
"BIErrorDomain error 3" is a definitive indication that Hax.dylib (or Hax2.app/Hax2Lib.dylib, for people trying that instead) did not do its thing.
 

jhowarth

macrumors 65816
Jan 13, 2017
1,122
1,500
To insert properly the Hax.dylib you should copy it to the ~/ (home folder root as ~/Hax.dylib) and then run from terminal: launchctl setenv DYLD_INSERT_LIBRARIES $PWD/Hax.dylib

but first you should set in nvram boot-args="-no_compat_check amfi_get_out_of_my_way=1" from a recovery environment or USB Catalina patcher and "csrutil disable".

I am still rather puzzled how you ever managed to successfully run the Big Sur Beta installer on a MacPro 3,1 with or without the ROM patch applied. In either case, it should have prevented you from selecting an APFS target volume due to the firmware check failing in /Applications/Install macOS Beta.app/Contents/MacOS/InstallAssistant.
 

Barry K. Nathan

macrumors 6502
Jul 6, 2018
387
1,145
Irvine, CA, USA
It looks like the InstallAssistant binary will need a binary patch to disable the firmware check as the error message "Your Mac needs a firmware update in order to install to this volume. Please select a Mac OS Extended (Journaled) volume instead." occurs in the associated Frameworks/OSInstallerSetup.framework/Versions/A/Frameworks/OSInstallerSetupInternal.framework/Resources/en.lproj/OSISError_Server.strings file.
I don't think a binary patch will be needed. After all, the whole idea of @ASentientBot's Hax.dylib/Hax2Lib.dylib is to patch the installer as it runs, LD_PRELOAD-style. (Unfortunately I doubt I'll have a chance to look into doing this anytime soon, though. My needs right now involve Macs that are supported by High Sierra.)
 
Last edited:

quaccOS

macrumors regular
Apr 19, 2020
126
208
@ ASentientBot are you guys in high school or college? I know it may be a weird question. Just wondering because I just graduated from college.
Schools closed in March, and I was in my final year of secondary (high school). We would have set the Leaving Certificate Examination to determine our university place (no GPA system here, just one set of finals). That didn’t happen…so the teachers are ‘predicting’ our grades. I’m pretty much in limbo until September :)
 

quaccOS

macrumors regular
Apr 19, 2020
126
208
I already included in my usbopencore setup a similar apple startup gui (but I prefer to use a text menu to differentiate), to enable it, from Catalina (or BigSur) open terminal and type:
Code:
diskutil list

locate your USB external EFI on diskX (where you installed usbopencore)

sudo -s
diskutil mount diskXsY

cd /Volumes/EFI/EFI/OC/Drivers/
mv OpenCanopy.efi OpenCanopy2.efi

diskutil unmount EFI


About the Wifi and Sound kext, those kmutil output are normal but they are valid for BootKernelExtensions.kc, instead for usbopencore you need to rebuild the "kextcache" for prelinkedkernel, this currently can only been done from BigSur normal booting, but after you replaced those kext from USB BigSur recovery, you could try to boot from BigSur (normal booting) terminal: sudo kextcache -i /
OpenCanopy2.efi.jpg
I prefer the text menu too for differentiating. I like the dark background especially, but I doubt it is possible to modify Apple's default firmware on our Macs to make a fancy Apple GUI boot picker

I think kextcache was rebuilt for prelinkedkernel but it's not working yet.
The WiFi & sound kexts must have loaded, so maybe the errors in the Terminal output have some clues?
I will copy-paste my entire recovery & open Terminal output…but it's very long, so only read if you want
Bash:
-bash-3.2# cd /Volumes/Big\ Sur\ -\ Data/Users/home/Downloads; ls
AppleHDA.kext    IO80211Family.kext
-bash-3.2# mv *.kext /Volumes/Big\ Sur/System/Library
-bash-3.2# chmod -R 755 Extensions; chown -R 0:0 Extensions
-bash-3.2# kextcache -i /Volumes/Big\ Sur/; kmutil install --update-all; kcditto

root@MBP71 ~ # kextcache -i /; kmutil install --update-all; kcditto
Ignoring CoreStorageLVF UUID Request for apfs snapshot: /
Can't read info dictionary for /Library/Apple/System/Library/Extensions/AppleMobileDevice.kext: IOCFUnserialize: syntax error near line 1.
Can't read info dictionary for /Library/Apple/System/Library/Extensions/AppleMobileDevice.kext: IOCFUnserialize: syntax error near line 1.
Can't read info dictionary for /Library/Apple/System/Library/Extensions/AppleMobileDevice.kext: IOCFUnserialize: syntax error near line 1.
Can't read info dictionary for /Library/Apple/System/Library/Extensions/AppleMobileDevice.kext: IOCFUnserialize: syntax error near line 1.
Can't read info dictionary for /Library/Apple/System/Library/Extensions/AppleMobileDevice.kext: IOCFUnserialize: syntax error near line 1.
checking collections...
updated extension 'com.Accusys.driver.Acxxx' found in collection 'auxiliary kext collection' (mach-o UUID changed from <unknown> to A445E0EC-4DDC-30AF-BEE0-25FF063C9640)
updated extension 'com.softraid.driver.SoftRAID' found in collection 'auxiliary kext collection' (mach-o UUID changed from <unknown> to 58844C00-8FB7-3DE4-84CC-F023DAD09DC6)
updated extension 'com.ATTO.driver.ATTOCelerityFC8' found in collection 'auxiliary kext collection' (mach-o UUID changed from <unknown> to C88E0E7A-8F11-57D8-10EB-D83BD64E529E)
updated extension 'com.ATTO.driver.ATTOExpressSASRAID2' found in collection 'auxiliary kext collection' (mach-o UUID changed from <unknown> to 09E2D3CD-9959-56F9-15D9-620C7B7CCCE1)
updated extension 'com.highpoint-tech.kext.HighPointRR' found in collection 'auxiliary kext collection' (mach-o UUID changed from <unknown> to A0C06D9F-5C9F-39E2-BA85-8720A8FF5BA6)
updated extension 'com.ATTO.driver.ATTOExpressSASHBA2' found in collection 'auxiliary kext collection' (mach-o UUID changed from <unknown> to 6B01EE8B-9786-614A-7E03-D14C16EE2646)
updated extension 'com.Areca.ArcMSR' found in collection 'auxiliary kext collection' (mach-o UUID changed from <unknown> to 05FBCBFC-1AE6-3BF9-BD0F-7655CC822E34)
updated extension 'com.highpoint-tech.kext.HighPointIOP' found in collection 'auxiliary kext collection' (mach-o UUID changed from <unknown> to 2795A2E4-27BC-333B-BE4D-EA04D25270EE)
updated extension 'com.promise.driver.stex' found in collection 'auxiliary kext collection' (mach-o UUID changed from <unknown> to AE253556-66D8-38D2-B9D1-179B78F29153)
updated extension 'com.CalDigit.driver.HDPro' found in collection 'auxiliary kext collection' (mach-o UUID changed from <unknown> to 7AB5C9DC-46D9-2868-5660-CE03CD4950C7)
updated extension 'com.apple.driver.LuaHardwareAccess' found in collection 'system kext collection' (mach-o UUID changed from <unknown> to 5022EF17-5F63-318B-9EC5-5ECE5B640929)
rebuilding release collections: boot, system
rebuilding release collections:
    boot kernel collection
    system kext collection
failed to build release collection:
    Invalid argument: Writing boot kernel collection failed.
failed to build any collections (expected: 1)
rebuilding local auxiliary collection
Error: Error Domain=NSCocoaErrorDomain Code=4097 "connection to service on pid 0 named com.apple.KernelExtensionServer" UserInfo={NSDebugDescription=connection to service on pid 0 named com.apple.KernelExtensionServer}
Copying deferred prelinked kernels in /...
Ignoring CoreStorageLVF UUID Request for apfs snapshot: /
/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/kext_tools/kext_tools-685/kc_staging.m.279: Encountered error while inspecting path: Error Domain=NSCocoaErrorDomain Code=260 "The folder “PrelinkedKernels” doesn’t exist." UserInfo={NSFilePath=/Library/Apple/System/Library/PrelinkedKernels, NSUserStringVariant=(
    Folder
), NSUnderlyingError=0x7fca6a505ae0 {Error Domain=NSOSStatusErrorDomain Code=-43 "fnfErr: File not found"}}
/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/kext_tools/kext_tools-685/kc_staging.m.279: Encountered error while inspecting path: Error Domain=NSCocoaErrorDomain Code=260 "The folder “PrelinkedKernels” doesn’t exist." UserInfo={NSFilePath=/Library/Apple/System/Library/PrelinkedKernels, NSUserStringVariant=(
    Folder
), NSUnderlyingError=0x7fca6a508500 {Error Domain=NSOSStatusErrorDomain Code=-43 "fnfErr: File not found"}}
Copying KCs in /...
Ignoring CoreStorageLVF UUID Request for apfs snapshot: /
System Volume UUID: E0FB33C6-05B6-42FC-A08D-0E552D1DEB9E
Volume Group UUID: 2B9C924F-9B05-4337-9383-0C2057994587
Preboot disk: /dev/disk2s2
Preboot volume: /System/Volumes/Preboot
Copying: /System/Library/KernelCollections/BootKernelExtensions.kc.elides -> /System/Volumes/Preboot/2B9C924F-9B05-4337-9383-0C2057994587/boot/System/Library/KernelCollections
Copying: /System/Library/KernelCollections/BootKernelExtensions.kc -> /System/Volumes/Preboot/2B9C924F-9B05-4337-9383-0C2057994587/boot/System/Library/KernelCollections
Copying: /System/Library/PrelinkedKernels/immutablekernel -> /System/Volumes/Preboot/2B9C924F-9B05-4337-9383-0C2057994587/System/Library/PrelinkedKernels
Copying: /System/Library/PrelinkedKernels/prelinkedkernel -> /System/Volumes/Preboot/2B9C924F-9B05-4337-9383-0C2057994587/System/Library/PrelinkedKernels
 

Macbookprodude

Suspended
Jan 1, 2018
3,306
898
Yes, everything works "out of the box" except WiFi. But it's possible to make it works, just in a little tricky way. I'm trying right now :)

try the wifi kextfrom Catalina
[automerge]1593308335[/automerge]
I think the 2011 however, should be retired.. it was a good run for those - sorry, but 2012 is where it’s at - out of the box.
 

TimothyR734

macrumors 68030
Apr 10, 2018
2,723
2,753
Logsden Oregon
Which usage of csr-active-config correct for OpenCore?

csr-active-config=67080000
csr-active-config=w0800000
[automerge]1593313525[/automerge]
  • macOS Big Sur now adds root auth to SIP so the final value now is 0x867 or 67080000 hex-swapped
 

Payne Mononymous Bachman

macrumors member
Jun 22, 2020
97
181
Schools closed in March, and I was in my final year of secondary (high school). We would have set the Leaving Certificate Examination to determine our university place (no GPA system here, just one set of finals). That didn’t happen…so the teachers are ‘predicting’ our grades. I’m pretty much in limbo until September :)
Cool. Thanks for your reply
[automerge]1593314533[/automerge]
Well, I will be Ok with this "hack" to install BS, that at least takes me forward to not buying another Intel Mac before the transition to arm, I will be buying a new one as soon as there's an arm proc inside.

And then this, no big deal but you quoted your own post, you might take the time to edit it. :)



You quoted your own post again. ;)





How did you manage to get Wifi working?
Thanks for letting me know. I didn't mean to quote my own post twice. I am still new to Mac Rumors and learning how to use it.
 

ASentientBot

macrumors 6502a
Jun 27, 2018
863
3,421
SkyLight.framework
Think I've gotten prelinkedkernel (or whatever it's called now) rebuilding working from single-user mode. Steps are as follows:
Code:
# mount the system and data volumes
mount -uw /
/System/Library/Filesystems/apfs.fs/Contents/Resources/apfs_boot_util 1
/System/Library/Filesystems/apfs.fs/Contents/Resources/apfs_boot_util 2

# fix permissions
chown -R root:wheel /System/Library/Extensions
chmod -R 755 /System/Library/Extensions

# update caches
kmutil install --update-all

# copy into place
kcditto

The main addition is, of course, the apfs_boot_util command. That replaces mount -uw /System/Volumes/Data which no longer works for me.

There is also an error talking to a service in the kmutil step, but it doesn't seem to impede this from working. This all requires snapshots to be disabled, of course.

Hope this helps!
 

TimothyR734

macrumors 68030
Apr 10, 2018
2,723
2,753
Logsden Oregon
[automerge]1593319646[/automerge]
 

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,068
Which usage of csr-active-config correct for OpenCore?

csr-active-config=67080000
csr-active-config=w0800000

For my USBOpenCoreAPFSloader3 customized setup, I use this:

csr-active-config=77000000
[automerge]1593327147[/automerge]
I prefer the text menu too for differentiating. I like the dark background especially, but I doubt it is possible to modify Apple's default firmware on our Macs to make a fancy Apple GUI boot picker

I think kextcache was rebuilt for prelinkedkernel but it's not working yet.
The WiFi & sound kexts must have loaded, so maybe the errors in the Terminal output have some clues?
I will copy-paste my entire recovery & open Terminal output.

It is possible to change the VolumeIcons but they need a 32 bit icon format for apple startup manager, for Catalina you could try this: https://forums.macrumors.com/threads/macos-10-15-catalina-on-unsupported-macs.2183772/post-27499212

run the script directly from Catalina (and its Downloads folder).

About BigSur, to rebuild properly the kextcache try with this new @ASentientBot method from single user mode, this method requires snapshots disabled, so I guess you should first disable or delete the BigSur snapshots from its USB BigSur Installer or using my USBOpenCore booting the Recovery 10.16 (dmg)

Once you disabled the snapshots, this I write is for those who used my prelinkedkernel method with usbopencore, so boot using opencore then from its text menu use CMD+S (without holding) and select with keyboard the BigSur Label:

Code:
mount -uw /

cd /System/Library/Filesystems/apfs.fs/Contents/Resources/

./apfs_boot_util 1

./apfs_boot_util 2

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

chmod -R 755 /System/Library/Extensions/

kextcache -i /

kcditto

reboot

after kextcache -i /
this will takes some minutes and during it you will encounter many "kext with invalid signature: allowed" but this is completely normal to make a BigSur prelinkedkernel.
 
Last edited:

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,068
It looks like the InstallAssistant binary will need a binary patch to disable the firmware check as the error message "Your Mac needs a firmware update in order to install to this volume. Please select a Mac OS Extended (Journaled) volume instead." occurs in the associated Frameworks/OSInstallerSetup.framework/Versions/A/Frameworks/OSInstallerSetupInternal.framework/Resources/en.lproj/OSISError_Server.strings file.

I am still rather puzzled how you ever managed to successfully run the Big Sur Beta installer on a MacPro 3,1 with or without the ROM patch applied. In either case, it should have prevented you from selecting an APFS target volume due to the firmware check failing in /Applications/Install macOS Beta.app/Contents/MacOS/InstallAssistant.

Infact, as I wrote you need or to clone first a BigSur install, or you need to use the USBOpenCoreAPFSloader3 spoofing to a supported BigSur Mac, make an external usbopencore, and then I can send a spoofing modified config.plist for your machine, because currently the usbopencore doesn't spoof to any supported mac.

This should work without editing any binary or .strings file .
 

Luki1979

macrumors member
Sep 13, 2019
48
59
Guys please tell me how to go around this:
bash-3.2# mount -uw /
mount_apfs: volume could not be mounted: Permission denied
mount: / failed with 66
 
  • Like
Reactions: TimothyR734

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,068

Luki1979

macrumors member
Sep 13, 2019
48
59
You should try this: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28603788

You need to make with createinstallmedia an USB BigSur Installer and boot from there recovery environment.

Deleting BigSur snapshots will allow to use "sudo mount -uw /" from BigSur normal booting.

Thank you, yeah you have to do it from recovery as if you do this command from system it throws an error:
diskutil mount disk1s5
/S*/L*/F*/apfs.fs/C*/R*/apfs_systemsnapshot -v "/Volumes/OSX" -r ""

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

Minh_Ton

macrumors member
May 15, 2019
64
131
Hue, Vietnam
Infact, as I wrote you need or to clone first a BigSur install, or you need to use the USBOpenCoreAPFSloader3 spoofing to a supported BigSur Mac, make an external usbopencore, and then I can send a spoofing modified config.plist for your machine, because currently the usbopencore doesn't spoof to any supported mac.

This should work without editing any binary or .strings file .

Is that spoofing related to SMBIOS (Board ID / Serial) key in config.plist?
 
Last edited:
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.