- Jan 17, 2017
- Gigabyte Z170X-Designaire
- Intel Core i7 6700k
- MSI GTX 1080 Aero
Oh my!!!! It seems we are slowly creeping back to the bad old days of Cloning genuine Mac values to get iMsg/F-Time working on our Hacks. I don't want to come across as some pretend Apple wizard or authority on the subject and I do understand the frustrations but Cloning is absolutely WRONG and sooner or later will lead to tears for both genuine Mac and hack, also worst case scenario all connected Apple ID's being blocked.
The only time cloned values should be used and I reluctantly say this, is if the cloned Apple machine will never connect to any Apple services, preferably never ever connecting to the internet. If you think that I am just scare mongering, please read this section Using Cloned ID's in the main 'How to Fix iMessage' guide. The lock out did happen affecting both real Macs and Hacks along with ID's hence the reason for the frustration some of you are experiencing some difficulty in getting iMsg/F-Time working on your Hacks. After so many cases of cloned machines plus the iCloud security breach, Apple completely changed the security protocol for iMessage and FaceTime.
Well I did say the iMac I used was part of our render far and as such will *NEVER* access any Apple online services. That said, it worked WORSE than using generated values per the guides. I'm stuck at the contact apple with customer code issue.
I called Apple, they sent it to engineering, had me pull logs (which I had to sanitize of hack related items) and I'm waiting on a resolution on their end. According to the engineer I've been working with it should be working but something on Apple's end is still preventing successful registration.