Related
Hey guys,
I have a rooted Nook Color, that was running CM7 (very smoothly to say the least), and now it won't boot. Last time it actually turned on was a few days ago and I turned it off, at that point, and now it won't turn back on.
The really weird part is that if i put in my recovery sd card, it'll boot into recovery just fine. From there I've tried to flash pretty much every rom, take out my recovery sd card and boot.. with no avail (on the booting part).
If anyone knows how to get my nook to power on, i would be the happiest guy ever.
P.S. I've tried the whole 'hold power for 10 secs and plug in to have it turn on' deal, and even that doesn't work.
[EDIT] I found THIS xda page that helps you re-format boot. So if you have the same problem go here.
ryanolson7 said:
Hey guys,
I have a rooted Nook Color, that was running CM7 (very smoothly to say the least), and now it won't boot. Last time it actually turned on was a few days ago and I turned it off, at that point, and now it won't turn back on.
The really weird part is that if i put in my recovery sd card, it'll boot into recovery just fine. From there I've tried to flash pretty much every rom, take out my recovery sd card and boot.. with no avail (on the booting part).
If anyone knows how to get my nook to power on, i would be the happiest guy ever.
P.S. I've tried the whole 'hold power for 10 secs and plug in to have it turn on' deal, and even that doesn't work.
[EDIT] I found THIS xda page that helps you re-format boot. So if you have the same problem go here.
Click to expand...
Click to collapse
I'm having the exact same problem. I'll follow that thread. Thanks for updating your post!
[HOW-TO] : Restore Nook Color back to stock EASILY!
Completely resets Nook to out of the Box condition.
Works every time
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
japzone said:
[HOW-TO] : Restore Nook Color back to stock EASILY!
Completely resets Nook to out of the Box condition.
Works every time
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
Click to expand...
Click to collapse
How is that possible if you can't get it to power back? I burned the clock recovery on it and the rootkit and it won't power on at all to even pick up the files.
mrairbrush said:
How is that possible if you can't get it to power back? I burned the clock recovery on it and the rootkit and it won't power on at all to even pick up the files.
Click to expand...
Click to collapse
Just because the backlight isn't coming on doesn't mean it's not powering on
To the OP: sounds like you broke something in the boot partition. Follow the link japzone sent and see if that fixes it.
Just installed CM7 final on uSD card. Works fine. So I went on and followed instruction here http://forum.xda-developers.com/showthread.php?t=1000957 to install gapps. Rebooted a few times, including using the shutdown menu to boot into recovery. But nothing happens. CM7 boot the system without any interaction and there is no sign of gapps anywhere.
Anybody succeeded?
zip file I installed was gapps-gb-20110307-signed.zip
Rename to "update-gapps-gb-20110307-signed.zip"
I had the same problem too with gapps using those instructions. When CM7 final was released, I just reimaged my SD card and tossed cm7.zip and the gapps.zip file onto the root of the SD card and reinstalled CM7. It installed gapps as well and it appears to be working fine.
barf99 said:
Rename to "update-gapps-gb-20110307-signed.zip"
Click to expand...
Click to collapse
Nonsense, you use the name as-is.
OP,
Sounds like you're just not getting into recovery right, it takes some practice with the timing. And you can't 'shut down into recovery', AFAIK that does not work. You'll have to hold the right combination of buttons bootup.. You'll need to look for your particular recovery, but for me I hold Power and the N button during the boot process and let go of the Power button about 5s after seeing the "Reading" message.
Thanks. It looks like khaytsus is right: I need to let go of the power button but hold on to the N button for a bit.
Works now!
After flashing gasps and if you don't see market icon, connect to wifi. Then it should show up.
OMG thanks for the one above me! i was flashing and flashing again and again the whole day about 10 times or more! and the only thing i should do, was enabling wifi -.-
Hello,
Earlier today i successfully installed CM10.1 on my new Nook HD+ tablet. After setting up CM10.1 and installing some basic apps i restarted the Nook and it is now stuck in a loop at the Cyanogenmod start up screen. Any suggestions on how to fix this?
Thanks guys!
I had this same issue. I made a titanium backup of everything, and then reinstalled cwm, cm 10.1, and emmc ovation. I used titanium to restore and now it resets just fine.
Sent from my BN NookHD+ using Tapatalk 2
Same here...
I had the same issue. I went in and cleared the cache then reboot and it was fine. My issue now is it'll randomly reboot on its own and sit at the Cyanogen circle boot up but won't boot up. Anyone else?
I booted into recovery and wiped dalvik cache and the othe cache and it booted fin out of recovery but when i would attempt to reboot it normally it would still be stuck in a boot loop...I just factory reset it and it seems to be working fine now *fingers crossed*!
still no go...
I tried that too and it still reboot randomly. Thought that was fixed with latest version
I had the same problem. This is what I did. In the recovery menu I did a wipe / factory reset. Then installed CM and Google apps again. After that I did another wipe / factory reset. After that I rebooted. No more random reboots and no more boot loops. I hope this helps.
trouble restart
Just got a Nook HD+ on the 26. installed CM10.1. every time I turn off or restart the Nook, For the first 3 times, it would stuck at the fast spinning CM logo. I would have to long press the Power button to turn it off, then turn it back on. For the 4th time it would boot without any problem. same thing with boot into recovery, the first 3 times it would ignore my N+down press, only on the 4th attempt. Not sure why, but that's what I found out. I dont see any random reboot yet. Have not try to reinstall CM10.1. Will do that when I have more time. Anyone else with a newly bought Nook care to sound in?
Very similar problems for me, though I don't know if it's exactly every fourth time that it boots properly.
I did a factory reset, re-flashed everything, and it worked perfectly for a couple of days. Then yesterday, a random reboot, and it got stuck at the CM boot animation. It rebooted properly on the second or third try. I just rebooted it manually, and it worked fine again.
I really like this tablet, but I'm seriously thinking of returning it because of this problem. It seems like it could become completely unusable if it gets worse.
CM 10.1 Boot Loop CWM non responsive
I have the same issue. I used powered up and used Volume Down>Menu and it rebooted my Nook HD+ to back to the original Nook OS. Weird because when installed I deleted factory defaults like the instructions said before flashing. Anyway, now when I hold volume down>Menu on boot it come up Black screen with warning telling me it will delete all my documents and reset to factory. Will this wipe the CM 10.1 OS totally? Is there a way for me to get my CM 10.1 back without going through and making a boot image again and reinstalling from starch? CWM dose not seem to be working or am I using the wrong method to booth into CWM on my Nook HD+?
selwynbaptiste said:
I have the same issue. I used powered up and used Volume Down>Menu and it rebooted my Nook HD+ to back to the original Nook OS. Weird because when installed I deleted factory defaults like the instructions said before flashing. Anyway, now when I hold volume down>Menu on boot it come up Black screen with warning telling me it will delete all my documents and reset to factory. Will this wipe the CM 10.1 OS totally? Is there a way for me to get my CM 10.1 back without going through and making a boot image again and reinstalling from starch? CWM dose not seem to be working or am I using the wrong method to booth into CWM on my Nook HD+?
Click to expand...
Click to collapse
What you are seeing is stock recovery (I assume you mean you held n and power on boot, there is no menu button). You must not have successfully flashed the CWM or TWRP recovery to internal memory. That reset to factory it will just wipe your data, not remove the ROM. It will cause you to reinstall your apps though.
If you ever intend on updating your CM10.1 to a newer version in the future, you need to have that bootable recovery SD anyway (or successfully put it on internal memory).
Sent from my Nook HD+ running CM10.1 on emmc.
Reinstalled CWM and CM 10.1
leapinlar said:
What you are seeing is stock recovery (I assume you mean you held n and power on boot, there is no menu button). You must not have successfully flashed the CWM or TWRP recovery to internal memory. That reset to factory it will just wipe your data, not remove the ROM. It will cause you to reinstall your apps though.
If you ever intend on updating your CM10.1 to a newer version in the future, you need to have that bootable recovery SD anyway (or successfully put it on internal memory).
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
In did install both the CWM and CM 10.1 the first time. It booted and rebooted for days without a problem. I believe b what happened was error. I had the alarm set to wake me and half asleep tried to turn it off while the groovy cover was shut by holding down the power button. I may have held down more keys then I thought in a sequence that deleted something that caused the Boot to hang. After that there was no way for me to enter the CWM. The command sequence that would normally send me to CWM sent me to nook factory reset. I noticed that there is a small glitch between hibernate and the b alarm. Holding down the power key to get it to shutdown can cause it enter CWM from time to time.
When I reinstalled everything funny thing is my screen lock settings and background selection (I previously downloaded) stayed along with my user profile. That leads me to believe that everything was in tact on the internal storage. Google play backed up and reinstalled all my apps automatically once I signed in:good:. I'm taking your advice and buying a 4G SD to keep the CMW boot image on with the latest CM. Thanks for your help.
Distorted Boot Animation
Is there a way to fix the distorted boot animation on Nook HD+ CM10.1? I have tried installing a different bootanimation.zip but it didn't make a difference.
I found this post on a similar problem with the nook color running CM10.1, and steven676 fixed the boot animation issue with a new kernel. "I was wandering if it could be used to fix the Nook HD+ as well?"
Josmar1993 said:
Is there a way to fix the distorted boot animation on Nook HD+ CM10.1? I have tried installing a different bootanimation.zip but it didn't make a difference.
I found this post on a similar problem with the nook color running CM10.1, and steven676 fixed the boot animation issue with a new kernel. "I was wandering if it could be used to fix the Nook HD+ as well?"
Click to expand...
Click to collapse
Yes that could fix it, but it messes up other things. Best to just live with the distortion.
Sent from my Nook HD+ running CM10.1 on emmc.
Thanks for the reply
leapinlar said:
Yes that could fix it, but it messes up other things. Best to just live with the distortion.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
"I guess in order for one to gain, one must lose something." LOL
In meantime I'll just disable the boot animation with Rom Toolbox.
Hopefully it get's fixed in later updates without any lost.
This thread seems to be in the range of what my issues are. The Nook worked fine for about 4 days and then while installing the Retro Arc apk I sideloaded, it picked up on an unprotected Wifi connection in the area. It then locked up as the notifications were flying in, and the screen went black. I powered off then off after that once and the Cyanogen logo just kept looking. Tried again after and it went to Stock Nook.
The last few days have been spent doing clean installs with care taken to follow the exact steps, but now all I get for 2 days is the Cyanogen Logo looping over and over. Help?
nkca6384 said:
This thread seems to be in the range of what my issues are. The Nook worked fine for about 4 days and then while installing the Retro Arc apk I sideloaded, it picked up on an unprotected Wifi connection in the area. It then locked up as the notifications were flying in, and the screen went black. I powered off then off after that once and the Cyanogen logo just kept looking. Tried again after and it went to Stock Nook.
The last few days have been spent doing clean installs with care taken to follow the exact steps, but now all I get for 2 days is the Cyanogen Logo looping over and over. Help?
Click to expand...
Click to collapse
Just found this on a thread here. I can't find it at this time. I would really like to credit and thank the poster. I had to go into CWM and wipe dalvick cache on every boot. I have only booted once but this change seems to have fixed this issue.
Firsts go into CWM and wipe dalvick cache.( Hold down the power and n buttons until you get into CWM. Go to advanced and wipe dalvick cache. Reboot)
When you get it booted, go into setting/launcher/home screen and uncheck Wallpaper quick render.
Good luck!
josim
Edit to say credit goes to Arron Camp for this fix. Thanks Arron!
josim said:
Just found this on a thread here. I can't find it at this time. I would really like to credit and thank the poster. I had to go into CWM and wipe dalvick cache on every boot. I have only booted once but this change seems to have fixed this issue.
Firsts go into CWM and wipe dalvick cache.( Hold down the power and n buttons until you get into CWM. Go to advanced and wipe dalvick cache. Reboot)
When you get it booted, go into setting/launcher/home screen and uncheck Wallpaper quick render.
Good luck!
josim
Edit to say credit goes to Arron Camp for this fix. Thanks Arron!
Click to expand...
Click to collapse
I have had the same problem in this thread as well (reboots stuck at cyanogenmod logo). I have been wiping the dalvik cache every time (figured it out on my own) and can confirm it works but you do have to do it at every boot (or perhaps after you change wallpaper, not sure).
I got tired of it happening so i google'd the issue and found this thread; mine is stuck right now too (and also out of battery, lol), but once I charge it, wipe dalvik and boot into android I will try the "quick render" trick and see if that fixes the boot problem to begin with.
Edit: I can confirm that disabling quick render has fixed the need to do a dalvik wipe every reboot.
Question
I have a nook Tablet Color + I think, well three of them actually one of them acts like the battery is dead, however when I plut it in using the "Nook" cable it goes green tab turns on, at the first splash screen with the big N for the nook symbol, and than it powers off and loops there? Suggesstions
Tinyneustra said:
I have a nook Tablet Color + I think, well three of them actually one of them acts like the battery is dead, however when I plut it in using the "Nook" cable it goes green tab turns on, at the first splash screen with the big N for the nook symbol, and than it powers off and loops there? Suggesstions
Click to expand...
Click to collapse
I don't know if the color+ has sdcard recovery but if it does that would be the way to go except for...
The other thing is that if you had put on a custom recovery then holding what ever buttons to go to it could allow you to fix it. Or waiting until 8 reboots or whatever if its the same as the nook hd+.
I think there may also be additional stuff that can be tried on the nook logo screen via various button presses as well but don't have any knowledge about that especially for the color+
Just installed the latest update (0621), and now when I try to do anything to open the UI from the booted splash screen (lock image) I get the message above.
I cannot shutdown or reboot to go back to an earlier version, I can only power off with the power switch.
If I try to use the reboot option from the splash screen, the recovery option has disappeared.
Starting the unit again produces the same result.
My latest boot got me the animated logo then presented a solid light blue screen.
How do I get it back so I can install the earlier build that was working while you fix this problem.
Right now the unit is useless, absent making up a new SD card. I have lots of stuff on the current card so would prefer not to do this.
This is somewhat similar to the clock has stopped warning on some earlier builds, but these did not render the unit inert.
exfed2002 said:
Just installed the latest update (0621), and now when I try to do anything to open the UI from the booted splash screen (lock image) I get the message above.
I cannot shutdown or reboot to go back to an earlier version, I can only power off with the power switch.
If I try to use the reboot option from the splash screen, the recovery option has disappeared.
Starting the unit again produces the same result.
My latest boot got me the animated logo then presented a solid light blue screen.
How do I get it back so I can install the earlier build that was working while you fix this problem.
Right now the unit is useless, absent making up a new SD card. I have lots of stuff on the current card so would prefer not to do this.
This is somewhat similar to the clock has stopped warning on some earlier builds, but these did not render the unit inert.
Click to expand...
Click to collapse
Developer has said he will fix this in next build. Look at his thread.
Sent from my Galaxy Tab 2 using XDA Premium
leapinlar said:
Developer has said he will fix this in next build. Look at his thread.
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
And that is going to help how?
Did you read my post?
The unit is unable to get past the splash screen with the lock icon. I can't even regress to a working build.
exfed2002 said:
And that is going to help how?
Did you read my post?
The unit is unable to get past the splash screen with the lock icon. I can't even regress to a working build.
Click to expand...
Click to collapse
Just boot to recovery, wipe data and reflash. But you will lose apps and settings, not much you can do about that.
Sent from my Galaxy Tab 2 using XDA Premium
leapinlar said:
Just boot to recovery, wipe data and reflash. But you will lose apps and settings, not much you can do about that.
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
I wasn't able to do that as I had to shutdown, that was the only option.
In some way, punching the power key and home key in some sequence, suddenly the recovery menu appeared. Don't ask me how.
I was able to go back to the 0615 build, and from there do the upgrade to the 0623 build and now it's working.
But I have no idea how I got the revery menu to come up when all else failed.
exfed2002 said:
I wasn't able to do that as I had to shutdown, that was the only option.
In some way, punching the power key and home key in some sequence, suddenly the recovery menu appeared. Don't ask me how.
I was able to go back to the 0615 build, and from there do the upgrade to the 0623 build and now it's working.
But I have no idea how I got the revery menu to come up when all else failed.
Click to expand...
Click to collapse
Holding power + n key on boot takes you to recovery.
Sent from my Nook HD+ running CM10.1 on emmc.
System ui stopped Nook
I encountered this problem as well. Thanks to your posts, I started trying things before the flash screen locked. I downloaded a Nook app and the error message and display screen errors went away. I hope this works for someone else also..
I installed evergreens rom for ds on the nook tablet hd+ and every thing seems to work fine but when i try to reboot the option to boot to recovery is not avail... every thing about the tablet seems to work just fine but.. i wish to update the rom a bit but with out a recovery option at boot up im a bit stuck... any ideas on where im fouling this up?
scuzzo said:
I installed evergreens rom for ds on the nook tablet hd+ and every thing seems to work fine but when i try to reboot the option to boot to recovery is not avail... every thing about the tablet seems to work just fine but.. i wish to update the rom a bit but with out a recovery option at boot up im a bit stuck... any ideas on where im fouling this up?
Click to expand...
Click to collapse
In order to get the reboot menu on 10.1 you need to activate developer options and enable Advanced Reboot as well as enable Reboot Menu in System, Power Menus. Activating developer options is tricky. As I recall you have to tap the Android version number seven times in About Tablet. I have 10.1 on emmc, but I suspect all of the above also applies for SD installs.