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.
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.
So, lately my phone has been acting kinda weird.. Basically, it'll shut off on it's own, no matter what my battery level or if I'm on the charger, its pretty random. When I go to turn it on, it shows me the samsung logo and shuts off after about 3 seconds of the galaxy s3 logo. It does the same in download mode and recovery. The phone will stay off and do that for an hour or more, and then itll turn on and be all dandy again for hours or at least another day. I'm going to take off all my pictures on the sdcard and odin back to stock as soon as possible for warranty, but does this sound like a hardware failure or software? I read about the s3 sudden death syndrome, but this one isnt permanent. Any ideas?
I agree with your assessments.
I'd wonder about overheating or a bad battery.
Sent from my SGH-T999 using xda app-developers app
what's your setup as of right now?
Beware if it shuts down when your flashing back to stock in the middle of the process it may never turn back on.
Sent From My Galaxy S3 Boricua 100%
It might be the kernel that came with the ROM you installed. I used to have problem with ktoon kernel.
I'm running Darthstalker XI, the problem happened with both the stock kernel and the faux samsung kernel. The battery is fine, its completely flat with no bumps or humps. I managed to turn it on once yesterday but as I was getting ready to transfer over the files the phone shut off and didn't start again. I'll try to get it running tomorrow.
EDIT: Now that I think about it, the problem happened when I dirty flashed XI over X. Afterwards I did a wipe and clean install of X1 and the problem persisted. Has anyone else on Darthstalker/UDVLJA based roms had this?
EDIT2: Well after being on the charger all day, I noticed that the green samsung battery icon was on the screen, something it only does when it's about to turn on properly. I instantly pulled out the sdcard and put the latest cm10 nightly and gapps on there and I booted to recovery, wiped, and flashed them right up, no issues. I booted just fine, I signed up and I was downloading youtube, latest now updates etc (bare essentials).... and it shut off again. I'm positive now that it's a hardware failure
mejorguille said:
I'm running Darthstalker XI, the problem happened with both the stock kernel and the faux samsung kernel. The battery is fine, its completely flat with no bumps or humps. I managed to turn it on once yesterday but as I was getting ready to transfer over the files the phone shut off and didn't start again. I'll try to get it running tomorrow.
EDIT: Now that I think about it, the problem happened when I dirty flashed XI over X. Afterwards I did a wipe and clean install of X1 and the problem persisted. Has anyone else on Darthstalker/UDVLJA based roms had this?
EDIT2: Well after being on the charger all day, I noticed that the green samsung battery icon was on the screen, something it only does when it's about to turn on properly. I instantly pulled out the sdcard and put the latest cm10 nightly and gapps on there and I booted to recovery, wiped, and flashed them right up, no issues. I booted just fine, I signed up and I was downloading youtube, latest now updates etc (bare essentials).... and it shut off again. I'm positive now that it's a hardware failure
Click to expand...
Click to collapse
If you have an app that controls kernel voltage that is still set up for set on boot and the voltage is too low when it boots or is granted root it'll kill it in this manner. Otherwise your phone is [email protected]#
Sent from my SGH-T999 infected with AnthraX using Tapatalk 2
I'd wager that if any overclocking/undervolting was done, it was disabled at the onset of problems. OP seems smarter than orangutan.
I used the phone for work, not play, no overclocking was done neither was any undervolting. I ran stock kernel settings.
Aerowinder said:
I'd wager that if any overclocking/undervolting was done, it was disabled at the onset of problems. OP seems smarter than orangutan.
Click to expand...
Click to collapse
I remember a time when XDA had helpful answers and users weren't reduced to insults. I've been around a couple years, hacked more phones than I can count and flashed hundreds of roms in my days, back when everything was still done in adb and terminal emulator. It's no wonder a lot of decent user has started moving over to rootzwiki
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.
I got my S3 last July and rooted it and installed a rom the first day. I've had zero issues with it so far outside of the occasional freeze or reboot. I've pretty much only run Task's AOKP rom. I do not think my problem is rom or kernel related whatsoever, but it seems more like some type of hardware issue.
Anyway, two days ago I was running the 4-26 version of Task's rom with the stock kernel. I did a full wipe and clean install. The phone had been running trouble free with no issues for a couple of days. Suddenly with around 75% battery, it just rebooted when I turned the screen on but kept failing and starting again at the Samsung screen or sometimes made it to the underwear kernel screen. I tried to go into recovery and it started into recovery for about a second and went into reboot again. Tried download mode and it went right in and then rebooted after a second or two. It will not stay in any mode for longer than a second or two. I've tried connecting it to the pc and put it into dl mode and it does the same. I have a usb jig and it puts into download but only for a second or two.
I'm sure I'm missing something, but any help would be appreciated.
double RL said:
I got my S3 last July and rooted it and installed a rom the first day. I've had zero issues with it so far outside of the occasional freeze or reboot. I've pretty much only run Task's AOKP rom. I do not think my problem is rom or kernel related whatsoever, but it seems more like some type of hardware issue.
Anyway, two days ago I was running the 4-26 version of Task's rom with the stock kernel. I did a full wipe and clean install. The phone had been running trouble free with no issues for a couple of days. Suddenly with around 75% battery, it just rebooted when I turned the screen on but kept failing and starting again at the Samsung screen or sometimes made it to the underwear kernel screen. I tried to go into recovery and it started into recovery for about a second and went into reboot again. Tried download mode and it went right in and then rebooted after a second or two. It will not stay in any mode for longer than a second or two. I've tried connecting it to the pc and put it into dl mode and it does the same. I have a usb jig and it puts into download but only for a second or two.
I'm sure I'm missing something, but any help would be appreciated.
Click to expand...
Click to collapse
Check the bad power button or bad battery.
tomy1986.nt said:
Check the bad power button or bad battery.
Click to expand...
Click to collapse
Good suggestion on the power button. Would make sense, but it seems to be fine feels exactly like it should. I took it apart and even left the button off. The part of it that's attached to the motherboard is very crisp and pops right back after pushing it in. Doesn't seem to be the problem. I've tried three different batteries with the same results. Guess I'm going to the service center tomorrow. Damn
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.