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
My wife and I have Nook Colors and I recently decided to root mine using AutoNooter. I went through all the steps, crossed referenced the steps with other sites, and went through the steps again. Here's the problem I run into; upon inserting the microSD card into the NC(while off)and plugging it into the computer using the USB cable the darn thing won't boot up.
Everything I've tried:
-a different SD card(I have now tried a 4GB PNY microSDHC and a 2G Sandisk microSD.....and a generic microSD card from my cellphone)
-I've tried loading the image from different sites and using different browsers
-I've tried different imaging software
-I've tried using BOTH mine and my wifes NC.
-I've tried it from 2 different laptops(a Toshiba and a Gateway)
-I've tried downloading the image from both laptops integrated disk reader using an adapter and I've tried loading it using an external USB card reader that reads/writes a microSD directly without needing an adapter.
-I've tried de-registering the NC and re-registering.
-I've let the NC sit for an hour while plugged in.
NOTHING. The light on the USB cable goes from amber to green....which is where the whole process ends.
-I'm running firmware v1.1.0 therefore I'm using AutoNooter 3.0
-I tried it a while back when running 1.0.1 using AutoNooter 2.12.25 with the same results. I'm getting impatient waiting for B&N's rumored update so I decided to try again.
-I do know how to format the SD card so that is not the problem
It's gotta be something simple. PLEASE HELP! Thanks for taking the time to read this. So frustrated
I used autonooter yesterday on my nc, and it never did reboot. I waited awhile, then just unplugged, turned it on and the android came up.
I did not care for it so I then did the emmc version of custom froyo 6.8 (as I will never use the NC for how it was intended) and am in hog heaven.
Sorry if you already know this but nothing happens when you boot the autonooter image. The screen stays black. All the magic just happens in the background. All the basic nooter does is enable side loading apps. Some of the others to more. Find your favorite apk and try
adb install myApp.apk
If it works then so did nooter. Find a launcher and go nuts.
vlucchetti said:
I used autonooter yesterday on my nc, and it never did reboot. I waited awhile, then just unplugged, turned it on and the android came up.
I did not care for it so I then did the emmc version of custom froyo 6.8 (as I will never use the NC for how it was intended) and am in hog heaven.
Click to expand...
Click to collapse
Same here. I thought I botched the install but the android showed up eventually when it finally booted and I'm running market apps so i know it worked. Very weird though.
I don't think autonooter has any coding in it to prompt the screen to turn on to let you know its installing, but usually (at least in windows) when you plug in your Nook you can hear it mount to the computer...I usually wait for this, leave it on then unplug//remove the uSD card and boot up my Nook.
What are you using to "burn" the .img to the SD card? If you see the same file written to the card after burning, its not imaged properly. I had this problem the night I bought my nook and it drove me nuts. Use WinImage. From the top menu select Disk>> Restore virtual hard disk image to virtual drive>> select SD card>> select file. The burn should take about 10 secs and you should see a file system structure on the card when opened. If you get an error that the file is in use when you go to burn it, log out, log in and try again or reboot. Burning the image is key, the rest is cake.
Sent from my LogicPD Zoom2 using XDA App
chris peas said:
What are you using to "burn" the .img to the SD card? If you see the same file written to the card after burning, its not imaged properly. I had this problem the night I bought my nook and it drove me nuts. Use WinImage. From the top menu select Disk>> Restore virtual hard disk image to virtual drive>> select SD card>> select file. The burn should take about 10 secs and you should see a file system structure on the card when opened. If you get an error that the file is in use when you go to burn it, log out, log in and try again or reboot. Burning the image is key, the rest is cake.
Sent from my LogicPD Zoom2 using XDA App
Click to expand...
Click to collapse
I've used WinImage 8.5 and Win32DiskImager. I know it has to be an issue with the image but the files on the sd card after it's been written look identical to screen shots I've seen of the image on multiple "how to" websites. How long did you wait before the NC booted up?
Taeseong said:
I don't think autonooter has any coding in it to prompt the screen to turn on to let you know its installing, but usually (at least in windows) when you plug in your Nook you can hear it mount to the computer...I usually wait for this, leave it on then unplug//remove the uSD card and boot up my Nook.
Click to expand...
Click to collapse
According to NookDevs when using the latest autonooter for use with NC firmware v1.1.0 the NC will boot up automatically once it's connected to the usb cable after a few minutes. Not to be confused with the previous autonooter for use with firmware v1.0.1 where you connect, let sit for 10 minutes, then boot after removing from the usb cable and the sd card. Tried that one too with no luck.
donballz said:
Sorry if you already know this but nothing happens when you boot the autonooter image. The screen stays black. All the magic just happens in the background. All the basic nooter does is enable side loading apps. Some of the others to more. Find your favorite apk and try
adb install myApp.apk
If it works then so did nooter. Find a launcher and go nuts.
Click to expand...
Click to collapse
I never get to the point of seeing the new boot up process, skipping log-in, logging in to youtube, enabling softkeys, etc. It's funning that I quote the sequence without actually having done it. It's because I've read the steps so many times.. So frustrating!
You have to connect it to a PC to initiate the boot from SD. You should connect it to a pc where its NEVER been connected to before. A few things you can try. Connected to the PC, hold down the nook's power button for up to a minute. Did you hear a chime on the PC as if you connected a device to it? No? Next, open device manager on your PC with the nook connected. From the Action menu >> scan for new hardware. Did it find anything new? Do see anything with the name "gadget" or portable gadget in the device list? Right click, delete it. Again, scan for new hardware. Did windows find new hardware now? Did it boot from SD? Try plugging into a different PC. This is THE ctritical step.
I had this problem when i wiped my device and rerooted. Because the device drivers were already installed, my nook wouldn't boot n root. Chances are you connected it to your PC before attempting to root. You have to get windows to detect as a new device and the PC should fail to load the drivers. If you get that far with no luck, keep deleting the device from device manager and reconnecting it with the cable. Hope this helps...
vlucchetti said:
I used autonooter yesterday on my nc, and it never did reboot. I waited awhile, then just unplugged, turned it on and the android came up.
I did not care for it so I then did the emmc version of custom froyo 6.8 (as I will never use the NC for how it was intended) and am in hog heaven.
Click to expand...
Click to collapse
Went this route and couldn't be happier with the result. Thanks so much for your input!
OP I have the same issues as you, very frustrating!
How did you solve the problem in the end?
edit: NM figured it out.
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.
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.