[Q] random reboot - Nook Color General

I have my NC overclocked to 950mhz vie "shes a screamer" Kernel and all of the sudden my nook reset itself completly. anyone experience the samething?
auto-nooted btw
EDIT: what i meant is it was running fine for over 24hours but suddenly it rebooted and i lost everrything and am stuck at the "welcome to LogicPD Zoom2" screen and i cant do anything. im not sure if i have CWM still installed because i cant get into recovery... any advice on what i should do

rumitg2 said:
I have my NC overclocked to 950mhz vie "shes a screamer" Kernel and all of the sudden my nook reset itself completly. anyone experience the samething?
auto-nooted btw
Click to expand...
Click to collapse
Running an overclocked kernel and the device rebooted? SHOCKER!

what i meant is it was running fine for over 24hours but suddenly it rebooted and i lost everrything and am stuck at the "welcome to LogicPD Zoom2" screen and i cant do anything. im not sure if i have CWM still installed because i cant get into recovery... any advice on what i should do

Related

Nook wont boot normally after being off all night..

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.

newly installed CM9 keeps rebooting

installed CWM and CM9 per the wiki on rootzwiki
everything seemed to install just fine, however the tablet keeps rebooting upon trying to boot into cyanogen. it goes to the loading screen then reboots shortly after. anyone have any idea as to why this is occurring?
knox07 said:
installed CWM and CM9 per the wiki on rootzwiki
everything seemed to install just fine, however the tablet keeps rebooting upon trying to boot into cyanogen. it goes to the loading screen then reboots shortly after. anyone have any idea as to why this is occurring?
Click to expand...
Click to collapse
Not sure but did you wipe the cache and the davlik cache? I'd try that first. Might want to try re-downloading the zip and reinstalling if that doesn't work.
At various times I get events:
Seems when charging cable is removed it settles down and behaves better..
When selecting the reboot it shuts down.
When shut down it reboots.
North do I get battery charging symbol when off.
knox07 said:
installed CWM and CM9 per the wiki on rootzwiki
everything seemed to install just fine, however the tablet keeps rebooting upon trying to boot into cyanogen. it goes to the loading screen then reboots shortly after. anyone have any idea as to why this is occurring?
Click to expand...
Click to collapse
Had the same issue. You need to install it with ACMEInstaller2 instead of the old one. Had to install and uninstall it 2 times before figuring that out.
If you came from cm7 also be sure to clear out the old kernel. Apparently the touchpad can have two kernels on it, which messes things up.
Sent from my android touchpad.
galaxy w with cm9 keeps restarting
hi guys sorry to bother but i recently flashed my galaxy w from http://forum.xda-developers.com/showthread.php?t=1576874 with cm9. it was wonderful at first but recently my phone just keeps restarting. i cant even use the phone. pls help!!!
junlongt said:
hi guys sorry to bother but i recently flashed my galaxy w from http://forum.xda-developers.com/showthread.php?t=1576874 with cm9. it was wonderful at first but recently my phone just keeps restarting. i cant even use the phone. pls help!!!
Click to expand...
Click to collapse
This is the HP Touchpad forum. You'd be better off asking in the Galaxy W forum.
http://forum.xda-developers.com/forumdisplay.php?f=1474

[Q] Nook Color Looping Flash

Ok guys heres the deal, i have been trying to reflash NC stock and to no avail i get the same issue everytime no matter what version i use, i have even tried ADB, and that does not work.
Ok my problem is this everytime i try to boot it it just loops at the barnes and noble nook color screen forever. When i tried ADB my computer would not even find the device but it found 2 which when i tried to uninstall them they install right after so i cannot use ADB(and yes i turned off automatic driver install). So here is where i land and my question. Do i have a 300 dollar paper weight or is their hope, and if so please explain what i am doing wrong. Thank you for your time
First off...
are you trying to flash the stock B&N?
how are you trying to flash it?
do you have CWM or TWRP on eMMC or stock recovery?
if you're trying to use cwm or twrp to flash stock rom... see the customizing rom thread in my signature for modifications required.
ok i am trying to flash to the stock bn, i am using cwm, but when i do that it just loops through, and adb now does not even recognize the device so i can tie them together so to speak.
Ok, i did everything that forum on your sig told me to do got it installed but it still loops at the "barnes and noble Nook Color" flash screen. Any Ideas?
Now that you have stock on the nook color... do the 8 failed boots to cause it to erase data and deregister the device... it should bring it back to factory and resolve the boot loop issue
Finally! thank you so much for your help been working on this issue for 3 or 4 months now, it works just need to get it charged and hopefully it will take a charge.

hd plus HELP!

so i understand im a complete noob without a post or anything
but i made an account just so i can possibly get help because im in way over my head..
i rooted my nook hd plus with cwm recovery and for about a week everything was working perfect then the other day i downloaded an app from the play store (directv app) and boom it reboots and wont reboot fully it gets stuck on the recovery page the spinning wheel with the logo
i ened up trying to restore it back to the stock non rooted nook but it WONT MOUNT DATA or EMMC
im so worried i really messed it up
im not worried about losing info cuz ive used titanium back up
so what do i do?! lol
Just to make sure I understand what you did, when you say rooted with CWM, do you mean you rooted stock with my universal root zip, or do you mean you installed a version of CM to replace stock. When you say spinning logo, that sounds like CM.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Just to make sure I understand what you did, when you say rooted with CWM, do you mean you rooted stock with my universal root zip, or do you mean you installed a version of CM to replace stock. When you say spinning logo, that sounds like CM.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
so luckly I was able to get it to fix itself some how...
what i did was restore it to factory even tho i know it would be able to mount data then i took out the card rebooted and let it bootloop till it finally went back to virgin nook then i put the sd card back in
when thru the normal back up again wipe data/ factory settings then install from sd card took it out mae it reboot and BAM!! i got my baby back
lmao

Bricked Nook HD+

Hi guys, I have bricked my nook hd+ and I hope to get some advice, thank you.
I had the problem where i was only able to boot to cwm recovery, I managed to solve it by using a stock backup, combined with flashing a 2.1 stock rooted rom as i had problems recovering the data partition.
After I did all that(I should have really stopped when I got it working) I tried to install cwm recovery by using the bootable sd card as i lost my custom recovery for some reason. However, I was not able to after rebooting 20+ times. I previously bought two nooks, my other nook had no problems but this particular device had to be rebooted 20-30 times before it worked the other time. Being the genius I am, I then tried to flash recovery using various apps since I still had root..one of the programs flashed and restarted my nook hd+ and I can only boot to the "nook" screen now. Holding power and the n button only restarts the tablet.
I guess my only way out is if i could somehow get adb to work? I know its a long shot but I have been trying for the past 1 hour and have not been able to do anything. My computer manages to recognize the tablet as "Blaze_Tablet" and i am unable to change the drivers. Anyway i was hoping if someone could give me an idea of what i could do or if i should give up on the device as it is unrecoverable. I would appreciate any response at all, thank you good people of xda!
I somehow managed to get fastboot working and flashed custom recovery and managed to restore from backup of stock :victory:

Categories

Resources