Related
I don't know if the phone is bricked, i sure hope not.
I had cm7 final running just fine. I was installing a kernel from clockwork recovery, and i followed the instructions. It installed, i told it to reboot the phone, it came to the cm7 blue booting screen. it kept repeating that for over 20 minutes. at that point i pulled the battery and replaced it. then i think it was stuck at the tmobile splash screen for a while. i was able to reboot and get to recovery mode again, i wiped cache and tried to install the kernel again, this time got an error. now it went to tmo splash screen and froze there for a while. after another battery pull, nothing will display on the screen and i cannot access recovery mode (i try by holding volume down, then holding power button). the ONLY thing that does happen is that the lcd backlight will stay on until i pull the battery. i plugged into pc without the battery, lcd lights up, but its not recognized by windows or adb.
I'd be grateful for any possible help or ideas, thanks in advance.
Could you give more info on Rom recovery kernel you were attempting etc?
Sent from my HTC Glaciee using XDA Premium App
Jay10826 said:
I don't know if the phone is bricked, i sure hope not.
I had cm7 final running just fine. I was installing a kernel from clockwork recovery, and i followed the instructions. It installed, i told it to reboot the phone, it came to the cm7 blue booting screen. it kept repeating that for over 20 minutes. at that point i pulled the battery and replaced it. then i think it was stuck at the tmobile splash screen for a while. i was able to reboot and get to recovery mode again, i wiped cache and tried to install the kernel again, this time got an error. now it went to tmo splash screen and froze there for a while. after another battery pull, nothing will display on the screen and i cannot access recovery mode (i try by holding volume down, then holding power button). the ONLY thing that does happen is that the lcd backlight will stay on until i pull the battery. i plugged into pc without the battery, lcd lights up, but its not recognized by windows or adb.
I'd be grateful for any possible help or ideas, thanks in advance.
Click to expand...
Click to collapse
Um sorry to say but your screwed. Sounds like a true brick to me
Sent from my HTC Glacier using XDA Premium App
Can you boot into the bootloader? Which one is installed? How can we help if we have no idea what's installed on your phone? There could be hope if you can boot into the bootloader and have the engineering SPL installed.
Also, what kernel were you trying to install?
TeeJay3800 said:
Can you boot into the bootloader? Which one is installed? How can we help if we have no idea what's installed on your phone? There could be hope if you can boot into the bootloader and have the engineering SPL installed.
Also, what kernel were you trying to install?
Click to expand...
Click to collapse
He already stated that he could not boot into h boot
Sent from my HTC Glacier using XDA Premium App
mark manning said:
He already stated that he could not boot into h boot
Click to expand...
Click to collapse
He did? I only saw that he could not boot into recovery. I was thinking if his recovery is screwed up, he could still use fastboot to flash a new recovery and then be able to wipe and start over. If he can't get into the bootloader or recovery, then yeah, it's the dreaded B word.
I'd really like to know what kernel he was trying to flash.
TeeJay3800 said:
I'd really like to know what kernel he was trying to flash.
Click to expand...
Click to collapse
Me too......
TeeJay3800 said:
I'd really like to know what kernel he was trying to flash.
Click to expand...
Click to collapse
First thing I asked.. still no reply kinda sucks when they can't help by responding so we can help them..
Sent from my HTC Glaciee using XDA Premium App
I was flashing the #107 kernel from this thread:
[Kernel]Gingerbread[2.6.32.36]MaxOC~1.84GHz,Smartass/UV/BFS/BFQ/SLQB-Faux123[Apr-10]
http://forum.xda-developers.com/showthread.php?t=957267
I'm not sure if there's a different procedure to get into hboot as opposed to recovery. I've only had the mytouch 4g for about a week (always had Nexus one before). After pulling and replacing the battery, i hold volume down, then hold power button. Is that how to get into recovery and/or hboot, or is there another procedure I can try?
I used the visionary app to obtain root, install rom manager, then installed clockword mod recovery and cm7 through that. Working fine for a few days until i decided to flash the kernel to get better battery life....
Jay10826 said:
I was flashing the #107 kernel from this thread:
[Kernel]Gingerbread[2.6.32.36]MaxOC~1.84GHz,Smartass/UV/BFS/BFQ/SLQB-Faux123[Apr-10]
http://forum.xda-developers.com/showthread.php?t=957267
I'm not sure if there's a different procedure to get into hboot as opposed to recovery. I've only had the mytouch 4g for about a week (always had Nexus one before). After pulling and replacing the battery, i hold volume down, then hold power button. Is that how to get into recovery and/or hboot, or is there another procedure I can try?
I used the visionary app to obtain root, install rom manager, then installed clockword mod recovery and cm7 through that. Working fine for a few days until i decided to flash the kernel to get better battery life....
Click to expand...
Click to collapse
Unfortunatly its the same procedure, hold volume down and power on. So if when u do that nothing happens and adb doesn't work your phone is done.
Sent from my HTC Glacier using XDA Premium App
A little more info, maybe good news...i've been trying to get it to do anything for the last few hours. i had the battery out for a while. When i would plug it into AC charger or my pc with no battery, nothing would happen. however now i put in the battery, plugged it into the pc, and NOW the orange charging light is on like its charging...i haven't tried to turn it on or anything yet though.
Jay10826 said:
A little more info, maybe good news...i've been trying to get it to do anything for the last few hours. i had the battery out for a while. When i would plug it into AC charger or my pc with no battery, nothing would happen. however now i put in the battery, plugged it into the pc, and NOW the orange charging light is on like its charging...i haven't tried to turn it on or anything yet though.
Click to expand...
Click to collapse
I'm not sure what the exact status of your phone is, but usually flashing a kernel does not brick the phone. If anything the ROM won't run right or there will be other problems, but never do they prevent the phone from booting into recovery (the recovery partition uses a completely different kernel). When you try turning it on again, don't bother trying to let it boot normally. Hold down power and volume down and see if you can get into recovery. Then run all three wipe options and flash a new ROM.
Jay10826 said:
A little more info, maybe good news...i've been trying to get it to do anything for the last few hours. i had the battery out for a while. When i would plug it into AC charger or my pc with no battery, nothing would happen. however now i put in the battery, plugged it into the pc, and NOW the orange charging light is on like its charging...i haven't tried to turn it on or anything yet though.
Click to expand...
Click to collapse
It's happened to me before where I thought I had completely bricked the phone. It crashed in CM7 RC2 when I tried to mess with the DSP settings. After that, I went through the same situation as you. I got tired of it, left it charging overnight while it was stuck on the splash screen. The next morning, it was on like nothing happened. I'm thinking it just needed to sort itself out. Not really a fix or suggestion, but at least an indication that there is hope.
Nah, its dead man. Not on its entirety but virtually. I know that JTAG could be an option albeit, im not sure.
I can assure you though that there must be something extra u must have missed that caused this, did you play with radio's or SPL's? Cause that is how i bricked a magic lol
blah
mine bricked on restoring. got to the point of not responding to anything - power button and even charge indicator no longer worked.
sorry to hear OP. it's bricked.
Jay10826 said:
I was flashing the #107 kernel from this thread:
[Kernel]Gingerbread[2.6.32.36]MaxOC~1.84GHz,Smartass/UV/BFS/BFQ/SLQB-Faux123[Apr-10]
http://forum.xda-developers.com/showthread.php?t=957267
I'm not sure if there's a different procedure to get into hboot as opposed to recovery. I've only had the mytouch 4g for about a week (always had Nexus one before). After pulling and replacing the battery, i hold volume down, then hold power button. Is that how to get into recovery and/or hboot, or is there another procedure I can try?
I used the visionary app to obtain root, install rom manager, then installed clockword mod recovery and cm7 through that. Working fine for a few days until i decided to flash the kernel to get better battery life....
Click to expand...
Click to collapse
By saying that you used the visionary app to obtain root, is that all you did? Then installed rom manager and etc etc etc? Did you go through the full root method to get S=OFF as well?
Well previous to using visionary...i was trying another method to root using the terminal, but it wasn't working, so then i found visionary and used that. I never interacted with the phone using adb, if it matters. If i never really had s=off, could this be why this whole thing happened?
Jay10826 said:
If i never really had s=off, could this be why this whole thing happened?
Click to expand...
Click to collapse
Yes it probably is
Sent from my HTC Glaciee using XDA Premium App
Jay10826 said:
Well previous to using visionary...i was trying another method to root using the terminal, but it wasn't working, so then i found visionary and used that. I never interacted with the phone using adb, if it matters. If i never really had s=off, could this be why this whole thing happened?
Click to expand...
Click to collapse
Not really, if you were able to run a custom ROM with no problems before then you were rooted properly. Somwhere after you must have gone wrong, not sure where
blah
Hey guys, I know this is the 1000th time you've seen this thread. However, I might be a little different.
I've read all the red blinking threads before posting this one.
ROM: CM10 Stable Snapshot
Kernel: Franco r53
Okay, yesterday as I was downloading and I opened a game, my phone screen just turned off completely. I'm assuming it was due to overheating as the phone was getting pretty hot.
So I assumed it died, no big deal. I tried to boot up using power button, no luck.
Then I panicked and started searching XDA for all these red blinking LED of doom threads.
I managed to get the phone to boot up to the Google screen by having it on a wall charger + hold the power button for 10 seconds. But then it just shuts down. I managed to make it stick with bootloader, but only on the wall charger, which isn't much help. On a USB connection with my computer, I'm not able to even open boot loader as it would just open and turn off the phone within a few seconds.
Threw it on the charger over night, no luck.
This morning, nothing has changed.
So what's weird about my situation is, I can get it into fast boot, but only when it's on a wall charger, nothing else. And getting it to Google logo for a few seconds.
Edit: I can't RMA, because when it boots to Google logo, it says bootloader is unlocked (the little icon). And I also bought the phone off Swappa, so it's not attached to my account (is it even possible to claim warranty?)
Interesting this sounds like a hardware problem all right. Simply because you said it works on the mains charger which has an output of 1.2a were as the USB to PC chargers phone at rate of 400ma. I would try getting a replacement if you can. Also are you able to boot into recovery through boot loader if so you could try wiping everything or restoring from back up.
Okay, something weird. I tried a different method of getting into fastboot, and it worked (connected to PC).
Hold volume - (DOWN) by itself WHILE plugging in the USB cable. And now I'm in fastboot. Now I'm just trying to find a way to erase cache via toolkit x)
Edit: Weird, toolkit picks up the ADB device but manual adb doesn't using adb devices command.
I've read another user who fixed this by removing the back, then disconnecting and reconnecting the battery connector. Sorry I can't find the post but I'm sure it was in one of the I bricked my phone threads.
Yeah, I saw that, too. But I don't have the equipments for it, unfortunately
ADB won't recognize my nexus 4.
Toolkit will (so I know that toolkit is installed properly). I tried opening a command prompt through toolkit and I couldn't run anything.
Any suggestions?
draikz said:
ADB won't recognize my nexus 4.
Toolkit will (so I know that toolkit is installed properly). I tried opening a command prompt through toolkit and I couldn't run anything.
Any suggestions?
Click to expand...
Click to collapse
Adb won't work from bootloader, you should have fastboot access though
I'm in fastboot now.
I cannot get into recovery =[ When I select recovery, it would just turn off the phone and the blinking lights begins again.
Try charging overnight with other charger, not stock
Sent from my Nexus 4 using xda premium
Just tried with a nonstock charger. It blinked red. Then the battery charging screen popped up (first time ever). And now it's dead blinking red again.
Hopefully I'll see results overnight.
draikz said:
Just tried with a nonstock charger. It blinked red. Then the battery charging screen popped up (first time ever). And now it's dead blinking red again.
Hopefully I'll see results overnight.
Click to expand...
Click to collapse
That's a good sign! Sounds like it was in some serious deep hibernation! The fact that the battery icon popped up shows u didn't brick it or anything, its just really really dead! However when I had my problem, I had just a red light on all the time, it never blinked
Sent from my Google Nexus 4
Mine is constantly blinking. :'(
And it's probably not dead because I did manage to get it into fastboot. And I got adb to pick up using fast boot.
Every after reflashing recovery, I can't get into anything other than fastboot. When I try to select "Recovery" from the fastboot menu, it just turns off and continues to blink ;[
if you can get it into fastboot while plugged in your pc, scroll down in fastboot to the "power off" option. leave it there to charge up for a bit. you can check if its charging by using adb
Code:
adb shell cat /sys/class/power_supply/battery/capacity
hopefully it comes back to life after you charge it a bit. After it charges I would flash stock images just to be safe.
rayford85 said:
if you can get it into fastboot while plugged in your pc, scroll down in fastboot to the "power off" option. leave it there to charge up for a bit. you can check if its charging by using adb
Code:
adb shell cat /sys/class/power_supply/battery/capacity
hopefully it comes back to life after you charge it a bit. After it charges I would flash stock images just to be safe.
Click to expand...
Click to collapse
Okay, trying that now. It's been on the charger all night.
How does one ADB with the phone "powered off"?
So if the phone died because of heat, didn't it throttle properly? How is this possible?
Why don't you reflash stock images through fast boot? I don't understand why the need to be in recovery?
Sent from my Nexus 4 using Tapatalk 2
Lownita said:
So if the phone died because of heat, didn't it throttle properly? How is this possible?
Click to expand...
Click to collapse
I'm not really sure. I'm just assuming that it died from heat.
joshnichols189 said:
Why don't you reflash stock images through fast boot? I don't understand why the need to be in recovery?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I thought I had to factory reset it first inorder to flash factory image? (Coming from CM and Franco) At least that's how I always done it or it'd get stuck in a boot loop on my old phone.
But it is my last resort as well, because I have some precious data on this phone x)
Oh and Google pulled factory images, do you knows know where I can get a copy of one?
draikz said:
I'm not really sure. I'm just assuming that it died from heat.
I thought I had to factory reset it first inorder to flash factory image? (Coming from CM and Franco) At least that's how I always done it or it'd get stuck in a boot loop on my old phone.
But it is my last resort as well, because I have some precious data on this phone x)
Oh and Google pulled factory images, do you knows know where I can get a copy of one?
Click to expand...
Click to collapse
Mskip tool kit has images. There might be a thread in general section with them
Sent from my Nexus 4 using xda premium
rayford85 said:
Mskip tool kit has images. There might be a thread in general section with them
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I've not flashed stock before for this phone. And I'm afraid it might be different.
So question noob question.... Do I flash the booterloader and radios too? I've read that it's pretty dangerous to flash those.
I'm following this guide: http://forum.xda-developers.com/showthread.php?t=2010312
Any instructions I should do differently?
EDIT: I just flashed stock, nothing happened. Still could only get to fastboot. I am now losing hope.
draikz said:
I've not flashed stock before for this phone. And I'm afraid it might be different.
So question noob question.... Do I flash the booterloader and radios too? I've read that it's pretty dangerous to flash those.
I'm following this guide: http://forum.xda-developers.com/showthread.php?t=2010312
Any instructions I should do differently?
EDIT: I just flashed stock, nothing happened. Still could only get to fastboot. I am now losing hope.
Click to expand...
Click to collapse
IF ur going to rma it don't forget to lock the bootloader :angel:
Hi all,
I was upgrading to android 4.3 using the factory image provided by google. During the upgrade it displayed a message that it will restart my phone in bootloader mode. But the phone never restarted and since then it isnt turning on. When i try to get into recovery mode using power + vol down or even just press the power key the phone does not turn on, instead the led flashes in red color till i let go of the keys.
For the red led issue i found this link http://forum.xda-developers.com/showthread.php?t=2250454. But on few other threads i read that if it shows QHSUSB_DLOAD in device manager on windows then you phone is bricked.
Can someone help me here. Not sure if my phone is bricked completely.
P.S. I was on stock rom + franco's kernel before flashing 4.3.
Did you use the correct image for the phone? The correct one should have 'Occam' in the file name.
mumaster20 said:
Did you use the correct image for the phone? The correct one should have 'Occam' in the file name.
Click to expand...
Click to collapse
yes, i flashed the file files for nexus 4 only. I have kept the phone attached to AC charger for 3 hours, still it's not booting :crying:
Did you use the guide by efrant to return to stock? or how did you tyry to do it?
mumaster20 said:
Did you use the guide by efrant to return to stock? or how did you tyry to do it?
Click to expand...
Click to collapse
I was on stock rom only. I downloaded the image for nexus 4 from google's site and ran the flashall.bat file. Then it showed a message 'Pushing bootloader' and this was successful then it displayed a message saying 'restarting phone in bootloader mode'(Initially connected the phone by pressing power + vol down). After that the phone never restarted. Since then I am not able to start my phone.
c4sp3r said:
I was on stock rom only. I downloaded the image for nexus 4 from google's site and ran the flashall.bat file. Then it showed a message 'Pushing bootloader' and this was successful then it displayed a message saying 'restarting phone in bootloader mode'(Initially connected the phone by pressing power + vol down). After that the phone never restarted. Since then I am not able to start my phone.
Click to expand...
Click to collapse
Do what it says in the red light thread. That should set you one step closer to solving your problem
Sent from my Nexus 4 using xda app-developers app
The OP has obviously flashed with the battery too low...
N10AP said:
The OP has obviously flashed with the battery too low...
Click to expand...
Click to collapse
the battery was at 30%... is there anyway to recover now?
If there is no sign then only a mother board replacement can be done, I hope u had bought the an official Indian piece with warranty and not an import.
please follow the red light of death thread. That should get you into bootloader / fastboot. Then reflash
N10AP said:
please follow the red light of death thread. That should get you into bootloader / fastboot. Then reflash
Click to expand...
Click to collapse
ohk, thanks will try this out.. hope it helps
i tried going back to stock firmware using the method in general section but i always seem to get an error at 49%. can someone explain how to get passed this.
i using the t-mobile d801.
also my recovery seemed to have gotten erased because i cant boot into twrp anymore.
LG G2 Stuck @ 49%
El Killer said:
i tried going back to stock firmware using the method in general section but i always seem to get an error at 49%. can someone explain how to get passed this.
i using the t-mobile d801.
also my recovery seemed to have gotten erased because i cant boot into twrp anymore.
Click to expand...
Click to collapse
HEY! I'm on the d801 as well and I've been where you're at a number of times, unfortunately. But I've always gotten out. Here's the conclusion I've reached. Trying to flash directly back to stock without wiping all the partitions first is what makes the RDTool get stuck. It's like the phone runs out of memory and can't host a full Gig+ of data since your last ROM is in the way. Sorry if I'm wrong but I'm only assuming you didn't wipe everything except the Internal storage. The good thing every time this has happened to me is that your recovery partition should be intact. Mine always is, and we're on the same variant. Another thing, booting back into recovery is not impossible. It's all in the timing it takes from the first time you see the LG logo while holding volume - and the power button, but don't let go. What worked for me was to let the phone cycle between off and boot power states twice until the phone is completely off again. You may even notice the LED indicator flash red. Release your keys if the phone stays off and immediately hold the combo down again until the phone tries to boot again just don't let go of the buttons. Once it powers down again, leave the phone alone for a few minutes. Come back and this time get ready to boot into recovery. The combo button press will initiate boot but don't let go until the next time you see the LG logo flash, then quickly release and depress the vol down power up combo and hold. May take a minute longer than usual but the reset menu should pop up thereafter. Tap power 2 more times and you should back into recovery. It's worked every time for me. Let me know if you're good and whether this helped!
Good Luck,
tinydynamite00
try with x86
El Killer said:
i tried going back to stock firmware using the method in general section but i always seem to get an error at 49%. can someone explain how to get passed this.
i using the t-mobile d801.
also my recovery seemed to have gotten erased because i cant boot into twrp anymore.
Click to expand...
Click to collapse
i had exact same issue that progress stucked on 49%. if you are using 64bit OS, try to flash it with 32bit(x86) OS
good luck
tinydynamite00 said:
HEY! I'm on the d801 as well and I've been where you're at a number of times, unfortunately. But I've always gotten out. Here's the conclusion I've reached. Trying to flash directly back to stock without wiping all the partitions first is what makes the RDTool get stuck. It's like the phone runs out of memory and can't host a full Gig+ of data since your last ROM is in the way. Sorry if I'm wrong but I'm only assuming you didn't wipe everything except the Internal storage. The good thing every time this has happened to me is that your recovery partition should be intact. Mine always is, and we're on the same variant. Another thing, booting back into recovery is not impossible. It's all in the timing it takes from the first time you see the LG logo while holding volume - and the power button, but don't let go. What worked for me was to let the phone cycle between off and boot power states twice until the phone is completely off again. You may even notice the LED indicator flash red. Release your keys if the phone stays off and immediately hold the combo down again until the phone tries to boot again just don't let go of the buttons. Once it powers down again, leave the phone alone for a few minutes. Come back and this time get ready to boot into recovery. The combo button press will initiate boot but don't let go until the next time you see the LG logo flash, then quickly release and depress the vol down power up combo and hold. May take a minute longer than usual but the reset menu should pop up thereafter. Tap power 2 more times and you should back into recovery. It's worked every time for me. Let me know if you're good and whether this helped!
Good Luck,
tinydynamite00
Click to expand...
Click to collapse
still no luck
El Killer said:
still no luck
Click to expand...
Click to collapse
OK. So tell me, what ROM were you on, which recovery version and name are you using, why were you flashing back to stock, i.e. were you having problems, what kind. Explain as much as you can in detail. Need to retrace your exact steps to best get you fixed up!
tinydynamite00
tinydynamite00 said:
OK. So tell me, what ROM were you on, which recovery version and name are you using, why were you flashing back to stock, i.e. were you having problems, what kind. Explain as much as you can in detail. Need to retrace your exact steps to best get you fixed up!
tinydynamite00
Click to expand...
Click to collapse
i was using pa4.0 and wanted to go back to stock because i preffered the lg ui. i had twrp 2.6.3.5 i restored my back up of stock but when i rebooted i got into fastboot mode.
twrp wasnt working after i had restored my back up go straight to fastboot was stuck in fastboot until i found a thread explaining how to get out of fastboot and restore download mode.
managed to get download mode working and tried to flash stock with mobile support tool and got the 49 percent error,
my phone never really displayed any progress just says download mode with a white box and blue dots
El Killer said:
i was using pa4.0 and wanted to go back to stock because i preffered the lg ui. i had twrp 2.6.3.5 i restored my back up of stock but when i rebooted i got into fastboot mode.
twrp wasnt working after i had restored my back up go straight to fastboot was stuck in fastboot until i found a thread explaining how to get out of fastboot and restore download mode.
managed to get download mode working and tried to flash stock with mobile support tool and got the 49 percent error,
my phone never really displayed any progress just says download mode with a white box and blue dots
Click to expand...
Click to collapse
K, now if you're only seeing the blue dots when you attach by USB your phone to PC, then you're not fully in DL mode to process the kdz. You should see a white wheel in the center of the screen when you connect and a viewing mirror near the base of your phone with ROOTED in red directly below that. And you're sure your PC is detecting your phone? You've the drivers installed? Because when RDT tells you to run the tool, you'll see some binary code in the viewing window I spoke of, the white wheel will turn and below it will be shown the COM port to which you're connected and a solid thin red bar will begin to fill a space in the viewer showing you the progress.
Also, be sure when attempting the first steps I gave you to boot into recovery that you are not USB connected. It won't work.
And, try to remember if your phone was well enough charged, should have been at least 80% full. It happened to me once that I couldn't boot recovery and my phone would go to fastboot like yours until I left it alone to charge and then I repeated the stepsvi laid out to get back into recovery. This part is paramount!
Please READ CAREFULLY
I used to be in your same situation. I thought I had bricked my phone for good. I finally figured it out. Here is my solution from my Thread.
Esteef said:
Okay, after 12+ hours of trying every method possible on XDA I finally resolved my issue. I will update the first post just incase any others care or fall into the same dilemma I was in.
The LG Mobile Support tool would not download the firmware and it would NOT ask me for my IMEI to download it either.
So my solution....
***
Installed LG Mobile Support Tool then Installed the LG Drivers. (FROM HERE http://forum.xda-developers.com/showthread.php?t=2471370
BEFORE I connected the phone to the computer. I opened the LG Mobile support tool clicked (Options on the top right).
When the dropped down opened, I clicked the (Upgrade Recovery) option. THEN, is when the prompt opened to ask me what my IMEI is.
Before I entered my IMEI, I connected my phone to the computer in download mode, then proceeded to enter my IMEI and hit OK.
This is when the LG Mobile Support tool SUCCESSFULLY downloaded the latest official LG firmware and installed it.
*** BE AWARE, with the phone connected to the PC, the prompt NEVER appeared to enter my IMEI.
*** But with the phone disconnected, the prompt came up every time. This might be the trick for some people.
*** with the IMEI prompt opened, I then connected the phone , entered the IMEI, then hit OK. BOOM HERPES....
Well I'll polish this up more later. I hope this works for every LG G2 Variant and not just the T-Mobile one (D801)
-Esteef
Click to expand...
Click to collapse
THIS WILL WIPE YOUR PHONE COMPLETELY...
tinydynamite00 said:
K, now if you're only seeing the blue dots when you attach by USB your phone to PC, then you're not fully in DL mode to process the kdz. You should see a white wheel in the center of the screen when you connect and a viewing mirror near the base of your phone with ROOTED in red directly below that. And you're sure your PC is detecting your phone? You've the drivers installed? Because when RDT tells you to run the tool, you'll see some binary code in the viewing window I spoke of, the white wheel will turn and below it will be shown the COM port to which you're connected and a solid thin red bar will begin to fill a space in the viewer showing you the progress.
Also, be sure when attempting the first steps I gave you to boot into recovery that you are not USB connected. It won't work.
And, try to remember if your phone was well enough charged, should have been at least 80% full. It happened to me once that I couldn't boot recovery and my phone would go to fastboot like yours until I left it alone to charge and then I repeated the stepsvi laid out to get back into recovery. This part is paramount!
Click to expand...
Click to collapse
yeah my computer does recognize my phone. but i cant run adb or fastboot anymore. all drivers are installed also.
i never got the while wheel or any progress indicator. so i guees im not really in download mode.
i let my phone charge for a few hours and try your method again and let you know what happens
El Killer said:
yeah my computer does recognize my phone. but i cant run adb or fastboot anymore. all drivers are installed also.
i never got the while wheel or any progress indicator. so i guees im not really in download mode.
i let my phone charge for a few hours and try your method again and let you know what happens
Click to expand...
Click to collapse
Sounds good. A full charge can make all the difference. I learnt the hard way! One or more of us will be along should you need further help.
I do hope you get this sorted! I've come back from the brink too many times to not believe you won't.
tinydynamite00
Do as esteef recommended..
Sent from my LG-D802 using XDA Premium 4 mobile app
Falaco147 said:
Do as esteef recommended..
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
im trying but i get a battery to low error. i guess i need to charge it longer
i owe you all a million thanks for helping me unbrick my phone. i really thought i was left with a paper weight and then i tried esteefs method again i really owe you guys thank you for the support
El Killer said:
i owe you all a million thanks for helping me unbrick my phone. i really thought i was left with a paper weight and then i tried esteefs method again i really owe you guys thank you for the support
Click to expand...
Click to collapse
You are welcome... The first time I did it too my battery was at 28% and I panicked since I got the low battery error.
I could of sworn that my phone officially became a paper weight. My heart dropped.
I'm glad you are up and running with the rest of us!
-Esteef
1732359994
hey !
I have the same problem, but... I can't acces to the recovery :/ i tried to install CWM (with Freegee) over Team win recovery and... boot loop :
The rom 4.2.2 flex was gone, no boot animation
-When i pres volum down + power, i have the reset menu, but after that, there is a black screen and it's written at the top left "started usb_start Fastboot Mode ()"
Please, i need your help, i'm so afraid !!
Thx !
Esteef said:
I used to be in your same situation. I thought I had bricked my phone for good. I finally figured it out. Here is my solution from my Thread.
THIS WILL WIPE YOUR PHONE COMPLETELY...
Click to expand...
Click to collapse
I know this thread is a bit old, but it saved my butt. Your method worked perfectly. Thank you for this post.
My LG F460 was bricked (error 570), only download mode was working. Esteef method works fine even my pictures and programs was saved. Thanks!
Hi,
My brother is having trouble with his Nexus 4 and I was hoping I could get some help here.
The phone won't go past the boot animation, with the 4 floating balls.
It keeps showing that forever (left it for 20 minutes with charger, phone got really hot but did not get past the animation)
- Never rooted or changed firmware. Only updates from Google. (It was on 5.1.1/5.1/5.0.1)
- Sent to a shop, which claimed it can't be fixed (I do not know the reason they gave him).
My brother thinks it is because a weight was accidently dropped on the phone, but the problem only started 3 days after the incident.
No outer damage can be seen on the device, other then a small brake in the back glass.
Thanks in advance to anyone who will try to help
possibly?
Did you just update and it got stuck at the booting up????
opeller said:
Hi,
My brother is having trouble with his Nexus 4 and I was hoping I could get some help here.
The phone won't go past the boot animation, with the 4 floating balls.
It keeps showing that forever (left it for 20 minutes with charger, phone got really hot but did not get past the animation)
- Never rooted or changed firmware. Only updates from Google. (It was on 5.1.1/5.1/5.0.1)
- Sent to a shop, which claimed it can't be fixed (I do not know the reason they gave him).
My brother thinks it is because a weight was accidently dropped on the phone, but the problem only started 3 days after the incident.
No outer damage can be seen on the device, other then a small brake in the back glass.
Thanks in advance to anyone who will try to help
Click to expand...
Click to collapse
Do you have data on it that you want to keep? If you don't you can try booting into the bootloader and unlock it. Then try flashing a factory image. This will wipe all the data on the phone though so that should probably be a last resort.
ChainFires Son said:
Did you just update and it got stuck at the booting up????
Click to expand...
Click to collapse
No, it did not occur after an update.
theminikiller said:
Do you have data on it that you want to keep? If you don't you can try booting into the bootloader and unlock it. Then try flashing a factory image. This will wipe all the data on the phone though so that should probably be a last resort.
Click to expand...
Click to collapse
I have no important data on it.
Which is the safest way to do this? I'd appreciate it if you would be detailed or refer me to a guide, as I want to be careful.
Where should I download the factory image from?
As the name of it states, I wish to get the one from Google, without any changes or addons from users.
Follow this guide http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
You can download factory images from here https://developers.google.com/android/nexus/images
opeller said:
I have no important data on it.
Which is the safest way to do this? I'd appreciate it if you would be detailed or refer me to a guide, as I want to be careful.
Where should I download the factory image from?
As the name of it states, I wish to get the one from Google, without any changes or addons from users.
Click to expand...
Click to collapse
First we should check if you can boot into the bootloader at all. First turn the device off. Then hold down both the volume buttons and then press and hold the power key. Keep holding all the buttons until you see some different colored text. If that happens we should be able to install a factory image, if it still gets stuck on the Google logo I unfortunately don't have any more ideas.
Tried pressing both volume keys and power button. Google logo show for a second, then black for 2 second, thank flashing red notification light every 1/2 second until I let go of the buttons.
When I release the buttons, the phone goes back to charging battery screen.
I see people suggesting that the red light flashing means a battery problem, but the device keeps trying to boot up while it is not plugged to the charger, unlike what happened to them
Any Ideas why this is happening or what the red light means in this case?
You need to press volume down+power button to get into bootloader. Unplug the charger before doing this.
harishmenace said:
You need to press volume down+power button to get into bootloader. Unplug the charger before doing this.
Click to expand...
Click to collapse
Oh it was just volume down, not both. Heh, sorry.
Use the Nexus Root Toolkit (NRT), it's the easiest way to unlock, root, flash and manage your SuperUser needs!
http://www.wugfresh.com/nrt/
Not sure, but maybe?
You can try using the nexus root kit & unlock your bootloader and see if a factory reset can work. If it does you can always relock it again ☺..Flashing a factory image can work too also ...
Tried volume down+ power button while unpluged from charger.
Google logo show up with vibration, then goes away after 2 seconds, like before, but then the screen goes blank. But red led not flashing.
What should I do now? Even just to use the Nexus Root Toolkit I have to allow Developer mode, which I can't as the phone will not boot up.
opeller said:
Tried volume down+ power button while unpluged from charger.
Google logo show up with vibration, then goes away after 2 seconds, like before, but then the screen goes blank. But red led not flashing.
What should I do now? Even just to use the Nexus Root Toolkit I have to allow Developer mode, which I can't as the phone will not boot up.
Click to expand...
Click to collapse
I'm you can't get into the bootloader then I am unfortunately not aware of any way to help you. If you can't even get into the bootloader I think it is a high probability that it is a hardware problem.
I understand. Thank you for your attempt to help me so far, I apriciate it
Anyone else has any Idea what I can try?
opeller said:
I understand. Thank you for your attempt to help me so far, I apriciate it
Anyone else has any Idea what I can try?
Click to expand...
Click to collapse
First you have to ensure "The Situation" of your phone, diagnostic is very important to decide the kind of medicine or treat. Your N4 booting, stuck on google-logo with red blink, then black screen.
To check : Connect your N4 to PC on linux check on terminal command $ lsusb if output
Bus 001 Device 005: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode),
Click to expand...
Click to collapse
on windows (XP/Vista/7)
Qualcomm something QDL Mode or something like this on "device manager"
Click to expand...
Click to collapse
there is a big hope to revive but very long journey. You are lucky since N4 is very popular device.You can obtain required file like MPRG8064.hex and friends
x1123 said:
First you have to ensure "The Situation" of your phone, diagnostic is very important to decide the kind of medicine or treat. Your N4 booting, stuck on google-logo with red blink, then black screen.
To check : Connect your N4 to PC on linux check on terminal command $ lsusb if output
on windows (XP/Vista/7) there is a big hope to revive but very long journey. You are lucky since N4 is very popular device.You can obtain required file like MPRG8064.hex and friends
Click to expand...
Click to collapse
Hi, thank you for your will to help.
When I turn on the Nexus 4 and connect it to my pc, it show the device as Nexus 4 in device manager.
What do you want me to do?
opeller said:
Hi, thank you for your will to help.
When I turn on the Nexus 4 and connect it to my pc, it show the device as Nexus 4 in device manager.
What do you want me to do?
Click to expand...
Click to collapse
detected as Nexus 4 mean your device well alive. any respons from the phone if you check with adb command ? if the phone give respond to adb you can ask phone to turn to recovery $ adb reboot recovery ...
opeller said:
Tried volume down+ power button while unpluged from charger.
Google logo show up with vibration, then goes away after 2 seconds, like before, but then the screen goes blank. But red led not flashing.
What should I do now? Even just to use the Nexus Root Toolkit I have to allow Developer mode, which I can't as the phone will not boot up.
Click to expand...
Click to collapse
That sounds like the battery is completely empty. Put the device on charger over a night and try then to boot into the bootloader.
Once I had these symptoms (red light flashing) on my N4, it was enough to charge the battery for one hour. Then it booted properly. It's worth trying.
x1123 said:
detected as Nexus 4 mean your device well alive. any respons from the phone if you check with adb command ? if the phone give respond to adb you can ask phone to turn to recovery $ adb reboot recovery ...
Click to expand...
Click to collapse
How do I do that?