.....
Then I noticed that on self solve.apple.com, where my S/N was previously invalid, there is a MacBook Pro with no purchase date, and now I can't use my S/N to contact Apple without paying the $19 for support.
So what do you suggest doing here? Changing my S/N and/or SystemId?
My UUID in the nvram.uuid.plist and in IORegistryExplorer are identical, Both "9402de03-8004-6905-4106-d40700080009". The UUID listed in System Information is completely different, "8DC91BAC-42A2-5B48-8F5B-155317FFE0ED".
Is the UUID supposed to be the same in all 3 of the locations?
@Garetty, @Albertsw + Others ...
The UUID in nvram.uuid.plist and in IORegistryExplorer ideally should be identical (but for some users this is sometimes not the case), The UUID listed in System Information should always be different.
To be honest I'm not sure what to advise, both of you have tried to call Apple with the customer code and both of you still have issues which puts you in uncharted waters, so far this has worked for everyone who has tried it ...... if it where me i would try the following:-
1. Logout of all Apple iCloud services & physically disconnect form your network (if possible)
2. Use the SId bug fix to override the BIOS SystemId regardless if your BIOS has SId bug or not.
3. Use Chameleon Wizard, check you have correct System Def for your Hack and generate new S/N
4. Use Step 3 in Part 1 of the guide to clear iMessage setup / config / data
5. Delete nvram.uuid.plist in /Extra
6. Reboot and check that new S/N and UUID's have taken
7. Check that the OSX Hardware UUID is different to the one you had originally.
8. Connect to network and create a new AppleID, make sure to register Credit Card against it.
9. Try iCloud, AppStore and iTunes first, if that works try iMessage
The above procedure will create a totally new identity for you and your hack (MAC) which has not been registered with Apple so hopefully no UUID lock out and iMessage will work for you. If not then we need to look a little deeper as to whats going on in your logs ... etc
If it works, try to avoid changing the S/N & UUID in the future, write them down and keep the safe, my personal theory is that the lock out occurs when the S/N has changed too many times against a OSX UUID, however it may be the other way round, I cover this in more detail part 2 of the guide.
Like i said in Post
#628 its also possible that we're on the verge of seeing a new set of iMessage issues with the release of the new iMessage features in OSX 10.10 & IOS 8, lets hope that its not the case .....
FYI, iMessage is still working for me across all five of my Hacks and my iPhone 4.
Good Luck
Cheers
Jay