Related
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!
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
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.
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...
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.