Having a bit of an issue here. I did the 8 failed attempts, it reinstalled the stock rom, or so I thought. When it books it still shows the nook color android screen, then asks if I want to continue with Soft Keys or Home screen...
Any ideas?
Weird. I had to do the 8 failed attempt wipe to restore mine as well and it worked. Maybe try again?
you need to do the 8failedboots which wipes /system...
and do a factory reset which wipes /data. with NC turned off, hold down N and power on.
On my third attempt now.. Just rebooted, and it still shows the android Noon COLOR (rainbow animation). And still has softkeys installed..
EDIT: Thanks cabbieBot, didn't see your post. Will do that now.
Related
Well here goes, I already reflashed the stock rom once from autonooter. 8 reboots then the stock rom becomes reflashed... Well in an attempt to return to stock 1.0 and install the updated autonooter I seem to have bricked my nook.
I can force reboot the nook 8 times and then the system update installed successfully... So it seems (progress bar reaches the end and nook reboots) but the splash screen is not stock! It runs the nook dev splash screen and will not boot. It will bootloop over and over. I tried another system reflash but same thing. What can I do?
Is it possible to run the autonooter sd card image ? Any other ideas?
Thanks
You need to wipe the NC. Power off. Hold power and home until it wipe screen appear. It might start wiping automaticlly or you may need to press home continue. Don't remember.
The 8 boot method is only half of the system wipe process. You still need to wipe /data. Steps to do that are at: http://nookdevs.com/Flash_back_to_clean_stock_ROM
It worked! Thanks
I could have sworn I did that several times. I had to hold both the power and nook button until the unit shut off. Then on the next boot attempt it gave me a data wipe option. Tricky little unit
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.
I would post this in the correct forum, but for whatever reason this website won't let me.
Not sure if anyone can help, but I had been running the CM7 rom in my Nook Color. However I wanted to restore back to the stock 1.1.0 firmware. But nothing is working for me.
And whenever I go to apply the stock 1.1.0 firmware, it starts to, then quickly aborts.
I've also tried the 8 times reset method, which looked like it might work, but it just sits on the N logo, loading screen and never finishes.
I just fixed it now. I held down the power button and the N button for like 30 seconds and it gave me options to reset, which fixed the problem.
Hi all, I'm having some serious booting issues on my touchpad running CM7. I always seem to get this error when I start it up:
Selected: 'boot CyanogenMod'
Loading '/boot/uImage.CyanogenMod'...OK
Checking uImage...Invalid Data CRC
BOOT FAILED!
Press SELECT to continue
, or on anything else I want to boot.
Then I have to do a power + home button restart a whole bunch of times before it successfully boots into webOS/CM7. This is a procedure I have to go through every time I turn on this device, so you can imagine it takes me anywhere from 5-10 minutes to finally get into the home screen.
I do however can see this coming, on that initial moboot screen, there is a dashed green line that randomly appears at times; this is an indication that the boot will fail. Also sometimes it goes through to booting android, but then boot loops back to moboot then displays that message again that I mentioned above.
To fix this I've been trying to avoid a full re-installation of CM7 but I've wiped the cache many times and did a full wipe back when this problem started.
Any suggestions for a fix? Thanks.
TPizzle said:
Hi all, I'm having some serious booting issues on my touchpad running CM7. I always seem to get this error when I start it up:
Selected: 'boot CyanogenMod'
Loading '/boot/uImage.CyanogenMod'...OK
Checking uImage...Invalid Data CRC
BOOT FAILED!
Press SELECT to continue
, or on anything else I want to boot.
Then I have to do a power + home button restart a whole bunch of times before it successfully boots into webOS/CM7. This is a procedure I have to go through every time I turn on this device, so you can imagine it takes me anywhere from 5-10 minutes to finally get into the home screen.
I do however can see this coming, on that initial moboot screen, there is a dashed green line that randomly appears at times; this is an indication that the boot will fail. Also sometimes it goes through to booting android, but then boot loops back to moboot then displays that message again that I mentioned above.
To fix this I've been trying to avoid a full re-installation of CM7 but I've wiped the cache many times and did a full wipe back when this problem started.
Any suggestions for a fix? Thanks.
Click to expand...
Click to collapse
When you wiped the cache, did you get the dalvik, too?
Yes I wiped the dalvik as well, but all that does is make the initial boot longer (when I manage to get it to successfully boot that is).
Did you try to reinstall/re flash CM7? You don't lose anything by doing that, and you could do it right from Clockwork recovery. Maybe something got messed up in the installation and reinstalling it would fix it.
Will give it a shot and let you guys know. Thanks for the input. Also one more question, do you guys go through the same thing at all? Or are all your initial boots successful straight to the home screen like any other Android device. Thanks again.
TPizzle said:
Hi all, I'm having some serious booting issues on my touchpad running CM7. I always seem to get this error when I start it up:
Selected: 'boot CyanogenMod'
Loading '/boot/uImage.CyanogenMod'...OK
Checking uImage...Invalid Data CRC
BOOT FAILED!
Press SELECT to continue
, or on anything else I want to boot.
Then I have to do a power + home button restart a whole bunch of times before it successfully boots into webOS/CM7. This is a procedure I have to go through every time I turn on this device, so you can imagine it takes me anywhere from 5-10 minutes to finally get into the home screen.
I do however can see this coming, on that initial moboot screen, there is a dashed green line that randomly appears at times; this is an indication that the boot will fail. Also sometimes it goes through to booting android, but then boot loops back to moboot then displays that message again that I mentioned above.
To fix this I've been trying to avoid a full re-installation of CM7 but I've wiped the cache many times and did a full wipe back when this problem started.
Any suggestions for a fix? Thanks.
Click to expand...
Click to collapse
Sounds like you either have corruption on /boot filesystem or faulty
hardware.
I would try running webOS doctor and then re-installing moboot/CM/etc.
with ACMEInstaller. This should not require a reinstall of apps, etc.
If you still have the same after that, then you probably have some bad
hardware.
Ok so I did the suggestion of jcsullins. Did webOS doctor with latest version (3.0.5) and re-installed moboot. A funny thing happened though, after the installation of moboot, the cyanogen and clockwork settings did not show up on the moboot menu, only the webos, recovery for it, shutdown and reboot. This was fixed with another re-installation of moboot. Long story short, everything seems to be fixed, my data and settings are in tact, and I just turned it off and on (not reboot) 6 times now with each initial boot being successful. Just posting this to thank you guys and for anyone else in the future that may have this problem. Thanks again!
same problem with moboot disappearing after the update. ive reinstalled moboot three times and still cant get the menu to display the cyanogen or clockwork options.
Is there something I am doing wrong?
edit: ended up adding moboot, the original CWM, and the latest XRON build and running ACME Installer and all is well. Just cant install preware to the touchpad since i used webdoctor to install the latest update.
justininhifi said:
same problem with moboot disappearing after the update. ive reinstalled moboot three times and still cant get the menu to display the cyanogen or clockwork options.
Is there something I am doing wrong?
edit: ended up adding moboot, the original CWM, and the latest XRON build and running ACME Installer and all is well. Just cant install preware to the touchpad since i used webdoctor to install the latest update.
Click to expand...
Click to collapse
Just reroot webOS and re-install preware.
My streak 7 just started acting up.
1.- I forgot to turn it off and the battery depleted and stayed without charge for about 4 days.
2.- At first it would not boot (after charging overnight) it would get stock on the pink animation.
3.- Contacted tech support and they had me do a factory reset (4 times).
- First time it got stuck on "Formatting DATA" (waited for it overnight)
- All other 3 worked fine.
The problem is that after it boots and I go trough the initial setup (google account, WiFi password - no sim card) it appears to be working properly, except when I turn it off and re-start it ask me for the configuration all over again. Just like if I had done an other system restore. If I try to install something from the market some times the tablet would crash (the screen would blink and then go black) and I have to use the reset pin.
I don't know what to do I'm completely new at this but I'm willing to learn. Any help giving me a direction to go will be greatly appreciated.
Thanks in advance.
You could try to NVflash back to Froyo with this file: http://d-h.st/iXc. What version were you on? This video is the first in a three part series by "giveen" which will show you how to load drivers to NVflash: http://www.youtube.com/watch?v=ydM7qkoCs00. This link will get you all the drivers: http://d-h.st/iqA. The links in the videos no longer work.
This page will get you the latest or last T-Mobile file link: http://forum.xda-developers.com/wiki/Dell_Streak_7#Official.
Thanks !
Thank you for the help. I will be trying this today.
Need more help
I tried doing the restore to factory 2.2 with the instructions above, the flash appeared to finish. But when I restarted the tablet I still have the same problem. Every time I turn it on it acts like it has just been restored to factory defaults.
I tried doing the HoneyStreak flash from here http://forum.xda-developers.com/showthread.php?t=1088225, and I got an error.
Formatting partition 2BCT please wait.. FAILED!
Could this be part of my problem? any other suggestions of what to do.
Thanks for your help.
luis_Hac said:
I tried doing the restore to factory 2.2 with the instructions above, the flash appeared to finish. But when I restarted the tablet I still have the same problem. Every time I turn it on it acts like it has just been restored to factory defaults.
I tried doing the HoneyStreak flash from here http://forum.xda-developers.com/showthread.php?t=1088225, and I got an error.
Formatting partition 2BCT please wait.. FAILED!
Could this be part of my problem? any other suggestions of what to do.
Thanks for your help.
Click to expand...
Click to collapse
You are in read-only status more than likely. Sucks.
OH NOOOOO
Does this mean I'm out of luck and pretty much have a worthless device now?
I've looked up read only mode and no one seams to have a way to get out of it (except for re-soldering components with some expensive machine)
I've also tried the "hold reset pin + capacitive buttons + power button for 2 minutes" with no luck.
And found one that calmed to have fixed it by flashing CWM to it but they did it with a version of CWM for 5.x and up and I'm still in stock 2.2
Please some one tell me there is a solution.
Yup.