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.
MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
The keys were unchanged but the key values in the right column (last 2 rows) were 0. Apparently those depend on the NVRAM MLB and ROM values. I was prompted to login again to my account. Obviously it triggers a change in Apple servers. The keys on the left and right in Hackintool should remain the same.
I was of course referring to both the keys and their values. Besides, I checked again: still unchanged. Our spoofing approaches must be different.
Can you get that Big Sur beta 3 incremental update only using the "VMM flag" (without the iMacPro1,1 SMBIOS) ?
I mean does the "VMM flag" is still a valid method to use on BigSur or only for Catalina ?
TBH, I really don't know. I just assume it won't work. And either keep the current hybrid config for Big Sur testing. Or use a complete iMac Pro spoofing for Big Sur installation / update.
What I don't want is that if VMM just half working (e.g. macOS can detect an update, but the update stuck at the middle of installation). Since the full installer doesn't work with VMM only (at least true on beta 1). It really means something, therefore, I always use complete SMBIOS for installation / update (just in case).
During Big Sur update installation, after the "29 minutes remaining" stage2 installer, do you encountered the big apple loading bar with grey screen (typically as the EFI SMC firmware update) ?
First I used full SMBIOS spoofing for the upgrade after which switched back to board-id only spoofing and later to this one (the one you linked):
See here update NVRAM is true but PlatformNVram is not defined. Here is a one liner to quickly check most of the parameters needed for iMessage:
Code:
DmiSystemSerial="$(ioreg -c IOPlatformExpertDevice -d 2 | awk -F\" '/IOPlatformSerialNumber/{print $(NF-1)}')"; echo DmiSystemSerial="'$DmiSystemSerial'" > macos_vm_vars_file &&
HOST_ID=$(ioreg -p IODeviceTree -r -n / -d 1 | grep board-id);HOST_ID=${HOST_ID##*<\"};HOST_ID=${HOST_ID%%\">}; echo DmiBoardProduct="'$HOST_ID'" >> macos_vm_vars_file &&
SYSTEM_UUID="$(ioreg -l -p IODeviceTree | awk -F"\<|>" '/"system-id"/{print $(NF-1)}')"; Echo SYSTEM_UUID="'$SYSTEM_UUID'" >> macos_vm_vars_file &&
DmiSystemFamily="$(system_profiler SPHardwareDataType | awk -F": " ' /Model Name/ { print $2 } ')"; echo DmiSystemFamily="'$DmiSystemFamily'" >> macos_vm_vars_file &&
DmiSystemProduct="$(system_profiler SPHardwareDataType | awk -F": " ' /Model Identifier/ { print $2 } ')"; echo DmiSystemProduct="'$DmiSystemProduct'" >> macos_vm_vars_file&&
DmiSystemUuid="$(system_profiler SPHardwareDataType | awk -F": " ' /Hardware UUID/ { print $2 } ')"; echo DmiSystemUuid="'$DmiSystemUuid'" >> macos_vm_vars_file &&
DmiBIOSVersion="$(system_profiler SPHardwareDataType | awk -F": " ' /Boot ROM Version/ { print $2 } ')"; echo DmiBIOSVersion="'$DmiBIOSVersion'" >> macos_vm_vars_file &&
DmiBoardSerial="$(nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB | awk -F" " ' /MLB/ { print $2 } ')"; echo DmiBoardSerial="'$DmiBoardSerial'" >> macos_vm_vars_file &&
ROM="$(nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM | awk -F" " ' /ROM/ { print $2 } ')"; echo ROM="'$ROM'" >> macos_vm_vars_file &&
MLB="$(nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB | awk -F" " ' /MLB/ { print $2 } ')"; echo MLB="'$MLB'" >> macos_vm_vars_fileJust cd to a working directory, copy/paste in terminal+ ENTER. Inspect the created file
macos_vm_vars_file with a text editor. I created this originally for the Vbox OS X iMessage fix.with full SMBIOS spoofing try :
BIOSVersion: "1539.0.0.0.1"
BIOSReleaseDate: "07/12/2020"
OpenCorePkg/AppleModels/DataBase/iMacPro/IMP11.yaml at master · acidanthera/OpenCorePkg
OpenCore bootloader. Contribute to acidanthera/OpenCorePkg development by creating an account on GitHub.
github.com
Attachments
Last edited:
No sign of firmware update for me.
I did see a big Apple logo with loading bar (double normal size on my non HiDPI 3840x1080 monitor), but that often happen during MacOS installation (Catalina / Bug Sur) regardless my OpenCore display scale setting. Also, the loading bar is the white colour, not grey. Therefore, I don’t consider that’s a sign of firmware update.
IMO, it's either use automatic spoofing, then only fill in the MLB, ROM, System Product Name, Serial number, and UUID in the Generic section.First I used full SMBIOS spoofing for the upgrade after which switched back to board-id only spoofing and later to this one (the one you linked):
View attachment 936989
See here update NVRAM is true but PlatformNVram is not defined. Here is a one liner to quickly check most of the parameters needed for iMessage:
Code:DmiSystemSerial="$(ioreg -c IOPlatformExpertDevice -d 2 | awk -F\" '/IOPlatformSerialNumber/{print $(NF-1)}')"; echo DmiSystemSerial="'$DmiSystemSerial'" > macos_vm_vars_file && HOST_ID=$(ioreg -p IODeviceTree -r -n / -d 1 | grep board-id);HOST_ID=${HOST_ID##*<\"};HOST_ID=${HOST_ID%%\">}; echo DmiBoardProduct="'$HOST_ID'" >> macos_vm_vars_file && SYSTEM_UUID="$(ioreg -l -p IODeviceTree | awk -F"\<|>" '/"system-id"/{print $(NF-1)}')"; Echo SYSTEM_UUID="'$SYSTEM_UUID'" >> macos_vm_vars_file && DmiSystemFamily="$(system_profiler SPHardwareDataType | awk -F": " ' /Model Name/ { print $2 } ')"; echo DmiSystemFamily="'$DmiSystemFamily'" >> macos_vm_vars_file && DmiSystemProduct="$(system_profiler SPHardwareDataType | awk -F": " ' /Model Identifier/ { print $2 } ')"; echo DmiSystemProduct="'$DmiSystemProduct'" >> macos_vm_vars_file&& DmiSystemUuid="$(system_profiler SPHardwareDataType | awk -F": " ' /Hardware UUID/ { print $2 } ')"; echo DmiSystemUuid="'$DmiSystemUuid'" >> macos_vm_vars_file && DmiBIOSVersion="$(system_profiler SPHardwareDataType | awk -F": " ' /Boot ROM Version/ { print $2 } ')"; echo DmiBIOSVersion="'$DmiBIOSVersion'" >> macos_vm_vars_file && DmiBoardSerial="$(nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB | awk -F" " ' /MLB/ { print $2 } ')"; echo DmiBoardSerial="'$DmiBoardSerial'" >> macos_vm_vars_file && ROM="$(nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM | awk -F" " ' /ROM/ { print $2 } ')"; echo ROM="'$ROM'" >> macos_vm_vars_file && MLB="$(nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB | awk -F" " ' /MLB/ { print $2 } ')"; echo MLB="'$MLB'" >> macos_vm_vars_file
Just cd to a working directory, copy/paste in terminal+ ENTER. Inspect the created filemacos_vm_vars_filewith a text editor. I created this originally for the Vbox OS X iMessage fix.
with full SMBIOS spoofing try :
BIOSVersion: "1539.0.0.0.1" BIOSReleaseDate: "07/12/2020"
OpenCorePkg/AppleModels/DataBase/iMacPro/IMP11.yaml at master · acidanthera/OpenCorePkg
OpenCore bootloader. Contribute to acidanthera/OpenCorePkg development by creating an account on GitHub.
Or complete manual SMBIOS injection (fill in every single item in the DataHub, PlatformNVRAM and SMBIOS section).
I never try to use manual mode but only inject so little info. That may be the issue.
As specified in the OpenCore manual, you can set the following NVRAM variable to prevent any (obviously incompatible) firmware updates:
Code:
<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<dict>
<key>run-efi-updater</key>
<string>No</string>
</dict>But still you need to create a new iMacPro identity for the iMessage. On the top of this if you change the UUID, the licensed software will stop working, so will the licensed Windows installation. This may be used as a temporary fix for upgrading/updating, but I would recommend logging out of all Apple subscriptions beforehand. This should not be used on regular basis.
I am still using opencore 0.5.9 version with previous method BlacklistAppleUpdate but apparently on BigSur it doesn't worked, because in middle installation I encountered the firmware update screen that simulated the EFI flash but hasn't updated the stock machine firmware and installed anyway BigSur beta 3 without issues.
I should add that I don't spoofed to iMacPro1,1 but some MacBookAir6,2 or MacBook10,1 .
Do you use the latest? :
Code:
BIOSVersion: "122.0.0.0.0"
BIOSReleaseDate: "06/10/2020"
Code:
BIOSVersion: "428.0.0.0.0"
BIOSReleaseDate: "06/16/2020"I use my original UUID to perform the iMac Pro SMBIOS spoofing. May be this is why I didn't see such issues.
So are the iMessage keys unchanged when you use MLB, ROM, System Product Name, Serial number of the iMacPro?
When running OpenCore .5.9 on a MacPro5,1 and when trying to capture video with various video capture programs on Catalina (10.15.6) I'm seeing errors such as
Full error:
Anyone see this before and what could be done to work around this problem on a fully compatible video card?
"There was an unexpected problem with the graphics sub-system that prevented screen capture." Full error:
Code:
failed: Error Domain=AVFoundationErrorDomain Code=-11844 "Cannot Capture" UserInfo={NSLocalizedDescription=Cannot Capture, NSUnderlyingError=0x600000dc5da0 {Error Domain=NSOSStatusErrorDomain Code=-67394 "(null)"}, AVErrorRecordingSuccessfullyFinishedKey=false, NSLocalizedFailureReason=There was an unexpected problem with the graphics sub-system that prevented screen capture.}Anyone see this before and what could be done to work around this problem on a fully compatible video card?
Did you allow the app for the screen recording in Security& Privacy/Privacy?
Yes.
Won't that screw up aspects of Apple ID activation and the key associated with this machine with Apple? I don't want to jeopardize the "Macness" of my system.
In looking at the suggestion to try an iMacPro1,1 I see that you did this yourself. Right now I am using the BoardProduct of Mac-7BA5B2D9E42DDD94, but where do you get the other values (and are they needed?) that you're using for your hybridization from your screenshot?
Thanks for pointing that out - on the FirmwareFeatures and FirmwareFeaturesMask: both in Xcode and other options, nothing seems to give the same result that you have shown there for the data contents. How did you insert these two values? I could cheat and ask you for a copy of your config.plist, but I'd also like to understand how to edit data fields in these plists properly...
Code:
FirmwareFeatures: 0xFD8FF53E
FirmwareFeaturesMask: 0xFF9FFF3F