Nook just shows Cyanoboot logo forever - Nook HD, HD+ Q&A, Help & Troubleshooting

My install of 10.1 to a Sandisk 64 GB card appeared to work fine. I was able to go to Play and install my whole app set and fiddle with various stuff. I left the Nook untouched for about a week and after making sure it had a full charge I tried to start it up. The Cyanoboot logo appeared as expected but after half an hour nothing has changed.
If I shutdown and remove the microSD card the Nook boots into stock normally. But it cannot get past the bootloader with the card inserted.
Am I hosed? Do I have to start over?

And... now it works again. I wonder if it was affected by cold from being near an open window? I'm in L.A. County, so we aren't talking freezing temps or anything like that.

Related

Nook freezing shortly after reboot?

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.

[Q] Is my nook color bricked?

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

Can't get past the "android" robot on screen.

Have read and re-read many posts, but now very confused! Hopefully someone can help me.........
Need some assistance to fix my color nook.
It auto updated with the first use to 1.1.0 version.
I tried Froyo first but lots of glitches and programs that wouldn't run or shut down unexpectedly.
Downloaded autonooter 3.0 from xda site, for 1.1.0 and using win32 disk imager burned to a 2G SD card.
Popped it in and followed instructions for set up and it worked like a charm.
2nd use started up slow but worked and downloaded my apps and they worked.
Turned off the nook and placed on charger as battery was way down.
After a full charge would only boot to the "android" robot screen, will not go past that
and initially I could not power off. Then it went to a dark blue screen with nothing on it, then I was able to power it off again after quite some time.
I tried it again several hours later. Now powers on but to the "android" robot screen, and it will not go any further. (have let it sit for 45 minutes)
Removing the SD card is no help, unable to power on past the "N" on the screen.
FYI, the SD card I used did originally have Froyo on it (I could not access the Market though), So I formatted via a USB reader on my PC, before I burned the 3.0 on it.

[Q] Bad SD Card or Bad SD card slot, or Defective NC, or Bad operator?

Yesterday I used autonooter 3.0.0 to try to root my NC 1.1.0. It would not boot up or turn on at all. Today when I go home from work, I plugged it into my PC and was told battery was too low to boot. I charged it to 100%, then it booted up. I checked, and to my surprise I was still on version 1.1.0. So, it was not bricked.
Today I tried autonooter 3.0.0....same result. My NC won't turn on...and when I plug it into my PC. I get a "RNDIS\Ethernet Gadget" found message, then the "Found New Hardware Wizard" opens up.
Is my sd card flaky, is the card not properly seated in the NC, or is the NC card slot bad? I tried booting a CWR card to restore my NC, but get the same messages.
I plan to wait till tomorrow and hope the battery drains, so that after a re-charge I will be back in 1.1.0. Then, I plan to take it back to B&N for an exchange...unless someone knows what my problem really is.
Autonooter does its thing with the screen off. It sounds like one of your boots was Autonooter working, because it was installing drivers for ADB. Plugging it in, w/ Autonooter in SD is what starts it. Maybe you just keep booting from the SD card, and only by plugging it into the computer was it able to do what it was supposed to.
You may be right, but right now the NC won't turn on.
Any idea if a HARD Reset will solve that?
I followed the instructions to a T. I even downloaded a new Autonooter 3 file. After writing to the card, I was able to view it and saw the 4 files and file sizes...very similar to those show in the instructions. I inserted the card in the NC, plugged it into the PC, .......black screen. I waited 30 minutes, but it never booted. I disconnected and removed the sd card. The NC would not turn on..........again. Failure # 3.
With the card out, I plugged it in to the PC again, and to my surprise, it turned on. It was still at v 1.1.0.
I transferred some mp3's, and all is good. I'm at a loss to know what to do next. I feel sure there is a problem with the sd card or the sd card slot. Since I am within 14 days of purchase, I think I will take it back to B&N, and try to exchange it for another new one.
Not sure how Autoneooter 3 is but the original 12.25 works great every one I did. Just go 1.0.1 full restore and then do the original autonooter and then the 1.1.0b through CW ZIP.
Most of what you posted didn't sound like anything was really wrong at all.
I do think wonky cards do mess it up though. try it for a while with a different card or no card to find out. You can also take your card and do a full format.

[Q] Strange reset from CM7 to Nook 1.2???

OK, here's the situation:
Nook Color running CM7 7.0.3 from SD card. Been running this since May without problems.
Last night I plugged in the Nook to charge and turned off the screen.
This morning I unplugged the charger from the Nook and it chirped. Never heard that before. I turned on the screen and it was at the out-of-the-box Nook lock screen. I swiped to unlock and found that overnight my Nook had somehow reset itself back to 1.2 of the Nook OS. I looked at the SD card contents and nothing was here.
I powered off completely, then back on, and all was well, back into CM7 from the SD card.
Any idea what caused this? I don't remember seeing any issues like this since I started following these forums in May.
Thanks in advance for any suggestions.
Steve
By "reset itself to back to 1.2," do you mean you had 1.3 installed and somewhat personalized previously, or just that it unexpectedly booted into stock instead of CM7?
I have no clue what happened either way--I'm just not sure what you're describing. If you were running CM7 from SD, stock was always still there, and some power irregularity caused your NC to shut down unexpectedly, and apparently fail to boot from SD, causing it to boot from stock on the internal storage instead.
Additionally, something may have triggered a factory-reset, but in that case it would have walked you through set-up again, and you said it took you straight to the lockscreen.

Categories

Resources