How to Fix iMessage

[jaymonkey]

Hi @JayMonkey,
I got values MLB/ROM from real Mac (I signed in my apple id) but I cannot use on my hackintosh (smbios imac12,2). Can u help me? Thx for ur help

@lethanhtung89,

Don't use MLB & ROM from another machine .. the MLB will not match your S/N and the ROM will cause a security miss-match with Apple. looks like you got your self in a right pickle ... you say your Using imac12,2 but the iMessage Debug Shows MacBook Pro 11,1 ??????

Use Chameleon Wizard to set your system type to the nearest hardware match (use Mac Tracker) do not use cloned S/N - follow Part-1, Step 3 of the guide for setting System Type and S/N then use Part1, Step 5d for injecting new MLB & ROM.

Do not contact Apple until you get the alert with a customer code.

Cheers
Jay

 

[pkdesign]

@pkdesign,

Glad you up and running, Messages used to be stored in the iCloud but i think changed that recently, you could try restoring the messages folder form /users/name/library/messages which should have the local copies ... I've not tried it as don't really ever need old msgs .... let me know if it works.

Cheers
Jay

Brilliant! Worked like a charm!

Thanks again for a great forum.

 

[Comcody]

Every time i restart, and open iMessages i get the same messages to contact support. But the Customer Code is always different, it keeps changing when i restart o turn on my Hackintosh.

ROM and MLB have no "zeros" or blank spaces... Should i format OS X and start over??

EDIT: After several reboot, ROM and MLB are persistent... Can't understand why Customer Code keeps changing

 

[jaymonkey]

Every time i restart, and open iMessages i get the same messages to contact support. But the Customer Code is always different, it keeps changing when i restart o turn on my Hackintosh.

ROM and MLB have no "zeros" or blank spaces... Should i format OS X and start over??

EDIT: After several reboot, ROM and MLB are persistent... Can't understand why Customer Code keeps changing

@Comcody,

Check your Sm-UUID is valid, some AsRock motherboards suffer from the SId bug - See Part-2 of the guide.

You said your ROM & MLB were not persistent then they were, if you didn't do anything to make them persistent then i would re-check your boot-loader and FileNVRAM versions, see Part-1, Step 5d of the guide. stuff like that shouldn't happen - computers cant fix themselves without human intervention ....

I think the Customer code uses your AppleID, UUID (Sm or Platform), ROM & MLB ...... all seem to have an impact on the customer code so if it's changing each time then you need to look deeper - I need to research this a bit more to confirm this, so if you find anything - please post feedback.

Cheers
Jay

 

[jaymonkey]

Brilliant! Worked like a charm!

Thanks again for a great forum.

@pkdesign,

Thats good to know, I'll add that bit of info to Step 4 of the guide, it may not actually be necessary to remove the Messages folder in the first place but it seemed logical at the time i was researching and experimenting while i was writing the guide.

Cheers
Jay

 

[doradekell]

@doradekell,

Should be no need to create a new AppleID but i recommend that while your setting up and getting up to speed with Clover avoid logging into any iCloud services. When you get to the SMBIOS configuration set the SmUUID, S/N, MLB & ROM to what your using now that way there should be no changes detected at Apples End.

Once your happy that your values are correct and persistent (use iMessage Debug) then you should be able to login and all should good.

Just take your time, when using Clover Configurator be sure to mount the EFI partition and load the config.plist from /EFI-Partition/EFI/Clover/config.plist - this is where many people fall down. Clover Configurator has its own built in EFI Mounter but i use Semulov 2.0 which is a great little utility that sits in the menu bar, its free and you can get it here.

Just take your time and digest what your doing.
Good luck, let me know hoe you get on.
Cheers
Jay

@jaymonkey,

OMG! I have to say my Clover install had to be one of the easiest things I have ever had to do! Made easier as well by you with the excellent directions!!! I did this from my clean test install on a spare HDD.

I feel like I did not do it right as I really did not have to much at all. After reading up more on Clover, it does a lot of things automatically for you. After adding FakeSMC.kext and installing my audio driver i ran iMessage debug several times after reboots and the ROM and MLB stayed the same. I kept wondering where was the system info coming from since About this MAC had my system identified as iMac 13,2.

That is when I read about Clover auto-detecting your hardware and choosing the best profile for you. Holy crap was all I could say! How sweet! Still thinking I needed to do more I did decided to override that and hard code the system profile using the Clover configurator.

Could it really be that simple? Did I NOT configure something that was really needed? I could not believe it!

Needless to iMessage worked first time I signed in.

To everyone else, as Jay has been saying, "You have to give Clover a chance!" I will say that I am getting ready to switch over my main install to Clover now. I know technically it is still in "Beta" but OMG you will not regret it one bit!!!

Again, I very special thanks to jay monkey for all of his work on this guide and taking care of the community!

THANKS JAY!!!!!

EDIT: Well I posted this too soon it appears. I closed iMessage and reopened and was presented the login box again all be it with another customer code again to call them.

Could I have missed something after all?

 

[jaymonkey]

To everyone else, as Jay has been saying, "You have to give Clover a chance!" I will say that I am getting ready to switch over my main install to Clover now. I know technically it is still in "Beta" but OMG you will not regret it one bit!!!

Again, I very special thanks to jay monkey for all of his work on this guide and taking care of the community!

@doradekell,

You welcome and thanks for the feedback, I only ever use Clover these days, compared to Chameleon/Chimera and FileNVRAM it's light years ahead and no compatibility with versions .. etc

Whilst clover does do a lot of things automatically I always set the System Type to what i want using the 'magic wand' on the smbios page. Then I always generate a new unique uuid in terminal and set at as a custom SmUUID in the RtVariables page regardless if BIOS suffers from SId bug.

Many motherboards BIOS do not generate or return a full 128bit UUID so by doing this you guaranteed not to have UUID issues in the future, after the first re-boot i then go back into Clover Configurator and set the ROM to my en0 MAC address and the MLB to the one returned by running iMessage Debug. That way everything important to iMessage is set permanently in the clover config.plist which you can then back up for each machine and use in the future if you ever have to reinstall.

It's normal to get the Alert msg to contact Apple with a customer code as so much has changed but you should be fine after that, if you have lots of Hacks, its worth updating them all to Clover first and then call Apple....

Be aware that some hardware configs require a bit more manual configuration to get everything working correctly, just wish more people would give it a go ..... then i wouldn't have to spend so much time answering questions ....LOL

Cheers
Jay

 

[doradekell]

@jaymonkey,

Thanks as always Jay. I did neglect uuidgen to add the SmUUID value into the Clover configurator. I also added the ROM and MLB as you suggested as well which makes sense to always know what values I am sending to them and can easily back up the config.plist.

I need to buy you a case of beer (or lemonade if you prefer) for all the help!

Dora

 

[davelaw56]

I have 2 hacktintoshes. I have this message to contact them with the customer code only on one of them. I tried to re install osx on it and the same message appears. It it appears I will have no choice but to call them and I don't know what to say to them since I have tried to change smbios so many times. I guess they will see it...

 

[jaymonkey]

I have 2 hacktintoshes. I have this message to contact them with the customer code only on one of them. I tried to re install osx on it and the same message appears. It it appears I will have no choice but to call them and I don't know what to say to them since I have tried to change smbios so many times. I guess they will see it...

@davelaw56,

Just make sure to check things like your S/N, System Type, UUID, ROM & MLB are ok before calling, see Part-1, Steps 3 and 5d when your ready to call them use the guidance in Part 2, Step 8

I'm sure it will be fine
Cheers
Jay