Hello, AF! First time poster, long time reader. In a nutshell, I believe I've inadvertently bricked my phone by way of a botched update. I checked for an update yesterday on the LG update program and, low and behold, there was. All was well until the update was about 60% complete, then it tells me there was a communication error with the phone. I follow the instructions, unplug it, remove and reseat the battery and reconnected it. It turns on fine, LG bootscreen loads, telus bootscreen loads and holds on the animated android bootscreen. I restart the update from the computer as per the programs instruction, and again, part way through, it tells me there was a communication issue. After this second botched attempt, the phone now loads the LG bootscreen, then immediately cuts to and hangs on the yellow "Emergency Mode!" screen. With the battery attached, the computer will not recognize the phone at all. Though, strangely, if I remove the battery and attach it to the computer, the computer will recognize it, identifying as "LGE Android Platform Composite USB Device" in the device manager. To clarify, it hangs on the "Emergency Mode!" screen regardless of whether the battery is attached or not, which is what I find strange. Attaching it to the computer with the battery removed, I opened the update program. It does identify with the program initially, but the program freezes about 6 bars into the "Checking the connection with the cell phone" routine and will effectively "un-hang" itself if I disconnect the phone from the computer. To note, I consider myself fairly technologically competent, but this has totally thrown me for a loop. I'm under the impression the emergency mode is specifically for directly flashing the ROM, but the part that really confuses me is what the battery being attached has to do with it being identified by the computer. I'll assume, based on past experience and a bit of guess-work, that as long as it is still identifying with the computer in some capacity, and also assuming emergency mode is what I suspect it is, I should be able to re-flash the ROM by some method or another. Sorry for the obscene length of the post, but I figure the more thorough I am, the more chance I have of finding a solution. Thanks in advance!