Hi,
My HTC One seems bricked, I just want to go through all the things I have tried hoping I've missed something . My only other option is to contact HTC.
My phone was running Slimkat 4.4 and also had an app called One Power Guard which saved power by messing with the Kernel. It was running stable with the rom for more than a month.
My phone was charged all night 2 days ago, it reached hundred percnt but I noticed it when I stated using it that very very hot. The battery also heavily drained and the phone died about about an hour and a half later. This was the first time this had happened also beside the heat and the drain the phone was working fine.
It has not switched back on since neither has it shown any sign of life.
I have tried the following:
1. held the power button and the volume down or up button in all combination ranging from 10 seconds to minutes.
2. Done the same under a bright light.
3. Tried unbrick beta on 32 bit llinux (was not detected).
4. Tried putting it in freezer for 2 minutes.
5. charging the phone for over 36 hours straight.
6. plugging it into pc (not detected).
Any help would be great.
ronin90 said:
Hi,
My HTC One seems bricked, I just want to go through all the things I have tried hoping I've missed something . My only other option is to contact HTC.
My phone was running Slimkat 4.4 and also had an app called One Power Guard which saved power by messing with the Kernel. It was running stable with the rom for more than a month.
My phone was charged all night 2 days ago, it reached hundred percnt but I noticed it when I stated using it that very very hot. The battery also heavily drained and the phone died about about an hour and a half later. This was the first time this had happened also beside the heat and the drain the phone was working fine.
It has not switched back on since neither has it shown any sign of life.
I have tried the following:
1. held the power button and the volume down or up button in all combination ranging from 10 seconds to minutes.
2. Done the same under a bright light.
3. Tried unbrick beta on 32 bit llinux (was not detected).
4. Tried putting it in freezer for 2 minutes.
5. charging the phone for over 36 hours straight.
6. plugging it into pc (not detected).
Any help would be great.
Click to expand...
Click to collapse
looks like a defective battery or even a dead board...
It happened my HTC one. I returned to HTC and they replaced the motherboard under warranty
Thanks for the help guys sent mine back to htc. Hopefully will be fixed.
Related
I found a ROM I really liked around 2 months ago and stopped following the development on this phone.
Yeah, so, my phone started freezing up occasionally about two weeks ago. Couldn't fix it, so I just pulled the battery and didn't think much of it. Kept working until a day or two later when it would freeze again. Last night, it was at 4% battery life, and it froze. I let it die and went to sleep.
This morning, I started downloading AIO so I could flash it to stock. Plugged my phone in, nothing. Not showing any signs of functionality. No combination of battery pulling, plugging in, holding the volume buttons/power button can get any life out of this thing.
Also, it gets hot if I have it plugged in for 5 min or so.
Is my Captivate dead?
Sounds like it could be a hardware problem. I works suggest taking it to att if you can't get it to do anything
Sent from my GT-I9000 using XDA App
I rooted my phone last week thanks to the xda forum
[ROM]-Unoffical AOKP
[Kernel]-No change.
phone worked great, awesome battery life, was on the phone for 4 hours and still i had 40% left, that to while using skype on wifi. Normally the phone used to die within the first 2-3 hours.
I was checking on the various kernels, just coz i wanted to get the ATT world phone image out of my phone! so i used icyglitchv14, well it worked.
But for some reason the phone's battery seemed to drain faster when the phones idle. The phone was back to its crappy battery life.
Yesterday, i flashed the unofficial AOKP ROM build 25 (thanks) the battery life improved drastically, though i have no clue as to why!
Problem now? Battery won't charge, rebooted, turned phone off, but battery just wouldn't charge.
Solution: Remove the battery, hold on to the power button for 5s, replace the battery and turn on the phone. It started charging.
I don't know if its a bug, or if its got to do with the icyglitch power states ( i used conservative), but hope someone checks this out.
i am 100% baffled that this just worked for me, but thanks so much for posting this
Thanks marcknight.
Noticed it around 15% and started to panic.
Turned to my trusty XDA hoping for a solution before it died completely.
One of those strange instances of: Don't ask HOW or WHY, just know that it works.
this worked for me!
this worked for me!
I was also using aokp build 40 ics. and the power mode I believe that I set it on was conservative, I guess i shouldn't use that mode anymore! My power button also doesn't work very well so i was basically mashing all of the buttons while the battery was out of the phone and also while the phone was plugged in, then i inserted the battery and it just started booting with the att screen.
Not charging
That happens to me today. Because I read this earlier I did the same and Voila!!
Thanks!!!
Mine stopped charging too.. and its stock
I am running stock ATT firmware and the battery will charge outside the phone but in the phone it shows charging but gos dead. I have tried the 2 amp power charger for my nexus 7 and that won't even charge it. Good thing I got a cheap external charger a while back.
Anyone know what could be causing this?
a guess: removing the battery, then holding the power key for a few seconds causes the max8998 power management chip to reset, probably by discharging a capacitor or equivalent.
liberate your captivate on xda
Having the same thing happen to me right now. I using the Captivating ROM, just tried your solution, will see how goes. Thanks.
Good evening everyone, I have a Nexus 7 8gb, but the thing is, I cannot turn it on now.
It happened as follows:
I was using it every now and then, mostly to read and play.
I was using the charger to charge my cellphone too (XTC Explorer) as it was a lot faster, being 2amp/h.
I updated the cell to 4.1 and at the same week noted the battery wasn't running that long, but blamed it to the rom.
The cellphone also took a lot longer to charge with the nexus charger, yet again I blamed the rom.
I noticed the Nex was at 8% while reading so decided to charge it, but I guess I forgotten.
The next time I wanted to use it it wouldn't turn on. I figure it had no battery.
I plugged the nexus charger to the nexus a whole night and in the morning it still wouldn't turn on.
I figured something must be wrong with the charger, so I tried with the cellphone and nook color charger, but both are .5 amps/hour.
It wouldn't charge, neither connected to the pc (also .5a/h via usb) so I tried a psp go charger, as it is rated at 1.5 amp/hour, much closer.
I connected it at night and saw the charging icon (white on black battery with the ray) and left it overnight.
The next morning it wouldn't turn on either.
I've bought it almost two months ago and I really enjoy it =) but now I'm desperate.
I cannot call google play for the warrant because I'm in Argentina, and I don't believe they will ship me a replacement, nor anything. This one my brother bought from them, but he went back to US a few days ago, and I didn't think of giving it to him to RMA.
I tried keeping the on button, for 5 secs, 30 sec, 90 secs, 120 secs, and no dice. Also tried holding the Up Volume key to restart it, but no chance.
Please help!
Had a similar issue to this over the weekend after not charging for 2 days and the battery going dead. I let it sit on the original charger overnight and for some reason it did not charge. It kept booting and shutting down once it booted due to a low battery warning. It eventually got to the point where the screen would go to fuzzy lines and light but no boot.
To finally get it working I did a combination of a few things but don't actually know what got it going.
Put it on a different (kindle) charger and let it sit for an hour or 2, did several hard resets holding both just the power and also the up/down volume and power all at the same time for up to 60 plus seconds. I switched back to the stock charger and did an additional hard boot by holding just the power for 30+ seconds and it started booting and charging.
I did however put it on the charge again last night and noticed this morning it was still at half battery and didn't get a charge. I ended up putting it on a mifi charger this morning and it's charging again so don't know what is up with the stock charger. Also, have all the latest updates to 4.2 as far as I know as there have been charging issues reported with earlier versions...
Sent from my Nexus 7 using Tapatalk 2
Try this, it just saved my device:
davidcampbell said:
try holding down the volume DOWN and the power key for 10 seconds, then release the power key and keep the volume down key pressed, and it will force the unit to restart into the bootloader from any stage, its effectively like pushing the restart button on the front of a computer and constantly pressing the delete key to get into the bios.
Click to expand...
Click to collapse
A month or so ago, my mother told me her Nook HD+ (on which I had installed CM 10.1.3) would not turn on. I told her to plug in the charger for a few hours and try again. Still no go. I will be visiting her in a couple weeks and will see what I can do.
Today I tried to turned on my wife's HD+ (running CM 10.2.1) which had been off for several weeks. It was almost fully charged that last time it was turned off. It would not come on. I plugged in the charger in and no light came on. After a couple hours I held the power button on and after 10-15 seconds the battery symbol came on for 2 or 3 seconds then disappeared. This time the orange charging came on and stayed on so I assume it is charging. I will give it a few more hours before trying again.
What I'm wondering is: why does the battery seem to drain when the device is off, why won't it boot with the charger plugged in (I assume there must be some minimum battery charge required even when plugged in), is this typical of this device?
Any and all ideas or suggestions appreciated.
lmacmil said:
A month or so ago, my mother told me her Nook HD+ (on which I had installed CM 10.1.3) would not turn on. I told her to plug in the charger for a few hours and try again. Still no go. I will be visiting her in a couple weeks and will see what I can do.
Today I tried to turned on my wife's HD+ (running CM 10.2.1) which had been off for several weeks. It was almost fully charged that last time it was turned off. It would not come on. I plugged in the charger in and no light came on. After a couple hours I held the power button on and after 10-15 seconds the battery symbol came on for 2 or 3 seconds then disappeared. This time the orange charging came on and stayed on so I assume it is charging. I will give it a few more hours before trying again.
What I'm wondering is: why does the battery seem to drain when the device is off, why won't it boot with the charger plugged in (I assume there must be some minimum battery charge required even when plugged in), is this typical of this device?
Any and all ideas or suggestions appreciated.
Click to expand...
Click to collapse
When you say off, do you mean completely off or sleeping? If completely off, it should not drain like that. Might be a weak battery.
And yes the power up sequence you described is normal with a dead battery. It must charge a little before turning on.
Tell your mom to try the same thing, holding power button for 15 sec.
If you are going to store it, it is best to have it at about 50% and then turn it completely off.
Sent from my SM-T707V using XDA Premium HD app
Pretty sure my mom just let battery run down. She's 89 so not too attentive to electronic things. I'll make sure it's charged when I see her and try to get it going again.
Also pretty sure (but not 100%) my wife's unit was off-off, not standby-off. At any rate, it booted up after being charged. Updating 19 apps right now. Thanks.
Sent from my BN Nook HD using XDA Free mobile app
This may be late, and sound odd, but humor me if it's not resolved yet. Try to boot it with the SD card removed. My ovation went to doing the same thing, then further to showing false battery levels, and the SD card caused it. Inleqrndnthis by trying the SD card in a spanking new ovation, and my "faulty" ovation then booted, while the new one became problematic. Upon replacement of the now deemed faulty SD card, the problem has not returned.
ieatabiscuit said:
This may be late, and sound odd, but humor me if it's not resolved yet. Try to boot it with the SD card removed.
Click to expand...
Click to collapse
Thanks. I'll be seeing my mom on Friday. Will try this if I can't get it started.
Sent from my Nexus 7 using XDA Free mobile app
Got my mother's Nook started. She just doesn't have enough finger strength to hold the button down for the 15 seconds or so it took to start. I'm going to tell her to leave it on all the time and plug in the charger every night so the battery never runs down to nothing again.
Sent from my Nexus 7 using XDA Free mobile app
Hi All,
I have come across a weird problem with my realme X2pro.
Few months ago I dropped my phone and the screen was dead, however the phone was powering on and since it had Microsoft My Phone setup I was able to receive the calls and messages on my laptop whenever the phone was powered On.
Since there was lockdown I preferred to order OnePlus and get the phone repaired later, after 2 months I got the screen replaced at authorized service center and the phone worked fine for 10 days.
After that one day it just switched off and wont power On irrespective of what I try, after about 20 days I tried to power it on again and to my surprise it powered on and then switched of after 5 minutes (battery showed 100% charge). After that if I try to power On there is no sign of any power or activity on the phone.
I lost all hopes and now after 3 months I powered it on randomly after leaving it for a full charge (4 hours) and surprisingly it power on and worked fine for 5 minutes and then shut down.
I had taken the phone to service center and they say that motherboard was fault and wanted to charge 18K as its the Master Edition Phone.
I am technically sound person as I work for a tech company and know my stuff around Android, Windows and BB phones very well.
I have tried fastboot and recovery to load with diff power button combinations but absolutely no sign o power.
I am suspecting this is a battery issue but need to get some 2nd opinion before I spend 2k, already spent 15k for the screen though.
Thanks in advance for your support and guidance.
I think i have figured out that there is a battery issue with the phone.
The battery has to be charged for at least 10+ hrs before it allows to power ON.
However now I have ended up with another issues.
After booting the phone to the OS successfully, I chose to flash to old version as I wasn't able to access fastboot.
The flashing completed successfully but now I am stuck on Realme Logo and phone does not boot to android.
I am also not able to boot to recovery or fastboot mode as I was rolling back from Android 11
Any help here will be appreciated.