How to Fix iMessage

[viking1304]

That's right, I'm getting the second message with the same customer code on every boot, shown in my attachment. I'm able to sign into another Apple ID on the same system, so FaceTime and Messages are working properly, but my personal Apple ID is the main problem for me. My messages account is inactive, so sending messages is pretty fruitless.

Wellcome to the twilight zone. At least I am not alone anymore.

I cannot use nor my ID, nor my sons ID. My ID is used on my iPhone, his ID is used on his iPhone. iMessage and Facetime works on both phones, none of them doesn't work on two different installs with different set of serials on this laptop. My ID works without any problem on my friends real MacBook.

I managed to login with my friends ID few days ago, but unfortunately I didn't checked if I can send messages or if my status is Inactive.

 

[hackinandrackin]

Wellcome to the twilight zone. At least I am not alone anymore.

I cannot use nor my ID, nor my sons ID. My ID is used on my iPhone, his ID is used on his iPhone. iMessage and Facetime works on both phones, none of them doesn't work on two different installs with different set of serials on this laptop. My ID works without any problem on my friends real MacBook.

I managed to login with my friends ID few days ago, but unfortunately I didn't checked if I can send messages or if my status is Inactive.

I'm facing the exact same problem then :/, I asked a friend at his garage to sign into iMessage on his MacBook Pro and it worked flawlessly, yet on my hackintosh I'm still faced with the same problem. The hardest thing is that I'm unable to pinpoint the exact problem with this, so it's flabbergasting on how to fix it in the first place.

If it helps, I'm using a MLB value from a dead logic board on a MacBook Pro.

 

[viking1304]

I'm facing the exact same problem then :/, I asked a friend at his garage to sign into iMessage on his MacBook Pro and it worked flawlessly, yet on my hackintosh I'm still faced with the same problem. The hardest thing is that I'm unable to pinpoint the exact problem with this, so it's flabbergasting on how to fix it in the first place.

If it helps, I'm using a MLB value from a dead logic board on a MacBook Pro.

If you have desktop system identified as iMac as you wrote in your details, but you are using cloned MacBook Pro MLB serial, it might be a source of your problem. You should not use cloned MLB from real laptop in your desktop hack system. It's not important if that board is dead or not if that value is checked against database of known MLBs, since there is no way to have laptop motherboard in desktop system. I have no idea if that check is made or not, but I know that using of cloned values is not recommended:

Update-2: Feb 2015 - It would appear that Apple have now relaxed the level of MLB verification allowing the use of basic generated MLB's as detailed in this chapter, however cloned values will still cause issues.

I guess that only safe way of using cloned IDs would be to use all of them and to be sure that original Mac would not be used anymore.

 

[hackinandrackin]

If you have desktop system identified as iMac as you wrote in your details, but you are using cloned MacBook Pro MLB serial, it might be a source of your problem. You should not use cloned MLB from real laptop in your desktop hack system. It's not important if that board is dead or not if that value is checked against database of known MLBs, since there is no way to have laptop motherboard in desktop system. I have no idea if that check is made or not, but I know that using of cloned values is not recommended:



I guess that only safe way of using cloned IDs would be to use all of them and to be sure that original Mac would not be used anymore.

I don't think it's a problem to use that MLB, since FaceTime and Messages still work properly, so it means that I'm still properly connecting to Apple's servers, and the MacBook is dead and isn't connecting to any servers for good, but I've tried generated MLBs and they produce the exact same result, except a different customer code.

 

[Sniki]

I don't think it's a problem to use that MLB, since FaceTime and Messages still work properly, so it means that I'm still properly connecting to Apple's servers, and the MacBook is dead and isn't connecting to any servers for good, but I've tried generated MLBs and they produce the exact same result, except a different customer code.

I agree with you on this part, from my 3 year experience on hackintosh i fixed everything else but iMesssage until a friend gave me his values.
No matter how many times i tried, i was just getting another customer code, i even called apple support and they said that the fixed but it never worked.
I finally got it working after a friend/colleague at work gaved me his macbookpro id's since he works as a DJ and never uses any single apple services.

I only used his MLB and ROM and generated my Serial Number & UUID and it worked on first try.

Maybe we might need to study more how MLB & ROM pairing works, i tried all the existing variants like:
Just using his ROM and generating my MLB - it didn't work
Tried using his MLB & Generating my ROM - it didn't work.
From my 3 year experience and endless attempt i can confirm that the only Valid IDs required for you to have working iMessage and FaceTime are MLB & Rom (ofc serial number has to be valid format & but it doesn't matter what type it is)
You can generate thousands of UUID & Serial Number and use the working MLB & Rom, it will always work.

Maybe someone 1 day will come up with an idea on how MLB & Rom works as a pair or how they must match with each other.

 

[hackinandrackin]

I agree with you on this part, from my 3 year experience on hackintosh i fixed everything else but iMesssage until a friend gave me his values.
No matter how many times i tried, i was just getting another customer code, i even called apple support and they said that the fixed but it never worked.
I finally got it working after a friend/colleague at work gaved me his macbookpro id's since he works as a DJ and never uses any single apple services.

I only used his MLB and ROM and generated my Serial Number & UUID and it worked on first try.

Maybe we might need to study more how MLB & ROM pairing works, i tried all the existing variants like:
Just using his ROM and generating my MLB - it didn't work
Tried using his MLB & Generating my ROM - it didn't work.
From my 3 year experience and endless attempt i can confirm that the only Valid IDs required for you to have working iMessage and FaceTime are MLB & Rom (ofc serial number has to be valid format & but it doesn't matter what type it is)
You can generate thousands of UUID & Serial Number and use the working MLB & Rom, it will always work.

Maybe someone 1 day will come up with an idea on how MLB & Rom works as a pair or how they must match with each other.

Just a question, how did you get the ROM value from his MacBook? I only have this dead MacBook Pro, so if there's anyway on getting that ROM value, please let me know.

 

[Sniki]

Well he brought his MacBook Pro to work and i dumped his values with iMessageDebug and Clover Configurator.
From a dead Macbook Pro, i have no idea.

 

[viking1304]

'I learned that really old Apple ID's do not need a valid MLB / ROM to work'

Man Ive been saying that for a long time because I have seen that pattern since apple introduced the two step verification security check which is a PITA at times. No matter how many times I've clean installed which I prefer to do, logging into iMsg/F-Time never throws a code to call apple, my ID is as old as the hills. New IDs' has a greater chance of failure specially on new or first time builds.

Ouch! If this is true, it's very obvious why I have a problem. None of my AppleIDs is older than one year.

Looks like MLB and ROM must have been paired after all.

It also looks like those with accounts which are old enough can use any MLB and ROM value, as long as they are in correct format, and that's why people with older accounts do not have any issue with any of those tutorials with generated values.

Rest of us can only call Apple and hope that they will fix an issue for us or give up.

Using cloned values from the net is out of question, since at least 100 other people will have same "strike of a genius" idea. I do not know anyone with a "spare" Mac who can "donate" his MLB/ROM to me, so cloning is not an option for me.

I guess I need to reset all iMessage preferences and cache and to ask some of my friends with an older account to access my laptop over TeamViewer and to try to log in to iMessage. If that is working, I guess I will need to call Apple, since looks like there is no other way to fix this.

 

[DaveSuriano]

I always get this warning and I've done 1000 tests. those of the apple say there is no blockage.
I followed the guide to perfection. I do not know what to do.

 

[viking1304]

I created completely new set of serials (OS, MLB, ROM and SmUUID) and reinstalled everything from scratch, but I didn't try to use any of my family accounts.

I asked my friend who have AppleID that was created in 2013 to sign in to iCloud, iMessage and FaceTime on this new installation. Everything worked like a charm in first attempt. He was able to send and receive messages and he called me on my iPhone over FaceTime without any problem.

He logged off and then I tried to use my account. I instantly got a message to call support. It was same with my sons account. My sons account was mad in 2016 and mine is from 2017. Our accounts work on iPhone and real Macs, but not on any hack.

So, people with new accounts are probably doomed.