I have a weird issue that just started a few days back. I was on rooted 1.1 when the "Do you want to shut-down?" window would randomly pop up. If I did nothing, the unit would completely power off. If I hit the power button quick enough, the screen would shut off (putting it into standby) and the unit would not power off. I could then press the power button, swipe to unlock, and continue where I was.
I thought maybe it was related to me modifying the db to disable the auto-update from 1.1 to 1.2. However, I updated to 1.2 yesterday evening and rooted it as well. Unfortunately, the "Do you want to shutdown?" window started popping up again all by itself.
It's almost as though the unit thinks the power button is being pressed (and held). I tried squeezing the case around the edges, wiggling the power button, cleaning the screen, etc. There doesn't appear to be any particular reason why this is happening. I'm going to try wiping the device and flashing 1.2 again, unrooted, and see if the issue persists.
Does this sound like a hardware issue that requires replacement?
Restore your nook to stock and go to B&N and get your nook exchanged.
It definitely seems like a hardware fault.
I had the same problem with my first NC. I would be reading, doing whatever and the screen would blur and shutdown menu would appear. If I did nothing (and even if I hit cancel) it would shutdown as if the power button was just being held.
I had used the autonooter with 1.1 at the time, though I believe it was pure coincidence since the problem persisted after completely restoring to stock. My advice would also be to restore to stock and exchange it.
I consider myself lucky because I tried multiple times to restore to stock but would get interrupted since I had this problem even on boot. It was common for the device to interrupt boot so many times (>8 times) because the power button would get "stuck" that it would attempt to reflash. The button never felt physically stuck though.
I finally reverted to stock successfully, took it to B&N, showed a manager, during which the NC failed to boot, shutdown automatically, etc. and I had it exchanged no problem.
2nd NC works great though.
Thanks for the input - I will restore to stock tonight and take it in tonight or tomorrow.
I called one store - their "guru" isn't in until Tuesday.
I called another nearby store and the guy on the phone sounded irritated, brushed it off as a registration issue, and finally made it very plain that they will simply mail it off to the repair center if I bring it in...
After going back to stock 1.2 without root, the power-off message issue mysteriously disappeared. I've used it for 2 days now and have yet to see the message pop up.
Is it possible that it's software-related??
Related
My brothers phone was dropped (apparently hes a bit clumsy!) Whenever he was texting using the keyboard, it was making some very strange characters on the screen, whenever he would push 1 key, several would appear, etc.
't' ='d 's03' etc... stuff like that.. obviously thought a reboot would fix the issue. So when we rebooted the phone, it turned out that it couldnt get past the g1 screen and was stuck at the Triangle with the yellow exclamation point. Pushing ALT+L showed the recovery screen. We went through the appropriate options and held down back + home for 25+ secs to get it to reboot. It rebooted fine and worked for an hour or so, until the Voice Search just kept popping up as if he was asking it to, so we tried to reboot the phone again and do the recovery thing, this time it wouldn't get past the recovery after holding down home + back. I can't push back + home either to get it to restart, so I'm thinking the home key may be broken or stuck.
Any thoughts on this issue or has anyone else experience such? He'll more than likely be sending it in today since its still under warranty and has NOT been rooted.
Thanks!
same thing happened to my first g1..its a hardware issue send it in
Was hoping it wasn't a hardware thing, but so be it. Thanks for the heads up.
My phone has be working fine until it ran out of battery and now doesn't boot properly. I have fully charged the battery overnight but it still not functioning. It appears to boot, vibrates several times in a sequence(buzz---------------------buz-buzz-buzz). Sometimes it repeats this in a loop. I get the login screen briefly and can unlock, but the apps are frozen, or will open then screen goes black and I can't turn on the display. The nav buttons stay lighted. I've removed the battery several times but same result. Sometimes when I hold down the display button I get the
I rooted the phone weeks ago and running stock froyo -- no other changes and no recent changes so this doesn't make any sense other than a hardware failure.. possibly the internal SD. Any suggestions are appreciated.
Something like that happened to my friend's vibrant. His phone was completely stock - no root, no custom rom. One day it just decided to start going in to boot loops for no apparent reason. Battery pulls didn't help. He tried doing a factory reset from recovery and ended up in even worse shape.. The phone would boot into some debug screen and just die there. We figured it was probably some hardware problem, took it back to T-mo and got a replacement.
All of the buzzing was different things force closing, I would flash back to stock. And see if it still does it. Also this is not development related so I will move it over the Q&A
I was able to disable gps when the phone had a brief moment of clarity. Once I did that it stopped having spasms, so possibly a bad gps??
Did a factory reset and the phone is back to normal
Build date 1007 - in service August 2010.
I've been running Pinnacle 1.2 (been on it since v1.0).
Just moments ago I've found the power button to be unresponsive. This happened after I rebooted into recovery, sticking me there for a while.
I was stuck in a recovery loop- pull batt, reinstall batt, automatic boot back into recovery.
Somewhere in the process of trying different combinations of battery pulls with cable installs and volume up/down holds (trying for download mode) I ended up finally launching the ROM, but w/o a power button all I can do is pull the battery, and the moment I do, the phone automatically wakes w/o even touching the power button (which is totally new to me).
Any input would certainly be appreciated.
My first order of business is to flash to stock (JF6, bootloaders and all if all else failed) but being that it automatically boots when the battery is installed I don't think even a jig would help...or is the beer steering me wrong?
I am confused. You can go back to stock or no?
I cannot get into download mode. The only way to power the phone off is via battery pull.
I cant flash anything from recovery because it says the power button is disabled (it is).
As I put the battery back in the phone boots immediately...I mean the at&t screen lights up my palm before I put the cover on or even flip the phone over.
Use an app from market to enter download mode? system toolbox free is one
Used Odin to go back to stock KF1 and still no power button. Now System Toolbox won't work w/o root/busybox. lol
Once my phone falls asleep I can't wake it back up.
It may seem obvious that the power button is physically broken but I don't know why the phone boots up as soon as the battery is installed...that was never the case before this issue came up.
watsa? Anyone?
Can anyone else shed some light on what would make the phone boot when the battery is inserted (happened at the same time the power button became unresponsive), essentially denying me the opportunity to get to download mode.
beyond this point I am consfused myself. I initially blamed Pinnacle and thought going back to stock might fix it which obviosly didn't happen.. It seems like your power button is always "pushed" so as soon as you pop your battery in phone reboots..
watsa said:
beyond this point I am consfused myself. I initially blamed Pinnacle and thought going back to stock might fix it which obviosly didn't happen.. It seems like your power button is always "pushed" so as soon as you pop your battery in phone reboots..
Click to expand...
Click to collapse
On a second thought if it was the case then power button should have messed up functioning of your phone even after powering on. So I am consfused more. Need a hardware expert here
I'm preparing myself to deal with my beloved phone finally letting me down after all the success we've had...it's just really bad timing as I'm currently unemployed, broke and only 13ish months into a 48 month contract.
Ok, so after a physical tear down it seems to be in the external plastic of the button itself?
After removing the outer case and reinserting the battery I noticed it did not automatically boot up. I pressed the actual power switch/button that is connected to the board and the phone then powered up. I let it finish booting and held the power button down and the power options menu popped up. I clicked Power Off and it shut down fine.
This means it certainly isn't Pinnacle ROM (never thought it was, personally), or software related at all. Now to figure out what is going on between the plastic external power button and the power switch on the board.
Edit: Nothing was there? I blew out the dust reassembled the phone and now it works fine. Weird.
So. My Moto G is completely un modded, not rooted, and is exactly stock how I bought it and haven't changed any of the software. My Moto G has been getting slower in the past couple of months with everything going slower than usual. I bought my phone in February 2014.
Yesterday while I was at school, in my pocket I had my phone. I felt random vibrations in timed cycles. So I pulled out my phone and had a lol at it randomly rebooted but came back to the home screen. As I started to use it just to send a couple of messages it rebooted again but this time after the reboot animations they just went on and on, what I've found out to be called a boot loop.
So I went home did some research and figured I would have to factory reset. I couldn't get into the phone therefore I had to do it externally. I got the the menu thing ( I think it's called fast boot menu ) and I wanted to select newer bootup or power up just to see if that would possibly stop the boot loop. I selected it and got into my phone, into setting and factory erased my phone.
Well I factory erased my phone and re installed the apps I on,y essentially use or NEED such a social media, within this time there was no unusual activity. Shortly after my phone randomly rebooted ( after downloading the apps ) and turned off, and then went in to the former boot loop! I was furious!
Well here I am, left it overnight for charge and it's been looping for 10 hours. I tried going back into the fast boot menu, the first time I got into it this morning I selected recovery in hope to reset it, however the screen said no command with the android and the exclamation point. The second time I got into the menu I tried 'Factory' and it just rebooted and back into the cycle.
At one point I did get into my phone however shortly after that guess what happened, it turned off and rebooted. And back into the vicious cycle.
I am led to believe it's the power button that's causing the problem ( correct me if I am wrong ) as when I did manage to get I to the phone I did try pressing the power button to investigate this and on some occasions in did lock the phone but in several others it displayed the power off popup and then turned off shortly after indicating that I was holding the button down which I definitely wasn't doing.
So where would I go from this? Do I call Motorola, try flashing a stock ROM ( it's completely stock ATM , I don't know how to do this so if I have to do this can you please explain briefly ) or try going back into the fast boot and go into recovery and try and get rid of no command ( if I can, and how ? ).
Please any help would be very appreciated!
Thanks in advance.
PS you don't think it's the back cover that's doing it because it took that off last night '
kevlarpatel said:
Do I call Motorola, try flashing a stock ROM
Click to expand...
Click to collapse
Since your phone is completely stock, don't start tempering with it now. Just return the phone. But you have to act quick, warranty is about to expire.
doppelhelix said:
Since your phone is completely stock, don't start tempering with it now. Just return the phone. But you have to act quick, warranty is about to expire.
Click to expand...
Click to collapse
Hi, I had a look online and came across a forum post saying it was a jammed or sticky power button and the poster stated to hit the power button side of the phone on a desk a couple times and it will go back to normal. I'm glad to say it did work after I hit it a couple times, as fast as ever now due to the reset!
I was wondering if I call Motorola would they give me a free new moto g out of it, as I see it as an opportunity to do so, or will they just prompt me to send it so they can repair it under warranty? Is it worth calling ?
Sorry if this is the wrong place for this. Feel free to point me in the right direction if it needs moved.
Fifth gen Kindle Fire, running Fire OS 5.3.3.0. All current updates, OEM otherwise.
It very often goes into a state where the System & Notification sound bar keeps beeping, like it's constantly trying to turn the volume the entire way up, but the button is not being pressed. The button does not appear to be stuck. When I press the volume down, it'll go down but then go back up on it's own when I let it go.
I've tried a factory reset. If I put it in Do Not Disturb mode, the System & Notifications drop down box still appears at the top of the screen, but it's grayed out.
At the same time, the power button stops functioning properly. It does not lock the screen, but if I hold the button it eventually it will hard shut down the device, and then start in Safe Mode when I power it back up.
Something to note is that it behaves this way often, but not constantly. There are brief periods where it is 100% functional. Just today I turned it on, ran some updates, and all was normal for an hour or so. After that it started with the volume nonsense.
It has barely any use since I purchased it forever ago and was always taken care of, so I don't suspect hardware unless something is defective from the factory. It has done this for as long as I can remember, but it literally saw almost no use for the first year and by the time I noticed it, the warranty was expired.
Any thoughts or suggestions?
SlightlyOpaque said:
Sorry if this is the wrong place for this. Feel free to point me in the right direction if it needs moved.
Fifth gen Kindle Fire, running Fire OS 5.3.3.0. All current updates, OEM otherwise.
It very often goes into a state where the System & Notification sound bar keeps beeping, like it's constantly trying to turn the volume the entire way up, but the button is not being pressed. The button does not appear to be stuck. When I press the volume down, it'll go down but then go back up on it's own when I let it go.
I've tried a factory reset. If I put it in Do Not Disturb mode, the System & Notifications drop down box still appears at the top of the screen, but it's grayed out.
At the same time, the power button stops functioning properly. It does not lock the screen, but if I hold the button it eventually it will hard shut down the device, and then start in Safe Mode when I power it back up.
Something to note is that it behaves this way often, but not constantly. There are brief periods where it is 100% functional. Just today I turned it on, ran some updates, and all was normal for an hour or so. After that it started with the volume nonsense.
It has barely any use since I purchased it forever ago and was always taken care of, so I don't suspect hardware unless something is defective from the factory. It has done this for as long as I can remember, but it literally saw almost no use for the first year and by the time I noticed it, the warranty was expired.
Any thoughts or suggestions?
Click to expand...
Click to collapse
You can try to reload (sideload) FireOS via the stock recovery menu to rule out a software glitch. However, based on symptoms I suspect the board holding the buttons and/or associate ribbon cable is the culprit. Not much you can do about either unless willing to crack open the case.
I wouldn't mind opening it up to replace some things, but I was hoping that based on it working fine for 20 minutes, and then out of nowhere showing problems, that it was software related. I've had it turned off since I posted, fired it back up now, and it's working as it should. I suspect within the hour it'll be back to broken, though.
Edit: Also, as mentioned, the power button stops behaving normally when this happens as well. I haven't looked into the layout of the buttons internally, but I would think that the volume and power buttons would be on separate ribbons leading to separate places?
SlightlyOpaque said:
I wouldn't mind opening it up to replace some things, but I was hoping that based on it working fine for 20 minutes, and then out of nowhere showing problems, that it was software related. I've had it turned off since I posted, fired it back up now, and it's working as it should. I suspect within the hour it'll be back to broken, though.
Edit: Also, as mentioned, the power button stops behaving normally when this happens as well. I haven't looked into the layout of the buttons internally, but I would think that the volume and power buttons would be on separate ribbons leading to separate places?
Click to expand...
Click to collapse
You can view the internals on a self-repair site such as iFixIT or by searching YouTube. The delay prior to acting up suggest heat may play a role. Not necessarily overheating, just the normal warming that electronics emit with use. Good luck.