I've got two gnex (gsm) devices, one was mine (until switched to nex 5) and one my wife's. They were purchased about 6 months apart, and both worked with stock roms for over a year.
At some point, my wife's device began working super slowly, and shortly after, it started rebooting randomly. The reboots became more and more frequent, and hard resets didn't help. I tried installing Cyanogen, didn't help. She switched over to my device and the same happened. Eventually, both devices somehow became soft-bricked - they're both stuck in bootloop, without any interference on our side (my device was still on stock rom).
I tried returning them to stock via the toolkit (didn't work), manually using fastboot (didn't work), and eventually flashed both of them to 4.3 using Odin, with re-partitioning and the whole shebang.. Nada. One device was flashed using Odin 3.07, worked for about one hour, then started bootlooping again, the other device couldn't get flashed with 3.07 (got an error on system.img write) so I tried with Odin 1.87 which completed successfully, but once reset it was still somehow on Cyanogen and still bootlooping.
I've tried all the methods I'm familiar with, and several different stock roms. Tried switching the batteries, fully charging them, even flashing from different PCs.. To no avail. As far as I can see, the only explanation right now is that there's a hardware issue, somehow in both devices.
Will greatly appreciate any input from you guys as I'm pretty much at a loss here. :crying:
i would say its hardware but try flashing multiple roms idk why when stock fails or CM i got full on rom switching and it fixs my problems
Similar thing happened to me, I bought whole new batteries for my two phones and it fixed it. The batteries went REALLY bad.
So my g4 started randomly restarting itself, so i decided to do a factory reset.
In my haste, i wiped all data from the phone including the OS. Since then i have tried flashing genisys rom 4.2 via twrp.
It installs okay, but after inital set up, it either freezes and becomes unresponsive, or starts ressting itself over and over.
Thinking it was the rom i have since tried flashing CM13, but again, it either freezes and becomes unresponsive after install on the homescreen or is resetting itself.
I am now stuck for ideas on how to resolve this, so any help and advice on solving this would be greatly appreciated
Try to flash a STOCK ROM and STOCK recovery.
Try flashing stock rom with LG UP and please dont try flashing roms u might end up with a permanent bootloop..stick with stock,root and xposed
Sent from my LG-H815 using XDA-Developers mobile app
Hi,
I have searched this forum a lot and found many solutions to my restarting problem but i am still not successful in getting rid of this issue. Let me explain the problem and solutions i tried without success.
Phone Specs
LG G3 D-850 AT&T When i got it, it had stock rom lollipop 5.0.1
Problem
It restarts automatically. It restarts whether i am using it or it is in idle state. It restarts even when being charged by Laptop USB cable. It restarts more often when battery is low like 5%. It restarts even without wifi without sim card.
Sometimes my phone does not start and i have to pull the battery out and put it on charge for a while then insert battery in and then it is able to start.
Solutions i tried but without success
1- Bought a new IbestWin Battery from Amazon 3000 MAH but the issue is still there. I also tried my colleague's OEM battery and restart was still there. His phone is also Lg G3 D850 ATT but from a different vendor and his phone is working fine on a custom rom of Fulmics marshmellow.
2- I tried custom rom of Cyanogen 12.1 lollipop through TWRP recovery but restart issue worsened, In fact the cyanogen did not always load correctly, phone shuts down at cyanogen pulsating logo.
3- I reverted back to stock rom successfully using the .Tot and DLL method (KitKat stock rom) but it even restarted more. I never installed anything, only built in apps already in the rom.
4- I read somewhere that putting a piece of paper between battery and card slot might resolve it, but still no success.
I took the phone to a repair technician and he thinks that this is either the software issue or the battery issue, phone seems okay.
Kindly help me resolve the issue.
Any one?
Did you try factory resetting the phone ?
youssefkr said:
Did you try factory resetting the phone ?
Click to expand...
Click to collapse
Yes i did (By pressing power button and volume down key) but still the frequent restart issue is there. I notice one thing though, that on Stock rom lollipp with stock firmware the restart was less as compared to stock Kitcat rom (.tot and dll). That leads me to believe that it is related to software and not hardware.
Hello everyone,
yesterday I flashed a new Cyanogenmod 14 nightly (12062016) for my G4 from earlier nightly in TWRP. After reboot the phone keeps going back to TWRP and I can't seem to get it to boot to system..
I tried factory reset, reflashing back to old nightly, flashing stock.. but nothing seems to work.
Also tried doing this in the TWRP terminal:
dd[space]if=/dev/zero[space]of=/dev/block/platform/f9824900.sdhci/by-name/fota
Didn't fix the loop, I guess because it wasn't the OTA update that caused the problem in the first place.
If anyone has an idea, I would greatly appreciate the help!
Thanks.
If you can reach download mode you could try reflashing back to stock then starting again.....Hope you get yours fixed - Sorry to say this but mine did a very similar thing only 24 hours before you posted!!! Only mine was on stock FW and was in use at the time - I've now had to swap it as valuebasket who sold me the phone have ceased trading. If yours is a UK model you may be able to get it replaced under warranty - believe that LG guarantee their phones for 2 years and a ruling by the European court said that flashing a custom rom doesn't invalidate any warranties.
I have the same exact issue, I also flashed the latest CM14 nightly and cannot get the device to boot any rom.
I have even tried flashing stock rom but I get the same problem.
From what I have read, the bootloop issue happens once the device boots but I don't seem to be getting that far.
Any ideas?
Ran into the same problem 3 days ago. This is the first time I have encountered a non-revertible issue in 3 years as a cyanogenmod user. This changes my opinion on how safe it is to make use of a custom ROM. I tried to wipe everything, reinstall TWRP, change TWRP with another recovery, reinstall a safe NAND backup of mine.....nothing.....it went into boot loop. Before I read this post, I was convinced my phone encountered the infamous G4 bootloop problem.....now I see there are other examples, so it shouldn't be the case. Long story short, I had to check my device in at the LG assistance, with 25 days as time forecast.
The guilty nightly was 20161205.
I have never seen anything like this...
This has solved it for me - I installed LG Bridge and flashed the factory firmware using the tool. Now it seems I'm back on stock but at least it's working.
got mine working. I had to install LGUP and flash stock ROM. Once flashed I installed CM14 and I am back up and running again.
I tried LGUP but it could not recognize the device while this was looping.....a bad experience......
I have the same issue. My phone was updated to 20i via the original stock firmware, then I put twrp 3.0.2-0 and cyanogenmod on. I did a cyanogenmod update from within cyanogenmod, which just booted into twrp, then I manually installed the update zip that cyanogenmod had downloaded, then it always boots into twrp. I wonder if initiating the update from within cyanogenmod was the cause. The phone is not detected by LGUP or LG Bridge. I've tried this on a win10 machine, and a win7 vm from linux. I have access to twrp, and download mode by doing the reboot into bootloader from within twrp.
If those people who have fixed this could give more details about how they did it, that would be good. What exact steps did you take? What stock firmware version did you have before installing a custom rom? What OS version were you using? What twrp version?
Well. Mine got stuck in bootloop for the second time today. What is going on? In between the two bootloops I had one good update with CM. Using TWRP 3.0.2.1. Steps to reproduce failure: updating CM from within CM, it autoreboots into TWRP and after that nothing happends, no autoinstall. Then after a manual install of the new CM the bootloop starts.
Resolve the problem:
* Install LGUP 8994 DLL Ver 0 0 3 23, Install LGUP Install Ver 1 14, get the latest KDZ
* Get the phone into download mode with usb cable and after that in firmware update mode
* Startup LGUP and choose refurbish and select the kdz file.
* After that you can boot into your stock LG firmware again, reinstall TWRP an CM. If you want so.
Read that it is advised to manual update cm from within TWRP. TWRP will get an update in the future to solve this bootloop problem.
iankelling said:
I have the same issue. My phone was updated to 20i via the original stock firmware, then I put twrp 3.0.2-0 and cyanogenmod on. After a cyanogenmod update, it always boots into twrp. The phone is not detected by LGUP or LG Bridge. I've tried this on a win10 machine, and a win7 vm from linux. I have access to twrp, and download mode by doing the reboot into bootloader from within twrp.
If those people who have fixed this could give more details about how they did it, that would be good. What exact steps did you take? What stock firmware version did you have before installing a custom rom? What OS version were you using? What twrp version?
Click to expand...
Click to collapse
I second that. Same issue and neither LG Up nor LG Bridge will recognize my device. Looking in device manager there are no serial interfaces. Do I need a special driver that provides a com port for a phone in recovery or fastboot mode?
---Edith 2016-12-12: Found a solution for my issue:
The phone has to be in _download_ mode, not in recovery or fastboot. After realizing that I have to boot the phone in a different manner, it will be recognized by LG UP.
Here is how to boot the pone in download-mode:
- Power off your LG device.
- Press and hold Volume Up button.
- Connect your device to PC with a USB cable while holding the Volume Up button.
- You’ll boot into download mode with “Firmware Update” written on top of the screen.
Now everything is fine again.
croclacrimae said:
Hello everyone,
yesterday I flashed a new Cyanogenmod 14 nightly (12062016) for my G4 from earlier nightly in TWRP. After reboot the phone keeps going back to TWRP and I can't seem to get it to boot to system..
I tried factory reset, reflashing back to old nightly, flashing stock.. but nothing seems to work.
Also tried doing this in the TWRP terminal:
dd[space]if=/dev/zero[space]of=/dev/block/platform/f9824900.sdhci/by-name/fota
Didn't fix the loop, I guess because it wasn't the OTA update that caused the problem in the first place.
If anyone has an idea, I would greatly appreciate the help!
Thanks.
Click to expand...
Click to collapse
I was able to get out of that by also wiping by-name/misc. Don't do that, though, because then your wifi mac address will get messed up and you'll spend all day looking for a permanent fix for that.
I suggest reflashing a stock KDZ using LGUP, as others have said. You can get the usb drivers from LG Bridge.
I will release a fix for that soon. Check the twrp thread for updates on this.
Hi
I also have this problem
I installed cm-14.1-20161201-NIGHTLY-h815 successfully and was running it for almost 2 weeks without issues, today I updated to cm-14.1-20161213-NIGHTLY-h815 from cmupdater and I have been ending up in recovery every time I rebooted.
I tried flashing the latest cm recovery and reflashing the rom, with full wipes but no luck.
Full steps of recovering would be appreciated (for example, there are comments about flashing the latest stock rom, but a link to this rom would be helpful)
Thanks
Good news regarding this:
http://forum.xda-developers.com/showpost.php?p=70082901&postcount=213
The above will fix TWRP bootloop issues as well and I also released a first h811 version which should allow installing CM etc as it should.
Keep in mind that this is a BETA and not an official TWRP release.
Please report back in the above thread!
.
Does your twrp beta really fix the boot loop even it is already happening. What do I have to wipe? I have not managed to get out of the boot loop despite intalling it.
Is using using LG Up to flash to the stock rom really the only option?
Edited 2017-01-25 2:45 pm:
Well, sometimes you just have to be patient. Powered down the phone and when th H815 restarted CM did boot. Great. :good:
Hey, I just want to share a small detail, possibly a fluke that helped me overcome the bootloop.
So...I started with a fresh, stock H815, I don't quite remember the firmware version..it was something like version "20g"..
OK, I looked up several guides and tried to get the newest stable versions of each tool. I went through with the official bootloader unlock, then moved on to rooting: Kingroot didn't work for me so I went on installing twrp in fastboot mode so I could afterwards install supersu and root.
I got there eventually but first I was stuck in bootloop - kept ending up in twrp interface. I found the 2 dd commands but those didn't work for me as the msm_sdcc folder did not exist, but instead there was a "f9824900.sdhci". Tried to overwrite this one ...but as others have stated as well, it didn't work.
At that point, I had nothing to lose, I was starting to accept that I had soft-bricked my precious G4 so..I went on installing the DU 10.6 7.1.1 rom and the stock gapps, wiped dalvik, rebooted and held my breath...not literally
About 12 minutes later, after an endless red, spinning logo, my shiny ping pong paddle showed me a different screen, a fresh start welcome screen .
Almost 24h / 10-12 reboots (twrp included) / 70+ apps installed and removed later, the new OS holds around 2G ram average, a bit better battery life, smoother transitions, flawless navigation, flush streaming over both 3G/LTE & 2.4/5 G wifi.
FYI the reboots were intended, wanted to see consistency in boots - we're in the green . Now testing long term stability with moderate/high usage.
There is 1 aspect I noticed, there are a couple of contexts when the interface burps (several menus, various situations, never in apps) and resets back to homescreen...but I think that's more of a launcher topic than an OS one.
Other than that, so far I'm happy with the mod.
Hope my experience helps others that might be in the same spot I was or at lest boosts their confidence to try out a decent idea they might be pondering.