So you're saying you're using the option in clockwork to reboot to system and that's not working? If so does it act like it's rebooting but then just come back to clockwork recovery each time? Perhaps try wiping cache and dalvik cache and then try rebooting to system.

 

Did it actually seem to apply the update when you pressed on that earlier? As in did you get a update successful type of popup afterward?

If not, it'd be interesting to see if the update is still housed in the cache partition. Namely /cache/fota. Do you have adb and know how to use it while in recovery? If so, try an adb shell, then cd /cache/fota, then ls-l to see what's in there.

 

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.

 

I have assumed to this point that you forgot to make a nandroid backup but I suppose I should ask anyway because that would be the easy way out. Did you ever use the backup feature in clockworkmod recovery? If yes, just use the restore option now and choose your previous backup and let it apply.

If not, yeah pushing a rom to the card would be the next best route I can think of. If you're having problems with the device connecting, it's likely a driver issue. Those are always a pain. Don't forget, with the newer adb repositories, you have a popup that comes up on the phone screen the first time you use it. At that time, you must authorize the PC by pressing the "always allow this pc" or similar wording. If that isn't your issue, then again it appears to be a driver problem.

 

It could still be the drivers because just installing the USB driver doesn't always seem to cut it. It doesn't apply the adb interface driver which causes the device to not be recognized for adb usage. The problem we have now though is since your PC hasn't been authorized, I don't think you'll be able to do that in your current state because you need to answer a popup that shows up on the phone screen...and I don't think it'll come through while in recovery, not sure.

If you want to try it anyway, you can get the driver package here:

LG G2 Quick Guide - Pastebin.com

I'm pretty confident the D800 package is the 3rd one from the bottom that's 9.3 MB in size. Download to desktop and then unzip contents to a folder. Then plug in phone while at the SAME time, watching the device manager on your pc. If it all of a sudden shows an unknown device (yellow triangle), you could try manually updating it by right clicking on that device, update driver manually, choose location as that driver folder on the desktop. Point it to the entire folder, it'll seek out any compatible drivers in that folder if they exist.

Again, I'm worried about the ability to authorize the PC in your state though. And if you can't clear that hurdle, and therefore no adb, then the only other idea I have is to either use a .kdz or .tot file and reflash stock as outlined here:

LG G2 Stock Firmware (Go Back to Stock) - xda-developers

Little more intensive than I was hoping we could get by with but that should do the trick also.

 

iowabowtech: It's not the USB driver, but the "modem driver" it's complaining about right? Possibly wrong Driver package? Isn't there a Universal Driver install?

If all fails, would the LG Mobile Phone Support Tool an option?

How about a reset using the physical buttons?
http://www.lg.com/us/support/product-help/CT10000003-CT10000027-1380725261927

((johnathan4tw, let iowabowtech respond. I'm just throwing stuff out.))

 

I think you may need the modem driver. I think this site has it:
Download LGtool/SGtool and Drivers

 

Just to be sure, when you placed the united driver zip onto your desktop, you unzipped it into a regular folder right? All those contents need to be in a regular folder on the desktop for the drivers to be detected.

Aside from that, I think we might be able to get you into download mode. Long press the power button until the phone shuts down. At that point, I'm hoping it doesn't auto reboot to recovery. If NOT, then hold volume up while plugging the usb cord into the phone from the pc.

 

Maybe those would work idk. I crossed referenced the driver file name from the LG website and it seemed to match the one I posted (lg united drivers zip) so I figured that must be the one for the D800 but I'm not 100% on that.

 

In addition, after installing the driver package, with the phone not connected, reboot the PC, and use a different USB port and reconnect the phone.

 

My fault jon. I just checked that download I menioned in my post. It's just a zipped version of the .exe program. That's not what I was wanting. I'm hoping the actual driver files are zipped somewhere as is the case for my version, the verizon version. Maybe those ones you have now are the ticket. Do they have a bunchh of driver files inside the zip that you can actually open and see? If so, try updating the same way I mentioned from device manager but instead pointing to that new folder.

 

Whatever Stef linked.

edit: if you're talking about what kind of files, there should be some .inf files in there.

 

Yeah the .exe method of install doesn't seem to always work for the adb interface. Might try Koush's universal driver? Haven't heard if this is working for the LG G2 or not but might be worth a shot.

Koush

^^Try updating manually from device manager and point it to that.

 

I've heard of others having that same problem especially if you previously owned a Gnex. So no worries there so long as adb is working, we are cooking with gas now.

So do you know how to adb sideload a working rom? Personally, I'd recommend moving a stock(ish) rom instead of cyanogen because it needs google apps seprately. So find a rom for the ATT version that fits that description either here or at xda, etc and let's get it onto your phone.

If we have major problems using adb sideload (I'm no expert on that), we can instead just try good old adb push. That I can do.

Make darn sure it's a rom for the D800!!!!