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??
I tried to downgrade from Kitkat to JB via flashtool this morning which I often successfully flashed with the same method. But while the flashing is going on and almost finish the flashing (system.img, userdata.img, etc. are already flashed), there seems to be some problem and popped out that the flashing is fail. And then the device does not boot up. While I tried to reconnect the device to PC, the PC cannot recognize the device as shown in the picture. Unable to process any further method. Does anyone in this forum knows how to recover the bricked device like this?
The phone starts? In a black screen?
If the PC detects it like that the phone has some energy and connection...
Does anything apears on the screen? Can you go to the Recovery Mod?
Have you tried to force the driver installation on that USB item that appears on device manager?
Do you have access via ADB or fastboot?
Did you nottest in what partition did the error message appeared?
Please provide some answers to these questions so i can try to help you...
RSGI_PT said:
The phone starts? In a black screen?
If the PC detects it like that the phone has some energy and connection...
9Does anything apears on the screen? Can you go to the Recovery Mod?
Have you tried to force the driver installation on that USB item that appears on device manager?
Do you have access via ADB or fastboot?
Did you nottest in what partition did the error message appeared?
Please provide some answers to these questions so i can try to help you...
Click to expand...
Click to collapse
Nothing on the screen. Not able to boot into recovery or adb is not working. The phone is just death. But, when I insert the usb cable, the pc can detect it. I even approach the Customer Care here in Aizawl, but they cannot fixed. Even when I followed the instruction as per one xda member posted here, The qualcom hs - 9006/8 is displayed on the device manager and when I tried to flashed it with emergency mode, the result always the same. FAILS
hruaiapunte said:
Nothing on the screen. Not able to boot into recovery or adb is not working. The phone is just death. But, when I insert the usb cable, the pc can detect it. I even approach the Customer Care here in Aizawl, but they cannot fixed. Even when I followed the instruction as per one xda member posted here, The qualcom hs - 9006/8 is displayed on the device manager and when I tried to flashed it with emergency mode, the result always the same. FAILS
Click to expand...
Click to collapse
Try this:
- Start GNQC with the phone disconnected
- Connect the Phone and see GNQC recognizes the QLoader
- If so, press power button until the phone vibrates
- Wait for the GNQC recognizes again the QLoader and press Download on Emergency Mode
Use this KIKAT ROM: https://docs.google.com/uc?id=0B8H5JoBDpTnJMGE2QTJPR0FWX0E
This worked for me, i had the phone completly died, not even recognized by the PC, waited a day and tried again.
Once the QLoader is recognized your good to go!!
I'm having another problem after that, now theres no GSM/3G signals....
I need a EFS backup with the TWRP recovery.... No one seems to have
RSGI_PT said:
Try this:
- Start GNQC with the phone disconnected
- Connect the Phone and see GNQC recognizes the QLoader
- If so, press power button until the phone vibrates
- Wait for the GNQC recognizes again the QLoader and press Download on Emergency Mode
Use this KIKAT ROM: https://docs.google.com/uc?id=0B8H5JoBDpTnJMGE2QTJPR0FWX0E
This worked for me, i had the phone completly died, not even recognized by the PC, waited a day and tried again.
Once the QLoader is recognized your good to go!!
I'm having another problem after that, now theres no GSM/3G signals....
I need a EFS backup with the TWRP recovery.... No one seems to have
Click to expand...
Click to collapse
my e7 died. you are stuck using flash tools. is not even recognized by most PCs. maybe it drain? I can do? help me
I have the same problem, screen is completely black after trying to instal newer official rom. When I connect it to PC, it detects "hid device". I tried power + volume buttons combinations, but nothing changes. Sometimes notification led turn red for a few seconds but nothing else. And once win xp randomly detected phone as that "q..." thing, but it doesn't anymore. What else can I do?
Can anyone help me? I tried everything and my phone is still hardbricked.
Hello guys
Today i received my E7 and i tried to update via the tool unfortunately something went wrong and now i cant open it nor fastboot or recovery. Some hours ago i tried to connect via usb and appeared on the GNQC but later it showed as unknow device. It was my first day with the phone. Right when i connect /disconnect the usb i can hear the sound but i cant do anything. Is it dead or i can revive it somehow?
It was the first day:crying::crying:
Reinstall the drivesbob the PC, press 30 secs on the power button than connect the phone to the PC. If appears a QLoader port use emergency download on gnqc 1.6.9.0
RSGI said:
Reinstall the drivesbob the PC, press 30 secs on the power button than connect the phone to the PC. If appears a QLoader port use emergency download on gnqc 1.6.9.0
Click to expand...
Click to collapse
PLZ HELP i try to update using this http://www.needrom.com/download/gionee-elife-e7-32g/comment-page-2/#comment-165291 but now my phone doest enen boot or fast boot or anything.. in the proces it said "firehose ping phone fail" and stopped updating since then my phone isnt booting or anything and my pc dont recognize it any more.. plz help
---------- Post added at 15:32 ---------- Previous post was at 15:29 ----------
RSGI_PT said:
The phone starts? In a black screen?
If the PC detects it like that the phone has some energy and connection...
Does anything apears on the screen? Can you go to the Recovery Mod?
Have you tried to force the driver installation on that USB item that appears on device manager?
Do you have access via ADB or fastboot?
Did you nottest in what partition did the error message appeared?
Please provide some answers to these questions so i can try to help you...
Click to expand...
Click to collapse
plz help...
PLZ HELP i try to update using this http://www.needrom.com/download/gion...comment-165291 but now my phone doest enen boot or fast boot or anything.. in the proces it said "firehose ping phone fail" and stopped updating since then my phone isnt booting or anything and my pc dont recognize it any more.. plz help
thianpa he thil hi i solve thei toh m
Well. First things first. the root of the issue is probably a bad usb port i guess as it's very unstable it even sometimes reboots into download mode on its own when i plug my phone to charge or even gives a Not charging state until i replug it many times then it gives the normal charging (AC) so it's a really messy one.
that's the usual anyway i was rooted and flashed a lollipop rom normally then bugged some apps so i decided to reflash stock kitkat rom however like i said it's a bad usb connection so sometimes the flashing goes slowly and i have to replug the cable for it got smoothly again.
this time i noticed this at 15% and instead of staying in download mode stuck at that the phone rebooted and ofcourse this time only a black screen no download mode no recovery no nothing i guess a typical hard brick? this is my first time dealing with a hard brick so i didn't know what to do at all so i'm still figuring out stuff anyway i installed Qcomm drivers and checked the device manager it's the 9006 one not the 9008 and it shows many drives on my pc (windows 7 64-bit) but no partitions in windows xp 32-bit on another pc and on the laptop it gives no drives i think. i tried with SRK tools it says everything as it should but when it's done i unplug the cable then reboot however still shows many partitions and no download mode.
I don't use my phone alot however i don't own another one so i kinda need help fast please so if anyone has any ideas don't hesitate please.
Thanks in advance.:good:
Update: After following the linux method i now don't have a black screen only stuck on lg logo and still no download mode.
the phone isn't recognized by the pc at all not even 9006 or 9006
the recovery gets stuck at processing and it doesn't say fastboot either on the logo screen.
Croshio said:
Well. First things first. the root of the issue is probably a bad usb port i guess as it's very unstable it even sometimes reboots into download mode on its own when i plug my phone to charge or even gives a Not charging state until i replug it many times then it gives the normal charging (AC) so it's a really messy one.
that's the usual anyway i was rooted and flashed a lollipop rom normally then bugged some apps so i decided to reflash stock kitkat rom however like i said it's a bad usb connection so sometimes the flashing goes slowly and i have to replug the cable for it got smoothly again.
this time i noticed this at 15% and instead of staying in download mode stuck at that the phone rebooted and ofcourse this time only a black screen no download mode no recovery no nothing i guess a typical hard brick? this is my first time dealing with a hard brick so i didn't know what to do at all so i'm still figuring out stuff anyway i installed Qcomm drivers and checked the device manager it's the 9006 one not the 9008 and it shows many drives on my pc (windows 7 64-bit) but no partitions in windows xp 32-bit on another pc and on the laptop it gives no drives i think. i tried with SRK tools it says everything as it should but when it's done i unplug the cable then reboot however still shows many partitions and no download mode.
I don't use my phone alot however i don't own another one so i kinda need help fast please so if anyone has any ideas don't hesitate please.
Thanks in advance.:good:
Update: After following the linux method i now don't have a black screen only stuck on lg logo and still no download mode.
the phone isn't recognized by the pc at all not even 9006 or 9006
the recovery gets stuck at processing and it doesn't say fastboot either on the logo screen.
Click to expand...
Click to collapse
You must have flashed wrong version of the rom .
After trying the linux method, if you cant get into fastboot mode, recovery or not in download mode, then try this : http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
This requires you to open your phone so be cautious .
Thanks I followed that guide. Download mode after. Using the Windows tool instead of Linux then flash tool normally.
Hi everybody,
ill try to make it short:
My 6p has entered into the bootlooping mode.
I have never unlocked the bootloader/changed ROM/kernal.
After I let it bootloop until the battery is dead it's changing from bootlooping into blinking red dot. Then when I charge it for a couple of minutes it comes back to life after 10~ min it's bootlooping again - so I have a window of possibilities to play with the setting. In that window I have used the "OEM unlocking" option.
In the bootlooping state when I boot into the bootloader and connect it into the PC the device doesn't recognize that it has been connected and a PC ,and the PC recognize a entry of new device but doesn't recognize it is a Nexus 6p.
this situation is the same when I connect the phone when it is alive.
I have installed adb and fastboot with this software
https://forum.xda-developers.com/showthread.php?t=2588979
with the 1.4.3 version it shows in the end of the process "0 files copied" and then I tried the 1.3 version and it showed that 4 files were copied but it also showed an error.
I have also downloaded ADB from google site but it does not work either.
When I try to open the powershell in a folder where I have downloaded an img and type in a fastboot command the computer doens't recognize any type of command.
So if anyone can help me ill be glad.
Thanks in advance,
Matan.
matan4442 said:
Hi everybody,
ill try to make it short:
My 6p has entered into the bootlooping mode.
I have never unlocked the bootloader/changed ROM/kernal.
After I let it bootloop until the battery is dead it's changing from bootlooping into blinking red dot. Then when I charge it for a couple of minutes it comes back to life after 10~ min it's bootlooping again - so I have a window of possibilities to play with the setting. In that window I have used the "OEM unlocking" option.
In the bootlooping state when I boot into the bootloader and connect it into the PC the device doesn't recognize that it has been connected and a PC ,and the PC recognize a entry of new device but doesn't recognize it is a Nexus 6p. Matan.
Click to expand...
Click to collapse
What is the new device identified as....Qualcomm HS-USB QDLoader 9008? Your phone may be stuck in EDL mode. If that is the case you need to search XDA and attempt solutions for that problem first.
Did you previously have your PC setup properly with the correct USB drivers and it was working OK, or just now trying to get your dead phone to communicate? If the former it may be the EDL issue above. If it was the latter, the communication problem may just be the drivers were never set up in the first place. Have you tried a different cable or port on your PC, or another PC?
With no access to the OS you will be unable unlock the bootloader or access to ADB because those have to be enabled FIRST in the OS, so there's no helping you here until you can actually boot into the OS. Do you have access to Recovery mode? Tried a factory reset? If you don't have recovery, that was a major omission.
Hey there guys!!!
Can you please help me with this?
Yesterday i tried to install a new ROM on my LG Android phone (My LG phone is not working properly, it has a reboot loop). I tried to do a factory reset without success -> the dead Android logo appeared :/
I put my phone in Download Mode and connected to the pc but Windows does not recognize my phone.. it says: "USB device not recognized.. the last USB device you connected to this computer malfunctioned and Windows does not recognize it"
I do not know what to do now.. when i try to flash a ROM with the LG Flash Tool it fails because LG program does not recognize my device..
PS: LG Support Tool recognizes my phone (it shows the model) but i cannot flash a ROM
Thanks!!:fingers-crossed: