Hi, I'm finally considering to make the switch but I have a problem. When I was building this hack last year I followed vanilla guide but, I don't remember where I got the tip, I read a lot and watched a lot about SMBIOS and iMessage activation and created CustomUUID with Clover Configurator.
I've generated SMBIOS with macinfo (former macserial) as it is stated in the guide, macserial -a | grep -i iMac15,1
and used one of the generated Serial | Board Serial (MLB) pair in SMBIOS. Also created SmUUID with uuidgen
and used it in SMBIOS and set the rest by the guide. But, I also clicked Generate New under CustomUUID in Clover Configurator.
We can create an SmUUID by running
uuidgen
in the terminal (or it's auto-generated via my GenSMBIOS script) - and that gets copied to SMBIOS -> SmUUID.
InjectSystemID
This setting tells clover to set the SmUUID as the system-id at boot - which is important for iMessage and such.
When I checked what my system sees I found out instead of the SmUUID value in SMBIOS, OS sees the CustomUUID as System UUID.
config.plist:
SmUUID: 111 (made up value to show what matches what)
CustomUUID: 222
Hackintool:
Hw UUID: 333 (this is auto generated with SmUUID as I've seen)
System ID: 222 (this is supposed to be the same with SmUUID in the config.plist but it is the value of CustomUUID)
System Info:
Hw UUID: 333
IOReg:
IODeviceTree:
IOPlatformUUID: 333
IODeviceTree:/efi/platform: system-id: 222
Because I've generated Custom UUID, the system sees it as SmUUID and the real SmUUID that is generated by running uuidgen
in the terminal and used in SMBIOS -> SmUUID in config.plist is not used.
So, OpenCore does not support CustomUUID and as I understand (correct me if I'm wrong) in order to get the same Hw UUID, I need to use CustomUUID to fill SmUUID in the new config.plist of OpenCore. In this way Hw UUID will be same and I don't get blacklisted from iCloud and iMessage etc.
Is that correct?
Thanks!
[link] [comments]
Post a Comment