Jump to content

iMessage not working - iCloud/Internet etc working - Changed boot.plist file and network.plist file - Help

hamzab

By hamzab,
in OSx86 10.8 (Mountain Lion)

 Share
418 posts in this topic

Recommended Posts

  • 3 weeks later...
stuppy_
stuppy_
Posted
Posted

The module causes the boot-args to be saved and restored automatically on reboot. You may change this by using the nvram command or by updating the boot args in the boot console.

 

Hi meklort,

 

Please could you tell me what I need to edit to get rid of the verbose booting option? What is 'the nvram command' ?

 

Thanks

Link to comment
Share on other sites
Mr. Zarniwoop
Mr. Zarniwoop
Posted
Posted

It's broken for me again.

Anyone else?

Just posting here in case it helps others. It wasn't working on a friend's genuine Mac Pro, so I was troubleshooting and found he had a strange hosts file filled with entries meant to defeat Adobe applications DRM.

 

Anyway, the lines that killed iMessage in hosts were: 127.0.0.1 crl.verisign.net 127.0.0.1 CRL.VERISIGN.NET.*

 

Those are Verisign's Certificate Revocation List, and by blocking them it blocked iMessage and FaceTime from securely logging in.

 

Once I removed those entries, both iMessage and FaceTime worked instantly.

  • Like 1
Link to comment
Share on other sites
eep357
eep357
Posted
Posted

Just posting here in case it helps others. It wasn't working on a friend's genuine Mac Pro, so I was troubleshooting and found he had a strange hosts file filled with entries meant to defeat Adobe applications DRM.

 

Anyway, the lines that killed iMessage in hosts were: 127.0.0.1 crl.verisign.net 127.0.0.1 CRL.VERISIGN.NET.*

 

Those are Verisign's Certificate Revocation List, and by blocking them it blocked iMessage and FaceTime from securely logging in.

 

Once I removed those entries, both iMessage and FaceTime worked instantly.

Good reminder, as blocking Verisign will break access to just about every secure website or 3rd party server. (won't help defeat Adobe DRM either :) )
  • Like 1
Link to comment
Share on other sites
  • 2 months later...
  • 2 weeks later...
MacFaulty
MacFaulty
Posted
Posted

I don't know if it's been posted before, but I had the same issue. iMessage just wouldn't activate. I traced this problem to the roots and it is because you do not have a unique serial number in your smbios.plist. I had to generate one with Kext Wizard. After I replaced that serial with the old one and rebooted, everything works fine. I highly suggest to anybody try that first, it will probably solve your issue.

 

For clarity: I installed a fresh copy of OS X 10.8 a few days ago and iMessage worked after the above trick^^

Link to comment
Share on other sites
  • 3 months later...
PHC
PHC
Posted
Posted

iMessage and iCloud problem:


 


1. I tried rampage's guide


2. Modified MLB and ROM in the NVRAM


3. Ethernet En0 and delete networkconfig. plist


4. Add smBios with a working serial number (Mac Pro 3,1)


4. My iMessage and iCloud worked in my previous Mavericks install I logged out and then it was impossible to log in. I reinstall and now is impossible to make it work


 


Something bizarre if I open the iMessage_debug I have this info and shows for 5 results as failed ( http://www.insanelym...help/?p=1883146 )


 


 


2013-11-04 16:14:12.544 imessage_debug[402:507] Gq3489ugfi: failed


2013-11-04 16:14:12.545 imessage_debug[402:507] Fyp98tpgj: failed


2013-11-04 16:14:12.545 imessage_debug[402:507] kbjfrfpoJU: failed


2013-11-04 16:14:12.546 imessage_debug[402:507] IOPlatformSerialNumber: CK909025XYL


2013-11-04 16:14:12.546 imessage_debug[402:507] IOPlatformUUID: 0E1B36C9-FDE2-5131-9040-4F532976F0AF


2013-11-04 16:14:12.547 imessage_debug[402:507] board-id: Mac-F42C88C8


2013-11-04 16:14:12.547 imessage_debug[402:507] product-name: MacPro3,1


2013-11-04 16:14:12.547 imessage_debug[402:507] 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM: <(..my mac address..)>


2013-11-04 16:14:12.548 imessage_debug[402:507] 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB: CK909025XYL123456


2013-11-04 16:14:12.548 imessage_debug[402:507] oycqAZloTNDm: failed


2013-11-04 16:14:12.548 imessage_debug[402:507] abKPld1EcMni: failed


 


 


I have a sabertooth x79, i7 4930k 


 


 


iMessage works for you guys?

 

Thanks

Link to comment
Share on other sites
cosmo1t
cosmo1t
Posted
Posted

 

iMessage and iCloud problem:

 

1. I tried rampage's guide

2. Modified MLB and ROM in the NVRAM

3. Ethernet En0 and delete networkconfig. plist

4. Add smBios with a working serial number (Mac Pro 3,1)

4. My iMessage and iCloud worked in my previous Mavericks install I logged out and then it was impossible to log in. I reinstall and now is impossible to make it work

 

Something bizarre if I open the iMessage_debug I have this info and shows for 5 results as failed ( http://www.insanelym...help/?p=1883146 )

 

 

2013-11-04 16:14:12.544 imessage_debug[402:507] Gq3489ugfi: failed

2013-11-04 16:14:12.545 imessage_debug[402:507] Fyp98tpgj: failed

2013-11-04 16:14:12.545 imessage_debug[402:507] kbjfrfpoJU: failed

2013-11-04 16:14:12.546 imessage_debug[402:507] IOPlatformSerialNumber: CK909025XYL

2013-11-04 16:14:12.546 imessage_debug[402:507] IOPlatformUUID: 0E1B36C9-FDE2-5131-9040-4F532976F0AF

2013-11-04 16:14:12.547 imessage_debug[402:507] board-id: Mac-F42C88C8

2013-11-04 16:14:12.547 imessage_debug[402:507] product-name: MacPro3,1

2013-11-04 16:14:12.547 imessage_debug[402:507] 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM: <(..my mac address..)>

2013-11-04 16:14:12.548 imessage_debug[402:507] 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB: CK909025XYL123456

2013-11-04 16:14:12.548 imessage_debug[402:507] oycqAZloTNDm: failed

2013-11-04 16:14:12.548 imessage_debug[402:507] abKPld1EcMni: failed

 

 

I have a sabertooth x79, i7 4930k 

 

 

iMessage works for you guys?
 
Thanks

 

 

boot single user mode. delete nvram.plist

reboot. you don't set MLB and ROM they are autogenerated by FileNVRAM.dylib

Link to comment
Share on other sites
PHC
PHC
Posted
Posted

 

 

FIXED: the kernel for the Ivy-e bridge was patched twice. The second version generates this problem. As soon as I rollback to the first version iCloud and iMessage was able to log in.

Great!

 

 

 

I have a sabertooth x79, i7 4930k 

 

 

iMessage works for you guys?
 
Thanks

 

 

boot single user mode. delete nvram.plist

reboot. you don't set MLB and ROM they are autogenerated by FileNVRAM.dylib

 

Como1t thank you but no difference. The MLB now is 16 letters instead of 17 and my Rom is not my mac address.

 

 

Here is the output:

 

2013-11-04 18:14:25.399 imessage_debug[343:507] Gq3489ugfi: failed

2013-11-04 18:14:25.400 imessage_debug[343:507] Fyp98tpgj: failed

2013-11-04 18:14:25.400 imessage_debug[343:507] kbjfrfpoJU: failed

2013-11-04 18:14:25.401 imessage_debug[343:507] IOPlatformSerialNumber: CK909025XYL

2013-11-04 18:14:25.401 imessage_debug[343:507] IOPlatformUUID: 0E1B36C9-FDE2-5131-9040-4F532976F0AF

2013-11-04 18:14:25.402 imessage_debug[343:507] board-id: Mac-F42C88C8

2013-11-04 18:14:25.402 imessage_debug[343:507] product-name: MacPro3,1

2013-11-04 18:14:25.402 imessage_debug[343:507] 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM: <d48d9829 cb2a>

2013-11-04 18:14:25.403 imessage_debug[343:507] 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB: CK909025XYLKKEDH

2013-11-04 18:14:25.403 imessage_debug[343:507] oycqAZloTNDm: failed

2013-11-04 18:14:25.403 imessage_debug[343:507] abKPld1EcMni: failed

 

 

any idea?

Link to comment
Share on other sites
cosmo1t
cosmo1t
Posted
Posted

the ROM doesn't need tob e your mac address, and the value you are seeing is a base64'd value

you need to delete both plists if u have more than 1 .plist in the /Extra/ (nvram or uuid.plist)

if u delete them not in single user mode, they will recreate on shutdown.

 

You need to make sure you have the newest version of chameleon adn the newest version of filenvram.dylib.

 

Dont' know what else to tell you since most other people havne't reported an issue.

and that output anyway isn't a good log, it's just imessage_debug. if your eally think it's a bug, you should file it as such on the xzenue.com and post all the required files.

Link to comment
Share on other sites
theconnactic
theconnactic
Posted
Posted

Cosmo, his problem is that he's using a compiled kernel. When you run OSX on top of a kernel compiled from XNU sources, no iCloud services will work...


By the way, and i must stress i know here's not the appropriate place, but the Kernel Patcher Module of yours seems not to be working with 10.9. I've been trying to file a bug report about this, but every time I try to create an account in Bugzilla i get an "internal error" message...

Link to comment
Share on other sites
cosmo1t
cosmo1t
Posted
Posted

Cosmo, his problem is that he's using a compiled kernel. When you run OSX on top of a kernel compiled from XNU sources, no iCloud services will work...

By the way, and i must stress i know here's not the appropriate place, but the Kernel Patcher Module of yours seems not to be working with 10.9. I've been trying to file a bug report about this, but every time I try to create an account in Bugzilla i get an "internal error" message...

 

Cosmo, his problem is that he's using a compiled kernel. When you run OSX on top of a kernel compiled from XNU sources, no iCloud services will work...

By the way, and i must stress i know here's not the appropriate place, but the Kernel Patcher Module of yours seems not to be working with 10.9. I've been trying to file a bug report about this, but every time I try to create an account in Bugzilla i get an "internal error" message...

wtf. yeah compiled kernel doens't include any of that.. and well meklort has been moving. will try fixing it. can u just msg us on irc?

Link to comment
Share on other sites
PHC
PHC
Posted
Posted

Thanks Cosmo1t and theconnactic. i don't really know what was changed in the second version of the patched kernel that is messing up with iMessage and iCloud. The good thing is that the first version of the patched kernel for Ivy-e bridge cpus is working without issues. i will revert to you if stinga11, who modified the kernel, can clear out the issue.

Link to comment
Share on other sites
  • 7 months later...
nmano
nmano
Posted
Posted

Hi anybody work try osx10.10 with filenvram I try it's stack booting

Link to comment
Share on other sites
  • 1 month later...
badkidforum
badkidforum
Posted
Posted

Worked like charm!

Steps @ basic

1. Fix network cards (inject ID using DPCIManager) for both en0 (realtek) and en1 (wireless).

2. Generate random serial number using Chameleon wizard.

3. Clean the slate.

4. Install NVRAM module

5. Reboot.

6. Re-setup.

 

Update: Only problem for me was iMessage, rest everything was working fine, i suspected only step 5c to be required but ended up following the guide to rule out any irregularities.

OSX 10.9.4 works fine.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...