Bought a NC Friday, rooted it, and noticed an issue when I tried to turn it on Sunday:
Whenever I turn on my nc after leaving it off for a long time (overnight) it doesn't boot past "touch the future of reading." Booting into cwm from sd and restoring a backup fixes the problem, but not permanently (because it just happened again).
Is this normal? Should I exchange the NC? What would you do?
Sent from my SPH-D700 using XDA App
When i get this message i boot like you in CWM. I fix permissions + clear cache.
Generally it is ok.
For the root cause, it seems to be from the way i shutdown the nook. Stay alert
Interesting, thanks. How do you turn your's off?
Sent from my SPH-D700 using XDA App
Now, only with 2s press on "Power".
I disabled power widget.
Cross fingers now
Related
And now I'm boot looping won't go past n color startup animation wth
Sent from my Cyanogen Mod EVO using Tapatalk
I had that problem on my NC when it was rooted. Luckily I had another problem that let me get out by the 8 times reset manual method. Mine would occasionally update itself back to version 1.0.0. When it did that I managed to reset it & now a new NC is on its way to replace this one.
This probably won't help solve the issue but at least it lets you know you're not alone.
Mine boot looped and I did the full 8X reboot thing and then the 3 button data reset. All of that puts you back to "out-of-the-box" stock. You can then redo the autonooter rooting procedure.
Can't get out
I am stuck in a boot loop and cant get out.
First it was stuck on the droid boot animation from the auto config. After I put the autonooter card back in it started looping the rooted boot animation.
Did the 3 button thing and that forced an update but went back to bootlooping the rooted animation.
Then did the 8X reboots manually and that also forced the down arrow update, but then it still bootloops.
I tried getting in from PuTTy (as admin) but it never connects. Do I just use port 22? (to 192.168.2.2 with Data and username as root?)
adb doesn't work... going to bed now and will try again tomorrow after work.
What i had to do to resolve my issue was that was to do the 8x reset to trigger the factory reset of the OS and then do the 3 button reset of the user data. In my case it was a self tweaked issue with an app permisson. If I remember right the key combo is Power+VolUp+"n" key. Try this and let us know.
Sent from my NookColor using XDA App
Bigger Issues.... First Brick?
Nate731 said:
What i had to do to resolve my issue was that was to do the 8x reset to trigger the factory reset of the OS and then do the 3 button reset of the user data. In my case it was a self tweaked issue with an app permisson. If I remember right the key combo is Power+VolUp+"n" key. Try this and let us know.
Sent from my NookColor using XDA App
Click to expand...
Click to collapse
So ... I left my Nook in what I thought was an "OFF" state last night, only to bring it to work and find it says "Battery too low to Power on" "Please wait 15 minutes and try again"
I think... no worries... plug it in and let 'er sit for an hour.... an hour passes and I'm still getting the same screen.
Is this better or worse? let me see...
1) if it stays like this, I can return/exchange it at B&N and they won't be able to verify that it was rooted due to non-bootiness
2) If it eventually boots, I will have to try to get it out of bootloop.
3) If it comes to life and I can't get it out of bootloop, I will drain the battery again and go back to #1.
Any thoughts besides this current train?
sort of working?
OK....
so after charging on USB port (all I have at work today as I forgot the base to the charger), it will bootloop again... yay!
problem is... the bootloops take too much juice and won't allow me to fail 8 reboots. I can't even charge it up enough since I'm on USB charging and it keeps trying to turn itself on.
2 Options i see:
1) Go home and charge it on the wall and see if that helps
2) Discharge it to death and return within my 30 days (X-mas gift)
Doubt this will work, but have you tried putting in an autonooter sdcard and then plug it into the usb? If it tries to boot maybe it will boot from that sdcard?
Boot from the Froyo SD card, then fix /rom/devconf/BootCnt from ADB.
Cal you never mentioned if you cleared the user data... Did you?
Nate731 said:
Cal you never mentioned if you cleared the user data... Did you?
Click to expand...
Click to collapse
If you mean the 3 button reset? Yes.
If not... I did not because I'm not aware of it. (couldn't through the UI of course)
cal3thousand said:
If you mean the 3 button reset? Yes.
If not... I did not because I'm not aware of it. (couldn't through the UI of course)
Click to expand...
Click to collapse
Try Geezer's tip but do this:
Do three button reset WITH the autonooter card in there.
Got it working
Finally got it working after creating a Nookie Froyo card and booting off of that.
Then I reinstalled ADB on my work computer and reset the BootCnt file to 8...
that successfully restored /system and then the 3 finger trick actually gave an option to wipe.
Now to start over.
New Question: How likely is this hardware related and should I be looking to replace it before my 30 days is up>?
I ran into the same problem, trying the same solution - any luck the second time?
JasonBunting said:
I ran into the same problem, trying the same solution - any luck the second time?
Click to expand...
Click to collapse
My Nook has been great since the fix. But I also needed to use a program to turn off Wifi when I turn the display off.
I did it all from my Nookie...
confused?!
I was wondering how you fixed this..i have read everywhere, but nothing...im stuck in the nook co screen. This happened right after i plugged my nook to charge after my battery was drained...thnks
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
So I have been wanting to flash a new os on my tab for awhile..i figured I'd start prepping for it today while waiting for an oil change. Backed up all my apps and whatnot with titanium backup. Then downloaded the verizon tab boot strap thinking it was like my droid x bootstrap. Stupid me.
I rebooted into recovery and it automatically did a backup for me, ok...odd liked like it wiped the phone first. Then when it finishes and leaves me st the reboot now prompt I do that.
My tab freezes at the samsung logo. Just sits there. Figured ok. This must be like my droid x or the wife's incredible. Hold down some hard button and power button and just clear my cache and data. Tried vol up and power, got nothing. Did vol down and power and now it its just sitting at a screen saying "Downloading...Do not turn off target!!!!"
What stupidity did I now? :-( been on that screen for 30 min now. Any help would be appreciated. Yes I know I should have researched more before running that app. I am an idiot. I can admit that.
Can I just hook this up to my pc and flash a new os now? Our reboot and find a different way to clear my cache?
Sent from my DROIDX using XDA Premium App
Ok found a thread through google that just said reboot. Did that. Stock back st the samsung screen. :-(
Sent from my DROIDX using XDA Premium App
Search the forums for how to restore verizon tab back to stock.
I have/had my nook color rooter (1.4.2) and then the lovely update came by...now, I find I can not power off my nook. I hold the power button for minutes and nothing. I normally would run quick boot, but since root was taken away, I can't even get that to work.
I need to fix this so my wife doesn't yell at me too hard.
Any thoughts/help? Please?
Plug it up to the wall charger....not to the computer.....and try it again.
dparrothead1 said:
Plug it up to the wall charger....not to the computer.....and try it again.
Click to expand...
Click to collapse
I just tried that again. It didn't work, I appreciate the suggestion, but I'm not sure what being plugged into the wall would have to do with shutting of the nook, but I'm desperate, I'll try anything. I just need it to reboot, I have the crm card installed in the nook. The button used to work. I'm just hoping that when the battery runs down, I'll be able to restart the nook.
Ok, so got the battery run down, managed to get it charged enough to reboot into recovery. Got root back so that much is done. But the power button still won't work.
And I made the mistake of powering it down (quick boot app)
I was able to get it start booting, (got the skull and crossbones Loading screen) but now it is hung there.
Any thoughts? You guys here are usually really good with coming up with something off the wall that works
ufkal said:
Ok, so got the battery run down, managed to get it charged enough to reboot into recovery. Got root back so that much is done. But the power button still won't work.
And I made the mistake of powering it down (quick boot app)
I was able to get it start booting, (got the skull and crossbones Loading screen) but now it is hung there.
Any thoughts? You guys here are usually really good with coming up with something off the wall that works
Click to expand...
Click to collapse
And buying one used on eBay before the notices just won't cut it?
Seriously, do you have a bootable recovery SD card?
Sent from my NookColor using xda app-developers app
DublinLarry said:
And buying one used on eBay before the notices just won't cut it?
Seriously, do you have a bootable recovery SD card?
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
Before the WIFE notices, of course..... when I totally hosed my nook from booting I was able to restore from last backup after booting into recovery off SD.
Sent from my NookColor using xda app-developers app
DublinLarry said:
And buying one used on eBay before the notices just won't cut it?
Seriously, do you have a bootable recovery SD card?
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
Yea I do have a bootable recovery SD Card. I re-ran it and still no love with the power button. Can I just use the old old 1.01 image (if I could find it) and take it back to that point?
I can't even to the 8 interrupted resets, because obviously the power button won't work
DublinLarry said:
Before the WIFE notices, of course..... when I totally hosed my nook from booting I was able to restore from last backup after booting into recovery off SD.
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
and unfortunately I never got to make a backup yet.
ufkal said:
and unfortunately I never got to make a backup yet.
Click to expand...
Click to collapse
Wow... I've hosed my nook many times but never had the power button fail. Is it physically just not working?
Sent from my NookColor using xda app-developers app
I think the button is still good. About a month ago I was able to do the interrupted boot process. When I rooted her NC, was when I noticed the button didn't work. Don't know if something with the flash or if I beat the button to death.
Sent from my Galaxy Nexus using Tapatalk 2
ufkal said:
I think the button is still good. About a month ago I was able to do the interrupted boot process. When I rooted her NC, was when I noticed the button didn't work. Don't know if something with the flash or if I beat the button to death.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
From my POV the Physical Button is dead… If you have tried turning off the NC while it was runing on CWM Bootable uSD using the Power Button and it did not turn off then the Button is dead.
Well, at least I have it rooted, and quick boot installed, I also have a CWM sd card in there, so if it happens to bork again, I can just let the battery die and then when it recharges it will power up....
I guess the button is dead, and I've not seen much in the way of instructions on how to repair the button. And out of warranty its probably cheaper to buy a new one than take it in to get repaired, cuz I can't actually get it back to factory state without having the power button to do the factory resets...
ufkal said:
Well, at least I have it rooted, and quick boot installed, I also have a CWM sd card in there, so if it happens to bork again, I can just let the battery die and then when it recharges it will power up....
I guess the button is dead, and I've not seen much in the way of instructions on how to repair the button. And out of warranty its probably cheaper to buy a new one than take it in to get repaired, cuz I can't actually get it back to factory state without having the power button to do the factory resets...
Click to expand...
Click to collapse
There is an app on play store called NookColor Power Button. It is a widget you can configure to do all of the power functions, sleep, power off, reboot, etc. I suggest you get the donate version. I think it is only 99¢. You can configure it for what you need.
computerist said:
There is an app on play store called Nook Power button. It is a widget you can configure to do all of the power functions, sleep, power off, reboot, etc. I suggest you get the donate version. I think it is only 99¢. You can configure it for what you need.
Click to expand...
Click to collapse
Yeah, I saw that one, forgot about it. Thanks. I need to try the free just to make sure it will do what I need it to.
Thanks!
Got nook hd+ yesterday. Immediately got CM10 on it. Everything was working great for a few hours. All of a sudden it started rebooting it self randomly, but I kept using it. Then it happened more frequently. Then it rebooted to the Cm boot screen and never left there. Kept looping. So I turned it off and rebooted. No success. Tried again. Nothing. Then I got mad and let it loop for like an hour. Came back and nothing happened so I turned it off.
Next morning I wake up and it boots fine but this time in nrmal nook mode like when I turned it on the first time. It even had to update the nook software again. I am just using the standard nook mode now and have some questions.
1. How did that happen?
2. Is all my info still on here somewhere? Like the login to gmail, evernote, instagram etc?
3. If yes, how do I get that stuff off?
Thanks
Sent from my BNTV600 using xda app-developers app
The HD+ has a self repair utility built in that will reset itself to stock if it fails to boot 8 times in a row. That is what happened to you. It put stock back along with wiping all your data. So your personal stuff is gone.
I don't know why your CM10.1 quit in the first place, but now that you are back to stock, you can start over.
Sent from my Nook HD+ running CM10.1 on emmc.
Ah.
Thanks for the info. Didn't realize it could fix itself.
Sent from my BNTV600 using xda app-developers app