Related
A couple weeks ago I bought a Nook Color on ebay. The first thing I did was turn it on and let it fully charge overnight. I noticed that it was in normal condition, but didn't bother going past the intro screen since an off the shelf Nook Color was not what I was interested in anyway.
The next day I flashed phiremod 6.2 on it with no problems (I have done this process successfully to two other Nook Color's by the way). I am able to connect to my wifi, setup my google account, and open the market. Life is good so far. Then I notice in ROM Manager that there is a phiremod 6.3 version out. I try to download phiremod 6.3 from ROM Manager for an entire day with no luck. The download just kept stalling on me. No problem I'll just download phiremod 6.3 onto my sdcard and flash it through clockwork recovery as normal (performing a full wipe first of course).
Then boot loop for no reason I can tell. Just a boot loop at "Touch the future of reading" with no way to get into recovery without restarting it with the sdcard.
So I put the sdcard back in and wipe and reflash phiremod 6.3 with the same results. Then I wipe and reflash phiremod 6.2...boot loop again. I repeat this process until my eyes start to bleed.
At this point I'm thinking, "There's no reason this should be happening. I wish I could just go back in time and start over." That's when I find this link: http://forum.xda-developers.com/showthread.php?t=914690
Ok, I'll just restore everything back to stock. No clockwork, no phiremod, just Barnes and Noble software just like the day it was born. So I go down the road of restoring the device to stock and instead of bootlooping at "Touch the future of Reading" it bootloops at the "N" screen. I'm running out of ideas so I perform the 8x method, get the OTA install, and still bootlooping at the "N" screen. Oh yeah, and "power + n" wont take it into recovery of any kind.
Now that it seems that I've failed to restore the device to stock, I try to flash phiremod 6.3 again because this is really my end goal anyway. This time it is a success. I connect to my wifi. The device says I am connected and the wifi signal is strong, but I can't establish a reliable data connection with google, or open the market, or browse the web. I turn the wifi off and on, I tell it to forget my connection and add it again, but nothing seems to work until a day later when it suddenly establishes a connection.
So everything seemed like it might be ok at this point except strange things started happening with the device. Power + n doesn't take it into recovery, and never did at any time it has been in my possession. When I try to go into recovery from ROM Manager after flashing CWR I go into a bootloop. This is even after updating Rom Manager and doing things like rebooting after flashing CWR. Wifi always says it's strong and connected but any app with internet access is often times painfully slow to the point of being unusable or at least impractical. Downloading a single app from the market is like pulling teeth, and I regularly get the "retry or cancel" popup over and over again. Sometimes when I tell it to reboot or shut off, I get the "rebooting" or "shutting off" message and it just grinds away endlessly.
The device is currently in a bootloop after just telling it to reboot (normal reboot not reboot into recovery), and I know how to pop in my sdcard with CWR and get out of it. However, my problem is that this is a gift for my sister, and I just cant seem to get this device into a normal working state that I can give to her.
I know that there are plenty of threads answering all of the little problems I have outlined here, but none have resolved them for me nor have I found a single thread that deals with a whole host of problems like this device seems to have.
Thank you for your patience in reading this.
Try restoring to stock 1.2:
http://forum.xda-developers.com/showthread.php?t=1050520
It can't hurt at this point, and it may get you fixed.
Thanks for the reply.
No dice. I tried both of those files. I made sure to format the system and data before flashing each time, and I'm still stuck at the "n" screen.
Alright so here's what I just did:
1) Format system
2) Format data
3) Flash B&N v1.1 "old" 1GB "/data", 5+GB "/media" partitioning zip from:
http://forum.xda-developers.com/showthread.php?t=1094371
4) Reboot
5) Flash Stock 1.2 update.zip from:
http://forum.xda-developers.com/showthread.php?t=1050520
6) Unmount sdcard
7) Reboot
8)Still stuck at the "n" screen.
The story so far:
I was forgetting to do the 8 reboots after repartitioning and flashing stock apparently.
I performed the 8 reboots, and my Nook did a factory reset and OTA update. Now it boots into stock v1.1.0. I see the pretty lady, there's a video, I get to accept a B&N agreement, I connect to either of my wireless connections, but after I enter my account name and password it always says "Error sorry we're having trouble setting up your Nookcolor. Please shutdown the device and try again...." It gives me a number to call so I do. After a long bewildering conversation with tech support, I'm told that my device was once registered to someone else (which I already suspected having purchased it on ebay). I'm told that in order to fix the problem they are going remove the old account from the device, and that when I restart it in an hour I will be one with the Nookcolor universe. It has been many hours, and I am still getting same error message.
Should I continue down this path with customer service (who are failing to inspire me), take it into the Barnes and Noble store this weekend (I don't have a receipt but it at least it boots into stock now), or just go ahead and load phiremod 6.3 (which is my end goal, but I want to make sure I don't take one step forward and then two steps back now that I've gotten this far)?
"Device Info" only has "back," "power off," and "reset."
I just tried holding the "power + n" for 10 seconds as demonstrated here Nook blocked after downloading latest software - Barnes & Noble Book Clubs. This guys seems very happy that this solution worked for him. I don't know why it wont work for me seeing as I have the exact same problem.
Barnes and Noble tech support came through and reset my device. It appears that I have a stock 1.1 Nook Color and all is well. I am even connected and able to browse the internet. Does this mean I am ready to start flashing new ROMs onto it, or should I do more testing while it is still stock?
So I made a nandroid backup of the stock system with no problem. Then I flashed phiremod v7 test. Everything was going well until I went to ROM manager, flashed CWR, and tried to make a backup. It went into a bootloop so I put in my sdcard with CWR. Immediately it started putting my backup on that card. I rebooted it through CWR, but it still went into a bootloop. I then did a factory reset, full wipe, and flashed phiremod 6.3... still bootlooping away. This is one of the problems I was having before I started this thread. The CWR on my sdcard is ClockworkMod Recovery v3.0.0.6.
Sorry to read that you're having so much trouble. FWIW I'm having one hell of a time using Phiremod on my NC, too. I've found solace with CM7 nightlies and the latest Dalingrin kernel.
CWR 3.0.0.6 is very outdated at this point. I use CWR 3.2.0.8 on my recovery SD. I think it was V3.0.0.6 that had problems formatting the data partition, but I could be wrong.
Hope you get it sorted out.
Thanks for the support. Do you know where I could find the latest versions of Clockwork?
There's a typo in my post above. The current version is 3.2.0.1
I read about it and got the files from androidforums.com, although I'd be surprised if they weren't on this forum, too.
I downloaded recovery-clockwork-3.2.0.1-bravo.zip, put in my sdcard, flashed the new version of CWR, and now it is endlessly scrolling through the CWR menu on its own. The log at the bottom says "ClockworkMod Recovery v3.2.0.0," then "Back menu button enabled," then "Back menu button disabled," then "Back menu button enabled," and seems to be continuing like that without end. After powering off, removing the sdcard, and holding the power + n buttons for about 8 seconds, the screen shows the cyanogenmod logo and says "booting into recovery" but does nothing. I've repeated this entire process several times while holding the power + n buttons for varying times and it still doesn't actually boot into recovery.
Wulfie6 said:
I downloaded recovery-clockwork-3.2.0.1-bravo.zip, put in my sdcard, flashed the new version of CWR
Click to expand...
Click to collapse
This is the problem. The nook color is the encore not the bravo. You have the wrong recovery image. Its a good thing its unusable...you might fubar your device if you were actually able to use that recovery.
Sent from my Phiremod Nook Color using XDA Premium App
I created a new boot disk with CWR 3.02.8 and successfully flashed Phiremod 6.3 and CM7 nightly 107. I was still essentially unable to use the internet on both of these ROMs even though my wifi connection said it was good. I did not try using my phone as a hotspot with these versions.
I'm on CM7 108 at the moment. I'm still getting sporadic internet access even though my wi-fi is pretty good (usually just shy of full bars). I connected to my phones wi-fi hotspot which produces full bars on the Nook with good internet results. This isn't practical though because I can't always have my phone creating a wi-fi hotspot. Doesn't this seem odd that my Nook is only internet reliable when it's connected to an excellent wifi connection, but functionally wont work when it's on a good wifi connection?
Also when I go into ROM Manager and try to flash the current version of CWR, it pulls up the "confirm phone model" (when it is actually connecting to the internet) but as soon I put my finger on the menu to scroll through, it selects the first one I touch. This is one of the problems I was having before on all ROMs.
So I just went into ROM Manager, flashed the latest version, then tried to make a backup through ROM Manager, and now I'm in a boot loop again except this is the kind of bootloop where I can't get it to turn off. It just sits there with the cyanogenmod logo saying "Loading..." When I hold the power down, it turns off and then comes right back on. When I hold power + n, it does the same thing but instead of saying "Loading..." it says "Booting into recovery..." I don't understand why this time it's different. If I take out the card that's in there now and put in my bootable SD card while it's in the boot loop, will it fry my cards?
Wulfie6 said:
S When I hold the power down, it turns off and then comes right back on.
Click to expand...
Click to collapse
sounds like it's plugged in
TheAmazingDave said:
sounds like it's plugged in
Click to expand...
Click to collapse
It's not plugged in.
Return to stock 1.2 - Stuck at n screen fix.
After you flash the 1.2 image with a clockwork recovery sd boot card, and are stuck at the n screen, you will need to restart and have the Nook software reset to default.
1. Hold Power+n for 8 seconds, release n, then power (it may take a couple of tries to get it right).
2. At the "Factory Reset" screen, confirm your intention to reset to defaults (press "home" n).
3. At the "Are you sure?" screen, confirm again (press "home" n).
It will then go to a "Clearing data..." screen and reboot to the stock nook software.
This procedure will reset your device to stock 1.2, just as it was when it shipped.
I second what JoeInternet says. You NEED to be on stock B&N 1.2 to be able to run the latest CM7 builds and ANY .32 Dalingrin kernels or it will not work.
Quick thought... The first thing that should have been done is an ATO 'deregister' to get that nook's ID dis-associated with the original BN account.
Heya XDA - I have no idea WTF happened to my tab. Received notification of a OTA upgrade yesterday, taking me to one of the most recent 3.1 builds (.10 if I remember) - this morning woke up to another OTA update message offering me to go to .11 - accepted, downloaded, tablet hung up during the OTA process.
Now here's where it gets tricky. No matter what I do, when powering up my tablet I get the "Power Off - Shutting down" screen, and a endless spinning circle as the tablet claims to be shutting down. I cannot access any part of the system - all on screen commands are dead, except for the Settings icon in the lower right hand corner - i can click it, enter settings - but the moment I try to select a catagory or change any setting, the system goes right back to the "Power off - Shutting down" screen.
I am way outside the 30 days I can get a trade in - really don't want to have to mail this thing off to Acer.
Here's what I have tried:
One of Vache's full ROM images for my Region - flashed via power and vol process- fails about 1/4 of the way through.
Clearing cache/data - managed to get the vol/power+rotation lock combo going that clears cache and data. Still cannot boot - once I power on no matter what I do I get the "Power Off - Shutting Down" screen.
Tried to do the factory reset via USB keyboard + "Home"??? button? Heard mention this opens up a menu of some sort that I can factory reset from, I have two different USB keyboards and cannot manage to make this happen. Anyone able to explain this? Can this help me?
What's so weird about this - once I power up, I get the "Power Off - Shutting Down" screen no matter what I do. During this time, my battery shows up as %15 - this a500 has been on the charger for hours and hours, overnight last night, was 100% this morning before I applied the OTA update. Even with tablet plugged in, the battery shows as only 15%. What's even weirder - with tablet power off and plugged in, I do not get the red or blue charging light from the power button.
Totally freaking out here, no idea what to do. Anyone able to help?
Edit: When trying to manually flash a update.zip - I am getting the Clockwork Mod (I think?) flash screen - a green droid guy with gears turning. This fails about half way through. I have installed ClockWorkMod before this problem - but cannot enter the clockwork menu by the normal vol/power combo - I am so confused
Edit again: From browsing other posts - seems I am not the only one with this problem. The most recent OTA update failed, every single reboot since then is useless - all I can get is the "Shutting Down.." screen. Trying yet another update.zip via MicroSD to see if I can actually restore my tablet
Edit Yet once more (Problem Resolved!) - no idea how - but after a lot of searching I found a full package with build number 4.010.40_COM_GEN1 - this update.zip flashed with no problems, and my Iconcia is UNBRICKED! Sorry for the panic, everyone
OTA .13 Failure
I have the same problem, but got there by a different path. After many attempts to upgrade to .11 from .7, I downloaded the full file .02 to .11, decrypted and moved update.zip into the external sd card. Used the power / vol- combination and the update to version .11 went on without a hitch. Shortly after that, I received a notice that .13 OTA was available. It appeared to install without a hitch but after it rebooted (automatically) the tablet came back and immediately displayed the never ending Power Off screen described above. I would add that a two gears with a belt icon is sitting in the top left corner and "Android System" is noted beside that icon. I have tried every trick I have found in the forums to fix this:
1. Removed the SD card and shut down the tablet
2. Used power / vol- with portrait rotation lock turned on
3. Put the SD Card (with the .11 update.zip file ) back in and tried 1 and 2 again (no change: never ending power Off)
4. Tried power / vol+ with rotation lock. Saw the cach clear and looked very promising. Came back up with the rotating gears guy, but still went back to Power Off.
As soon as the power button is pressed the power icon goes red and stays there. Looks like the .13 update fools the device into thinking the battery is dean and it tries to shut down but never completes the cycle.
Acer A500
Rooted
Acer Recovery installed
.11 last successful update
US (Texas)
Failed .13 OTA
alamotx said:
I have the same proble,, (trim) I would add that a two gears with a belt icon is sitting in the top left corner and "Android System" is noted beside that icon. I have tried every trick I have found in the forums to fix this:
1. Removed the SD card and shut down the tablet
2. Used power / vol- with portrait rotation lock turned on
3. Put the SD Card (with the .11 update.zip file ) back in and tried 1 and 2 again (no change: never ending power Off)
4. Tried power / vol+ with rotation lock. Saw the cach clear and looked very promising. Came back up with the rotating gears guy, but still went back to Power Off.
As soon as the power button is pressed the power icon goes red and stays there. Looks like the .13 update fools the device into thinking the battery is dean and it tries to shut down but never completes the cycle.
Acer A500
Rooted
Acer Recovery installed
.11 last successful update
US (Texas)
Failed .13 OTA
Click to expand...
Click to collapse
Exact same problem here. Downloading update.zip files like mad trying to find one that will work. Anyone have any idea what the hell is going on?
Moving to Q&A.
PS: Every Q? thread should be posted in Q&A.
Thanks for that - sorry for mispost. Again, as noted in my original post - question answered, issue resolved. Total panic this morning
entropy.of.avarice said:
Exact same problem here. Downloading update.zip files like mad trying to find one that will work. Anyone have any idea what the hell is going on?
Click to expand...
Click to collapse
Me too... Ive tried 104.02, 4.010.22, 141.07, 141.02 none of them are getting me back... I can boot the tablet, but I now have no launcher icons for back, tabs, and home, and of course no clock and settings tab at the bottom. I have no root, and no CWM now. HELP!!!!
entropy.of.avarice said:
Thanks for that - sorry for mispost. Again, as noted in my original post - question answered, issue resolved. Total panic this morning
Click to expand...
Click to collapse
Please share your solution for the rest of the community.. if the solution is in a different thread, could you put a link here to the other thread with your solution?
Thanks
Euclid's Brother said:
Please share your solution for the rest of the community.. if the solution is in a different thread, could you put a link here to the other thread with your solution?
Thanks
Click to expand...
Click to collapse
For sure - sorry about the delay on that, was just so excited to be unbricked after a day of futile effort, I needed a break.
Anyway - here's what I have figured out. Somehow during the ota update I received this morning something failed - the tablet rebooted, and regardless of what I did the moment I booted up I would get the powering down notification. System access was not possible. This was on a 100% stock official 3.1 version - even unrooted before letting the update run.
Tried one of the full ROMS from Vache's thread in the dev section, as well as a bunch of other backup images I was able to find. Every single one failed at about 25%.
After a lot of fail - I gave this thread a try:
http://forum.xda-developers.com/showthread.php?t=1187578
"Bricked Tablet...help!"
I used the link on the bottom of page one - the unencrypted update.zip user kjy2010 was kind enough to upload - here is the direct link - http://www.multiupload.com/WCT2FYLMQC
This one worked - put on MicroSD card and flashed via vol/power method - result - 4.10.40_COM_GEN1 - and I am unbricked! Iconiaroot 1.3 worked for getting root after install - slowing getting my tab back to normal now
Okay, I've seen a lot of "I bricked my Nook Touch" posts around, and floating everywhere but none of their solutions worked. I used the TouchNooter step by step, got the checksum right, did everything right.
Loaded the SD card, restart the nook, BAM! Got stuck on the dreaded "Rooted Forever" screen.
Here's what I've tried so far:
redoing the process
booting without sd card
booting again WITH sd card
8 failed boots
factory reset (bottom left and right and the power button)
30 seconds power button hold, 10 seconds without, 10 seconds holding it down
I think that's about it. i'm just about ready to throw this thing out, seriously. Any other ideas?
I think I'll keep on trying to do the 8 failed boots thing
wajanus said:
Okay, I've seen a lot of "I bricked my Nook Touch" posts around, and floating everywhere but none of their solutions worked. I used the TouchNooter step by step, got the checksum right, did everything right.
Loaded the SD card, restart the nook, BAM! Got stuck on the dreaded "Rooted Forever" screen.
Click to expand...
Click to collapse
As you're able to power down and reboot your Nook I wouldn't even call it bricked. Bricked is when your hardware fails or you manage to screw up your bootloader
I always get stuck on the "Rooted Forever" screen or boot animation when using either Noogie or TouchNooter image, but the process still works, so this doesn't really indicate that something went terribly wrong.
wajanus said:
Here's what I've tried so far:
redoing the process
booting without sd card
booting again WITH sd card
8 failed boots
factory reset (bottom left and right and the power button)
30 seconds power button hold, 10 seconds without, 10 seconds holding it down
I think that's about it. i'm just about ready to throw this thing out, seriously. Any other ideas?
I think I'll keep on trying to do the 8 failed boots thing
Click to expand...
Click to collapse
1,2,3: Unless a simple reboot without the SD card helped this ain't gonna do much good.
4: This usually helps if you can mange to trigger it, it will properly replace both boot and system.
5: This is completely useless. As far as I've seen all it does is clean your /data/app folder and not much more.
6: Never heard of this, can't imagine what it's supposed to do.
One thing you can try the original NookDevs rooting process , see if that kicks your boot into working order again. This is my preffered rooting method.
Your best bet is trying to trigger the 8-failed boot recovery. I've done this a few times on my N2 and it can be a little tricky.
May I ask what version you're running? 1.0.0 or 1.0.1 ?
Thanks.
As far as 6 goes, I saw it on a few forums on the 'net and it was said to break the boot cycle.
I suppose it's not "completely bricked" but I've spent so long with it, trying to get it to work that I'm really, about to ready to throw it away.
I'll try the original guide, hopefully that will trigger it.
It's a 1.0.0, I got it a week after it came out (and it's been bricked since the first TouchNooter came out).
Also, how should I try to do the 8 failed boot recovery? Half the time, it's hard to tell if it's booting, or if it's turned off o.o the only difference I saw is when the Nook is plugged in. Any ideas?
wajanus said:
Thanks.
Also, how should I try to do the 8 failed boot recovery? Half the time, it's hard to tell if it's booting, or if it's turned off o.o the only difference I saw is when the Nook is plugged in. Any ideas?
Click to expand...
Click to collapse
First you need to check whether long pressing power will reboot or just power down you Nook. From my experience a unit that "hangs" on boot will power down when the power button is pressed for at least 10 seconds, while a successfully booted unit will simply reboot.
The following is based on my experience with "hung" units:
Prereqs:
- No USB cable attached (not even charger!)
- No SD Card inserted
Steps:
1: 12 second press (to be sure) for power down
- most likely you'll see no change in the screen!
2: Wait 5 seconds for Nook to settle
3: Press power for 4 seconds to turn it back on
4: Goto step 1 as soon as you see the screen flicker!
- Do not wait for boot animation, a simple flicker is enough!
Repeat 8 times
Also, see this thread for a factory restore image
I wonder, if desperate, whether JTAG could be used.
It is REALLY too bad that some people are so impatient.
When it says "rooted forever", that does NOT mean that the process has completed. It means that the process has ONLY STARTED. Give it some time.
WAIT.
Wait 20 minutes.
It will complete.
Be patient.
If you have to, pull out the battery from the thing.
Then put in the special sdcard.
Plug the battery back in, plug the charge plug in.
Turn on.
WALK AWAY AND COME BACK TOMORROW.
Sorry, but I wouldn't call myself impatient. I pre-charged my nook to full charge before attempting rooting. I left the Nook alone without restarting it until I realized it may need charging again. It was THEN that I tried to restart it.
"WALK AWAY AND COME BACK TOMORROW" <- Yeah, I did that.
However, I do admit, I was expecting a quicker root/rom flash I'm used to my Samsung Vibrant
ros87 said:
First you need to check whether long pressing power will reboot or just power down you Nook. From my experience a unit that "hangs" on boot will power down when the power button is pressed for at least 10 seconds, while a successfully booted unit will simply reboot.
The following is based on my experience with "hung" units:
Prereqs:
- No USB cable attached (not even charger!)
- No SD Card inserted
Steps:
1: 12 second press (to be sure) for power down
- most likely you'll see no change in the screen!
2: Wait 5 seconds for Nook to settle
3: Press power for 4 seconds to turn it back on
4: Goto step 1 as soon as you see the screen flicker!
- Do not wait for boot animation, a simple flicker is enough!
Repeat 8 times
Click to expand...
Click to collapse
Will try. Currently, my nook doesn't even turn on -.-
wajanus said:
Will try. Currently, my nook doesn't even turn on -.-
Click to expand...
Click to collapse
If you can't get it to work, try nookRestore. It basically tricks the nook into thinking you've restarted eight times already.
wajanus said:
Will try. Currently, my nook doesn't even turn on -.-
Click to expand...
Click to collapse
How do you know it's not turning on?
Thread moved. Development goes in the development section, questions in the general section. Thanks.
okay, fast forward a few months forward. I did figure out that the nook DOES turn on but it's probably stuck on an infinite loop. I was successful in booting several different "recoveries". There was a tool a few months back that removed root. The "recovery" booted but didn't help.
Since then I tried the new CWR and it booted! I was so excited. I did the whole "factory reset" and deleted all of the caches. Didn't help, the screen still showed "Rooted Forever". I tried to use the "Touch Formatter", unfortunately, that didn't help either. I used the TouchNooter again but again, nothing happened.
Any suggestions? I haven't seen a "stock" image or anything like that to boot into anywhere.
If your partitions are still intact and you haven't overwritten your rom-partition by writing a touchnooter or cwm img-file directly to the nook you could try the following:
-Create a sd-card with cwm,
-download nook_1_1_update_cwm.zip from http://code.google.com/p/nst-recovery/downloads/list and copy it to the sd
-boot into cwm
-use the install zip from sd-card function to apply the update.
The nook_1_1_update_cwm.zip contains the original update to 1.1, it is just repacked to be usable with cwm. That means, if you want root, you have to root afterwards.
The nook_1_1_update.zip that you get directly from Barnes & Noble is a standard zip file with with a signature attached to the beginning. You can strip off the first 0x1A8 (424) bytes and open it with any unzipper.
Renate NST said:
The nook_1_1_update.zip that you get directly from Barnes & Noble is a standard zip file with with a signature attached to the beginning. You can strip off the first 0x1A8 (424) bytes and open it with any unzipper.
Click to expand...
Click to collapse
I actually found 7-zip can open it without having to do anything to the zip first.
you guys are AMAZING! I couldn't find the 1.1 anywhere. I'm downloading it and installing it later on today. Will update on progress
Steps work
ros87 said:
The following is based on my experience with "hung" units:
Prereqs:
- No USB cable attached (not even charger!)
- No SD Card inserted
Steps:
1: 12 second press (to be sure) for power down
- most likely you'll see no change in the screen!
2: Wait 5 seconds for Nook to settle
3: Press power for 4 seconds to turn it back on
4: Goto step 1 as soon as you see the screen flicker!
- Do not wait for boot animation, a simple flicker is enough!
Repeat 8 times
Click to expand...
Click to collapse
Steps 1-4 solved an infinite loop loading problem with Nook Simple Touch (firmware 1.1).
okay, that seems to have helped some. The Nook boots into a "Read Forever" with a "starting up" thing on the bottom (basically the way stock looks) instead of "Rooted Forever" but it seems like it's in a bootloop, stays on the same screen and never progresses. I'm going to try the n2T to trigger a factory reset. Hopefully, that'll work :/
n2t did not work. Not sure what to do next.
The Device:
Nookcolor Refurb - came with stock 1.2 installed. Rooted with CM7 - initially had boot partition problems and went back and did the fix for it. (was using an old CWR, so had to redo that, too). Worked mostly fine for a few weeks. Had a little trouble installing the recent cm7 stable update. But after clearing and redo, no problems. Then I updated Adobe flash to 10.3 through the market. bad, bad, bad. (I've discovered). It has gone into a bootloop, but it doesn't even get in far enough to bring up CWR either internally or on a bootable SD card. It brings up "loading" - whether in CM7 or CWR - then shuts itself off. I have tried the 3 button salute and 8 interrupted boots, but neither works in any way. Is there something else I can do?
Also, a side note, the device will not charge to green light - even if charging overnight. At first I thought it was a battery issue, but after a day of combing the boards, I'm thinking bootloop from hell.
Help!!!!
Are you running CM 7 internally or from a card? If internally, try making a bootable CM 7 card and booting from that.
I am running it internally. The device will not boot from a card or internally. It doesn't get far enough into the boot before it loops for CWR to start up - either internally or off the sd card. I can get to the boot menu (hold down n when it starts up), but it doesn't boot off any of the options there, just goes to black screen.
What happens when you do the 8 failed boots?
Nothing really happens with 8 failed boots. I think it terminates the boot process before it gets far enough along for it to "count". Loading comes up, I count one thousand one....all the way to one thousand seven. Then it shuts off, often reboots itself. Same deal with CWR. Loading comes up, count to 7, shuts off. I can get to the boot menu in CM7, but I it doesn't respond when I request any type of boot from anywhere. Either hangs or restarts.
I'm trying ADB, but it won't stay connected. Flicks on right at the end of the loading process and then shuts down. It really sucks.
Shelly, shoot me a pm... i'll give ya my phone number and we'll work on getting it going.
Sorry if this is redundant, but in very basic troubleshooting have you tried charging your Nook? It probably is more complicated/serious than a low battery, but it wouldn't hurt to rule it out.
I finally did get it to charge to green light. Didn't make a difference. I can get it to hang sometimes when it's trying to get into CWR. And it will stay on the Boot Menu.
Just a side note, I have another NC that I've had since Jan. Autonootered, Manual Nootered, CM7ed, brought back from the dead many a times.
Dizzy Den - am shooting you a message shortly. Thanks.
Has this been solved? If yes how?
Could you find a solution to your problem?
I'm having the same issue now. Bought a Nook Color in November, Autonooted, flashed recovery from ROM Manager, flashed CM 7.1.0 internally from downloaded ZIP files via ROM Manager, was working just fine for a week, stable, fast, perfect. Overclocked to 1200 MHz after a few days which made the experience even nicer.
Then installed and started Google Maps which didn't work - the Nook turned off on launch of Google Maps app.
I had set Wifi to "stay on all the time" beforehand (which might have been bad because it creates Sleep of Death syndrome as i now know).
Now when i turn it on it shows "Loading" for 7 seconds and then the screen turns off. This is when booting CM, when booting the internal recovery (shows "loading recovery" for 7 seconds) and when booting from any SD card image (i've tried at least 10 different bootable SD card images, different cards and different card readers).
It recognizes and tries to boot off SD cards - i get different "Loading" screens depending on the image, honey-colored for a honeycomb image, with two skulls for a recovery, ... So that works.
The nook seems to be in some kind of "on" state because i need to hold the power button to turn it off before i can get it to boot again.
I can get to the boot menu as you could, but booting from there doesn't do anything at all. So the hardware seems to be OK because the boot menu itself works well and for more than 7 seconds.
I can charge it and it goes to a green light so it's no battery issue.
The nook does not show up on USB - well once it did for a second but that was it.
I even tried to let the battery run completely empty so internal registers can get reset - didn't change anything.
Help! Is it bricked now?
Going to a B&N store isn't an option btw - the next one is 6500 km from here.
(This is the first time i ever ask for help on a forum. I am running a ZTE Blade with CM7 just fine, and I've been stuck often enough but always found a solution myself...)
Gunnar
Have you guys tried this:
http://forum.xda-developers.com/showthread.php?t=1308304
Or completely restoring it to stock:
http://mrm3.net/nook-color-recover-any-bricked-device/
Tried, can't get far enough
Kingdruid, thanks, yes i've tried both of those links - sadly they don't help at all because i can't even boot SD card recovery images...
I tried various recovery images including the newest clockworkmod, but i am still stuck They all work for 7 seconds only.
So yes, a nook can actually be bricked it seems.
G.
tralulu said:
Kingdruid, thanks, yes i've tried both of those links - sadly they don't help at all because i can't even boot SD card recovery images...
I tried various recovery images including the newest clockworkmod, but i am still stuck They all work for 7 seconds only.
So yes, a nook can actually be bricked it seems.
G.
Click to expand...
Click to collapse
When you overclocked it, did you notice it getting hotter than usual? I wonder if it was due to the overclocking. All the users I see with unrecoverable nooks is after they overclocked.
No, i did not notice much heat. And it was working well in its overclocked state for a few days.
Do you think it's CPU is fried now?
tralulu said:
No, i did not notice much heat. And it was working well in its overclocked state for a few days.
Do you think it's CPU is fried now?
Click to expand...
Click to collapse
I own 4 of them so I would prefer the term "Unbrickable", but at this point I'm not really sure.
Try 8 failed boots and see if you can get into recovery to reset to factory.
cant get it working
so first noob post
i used this thread to root my nook color
http://forum.xda-developers.com/showthread.php?t=1000957
problem is i have followed the steps and re done it about 5 times and every time i turn on the nook it goes right to read forever and runs the stock OS
nook 1.2 brand new, and 8gig SD card
when i boot i hold the power button for the 5 seconds, am i missing something?
tntviper1 said:
so first noob post
i used this thread to root my nook color
http://forum.xda-developers.com/showthread.php?t=1000957
problem is i have followed the steps and re done it about 5 times and every time i turn on the nook it goes right to read forever and runs the stock OS
nook 1.2 brand new, and 8gig SD card
when i boot i hold the power button for the 5 seconds, am i missing something?
Click to expand...
Click to collapse
how did you write the image to the SD card? you can't just do the write button in winimage, you have to use the "convert virtual hard disk image to drive" or something... really should be mentioned in the n00b guides.
Sequence in winimage:
Disk->Use disk (whatever your sd card is)
Disk->Restore virtual hard disk image on physical drive (select the image you're trying to write)
Click ok on the warning and you should have a boot disk
"Write disk" is prominent but just copies the files to the disk, not resize or make it bootable.
Nope - no change
DizzyDen, nope, 8 failed boots does nothing. Just fails 8 times, no restore.
I've read the other posts, and there are some similarities, but I still don't get a clear picture... So here goes...
I've had my Nook Color for about two years and created a SD card boot to CM7 that worked like a charm for these last two years, then...
the system a few days ago went into a boot mode automatically, and just looped. All I could do was turn it off by long press on the power button.
I removed the SD card and booted to the Nook operating system and all went fine.
Re-installed the SD card and started the boot process, it again went to continuous CM7 logo looping.
Tried recovery mode, which seemed to go well, although it shut itself down without completing the boot process.
I have tried every imaginable switch combination (volume, power, n), all to no avail. Depleted power, full power, power connected, etc. Nothing breaks the cycle.
Recent app installations were Netflix, a word document processor, a speaker amplification. Titanium backup was running sometime in the near past. Most apps were loaded to the SD card.
I would like to be able to save some documents on the SD card, but now what to do?
Reload a fresh copy of CM7?
Load a new triple boot of basic, CM7 and CM9?
Just jump to a altogether new CM10.1?
Any suggestions (remember the forum rules, now...).
Thanks a million.
Well, here's what I've done.
Burnt another SD card with CM10.1 - works like a charm but don't have any of my old files on the card -started all new.
Downloaded CWM on another card, booted to it, but got menu choices I wasn't sure about, so chose "SD boot". removed the CWM card, put in my old CM5.7 card, pressed the "N" (to start the reboot), and got the same old loop.
I guess I just don't know enough, and don't know where to go to get smarter.
And the rest of the story...
CM10.1 ran fine for two days, then this morning on power-on, I got a message of "Trebuchet" error - no matter what I did, the error message prevented starting any other program or a normal power off. So...on restart, got LOOPING AGAIN! CWMod doesn't help.
Back to Google and forums.
Problem solved! (But, other than getting a good installation, I don't remember exactly HOW!)