- Joined
- Mar 9, 2012
- Messages
- 2,894
- Motherboard
- MSI Z490 TOMAHAWK MAG
- CPU
- i7-10700K
- Graphics
- RX 580
- Mac
- Mobile Phone
Hi
Followed the "an idiots guide to iMessage". So far i have done the guide 5 times (triple checked all), with different model numbers of macs, from 2013 models to 2016 iMac, also did a full reinstall of the whole OS X and dit not help. Running a skylake 6500 i5 rig, everything works perfect except iMessage, iCloud and photos etc works fine. My rig should be very similar to an 27 iMac with skylake but that does not help.
Tried with two different apple id, with both i get the error message that i need to call the support to activate iMessage at this computer. I get the same message every time i tried, independent of id. My iMessage id are created during 2014 and 2015. I can se that if i put in wrong password then it does not work, so it is checking my data, and then blocking me actively most obviously from the servers, making a new id does not help neither i could se.
I am connecting with ethernet, e0 is working well.
Please asking for any help or advice. I can only se that most other get this to work?
Unfortunately as often said, once your rig throws up the 'Call Customer Services' there is nothing else you can do regardless of how many times you reinstall, reconfigure or change IDs. Its a very strange situation - the general consensus seems to lean towards Hacks with old and established IDs coupled with solid financial details. It was discussed here on the forum by one individual some posts back that once those details are logged by Apple it seems ROM, MLB and other injected values doesn't matter, at which point I thought they were talking rot. To prove his theory I did a fresh install on a test rig with only a s/n injected and was abled to instantly login to All Apple Services with my ID - iMsg/F-Time, iTunes, iCloud, App Store plus was abled to setup 'Continuity' between the Hack and other devices.
I must admit I had to climb down from my very limited knowledgeable high horse and admit they were right in their findings which completely threw a spanner in the mix of correct and properly injected values as per the 'Fix iMessage' guide which is still the right way to go. In conclusion one can only surmise that established and verified Apple IDs coupled with solid financial details carry more sway on a new hack. Not wanting to sound smug or condescending but now when I am testing new updates or upgrades on a test rig before putting them on my regular day to day rigs, I don't pay much attention to getting and injecting correct values just using the Generic ones and my Apple ID, I can login to all the services without the need to call Apple.
To reiterate again you need to call Apple with the code - see the GUIDE how to conduct the call. Good luck.