How to Fix iMessage

[ellissitzky]

View attachment 103685

View attachment 103686

@ellissitzky, @Kris404,

Guys, i've not seen either of these messages before so this may be something new ? possibly a result of those imminent security updates that Apple were talking about - See post #1212.

Before contacting Apple I would check everything, ensure SM-UUID is unique and you have a valid and random S/N (12 digits) - Check System Type is correct for your hardware and that both MLB & ROM are persistent.

See Steps 3 & 5d of the guide .... go steady and let me know hoe you both get on.

Good Luck
Cheers
Jay

I found a post somewhere on the Apple Support Communities that suggested deleting I think the NetworkInterfaces.plist and rebooting, seems to have fixed it.

 

[jaymonkey]

Had so switch back to Chameleon r2283 to have persistant MLB & ROM values. However I lost support for my HD4600 and my Hackintosh can no longer go to sleep. I know it's not really related to this topic but since many of you already did this, could you help me?

Will call Apple tomorrow to unlock my Apple ID.

@Flo655,

r2283 works for some but can also cause issues with SM-UUID (SystemId). Try using the alternate SM-UUID method if that does not work it's worth putting in the time and effort to get Clover working. It gives you a lot more control and once working you wont have any issues with SM-UUID. S/N ROM & MLB ....

Cheers
Jay

 

[jaymonkey]

I found a post somewhere on the Apple Support Communities that suggested deleting I think the NetworkInterfaces.plist and rebooting, seems to have fixed it.

@ellissitzky,

Glad your up and running, see Part-1, Step 2 for info on Network interfaces and bsd names - deleting the NetworkInterfaces.plist is discussed as a possible for fix for non sequential bsd names.

Cheers
Jay

 

[doradekell]

Two things I found using the official wiki for clover's config.plist that were very counterintuitive (or my system is not following the rules of this multiverse).
-MLB and ROM values may be deprecated, but this method works and you need to take any spaces out of the ROM string value
-CustomUUID works only when InjectSystemID is /false. The explanation there is either wrong, not worded properly or I just don't understand how it works.

Either way, Clover seems to be pretty awesome and I'm feeling silly for avoiding it in the past.

Cheers!

JohnnyV,

I too would like to know what links you used as a guide for Clover. I have been avoiding it like you mentioned thinking it was hard to setup/configure. I have a test drive that I would love to use to learn hwo to setup Clover so any links/suggestions you have would be great!

Jay,

A HUGE thanks to Jay for all of his hard work answering questions and keeping this guide up to date. I was able to get my system configured properly and called Apple. The whole call was at most 5 minutes including the wait time! iMessage is now working as it was before! I used your suggestion as well to update my SMBIOS to iMAC13,1 from the MacPro 3,1 that I had set (GA-Z77-UDH5 w/ i3770k CPU).

Thanks JAY!!!!!!!

 

[Kris404]

View attachment 103685

View attachment 103686

@ellissitzky, @Kris404,

Guys, i've not seen either of these messages before so this may be something new ? possibly a result of those imminent security updates that Apple were talking about - See post #1212.

Before contacting Apple I would check everything, ensure SM-UUID is unique and you have a valid and random S/N (12 digits) - Check System Type is correct for your hardware and that both MLB & ROM are persistent.

See Steps 3 & 5d of the guide .... go steady and let me know hoe you both get on.

Good Luck
Cheers
Jay

Looks like they are checking for a valid serial number now. Just a random serial for the system identifier generated via Chameleon Wizard (iMac12,2 in my case) may or may not suffice.

So before calling Apple, I changed my serial to valid one and it took only about 3 minutes to unlock.

Here are the steps:

Required:
1) Check your serial against https://selfsolve.apple.com/
a) Your serial has to pass hardware serial number test at the URL above.
b) Keep trying with a new serial if it does not.
c) The serial number is closely dependent on the model identifier (iMac12,2, Macmini5,1 etc). So, do not use serial number for a different model.
d) Login to iMessage and get a new validation code.
e) Call Apple and ask for OS X support.
f) Support will make you login with your Apple ID at http://appleid.apple.com
g) This is to generate & obtain a 'Temporary Support PIN' for identity verification.



Optional (but makes the process faster)
Apple SupportProfile VoicePass & Device Registration
a) Login with your Apple ID at: https://supportprofile.apple.com
b) Add the phone number you are calling from & check 'VoicePass'. This makes it easier for Apple to identify you and your device you're calling about via nicknames & caller ID.
c) 'Register & Add Products' - If you have a valid serial for your model, you can it register against your account and add a nickname ('iMac'). Now is also a good time to 'Disassociate' any devices not in your possession anymore (sold, broken etc.)

 

[Flo655]

Account unlocked, though my S/N is not a valid one, I hope it will still work across reboots..

 

[jaymonkey]

A HUGE thanks to Jay for all of his hard work answering questions and keeping this guide up to date.

@doradekell,

Thanks for the feedback and i'm pleased your iMessage is up and running ....

I too would like to know what links you used as a guide for Clover. I have been avoiding it like you mentioned thinking it was hard to setup/configure. I have a test drive that I would love to use to learn how to setup Clover so any links/suggestions you have would be great!

Best advice i can give is dive in there, sure its different and may seem complex but it's not.
There are many clover guides out there to follow but here is my method:-

If you have an spare/old drive kicking around use it as a test for installing OSX & Clover, only move on to your main build once your a bit more confident with clover.

I find it much easer to install OSX using Unibeast, we're all familiar with making a unibeast install USB and most of us already have one laying around so why change ?, it is not necessary to install OSX using a Clover based USB stick.

Once you have a clean/ vanillia install of OSX boot into it as normal using Unibeast but do not install Chameleon, download Clover and jump to Step-4 (post Install) of Tony's guide here:

Its only necessary to do items 1 to 6 of Step-4, when you reach the step to to edit the config.plist you can download one of configs from Tony's guide as a starting point or use the default, use Clover Configurator to fine tune the Boot-settings. Use the SMBIOS page and click on the 'magic wand' to select a pre-made SMBIOS and set your OSX S/N and SmUUID to what your using now and then on the RtVariables page set your ROM & MLB to your current values - use this guide to understand what all of the options do.

I've updated the Clover instructions in the guide with screen grabs when setting S/N & SmUUID and MLB & ROM.

While fine tuning your Clover configuration you'll probably have KP's or lockups during booting, if this happens you can use your unibeast USB to get back into OSX, re-run Clover Configurator, mount the EFI Partition and load the config.plist and make any necessary adjustments.

Use Multibeast 6.4.2 to install any needed 3d party kext's (Ethernet, Trim, EvoReboot ... etc) into /S/L/E as normal (use multibeast 6.2.2 for ALC audio to avoid the wake issues) - For most installs there is no need to install any kexts on the EFI Partition.

That should get you up and running, from there you can start to explore the more sophisticated Clover features such as dynamic kext patching ...

It's really not that much different from using Chimera once you get used to it and understand it, Clover gives you far more control over everything and has far superior support for NVRAM/SMBIOS injections which is what is required for iMessage, once working you'll never want to go back to Chameleon or Chimera.

I'm sure that some Clover purists will frown on my hybrid method but it works really well and gives a certain amount of familiarity and confidence by using unibeast as the installer and for getting out of trouble.

Good Luck
Cheers
Jay

 

[jaymonkey]

CustomUUID works only when InjectSystemID is /false. The explanation there is either wrong, not worded properly or I just don't understand how it works.

@johnny37v,

It's best not to use 'CustomUUID' as your over-riding OSX, you want to over-ride the BIOS so better to inject SmUUID on the SMBIOS options page along with MLB & ROM. OSX uses SmUUID as a crypto key for generating Hardware/Platform UUID.


I've updated the Clover Instructions for Step-7, Part-2 of the guide with this so others wont make the same mistake.

Cheers
Jay

 

[jaymonkey]

Looks like they are checking for a valid serial number now. Just a random serial for the system identifier generated via Chameleon Wizard (iMac12,2 in my case) may or may not suffice.

@Kris404,

Thanks for your feedback and the steps you used in post #1270, I think you may have had to do this because of the message you got in post #1255. This is very different to the standard iMessage alert with a customer code. However it may be something new so will keep an eye on things for the next few weeks and see is anyone else gets this issue. I've updated Step-8 with using Voice ID though, thanks.

Cheers
Jay

 

[jaymonkey]

Account unlocked, though my S/N is not a valid one, I hope it will still work across reboots..

@Flo655,

It does not matter if S/N is not valid but OSX S/N, UUID, MLB & ROM must be persistent, if any of these values are changing between reboots then you will have issues with iMessage if you have to log back in again.

See Part-1, Step 5d to check if ROM & MLB are persistent, Part-1, Step 2 for advice on S/N, Part-2 covers SmUUID.

Cheers
Jay