My NC will no longer turn on AT ALL -- doesn't even flash the screen -- after maybe about the 4th boot of the Froyo on eMMC install I put on there. It's not my hacking it, that would make no sense as it booted several times before just failing when I rebooted it with ADB after deleting the YouTube app. I think somewhere in there something connected to power just failed. But I suspect if I get it warranty replaced B&N will just blame my rooting it rather than finding the actual cause of the problem.
So I want to know if the extended warranty is just a "no questions asked" type, because that would be helpful in getting my device fixed!
If it won't turn on at the store, they can't check. However this isn't 100% ethical, as you did make major changes, which could be at the heart of this.
Can you boot from sd at all?
Sent from nookcolor
I'd say go for it, companies shouldn't get mad at us for doing what we want for the device that we bought.
...But this isn't really the best train of thought for this situation because you want to get another one or your money back xD
Had this same issue earlier. Have you tried booting without the sd card? Plug it into your computer, and see if it shows it as connected, hold down power and try it a few times.
Sent from my LogicPD Zoom2 using Tapatalk
Had this happen to me also. What I did was burn the ClockWorkMod to your SD card, also copy the factory boot.img and system.img file from the [ADV][DEV][STOCK IMAGE]Nook 1.01 stock dd images thread in development. Put it into your Nook, connect the USB cable to your computer and then hold the power button for about 20-30 seconds. It should flash to life, at least mine did. Once it comes up use the volume buttons to scroll down to the mount and storage option. use the "N" button to click it, then click on the mount /system option, then format /system option. then the same for mount /data, then format /data. Finally mount /sdcard, then on your computer using adb, use the adb shell command, and then use the 2 dd command from the thread mentioned above.
Rebbot after that and remove the sdcard, then do the power + N reset and the 9 reboot thing and you should be back at stock.
Hope that helps.
Turned out to be that whatever was broken installed on the eMMC had caused the device to be turned on, with the screen off, but entirely unresponsive to the buttons. I brought it into B&N and managed to get it to power on once with the battery nearly depleted. Then I recharged it, rebooted it and it went black and unresponsive again. They swapped it for me with about 10% battery left. So what will happen is: it will get to the depot with no battery left, they'll power it up, flash it, and it will go to some other deserving customer
Related
Hello All
I did search the forum and still not answer for the stranger reboot loop.
I got a phone call, and answered it. The reception was crappy and hear no voice. I then looked at the phone to see if call had dropped and it was frozed on the incoming call screen. I then pulled the battery and pressed the power button to turn on the phone and It would not power on. After multiple battery pulls and many many power button presses, still nothing. It was like it was out of battery. It was stitting on the home charger before i left the house. Prior to this the phone worked fine. Over the past week or two I had to do a battery pull may be 3 times.
I got to my car and plugged it into the charger and the orange charge led came on, on the front of the device. I then pressed the power button and it vibrate once as normal and then went to the multi-colored nexus "X." he screen went black and then vibrated once again and and was back at the mulit-colored "X." Then the loop starts.
In between the restarts I try to get it to boot into the bootloader by using the "vol down and power" and the "trackball and power button" and the white screen for the boot loader flashed for a milisecond the goes to black. As long as I hold the "vol down" button the while bootloeader or recovery screen flashes every 4-5 sec for a milisecond. As soon as I let go of one of those button, it automatically goes to the full reboot loop.
THis all happens when it is plugged into a power source. As soon as i unplug it, it goes back to the power button not responding. Again it acts as if it has no battery power. But it is in the 90%.
So i am unable to do any other step as in reflashing, and or doing a recovery.
ANY IDEAS any one.
I was running Cyanogen RC3. the latest rom with amon RA 1 7 1, korean radio 5.0.8
It was running perfectly up till today. when it went into its loop.
ANY HELP WOULD BE AWESOME
THanks in advance
DD
Plug it in to the USB, adb reboot recovery, reflash rom. Or even wipe and reflash if needed.
Sounds like it could be hardware the way you have to hold the keys down and you said it wasn't responding to the power button press.
ok thanks, ill give it a try.
here is my only issue. I am not using my original computer Mac. I just sent it out to apple for repair. So i am using my companies computer. I need to set up the AndroidSDK to be able to talk to the nexus. Since the phone will not turn on i can not load the drivers. and ive tried every way and it has not installed and i cant check because it wont stay on. it just goes to the loop. and it wont turn on if its not plugged to a power source.
Any ideas or suggestion.
SOrry I am an noob, so could you please be specific in your instructions.
I as of right now have insalled the Android SDK and i am unable to see the serial number (working on an old dell, running XP sp3) because it wont turn on.
It cant manually install the drivers because I cant turn the phone on to specify the drivers.
and
I using USBDeview, the phone also has to be on to erase all HTC previously installed drivers. i think. but there were none in the usb log...i think becuase they didnt install...agains because it would not power on...:-(
any ideas...please
DD
Also
Sorry excuse me if its a sort of a duhhh question...
even if i am able to load the device bridge, if the phone will not boot can i still flash another rom, or do a recovery. The phone is not getting past the Multi-colored "X" ???
DD
It should still read the commands when it's trying to boot. You don't need to turn the phone on at all to be able to install the ADB drivers, they are independent of each other.
As strange as it started, is a strange as it went.
This morning open the phone to pull the sd and the sim to put it in a throw down phone. I replaced the battery and cover and just hit the power button. The phone does a full boot and it appears to be working properly. the sd card and sim are fine. I the odd thing is i did this multiple times yesterday and last night. I pulled both sim and sd, replaced the battery and tried to boot with the same issues as named above with nothing different.
I left the phone on charge last night and it was charging for close to 8 hours and it was still showing the orange charging light.
So after it booted this morning, and i checked everything. It showed the same amount of charge as yesterday, right before it froze, which was 75%. So that is another strange occurance.
I plan on reflashing the rom and seeing how things go.
I thank you for your assistance and time.
appericate you helping out a clueless noob.
DD
Having an odd issue with my Nook (rooted with Auto-Nooker).
When I power it off, I cannot seem to power it back on with the power button, unless I plug the USB cable in first. Any ideas? Is this normal? Thanks.
I had problems the first couple of power ups, then is started acting normal.
I just got ny nook last night and when i tried to wake it up this morning i had to plug it in. I hope it fixes itself soon.
Sent from my NOOKcolor using the xda app
Silly question perhaps, but a few people have forgotten... Did you remove the SD card with the Auto Nooter image and reformat it? Otherwise it will boot into that every time you try to turn it on.
peiziyu said:
Silly question perhaps, but a few people have forgotten... Did you remove the SD card with the Auto Nooter image and reformat it? Otherwise it will boot into that every time you try to turn it on.
Click to expand...
Click to collapse
This was my problem as well until I did what you said. Thanks for the reminder!
I was having the same issue in the beginning. Even without the sd card inserted, I'd have that issue. It seems to be fine now, though.
Are we supposed to see the Nook color custom boot animation with the little android guy on the bottom right, though? I thought it was just part of the rooting/setup.
sano614 said:
I was having the same issue in the beginning. Even without the sd card inserted, I'd have that issue. It seems to be fine now, though.
Are we supposed to see the Nook color custom boot animation with the little android guy on the bottom right, though? I thought it was just part of the rooting/setup.
Click to expand...
Click to collapse
Everytime I have rebooted I have seen that boot screen, so it should be normal
I have taken my card out and reformatted it. My issue is more so when i leave my nook alone for a long period of time and it is just sitting in sleep mode. I have to hold the power button to get it to come back on(it reboots).
Sent from my NOOKcolor using the xda app
I think that is intended, pretty sure you had to push the power button for a second or two stock as well... reduce accidental power ons?
Seems odd, but I found a way to start up my Nook Color without having to plug in the USB. If I press and hold the Home button for a few second, then press the power button, it'll come on.
The custom logo is a standard part of the rooting process. If you don't like it, you can revert to the standard by moving or renaming /data/local/bootanimation.zip
I rooted my nookcolor today using 2.12.25. I linked to gmail and browsed the web and then put the nook on the charger. When I went back to use the nook about an hour later, the nook had a black screen and was unresponsive. Held the power button down for 10sec and still nothing. I also tried n, + and power and nothing. Tried nooter sd and the n goes green and windows sees it as a Android ADB device. Any suggestions?
By any chance do you have the microsd card still inserted with the image file on it? Remove it (if so) and hold the power button for 15 sec to shut down. Then start up w/o the card.
If you do not, try an adb reboot to see what happens. We can pretty much guarantee you do not have a brick, if you can see it in adb.
Thanks for your response. I will try to connect via adb when I get home tonight.
brockster said:
Thanks for your response. I will try to connect via adb when I get home tonight.
Click to expand...
Click to collapse
Cool.
If that does not work, just start again, by flashing back to a clean stock image and then wiping the data, which is also also in that tutorial.
Yeah sounds like as card was still in reader slot, I did that a few times myself
Sent from my Nootered Nook Color using XDA App
OK, I made sure there was no card in held the power for 15secs and all I get under window device manager is a device called OMAP3630 for a split second. With the nooter2 sd in, In putty I can connect to 192.168.2.2 as root. I can get in and mount the directories and see my files/books. Is there a way to fix it so it will boot?
I recently tried booting using what turned out to be a bad SD card image. At the time it got as far as the ANDROID block letters on the edge of the screen. I took the SD card out but then realized I had no way to reboot it: the power button did nothing and I couldn't pull the battery like on my Droid. At first the only option I could see was to wait a day or two until the battery ran down. Now, I know nothing about adb except what I did to get the market added to froyo but I did remember that it ended with an adb reboot command. I tried that, my NC rebooted and all is good.
So I'm wondering what options exist when the device doesn't boot?
- adb reboot (may not respond and probably of little use if EMMC boot is bad)
- ???
Make a bootable sdcard with CWR on it. Then no matter what state the device is in if you put the bootable sdcard in the device and power on it will boot into CWR so you can do whatever is needed to get yourself back up and running again in short order
But what if the device is already on like in my case? Other than adb reboot (which may or may not work) there's no way to force a reboot, or is there?
FYI you can always turn the device off no matter what. Just hold the power key for about 10 - 15 secs and no matter what states you are sitting at it will force it to power down. Just like a comp when you hold the power key down for an extended amount of time it will in fact power off.
On another note depending on what recovery you have on the device if it does get stuck and you force it to power down like I just mention you can boot into ( CWR ) recovery mode and from in there there is a reboot option also. Again tho that would only work if you have CWR installed on the internal memory.
I did hold the power button down for fairly long time. Apparently it wasn't long enough.
I just have the rooted stock 2.1 internally. Don't know what, if any, recovery that gives me.
So much to learn, so little time...
lol.... I hear ya there. Been messing with Android phones for ages now but a new learning curve when it comes to the Nook with so many different options we have to choose from. BTW I have had it to where I had to hold the power key down for over 30secs to get it to power down just so you know. If you run into the issue again for sure just keep holding it and it will power down at some point.
Good to know. Thanks.
Hello,
I'm hoping this group can offer a few suggestions to resolve this problem.
Situation:
My wife's LG-P999DW phone appears to be having severe power issues.
It is set to go back to Wind Mobile for a replacement. However she has photos on the device that she needs to retrieve - apparently the SD card was never initialized so the photos are stored in the phone's memory.
The phone is completely stock and was picked up new in November 2011. I have not rooted or modded the device in any way.
Unfortunately the power will not power on. The charger makes a high pitched humming noise when plugged into the phone. At this point I've tried directly connecting it via both the USB cable that came with the charger and another separate cable to my iMac.
After lots of searching on the this board I discovered that the phone does have a recovery mode (Volume Down & Power button). The phone launches the white LG logo and after about 3 seconds the screen flashes and goes blank before recycling to the LG logo again.
At this point I'm desperate to figure out a way to access the memory on this device to try and retrieve these pictures (basically pictures of a pet that passed away that were not unfortunately backed up).
Any suggestions are welcome - I'm open to all options.
Thanks
Interesting problem. If the phone is hosed, then so of course are you, so let's assume it's not.
Since you say you get some activity when holding vol-down + power, you can try to install clockworkmod on it via nvflash, boot into that, mount usb and if you're lucky you'll be able to copy the images. (If you only get this blinking when it is plugged in you can ignore the next part - you will not be able to boot into CWM.)
To try that, find a guide for P999 on how to install CWM via NVFlash (this is the P990-thread).
I would not get my hopes up, since it will not start the built-in recovery by itself then the entire internal storage may be hosed (including the partition with the pictures), but it's worth a shot.
You may even be so lucky that it's only the charging curcuitry that is damaged (I assume you get the blinking lg-logo when it's plugged in only, which a phone without a battery will do), in which case you can borrow a charged battery in a phone store and copy the images from internal storage to an external sd-card there.
If the entire power-delivery system is damaged, your only hope is to beg and beg the support people to ONLY repair the electronics and not do anything else to it (wrap the phone in a big please-note).