Develop Bugs

Not charging, screen flickering

I bought a note 10.1 2014 Ed a couple of weeks ago on eBay. Not refurb and sealed in the box.
Devastated to find tonight, after completely discharged and shut down, that it seemed not to charge at all.
It becomes stuck on either the battery symbol, where nothing happens, arrow doesn't spin and no animation, or goes to the device model name. All the while the brightness flickers.
Have tried various chargers, I've taken all the cards out but nothing is working
I think it may be a loose connection with the battery (but open to other theories).
If anyone has had this problem, how have you fixed it? Is it worth disassembling and trying to fix it myself (as I'm sure you can tell I don't have a lot of knowledge about this)? Being an eBay purchase is it still under warranty with Samsung? How much would a fix be if it was a loose battery?
Thanks in advance

shining08 said:
I bought a note 10.1 2014 Ed a couple of weeks ago on eBay. Not refurb and sealed in the box.
Devastated to find tonight, after completely discharged and shut down, that it seemed not to charge at all.
It becomes stuck on either the battery symbol, where nothing happens, arrow doesn't spin and no animation, or goes to the device model name. All the while the brightness flickers.
Have tried various chargers, I've taken all the cards out but nothing is working
I think it may be a loose connection with the battery (but open to other theories).
If anyone has had this problem, how have you fixed it? Is it worth disassembling and trying to fix it myself (as I'm sure you can tell I don't have a lot of knowledge about this)? Being an eBay purchase is it still under warranty with Samsung? How much would a fix be if it was a loose battery?
Thanks in advance
Click to expand...
Click to collapse
As far as I am aware items from ebay are not covered under warrenty.
Even with the screen off and nothing happening, leave it on charge for few hours then unplug and try to put it on.
Also have a look into the charger port of the tablet at the bottom to make sure nothing looks bent or out of the ordinary.
Sent from Galaxy Note 10.1 2014 Edition via Tapatalk.

samsung sm-p605 dead not starting
havig the same error mentioned above.. got the device new from amazon, shipped to chile where i live.. recieved it and tried switching on and didnt switch on.. tried connecting wall charger for couple of hours no progress not even battery symbol coming up.. tried usb to laptop battery image comes up with no animation.. and screen flickers... boots in odin mode... when tried booting in recovery mode stucks in screen where the model name appears...
plz help since i have 0 hrs of usage completely new.. chile samsung doesn't accept becos its purchased in usa.. any email of samsung will also help
shame i always liked samsung over apple.. and bought a product with no support.. apple atleast accepts product bought anywhere in the world and even replaced battery for my frnds iphone 5s when in warranty...

I have not had this issue with my Note, but my Nook did the same thing once. I disconnected the battery for a few minutes and everything reset. No idea if this will help, or if you are adventurous enough to try it.
Here are some pictures of the Note tear down. http://forum.xda-developers.com/showthread.php?p=49595697

samsung sm-p605 dead not starting, screen flickers
i am going to try removing the battery as u said.. lets see..
anyother ideas plz let me know..
but shld i do this quite often?? is this an known error of note???.. do we have this problem when complety drained????

samsung sm-p605 dead not starting, screen flickers
no luck.. i removed the battery from the board, then plugged in back after couple of minutes..
still in same state..
the screen flickers a lot.. is that normal when the note is completely drained..???

It is very bad for the battery to go completely down. I don't let it happen on my devices, so I cannot say if the flicker is normal.
My experience with the Nook was actually a friend's device. He had let it run down, and it was not charging. He left it on the charger for a few days, and it was still not showing a charge. He gave it to me to check out. I disconnected and reconnected the battery. It was probably half an hour or so, because I was interrupted. When I reconnected the battery, the Nook popped on and reported a full battery. Apparently it was charging but not registering anything, and the disconnect allowed things to reset.
If you do not any other ideas, I would suggest leaving on the charger overnight (or longer) and trying the disconnect again. Maybe leave it disconnected longer too.

shining08 said:
I bought a note 10.1 2014 Ed a couple of weeks ago on eBay. Not refurb and sealed in the box.
Devastated to find tonight, after completely discharged and shut down, that it seemed not to charge at all.
It becomes stuck on either the battery symbol, where nothing happens, arrow doesn't spin and no animation, or goes to the device model name. All the while the brightness flickers.
Have tried various chargers, I've taken all the cards out but nothing is working
I think it may be a loose connection with the battery (but open to other theories).
If anyone has had this problem, how have you fixed it? Is it worth disassembling and trying to fix it myself (as I'm sure you can tell I don't have a lot of knowledge about this)? Being an eBay purchase is it still under warranty with Samsung? How much would a fix be if it was a loose battery?
Thanks in advance
Click to expand...
Click to collapse
I have the same exact issue right now! But mine is a refurbished unit. I tried the battery unplug, tried leaving it charging overnight, letting it discharge, flashing new roms, new kernels, etc. Nothing. THe only thing that did work a little bit was changing the kernel. Other than that, even flashing stock ODIN roms wasn't working.
When you charge yours, does it charge up to 75% but won't go any further? And does it take an extremely long time to get there? Because mine does. Reading about other devices that have the same issue, it seems to be the battery. But the other devices were phones. This is a tablet. The battery costs $65 :/

shining08 said:
I bought a note 10.1 2014 Ed a couple of weeks ago on eBay. Not refurb and sealed in the box.
Devastated to find tonight, after completely discharged and shut down, that it seemed not to charge at all.
It becomes stuck on either the battery symbol, where nothing happens, arrow doesn't spin and no animation, or goes to the device model name. All the while the brightness flickers.
Have tried various chargers, I've taken all the cards out but nothing is working
I think it may be a loose connection with the battery (but open to other theories).
If anyone has had this problem, how have you fixed it? Is it worth disassembling and trying to fix it myself (as I'm sure you can tell I don't have a lot of knowledge about this)? Being an eBay purchase is it still under warranty with Samsung? How much would a fix be if it was a loose battery?
Thanks in advance
Click to expand...
Click to collapse
I know this is a very late reply and you have probably solved your problem by now, but for future readers with this problem:
I currently have the exact same problem, and just found out what it was. Either my charging cable (official Samsung cable) is faulty. I plugged it into another microUSB cable, and it is now charging again. No more battery symbol that doesn't have the spinning animation or flickering, and now it turns on.

StandardLeopard said:
I know this is a very late reply and you have probably solved your problem by now, but for future readers with this problem:
I currently have the exact same problem, and just found out what it was. Either my charging cable (official Samsung cable) is faulty. I plugged it into another microUSB cable, and it is now charging again. No more battery symbol that doesn't have the spinning animation or flickering, and now it turns on.
Click to expand...
Click to collapse
Thanks for this information. Exactly this was the issue. Great!

Charging works and screen stops flickering with Samsung charger if you let it charge in Recovery mode. Mine is still charging as of now, so I don't have any news further yet, but it went from 0% -> 3% after around 30min.
Other than that, I only managed to get charging working with a Motorola's turbo charger.

Hardware issue with battery, crashing, rebooting, powering off

I just bought a used SM-T800. I didn't see any immediate issues but I've noticed it has been intermittently powering off or rebooting on it's own. These aren't graceful shutdowns, it powers off immediately, either when I'm using it or I'm not touching it. It can even happen while the battery is supposedly full and the charger is plugged in. This can happen many times in a row, a lot of times during the bootup process. If I leave the cable unplugged I've noticed if it finishes booting the battery can sometimes claim to be almost dead at like 3% when I thought it was 100% full.
I've done a bit of searching and saw a reference to an issue with a cracked interface to the battery. Is there a known issue with this device regarding this? Any detailed links on this? My alternative was to buy and replace the battery. Anyone else having the same issue?

ccoager said:
I just bought a used SM-T800. I didn't see any immediate issues but I've noticed it has been intermittently powering off or rebooting on it's own. These aren't graceful shutdowns, it powers off immediately, either when I'm using it or I'm not touching it. It can even happen while the battery is supposedly full and the charger is plugged in. This can happen many times in a row, a lot of times during the bootup process. If I leave the cable unplugged I've noticed if it finishes booting the battery can sometimes claim to be almost dead at like 3% when I thought it was 100% full.
I've done a bit of searching and saw a reference to an issue with a cracked interface to the battery. Is there a known issue with this device regarding this? Any detailed links on this? My alternative was to buy and replace the battery. Anyone else having the same issue?
Click to expand...
Click to collapse
HI Dude
I have experienced the same thing with my SM-T705 except before shutting down i see green flickering lines for a very short peroid of time.....how about you????

rewa99 said:
HI Dude
I have experienced the same thing with my SM-T705 except before shutting down i see green flickering lines for a very short peroid of time.....how about you????
Click to expand...
Click to collapse
Yes, I've seen that happen with the video glitching but it doesn't happen all the time.
Currently my device won't boot up anymore. Even with the device plugged in, the surge of power it needs to boot up isn't available from the battery.

ccoager said:
Yes, I've seen that happen with the video glitching but it doesn't happen all the time.
Currently my device won't boot up anymore. Even with the device plugged in, the surge of power it needs to boot up isn't available from the battery.
Click to expand...
Click to collapse
As was mine a couple weeks ago, i tried everything...rooting flashing re partitioning, you name it, i did it. NOTHING WORKED!!
Until 2 days ago i opened up the back and noticed that the piece where the battery wire connects to the motherboard was loose i simply placed some foil above it and closed it up again( the foil put pressure on the connection which allowed it to carry power across). And now everything works fine, while its not a permanent solution(ill take it to samsung sometime later this month) it does work and now my tab is fully functional. While i dont know your situation this worked for me so maybe it will work for you...Let me know how it goes!!!!!

[Q] SM-P600 weird (battery?) issue

This past week, I purchased a 2014 Note 10.1 off Craigslist. I did check it out before buying it, and the device is in pristine condition, including the screen. It booted fine, and I went partway through the setup (the guy had factory reset it) before closing the deal. It is the wifi-only model, 3G RAM, 8-core Exynos version. It's white if that matters.
Anyways, a while later when playing with it some more, completing setup, etc, it just died on me. I wasn't home, and didn't have a place to charge it until I got home, but just figured that despite the device having said the battery was 99% charged, the guy keeping it unused for a long time might have thrown off the battery calibration. My understanding is that a Li-ion battery has one or more cells, plus circuitry that protects against overcharging and undervoltage conditions, as well as tracking the current charge state. With lengthy non-usage, the circuitry's idea of the current charge can get out of sync with reality, so I figured a few charge-discharge cycles would get it back in shape.
However, the situation after I got home turned out to be a little more complex. If I plug in the device to a power source with enough current (like the charger it came with, or my 2.1A USB outlet by my bed), it will run just fine while plugged in. However, upon unplugging, it would die quickly. Naturally, I assumed the battery was probably shot, so resigned myself to spending $50 on one. This is where it started to get a little weird. It seemed that when I booted into either fastboot or Odin mode, it would stay on much longer than normal, while unplugged. I'm talking hours, rather than between several seconds and several minutes while booted into the OS proper.
This lead me to believe that perhaps it wasn't my battery itself, but rather a glitch in the OS that was causing it to shut down. When I say shut down, I mean an immediate full-off state, not a nice shutdown or one preceded by low battery warnings. It just clicks off like a light that's been turned off. However, trying several different firmwares, including a couple custom ones, has not yielded any improvement. The issue remains.
The device was stock 5.1.1 when I bought it. I tried flashing KitKat (various images downloaded from SamMobile), but for some reason, it would still say it was running 5.1.1. I tried xKat, as in this thread. That results in 4.4.2 with the associated customizations, but the shutdown issue remains. I tried CyanogenMod 13, as instructed here. It works fine, notwithstanding the same issue. In between the stock firmwares (pushed to the device with Odin) and the custom ones, I would do a full wipe through TWRP.
I've popped the back off, disconnected the battery, waited a bit, and reconnected it.
Now my question: does anyone have any idea what's going on? If it's a dying battery, then why does the device say it's got a nearly full charge, and why no low battery warnings? Why would Odin mode or recovery (TWRP now) seem to keep the device powered up so much longer? Sure, they draw less power, but hundreds of times less power? I doubt it. If it's some hardware issue with the chipset/motherboard/etc, then why does it only manifest when running on battery, or a low-current USB connection? If it's an issue with Android itself, then why does nobody else seem to have this issue (googling revealed nothing that matched my symptoms), and why did several different versions exhibit the exact same problem?
I really don't want to spend money on a new battery and wait a few weeks for shipping if there's something else I'm missing that could get my device functional for free and a lot faster.

My tablet had a similar issue, in that when you would get to the 15% mark, I had maybe 3-5 minutes before it would get to 0% and abruptly turn off. I used the battery calibrator app for rooted devices, followed the instructions, and now all is good again. For me, I noticed a variance from what the OS was reporting and twrp was showing in between flashing. For what its worth, I'm on the KitKat bootloader, and haven't used an official Samsung firmware since KitKat. Oddly enough, the battery calibration having been off survived through lollipop and into marshmallow. Hopefully you can get your tablet back on track.
Sent from my SM-P600 using XDA Premium HD app

Thanks for your reply.
siralsmooth said:
My tablet had a similar issue, in that when you would get to the 15% mark, I had maybe 3-5 minutes before it would get to 0% and abruptly turn off.
Click to expand...
Click to collapse
That's a bit different from my issue. Even when the device reports full charge, if I unplug it, it usually dies within seconds, and always within 2-3 minutes.
siralsmooth said:
I used the battery calibrator app for rooted devices, followed the instructions, and now all is good again.
Click to expand...
Click to collapse
I don't think that's going to make a difference for me. From what I was reading, all it does is delete the batterystats.bin file (hence the root requirement), which doesn't have anything to do with calibration for most devices. It just contains the stats for how much battery drain various things have caused, during this 'running on battery power' session. It's also reset every time the device is charged. Read here for more info.
Furthermore, even if this were not the case, I'd conclude that wiping the system partition (indeed, all partitions except recovery) would have cleared this data.
Still, that said, it's conceivable (though exceedingly unlikely) that some of these calibration apps might do something else, such as talk to the battery circuitry at a low level. Since I've got nothing to lose, I will probably give a few of them a shot. Do you happen to know which one it was that you tried?
siralsmooth said:
For me, I noticed a variance from what the OS was reporting and twrp was showing in between flashing.
Click to expand...
Click to collapse
In my case, the values seemed to track pretty closely, and with numerous freshly-flashed versions exhibiting the same issue, I'm pretty sure at this point it's not a software glitch. I've resigned myself to ordering a new battery. I just wish I was certain that it would fix the issue.
siralsmooth said:
For what its worth, I'm on the KitKat bootloader, and haven't used an official Samsung firmware since KitKat. Oddly enough, the battery calibration having been off survived through lollipop and into marshmallow. Hopefully you can get your tablet back on track.
Click to expand...
Click to collapse
My understanding is that the bootloader doesn't change with flashing. I might be wrong though; is there a way to check the version?

Just a heads up. I ordered a new battery, which arrived yesterday. It seems to have completely solved the issues I was having.
My guess is that Android itself monitors the battery more diligently, and takes a more conservative approach to preserving battery life by shutting down when the voltage drops too low, while recovery mode would just let it run down completely flat (not good for Li-ion cells).
It's a moot point now, because it all seems good.

Battery replaced, now won't stay on due to temperature.

Hi all,
I have been running my Z1 Compact on 4.4.4 for the longest time, mainly due to sound issues after updating to Lollipop.
Recently, the battery has been dropping randomly from 60 odd percent to 3 or 4 and then shutting down all within a few seconds. The last time it did this, I tried charging it when I got home but the charging light would not stay on, thus it was not charging. All typical signs of battery failure due to age.
Having already replaced the battery successfully on my Z1, I bought a replacement original Sony battery and replaced it. The problem persisted. On first boot, the phone got to the blue waves then black screen, and power off. Charging screen just showed the battery at about 40%.
I risked it and flashed the latest software with Flashtool, having done a complete wipe. The result of this proved no better, but I did get a different message on the charging screen, a message saying the phone had shut down due to overheating. Picture is attached.
The phone is in no way overheating and I've even booted it while sat on a shelf in the fridge to help dissipate any heat generated but with no luck.
So, the old battery maybe did overheat and caused the phone to shut down, I'll accept that as a probability. It may have even damaged something, but I don't think that's likely.
After changing the battery, I would have expected the problem to resolve itself, but it seems like some kind of hardware 'flag' has been raised that is now not allowing the phone to boot in case it overheats again.
Does anyone know of any way to resolve this, reset the 'flag' per se, other than going to Sony? The phone is definitely out of warranty due to its age, never mind me taking the back off lol
It is a shame because it has been a great phone over the years, and I would like to fix it if possible, even if to give it to one of the grandkids. I have my Z3 still (which I won't part with for anything) and I have an XZ too and both are great phones. I would just like to save the XZ1c if I can.
The phone is not, and has never been modified in any way, no rooting, no bootloader unlocking. Only stock roms have ever been flashed, and then only once or twice, to put it back on 4.4.4.
I have tried reflashing just the kernel, or just the system too, to no avail.
In desperation I even left it in the fridge for a few hours in case the temperature sensor was on the fritz, but that did nothing at all.
I just feel like there's nothing actually wrong with the phone, apart from this trigger that won't reset.
Any help greatly appreciated of course.
Thanks,
Mick

Maybe theres lot of consideration:
1. Rom Bugs
2. The Kernel not supported well
3. Battery Issues (But you already change it right)

There are two temperature sensors afaikin our phone. One in the SOC and another one in the battery (hence three pins).
The battery is probably the one giving the high temp report. Try yet another battery.
A bad battery normally heats up very fast inside and the battery temp sensor stops the battery from charging and/or working to protect the phone and the battery.
I changed my battery before when it had symptoms like yours 100-90-0 drop and after replacing with a battery from eBay it was OK. I gave it a full charge then complete discharge and then complete charge to full cycle the battery once and let the phone Guage its full capacity. one year later now my battery is acting funny again (not charging past 30%) and getting so hot when charging it triggers overheat control service in Android.

Any luck?
Apologies for the necro. But did you ever fix this issue, having the same problem

Karter Ires said:
Apologies for the necro. But did you ever fix this issue, having the same problem
Click to expand...
Click to collapse
No, I never did figure it out. I've been loathe to spend more money on another battery when I've got other much newer phones. I really have no idea why it would not reset once the battery was replaced, maybe it's the replacement battery.
Have you tried changing the battery?
I've tried flashing different stock roms, Kit Kat, Lollipop, and it doesn't help.
Short of going to Sony, I'm not sure what else to do.

Replaced screen and battery, now in (another) bootloop!

Recently I posted about a problem others had as well - when under 50% ish battery, my HTC 10 would randomly reboot, and that would loop until it was plugged in.
Once plugged in and fully rebooted, the battery % reading would vary from where it was before to 1%. Also, certain apps' data or cache would be deleted. I would open, Macrodroid, for example, and it acts like it's the first time being opened after installation.
This has been exhausting, having to constantly be charging, staying above 60% - and even then it still happening. After it does, the apps whose data was cleared varied, and I wouldn't always know until I opened each.
So after this I dropped it and cracked the screen. I have fixed all of my HTCs before with various problems - M8, M7, DNA, Incredible, Max - so I decided to put in a new battery to hopefully fix the bootloop problem.
After watching a few disassembly videos, it seemed best to replace the screen when I opened it for the battery. So I ordered a screen, and waited more, constantly charging, restoring data to apps like Macrodroid and initializing apps all over again.
I finally have the new battery and screen. I have a few hours. I get out all my tools.
A few hours later, I have put it back together. It's like Medusa inside this thing! I was really being risky doing this last night, because I have a ton of work to do today, yet here I am typing this on my backup nexus 5x - so slow!
So the result? Success for the screen replacement, and the battery as well. But, now, it is bootlooping still! I plug it in, and two things:
Plugging it in does not stop the bootloop.
The charging LED does not light up.
So I am hoping someone may have some insight as to what I may not have connected properly. I can post pictures later, I'm not home right now.
I looked and looked and looked and cannot find where I went wrong. I am going to take it apart and put it back together if I can't find the error. Any ideas? Any other places I should post this?
I guess when I get home, assuming it has completely drained itself, I can plug it in, and see if it gets a charge, and if the LED illuminates. I am thinking: charging port is not properly connected back + the new battery did not fix the bootloop / battery issue.
Thoughts?

Bootloops/shutdowns are going to corrupt your data. I would RUU the thing before looking for hardware trouble, which you've likely sorted out by replacing the battery (of course, we're assuming the new battery is good).
BUT before that, is there a memory test in the bootloader or recovery? If so, I would run that very first thing.

bluedimensional123 said:
Recently I posted about a problem others had as well - when under 50% ish battery, my HTC 10 would randomly reboot, and that would loop until it was plugged in.
Once plugged in and fully rebooted, the battery % reading would vary from where it was before to 1%. Also, certain apps' data or cache would be deleted. I would open, Macrodroid, for example, and it acts like it's the first time being opened after installation.
This has been exhausting, having to constantly be charging, staying above 60% - and even then it still happening. After it does, the apps whose data was cleared varied, and I wouldn't always know until I opened each.
So after this I dropped it and cracked the screen. I have fixed all of my HTCs before with various problems - M8, M7, DNA, Incredible, Max - so I decided to put in a new battery to hopefully fix the bootloop problem.
After watching a few disassembly videos, it seemed best to replace the screen when I opened it for the battery. So I ordered a screen, and waited more, constantly charging, restoring data to apps like Macrodroid and initializing apps all over again.
I finally have the new battery and screen. I have a few hours. I get out all my tools.
A few hours later, I have put it back together. It's like Medusa inside this thing! I was really being risky doing this last night, because I have a ton of work to do today, yet here I am typing this on my backup nexus 5x - so slow!
So the result? Success for the screen replacement, and the battery as well. But, now, it is bootlooping still! I plug it in, and two things:
Plugging it in does not stop the bootloop.
The charging LED does not light up.
So I am hoping someone may have some insight as to what I may not have connected properly. I can post pictures later, I'm not home right now.
I looked and looked and looked and cannot find where I went wrong. I am going to take it apart and put it back together if I can't find the error. Any ideas? Any other places I should post this?
I guess when I get home, assuming it has completely drained itself, I can plug it in, and see if it gets a charge, and if the LED illuminates. I am thinking: charging port is not properly connected back + the new battery did not fix the bootloop / battery issue.
Thoughts?
Click to expand...
Click to collapse
Whatever happened to your phone? I have the exact same problem. Infinite boot loop, no illuminated LED, and no way of getting into recovery or anything else with it bootlooping. It occurred after I made the mistake of trying to restart it at 25%. I have the new battery and screen. i'm going to attempt to open this Pandora's box. Seriously going to have to turn my back on HTC. The 10 is so full of software issue problems regarding the batteries that they never bothered to address.

I did the exact same thing a few days ago and my phone won't charge or boot, but I do think the problem is with the button strip, that's what i think, because i tried turning it on before re assembling it and it did turn on successfully and was charging normally but when i re Assemble it, the phone got this problem, now i think when i turned it on before assembling i pressed the power button with a screw driver because i couldn't press it with my fingers, I think there i messed it up, any advice how to fix the button strip and remove a slip nut would be very much appreciated

I had the exact same issue as you(shutting down at 50%), have you found any solution to it?
edit: I THINK clean flashing oreo firmware then latest RUU then twrp then lineage fixed my issue, charging to full rn will drain it over the next day and report back if its gone for good