Download FileNVRam 1.1.2 from
http://public.xzenue.com/downloads/
its under the archives folder - For some reason 1.1.3 didn't work
Put the .dylib file in Extra/Modules folder on your drive
Reboot and sign in to iMessage
This worked for me!!
Reference -
http://www.insanelymac.com/forum/topic/286563-filenvram-113-released/
Mmmhh, quite an interesting post, I'll give it a try
I have an even stranger issue, obviously I am unable to get the iMessage working with either method mentioned here and after doing some research I finally found out that it is my UUID that is invalid, (or blocked at apple). So I tried changing the UUID by using Chameleon Wizard, text edit, and other methods and when I reboot, the same UUID is there, it doesn't change. Did a fresh install of Mavericks, (making sure I deleted and recreated the partition)... guess what, same damn UUID appears in System Report instead of the generic one generated by the installation, and strangely enough, when you edit the SMBios file, the generic UUID is there. Even weirder, I reboot the machine using an older version of clover, (the one that iMessage was working %100 percent), and I boot to my old drive with mountain lion, and guess what? The same error message when trying to get to iMessage, and long behold, guess who is there on the System Report? The same damn UUID, how the heck did that get across separate partitions and versions of installs is beyond me. My only theory is that Apple some how found a way to permanently register that UUID on my computer hardware so I won't be able to use iMessage on this build, or any builds. (by the way it works fine on my MBP, and all my other idevices).
Guess what... I'm on the same road as you, I mean the same "thoughts processing", by looking deeper into IOPlatformUUID and NVRam registers.
So, what I tested so far:
1.
-Boot, and try to login to iMessage, receive 'Call Apple Support'
-Change NVRam MLB Value to a 18 digits number instead of a 17 digits number (or the contrary depending on the SMSerial you're using)
-Try to login to iMessage, first attemp NO-GO (seems to wait for some anwser from the serveur which never comes...)
-Try to login to iMessage, second attemp, Message is telling me I'm connected, I can see all the addresses I can be reached at (also my Phone Number), I can add/delete any address I want, BUT GUESS WHAT? -> I CAN'T SEND A BLOODY MESSAGE!
2.
-Change SystemId key in org.chameleon.boot.plist to a custom made one, as to change the NVRam IOPlatormUUID register to a "non-blacklisted" one (at least that's what I thought)
-Reboot, verifiy changes have been made into NVRam registers
-Try to login to iMessage, receive the bloody 'Call Apple Support" message
BTW: I think iMessage, or ANY other Apple service, cannot be bound by Hardware UUID, because if it was so, I could login for example on any other iMessage working Hackintosh... and THAT'S NOT THE CASE.
There definitely IS something between "AppleID/NVRam MLB register/IOPlatformUUID"...
I setup 3 different Hackintoshes (including mine) for the last month, the two others having a 100% working iMessage (with NVRam 1.1.3 BTW), with perfectly set NVRAM registers (all different from each other Hackintosh), and I STILL CAN'T LOGIN! (could be on any other Hackintosh, still the same)
I also tries the flollowing famous "fixes":
-Removing/re-Adding credit Card
-Log out from iMessage on all my other Apple devices, then log back in on those devices, then log back in with the Hack
The ONLY thing I didn't try was to change my password... I don't want to change it wihtout being SURE it REALLY DOES something... (yeah I've 3 other Apple Devices, it's a bit annoying...)
Last word, I think we're on the right track, but something's missing here...
