[Q] brick? - G2 Q&A, Help & Troubleshooting

So my vs980 running xdabbeb's 24a started bootlooping the other day for no apparent reason. After 15-20 cycles it stabilized and then was fine. Today it did the same thing but won't fully start up. I get some artifacts on the screen (lines, checkerboard) some of the time but most of the time it doesn't get past the lg logo. I tried manually going into TWRP with the hardware keys but it hangs on the factory reset processing screen after I've hit the power button twice and won't enter TWRP. Am I completely bricked? Any suggestions for fixing it?
Edit: I also did not take any OTA update. I froze system updates MUC after I started getting the notification.

Related

[Q] Verizon LG G2 (VS980) Security Error Bootloop

I have a VS980 and I have an issue where I cannot get it to do anything. I spent all kinds of time looking through forum after forum to find an answer. Nothing has helped. The problem:
I try to get into Download Mode and I get the LG Security Error message and reboots and repeats. I plug in the USB cable without touching any buttons it powers up and loops. Going into recovery only gets me to the LG Rooted Hard Reset and nothing else.
I am at a loss as to what to do now. I see there are threads that say that it is easy to get the Security Error fixed but it requires the LG Support Tool but that tool does not recognize my phone cause it is constantly booting. Other threads tell me to get it into download mode but I get the security error and reboots. I can no longer get into fastboot. And I don't have a custom recovery that I can get into it seems.
I can power the phone off by holding down the power key and letting it reboot a couple of times and it turns off. Nothing else seems to work.
Any ideas?

AT&T L2 G2 random reboot and frozen

In the beginning of this year, my daughter AT&T LG g2 phone got OTA update to Lollipop. After that, phone battery did not last long and phone got hot very often. I reloaded AT&T KitKat ROM and it worked fine again until last week. Phone could not be turned on - black screen. Sometimes, it came up but reboot again randomly. She tried multiple soft reset but most of the times, phone just stuck in LG logo. I did hard reset, and it tried to came up and frozen during "new phone setup". Right before it freeze, phone speaker made a loud noise.
I replaced battery and same thing (random reboot, frozen screen) happened. I then tried reload the AT&T KitKat ROM again. That did not fix the problem.
My question is that is this a hardware issue or ROM issue ? Phone could go into download mode, and Hard reset mode, but not recovery mode. I could never get it into recovery mode - phone off; holding Down Vol and Power buttons; when LG logo appeared, let go both buttons and press/hold them again until recovery menu appeared. I could not see any recovery menu All I saw was the LG logo again.
Thanks.,
Ching-Ho Cheng

Nexus 10 powers off during boot screen

Hey all,
Just some details before the background.
I was running a stock with a unlocked bootloader for a while now. I basically only use my nexus now to watch netflixs and HBOgo. Got the tablet over four years ago.
This morning after it's nightly charge I went to unlock it and it froze up. I rebooted it, noticed the date was off (Jan 1st) and froze after I unlocked it. Reboot again, it made it to the screen where it was optimizing my apps but the screen starting flickering and having artifacts, and powered off. Now it will power itself off 5 or so seconds into the boot animation.
I've tried going into recovery via the bootloader but when I select it and hit the power button it just turns it self off. I then used the nexus toolbox to reflash a stock rom (along with a factory reset), and TWRP. I tried booting up again and same thing. I then went into TWRP and start troubleshooting, but the screen is starting to flicker and have artifacts, then powers off.
Is the hardware dead on this?
Sorry for the jumbled mess of details, i've been bouncing around trying to troubleshoot/fix this.
PIT files
PIT files
My nexus 10 has the boot loop problem and I think I have been left with the only option of Re-Partition but I need the PIT file. Can anybody help or provide this file?
I have tried everything else (fastboot, adb, temporary custom recoveries, Nexus Root Toolkit) with no success.
Is the battery original? If so, it's possible the battery could be reaching its end.
Reddog090 said:
Hey all,
Just some details before the background.
I was running a stock with a unlocked bootloader for a while now. I basically only use my nexus now to watch netflixs and HBOgo. Got the tablet over four years ago.
This morning after it's nightly charge I went to unlock it and it froze up. I rebooted it, noticed the date was off (Jan 1st) and froze after I unlocked it. Reboot again, it made it to the screen where it was optimizing my apps but the screen starting flickering and having artifacts, and powered off. Now it will power itself off 5 or so seconds into the boot animation.
I've tried going into recovery via the bootloader but when I select it and hit the power button it just turns it self off. I then used the nexus toolbox to reflash a stock rom (along with a factory reset), and TWRP. I tried booting up again and same thing. I then went into TWRP and start troubleshooting, but the screen is starting to flicker and have artifacts, then powers off.
Is the hardware dead on this?
Sorry for the jumbled mess of details, i've been bouncing around trying to troubleshoot/fix this.
Click to expand...
Click to collapse

Verizon Lg g2 stuck in bootloop

So for a few weeks now, my phone has been having bootloop issues. I've been trying to fix it on my own, but no luck so far.
I can get it into download mode. Up until I tried to restore it to its stock version via the User Tool, I could get it to the factory reset options, which led to the options to wipe cache, reboot, etc. However, none of those options worked. When I attempted to reset to factory settings, I got the "dead" green android with the red triangle. Then the screen goes black and starts bootlooping again.
Once in awhile I can manage to turn it on after having it turned off for hours, or even days and it works like normal, except that if I lock it or turn it off it will end up restarting and starting to bootloop again. Which is bad seeing as it drains somewhat fast due to being overheated while having the screen constantly on.
As for my experience trying to use update recovery, it gets to the downloading part then stops and gives me this message "[011.700.147.062.092]??? ??? ? ? ????". I don't even know if I am using the correct stock rom for my phone, since I only know its MEID and model name.
do u resolved this, i have the same problem

Is my stock H910 truly a brick now?

TL;DR it's bootlooping, and I can't enter download mode.
My V20 H910 hasn't been touched for a couple years now. It started bootlooping years ago, and it's only now that I'm trying so hard to fix it. When I try to boot it, I get the LG screen for a few seconds, then it goes all black, and then it repeats until I pull the battery.
I can navigate to the screen to initiate a factory reset, but when I confirm, it freezes up for a moment and then goes back to the boot loop.
When I plug it in to initiate download mode, I get the screen that says it's trying to start download mode for a couple seconds, and then it goes back to the boot loop. I tried launching LGUP during this two second period, and unsurprisingly, it does not see the phone.
I've tried putting it in the freezer, and I've tried using a different battery. I tried "discharging the capacitors on the motherboard" by removing the battery and pressing the power button fifteen times. This causes it to vibrate briefly when I attempt to power it on, but then it bootloops as normal.
It's totally stock Oreo - no root, no custom ROMs, no TWRP, no unlocked bootloader. I might have enabled USB debugging, but that doesn't do me much good when it won't boot (yes, I tried ADB anyways, and no, it doesn't see it).
I did use third party USB cables to charge it back when it worked, so I am aware that this may just be a faulty motherboard. But I'm hoping there's another option I haven't pursued yet.
What do you think? Is it a brick? I've spent all day searching for potential fixes, so any help is appreciated!

Categories

Resources