Cool. Thanks for your reply
[automerge]1593314533[/automerge]
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.
No worries, you can always edit your posts afterwards.
Cool. Thanks for your reply
[automerge]1593314533[/automerge]
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.
Is that spoofing related to SMBIOS (Board ID / Serial) key in config.plist?
MBP5,2 mid 2009 17". ROM patched for APFS. Running 10.15.5 (version 15.5.02).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.)
Since I created the Big Sur partition, Bootcamp has disappeared from the boot menu. how can i repair it?
Thanks!
I would never risk installing the developer releases of macOS onto the same physical drive as your current operating systems.
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.
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.)
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.
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.
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.
Thanks! I see there are good options to keep on trying. Will try Catalina as MB7,1 now.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!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.
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.