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?
Related
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've had my NC rooted for 3 weeks. No probs. I decided to update to 1.0.1 to see if wifi was better and so I entered the adb command to force system update and all seemed to be well. After that it went into a boot loop.
I forced another "update" by powering down 8x during bootup. It reinstalled and then same problem. I then tried the directions at nookdevs to fix boot loops. I couldn't ssh into the NC, but to my surprise I could use adb, but I can't do the listed commands because I get "permission denied".
I did an adb logcat and I get nonstop info going by, mostly looking for stuff that shouldn't be there anymore, i.e. apps I loaded when it was rooted. Dalvik cache??
So, long story short, I've tried a system wipe 4x now and I'm stuck in an endless boot loop BUT I do have adb access. What now?
Power, +, N button doesn't work either?
norkoastal said:
Power, +, N button doesn't work either?
Click to expand...
Click to collapse
Haha. Good call. That did work. Bigtime brain fart. Trying all the hard stuff and not the easiest. What's the diff between the two methods?
GTOMEX09 said:
Haha. Good call. That did work. Bigtime brain fart. Trying all the hard stuff and not the easiest. What's the diff between the two methods?
Click to expand...
Click to collapse
Head over to Nook Devs for the breakdown of the two.. Both methods are requied for using the newest AutoNooter... Glad to hear the device is still in working order.
Stuck in Boot Loop
Noob here with a problem. I’ve had my NC rooted for 5 days and the rooting went well. I had all my favorite android apps up and running. However I was experiencing random reboots (2-3 times per day). So, I decided to unroot and let the 1.0.1 update install and then I was going to use Auto-Nooter 2.12.18 to get everything back.
I did the 8X reboot thing and after reloaded, the NC went into a boot loop. The first thing I tried to do was the n, volume+ and power button. It simply went back to the boot loop.
I immediately put the auto-nooter sdcard in the NC, plugged in the usb to the pc. As opposed to the other times I did this, I got no visual indication that the PC recognized or activated the NC. I waited the full 5 minutes and removed it. The boot animation had changed, but the NC stayed in the boot loop.
I then searched and found this on nookdev.com (nookdevs.com/NookColor_Fix_Boot_Loops ). Following the instructions there, I installed putty.exe in the same folder as adb.exe. Putty would start and the session window would open, but I could not type or paste anything into the ssh screen. I assumed I had a bad download so I redid that and the install – no luck. I then searched and found another site from which I could download putty.exe, same results.
Before I ejected the NC I opened the command line window and I did adb devices and it came back with nothing. So now my NC is not recognized by the PC (and was before all this).
Can anyone point me in the right direction? Any help with the putty ssh screen issue? Any help will be appreciated.
Geezer Squid said:
I then searched and found this on nookdev.com (nookdevs.com/NookColor_Fix_Boot_Loops ). Following the instructions there, I installed putty.exe in the same folder as adb.exe. Putty would start and the session window would open, but I could not type or paste anything into the ssh screen. I assumed I had a bad download so I redid that and the install – no luck. I then searched and found another site from which I could download putty.exe, same results.
.
Click to expand...
Click to collapse
Out of desperation I downloaded putty.exe again and it worked this time. Using the script on the nookdev.com website, the NC booted. I then did the data wipe and the 8X reset. I'm now back to stock (mostly) and I'll see if it updates tonight. If not, I'll force it tomorrow and don the new auto-nooter.
I'm learning!!
Glad you fixed yours too. This device is nearly impossible to brick unless you deliberately try to. Definitely easy to undo hard work, but hard to brick.
I have the same problem. Minutes after rooting with autonooter, my Nook restarted and I didn't even set up ADB access. I tried reseting several times with no luck Please help!!
Mine is currently stuck in a boot loop as well. I did not update to the newer firmware it auto-updated and jacked everything up. Pretty upset right now.
I know I can reset the device but I need to get the data from it first. I have the entire storage full of data that I need. It will not boot at all and if this gets erased i'll more than likely end up returning the device and purchasing something that I won't have this problem with every update.
Unfortunately, there aren't many devices that will automatically backup all your important data to external media without you having to take some action on your own to set that up.
hey guys i'm noob here yesterday i rooted my nook color and everything was going fine until i turned it off when i tried to turn this again i couldn't so i took the sdcard off and tried again it powered but now i'm stuck in the grey 'N' screen, any idea on how can i fix this?
Mbside said:
hey guys i'm noob here yesterday i rooted my nook color and everything was going fine until i turned it off when i tried to turn this again i couldn't so i took the sdcard off and tried again it powered but now i'm stuck in the grey 'N' screen, any idea on how can i fix this?
Click to expand...
Click to collapse
Well, I'm not an expert, but I have been through this kind of thing. I would think you have two possibilities. One would be to put the nooter sdcard back in and hook it to the computer again. If it isn't very corrupted, it may automatically reload from the nooter sdcard.
If that won't work, then I think it's time to do the 3 finger data wipe and then the 8X reboot thing. You can then redo the nooter sdcard thing.
Good luck.
Mbside said:
hey guys i'm noob here yesterday i rooted my nook color and everything was going fine until i turned it off when i tried to turn this again i couldn't so i took the sdcard off and tried again it powered but now i'm stuck in the grey 'N' screen, any idea on how can i fix this?
Click to expand...
Click to collapse
EXACT Same thing happened to me and a friend when using autonooter and 1.0.1. I think there is a problem with autonooter or 1.0.1 messing up the booting process. I wonder whats wrong So I was able to do the 8X reboot thing and get back to stock 1.0.0 and from here I'll try to attempt to use autonooter for 1.0.1. But I'm staying with 1.0.0 until Froyo next month.
thanks! the 8x thing worked good, I did the whole auto noot process again and it works at all except by this market issue
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'm sorry if this has been answered before, I searched but wasn't able to find anything.
It started when my phone suddenly didn't recognize the sd card. I took the card out and put it back in a couple of times, and reebooted the phone a couple of times. After that didn't work, I figured I would factory reset the phone, and as I did, it started to reboot, but was never able to boot back up.
When I now try to boot the phone, I get to the initial Samsung-S4 Active GT-I9295 -logo, and it says BOOTING RECOVERY in the top left corner, but after ~2 seconds it shuts off.
Interesting: It only boots a couple of seconds after I let go of the power button.
The phone was rooted using this guide: (not able to post links. The guide is on android geeks, and can be found by searching for Root Galaxy S4 Active (International I9295 and AT&T I337 models))
And Xposed was installed, but no modules were activated.
Firmware was 4.2.2 MF/MU 3 - something, I think. Sorry I cannot remember. I got it OTA some two weeks ago.
Any suggestions?
Thank you!
EDIT: When playing around with it, I managed to solve it. When booting, as soon as the logo appeared, I pressed and held the volume up + home button, which caused it to not shut down (?). It then preceeded to boot for a long time while, I guess, the phone was factory reesetting itself. Now it boots just fine, factory reset =D . (SD card still not detected )
I updated to the new version of the software a few weeks ago and have had trouble with my SD card ever since. Today I was transferring an app to my SD card, when the phone reset on it's own. I tried to turn it off to do a proper boot, and it went to the BLU screen but never changed from there, it's stuck on that screen. I don't know how to remove the battery on this thing, it's screwed in or something. I tried holding the power button, tried holding the volume up button, but it's not responding at all.
Please help.
EDIT: Okay, got it to reboot, but I REALLY need to downgrade my operating system. Does anyone know how I can roll back the update from last month?
Terrabull said:
I updated to the new version of the software a few weeks ago and have had trouble with my SD card ever since. Today I was transferring an app to my SD card, when the phone reset on it's own. I tried to turn it off to do a proper boot, and it went to the BLU screen but never changed from there, it's stuck on that screen. I don't know how to remove the battery on this thing, it's screwed in or something. I tried holding the power button, tried holding the volume up button, but it's not responding at all.
Please help.
EDIT: Okay, got it to reboot, but I REALLY need to downgrade my operating system. Does anyone know how I can roll back the update from last month?
Click to expand...
Click to collapse
If it was an official update and not a modified one,then no we don't currently have any roll-back.