Bizzare Reset - Has this happened to anyone else? - Nook Color General

I have an autonootered NC at 1.1 (and Dalingrin's OC kernel). I use soft keys and have it set to a long hold on the virtual home key to go back to the stock B&N launcher (I use zeam usually). Today, I went back to the stock B&N launcher and an error popped up saying something about an authentication error and then it immediately rebooted. Upon reboot it took me back to the B&N tutorial (but my keyboard wouldn't work so I couldn't complete it). After another reboot or two it started normally but with the fresh stock interface. ROM Manager was still in my extras and I'm in the process of a restore so hopefully this won't be a serious problem.
Anyhow, I've heard of this happening with opening the B&N shop, but didn't know if this has happened to anyone upon opening the launcher? Any idea why or how to prevent it from happening again? I have opened the stock B&N launcher before with no problem. From what I can tell people decided the reset upon opening the B&N shop was a freak accident unlikely to happen again.

Seseo17 said:
I have an autonootered NC at 1.1 (and Dalingrin's OC kernel). I use soft keys and have it set to a long hold on the virtual home key to go back to the stock B&N launcher (I use zeam usually). Today, I went back to the stock B&N launcher and an error popped up saying something about an authentication error and then it immediately rebooted. Upon reboot it took me back to the B&N tutorial (but my keyboard wouldn't work so I couldn't complete it). After another reboot or two it started normally but with the fresh stock interface. ROM Manager was still in my extras and I'm in the process of a restore so hopefully this won't be a serious problem.
Anyhow, I've heard of this happening with opening the B&N shop, but didn't know if this has happened to anyone upon opening the launcher? Any idea why or how to prevent it from happening again? I have opened the stock B&N launcher before with no problem. From what I can tell people decided the reset upon opening the B&N shop was a freak accident unlikely to happen again.
Click to expand...
Click to collapse
I haven't experienced what you describe, but my rooted nook has lost root. All that works is the B&N stuff it came with. Facebook, Opera, Titanium don't start. Sqlite will only allow me to look at databases on the SD card - says my phone is not rooted. Well it was a couple of days ago. Root explorer will let me look but not mount R/W. Go to the home key (I was using Go Launcher EX) & I get a notification about an unexpected error.
I thought I'd disabled OTA updates in the database but maybe not? I am at a loss. Reroot tomorrow & see what happens I guess.

Related

NookColor reflashes itself back to stock?

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

[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] Nook Color Random Restore (Autonooter 2.12.25)

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

[Q]B&N authentication service!!

*2nd EDIT*
Okay now I don't feel so dumb, I renamed the otacerts.zip thing but i am still getting reset
I did find an application that is call BN authentication service. I can't uninstall it from the normal App installer, anyways to get around this? Like ADB
*EDIT*
Ha I feel so dumb, I just needed to reboot, then change the names. So after i changed the names I rebooted again and its all good now
Thanks eyecrispy
* original*
I have a rooted nook color with a stock 1.0.1 rom, CWR, and a over clocked kernal. I have only 1 real problem, I guess besides not being able to download from the marketplace - my nook keeps on getting reset by B&N! They don't unroot it, and my recovery is still intact, but it really sucks not being able to connect to their shop. It's not that I would use their shop it's just that I accidentaly press it every now and then and it resets my device. I have to back up my device once everyday to make sure nothing gets deleted because sometimes, even when I don't press the shop button, I don't even have to press anything, it resets the device after its been connected to wi-fi for a while. Like the other day, i just set it down to go to the restroom, I come back to find it at the Android setup or the quick setup selection page. When I select Android setup when I press the little android nothing happens. When I select the B&N quick setup it, i can do that no problem. So now I just turn it off from there and load my back up through CWR.
Anyways, is there anyway to stop it from connecting to the B&N authentication service or something? I have seen people with similar problems, but no one seems to have it happen to them over and over and over again.
Plenty of folks have reported this continuously happening. Have you disabled OTA updates?
Sent from my Nook Color
eyecrispy said:
Plenty of folks have reported this continuously happening. Have you disabled OTA updates?
Sent from my Nook Color
Click to expand...
Click to collapse
Really? All th threads I have read people say it happened once but after a reboot it was fine. Maybe I just missed it. If you could please tell me how to disable OTA updates that would be a big help. Thanks
*EDIT*
Found what you meant, I am trying to use Root Explorer but am having no luck. I gave it superuser permissions yet it still wont let me changes any system files

nook keeps waking up, killing battery

I am now on my second nook hd (upgraded from a 7" to a 10")
booth nooks have had the same issue, where i turn the screen off (sleep mode) and then for whatever reason the screen wakes up, (and the lock screen is shown) but it never goes back asleep and eventually kills the battery.
this behavior is random. and doesn't happen all the time.
Once i find the nook turned on, i can make it go back to "sleep" and it will mostly do that.
The nooks are on stock firmware, have most recent frimware and are not rooted.
the case that is used, is not a smart case.
the nook only has 2 applications installed. Astro file manager and bsplayer. using nova launcher
it is kept 99% in airplane mode.
this has been my only android device that doesnt turn off the screen when the lock screen is displayed. (on a side note this is also my only android device that is running stock firmware)
any ideas?
google hasnt been much help...
THRiLL KiLL said:
I am now on my second nook hd (upgraded from a 7" to a 10")
booth nooks have had the same issue, where i turn the screen off (sleep mode) and then for whatever reason the screen wakes up, (and the lock screen is shown) but it never goes back asleep and eventually kills the battery.
this behavior is random. and doesn't happen all the time.
Once i find the nook turned on, i can make it go back to "sleep" and it will mostly do that.
The nooks are on stock firmware, have most recent frimware and are not rooted.
the case that is used, is not a smart case.
the nook only has 2 applications installed. Astro file manager and bsplayer. using nova launcher
it is kept 99% in airplane mode.
this has been my only android device that doesnt turn off the screen when the lock screen is displayed. (on a side note this is also my only android device that is running stock firmware)
any ideas?
google hasnt been much help...
Click to expand...
Click to collapse
When I had a problem with my original nook hd+, verygreen reminded me of trying the bn rom again.
Since your on the bn rom and its fully updated, I'm going to say for you to backup, then do a factory wipe and restore. After that, leave it as-is (no apps, as little setting changes as possible) and see what happens - no nova launcher either - basic and plain untouched. While your at it take away the case too. Perhaps its adding pressure or something else in some crazy way.
If that works then its a start.
If it doesn't then try cm on sdcard and see if it still happens. That way the bn rom could be ruled out.
sandsofmyst said:
When I had a problem with my original nook hd+, verygreen reminded me of trying the bn rom again.
Since your on the bn rom and its fully updated, I'm going to say for you to backup, then do a factory wipe and restore. After that, leave it as-is (no apps, as little setting changes as possible) and see what happens - no nova launcher either - basic and plain untouched. While your at it take away the case too. Perhaps its adding pressure or something else in some crazy way.
If that works then its a start.
If it doesn't then try cm on sdcard and see if it still happens. That way the bn rom could be ruled out.
Click to expand...
Click to collapse
thanks for the suggestions.
i finally had time to wipe and do what you suggested
figured out the case is what was waking it up, but i still had the issue of it never going back to sleep.
i installed go locker. and now its working as expected no more dead batteries.. i am happy!

Categories

Resources