Related
My G2 suddenly just stopped working yesterday. When I try to power it on the phone either freezes shortly after the boot screen, gets to the homescreen then shuts off, or boots to an all blue screen. I can access TWRP but haven't been able to fix it with anything I've found. My pc isn't recognizing the phone so don't know if I can flash another rom. Also tried factory reset with no luck. Any help please this is driving me crazy!!!
The same thing just happened to me! Someone please help us! IS there a solution to this?
dsljk2009 said:
My G2 suddenly just stopped working yesterday. When I try to power it on the phone either freezes shortly after the boot screen, gets to the homescreen then shuts off, or boots to an all blue screen. I can access TWRP but haven't been able to fix it with anything I've found. My pc isn't recognizing the phone so don't know if I can flash another rom. Also tried factory reset with no luck. Any help please this is driving me crazy!!!
Click to expand...
Click to collapse
colbyrainey said:
The same thing just happened to me! Someone please help us! IS there a solution to this?
Click to expand...
Click to collapse
Ok, since there is little to no information out there I thought I would share how I created and fixed this problem.
I received a new phone under warranty because of a failing sim card reader. Naturally, the first thing I did once I received it was root it. Next, I thought I would be slick and use flashify to flash a custom recovery (TWRP). Little did I know, with the new version of Android, our phones have a locked bootloader. I freaked out when I saw some weird error messages about it and tried to power off the device in the middle of it booting. BIG MISTAKE. In hindsight, I am assuming that it was re-flashing the factory recovery when I powered it off.
It gave me a solid blue screen for two hours, unless I held the power button for 10 seconds, which would just repeat the process from black screen to solid blue screen repeatedly. I tried to reboot into recovery for 2 hours by holding volume down and power. 2 HOURS!
At that point, I realized that I may have some luck getting it into download mode by powering it off, then powering it on with volume up and power and plugging in a USB cable. VOILA! It booted up normally (somehow) and I got it running the OS.
After that, I made sure that I did a factory reset by reverting to stock using the LG Software Upgrade tool.
The moral of this story is, if you are going to try to install a custom recovery on 4.4.2, make sure you know what you're doing. It turns out an app called AutoRec did the trick for me.
dsljk2009 - I hope this message helps you, or anyone else who may think they've bricked their phones.
CHEERS LADS!
If this post helped you be sure to hit thanks!
colbyrainey said:
Ok, since there is little to no information out there I thought I would share how I created and fixed this problem.
I received a new phone under warranty because of a failing sim card reader. Naturally, the first thing I did once I received it was root it. Next, I thought I would be slick and use flashify to flash a custom recovery (TWRP). Little did I know, with the new version of Android, our phones have a locked bootloader. I freaked out when I saw some weird error messages about it and tried to power off the device in the middle of it booting. BIG MISTAKE. In hindsight, I am assuming that it was re-flashing the factory recovery when I powered it off.
It gave me a solid blue screen for two hours, unless I held the power button for 10 seconds, which would just repeat the process from black screen to solid blue screen repeatedly. I tried to reboot into recovery for 2 hours by holding volume down and power. 2 HOURS!
At that point, I realized that I may have some luck getting it into download mode by powering it off, then powering it on with volume up and power and plugging in a USB cable. VOILA! It booted up normally (somehow) and I got it running the OS.
After that, I made sure that I did a factory reset by reverting to stock using the LG Software Upgrade tool.
The moral of this story is, if you are going to try to install a custom recovery on 4.4.2, make sure you know what you're doing. It turns out an app called AutoRec did the trick for me.
dsljk2009 - I hope this message helps you, or anyone else who may think they've bricked their phones.
CHEERS LADS!
If this post helped you be sure to hit thanks!
Click to expand...
Click to collapse
Hey,
How did you power off your G2 before putting it into download mode? Im experiencing the same problem.
Please assist me.
jocyrus said:
Hey,
How did you power off your G2 before putting it into download mode? Im experiencing the same problem.
Please assist me.
Click to expand...
Click to collapse
I didn't get the blue screen but I kept getting the security error screen on my d802. To turn it off, I kept holding down the power button for about 10 seconds after the screen went blank. This caused the phone to remain powered off. After that, I was able to boot into download mode. Maybe this method will work for your phone.
audit13 said:
I didn't get the blue screen but I kept getting the security error screen on my d802. To turn it off, I kept holding down the power button for about 10 seconds after the screen went blank. This caused the phone to remain powered off. After that, I was able to boot into download mode. Maybe this method will work for your phone.
Click to expand...
Click to collapse
It didn't work. Any other suggestions? :|
jocyrus said:
It didn't work. Any other suggestions? :|
Click to expand...
Click to collapse
Don't know of any other methods because holding down the power button got the phone to turn off and allow me to get into download mode. From download mode, I was able to restore a stock 5.01 ROM to my phone via LG Mobile Support Tools.
LG G2 Bluescreen then no boot after disconnecting battery
Found my LG G2 with a completely blue screen. It would not turn off. Took it apart and disconnected the battery. Reconnected the battery and there was only a blank black screen and the phone would not boot. Zilch. Even with pressing the power button with the volume down to boot into recovery.....still zilch.
I sucessfully got my phone to work again using a hair dryer trick on an LG G3, which I found here.
1. I took the back off the phone, disconnected the battery, and removed the SIM card.
2. I then used a hairdryer on high heat and blew the heat over the uncovered areas for 10 minutes.
3. I let the phone from hot to warm, reconnected the battery and put it all back together with the SIM card replaced.
4. I booted into recovery and restored a TWRP backup, and my LG G2 is working like a champ again.
Hi,
I have a LG G2 D800 (ATT Black version) which I was running with cm 11 for a long time.. Last week I got curious and tried to install CM12 on it and that's where started my nightmare.
To begin with, I think I flashed the wrong twrp version (d802) instead of d800.. So I was stuck for a while.. I finally was able to recover from that and Installed CM12. The install went ok, but the phone would freeze and turn off.. It wouldn't turn back on unless I did a soft reset.. I tried a few times and then gave up.. With the nandroid backup that I had, I went back to cm11, but the problem started to follow me in CM11 as well.. The phone was constantly rebooting.. Sometimes the phone would stay on for 2-3 hours and sometimes it wouldn't stay on for 2 minutes.. So I got frustrated and went thru' different threads and finally went back to Stock Rom using the LGFlashtool method.. In stock rom, the phone booted up fine, but the rebooting issue started happening there as well.. The phone was definitely much stable under stock rom than CM11/CM12 but it won't still power off all of a sudden and I could go a couple of hours before noticing that it had turned off.. Frustrated with it, I started all over again to root and install twrp and that's when it went from Bad to worse.. Something happened with my TWRP flash and I was not able to go to recovery or download... I was stuck...
I tried several methods. 1 ) Using ubuntu was my first try.. I followed the initial steps (ls devices and gdisk -l command) and after I ran the first step (dd if=/home/med/Desktop/sbl1.img of=/dev/sdb2), my phone went into fastboot mode and ubuntu couldn't recognize my device. after that.. I couldn't run the remaining commands..
2) since I was stuck in fastboot, I followed the fastboot method from another thread by downloading the fastboot and laf.img.... The phone was responding and said recovery erased successfully, but it kept going back to fastboot.. When I tried a different laf.img file, that's when the phone rebooted and now wouldn't turn on at all..
No LG image, no recovery, no response.. I've tried all button combinations (holding vol down and power, power alone, all 3 buttons, vol+ and power)... nothing happens with the phone... Windows doesn't recognize the phone.. It says 'lg g2 qhsusb_bulk' but that's pretty much it..
Atleast until today morning I had a LG image flashing that tells me that the issue is a software / partition issue.. Now I don't know if I have fried something..
I bought the fone in november 2013 and hence its out of warranty.. . I'm not eligible for upgrade till November and I'm stuck with using a iphone 4s (ouch...) until then... It sucks big time to go from the g2 to the 4s... any thoughts or ideas?
I had the same problem when I flashed the wrong kernel.... This link helped me http://forum.xda-developers.com/showthread.php?t=2582142 one of these 7 solutions should help you....
I found this link on YouTube which is exactly like your case
http://m.youtube.com/watch?v=_d5b_osUTug
And the second link which I didn't try is
Sent from my Lightning D802 G2
Supracer said:
I had the same problem when I flashed the wrong kernel.... This link helped me http://forum.xda-developers.com/showthread.php?t=2582142 one of these 7 solutions should help you....
I found this link on YouTube which is exactly like your case
http://m.youtube.com/watch?v=_d5b_osUTug
And the second link which I didn't try is
Sent from my Lightning D802 G2
Click to expand...
Click to collapse
Thanks. I looked into that thread before. Unfortunately in my case the phone is not recognized in adb or fastboot. Adb shows no device listed whereas fastboot says waiting for device.
Lg flashtool doesnt do anything either.
Only thing is that fone was showing up as unknown device and by me pressing vol up and power and vol down, it shows up as qhusb bulk..
askthiru said:
Thanks. I looked into that thread before. Unfortunately in my case the phone is not recognized in adb or fastboot. Adb shows no device listed whereas fastboot says waiting for device.
Lg flashtool doesnt do anything either.
Only thing is that fone was showing up as unknown device and by me pressing vol up and power and vol down, it shows up as qhusb bulk..
Click to expand...
Click to collapse
Go to the Device Manager => device properties of the "unknown device" => Details => Hardware ID and search the value on the internet for a driver... Maybe with a driver you can get the phone to be recognized
Folks,
I finally was able to get my G2 working from a hard brick..
My final non working symptom : Blank Screen.. No download.. No recovery.. No LG logo… Windows was showing device as unknown device sometimes and sometimes as qhusb_bulk.
Steps that I followed: You need to know how to use fastboot.
1) Kept trying different combinations of the 3 buttons (power, vol + and Vol -). The one that worked for me was to unplug the phone from pc… Press all 3 buttons together for 15-20 seconds and will keys pressed, plug into the PC.
2) This put me in the fastboot mode.. Here I tried flash laf.img with several laf files. My phone was a lg g2 d800 (ATT variant). Nothing really worked..
3) So I downloaded the Stock Rom files (aboot, boot, dbi, laf, misc, modem, persist, recovery, rpm, sbl1, and tz images) from http://downloads.codefi.re/autoprime/LG/LG_G2). I flashed all these files using Fastboot and then after flashing, rebooted the phone.
4) The phone automatically went into AT&T update and at 3% failed with an error and booted into safe mode. (This is probably because when it got bricked, I accepted a OTA update on a rooted phone and I didn’t have twrp recovery either).
5) I came out of safe mode and booted normally and voila, I got the stock rom 4.2.2 on my phone.
Thanks so much to the various threads in XDA developers that I was able to fix this.. Much thanks to etm34 for this thread: http://forum.xda-developers.com/showthread.php?t=2681089
Also to Partager.info for this thread: http://forum.xda-developers.com/showthread.php?p=48765620#post48765620
And cms88168 for this thread http://forum.xda-developers.com/showthread.php?t=2477595
I had to use all these 3 threads above to get my g2 back to working..
Thanks for sharing
askthiru said:
Folks,
I finally was able to get my G2 working from a hard brick..
My final non working symptom : Blank Screen.. No download.. No recovery.. No LG logo… Windows was showing device as unknown device sometimes and sometimes as qhusb_bulk.
Steps that I followed: You need to know how to use fastboot.
1)Kept trying different combinations of the 3 buttons (power, vol + and Vol -). The one that worked for me was to unplug the phone from pc… Press all 3 buttons together for 15-20 seconds and will keys pressed, plug into the PC.
2)This put me in the fastboot mode.. Here I tried flash laf.img with several laf files. My phone was a lg g2 d800 (ATT variant). Nothing really worked..
3)So I downloaded the Stock Rom files (aboot, boot, dbi, laf, misc, modem, persist, recovery, rpm, sbl1, and tz images) from http://downloads.codefi.re/autoprime/LG/LG_G2). I flashed all these files using Fastboot and then after flashing, rebooted the phone.
4)The phone automatically went into AT&T update and at 3% failed with an error and booted into safe mode. (This is probably because when it got bricked, I accepted a OTA update on a rooted phone and I didn’t have twrp recovery either).
5)I came out of safe mode and booted normally and voila, I got the stock rom 4.2.2 on my phone.
Thanks so much to the various threads in XDA developers that I was able to fix this.. Much thanks to etm34 for this thread: http://forum.xda-developers.com/showthread.php?t=2681089
Also to Partager.info for this thread: http://forum.xda-developers.com/showthread.php?p=48765620#post48765620
And cms88168 for this thread http://forum.xda-developers.com/showthread.php?t=2477595
I had to use all these 3 threads above to get my g2 back to working..
Click to expand...
Click to collapse
Happy to see you solved.
All,
Even though I resolved my bricked G2, it is still giving me issues by turning off automically after a while... It looks like a hardware failure to me where it ceases to operate at times.. The phone has stayed on sometimes for an entire day and sometimes it goes off in 5 minutes.. I'm sending it to LG repair service.. Hopefully they fix it for me under warranty (even though it has been 13 months since i bought it)..
So, I downloaded the A2017G B08 from this thread onto my SD card and went into the settings to update. All was fine until the phone got to the update screen and to 25% on the progress bar. Then the screen turned off, along with the phone. If I try to boot it, it's the same story. I see the ZTE screen, get to the update progress bar but it gets stuck on 25% and turns off. Kind of like a manual boot loop.
The phone isn't rooted or anything, I was downgrading to marshmallow to try and fix mic issues I was having earlier but never expected this.
Please help.
Thanks.
*deleted*
vesheljinn said:
So, I downloaded the A2017G B08 from this thread onto my SD card and went into the settings to update. All was fine until the phone got to the update screen and to 25% on the progress bar. Then the screen turned off, along with the phone. If I try to boot it, it's the same story. I see the ZTE screen, get to the update progress bar but it gets stuck on 25% and turns off. Kind of like a manual boot loop.
The phone isn't rooted or anything, I was downgrading to marshmallow to try and fix mic issues I was having earlier but never expected this.
Please help.
Thanks.
Click to expand...
Click to collapse
Ouch. We can try stuff but I never read anything like this here.
First try to access the recovery directly. I think it's Volume up and power, but if you get into FTM mode just try with volume down. If you can, then download B10 from the download center (it's weird that we have everything there and nobody uses it, it's frickin stickied on the Guides section for God's sake) or Nougat B04 and try to install it from an SD card.
If it doesn't work you have two ways to go: if the bootloader is unlocked, install TWRP via Controllerboy's guide (using axon7tool, it works every time)
OR
put your phone on EDL mode (Connect the USB cable to the PC, then hold both Volume buttons (NOT POWER) and insert the cable on the phone, and use MiFlash to get a working B10 on your phone. (there's a B10 package on 4pda)
If you choose the TWRP way you can install MiFavor 5.0 and be done with it. Or maybe a custom ROM, but if you didn't have any problem staying stock as it seems that you did, then you'll probably not like custom ROMs and their bugs
This is what I thougth as well. But his link only refers to B08 in MM. So he didn't want to install B08 on Nougat. As his bootloader is still locked he cannot install this ROM in no way.
Choose an username... said:
Ouch. We can try stuff but I never read anything like this here.
First try to access the recovery directly. I think it's Volume up and power, but if you get into FTM mode just try with volume down. If you can, then download B10 from the download center (it's weird that we have everything there and nobody uses it, it's frickin stickied on the Guides section for God's sake) or Nougat B04 and try to install it from an SD card.
If it doesn't work you have two ways to go: if the bootloader is unlocked, install TWRP via Controllerboy's guide (using axon7tool, it works every time)
OR
put your phone on EDL mode (Connect the USB cable to the PC, then hold both Volume buttons (NOT POWER) and insert the cable on the phone, and use MiFlash to get a working B10 on your phone. (there's a B10 package on 4pda)
If you choose the TWRP way you can install MiFavor 5.0 and be done with it. Or maybe a custom ROM, but if you didn't have any problem staying stock as it seems that you did, then you'll probably not like custom ROMs and their bugs
Click to expand...
Click to collapse
Hey, thanks for the response.
I downloaded MiFlash and got a working B10 but when I went to reboot the phone the screen wouldn't turn on, just the red LED was on. If I tried to go into recovery mode the phone vibrates and the LED flashes but it goes back to the same state. Also if I connect it to the PC and try and enter EDL mode there are sounds from windows that a USB device is being connected but that's it. MiFlash can't recognise the phone.
vesheljinn said:
Hey, thanks for the response.
I downloaded MiFlash and got a working B10 but when I went to reboot the phone the screen wouldn't turn on, just the red LED was on. If I tried to go into recovery mode the phone vibrates and the LED flashes but it goes back to the same state. Also if I connect it to the PC and try and enter EDL mode there are sounds from windows that a USB device is being connected but that's it. MiFlash can't recognise the phone.
Click to expand...
Click to collapse
I just had this issue, I plugged the phone into the orginal charger and for a legit 60sec held volume up and power button it will eventually power on .
jjallday said:
I just had this issue, I plugged the phone into the orginal charger and for a legit 60sec held volume up and power button it will eventually power on .
Click to expand...
Click to collapse
Did that for ~2 minutes, still nothing. Forgot to mention, when I connect it to the PC I get Handset Diagnostic Interface as a connected device.
vesheljinn said:
Did that for ~2 minutes, still nothing. Forgot to mention, when I connect it to the PC I get Handset Diagnostic Interface as a connected device.
Click to expand...
Click to collapse
hmm well idk i had this problem earlier today, even when i had mine connected to the pc the pc would make a noise as if the phone was turning on, but when i connected to the actual charger is when the 60sec thing actually worked , also i noticed that when i finally got it on the battery was down to 1% maybe some sort of battery issue. maybe let it set on the actual wall charger for awhile and try again.
vesheljinn said:
Did that for ~2 minutes, still nothing. Forgot to mention, when I connect it to the PC I get Handset Diagnostic Interface as a connected device.
Click to expand...
Click to collapse
Do the 4th category brick repair guide. Yes,you have to tear apart the phone, but I did this and didn't break it idk
No USB jigs or weird cables will work, you need to use the test pad to get into EDL.
There is another way though: it seems that if you discharge the phone completely, then hold vol down and power, and try a bunch of times, you might be able to get into FTM mode. You'll have adb from there, so you can do 'adb reboot edl' and use MiFlash to fix the software. But I haven't tried
Alright.
So yesterday i was just cassualy using my phone, when suddenly my volume down button started to act weird.
It kept pushing itself and raise or lower the volume. Since i didnt update my phone in a while, i figured it might be a software issue.
So i installed the latest update, and suddenly my phone booted in safe mode. Tried to reboot, no luck. Now my volume down key is unresponsive... I opened the phone up and cleaned the ports, but still no luck...
Looks like the key is dead. Now i am rooted and have twrp installed.
What are my options here?
Can i install an android 9 rom, maybe they wont boot into safe mode, i'm not sure?
I do still have warranty, so i could try my luck with relocking the phone and sending it back, but i also already opened it to look at the volume keys.
Do you guys have any ideas on how to handle this?
Ok so before I started writing this I had only one problem now I'm worried my problem has gone from bad to worse.
I updated my 6T to 10.3.2 from the latest Beta after the process it prompted for a restart, upon restarting it got stuck in the boot animation. I tried going into Recovery and Download mode unsuccessfully so I went through the forums a bit and saw that someone who had the same problem successfully entered Recovery mode by pressing VOLUME UP+DOWN+POWER buttons simultaneously, I tried to do the same and my phone turned off and now it doesn't turn on! :crying:
Has anyone experienced this or know how to fix this? Any help will be much appreciated. Tia!
theDUD3 said:
Recovery mode by pressing VOLUME UP+DOWN+POWER buttons simultaneously, I tried to do the same and my phone turned off and now it doesn't turn on!
Click to expand...
Click to collapse
These should be clarified:
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool.
Turn the phone off, let it sit. Then try turn it back on. Any response?
try to shutdown phone ...hold vol+ and power button for like 15 sec and restart your phone if this didnt work then u can try MSM tool
Thanks guys, got it working using MSM Tool!
regarding oneplus 6 got stuck on logo screen and recovery mode not working
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!
frankynehemimah said:
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!
Click to expand...
Click to collapse
You are likely going to lose your data. Know that going in if its not already backed up.
If you have the fastboot menu you can use the fastboot roms.
Or my least favorite option or what I would try last, MSM Tool (Tmobile 6Ts use a different tool).
IMPORTANT if you want to try and recover and data off your phone first, go to fastboot, and try and "boot" the TWRP img (not the installed one, one from your PC using the fastboot command). If that works you might be able to recover data. If that does worm, try dirty flashing the last ROM you were running and see if it boots.
No worries!
frankynehemimah said:
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!
Click to expand...
Click to collapse
Hello, I am sorry to hear of you having this issue, I just went through 3 1/2 days (off and on) of recovering my T-Mobile OnePlus 6t which I found a way to get my unlock code within 2 weeks of having it, so I rooted it and put a custom kernel on it, stuck on 9.0 never let me update as I was not familiar with A/B partitioning, yet! The answers I saw to your questions were spot on, I just had a little to add to it and I'm sure I am not alone. Real quick let me list what has gone wrong on the rare occasion it hit the fan with the 6t...
- When I would accidentally and rarely let my battery die it seemed like it took forever to get it to reboot, I mean it sat on my desk of DOA devices for 2 weeks!
- It often seems like the buttons do not always respond properly and never have when I needed them to. Been through this before, I've bricked and unbricked and flashed and re-flashed and wiped all weekend and I like Android 10 and all but seems everything is different for every build, and everything seems to have to go in the right order with the exact right file or you wind up in a jam, period..
- That said, the previous person that answered your question has likely encountered similar, I've heard of right down to the buttons not physically working, but I have been a Smart Device Master III Technician for over 5 years, i know my buttons were not broken.
- Most likely culprit that I just handled and worked, i did have to use the MSM tool, several times - and re-unlock the BL, several times I would not even get the chance to get to fastboot, just a screen saying Build and Hardware not a match"" in yellow letters and it just bootlooped. No fastboot is no good, but when you said the tool would show some signs of working but then not, I have 2 solutions that I needed on diffrent occcasions.
1 - As mentioned fully try other USB cables, and ports, if you pull the usb-c out of the port and hold <power + vol up + vol down> eventually it will do something, very picky, sometimes gotta move your fingers to different spots on the buttons and also after 15-20sec let go of power and hit and hold it again... after a few seconds before it vibrates stick the cable in connected to your PC and the screen will be black (obv) but the msm tool will pick up on it. I know about the cables because I take good care of my phones and cables and charging ports, however on my final fix today it showed in msm tool it was connected but waiting for device.... Fed up i put the phone down and moved the usb cable a little bit and it picked up on it and did its thing! That part was just the cable, getting into qualcomm mode or w.e. is a bit tricky sometimes.
- Also someone said set it down for a while and come back to it.. THAT WORKS!! Let it fully charge and often just plugging in charger turns it on, bootloop soft brick or however have you, very simiilar to an Apple device and their DFU (don't f up mode cause screen is black..)
I hope that helps you get in touch with your family and friends.. Whatever you do, don't give up bc if you have not got it yet, you will! One other note, there are a few different msm tools available and they look the same some same size, but the one that supposed to work on my phone didn't and one that they say only a fool would attempt to try actually saved me, so if all else fails, use a different msm tool/usb cable and you will get it! I don't think I can post links yet I am on here very rarely, but plan on more! I have received so much help from XDA throughout the years on thousands of phones with just software issues alone, aas well as guides to my own phones. I would be honored to give back as I also have some extensive knowledge on many devices but I am a noob in comparison to many! Stay safe, good luck and please update and let us/ me know how it worked out for you. If i can help further I will, I have every firmware file for the OP6t, recovery, tools, software, this is not new to me but I feel your frustration!