I just rooted and installed TWRP. Now when I power off my G3, I cannot boot it back up unless I pull the battery. I am not sure what went wrong. Please help
this happens to me on both D852 stock ROM and Cloudy.
I have the Sprint variant and I used to have the same issue on every power cycle. But now it happens maybe once every 20 power cycles. Do you have xposed installed? Make sure you flash the latest framework.
alqoshi4life said:
I have the Sprint variant and I used to have the same issue on every power cycle. But now it happens maybe once every 20 power cycles. Do you have xposed installed? Make sure you flash the latest framework.
Click to expand...
Click to collapse
no exposed. what is this power cylce you are talking about?
oxxshadow said:
no exposed. what is this power cylce you are talking about?
Click to expand...
Click to collapse
Sorry, by power cycle I mean the power off/reboot process. Sometimes, I would reboot my phone, but instead it would power off and it would not power back on until I did a battery pull. I also noticed that this happened more often when my battery was very low (below 10%). But for some reason I haven't had this happen to me in a while.
alqoshi4life said:
Sorry, by power cycle I mean the power off/reboot process. Sometimes, I would reboot my phone, but instead it would power off and it would not power back on until I did a battery pull. I also noticed that this happened more often when my battery was very low (below 10%). But for some reason I haven't had this happen to me in a while.
Click to expand...
Click to collapse
Did this happen to you when you were stock and unrooted?
Can you charge the phone while the screen is off? Because when it happens to me, I cannot charge the phone with screen off.
oxxshadow said:
Did this happen to you when you were stock and unrooted?
Can you charge the phone while the screen is off? Because when it happens to me, I cannot charge the phone with screen off.
Click to expand...
Click to collapse
Well, once I upgraded to Lollipop this started happening. It never happened when I was on kitkat, and both times I have been rooted with custom recovery. It would do the same thing as you are describing. The phone acts dead and it does not charge/power on until I do a battery pull. The first time it happened I was scared because I thought I bricked the phone!
alqoshi4life said:
Well, once I upgraded to Lollipop this started happening. It never happened when I was on kitkat, and both times I have been rooted with custom recovery. It would do the same thing as you are describing. The phone acts dead and it does not charge/power on until I do a battery pull. The first time it happened I was scared because I thought I bricked the phone!
Click to expand...
Click to collapse
Is there a resolution to this? Or how is the problem for you now
I haven't found out what caused the problem to go away. I can either relate it to installing g3 tweaksbox and having the power menu come up through long press of home button, or by making sure I didn't greenify/freeze any critical system app. There is a system app called "Shutdown Monitor" that I think controls this power down process.
alqoshi4life said:
I haven't found out what caused the problem to go away. I can either relate it to installing g3 tweaksbox and having the power menu come up through long press of home button, or by making sure I didn't greenify/freeze any critical system app. There is a system app called "Shutdown Monitor" that I think controls this power down process.
Click to expand...
Click to collapse
does the issue still occur with you?
oxxshadow said:
does the issue still occur with you?
Click to expand...
Click to collapse
It used to happen almost on every reboot, but it only happened once in the last month. I can't trace it down to one cause. I think it has to do with active apps or processes that are interrupting the shutdown process. Make sure all your apps are closed and cleared from recents before shutting down.
I've been seeing this issue on CM12.1. I always thought the problem was CM related. It's interesting to see it's happening on stock ROM.
EDIT: phone is a d852
oxxshadow said:
I just rooted and installed TWRP. Now when I power off my G3, I cannot boot it back up unless I pull the battery. I am not sure what went wrong. Please help
Click to expand...
Click to collapse
U have D850 right?
This issue is mainly with the at&t version of g3. On stock KK everything will be fine.
But on any LP rom there will be the No boot without battery swap issue and also Signal Drop issue.
This is not a issue with the roms. It is an issue with our AT&T lg g3. After a whole lot of search i still could not find anything. So i exchanged it with the international version.
Ive got the 32gb 3gb ram International version and mine does it too.
Its completly stock no root.It did it once about a month ago.
Then today i did a factory reset,charged the phone to 100% and unplugged it.
Went to use the phone a few hours later and it was dead had to do the battery pull connect to charger.
Battery was at 84%.
I also have this issue on my 32GB D852 variant. Battery pulls about 50 or 60% every time I try to boot. Sucks big time.
Sent from my LG-D852 using Tapatalk
I have the issue too- D850 Fulmics 2.7. It's randomly shut off twice now in the past two weeks. Hopefully marshmallow will fix it! At the very least I'm glad it's not just me experiencing the issue- I just bought the phone used and was worried it was a dud.
Since this thread is pretty old now I'm wondering if people who have had the issue have any recommendations for potential fixes too.
Downgrade your TWRP to 2.8.5.1 and this will most probably (90%) solve booting problem. Before that you want to backup your modem with newest version of TWRP because old wersions can not do that. In case you need to restore your modem, just upgrade to newest version. So you are fully covered
I know I'm late to the game, but I want to thank @Navuhodonosor. Downgrading TWRP fixed my problem. I haven't had to pull the battery in over a month. Reboot and power on both work now, though Chainfire's Liveboot doesn't always load. Considering I installed that to try to troubleshoot the problem, I don't care
Related
I can't turn on the device while its plugged in and charging while its turned off. I would have to take out the batteries everytime. Is this a bug or is it suppose to be like this?
Sent from my Galaxy Nexus using Tapatalk
i have the same problem with all coocked rom but no with stock
i can turn it on... just hold the power button for a few seconds.
melterx12 said:
i can turn it on... just hold the power button for a few seconds.
Click to expand...
Click to collapse
Tried holding it for 2 minutes yet nothing happens. Don't think it is rom problem?
Sent from my Galaxy Nexus using Tapatalk
Good thing I read through this q n a, I'm going crazy too. When I power off (to reboot after installing tons of apps, to refresh etc.) I get the battery charged icon and freezes there. Only battery pull works. I'm on Android Revolution 2.1.0 unlocked and rooted. I guess bug? Annoying, feel like I'm going to tear the cover every time and damage the screen
This happened to me too, and the battery charging icon caused burn-in. Fortunately, it went away after a day or so.
Same bug here. We'll have to hold tight and wait for a fix or run stock.
On my Fascinate you could hold the vol up and power button to get soft boot the phone, but the GNex does not seem to have this feature. I hate pulling the battery.
Same issue for me ... I think we have to open a bug tracking. This is a very annoying problem.
Android 4.0.2
Kernel 3.0.8-gaaa2611
Since my phone is new to me I wanted to power down and get a full charge.. but I can report this bug as well. /cry
Did any of you use a different rom prior to ARHD? I wonder if its something in the kernel or the OS. What allows the phone to show that animation when turned off? That could hint at what modification breaks offline charging.
I have this problem too running a revolution rom. The phone charges fine but I have to pull the battery to boot up. It's a strange one!
does this happen to stock rom? the one shipped with the phone?
zeke1988 said:
does this happen to stock rom? the one shipped with the phone?
Click to expand...
Click to collapse
No!
The bug happens with custom roms. Infact I went back to the stock rom and (even if rooted) I can charge the phone when it's turned off without having problems.
I am certain the phone still charges to 100% but it appears to be frozen. The only way to boot back up is a battery pull.
Any more info on this from anyone? I saw a 4.0.3 rom yesterday that claims to fix the issue so maybe that's the way forward.
Same here, on bigxie's ROM, if I try to boot with phone plugged in from being dead, freezes right at battery charging icon, have to battery pull. Very annoying.
just4747 said:
Very annoying.
Click to expand...
Click to collapse
I agree.... infact I will not use custom roms until the bug will be closed!
This seems to be more prevalent in 4.0.3 roms. I have a deodexed 4.0.2 rom from bigxie which charges just fine when powered off. However any 4.0.3 rom will not let me charge while off.
Not sure if it's an unintented bug but we'll have to see when the full update hits gnex officially.
ihyln said:
This seems to be more prevalent in 4.0.3 roms.
Click to expand...
Click to collapse
I don't think so. I had the bug in a 4.0.2 custom rom
Fixed in 4.0.3 ROM/Kernel.
RMatt1992 said:
Fixed in 4.0.3 ROM/Kernel.
Click to expand...
Click to collapse
what and where? GSM usually doesn't apply to us CDMA/LTE users especially if it's a rom/kernel issue.
Might be related to a custom recovery. Do you guys all have ClockworkMod in common? I have a stock recovery and don't have such problems.
Hi XDA,
My friend her G3 randomly shuts down sometimes, and it's impossible to boot it again for a while. After several hours it'll boot again on its own, and it seems like it went into some sort of hibernation since she doesn't have to enter her pin or anything.
Things she tried include removing the battery, holding down the power button for a long duration and charging the phone. Last time this happened the phone was at roughly 30% battery.
Does anyone here maybe have an idea what it could be or what a possible solution would be? It sounds like a very strange and improbably issue to me.
Thanks for reading!
verluci said:
Hi XDA,
My friend her G3 randomly shuts down sometimes, and it's impossible to boot it again for a while. After several hours it'll boot again on its own, and it seems like it went into some sort of hibernation since she doesn't have to enter her pin or anything.
Things she tried include removing the battery, holding down the power button for a long duration and charging the phone. Last time this happened the phone was at roughly 30% battery.
Does anyone here maybe have an idea what it could be or what a possible solution would be? It sounds like a very strange and improbably issue to me.
Thanks for reading!
Click to expand...
Click to collapse
This is due to kernal panic.
Flash stock firmware may be this will fix your problem
http://forum.xda-developers.com/showthread.php?t=2785089
Again this is a biasn answer could be kernal panic bad tweak rogue app. Ive even saw one that had a battery crap out on him out of nowhere
TheMadScientist420 said:
Again this is a biasn answer could be kernal panic bad tweak rogue app. Ive even saw one that had a battery crap out on him out of nowhere
Click to expand...
Click to collapse
From next time i will try to mention all the possible reasons
Thank you straight flashing back stock may be a quick fix most of the time but we dont figure out the cause so we end up in the same boat cause we try to tweak the same tweaks. I dont claim to have the answers and yours could be correct. And i also accept critisism if im wrong
verluci said:
Hi XDA,
My friend her G3 randomly shuts down sometimes, and it's impossible to boot it again for a while. After several hours it'll boot again on its own, and it seems like it went into some sort of hibernation since she doesn't have to enter her pin or anything.
Things she tried include removing the battery, holding down the power button for a long duration and charging the phone. Last time this happened the phone was at roughly 30% battery.
Does anyone here maybe have an idea what it could be or what a possible solution would be? It sounds like a very strange and improbably issue to me.
Thanks for reading!
Click to expand...
Click to collapse
This could be a battery error. Is your battery old or new?. Otherwise it could be a kernel issue which can be caused by under volting or other tweaks within the kernel. If you are on stock ROM with stock kernel the only option is bad battery or hardware issue. Try factory resetting your phone if this doesn't work it is likely to be a hardware issue
Hi, Since i updated to android 6.0 I have been experiencing alot of issues. My phone recently started to turn off for no reason for every Rom I install. I cant use it for 10 minutes for it to turn off. Sometimes I must try like 5 times for it to boot. Is there anything I can do about it? Im just thinking I should throw it to garbage and get the S7?
Thanks
Does the same thing on a stock ROM? Possible battery problem?
audit13 said:
Does the same thing on a stock ROM? Possible battery problem?
Click to expand...
Click to collapse
I am trying to install the stock rom right now but during installation it shuts down randomly. I have tried another battery and it still does the same thing so I think the battery is not the problem.
Also wanted to say that I dropped the phone few times without any screen damage. Maybe that caused a hardware problem?
EDIT: I successfully installed the stock rom. I will let you know if it runs smooth now, thanks!
It seems that my power button has a problem, every time I press it, sometimes it opens the menu where you can select if you want to reboot/turn off/vibrate and the phone turns off.
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.
Hi guys. A relative asked me if i can repair his note 2. I think his network was locked and the phone keeps restarting everytime. I flashed a new firmware on the phone. The one I use on mine..XXUFNG1, and also I went into recovery and clear data and cache after flashing. But still the phone keeps rebooting everytime. Why is that and how can I fix this?
Note : It's not bootloop or anything. You can switch on the phone, use it for like 5mins and then it freezes and restarts itself. And it goes on like that. Sometimes it doesn't restart also and you can use for more. But most of the time after 5mins, it restarts.
naeem86 said:
Hi guys. A relative asked me if i can repair his note 2. I think his network was locked and the phone keeps restarting everytime. I flashed a new firmware on the phone. The one I use on mine..XXUFNG1, and also I went into recovery and clear data and cache after flashing. But still the phone keeps rebooting everytime. Why is that and how can I fix this?
Note : It's not bootloop or anything. You can switch on the phone, use it for like 5mins and then it freezes and restarts itself. And it goes on like that. Sometimes it doesn't restart also and you can use for more. But most of the time after 5mins, it restarts.
Click to expand...
Click to collapse
ROM?kernel?
hishamnoobie said:
ROM?kernel?
Click to expand...
Click to collapse
Everything stock..like I said! Before flashing to the newest rom too, everything was stock.
Was the phone dropped or exposed to moisture? Possible battery problem? Reboots even when connected to a charger?
audit13 said:
Was the phone dropped or exposed to moisture? Possible battery problem? Reboots even when connected to a charger?
Click to expand...
Click to collapse
Hi..thanks for reply. I tried another battery in it. The one I use myself. But it still restarts. I don't know if the phone was dropped or anything though. The relative just told me that it needs to be unlocked. Do you think it's software related? Or something is damaged in the phone?
Since it is running a stock ROM and still behaves this way after a factory reset, I think there is a hardware problem.
I might have a similar problem. I copy from another thread:
Hey guys,
I like this rom so far. But since 2 weeks I got an issue.
My phone randomly turns off, atleast I guess that's what happens. Sometimes the "notify" LED is on permanently but the display won't go on. To start the phone again I have to put out the battery and put it back in.
My battery is randomly empty pretty fast even if I just let the phone turned off. This happens like every 5 minutes.
I already bought a new battery but the problem hasn't changed.
What to do now? :>
Click to expand...
Click to collapse
I like the phone. It's over 5 years old and runs like the first day. Except it DOESN'T wake up anymore after a short time when the screen is off. I can press the power/home button as many times as I want and wait for 5 minutes, screen will still be off. Only way to "wake" it up again is to put the battery out and in again.
Currently I don't have enough money to buy a new phone and I can get a new motherboard for 25$. But I'm not sure if this will fix my problem.
I'm not even sure if this is the ROMs problem since it worked with all earlier versions of this rom perfectly and even the latest release worked for weeks/months.
Click to expand...
Click to collapse
As long as I leave the screen turned on the display/phone won't go off and I can use it as always. Even the battery don't drop drastically then.
It might be exposed to moisture tho. When I take a hot shower I'll leave it on the window sill and the room gets steamy.
ROM: [7.1.2 r24] LineageOS for N7100 [Unofficial] - Version from 08.10.2017
GAPPS: Open Gapps ARM 7.1 Aroma - 03.05.2017
Baseband: N7100XXUFND3
Ril and other stuff I don't know where to check.
Some years ago I had the SDS and the motherboard was changed without the EMMC bug.
Sometimes my phone only charges in slow mode too.
I try a clean install and newer pico gapps now. Maybe it will solve the problem. I'll reply then if it worked or not.
[EDIT]
Since my phone was low on battery I turned it off completly and put it on the charger. After an hour or so I wanted to look after it.
The green charging light stays on and if I want to turn the phone on nothing happens. The light stays on even after removing the charger.
Seems like a hardware, not a rom problem? Will changing the motherboard fix this?
[EDIT 2]
Quick update. I fully wiped/factory resetted and clean installed newest version of this ROM + newest mini pico GApps. Still the same problem. Gonna try it with another ROM/kernel now and if the problem persists it's a hardware fault.
[EDIT 3]
Fully wiped again and changed ROM+Kernel. Still the same problem.