Develop Bugs

is this **** bricked??

its just sitting on the freaking LG screen... every time i vol dwn + pwr and double press power it goes normal but then cwm doesn't come up and it just restarts and hangs at LG again. i ****ing hate this phone can someone please help me out? why won't cwm load

can you describe exactly the process you took to port CWM into your phone? Let's see if something happened along the way to cause it to not work properly.
Also, is CWM the one not working, or did you flash a ROM on your phone and something went wrong, and you are trying to get to CWM to restore your phone but not getting anywhere with it?

aquariuz23 said:
can you describe exactly the process you took to port CWM into your phone? Let's see if something happened along the way to cause it to not work properly.
Also, is CWM the one not working, or did you flash a ROM on your phone and something went wrong, and you are trying to get to CWM to restore your phone but not getting anywhere with it?
Click to expand...
Click to collapse
followed the steps on the cwm thread. used terminal emulator. worked great. was working fine until now. i flashed kernels beta 2 and only wiped cache and dalvik and now nothing is working. no cwm to restore, can't even get to the at&t boot animation. this is a mystery.

mic.mayorga said:
followed the steps on the cwm thread. used terminal emulator. worked great. was working fine until now. i flashed kernels beta 2 and only wiped cache and dalvik and now nothing is working. no cwm to restore, can't even get to the at&t boot animation. this is a mystery.
Click to expand...
Click to collapse
Sorry to hear that. Unfortunately I can't help much at all since I haven't done either yet (CWM or Kernels/rom installations) so rather than making things worse for you, I'll leave it to the Pros here to help you. Im sure one of them will respond back soon enough.

Try this:
Disconnect the phone and pull out the battery.
Put battery back in and plug phone to a wall charger. Let it boot to the battery charging screen. Once there press and hold POWER + VOLDOWN
Depends on type of the problem, it helped me 9 out 10 times...

tried it at least 20 times now. just realized that i didn't format /system nor did i update cwm yesterday. probably the root of all these problems. I'm just gonna start fresh with the kdz. I'm on a mac though so its going to be a long night starting with boot camp.

I'm having the same problems...well kind of...
I followed all the instructions for CWM and everything went great. No real issues but had to reinstall the .img twice and then was perfect thereafter. Saw the beta 2 ROM and figured what the hey...downloaded and installed to SD Card. Used CWM/Nandroid to do a backup then installed the zip for the ROM from the sd card.
It took a matter of 10 seconds and said it was successful/done and restarted phone-got a boot loop on LG screen for about 15 minutes and finally did a battery pull-tried several times to get it into CWM with no luck and finally was able to get in-but had to plug it into the wall and wait for charging screen to show. Was able to restore and all was well until turning the phone off.
Turning off the phone now causes the phone to loop on the ATT screen-I can get into download mode and can get into CWM and restore and all is well until turning phone off.
I figured it just needs a fresh install so I've been trying to flash the kdz but the firmware updater keeps faulting and never makes it through the process...so I'm stuck...have all the files I need (I believe) and have everything in place...just can't get it back to normal.
Any ideas from here?
Thanks in advance!

Yeah, sometimes it could be quicker just start over and restore backups...
While you there, would you mind do this: Needed SystemUI.apk from SU640
[EDIT]
@fishscale28:
did you do kdz unbrick before? If not, then perhaps you are not doing it right...btw, kdz file for LU6200 didn't work for me.

Nope-never done a kdz unbrick before-I have the kdz v10i_00 for the 640. I have all the drivers installed, the parser deal installed, windows enabler program running and use the kdz updater to update the firmware. Is there something Im missing here? Seems like several people have gotten the updater to crash when trying to update the firmware...any ideas why?
---------- Post added at 05:51 AM ---------- Previous post was at 05:38 AM ----------
I went through a few of the threads and saw there was a .dll file to be deleted in the updater folders so I did that and now I can do absolutely nothing with the program. Only start and exit...am unable to select anything, view anything, get anything to function...

fishscale28 said:
Nope-never done a kdz unbrick before-I have the kdz v10i_00 for the 640. I have all the drivers installed, the parser deal installed, windows enabler program running and use the kdz updater to update the firmware. Is there something Im missing here? Seems like several people have gotten the updater to crash when trying to update the firmware...any ideas why?
---------- Post added at 05:51 AM ---------- Previous post was at 05:38 AM ----------
I went through a few of the threads and saw there was a .dll file to be deleted in the updater folders so I did that and now I can do absolutely nothing with the program. Only start and exit...am unable to select anything, view anything, get anything to function...
Click to expand...
Click to collapse
I installed from the kdz yesterday and didn't have to delete any files. I'm on Win 7 x64. The first time it ran it told me to restart my phone cause it didn't see it, but the second time it ran until my phone reboot and I killed the program. Be sure you have the KDZ_FW_UPD_EN with UpTestEX_mod2_marwin.exe in it. Hope this helps.

Thanks for your help. I did all that...again...I even deleted, reinstalled all the updater stuff, tried running as admin, tried running in compatibility mode, ran it after deleting the recommended .dll file and the option to do anything was gone, put it back in and was able to run everything fine and a little after extracting the kdz it would crash. I unplugged the phone and re-ran the proggy and it went through the check, noticed the phone wasn't hooked up and finished the check. Plug phone in, start process over and proggy crashes.
I don't get it-I would say its the wrong kdz but its not. I installed all the drivers and it still doesn't work. I've tried every combo of everything and the proggies keep crashing.
Now I was finally able to get into CWM to flash another ROM and was able to get one going-was able to boot into the os but same as before-once the phone is turned off it starts the boot loop. Now its even harder to get back to CWM but a restore works from there. Any ideas on why the boot image keeps reverting back to whatever was screwed up? Has to be something that happens once the system starts up again as it's after a restore and when the phone is turned off. Stumped and would love to be able to use my phone...It seems like flashing the kdz would be the sure fire way to get it done-are there options aside from the updaters that keep crashing?
Thanks in advance!

Maybe http://www.microsoft.com/windows/virtual-pc/ can help?

alright so i got to the 4% thing and my phone rebooted but it kept looping to the screen LG Optimus LTE bootscreen with the pink candy cane. thats it. i did vol dwn + pwr and got the android arrow and box with loading bar no text, then it rebooted back to the optimus lte screen. never got to the setup screen. tried the kdz again and my phone died. now when i plug it in i only get download mode... does it charge in download mode and why did it not get to the setup screen?!

fishscale28 said:
Thanks for your help. I did all that...again...I even deleted, reinstalled all the updater stuff, tried running as admin, tried running in compatibility mode, ran it after deleting the recommended .dll file and the option to do anything was gone, put it back in and was able to run everything fine and a little after extracting the kdz it would crash. I unplugged the phone and re-ran the proggy and it went through the check, noticed the phone wasn't hooked up and finished the check. Plug phone in, start process over and proggy crashes.
I don't get it-I would say its the wrong kdz but its not. I installed all the drivers and it still doesn't work. I've tried every combo of everything and the proggies keep crashing.
Now I was finally able to get into CWM to flash another ROM and was able to get one going-was able to boot into the os but same as before-once the phone is turned off it starts the boot loop. Now its even harder to get back to CWM but a restore works from there. Any ideas on why the boot image keeps reverting back to whatever was screwed up? Has to be something that happens once the system starts up again as it's after a restore and when the phone is turned off. Stumped and would love to be able to use my phone...It seems like flashing the kdz would be the sure fire way to get it done-are there options aside from the updaters that keep crashing?
Thanks in advance!
Click to expand...
Click to collapse
Even after running the kdz, my phone still does that after installing CWM. I don't know if it's something with my ROM or something with CWM, but if you can't get into CWM you probably don't need to run the kdz. I couldn't get into CWM anymore when I ran it.

So you're saying you go into the boot loop after turning off your phone even after unbricking?

I don't get it-now I can't get into recovery and it keeps up with the boot loop. I've tried running on the virtual PC/XP deal and it doesn't crash but now it doesn't even see the phone...reinstalled all the drivers, etc. and still no luck. Is there anyway to get the kdz installed without this updater?

fishscale28 said:
So you're saying you go into the boot loop after turning off your phone even after unbricking?
Click to expand...
Click to collapse
Yes. I don't think that was happening until I put CWM on. But I can live with it until the issue is solved. I don't think I'm the only one having it.

[Q] @ Standstill with phone after multiple LGNPST and LGFLASHTOOL attempts to fix

Where to begin?
I upgraded from Paranoid Android (Android 4.3.1 variant) to KITKAT 4.4 which I believe has turned my phone into an LG E960? Nexus 4.
After some data issues with 4.4 I decided to go back to PA and things seemed OK for a day or two outside of com.android.phone crashes once in a while. Then a random power cycle (initiated by me) brought me to a softbrick? beyond repair (at least every flash/fix seems to do little)
I have been able to boot into both DLmode and Recovery (TWRP 2.6) since this problem began but nothing allows me past either of those or any of the following : LG Logo (reached after my 8th or 9th teenybin attempt, and first attempt at flashing stock teeny. OR the Google logo with tiny unlock symbol at bottom.
I became frustrated and wiped everything (formatted data) through TWRP and have failed miserably with every attempt to sideload or lgnpst both .zips and .bins respectively. Now any attempt to sideload results in a "failed" attempt as it there is no folder "TWRP/Backups/......."
I have tried LGFLASHTOOL and followed directions to a T. but the issue here seems to be this. LGFLASHTOOL recognizes my phone as the LG E960 and states the LG LS970.dll isn't compatible with my phone.
Is there anybody out there that can make sense of my ranting explanations here?
The two MAIN problems troubling me seem to be this:
1) The phone is being recognized as the E960 via FLASHTOOL thus any LS970 flash or file creates a not compatible error.
2)Though TWRP seems functional, it is maybe only partially so. It wants to access a folder within itself that isn't there TWRP/Backups/....(specific random backup number)
ANY help would be GREATLY APPRECIATED. I have been at this for a day and a half.
p.s. a very odd side note. One sideload rom I flashed was Carbon, which failed to boot initially. I DID manage to have teenybin unlock, flash and reboot the phone directly into Carbon (with no data or gapps) and was able to usb over a couple .zips before getting an error "cannot be copied because device has been disconnected or has stopped responding" I thought I was in the clear and booted back into recovery via the carbon rom to flash gapps only to revert right back to my initial problem(s).......
WTF! I am lost. I've had this phone for almost a year and have used LGNPST more than a couple times with great success. I've flashed, unbricked and restored this phone and many others multiple times over the years (i.e. not a noob) Just effing dumbfounded.
edit: I have searched and read through countless threads in an attempt to find a fix for my problem with no luck. I've searched constantly to find a fix with no luck.

That was a lot of info. So lets see if you've tried these things yet.
Are you sure you don't still have the att TWRP to flash KK?
Flash TWRP 2.5.0.0
And try to flash a Stock ROM.

to get sideload to work: there is an option to make a log. it will make the partition writable after a format. had a similar issue when i first go the phone.
otherwise use an img. not a teeny bin and go back to stock zvb.

engine95 said:
That was a lot of info. So lets see if you've tried these things yet.
Are you sure you don't still have the att TWRP to flash KK?
Flash TWRP 2.5.0.0
And try to flash a Stock ROM.
Click to expand...
Click to collapse
I noticed in bootloader it references the device as mako, with a bootloader version of MAKOZ10f
I'll try TWRP v2.5.00 now. I just downloaded a Stock ZVC build.
I feel dumber and dumber as this process drags on. But appreciate the replies. I now realize my OP wasn't full of a ton of specific information. Sorry.

octhrope said:
to get sideload to work: there is an option to make a log. it will make the partition writable after a format. had a similar issue when i first go the phone.
otherwise use an img. not a teeny bin and go back to stock zvb.
Click to expand...
Click to collapse
in TWRP (still 2.6) I went into Advanced and ran 'Copy Log to SD' a button/feature I have always saw before, and never used.
I'm going to try to install TWRP 2.5 back onto the device first per previous post(er) and then I'll run this again before I try to install a stock rom.
Thanks for the idea.

I've used fastboot to flash twrp 2.5 and proceeded to 'Copy log to SD' before attempting to sideload stock rom.
In CMD this error is now returned when using commnd "adb sideload update.zip" :
failed to write data 'protocol fault <no status>
LGNPST method still giving same results. Gets to 85% error (I know this is normal) but when rebooting, boots to nothingness/black screen after quick glimpse of Google logo....

toastedjelly said:
in TWRP (still 2.6) I went into Advanced and ran 'Copy Log to SD' a button/feature I have always saw before, and never used.
I'm going to try to install TWRP 2.5 back onto the device first per previous post(er) and then I'll run this again before I try to install a stock rom.
Thanks for the idea.
Click to expand...
Click to collapse
Glad to hear ZVC almost worked for you.
If you can get into fastboot, you can install a different TWRP. fastboot erase recovery then fastboot flash recovery recovery.img
Or in TWRP flash a different TWRP, octhrope has them all here. http://forum.xda-developers.com/showpost.php?p=47679587&postcount=123
EDIT. Yeah... I was slow. lol
---------- Post added at 01:36 PM ---------- Previous post was at 01:27 PM ----------
toastedjelly said:
I've used fastboot to flash twrp 2.5 and proceeded to 'Copy log to SD' before attempting to sideload stock rom.
In CMD this error is now returned when using commnd "adb sideload update.zip" :
failed to write data 'protocol fault <no status>
LGNPST method still giving same results. Gets to 85% error (I know this is normal) but when rebooting, boots to nothingness/black screen after quick glimpse of Google logo....
Click to expand...
Click to collapse
2 things:
Are you running as admin in the CMD prompt?
Make sure to use USB 2.0. Not USB 3.0
After LGNPST, press and hold the power button+vol up for 20sec+. Then press power+vol up again and maybe TWRP?

engine95 said:
Glad to hear ZVC almost worked for you.
If you can get into fastboot, you can install a different TWRP. fastboot erase recovery then fastboot flash recovery recovery.img
Or in TWRP flash a different TWRP, octhrope has them all here. http://forum.xda-developers.com/showpost.php?p=47679587&postcount=123
EDIT. Yeah... I was slow. lol
---------- Post added at 01:36 PM ---------- Previous post was at 01:27 PM ----------
2 things:
Are you running as admin in the CMD prompt?
Make sure to use USB 2.0. Not USB 3.0
After LGNPST, press and hold the power button+vol up for 20sec+. Then press power+vol up again and maybe TWRP?
Click to expand...
Click to collapse
A similar thing happened when flashing a stock ZVB rom via lgnpst. This time it hit 85% and rebooted past Googe and hung briefly on the LG logo. It started to boot and ran the "optimizing apps" function. It loaded the OS and a couple seconds later rebooted itself back into the hanging LG logo bit.
In using sideload, I had COMPLETELY forgot to "erase recovery" before flashing a new one. Maybe that was causing the issue? Flashing a recovery over a recovery. Time to try sideload again.....

When it gets back to lg logo and goes no further then turn it off and get back in recovery and do a factory reset
Sent from my LG-LS970 using xda app-developers app

foxsdaddy67 said:
When it gets back to lg logo and goes no further then turn it off and get back in recovery and do a factory reset
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
WOOOOOOO that did it for me! I'm now on stock 4.1.2 LMAO. I used LGNPST to get a stock (rooted) ZVB build onto it. I let it reboot and sit on the LG logo for 10 minutes to err on the side of caution, Then powered down and back into recovery to do a factory reset.
It can make calls and connect to wifi. But no data. Probably just need to flash the zvb radio but again I'm almost scared to turn off/reboot/update anything at this point. Just happy to see the phone back after 2 plus days all jacked up.
Thanks for the help everyone!

toastedjelly said:
WOOOOOOO that did it for me! I'm now on stock 4.1.2 LMAO. I used LGNPST to get a stock (rooted) ZVB build onto it. I let it reboot and sit on the LG logo for 10 minutes to err on the side of caution, Then powered down and back into recovery to do a factory reset.
It can make calls and connect to wifi. But no data. Probably just need to flash the zvb radio but again I'm almost scared to turn off/reboot/update anything at this point. Just happy to see the phone back after 2 plus days all jacked up.
Thanks for the help everyone!
Click to expand...
Click to collapse
Ive had that happen before and it was the only thing that i could find that would work. glad it worked for you
try updating your PRL and Profile now might get data back

foxsdaddy67 said:
Ive had that happen before and it was the only thing that i could find that would work. glad it worked for you
try updating your PRL and Profile now might get data back
Click to expand...
Click to collapse
I managed to do a complete back-up in TWRP of the fully functional 4.1.2 I got up and running. My data (wifi + lte) came back after I eventually flashed the correct radio.
I'm going to maybe stay stock for a couple days. I honestly can't remember the last time I used stock Android on my phone....
Right now I'm attempting to update it to zvc because i'm impatient. Fingers crossed.....

Normally I run stock rooted. Can't beat the battery life on stock. Running asop kit Kat right now
Sent from my LG-LS970 using xda app-developers app

[Q] Fastboot mode started udc_start() BRICKED!

my LG G PAD v500 is stuck at :
Fastboot mode started
udc_start()
the only thing hat i can do is to be turned off....help!!!!!!!!!!!!!!
:crying:
im unable to go to download mode...... can you please instruct me in detailed in what to do?

Hey i have the same problem
I have the same problem after i did a factory software upgrade and i was rooted but no recovery. did yo ever get it fixed

Solematrix said:
I have the same problem after i did a factory software upgrade and i was rooted but no recovery. did yo ever get it fixed
Click to expand...
Click to collapse
If this error shows up because of bad recovery, boot into normal ROM, root and flash stock recovery or twrp
If this error shows up because of bad boot.IMG, then you'll have to restore firmware from kdz file via download mode.(download mode = plug in usb plus volume up(?)... You should see a "Download" logo, brightness mat be very low and you have to squint )

Thanks
Yes thanx i figured it out from reading threw the forums but your help was much appreciated now to find out why my vk810 will not upgrade to 4.4.2 keep getting a error message
paperWastage said:
If this error shows up because of bad recovery, boot into normal ROM, root and flash stock recovery or twrp
If this error shows up because of bad boot.IMG, then you'll have to restore firmware from kdz file via download mode.(download mode = plug in usb plus volume up(?)... You should see a "Download" logo, brightness mat be very low and you have to squint )
Click to expand...
Click to collapse

Solematrix said:
Yes thanx i figured it out from reading threw the forums but your help was much appreciated now to find out why my vk810 will not upgrade to 4.4.2 keep getting a error message
Click to expand...
Click to collapse
I went to the Verizon store just now, their vk810 were still on 4.4.2, "check for update" says no update
Try updating via WiFi. If you removed any system apps, you need to put them back
Also, at least post the error :/... How can I help you debug if you don't tell me which step had the problem (can't search for update, update failed with x error code, tablet blew up to pieces during update...)

i did post it in another thread i started but never really got answers
paperWastage said:
I went to the Verizon store just now, their vk810 were still on 4.4.2, "check for update" says no update
Try updating via WiFi. If you removed any system apps, you need to put them back
Also, at least post the error :/... How can I help you debug if you don't tell me which step had the problem (can't search for update, update failed with x error code, tablet blew up to pieces during update...)
Click to expand...
Click to collapse
---------- Post added at 10:40 PM ---------- Previous post was at 10:37 PM ----------
i wiped it clean and started from new and it still say the same thing i tried it on wifi same time. i even took out my t mobile sim thinking it was that
paperWastage said:
I went to the Verizon store just now, their vk810 were still on 4.4.2, "check for update" says no update
Try updating via WiFi. If you removed any system apps, you need to put them back
Also, at least post the error :/... How can I help you debug if you don't tell me which step had the problem (can't search for update, update failed with x error code, tablet blew up to pieces during update...)
Click to expand...
Click to collapse

Hi,
Just to know if this problem is solved...
If it is, then this is most probably useless... unless somebody else stumps into the same problem.
If I can guess it correctly, this message typically display when you have rooted your V500, installed a custom recovery from an app flasher (i.e. Flashify, ROMToolBox...) and the recovery isn't compatible with your device and you tried a hard reset.
This means that you are able to boot into fastboot and that is what's going to save you
Why ? Simply put : because you can flash some files using the fastboot command line
Try to flash bootloaders, aboot, boot and recovery just for a try. You can find those I guess.
Regards.

Stuck with "Fastboot mode started"
I was currently on Altev vk81035b-rooted-SU installed but no custom recovery. I followed Altev-Hnk1 instructions for flashing aboot.4.2.2 & commands (dd if=/......Etc) you know the rest) which successfully copied the file. Then when I typed "reboot recovery" BAM, that's when my gPad slapped me in the face with the following--> Fastboot mode started udc_start()
I press & constantly hold "power & down" buttons which always brings me to "System Recovery" screen listing 4 options, "Continue reboot"-"Factory data reset"-"Wipe Cache"-"Safe mode boot". Anytime I have a problem I'll choose "safemode" which always got me back in after any "Boot Verification Errors", but now it doesn't & I'm stuck no matter what I chose. I'm starting to think I may need to connect my laptop and flash the KDZ starting from scratch with plain-Jane Verizon stock!?!? Whatcha think, yes-no-maybe so!?!? LOL

[Q] Need help with my E-988

I hope someone can help me.
I bought an LG Pro E-988 which is already rooted and have a nightly CM11 installed.
I saw the LG Flex Rom and tried to install. I hit an error (Status 7), so I restored my back up. It booted correctly and decided to install/run the LG Recovery and Freegee apps as I suspected that the error (Status 7) was because I didn't install the apps before the LG Flex ROM.
After I run FreeGee, I restarted in recovery and tried to install the ROM but still same error (Status 7). So I decided to restore my back up again, but this time around, the boot is not pushing through. I'm stuck in the LG Logo.
Has anyone experienced this before and maybe you can help me to fix my phone.
I admit I got a bit excited rooting and flashing custom ROMs again after 1 year of hiatus.
Thanks in advance!!

hd2_droid said:
I hope someone can help me.
I bought an LG Pro E-988 which is already rooted and have a nightly CM11 installed.
I saw the LG Flex Rom and tried to install. I hit an error (Status 7), so I restored my back up. It booted correctly and decided to install/run the LG Recovery and Freegee apps as I suspected that the error (Status 7) was because I didn't install the apps before the LG Flex ROM.
After I run FreeGee, I restarted in recovery and tried to install the ROM but still same error (Status 7). So I decided to restore my back up again, but this time around, the boot is not pushing through. I'm stuck in the LG Logo.
Has anyone experienced this before and maybe you can help me to fix my phone.
I admit I got a bit excited rooting and flashing custom ROMs again after 1 year of hiatus.
Thanks in advance!!
Click to expand...
Click to collapse
Nothing to worry about. Here is a pinned post where you can find all the information you need.
Just download your kdz from here and follow the steps from this post
Download kdz, install lg flashtool, lg drivers, after turning off your phone, press volume up and down together and connect your usb cable to get into download mode, then follow those pictures in that post to flash the kdz. You will be back to stock.

spirallingspiral said:
Nothing to worry about. Here is a pinned post where you can find all the information you need.
Just download your kdz from here and follow the steps from this post
Download kdz, install lg flashtool, lg drivers, after turning off your phone, press volume up and down together and connect your usb cable to get into download mode, then follow those pictures in that post to flash the kdz. You will be back to stock.
Click to expand...
Click to collapse
Thanks a lot man :good:! Although, I'm stuck with 'Connection error' in the FlashTool. Is this normal? I tried again and again more than 20 times but I'm getting the same connection error.
Also, earlier I was still able to go to recovery, but now even if I press the power button it goes straight to the download mode.
Hope you can help again.

You cant get out of download mode? did you try volume down and power button together for 5 secs? And btw what error are u getting on flash tool? its not detecting your phone? Did you install the mobile drivers?

spirallingspiral said:
You cant get out of download mode? did you try volume down and power button together for 5 secs? And btw what error are u getting on flash tool? its not detecting your phone? Did you install the mobile drivers?
Click to expand...
Click to collapse
The error was in the LG Mobile Support Tool (sorry to in the Flash tool). During the upgrading of the phone it always give the error - 'Connection to server failed. Try again in a moment'
Also, if I try to turn on the phone it will not boot but go straight to download mode.

hd2_droid said:
The error was in the LG Mobile Support Tool (sorry to in the Flash tool). During the upgrading of the phone it always give the error - 'Connection to server failed. Try again in a moment'
Also, if I try to turn on the phone it will not boot but go straight to download mode.
Click to expand...
Click to collapse
Did you remove the battery and put it back in? And it still goes to download mode? Try starting the phone pressing Volumedown+power key for sometime or you could try Volumeup+Homekey+Power to boot into recovery and try restoring backup or flashing some other rom and see if you can get out of boot. I really don't know why you are getting that connection problem. I got stuck at boot a couple of times and followed exactly what was given in that post and reverted back to stock. I guess some of the senior members will help you here. Meanwhile ill see if i can search a solution for that connection error, i haven't faced that yet so i really don't know the fix. There is a second TOT method given in that post, that might help.

spirallingspiral said:
Did you remove the battery and put it back in? And it still goes to download mode? Try starting the phone pressing Volumedown+power key for sometime or you could try Volumeup+Homekey+Power to boot into recovery and try restoring backup or flashing some other rom and see if you can get out of boot. I really don't know why you are getting that connection problem. I got stuck at boot a couple of times and followed exactly what was given in that post and reverted back to stock. I guess some of the senior members will help you here. Meanwhile ill see if i can search a solution for that connection error, i haven't faced that yet so i really don't know the fix. There is a second TOT method given in that post, that might help.
Click to expand...
Click to collapse
Yup, i tried removing the battery. Also tried different key combos to boot but it all goes to the download mode, with the small with box in the middle.
I also tried the option of going straight to the LG mobile support tool (not the LG Flash tool). But the same server connectiom error.
Thanks again for the help.
Hope other members can help me too.

Since I'm not able to do recovery using the KDZ file. Can I use the TOT file?
I have E988 Singapore version, but the last ROM installed was with a CM11. And in the Phone details it shows E980.
Will it work or will it just make things worst?

hd2_droid said:
Since I'm not able to do recovery using the KDZ file. Can I use the TOT file?
I have E988 Singapore version, but the last ROM installed was with a CM11. And in the Phone details it shows E980.
Will it work or will it just make things worst?
Click to expand...
Click to collapse
I haven't flashed using TOT method so i cant comment on that. I heard few people had trouble using flashtool on windows 8, are u you using windows 8? maybe try the kdz method again from a windows 7.

spirallingspiral said:
I haven't flashed using TOT method so i cant comment on that. I heard few people had trouble using flashtool on windows 8, are u you using windows 8? maybe try the kdz method again from a windows 7.
Click to expand...
Click to collapse
Yeah, I read that also. I used a windows 8 pc previously, that might be causong the connection error. I will try my old pc and hopefully it will work.
Thank you!

LG G3 Stuck In Bootloop

Hi XDA, many threads here have helped me in the past so time to ask another (probably stupid) question. It's a bit of a long story so I apologise in advance.
I've been running CM (one of the nightly builds from about 3 weeks back, don't have the file so I can't say which) on my phone for a while with no issues until a couple of nights ago when it was overheating (charging while playing a game, stupid I know) so I decided to turn it off so it could cool down without taking it off charge.
The following morning I turn it back on to find that it's getting to the blue android head logo of CM and getting stuck there. First thing I do is reboot into TWRP and flash my backup from right after I installed CM. Reboot and... same result. Okay, no biggie right? Time to reinstall CM (the latest nightly build from yesterday) and Google Apps (nano package) via TWRP and reboot again. Still stuck at the blue android head logo. The reinstall was handled after using the Wipe-Factory Reset function of TWRP, as the guide here explains.
At this point I decide to do a bit of research and learn that it's called a softbrick or bootloop and apparently flashing the stock rom can fix it. The LG software suite won't even recognise the device but a friend of mine found this guide so I attempted to run through it. All goes well until it comes time for the software to connect to the phone - I pop it in download mode while putting the USB cable in, the program says waiting for connection, runs for 14 seconds and says it's trying to put the phone into download mode, at this point it fails saying the phone can't be put into download mode.
Some of the comments beneath the article offer fixes like using USB 2.0 instead of 3.0, putting the program into compatability mode for Win7 and running in administrator mode. To be thorough I tried every USB port on my machine (both 2.0 and 3.0) and run the program in compatability mode (with and without admin mode) for several versions of windows. Same result every time.
Another friend then suggests that somehow permissions got borked and it might be worth reflashing SuperSU to the system but at this point I'm at a loss for how to do that. I have the one click root script that I got from god knows where (not this one because that didn't work for me) that has a SuperSU zip in it, presumably it flashes that to the phone when it runs (found this out the hard way because I've been a moron in the past and tried installing SuperSU through TWRP and broke the boot previously, fixed by re-running the one click root script - this was ages ago before even installing CM.)
So right now I can put the phone into download mode manually, get into TWRP and use all its functions as well as connect to my PC and use ADB functions while the phone's in TWRP but can't boot into CM or flash a stock rom. Any help would be appreciated, I've spent a whole day reading guides, asking friends and clumsily trying to fix this only to get nowhere.

Have u tried installing the stock via TWRP? Via zip ... Wipe cache delvik also..

jinderation said:
Have u tried installing the stock via TWRP? Via zip ... Wipe cache delvik also..
Click to expand...
Click to collapse
I haven't tried that, I didn't even know it was possible. Could you give me some more detailed pointers on how to do this? I noticed that the stock ROM I have cames as a .TOT file but CM is several files and folders in the zip. Will it install fine from that zipped up TOT file?
Thank you so much for your time.

When the rom is uploaded by the dev its also uploaded in .zip file place it ur system rom just go into twrp recovery flash the the zip file before flashing wipe cache n delvik too its easy as 1,2,3 search here on xda for ur compatible model

jinderation said:
When the rom is uploaded by the dev its also uploaded in .zip file place it ur system rom just go into twrp recovery flash the the zip file before flashing wipe cache n delvik too its easy as 1,2,3 search here on xda for ur compatible model
Click to expand...
Click to collapse
Thank you so much. I got it sorted. I really appreciate you taking the time to help me out with my stupidity.