Im happy to help see if there is indeed a bug but I got no idea what you written in that post to find out
@Wolfie81
It might be useful to know what the BIOS has passed as a seed UUID to OSX on systems that have been effected by this latest iMessage issue.
make sure that you do not have SystemId being defined in your chameleon.plist and reboot (might need cold boot ?)
open ioregistryexplorer and check the following location :-
IODeviceTree : efi / platform / system-id
On all my systems there are 16 x 16 bit values all different
Theory:-
If this location contains all zeros then setting SystemId in the chameleon.plist fixes your issue.
If this location already contains 16 seemingly random numbers then setting SystemId does not fix your iMessage problem, in which case we've only solved half the puzzle ?
Would like feedback on the above to prove or disprove.
If it is still not working, try the following:-
@All
To those of you that it hasn't worked for :-
- Please ensure that the key value you set in your plist is called "SystemId" not "SystemID" or other permutation.
- Use a random UUID as the value for SystemId not one of your existing UUID's, this will ensure that the newly generated platformUUID will be unique.
- Delete the existing nvram.xxxxx.plist in /Extra.
- make sure you have FileNVRAM version 1.1.2 installed
- Reboot and try again
If iMessage is working for you now ... does the value in the IOReg at location :-
IODeviceTree : efi / platform / system-id -> (see above post to @wolfie81)
.... match the value you set the key "SystemId" in the chameleon.plist ?
- The platform UUID and hardware UUID should always be the same
- SystemId should always be unique and will always be different to the platform & hardware UUID
Cheers
Jay