How to Fix iMessage

[dickybow]

Hello

Running Yosemite 10.10 via Clover - this guide says iMessage should work however when I try to use it,
error message "Could not sign into iMessage - An error occured during activation. Try again"

Should I use Path C ?

Regards



OSX 10.10 Yosemite and iMessage

If you followed my advice from the last six months and you've already made the transition to using Clover as your boot-loader then the good news is you don't have to do anything in order to get iMessage working.

 

[jaymonkey]

Hello

Running Yosemite 10.10 via Clover - this guide says iMessage should work however when I try to use it,
error message "Could not sign into iMessage - An error occured during activation. Try again"

@dickybow,

Was Clover and iMessage running ok on Mavericks first ?
Check OSX Serial Number validity

Have you read the guide and checked everything ?

Cheers
Jay

 

[dickybow]

@dickybow,

Was Clover and iMessage running ok on Mavericks first ?
Check OSX Serial Number validity

Have you read the guide and checked everything ?

Cheers
Jay

Hello Jay, thanks for replying

This is on a new build so no experience in Mavericks . What path would you recommend?

 

[jaymonkey]

Hello Jay, thanks for replying

This is on a new build so no experience in Mavericks . What path would you recommend?

@dickybow,

From Part-2, Step-7 ....

To continue select the correct path based on your boot-loader and version.

• If you are using a version of Chimera earlier than V3.0 start the guide at Path A
• If you are using Chimera V3.0 or later then please start the guide at Path B
• If you are using a version of Chameleon earlier than r2284 then start with Path A
• If you are using Chameleon r2284 or later then please start the guide at Path B
• If you are using Clover then start the guide at Path C

So Path-C ....

Stay disconnected from network .... and do following

Check Network Configuration settings: Part-1, Step-2
Check OSX S/N is correct for System Type: Part-1, Step-3
Check MLB & ROM are ok and persistent: Part-1, Step-5d

Cheers
Jay

 

[dickybow]

Ok thanks, that is what I suspected in my first post. Thank you for confirming

 

[aqp99]

I used this guide to successfully resolve iMessage problems when running 10.9.5.

I just followed the guide to upgrade to 10.10 using Clover with success, but when checking all my id's before connecting to iMessage, I've found that Clover is not injecting my SystemID from previous profile, despite it being in the edited config file. Somehow it's using another SystemID.

edit: My mistake - I think I was mistaking the platform id with Systemid. (I think that mistake is in the Guide to Installing Yosemite using Clover - though.) Will try this again.

update: Yes that was the mistake. Put in proper SystemID from previous build and the resulting PlatformUUID (after reboot) matches previous build. However, I also checked the Yosemite install with Clover guide and can confirm that those were the instructions regarding editing the config file. You may want to advise the moderators to update that Guide.

Have checked and iMessage works on my build. Thanks for this great guide!

FYI - I used the latest Clover version (2976) without a problem (other than mistake noted above).

 

[herrlee]

@herrlee,

That will never find the key because the terminal command only searches the IOService Device tree by default. You need select the IODevceTree the find system-id under /EFI/Platform.

View attachment 114044

The only other possible explanation is that your manually injecting the Hardware (platform) UUID rather than the SmUUID in your clover config .... check the System Parameters page in Clover Configurator, if you have a value for 'Custom UUID' then it's likely that the check box for 'Inject system-id' is un-checked in this case Clover will over-ride OSX's generation of the Hardware UUID and replace it with the value you've specified in 'Custom UUID' ... this is not recommended as other services may try to generate their own special UUID by using the SmUUID rather than the Hardware UUID.

This issue was just discussed on the previous page in post #2228

Cheers
Jay

I've double-checked, i didn't set the CustomUUID value. Are the following pairs true? If it is, then it'll make sense.


System-ID ---> CustomUUID with InjectSystemID set to true
PlatformUUID=HardwareUUID ---> SmUUID

 

[jaymonkey]

I've double-checked, i didn't set the CustomUUID value. Are the following pairs true? If it is, then it'll make sense.

@herrlee,

From Part-2 of the guide :-

UUID Summary:

On a working OSX system the following should all be true.

• The platform UUID (via terminal command: "ioreg -lw0 | grep PlatformUUID") and hardware UUID (via System Profiler -> Hardware Overview) should always be the same.
• The IOReg key "system-id" (IORegistry: IODeviceTree : efi / platform / system-id) should always be 16 x 16Bit unique hex numbers and will always be different to the OSXplatform & Hardware UUID regardless if manually injected or supplied by the BIOS.

As for Clovers "Custom UUID" field on the "System Parameters" page ..... as already discussed in almost all instances this should be left empty but "Inject System-Id" should always be checked/selected in which case Clover will inject the value of "SmUUID" on the "SMBIOS" page as the SystemId or if "SmUUID" is left blank then Clover will attempt inject the UUID provided by the BIOS for System-Id.

I agree that it is a little confusing but remember that both Clover and Clover Configurator are still in beta and being developed ....

I think "Custom UUID" should be renamed "Custom platform-UUID" and the "Inject System-Id" option should be moved next to the "SmBIOS" field on the SMBIOS page.

Hope this helps to clarify things for you, I take it you found System-Id in correct location in the registry.

Cheers
Jay

 

[herrlee]

@herrlee,

From Part-2 of the guide :-

As for Clovers "Custom UUID" field on the "System Parameters" page ..... as already discussed in almost all instances this should be left empty but "Inject System-Id" should always be checked/selected in which case Clover will inject the value of "SmUUID" on the "SMBIOS" page as the SystemId or if "SmUUID" is left blank then Clover will attempt inject the UUID provided by the BIOS for System-Id.

I agree that it is a little confusing but remember that both Clover and Clover Configurator are still in beta and being developed ....

I think "Custom UUID" should be renamed "Custom platform-UUID" and the "Inject System-Id" option should be moved next to the "SmBIOS" field on the SMBIOS page.

Hope this helps to clarify things for you, I take it you found System-Id in correct location in the registry.

Cheers
Jay

Thanks. It's clearer now. I've tried these two combinations:
1. SmUUID -->some value, InjectSystemID -->no
Result: no System-Id in 'IODeviceTree', 'Hardware UUID' is SmUUID
2. SmUUID -->some value, InjectSystemID -->yes, CustomUUID-->same as SmUUID
Result: System-Id is SmUUID, 'Hardware UUID' is some random number, CustomUUID seems useless.
Is this a bug of clover(r2999)?
In both situations, the system functions well, should I set InjectSystemID -->yes and let the system generate 'Hardware UUID'? Doing this, it'll be identified as a different mac.

 

[jaymonkey]

should I set InjectSystemID -->yes and let the system generate 'Hardware UUID'? Doing this, it'll be identified as a different mac.

@herrlee,

Yes that is the preferred and recommended method (as detailed in the guide) but if your motherboard suffers from the Sid bug (see Part-2) then you should also enter your old SmUUID/System-Id on the SMBIOS page then the Hardware-UUID should be the same as it was before meaning that you'll avoid having to call Apple to remove the device lock-out.

If you're Mobo was not suffering from the SId bug and you were not injecting SystemId via the boot-loader then you can leave SmUUID empty and Clover will inject default BIOS SystemId UUID.

However .. as a matter of precaution I aways put a value in for Clovers SmUUID .... if mobo does not suffer from SId bug then enter the SystemId from the BIOS .... if mobo does suffer from SId bug then enter value generated via 'uuidgen' console command. This way you can make a backup of your config.plist file and keep it with a copy of iMessage Debug's output and you should always be able to restore your working ID's should you ever need to reinstall OSX ... etc

Custom UUID (On System Parameters page) is there to allow injection of your old Hardware UUID if you don't know what your old SmUUID was ..... however as already discussed, by-passing OSX's automatic Platform UUID generation is not recommended and may introduce unforeseen issues.

Quote from the Clover Guide:-

CustomUUID

[COLOR=#000080]<key>[/COLOR]CustomUUID[COLOR=#000080]</key>[/COLOR]
[COLOR=#000080]<string>[/COLOR]511CE200-1000-4000-9999-010203040506[COLOR=#000080]</string>[/COLOR]

Unique identification number of your computer. If not set, an automatically generated UUID will be used. Customise it with hexadecimal digits for full control over your hackintosh.

InjectSystemID

[COLOR=#000080]<key>[/COLOR]InjectSystemID[COLOR=#000080]</key>[/COLOR]
[COLOR=#000080]<false/>[/COLOR]

The number described above can be injected differently and transformed by the OS into another ID. The aim is to provide an option for Chameleon users to replicate their UUID. Set to <true/> and change CustomUUID to match the UUID used with Chameleon found in registry at IODeviceTree:/efi/platform>system-id. Profiler will show a different UUID that will match the one generated with Chameleon.

The feature has been flakey for a while now and is not recommended, however i have not tested it with the latest Clover builds > r3000 so things may have improved.

Cheers
Jay