May have a lead on VC LG Logo Brick, But Need Data

[O.a.T.]

Ran into this issue last night trying to update from V9 with nROM 1.5.1 to VC. I followed all the stickies to the letter:

1) Reverted to stock and unrooted phone.
2) flashed the V9 update.zip via LG recovery
3) updated to VC via LG Update Utility on the PC
4) rooted via the VC root guide
5) installed CWM recovery via the guide
6) got stuck at LG Logo screen

Ugh.

Finally was able to flash V9 back via the "Emergency Mode" sticky thread (following the directions in there and trying to flash VC WOULD complete fine, but phone would still be stuck at LG Logo after a reboot... with no means to get into recovery at all). Once I got V9 back on there, it booted fine and I was able to just restore the nandroid backup of nROM 1.5.1 without issue. Oddly enough, like many others mentioned, I never saw a screen that said "Emergency Mode". Just got the physical keys to light up, and a notification from Windows that a new USB device was plugged in (that Windows notice was how I knew whether or not it was actually in emergency mode at all).

Might give it a go again in the future if a reason for this stuck LG Logo is found

Yup, know what you mean. I followed the above procedure exactly too, never generating an adb error of any kind. But when I powered down/up after installing custom ROM, BANG!, the LG Logo hang.

I've been able to get it into recovery mode by pulling battery and doing 3 finger Optimus salute, sometimes necessarily multiple times. Kind of bothers me that I now have seen 4 variations on the latter with variances in volume down/up, and release at LG logo or hold until you enter recovery. Anybody want to comment on what is the proper way to enter into recovery mode?

Anyway, once in recovery mode, I could successfully boot into a usable phone. From there, after about a week, I finally gave up on VC and went to V9 via the above mentioned method. Not a big deal IMO, since I didn't really see any advantages in the new radio in my area and there were some graphics changes, presumably resulting from the new display drivers, that in fact I thought were much worse.