How to Fix iMessage

[ahmed_shiko]

try injection MLB&ROM IN chimera

 

[esafeddie]

Looking at this - Your values are null hence the reason you cannot not log into iMsg and F/Time until you correct the problem. Delete all your iMsg F/Time cache folders contents, reboot and try manually injecting your MLB and ROM values (see chapter 7.1), repair Disk Permissions and reboot, run DeBugger again and see if the values you just inputted are unchanged, if they are try to log in.

 

[brick0044]

Can you please run iMessage DeBugger and post the results.

Model: MacBookPro8,1
Board-id: Mac-94245B3640C91C81
SerialNumber:
Hardware UUID: A6A967A7-0360-510A-A55D-E452EDD22BAD

System-ID: 1C5E176B-8D57-45AC-BBCD-0A00E5356816
ROM:
BoardSerialNumber:


Gq3489ugfi: ec8b159d63048ecd26e5adfe815d78249e
Fyp98tpgj: 944b9cb69afb605197e69bf148fedc722d
kbjfrfpoJU: 46e3cb02c543aa6f201f113fe1b2cfb180
oycqAZloTNDm: 2b6020b333ddb9198f4fc9d8a510b9c47f
abKPld1EcMni: a8797cc4fb3a65f017d1ec7edd401f5e8f




hope i didnt post to much info

 

[esafeddie]

Please note - Since the upgrade from Mavericks, I have not used Chimera as a boot loader as it was discovered that the then version FileNVRAM module would not work with Yosemite and the general advice was to switch over to Clover, as this was proven to be more reliable to get iMsg/F-Time to work. The FileNVRAM module has been updated and reworked to enable functionality with Chimera as the boot loader for Yosemite to a successful degree, but with a greater chance of breaking with any major Apple updates than with Clover as the boot loader.

Jay has advised a long time ago about making the switch to Clover and the reasons why we should make the switch, he also provided extensive Solutions and Guides to solve iMsg/F-Time connectivity problems in both Chimera and Clover. I am no longer familar with the Chimera method apart from what I have boned up and gleaned from Jay's tutorial, my limited knowledge is akin to the Clover method and will pass on or try to help with that limited knowledge when ever possible.

 

[brick0044]

Please note - Since the upgrade from Mavericks, I have not used Chimera as a boot loader as it was discovered that the then version FileNVRAM module would not work with Yosemite and the general advice was to switch over to Clover, as this was proven to be more reliable to get iMsg/F-Time to work. The FileNVRAM module has been updated and reworked to enable functionality with Chimera as the boot loader for Yosemite to a successful degree, but with a greater chance of breaking with any major Apple updates than with Clover as the boot loader.

Jay has advised a long time ago about making the switch to Clover and the reasons why we should make the switch, he also provided extensive Solutions and Guides to solve iMsg/F-Time connectivity problems in both Chimera and Clover. I am no longer familar with the Chimera method apart from what I have boned up and gleaned from Jay's tutorial, my limited knowledge is akin to the Clover method and will pass on or try to help with that limited knowledge when ever possible.

I am on Clover

 

[esafeddie]

Model: MacBookPro8,1
Board-id: Mac-94245B3640C91C81
SerialNumber:
Hardware UUID: A6A967A7-0360-510A-A55D-E452EDD22BAD

System-ID: 1C5E176B-8D57-45AC-BBCD-0A00E5356816
ROM:
BoardSerialNumber:

Gq3489ugfi: ec8b159d63048ecd26e5adfe815d78249e
Fyp98tpgj: 944b9cb69afb605197e69bf148fedc722d
kbjfrfpoJU: 46e3cb02c543aa6f201f113fe1b2cfb180
oycqAZloTNDm: 2b6020b333ddb9198f4fc9d8a510b9c47f
abKPld1EcMni: a8797cc4fb3a65f017d1ec7edd401f5e8f




hope i didnt post to much info

Ok - You could have blanked out your S/N and ROM, but we are all friends here. Are these values constant between reboots? if they are I see nothing wrong with the values you post. Am I right in assuming your boot loader is Chimera? If it is Chimera I think 'Stork' done a write up in one of his Builds or upgrade on the reworked FileNVRAM for Yosemite - sorry to be so vague on the subject, maybe someone can chip in and offer more clarity.

Ok I see you're on Clover

 

[esafeddie]

Ok - Note your DeBugger read outs, do three reboots and compare all values on each to insure they are constant between reboots.

 

[brick0044]

Yes they are all consistent. Could you edit out my serial and rom please?

 

[esafeddie]

Model: MacBookPro8,1
Board-id: Mac-94245B3640C91C81
SerialNumber:
Hardware UUID: A6A967A7-0360-510A-A55D-E452EDD22BAD

System-ID: 1C5E176B-8D57-45AC-BBCD-0A00E5356816
ROM:
BoardSerialNumber:

Gq3489ugfi: ec8b159d63048ecd26e5adfe815d78249e
Fyp98tpgj: 944b9cb69afb605197e69bf148fedc722d
kbjfrfpoJU: 46e3cb02c543aa6f201f113fe1b2cfb180
oycqAZloTNDm: 2b6020b333ddb9198f4fc9d8a510b9c47f
abKPld1EcMni: a8797cc4fb3a65f017d1ec7edd401f5e8f

@ brick0044 - I just noticed Your SerialNumber is missing in your readout, did you deliberately omit it? the reason I asked, its strange you left the Board's S/N in and the Mac S/N is missing (should be 12 Characters)

Sorry only you can edit your post - I have edited out your details from my quotes.

 

[brick0044]

Model: MacBookPro8,1
Board-id: Mac-94245B3640C91C81
SerialNumber:
Hardware UUID: A6A967A7-0360-510A-A55D-E452EDD22BAD

System-ID: 1C5E176B-8D57-45AC-BBCD-0A00E5356816
ROM:
BoardSerialNumber:

Gq3489ugfi: ec8b159d63048ecd26e5adfe815d78249e
Fyp98tpgj: 944b9cb69afb605197e69bf148fedc722d
kbjfrfpoJU: 46e3cb02c543aa6f201f113fe1b2cfb180
oycqAZloTNDm: 2b6020b333ddb9198f4fc9d8a510b9c47f
abKPld1EcMni: a8797cc4fb3a65f017d1ec7edd401f5e8f

@ brick0044 - I just noticed Your SerialNumber is missing in your readout, did you deliberately omit it? the reason I asked, its strange you left the Board's S/N in and the Mac S/N is missing (should be 12 Characters)

Sorry only you can edit your post - I have edited out your details from my quotes.

Iedited it out after your post saying i shouldnt have posted it