Database Users

[Q] shut down normally: now no power light or boot

I apologize in advance if there is a similar thread; I could not find one.
My EVO has been fine, no issues. I use it heavily every day. I'm running Cyanogen 7 nightly 147 (I think) and have been for 4 or 5 days. Using the Tiamat kernel running SMARTASS.
Last night I shut down around midnight with around 50% power. I plugged in the charger but don't remember if the charging light came on then. This morning there is no charging light and the phone won't boot. Tried long holding the power button, battery pulls, pulled the SD card (for lack of anything else to try). Nothing has had any effect.
Does anyone have other ideas? I'm at a loss. If it's dead, it sure chose a strange way to go. Any advice would be very appreciated. I need this thing for work and home. Many thanks.

Just after posting I went back to playing with different chargers and power button pushes. The white HTC logo flashed for a second and the phone vibrated but it went right back off. It's the first sign of life I've seen, but I can't get it to repeat or go further.

This happened to my sisters Evo when she first got it last summer. Luckily it was the battery and HTC shipped a new one for free. The warranty on the evo is 15 months so you can try and request a new battery!
Sent from my PC36100 using XDA App

I have found one similar thread: http://forum.xda-developers.com/showthread.php?t=913258. So maybe it is a dead battery. Been getting amazing life recently, so it seems crazy that it would suddenly be dead. Is this common?

Any suggestions for going to the Sprint store with a rooted phone? Since it's a bad battery, they may not need to look at the phone once it boots. I haven't had to do this before, so I'm not sure what to expect.

if you do go to a sprint store, i would not let them keep the phone or even take it out of your sight. if that happens you may well find yourself unrooted. but thats just a guess. you can get on ebay or any other similar site and buy a cheap battery for less than $5. then if thats not the problem go from there. this same problem happened to me but luckily one of my friends also has an EVO so i just used his battery and my phone worked great. so i just bought a new battery

Thanks for the input. Headed to the Sprint store in a minute to see if a battery will solve it.

It was the battery. They tested in at the Sprint store and pronounced it DOA. They said they don't normally have spare batteries but they happened to have one, luckily. I was pretty grabby with the phone and didn't let it go for long. Once it started to boot I took it back and they never saw the Cyanogen screens.
Overall they handled it very well. I was impressed with how responsive they were. I was out of there in 10 minutes.

Be carefull with the new ICS ROMS. Always shut down by holding the button for 20 secs

I have been using a new ICS build and wanted to warn everyone about the shutdown problems. It seems that by choosing to shut down by pushing the button and choosing "shut down" leaves the backlight running (you can see it if you look).
This has drained my battery down to nothing preventing my Kindle from booting. The stock charger did nothing, no charge, no light, no boot. Plugging in to the PC made the Kindle come on, but reboot after a couple seconds, not long enough for me to even get into recovery mode.
On a hunch I used my phone charger. Not only did the Kindle kick on and boot, but it seems to be slowly charging. I restored back to the stock ROM and now it seems like the stock charger has no effect at all.
Just be careful and be aware that the back light will stay on for now until the kernel is updated.

Thanks!
Sent from my Kindle Fire using xda premium

It happened to me already, but it woke up with the original charger.
Thanks!

yeah two known bugs for the 3.0 kernal are usb wall charging and the device not shutting all the way off (backlight stays on). if you need to you can always go into recovery to charge up. also turning lockscreen and touch sounds off in settings>sound will help save battery

It's 2 different bugs that can combine in a bad way: quick battery drain and loss of wall charger.
Anyways there is hope, people have been grabbing a USB charger form other devices or for most the USB-PC route still charges.
The ROMs are getting very good, the banding is fixed and it seems the AC charger issues have been patched up, even the small menu buttons are fixed in one of the ROMs. Now all I need is a volume bar and I will have my daily driver for a while.

This just happened to me...
My kindle died after shutting down for one day. No battery at all...

Did you even read the first post of the kernel thread?

ryanhuong said:
It's 2 different bugs that can combine in a bad way: quick battery drain and loss of wall charger.
Anyways there is hope, people have been grabbing a USB charger form other devices or for most the USB-PC route still charges.
The ROMs are getting very good, the banding is fixed and it seems the AC charger issues have been patched up, even the small menu buttons are fixed in one of the ROMs. Now all I need is a volume bar and I will have my daily driver for a while.
Click to expand...
Click to collapse
Something for the volume control:
https://play.google.com/store/apps/details?id=rubberbigpepper.VolumeControl
Back to OP, I used to hold power until the backlight would turn off (about 15sec) but one day it just so happened that my kindle did not turn off completely even then. After that I have been holding it down for a straight 20sec.
Sent from my Amazon Kindle Fire using XDA

StaticMatt said:
Did you even read the first post of the kernel thread?
Click to expand...
Click to collapse
No, and that's why it's a surprise to them. Hashcode has been saying, repeatedly, he doesn't recommend it as a daily kernel. In big red letters, at the top of two threads, it says wall charging doesn't work. Throughout those threads it has other people posting who say they don't know why their kindle died overnight.
It's just a neverending...I wanna call it a cycle, but there's no cycle to it. It's more like a neverending stream of people who refuse to read.
Guaranteed, if I made a thread offering a kernel and in big red letters at the top it said "THIS KERNEL WILL BRICK YOUR KINDLE" and then proceeded to post a changelog and other information about how to install, etc... There would be no less than 100 posts the following day asking why their kindle doesn't work.

If the devs were offered a dime every time somebody failed to follow directions...

Felnarion said:
No, and that's why it's a surprise to them. Hashcode has been saying, repeatedly, he doesn't recommend it as a daily kernel. In big red letters, at the top of two threads, it says wall charging doesn't work. Throughout those threads it has other people posting who say they don't know why their kindle died overnight.
It's just a neverending...I wanna call it a cycle, but there's no cycle to it. It's more like a neverending stream of people who refuse to read.
Guaranteed, if I made a thread offering a kernel and in big red letters at the top it said "THIS KERNEL WILL BRICK YOUR KINDLE" and then proceeded to post a changelog and other information about how to install, etc... There would be no less than 100 posts the following day asking why their kindle doesn't work.
Click to expand...
Click to collapse
This is a discussion forum right? We are discussing.
If I can help even 1 person avoid that problem then I will. Maybe you guys should stick to the dev threads with all the smart people. This thread is for dummies who can't read.

Not going to argue with you on that one.

ryanhuong said:
This is a discussion forum right? We are discussing.
If I can help even 1 person avoid that problem then I will. Maybe you guys should stick to the dev threads with all the smart people. This thread is for dummies who can't read.
Click to expand...
Click to collapse
You do see the irony in all that, right?

@ryanhuong - just wanted you to confirm once that the wall charger is not indeed working for you.
I too had the same impression for some time as it _looks_ that way, but then realized it is working when I hit the top-left Refresh button in Settings -> Battery. The % kept going up.

umash4 said:
@ryanhuong - just wanted you to confirm once that the wall charger is not indeed working for you.
I too had the same impression for some time as it _looks_ that way, but then realized it is working when I hit the top-left Refresh button in Settings -> Battery. The % kept going up.
Click to expand...
Click to collapse
With the newest kernel yes it seems to charge fine. The Pure AOKP build seemed to have more issues. Now I am using the newer AOKP and not does the charger work again, but the LED now shows orange or green (but the battery icon s still wrong).
Huge improvements so far.

This happened a few times with my Optimus V. This was because there was no offline charging support for AOSP ROMs at the time. The only way I could get the phone to stay on was to force the battery into a LG Rumor Touch and recharge it with that until the battery could boot the Optimus. Thinking how the Kindle Fire has no offline charging support and a non-removable battery strikes fear into my soul.
I know the AOKP ROMs fully power off the device. So at least I'm okay with that.
Also, is it bad that my Kindle Fire charges extremely slow with any other cable than the stock charger?
Sent from my Amazon Kindle Fire using Tapatalk 2

It will always work best with the stock charger, but until the bugs are fixed, who knows.

KemikalElite said:
Thinking how the Kindle Fire has no offline charging support and a non-removable battery strikes fear into my soul.
Click to expand...
Click to collapse
It does charge offline, the problem lies in the LED not reporting this properly (it doesn't turn on to reflect the charge status).
KemikalElite said:
Also, is it bad that my Kindle Fire charges extremely slow with any other cable than the stock charger?
Click to expand...
Click to collapse
This is normal, as they usually provide less amps than the stock charger (1.8).

For what it's worth, I am on #33 AOKP KF Edition and the LED works perfectly. It's the icons that don't work right.
EDIT: I take that back. If the KF is asleep and you plug it in the LED stays dark. If the tablet is awake and you connect the charger, the orange comes on, putting the tablet to sleep the LED stays orange till it turns green when full.

Felnarion said:
No, and that's why it's a surprise to them. Hashcode has been saying, repeatedly, he doesn't recommend it as a daily kernel. In big red letters, at the top of two threads, it says wall charging doesn't work. Throughout those threads it has other people posting who say they don't know why their kindle died overnight.
It's just a neverending...I wanna call it a cycle, but there's no cycle to it. It's more like a neverending stream of people who refuse to read.
Guaranteed, if I made a thread offering a kernel and in big red letters at the top it said "THIS KERNEL WILL BRICK YOUR KINDLE" and then proceeded to post a changelog and other information about how to install, etc... There would be no less than 100 posts the following day asking why their kindle doesn't work.
Click to expand...
Click to collapse
Actually as one of the guys that's working on the kernel I would have to say you're incorrect. Wall charging does in fact work. The issue with the led is that the kernel doesn't correctly update it, as well as it doesn't update the from in a manner for the icon to change. If you download a battery widget in the market you will see that it does in fact charge with a wall charger. This is also a better route to go since the OEM charger puts out about 1000mv as opposed to 100mv w/USB 1.0 or 500mv w/USB 2.0. Only other steady charging scenario would be USB 3.0 because its output is 900mv.
Sent from my MB860 using XDA

Blu Vivo Air 4G LTE in charging bootloop

I've seen a few threads about bootloops but so far not one like this - or one with a solution. In the past if my Vivo went dead when I'd try to charge it, like now, it would start to charge, power on to the white/black Blu Bold Like Us screen then power off for a few seconds and repeat. It's like it never gets enough charge to go any further than that. I've tried a few chargers where I am (traveling) and it seems none can get it enough juice to finally get past this and power on.
Any thoughts if that's the issue or not? Any way to stop it from trying to power on constantly automatically so it can build up some juice before doing so? If that's not the issue any thoughts on a way to fix?? I really love this phone but am gonna have to finally get something new if I can't correct this.
Thanks,
-Ross

Well once again on xda I'll answer my own question. I finally found a 2.1 Amp charger after using some others and bingo, it charged up just fine. So odd that such a small device needs such a strong charger...

Help: Bought used HTC 10, it started randomly reboot, now stuck in bootloop, stock sw

I guess Santa gave me a lump of coal this Xmas... I finally treated myself to an upgrade from my trusty One M7 and got an used S-offed HTC 10 from Swappa. Yeah I know... as a poor grad student, funding is pretty damn tight.
The phone is in good physical shape - no obvious signs of abuse. However, in the first week of use, I experienced a couple random reboots, and the phone itself was getting hot (>40 degrees C) while just texting and on wifi, with airplane mode on. Battery life with that usage pattern and load was maybe 1.5 hours screen on time. Deep down I knew something felt off, as that's WORSE battery life than my 4+ year old One M7. But I thought hey, it's a used phone. I was planning to flash TWRP and custom roms on there, maybe the debloated roms will help.
When I finally was able to flash TWRP and Santod's debloated stock rom, it was okay. Still some random reboots, but I loved the new phone so much, I was okay with it.
Until it got worse and worse. To the point where unlocking the phone will make it freeze, then reboot. At first, it was when the battery was low, like 40%. Then gradually it started freezing and rebooting at higher %, until it started doing it with a full battery.
Fast forward to just before Xmas - the phone is unusable. It will reboot show the white HTC boot screen, then black out, and start again. Bootloop forever. All while plugged in. I noticed the charge light isn't on even when plugged in, I guess during the initial seconds of booting up, it relies on battery power alone? Such a bad design if true
I've had to leave it overnight. I would wake up to a seemingly dead phone. I'll plug it in, and it would show the charge screen. If I turn it on then, it would go into bootloop. It won't even make it into recovery, stock or TWRP when I had it. If I let it charge until the charge light is green, it MIGHT boot into the welcome screen. It'll freeze up after a few taps, then back to bootloop.
My best guess is the previous owner abused the battery so bad that the cell is completely ****ed. I regret that I forgot to ask about the battery life before I made the purchase - I was just too excited about getting an upgrade from my M7 As of now, I am back to my trusty M7, which although slow and janky, it's 100% stable and still has usable battery life.
I paid $200 for the HTC 10, which might not be a lot of money to some, but it is to a struggling grad student like me. The phone is nothing but an expensive paper weight right now. And I never got to enjoy it Has anyone experienced similar problems with their 10? I am so angry and sad...

Roughly the same thing happened to a friend, we got our 10's at right around launch. We had similar battery usage, we both played a lot of Pokemon Go which is hard on the battery. Mine has been running custom ROM's as far back as when Sunshine was still mail in, his is purely stock S-on. His started doing the same thing as what you are describing a couple months ago, we even tried a RUU and while that helped for awhile he traded it in asap for a Pixel 2. There are a few reports of this going around, not sure if it had to do with a recent update from Verizon that borked something or if it's a hardware flaw, either way you are probably better off trying to get your money back or trading it in to HTC of Verizon for something newer

S7 edge bricked in pocket, no apparent reason.

Hello.
Today after i was back from town, I left my S7e in my pants pockets while i changed clothes and opened my pc. I tried to check whatsapp web from my pc, and it told me your phone is out of range(out of battery in this case). and i was like oh well ok, its ran out of juice. Tho i was a little suspicious about it, as it was at 20%+ while i was at town, out of experience i know that 20 lasts a long time. But, i forgot about it and was too lazy to get my charger out of my backpack.
Now after about 2,5 hours i quit the stuff on my pc, moved up and got ready to charge the phone again.
And HEH HEH its bricked. Or optionally the screen is totally dead, wich i think is not.
Have not flashed ANY roms on the device, have had a stable root and stable xposed and stable everything since note 7 launch. Never had any issues.
So, what do yall think?
If the battery dies can it cause this? Havent had any water contact or anything with the phone today.

its dead even when charging?
if yes thats not battery fault.
there is a sticky thread for bricked S7 edge, try that.
or maybe you hit your phone and it died?

Lithium-Ion batteries don't like having less than ~40% charge. You said that out of experience you'd knew that 20% left charge lasts a long time, suggesting that your device has been run below 40% of capacity quite often.
For me, this indicates a dead battery that is no longer capable of delivering/holding a sufficient current.

it should work on usb even without battery, like notebooks.
dead battery just dont hold energy and capacity

yaro666 said:
it should work on usb even without battery, like notebooks.
dead battery just dont hold energy and capacity
Click to expand...
Click to collapse
Not necessarily. Most, if not all modern smartphones will not turn on with a malfunctioning battery.
I tried it out of curiosity. I have a few devices lying around.
Trying to turn them on without a battery:
LG G4 - negative
LG Nexus 5 - negative
HTC One M7 - negative
HTC One M9 - negative
Samsung Galaxy S3 - negative
Samsung Galaxy S4 - negative
Samsung Galaxy S5 - negative
Samsung Galaxy S6 - negative
Samsung Galaxy Note 3 - negative
Samsung Galaxy Note 4 - negative

thanks we learn every day.
mostly devices that I repair turn on just on cable, but I dont ha e a lot of experience with modern smartphones - mostly lcd replace.

I had the same problem, I was sending a TX message on my S7 Edge and all of a sudden the screen just went blank. The phone wouldn't turn on or off and it was getting hot. So I booted into safe mode, now the phone is in safe mode and won't boot back into a normal operating system mode. Now my S7 Edge is stuck in safe mode. I can move through the different options, but the phone will not act on any of the power options