Hey,
today I had a freez with my G2 LOS16 during normal use (Browser, gaming). Since this freeze the G2 freezes after booting. Sometime while the LOS logo is shown or sometime the phone boots to the PIN Lock Screen. But the phone freezes every time. I've tried to boot into recovery (Power + Vol down, didn't work) or with reboot into recovery. The phone reboot wit a black screen (it is on but nothing on it).
I've diconnected the battery from the phone and waited af few minutes. But is the same result. Is this some kind of hardwarefailure?`
I manged to boot into recovery. But after a few seconds in recovery, the screen was also frozen.
After a normal boot the phone freezes after a few seconds an the CPU is very hot (like running with 100% all the time)
Related
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
So I have TWRP 2.8.7.0 on the phone, and I accidentally went to Reboot -> Download, and then after like 20 minutes my phone shut off (battery might have fallen out) and now I can boot into the TWRP recovery mode, but when I try to boot the phone, It goes through the Metro PCS splash screen mostly, and then near the end, it freezes, and vibrates 3 times every few seconds. (pattern: 1.2...3...........1.2...3) It will do this in a continuous loop until I unplug the battery and plug it back in. I am running Android Lollipop 5.1.1. How do I solve this?
Hey,
I have D802 16GB with pre-last CM version. Wanted to restart the phone (no mods nor installing apps before, just a normal restart) and the trouble started:
-it was stucking on LG logo and then screen turning off; sometimes it came to CM boot animation followed by turned off screen
-managed to boot the phone in safe mode in order to backup files from the phone, it freezed and turned off. Booted in safe mode few times again, the freeze was coming faster and faster
-once or twice phone booted up normally, freezed very soon
-booted to safe mode couple of more times. I noticed the phone was freezing shortly after releasing the volume buttons.
-booted up in normal mode, was holding the volume up button during the boot. The phone worked normally, after couple of mins released the volume button. Few mins after the phone freezed.
-LG logo was shown few more times out of dozens of attempts with different power button and volume buttons combinations
-LG logo showed for a short moment after pluging the charger
-now nothing happens at all, even when connected to charger or PC. The computer doesn't detect any device.
I really want to get the data that are in internal memory of the phone. What should I do? What happened with my phone?
Found this:
https://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
but will the internal memory data be affected? Moreover, there is written:
12 After attaching buttons plate,check your device going into download mode, and use flash tool to flash stock rom.
Click to expand...
Click to collapse
On the phone is CM which is not stock ROM, can I proceed?
Each advice will be much appreciated
hi all,
Just come back from holiday and SM-G928F edge plus (european model) battery was completely flat.
I charged the mobile and booted it up, loaded into Android then sounded like a lots of notification alerts then phone made a loud buzzing noise and crashed/auto-reloaded.
Since then it had gone into a boot loop. Tried holding power and vol down to reboot phone. Initially this function worked then no longer worked. Phone still stuck in boot loop...
Could not get into safe mode (hold power and vol down then release power)
Tried in recover mode (hold power, vol up and home), tried clearing cache took ages about 1 hour, also tried the format option, rebooted system and still boot loop..
Tried going into Odin mode (power, vol down and home) , used ODIN s/w and installed the latest XER version firmware, got success message but still boot loop...
Interestingly when I left it to constant boot loop, eventually it booted up Android now. However once I start using the mobile it intermittently reboots the mobile and then goes back into boot loop again...
When I did manage to get into Android I tried using an app to check the mobile health, strangely I notice it said I only had 1gb ram spare and the rest was used when mobile was factory reseted and I didnt expect so much RAM in use. During stress test mobile crashed and gone into boot loop again...
I am not sure this was affected by an auto update that may had gone wrong.
I don't root, just used stock firmware.
UPDATE:
Left mobile in boot loop until battery went flat, fully charged it and now can get back into Android. But it started to auto update some app and then auto rebooted/crashed and went into boot loop again.
Please help.
Thanks
Is there anyone who can help me please?
Hi, i have a problem, when i boot my phone IT stucks for something about 3-4 minutes and then normally boots. Boot animation is normal only splash screen is long it also happens when i reboot to recovery
I always had the same feeling since I rooted my stock device.
That didn't change with custom ROMs, so I'm still facing that problem.