[G2 Q&A, Help & Troubleshooting] kuwlij:
A few posters here claim that the G2 is unbrickable - but I think I can challenge that. It started off with me wrongly flashing the Cloudy ROM 3.0 - what I didn't realise only till later was that it was intended for the Korean variant of the G2. Dummy move indeed.. I had previously taken the necessary precautions and took a full titanium backup and ROM backup onto a USB drive via TWRP - I previously ran Cloudy ROM 2.2 with Dorimanx Kernel on KK 4.4.2.

Right now, the phone doesn't seem to power on via buttons. When I plug it to the PC via the USB, I get "QHSUSB_BULK" as an unknown device only.. no black screen while on, no drives or COM port.

First off I want to be clear that I know I and only I am responsible for bricking my phone - The reason I'm in this mess is completely down to my stupidity, and trusting 'educated guesses' instead of confirming specs black of white. Just wanted to be clear in case anyone gets the wrong impression.

So this is more or less the sequence of events;

1. After flashing, I got stuck in fastboot mode.. (can't find the link) I followed one post where I needed to flashed .img files via the Fastboot CLI (similar to ADB). I used the images from the LG G2 D802 16GB in europe. source.. It was a toss up between the EUR and non EUR, and so I made the first of my so called 'educated guesses' that sent this phone deeper into the ground.

2. Something went wrong as when I rebooted the phone (had no idea what had gone wrong at the time), I got no logo. After some time, I noticed the screen on with a black background. when plugged into the pc, the QHSUSB_BULK would appear and with it a bunch of drives that Windows thought needed repairing. so I followed This .. I installed ubuntu, booted to terminal so I don't get those auto discovery pop ups, I used the images recommended there for my device (again, it seemed to make sense to use the same that the OP was using for my LG G2 D802 16GB in europe... After I rebooted, it was to my horror that the screen didn't even turn on, with no drives being detected via USB.. just the QHSUSB_BULK. This is what made me realise that the culprit was most probably using wrong images rather than improperly executing the instructions.

3. I opened the phone and tried shorting some capacitors where I'm supposed to see the drives again to no avail. I even tried shorting the capacitors ends as described here to no avail. I done a good full hour shorting the hell out of those capacitors (the post says to keep at it till it works cos it can sometimes be a bit tricky) but I saw no change. I would like to try the DL mode described there but I can't figure out what I have to ground from the images shown in the post regarding the "BOOT CONFIG".

This is basically the state the phone is in at the moment. so to recap:

No bootloader,

no recovery,

no fastboot,

no download mode,

no drives when in QHSUSB_BULK mode,

no COM port.

From the multitude of unbricking guides here, I gather that I either need to see that bunch of drives again when via USB or a COM port. I tried installing Qualcomm drivers, thinking that if the pc recognises the device, I might get the pc to identify the COM port, but the driver couldn't be installed for the QHSUSB_BULK device (got some error.. I can update this post later).

I tagged this post as a question.. i'm sure there's a question here somewhere...

HELP?!