Related
I flash my NC with CM7.0, now everything seems working fine, but I found there are sometime(not always) it stuck at boot animation, after touch the future of reading, it just stuck there.
this happens alot when I turn it off for long time, I am not sure what is the problem seems it doesn't happen every time.
I am having the same problem, but noticed that if i take the SD card out the NC starts normally. so i am figuring somthing is left on there from the install that is causing the hang up.... or maybe it is something else and i am too naive to realize what it is. Any help would be appreciated.
Using CM7.0 stable.
I tried to install CM7 on my nook color and i didnt follow the proper method and instead saved the CM7 file to the root of my sd card and installed the zip through clockworkrecovery without wiping or cache and now im stuck at the android boot screen. It isnt the CM7 skateboard android boot but rather the plain android root boot screen. If anyone could help it would be helpful thank you! IM crying right now about it
ikryptic said:
I tried to install CM7 on my nook color and i didnt follow the proper method and instead saved the CM7 file to the root of my sd card and installed the zip through clockworkrecovery without wiping or cache and now im stuck at the android boot screen. It isnt the CM7 skateboard android boot but rather the plain android root boot screen. If anyone could help it would be helpful thank you! IM crying right now about it
Click to expand...
Click to collapse
Hold power+n for 10 seconds to turn off
Clockwork bootable sd card, wipe system/data/cache (not boot), install cm7 from zip, install gapps from zip.
This is for a clean fresh install.
I made the same mistake yesterday going from stock nook to cm7 on nook #3 (so used to flashing nightlies on the other 2 i forgot to wipe system first)
Hello everyone,
I just hardbricked my SGS+ and now I'm a bit curious how this could happen.
This is what I did:
I used to run CM9 RC5 from arco68 along with the Kernel for ICS from Christopher83 and CWM 6.0.1.2.
Because my phone always lost the wifi-connection and also had some freezes I decided to try out CM10 Beta 3 from ivendor.
I backuped my phone, downloaded the zips and even verified the MD5sums. Next I flashed CWM 6.0.1.9 as recommended in the thread from ivendor.
After exporting the nandroid backup and other stuff like photos to my computer I wiped everything as mentioned in the thread, flashed the two zips and rebooted. Everything went fine and I was almost ready with setting up my phone again when I got my first softreboot.
Suddenly it showed the CM-bootlogo and after maybe 10 seconds I was back on my homescreen. I got another two or three softreboots until I decided to flash the Kernel 3.x from CastagnaIT.
I rebooted into recovery, wiped cache and dalvik cache, flashed the zip and rebooted.
Now I wanted to reboot into recovery again to fix permissions but instead I got a softreboot and my phone stuck at the CM10 bootlogo.
I waited for around 5 minutes and then I just turned the phone off and booted into the recovery mode.
Because I wanted a clean install without any problems like softreboots I decided to wipe my phone again (data, cache, system) and just reflash the zip for CM10. And at this point everything went wrong.
I flashed CM10 but when I tried to flash gapps my phone just turned off. And no, the battery was not empty. In fact the battery was at around 50-60% and my phone was also connected to my computer.
I tried to turn on my phone but now it stuck at the Samsung bootlogo.
The next thing I did was probably a horrible mistake. I tried to un-brick my phone but I did not realize that I could boot into download mode without problems so I guess my phone wasn't softbricked at all.
Well, after that I still stuck at the Samsung bootlogo and couldn't enter recovery mode. I got into download mode somehow and maybe this was my second mistake. I tried to flash the "i9001Reset.zip" via Odin. Everything went fine but when Odin said "Close serial port and wait until rebooting" my phone was completely dead. I think it was while I tried to flash the reset-file when I got a message like "MBR: read failed". So somehow I managed to destroy my master boot record.
Now I can't turn on my phone or enter download nor recovery mode. I already removed the battery for about 45 minutes but this didn't work either.
My phone is dead but at least I saved the important data and maybe I'll get a new one through warranty. Or I just buy a Nexus 4.
My questions are:
What did I do wrong especially when I tried to save my phone?
How can I prevent such things from happening?
And at which point I should have got help here in the forum or elsewhere?
I would really appreciate some tips for the future because I already flashed and used a lot of different ROMs but this is the first time something really went wrong.
Thanks for reading and thanks for your help in advance.
(Please excuse my non-perfect englisch.)
Greetings,
Mangoniter
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.
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 all
First of all, I'd like to say that I've spent a lot of time searching through XDA and other websites on the internet, and so far I didn't find a solution to my problem, and that's why I'm creating this new thread.
I have a Galaxy Ace S5830B and just flashed Mardon's version of CM10.1.6 ROM in it, following every single step on his guide, using CWM 5.0.2.6.
I made sure that before flashing the new ROM I wiped the whole thing, clearing cache, dalvik cache, formatting /system and doing the factory reset.
I did not manually flash any kernel.
Everything runs smoothly and ok, just like all compliments the ROM gets on his topic, except for when I have to shut the phone down.
Once it is shut down and I'm powering it back on it gets into a boot loop that won't go past the Samsung logo. It means that the Samsung logo goes on, fades off and then it loops back to it, and the Cyanogenmod blue circle loading animation never comes.
It only works when I get back into CWM and hit "reboot system now" . Then it reboots normally.
I'd just like it to act normally, booting normally straight from a powered off state without having to go through CWM everytime I need to switch the phone on. That's because it's my father's phone, and having him getting into CWM every now and then after a battery run off is too risky, you know what I mean.
Any help will be very very much appreciated.
Thank you
Riggs
Sent from my GT-i9300. Forgive some misspelling here and there.
offRiggs said:
Hello all
First of all, I'd like to say that I've spent a lot of time searching through XDA and other websites on the internet, and so far I didn't find a solution to my problem, and that's why I'm creating this new thread.
I have a Galaxy Ace S5830B and just flashed Mardon's version of CM10.1.6 ROM in it, following every single step on his guide, using CWM 5.0.2.6.
I made sure that before flashing the new ROM I wiped the whole thing, clearing cache, dalvik cache, formatting /system and doing the factory reset.
I did not manually flash any kernel.
Everything runs smoothly and ok, just like all compliments the ROM gets on his topic, except for when I have to shut the phone down.
Once it is shut down and I'm powering it back on it gets into a boot loop that won't go past the Samsung logo. It means that the Samsung logo goes on, fades off and then it loops back to it, and the Cyanogenmod blue circle loading animation never comes.
It only works when I get back into CWM and hit "reboot system now" . Then it reboots normally.
I'd just like it to act normally, booting normally straight from a powered off state without having to go through CWM everytime I need to switch the phone on. That's because it's my father's phone, and having him getting into CWM every now and then after a battery run off is too risky, you know what I mean.
Any help will be very very much appreciated.
Thank you
Riggs
Sent from my GT-i9300. Forgive some misspelling here and there.
Click to expand...
Click to collapse
Try doing a factory reset, it might solve it. Do post the result. Hope I Helped
Already did it, also wiping cache and dalvik cache. No solution.
But thank you anyways =)
Sent from my GT-i9300. Forgive some misspelling here and there.
I also noticed this problem on my Ace S5830 and I have no idea why. I thought I was the only one who is having this problem. If anyone knows why, please tell.
Sent from my GT-S5830 using Tapatalk
offRiggs said:
Already did it, also wiping cache and dalvik cache. No solution.
But thank you anyways =)
Sent from my GT-i9300. Forgive some misspelling here and there.
Click to expand...
Click to collapse
When you are using CM10.1 by Mardon, NEVER WIPE DATA/FACTORY RESET!! ...You should fix your problem flashing again the rom
The ROMs are already preconfigured and when you wipe data/factory reset, all those settings will be lost and the device won't be able to boot successfully again
Oh, nice to know that! I'll try it soon, then I'll post the results.
Sent from my GT-i9300. Forgive some misspelling here and there.
offRiggs said:
Oh, nice to know that! I'll try it soon, then I'll post the results.
Sent from my GT-i9300. Forgive some misspelling here and there.
Click to expand...
Click to collapse
Ok, so just follow the correct steps to re-flash CM10.1