I don't think so, after I pressed it it just turned off and it showed the LG symbol and then it went into the clockwork mod. I have no clue how to get to that lol. I'm not sure but I think so, I just tried to sideload the cyanogenmod using the adb device in the command prompt stuff. No clue how to check that. If you think it'd be easier I could Skype you or something.
If you do have adb set up, and you were able to use it to sideload a rom, then you can visually see what's on your phone by using the adb shell command. The words I bolded my last reply were meant to be commands. You can issue adb commands while in recovery without even selecting (pressing) any options in the recovery menu. Just start issuing commands while the phone is plugged into the pc and you're in recovery.
Adb shell is basically giving you rights to enter the phone and mess about. You can then look at the current file structure and determine the presence or absence of any files you might be curious about. Like the OTA udpate file or the cyanogenmod rom you may have pushed to the phone via adb sideload. So the command set (bold items) I'd use in this case is:
adb devices (just to check for connectivity. Should list your device #)
adb shell (if you get a # afterward, you're good. If it shows a $, then type
SU in order to proceed as root)
cd /cache/fota
ls-l
That list command (ls-l) should tell you what's in /cache/fota which is the spot the ota will be housed I believe and it may show up as a long string of numbers & letters as the filename. So if it's there, we should be able to remove it. Not sure if that would allow boot at that point, but it's something to try.
You could also, while you're in there, look to see if the cyanogen rom actually made it to the device. Not a bad idea by the way to push a rom to the device since that's a likely means to get a booting phone again. I'm not sure if there's a default directory cwm uses for adb sideload or if you already set the path when using it but if you're not sure, I'd start with listing the contents of the entire /sdcard and if that shows a subdirectory that appears to be a likely suspect, then drill in further and check there. So while still in adb shell...
cd /sdcard
ls -l
If the rom is on the root of the /sdcard directory then great. At that point you know you can install it via recovery. If not and if you see something like /sdcard/clockworkmod listed as a folder, then you might want to check that out. So...
cd /sdcard/clockworkmod
ls-l
If you aren't comfy with all the adb stuff, you could start instead by doing a "fake" install of a would be rom. So act like you want to install it but don't actually go through with it. That would allow you to look for the rom to see if it's there. To do that, use the clockworkmod menu options to "install zip from sdcard", "choose zip from sdcard", then you should be able to browse the sdcard and look for that rom. If it's there, you're in the clear but don't install it yet. You'd want to do a full wipe of data/cache/dalvik prior to installing the rom. So back your way back out the main menu, and wipe all those before installing.