Related
Hi, new here but I've been lurking for a while.
I followed Powerpoint's guide to instal CM10 on my KF2
http://forum.xda-developers.com/showthread.php?t=2105077
Everything was running great and has been since I first loaded version 3 a few weeks ago, and last week i went to version 4 of powerpoint's rom with no problems. Then a couple days ago after i had been browsing the internet on it for maybe 30 minutes, I set it down and when i came back the screen was off and wouldn't turn back on. so i figured the battery was just dead, so i plugged it in to the wall charger. At first the charge/power light wouldn't come on at all. Then after several plugs and unplugs the orange light started to come on but would only stay illuminated for 30 seconds-ish. So I tried it on my phone charger and the orange light came on and stayed on, so i decided to let it charge overnight. The next morning the light was still glowing orange so I unplugged it and tried turning it on, but still nothing happens. But when I plugged it back in afterwards the light came on green. now it has been plugged in for almost a day with the green light on but it still wont turn on.
Anyone else have this problem? Any ideas what i can try? for obvious reasons i can't exactly ship it back to amazon lol
p.s. I have a final on friday and the text book for that class is on the kindle. So urgent responses will be greatly appreciated.
Nevermind guys, I figured it out. Power button for 20 and it booted right up
Sent from my EVO using xda app-developers app
docnougat said:
Nevermind guys, I figured it out. Power button for 20 and it booted right up
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I've had this a couple of times on both 10.1 ROMs. As you stated the only way I got it working was to hold the power button for 20 secs, then power on normally.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
It just happened to me again, seems to be a recurring problem. Anyone have a clue what's causing this?
on a side note, perhaps this problem could be dealt with simply by installing a battery management app like juicedeffender. any thoughts?
docnougat said:
It just happened to me again, seems to be a recurring problem. Anyone have a clue what's causing this?
on a side note, perhaps this problem could be dealt with simply by installing a battery management app like juicedeffender. any thoughts?
Click to expand...
Click to collapse
Wow, for once I can completely and knowledgeably help with almost no guess work!
The issue is Sleep of Death.
The cause is unknown, and due to the nature of how to reset it, it's been difficult to get logs. It happened to FMK not too long ago and last I heard he was going to get the logs (to find what causes this) and get those to Hashcode to look at potential fixes.
It's not battery related....well in the sense that, if it happened, you reset the device, and looked at the battery, it should be at a similar level to what it was before.
TO FIX
You guys were right on fixing it mostly.
If you ever press power a few times and it won't turn it, don't bother fretting about it. Just do the hard reset, which is holding the button down for 10 seconds. After you do that the device will reset to the point where if you just press the power button once, it will boot up like normal.
I would hold it down for about 15 seconds just in case, or if you have headphones it, you can here when it does the reset and can get used to the timing.
I would say....in a few weeks with the device, I've had the issue around 5-6 times.
I've also NEVER had it happen while I'm doing things, so it hasn't caused issues besides making me a wait a bit before using the device, which is good. If it happened during doing things I would want this fixed ASAP, but so far, no major issues.
agreed, if it was happening while i was trying to do stuff it would be problem. As it is though, I just consider it a minor inconvenience. Glad to know I'm not the only one experiencing this though.
iytrix said:
Wow, for once I can completely and knowledgeably help with almost no guess work!
The issue is Sleep of Death.
The cause is unknown, and due to the nature of how to reset it, it's been difficult to get logs. It happened to FMK not too long ago and last I heard he was going to get the logs (to find what causes this) and get those to Hashcode to look at potential fixes.
It's not battery related....well in the sense that, if it happened, you reset the device, and looked at the battery, it should be at a similar level to what it was before.
TO FIX
You guys were right on fixing it mostly.
If you ever press power a few times and it won't turn it, don't bother fretting about it. Just do the hard reset, which is holding the button down for 10 seconds. After you do that the device will reset to the point where if you just press the power button once, it will boot up like normal.
I would hold it down for about 15 seconds just in case, or if you have headphones it, you can here when it does the reset and can get used to the timing.
I would say....in a few weeks with the device, I've had the issue around 5-6 times.
I've also NEVER had it happen while I'm doing things, so it hasn't caused issues besides making me a wait a bit before using the device, which is good. If it happened during doing things I would want this fixed ASAP, but so far, no major issues.
Click to expand...
Click to collapse
I wouldn't call it a fix. I would call that a workaround. We need a fix, and I think if anyone could get an effing log to hashcode of it happening, we could fix the problem. I think it is a kernel problem, what with the recent merges and such. I think something is incorrectly copying from kf1 to kf2... if anyone understands what I'm trying to say, it makes sense..
fmkilo said:
I wouldn't call it a fix. I would call that a workaround. We need a fix, and I think if anyone could get an effing log to hashcode of it happening, we could fix the problem. I think it is a kernel problem, what with the recent merges and such. I think something is incorrectly copying from kf1 to kf2... if anyone understands what I'm trying to say, it makes sense..
Click to expand...
Click to collapse
I wonder if pulling the log cat via adb would work, I.e. wait till it goes wrong' then connect it to a PC to pull the log. The issue is its very random and being at a PC to do it when it goes wrong could be tricky.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
chronicfathead said:
I wonder if pulling the log cat via adb would work, I.e. wait till it goes wrong' then connect it to a PC to pull the log. The issue is its very random and being at a PC to do it when it goes wrong could be tricky.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
or you could have kmsg being written to a file during it...
the hard reset (power button for 20s) clears memory
I installed a new rom, and this is still happening.
Sometimes I press the power button on my kindle to wake it up, and it doesn't do anything. But I never turned it off, and I know it didn't run out of batteries. So I have to hold down the power button for a while to forcibly shut it down and then turn it back on.
This is getting annoying since it happens at least once a day, but I don't know how to troubleshoot this.
And yes, I wiped everything before flashing, and I'm using a recent version of TWRP.
Artel said:
I installed a new rom, and this is still happening.
Sometimes I press the power button on my kindle to wake it up, and it doesn't do anything. But I never turned it off, and I know it didn't run out of batteries. So I have to hold down the power button for a while to forcibly shut it down and then turn it back on.
This is getting annoying since it happens at least once a day, but I don't know how to troubleshoot this.
And yes, I wiped everything before flashing, and I'm using a recent version of TWRP.
Click to expand...
Click to collapse
What ROM are you using and what ROM were you using before?
soupmagnet said:
What ROM are you using and what ROM were you using before?
Click to expand...
Click to collapse
SmoothRom and twa priv's cm 10.1
From 4.21 version, My KF always could not turn on from standby, even with the latest ROM. Have to long push power button to force off than turn on. Does it conflict with some apps? Full wipe could not solve. Please advise. Thanks
Sent from my Amazon Kindle Fire using xda app-developers app
Artel said:
I installed a new rom, and this is still happening.
Sometimes I press the power button on my kindle to wake it up, and it doesn't do anything. But I never turned it off, and I know it didn't run out of batteries. So I have to hold down the power button for a while to forcibly shut it down and then turn it back on.
This is getting annoying since it happens at least once a day, but I don't know how to troubleshoot this.
And yes, I wiped everything before flashing, and I'm using a recent version of TWRP.
Click to expand...
Click to collapse
I've been having this issue for a while now. I don't think it has anything to do with the ROM because there are MANY threads with this same question on the official Amazon boards and they are all running the original Kindle software.
It seems like something is causing the kindle to hang while the screen is off and the processor keeps working because I see significant battery drain when I reboot (especially if it happens overnight). The interesting thing I saw today was that it's due to a battery calibration bug on the Fire that it hangs when the battery reaches 100% charge and then freezes when the device stops charging. This SEEMS to coincide with what I am seeing, but I haven't looked into it yet.
Regardless, this issue has been coming up in forums for several years and there appears to be no fix that I have found, at least... but it IS annoying!
I recently installed Alien Droid for kf2 on my kf2 and everything was going smoothly so I doubt it was that, but I woke up this morning to a kindle fire that wouldn't turn on at all, the screen doesn't flash or anything and it just stays blank. I've done the hard reset where you hold power button for 20 seconds and still nothing. The battery indicator light comes on when I plug it in and it will turn off when I do the hard rest. Could this have anything to do with maybe the battery dying overnight?
While it's plugged in to the computer (given time to boot normally), are you able to communicate with the device via adb?
Nope, I've also left it to charge for about six hours. Now when I try to press power button it flashes green but the screen does nothing
Sent from my DROID X2 using xda app-developers app
I would suggest checking to see if it can be detected by Linux (lsusb). If not, your last available option may be to try and usbboot. I can't imagine what would cause the device to act such a way, but guess it's still remotely possible that the bootloader or bootloader partition got corrupted.
Hopefully, you're not looking at a bad eMMC.
I have a suggestion that your kindle has a bsod (black screen of death) hold the power button for 20 sec. and then press it another 3 sec. hopfuly i am right and your kindle will turn on. have this bsods 1-2 times per day.
It absolutely sounds out of power.
I know when my kindle isn't charged the light blinks like that. Maybe if the above suggestions don't work.. Try another charger
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I just realized you have a kf2 and not a kf1, so usbboot is obviously not an option for you. Disregard my previous statement.
You' already tried the hard shutdown and you say you've let it charge, but have you tried letting it charge while completely powered down?
Outside of that, I wish I had a better suggestion for you. It's definitely an odd situation.
I need some help with this issue. My tablet is stock out of the box. I have been using it since last Friday. But today I turned it off then after an hour later I turned it back on, it gets stuck at x logo. I really dont know what issue is called? I have tried to restart the tablet several times by holding the powerbutton, but it is still stuck at X logo, and I have tried to use recovery mode in bootloading, but I get no command message everytime.
If you don't have a lot on your nexus and don't mind wiping then just hold power and vol up, which will data wipe your nexus. I know when I first started my nexus it would go to the welcome screen and then bootloop if I didn't click the next button fast enough. But you're saying you've been using it so dunno.
or you could fastboot then flash twrp and try to clear cache/dalvik and see if that helps
mmikeee said:
If you don't have a lot on your nexus and don't mind wiping then just hold power and vol up, which will data wipe your nexus. I know when I first started my nexus it would go to the welcome screen and then bootloop if I didn't click the next button fast enough. But you're saying you've been using it so dunno.
or you could fastboot then flash twrp and try to clear cache/dalvik and see if that helps
Click to expand...
Click to collapse
Thank you for replying. I tried like you said holding vol up+power button, but I got no command message.
david84us said:
Thank you for replying. I tried like you said holding vol up+power button, but I got no command message.
Click to expand...
Click to collapse
First hold power+volume down to go to boot loader, then select recovery, then in recovery do power+volume up. I think that's the proper order.
Sent from my Nexus 7 using XDA Premium HD app
Just as a side-note, I've had 2 Nexuses 7 (the older versions) and BOTH of them did this to me when updating to a higher version of Android. I swore like a madman as I had to hard-reset the device thus losing nearly all my data. If anyone reports that this happens with the new Nexus, it might be the deciding factor for me to not buy it... unfortunately...
dark2099 said:
First hold power+volume down to go to boot loader, then select recovery, then in recovery do power+volume up. I think that's the proper order.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks, but I still get no command message screen.
david84us said:
Thanks, but I still get no command message screen.
Click to expand...
Click to collapse
Try using the freshly updated toolkit by WugFresh.
Sent from my HTC One using XDA Premium HD app
dark2099 said:
Try using the freshly updated toolkit by WugFresh.
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
Thank you for all inputs, but I am new/noob about these stuffs, and im still able to exchange, so I'm going to exchange for another one. Thank you everyone who tried to help me. Have a nice day.
It's really easy to do. I had the same issue as you and a factory reset corrected it. Just make sure to follow the steps and everything will be fine
dark2099 said:
Try using the freshly updated toolkit by WugFresh.
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
Wugfresh has the best root toolkit for Nexus, period.
dark2099 said:
First hold power+volume down to go to boot loader, then select recovery, then in recovery do power+volume up. I think that's the proper order.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I'm having the same issue since last Saturday when I picked it up. Still running stock and it just would not boot up and it seemed no one else was facing any problems. So I did fastboot unlock, it reset the device and cleared all data. Since then, I've been running stock, and I'm still facing the issue. I'm not sure if it's actually an issue with stock or not.
Just had this same problem on a brand new nexus 7 only a couple of days old. I really can't believe Asus/Google has these problems in 2013. Unbelievable.
Do you have a custom recovery installed?
Just happened to me very weird.
Sent from my Nexus 7 using xda app-developers app
Have you guys tried 1 click factory reset?
It happened to me with old. Exchanged it. And happened today in new one this time I was able to turn it off then try again and it booted. Started after 6 days of flawless use. Weird.
Sent from my SPH-L710 using Tapatalk HD
Team SXTP
Just happened to me...
I just had my SECOND one do this to me this morning. I bought the 2nd Gen Nexus 7 last week and it did this within an hour of using it (after an update). I took it back and got another one. This morning the second one did this after a simple reboot. I never had this trouble with my 1st Gen Nexus 7. I'm about to start trying the tips listed in this thread before I return yet another one. I'm wondering if this is the first reboot since the 4.3 update... maybe that is the issue.
Try Fully Charging?
Something similar happened to me on the first one I got, not sure if it will happened to the exchanged one since I only had it for a few days.
It happened after I shut it down one night, battery was about 80% or so. Next morning, I started it up and it actually loaded up fine but after a minute, it just rebooted, stuck at the X, then rebooted to the Google logo, over and over again. Did a factory reset and cleared the cache and still would get into the boot loop after 1 minute of successful boot up. Battery was about halfway when I decided to just charge it fully.
After the battery was fully charged, everything worked fine again. I suspect that the battery was run down next to nothing, but indicated that it was halfway. To me, that indicates a hardware issue so I exchanged it. I am wondering if they are using cheap batteries to keep the cost low. Not sure anyone else has seen this happened to them.
Anyway, if you watch the X, the colors move around, then suddenly stop after a while, it reboots again.
Same thing happened to me this moring around 3 a.m, shutdown and restarted and it was still stuck on the x screen. Tried wiping the cache from recovery and nothing. Had to do a factory reset in order to get passed boot screen. Tablet is working normally now.
Getting stuck on boot screen occasionally occur on 4.3. It seems like an OS issue not the hardware issue. I have seen it once or twice on my stock non-rooted Nexus 4 running 4.3. Never happened on 4.1~4.2.
On the other hand, if you have rooted your 4.3 device, the chance of ****up at boot rises dramatically. The toolkit is, while an admirable work, not perfect and you have no one but to blame yourself.
My Kindle Fire is bricked. The problem is that the Kindle Fire cannot even TURN ON, so do not mention get connected to computer and let Kindle Fire Utility find it.
I read lots of solutions and finally I bought a factory fastboot cable, it suppose to boot the device into Fastboot, but still nothing happened to the device. The screen is still off.
So, is there any way to save this bricked Kindle Fire? Thanks soooooo much!
Are you sure its not deep sleep of death? Did you try holding the power button for at least 25 seconds and then letting go and pressing the power button again once to see if it turns on?
Sent from my Nexus 7 using Tapatalk
SwoRNLeaDejZ said:
Are you sure its not deep sleep of death? Did you try holding the power button for at least 25 seconds and then letting go and pressing the power button again once to see if it turns on?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes, I have done this again after seeing your answer, but it still does not work.
Does anything happen after holding the power button down for thirty seconds, then plugging in the charger?
Sent from my SM-T210R using Tapatalk
jlshady00 said:
Does anything happen after holding the power button down for thirty seconds, then plugging in the charger?
Sent from my SM-T210R using Tapatalk
Click to expand...
Click to collapse
Unfortunately, no. And I've tried many times.
ViolaDante said:
Unfortunately, no. And I've tried many times.
Click to expand...
Click to collapse
Where you able to figure this out? I'm in the same situation. I accidentally yanked the cable out while it was installing recovery and it just went black. I was able to turn it off....big mistake.... but can't turn it back on. I've tried using the firekit too...
SilviaIchigo said:
Where you able to figure this out? I'm in the same situation. I accidentally yanked the cable out while it was installing recovery and it just went black. I was able to turn it off....big mistake.... but can't turn it back on. I've tried using the firekit too...
Click to expand...
Click to collapse
I believe you have a different problem then ViolaDante, but we'll find out.
Did you try the aforementioned attempts to recover the kindle?
(Hold down power button for >20 seconds?)
And @ViolaDante, it sounds like a battery problem.
Sometimes there are occasions where the battery drains below the required amount to make it turn on; as it is a stupid setup, there is actually a need for a small amount of battery left to turn on, even if you are wanting to charge it. I would do a search on this if I were you. I will try to find a useful post for you, but no guarantees.
Sent from my Nexus 7 using Tapatalk
jma9454 said:
I believe you have a different problem then ViolaDante, but we'll find out.
Did you try the aforementioned attempts to recover the kindle?
(Hold down power button for >20 seconds?)
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I have. I've tried all kinds of lengths of time and kept it plugged in overnight... nothing. What do you think could be wrong?
SilviaIchigo said:
I have. I've tried all kinds of lengths of time and kept it plugged in overnight... nothing. What do you think could be wrong?
Click to expand...
Click to collapse
I don't know...
Does anything happen when you plug it into the computer?
----EDIT----
Try what this person does to get their kindle to turn on, and see if yours turns on:
http://forum.xda-developers.com/showthread.php?t=2653387
Sent from my Nexus 7 using Tapatalk