How to Fix iMessage

[arehep]

@ all
Read and then read once or twice again before posting !!!

 

[Wolfie81]

EDIT: FIXED.
For anyone having this issue, I managed to resolve it by changing password.


Guys I've buggered up.

I noticed jaymonkey rewrote instructions for this latest fix which included generating a random UUID from a website and use Chamelon Wizard to regenerate a new serial number and I cannot get iMessage working anymore. I decided to follow his instructions to make sure everything is solid despite having it working before by only copying the UUID generated in system profiler.

I am using everything Tonymac for my Hackintosh so it is the latest version of Chimera.

I now get

Could not sign into iMessage. An error occurred during activation. Try again.
Everytime I regenerate a new UUID and put it into the plist I do get asked for passwords for mail, iCloud and other programs but NOT FaceTime or iMessage.
I have now done this a few times and I know immediately I cannot sign into iMessage/facetime as I simply do nopt get prompted anymore to enter a password.

Im stuck and regretting trying to do this the 'complete' way.
I have tried replacing the original working UUID number back into the boot.plist but they didn't work either. I have regenerated a new serial number through chameleon wizard but they didn't work.
I have even tried using the random UUID found in system profiler but they didn't work.

Argghhhhh.

 

[3square]

I can remove it without effecting imessage? Keep in mind my iMessage is working perfectly right now.Reason for wanting to tidy it up is because i have to go back in there to add some entries to hide a bunch of non-OS hard drives from the bootloader menu screen (Tri-booting system).

Yes you can remove the SystemID, since the smbios UUID is taking effect, and NOT the SystemID in chameleon boot plist.

So is it called KextWizard exactly? And is it compatible with mavericks? Links? How often should i run this utility or is it something that you cant really harm anything by using too often?

yes exact name, google it and download it. it is compatible with mavericks. run it when ever you make changes to anything in extra folder or S/L/E. No harm in running it too often.

I've been messing around with it back in the Snow Leopard days and i had my first hack running on one of those crappy nVidia chipset boards. 680iSli chipset to be exact. Every time i think im wrapping my head around this, ill get my system up and running and time will go by and ill forget everything by the time i need to do it again lol.

But ill tell you what, after i got my bios settings figured out to where i could actually boot to the installer and not get the quick reboot issue, it was one of the easiest times i've ever had installing OSX. Unibeast and multibeast got everything going pretty much flawlessly. The iMessage issue was my biggest headache. Last time i installed Lion on this same setup it seemed like such a daunting task. But now that i got unibeast working with proper bios settings it actually felt easy for once. Keep in mind I haven't been able to get unibeast working since the release of mountain lion........all because of one stupid bios setting

good that you figured it out on bios, you learned something. What i do is to use CarbonCopyCloner, it's an app that create an EXACT duplicate of your OSX drive. After that i install chameleon to that drive. Effectively creating a duplicate BOOTABLE drive. I call that drive CLONE. When ever i want to test something or install an update, i do so to THAT DRIVE. If whatever i do to it mess it up, i still have my MAIN OSX drive to troubleshoot. All i have to do is on chameleon boot, i either select my MAiN drive OR the CLONE drive.

hope that helps.

 

[3square]

EDIT: FIXED.
For anyone having this issue, I managed to resolve it by changing password.


Guys I've buggered up.

I noticed jaymonkey rewrote instructions for this latest fix which included generating a random UUID from a website and use Chamelon Wizard to regenerate a new serial number and I cannot get iMessage working anymore. I decided to follow his instructions to make sure everything is solid despite having it working before by only copying the UUID generated in system profiler.

I am using everything Tonymac for my Hackintosh so it is the latest version of Chimera.

I now get

Could not sign into iMessage. An error occurred during activation. Try again.
Everytime I regenerate a new UUID and put it into the plist I do get asked for passwords for mail, iCloud and other programs but NOT FaceTime or iMessage.
I have now done this a few times and I know immediately I cannot sign into iMessage/facetime as I simply do nopt get prompted anymore to enter a password.

Im stuck and regretting trying to do this the 'complete' way.
I have tried replacing the original working UUID number back into the boot.plist but they didn't work either. I have regenerated a new serial number through chameleon wizard but they didn't work.
I have even tried using the random UUID found in system profiler but they didn't work.

Argghhhhh.

try what i did in post #439
http://www.tonymacx86.com/general-help/110471-how-fix-imessage-44.html#post795667

 

[jaymonkey]

I managed to resolve it by changing password

@Wolifi81

Glad that it's working for you now.

Your not alone in finding that after applying the SID Bug fix.

As stated in the guide you may need to perform one or more of the steps from part-1 of the guide to get things working correctly again, I note a few other users had to also change their passwords.

Thanks for your feedback, I'll update Part-2 of the guide with the password tip as the first thing to try if iMessage is not working after applying the SID Bug fix and you do not get the customer code/contact Apple message.

@All

After applying the SID BUG, some users find that all is well and iMessage is working again.

A few users get a message to contact Apple with a customer code, if you get this message the only way forward (if you want to keep your AppleID) is to call them, Apple will reset the miss-match or UUID or whatever in their database and you should be back in.

For others who do not get the above message, as Wolfi81 found above, it looks like updating the password of your AppleID (an old iMessage fix) is enough to get things working again.

If all else fails, working thorough Part-1 of the main guide again should get iMessage sorted.

If your BIOS suffers from the SID Bug, do not use a UUID from within OSX (hardware UUID or platform UUID) as you run the chance of using a non unique UUID, always use a random (unique) UUID, I've made this a bit clearer now in Part-2 of the guid.

Cheers
Jay

PS: I really do appreciate any and all feedback, wether you consider yourself a seasoned hackingtosher or your just starting out in the world of OSX, it all helps to fine tune the guide to cater for all experience levels.

 

[mrcivic98]

PS: I really do appreciate any and all feedback, wether you consider yourself a seasoned hackingtosher or your just starting out in the world of OSX, it all helps to fine tune the guide to cater for all experience levels.

Jay- just wanted to thank you again for your help in getting this fixed sorted out and more generally, for so diligently maintaining this guide. It's great to have such a helpful community out there for hackintoshers of all skill levels! Thanks again! Great work everyone. It's great to have iMessage back.

 

[chaoticmayhem65]

Yes you can remove the SystemID, since the smbios UUID is taking effect, and NOT the SystemID in chameleon boot plist.

Wait huh? Is that a typo? I already deleted the SystemId entry in org.chameleon.Boot.plist and left the SMsystemuuid entry in the smbios.plist. iMessage is still working.

yes exact name, google it and download it. it is compatible with mavericks. run it when ever you make changes to anything in extra folder or S/L/E. No harm in running it too often.

And what version is the most current? im using Kext Wizard Version 3.7.10 and when i open the maintenance tab the only selection i can select is the System/Library/Extensions box that also checks the repair permissions box and rebuild cache box. The Extra box is greyed out.

The extra folder is the main one i want to run it on since that's the only place ive been editing .plist's in correct?

And when i hit the Extra option up top in the menu bar it has checked system version independent and has selections for 10.4, 10.5, 10.6 and 10.7. It doesn't have an option for 10.9. I attached a pic so you can see what i mean.

And thanks for all your help.

 

[arehep]

@ chaoticmayhem65

KextWizard 3.7.10 is the latest up to date version.
And from what i se on the attached picture everything is fine.
Don´t worry about you don´t se 10.9 in the dropdown menu as long as the System version independent is checked.
The reason the Extra option is greyed out is because you don`t have a Kext folder in your Extra folder.
(leftover from the "good old days" where some kexts had to be in the Extra/Kext folder - but some people still have)
The most important thing (correct me if i´m wrong) is to Rebuild Cache as important info is stored in the cache and probably info about UUID´s
The Repair permission option is not important unless you have installed new kexts in S/L/E.
But as 3square wrote "No harm in running it too often"
As i read your post iMessage is working for you and that´s the most important issue

 

[3square]

Wait huh? Is that a typo? I already deleted the SystemId entry in org.chameleon.Boot.plist and left the SMsystemuuid entry in the smbios.plist. iMessage is still working.

yes remove the SystemID in your chameleon boot plist. that is not being use anymore. the SMsystemuuid in smbios is the one that is working.

And what version is the most current? im using Kext Wizard Version 3.7.10 and when i open the maintenance tab the only selection i can select is the System/Library/Extensions box that also checks the repair permissions box and rebuild cache box. The Extra box is greyed out.

The extra folder is the main one i want to run it on since that's the only place ive been editing .plist's in correct?

And when i hit the Extra option up top in the menu bar it has checked system version independent and has selections for 10.4, 10.5, 10.6 and 10.7. It doesn't have an option for 10.9. I attached a pic so you can see what i mean.

And thanks for all your help.

http://www.osx86.net/files/file/2136-kext-wizard-3-7-10/

 

[chaoticmayhem65]

@ chaoticmayhem65

KextWizard 3.7.10 is the latest up to date version.
And from what i se on the attached picture everything is fine.
Don´t worry about you don´t se 10.9 in the dropdown menu as long as the System version independent is checked.
The reason the Extra option is greyed out is because you don`t have a Kext folder in your Extra folder.
(leftover from the "good old days" where some kexts had to be in the Extra/Kext folder - but some people still have)
The most important thing (correct me if i´m wrong) is to Rebuild Cache as important info is stored in the cache and probably info about UUID´s
The Repair permission option is not important unless you have installed new kexts in S/L/E.
But as 3square wrote "No harm in running it too often"
As i read your post iMessage is working for you and that´s the most important issue

yes remove the SystemID in your chameleon boot plist. that is not being use anymore. the SMsystemuuid in smbios is the one that is working.



http://www.osx86.net/files/file/2136-kext-wizard-3-7-10/

Ok so by just manually editing the org.chameleon.Boot.plist or the smbios.plist does not call for any type of permissions repair or cache rebuild with Kext wizard?