Contribute
Register

How to Fix iMessage

Joined
Oct 30, 2014
Messages
10
Motherboard
ASUS 74SX OSX 10.9.5
CPU
i7 2670qm
Graphics
NVidia 560M
Mac
MacBook Pro
Just an update....

I finally got iMessage to work!

I too was having the same issues as all of you where the unlock code wasn't working even with numerous attempts by the support staff.

I got a buddy to run the iMessage debugger on his mac. I kept my generated SN, used his MLB/ROB however I only changed the last 12 digits of the MLB (SMUUID) to match what he had.

I logged out of everything I, rebooted verified the values matched using the new config.plist I edited. Restarted again this time plugged into the network. Got the mail, iCloud log in message and logged in. I started iMessage, logged in and it took about 1-2 minutes but I finally got logged into the server and tested iMessage with success.

Long story longer, apple seems to have a new algorithm to check the MLB/ROM values to ensure they were generated.

I will say I noticed the MLB final 5 digits were all alpha characters with no numbers what so ever. Id try generating a new MLB with the last 5 digits all letters (i.e 123-ABCDE).

I don't want to change it to find out if different letter values work and get my working iMessages now broken and worse yet blacklist my buddies legit setup.

Good Luck!
Pat
 
Joined
Jun 11, 2012
Messages
45
Motherboard
GIGABYTE GA-Z87X-OC
CPU
i7-4770k
Graphics
GIGABYTE GV-N770WF3-4GD
Mac
iMac
Classic Mac
Mobile Phone
iOS
I just want to confirm that if I use MLB & ROM from my MACbook pro for my hack I still have to call Apple up? Do I need to change SmUUID & SN or can I just leave as is? Thanks!
I would love to say yes 100%. However, it is possible that the Apple ID in question may also be part of the lockout equation. If you decide to try it, remember that the Product ID seems to need to be the same as the Product ID from the MLB and ROM.

My advice at this time, is to wait for Jay to chime in and see if there is indeed a consensus as how to proceed forward. No question in my mind that the more used and abused the ID in terms of attempts, the less likely it is for iMessage to function.

The next concern is for those who have functional iMessage, on whether or not they will loose functionality down the road. I think not. For those who do brand new installs, with known working good config.plists from Clover, I fear that they will no longer unlock without valid MLB and ROMS.
 
Joined
Oct 30, 2014
Messages
10
Motherboard
ASUS 74SX OSX 10.9.5
CPU
i7 2670qm
Graphics
NVidia 560M
Mac
MacBook Pro
I just want to confirm that if I use MLB & ROM from my MACbook pro for my hack I still have to call Apple up? Do I need to change SmUUID & SN or can I just leave as is? Thanks!
Just to directly answer your question and clarify my experience for anyone else wondering. I didn't have to call Apple back to remove the reg block again. I called a few days ago and got stuck with the same customer code however changing my MLB/ROM values made it work with no further contact from Apple.

It seems that once you get it unblocked once, it stays unlocked, at least for the sat 3 days (my last attempt to unlock my reg block with no success)

Good Luck!
Pat
 
Joined
Mar 24, 2014
Messages
6
Motherboard
10.8
CPU
1055t
Graphics
6870
Mac
Classic Mac
Mobile Phone
Just an update....

I finally got iMessage to work!

I too was having the same issues as all of you where the unlock code wasn't working even with numerous attempts by the support staff.

I got a buddy to run the iMessage debugger on his mac. I kept my generated SN, used his MLB/ROB however I only changed the last 12 digits of the MLB (SMUUID) to match what he had.

I logged out of everything I, rebooted verified the values matched using the new config.plist I edited. Restarted again this time plugged into the network. Got the mail, iCloud log in message and logged in. I started iMessage, logged in and it took about 1-2 minutes but I finally got logged into the server and tested iMessage with success.

Long story longer, apple seems to have a new algorithm to check the MLB/ROM values to ensure they were generated.

I will say I noticed the MLB final 5 digits were all alpha characters with no numbers what so ever. Id try generating a new MLB with the last 5 digits all letters (i.e 123-ABCDE).

I don't want to change it to find out if different letter values work and get my working iMessages now broken and worse yet blacklist my buddies legit setup.

Good Luck!
Pat

Hi I suffer from the contact apple problems this morning and I try your method to change the MLB last characters and this MLB this my is from real mac but it show contact apple alert again But these days apple check mlb/rom pair strict
 
Joined
Mar 10, 2013
Messages
38
Motherboard
GA-Z77X-UP5 TH
CPU
Intel Core i5-3570K
Graphics
nVidia GTX 560
Mac
Classic Mac
Mobile Phone
Thanks for all the help guys. However, I just bought a Mac Pro because I couldnt deal with this anymore.
 
Joined
Jan 20, 2012
Messages
60
Motherboard
MSI Z77A-G43
CPU
i5 2500K
Graphics
GTX 970
Mac
MacBook Pro
Classic Mac
Mobile Phone
iOS
Just an update....

I finally got iMessage to work!

I too was having the same issues as all of you where the unlock code wasn't working even with numerous attempts by the support staff.

I got a buddy to run the iMessage debugger on his mac. I kept my generated SN, used his MLB/ROB however I only changed the last 12 digits of the MLB (SMUUID) to match what he had.

I logged out of everything I, rebooted verified the values matched using the new config.plist I edited. Restarted again this time plugged into the network. Got the mail, iCloud log in message and logged in. I started iMessage, logged in and it took about 1-2 minutes but I finally got logged into the server and tested iMessage with success.

Long story longer, apple seems to have a new algorithm to check the MLB/ROM values to ensure they were generated.

I will say I noticed the MLB final 5 digits were all alpha characters with no numbers what so ever. Id try generating a new MLB with the last 5 digits all letters (i.e 123-ABCDE).

I don't want to change it to find out if different letter values work and get my working iMessages now broken and worse yet blacklist my buddies legit setup.

Good Luck!
Pat
Just want to add that my Macbook's MLB has some numbers at the end, so it's not letters only.
 
Joined
Jan 20, 2012
Messages
60
Motherboard
MSI Z77A-G43
CPU
i5 2500K
Graphics
GTX 970
Mac
MacBook Pro
Classic Mac
Mobile Phone
iOS
Nice joke.....
Well, some people use a hackintosh to work, and might get tired of the limitations hackintosh have sometimes. And after the Mac Pro refresh last year, a lot of people moved from a hack to the can.


---

So from barracudamuscle's posts, it appears that with a real MLB and ROM values it works. What happens if you use only a real one and the other is randomly generated?
 
Joined
Jun 24, 2011
Messages
221
Motherboard
HP Elite Book 840 G1 - Clover
CPU
i5-4300U
Graphics
HD 4400, 1366 x 768
Mac
MacBook Pro, Mac Pro
Mobile Phone
iOS
can someone tell me how to get real MLB and ROM from real Mac?
 
Joined
Jan 7, 2012
Messages
21
Motherboard
OSX 10.10 on ProBook 4730
CPU
Intel Core i5-2410M
Graphics
Intel HD 3000 on 1920x1080 17" screen
Mac
Classic Mac
Mobile Phone
Here's my story with iMessage so far:

I've got a unique S/N and generated a random SmUUID. AppleId is verified but I got the message "You're AppleID can't be used....blabla" with the customer code.

So today I called the support. The first staff said he unblocked the account after naming my name, AppleID and S/N, but I still couldn't log in to iMessage. Of course there also was a problem with the S/N (he couldn't find it). He forwarded me to a more technical staff who wanted to know my three security questions as well as AppleID, name and S/N. I think he tried the same thing as the first staff (remove the blockage in some database) so I had no luck with this guy either.
He then forwarded me to a more superior staff who now wanted to directly solve the problem on my "macbook" via remote access. Of course that scared me a little but I followed his advice and gave him access to my probook (The good thing is, it's you who is doing all the actions. The staff just points with a cursor where you should click next).

He reproduced the error and now we created an iCloud alias for my AppleID by going into system preferences -> iCloud. Then I tried to login with the alias@icloud.com ID and it finally worked!
Everything was working, Facetime, iMessage, Updates via Appstore etc.

The sad thing is: Now that I was able to do system updates through the AppStore, I made the update from 10.10 to 10.10.1 and now I get the message again :clap::banghead:

Well I'll try to contact the support again next week... my hopes are low.
 
Top