How to Fix iMessage

[rockinwaggy]

@McMighty,

...if your using Mac Pro 3,1 then you may find that the S/N is 11 digits, i don't why this is.

It appears that some machines use 11 digit serials. My 6,1 MBP has an 11 digit serial. No issues.

Edit: My Hack's Mac Pro 3,1 serial is also 11 digits.

 

[godis1coolguy]

I had a similar issue last night. I was randomly no longer logged in and despite many different things that I've tried, nothing has worked yet. Please let me know if you figure something out.

 

[miramar]

My board is a Zotac Z77ITX-A-E. (build link is sig) Currently running 10.8.4, Chimera 3.0.1 and FileNVRAM.dylib 1.1.3.

SMsystemuuid (generated with uuidgen) is defined in smbios.list and is consistent with IODeviceTree:/efi/platform/system-id.

SMserial is an iMac serial number generated with Chameleon Wizard.

However my ROM and MLB (last 5 chars) are changing at random on every reboot. Any ideas on how to fix this?

I read earlier in this thread to disable anything that is UEFI in the BIOS but there doesn't seem to be any UEFI toggle in the BIOS.

iMessage is currently working after calling Applecare but I'm afraid with the changing MLB and ROM that it will be just a matter of time before it gets disabled again.

 

[tommo84]

Finally, after updating to chimera 3 and changing my system to an Imac 13,1, I was able to have the correct nvram.xxxxxxx.plist file! thanks a lot.

Now I have the message from apple with an error code...so I will call tomorrow applecare and fix the problem!

thanks a lot

Tommo

and finally....called applecare, fixed everything!
thanks again for the great help and job with this guide!

cheers

 

[jaymonkey]

My board is a Zotac Z77ITX-A-E. (build link is sig) Currently running 10.8.4, Chimera 3.0.1 and FileNVRAM.dylib 1.1.3.

However my ROM and MLB (last 5 chars) are changing at random on every reboot. Any ideas on how to fix this? iMessage is currently working after calling Applecare but I'm afraid with the changing MLB and ROM that it will be just a matter of time before it gets disabled again.

@miramar,

If ROM value is not persistent between reboots then there is an issue with the interaction between the Boot_loader and FileNVRAM try the suggestions in Part 1, Step 5d, i suspect that anything you do will initially stop iMessage working so perform a full backup/clone before trying to resolve the issues. I'm not sure but i think that they may be some issues with that combination of Chimera & FileNVram with Mountain Lion. You may want to try using Chimera 2.2.1 and FileNVRAM 1.1.2 or update to Mavericks.

The ID's are only validated on Apples systems during a login not every time, as long as you stay logged in to iMessage then it will continue to work however it seems that Apple systems are able to force a log out in certain circumstances.

Cheers
Jay

 

[jaymonkey]

and finally....called applecare, fixed everything!
thanks again for the great help and job with this guide!

cheers

@tommo84,

Glad your up and running, thanks for the feedback.

Cheers
Jay

 

[jaymonkey]

Hi jaymonkey,

I got the the dreadful message: your Apple ID cannot be used to setup iMessage at this time. ... To use this Apple ID with iMessage,contact iMessage with the code below.

Could you help me to figure out what went wrong and what action I could try to take in order to resolve this? Thanks a lot

@elgipsy,

If you getting the iMessage alert to contact Apple with a customer code then thats what needs to be done. Before contacting Apple, check your SM UUID Value (see part-2 of the guide) then run iMessage Debug and check all your IDs (S/N, MLB, ROM) - see part 1, step 5d. Reboot and check again if all the values are the same then go ahead and contact Apple to remove the lock-out. If values are not persistent then use the guide to resolve the issue(s) then contact Apple.

As explained in the guide and over the last few pages, if you get this message there is nothing you can do locally (other than to change all id's and create a new AppleID) the issues is at Apples end.

Good Luck
Cheers
Jay

 

[elgipsy]

thanks for the feedback jaymonkey,

I will check all this and report the progress in this thread.

 

[barranco]

@jaymonkey

Hi, just to shed more light on this issue, even though I get this message on my hackingtosh, I can still remove and setup iMessages on my Apple computers without a problem, I'm guessing the account it's not completely blocked.

@elgipsy,

If you getting the iMessage alert to contact Apple with a customer code then thats what needs to be done. Before contacting Apple, check your SM UUID Value (see part-2 of the guide) then run iMessage Debug and check all your IDs (S/N, MLB, ROM) - see part 1, step 5d. Reboot and check again if all the values are the same then go ahead and contact Apple to remove the lock-out. If values are not persistent then use the guide to resolve the issue(s) then contact Apple.

As explained in the guide and over the last few pages, if you get this message there is nothing you can do locally (other than to change all id's and create a new AppleID) the issues is at Apples end.

Good Luck
Cheers
Jay

 

[barranco]

@tommo84

That's great, can you elaborate how the call went on? I think I'll have to call them soon

and finally....called applecare, fixed everything!
thanks again for the great help and job with this guide!

cheers