[Q] Looping in "Nook color" splash page - Nook Color General

I'm having the same issue as this guy: http://forum.xda-developers.com/showthread.php?t=1156371
I let my nook battery get really low... too low to boot. So, I hooked it up to charge and then it began doing the loop. It comes to the "nook color" splash screen and gets part way through the word "color" when it starts all over.
My question is two-fold:
1) Is there some way to fix this?
2) If the answer to the above is 'no', then how do I boot into Clockwork? It's some combination of holding the 'n' during boot... right?

I've been having this problem too. The way to get back into CWM is to use the rhythm method:
hold nook N key and then press and hold power until the "Loading..." message appears and then disappears with screen going blank. Release power button, then press it again and hold for ~5 seconds, the bootloader "Loading..." message should be on the screen for three seconds or so before you release power button, keep holding N button until screen blanks again. If the screen went off while you were holding the power key, that means you were holding it for too long.
Click to expand...
Click to collapse
Now as for fixing the boot loop... I've actually given up on 1.3 manual nooter and gone back to CM7.1 for now... That fixed it, although there are plenty of reasons for wanting stock rooted.

I'm having this issue now. It probably is because I formatted the SD card (if just to make the bloody status pop-up go away...), but I have...well, another problem.
I can't even start trying a fix because I can't shut the thing off. >.> Do I have to wait for my battery to die?
Edit: Got it to turn off (Hold Volume UP+DOWN and Power key), but I can't get it to boot to CWM. There's no 'loading...' screen, just "Read Forever" Then the N screen. =\ I might just act as if I was rooting it for the first time (flash SD card, boot by plugging it in to PC, etc.)

Did you ever get this fixed? I'm having this problem now.
Edit: Nevermind. I wound up wiping and re-installing.

I had a boot loop issue with Manual Nooter. My issue and soln here
http://forum.xda-developers.com/showpost.php?p=19116889&postcount=10
Good Luck.

I've the same problem. It've fixed by:
Right after rooting. Download astro file manager from the market. Go into /system/app and delete Adobe Air, Adobe Flash.
After deleting them .. Just go into Market, download and re-install them again. Should fix your problem.

This boot loop issue has become a serious problem for me. I have re-imaged my Nook Color 3 times, twice with 1.2.0 and once with 1.3.0. All three times the install was successful but upon re-boot I wound up in this loop lock. I got my Nook to run the Kindle android app as most of the technical books that I wanted on the Nook are not available from Dunn and Bradstreet. I've down loaded $350 worth of e-books from Amazon and now I can't download them again. I tied this Flash and Air trick but it didn't fix the problem. So now I've burned $350 in e-books plus the cost of the Nook and memory card. I should have just bought an I-Pad. This is beyond unfunny.

There seems to be some issues with Youtube that can cause this issue. I had to give up on running 1.3 rooted and go to CM 7.1.

It looks to me like the Adobe applications cited above may actually be causing this loop lock problem. With the auto-updates turned off it looks like the loop lock on the Nook Color banner does not occur for a while. Eventually the updates get turned on somehow, and the loop lock occurs. The android OS looks like it's built on a Linux base. I was unable to gain superuser status (perhaps I just don't know how to do it). Without it all I could do was to update Adobe Air and Adobe Flash. As soon as that is done, the loop lock occurs.

Correction to the above comment.
I guess I'm a little brain dead after all this re-imaging. What I meant to say above was the the technical and text books that I was referring to, are not available from Barnes & Noble (not D&B duh!), nor any of their e-book business partners. I would have gladly purchased them from B&N in ePub format.
After putting the Nook Color back to stock condition (1.2.0), I reinstalled the ManualNooter 4-6-16 then immediately attempted the fix recommended above.
In any case, I downloaded the Astro File manager, but since i could not figure out how to obtain superuser status (even with the superuser app) it would not let me remove the two Adobe applications. I could only update them. When they were updated, the banner locked up on the first re-boot. Unlike, the first lock up it displayed the full banner continuously, without completing the boot.
Without source code, it's impossible to tell if there is a bounds problem created by the rooting process, or if this is something else. Someone smarter than I will have to solve the problem.
I think I'm moving on to the less than ideal Kindle Fire, whenever one becomes available. If anyone wants a brand new Nook Color it will show up on e-Bay in a couple of days.

Has anyone here tried rebooting with the sd card removed? This is what worked (previously) for me.
Sent from my NOOKcolor using Tapatalk
---------- Post added at 10:18 AM ---------- Previous post was at 09:44 AM ----------
Now the removal of the SD isn't working... Trying the Abobe AIR and Flash replacement fix mentioned here:
http://forum.xda-developers.com/showthread.php?t=1308304

the adobe air / flash replacement fix worked for me.

Related

Afraid I have a $250 paperweight..root issue

As I have posted in a development thread about rooting..
Alright guys, I have a problem. And there is very little info about doing this on a Mac
I have created the autonooter2 sd card using terminal.
My nookcolor is powered off, sd card inserted, nook USB cable plugged in to nook and then computer. (nook symbol lights up on cord), my mac pops up and shows a RNDIS ethernet device
-1 st problem, It says on nookdevs that this RNDIS dialog will pop up and to ignore it...does that mean ignore it, leave it there or click cancel? I have tried ignoring for a while and then clicking cancel.
- It says both here on xda and there that when the autonooter is finished the nook should reboot itself..its been 10 mins this never happens??
any help is appreciated
edit:
alright I just unplugged the USB and turned on my nook and it brought me to the Android setup screen. I skipped the tutorial and sign in and checked both location boxes and then when I clicked continue the screen flashed and it threw me into the normal B&N interface and the nook color user guide automatically popped open and starts flipping pages rapidly. I can close out of the user guide but then it auto reopens :/
edit2: restarted , everything appears to be working alright except I cannot pull up a keyboard in any instance...searching store or through books
edit3: i have tried erasing and un registering my device. my nook is now unregistered. I have been trying to get rid of root. i have cleared data ( power+ volume + nook button) but I cannot factory reset using 8 reboot method.
My device is on, has NookColor settings under extras but I have no keyboard and cannot connect to wifi or re register..
Please.... help
You should register your NC prior to rooting it. You can restore your nook to its fresh state by interrupting the reboot process 8 times or, using the Android Debug Bridge (instructions for enabling it here: nookdevs.com/NookColor_USB_ADB) by following these instructions: nookdevs.com/Flash_back_to_clean_stock_ROM. Once you're done with that, register your Nook and then follow the AutoNooter instructions (nookdevs.com/NookColor_Rooting). Note: autonooter will reboot by itself once it's done; don't interrupt it by restarting the nook by yourself!
Ok quick question..
I figured I could not do any more harm so I started the autonooter process over from start to finish remaking the sd card but this time on a PC.
Everything worked better, the nook auto restarted itself and I got the Nook Color Dev screen and then to the unlock screen. I unlocked, ready to do the next steps (skipping tutorial and skipping gmail sign in) but I was never prompted. I am just at the normal nook homescreen, I now have much more options in extra( superuser, email, etc) and also the soft keys but I still do not have a keyboard.
Since I did this autonootering from an unregistered device do I need to start completely over?
Thank you for your response
foethalove said:
Ok quick question..
I figured I could not do any more harm so I started the autonooter process over from start to finish remaking the sd card but this time on a PC.
Everything worked better, the nook auto restarted itself and I got the Nook Color Dev screen and then to the unlock screen. I unlocked, ready to do the next steps (skipping tutorial and skipping gmail sign in) but I was never prompted. I am just at the normal nook homescreen, I now have much more options in extra( superuser, email, etc) and also the soft keys but I still do not have a keyboard.
Since I did this autonootering from an unregistered device do I need to start completely over?
Thank you for your response
Click to expand...
Click to collapse
It doesn't sound like you have anything resembling a paperweight, I'm sure you'll get it to where you want it.
Did you try the steps of signing in youtube then gmail, then market? If your only problem is a missing keyboard, that can easily be remedied. Get the apk of a keyboard that's known to be working (there's a thread in the NC section on the DroidX kb), and push it via adb as system/app/LatinIME.apk. Reboot, and you should have a keyboard.
You said you can't do the 8 failed boot attempts... Why not? All you have to do is power-down 8 times during boot (hold down power for about 10 seconds, then hold down again to power on... Repeat 8x).
Hey,
I'm kind of in the same position that you were originally in. My NC's firmware is 1.0.0. I used the guide on nookdevs.com, flashed my SD card w/ the proper image, inserted the card, plugged in the USB, and... over 30 mins and nothing.
What did you do once you were in this step to continue? Did you remove the SD card?
-Taser
edit:
wvcachi, that's actually exactly what I ended up doing, and it came right up - thank you!
Also, I ended up doing this (sorry, no linking allowed - nookdevs.com/Installing_the_1.0.1_update_on_a_rooted_NC), re-rooted, and the 1.0.1 root actualy did auto-reboot.
Thanks eveyone for your help, and OP for not getting too ticked I hijacked their thread
Taser420 said:
Hey,
I'm kind of in the same position that you were originally in. My NC's firmware is 1.0.0. I used the guide on nookdevs.com, flashed my SD card w/ the proper image, inserted the card, plugged in the USB, and... over 30 mins and nothing.
What did you do once you were in this step to continue? Did you remove the SD card?
-Taser
Click to expand...
Click to collapse
Ya same issue here, except now my nook is stuck at the giant n. It was responding to my adb shell commands to to the 8x reboot for the BootCnt. But after it did the update it still sits on the giant n. I'm not sure what is screwed up on mine. I wonder if the auto-nooter just messed up some how...
I was upgrading from 1.0.0 to 1.0.1 to fix my wifi drop issues.
Edit: Just let the n sit there for a good 15 minutes. I've never been so happy to see that intro video with that girl showing you how to use the nook!
Will try to auto noot again...
I've done auto-noot several times now, and it's never rebooted on its own. After a couple minutes of it doing its thing, I just unplugged it, held down power for 10 seconds to power off (it's on even though it doesn't look like it), removed the SD, then powered on. Everything was as expected after that, it just never rebooted on its own.
Mine from 1.0.1 behaves exactly like the wiki described for me. Ran with the screen off for about 45s and then rebooted and was good to go. I followed the post instructions to set up the account and everything went exactly as they described. Only difference was it seemed to me like the instructions duplicated themselves at one point, steps in had already done were listed.
Works great, but might should revise the steps of there are duplicate ones. If I remember or root again I might do it. Adding renaming the phone apps woukdvbe a good thing to do too.
The version of Auto-nooter for 1.0.0 doesn't auto-reboot after it's done. You'll have to let it sit and reboot yourself.
I strongly recommend you upgrade to 1.0.1 before you root anyway. It's more stable, and when you eventually upgrade, you'll have to wipe your nook to do it. Better to do it while you don't have anything on it.
Thanks to everyone that helped out. I have everything up and working!

[Q] rooted OK but now it continues to try to boot

I rooted my NC yesterday using the auto-nooter 2.12.25. Things seemed OK. I DLed some apps & used them. Got ADW launcher loaded and began setting it up for my preferences. The NC went most of the way through an update cycle even though I had already updated to version 1.0.1. However this time it never got to the green "n" and then it started cycling through the part where it comes up & writes "nook color", continues until the colors quit flashing & then starts back at "nook color".
None of the buttons seem to have any effect. I tried to follow the 'solution' entitled "NookColor Fix Boot Loops". I tried both the auto-nooter SD card and then when that didn't work, I tried the original manual nooter SD card.
Anyone have another idea to fix this. I'd really appreciate some help. A PM would be great or just answer here.
I had the same problem earilier today, I held down the power button until it did a complete reset (about 8 seconds of holding). It is working great since.
Thanks. I had already tried that, several times.
restore to factory and start again?
add http : // www to front of links with out the spaces i don't have the 8 post count needed to post links and
am not going to just reply needless info to 8 post to get rights to post links to help
don't get me wrong i believe it is a very good policy
unrooting
.nookdevs.com/NookColor_UnRooting
flashback to clean stock
.nookdevs.com/Flash_back_to_clean_stock_ROM
i have not tried any of these methods no need to but i do so much messing up
i guess eventually i will with that said this might be a long way around to your solution
read both carefully
Thanks, nookroot but this is not working.
Method 1 for unrooting - Holding those 3 keys together for over 30 seconds has no effect.
Method 2 for unrooting - I can't unroot with method 2 because the NC has to boot before I can go to settings.
Any other suggestions? In fact it seems that if it ever does power off, the only way to make it power on is to plug in its USB cord & this doesn't always work. When it does it just stats cycling. Sometimes it seems to just power up on its own and start cycling.
Whatever happened, since it's rooted I can't return it to B&N and I don't seem to be able to unroot it. Effectively I have bricked it even though many people say that's impossible.
Edit: something new just happened & I was able to go through the method 1 reset. It's booting now & looks like the B&N screen is coming up. I'm not sure how it happened. I'm going to leave it unrooted until I feel adventurous (or foolish) again.
P.S. Came back with version 1.0.0 SW.

[Q] Can't load past "n" boot screen

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?

[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

Nook color will not boot/black screen

my nook color will not boot at all. I formmatted /system and /boot, then it froze. Now I can't boot it up anymore. I was trying to update CM7.
Help please !
Thank you guys.
boot from an SD card. Works every time.
Even backlight doesn'flicker on.
Sorry, but I'll just borrow this thread for my Nook Color nightmare which may be more sinister than anyone else's on this forum.
I've read through Dummies Guide to Fixing 'My Nook Won't Boot' and was unable to come across a post that was able to solve my problem. However, there where three other posters who reported similar symptom as I, and who also were never able to find a solution.
I suspect that my NC, and the three other posters', is truly BRICKED.
Currently my situation is as follows:
- Attempt to power on NC does not yield any response, not even a flicker of the backlight turning on
- Cannot boot from uSD card that had previously successfully booted from in the past (have used it for flashing ROMs to EMMC).
- Attempt to power on while connecting to PC (XP) via USB causes computer to recognise device OMAP3630, but immediately loses it (NC unresponsive as per 1st point).
I had Nookie Froyo 0.6.8 on it for quite some time. And I think I witnessed it die. This is what happened: I turned on the screen using the N button. Everything seemed okay except that it was responding rather sluggishly to my inputs and gestures, and then it just froze (screen still on). I used the power button to try to cycle it but once it turned off that was the end.
I've already followed these suggestions:
- Press power button for 60 seconds.
- Press combination of Power, N, Volume.
- 8 boot attempts (as there is no visible response I press the button for 10 seconds, release it for 5, and then repeat that about nine times)
Hoping that someone could throw some suggestions around before I part with my expensive brick.
It's dead, Jim.
Why not do a warranty replacement?
Rodney
rhester72 said:
It's dead, Jim.
Why not do a warranty replacement?
Rodney
Click to expand...
Click to collapse
My thoughts exactly. Although I don't have extensive android experience, I've got a decent bit of PC time and that sounds like a problem based on faulty hardware rather than improperly installed software.
Sent from my NookColor using XDA Premium App
Other thing is, remember when messing around with flashing roms etc, that your battery is fully charged. Not sure about the nook, but for some phones, they don't charge while in this process and some people have bricked their phones while running out of power doing a flash.
I suspect you might have a battery problem and may not have a charge enough to boot from SD.
I'm in the same boat...
Same thing happened to me. I was fully charged, went to clockwork to boot while trying to update CM7 and now my nook is unresponsive. The only thing I get is the battery too low screen. It has been on its charger for 4 hours. If anyone has any suggestions...
I had the same problem.... wiped the boot and then was unable to boot even with SD card; only got black screen.. Then I decided to hold down the n and the power button at the same time and then after about five seconds I saw my screen flash and I let go of the power button and n buttons. Now the nook is booting fine off of my SD card once again... whew! Won't wipe boot again...
Time to replace this brick
lanje78 said:
If anyone has any suggestions...
Click to expand...
Click to collapse
Well, I've made the decision to exercise the 1 year replacement warranty.
I've been told by B&N customer support that you can simply walk in to a B&N store with the complete package (charger and cable) and they will replace it on the spot. Helps if you take the receipt with you.
For us people who live outside of the US it's a whole different kettle of fish...
UPDATE:
So I sent the NC back to my US seller and had it replaced under the 1 year warranty. I received a refurbished NC, but with the serial number starting with 2010... which I understand indicates a newer version.
I'm still wondering if OCing the NC may have cause the problem on my bricked one... I guess I will find out after I OC it again, which I am certain to do as it improves flash video play...

Categories

Resources