Hello All,
I was one of the first to get my hands on the LG G3 when it came out last year. The phone has been excellent so far, with no issues whatsoever. Lately, the phone crashes very frequently and there is a sort of reboot loop (without evening powering up to the main screen) that goes on until I manually pull the battery out. At first, it used to happen once in a while, but now it seems to happen every time i use the phone for more than 5 min.
Do you know what may be at fault over here?
I have the same issues on my G3-d855.. I did a hard reset but I had no luck.. I also installed the v21A stock ROM but nothing.. I have noticed, though, that there is a pattern in the reboots: they mostly happen when I am receiving an incoming call ( It happens before I answer the phone) or there is a switch from Mobile Data to WiFi and vice versa.. I came back to xda to find a new radio/modem to flash.. I will tell you how that goes..
Related
Hey Guys, I have been beating my head against a brick wall trying to fix my phone.
Yesterday I was on a call with someone and suddenly I lost service (not uncommon for where I was since I have weak service there), but this time the phone was frozen. The dialer screen was on but was frozen. My phone would not react to anything. So naturally I pulled the battery and rebooted the phone. The phone started up as normally it would but then after 5 minutes of the phone running it froze again. During those five minutes I never received any cell signal.
The most recent "work" I had done on my phone was change the kernel to the AK Kernel on the guide here. This was done 3 days before anything started happening. I tried a new kernel because ever since upgrading to Paranoid 3.0 my phone was acting slow and occasionally I would get a screen of death typically about once a day. The 3 days that I had the new kernel, everything was working great (phone was faster, responsive and no SOD).
I tried restoring a nandroid before upgrading the kernel and it made no difference. Ever since the first time my phone down freezes after 3-5 mins after booting up. Nothing that I have tried has fixed the issue.
I have done a clean install, tried locking and re-rooting, tried a different kernel. All to no avail. Please help I am thinking there is something seriously wrong and may need to take it back to verizon. I am trying to restore my device to stock but am unable to do so. I have been using this guide: Restore to Stock. Any suggestions to make it "clean" enough to get verizon to replace it?
I'm going through withdrawals, please help!
Could not fix it, so I contacted tech support and explained everything that I did to try to fix and they just sent me a warranty replacement. I hope that it was a device error and not something that was caused by other ROMs or Kernels.
Hello,
I'm noticing a strange behavior on my (rooted) LG G3 since 1 month.
Every afternoon I leave my car more or less in the same place and them I walk home.
This thing happens everyday at different times (from 16 to 21).
The strange thing is that once that I'm walking home if i get my LG and start to unlock it the phone reboots.
If I walk a little more (far from the place where I park) no reboots happens.
Really strange to me. It seems something related to the place (phone cell?)
Anyway on that place the phone often locks the phone cell with alternative telephone operator (with "R").
But I think that this couldn't be the reason of the reboot, otherwise the reboot should happen also in the morning.
I have Wifi and Bluetooth turned on too.
Can someone help me to investigate using logs to the reason of the reboot?
I have bought 3C application (without any tweak added) so that i can access logs once that the phone completed the reboot.
Can someone help me to understand what I have to look for to find the reboot reason?
Thanks a lot
Hi, I don't know if this has been mentioned anywhere and yes i know the bootloop issue is a big problem but i wondered if anyone else has been semi-successful like me. First off the other day my phone rebooted and ended up in a bootloop except the screen never goes completely blank it just dims and comes back on. I did a hard reset and it starts working again for a few days. Then when i connect to wifi it will reboot all of a sudden and be fine until it reboots again and i have to hard reset for another few days. sometimes when looping it will get to the updating apps screen then when it finishes it loops again.
Is this the standard bootloop or does it seem like something different?
Sorry if this is just another repeat of an old issue it just seems to be slightly different from what i have read about the bootloop caused by the known hardware issue. Also the first 3 digits of the serial are 507 if this helps.
BipolarBinary said:
Hi, I don't know if this has been mentioned anywhere and yes i know the bootloop issue is a big problem but i wondered if anyone else has been semi-successful like me. First off the other day my phone rebooted and ended up in a bootloop except the screen never goes completely blank it just dims and comes back on. I did a hard reset and it starts working again for a few days. Then when i connect to wifi it will reboot all of a sudden and be fine until it reboots again and i have to hard reset for another few days. sometimes when looping it will get to the updating apps screen then when it finishes it loops again.
Is this the standard bootloop or does it seem like something different?
Sorry if this is just another repeat of an old issue it just seems to be slightly different from what i have read about the bootloop caused by the known hardware issue. Also the first 3 digits of the serial are 507 if this helps.
Click to expand...
Click to collapse
Maybe yours is jut preparing for proper bootloop maybe the pins on the bigger qualcomm chip still connect to the motherboard from time to time so you manage to get it booting. Though I wouldn't call it a working device so I would suggest you to start working with LG to have it fixed.
BipolarBinary said:
Hi, I don't know if this has been mentioned anywhere and yes i know the bootloop issue is a big problem but i wondered if anyone else has been semi-successful like me. First off the other day my phone rebooted and ended up in a bootloop except the screen never goes completely blank it just dims and comes back on. I did a hard reset and it starts working again for a few days. Then when i connect to wifi it will reboot all of a sudden and be fine until it reboots again and i have to hard reset for another few days. sometimes when looping it will get to the updating apps screen then when it finishes it loops again.
Is this the standard bootloop or does it seem like something different?
Sorry if this is just another repeat of an old issue it just seems to be slightly different from what i have read about the bootloop caused by the known hardware issue. Also the first 3 digits of the serial are 507 if this helps.
Click to expand...
Click to collapse
flash stock firmware and then try it for weeks if it happens then hardware is damaged..
BipolarBinary said:
Hi, I don't know if this has been mentioned anywhere and yes i know the bootloop issue is a big problem but i wondered if anyone else has been semi-successful like me. First off the other day my phone rebooted and ended up in a bootloop except the screen never goes completely blank it just dims and comes back on. I did a hard reset and it starts working again for a few days. Then when i connect to wifi it will reboot all of a sudden and be fine until it reboots again and i have to hard reset for another few days. sometimes when looping it will get to the updating apps screen then when it finishes it loops again.
Is this the standard bootloop or does it seem like something different?
Sorry if this is just another repeat of an old issue it just seems to be slightly different from what i have read about the bootloop caused by the known hardware issue. Also the first 3 digits of the serial are 507 if this helps.
Click to expand...
Click to collapse
Dont play around with it too much it might get permanently bricked ur best option now is to flash a lollipop kdz root it then apply the disable core method to working it again ofcourse the phone will be slow ...or u could just send it to lg for replacement or repair...check youtube for disable core method for g4
I have just plugged it into Lg bridge and run the update error recovery. It hasn't rebooted when connecting to wifi yet but if it does I'm just going to phone LG to sort out a repair and buy a temp phone to use while that happens. I just don't want to do anything that could affect warranty although usually, the warranty would be out the window on day 1 with me
It just seems weird that every time I have seen it reboot it was when it connected to wifi.
I was just wondering if anyone else has an issue with their Note 4 rebooting randomly with no external input. This started happening with the Android 6.0 update both on the download from here and the AT&T official release, Any Ideas? I've already purchased a new battery due to a separate issue, any idea?
I had the same problem. The phone would freeze and randomly reboot. Sometimes the system crashes and asked me for the typed-in password (not fingerprint). Sometimes when I charge the phone, and unplug the power cable, the charging led stays lit and the battery has to be pulled. I decided to switch the battery with my wife's Note 4 and see if the effects remained. So far I haven't had any problems after switching the battery, so I believe the battery may be the cause of all these issues. I'll keep you updated on the issues.
I'm back. The battery replacement didn't fix the reboots. I think my phone's hardware is permanently damaged. :crying:
have you downgraded?
and can you help me with my problem?[
AlexanderDAB said:
have you downgraded?
and can you help me with my problem?[
Click to expand...
Click to collapse
I'm downgrading to stock 5.1.1 right now. I'll keep you updated. I placed an order for a Galaxy S7 Edge International Version (G935F) yesterday.
ajumatt said:
I'm downgrading to stock 5.1.1 right now. I'll keep you updated. I placed an order for a Galaxy S7 Edge International Version (G935F) yesterday.
Click to expand...
Click to collapse
can you downgrade to Android 5.0.1 and help me with my problem?
its something completely different to this topic
I've been having the same issue, started about 2 weeks ago. phone would start being sluggish then if I continue tapping on screen, it'll reboot. At least once I saw it go into recovery & reinstall firmware(?). Another time it just sat at the bootloader screen waiting for software download or something till I took out the battery. Most likely it's a software issue related to 6.0 update or updates afterwards. taking out the SD card helped a bit.
but basically got annoyed & upgraded to LG V20 today. Coincidentally, there was another person at the AT&T store with a Note 4 having the same issue.
Mine just rebooted twice on me a while ago, first is emergency calls only now the reboots then what. And yes the slow charging is a problem too. MM got serious issue dam att
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app
adavis1201 said:
I was just wondering if anyone else has an issue with their Note 4 rebooting randomly with no external input. This started happening with the Android 6.0 update both on the download from here and the AT&T official release, Any Ideas? I've already purchased a new battery due to a separate issue, any idea?
Click to expand...
Click to collapse
use wakelock its an app u get it from play store.it makes ur cpu always running.some how it fixes the problem of random reboots. dl it and set it to partial lock (the 5th option)
Same problem. Just started a few weeks ago. REALLY frustrating having to enter my password every 3-4 minutes. NEVER buying another Samsung, too many damn issues with this phone.
My reboots tend to happen once the phone goes below 60% battery. It's fine above 60%. Once it goes below 50%, the reboots tend to happen with any intense network activity. The phone will often go from 50% to 22%. I forgot what the 30's and 40's look like. I will try the Wakelock app.
Ugh. I posted about this a few weeks ago. It's started happening more frequently and will occasionally go into a boot loop or show 0% battery even though there's a charge.
Has anyone found any solution? I haven't tried wiping / resetting but I'm getting close to trying it.
Here is a cautionary tale for you. My completely stock, unroooted phone started acting the same exact way. On the 4th or 5th battery pull (to fix a frozen screen) it just crapped out. It's totally unresponsive. Deader than a door nail. Tried everything. The download mode, discharging by power button depression/battery removal, etc. Adb shell command does not detect it. Nor Odin. Computer throws up a qhsusb_bulk error when I plug it into pc. I have NO CLUE how to fix it & I am desperately seeking a solution. Please proceed wisely with your oddly acting phones & don't let this happen to you.
k.babymamma said:
Here is a cautionary tale for you. My completely stock, unroooted phone started acting the same exact way. On the 4th or 5th battery pull (to fix a frozen screen) it just crapped out. It's totally unresponsive. Deader than a door nail. Tried everything. The download mode, discharging by power button depression/battery removal, etc. Adb shell command does not detect it. Nor Odin. Computer throws up a qhsusb_bulk error when I plug it into pc. I have NO CLUE how to fix it & I am desperately seeking a solution. Please proceed wisely with your oddly acting phones & don't let this happen to you.
Click to expand...
Click to collapse
Same issue. Just got off the phone with Samsung support, all possibility of having this particular phone with this particular issue sent in for evaluation has been suspended. Translation, they know it is an issue and will not stand by the changes they push to their products (latest OS). I am researching the prospect of legal action since THEY pushed the new OS against my request. Shouldn't that affect the warranty or coverage? Consulting my attorney friends as we speak. Will let you know. I am not sure how WakeLock will help, it is not going to sleep, it is repeatedly power cycling through a kernel process until the battery overheats or it reboots.
Same issue
Since Marshmallow, my 910A will get sluggish or freeze, shut down, sometimes reboot and sometimes just brick (temporarily). Sometimes--more often in recent days, I get a "dll_mmc read fail" message and the target that says do not stop downloading. No matter what I've tried--factory and soft resets, cache clearing, battery pull, replacement, and SD card switch, contacting AT&T and Samsung rep--it doesn't seem to change. This is a daily issue and becoming more frequent. Any suggestions or do I just need a new phone? Thank you.
Hello everyon everyone.
I have the SM-P600 version, everything was good until the beginning of the week when touchpad began to go off without reason, and completely random.
I first reinstalled several official ROMs from the most recent to the oldest, with no significant improvement
Then i rooted and tried Lineage, it looked good for a while, but in the end same problem.
Please note, when the tablet begins to mess, the reboots are occuring more and more often and after a while it turns in a loop and im not even able to switch it off.
Samsung logo display, black screen, logo, black screen, etc ...
I think rather for a battery-side problem, if some people have faced similar problem, I'm taking help.
Do you know if by chance we can use the tablet without battery to test this theory?
Thank you in advance for any answers.
jb1207 said:
Hello everyon everyone.
I have the SM-P600 version, everything was good until the beginning of the week when touchpad began to go off without reason, and completely random.
I first reinstalled several official ROMs from the most recent to the oldest, with no significant improvement
Then i rooted and tried Lineage, it looked good for a while, but in the end same problem.
Please note, when the tablet begins to mess, the reboots are occuring more and more often and after a while it turns in a loop and im not even able to switch it off.
Samsung logo display, black screen, logo, black screen, etc ...
I think rather for a battery-side problem, if some people have faced similar problem, I'm taking help.
Do you know if by chance we can use the tablet without battery to test this theory?
Thank you in advance for any answers.
Click to expand...
Click to collapse
I think I'd be taking a close look at the physical power button. Seems to me that if it had gone flakey it could cause something like this.
marshallartsoz said:
I think I'd be taking a close look at the physical power button. Seems to me that if it had gone flakey it could cause something like this.
Click to expand...
Click to collapse
Hello and thanks for you answer,
Just to precise i never faced this issue while flashing an official or custom ROM, dont know if it is just luck or it can help in anything
Anyway ill try to check it the power button just in case
It's weird I just started having this exact problem myself. One morning I unplugged it and it had shut itself down overnight. Since then it randomly reboots. Sometimes I can get 20/30 minutes out of it, but once it starts, it can get into multiple reboots with the only way to stop it is to plug in the charger. I tried wiping cashe/dalvic (no help). Nothing was recently changed (including apps). Tried resoldering battery connector (battery was replaced a year or so ago with OEM Sammy). The P600 is rooted with TWRP installed, but no custom ROM. Usually the reboots start while I'm doing something (surfing, email, etc.), but I don't think it will do it while sleeping. I'm considering the power button, but I don't see this exact problem anywhere else, but this post. Any ideas?
OK. My tablet has taken a turn for the worse. Now it is stuck in a continuous boot loop. I tried the power switch, no help. I tried booting into TWRP, and it went back into rebooting before I could do anything. Strange thing is I can put it into download mode indefinitely without it rebooting. Should I ODIN back to stock? I tried the resoldering of the battery connection earlier. Any other ideas?