Database Users

[Q] Lg F320S Stuck on bootloop

Hi all,
My phone is bricked with following syptoms:
1) Not being recognised in download mode
2) Adb without root acess (unable to push files)
3) No recovery
Detailed problems
I have a (Korean) Lg G2 (F320s) and its stuck on bootloop. It goes into download mode with Vol + with plugging into computer but the computer doesnt recognise it as attached...no sound, nothing in device manager and no found by Lg Flashtools or Kdz updater.
When simply turning on i connect it to the PC it shows as an ADB interface device and i have ADB but no root authorization (my phone was rooted before).
Lastly when i try to enter recovery it just flashes a couple of times and goes black...back light still on. In this mode when i connect it to PC it shows up several drives and phone comes up as Qhsusb_bulk device. I read a thread using UBUNTU to repair this but it wont work for me....the PC just hangs up and Ubuntu is unable to mount the drives (Even after the settings from Dconf Editor).
Please help i have been stuck for days

Please help
Please help ppl... is there a possible solution to the problem..?? JTAG maybe??

[Q] G2 Soft bricked no ROM on Internal Memory

SOLVED!
Hello All.. I have searching for hours not making much progress. Last night my LG G2 ran out of battery and I plugged it into the car charger and it soft bricked. I've been pretty busy lately so I'm on an old ROM Optimus DE 2.2. I don't have the ROM saved and I've been trying to ADB sideload the ROM back onto my phone but in the command prompt it says device not found. I tried installing some generic drivers and that didn't work. I tried the LGUnitedMobileDriver and that isn't working either.
I'm not sure what to do next. I have ADB on my computer and ADB sideload on my TWRP recovery, so I would like to push the ROM on my phone so I can flash it without having to wipe my phone. What drivers do I need; right now my phone shows up under other devices in device manager. Or am I sideloading wrong? Any help please lol..
I was caught off guard because of the random soft brick. If I would have been working on my phone I would have had the proper backups made. Thanks for any help, it is much needed I need my phone back ASAP!! Thanks again.
SOLVED
Finally figured it out. I had to updated my device (LG G2) with the ADB drivers not the LG drivers.
I went into Device Manager, right clicked my phone, clicked update driver software, clicked browse my computer, clicked let me pick from a list of drivers, then selected ADB drivers, then selected HTC Dream Composite ADB Interface. I believe the drivers I last installed were Snoop05's adb-setup-1.4.2.
Then I did a backup in TWRP, then I sideloaded the ROM. Next I had to wipe everything but internal memory and the use Nandroid Manager to restore my data from the backup... Took my whole day but at least I have a phone again.

The car charger soft bricked it ?
So you have TWRP, the drivers you can get from the LG site too. Just search for your model and go to software update section. This is for D802, i dont know if the drivers are the same: http://www.lg.com/uk/support-mobile/lg-D802
Hmm..i dont know how to use the sideload..
Another way can be with USB flash drive and OTG cable, i used my usb flash drive with OTG cable to flash ROMs from TWRP

Last option is lg flash tool and then reroot

Thanks for your help guys.. I appreciate it! Looks like I just needed to update my phone with the ADB drivers in Windows 8 Device Manager. I'm back up and running.
But yea so weird.. I haven't flashed anything on this phone in months so I guess something was corrupted when it died. I think it was trying to boot with too low of a charge and the battery died mid boot which corrupted something.

Although you've solved it let me recommend you another way.
Use : "adb push romname.zip /sdcard/romname.zip"
instead of "adb sideload romname.zip"

[Q] LG L5 E610 bricked

Hello. Few months ago I installed unofficial Cyanogenmod 11 on my E610. After updating baseband it worked perfectly. After some time I decided to restore my phone to the state after installing CM11. It worked no problem. Today I wanted to do the same, and after installing SuperSU and Texdroider DPI I rebooted my cellphone, and it stucks on the cyanogenmod boot logo. If I try to get to recovery mode it stucks on the LG logo instead of CM. Hard reset is not happening at all. I tried to connect my phone via LG User Support Tool and install kdz firmware, but no luck. Although when I connect my phone without the battery to my PC i hear the "ding" windows sound, and phone exists in device manager. It also creates some disc drive in my computer, but unfortunately it's empty. I think textdroider has changed the build.prop file, so the cyanogenmod is not able to start at all. Is there any possibility to get to the build.prop file and change it, so phone will start? Or maybe somehow I can reset my phone or reinstall firmware using my USB cable without entering usb debug or recovery mode? Thanks in advance for any idea :crying:

Put your phone in Emergency Download Mode : switch it off, hold volume down button while plugging USB cable (already connected to the PC).
Then use the Support Tool to go back to LG ROM

mikesrike said:
Hello. Few months ago I installed unofficial Cyanogenmod 11 on my E610. After updating baseband it worked perfectly. After some time I decided to restore my phone to the state after installing CM11. It worked no problem. Today I wanted to do the same, and after installing SuperSU and Texdroider DPI I rebooted my cellphone, and it stucks on the cyanogenmod boot logo. If I try to get to recovery mode it stucks on the LG logo instead of CM. Hard reset is not happening at all. I tried to connect my phone via LG User Support Tool and install kdz firmware, but no luck. Although when I connect my phone without the battery to my PC i hear the "ding" windows sound, and phone exists in device manager. It also creates some disc drive in my computer, but unfortunately it's empty. I think textdroider has changed the build.prop file, so the cyanogenmod is not able to start at all. Is there any possibility to get to the build.prop file and change it, so phone will start? Or maybe somehow I can reset my phone or reinstall firmware using my USB cable without entering usb debug or recovery mode? Thanks in advance for any idea :crying:
Click to expand...
Click to collapse
in these cases emergency mode should work
removing battery sim sd etc... connect your phone to the pc throught us cable pressing vol- it automatically boot into download mode and you can easily use kdz.
make sure you have the last driver from lg websites else kdz wont find your phone, and set emergency option in kdz everything else it similar to a normal flash

[Q] No Recovery, No Download Mode, Not Recognized in Fastboot mode by PC

Hello there!
So I accidentally bricked my phone a few days ago and now it is resting as a brick on my desk, but how did all of this happen, you may ask?
Well, the story is rather simple, I had the Simple ROM V. 1.4 installed on my G2 and decided to update it to version 2.0, which is posted here somewhere, but what I didn't notice was that the file I was downloading (even though it said it was compatible with all versions) was not for the D800 but for the LS980 and this bricked the phone.
First I was stuck on fastboot mode and was able to get my download mode back, but it kept saying that it couldn't flash the stock rom because it was the wrong model.
Looking online and through these forums, I found out that it was because the download mode that it had was not the right one to use, and that I needed to "destroy" download mode, enter once again in fastboot mode and flash the new download mode, this, however, turned out out to be impossible as the fastboot mode is no longer being detected by Windows nor Linux.
I installed back the USB drivers, installed Android ADB, changed the UDEV rules with mew vendors ID from the list provided by Google, updated the drivers on my PC and even tried to change the directory in which the phone would appear.
The problem resumes to this:
When in fastboot mode (connected to the PC) and type
Code:
fastboot devices
in both Windows and Linux, I get the response as
Code:
???????? devices
.
When I try with
Code:
adb devices
I get back nothing.
Curious thing is that the phone does appear on Device Manager as an Android ADB device and when on Linux I use the
Code:
lsusb
I get back that it is being recognized as
Code:
Google Inc. 18d1 d00d
, which I believe is the phone.
When trying to run any fastboot commands, the phone stays on "waiting for device" on Linux or "flashing" on Windows and later a messages pops back at me with
Code:
Error too many links
.
With all this in mind, I would like to ask you guys, is there something that I am missing?
Any help will be truly appreciated!
PS. Forgot to mention that I have tried with other computers and have the same result and the model of my phone is the D800.

Just to add a bit more into the case.
I had installed prior to all this mess, TWRP which had a Nandroid backup in the internal storage and file backup.
When using the LG Flash tool (KDZ one) I am able to see the available storage, which is about 2.5gb. This leads me to believe that both the Nandroid backup and Backup files are still in the internal storage.
Also, I did some more digging and got information that it might be the USB cable, however, this cable worked fine the first time and with other devices. and while connecting the phone with it to the PC it will still register the device as connected, but apparently no USB port is assigned or fastboot flash tool does not find the phone.

LG G2 stuck in halfbrick and device not recognized by PC

I was having problem of device not recognized by PC at fist stage and i thought it was software issue and did factory reset and still problem was not solved and thought installation of cynogenmod would solve my problem so i followed the steps to install and rooted my device and as my PC dont recognize my phone i downloaded Autorec and followed simple steps and my phone stuck in fastboot mode and PC also dont recogize my phone..when i try to open download mode it goes back to fastboot mode...Any suggestion and help would be highly appriciated.