- Joined
- Dec 31, 2013
- Messages
- 28
- Motherboard
- Gigabyte Z390 GAMING X
- CPU
- i9-9900K
- Graphics
- RX 6900 XT
- Mac
- Mobile Phone
Just updated to Chimera 3.0.1
iMessages does not work again, even with the UUID additions in SMBIOS and regenerating the NVRAM.
Tried both with FileNVRAM.dylib ver 1.1.2 and 1.1.3 and the results are the same.
I have followed all the instructions in Part1 and Part2 again about 4 times and it still will not work.
iMessage gives the error "An error occurred during activation. Try again."
Anyone with experience with Chimera 3,0,1?
My OSX is 10.9.2
Hardware is i7 3770 Z77PRO3
Thanks in advance
UPDATE:
It works now.
I left it overnight based on Chimera 3.0.1 and FileNVRAM 1.1.3 and logged in again the next morning and iMessage works, albeit with a few errors before being accepted. Strange. Nothing changed and nothing updated since, just time lapse. Perhaps their server needs time to acknowledge the UUID? Or I am having a case of midnight computer elves.
Anyway the only thing is Facetime and iMessage cannot seem to log in at the same time. Only one or the other but I am glad iMessage works for now. Perhaps some more time will help
UPDATE2: Both works fine now after logging off iMessage and logging in Facetime first and then signing in iMessage. There was a few errors but somehow it worked again after a while.
Thanks to Jaymonkey again for this fix.
iMessages does not work again, even with the UUID additions in SMBIOS and regenerating the NVRAM.
Tried both with FileNVRAM.dylib ver 1.1.2 and 1.1.3 and the results are the same.
I have followed all the instructions in Part1 and Part2 again about 4 times and it still will not work.
iMessage gives the error "An error occurred during activation. Try again."
Anyone with experience with Chimera 3,0,1?
My OSX is 10.9.2
Hardware is i7 3770 Z77PRO3
Thanks in advance
UPDATE:
It works now.
I left it overnight based on Chimera 3.0.1 and FileNVRAM 1.1.3 and logged in again the next morning and iMessage works, albeit with a few errors before being accepted. Strange. Nothing changed and nothing updated since, just time lapse. Perhaps their server needs time to acknowledge the UUID? Or I am having a case of midnight computer elves.
Anyway the only thing is Facetime and iMessage cannot seem to log in at the same time. Only one or the other but I am glad iMessage works for now. Perhaps some more time will help
UPDATE2: Both works fine now after logging off iMessage and logging in Facetime first and then signing in iMessage. There was a few errors but somehow it worked again after a while.
Thanks to Jaymonkey again for this fix.