LG F400L (Korean Variant)
I've had random reboot issues before but very rarely. It only occured during turning on the wi-fi and making a call at the same time.
2 days ago I went from Cloudy 2.5 (L) to Fulmics 5.0 (M), restored all my apps and my settings, then after a day, the bootloop issues started to occur. Sometimes it works and I'm able to use the phone for 1-2 minutes but then it would start bootlooping again (NONSTOP). So i thought the problem had something to do with the ROM so I restored my backup, went back to the Cloudy 2.5 ROM, same settings but SAME ISSUE.
But I found out that, it works when it is plugged in (charging). Even I load it with a lot of apps, no problem, but as soon as I remove it from being charged, it would start bootlooping.
I just need to know what could possibly be the issue?
BATTERY? (Replace the battery)
ROM? (Flash the original Kitkat via download mode)
or somethings else..
and would it help if I post a log?
Thanks. I am in desperate need of an answer
I think your going to need a new battery. Bootloops on 2 rom that have no known bootloop issues and only happening when unplugged from the charger sounds like a faulty battery that can no longer supply high enough voltage or current. A new battery will most likely fix your issue.
Sent from my LG-D852 using XDA Labs
Related
This only seems to be the case when I have the phone plugged in and charging: if I turn the phone off, naturally I get the battery charging icon in the center of a black screen. After this, the power button does nothing, even if I pull the charger from the phone. Further, the charging icon does not go away once the charger is pulled. At that point, I have to pull the battery from the back and put it back in to restart.
Anyone else experiencing this?
same thing is happening to me as well. are you using francisco's kernel running on stock? if no one else is experiencing this, it may be a specific app or kernel thats not playing well with our devices
I believe there are a few people are also having the same problem, so I don't think you are alone.
There is a new update being tested at the moment, apparently a major update and should hopefully address some problems (called 4.1.X). So let's hope that this problem is fixed with the update! (I have no clue what the actual update includes so I am only guessing here)
this seems to be a bug in the os, I had to do a battery pull when this happened to me
Sent from my Galaxy Nexus using Tapatalk
I have this exact same issue when I had Android Revolution HD rom installed with the modified kernel. After restoring back to stock the issue went away. But, I installed a maguro_ITL41F_rooted_deodexed.zip using CWM yesterday and this problem has reappeared. I'm pretty sure the zip included the stock kernel though so this may be an ICS problem.
I'm using a T-Mobile Samsung Note 2 w/ Gummy Nightlies installed currently
Gummy: M3.0-09-02-14-NIGHTLY-t0ltetmo
The problem I'm running into happens consistently but not at predictable intervals. When the phone powers on, every so often while I'm using the phone, whether it be using the internet, browsing through Instagram or Twitter, or just scrolling through the apps my phone will perform a soft reboot.
I've tried multiple ROMs, stable releases, ROMs that aren't CM11 based, nothing seems to fix this issue.
Can anyone shed some light on what might the problem be and possibly a fix?
I'm not sure what else to include that might help anyone with diagnosing the problem, but if there is something that I forgot, I could definitely get you that information.
Have you noted this issue on TouchWiz Roms or is it happening on AOSP Roms exclusively?
Coug76 said:
Have you noted this issue on TouchWiz Roms or is it happening on AOSP Roms exclusively?
Click to expand...
Click to collapse
It hadn't happened on TouchWiz ROMs, but this just started happening about 2-3 weeks ago. I havent used a TouchWiz ROM in months. I've gone from OmniROM to LiquidSmooth to PacMan, to the most recent Gummy. From what I can remember its happened on the two latter ROMs.
It's strange because, I've called T-Mobile to have them send out a replacement battery, I figured that was the issue. I've had no issues with soft reboots while the phone was plugged into the charger, only when unplugged.
T-Mobile decided to just send me a new phone, so I reflashed to stock and im using my phone to send this message with no issues. So maybe AOSP problems?
What can I do to fix this?
Easy answer is stick with TW. That or try an older AOSP build and see if your issues go away. It may be that a specific commit messed with a setting you are running and issues start. I would do a wipe on the offending rom, avoid restoring data via titanium and see if the issues return.
Coug76 said:
Easy answer is stick with TW. That or try an older AOSP build and see if your issues go away. It may be that a specific commit messed with a setting you are running and issues start. I would do a wipe on the offending rom, avoid restoring data via titanium and see if the issues return.
Click to expand...
Click to collapse
The funniest thing just happened, it did it on the stock Firmware. My best guess would still be the battery. Good thing T-Mo sent the phone via Priority Next Day Air. I'll have it some time tomorrow
UPDATE: It now constantly just gets stuck in a boot loop when unplugged from the charger, but when plugged into the charger it has not a single issue. I've ordered a battery from Amazon, but I would still love to know what the issue might be. For example, I want to know why the battery isn't working correctly.
_lolzack said:
UPDATE: It now constantly just gets stuck in a boot loop when unplugged from the charger, but when plugged into the charger it has not a single issue. I've ordered a battery from Amazon, but I would still love to know what the issue might be. For example, I want to know why the battery isn't working correctly.
Click to expand...
Click to collapse
Did the new battery work?
I've got a similar issue ...
I was running Liquid Smooth 3.2 (4.4.4) with TWRP v2.7.0.1 and up until about a month ago, my 2 OEM batteries worked fine.
I was going to head out for the night, so I swapped to battery #2, it went into a boot-loop.
I thought it was a ROM issue, so I reflashed the ROM and still had the boot-loop, even after charging the battery to 100%
It wasn't until the next morning that I re-installed battery #1 and the phone booted fine.
Every time I swap to battery #2, the phone goes into a boot loop.
I ordered another OEM battery from Amazon and the phone goes into a boot loop as well.
The battery contacts on the back of the phone look fine.
I used the following procedure to delete the battery stats and it didn't help:
http://forum.xda-developers.com/showpost.php?p=38500258&postcount=8
I also switched to the JEDI Open Source Project (4.4.4) ROM and only battery #1 works.
I just removed battery #1 from the phone with it plugged into a charger and it remained powered up. I then installed battery #3 and it worked fine. When I rebooted the phone it went into a boot-loop again.
Hello everyone,
I have a serious problem with my 3 months old LG G3 (D855):
It keeps rebooting randomly, and by rebooting I mean the LG logo appears for 3 minutes to several hours, then back to the desktop screen again. It annoys me so much since it occurs pretty much all the time even in the middle of a phone call, rendering the phone completely obsolete…!
I initially thought it was a “compatibility” issue between stock Lollipop and the phone, so I went on rooting and flashing the device back to KitKat then to CyanogenMod 12.1, but the problem persists and now it's the Cyanogen logo that appears instead!
Additionally, I noticed a tremendous heating of the device and quite a lot of lagging even on Nova Launcher!
I’d send it back to SAV if I could but I live in Morocco and the purchase was made from France...
I need your help!
Factory reset it. Remove SD card if you have one. Flash back to complete stock.
DO NOT INSTALL ANY NEW APPS for a couple of days. If issue persists, it's either the battery or the hardware.
I have the same issue I don't think its a one off either my problem started when my phone gets to 15% battery then just randomly rebooted now its stuck like in a boot loop I've tried everything to get it back I was running stock rooted d855
Sent from my Nexus 4 using XDA Free mobile app
Thanks for the replies,
@ nickslg
Yeah I've seen some people having the exact same issue but no real answers were given...
@ robogo1982
Will do, I'll be posting the results soon !
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..
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.