OK, it's probably happened to some people - you're running CM7 from an SDcard installation, the screen is off, and you just pop the card out because you think it's off.
Then the screen comes on, it tries to show a force close message that gets garbled, and then you have to hold the power button to shut it off.
You go to turn it back on, and you can't get the power button to work, no matter how many times or how long you press it.
The solution?
Plug it in to the charger. As soon as you plug the power cable in that's connected to a power outlet, it'll cause the device to turn on.
If you have a stock nook color, and never installed anything on it directly, it'll boot to the default barnes and noble operating system like normal, and then you can power down and put your SD card back in and power up.
I was going crazy and thought I screwed it up permanently, this is the second time i've done this in the last few months, and figured i'd throw this P.S.A up in case anyone else lands in a similar circumstance and thinks it's the end of the world.
That is all.
Just a logical thinking, you are running CM7 off the uSD and why on earth you remove it from the NC while it's running (sleep is considering running)?
Think about your computer at home, Windows 7 OS installed on your hard drive, and while it's in the hibernate mode or sleep mode or whatever, you for some reason, decide to pull it off and expect it awakes normally?
votinh said:
Just a logical thinking, you are running CM7 off the uSD and why on earth you remove it from the NC while it's running (sleep is considering running)?
Think about your computer at home, Windows 7 OS installed on your hard drive, and while it's in the hibernate mode or sleep mode or whatever, you for some reason, decide to pull it off and expect it awakes normally?
Click to expand...
Click to collapse
Negative, just an absent minded moment with switching back and forth between different installs.
I have a couple of cards with different versions of android, and didn't realize it was on before I went to swap them out.
Wasn't expecting it to run normally after popping the card, but for the life of me could not get it to turn back on the first time it happened, until I plugged the power cord in.
Figured i'd share in case anyone else ended up there and didn't realize they could get it to boot by plugging it in.
Related
Hi everyone,
I have had some trouble with my Vogue. At first it simply would not turn on. I would get a red light when I plugged the phone in to charge it. I have been using my old phone for several months now. Today I went out to the nearest Bell store and it seems like anything new is going to cost in the $500 area because I still have 1 year left on my contract. So I have renewed my interest in getting my Vogue working again
The original thread describing my original problem (with the red light) is here:
http://forum.xda-developers.com/showthread.php?t=546674
I purchased a new battery and now when I plug it in on the USB I can turn it on (no lights, red, green, or otherwise) but it does turn on. It boots up just passed the blue “Bell” splash screen and then reboots. It does this over and over again.
I am able to get into the boot loader screen by holding down the power and camera buttons and pressing the reset button.
Any ideas on what I can do? Any suggestions are welcome.
Regards,
The Fish
Reflash your rom when you get to the bootloader screen.
If you are unlocked flash nfsfan or whatever, just rename the nbh file to 'VOGUIMG.nbh' and it will flash.
If you were on stock you'll need the nbh from the stock package.
OK, here is an update
I have tried a hard-reset (press Send and End buttons at the same time and press reset button). This worked but the phone still kept rebooting. Tried the original battery, phone booted a little further up before rebooting.
I got the phone into boot loader mode and left it plugged in on the USB cable for a few minutes. This time when I rebooted I became ecstatic. I got all the way to the “align your screen” stage before hearing the “phone is dying” sound and the phone turned off. So here is what I think may have happened:
I have long lost the home charger kit. So I have, for as long as I can remember, been charging it by plugging it into a PC via the USB. This is fine except that Windows will only power the USB for the device if there is a driver installed. The device/phone looks different to Windows when it is in boot loader mode then when it is fully booted up. If the device is so dead as to not even have a flicker of life I don't think Windows sees it.
I have been doing this tonight under Linux. Linux seems to either have the driver, a more generic driver or powers the USB all the time for any device. I noticed this same behavior when charging my Moto Razr the same way. Under Linux it just worked by plugging it in. Under Widows I had to install the driver. So maybe here is what happened.
The battery got SO dead that it was not able to boot the phone up far enough for Windows on the PC to see it, recognize it and begin powering the USB port. Perhaps leaving the phone in bootloader mode and plugged into a Linux box got the battery a little more charged till I got to the point of being able to align the screen.
Anyway, I am more then ever convinced that this is some kind of battery/power issue. The phone is now lying here powered up and charging (already at 20%). The carrier customizations ran, rebooted while I crossed my fingers, and came back up. I even called *BELL and got a message about activating my phone. Tomorrow if the phone is charged up and behaving normally I will get an ESN change done and be back in the world of decent smartphones. Man have I ever missed my Google Maps
The next step is to flash a more up-to-date ROM... if I dare mess with a good thing.
The Fish
So I have been using my HD2 with Android installed in the internal memory for at least 6 months with no issues. My HD2's battery life has dwindled down to being about 3 hours, so I ordered a new one. I popped in the new battery and plugged the phone in, and now the phone will continuously reboot itself while plugged in, when it reaches the Dark Forces Team screen. I installed the old battery, and the same thing happens. The phone will not turn on unless it in plugged in. Also is there anyway to charge the phone while it is off? When you plug it in, it turns itself on automatically. Lastly, I don't know if this affects anything, but I did drop the phone from about 3 feet with the charger in, and now the plug has to be pushed in to get charged. Thanks for all your help guys.
simplesauce said:
So I have been using my HD2 with Android installed in the internal memory for at least 6 months with no issues. My HD2's battery life has dwindled down to being about 3 hours, so I ordered a new one. I popped in the new battery and plugged the phone in, and now the phone will continuously reboot itself while plugged in, when it reaches the Dark Forces Team screen. I installed the old battery, and the same thing happens. The phone will not turn on unless it in plugged in. Also is there anyway to charge the phone while it is off? When you plug it in, it turns itself on automatically. Lastly, I don't know if this affects anything, but I did drop the phone from about 3 feet with the charger in, and now the plug has to be pushed in to get charged. Thanks for all your help guys.
Click to expand...
Click to collapse
1- dropping your phone with damage may certainly have caused this. did the problems start right after?
2- with magldr you cannot charge with it turned off.
3- try to boot into bootloader. is that possible?
I didnt notice anything different after dropping it, except now I usually have something wedged under the charger. I tried Loading in through MAGLDR BOOT AD NAND. No luck.
you misunderstood.
can you boot into bootloader (not magldr)? the tricolor screen- turn phone off, turn on and hold down the volume down key.
if you can (and should be able to do so) - i would start over. flash back to WM. i never do task29 though conflicting reports. then reinstall whatever OS you are using. if problems persist on WM, then is hardware. however, to flash back to WM you will need battery life (>50%) which may represent a problem. but try to get into bootloader first.
This morning I was playing angry birds and my nook just shut off. I assumed my battery died so I tried to plug it in. Immediately it started to turn on and then as soon as the nook color screen came on it cut off. It's been doing this all day. It also keeps saying that it is preforming a system update and that it is restoring to factory settings. It only does has any activity when it is plugged in but it will not do anything when it is not plugged in. I have tried every combination of the power and the "n" button possible to try to fix it. is there anything else i can do?
jam28570 said:
This morning I was playing angry birds and my nook just shut off. I assumed my battery died so I tried to plug it in. Immediately it started to turn on and then as soon as the nook color screen came on it cut off. It's been doing this all day. It also keeps saying that it is preforming a system update and that it is restoring to factory settings. It only does has any activity when it is plugged in but it will not do anything when it is not plugged in. I have tried every combination of the power and the "n" button possible to try to fix it. is there anything else i can do?
Click to expand...
Click to collapse
Is the nook color a refurbished unit? Did you root it? Is is on the stock ROM? If it is a new unit bought at B&N return and exchange for a new one.
jam28570 said:
This morning I was playing angry birds and my nook just shut off. I assumed my battery died so I tried to plug it in. Immediately it started to turn on and then as soon as the nook color screen came on it cut off. It's been doing this all day. It also keeps saying that it is preforming a system update and that it is restoring to factory settings. It only does has any activity when it is plugged in but it will not do anything when it is not plugged in. I have tried every combination of the power and the "n" button possible to try to fix it. is there anything else i can do?
Click to expand...
Click to collapse
It could be your battery is not charged enough. It is trying to update, but will not update if your battery is below 15%, so that it assures there is enough to finish. Leave it plugged in for a while, even if it does cycle.
It is also possible that it is trying to repair itself with a built in repair zip,'romrestore' and failing. Try making my bootable CWM SD from my tips thread linked in my signature. Boot to that and see if it is stable. You may have to run some of my partition repair zips if you cannot revive it. Then you would have to reinstall stock.
Sent from my Nook HD+ using Tapatalk
Hiya,
So my colleague gave me an USB stick for me to copy some photos on to, and it seemed to of killed my N7.
Here's how it all went down:
I have an Intel MBP and when I plugged the USB drive in, it didn't recognise it (it didn't even show up in the Disk Utilities). And yes, it was directly connected to my laptop, no USB hubs involved.
I tried even the other USB port, and even with a USB hub, no difference.
I've installed a program to write onto NTFS formatted drives, and OS X natively can read just about all the Windows file formats (in my experience any way). And so, just for the giggles, I popped the drive into my updated and rooted N7 via a Motorola USB OTG cable (which has worked for a long time and no flaws) and then my N7 could read it. No worries.
I copy all of files into a separate folder on the drive, and then pop it back into my MBP. It then detects it. Very strange. I copy over some files, and unplug. Later on in the day, I remember that I forgot some files, so I plug it back in, and my laptop starts going into some crazy lag mode as if it just got Parkinson's. Unplug the drive, and then it freezes (i have to do a force shut down) and when it boots back up, it's seriously FUBAR'd.
I felt the drive belonged in the pits of Mordor with what havoc it was causing.
I didn't plug it back into anything else after that. Told my colleague and he did a virus scan on his Windows work comp: nothing.
Battery dies on the N7 (ie, ran out), and when I go to charge it. Nothing. Okay, something happens. The backlight goes on, but no battery symbol. Just see some sort of light leek (which I had before, but nothing dier.)
It's a 32GB CC0K "generation".
Any clues, tips?
Thanks for any and all help!
TL;DR version:
A) Big long story about MacBook Pro and a wonky USB drive.
B) Separately, "Battery dies on the N7 (ie, ran out)", N7 won't start up.
Not clear from story if (A) has anything at all to do with (B).
Try charging battery for a while? Hold Power button down for 20 seconds afterward? If not, unplug battery connector, wait 10 seconds, plug it back in, charge device, try to reboot?
There have been a number of similar sounding stories on here. Some of them seem to self-resolve after charging, some of them are reported to respond to various voodoo operations (e.g. battery disconnect/reconnect), some of them the person making the report never checks in again. I suppose that leaves open the possibility that some devices never turn back on?
It isn't obvious if there is a single syndrome or mutiple problems that exhibit similar symptoms.
good luck.
Thank you for shortening it!
I tend to go a bit overboard with details and what not.
Ok, will try having it in the charger and see what happens.
Thanks!
I also find it strange that a USB drive could be so destructive. However, if you do have a wonky USB drive, what chance of is there for its faultiness doing harm like I just described?
Don't forget to make sure the internal battery lead isn't disconnected!!! It happens..
Ok, plugged it, it sat in for a while, held the power button for a few seconds longer (along with the bottom volume rocker) and it turned on!
So, thanks for the help!
Must be the 100th time I've read about grouper's funny little "death" because of drained battery. Hasn't happened to me but if it ever does I'm prepared and properly informed lol
Sent from my Nexus 7 using XDA Premium HD app
My tablet had 55% power at night WiFi/BT off and on sleep I woke up and it was so dead it wouldn't even turn on. Just glitches here and there with the battry
Sent from my Nexus 4 @1.67 GHz on Stock 4.2.2
Few weeks ago I found wife's old NST (non-glowlight model) in working order and decided to root it. Rooted it, played around with it. Wasnt too impressed, so just threw some ebooks for my kid to read while on vacation. Left it on my desk for a few weeks as I got busy with work. Today I picked it up as my son's vacation is next week and it's frozen on the "Installing... A new software update is being installed This will take a few minutes" screen.
I mean I googled for several hours, the hold the power button for 20 sec method....the hold the power and the "n" button method, I charged it, indicator light is green. I even opened it up and pulled the battery cable..... NOTHING WORKS...]
Please help. So weird...it was working fine and now frozen.
KEVIN88GT said:
Few weeks ago I found wife's old NST (non-glowlight model) in working order and decided to root it. Rooted it, played around with it. Wasnt too impressed, so just threw some ebooks for my kid to read while on vacation. Left it on my desk for a few weeks as I got busy with work. Today I picked it up as my son's vacation is next week and it's frozen on the "Installing... A new software update is being installed This will take a few minutes" screen.
I mean I googled for several hours, the hold the power button for 20 sec method....the hold the power and the "n" button method, I charged it, indicator light is green. I even opened it up and pulled the battery cable..... NOTHING WORKS...]
Please help. So weird...it was working fine and now frozen.
Click to expand...
Click to collapse
The real question is whether it is actually still on or off. What happens when you connect it to a PC via USB?
nmyshkin said:
The real question is whether it is actually still on or off. What happens when you connect it to a PC via USB?
Click to expand...
Click to collapse
Only the green charging light goes on. I do not hear the little sound it should make when making a successful USB connection.
KEVIN88GT said:
Only the green charging light goes on. I do not hear the little sound it should make when making a successful USB connection.
Click to expand...
Click to collapse
And I guess the drives don't mount successfully. Well, disconnecting the battery should certainly turn it off. If reconnecting makes it start spontaneously (should not), you could prepare a Nook Manager sdcard and insert it before reconnecting the battery. But this sort of sounds like the ability to boot is lost. Hmmm. I'll have to think about it.
unfortunately disconnecting the battery does not appear to do anything... screen continues to show that 'Installing... " screen. Hoping to get this thing figured out with someone's help
KEVIN88GT said:
unfortunately disconnecting the battery does not appear to do anything... screen continues to show that 'Installing... " screen. Hoping to get this thing figured out with someone's help
Click to expand...
Click to collapse
E-ink screens stay the same unless there is a new powered input so it could simply be off, having run the battery down completely during an update (maybe Wi-Fi was left on? That would run down the battery for sure). So if all of this happened during an OTA update, it could be really messed up
When my NST is off, plugging in the power pack turns it on. Initially the LED is green and then changes to orange as charging begins. I'm assuming nothing happens when you do the same. If the OS is scrambled from losing power during an update it may not be able to boot. You didn't say how you rooted. If you used Nook Manager you could try putting in that card and then connecting to the power pack, hoping for a boot from the SD card. If you got that far you could try a factory reset.
My power button is sometimes really cranky and a few times I've run through my entire stock of words that do not come from children's books trying to get the device to turn on. So you might try, but if it's really off the power pack should turn it on.
Edit: Take a look at this: https://forum.xda-developers.com/showthread.php?t=1813384
nmyshkin said:
E-ink screens stay the same unless there is a new powered input so it could simply be off, having run the battery down completely during an update (maybe Wi-Fi was left on? That would run down the battery for sure). So if all of this happened during an OTA update, it could be really messed up
When my NST is off, plugging in the power pack turns it on. Initially the LED is green and then changes to orange as charging begins. I'm assuming nothing happens when you do the same. If the OS is scrambled from losing power during an update it may not be able to boot. You didn't say how you rooted. If you used Nook Manager you could try putting in that card and then connecting to the power pack, hoping for a boot from the SD card. If you got that far you could try a factory reset.
My power button is sometimes really cranky and a few times I've run through my entire stock of words that do not come from children's books trying to get the device to turn on. So you might try, but if it's really off the power pack should turn it on.
Edit: Take a look at this: https://forum.xda-developers.com/showthread.php?t=1813384
Click to expand...
Click to collapse
When I plug in the power cable the light just becomes green it never (not even for a split second) turns orange. Yes, I'm rooted using nook manager. I just suck my Nook Manager SD card in the nook but nothing happens. I'm not sure what you mean by using the power button, in my original post I mentioned I tried the power button with no luck. What do you mean by power pack?
KEVIN88GT said:
When I plug in the power cable the light just becomes green it never (not even for a split second) turns orange. Yes, I'm rooted using nook manager. I just suck my Nook Manager SD card in the nook but nothing happens. I'm not sure what you mean by using the power button, in my original post I mentioned I tried the power button with no luck. What do you mean by power pack?
Click to expand...
Click to collapse
Power pack = charger.
So if the Nook is actually off, attaching the charger with the NM card inserted should make it boot. Did you try the procedure in the link above?
Just tried the procedure of unplugging the battery, holding the white power button for 30 secs, then connecting battery and connecting to charger. There is a split second orange light and then green the first time i plug it in....subsequent plugging results in always green....the issue with the frozen screen on "Installing" remains. Tried the holding x 20 secs method to promt a restart....nothing.... what else can I do?
KEVIN88GT said:
Just tried the procedure of unplugging the battery, holding the white power button for 30 secs, then connecting battery and connecting to charger. There is a split second orange light and then green the first time i plug it in....subsequent plugging results in always green....the issue with the frozen screen on "Installing" remains. Tried the holding x 20 secs method to promt a restart....nothing.... what else can I do?
Click to expand...
Click to collapse
If the battery is actually "dead" (not impossible on these old devices), the NST will not start, even if plugged in. Do you have a voltmeter of some sort to check the battery? If it's actually charged, it should show a solid voltage. If not, that may be the issue. If the battery is actually charged then there's a pretty serious issue that can't be fixed without access to the OS by ADB, or the ability to boot from the SD card. Beyond my "pay grade", at any rate, I'm sorry to say. There are batteries available online but the price may not make sense.
I don't think it's a battery issue. I had another NST with a good battery but a bad screen (lines all across screen) . I fully charged it using the bad screen reader and used the battery from it for the frozen nook... no luck.. oh well... I guess this is a paperweight now... thanks for your help everyone.