My n2a rooted nook color won't boot. The circle just goes round and round the Android on his skateboard and it won't boot. Any ideas?
No idea but I had the same exact thing happen today. I just held the power button in until it powered off. I waited a few minutes and powered it back up. CM7 started with no problem.
Mine did this right after I tried to turn wifi on at home without first turning off airplane mode. For some reason that cause havoc. I got the round and round after rebooting. Everything works fine now. No idea why.
i read that sometimes it can take up to 3-8 boot load trys for it to work, it might be normal, mine took awile for it to load as well, im running 7.0.3 what are you?
I'll let you know what I'm running if I ever get it running again to see what I'm running.
Ok cool
Sent from my Nookcolor Cyanogenmod 7.0.3
jlhatch said:
My n2a rooted nook color won't boot. The circle just goes round and round the Android on his skateboard and it won't boot. Any ideas?
Click to expand...
Click to collapse
Did you call N2A for support? Isn't that the reason people pay all those extra bucks for those cards?
Easy enough (and cheaper) to roll your own using the directions found here, if you're interested.
I rolled my own originally, and the wifi stopped. Couldn't figure it out, so I just bought a n2a card for easier usage. Apparently there are problems no matter which way I root.
Related
Since this morning, when I boot it will get stuck on that red eye screen. I've waited several minutes and it won't go on.
So I end up pulling the battery and usually that works. Sometimes I have to do this twice.
Not sure how to even diagnose this.
HoochieCoo said:
Since this morning, when I boot it will get stuck on that red eye screen. I've waited several minutes and it won't go on.
So I end up pulling the battery and usually that works. Sometimes I have to do this twice.
Not sure how to even diagnose this.
Click to expand...
Click to collapse
Are you rooted or completely stock?
Sent from my ADR6300 using XDA App
Rooted. I just tried restoring a backup from 3 days ago and had the same problem. So I restored back to the latest. When it finally does boot, it seems to run great.
I have a backup from further back, just not sure it will make a difference. Might give that so shot too.
I really think it is booting all the way, and just doesn't stop displaying the boot animation.
The reason I think that is because at some point the power button makes the screen go on and off, and there is haptic feedback in the same places where my lock screen tabs are.
At any rate, and this sounds unbelievable, but I pulled the sd card out and it booted normally. I put the card back in, and now it seems to boot normally. Can't explain it.
When I hit the power button to shut the screen off, it flashes brightly before it goes off.
Wondering if this is a Nook Color thing in general, or just a CM7 thing. Is this related to the fact that the screen animation doesn't work on CM7 when using the current kernel? I heard that Dalingrin had the screen animation working in the early test kernel and wondered if this got rid of the screen flash as well.
FWIW, mine flashes also. I haven't researched the cause, though.
CM7.0.2 from SD, when I tap the power button, it fades over about half a second. No flash, although occasionally there's a flicker in the middle of the fade. Power on happens much quicker, but there is a bit of fade-in.
I did enable on and off animations, even though I didn't think they were supposed to work yet.
this is a CM7 thing. its a power off and on animation. if you dont like it you can turn it off in settings. personally i like it. it reminds me of the old CRT screens.
boxcar8028 said:
this is a CM7 thing. its a power off and on animation. if you dont like it you can turn it off in settings. personally i like it. it reminds me of the old CRT screens.
Click to expand...
Click to collapse
More specifically it's a 2.3 thing - but I think the problem is that it doesn't work the same as on other standard resolution screens so it just ends up 'flashing' rather than doing a fancy animation. Your solution is correct though.
Interesting. The on/off animations are off by default in the Encore build. I enabled them in the settings and still had the flash (as one would expect). However, once I disabled them again everything was fine. I wonder if this is another persistence bug, similar to airplane mode?
My screen flashes whether the screen animations are on or off, though to be fair it doesn't flash every time, definitely more often than not though.
Mine is more of a quick blink rather than an obvious flash. And it isn't consistent.
My screen flashes as well. It just started doing this yesterday and I've been running cm7 off my sd card for about a week with no other problems. Worse, sometimes the screen turns green and stays that way until I hit the N button. Any idea what this means and possibly how to fix it? Any input would be greatly appreciated. Thanks.
FairJuno said:
My screen flashes as well. It just started doing this yesterday and I've been running cm7 off my sd card for about a week with no other problems. Worse, sometimes the screen turns green and stays that way until I hit the N button. Any idea what this means and possibly how to fix it? Any input would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Which version of CM7 are you running? I haven't seen the flash or the green screen since I switched from 7.0.2 to nightly 86. Maybe it's coincidence, but it looks like the flash issue has been fixed.
(The power button does sometimes turn off the screen briefly then turn it right back on again -- hitting the power button a second time always turns it off.)
akaCat said:
Which version of CM7 are you running? I haven't seen the flash or the green screen since I switched from 7.0.2 to nightly 86. Maybe it's coincidence, but it looks like the flash issue has been fixed.
(The power button does sometimes turn off the screen briefly then turn it right back on again -- hitting the power button a second time always turns it off.)
Click to expand...
Click to collapse
It's the CM7.0.3 stable version. Maybe I should do an update. I wasn't sure if that was the problem since it had just started doing this. Are you saying you've seen the green screen? Just curious because I can't find anything about it anywhere. Thank you for your response. I'm going to try out the nightly and see if that fixes the problem.
Mine does more of a quick flicker,i think its the screen off/on animation issue on the nook because the animation works fine on my droid incredible cm7
GreenXSniper said:
Mine does more of a quick flicker,i think its the screen off/on animation issue on the nook because the animation works fine on my droid incredible cm7
Click to expand...
Click to collapse
Actually, that's what mine does too. Sometimes there's a flash, but most of the time it's a quick flicker. If it's just the animation then I probably don't need to worry about it. It's just the green screen that worried me...though that only occurred when I kept messing with it. I haven't messed with it the past couple of days so I haven't seen the green screen. Maybe I was causing some kind of error.
FairJuno said:
It's the CM7.0.3 stable version. Maybe I should do an update. I wasn't sure if that was the problem since it had just started doing this. Are you saying you've seen the green screen? Just curious because I can't find anything about it anywhere. Thank you for your response. I'm going to try out the nightly and see if that fixes the problem.
Click to expand...
Click to collapse
Yup, I've seen the green screen. I don't remember what build I was on at the time because I looked at a bunch over a couple of days. It could have been 7.0.3.
Or maybe I messed up something on my nook, and flashing another build corrected it? Either way, I haven't seen it in a few weeks.
akaCat said:
Yup, I've seen the green screen. I don't remember what build I was on at the time because I looked at a bunch over a couple of days. It could have been 7.0.3.
Or maybe I messed up something on my nook, and flashing another build corrected it? Either way, I haven't seen it in a few weeks.
Click to expand...
Click to collapse
That's good that you haven't seen it in a while. And not that I want anyone else to suffer, but I'm glad I wasn't the only one. LOL. Hopefully that means I'll have an easy fix. I haven't seen it in a few days myself, so I'm just going to wait and see what happens. Most likely I'll update to a nightly. Thanks for the responses. Now I'm not worried about it anymore.
Close to two months ago I installed the latest Phiremod ROM onto my Nook Color. (Phiremod 7 I think) I followed a webpage tutorial and referenced XDAdevelopers instructions. Has been working excellent for the past couple months. Got everything set up and working great... youtube, hulu, netflix, etc. Now all of the sudden my Nook Color won't bootup but gets stuck. I turned it on yesterday to check the battery life because I haven't used it in a couple days and it was at 15% and everything was fine. I remember hearing the notification sound last night so I looked and said battery was dead so I plugged it in and left it last night. This morning I noticed the screen was on, even though it was a black screen.
Now after I hold the power button for 10 seconds it goes to the "Touch the future of reading" page for a few seconds, next it shows "loading..." in white letters in the middle of the screen for less than a second before going to the screen where "ANDROID_" is spelled in small light blue letters vertically in the upper left hand side of the screen. It will stay at this "ANDROID_" screen indefinitely until the display goes black after about 10 minutes, or until I hold the power button for 10 seconds to turn it off.
Any ideas how I can fix this or get it to boot up? I don't understand why it has worked great for two months and then out of the blue quit working? I haven't installed anything, modded anything, or stuff like that before it quit working. In fact the last few days before it quit this morning all I have done is turned it on briefly to check the battery level (because I decided to monitor it more, loses about 25% battery per day just sitting turned off). Any help is greatly appreciated, really have enjoyed using the NC as an android tablet.
rjl2001 said:
Close to two months ago I installed the latest Phiremod ROM onto my Nook Color. (Phiremod 7 I think) I followed a webpage tutorial and referenced XDAdevelopers instructions. Has been working excellent for the past couple months. Got everything set up and working great... youtube, hulu, netflix, etc. Now all of the sudden my Nook Color won't bootup but gets stuck. I turned it on yesterday to check the battery life because I haven't used it in a couple days and it was at 15% and everything was fine. I remember hearing the notification sound last night so I looked and said battery was dead so I plugged it in and left it last night. This morning I noticed the screen was on, even though it was a black screen.
Now after I hold the power button for 10 seconds it goes to the "Touch the future of reading" page for a few seconds, next it shows "loading..." in white letters in the middle of the screen for less than a second before going to the screen where "ANDROID_" is spelled in small light blue letters vertically in the upper left hand side of the screen. It will stay at this "ANDROID_" screen indefinitely until the display goes black after about 10 minutes, or until I hold the power button for 10 seconds to turn it off.
Any ideas how I can fix this or get it to boot up? I don't understand why it has worked great for two months and then out of the blue quit working? I haven't installed anything, modded anything, or stuff like that before it quit working. In fact the last few days before it quit this morning all I have done is turned it on briefly to check the battery level (because I decided to monitor it more, loses about 25% battery per day just sitting turned off). Any help is greatly appreciated, really have enjoyed using the NC as an android tablet.
Click to expand...
Click to collapse
I had a similar problem, or at least similar symptoms (but it was caused by an ID-10-T error) and I ended up just booting into recovery and restoring my last nandroid (oddly enough this nandroid didn't include any of the apps I had installed and it has been a while since my last TiBa so I have a lot of "manual recovery" to take care of).
So I would go ahead and try to restore. Sorry I can't be more help.
Drachen, thanks for the reply. I'll take any advice or information anyone has. I would definitely be happy to restore, losing all my apps is better than having a bricked NookColor lying around.
Do you know where I can find directions on how to do a restore? I'm not too technical when it comes to this stuff, I've just rooted it a couple different times because I had some clear and precise step by step instructions of exactly how to do so. I know I'm unable to boot into the recovery mode like I was able to do before when I was first installing Phiremod. Also since it has been a couple months a lot of the steps and details are not fresh in my mind.
There was no version7 2 months ago.
Sent from Nook Color on Phiremod 6.3 @1.3Ghz
OK, I guess I don't remember which version is installed then.
Well I am able to boot into ClockworkMod Recovery v3.0.2.8 , so this gives me some hope now. However, I'm still unsure what the next course of action is. Any reboots still get hung up on that one screen. I had erased the Phiremod files from the SD card, so I don't think I can reboot using it, nor do I have any backups listed on ClockworkMod.
rjl2001 said:
OK, I guess I don't remember which version is installed then.
Well I am able to boot into ClockworkMod Recovery v3.0.2.8 , so this gives me some hope now. However, I'm still unsure what the next course of action is. Any reboots still get hung up on that one screen. I had erased the Phiremod files from the SD card, so I don't think I can reboot using it, nor do I have any backups listed on ClockworkMod.
Click to expand...
Click to collapse
Download the phiremod zip here, put it on the root of your SD card, and then boot into recovery>install zip from sd card>choose zip from sd card>Phiremod zip.
Finally figured it out after a few weeks of a Nook paperweight and hours of googling and trying different methods. What wound up working for me was totally restoring it back to stock. This website "Maurice Mongeon - Nook Color: Recover Any Bricked Device/return to stock" had great step by step directions on how to do it, and it was actually easy. Now I just need to figure out if it is worth rooting again, or would it just fail out of the blue like it did this time?? Anyways, thanks for the help.
Someone gave this to me to figure out how to get it to JB.
Well, it was stock HC and worked great. no problems, he flashed the ICS that lenovo offered and didnt realize that it wiped everything including the play store.
So I went ahead and nvflashed the CM10 Version 2 on it, as the new V6 isnt in nvflash format. (sucks).
Well it got all the way through and the battery died at the cyanogen boot screen. So i had to go get the charger from him (didnt charge from USB.) and plug it in. let it charge a little bit
Well it booted up, but noticed the home button did NOT work anymore, and the wifi was dead now. Never finds anything, doesnt connect to anything.
So i tried downloading stock images, tried all the hanning things, for what little he has left on the hosting site, etc... and absolutely cannot restore wifi and home button. Also since the home button quit, CWM isnt usable. So i cant flash any CWM images, impossible as it requires the home button to respond. so trying the keylayout fix is pointless because of the chicken and the egg syndrome. I tried all the tricks like holding the button while powering into normal mode, or recovery. no change. Same deal. its just dead jim.
Once i put the factory HC back on, the Wifi did the same thing. and home didnt work still. Took it back to the lenovo JB which is what it was at when I got it, still no WIFI. but it just stays stuck on turning on.... And still, no home button.
I am at a loss.... any ideas? Everything worked before this whole fiasco started.
after trying to get into CWM at least 20 times, one time it DID finally recognize the home button just that once. So i was able to flash on V6 but it made no difference in operation on home button or wifi.
So, I got the key patch and booted back into CWM, again lost the home button. it only worked 1 time after a million tries. I wonder if there are multiple hardware versions? and i got one of the odd ones?
It requires the flash_old and oldboot files in order to take it to stock. new craps out.
mbates14 said:
after trying to get into CWM at least 20 times, one time it DID finally recognize the home button just that once. So i was able to flash on V6 but it made no difference in operation on home button or wifi.
So, I got the key patch and booted back into CWM, again lost the home button. it only worked 1 time after a million tries. I wonder if there are multiple hardware versions? and i got one of the odd ones?
It requires the flash_old and oldboot files in order to take it to stock. new craps out.
Click to expand...
Click to collapse
I'm not sure about your WiFi problem, but I heard if you restart the tab and hold the home button while its restarting and after the lenovo screen goes away you can let go. That might work. Do it even if you're booting into CWM
Sent from my CM10 K1 Tab
DevsAwesome said:
I'm not sure about your WiFi problem, but I heard if you restart the tab and hold the home button while its restarting and after the lenovo screen goes away you can let go. That might work. Do it even if you're booting into CWM
Sent from my CM10 K1 Tab
Click to expand...
Click to collapse
I have tried that trick. It only worked the 1 time out of maybe 500000.
Wifi, the Stock HC gets stuck on Turning on. All the rest of the ROMs will turn the wifi on, but the scan is empty. and it wont connect to nothing.
Edit: Nevermind on the WiFi, its just really really weak. If i walk closer to the router it finally picks it up. I am a dumbass. My ancient g1 works great with 3 out of the 5 bars. But the Home button problem is extremely elusive.
mbates14 said:
I have tried that trick. It only worked the 1 time out of maybe 500000.
Wifi, the Stock HC gets stuck on Turning on. All the rest of the ROMs will turn the wifi on, but the scan is empty. and it wont connect to nothing.
Edit: Nevermind on the WiFi, its just really really weak. If i walk closer to the router it finally picks it up. I am a dumbass. My ancient g1 works great with 3 out of the 5 bars. But the Home button problem is extremely elusive.
Click to expand...
Click to collapse
Yeah, thats the one thing I hate about this tab is the weak WiFi strength. I've never had any problems with the home button but I've heard the people have had luck using that trick. Wish you luck
Sent from my AOKP GS2
I applied the 4core fix for my N6P back in September of last year, and stopped using it around December because of the battery life. Around July/August I purchased a battery and installed it and things were going well. Now my phone is freezing and booting to the Google Logo and... Crash again. No Nexus animation; Google, crash. Sometimes it will attempt to boot and bootloop and sometimes it turns on and works fine. Sometimes if it turns back on it freezes and boom. Google logo.
I guess the remaining 4 cores in this phone are done completely from the looks of it? I know the patch wasn't meant to be permanen, only temporary because the remaining 4cores would eventually die.
snappycg1996 said:
I applied the 4core fix for my N6P back in September of last year, and stopped using it around December because of the battery life. Around July/August I purchased a battery and installed it and things were going well. Now my phone is freezing and booting to the Google Logo and... Crash again. No Nexus animation; Google, crash. Sometimes it will attempt to boot and bootloop and sometimes it turns on and works fine. Sometimes if it turns back on it freezes and boom. Google logo.
I guess the remaining 4 cores in this phone are done completely from the looks of it? I know the patch wasn't meant to be permanen, only temporary because the remaining 4cores would eventually die.
Click to expand...
Click to collapse
My 6p also started bootlooping again today and this time fix didn't help me. I think it's gone for good.
maxguncel said:
My 6p also started bootlooping again today and this time fix didn't help me. I think it's gone for good.
Click to expand...
Click to collapse
Is yours booting to the Google logo and crashing? Or simply bootlooping? Mine goes to the logo, crashes about 10-15 times and then eventually attempts to boot.
It's a shame, got a baby on the way and simply can't afford another phone right now
snappycg1996 said:
Is yours booting to the Google logo and crashing? Or simply bootlooping? Mine goes to the logo, crashes about 10-15 times and then eventually attempts to boot.
It's a shame, got a baby on the way and simply can't afford another phone right now
Click to expand...
Click to collapse
Displays Google logo about 20-30 sec and restarts. Before I could see the animation but this time no luck.
Congratulations! I also have a newborn, we'll see what the future holds
maxguncel said:
Displays Google logo about 20-30 sec and restarts. Before I could see the animation but this time no luck.
Congratulations! I also have a newborn, we'll see what the future holds
Click to expand...
Click to collapse
Thank you You too! Day of Thanksgiving he is supposed to get here, but my wife isn't doing too well lol do you know of any way for us to pull data? Adb is failing to see my device when it's in the bootloader, fastboot is working though. I tried once more to flash twrp 4 core and boot it with no luck. Those small cores gave out I guess. I left my phone on overnight bootlooping with no luck. I got most things off, just my actual camera fder I couldn't get and apps which aren't a huge deal.
Sadly this morning I had the same problem. Bootlooping, I even cannot enter into Recovery. Then, suddently, it restarted, but I wasn't home, so I hadn't the chance to save the data. Then, about 3 hours later, it restarted bootlooping and, since then, it's stucked into this bootloop. Even reflashing the modified boot won't work.
Anybody knows how to at least recover the data inside? Even if I have to break the phone (I'm going to buy onther one soon)
hey guys, me too. but you know something? my initial assessment was that it was a result of an update. Now looking here annd seeing so many others with the same problem at the SAME TIME?? mine happened out of the blue on about October 4th or 5th. Ive had this phone for two years and never had aproblem with it at all. right out of the blue (in the morning) i get the bootloop. I cleared the cache and it booted up again. it was just fine for two days and now it is down black and out. When i push the power button i get a red light. one blink. if i hold down pwr and vol i get 8 blinks. tried on stock charger and other charger. like was previously mentioned when i tried it on a different charger it worked. the first time. now its dead. any solutions?
Marxmellow said:
hey guys, me too. but you know something? my initial assessment was that it was a result of an update. Now looking here annd seeing so many others with the same problem at the SAME TIME?? mine happened out of the blue on about October 4th or 5th. Ive had this phone for two years and never had aproblem with it at all. right out of the blue (in the morning) i get the bootloop. I cleared the cache and it booted up again. it was just fine for two days and now it is down black and out. When i push the power button i get a red light. one blink. if i hold down pwr and vol i get 8 blinks. tried on stock charger and other charger. like was previously mentioned when i tried it on a different charger it worked. the first time. now its dead. any solutions?
Click to expand...
Click to collapse
It simply means that the battery is fully discharged. Keep it connected to the current and maybe it restarts working.
I'm in the same situation since yesterday, hoping that at some point it returns working for some time, just to backup some data. I have like 10GB of photos not backupped in it.
When I replaced my battery I reinstalled factory. Start from scratch.
I had the same issue and that's all I did. Booted fine after that. I used the ifixit battery tho, cause if you got a lower cost one it could be the battery itself too