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.
Related
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.
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.
I tried a flash and think i messed my tab...now its just a black screen with a faint light in the background like its on but its no images.......my battery icon pops up then distorts away and thats it ....can get into download mode but not recovery.....tried holding all 3 buttons got this lil android dude in the corner with a sign sayin something about power reset but cant select nothing......help me please......
Put it in d/l mode and flash one of the stock roms with Heimdall.
D
i tried a stock flash with heimdall it flashed successfully but i still get the SAMSUNG logo that flashes and go away,buttons light up at the bottom,can go in download mode but not reboot mode,phone stay on with a faint light ,so i assume that its on somehow.....help
Did you follow this exactly?
http://forum.xda-developers.com/showthread.php?t=967175
One thing I missed here before was to wipe data and cache. Otherwise I go into boot loop.
how to get recovery mode
i cant wipe nothing because i cant get to recovery,just download mode
done it step by step
i followed evrything it flashed successfully but when it rebooted i turned off.and tried recovery but nothing......
chubbyflood said:
i followed evrything it flashed successfully but when it rebooted i turned off.and tried recovery but nothing......
Click to expand...
Click to collapse
Use UnBrickable Mod
http://forum.xda-developers.com/showthread.php?t=1341753
Although you get a black screen on boot, it might still be working....
Chubbyflood,
If you are in the same situation as I am then the tab is still working, you are just getting black screen on boot up. It played tricks on me for ages when I was first rooting by tablet; but it turned out it is just the boot up screen that isn't showing.
This is my situation:
-Press and hold Power button to turn on.
-I see the Galaxy Tab / Samsung initial boot image for about 1 second, and also hear the "boot chime"
-Then the screen goes completely blank (but you can tell it is still on with a little light showing.
-The four "hard button" lights will light up briefly a couple times
-Wait approximately 30 seconds to a minute (to be safe and give the tablet time to boot up - it is actually booting up)
-Tab the Power button once, to turn the tablet off (now the screen is clearly off)
-Tab the Power button again, and the tablet will be up and running as normal.
I am guessing the boot animation / images are failing in some way, but the tablet is booting up as normal.
I've just learned to live with it, because I haven't had a chance to figure out what's going on, but it honestly took me a good hour or so, and a few (unnecessary) flashes, before I realized the thing was up and running fine, it just need to have the button pressed on and off.
One final thing to mention; don't have the tablet plugged into anything. I seem to remember leaving it plugged into the PC didn't help (I think).
Hope that makes sense.
Cheers
Ed.
Has your situation been resolved?
I am in the same boat. What I have done to temporarily fix this was to Flash a ROM that uses Hemdall and it will boot as flukebu stated but only with the Galaxy Cubed ROM.
I cannot get the factory files to boot as you have stated.
I have continually tried to return to stock using the files provided on this forum and all "unbrick" posts.
While flashing the stock images everything completes and works well. The device reboots and the Samsung Splash screen appears. Once it appears it disappears and scrambles the screen. I believe it then goes into a bootloop which easily enough I could access factory recovery to correct but when I do attempt to access factory recovery the screen is as posted above (black but illuminated).
Once I flashed Galaxy Cubed ROM and it booted I hit the power button and the locksreen appeared. I can tell you I was excited but there are some issues with that ROM I have not tried to correct yet because my main goal is to return to stock.
Even with this ROM working correctly I have attempted to access CWM once installed to complete a Data Wipe and that does not show up either.
I would really like to find a solution to this I want to return to stock and not have this custom ROM running.
Juiced_RL said:
Has your situation been resolved?
I am in the same boat. What I have done to temporarily fix this was to Flash a ROM that uses Hemdall and it will boot as flukebu stated but only with the Galaxy Cubed ROM.
I cannot get the factory files to boot as you have stated.
I have continually tried to return to stock using the files provided on this forum and all "unbrick" posts.
While flashing the stock images everything completes and works well. The device reboots and the Samsung Splash screen appears. Once it appears it disappears and scrambles the screen. I believe it then goes into a bootloop which easily enough I could access factory recovery to correct but when I do attempt to access factory recovery the screen is as posted above (black but illuminated).
Once I flashed Galaxy Cubed ROM and it booted I hit the power button and the locksreen appeared. I can tell you I was excited but there are some issues with that ROM I have not tried to correct yet because my main goal is to return to stock.
Even with this ROM working correctly I have attempted to access CWM once installed to complete a Data Wipe and that does not show up either.
I would really like to find a solution to this I want to return to stock and not have this custom ROM running.
Click to expand...
Click to collapse
Have you found a resolution to this? Mine tab is doing the exact same thing as yours after the cubed rom.
Droid 4 running Stock Jb 4.1.2, Safestrap 3.11, Liquid smooth 2.9, CM (last stable)
Everything working fine for a number of months, installed Liquid smooth via -> delete romslot 3, create romslot 3, install Liquid 2.8.
It ran for a number of days no problems. Restarted fine, all features worked great, even the annoying random restart from 2.4 went away.
6 - 10 days in, im surfin' the news sites at work, put it down, screen goes black, i pick it up. Hit the power button cause i realize its off and it just boot loops... so bad i had to vol-/+ pwr, go to flash mode and THEN turn it off b/c it just kept trying to restart, hang on logo.
I got home and decided to AP flash the latest:
9.8.2O-72_VZW-18-2
Blur_Version.98.72.182.XT894.Verizon.en.US for the maserati.
Boot looped a few times, i was able to get it to go into recovery mode, after that it loaded up the stock JB system. First boot it crashed and restarted, second boot it loaded but only the keyboard worked, not the touch screen. Went to the in OS option of factory reset mode + delete storage.
Rebooted, worked. Checked it a few boots, everything is fine. I use Druid 4 Utility Xt894 JB version and apply the root. Works great. Install safestrap, Create new partition, install liquid smooth 2.9. Works for an afternoon... at work today the touch screen stops responding, i restart it a few times. I try to enter recovery mode. Now im in boot loop again...
I've tried re flashing it again, a few times. I tried even going down to the previous release of JB for the phone. STILL 4.1.2!!!! But nothing.... it just boot loops... what did i do wrong? It was running great. No tweaks or anything done to it prior to it having its melt down.
Help please.. ive provided as much information as possible and though i only joined XDA now to post for help, i have read it for a long time as my main source for my phone and have donated to both CM and Liquidsmooth teams previously..
help!!!
I can't see where you are doing anything wrong. You have obviously done your research and have a good idea of what you are doing. I see, after you fastbooted, you went back to Liquid. I think I would try running CM10.1 or even stock for a few days and see if you have the issue there as well. If you do than it sounds to me like it might be a hardware issue. If not, maybe try re-downloading Liquid. Perhaps your zip got corrupted somehow.
I would love too. In fact i would be willing to run it on the stock crappy 4.1.2 if i could get it out of boot loop this time...
It just keeps boot looping on the logo. AP Fashboot flash and BP flash work but recovery and normal boot/reboot mode just goes into M logo boot loop.
I've re downloaded the 4.1.2 jb SBFs from 2 different sources to ensure its not a corrupt file, tried 18_1 and 18_2 software versions...
Is there a way to use the abd shell to get into the filesystem and check whats going on? Is the SBF the last call? or is there another route to see whats going on or just flash EVERYTHING? Like completely back to stock?
I can find my way around a PC file system but im not familiar with linux. Please help me understand, Is it like having CMOS and BIOS settings or equivalent to damaged CMOS firmware? What am i not replacing/reverting by SBF and HOW can i replace/revert BEYOND the basic sbf...
If ya point me in a direction or to someone who can help me out i can do all the foot work just point me in the right direction?
Is this applicable? I found a site talking about using CWM in a ADB shell file push to possibly get access to more features?
The article also goes into reading the busybox / ADB command screen? (sorry for not proper jargin) and see what its doing during the boot loop before it restarts?
Id add the link but i need more posts....
Update: Flashed 18_2 again with a "factory cable" i made, let it boot loop a series of times before it started up into the stock system again.
At first, again the touch screen wouldn't work, random lockups and restarts, etc. Since i just got it into the main system again and i had to leave for the weekend for a trip(no wifi or network), i couldn't mess with it all weekend but i left it on the whole time and kept checking its functionality... gradually its come back to full function. Touch screen works and is accurate, no more lockups, no more restarting, even stopped boot looping when i restart and enter recovery..
Im not sure and i couldn't find any forum converstations or write ups to support to idea but i think after a major crash and you flash new or reflash your SBF, it seems the phone needs time to recalibrate and index? Not sure, but just an FYI. Gonna try loading SS and liquid again.
I was on Cyanogen 10.1.3 stable (at&t), S-off, rooted with Team Win recovery.
I flashed this rom: http://forum.xda-developers.com/showthread.php?t=2582066
which is the unsense with Beats (my reason for flashing)
It flashed fine, but when it loads the OS, it displays a message saying something along the lines of htc.dialer not responding, so i select ok to force close. the phone works fine for 20 seconds, then reboots. cannot open the phone number pad, though, it remains blank. if i select wait, same thing, 20 seconds and reboots.
the power button seems to not work anymore, i press it and nothing happens so i am unable to enter recovery/bootloader, it is just endlessly rebooting.
one thing i didn't do (i should have but i was lazy) was to make sure my firmware and radio was up to date, mainly because i couldn't figure out which version to use. i am on bell canada.
am i completely screwed, or is there some way to save this?
i can follow step by step instructions, and have rooted/flashed several phones throughout the years with no issue, and have flashed this HTC one about 15-20 times with no issue. however, i am not a programmer by any means.
i tried to follow this guide (i don't know if this is for my problem or now) but i couldn't find the adb usb device thing
http://forum.xda-developers.com/showthread.php?t=2503646
if anyone has any suggestion, please let me know!
thank you
EDIT: Nevermind!!! For some reason, the power button randomly started to work again, and after trying 20 times, I was finally able to load recovery and revert back to CM. Whew.