How to Fix iMessage

[Ikyo]

I had the SAME exact problem. SOME apple IDs will work on the hackintosh, but other ones won't. ALL of the IDs have credit cards on them.

This is an Apple server side problem.

Some Apple IDs are practically blacklisted no matter if you add a CC and also adding it to a legitimate device.

edit: ONE THING I NOTICED WITH THE WORKING ACCOUNTS IS THAT THEY HAVE @ICLOUD.COM ADDRESSES LINKED TO THEM. YOU CAN ADD AN ICLOUD ADDRESS TO YOUR REGULAR APPLE ID BY GOING INTO iOS -> Mail -> iCloud Mail -> Create iCloud e-Mail address. Then try logging in. Also add a CC if you haven't already. Also, call into Apple again to input the validation code.

Having an @icloud.com email address may be the missing link.

I have tried both and it doesn't work. The strange thing I found was when trying to use my icloud/me email--it seems to login for a second then kick me out.

 

[luja]

Hello,
my smUUID is not consistent through multiple reboots which i check by running iMessage debug after every reboot. ROM, MLB and other values are constant but smUUId is different anytime i reboot. Is that normal or i have to do something? Ty.

 

[Mernie]

I am having a strange issue. I contacted Apple tier 2 support and did everything they suggested. Nothing worked on my account. I even deleted all of the iMessage information to see if that helped. With my account I keep getting the call apple error. When I use my wife's account, it logs in and everything works perfectly fine on the same machine. I can even trick the machine by using the alternate email address on my iCloud account. It will login then pop up the error. Is it something to do with my iCloud account just being banned?

I have tried both and it doesn't work. The strange thing I found was when trying to use my icloud/me email--it seems to login for a second then kick me out.

Right – it's an Apple server activation issue – even when you call into Apple customer support and give them the "customer code" to whitelist the ID, it still won't work. Maybe the IDs are just blacklisted.

 

[esafeddie]

Hello,
my smUUID is not consistent through multiple reboots which i check by running iMessage debug after every reboot. ROM, MLB and other values are constant but smUUId is different anytime i reboot. Is that normal or i have to do something? Ty.

According to one poster, these values are not needed, or possibly pointless in getting iMessage and/or F-Time to function on a hack. It's all to do with your Apple ID, I am sure he can point you in the right direction - Good luck.

 

[Ikyo]

Right – it's an Apple server activation issue – even when you call into Apple customer support and give them the "customer code" to whitelist the ID, it still won't work. Maybe the IDs are just blacklisted.

Are you referring to my Apple ID? I am guessing that is possible, but it wouldn't add up to why it works on my other devices. I guess I might need to build another hack and try it on there.

 

[esafeddie]

There are some very important points to remember when trying to activate iMessage, F-Time, iCloud etc on a hack - Despite the misleading info by some individuals the below listed factors plays an important role in a successful logon.
1. A generated Mac s/n (not cloned or listed as registered by Apple in their data base)
2. A generated SmUUID value, ROM value and a MLB value
3. NvRAM - iMessage uses some of the key values stored in NVRAM during login and authentication to Apples iMessage servers. If certain keys are not saved in NVRAM then the next time the system is powered off or re-booted iMessage may suffer from login and/or activation problems.
4. All injected values must remain constant between reboots (very important for #3).
5. Unsuccessful logons - iMsg cache folders should be deleted as they maybe sending corrupt data to Apple servers.
6. Apple ID's must now include some sort of financial detail integrated into your account so that the hack can be issued with a Security Token at logon.
7. Constant changing of financial details can and will have an impact on an Apple ID account.

This just a check list that one should bear in mind apart from the ones compiled in the 'Fix iMessage' guide.

 

[Ikyo]

There are some very important points to remember when trying to activate iMessage, F-Time, iCloud etc on a hack - Despite the misleading info by some individuals the below listed factors plays an important role in a successful logon.
1. A generated Mac s/n (not cloned or listed as registered by Apple in their data base)
2. A generated SmUUID value, ROM value and a MLB value
3. NvRAM - iMessage uses some of the key values stored in NVRAM during login and authentication to Apples iMessage servers. If certain keys are not saved in NVRAM then the next time the system is powered off or re-booted iMessage may suffer from login and/or activation problems.
4. All injected values must remain constant between reboots (very important for #3).
5. Unsuccessful logons - iMsg cache folders should be deleted as they maybe sending corrupt data to Apple servers.
6. Apple ID's must now include some sort of financial detail integrated into your account so that the hack can be issued with a Security Token at logon.
7. Constant changing of financial details can and will have an impact on an Apple ID account.

This just a check list that one should bear in mind apart from the ones compiled in the 'Fix iMessage' guide.

I will check tonight because I just put a credit card on my account.

 

[luja]

According to one poster, these values are not needed, or possibly pointless in getting iMessage and/or F-Time to function on a hack. It's all to do with your Apple ID, I am sure he can point you in the right direction - Good luck.

Is that a joke....My Apple ID is fine...if some1 can help me about thing i asked hes wellcome( so my question is how to make constant smUUId and not different anytime i reboot or is it normal)...i dont like treatise between forum members here, ty.

 

[davelaw56]

Never had problem with iMessage and FaceTime since I took the time to carefully read the entire post over and over again. it really is straight forward once you read it all. I always succeeded login in on any customac with any account for any body without any problem since I'm following the post...Something really new happened to me though... For some reason one account I have just lately created for someone else won't login on any customac. Apple customer code (as usual). On iOS devices, no problem, it logs in successfully... The account has a credit card linked to it and has only an iCloud email address. The person doesn't have any iOS devices so I used an old one of mine (old iPhone) to verify if the account could log in. My personal account logs in successfully on those same customacs and devices... So values are good and persistant. I'm guessing the apple ID is, for some strange reason, going through some verification process. Kind of strange since it has been almost a week now... I'll wait, verify and report back...

 

[esafeddie]

@ Davelaw56 - The common denominator here is the Apple ID, it has been flagged for some reason on the Server. Was it created with the 'Two Step Verification' option? If not try that route. Unfortunately you will have to call Apple and say - 'I am having a problem logging in with my ID' they will ask some security details, do not mention about a particular device because they will ask for s/n for that device just stick to ID problem logon. They will then remove the block on the ID.