Been using Lineage OS for a few months and phone was running smooth and battery still strong.
Never had any unusual crashes etc, and gave me no need to upgrade.
Yesterday it would no longer turn on and trying to hard/soft reset only had the 1st RED LED blink occasionally.
Battery is at 3.75V and appears fine with no past problems.
Tried with power cord, left battery out over night but still no boot.
Took to a legit repair shop and they said if it doesn't boot they can't diagnose etc...
Is it time to finally replace the Note II? Doesn't have a scratch on it and always taken care of.
Only reason for Lineage OS was that a few apps no longer worked with the last Note II Android OS 4.1?
Any help is very much appreciated.
Related
Hi everyone...hope i have posted this in the right place.
I have a GALAXY note 2 ...uk version which is rooted running tigra rom.
All was fine with it until yesterday, my battery was running low so decided to put it on charge. noticed that it didnt recognise the charger. It now has dead battery and will not charge.
When i plug in the charger, i the grey battery icon with the circle in it. then it goes to the battery icon with the green line at the bottom of the battery like its going to charge, but the just goes off and nothing.
Weird thing is that i can get to my recovery screen and can go through my options on there for however long i want to.
thought it may have been a rom issue, so tried putting another one on it, but just installs to 20% then goes off...
so tried resetting, tried to install new rom. tried holding volume up, home and power keys...etc...
HELP WOULD BE GREATTTT....PLEASE...:crying:
Just had the same problem, samsung sucks
Can anybody suggest any solution?
Just had the same problem..gonna het a new battery..hope it will work...
Hello, I repair phones for a living, and ive been troubled with this for a few days, I did some research and found the S2 had similar problems. I took the note 2 im having the charging issues with and compared to a working board and found the problem quickly. I tried replacing the charging port many times and still had same results, also tried flashing roms.
This is what i came up with, check and see if you have a damaged chip on the board above the charging ribbon connector. I have included pictures to help you locate the issue.
Hi!
A little back story, I lost my IMEI a few months ago, Samsung couldn't fix it so I continued to use it as a wifi only device for a couple months.
Fast forward to 3 days ago, I found someone who would repair it, and I can now make calls and so on. I assume they reflashed/formatted my phone, since I lost root, (but an icon with SuperSU was still there, but not with the usual icon).I factory reset my phone after the repair as well
Last evening, I had my phone in my bag for a couple of hours, and later found the device extremely hot, and it was stuck at the pulsing Samsung logo with the led on a solid blue.
This evening, I found the phone the same way, except that I hadn't used it for a half hour. And I don't think the blue led was on.
I'm on stock 4.4.2, not rooted (For fear of losing my IMEI again)
Would be grateful for any help, thanks!
So my wife's Note 4 is on the latest 5.0.1 update from Verizon, and lately has developed a strange issue. Anywhere between 0-30% battery life left, it will go into a reboot loop. If you let it reboot over and over long enough, the Verizon screen gets shorter and shorter every time, before it finally gets to a black screen with small red text in the top left that reads "Secure fail: modem" and a large yellow exclamation point in the center, and instructs to use "VZW Software Upgrade Assistant" to fix the issue.
But even more strange, is once she plugs it into a power source, she is able to boot it up fine with no issues until the next night the same scenario happens all over again. She's never modified any software, attempted to use temp root methods, etc. and has always run stock OTA updates. She has also tried factory resets and the issue returns a few days later.
tl;dr Random reboot loop every day, eventually leading to "Secure Fail: modem" screen until plugged into power, then boots/runs fine until next day.
Any ideas of what could be going in is greatly appreciated!
My note 4 had the same problem. Battery would get to 30% die, and reboot constantly. I bought a new battery but it made the phone do the opposite then. Now it will on charge up to 65% and no more. But, it will reach 0% before it actually die. It is a glitch in 5.0.1 that affects several galaxy phones. The sad thing is that it is NOT the latest update. Currently 5.1.1 is, and Verizon refuses to release that for unknown reasons. Sprint is the only carrier that pushed 5.1.1 after these problems started. Other problems are the note 4 crashing, battery drains, overheating, poor processing, restarting out of no where, slow, and app crashing. I myself, is unhappy with the note 4 and I am most likely going to go with a different phone. (which is sad because my note 2 was just awesome.)
Verizon is going straight to 6.0 because of all the bugs even with 5.1.1. Good move on their part I think.
Sent from my Samsung Galaxy Note 4 using Tapatalk
I'm having the same problem. mine starts anywhere from 40-50% battery life, will reboot till phone is dead. As soon as I plug in the charger it will start charging the battery at what ever % was left.
My phone went into a reboot loop this morning after a full charge for the first time. It has never done this before andI tried to stop the reboot loop by entering bootloader/safe mode screen and I did "reboot" but my phone went dark and has not responded since. I believe it is bricked. Anyone have any ideas?
new battery fixed my problem
had same problem new battery fixed it
New battery fixed for me too.
Sent from my SM-N910V using Tapatalk
I'm running into the same boot loop issue and I see that basically 5.0.1 caused it and 5.1.1 has fixed it... And the only fix is a new battery... Anyone try getting Verizon or Samsung to go good for a new battery since it was their software that damaged it?
Just as it says in the title i am experiencing horrible battery performance on my HTC ONE (M8) ever since i rooted and custom rommed my phone along with other small bugs i noticed. I am currently running the latest DIRTY UNICORNS for the android 6.0 update. Though this was not my first ROM used. Not i will get out of the way that my charging port is very poor quality due to being abused for a while. (Laying in bed with the charging cable and port recieving light pressure while i browse pictures for hours on end.) Anyways. I was charging my phone it being at 34% yesterday and i made sure not to touch it and the little charging light was on indicating charge the entire time while the phone was TURNED OFF. Now at this time I had finished trying out a dozen different roms and was full charging the phone. When i picked up the device about an hour and a half later expecting a full charge it you wont believe me. The phone displayed 17% and was still charging. I was shocked. I figured it was some fluke and left it to charge more. After all i'd installed roms and maybe it'd affected the % reading. I went to pick it up later and the phone was fully dead. but the indicator said 0% and was charging. Now i knew 2 days ago my battery was pristine before rooting my device and before trying out roms. Is it possible i tried a dirty rom that hijacked my phone while it was "Off" ? I have no clue. I know my battery was pristine because on a 1.5A plug my phone would 0-100 in under 2 hours. This is the most of the information i have for you. Again i have no idea what's causing this issue.
Another issue i am having is since i rooted and tried custom roms my LED light on the front of my phone got IIIINNNNCCRREEEdibly dim. It has to be pitch black for you to even see the glow from it. Along with the issue stated above my phone cant seem to charge more than about 35%~ and it takes so long per % i swear i could leave it plugged in WHILE TURNED OFF and it would never reach 100% until the day i keel over and die. Note all battery tests were while the phone was off. Whenever i turn the phone on the % is always different from the on screen while off. (it use to be the same, maybe the ROM messes with that?) Any advice or assistance is greatly appreciated. I already am saving up for maintenance on the charging port.
An additional issue I am facing is the fact even with minimalist android 6.0 my HTC ONE M8 is incredibly slow. As in there is absolutely no apps running or installed with this test. But i tried 1 single game and while on a normal HTC update for 6.0 and the game ran smooth with no lag. So what gives? I thought a minimalist android rom would give my phone a power boost with all the bloatware and applications removed.
I began typing this message at 5:45pm MST my time. It's now 5:55pm MST and my phone managed to go from 0%-2%. Now obviosuly anyone whos owned an HTC ONE M8 on the correct charger this thing really charges so what gives?
Yes i am making sure the ROMS i used were compatible with my HTC being on the carier of AT&T. Any and all assistance in my troubles is greatly greatly appreciated. I really hope you can help me with my issue.
**Edit:: Also my Megabits Per Second on wifi greatly decreased. I on the regular android 6.0 by HTC for AT&T was getting 250-300 Mbps. Now i get 130-180. If there's a comment or fix for this i'd also like to know.
****Secondary Edit: When i installed the A ROM(unknown i tried too many) a while back my phone freaked out on install and the charging animation on the front of my phone went from the normal android 6.0 to the old old HTC charging animation for android 4.4. When the phone goes to display charging it shows that new charging icon with the ghastly red text on bottom from rooting/ROMS(You know what i mean haha) and then it switched to an animation of old. Idk how a rom might have changed this i did not.
Hello, I'm new to the forum and I may need your help for a problem I've had today. I've been an happy owner of a Nexus 5X until this morning, when I was regularly using it while on charge and at one point it freezed for a few seconds with the screen still on. I pushed the standby button, the screen went off and from then on it was completely bricked. No signs of life, nor access to recovery mode via bootloader. Nothing. Already tried all the possible physical buttons combos, nothing.
It was on Android 8.1 (beta, very happy about that by the way), no root and with locked bootloader. I did some flashing experiments one year ago but in the end I reverted it back to totally stock and I haven't had issues ever since. Never had bootloops or similar problems, it just happened all of a sudden.
Hope to receive your help, by the way it should still be under warranty, so let's see...
Thanks for your help.
Same problem heare. I tried to install the factory image but now, the phone is completely death.
I beleve thet it was a android 8.1 issue because it was not a bootloop problem.
Same problem heare. 8.1 need a reboot but now, the phone is completely death
It might be an 8.1 issue then. By the way, being under warranty I sent it to customer assistance. I've had some signals of life before this morning though. The LED was flashing red indicating very low battery. I connected it to the charger and followed the instructions by Google themselves:
"If you see a red light, your battery is fully discharged. If the red light is flashing, there isn't enough power to turn on. Charge your phone for at least 30 minutes before restarting".
This seemed to resemble my case, so I waited for about 40 minutes (by that time the charging battery icon did show up with the phone still off) and tried to turn on. The only thing that I got has been the Google logo before the boot animation for a few seconds. Then the screen has gone off again and back to death.
From your comments it seems it might be an 8.1 related issue. Watching videos on Youtube about 5Xes with similar behaviours I was actually thinking about a motherboard failure, or a battery failure (the latter is more unlikely though). Disassembling and heating up the motherboard providing a temperature shock seemed to be a decent temporary solution to bring it back to life. I have warranty though so I sent it to assistance, we'll see... I'll probably unenroll my phone from the beta program just to stay safe.
Thanks for your answers.
My nexus 5x had same issue. A few weeks after 8.1, it totally bricked. I was able to get bootloader on once, but it was locked and fastboot didn't see it. Then after i let it discharge, I haven't been able to get it to recharge or get to boot screen at all. I bought another nexus 5x, but bit worried that 8.1 will kill it.