lg g2 keeps restarting - G2 Q&A, Help & Troubleshooting

Hi.i have lg g2 d800 32gig.it was with stock 4.4.2 and from time. To time it freeze and restart itself. I install. Cm 12.1 lolipop snapshot.and it keep doing it,every houer or so.i even unolugged the motherbord and installed again.what is the prob??

Probably one or more than one apps causing this.

Try another rom. I never use CM base, let alone a snapshot/nightly. Install Resurrection Remix M, it's based on CM stable and is faster and has more features.

But the device also restart. With the stock rom 4.4.2. Is there maybe prob in the motherbord?
Sent from my LG-D800 using Tapatalk

could it be or maybe a stuck or sticky power button?

Hi,idont think its asticky power,because it happends 6-8times aday.not all the time.i dont know how to fix this prob...

boot stack
I had the same problem. Install boot stack first then flash CM then gapps.

More likely its a hardware issues. Or May be something has to relate with Bootstacks.
I have lost My G2, In no point return mode! So move on with other device. Honesty G2 isn't made for all people. That's all I can say.

Related

[Q] Bootloop after installin XCam LG v5.0.0 binaries

Anybody know if there is a fix or solution to this situation? :
Installed Pardus HD Rom on My LG G2 32gb D802 and then flashed through TWRP 2.7.0.0
[MOD] XCam LG v5.0.0 [G2/GPro2/G3] >> xdabbeb_camera_binaries_v1.0.0g2.zip
After that my system hasnt booted up, its stucked in bootloop kid of. Sometimes it was saying proccess android.systemui was stopped or in most cases it was just in bootloop. As a result i had to use recovery and get back to previous ROM (CM M9)
Any idea whats going on ?
Reply
Pardus is heavily modified, lots of stuff can go wrong. If you see the original XCam thread, there is a way to take a logcat and see it, but as you said you have gone back to CM. Try Cloudyfa's ROMS, expecially the new G3 one, pretty good, better than CM in my opinion even thou I am staunch advocate of AOSP. Also, read and re-read to make sure you know what you are getting into.

CM11 - i9505 Boot Delay/Hangs

Hi at all! Since I had my first smartphone I always used CyanogenMod to unlock all the power of my devices and have an pure stock android experience. I use CM11 on a s3 and a few times ago on a s4. I used always nightly build because I'm curios and I like to discover bug and discuss with other to solve them (I'm not a developer, only an appasionated smartphone user).
With my s4 (i9505) I used officials nightly from jflte section of cm download site and I updated it with Cyandelta app. I used Ktoonsez kernel.
It's impossible for my s4 to boot into Cm11 after a reboot or when I PowerOn my device after a battery change (because previous battery was 1% and device shuted down), because it hang on Model Number Splash screen. I have to remove battery, Hold for 5-10 seconds power button, insert battery and powerOn. Anyone has any idea for this problem? I've tried a lot of times to change from CM to TW and From TW to CM but problem persist anyway with Kt kernel and with stock cm kernel, but with TW rom problem doesn't appear.
A little note, I'm not using original Samsung Battery. Thanks at all and sorry for my crappy english. I'm a young student.
Try removing the batterystats.bin file... Maybe its getting confused on that.
See here for details on how to remove it: http://forum.xda-developers.com/showthread.php?t=1699687
I've found problem. Kernel wasn't compatible with last version of CM11.
How to close post?

[Q&A] [Kernel]***[D80*/LS/VS980/F320x] B14CKB1RD AOSP [1/18/15]***

Q&A for [Kernel]***[D80*/LS/VS980/F320x] B14CKB1RD AOSP [1/18/15]***
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Kernel]***[D80*/LS/VS980/F320x] B14CKB1RD AOSP [1/18/15]***. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
4 cores working with the screen on... battery life....
stuck at logo after kernel flash
I am on the liquid milestone 3.2. I saw that this is the same kernel but updated version that came in the rom so i wanted to update. No matter
Now i am stuck in a boot loop. phone powers on, stays at the LG logo, goes no further. I can get to Download mode, but no recovery.
Is there a way to recover this thing with out having put a locked stock rom on it??
DT2W double tap to wake
I love the Kernal so far however i've got a question about the double tap to wake features. Is there a way to have the screen turn off by double tapping somewhere OTHER than the notification bar at the top of the screen? Also it takes me about 4 or 5 double taps to get the screen to actually wake up, any ideas on any of this ? Thanks!
Hear myself in the phone... rom or kernal problem?
hello love the work you guys do its exciting and interesting. Ive relatively recently started playing with custom roms and kernals etc. love this one because i get excellent battery life as well as a solid LTE signal (two things ive had trouble finding with lollipop so far.. might just be me). Anyway ive got an issue with hearing myself in my phone when im on the phone... its like everything i say approx half a second after i say it.. needless to say its rather annoying, is this a rom or kernal problem? volume settings issue? not sure.. Also my proximity sensor occasionally wont register that my ear is near it.. baaically the screen stays on if im say checking my voice mail or on the phone.. not sure why this happends.. Everything else works great.. some info: d801 lg g2, lastest rr build for lp and i have the lasest blackbird for lollipop. its a really solid combo and im loving it.. thanks for any information you may have
asustweaker said:
I am on the liquid milestone 3.2. I saw that this is the same kernel but updated version that came in the rom so i wanted to update. No matter
Now i am stuck in a boot loop. phone powers on, stays at the LG logo, goes no further. I can get to Download mode, but no recovery.
Is there a way to recover this thing with out having put a locked stock rom on it??
Click to expand...
Click to collapse
did you flash kitkat version or lollipop version? Sounds like you flashed lollipop version
Nicholi85 said:
I love the Kernal so far however i've got a question about the double tap to wake features. Is there a way to have the screen turn off by double tapping somewhere OTHER than the notification bar at the top of the screen? Also it takes me about 4 or 5 double taps to get the screen to actually wake up, any ideas on any of this ? Thanks!
Click to expand...
Click to collapse
Update the touch screen firmware....there's an echo call via android terminal emulator or in my updated version in synapse
Nicholi85 said:
hello love the work you guys do its exciting and interesting. Ive relatively recently started playing with custom roms and kernals etc. love this one because i get excellent battery life as well as a solid LTE signal (two things ive had trouble finding with lollipop so far.. might just be me). Anyway ive got an issue with hearing myself in my phone when im on the phone... its like everything i say approx half a second after i say it.. needless to say its rather annoying, is this a rom or kernal problem? volume settings issue? not sure.. Also my proximity sensor occasionally wont register that my ear is near it.. baaically the screen stays on if im say checking my voice mail or on the phone.. not sure why this happends.. Everything else works great.. some info: d801 lg g2, lastest rr build for lp and i have the lasest blackbird for lollipop. its a really solid combo and im loving it.. thanks for any information you may have
Click to expand...
Click to collapse
These are ROM related errors...the call echo especially... Depending on ROM I could help....also see if it still persists in my latest update
Love this kernal, and I flash when installing a new LP build, but I've been having problems lately. After initial setup or reboot I get the" NO UCI SUPPORT " message. I'm running LiquidSmooth's latest build for the LS980, is anyone else having this issue.
Run om g3 based roms?
VictorAKAx said:
Run om g3 based roms?
Click to expand...
Click to collapse
No. This kernel is for AOSP-based ROMs. G3 ROMs are stock-based.
Typos courtesy of my Ice Cold LG G2 (D803).
just flashed your kernel, got stuck in a boot loop.
VS980, liquidsmooth 3.2 milestone.
what can i do? was excited to try out your update
Great kernel, running super smooth on AICP.
Thanks!
He's working on the fix for cm 12.1.
I sent my files on hangouts, just wait
edit: figured it out
does anyone have a dt2w fix for vs980? i just flashed liquidsmooth 4.0 and everything was working fine, flashed the kernel and it broke my knock on support. i found the zip posted in the main kernel thread (this one) and twrp tells me the file is corrupted
perforatedpaper said:
does anyone have a dt2w fix for vs980? i just flashed liquidsmooth 4.0 and everything was working fine, flashed the kernel and it broke my knock on support. i found the zip posted in the main kernel thread (this one) and twrp tells me the file is corrupted
Click to expand...
Click to collapse
Use the 0 init method:http://forum.xda-developers.com/showpost.php?p=56948464&postcount=73
I'm using F320K with BlissPop v2.3 rom, when flash this kernel for lp 5.0.2, it cause loopboot. Pls up kernel fix for lolipop 5.1. Hope to see it soon. Thanks u
llamas612 said:
I'm assuming that those are 5.0 based, since they're from January, right?
Click to expand...
Click to collapse
I think they're KitKat based. I tried already and it caused my d800 to go in a boot loop.
I wonder if anyone has got, perhaps, the 5.1 d800 version? I'm getting kinda desperate since my fav rom switched to a kernel that makes my phone really really hot.
Really need a link to latest 5.1 B14ckB1rd kernel for D800 :/
Pls...

Lg G2 VS980 wont go past Lollipop for me?

I need some help, anyone, please! I have a Lg G2 VS980, rooted supersu by chainfire version 2.79 latest, i guess. twrp 3.2.0-1 by blastagator, and running resurrection remix 5.4.7(Lollipop 5.1.1) from stock rom VS98024a which i pushed with lgtool14, i believe. From stock VS98011a which i also installed a year ago when my ParanoidAndroid os Lollipop rom 5.1.1 just stopped working all together dont know why, still. tried flashing over that with lollipop CrDroid rom Lollipop 5.1.1 when the phone bricked. So I proceeded to start from scratch again learning as i go, im kinda good like that sometimes. so i did all of this all is working well and good again, except for one thing, when I try to flash any custom marshmallow even nougat roms they install like the lollipop ones fine, matching micro Gapps packages every time for marshmallow and nougat roms. wipe the dalvik and cache properly, all is good til reboot of the system. Lg logo comes up then black screen and nothing else ever, Ive let it sit for hours and nothing. i dont know what i am missing here i know its possible to go past lollipop but im at a loss here. ive searched til my eyes bleed but there is no comprehensive guide on how this is accomplished and what to do with the black screen issue im facing. i dont know if i need to do a bootstack change or something else i dont know about. If i could get some guidance here maybe a solution to this issue. hell i dont care if i got to start from scratch again. something guys. if you need any info i havent provided ask. and yes i have all the proper latest drivers, adb, fastboot, and even latest android studio from google, which i dont have a clue as to how to use. im not a noob but by no means a developer, lol.

Moving to LineageOS worth it (and possible) from Cloudy G2.2?

I've been running Cloudy G2.2 for a year an a half. It's given the phone enough legs to mostly make it through 2017. However, about every other week I have to restore my latest backup when Bluetooth stops working because it saw too many devices. This wouldn't be terrible if it wasn't for Authy refusing to sync my newer 2-Factor auth accounts. I think I've convinced myself that the G6 (US997) is my next phone, but now is a silly time to buy as the price should drop like a rock as the next wave of flagships come out.
I'm hoping to make it another couple months and was wondering anyone's experiences moving from Cloudy G2.2 (or other ROMs) to the latest lineage? From what I've read, it's very stable. However, I'm on Kit Kat bootloader, so it doesn't seem like this will be a straightforward process. I was hoping to get some experiences from people who made the same move before starting.
I currently have:
LG G2 D800
Root using stumproot (I think, it's been a while) with supersu installed
TWRP 2.7.0.0 installed by autorec
Cloudy G2.2 KOT49I
So, after some research, I set off to install LineageOS. In hindsight, this might have been a bad idea since it specifically only mentions the D802 in the title. However, it listed links for D800 builds, though they were crossed out.
I updated TWRP to this version by Blastagator and that was painless. I then wiped the phone, made a fresh backup and flashed the latest nightly of LineageOS, and the latest GApps (Mini) for 7.1. That was disappointing since I got the quick "LG logo" followed by a blank screen, that I later found was mentioned in the same Lineage post. Should've read farther.
I think the issue is that I'm on the wrong bootloader. I thought I was on KitKat which the post requires, but in order to enter recovery, I have to press enter three times (rather than using volume buttons to navigate), which indicates I'm on JellyBean bootloader.
So, this is the scary step that I was hoping to avoid. My big fear is that I run Linux on my desktop, so I can't use the LG Flash Tool. As long as I can keep a working recovery, I have backups, so I'm fairly safe. Following the Blastagator bootloader post, I'm not really sure how you go back and forth between bootloaders so easily as it suggests. Is that really as simple as loading the zip file on the phone and installing it in TWRP?
Is there a safer way to handle this?
From my experience, it is that easy. Simply install the zip file and you have loaded a new boot loader. Also, I was in the same boat as you with Cloudy rom and moved to Nougat with crDroid. However it's not stable and I am considering looking for something else more stable but fast like crDroid.
ernie young said:
I was in the same boat as you with Cloudy rom and moved to Nougat with crDroid
Click to expand...
Click to collapse
When you updated your bootloader, were you still able to run the Cloudy ROM before you switched to crDroid? Once I flash the KitKat bootloader, am I only able to use the Nougat ROMs? My big concern is that there might be something a bit off with my bootloader, so I won't be able to get back to TWRP.
I think there's something a bit off with my bootloader as is, because about a year ago I flashed back to stock Jellybean, and took all the OTA updates. However, when the phone tried to take the KitKat update, it softbricked, and could only be recovered using the LG Update Tool, which I don't have access to anymore. Because of this, I'm a little worried that just dropping on the Blastagator KitKat bootloader may have some atypical issues.
i m using it for a while. u know, on Los you won't be able to use lg features such as qslide, qmemo, plug&pop, knockcode etc. Only worth it if you want your phone to look a little bit fresher and lighter or you need a newer android version for some reason. Else, don't take the risk if you can't use flashtool. You can consider installing another kitkat rom. There are lots and they are nice :]
S YILDIRIM said:
or you need a newer android version for some reason.
Click to expand...
Click to collapse
My primary issue is that KitKat (or whatever Cloudy G2.2 is?) has the old Android bluetooth bug where once it sees too many devices, it stops connecting to anything. I have to make sure to turn off my phone if I go somewhere like an airport, and have been having to restore my clean Cloudy backup about once a month. It's getting pretty frustrating. On the other hand, I'm hoping to upgrade to an LG G6 (US997) in a month or two when the V30 release pushes down on prices. So, if it's a case of potentially hard-bricking my G2 at the worst possible time, I should hold off flashing.
I think you need hybrid bootstack for android 7.
WORF84 said:
I think you need hybrid bootstack for android 7.
Click to expand...
Click to collapse
That makes sense, but will I not be able to use my Cloudy 2.2 backup after that? It says that the hybrid bootstack will only boot CM 12.1, CM13, and LP stock roms.
superlou23 said:
That makes sense, but will I not be able to use my Cloudy 2.2 backup after that? It says that the hybrid bootstack will only boot CM 12.1, CM13, and LP stock roms.
Click to expand...
Click to collapse
These questions if this works with that or that are easier to answer for yourself by reading what goes with what.
Just Google LG G2 bootstack and you can probably find the ones you need for any available rom.
I use hybrid on Marshmallow 6.0.1 but I tried Nougat 7.1.2 too, it works.

Categories

Resources