How to Fix iMessage

[b0bbyd33]

For example, someone using Chimera will have the MLB/Rom changing on every reboot and that causes iMessage not to work as it see too many Macs login in on every reboot and blocking your account due to that.

That's the theory anyway

There's more to it than that, I did my best to trigger the message on a real mac, I literally logged in to iMessage on as many different Macs I could find at work, and succeeded every time. There is possibly a limit to the number of "unknown" Macs (ie. serial numbers that Apple doesn't recognize). Hopefully though its an algorithm for valid MLBs so we can get back on iMessage without cloning a real mac MLB.

 

[tovkal]

Maybe there is something in the application itself that is different. Apple has changed its way of iCloud 2 years ago and, from my research, Messages (iMessage)/Facetime has to talk with iCloud differently. Unfortunately, I am not a coder at all. I am still a noob in the Hackintoshing and wonder if someone can find the differences in the coding between when Messages was hackable and now.

New stuff was added with Yosemite for sure, like SMS forwarding. And with that, security must have been tightened because someone with an Apple ID could use it to bypass two factor authentication that send a code via SMS, for example.

 

[xnaron]

Here's what I did just to give it a try.
1. created a new user in my hackintosh
2. created new Apple ID during log in with new user (so I hope to keep mine safe)
2a. Disconnected ethernet cable
3. Got into clover configuration and injected new sn, same model, etc. Shut down, and on again
4. Used clover configurator to calculate ROM and MLB
5. Infected Those values and just took 4 numbers out from the middle of MLB.
6. Shut down ant start again.
6a. Connected ethernet cable
7. Started iMessage, automatically logged in. Was able to send some iMessages to friends and were received.

What I'll do next is try changing all the info in my original account as it was a new Mac. I'll let you guys know how it goes.

For step 4, when you say you took 4 numbers out from the middle to make the 17char MLB 13chars.... Which 4 numbers? What position did you start at to take them out?

Lets pretend this, obviously invalid MLB, is the 17 char MLB: ABCDEFGHIJKLMNOPQ

Which 4 letters did you remove?

thanks

 

[cap2587]

I would go with removing GHIJ! That is 6 letters before and 7 letters after. Just a guess on my part.

 

[RideTheCliche]

Apple knows the model and basic spec of every one of their machines with a serial number.

If you attempt an iMessage login using a valid S/N, which belongs to a supported Mac, you're golden. However if you create a 'collision' of the same serial number (security token) on another machine, well that's not supposed to happen! Only one serial number can possibly exist, so iMessage goes kaboom and you have to phone up the mother ship. That 12 digit code has enough information about your system to give a support rep a good guess about whether or not you're on a real Mac or a Hackintosh.

They want people who don't own a Mac off their network, but they don't want to overly **** off owners of unsupported Macs or other edge cases. I can't say I blame them - I've been messing with Hackintoshes since MSI Wind U100 was the latest craze, but I don't expect to be able to use Apple's online services for free.

~RTC

 

[Humanate]

I would go with removing GHIJ! That is 6 letters before and 7 letters after. Just a guess on my part.

I would go with D,I,K,S - Just a guess

 

[flicka]

Apple knows the model and basic spec of every one of their machines with a serial number.

If you attempt an iMessage login using a valid S/N, which belongs to a supported Mac, you're golden.

~RTC

That's not true, I can assure that an attempt with a real Mac S/N but Bad/Wrong MLB/ROM will fail.
But people are working on a method to have a working Hack with custom S/N MLB and ROM, not from a real Mac and no needs to call Apple support.
Never minds naïf trial and error

 

[johnap987]

For step 4, when you say you took 4 numbers out from the middle to make the 17char MLB 13chars.... Which 4 numbers? What position did you start at to take them out?

Lets pretend this, obviously invalid MLB, is the 17 char MLB: ABCDEFGHIJKLMNOPQ

Which 4 letters did you remove?

thanks

I took 4 numbers from the middle, not letters. In the end l don't think it really matters. When I tried using my Apple ID I got the contact Apple message. Started reading other sites and forums and there's a lot more about S/N and MLB. I think I'm not allow to put those links here, but you can easly find it through Google.
2010 and before models use 11 digit SN and 13 digit MLB. Newer models use 12 digit SN and 17 digit MLB. As SN, MLB has logic to it, like manufactured date, place, part model, etc, etc.
Therefore, using random numbers or deleting random numbers in Clover generated MLB will probably end up failing sooner or later. Actually I found out, that clover generated exactly the same MLB in another hack (obviously this other hack uses a different SN, ROM, etc). So this MLB is probably blacklisted by Apple servers, and probably just works temporarily. And probably is the same MLB a few of us have used (it was a big surprise for me to see the exact same MLB I got a few days ago, when I ran iMessage debug to extract the MLB in this other hack).
There's work being done to make a MLB generator tool. I'm not part of it, but seems it is going to be out soon (just my guess).
Personally I'm trying to generate my own MLB, ROM and SN, with all the info gather in this and other websites.
If that fails I may try to get the 13 MLB working by calling Apple in my Apple ID.

 

[iDVD]

I have working Messages about a month, now after one of restarts, login to my account then I start Messages and it was log out. I try to log in, but I got Customer Code error.
Data from iMessage_debug are the same before and after restart.

Any progress to fix Messages?

 

[joppez]

Same thing here. Stayed at Mavericks and never upgraded to Yosemite and iMessage has been working since I called Apple a few weeeks ago.

However, two days ago it failed again and I am now shown a dialog with a customer code when I try to login. The utility imessage_debug is showing exactly the same information now as it did when it was working.