Contribute
Register

jaymonkey

Moderator
Joined
Aug 27, 2011
Messages
3,856
Motherboard
ASRock-Z97 EX6
CPU
i7-4790K OC @ 4.8GHz
Graphics
Vega 64LC + HD4600
Mac
  1. MacBook Air
  2. MacBook Pro
Mobile Phone
  1. Android
  2. iOS
hello heryts
i have been used your MLB and ROM value.
i'm block my iMessage login today.

how can it find MLB, ROM value for using iMessage?

@sherlocks,

Do not used leached/shared MLB & ROM values, it will only lead to more problems, please see Part-1, step-5d of the guide on how to check and set your MLB & ROM correctly.

Cheers
Jay
 

jaymonkey

Moderator
Joined
Aug 27, 2011
Messages
3,856
Motherboard
ASRock-Z97 EX6
CPU
i7-4790K OC @ 4.8GHz
Graphics
Vega 64LC + HD4600
Mac
  1. MacBook Air
  2. MacBook Pro
Mobile Phone
  1. Android
  2. iOS
Thanks Jay for the detailed Clover steps!. Can/Should I test iMessage with my current AppleID or should a create another one for testing. Thinking this will not lockout my main installation again?

@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
 
Joined
Sep 26, 2013
Messages
5
Motherboard
GA-Z87X-UD3H
CPU
Intel Core i7-4770K
Graphics
Asus GTX680-DC2O-2GD5
Mac
  1. MacBook Pro
  2. Mac Pro
Classic Mac
Mobile Phone
  1. iOS
I remember the day that thread only had one page. iMessage worked fine for me. But now all of a sudden I'm getting the message that asks me to call Apple (with a "Customer Code"). imessage_debug gives me the same value after a reboot… Nothing changed on my end. Any ideas on how to fix this?
 
Joined
Mar 24, 2014
Messages
13
Motherboard
GA-Z87X-UD4H
CPU
i7-4770K OC 4.2Ghz
Graphics
ASUS GTX 770 2gb
Mac
Classic Mac
Mobile Phone
  1. iOS
Any thoughts on what to say to Apple once you call? I've unsuccessfully called 3 times, and each time they have said they don't see what's wrong on their side and it should work. I get the message to call with the Customer Code, and when I mention I have the customer code to give them, they behave as if they don't need that info or don't know what that is.
 

jaymonkey

Moderator
Joined
Aug 27, 2011
Messages
3,856
Motherboard
ASRock-Z97 EX6
CPU
i7-4790K OC @ 4.8GHz
Graphics
Vega 64LC + HD4600
Mac
  1. MacBook Air
  2. MacBook Pro
Mobile Phone
  1. Android
  2. iOS
I remember the day that thread only had one page. iMessage worked fine for me. But now all of a sudden I'm getting the message that asks me to call Apple (with a "Customer Code"). imessage_debug gives me the same value after a reboot… Nothing changed on my end. Any ideas on how to fix this?

@kaboon,

If MLB & ROM are ok and you get persistent values (see Part-1, step-5d) then check your S/N & System Type, many people change their System Type (Mac Pro 3,1, iMac 13,1 .. etc) without changing their S/N .... the first two digits of the S/N also identify the System Type and must be changed together. If your using Mac Pro 3,1 then try iMac 13,1. Mac Pro 3,1 & 6,1 have a 11 digit serial number which seems to cause issues with newer hardware, newer Mac's have a 12 digit S/N - see Part-1, Step-5d of the guide for more info.

Apple have been forcing logouts on AppleID devices that look like they have a S/N or SmUUID miss-match, when you log-back-in if the MLB and/or ROM value has changed from the first time you registered with the iCloud then a miss-match is detected and you'll get the contact Apple alert with a customer code, which is fine and can be un-blocked by calling Apple as long as S/N, SmUUID, MLB & ROM are all ok, if not you'll get kicked out again soon. All the answers are in the guide .....

Any thoughts on what to say to Apple once you call? I've unsuccessfully called 3 times, and each time they have said they don't see what's wrong on their side and it should work. I get the message to call with the Customer Code, and when I mention I have the customer code to give them, they behave as if they don't need that info or don't know what that is.

@tadoan,

Before trying again check your S/N (see above), SmUUID (see Part-2), MLB & ROM (see Part-1, Step 5d) if all looks ok try following the advice in Part-2, Step-8 of the guide to contact Apple - it's worked multiple times for me and many others, You need to make sure you get through to MAC OSX, iMessage/AppleID support - don't use the link in the on the Alert Box try my method in Step-8 and let me know how you get on.

Cheers
Jay
 
Joined
Oct 12, 2011
Messages
16
Motherboard
GA-Z87X-UD5H
CPU
Core i7-4790 3.6Ghz
Graphics
GTX 980 4GB
Mac
  1. MacBook Air
Mobile Phone
  1. Android
  2. iOS
I called Apple support 15 minutes ago and they were super helpful. I even told the guy that I had been using my mackintosh for 3 years without any problems, but the recent security measures rendered my iMessage inactive. I gave him the 12 digit customer code iMessage gives you when you can`t log in, and he fixed it in a minute, and immediately after he told me it was sorted, I could log in.

All I can tell you is, don`t be afraid to call them if you get the customer code error message, they`ll surely help you if you have more apple devices under your account.
 
Joined
Mar 24, 2014
Messages
13
Motherboard
GA-Z87X-UD4H
CPU
i7-4770K OC 4.2Ghz
Graphics
ASUS GTX 770 2gb
Mac
Classic Mac
Mobile Phone
  1. iOS
@tadoan,

Before trying again check your S/N (see above), SmUUID (see Part-2), MLB & ROM (see Part-1, Step 5d) if all looks ok try following the advice in Part-2, Step-8 of the guide to contact Apple - it's worked multiple times for me and many others, You need to make sure you get through to MAC OSX, iMessage/AppleID support - don't use the link in the on the Alert Box try my method in Step-8 and let me know how you get on.

Cheers
Jay

Ok, Thanks! I'll give that a try and will update with my progress.
 
Joined
Mar 24, 2014
Messages
13
Motherboard
GA-Z87X-UD4H
CPU
i7-4770K OC 4.2Ghz
Graphics
ASUS GTX 770 2gb
Mac
Classic Mac
Mobile Phone
  1. iOS
So the "Contact Apple Support" link worked well and got me to the correct department. Verified my Apple ID, phone number and tried to get a SN from me, but I said I wasn't in front of my Mac. Gave them the Customer Code, and within seconds, she said it was taken care of for me. SWEET and painless. Thanks!

F/U question: how long should I give it before trying to log back into iMessage?

FYI: ROM/MLB persistent confirmed with 2 reboots. Chameleon v2283 NVRam 1.1.3 worked well.

update: Log in successful for FaceTime and completes calls. iMessage logs in, but won't let me send messages; has red font contacts and won't send. Account settings in iMessage looks like this:
Screen Shot 2014-09-10 at 1.11.36 PM.png

Any thoughts?
 
Joined
Jul 29, 2014
Messages
132
Motherboard
GA-Z87X-UD5H
CPU
i7-4770K
Graphics
RX 580
Mac
  1. MacBook
  2. MacBook Air
Classic Mac
  1. PowerBook
Mobile Phone
  1. iOS
Customer support fail.

I followed the extremely helpful guide (part 2, step 8) - thank you! However things didn't go well on the Customer Support side. The first guy transferred me to the wrong (iOS) department. After taking down my customer code and other info, they transferred me to the computer support.

They wanted my Serial Number, but I said I wasn't in front of my computer. I said that I had written the SN down, but there had been a problem with it when I called the day before. I asked if he wanted the number I had written down - he did not. He directed me to delete the chat.plist in preferences of the hidden user library. He said he was "85%" confident that was the problem. [No, it didn't help]

I also asked if there were any other possible causes for the problem, whether there was a generic hold on the account, new security measures, etc. No, he was convinced it was a problem with my machine, and related to my newly changed password... even though I explained that I changed the password *after* the problem started, that this message to contact customer support was *not* the same that I've seen before when my password is mismatched, etc. [My alert matches the screenshots people have been showing]

I then (rather stupidly) asked if it would matter if the computer in question was a Hackintosh, and he said yes it would, that the problem wouldn't be supported and they wouldn't help further. Hopefully he didn't make a note of that, but my guess is that he did. So... yeah.

Any thoughts or suggestions?

[on edit]
It appears that my ROM and MLB numbers are changing, so that's (at least part of) my problem.

Clover sounds like the easiest/best solution in the long run, but all the guides I'm finding are in the context of performing a clean install of the OSX.

Question 1: Is it possible to switch over to Clover on an existing OSX build?
Question 2: Are there any guides to this effect? (or can I just follow the Clover Guide and jump in at, say, "Step 4: Post-Installation"?

If it's not possible, then presumably my only option is to go the Chameleon route?
 
Last edited:

jaymonkey

Moderator
Joined
Aug 27, 2011
Messages
3,856
Motherboard
ASRock-Z97 EX6
CPU
i7-4790K OC @ 4.8GHz
Graphics
Vega 64LC + HD4600
Mac
  1. MacBook Air
  2. MacBook Pro
Mobile Phone
  1. Android
  2. iOS
update: Log in successful for FaceTime and completes calls. iMessage logs in, but won't let me send messages; has red font contacts and won't send.

@tadoan,

Check your console log when opening iMessage, red contact's are usually caused by iMessage authentication issues which is usually down to an invalid or black-listed hardware (platform) UUID which is a result of a bad SmUUID (SystemId) - Read part 2 of the guide which explains all of this in detail.

Check if your BIOS suffers from the SId bug.

What motherboard are you using ?, I have a list of Motherboard's that are confirmed to suffer from the SId bug in Part-2, if you suspect yours let me know and I can add it to the list if its not already on there.

Cheers
Jay
 
Top