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+
Related
I think this was caused from the update that went out. It would boot up and ask me what home screen i wanted to use zeam, android, or prolauncher. I would try and click on one and it wouldnt respond to touch input. So I had to do a hard reset and now its just stuck at the nook color boot animation..
Anyone else have this problem?
Yes, I have this same problem.
It was working fine until, I powered it down and powered it back. After the first unlock screen, your are prompted if you want to use ADW, luncherpro, or home. It does not allow you to select anything from the menu.
After you do a hard boot you are stuck at the nook color loading screen.
If I do the factory reset, I assume I will have to root it again
When I was there (boot loop after 1.0.1 install) a few days ago, I had to do the 3 finger data reset (power, Volume up and Home key press and hold) and then re-register the nook with B&N.
Just did the same thing
Geezer Squid said:
When I was there (boot loop after 1.0.1 install) a few days ago, I had to do the 3 finger data reset (power, Volume up and Home key press and hold) and then re-register the nook with B&N.
Click to expand...
Click to collapse
I just did the same thing, I set a launcher with softkeys then uninstalled that launcher then hit home, softkeys got stuck looking for a launcher. I rebooted and then it was stuck on the nook color boot screen.
I got into clockwork and now I am nandroiding back.
It should be all fine... I hope.
Edit: worked fine, up and running great again, Gotta love that nandroid!
Stuck at COLOR boot after flashing CM onto ManNoot
Flashed ManualNooter. Seemed to go perfectly. However, I downloaded Cyan 7 from ROM Manager, backed up, wiped, flashed it (apparently successfully), but got stuck on boot screen. Had to reboot into Recovery and restore Nand backup. Same exact results with Phiremod. HOWEVER, I am able to boot into CM 7 from a flashed SD card I created. Can any of you extremely AWESOME people help me get CM correctly flashed onto my NC running MN? Thanks!
Well here goes, I already reflashed the stock rom once from autonooter. 8 reboots then the stock rom becomes reflashed... Well in an attempt to return to stock 1.0 and install the updated autonooter I seem to have bricked my nook.
I can force reboot the nook 8 times and then the system update installed successfully... So it seems (progress bar reaches the end and nook reboots) but the splash screen is not stock! It runs the nook dev splash screen and will not boot. It will bootloop over and over. I tried another system reflash but same thing. What can I do?
Is it possible to run the autonooter sd card image ? Any other ideas?
Thanks
You need to wipe the NC. Power off. Hold power and home until it wipe screen appear. It might start wiping automaticlly or you may need to press home continue. Don't remember.
The 8 boot method is only half of the system wipe process. You still need to wipe /data. Steps to do that are at: http://nookdevs.com/Flash_back_to_clean_stock_ROM
It worked! Thanks
I could have sworn I did that several times. I had to hold both the power and nook button until the unit shut off. Then on the next boot attempt it gave me a data wipe option. Tricky little unit
Hi guys,
I just got two HD+ 32GB and installed cm-10.1-20130527-UNOFFICIAL-ovation-emmc following evergreen and leapinlar's instructions. The installation went well, and I can boot the tablets into twrp recovery. But I cannot boot one tablet into Android. It always hangs on CyanogenMod log (the rotating circle/wheel with CyanogenMod text at the center) when trying to boot into Android. I reboot the tablet several times now and still have the same issue.
I repeated the same procedure on another Nook HD+ 32GB and I can boot the second tablet into Android after several reboots. But I still have no luck with the first tablet.
Any suggestion?
Thanks a lot for the help!
Sean
I installed CM10.1 eMMC on my HD+ for the first time last night and the same thing happened to me. So I went back into recovery and installed the CM10.1 again and then it booted up normally afterwards. So in my case at least it seems like it didn't install right on the first try.
Ravynmagi said:
I installed CM10.1 eMMC on my HD+ for the first time last night and the same thing happened to me. So I went back into recovery and installed the CM10.1 again and then it booted up normally afterwards. So in my case at least it seems like it didn't install right on the first try.
Click to expand...
Click to collapse
Thanks a lot for the suggestion. I finally got It to work by booting into TWRP to wipe system, data, and caches, then re-installing from zips.
Sean
Same issue, apparently (hopefully...) resolved
LIke many other posters here and elsewhere, I installed CM 10.1 on my brand new Nook HD+ 32gb, got it to boot into CWM after many trials and tribulations (I had to reboot about 30 times to get the device to boot into recovery from SD; it crashed halfway through backup in spectacularly frustrating fashion, and it took me about 30 more hard resets to get it to boot into CWM again. I used a brand new Amazon Basics 32gb class 10 card). I did a little victory dance, loaded up some apps (probably too aggressively: 50 or 60 of them), rebooted, and.... you know what happened then, or you wouldn't be reading this (probably whilst sweating and/or crying).
After uninstalling some resource-intensive apps, then booting into recovery and wiping both caches, I was able to reboot normally (aside from waiting a couple of minutes for apps to be "updated" or "optimized" or whatever), but the next and all subsequent reboots failed unless I first booted into recovery and wiped the caches.
Finally, after reading a number of posters with the same problem (including @Ravynmagi and @sean_nj here--thanks, guys), I took a deep breath, did a full Titanium backup, booted into CWM, did a factory data reset, and reinstalled the three zips from the bootable SD. CM booted quickly and normally. I rebooted a couple of times with no problems. I installed a few apps, rebooted normally. I installed a few more apps (including a couple which I sideloaded), again rebooted normally. In the last 18 hours, I've installed a few more apps, played some resource-intensive games, tested Netflix and a sideloaded video, etc.
As of now, the device works like a charm and boots quickly and without drama. If anything changes (and I'm still able to communicate like a civilized human being), I'll make sure to update here.
unable to reboot get spinning logo
I recently updated Nook HD+ to 10.1 w/o problems.Each time I have rebooted it take 2 -3 tries before it finally boots ups. Those other times if boots to the spinning Cyanogen logo. Is there something I can do to check with the system booted up correctly to figure out the problem. If not, what steps should I take now and how do you do a complete backup of all the newly added material since the initial update. Thanks again,
Al
I'm facing the same problems but with a different setup: latest CM 10.2 Carbon ROM release (both versions with and without multiwindow). I have random bootloops and I'm unable to track down the problem.
Are we the only users with those bootloops?
Was searching for this. I am not having a problem booting per se, but all of a sudden I am getting a weird booting thing. Where the logo comes up and spins but its distorted, then it becomes normal looking, then my Nook will kind of reboot. Not a complete reboot just the screen goes black for a millisecond and then the logo starts over again where its all distorted, then it goes normal and then it boots.
I guess you can call it a logo boot loop. The thing is, it doesn't happen all he time, just most of the time now. When it happens, my SD card is incorrectly mounted and I have to umount it and take it out physically and re-insert it.
Nook HD+ 32gb, CM 10.1.3 stable and mbg4ga emmc. Not sure if this is the same as you guys but it sounds related. I've re-flashed several times. I think if you guys can find a cure, then it would probably work for me as well. Quick question, any of you guys using auto-patcher to patch Pdroid? How about Xposed?
For getting caught in the boot loop try:
Settings>Launcher>uncheck wallpaper quick render.
This is for stock Trebuchet 1.0 Launcher. I hope the developers are aware of this.
Probably coincidental but, the glitch caused by the magnetic closure on my case much better.(when you try to unlock and it blinks and goes back to lock).
Good luck.
I am running the 6/13 binary and the system gets stuck when I attempt a reboot. It freezes at the CyogenMod screen with the animation. I have attempted a reboot through powering off, and through the CWM, but I am still stuck. I was previously able to wipe the delvik cache, which worked, but all of the applications had to "optimize" every time before it booted up.
Is there a way to get past this?
I am running a 16GB Nook HD+ with an emmc install. It worked fine for a day, but now every time it boots it doesn't get past the CM animation.
I ended up with the same problem until I realized I flashed one of the nook HD zips instead of the HD+ version. Make sure everything you have says ovation and not hummingbird. Also don't flash any tablet UI stuff until you have a working nook
Sent from my Barnes & Noble Nook HD+ using xda app-developers app
ridetheworld said:
I am running the 6/13 binary and the system gets stuck when I attempt a reboot. It freezes at the CyogenMod screen with the animation. I have attempted a reboot through powering off, and through the CWM, but I am still stuck. I was previously able to wipe the delvik cache, which worked, but all of the applications had to "optimize" every time before it booted up.
Is there a way to get past this?
I am running a 16GB Nook HD+ with an emmc install. It worked fine for a day, but now every time it boots it doesn't get past the CM animation.
Click to expand...
Click to collapse
I've had the same thing happen. I've completely reflashed my HD+, but occasionally it will still happen. Sometimes it does not ever boot correctly and instead when I reboot it, it reloads the Nook software (people say 8 times, but I counted and mine restore Nook software after 5 hard reboots).
If you have your SD card installed, try taking it out. That's what started mine...I put a 64GB card in and it never booted again. Just sits on the circle animation, spinning forever.
Thanks, I will try reflashing everything and see how that goes. I am going to back it up with Titanium First.
I installed the latest CM 10.2 (cm-10.2-20130827-NIGHTLY-ovation.zip) as well as the newest GApps. Everything seems to work fine until I install a few apps. Unfortunately I can't say if any of the apps could be causing the behavior which is as follows:
I've had this issue a couple of times already and, after becoming frustrated mostly due to the Nook only deciding to boot from the SD every once in about 30 retries, usually resulting in a revert to stock by default, I gave up and reverted to stock. Of course the taste of CM that I got was too sweet to give up completely. So, today I tried again and had the same problem. Seemingly it will work fine until you reboot after installing quite a few apps. I made sure to restart the tablet several times after installing it and everything went as planned. Whenever the play store had finished installing my swathe of apps, I decided to restart and this is when I was met, yet again, with the rotating CM boot animation.
It's quite annoying really, considering how fast it seems when I'm using it. I haven't got CM installed on the tablet's own recovery partition (if it has one -- I've not read up on these things) but have been running it from the SD. I don't know if that makes a difference. I've formatted all the pertinent partitions before starting the ROM for the first time. I delete the data/cache twice all-in-all, once before and once after. Dalvik too.
Basically I'm flummoxed.
Does it boot up after you clear cache?
I no longer saw this issue after unchecking wallpaper quick render under homescreen settings.
Sent from my BN NookHD+ using Tapatalk 4
realeze said:
Does it boot up after you clear cache?
I no longer saw this issue after unchecking wallpaper quick render under homescreen settings.
Sent from my BN NookHD+ using Tapatalk 4
Click to expand...
Click to collapse
I can't clear cache because I keep the recovery on the SD and it decides it doesn't want to boot from it nine times out of ten, even after following the newer instructions for formatting the SD. After a few failed reboots it just reverts to stock. If I flash CMW recovery to the Nook's recovery partition, will I still be able to revert to stock that way? As annoying as it is, it's nice to have that ability.
I'll try a new install today and avoid checking the wallpaper hack because that appears to cause a problem. I had flashed it yesterday and used it for quite a while, installed all my apps and restarted it many times without issue. After checking that I think I restarted and met the endless logo. Will report back later today.
I can confirm that when I leave the quick wallpaper render option unchecked, it does not lead to a catastrophic failure. Strange that I need to reformat the SD each time or it doesn't reliably boot from it. Either way, I've been using this install for a few days now without any unexpected issues.
Thanks for the advice.