Jump to content

Toonces Katt

  • Content count

  • Joined

  • Last visited

About Toonces Katt

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
  1. iMessage/Messages Fix-How To

    It will only work until it signs out again then you can reboot with clover and sign in again and go back to Chameleon until it signs out again. Chameleon also has a fix out now but it's not yet working for me though many others have had success with it.
  2. 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. I get 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB CK916531XYL123456 I'll give iMac 12,2 a try and see if that makes a difference. 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>
  3. 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!
  4. 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
  5. 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!
  6. So does the filename in /Extra make a difference? I can't get iMessage working, still getting the same server error though I can boot Clover off a USB stick and get back in just fine. You can see from my nvram -xp above that I have the UUID from ioreg and another one both with MLB and ROM data but the file name is different still. Thanks Again!
  7. I haven't specified a UUID anywhere that I am aware of. the output of my nvram and ioreg are below. The 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14 UUID is generated when I boot nvram.plist removed. If I delete the 4D1E values using nvram and reboot, it comes back. $ sudo ioreg -lw0 | grep PlatformUUID | "IOPlatformUUID" = "371A61AF-D774-58C5-870D-82C4D7054ED8" | "IOPlatformUUID" = "371A61AF-D774-58C5-870D-82C4D7054ED8" $ sudo nvram -p IOPowerManagement:MaxPowerState %00%00%00%00 371A61AF-D774-58C5-870D-82C4D7054ED8:ROM 00064f49be86 IOPowerManagement:CurrentPowerState %00%00%00%00 boot-gamma %ac%10%00%00.%a0%00%00UNC1%b6%00%00%00%00%00%00%00%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%ac%10%00%00<@%00%00S2FC%b6%00%00%00%00%00%00%00%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%ac%10%00%00B@%00%00L271%b6%00%00%00%00%00%00%00%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB CK916531XYLODT3Q%00 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM %00%00%00%00%00%00%00%00%00%00%00%00%00 IOPowerManagement <INVALID> boot-args -v -f%00 371A61AF-D774-58C5-870D-82C4D7054ED8:MLB CK916531XYL123456%00 Will do.
  8. I don't know why but when I use the uuid from ioreg, it gives me the value 371A61AF-D774-58C5-870D-82C4D7054ED8. When I delete the nvram.plist and the one in Extra, it creates new ones with a different UUID, 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14 and populates nvram with that. I've had up to 3 different UUID:MLB combinations in nvram at the same time according to nvram -p and still get the server error message from iMessage. This last time I went through and deleted all of the nvram UUID except for 371A61AF-D774-58C5-870D-82C4D7054ED8:MLB & ROM entries and got 2 kp in a row. on the 3rd boot, it booted but now has 2 UUID:MLB & ROM entries for the 2 UUID's above.
  9. Thanks!, sudo lets me enter the values but it enters them into /Extra/nvram.44454c4c-5400-1037-8058-b1c04f544631.plist. My UUID is supposed to be "371A61AF-D774-58C5-870D-82C4D7054ED8" according to ioreg so I don't understand why the difference. Is there a way I am supposed to enter the UUID I got from ioreg?
  10. I know I must be doing something wrong. I installed 2170 and rebooted to auto generate the nvram.plist. I copied it to /Extra/nvram.371A61AF-D774-58C5-870D-82C4D7054ED8.plist and rebooted again. Every time I try to add using the nvram command, I get an error "Error setting variable - '371A61AF-D774-58C5-870D-82C4D7054ED8:MLB': (iokit/common) general error" and a new nvram plist file is created witht he UUID with the name nvram.44454c4c-5400-1037-8058-b1c04f544631.plist What am I missing to set?? Thanks and GREAT JOB!
  11. Dell Bios, AHCI/RAID, SSD

    I saw the changes but the device I'd was a typo? I corrected it according to what you posted earlier in the thread and everything works perfectly! Sleep works a well as shut down. Previously it always rebooted even when choosing shut down. Thanks again! I appreciate your help.
  12. Dell Bios, AHCI/RAID, SSD

    Thanks! I removed the referenced kexts and using the attached dsdt.aml, I am getting waiting on root device. I have verified my bios is still set for RAID. My HDD is connected to SATA0 and my DVD is on SATA1. SATA 3&4 are not present and Sata 4 & 5 are empty. If I move the kexts back, I boot up to the desktop. My boot plist is set for MacPro 3,1. If I set my BIOS to IDE, I am able to get to the desktop using this DSDT. Any ideas? Actually, I just found it. the DSDT had x28 x28 for the device id. I changed it per your earlier instructions and it's all working! Thanks Again Latin! You're help has been invaluable!!! I have attached the corrected DSDT for anyone looking for a good working Vostro 400 DSDT under 10.8. This is for the G33M03 motherboard with 1.0.15 BIOS. V400dsdt.zip
  13. Dell Bios, AHCI/RAID, SSD

    Using Yellowguy's extra I was able to get booted into a clean myhack install of ML. I was able to boot without his DSDT and dumped my Vostro 400's DSDT which is attached. LatinMcG, if it's not too much to ask, could you please take a look at it and make any patches needed? I understand the Orange Icon fix but the others may be needed I am not sure about. My video is HD 5770 which shows correctly using GraphicsEnabler. The contents of my /E/E/: fakesmc.kext Intel82566MM.kext IOAHCIBlockStorageInjector.kext LegacyAppleAHCIPortIntelICHx.kext PlatformUUID.kext lspcidrv.kext (added by myhack) Patched_10.7_AppleRTC.kext (added by myhack) ApplePS2Controller.kext (added by myhack) AppleACPIPS2Nub.kext (added by myhack) I am pretty sure I don't need the ones added by myhack, they are part of the generic kexts added by default to all installs. Thanks again to Yellowguy and LatinMcG! I really appreciate your assistance. I've been messing with ML for the last 2 days and got farther in the last 2 hours than the previous 2 days Vostro400DSDT.zip