The reason I'm going with no is that HDMI "chips" are coming with non-updateable code so if there are bugs like you describe no update short of board replacement can fix it. You can research further about this and find others that experience problems with the HDMI handshake system.
Yes it could be a cable issue but nothing in your post tells me it's a bad cable. That is, usually the system works until the cable goes bad. But your system has failed from day one so it's a HDMI chip issue.
I have a problem with my 42LK450U TV and I hope someone can help.
When I use my laptop running Windows 7 and connect to my TV using an HDMI to HDMI cable, I can later change input to antenna or switch TV to standby, and then reselect the HDMI input, and the TV will reconnect to the laptop. No problems.
However, when I use my ageing desktop running Windows XP, and connect using a DVI (desktop) to HDMI (TV) cable, the TV cannot reconnect to the desktop after switching input to antenna or putting on standby. When I select the correct HDMI input, I get a 'No Signal' message. Also, I can only connect the TV to the desktop immediately after the computer has been switched on - if I wait 5 seconds or so, the TV will not find a signal.
It doesn't matter which HDMI-in port I use.
Is this due to a technical shortcoming due to DVI or the operating system, or is it a problem with the TV? Can it be fixed?