I know other people are having this same issue and it is happening to me quite frequntly now ( sometimes twice a day ) ... I could be doing anything or nothing at all and the nook is just sitting there in standby mod, when all of a sudden the NC just reset's itself back to stock. It does not delete anything and the sdcard is fully intact, but the nook is now back to stock and at the setup screen !!! Thank god I have ClockWork Mod installed and a copy to restore, so I can just restore my old system .... but it is just a matter of time until it resets itself again.
What could be causing this ??? Can anyone help me and the others that this happens to, and try and figure out why ?
My NC is running 1.0.1 and is fully rooted (with auto nooter ) and all the little extra's installed ( like geographic location fix and cell service turned off and adhoc support ect... ) I am also using ZEAM as my launcher. Any other info needed ??
There is a post about this in another sub forum here but I think this is a better place to post it.
Thanks for any help with this !!!
John
Just an update to my above post..... now It is factory reseting about every hour. What the heck !! What could be causing this ??
I posted about this on another thread. In my case it seemed to be a mechanical failure of the power button. It was stuck half on and the tiniest movement would trigger it. It actually seemed like the button had dislodged slightly and got stuck under the case. My replacement machine seemed to have a more sturdy case, and also came loafed with 1.01. There's several reports of this on the vanilla NC sites.
Sent from my NC using XDA app
bonobomidwest said:
I posted about this on another thread. In my case it seemed to be a mechanical failure of the power button. It was stuck half on and the tiniest movement would trigger it. It actually seemed like the button had dislodged slightly and got stuck under the case. My replacement machine seemed to have a more sturdy case, and also came loafed with 1.01. There's several reports of this on the vanilla NC sites.
Sent from my NC using XDA app
Click to expand...
Click to collapse
Ummm, well that would have nothing to do with the device reseting into factory default mode. My NC is 100% rooted and even if the power button was to get push in by mistake or by the case, it would not reset the device to stock.
But thanks for the reply ....
Are you using Titanium Backup to restore your apps? Don't restore the system app data. It will mess with the BN authentication, forcing resets.
ewong90 said:
Are you using Titanium Backup to restore your apps? Don't restore the system app data. It will mess with the BN authentication, forcing resets.
Click to expand...
Click to collapse
Mmmm ok I will keep that in mind. Thank you.
Boot Loop Even After Factory Resets
Hopefully my experience will help some other frustrated or novice users that may encounter their NC doing a random factory reset.
The B&N reset happened to me this past Fri. I was on firmware 1.0.0 with 900MHz kernel flash, Zeam, and many market and sideloaded apps. I was not in any B&N apps. I had been using this configuration for 3+ days with no issues (no reboot or reset issues prior to this and had my NC since late Dec 2010). All of a sudden a message stating that the Nook encountered a problem and that the NC would be reset to its original state??? message flashed. Since I had Clockwork installed, the NC simply booted into Clockwork. I had not done a Clockwork backup (read about an incomplete backup). I tried cycle powering, but the NC simply stalled after the black NC screen (the screen after "loading..."). I tried to flash the 1.0.1 kernel that was posted, but still stalled at the same screen. Since Clockwork was installed, I could not figure how to do a two/three finger salute to initiate a factory restore. I tried everything to get out of the boot loop or even perform a factory reset.
I followed NookDev instructions here http://nookdevs.com/NookColor_Fix_Boot_Loops
which for some reason invoked the factory reset (I still had adb functionality at that point). I performed the factory reset, but the process reached the end and indicated that it failed. Upon restart, I had lost Clockwork (probably because the orig boot image was restored) and the NC stalled at the same blank screen again. I did the two finger salute (power button + N button) which started the factory reset process (since I did not have Clockwork anymore). This time the factory reset indicated it completed successfully. However, upon restarting, the NC still stalled at the same screen. I tried several more time to factory reset my NC (from then on indicating successful factory reset), but still stalled at the same screen. Since I had lost Clockwork, I tried to boot of the SD card (flashed with Nook Froyo) thinking that I could adb the boot files onto the NC. Nookie Froyo hung at the "A N D R O I D" msg at the bottom even though adb devices showed 1122334455?? Thinking I had nothing further to lose, but to possibly return a bricked NC, I kept attempting performing factory resets. After the third or fifth (lost count) factory reset, the factory reset that time was different. It read "Performing ??? upgrade." Upon completing and restarting, I finally got past the blank screen I was stalled at. I tested the factory state several times by performing several reboots and several shut downs and boot ups. In device info, it read I was on firmware 1.0.0 which made sense since I had not upgraded to 1.0.1 (1.0.0 should still be the image in ROM). I rooted with Autonooter then installed all my previous apps and flashed the 900MHz kernel. I performed most/all the mods posted including disabling octcerts against upgrades. Yes, I ran a few Clockwork backups!!!
In short, if you encounter the dreaded NC factory reset for no reason, restore with Clockwork/Titanium. If you are stuck in a boot loop as I was (even after factory resets), keep at it. Unless there is something ridiculously wrong with the ROM/NC (hard to brick as other devs have noted), your NC has to restore from the image in ROM. You may have to manually interrupt/boot loop 8 times ??? like I did (24-40+ times???), but keep at it...it should restore.
Related
I had my phone randomly soft brick today and I was wondering if someone might be able to shed some light on what happened to me.
So, my phone is a Samsung Galaxy S GT-I9000M on Bell Canada. Rooted, ADW, Clockword Recovery, *No* Lagfix (I removed it), GPS Update. Today I went to open an app and the phone froze and subsequently rebooted. Upon restart the boot animation displayed for a while and then went to a black screen. Phone did not respond to any input. Force restarting led to the same effect. Tried a battery pull, no dice. Wiped the cache partition, no dice. Booted into recovery then clockwork recovery. Restored to my last nandroid backup. Phone restarted, displayed boot animation for a long time then went to the black screen and accepted no input. Restored to my nandroid before that, no luck. Wiped dalvik cache, no luck. Connected the usb, booted into recovery, opened android commander, and pulled down a copy of everything on the internal sd card. Finally, while walking to the Bell Canada store to get a replacement, I did a factory reset... The phone booted.
So what has me extremely curious is what did a factory reset do, that restoring from a nandroid backup didn't? And what the hell happened to the phone that an app crash trigged a quasi soft brick. Let me know if anyone has any ideas.
Thanks!
I had the same thing happen to me all the time on the XXJPC TOM after having installed the TaskManager update (it was 1.4 back then) from Samsung Apps. Everything seemed fine until I rebooted. After the boot animation played, there was the "I'm crashing" vibration (vibrating once, then three times shorty after) at which point the phone went off. I had this happen four times in a row before I figured out (by accident) that it's the TaskManager update that did this to me. Only a factory reset could revive the phone. Did you, by any chance, install the TaskManager update, too, on a Froyo ROM?
Hope this helps a bit. It was rather frustrating to me.
I'm just running a rooted stock i9000 rom (android 2.1). No task manager update.
I did manage to recover. The process ended up being this:
Backup data on internal sd card while in recovery mode
Factory reset
Wipe cache partition
Boot
Install rom manger
Copy data back to internal sd card
Restore from most recent nandroid backup
The only thing I can think of is somehow I suffered a corruption of my data partition, so the factory reset fixed it by wiping the partition. Not sure if that's a possible explanation.
Sent from my GT-I9000M using XDA App
Just mandatorily installed the update over the air, and after that my rooted NC becomes brick, can not get to the home screen anymore, any solution? what did BN do on this update?
gtechnical said:
Just mandatorily installed the update over the air, and after that my rooted NC becomes brick, can not get to the home screen anymore, any solution? what did BN do on this update?
Click to expand...
Click to collapse
Do a factory reset, install the update, then use the new autonooter.
how to do a factory reset? thanks, I am a newbie to this area!
Not sure how much I can help-
Just how "bricked" is it?
A truly bricked device will do nothing. It will not start or do anything whatsoever.
A machine that is thoroughly HOSED may get stuck in a boot loop, or try to start and fail every time you press the power button.
When I forced the update manually it took a few minutes to take and reboot; how long ago did it do the update?
Have you tried connecting with adb yet?
Have you tried booting it with a nooter or auto-nooter sd card yet?
http://nookdevs.com/Installing_the_1.0.1_update_on_a_rooted_NC
Instructions for manually updating.
Here is my situation:
Around 9:30, my NC started updated itself, it reboot in about 15 minutes, and takes a very long time get to the "nook color" screen, then took another 10 minutes letting me select "home or zeam", after that, it has no response.
I tried to reboot, it got up to the "Nook Color" welcome screen, no further response!
I tried to factory reset, not working through adb, it did appear on the adb devices command!
Do a factory reset and start over.
I ran into a similar problem, but here is what happened to me:
1. I reset the device to factory settings.
2. I rebooted the nook 8 times, stopping the boot process. This took my NC back to factory version and no rooting at all.
3. Installed NC update 1.01 per B&N instructions.
4. Used AutoNooter (latest version for 1.01). AutoNooter rebooted the device as it is supposed to.
5. After AutoNooter reboot, I installed Astro File Manager and then after that the NC stopped responding to screen touch.
6. I held the power button to shut the device down. Strangely, the screen shut off and it appeared to be shut down, but I think it did not truly shut down.
7. I could not turn the NC back on. I tried to reset to factory settings 2-3 times and no response.
8. I plugged in my NC as if to charge, and it went through the boot process.
and it has worked just fine since then. To be honest it kind of scared me, because I love this thing to death, but I remained calm and kept at it and it was not bricked. I guess what I'm trying to say is that before you post here that the new update bricks the NC, you should be absolutely sure it is bricked and not just frozen like mine was.
gtechnical said:
Just mandatorily installed the update over the air, and after that my rooted NC becomes brick, can not get to the home screen anymore, any solution? what did BN do on this update?
Click to expand...
Click to collapse
Brick, like you can't do anything at all anymore, might as well lay it on papers, use it as a door stop and pour cement to build a house?
That's what bricked means... If you still can access it via ADB, run recovery, etc.. it is far from "BRICKED"...
-CC
I did a manual shutdown because I couldn't kill some goofy NES rom app. Now it won't reboot. Do I have to replace the SD card with the imaged one every time I want to restart this thing?
No... Sounds like you medded something up when you manually rebooted, though. Oh well, just restore to factory and reroot and you should be fine Id bet...
Sent from my NookColor using XDA app
Crapcrapcrap. I think I broke it.
I tried to do the factory reset as you suggested but it wouldn't do ANYTHING. I did some more searching and finally got it to work by holding power button plus volume up plus home button and then holding power button. But it went to the future of reading screen and then the Nook screen and wouldn't do anything. More searching told me to reset it 8 times and on the 9th it would completely restore factory, so I tried that.
It seemed to have worked but then went into ANDROID boot/initialize sequence and was repeating that over and over and over. Seems weird that it would boot Android after a complete reset, but I digress....
I thought maybe it was because the imaged card was not in, so I inserted that into the slot. Same thing....repeat over and over Android boot up sequence.
I powered it down manually and it seemed dead again - not booting back up by traditional means. I tried holding different buttons, whatever...FINALLY got it to the future of reading screen again. Proceeded to boot up - Android sequence....you guessed it, on repeat. No card in now. Crap!
Please help! Newbie here not sure what to do!
your case is similar to what I experienced yesterday. I took out my memory card, and did factory reset and 8-time reset trick. On the 9th it installed a fresh rom (1.0.0), and booted successfully afterwards.
jerry_smith_80 said:
your case is similar to what I experienced yesterday. I took out my memory card, and did factory reset and 8-time reset trick. On the 9th it installed a fresh rom (1.0.0), and booted successfully afterwards.
Click to expand...
Click to collapse
Thanks for the response jerry. Something is definitely jacked here.
I did the 8-time reset again....Got the message it was installing a software update, the future of reading screen, etc.....and then it went into the freaking Android boot sequence on repeat again. Why is it booting up Android instead of 1.0.0?
No memory card here, either. I am totally flustered.
I would really appreciate any help that anyone out there can provide. Did I brick this thing?
Update. I powered it down from the Android reboot cycle and then followed the instructions here to perform another factor reset. Somehow this time it worked. It rebooted with 1.0.0 and made me go through the setup steps again.
I think I'm going to upgrade to 1.0.1 this time before rooting....I was having some bugs and somehow it culminated in the above debacle. Hopefully it is smooth sailing from here.
Something is still messed up here and I'm not sure what's going on.
As mentioned above, I finally got the thing to reset, clear, and boot back up with 1.0.0....or at least so I thought.
I had only ordered one book and it was present on the reboot - not sure if that is significant or not. At any rate, my initial plan was to update to 1.0.1 like I mentioned since I seemed to have issues/bugginess before w/ 1.0.0. I downloaded the .zip file to my desktop, copied it over exactly as instructed and the thing never rebooted with the update. I waited and waited. I put it to sleep and waited. I woke it up. I tried to navigate to it. Nothing.
Ok, perhaps another fluke. From what I've read the update is unimportant anyway. So I tried to root again with auto-nooter on 1.0.0. Followed steps again to a T. Even re-downloaded all of the files to my computer just to eliminate issues. Put my card in, plugged it into my laptop....never found any drivers. CN stayed off. Tried to boot it up manually - nothing. Tried to reset it manually w/ Power + home + volume up. Nothing.
Finally I removed the SD card and booted it up and it worked. During initialization I quickly put my card into the slot and it booted Android successfully....much like the first time I rooted it.
It is working...but not like it is supposed to. I'm wary to go down this path again considering the trouble I eventually encountered last time. Should I start over? What the hell did I do wrong?
Is there another way to invoke the ROM update during the boot up process (maybe as a last option restore measure?)?
I somehow got the ROM update to run during my random reset issue (after 3-5 factory resets???).
http://forum.xda-developers.com/showpost.php?p=10675682&postcount=7
I suspect that somewhere in the boot up algorithm, there is logic that attempts the ROM update if factory resets do not fully boot NC.
# factory resets fail => run ROM update (absolute factory reset + data wipe???)
Has any dev come across coding during their mods/hacks/investigations or know how to activate the ROM upgrade process during boot? This could be possibly used as a final attempt to break the boot loop if factory resets don't work, and you don't have/lost Clockwork, or can't boot Nookie Froyo off of uSD as was my case.
escabar said:
Is there another way to invoke the ROM update during the boot up process (maybe as a last option restore measure?)?
I somehow got the ROM update to run during my random reset issue (after 3-5 factory resets???).
http://forum.xda-developers.com/showpost.php?p=10675682&postcount=7
I suspect that somewhere in the boot up algorithm, there is logic that attempts the ROM update if factory resets do not fully boot NC.
# factory resets fail => run ROM update (absolute factory reset + data wipe???)
Has any dev come across coding during their mods/hacks/investigations or know how to activate the ROM upgrade process during boot? This could be possibly used as a final attempt to break the boot loop if factory resets don't work, and you don't have/lost Clockwork, or can't boot Nookie Froyo off of uSD as was my case.
Click to expand...
Click to collapse
It does the reset automatically after 8 resets. There's actually a counter file that gets updated after every failed boots and is part of the original way to restore a rooted NC to factory stock.
Do a search of the dev forum, maybe look at the mobileread forums too and nookdevs for more info... They obviously put it in as a failsafe, probably along with the default of booting from uSD card... which makes it difficult to brick a NC.
Reset after 8 failed boots yes. But if you take a look at the link to my post, my NC did not boot even after multiple successful system restores - as shown by the green check mark on the SD card icon at the end of the process (I did complete the 8 count failed boot sequence to system reset many times). Only after 3-5 times of these 8 count failed boot process => system /reset/restore successful did my NC enter an upgrade process to flash/upgrade whatever firmware was on my device. This is the mode/process (upgrade process) I am asking about.
I had posted in another thread regarding a boot loop but now I see something different and I wonder if it can help.
I did rename otacerts.zip and I guess in the coming days I will really see whether this has any effect on my problem BUT I f was messing around last nite after restoring a nandroid and thought I was bootlooped yet again...
I was wrong.
I pressed the N buttong while in what I thought was loop or stuck then power for like 2 seconds and voila it boots... Ive done this 6 times now but I still have not figured out whether the power button actually helps or if it's the N button.
Previous to this my wife always had it when this happened and while I can say with a certain amount of pride in her that she can reboot recovery and restore a nandroid... she would always call to say its stuck at "the future of reading", then at home later on I discovered that I could get it to boot.
Now left alone, without coxing it with N/Power at "future of..." it stayed there all day the first day and the next too until I got it at home (she used a nandroid but then never shut it off the next day so she could have it for her commute from NYC.
Anyone have a similar result? Im very happy that I don't have to do restores but she does'nt have enough practice/patience to do it yet.
escabar said:
Reset after 8 failed boots yes. But if you take a look at the link to my post, my NC did not boot even after multiple successful system restores - as shown by the green check mark on the SD card icon at the end of the process (I did complete the 8 count failed boot sequence to system reset many times). Only after 3-5 times of these 8 count failed boot process => system /reset/restore successful did my NC enter an upgrade process to flash/upgrade whatever firmware was on my device. This is the mode/process (upgrade process) I am asking about.
Click to expand...
Click to collapse
You need to learn to search the forums and Google as there are several articles about this in the dev sub-forum and wiki's as I indicated in my reply.
cutterjohn said:
You need to learn to search the forums and Google as there are several articles about this in the dev sub-forum and wiki's as I indicated in my reply.
Click to expand...
Click to collapse
I have Googled/searched extensively and have read the Wiki, extremely informative NookDev portal, and XDA NC dev forum. I have not seen any reference to triggering the ROM update during boot up process to restore firmware (which my repeated system restores seem to have done). ROM updates have been possible through GUI once the device has booted up and the user has registered with B&N.
Therefore my question still stands. If I have missed the obvious, please paste/direct me to the thread/posting I have missed regarding boot loop recovery through ROM upgrade during boot cycle. Thanks.
Perhaps this is what I encountered, but I didn't do it right...I let my NC boot as far as possible each time. For those who can't boot off of SD and have lost Clockwork to restore/restore partitions try the method below.
http://forum.xda-developers.com/showpost.php?p=9829898&postcount=16
When you say you updated, you mean that your NC booted to v.1.0.1? Are you sure about that? That would be a miracle, if you nook is a stock 1.0.0. By miracle, I mean that's impossible.
I think you're confused. There are two different resets available on the nook color. One will erase and replace /system, the other will erase /data. The first one is triggered by 8 failed boots, the other by power+n booting and holding until seeing the reset screen.
In your case, I'm inclined to say that you ended up doing both resets, which made your NC funxtionnal again. Note that you should start with the 8 failed boots reset!
Sent from my HTC Desire using XDA App
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
whoisthisis said:
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
select recovery by holding the vol buttons and power on boot just like fastboot. press vol - for recovery. when u see dead droid hit both vol up and vol down and theres the recovery
Thanks, I was finally able to get into recovery. Wiped data and did a factory reset which again got stuck at the logo screen. Went back into fastboot and ran RSDlite again to flash the stock ROM which gets me to the "Welcome to Droid4" screen where it says "touch the android to start" but the touchscreen is unresponsive. Starting to think there is something physically wrong with the phone....
send it to motorola, I've heard their customer support is pretty good. but if you voided your warranty by rooting/flashing other roms, I've heard bricking the phone and sending it in works to get a new one too
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
whoisthisis said:
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
Click to expand...
Click to collapse
So it has been a couple days now and the phone works totally fine. It looks like the problem was that by removing whatever bloatware that I did, the phone's OS got borked when VZW pushed an update of some kind. Flashing the stock ROM without doing a factory wipe would temporarily solve the problem but eventually the update would get pushed again and the whole thing would lock up again. The factory wipe + reinstall seems to have been the solution to the problem.