Adam1203 Posted January 23, 2013 Share Posted January 23, 2013 I also would like to know if this is possible? Shouldn't we just be able to add a key & value to the nvram.uuid.plist to enable it upon boot? By the way, iMessage also working great here! Thanks!!!!! Dil83 I was using a NVRAM launch daemon found in another thread, but now with Chameleon injecting NVRAM at boot... the launchdaemon won't work. I looked at the nvram.uuid.plist and the FMM token is there, it seems like it's missing the part that tells it to enable. Link to comment Share on other sites More sharing options...
cosmo1t Posted January 23, 2013 Share Posted January 23, 2013 JESUS. sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM=my mac address reboot. Link to comment Share on other sites More sharing options...
Toonces Katt Posted January 23, 2013 Share Posted January 23, 2013 JESUS. sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM=my mac address reboot. I assume this is for me. Thank you. I just tried that. Had to remove the generated values using nvram -d then added the correct values. First just the MAC address and a reboot, then when that didn't work, I changed the serial and rebooted again. The pic shows where it's at right now. All of the UUID values have the same serial number and MAC address. If there's any other information I can provide, please let me know. I appreciate your assistance! Link to comment Share on other sites More sharing options...
ncmontas Posted January 23, 2013 Share Posted January 23, 2013 fix works like a charm, thanks Link to comment Share on other sites More sharing options...
rcork Posted January 23, 2013 Share Posted January 23, 2013 I assume this is for me. Thank you. I just tried that. Had to remove the generated values using nvram -d then added the correct values. First just the MAC address and a reboot, then when that didn't work, I changed the serial and rebooted again. The pic shows where it's at right now. All of the UUID values have the same serial number and MAC address. If there's any other information I can provide, please let me know. I appreciate your assistance! I think you just need to start over from scratch. Remove the module from /Extra/modules, reboot, then delete /Extra/nvram.*.plist, then reboot, then copy the module back to /Extra/modules, reboot. Try iMessage. Don't mess with nvram, don't edit the files, just try iMessage. Link to comment Share on other sites More sharing options...
cosmo1t Posted January 23, 2013 Share Posted January 23, 2013 or. use nvram -d to delete all 6 of those UUID:ROM/UUID:MLB values reboot. Link to comment Share on other sites More sharing options...
jasonhun Posted January 23, 2013 Share Posted January 23, 2013 Hi! Please give me a STEP BY STEP FIX tutorial! What i need? How? Thank you! Link to comment Share on other sites More sharing options...
Toonces Katt Posted January 23, 2013 Share Posted January 23, 2013 I think you just need to start over from scratch. Remove the module from /Extra/modules, reboot, then delete /Extra/nvram.*.plist, then reboot, then copy the module back to /Extra/modules, reboot. Try iMessage. Don't mess with nvram, don't edit the files, just try iMessage. I tried this. removed the module, rebooted and removed the nvram files in / & /Extra then rebooted again. Pic1 shows nvram -xp after removals. I put the module back and rebooted allowing everything to be generated from scratch. pic2 shows the error and nvram -xp. Lastly, I changed just the ROM value from all 0 to my MAC address and rebooted again. Pic 3 shows the error and nvram -xp. Please let me know if I can provide anything else. iMessage not working on mine with Chameleon but it does work with Clover from a USB stick. Is there something else I should be looking at? certs or anything that might be associated with logging in with Clover? If there's anything I can provide, please let me know. I need to get some work done so I won't keep bugging you but am happy to give anything a try or provide any info from my system that may help. Thank You cosmo1t, rcork & meklort for your assistance. I appreciate it and your contributions to the Hac community. Best Regards, E Link to comment Share on other sites More sharing options...
rcork Posted January 23, 2013 Share Posted January 23, 2013 I tried this. removed the module, rebooted and removed the nvram files in / & /Extra then rebooted again. Pic1 shows nvram -xp after removals. I put the module back and rebooted allowing everything to be generated from scratch. pic2 shows the error and nvram -xp. Lastly, I changed just the ROM value from all 0 to my MAC address and rebooted again. Pic 3 shows the error and nvram -xp. Please let me know if I can provide anything else. iMessage not working on mine with Chameleon but it does work with Clover from a USB stick. Is there something else I should be looking at? certs or anything that might be associated with logging in with Clover? If there's anything I can provide, please let me know. I need to get some work done so I won't keep bugging you but am happy to give anything a try or provide any info from my system that may help. Thank You cosmo1t, rcork & meklort for your assistance. I appreciate it and your contributions to the Hac community. Best Regards, E Download and run THIS from the command line (i.e Terminal). Take a screenshot and post it. Also, attach your /Extra/smbios.plist. Link to comment Share on other sites More sharing options...
Toonces Katt Posted January 23, 2013 Share Posted January 23, 2013 Download and run THIS from the command line (i.e Terminal). Take a screenshot and post it. Also, attach your /Extra/smbios.plist. Done. smbios.plist.zip Link to comment Share on other sites More sharing options...
rcork Posted January 23, 2013 Share Posted January 23, 2013 Done. smbios.plist.zip Ok two things. First, what version of OSX are you running? Second, i thought the MLB was supposed to be 17 characters but yours is 16. Lets try changing it, reboot and try iMessage again. sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB=CK916531XYL123456 If it still doesn't work, run imessage_debug again and make sure the MLB is the correct length. Link to comment Share on other sites More sharing options...
jasonhun Posted January 23, 2013 Share Posted January 23, 2013 No working! Link to comment Share on other sites More sharing options...
dmazar Posted January 23, 2013 Share Posted January 23, 2013 Just a note: ROM is suppose to contain MAC address of your primary network card. Although, it seems it's not important at all for now. But, if you still want to set ROM to your MAC address, then do it like this: if MAC address is f1:2a:14:52:9a:60 (note: it's 6 bytes) then do sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM=%f1%2a%14%52%9a%60 For binary data: %<byte as two hex char>%<byte as two hex char>%<byte as two hex char>... and not as sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM=f12a14529a60 2 Link to comment Share on other sites More sharing options...
cosmo1t Posted January 23, 2013 Share Posted January 23, 2013 actually, just sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM=f1:2a:14:52:9a:60 it should be base64 encoded I think Link to comment Share on other sites More sharing options...
dmazar Posted January 23, 2013 Share Posted January 23, 2013 No, no. It's not base 64. It's %HexHex for one byte and if byte is printable character, then this character can be used. Just look how it prints other vars. Link to comment Share on other sites More sharing options...
Toonces Katt Posted January 23, 2013 Share Posted January 23, 2013 Ok two things. First, what version of OSX are you running? Second, i thought the MLB was supposed to be 17 characters but yours is 16. Lets try changing it, reboot and try iMessage again. sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB=CK916531XYL123456 If it still doesn't work, run imessage_debug again and make sure the MLB is the correct length. Sorry for the delay in replying. I am running 10.8.1 booting with Chameleon 2170 installed from earlier in the thread. Still not working, I entered 17 digits when I did the nvram command previously and it looks like things change between putting it in and rebooting. Here's iMessage_debug: localhost:Desktop erik$ nvram -xp <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">'>http://www.apple.com/DTDs/PropertyList-1.0.dtd">'>http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB</key> <data> Q0s5MTY1MzFYWUwxMjM0NTYA </data> <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM</key> <data> MDAwNjRmNDliZTg2 </data> <key>IOPowerManagement</key> <dict> <key>CurrentPowerState</key> <integer>1</integer> <key>MaxPowerState</key> <integer>1</integer> </dict> <key>IOPowerManagement:CurrentPowerState</key> <data> AAAAAA== </data> <key>IOPowerManagement:MaxPowerState</key> <data> AAAAAA== </data> <key>boot-args</key> <data> IC12IC1mAA== </data> <key>boot-gamma</key> <data> rBAAAC6gAABVTkMxtgAAAAAAAAANAAEB4wQCAgUIBAQpDQcHoRMODjQgGBhULyMj+D0w MKdNPT0nXE5O121ycguQmpqQssnJ+9cNAAEB4wQCAgUIBAQpDQcHoRMODjQgGBhULyMj +D0wMKdNPT0nXE5O121ycguQmpqQssnJ+9cNAAEB4wQCAgUIBAQpDQcHoRMODjQgGBhU LyMj+D0wMKdNPT0nXE5O121ycguQmpqQssnJ+9esEAAAPEAAAFMyRkO2AAAAAAAAAA0A AQHjBAICBQgEBCkNBwehEw4ONCAYGFQvIyP4PTAwp009PSdcTk7XbXJyC5CampCyycn7 1w0AAQHjBAICBQgEBCkNBwehEw4ONCAYGFQvIyP4PTAwp009PSdcTk7XbXJyC5CampCy ycn71w0AAQHjBAICBQgEBCkNBwehEw4ONCAYGFQvIyP4PTAwp009PSdcTk7XbXJyC5Ca mpCyycn716wQAABCQAAATDI3MbYAAAAAAAAADQABAeMEAgIFCAQEKQ0HB6ETDg40IBgY VC8jI/g9MDCnTT09J1xOTtdtcnILkJqakLLJyfvXDQABAeMEAgIFCAQEKQ0HB6ETDg40 IBgYVC8jI/g9MDCnTT09J1xOTtdtcnILkJqakLLJyfvXDQABAeMEAgIFCAQEKQ0HB6ET Dg40IBgYVC8jI/g9MDCnTT09J1xOTtdtcnILkJqakLLJyfvX </data> </dict> </plist> Here's what I did and where I see a change. 1. sudo nvram -d 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB 2. sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB=CK916531XYL123456 3. nvram -xp <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB</key> <data> Q0s5MTY1MzFYWUwxMjM0NTY= </data> 4. reboot 5. nvram -xp localhost:Desktop erik$ nvram -xp <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB</key> <data> Q0s5MTY1MzFYWUwxMjM0NTYA </data> Not sure if that has anything to do with it but the value changes after the reboot. Thanks Again! 1 Link to comment Share on other sites More sharing options...
theconnactic Posted January 23, 2013 Share Posted January 23, 2013 Toonces Katt, what exactly happens when you try to log in? Link to comment Share on other sites More sharing options...
rcork Posted January 23, 2013 Share Posted January 23, 2013 what do you get when you execute: nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB @Toonces - also might be worthwhile trying to use a different system definition like iMac12,2. If you do try that, you'd need to follow the same procedure to disable the module, delete nvram.plist, change system definition, reinstall module and let it recreate the nvram.plist. Link to comment Share on other sites More sharing options...
antipop2323 Posted January 23, 2013 Share Posted January 23, 2013 Just a note: ROM is suppose to contain MAC address of your primary network card. Although, it seems it's not important at all for now. But, if you still want to set ROM to your MAC address, then do it like this: if MAC address is f1:2a:14:52:9a:60 (note: it's 6 bytes) then do sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM=%f1%2a%14%52%9a%60 i tried this and in my plist ROM looks like <12eg487e 506e> is that how it should look in plist? Link to comment Share on other sites More sharing options...
dmazar Posted January 23, 2013 Share Posted January 23, 2013 if you open plist in plist editor, then you should get your MAC address (6 bytes) inside < and >. Your example above looks ok, except it has letter 'g' which is not possible - not a hex digit. But again, from the current user experience, ROM value must be present but it's not required to be MAC address to sign in to iMessage. For now. Link to comment Share on other sites More sharing options...
antipop2323 Posted January 23, 2013 Share Posted January 23, 2013 if you open plist in plist editor, then you should get your MAC address (6 bytes) inside < and >. Your example above looks ok, except it has letter 'g' which is not possible - not a hex digit. But again, from the current user experience, ROM value must be present but it's not required to be MAC address to sign in to iMessage. For now. ok, well i just made up the #s, but that's more or less what mine looked like heh... it did create a space though, so it appeared like <12ef487e 506e> /shrug Link to comment Share on other sites More sharing options...
Toonces Katt Posted January 23, 2013 Share Posted January 23, 2013 Toonces Katt, what exactly happens when you try to log in? I go through authentication it gets to the next screen of activating iMessage then gives the message "Could not sign in to iMessgae/ The server encountered an error processing registration. Please try again later." Same message I was getting since the iMessage beta ended. I am able to get in using Clover but would much rather use Chameleon. what do you get when you execute: nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB @Toonces - also might be worthwhile trying to use a different system definition like iMac12,2. If you do try that, you'd need to follow the same procedure to disable the module, delete nvram.plist, change system definition, reinstall module and let it recreate the nvram.plist. I get 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB CK916531XYL123456 I'll give iMac 12,2 a try and see if that makes a difference. what do you get when you execute: nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB @Toonces - also might be worthwhile trying to use a different system definition like iMac12,2. If you do try that, you'd need to follow the same procedure to disable the module, delete nvram.plist, change system definition, reinstall module and let it recreate the nvram.plist. I followed your instructions above and removed the model, reboot, remove nvram.plist (both), changed to iMac 12,2 reboot, reinstall module and it created nvram.plist. I tried to sign in and got the same error. Pic shows nvram -xp, iMessage_debug & 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB output. I'll boot up in Clover and try to run some comparisons to the values I have under that. Maybe something with my hardware is treaded differently? I do have a PCI gigabit ethernet card (eth0) the only card that is actually recognized by the system as the built in is disabled in BIOS and I don't load the kext for it. Though I suspect that shouldn't really matter since the primary card is the one that is being used and it works under Clover. Thanks Again, for your assistance! Update: I set the same values I found in Clover and still not getting in except with Clover. Attached are the screenshots of the relevant output. Clover: CHameleon: After comparing the two outputs, I even changed the serial via sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB: C02HK578DHJP7E1I1 and still not able to get in. iMessage_debug output after the change: localhost:Desktop erik$ sudo ./imessage_debug 2013-01-23 17:22:26.479 imessage_debug[373:a07] Gq3489ugfi: <4176ffdf af516d90 07c9854b 6145ed56 ff> 2013-01-23 17:22:26.481 imessage_debug[373:a07] Fyp98tpgj: <8d94ca87 3b8d86b9 9f60c03c 800c87de 4c> 2013-01-23 17:22:26.481 imessage_debug[373:a07] kbjfrfpoJU: <d8f48566 3454c887 bec9ea22 9059be4a 9e> 2013-01-23 17:22:26.482 imessage_debug[373:a07] IOPlatformSerialNumber: W80CF65ADHJF 2013-01-23 17:22:26.482 imessage_debug[373:a07] IOPlatformUUID: 371A61AF-D774-58C5-870D-82C4D7054ED8 2013-01-23 17:22:26.483 imessage_debug[373:a07] board-id: Mac-942B5BF58194151B 2013-01-23 17:22:26.484 imessage_debug[373:a07] product-name: iMac12,1 2013-01-23 17:22:26.484 imessage_debug[373:a07] 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM: <00000000 00000000 00000000 000000> 2013-01-23 17:22:26.485 imessage_debug[373:a07] 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB: C02HK578DHJP7E1I1 2013-01-23 17:22:26.485 imessage_debug[373:a07] oycqAZloTNDm: <c32e324e 39692550 a7909594 d43fc4af c1> 2013-01-23 17:22:26.486 imessage_debug[373:a07] abKPld1EcMni: <589311eb 31fb5e70 f471a5d3 46206890 4d> Link to comment Share on other sites More sharing options...
nyolc8 Posted January 24, 2013 Share Posted January 24, 2013 If I change MLB value with the nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB=CK111111XYL123456 command, and I check the data with nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB, I get this: 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB CK111111XYL123456 If I restart, and check the data again with nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB, I get this: 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB CK111111XYL123456%00 So a "%00" added to the end. Same thing happens with ROM value on restart. Is this normal? (The serial is just example in my post, I use valid serial.) Link to comment Share on other sites More sharing options...
kjp4756 Posted January 24, 2013 Share Posted January 24, 2013 I have lion on my mba (work laptop) so no imessage. Am I stuck? I'm getting the same error as you and like you, I also only have access to a 10.7 mac. I wish I knew what to do. I've tried signing in to icloud and facetime on my mac and that doesn't seem to help. Funny thing is my wife's appleid works fine on my hack for imessage. I even created a new appleid for myself and still got the same error with that. Link to comment Share on other sites More sharing options...
dgrx Posted January 25, 2013 Share Posted January 25, 2013 Thanks to all involved Everything working good again. Link to comment Share on other sites More sharing options...
Recommended Posts