I recently picked up a nook from barnes and noble and for a few day i have had no problem. But ever since i tried putting music and pdfs on to the internal storage its been freezing up right after i boot it up from it being powered off. Ive been able to get it running after multiple restarts but every time it freezes from regular use it takes like 10 trys to get it running again. I was able to go into settings and factory reset it but to no effect. any advise would be helpful thanks.
i forgot to say i havent rooted it yet its still stock.
When I try to boot my nook, I get past the "Touch the Future of Reading" screen but get caught up on the "n" loading screen.
I've tried to interrupt the boot process physically 8 times to no avail.
I've tried to SSH in the 8 failed resets script, nothing.
I can't boot the nook far enough to be able to shell.
I tried to do a factory reset but it tells me "install failed", and has an image of a nook with a red circle and while exclamation point.
I installed Nookie-Froyo from flash and tried to use that but soon realized I was over my head.
So finally I called BnN to see if they could do something and they offered to replace it. If I send them this wonky device, will it raise some red flags in their system?
I would say try some other methods before returning it if possible. I have read others on the forum in the same situation as you and they have gotten it working again. It will take some time for someone with more knowledge to respond, but I think it is worth it.
If you return it it seems like you might have a high chance of getting one that has hardware/software issues from what many have posted. I would try to stick with what I had even if it took a week of getting help from the forums.
Have you tried booting the AutoNooter 2010-12-25 ? I have heard some boot the sd card and then they can ssh to 192.168.2.2 and do some recovery work on the nook, like I said I am not experienced in this but I have read other's posts on success stories
I've tried the ssh method and it would never make it past the n screen. I've also searched the forums and haven't seen anything about an "Install Failed" screen. If someone has seen something about that and could point me to it, I'll try anything.
If you see an N on the screen it means it is not booting from the we card. Maybe the we card wasn't written correctly? Was this rooted previously?
Sent from my NookColor
It was rooted and then stopped working after I left it in a very cold car all night long. I don't know if that's what caused it, but until I figure it out, correlation will equal causation.
As for the card, I reformatted and re-imaged it 3 times in the process of trying to re-root it; once with auto-nooter for 1.0.0 and twice with 1.0.1.
This is crazy, I have the same issue right now....it's stuck in the boot screen. Mine rooted perfect today, apps installed from market with no problem, I noticed the battery was low but wanted to reboot it after I noticed Youtube stopped working, I shut it back down and restarted it before I put it on a charger.....it hasnt rebooted since.
I did get it to boot into clockwork a few times, I did a factory reset from there but it still didnt help. Anyone have an idea? Did I permently brick this thing?
I had FroYo running on eMMc and all was running smoothly until I went to reboot it and now the screen will not turn on. I have held the power button for a long time and tried pretty much every button combination to get it to power on. I also tried plugging it in and still nothing. Is my nook bricked?
Have you tried booting Froyo on a SD card?
If you don't even see anything on the screen maybe it's a hardware failure..
Were you overclocked?
I put froyo on a 2gb card and i still cant get it to boot. Is there a specific key combination i need to use to get it to boot off of the sd card?
Are you sure that battery wasn't almost dead? Try booting it while plugged in for a bit.
I've had it plugged in for about 10 minutes and ill try to boot it in a second. Whats my next course of action if that doesnt work? and thanks for the suggestions so far.
Still a no go on the boot. Im going to let it charge overnight and give it another go in the morning.
when I power my nook on by holding down the power button eventually the screen will "light up" (even though it will stay black, you can tell the backlight has come on). is it doing that, or just never seems to respond?
I had an issue once running Nookie Froyo where I thought my Nook was dead and realized it was actually on after a while. Only way I found it was that I saw it on my network via my router when checking something else. No matter how long I held the power button down it never seemed to do anything. After a while of fiddling the screen finally lit up and I could get in.
If you plug it into the USB port on your computer, does the computer see it and load the driver for it?
digeratix90 said:
I've had it plugged in for about 10 minutes and ill try to boot it in a second. Whats my next course of action if that doesnt work? and thanks for the suggestions so far.
Click to expand...
Click to collapse
Unless you're using the B&N supplied cable, the NC takes a REALLY long time to charge. I inadvertently let my battery drain and tried charging it using my EVO's USB cable and still couldn't use it more than an hour later, with the "try again in 15 minutes" warning on the screen the whole time.
Hope you managed to fix your problem and that your NC is functional again.
I had the same problem and I could actually replicate it. I had froyo running emmc. What I did was clear out some cache and data from market, Google framework, and also the download manager since I had the market download unsuccessfully problem. Right after I cleared the cache and data then force close the Google framework application (and of course reboot), I couldn't turn on the nook color anymore. I know the device wasn't dead because I got feedbacks if I do.SSH. I flashed the rom again and it came right back on. Then I did the same steps for the cache and data, the device once again couldn't turn on.
Ok i let it charge overnight with the b&n cable (the light was green this morning) And I tried to turn it on again. The screen still does not turn on and the backlight does not turn on. I do not get any response from the computer when I plug it in. I think that I may have bricked the hard to brick nook color :/
I ran into this very same issue a moment ago, and I just followed these steps:
http://forum.xda-developers.com/showthread.php?t=931720
In your case, you want to install the CWM to the SD with the nook 1.0.1 software zip, insert the SD card into your nook, then press and hold down the power and the N button ... and it should boot into CWM then continue with the rest of the steps.
Thanks for the help everyone. I think I may have had a coincidental hardware failure. I took the nook color to b&n today and they tried everything to get it to work and they were going to try to send me a refurbished one, but I asked for cash instead so they gave me a new one on the spot. I am going to stay away from the froyo stuff until it is a little safer (hopefully I can hold out until CM7 comes out)
I can confirm this is definitely a problem with the current Froyo build (.6.7). After loading it to my EMMC and loading Google Apps, I had the blank screen, no reboot issue after I sent the adb reboot command. Thinking I had bricked it (charging, holding the power button, etc. wouldn't do a thing), I popped in an SD card with bootable froyo on it and now the thing powers on and boots to SD. If I take the card out, it goes back to it's dead state.
I'm downloading the stock FW and going to reflash it, but I just wanted to confirm that this is a problem and it probably wasn't a coincidental hardware failure.
backlund said:
I can confirm this is definitely a problem with the current Froyo build (.6.7). After loading it to my EMMC and loading Google Apps, I had the blank screen, no reboot issue after I sent the adb reboot command. Thinking I had bricked it (charging, holding the power button, etc. wouldn't do a thing), I popped in an SD card with bootable froyo on it and now the thing powers on and boots to SD. If I take the card out, it goes back to it's dead state.
I'm downloading the stock FW and going to reflash it, but I just wanted to confirm that this is a problem and it probably wasn't a coincidental hardware failure.
Click to expand...
Click to collapse
I'm having the same issue. Nookie Froyo .6.7 on emmc. Completely dead and not recognized by computer usb. Will try the SD bootable froyo.
Edit: Ok, I was able to boot off the sdcard, but can't get to recovery. If I remove sdcard it won't boot. I guess I'll have to put the recovery on the sdcard to reflash a rom.
I had the same issue when using Froyo 6.6 to EMMC.
I really thought I had bricked it and out of Desperation I made a CWR card put it in and tried every button combo I could think of and low and behold it booted back up. lol, now I'm back to stock 1.1 rooted. I think I will wait till CM7 is out for the nook before writing to EMMC again.
But man props to the makers of the nook color, 99.9% Un-brick-able
Yeah I had a couple issues with throwing an image on the first time I went to root it, just re-formatted and put a diff image on the SD and everything was fine....
Ugh, I'm glad I'm not the only one having this problem. Now I get to walk through the recovery.
Update:
So after walking through the recovery, I still couldn't get it to boot. It wasn't until I performed step 5 that it finally worked.
http://forum.xda-developers.com/showthread.php?t=914690&highlight=cwm
I recently decided to go back to complete stock. I wanted to see how a factory stock rom would deal with the battery issues and others I've had. That's where the problems really began. I followed the instructions in a current thread. I used this thread years ago to root my nook without a problem. My Nook HD+ this time would not boot from any SD card. It did not matter what image I used or what method from the mentioned thread. The SD cards are good though. I stupidly did a factory wipe/reset in CWM, mostly because I had tried everything else. I knew not to do it, but I had tried everything! My Nook would stay on the Caynoboot after this. I finally got a flash to work using the old method and CWM 6028, but this time it hung on the Nook screen. After fighting this for a while, I finally got the stock recovery and stock rom to flash. Great, it's working again as it should. The problem I have now is if I leave it alone for a bit the Nook will shut off. I can power it back on, but sometimes it takes a couple of tries. I tried to charge it this morning when the battery went down to 6%, but I could not use my Nook charger. It would shut off or start to boot past the Nook screen and then shutoff. I'm typing this now and my Nook is charging fine through my computer. Has anyone experienced the auto shutoff when leaving it alone? It's totally annoying, but it functions fine other than that. All of these problems came to life after going back to stock root. Personally, I don't feel like starting over again. I'm to nervous that something will go wrong.
My thought is this relates to all the known battery problems the Nook has. CM might eliminated some of the obvious though. Mine started 3 months after I bought it years ago. It was part of the reason I went to CM10 at the time. I thought maybe the factory rom was the issue. Do you guys think the auto shutoff and normal charging method issues are battery related? I don't think it's a hardware issue. It could be the way the rom was finally flashed, but I would expect more problems other than the above. One thing the factory rom did fix was the Nook shutting off on almost any flash video. It was always random, but this has not happened since going back to stock.
Wow. This just gets weirder and worse(r). We've been running first CM 11 and then CM 12.1 on this HD for awhile and all was fine. Suddenly the battery indicator became wonky, dropping from 50-ish% to 1%, precipitating a shutdown unless the tablet was immediately plugged in. Then suddenly the battery indicator would return to normal and you could unplug the tablet.
Next, after running a backup on the CM 12.1 ROM the tablet started crashing during boot (the cyan android phase) UNLESS it was plugged in to the power supply (USB to computer is not sufficient). This, despite a good charge level on the battery. After a minute or so when the boot was complete, you could unplug the tablet and go on your way.
Today the screen flashing began. Makes the tablet completely unusable. Sometimes you can calm it down for awhile by connecting via USB to computer, sometimes not. This thing is freaking me out. I just recently took the tablet all the way back to stock and resintalled CM 12.1 from scratch, including building a new SD card from new files. Before someone asks, it's a class 4 card. I've always been fine with Class 10 or UHD cards when working with my Nook Tablet, but for some reason I decided to play it "safe" with the HD and hunted around for a lower class. Maybe a mistake?
Finally I took the tablet back to stock again today, completed the sign-in process to the old B&N account and everything is fine. No screen flashing, no funny business with the battery indicator, no problem booting without the power cable.
I just ordered a "new" (out of box) replacement for the tablet on ebay, but it doesn't seem like this is an actual hardware issue.
What scares me now is a potential repeat of this process with the new tablet. I've never had any experiences like this with my old Nook Tablet. I'm at a complete loss.
Help!
Edit: OK, we seem to have tracked down the general source of the screen flashing. The backup we have been restoring is from July 2017 so quite a few apps want updating. We noticed things would be fine for awhile and then the flashing would start. At one point "Unfortunately Google Play Services has stopped" kept popping up. I began to suspect either a bad or incompatible update was messing with the system. So...we did another restore of the same backup but immediately turned off auto-updates from the PlayStore. Three days later and no display flashing. One small victory.
Could the shutdown during the boot animation be caused by a corrupted file? I don't see how since it boots OK when plugged in, just not on battery, but I'm willing to pursue any possibility.
Edit.Edit: Well, well.... We got a "new" open-box HD from ebay and I started working on it. I noticed in making new SD cards that one I had been working with was not properly set to 0x0C FAT32 LBA. I fixed that. This time the tablet will boot into the OS without being plugged in! Yay! Still have to test that on the old one after I finish building a duplicate system.
I'm restoring apps and everything is fine until suddenly the flashing starts up again. But now I know when it did. The offender seems to be the 0.15 version of Lithium Epub reader. I managed to uninstall that via ADB (with screen flashing you can't do much with the tablet except ADB). Voila, no more screen flashing. I found a copy of version 0.13 and installed that. No flashing screen. Needless to say I've set the app to not auto-update.
Edit.Edit.Edit: Well, $40 later we now have a second Nook HD and both are running fine. Hard to imagine that the goof that somehow happened to the SD card would manifest as only being able to complete boot when plugged in, but that must be it. Returning to stock (tried that...) and reflashing with the newly prepared SD card did the trick. Moral: sweat the small stuff.