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.

Luki1979

macrumors member
Sep 13, 2019
48
59
I second step by step WIFI guide for 2012 machines. (I have MacBook Air 2012 wifi card in my Hackintosh :)), this is BCM943224PCIEBT2 a very good and tiny card that Apple just blacklisted for no reason. Bluetooth also doesn't work, everything worked in Catalina of course.
 

Stevenjmay

macrumors newbie
Oct 27, 2016
4
8
Edinburgh, Scotland
Installed after a few attempts on an i7 Early 2013 rMBP (MacBook Pro 10,1). Worked eventually as a clean install after trying upgrading an install.

WiFi using the sudo error 66 method.

Thanks to everyone who helped get all our Macs on macOS 11 Big Sur!

Especially the following people
@dosdude1 - Founder of the project
@ASentientBot - Finding a working patch
Unknown - Finding a WiFi patch

Everyone in the Unsupported Mac Community - well done!!!
 

jackluke

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

MathiasVH

macrumors regular
Nov 7, 2009
147
6
With the help of Andrey's guide, I'm now typing on my 2012 MBPr 15", Wifi working and all. Thank you so much. Will be interesting to see how updates play with this workaround
 

hvds

macrumors 6502a
Sep 1, 2017
848
2,019
Switzerland
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.)
MBP5,2 mid 2009 17". ROM patched for APFS. Running 10.15.5 (version 15.5.02).

Unable to get across the "firmware upgrade needed" message when selecting the target disk in BS installer, despite Hex.dylib. Hope I did things correctly so far - maybe the machine is too old, didn't find a success story for those in this thread.
(Except maybe post #989 for a MBP5,3 but there no details are given)

Meanwhile I'm also continuing the prelinkedkernel route with an USB BS installer and OpenCore, but no success yet. Anyway thanks ASentientBot, jackluke, all - this is a great thread with much early success reported.

(MBP5,2 17" mid 2009, 2.8GHz Penryn T9600, Nvidia 9600M GT, 8GB, APFS ROM patch applied. APFS SSD Samsung 860 EVO internal for production / 840 on USB for testing, with Catalina 10.15.5.02 / Big Sur 10.16.0b1 attempt, resp.)
 

Attachments

  • Bildschirmfoto 2020-06-28 um 14.29.23.png
    Bildschirmfoto 2020-06-28 um 14.29.23.png
    29.3 KB · Views: 208
  • Bildschirmfoto 2020-06-28 um 14.31.42.png
    Bildschirmfoto 2020-06-28 um 14.31.42.png
    151.4 KB · Views: 194
  • Bildschirmfoto 2020-06-28 um 14.23.32.png
    Bildschirmfoto 2020-06-28 um 14.23.32.png
    114.1 KB · Views: 191
  • Bildschirmfoto 2020-06-28 um 14.23.10.png
    Bildschirmfoto 2020-06-28 um 14.23.10.png
    114.3 KB · Views: 216
Last edited:

justperry

macrumors G5
Aug 10, 2007
12,627
9,931
I'm a rolling stone.
I would never risk installing the developer releases of macOS onto the same physical drive as your current operating systems.

Depends, it shouldn't be a problem with one partition and a backup, not so much with a bootcamp partition though.

But then again, I never even used bootcamp to install windows, I partitioned the disk myself and installed Windows on it, just for fun, I don't use Windows.

Edited: Grammar
 
Last edited:

jhowarth

macrumors 65816
Jan 13, 2017
1,122
1,500
Depends, it's shouldn't be a problem with one partition and a backup, not so much with a bootcamp partition though.

But then again, I never even used bootcamp to install windows, I partitioned the disk myself and installed Windows on it, just for fun, I don't use Windows.

Especially considering how bootcamp support is receding as a point of interest for Apple. Expect those issues to be at the bottom of their queue. It's 2020 and you still can't select APFS boot volumes in the Startup Disk panel under Windows 10.
 

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,068
MBP5,2 mid 2009 17". ROM patched for APFS. Running 10.15.5 (version 15.5.02).

Unable to get across the "firmware upgrade needed" message when selecting the target disk in BS installer, despite Hex.dylib. Hope I did things correctly so far - maybe the machine is too old, didn't find a success story for those in this thread.
(Except maybe post #989 for a MBP5,3 but there no details are given)

Meanwhile I'm also continuing the prelinkedkernel route with an USB BS installer and OpenCore, but no success yet. Anyway thanks ASentientBot, jackluke, all - this is a great thread with much early success reported.

(MBP5,2 17" mid 2009, 2.8GHz Penryn T9600, Nvidia 9600M GT, 8GB, APFS ROM patch applied. APFS SSD Samsung 860 EVO internal for production / 840 on USB for testing, with Catalina 10.15.5.02 / Big Sur 10.16.0b1 attempt, resp.)

You're right, if you could clone a BigSur installation on external or internal APFS disk, that method would work to boot BigSur on an "El Capitan supported Mac".

While about installing from an USB BigSur Installer the limit are the IOUSB legacy (currently I only added them to a BigSur installation not to the Installer), as also @jhowarth noticed

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.

an "Unsupported HighSierra Mac", even correctly loading the Hax.dylib, get that message of firmware upgrade when selecting the Volume where install BigSur, now, if you can't get a cloned BigSur installation, there are two possible fix to install directly on "El Capitan Mac":

1) @ASentientBot might try to improve his Hax.dylib to ignore that message for non-APFS mac

2) Booting Catalina (or Mojave) through USBOpenCoreAPFSloader3 but spoofing to a supported BigSur Mac (or maybe spoofing to MacBook7,1 that is a supported HighSierra APFS Mac) and then use the "Install macOS Beta.app"

I could provide a config.plist for the second method, but I am really not yet sure how EFI firmware updates are handled from BigSur, while ASentientBot method is more safer.

@hvds try to edit your config.plist spoofing your MBP5,2 as MacBook7,1 and through opencore booting Catalina, insert the Hax.dylib and check if you can install BigSur.
 
Last edited:

abelpinate

macrumors member
Jun 26, 2020
61
32
People, two questions

Im mean, I'm reading this and I don't get apfs patch thing. I'm not trying yet but that patcher it's for those who has the old hfs+?
Because the first thing I did when apfs comes out was out all them on that, even the mechanicals. I didn't care about it. Obviously, I had had a backup.

And the other question:
Anyone have tried Adobe, CAD, Parallels... you know, going beyond the system itself?
I hope be able to run iTunes via Retroactive app :(
 

jhowarth

macrumors 65816
Jan 13, 2017
1,122
1,500
You're right, if you could clone a BigSur installation on external or internal APFS disk, that method would work to boot BigSur on an "El Capitan supported Mac".

While about installing from an USB BigSur Installer the limit are the IOUSB legacy (currently I only added them to a BigSur installation not to the Installer), as also @jhowarth noticed



an "Unsupported HighSierra Mac", even correctly loading the Hax.dylib, get that message of firmware upgrade when selecting the Volume where install BigSur, now, if you can't get a cloned BigSur installation, there are two possible fix to install directly on "El Capitan Mac":

1) @ASentientBot might try to improve his Hax.dylib to ignore that message for non-APFS mac

2) Booting Catalina (or Mojave) through USBOpenCoreAPFSloader3 but spoofing to a supported BigSur Mac (or maybe spoofing to MacBook7,1 that is a supported HighSierra APFS Mac) and then use the "Install macOS Beta.app"

I could provide a config.plist for the second method, but I am really not yet sure how EFI firmware updates are handled from BigSur, while ASentientBot method is more safer.

@hvds try to edit your config.plist spoofing your MBP5,2 as MacBook7,1 and through opencore booting Catalina, insert the Hax.dylib and check if you can install BigSur.

Curiously, the installer currently allows you to select an Extended HFS (Journaled) volume as the target.
 

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,068
Curiously, the installer currently allows you to select an Extended HFS (Journaled) volume as the target.

Maybe it could automatically convert it to apfs during installation, but before trying this on MacPro3,1 I'd advise to make a backup of internal disks or data, then you could try , if succeed I explain how to use LegacyUSBInjector.kext , but first step is to have an APFS BigSur installation on an internal disk.

Currently for non-APFS mac you have to install BigSur on internal disk.
 

jhowarth

macrumors 65816
Jan 13, 2017
1,122
1,500
Maybe it could automatically convert it to apfs during installation, but before trying this on MacPro3,1 I'd advise to make a backup of internal disks or data, then you could try , if succeed I explain how to use LegacyUSBInjector.kext , but first step is to have an APFS BigSur installation on an internal disk.

Currently for non-APFS mac you have to install BigSur on internal disk.

It probably would be wise to also try installing onto an Extended HFS (journaled) formatted external usb drive from a supported machine to see if that completes.
 

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,068
It probably would be wise to also try installing onto an Extended HFS (journaled) formatted external usb drive from a supported machine to see if that completes.

I guess it completes (and automatically convert to an apfs container) because supported machine already have an APFS firmware since HighSierra.

The fact is if only converts the HFS+ volume selected or the whole disk, that's why I'advise a backup first.

As many now macOS beta releases are also an issue for supported mac in some cases.
 

hvds

macrumors 6502a
Sep 1, 2017
848
2,019
Switzerland
You're right, if you could clone a BigSur installation on external or internal APFS disk, that method would work to boot BigSur on an "El Capitan supported Mac".

While about installing from an USB BigSur Installer the limit are the IOUSB legacy (currently I only added them to a BigSur installation not to the Installer), as also @jhowarth noticed



an "Unsupported HighSierra Mac", even correctly loading the Hax.dylib, get that message of firmware upgrade when selecting the Volume where install BigSur, now, if you can't get a cloned BigSur installation, there are two possible fix to install directly on "El Capitan Mac":

1) @ASentientBot might try to improve his Hax.dylib to ignore that message for non-APFS mac

2) Booting Catalina (or Mojave) through USBOpenCoreAPFSloader3 but spoofing to a supported BigSur Mac (or maybe spoofing to MacBook7,1 that is a supported HighSierra APFS Mac) and then use the "Install macOS Beta.app"

I could provide a config.plist for the second method, but I am really not yet sure how EFI firmware updates are handled from BigSur, while ASentientBot method is more safer.

@hvds try to edit your config.plist spoofing your MBP5,2 as MacBook7,1 and through opencore booting Catalina, insert the Hax.dylib and check if you can install BigSur.
Thanks! I see there are good options to keep on trying. Will try Catalina as MB7,1 now.
A BS installation that I could clone isn't within reach.
 

telepati

macrumors 6502
Jan 20, 2009
476
309
SIP disabled and Authenticated Root also disabled but I am still getting error 66. Another weird thing my test drive shows greyed out. When I choose the drive it says disabled and looks Not mounted. But system working. How can I enable this drive? Also, I looked to diskutil list and I saw there is a snapshot it is possible to delete this snapshot drive or is it necessary?

Screen Shot 2020-06-28 at 17.52.54.png
Screen Shot 2020-06-28 at 17.51.53.png
Screen Shot 2020-06-28 at 17.50.23.png
Screen Shot 2020-06-28 at 17.56.16.png

Screen Shot 2020-06-28 at 18.08.31.png
 
Last edited:

hvds

macrumors 6502a
Sep 1, 2017
848
2,019
Switzerland
You're right, if you could clone a BigSur installation on external or internal APFS disk, that method would work to boot BigSur on an "El Capitan supported Mac".

While about installing from an USB BigSur Installer the limit are the IOUSB legacy (currently I only added them to a BigSur installation not to the Installer), as also @jhowarth noticed



an "Unsupported HighSierra Mac", even correctly loading the Hax.dylib, get that message of firmware upgrade when selecting the Volume where install BigSur, now, if you can't get a cloned BigSur installation, there are two possible fix to install directly on "El Capitan Mac":

1) @ASentientBot might try to improve his Hax.dylib to ignore that message for non-APFS mac

2) Booting Catalina (or Mojave) through USBOpenCoreAPFSloader3 but spoofing to a supported BigSur Mac (or maybe spoofing to MacBook7,1 that is a supported HighSierra APFS Mac) and then use the "Install macOS Beta.app"

I could provide a config.plist for the second method, but I am really not yet sure how EFI firmware updates are handled from BigSur, while ASentientBot method is more safer.

@hvds try to edit your config.plist spoofing your MBP5,2 as MacBook7,1 and through opencore booting Catalina, insert the Hax.dylib and check if you can install BigSur.
Success in overcoming the "firmware update" hurdle by spoofing my MBP5,2 as MB7,1!
Installation of BS to my external SSD has begun...
 

Attachments

  • Bildschirmfoto 2020-06-28 um 16.49.36.png
    Bildschirmfoto 2020-06-28 um 16.49.36.png
    34.1 KB · Views: 170
  • Bildschirmfoto 2020-06-28 um 16.42.54.png
    Bildschirmfoto 2020-06-28 um 16.42.54.png
    88.6 KB · Views: 190
  • Bildschirmfoto 2020-06-28 um 16.56.44.png
    Bildschirmfoto 2020-06-28 um 16.56.44.png
    27.2 KB · Views: 189
  • Bildschirmfoto 2020-06-28 um 16.53.47.png
    Bildschirmfoto 2020-06-28 um 16.53.47.png
    102.6 KB · Views: 177
  • Bildschirmfoto 2020-06-28 um 16.55.39.png
    Bildschirmfoto 2020-06-28 um 16.55.39.png
    81.3 KB · Views: 170
  • Bildschirmfoto 2020-06-28 um 17.06.41.png
    Bildschirmfoto 2020-06-28 um 17.06.41.png
    84.1 KB · Views: 190

AlexanderDev.

macrumors newbie
Jun 28, 2020
4
5
Netherlands
hello all, I am new here and have a MacBook Air 2012 5,2. how can I get this machine to Big Sur without the wifi problem? thanks a lot folks! can someone tell me how far you guys have gotten in the past days? I don't think I want to read the whole 43 pages :)
 
Last edited:
  • Like
Reactions: TimothyR734

Minh_Ton

macrumors member
May 15, 2019
64
131
Hue, Vietnam
You're right, if you could clone a BigSur installation on external or internal APFS disk, that method would work to boot BigSur on an "El Capitan supported Mac".

While about installing from an USB BigSur Installer the limit are the IOUSB legacy (currently I only added them to a BigSur installation not to the Installer), as also @jhowarth noticed



an "Unsupported HighSierra Mac", even correctly loading the Hax.dylib, get that message of firmware upgrade when selecting the Volume where install BigSur, now, if you can't get a cloned BigSur installation, there are two possible fix to install directly on "El Capitan Mac":

1) @ASentientBot might try to improve his Hax.dylib to ignore that message for non-APFS mac

2) Booting Catalina (or Mojave) through USBOpenCoreAPFSloader3 but spoofing to a supported BigSur Mac (or maybe spoofing to MacBook7,1 that is a supported HighSierra APFS Mac) and then use the "Install macOS Beta.app"

I could provide a config.plist for the second method, but I am really not yet sure how EFI firmware updates are handled from BigSur, while ASentientBot method is more safer.

@hvds try to edit your config.plist spoofing your MBP5,2 as MacBook7,1 and through opencore booting Catalina, insert the Hax.dylib and check if you can install BigSur.

@jackluke The Apple default Boot Manager freeze when I spoof my Machine to a supported Big Sur machine. Any reasons why does this happen?
 
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.