This is a very strange problem, assuming low level software/firmware/bios(?) related.
Background: Phone is 3rd physical phone (same model) I have had. First was water damage, Asurion replacement was still locked to someones account (wtf) so sent back, now with 3rd. All rooted, current running Liquid Gingerbread 3.0.
Cracked digitizer once, cracked the replacement digitizer upon forgetting to actually connect it internally (haha). 3rd digitizer works flawless and still in use.
The problem is as follows;
The phone will turn on, everything functions normally (normal as can be i guess). The screen works beautifully, displays all colors, full brightness, flows smoothly with whatever is being displayed. It never turns off when the screen is displaying something (ruling out a loose/broken connection). Screen dims and shuts off when idle as it should, but upon waking the device, no picture is displayed. Pressing the power button wakes the screen, in that the bottom row of softkeys(?) lights up, and the main LCD itself has the blueish tint from the backlight. During this period, the phone functions normally and responds to touch corresponding to what should be on the screen (digitizer still works and OS recognizes what is where and hasn't crashed).
If I press the power button again, all lights out. Press it again to wake, same as before with blueish tint and lit home keys. Press it again, lights out. Press it a 3rd time, screen/graphics appear. Wtf? For the first day it was doing this, it was 100% consistent that it would work on the third try. Two or Three days have passed, and now it takes anywhere from 3 - 10 tries to get graphics to appear, luck really. Also, the screen displays no graphics but has power/blueish tint when booting. No Motorola logo, no boot animation, no screen when it finishes booting. Commence the on/off waking cycle. I was going to attempt to do a wipe/recovery, but the screen will not display anything during even this low level access. I would rather not "guess" what I'm doing in the recovery.
Oh, and if you want somewhere to start looking maybe, this problem seems to coincide with the same day I selected the option to disable boot animations (LGB3.0). This may have corrupted something, but I have not been able to fix it with these types of settings as of yet. Normally I would try and fix this myself, but I'm out of ideas, and I travel quite a bit. I would like to have a functioning lifeline should something ever happen. And plus the ladyfriend gets mad when I cant answer T_T...
Any help would be GREATLY appreciated. If anybody feels up to it/wants more information, let me know and I will make a video depicting this issue and answer any questions. (have no access to video equipment atm, leaving work soon.)