How to Fix iMessage

[n3oNLit3]

For the MLB value use your OS X S/N + random alpha/numeric values to make the correct length based upon the length of your OS X S/N

If you have 11 digit S/N then your MLB should be 13 characters long
If you have 12 digit S/N then your MLB should be 17 characters long

From the guide

 

[n3oNLit3]

@ n3oNLit3 - Thanks for your help and input, I'm in my twilight years and the old grey matter gets bogged down a bit searching for all the answers - lol.

Well, as Ive seen you post before, you try to give back to what was given to you.. I asked tons of questions along the way to getting iMessage working, and Ive read that dang guide more times than I care to admit

 

[esafeddie]

LOL ;D thanx anyway. Maybe I don't really need iMessage.

Sounds like you're giving up - really you'll be missing out on quite a good feature but its your choice, maybe one day you'll go back to it and figure it all out and you will wonder why you let it beat you in the first instance - Good luck.

Do some more research, change your mac model from Pro to iMac and give it another shot and post back if you run into any snags, there's plenty of good folks here who faced the same trials and got through them all and only willing to help.

 

[n3oNLit3]

LOL ;D thanx anyway. Maybe I don't really need iMessage.

albertorossi these ARE the Droids your looking for You will get it, if you keep asking questions and doing some more reading along the way.

 

[esafeddie]

Quite a few posts back a member posted this useful bit of advice - 'Read and read and when you think you've got it read some more then you will have your Eureka moment'.

 

[interpolgp]

Hey great guide, truly brilliant!!!

I have a question, but first I wanna highlight some history. Prior to Nov 2014 I got iMessage working with this hackintosh. I whitelisted it and everything was great. However, as Clover seem to be the future I decided to change boot loaders. When I changed to the UEFI bios the SmUUID (SystemID) and the Sid Bug disappeared.

I now have a different set of values. Same serial number but different MLB and ROM values. (I still have a copy of the old ones).

Should I attempt to login with the new values as they are more closely related to the motherboard or should I patch the old values through Clover?

Any help would be greatly appreciated. Thanks in advance

 

[esafeddie]

Hey great guide, truly brilliant!!!

I have a question, but first I wanna highlight some history. Prior to Nov 2014 I got iMessage working with this hackintosh. I whitelisted it and everything was great. However, as Clover seem to be the future I decided to change boot loaders. When I changed to the UEFI bios the SmUUID (SystemID) and the Sid Bug disappeared.

I now have a different set of values. Same serial number but different MLB and ROM values. (I still have a copy of the old ones).

Should I attempt to login with the new values as they are more closely related to the motherboard or should I patch the old values through Clover?

Any help would be greatly appreciated. Thanks in advance

Hi if you have all the values i.e. Mac S/N, MLB (which is also the BoardSerialNumber) and ROM (which can be your mac address) from when you had iMessage working then yes you can inject these into your config.plist via 'Clover Configurator' and you should be good to go. All is not lost if this is not possible - just log the rig out of iCloud, iTunes, App Store etc and then disconnect from the internet, Generate and inject a set of new values -> Repair Permissions -> reboot (still off line) -> run iMessage DeBugger and check that the new injected values are static (not changing). Do this at least three times if looks good, reconnect rig to internet and try to login, you should be able to without the need to call Apple - any problems just post back - Good luck.

 

[rosendo]

View attachment 126981

How to Fix iMessage View attachment 127172 Chapter: 8 Contacting Apple Support (Activation of Customer Code) View attachment 126983

If you are receiving a iMessage alert informing you that you need to contact Apple Customer support with a customer code then iMessage is now communicating with Apples iMessage servers correctly, however it is possible that too many device ID's have been logged against your AppleID or that your MLB & ROM need to be registered on Apples database .... both these situations will result in the following iMessage alert:-

View attachment 127192
​

Background Info: As already detailed in the guide, Apple log and store various ID's from your OS X device's such as MLB, ROM and Hardware UUID each time you attempt to log into/authenticate with iMessage's servers .... these ID's must be valid and are verified against black lists, masks and security checks ... you will only see the above message once your ID's pass these checks.

Once logged into iMessage your system will receive a security token which will allow iMessage to continue to work without having to login and authenticate on each boot, the token has an expiry date/time ... when the token expires the iMessage agent service will attempt to automatically authenticate again with the iMessage servers ... if some of your ID's (MLB/ROM) have been changing then the service will be unable to authenticate because the ID's are different to those that were registered the first time your system connected to the iMessage servers.

By now you should have been through the entire guide and checked all your ID's to ensure they are the correct syntax and are persistent, if your getting the above alert and your still unsure about your ID's then an easy way to confirm that everything is persistent is to reboot / power off and restart two or three times and make a note of the Customer Code each time you try to login.

The Customer Code is generated by a crypto algorithm using several of your systems ID's and your AppleID. If the Customer Code is not the same each time you run iMessage then one (or more) of your ID's is still not persistent and you need to check everything again.

What Causes this Message ?

The most common cause of this message is that your MLB and/or ROM value are not registered on Apple iMessage system, this can happen to genuine Mac's after a system board has been repaired or replaced.

I found out about another cause of this message after a long chat with a particularly helpful Apple Support representative, he explained that Apple log the number of Apple iMessage capable devices against a single WAN IP (not your local LAN IP's but your routers Internet IP). So this will include any and all hackingtosh systems with changing personalities or ID's (eg ROM value changing on each boot). All of these miss-matches count as 'IP' marks against your account.

If you've been running OS X with non-persistent ID's for some time then it's quite likely that your AppleID will have been flagged as having too many OS X devices or ID miss-matches associated with it thus leading to the above Customer Code message.

Note: OS X USB installers such as Unibeast override many things during boot-up including nvram values which can cause the MLB & ROM to fail (confirmed by iMessage Debug). If the system is able to connect to Apples systems it will still attempt to identify it-self thus potentially logging anther bad device against your WAN IP.

Unless you are using a fully configured Clover based system, when re-installing or updating OS X such as applying a Combo-Update I recommend completely isolating the system from the internet. Only reconnect to the internet once the install/update is complete and iMessage Debug returns the same values you had before - see Chapter 7 of the guide for further info on using iMessage Debug.

There is not much you can do locally to stop this, it's automatic and is part of Apples back-end customer security service, they are basically looking for and logging WAN IP address that have a 'high-volume' of Apple Devices associated with them. If like me you have multiple hacks on your local LAN then try allocating them static IP address via your router's DHCP service .... anything you can do to limit changes may help.

It is important to understand that each device on your network will generate it's own unique customer code, so if you've got multiple hacks, first ensure that they all have valid and persistent ID's and that they always generate the same customer code each time you try to log into iMessage. If they generate different codes each time then one (or more) of your ID's is changing and you need to check everything again. If they are all consistent then make a note of all the Customer Codes, it's far easer to deal with all of them in one hit rather than calling Apple multiple times.

Update Feb 2015: Since initially writing this chapter Apple have changed the look and layout of some of the support pages on their web site, so you may find subtle differences between what you see and what is in the guide, however the following advice is still valid and should be followed as close as possible.

Before contacting Apple support its worth setting up a 'Voice Pass' telephone number for security checks, simply log-in to your Apple ID at: https://supportprofile.apple.com, add the phone number you are going to use to contact Apple with and check 'VoicePass'. This will make it easier for Apple to identify thats it's you calling and should negate some security questions. You can also add a mobile number and allow SMS security messaging which can help to avoid un-necessary security questions being asked when you contact Apple.

View attachment 127191

After setting up 'Voice Pass' you should get an email from Apple confirming your Telephone No.​

View attachment 127190If you own a Apple iPhone or iPad then I also recommend that you enable 2 step authentication on your AppleID, again this may help to affirm your identity with Apple and in some cases the support department may ask you to use your 2 step authentication to generate a temporary support code.

Do not be afraid to contact Apple just because your using a hackingtosh, but only do it once you get the alert with a customer code and a request to contact Apple support. In almost all cases Apple customer support will help you with the lockout. The easiest and best way to contact Apple and to get through to the correct department is via the the Apple Support Website :-

www.apple.com/support/country/

Select your country/location and on the next page click on the 'Contact Support' link just below 'Contact Us' then on the next page click on 'Get Started':-

View attachment 127189

View attachment 127188

View attachment 127187

You will now be presented with a list of options for different Apple support departments so from here follow this path :-

• More Products and Services
• Apple ID
• Other Apple ID Topics
• Messages and Apple ID
• Talk to Apple Support Now or Schedule a Call

If you follow the above path you'll enter your OS X S/N - use the one from your SMBIOS in most cases this may help to avoid having to give the operator your OS X S/N . Once you do get through to a human explain that your having trouble with iMessage login on you Mac and that you have a customer code.

Important: Make sure your OS X S/N is valid but unregistered ..... see Chapter 4.1.

In the instance of a iMessage lockout Apple are supporting the software (OS X) and your AppleID not the hardware so you do not need a warranty. The only reason they may push for a OS X S/N is to log the support call against as that is standard procedure, try and take control of the conversation and steer it back to the iMessage customer code issue and away from the OS X S/N ... be assertive and confident.

If they continue to push for a OS X S/N You have a number of options, you could say your away from home and not in front of the Mac so you may have written down the S/N incorrectly or that you've lent it to your parents or a relative. You could say it was bought from a friend or as a used system via eBay or Crags list.

If you own a real Apple Mac then go-a-head and give them the OS X S/N from that, if its registered to you then even better and you should avoid any further discussion about the OS X S/N not being registered.

Tip: Be sure that you know what your System Type and year of manufacture is as they may ask you to confirm it ... (Eg: iMac 14,2 = 27" iMac Late 2013) you can use Mac Tracker to confirm this if your not sure.
View attachment 127186If you don't own a real Mac try giving them the S/N generated by Clover/Chameleon Wizard - of course you know its not registered so it's not going to be on their system, never, ever give them a leached OS X S/N that is not yours .... doing so could be classed as fraud.

They may ask you to confirm the S/N two or three times while they tried to find it on their system, in my case I was told to hold while they tried a 'different older system' eventually they apologised for taking so long and that there must be an issue with their system.

As stated above, the only reason they want a OS X Serial Number is because Apples help-desk system asks the operator for the OS X S/N to log the call against, in my case I was asked if I was ok with them logging the call against my AppleID, I told them thats fine and we moved on to discussing the iMessage issue.

At this point you may be asked to login into your AppleID account via the AppleID support web page and generate a temporary support pin, this is straight forward and easy to do, as long as your have a validated AppleID and at least one registered legit Apple device. If you've set up 2FA then let the operator know what your doing, it all helps to add credibility to your call.

Eventually the operator will ask you to confirm your AppleID and the Customer Code from the iMessage alert at which point it will be entered into their system and the operator should say that it accepted the code and to try logging into iMessage - if you have followed the guide correctly then you should now be up and running.

As noted above, if you have multiple devices give the operator all the customer codes, one at a time and try iMessage as each device is unlocked. I did all five of my systems in one hit.

Many users have posted very positive feedback after contacting Apple to remove the lock-out, in almost all cases they are friendly and helpful and most don't really care about the fact your using a Hackingtosh. If you want to read some positive feedback from users who have already done this take a look at posts #1043 onwards ...

If you find yourself having trouble with the call be patent and try not to give up, keep pressing the Customer Code and use my tips above, if you do falter or have been particularly unlucky with the Apple support operator you got through and you have to end the call without resolution then give it a day or so and try again, hopefully you'll get through to a different Apple support representative who will be able to help, you can even tell them that the previous attempt wasn't successful just be calm and confident.

As noted through-out the guide once iMessage is working, try to keep all your critical ID's, OS X S/N, SM-UUID, System Type, MLB, ROM .. etc the same throughout the life of the system. The easy way to do this is to keep a backup of your /Extra folder or backup your config.plist if using Clover.

View attachment 127225

End of Chapter 8 End of Guide

View attachment 127154

Hello everyone

i did a fresh yosemite install migrating to clover and using some numbers of mine it was possible to get trough verification and reached this point where i'm supposed to contact apple support to enable my iMessage service

The issue is that i'm from Argentina and i can't find the way of contacting them

If i ask for a programmed call or initiate a chat it won't be possible thus i haven't a valid OS X S/N to set it

I tried calling to brazil phone support number but i can get communicaction

Any ideas?

Thank you all!

 

[damx]

On my laptop Asus Aspire 7720G I have similar problem with FileNVRAM.dylib / Chimera 4.1.0:
whichever version of it I use the system can not boot from HDD. I have to boot from Unibeast stick and remove FileNVRAM.dylib.
Some versions of it gave me a "Memory Allocation Error", some freeze with just a blinking underscore.
After playing for two days with it I had no success.

Hi there,
So does anybody have an idea of a good combination of FileNVRAM and Chimera/Chameleon version for Yosemite? Obviously FileNVRAM should be 1.1.4, but I have not got any success with it as the hack doesn't even start to boot (blinking cursor). I have tried several recent versions of Chameleon and Chimera.
Clover works on my other builds but here on Aspire 7720G I could not make it.

 

[n2nn2n]

So I just completed a hackintosh for my wife. She was not able to log in with her AppleID. However, I was apple to log in using my ID . Hence, I knew the MLB,ROM, etc was good. The error: You cannot sign in to iMessage on this Mac at this time. Customer code: xxxx-xxxx-xxxx

There was a button: Contact Support . I clicked it, it opened a web page with the contact number and the description: Apple needs more information to complete your iMessage registration. To me, this suggested the account needed to be verified.

Called them, they asked for my SN, I acted dumb and told them I didn't have it since there was the customer code. They continued and asked about the problem. In the end, the person really didn't care and passed me on to another department. Again, this new person also asked for the serial. this time I told them the generated SN, they replied that it was invalid. I mentioned that since I was not home, my wife just texted me the SN and she might have written it down wrong. He didn't mind it being incorrect, he went ahead and verified the account using the 3 security questions. Then he asked for the Customer Code. All good now. For some reason, sometimes they still need to verify the account. Hope that helps