Can anyone give me a hand with this?
I was running CM7 n40 with ALSA and dalingrin's 0413a kernel. Watching videos in vevo when the nook froze and reset itself and got stuck looping at the CM7 animation.
I've rebooted into CWR, tried first wiping Dalvik cache, it didn't seem to make a difference. I then tried formatting /cache and reinstalling n40 and dalingrin's 0404 kernel. No joy either.
Short of reinstalling everything, is there anything else I can try?
If you are running from an SD card then your problem is likely the card. If you aren't running from an SD card then... Maybe someone else can help you.
Forgot to add, running from eMMC.
I had the same thing, only with CM stable...ended up having to rebuild my / boot with the file here.... http://forum.xda-developers.com/showthread.php?t=914690.
Very last file in first post. Had to flash it then start all over....
Sent from my NookColor using XDA Premium App
You are not alone, mine just did this after updating to the latest nightly and restoring with Titanium Backup. I did not flash a kernel, just the nightly using Rom Manager.
My symptoms were that it seemed to run OK, then I opened the gallery to set a different wallpaper and got constant FCs, so then I restarted. Now I'm watching the circle go round and round.
OK, back to previous, just restored the nandroid backup Rom Manager made prior to the update. Seems to be working fine.
I flashed n40 and dalingrin's oc kernel 0404. Stable and happy as can be.
I'm thinking the issue was with ALSA and experimental kernel 0413a, which has been reported to crash video playback in some cases. Don't know how or why it would corrupt my install though.
Let me just mention a lot of people are claiming false boot loops lately. Sometimes it just takes a long time to reboot, especially after it froze. I've had it take up to 20mins before with the little skateboard android.
So next time unless it's giving you "Touch The Future" and then the CWM treatment, give it a bit to load and see if it does after 10 mins or so. (Usually just after the screen dims, my nook loads up just fine)
No that's unacceptable. Considering the amount of data it should be loading, something is very wrong with your nook if it takes more than 5 minutes to boot.
And yes it was boot looping, the animation restarted itself repeatedly (wasn't just the arrow spinning).
Can't help at all but to offer another data point: I was on nightly 39, ALSA update, and kernel 0413a. Was flicking between homescreens when it locked up, forcing a hard shutdown. When I booted back up, it was stuck in a bootloop. Tried all the usual paths to recovery, but had to resort to a backup.
Moved on to n41 (ALSA included) and kernel 0418c. Stable in every case so far.
I'm having same issue and mine is still not working no matter what I did.
I even tried to restore it back to stock - Format/ Fdisk / DD / etc... tried everything I could find. I even had my back up but couldn't restore. I think I created more problem while I was trying to fix it.
Now I can only boot from SD. So I was not the only one.
Eww, I would never touch any sort of partition change with eMMC installs. Usually I just go back to stock or latest backup. Found out there may be an issue with backups created from CWR flashed to eMMC (MD5 check failure). SO anyone who's made a backp from that, do yourself a favor and boot off a CWR SD and do a backup onto that just to be safe.
Sorry about your troubles, hope you get it sorted. Guess I got away easy with just format and nightly re-flash.
Related
OK i got a nook, rooted using AN3.0 (it is 1.1.0) and then put cm7 Tab tweaks on the eMMC using cwm and flashed GAPPS and The latest OC kernel with I/O fix. my nook runs GREAT!
however a buddy of mine liked what he saw so he went out and got one, we used AN3 to root it, then flashed cm7TT, gapps, and the kernel and his acts funny. on the first boot after the flash we got an error saying something like "bad install, please contact B&N" so i powered down, back up, and it worked. Funny thing is when we boot it still has the nook splash screen "harness the power of reading" or whatever it says. also he frequently gets boot loops and it just runs really buggy. we tried re downloading the ROM and re-flashing (with the stock cm7 kernel this time) and have the same issues. also i can OC mine to 1190 easy, if he does anything over 1000 he gets freezes and boot loops....any ideas...the weirdest part is the "enjoy the power of reading" splash screen.....help?
Sounds like something didn't get cleaned up. So if I were you, I would get CWM on a sd card, then I would get the stock 1.1.0 image and reflash it. Don't nooter or anything like that, there's no point.
Then I would wipe the following... /system, /data, /cache and dalvik cache. Then after all that is done, go ahead and reflash the newest nightly (it has the tablet tweaks), also you're running Madkat's OC, grab the newest Daligrin one as it's more stable and may work better with his nook.
I recently returned to stock 1.2 with the default recovery flashed (CWM SD card), and then I upgraded to 1.3, and then rooted with the ManualNooter 4.5.18 and 4.6.16 (or whatever their numbers are, I followed the instructions to the T).
It worked fine and I installed everything i needed from the market/titanium backup/etc but the second time I reboot the device it is stuck in a boot loop. The splash screen slowly writes out the word "Nook Color" and it will complete this once, but the second time it does this, it reaches the L in Color it stops and starts over. It will do this for hours.
I wiped it and started fresh over, reinstalling 1.2, re-updating to 1.3, re-nootering (sounds dirty...) all over again, re-installing all my apps all over again (took forever) and yet it still does this. As soon as I rebooted it, this began again
I'm a longtime lurker with a rooted and much-abused DInc, I've had PhireMod, CM7 (without the sleep of death) and Honeycomb on my Nook all without issues (that I couldn't fix). But this has me completely flummox'd. What makes this harder to deal with is that my Nook will not recognize my home Wi-Fi so I have to do all my work on it during my lunchbreak (another issue entirely; unrelated, home wifi is a software solution)
Any Ideas? I haven't yet had the chance to flash the better kernel, because when I reboot it's stuck in this loop. I tried re-nootering and that did not help.
Same with me. Happened 3 times to me last night. I'm still figuring out what i can do to make stock 1.3 + OC + rooted to work.
I'm trying to determine what I did in those 3 times in common. Only thing i can think of i did in all those 3 times was OC +format SD card and installed titanium backup from market.
I'm sure its not a new issue because I remember this happening to me a month ago then I gave up and just went back to miui.
I had the same problem. Look for post about adobe flash causing boot loops. I solved the issue by:
1: after installing 4.6.16, I signed into the marked, downloaded titanium backup
2: used TB to delete the copy of abode flash and adobe air.
3: restarted the nook and had no boot looping.
4: I searched and found a copy of the current adobe flash and sideloaded it using CWM.
It's been 3 day and no boot looping.
Regards
I also had the boot loop issue. It was caused because I updated my flash. Check out this thread....it fixed my issue.
http://forum.xda-developers.com/showthread.php?t=1208896&highlight=boot+loop
Thanks, Johnny. You've saved me a lot of trouble.
No problem! Happy to help! Thankfully GMPOWER threw together that zip file for everyone!!
Be careful when you install any 3rd party keyboards to /system, it also resulted in boot loops for me with a few of them
joej said:
Be careful when you install any 3rd party keyboards to /system, it also resulted in boot loops for me with a few of them
Click to expand...
Click to collapse
Was thumb kb one of them?
dohturdima said:
Was thumb kb one of them?
Click to expand...
Click to collapse
I have had no issues with Thumb keyboard (either after initial install or updates).
Before I screw anything up any further I figured it's time to ask.
I'm using Odin and I flashed ICS(ICS_4.0.3_MR1-RC4.2_Captivate.zip) awhile back and everything had been running fine for a couple months now.
I noticed longer load times during loading animation when powered up(Figured it was just 'cause of more start up apps) eventually it stuck looping @ animation screen. Out of frustration I was hitting the lock key while loading up and somehow managed to stop the animation loop and lock the screen which enabled me to use the phone again for the day until my phone was turned off by accident
In my attempts to resolve this issue, I tried clearing all cache's(Delvik,Partition etc.) and reflashing the rom to no avail.
I figured if I formated /boot and than reinstalled it might work, *BIG* Mistake. I could only access download mode so I couldn't reinstall /boot
I reflashed using the speed kernel to get back recovery mode and than flashed my ICS.zip again only to be still stuck with this boot loop issue. I've found the topic http://forum.xda-developers.com/showthread.php?t=731989 as a last resort.
How can I recover from boot loop without losing my data? Thanks.
3randon said:
Before I screw anything up any further I figured it's time to ask.
I'm using Odin and I flashed ICS(ICS_4.0.3_MR1-RC4.2_Captivate.zip) awhile back and everything had been running fine for a couple months now.
I noticed longer load times during loading animation when powered up(Figured it was just 'cause of more start up apps) eventually it stuck looping @ animation screen. Out of frustration I was hitting the lock key while loading up and somehow managed to stop the animation loop and lock the screen which enabled me to use the phone again for the day until my phone was turned off by accident
In my attempts to resolve this issue, I tried clearing all cache's(Delvik,Partition etc.) and reflashing the rom to no avail.
I figured if I formated /boot and than reinstalled it might work, *BIG* Mistake. I could only access download mode so I couldn't reinstall /boot
I reflashed using the speed kernel to get back recovery mode and than flashed my ICS.zip again only to be still stuck with this boot loop issue. I've found the topic http://forum.xda-developers.com/showthread.php?t=731989 as a last resort.
How can I recover from boot loop without losing my data? Thanks.
Click to expand...
Click to collapse
First off what do you mean by data? Do you mean your photos and music that is stored on the internal or external SD or do you mean the apps you've installed and any data or settings related to them or your current setup? If you're talking music and pictures, with the exception of rare cases your internal and external SDs should never be effected by a basic flash but the link you provided suggests that it will wipe everything if you use the master clear option. If mean the other "data" I mentioned theres no way around that short of a backup prior to a flash.
Now as far as the link you posted I've never used it so I don't know if it would help. However I would suggest this... http://forum.xda-developers.com/showthread.php?t=1300843 go to the third post and use the KK4 one-click without bootloaders. That should hopefully fix your situation and again unless something weird happens it won't touch your photos and whatnot.
On a side note have you attempted getting back into recovery from the bootloop, rewiping the usual, and flashing the rom again? Sometimes that corrects problems.
m1batt1 said:
First off what do you mean by data? Do you mean your photos and music that is stored on the internal or external SD or do you mean the apps you've installed and any data or settings related to them or your current setup? If you're talking music and pictures, with the exception of rare cases your internal and external SDs should never be effected by a basic flash but the link you provided suggests that it will wipe everything if you use the master clear option. If mean the other "data" I mentioned theres no way around that short of a backup prior to a flash.
Now as far as the link you posted I've never used it so I don't know if it would help. However I would suggest this... http://forum.xda-developers.com/showthread.php?t=1300843 go to the third post and use the KK4 one-click without bootloaders. That should hopefully fix your situation and again unless something weird happens it won't touch your photos and whatnot.
On a side note have you attempted getting back into recovery from the bootloop, rewiping the usual, and flashing the rom again? Sometimes that corrects problems.
Click to expand...
Click to collapse
I should be more specific when refering to data, I need my text message, pictures and videos everything else is synced online. I'm looking into the link you've suyggested now and I have tried wiping the caches(delvik,partition) and reflashing the rom to no avail.
I've looked @ the kernels you've suggested and looks good except I'm not sure what it means by wipe(What will it wipe?) and why not the one with the bootloaders since I'm having bootloop issues?
Thanks
3randon said:
I should be more specific when refering to data, I need my text message, pictures and videos everything else is synced online. I'm looking into the link you've suyggested now and I have tried wiping the caches(delvik,partition) and reflashing the rom to no avail.
I've looked @ the kernels you've suggested and looks good except I'm not sure what it means by wipe(What will it wipe?) and why not the one with the bootloaders since I'm having bootloop issues?
Thanks
Click to expand...
Click to collapse
Pictures and videos shouldn't be touched but unless you've backed up your messages they will be.
As far as what I linked they aren't kernels they are complete stock ROMs built into a one-click program to take you back to stock. It will wipe and repartition the internal memory that the ROM is installed on. It shouldn't touch your storage memory though.
As far as not using the one with boot loaders, you could but you already have the boot loaders installed if you're on ICS and reflashing boot loaders can potentially hard brick your device. Also flashing ROMs don't touch the boot loaders so they should be intact and using the one-click without boot loaders is the safer choice.
Sent from my SGH-i927 using xda app-developers app
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 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.