Related
ok so weird problem here..
my NC is fine besides this one problem.
ive rooted with autonooter to 1.0.1
if i turn my NC completely off and leave it all night, when i wake up in the morning it gets stuck on the "touch of... " screen. The only way to get past this is to reboot to recovery and select reboot..
any idea why this happens? if i just restart the NC, or just let it go to sleep this doesnt happen, only when its been fully off for a couple hours.
ive tried reverting to stock/rerooted all that to fix it, but nothing seems to work.
i know i can just let it sleep and problem solved, but id like to know why this happens or if anyone experienced anything like this before.. thanks!
Try holding down the "n" button while turning on the unit...
Other wise you might have messed up your boot partition, go to development and search for samelhaff's thread on a flashable zip where you can fix the boot.
it reboots to recovery (power+n) just fine... just doesnt reboot normally (just pressing n) .. gets stuck on touch of.. screen
after getting into CWR and selecting reboot it then boots up correctly..
dont know why it just wont reboot normally to begin with.
Same problem here.
After some testing with HC and CM7 roms i recovered to the 1.0.1 Eclair rooted with autonooter version. I turn it off and on some times and everything worked allright. Left it all night off and when i turn it on in the morning i was stuck at the "Touch the future...".
I flashed the stock boot repartition and it started normaly.
Yesterday i flashed the custom Froyo 0.6.8 and everything was allright untill the morning when i stuck again athe " touch..." screen.
I booted with CW and rebooted normally.
Same thing has happened to me twice. I've only been able to get it to boot by booting from my bootable cwr and selecting restart.
Also been noticing some oddities with it charging fully, sometimes while plugged in the status is simply "not charging", not "charging" or "dischargin" and the N symbol on the end of the cable is yellow, not green.
Now it's even worst. Every time i try to boot i get stuck in the "Touch..." screen and i can only boot through CW recovery.
Any ideas?
Glad I finally found some people with the same problem
So initially I took my stock nook (1.0.1) and ran autonooter. Worked great but I noticed it would randomly reboot. Also , same as the other posters, if I powered it all the way down it liked to automatically power up and get stuck on the boot screen. Only way to reset was boot into CWR and select the reboot option from there. I loaded CM7 and same problems so i thought it may be some kind of hardware issue.
Reverted to stock, no problems.
Back to autonooter and this time ran dual boot from EMMC with stock as main partition and HC v4 on second partition. So i don't have CWR anymore but have my SD card handy in case I need it.
Well after a couple days of normal usage the random reboots are gone. Left the unit on during the whole time. Last night I turned it off to apply my Phamtomskin and this morning woke up to find it stuck on the boot screen. Must have been doing that for a while because when i stuck in the SD card for CWR it gave me the low battery warning. After 15 minutes it rebooted to CWR and i was able to reboot normal from there.
Hopefully since a couple of us got the problem we can find some sort of fix. I would like to know if it is some kind of hardware issue or as poster #2 suggested its a simple matter of flashing the boot file. Would I loose my dual boot partition if I flash this zip? Any help appreciated and thanks what a great XDA community.
I think that it has to do with CW and boot. Can i remove CW recovery without affecting my configuration?
no change.
im at least relieved that others have this same problem and it isnt a problem with only my NC.
last night i went back to stock, rerooted 1.0.1 and all that jazz and opted NOT to install CWR and power it down over night (thinking maybe clockwork was the problem) ...
well that didnt work b/c this morning it is stuck on the "touch of" screen and worse yet, i obviously cant even boot into recovery to just reboot.
looks like another revert/reroot this morning for me...
very frustrating.
bump this?
pilotbluemike said:
im at least relieved that others have this same problem and it isnt a problem with only my NC.
last night i went back to stock, rerooted 1.0.1 and all that jazz and opted NOT to install CWR and power it down over night (thinking maybe clockwork was the problem) ...
well that didnt work b/c this morning it is stuck on the "touch of" screen and worse yet, i obviously cant even boot into recovery to just reboot.
looks like another revert/reroot this morning for me...
very frustrating.
Click to expand...
Click to collapse
Just get the bootable cwr, then you'll always have it handy. The stuck at touch of reading screen has happened to me twice, pulled out my bootable cwr, selected restart and all was well.
I've never heard of anyone having this problem with V 1.0.1. I know that a lot of people are having this same problem with V1.1. Apparently CWR and V1.1 don't coexist well. I had this problem after doing Stock Nook 1.0.1 --> Autonooter 2.12.25 --> Sideload to rooted V1.1. Some people also have the problem when going from stock V1.1 and using Autonooter 3.0. The fix in both cases is to uninstall CWR using the CWR removal tool mentioned here:
androidtablets.net/forum/nook-color-technical/6386-how-installing-using-clockworkmod-rom-manager-nandroid-backup-custom-kernels-20.html#post48469
(sorry, I can't post links yet.) It leaves the device rooted. It worked for me.
Edit: Aaand somehow this ended up in the accessories forum. Can I get this moved to general? I don't even browse accessories. Sigh.
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.
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).
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.
Droid 4 running Stock Jb 4.1.2, Safestrap 3.11, Liquid smooth 2.9, CM (last stable)
Everything working fine for a number of months, installed Liquid smooth via -> delete romslot 3, create romslot 3, install Liquid 2.8.
It ran for a number of days no problems. Restarted fine, all features worked great, even the annoying random restart from 2.4 went away.
6 - 10 days in, im surfin' the news sites at work, put it down, screen goes black, i pick it up. Hit the power button cause i realize its off and it just boot loops... so bad i had to vol-/+ pwr, go to flash mode and THEN turn it off b/c it just kept trying to restart, hang on logo.
I got home and decided to AP flash the latest:
9.8.2O-72_VZW-18-2
Blur_Version.98.72.182.XT894.Verizon.en.US for the maserati.
Boot looped a few times, i was able to get it to go into recovery mode, after that it loaded up the stock JB system. First boot it crashed and restarted, second boot it loaded but only the keyboard worked, not the touch screen. Went to the in OS option of factory reset mode + delete storage.
Rebooted, worked. Checked it a few boots, everything is fine. I use Druid 4 Utility Xt894 JB version and apply the root. Works great. Install safestrap, Create new partition, install liquid smooth 2.9. Works for an afternoon... at work today the touch screen stops responding, i restart it a few times. I try to enter recovery mode. Now im in boot loop again...
I've tried re flashing it again, a few times. I tried even going down to the previous release of JB for the phone. STILL 4.1.2!!!! But nothing.... it just boot loops... what did i do wrong? It was running great. No tweaks or anything done to it prior to it having its melt down.
Help please.. ive provided as much information as possible and though i only joined XDA now to post for help, i have read it for a long time as my main source for my phone and have donated to both CM and Liquidsmooth teams previously..
help!!!
I can't see where you are doing anything wrong. You have obviously done your research and have a good idea of what you are doing. I see, after you fastbooted, you went back to Liquid. I think I would try running CM10.1 or even stock for a few days and see if you have the issue there as well. If you do than it sounds to me like it might be a hardware issue. If not, maybe try re-downloading Liquid. Perhaps your zip got corrupted somehow.
I would love too. In fact i would be willing to run it on the stock crappy 4.1.2 if i could get it out of boot loop this time...
It just keeps boot looping on the logo. AP Fashboot flash and BP flash work but recovery and normal boot/reboot mode just goes into M logo boot loop.
I've re downloaded the 4.1.2 jb SBFs from 2 different sources to ensure its not a corrupt file, tried 18_1 and 18_2 software versions...
Is there a way to use the abd shell to get into the filesystem and check whats going on? Is the SBF the last call? or is there another route to see whats going on or just flash EVERYTHING? Like completely back to stock?
I can find my way around a PC file system but im not familiar with linux. Please help me understand, Is it like having CMOS and BIOS settings or equivalent to damaged CMOS firmware? What am i not replacing/reverting by SBF and HOW can i replace/revert BEYOND the basic sbf...
If ya point me in a direction or to someone who can help me out i can do all the foot work just point me in the right direction?
Is this applicable? I found a site talking about using CWM in a ADB shell file push to possibly get access to more features?
The article also goes into reading the busybox / ADB command screen? (sorry for not proper jargin) and see what its doing during the boot loop before it restarts?
Id add the link but i need more posts....
Update: Flashed 18_2 again with a "factory cable" i made, let it boot loop a series of times before it started up into the stock system again.
At first, again the touch screen wouldn't work, random lockups and restarts, etc. Since i just got it into the main system again and i had to leave for the weekend for a trip(no wifi or network), i couldn't mess with it all weekend but i left it on the whole time and kept checking its functionality... gradually its come back to full function. Touch screen works and is accurate, no more lockups, no more restarting, even stopped boot looping when i restart and enter recovery..
Im not sure and i couldn't find any forum converstations or write ups to support to idea but i think after a major crash and you flash new or reflash your SBF, it seems the phone needs time to recalibrate and index? Not sure, but just an FYI. Gonna try loading SS and liquid again.