How to Fix iMessage

MysticalOS said:

I'm sure i'll find out soon, but still waiting on 10.10 download. about 3 more hours. country internet. :\

Click to expand...

Ah, ok. Well, I'm going to bed but be sure to keep us updated here!

odds said:

Can you confirm working NVRAM/iMessage with Clover and 10.10?

Click to expand...

Working well, I have it running since last night. iMessage notifications are more reliable on Yosemite than on Mavericks.

Clover r2953

MysticalOS said:

You're not far off is right Jay. Between this and now 10.10 has NO nvram cause file nvram doensn't work. 10.10 is perfect time for a clean install of clover and 10.10 going forward. then go from there

Click to expand...

So there is not going to be a way to get imessage working again with chameleon?

carltom46 said:

So there is not going to be a way to get imessage working again with chameleon?

Click to expand...

@All,

If your mobo does not suffer from the Sid Bug then there is a good chance that the latest Chimera/Chameleon will work for you with OSX 10.10 and iMessage as long as it preserves NVRAM .. etc.

However if your mobo does suffer from the Sid bug then it limits your options to specific versions of Chimera or Chameleon which do not always play nice with FileNVRAM which has not been updated in a long time, so you may end up in cant fix everything loop ...

I have not had a chance to test the latest Chimera 4.0 as i use Clover these days, however i'd still like to hear from anyone (good or bad) about iMessage on 10.10. I'm currently in the process of testing iMessage on 10.10 using Clover and all is looking good.

I've been posting and warning users to consider updating to Clover for months now as i'm not sure about the status of FileNVRAM and on-going development, with that said it's possible that the new version of Chimera or Chameleon has something new and specific to help with iMessage NVRAM/SMBIOS issues but i see nothing in the change logs ... so i wont be holding my breath on that ...

I'll have more news soon and will update the guide accordingly ...

Cheers
Jay

I have the same problem with iMessage. Sadly I tried Clover but it didn't work for me. Always crashes my install and can't boot. I hope we will get a fix with Chimera / Chameleon

I had the customer code issue and called Apple this morning with my MacBook Pro serial number and just made out like I was having issues on that platform.

Gave him the code and it was unlocked immediately - no drama.

I'm running Yosemite 10.10 with Clover and it's working great. I just rebooted to ensure it's still working with persistent ROM/MLB etc and all's good so far!

Edit: Forgot to say THANKS for an awesome guide - it helped me out loads!

Kris404 said:

Working well, I have it running since last night. iMessage notifications are more reliable on Yosemite than on Mavericks.

Clover r2953

Click to expand...

Awesome. I have never used Clover before. Will you link me to the best Clover guide you have? Thanks! Can't wait to have Yosemite up and running with working iMessage.

I haven't fixed my iMessage problem for a few months knowing Yosemite was coming out. I'm gonna do a clean install on a new SSD next week. But disappointed latest Uni/Multibeast isn't using Clover or has an option for Clover.

I did all the steps listed and it worked...that was about a month ago but today when I went into messages it gave me the customer code screen again. Anyone else get that? Did apple update something? I'm still running 10.9.4.
Thanks

Quick question to Jay :

My Mavericks installation was working perfectly fine with good SmUUID, ROM and MLB values. However, I decided to switch from Chimera to Clover with the release of Yosemite.

You said in your guide that Clover now reads ROM value from SmUUID, however, in my previous install, ROM value was not a part of SmUUID which was completely random. How can I still use my old values with the latest Clover release? If I use the new method as you said, my SmUUID will change in order to keep my old ROM value and I guess it is going to break iMessage support, am I right? Should I do this and call Apple again or is there a way to avoid this?

Thanks!