Related
something interesting happened to my NC last night. i was messing around with system apks, trying to get better access to the system settings. i copied Settings.apk and SettingsProvider.apk from the 2.1 emulator to /system/app the NC. they didn't work, so i replaced Settings.apk with the original, but forgot to replace SettingsProvider.apk. bonehead mistake. anyway, upon rebooting, the device was stuck in a bootloop. it would get to the white "Nook Color, by Barnes and Noble" boot animation, and just loop over and over. i tried the factory reset twice, but as i expected, it didn't help.
i decided to give up for the night, and left the NC plugged into AC power, bootlooping over and over, just to see if anything would happen. after about 30 minutes, i tried to shut it down by holding the power button. the screen went off, and i set it down. when i looked back a few seconds later, the NC was booting again. this time, it came to the screen shown in the attached photo. on the screen, it says "A new software update is being installed. This will take a few minutes."
the process finished, and the device booted up into a fresh, clean, non-rooted 1.0.0 installation! a real software update wasn't installed. it seems the device decided to reflash the original ROM on itself. can it be that the NC is smart enough to know when something is catastrophically wrong, and flash back to stock? either way, i'm happy to have my NC back in business
pokey and I were talking about this in another thread (though he's better at dissecting this stuff than I am). There's a counter for unsuccessful boot attempts, and after 8 it apparently flashes "factory.zip" from partition 3, which is a full clean factory dump.
This actually happened to me, sort of, two nights ago. I was messing around with system settings, but didn't change anything too important...or so I thought.
Shortly after, I was using my Nook, as it was working normally, and the initial setup screen popped up, said something about being unable to authorize my account, and then went ahead and factory reset itself,forcing me to have to re-root. Pretty annoying, and it was odd, since my Nook seemed to be working fine.
It may be worthwhile to make a modified factory.zip so devices wouldn't lose root, no?
I haven't yet encountered this problem, but it would suck to have to reformat my microSD card if this should happen.
tokyomonster said:
This actually happened to me, sort of, two nights ago. I was messing around with system settings, but didn't change anything too important...or so I thought.
Shortly after, I was using my Nook, as it was working normally, and the initial setup screen popped up, said something about being unable to authorize my account, and then went ahead and factory reset itself,forcing me to have to re-root. Pretty annoying, and it was odd, since my Nook seemed to be working fine.
Click to expand...
Click to collapse
Mine did this exact same thing too. I messed with the settings apks and then when I went back to the B&N home screen an error about not being able to authorize and the device needed to be reset. then it rebooted and performed a reinstall of 1.0.0
clockworx said:
pokey and I were talking about this in another thread (though he's better at dissecting this stuff than I am). There's a counter for unsuccessful boot attempts, and after 8 it apparently flashes "factory.zip" from partition 3, which is a full clean factory dump.
Click to expand...
Click to collapse
well there you have it. a nice feature, for the reckless
any idea where the counter is kept?
might there be some way to put factory.zip on the SD card, and force a flash? this would just be a parachute in case something gets too messed up for the failed boot counter to work.
This can be done manually too. Look on nookdevs.com for NookColor_UnRooting
Withfeeling said:
This can be done manually too. Look on nookdevs.com for NookColor_UnRooting
Click to expand...
Click to collapse
That isn't the same thing. It only fixes a few things (like Ramdisk, obviously), while this thread is referring to a complete clean /system.
clockworx said:
That isn't the same thing. It only fixes a few things (like Ramdisk, obviously), while this thread is referring to a complete clean /system.
Click to expand...
Click to collapse
actually, in a quiet, unassuming box at the bottom of the nookdevs unrooting page, it does describe a method to flash back to stock. apparently you hold volume down (minus) while powering on. it's easy to miss. i'll break that bit of information out into it's own page.
Ben74 said:
actually, in a quiet, unassuming box at the bottom of the nookdevs unrooting page, it does describe a method to flash back to stock. apparently you hold volume down (minus) while powering on. it's easy to miss. i'll break that bit of information out into it's own page.
Click to expand...
Click to collapse
nookdevs wiki updated:
http://www.nookdevs.com/Flash_back_to_clean_stock_ROM
Given this possibility, is there a way to backup a rooted NC so it would be easier to rebuild after an inadvertant flash.
Some of us noticed that "quiet, unassuming box".
blacter said:
Given this possibility, is there a way to backup a rooted NC so it would be easier to rebuild after an inadvertant flash.
Click to expand...
Click to collapse
This, built-in, mechanism seems like a pretty bullet-proof protection against bricking your Nook Color. The Nook Classic has a similar mechanism. I think it's a great idea and I wish all these new tablets had such a capability.
I'm loving the Nook Color but other things require the money right now so it's going back, for now.
I just did the Home+Power key combination and it did a reset. I re-registered the device to make sure Angry Bird and a few other things were gone and they are. I got a notice at the bottom of the home screen saying something about a software update and it just said I was currently on 1.0.0, I clicked it and it went away. But, in Settings and Device Info there is a Erase & Deregister Device option. When I click the option it says the following "This will remove all digital books and files, including side-loaded content, from this device. The titles you have purchased will remain in your B&N account." I find this interesting since it specifically mentions "side-loaded content" and I'm wondering if this also triggers the 'factory.zip' file and as a complete factory hard reset of files and all. I haven't seen it mentioned anywhere else so I thought it might be worth mentioning.
Cheers
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!
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?
Not sure if this discussion has already happened.
I have noticed twice since rooting my nook (with 2.12.25) that it has randomly restores back to 1.0.0 (or seemingly).
The first time it was just sitting beside me and it did one of its un-commanded restarts. I noticed that it was reloading the original 1.0.0 version. I lost everything and the nook was unresponsive after finishing. I followed all the hard reset rules and then upgraded to 1.0.1. I then autorooted again and reinstalled all apps.
Last night it did it again while I was using it. I was reading a book and then went to check email. I got an error message something like "invalid authorization" and that it was reloading the base software. I let it do its thing and go through its reboots. I also let it automatically update to 1.0.1 before I touched it. I re-registered it. Now when it loads it doesn't show the normal rooted nook boot screens. When I go into extras I see only the stock apps plus the additional ones that the auto-nooter loads (everything else gone). I tries to get me to log into LogicPD Zoom (Google) but it fails to load.
Has anyone else seems this?
Is there a way to re-load or fix the nook color install without having to go through the complete wipe process?
Once I fix is there some setting we can change to prevent it from happening again?
Thanks
After nootering the nook, I proceeded to load clockwork mod and made a backup of the OS. Now when it auto restores, I can reinstall the backup from clockwork mod by holding both Power and the Nook Key for five seconds when powering on.
Still don't seem to know how to stop the auto restoring though
Mine restarts too, has since I rooted it. Thankfully, there is no data loss, just an inconvenience. If there were a log being kept (like in other OSs), I could at least go there to find out what is crashing it.
Acts like a low memory restart, but that isn't what it is.
TJD
Wanted to add that mine does this also. It has happened 3 times in 4 weeks. Thank god for ClockWork it is not to big a deal now to restore. I wish someone could figure this out tho.
Mine actually randomly boots up (I'll have it off, then hear it start up a few hours later). Not sure it's related, but thought I'd mention it in case it turns out to be.
Sent from my PC36100 using XDA App
Mine used to restart everytime it went to sleep. Happens to alot of people. SetCPU and On Demand usually fixes it. There is like 2 or 3 of these threads in Q&A
straby187 said:
Mine used to restart everytime it went to sleep. Happens to alot of people. SetCPU and On Demand usually fixes it. There is like 2 or 3 of these threads in Q&A
Click to expand...
Click to collapse
Except they're talking about the system restoring itself, not rebooting.
It has to reboot to restore. Thought if you fix the reboot problem it would help maybe not... My bad
I'm autonooted on 1.0.0 and have never had an ota restore or update.
Sent from my Nook Color
Have you guys made sure to rename the otacerts file after rooting?
There are several active threads on this. In my case it was a faulty power button. I went ahead and exchanged the unit. Replacement is 1.01 and feels like the case is sturdier. Might be imagining that. Check my other posts on the subject. Good luck.
Sent from my NC using XDA app
HI All,
So, i have a brand new NC. I was eagerly looking forward to using it as a tablet.
So, here are the steps:
1. I open it, turn it on, register it on B&N, play around with it; power it all the way down. (never hooked it up to my PC).
2. I burn auto-nooter3.0 on to a microSD card (using http://forum.xda-developers.com/showthread.php?t=942424) as my gospel.
3. Place microSD card in NC; hook up to PC -- and, nothing.
It does absolutely nothing. it doesnt boot up, it doesnt do anyhing.
now I can't get it to turn on at all.
Thanks for your thoughts on what I should do next??
Have you taken the SD card out and tried powering it on?
I'm not sure exactly what went wrong, but I would re-read the auto nooter steps, and like said above remove your sd card and see what happens.
Also you need to read more of the forums and see the NC is extremely hard to brick...
and figure out the multiple ways to fix it. there are forums where you can post issues with the bricks and i'm not sure the dev forums is where you want to do that. Many devs may not have time to help you and those who are skilled in this area aren't searching here.
Sometimes it takes hitting the power button several times in a row before it responds.
Yes, took out the microSD card, and tried to power on--- and, nothing. it
Take your power cord and plug it in and press the power button repeatedly somewhat fast until you see the screen flicker, then stop.
I see you missed the first step. Charge it up. Try plugging it in for a while
Hold the power button down for 5-7 seconds until it resets
Sent from my NookColor using Tapatalk
When you plug the nook color into the computer IT WONT DO ANYTHING!!! WAIT FOR IT. Turn the sound up on your computer you'll hear it connecting, disconnecting, etc. Just be patient, jeez! Learn to carefully read.
Sent from my NookColor using Tapatalk
Autonooter 3.xxx.x is for B & N firmware 1.1 You said your NC was brand new... out of the box it could have 1.0.0 or 1.0.1 firmware as well--most likely it wasn't 1.1 If you turn it on and off enough times (theres a correct point at which to turn it off as it is still booting, then turn back on--repeat 8 times) it will trigger a self-repair back to stock. You can get the side-load update and instructions from 1.0.1 to 1.1 from B & N web site. Your NC is not a brick, it's just feeling lousy at the moment
You still broke?
I feel your pain
Try viewing these videos and following the directions EXACTLY. First go back to stock, re-register your NC with B&N, make sure your firmware is updated to 1.1.0 (this is important because autonooter 3.0 can only be used with that firmware), get a gmail account if you don't have one, then try to root again.
To go back to stock:
http://www.youtube.com/watch?v=U_gNvZGSJD4
Rooting with autonooter:
http://www.youtube.com/watch?v=MUoHALWvPts
Written directions here:
http://forum.xda-developers.com/showthread.php?t=942424
Good luck!