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+
Hello. As per instructed, I have search the threads, but haven't found anything like the problem I'm facing. Most can get to recovery or hand on the cyanogen loading. As such I am posting this query to see if anyone can help me.
I have been using Cyanogen 10.1 emmc on my new B&N HD+ tablet for about a week now, installed by following the guide found here. I made sure to make back up at every step; before flashing Cyrogen, and after. Anyways Yesterday, the tablet refuses to boot. I can press the power button, the Nook hd+ and connect it using usb, but the screen remains blank (black). It never gets to the nook screen or the cyanogen loading screen. I have tried to restore a backup, but no matter what I do, I can't get the nook to boot into recovery mode. I have tried 3 different boot sd, but none bring up the loader, not even the one that work when I first installed Cyanogen.
I have drained the battery completely and recharge it about 2 times now and I have held down the N + Power methods. I installed TWRP as a replacement over stock recovery mode. Any help would be appreciated.
23Exploreus23 said:
I installed TWRP as a replacement over stock recovery mode. Any help would be appreciated.
Click to expand...
Click to collapse
Kind of out of my league, but search this thread - http://forum.xda-developers.com/showthread.php?t=2317500 for twrp. Reports of problems with backup/restore using twrp. Maybe try a bootable cwm card
I have a Nook HD+
So, I was having some issues with CWM so I decided to switch to TWRP.
Not sure if that caused the issue, but suddenly booting into recovery is a pain in my rear.
I got it to do it once again to flash a different rom, but now I cant really seem to get the shortcut to recovery to work?
And I dont have access to the app store because I forgot to flash the gapps apk so I cant get an app from there to send it to recovery.
Does anyone have any recommendations? I am gonna keep fiddling and see if I can get it to finally go into recovery.
RealEmotionX said:
I have a Nook HD+
So, I was having some issues with CWM so I decided to switch to TWRP.
Not sure if that caused the issue, but suddenly booting into recovery is a pain in my rear.
I got it to do it once again to flash a different rom, but now I cant really seem to get the shortcut to recovery to work?
And I dont have access to the app store because I forgot to flash the gapps apk so I cant get an app from there to send it to recovery.
Does anyone have any recommendations? I am gonna keep fiddling and see if I can get it to finally go into recovery.
Click to expand...
Click to collapse
The problem with switching recoveries should only be the correct recovery to the correct rom. Otherwise, going from cwm to twrp shouldn't do any harm.
What is a shortcut to recovery? <- Is this the recovery item on the power menu? Or holding down power + home?
If you have access to a browser you can just download gapps. There's no need to use an app.
If you have access to a pc, just make a bootable sdcard with recovery on it + gapps + rom and then you can't go wrong - though some people could still find a way. lol
I always do.
I dont have a microSD card reader on anything but this tablet and was under the impression I couldnt make a bootable card from the media browser.
The shortcut to recovery I had used before was from the TWRP manager app.
You can get the "Reboot to Recovery" option on the power button's menu by enabling Settings->Buttons->Power Button->Reboot Menu and Settings->Dev.-Options->Advanced Reboot Menu.
Oh wow, never knew that.
Problem solved. Thanks a bunch
Hi i recently installed xposed on my acer A-480FHD rooted tablet kitkat 4.4.4. The reason i installed xposed was for the app greenify. As i scrolled thru the settings for it i noticed it said "On some devices this may cause them to enter a boot loop" and something else i dont remember. I installed assuming i was not part of that list. When i installed it it told me that xposed would be running next time i boot up. After a few hours i decided to reboot it. Because why not. I rebooted it using chain fires app live boot and used its reboot option. Then i went into boot loop. If you need any more info i have some screen shots of my tablets details. Can you help me get my device out of boot loop? I am fine if you wanna debug my tablet live.
Should be easy
victolabs said:
Hi i recently installed xposed on my acer A-480FHD rooted tablet kitkat 4.4.4. The reason i installed xposed was for the app greenify. As i scrolled thru the settings for it i noticed it said "On some devices this may cause them to enter a boot loop" and something else i dont remember. I installed assuming i was not part of that list. When i installed it it told me that xposed would be running next time i boot up. After a few hours i decided to reboot it. Because why not. I rebooted it using chain fires app live boot and used its reboot option. Then i went into boot loop. If you need any more info i have some screen shots of my tablets details. Can you help me get my device out of boot loop? I am fine if you wanna debug my tablet live.
Click to expand...
Click to collapse
I think Xposed creates a rescue zip onto your SD card called Xposed-Disabler-CWM.zip
Try flashing that if you have a custom recovery. If you don't have a custom recovery or this doesn't fix it try reflashing the stock rom.
victolabs said:
Hi i recently installed xposed on my acer A-480FHD rooted tablet kitkat 4.4.4. The reason i installed xposed was for the app greenify. As i scrolled thru the settings for it i noticed it said "On some devices this may cause them to enter a boot loop" and something else i dont remember. I installed assuming i was not part of that list. When i installed it it told me that xposed would be running next time i boot up. After a few hours i decided to reboot it. Because why not. I rebooted it using chain fires app live boot and used its reboot option. Then i went into boot loop. If you need any more info i have some screen shots of my tablets details. Can you help me get my device out of boot loop? I am fine if you wanna debug my tablet live.
Click to expand...
Click to collapse
Whoa, an actual normal question about xposed. First time in a while.
You should be able to just reflash your rom
janekmuric said:
I think Xposed creates a rescue zip onto your SD card called Xposed-Disabler-CWM.zip
Try flashing that if you have a custom recovery. If you don't have a custom recovery or this doesn't fix it try reflashing the stock rom.
Click to expand...
Click to collapse
ldeveraux said:
Whoa, an actual normal question about xposed. First time in a while.
You should be able to just reflash your rom
Click to expand...
Click to collapse
victolabs said:
Hi i recently installed xposed on my acer A-480FHD rooted tablet kitkat 4.4.4. The reason i installed xposed was for the app greenify. As i scrolled thru the settings for it i noticed it said "On some devices this may cause them to enter a boot loop" and something else i dont remember. I installed assuming i was not part of that list. When i installed it it told me that xposed would be running next time i boot up. After a few hours i decided to reboot it. Because why not. I rebooted it using chain fires app live boot and used its reboot option. Then i went into boot loop. If you need any more info i have some screen shots of my tablets details. Can you help me get my device out of boot loop? I am fine if you wanna debug my tablet live.
Click to expand...
Click to collapse
Thanks for the help. None of those methods worked for me doe. As of this comment im reinstalling root now. But if others get in the same problem as i did i wont leave them in the dust. Here is what i did to fix my boot loop on my acer icona 8 A-840FHD.
First you wanna boot into stock recovery NOT CWM recovery. How i got into it was by holding the Power and volume up button at the same time. (assuming if your device is off) Then i was booted into recovery. If you are booted into fastboot then navigate to the "RECOVERY" Option using the volume keys and select it using the power button. The device will reboot into the appropriate menu. Then choose the option to WIPE your device, Factory reset Ect. After wipe is done reboot your tablet. Go thru the setup screen and proceed uninstall root using super su root manager. After that reboot tablet and update tablet to the latest ver. Then proceed to re-root tablet like you did the first time. And remember to not make the same mistake like last time. This is the guide i used to root my tablet.
http://forum.xda-developers.com/android/development/guide-root-acer-iconia-tab-8-a1-840fhd-t2933317
Guide 2.
Thanks! Victolabs
So I dug my old Nook HD+ out of storage and got it charged and booting just fine. It's running some old nightly build of CM13, but it insanely laggy and hard to use, like 10+ seconds just to open settings slow. As such, I want to flash a more recent rom, probably a Nougat based one. However I remember there were some oddities to this device, but I can't recall for sure what they were, and new guides seem to be for setting up from stock. So I just want to make sure I don't brick my device. Can anyone provide some guidance on what to do? Below is the situation
Nook HD+ running buggy CM13, refuses to boot into recovery, tried using home or volume up key and power button to no avail. I don't remember if I just used SD bootable recoveries before or not, I don't think I did, but at one point I think that was the only option.
I'm guessing I need to wipe my SD card and make it a bootable recovery. Can I just flash a recovery to EMMC from there and then flash a new rom? Is it possible my device needed some other steps to allow custom recovery on the emmc or something?
Also why do some guides say to hold the home button "n" key and power to boot into recovery and some say volume up and power? Is there not a universal standard way to boot into recovery for this device?
Sorry if I sound like a total noob, but I haven't done any custom romming or rooting in forever and don't even know if this device ever got an unlocked bootloader or if we just have some weird workaround for it to make things work, but I'd like to find a quick and easy way to get it working after work today if possible. Thanks for all your time and help and any recommendations.