D6603 power off at 80%-70% - Xperia Z3 Q&A, Help & Troubleshooting

Hi Guys,
I have a D6603 unrooted, was rooted before.
Installed a clean firmware 5.1.1, was on 6 and 7 before.
My problem is when i charge the phone 100% it just power off at 80% or 70% with a message of low battery went to 0%
When i power it on again, it stay blocked on the sony logo, i need to put the resest button to make works again, when fully powered, it goes off again.
I tough it was a battery problem, of course it is, but not hardware it's software related, Why? this why:
When the phone goes off on 80%, and reboot and stuck on sony logo, i let it like this to see how many hours it would stay.
And yeah, it took 3 hours on this logo screen to goes off, that' mean the battery still have power.
This problem happened to me when i rooted my phone the first time, unlocked bootloader "was never rooted before until i did"
now even with unrooted i still occur this problem.
I need your help guys; i there's any workarround.
Thank you

i made another thing few hours ago, when the phone is fully out of power, i tried to charge it using my laptop usb port.
It was charging great and slowly, until it reach 50% it jumped to 100% directly.

Related

Phone died all of sudden AGAIN?

Not sure if anyone has any new ideas as I've had this happened before and had to get the phone fixed with new motherboard. My phone has been working ok with the official ICS update. It's rooted. Things seem to be a little weird the last few days with the phone hanging and sometimes the screen will just turn into this fuzzy appearance and yesterday while it was just sitting on my desk..it seem to be using a lot of power with the battery going to 4% from 80% in just 3-4 hours idling. IT also got really hot while charging, so i turned it off and rebooted. Thought it was fine.
Then last night, while charging, it seem to be sluggish. so I restarted the phone. But after it turned off..it won't respond anymore. No light when plug in for charging, or plug to computer...cannot go into bootloader with vol down / power.
I had a similar experience before when the phone suddenly died 3 mths ago and thought it was related to a custom ROM, but HTC replaced the motherboard...now it's unresponsive same way.
Time to send back again? Or anyone have new ideas about this?
Take out the battery, put it back in. Try to turn it on. Still nothing? Volume down and power. No bootloader? Sorry, its probably dicked.
There's other things to try, but from what ive gathered, they probably won't help.

[Q] Phone Constantly Turns off

Hi guys,
I recently ran into this problem after I woke one morning to my alarm clock blaring for about half an hour, the phone was pretty hot but not unbearably hot. I took out the battery and left the phone to cool down til trying to boot again, when I did the phone booted fine but it soon shut off again 5-10 seconds into loading into android. I assumed the heat knocked the charge out of the battery / something went wrong with the reading of the battery (as it read like 85%) so I just plugged it into the charger and left til it said it was full. It doesn't shut off by itself and works fine while on the charger regardless. But as soon as I unplug the phone dies within a few seconds. So I turned off the phone and let it charge overnight, woke again to the same issue and the battery reading 85% again. Before I booted back up though I tried the "Wipe Battery Stats" thing in CWM hoping that maybe it would fix it after I fully charged but it made no difference. Also I found that the phone is able to run off the charger when I severely underclock it to 250MHz but obviously it's too damn slow for every day use at that speed. As soon as I clocked it up to 480MHz it had the same issue again. I forgot to mention I was rooted with CWM, unlocked bootloader and on stock rom. After this I decided to revert to my pre-root back up rom from CWM and I still had the same issue.
The final thing that seems to make it work is removing the sim, I tried booting this morning without sim and the phone functions flawlessly even while under a heavy stress test without turning off. So I tried inserting another sim, this one not active. Issues start up again...
Any Ideas guys? Seems to me like if the phone is pulling "too much power" the phone auto shuts itself off. But then the SIM thing perplexes me, not really sure how it all affects.
Lastly, do you think I can still claim on my warranty? I've had this phone for just under a month and it's still in perfect condition... I really don't want to switch back to my chopped and screwed Motorola Flipout. But atleast that thing could handle the overheating pretty damn well. Also I didn't get this on contract I bought it outright from a reseller as a prepaid phone.
In the Netherlands, the warranty for a phone battery is set to six months by law, just contact HTC, and find out.
Sent from my HTC ChaCha with CM9 using XDA app.

[Q] Nexus Fails to Stay Powered in System

Background: I had my completely stock Nexus 5 on the charger for around an hour. When it got near 100%, it locked up for about 5 seconds and powered off. It wouldn't charge or power on again until 2 days later where it would power up but not charge. It could go to the bootloader/recovery but it would still shut down. The charger used won't charge anything anymore, it may have been a power surge that messed it up.
I replaced the battery and the system is still unable to maintain power but recovery and the bootloader are stable (just formatted the cache and the phone did not power off, took around 15 minutes). Now it won't power up again.
Any idea what the issue could be? Could it be corrupted data?
First, try another cable and charger.
Also, make sure you have enough juice on the device first, reflash stock firmware with fastboot and see if the issue remains.
If you successfully flash your stock firmware and use another known working cable and charger and it's the same.... Then unfortunately it could be a hardware issue.
Thanks for the reply.
Unfortunately, that didn't bring my N5 back to life. I'm think a circuit may be fried on the motherboard but I don't have a real way of judging that at the moment.
Any chance you might be able to guess what the hardware issue could be? I'm mainly trying to save the data on my phone and I'm not against taking the phone apart to do that.
Update: I took the phone to a Sprint store and a technician looked at it. When the tech plugged it into the charger, the phone LED was flashing red with no charging screen. It eventually booted up and shut down. Later that day, I could see my notifications (Pushbullet is a wonderful app) and noticed the phone stayed on consistently. He said everything was fine and their formal report didn't mention any sort of damage to the phone that they could find. Later that same day, it died again. Today, I decided to completely wipe and load 5.1 to the phone. It stayed powered on through the whole flashing process (bootloader unlock and individual partition flashes) but shut off during "optimizing apps". Considering it powered off in the system, I'm thinking the issue is with the RAM or the CPU possibly being fried due to a power spike while on the charger. It seems like it only happens during heavy operations.
Something hardware it seems. Not sure what, but if a component on the mb is bad then it is a replacement.
I like the title though, doubt anyone has a device that stays charged while in system. Sorry about your phone, but made me chuckle. I really can't think of a better way to describe it, not trying to pick on you.

Software & Charging Problem

Hi, I have a z3 d6653 my phone was constantly rebooting even though I know its a software thing as it has happened before and by flashing stock lp again it got fixed this time I ignored it and by letting the phone off as it's not my daily driver I wanted to see if itll settle by itself. It did settle and I used the phone till 4% but when i took it back it was off Im sure bc of it starting to reboot again so I wanted to charge it then fix it but after 1% charging it was constantly rebooting in charging mode so with that 1% I thought of booting into recovery and wiping only caches but during the operation it went off and now even though the led is showing like it's charging, it isn't actually so I decided to ask here if any of you can help me i.e know any way how to charge the battery..
Update: I have the back of the phone opened so I thought of unplugging the battery and plug it again but now it's worse not even the red led of charging doesn't turn on, I tried a few fixes but none is working..
Update 2: Like I mentioned I tried many fixes for soft/hard brick and many many others but non worked or at least I had no result but today I thought of charging the battery of my z3 in xperia e4g and after I did so the phone started normally and now its working perfectly, so happy I got it back ^_^

Duraforce E6560 boot loop

I've had this phone 3 years and it worked well. It's an unlocked ATT phone so no OTA updates other than the standard app updates. It's on Lollipop 5.1. Been working perfectly fine until yesterday, I was watching the CBS app, when the phone rebooted. Now it's stuck on a boot loop and initally went to optimizing apps which it rarely finishes but the times it does, the phone just powers off. It then got into another loop later last night where it'd get to the Kyocera logo then reboot over and over. I let it do that until the battery died 2.5 hours later. Then I kept attempting to boot until the batter was entirely drained to the point it wouldn't attempt to power up any more.(battery is not removable on this model). I've now charged it up, trying to enter recovery mode with power+volume down. That doesn't seem to register. Tried volume up+volume down+power with no effect. Now after charging, it will do the reboot loop mentioned earlier to the Kyocera logo. If I plug it into a charger, it will go to the optimizing apps portion and repeat the above. At the optimizing apps screen, if I unplug the charger, the phone powers off immediately. It appears to be holding a charge according to the charge indicator and the fact that I can try to boot over and over unplugged. Any suggestions? Phone wasn't dropped or damaged in anyway. Very weird what could have happened.
An update: Phone finally got past the "optimizing app" phase last night sitting on the charger. Out of no where the phone booted completely. However, it only works while plugged in. If I remove the charging cord, the phone shuts down after about 2 seconds. Booting without charging cord results in the same boot loop. I've considered the battery has failed however when plugging in the charger, battery shows 100% and it will decrease appropriately over time. I'm thinking there must be a hardware issues at this point. Somewhwere in the charging/power circuit. Any other suggestions?
Last update I guess. I was able to keep the phone up and booted as long as it was plugged into a wall charger. PC USB was not enough. I managed to grab my photos etc. thankfully. Factory reset the phone from the settings menu. Unplugged from charger, ran for about 2 minutes. Still said 99% charged, then went into boot loop again. Phone still shows near full charge if you let it run for awhile and decrements the charge state appropriately as time goes on. However, i guess this 3 year old phone is toast. No known reason for it to fail unfortunately. Thought I'd share the experience if anyone else has this issue.
djhurt1 said:
Last update I guess. I was able to keep the phone up and booted as long as it was plugged into a wall charger. PC USB was not enough. I managed to grab my photos etc. thankfully. Factory reset the phone from the settings menu. Unplugged from charger, ran for about 2 minutes. Still said 99% charged, then went into boot loop again. Phone still shows near full charge if you let it run for awhile and decrements the charge state appropriately as time goes on. However, i guess this 3 year old phone is toast. No known reason for it to fail unfortunately. Thought I'd share the experience if anyone else has this issue.
Click to expand...
Click to collapse
I have the same exact problem. It started the crazy booting process in my pocket, and I did all the same things you did. Factory reset didn't correct the problem, so I'm think the battery has had a stroke. Sine your problem and my problem are very close to the same time frame, our phones are also probably about the same age, and its a quality control issue. Not bad quality control, just that these batteries were designed to last X number of months or cycles, and probably they died. Too bad, because my E6560 is the very best cell phone I have ever owned. Built like a tank and thank God for that.

Categories

Resources