My Kindle Fire, running CM7 and GoEx Launcher, froze today while browsing the internet. It is stuck on the last page I visited, no screen or power button response at all, and when I try to reboot using adb, it just tells me the divice is not found. Any ideas? I've tried remounting, rebooting, even just asking for log information and adb refuses to recognize my device. I'm not too savvy with adb, but I have used it to reboot the device before when I got it stuck in a boot loop, so I know basic commands and I know adb works. I'm not sure what else to do though. Any suggestions or ideas would be much appreciated. Thanks.
nogloww said:
My Kindle Fire, running CM7 and GoEx Launcher, froze today while browsing the internet. It is stuck on the last page I visited, no screen or power button response at all, and when I try to reboot using adb, it just tells me the divice is not found. Any ideas? I've tried remounting, rebooting, even just asking for log information and adb refuses to recognize my device. I'm not too savvy with adb, but I have used it to reboot the device before when I got it stuck in a boot loop, so I know basic commands and I know adb works. I'm not sure what else to do though. Any suggestions or ideas would be much appreciated. Thanks.
Click to expand...
Click to collapse
Hold down the power button on the Kindle Fire for about 20 seconds to shut it off and then turn it back on.
Thanks!
kinfauns said:
Hold down the power button on the Kindle Fire for about 20 seconds to shut it off and then turn it back on.
Click to expand...
Click to collapse
Well bloody hell I fell dumb. I guess I just wasn't holding the power button long enough. I though it wasn't responding. When I slowed myself down and counted one mississippi, ect. it worked haha! Any idea why that happened and why adb wouldn't recognize the device? No other screen controls or the power button were responding. Usually if I get stuck somehow, I can just type "adb reboot" into the terminal and it fixes it.
On a separate note, my device sometimes reboots spontaneously for no apparent reason. I haven't been able to see a pattern anyways. Any idea if these incidents are related?
nogloww said:
Well bloody hell I fell dumb. I guess I just wasn't holding the power button long enough. I though it wasn't responding. When I slowed myself down and counted one mississippi, ect. it worked haha! Any idea why that happened and why adb wouldn't recognize the device? No other screen controls or the power button were responding. Usually if I get stuck somehow, I can just type "adb reboot" into the terminal and it fixes it.
On a separate note, my device sometimes reboots spontaneously for no apparent reason. I haven't been able to see a pattern anyways. Any idea if these incidents are related?
Click to expand...
Click to collapse
If it's not a frequent occurrence, I wouldn't give it a whole lot of thought. It's just one of those things where several non-obvious things line up and the device gets the hiccups. Every few days, my KF with CM7 won't turn the display back on after sleeping, but it wakes up if I give it a jolt of power with the USB cable. Solar flares? Cosmic rays? I dunno.
If it really bothers you or it happens a lot, try wiping the caches or even reflashing the ROM.
kinfauns said:
If it's not a frequent occurrence, I wouldn't give it a whole lot of thought. It's just one of those things where several non-obvious things line up and the device gets the hiccups. Every few days, my KF with CM7 won't turn the display back on after sleeping, but it wakes up if I give it a jolt of power with the USB cable. Solar flares? Cosmic rays? I dunno.
If it really bothers you or it happens a lot, try wiping the caches or even reflashing the ROM.
Click to expand...
Click to collapse
Yeah, I guess it's not a big deal. Thanks for your help though.
Related
I'm having some serious issues with my phone. This morning the battery was suddenly drained completely, don’t know why yet. Then after charging the phone a bit and rebooting it, it constantly goes into driving mode and starting the voice command application. The most strange thing however is that when I choose to power off the phone, it shuts down but then automatically reboots.
I know I should try factory reset, but anyone else had this problem?
(I have original firmware and the phone isn't rooted)
EDIT:
Doing a hard reset seems to have solved the problem.
Maybe your power button is broken (constantly pressed)? Did the phone get wet?
I have not heard of this. I've heard of bootloops and the phone rebooting when trying to power off but thats usually due to custom roms and people flashing over other custom roms which causes conflict. I think factory reset may be the only option. However, with the Galaxy S there used to be a way to get into safe mode. I beleive you'd hit the menu button as soon as you saw the Galaxy S boot logo. I haven't heard of a safe mode yet for SGS2 but perhaps someone can confirm if its available in this model?
If you can still get into settings of the phone when its on, I'd try going into Settings > Applications > Manage Applications and clearning data for voice commands
It almost seems as though your phone is registering home button being clicked thereby turning voice mode on and also turning it back on after a power off.
delinne said:
I'm having some serious issues with my phone. This morning the battery was suddenly drained completely, don’t know why yet. Then after charging the phone a bit and rebooting it, it constantly goes into driving mode and starting the voice command application. The most strange thing however is that when I choose to power off the phone, it shuts down but then automatically reboots.
I know I should try factory reset, but anyone else had this problem?
(I have original firmware and the phone isn't rooted)
Click to expand...
Click to collapse
Hi,
I was have exactly same problem, reset don't resolve my issue.
Solution was to replace my phone.
Thanks for the help, gonna try factory reset first. But this doesn't look like a software problem, so probably gonna need to replace it
delinne said:
Thanks for the help, gonna try factory reset first. But this doesn't look like a software problem, so probably gonna need to replace it
Click to expand...
Click to collapse
Well this is a strange problem. Is it possible a bread crumb got under your buttons? Or some case is so tight it is pressing on some buttons?
Don't have a case around it, but the power button isn't stuck I think because wouldn't the menu for shutting down the phone etc. appaer constantly? And if it's something under the buttons then it is just bad design, had the phone only a couple of weeks.
delinne said:
Don't have a case around it, but the power button isn't stuck I think because wouldn't the menu for shutting down the phone etc. appaer constantly? And if it's something under the buttons then it is just bad design, had the phone only a couple of weeks.
Click to expand...
Click to collapse
I had the same problem mate. And that was exactly what I thought, I actually started a thread on this problem about 2 weeks ago. Was really strange, people told me to take it back. But What I did was factory reset on the phone. Which still didn't completely solve my problem. So I left the battery out the phone over night. The most annoying thing was, the screen kept turning on, like something was being pressed, can't have been the middle button, because the menu would have come up, it didn't do that. And then to make matters worse the tap to speak driving mode kept coming up.
I then took out the battery and left it out over night. Put it back in, in the morning. Charged it up. Didn't do it again.
Hope that helps. Try it.
Ok thanks, I will try it. It is really a strange problem as you say. After the factory reset the problem showed up again but not as often as before. Also after upgrading to latest firmware today, according to the battery monitor android OS is using 45%, that looks really strange to me.
I used it this morning to listen to music while getting ready for work just like any other day. When I turned it off it has about 65% batter left and I set it on my counter. Came home at lunch and it would not turn on. I plugged in the charger and got no response from the device, no orange light nothing.
I brought it to work and it has been plugged in for almost an hour now and it still has no orange light on it and it will not turn on. Any suggestions for what to do or what might have happened?
-Eric
I've had that happen twice with mine so far the fix is easy though:
Press and hold the power button for 20 seconds.
Press the power button again and it should come one.
Hopefully that fixes it for you.
mikbe.tk said:
I've had that happen twice with mine so far the fix is easy though:
Press and hold the power button for 20 seconds.
Press the power button again and it should come one.
Hopefully that fixes it for you.
Click to expand...
Click to collapse
Dude you are a FREAKING life saver!! I really thought it was dead, but when I did this it turned on just fine and was almost fully charged as well. Wonder what causes this? Any ideas?
Anyway, thanks!!
-Eric
EABonney said:
Dude you are a FREAKING life saver!! I really thought it was dead, but when I did this it turned on just fine and was almost fully charged as well. Wonder what causes this? Any ideas?
Anyway, thanks!!
-Eric
Click to expand...
Click to collapse
I would think it's some kind of problem, regardless. Software or hardware, who knows. Basically the 20 second power button as I understand it is just a hard reset akin to a battery pull.
Felnarion said:
I would think it's some kind of problem, regardless. Software or hardware, who knows. Basically the 20 second power button as I understand it is just a hard reset akin to a battery pull.
Click to expand...
Click to collapse
It's definitely a problem but it's not a problem with just his Fire; it's happened to me twice. Once when I turned off the Fire while playing a game (not a hard power off, just a quick power button tap) and again when another app crashed.
This happens to some other android devices. I think its an issue in some gingerbread builds where the device wont wake from sleep.
This has been happening to me frequently since the 6.2 update.
just for the record I too have experienced this problem. freaked me out that is for sure. glad to see others have seen this, and hopefully it will be fixed. at least its pretty easy to resolve the issue when it occurs.
it's useful topic for me.
Kindle Dead
This is happening every day now. Is there a fix? I'm not sure what the frequency is or why, but once or twice a day is becoming the norm...it's frustrating
Rooted Kindle
Go Launcher
Android market Apps, etc.
Try disabling wifi and see if the problem goes away.
kindle dead not wifi related
Thanks for the suggestion. I disabled wifi and waited 3 hours; dead Kindle. I'll try anything...please help as it's quite a nuisance.
Thanks
Is this happening to only rooted Kindle's? I'm getting one from the wife for Xmas and was wondering if this is happening to stock fires as well.
Sent from my Nocturnal E3D using Tapatalk
This only seems to happen to be when i am not using the factory supplied power supply. You guys still getting this using the factory plug?
My Kindle totally dead. I can't repair it. I can't get acces to adb shell. Nothing. this is really sad.
Dead Kindle
Try holding down power button 20 secs then re-press it...works for me
I had this happen to me while I was in a work meeting on Friday. Thankfully I found this thread so I learned about the 20 second hold down thing. It worked like a charm and I have only had it happen once. For the record I am not, nor have ever, rooted the Fire.
It was pretty discouraging to be sitting in the meeting with a "dead" Fire and unable to look at the manual to see how to factory reset it because, well, the manual is included in the Fire....
man, I hate irony.
Same problem here. Several times it has been dead now. This morning again and the power had fallen without showing any steps for about 10 per cent. Wifi was switched off.
Any more ideas?
Now it happend two times in a row. After this night again it was "dead" in the morning. Are there any ideas what might be wrong with the device? (rooted, wifi off, ADW launcher, but not activated, some google apps like market)
Any ideas what could be done?
It only happens to mine (rooted, adb, Go Launcher) when I put it to sleep while it is in "Go Launcher", if I put it to sleep from Kindle Launcher it wakes right up. Hope this helps.
Bruce
hey guys
was using my nexus 4 5.0.1 (stock, bootloader unlocked, not rooted) with no issues this morning. then suddenly i can launch google music. the app launches and i get a white screen with nothing on it. so eventually the app crashes. then i try launching messenger, good play, and many other apps with the same result. my phone begins to get very slow and laggy, nearly non responsive. i restart my phone and i get no service. restart my phone again and a few apps like chrome will launch, and whatsapp aparently, but ive tried so many other apps that will not launch or hang on launch. any ideas? is it a failure of sorts or will a wipe fix the issue?
edit: i think its helpful to note this is a refurb phone. there have been times when my phone suddenly restarts (normal for android) and other times when the screen just goes off and i have to hold the power button till i get red blinks or sometimes i have to plug the phone into the wall for it to restart.
edit2: just restarted my phone connected to the wall. wifi wont even turn on. i waited 60s and it finally switched on. its like the phone has gone limp lol. it wont connect to my mac anymore either ("try reconnecting or restarting your device").
It sounds like your memory chip is failing. I would advise you to extract as much valuable data off of the device while you still can. Then we can troubleshoot to see what the problem really is without having to worry about important data loss.
lolcakes203 said:
It sounds like your memory chip is failing. I would advise you to extract as much valuable data off of the device while you still can. Then we can troubleshoot to see what the problem really is without having to worry about important data loss.
Click to expand...
Click to collapse
i did a full factory reset from terminal. im not having any issues anymore.... yet. however im still concerned about potential imminent memory/storage failure.
Alright that's good to hear. Keep us posted.
I recently got faulty Xperia XA2 in my hands. Everything is brand new and works perfectly, except device shuts down after short period of inactivity.
On stock ROM it shuts down if the screen is turned off for ~10 seconds, or if I do not do anything with it for ~30 seconds, but it stays on if I run video in browser or use a music player.
I managed to flash TWRP and some custom ROMs. While in recovery, device always stays on, no matter if screen is locked or anything else happens, as it should be.
Now it has Lineage 17.1 installed and it shuts down just like on stock ROM.
Another thing to mention is that it doesn't exactly shuts down in those cases: after blackout, device restarts on short press on power button (it should only wake on long press if it is turned off conventionally) and blinks with green LED indicator.
And also, it doesn't turn off while charging
I would appreciate any help with figuring out what causes shutdowns and any ways to solve this. I have a few theories I cannot confirm, but I need more data.
MilesSeventh said:
I recently got faulty Xperia XA2 in my hands. Everything is brand new and works perfectly, except device shuts down after short period of inactivity.
On stock ROM it shuts down if the screen is turned off for ~10 seconds, or if I do not do anything with it for ~30 seconds, but it stays on if I run video in browser or use a music player.
I managed to flash TWRP and some custom ROMs. While in recovery, device always stays on, no matter if screen is locked or anything else happens, as it should be.
Now it has Lineage 17.1 installed and it shuts down just like on stock ROM.
Another thing to mention is that it doesn't exactly shuts down in those cases: after blackout, device restarts on short press on power button (it should only wake on long press if it is turned off conventionally) and blinks with green LED indicator.
I would appreciate any help with figuring out what causes shutdowns and any ways to solve this. I have a few theories I cannot confirm, but I need more data.
Click to expand...
Click to collapse
Change the phone ...
cojocar.andrei said:
Change the phone ...
Click to expand...
Click to collapse
Although I appreciate such straightforward solutions, sadly, it's not an option for me
MilesSeventh said:
Although I appreciate such straightforward solutions, sadly, it's not an option for me
Click to expand...
Click to collapse
From what you're describing probably this is the only solution if this happens with stock rom ...
Well, I sent it to service, actually. I tried to check logs via adb logcat, but there were no clues, they just stop going without any pattern. Then I gone lower and checked kernel logs, but they were clear, too, so I suggested it is related to power supply so I stopped and contacted repair service.
MilesSeventh said:
Well, I sent it to service, actually. I tried to check logs via adb logcat, but there were no clues, they just stop going without any pattern. Then I gone lower and checked kernel logs, but they were clear, too, so I suggested it is related to power supply so I stopped and contacted repair service.
Click to expand...
Click to collapse
If you don't mind, could you tell how the service has treated you?
aeolist said:
If you don't mind, could you tell how the service has treated you?
Click to expand...
Click to collapse
Well, they decided to change the mainboard (still in progress though, guys are working like morons). I think they would have it covered by warranty, if I had any.
Hey everyone, I've run into quite an issue.
My phone was in the charger working very well, I went away for only a few minutes and when I was back it was totally unresponsive.
I've tried to do a forced reboot, double click the screen, try to boot into recovery and fastboot. But so far no luck. Even upon inserting it to my PC and look at device manager, it doesn't show anything, not even when unplugging it and plugging it in again. Also have tried different adapters and so on.
I'm quite unsure what could cause this happening out of nowhere.
Could it perhaps be the bettery giving up? If any of you are able to come with suggestions before going out and getting a new phone, I'd be very greatfuld.
I'm running pixen-os 10.0. So far never experienced any issues, and been running it a long time.