My rooted Nook Color reboots itself randomly sometimes, and also gets stuck in a reboot loop as well. I've been searching around and have seen several other cases of this but with no resolution.
After I first got my Nook Color, I started off by sideloading the latest B&N 1.1 update. Then I went ahead and used Auto-Nooter 3.0.0 (1.1 only). That's it really... aside from loading a few other apps from the Market like LauncherPro, BeautifulWidgets, Astro, JustPictures, & Screen ON Widget.
The first time around my Nook Color worked for about 3 weeks with no problems before the boot loop happened. I figured it was a fluke, so I restored to stock and then started back from scratch with updating and then Auto-Nooting again. This time around, it only took about 2-3 days to get back to this boot loop issue.
Anyone else come across this? You think I just have a bad Nook Color, maybe a hardware issue? Like I said, I did search around on Google and did come across a few threads where people were reporting the same thing. The only answer anyone would get was to restore and start from scratch. I just wish there was some type of debugging I can do to see what's happening....
I have the same issue with no resolution. Did you find anything? I think i'm moving to an iPad if I cant sort this today.
Related
When I try to boot my nook, I get past the "Touch the Future of Reading" screen but get caught up on the "n" loading screen.
I've tried to interrupt the boot process physically 8 times to no avail.
I've tried to SSH in the 8 failed resets script, nothing.
I can't boot the nook far enough to be able to shell.
I tried to do a factory reset but it tells me "install failed", and has an image of a nook with a red circle and while exclamation point.
I installed Nookie-Froyo from flash and tried to use that but soon realized I was over my head.
So finally I called BnN to see if they could do something and they offered to replace it. If I send them this wonky device, will it raise some red flags in their system?
I would say try some other methods before returning it if possible. I have read others on the forum in the same situation as you and they have gotten it working again. It will take some time for someone with more knowledge to respond, but I think it is worth it.
If you return it it seems like you might have a high chance of getting one that has hardware/software issues from what many have posted. I would try to stick with what I had even if it took a week of getting help from the forums.
Have you tried booting the AutoNooter 2010-12-25 ? I have heard some boot the sd card and then they can ssh to 192.168.2.2 and do some recovery work on the nook, like I said I am not experienced in this but I have read other's posts on success stories
I've tried the ssh method and it would never make it past the n screen. I've also searched the forums and haven't seen anything about an "Install Failed" screen. If someone has seen something about that and could point me to it, I'll try anything.
If you see an N on the screen it means it is not booting from the we card. Maybe the we card wasn't written correctly? Was this rooted previously?
Sent from my NookColor
It was rooted and then stopped working after I left it in a very cold car all night long. I don't know if that's what caused it, but until I figure it out, correlation will equal causation.
As for the card, I reformatted and re-imaged it 3 times in the process of trying to re-root it; once with auto-nooter for 1.0.0 and twice with 1.0.1.
This is crazy, I have the same issue right now....it's stuck in the boot screen. Mine rooted perfect today, apps installed from market with no problem, I noticed the battery was low but wanted to reboot it after I noticed Youtube stopped working, I shut it back down and restarted it before I put it on a charger.....it hasnt rebooted since.
I did get it to boot into clockwork a few times, I did a factory reset from there but it still didnt help. Anyone have an idea? Did I permently brick this thing?
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
Has anyone ever ran into a situation where the UI locks up after a boot? I keep searching through threads and can't find anything. I'm not sure if it's something I have installed or if there is actually something wrong with the device. I had a nook previously and never encountered this problem but on the new one I just got (ebay refurb) the problem just keeps coming back.
Basically, it boots just fine and starts to show the Launcher but then the screen goes black and leaves the soft buttons at the bottom. The only way to recover is to shut it down and start it back up.
The funny thing is it doesn't do it all the time... sometimes it boots just fine and never locks up while in the OS... it's only on boot it does this.
I've tried multiple different versions of cm7 and am getting the same thing on all versions. I've tried different kernels and stock speeds and it still happens.
Any help or advice would be appreciated!
Hmmm... well after hours of troubleshooting I think I pinpointed it to beautiful widgets
I did a search and couldn't find any other topics covering the same issues I'm having, both here and a general Google search. I also called my mother, and she did indeed say I was special.
Anyway, bought a Nook HD+ two weeks ago and left everything stock for a few days before using Bokbokan's Hybrid SD/EMMC. Everything worked great and enjoyed it for a full week until my Nook started freezing and getting an odd ghosting and slow refresh on the screen.
Figured it was a rom issue so I removed the SD but even when powering it back on the screen had the same effect. And it continued into the stock rom. I de-registered and returned to stock and still had the same issue. Washed out screen, slow refresh, slight flickering an odd randomish burning which held even when the device was powered off and left off for hours. Used the HDMI adapter to see what happened and the output to the TV was fine, making me think I just had a defective screen.
So I returned it for a new one. Followed the same path. Stock a few days, then hybrid install (with the newer Bokbokan rom). Ran great for another few days until I had the screen freeze on me. Not ghosting like I had before, just lines like a disconnected ribbon cable. I reset a few times though and everything was fine. The next day it did it again but took removing the SD card and hard resetting into stock to get it to fix the screen. Then a few hours later I could only get it to boot into the stock rom with a normal screen(CM10 would always have lines and be unusable before it even started booting) , but would go out after 30 seconds. Booted into CWM from the SD card and the screen was fine so I did a factory wipe and left out the SD and booted into stock. De-registered before the screen went out and started over. Started re-registering it and the screen would start going out after the 30 seconds but then snap back to normal after another ten or on a new screen. Once it finished setting up my BN account I reset and... now it seems to be running normal... Left it sit like this for a few hours (checking it every few minutes) and I haven't had a single issue.
This seems to me to be something I'm messing up. I can't see having two defects like that in a row, when I know other people who bought the same week/store from me and haven't had any issues (also running the same Bokbokan rom). And the fact that it seems to fix itself the longer it sits in stock. I haven't dropped it. There has to be something I'm not thinking of that's causing the issues. But I'm completely out of ideas.
Is this maybe some kind of new anti-rooting thing by B&N? Does someone have a voodoo doll of my Nook? My SD card have some type of bacterial infection? Maybe a full blood moon overhead? An allergic reaction to my screen protectors?
Any ideas?
Do you have some big magnetic source or other device in your house that could be effecting your HD+? Just grasping for straws. Never heard of this before.
You might try verygreen's NEW SD scheme and see if you get the same thing.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Do you have some big magnetic source or other device in your house that could be effecting your HD+? Just grasping for straws. Never heard of this before.
You might try verygreen's NEW SD scheme and see if you get the same thing.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
My case does have a magnet in it, but this started before I got this new case.
But the way the screen looks is the way a screen looks like when it needs degaussing... But wouldn't explain why it only clears up after running a fresh stock rom for a bit.
Which has me thinking now it is something wrong with my rom. Even though both Nooks used different roms. I shall try using verygreens and see what kind of results I get.
I hate problems like this. =p
I'll report back in a bit!
First of all it's working again so I'm not really looking for any help to get it running but still I thought this is worth mentioning
I wanted to import a .mobi book to Nexus 7. This book was sent to me by a friend and I wasn't completely sure what it was. Not even sure if a .mobi file could cause this. But here it goes:
I tried to import this ebook to Aldiko, turned out, it does not even find the file - so I've downloaded Moon Reader from Play Store which found the book and offered me to import it. While importing it the app froze and superuser showed me that "Shell" asked root permissions but was denied. Eventually the tablet itself froze. After a few minutes the message occured that Moon reader does not response and I chose to kill the app. Then the display turned black and the tablet seemed to have turned off.
After that point the tablet was not responsive anymore. No matter what I tried, it would not respond to anything. Battery was at 40% before but I connected it to the charger anyways. I've tried to boot up again and this time I got some disfigured weird glitches but nothing like a bootscreen. After some time it actually booted into Android (at that point it was an older PACman ROM). As soon as I've tried to unlock the screen the tablet made some weird noises (sounded like R2D2 ) and turned black again.
Again the only reaction to pressing the power button were some glitches...I left the device untouched for a few minutes and tried booting again, this time holding volume down button and it got me into download mode where I was able to choose recovery mode which then gave me the chance to restore a backup. After that it worked as if all the above never occured
However I've decided to flash cm10.2 nightly build then since I had my little issues with PACman on Nexus 4. Though I don't blame the ROM. But quite frankly I don't have the slightest idea why this happened, what caused it and what exactly this issue was.
So I just thought maybe someone encountered similar before and might be able to tell me, what all this was about.
Besides I've checked this .mobi file with virustotal.com and not one antivirus raised alarm. Still don't know what was inside that .mobi, but I don't really wanna try it on any other device
Anyone ever had this?