What's the current state of iMessage functionality? Mine isn't working, any current fixes?

[raygan]

A while back my iMessage quit working but was fixed by using a then-beta version of Chameleon as my bootloader. As soon as the fix was incorporated into Chimera I switched back to that bootloader.

Now the same issue has returned. I'm not able to log into iMessage, and I gather that I'm not alone at the moment. Is this the case for everyone right now?

Does anybody know if there's a fix or alternative bootloader that I should try in the mean time? I've searched the forum, but I'm coming up with a lot of out of date messages and fixes that I don't think apply to the current situation.

 

[ppohio]

I used the NVRam fix detailed here:

http://www.tonymacx86.com/mountain-lion-desktop-support/87472-fixing-imessage-without-clover.html

I used NVRam 1.1.2, not 1.1.3 because the newest Chimera update made mention that 1.1.2 fixes iMessages and 1.1.3 fixes Facetime but not both.

I know that at the top of that thread it says "Use Chimera 2.0" instead and "Troubleshooting iMessage Login" but none of those solutions worked for me.

 

[raygan]

Thanks, I'll give this a try. Are you using this fix with the latest version of Chimera? And have you had to make any changes to your computer's serial number or other info?

 

[ppohio]

No change to the serial number. I tried that and all the ethernet tricks the first time around and couldn't get it to work. On my current build I just assumed iMessages wasn't going to work and started again from scratch. Then I saw the NVRAM fix a few days ago and decided to give it a try and that got it to work.

I am not sure how to check for a valid serial number - I tried the one on Apple's site for checking warranty and my serial came up as "not found" - is that valid or invalid? I have no idea. I assume if it came up as found that would mean that it was a serial tied to another machine already out in the field.

 

[mike5065]

does your icloud sync work fine as well? my imessages is still screwed up (i'll try this fix again), but i just noticed my safari bookmarks are not syncing from my hack.

 

[ppohio]

My iCloud sync is working fine I believe. Contacts sync has been working and I just tried adding a bookmark on my iPhone and it popped up on Safari on my Hack.

 

[rburgos]

I've been experiencing intermittent Messages.app functionality as well. About a week ago, I had good results after clearing .plist files related to messages and clearing my login keychain of everything having to do with iMessage authentication. Problem was that after a reboot, things would behave really unpredictably ... some of my known-good iMessage contacts would not work. Some messages were sent but not really transmitted, others would refuse to be sent because the number/email was supposedly not registered with iMessage.

I simply obtained my PlatformUUID and added it to my nvram.00020003-0004-0005-0006-000700080009.plist file (inside /Extras) and to org.chameleon.Boot.plist

A reboot later, Messages.app is now working and all known-good addresses and iPhone numbers immediately show the blue cloud icon next to them indicating they are registered with iMessage.

Will report back to see if the fix persists through several reboots and system shut downs.

 

[neronis]

Thank you rburgos.

Your solution fixed my iMessage

 

[rburgos]

I am not very clear what the change accomplished (other than fixing Messages.app). When I go back to the two files edited, org.chameleon.Boot.plist has the SystemId entry with the alphanumeric string that I got after using "ioreg -lw0 | grep PlatformUUID" in terminal. However, looking inside the nvram.00020003-0004-0005-0006-000700080009.plist file, I see the change was apparently lost after reboot. The computer's PlatformUUID entry reverts back to <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>.

Perhaps someone with good understanding of the issue could provide an explanation as to what the fix does and why it was broken to begin with.

 

[rburgos]

This is a bit off-topic but perhaps related to what is borking Messages.app...

After fixing Messages.app, I went on to updating FileNVRAM.dylib. Instead of version 1.1.2, I decided to try version 1.1.3. You can find it here.

I've read elsewhere in this forum that 1.1.2 fixes a problem with Messages and 1.1.3 fixes a problem with FaceTime but that you can't have both fixed ...

Installing FileNVRAM.dylib version 1.1.3 into /Extra/modules/, rebooting and then trying FaceTime resulted in success.

I find there is a bit of a problem with using FileNVRAM.dylib v 1.1.3. If you log out of Messages.app for whatever reason and then try to log back in, you will find a server error. The workaround is to place FileNVRAM.dylib v. 1.1.2 back into /Extra/modules/, rebooting and then signing into Messages.app. Since using FileNVRAM.dylib v 1.1.2 will cause FaceTime.app to crash you must again update FileNVRAM.dylib to v 1.1.3. So, once you are able to sign in to Messages.app, go ahead and put FileNVRAM.dylib v 1.1.3 into /Extra/modules and reboot. You should have a working Messages.app and FaceTime.app.

Good luck.