Hey there. I could really use some help. I rooted my nook color 1.1 a while back with no issues and finally decided to take another step. I added Rom Manager from the market. Did a backup and then after adding cm 7.02 encore to my class 10 16gb card, I followed the Rom Mgr directions to attempt an upgrade. Device is now stuck.
I have tried putting the various .zip files listed in the "Dummies Guide to fixing My Nook Won't Boot."
I have tried using various sized (128 mb, 4gb, 8gb) Clockwork recovery Images (that I write to my card via winimage) along with nook-complete-restore-1.0.1.zip adn also then with repartition-boot-with-stock.zip that i copy and paste onto the card that has the recovery images.
All attempts seem to have the same result:
With the uSD card out: I get "Touch the Future of Reading" then "android_" then the android robot splash screen where it hangs.
With the card in it just sits at a black screen.
I ahve also tried connecting with adb. My nook shows up as a usb device but i can't get a serial number from "Adb devices."
Any idea on how to get this back to something usable?
I really appreciate any help.
rileychris said:
Hey there. I could really use some help. I rooted my nook color 1.1 a while back with no issues and finally decided to take another step. I added Rom Manager from the market. Did a backup and then after adding cm 7.02 encore to my class 10 16gb card, I followed the Rom Mgr directions to attempt an upgrade. Device is now stuck.
I have tried putting the various .zip files listed in the "Dummies Guide to fixing My Nook Won't Boot."
I have tried using various sized (128 mb, 4gb, 8gb) Clockwork recovery Images (that I write to my card via winimage) along with nook-complete-restore-1.0.1.zip adn also then with repartition-boot-with-stock.zip that i copy and paste onto the card that has the recovery images.
All attempts seem to have the same result:
With the uSD card out: I get "Touch the Future of Reading" then "android_" then the android robot splash screen where it hangs.
With the card in it just sits at a black screen.
I ahve also tried connecting with adb. My nook shows up as a usb device but i can't get a serial number from "Adb devices."
Any idea on how to get this back to something usable?
I really appreciate any help.
Click to expand...
Click to collapse
You need to boot with your recovery card out otherwise you will just keep rebooting to recovery. Also how long did you wait at the android splash screen? First boot can take a while as the Nook is building cache/dalvik. I believe mine took nearly 10 minutes to boot the first time. Have you tried the 8 failed boot reset yet?
I think i had done well more than 8 without seeing anything happen, but maybe not. This time i tried holding the power, the n, and the volume+, buttons and doing that twice in a row all of a sudden brought me into the recovery menu.
All is well now.
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.
Hello,
So i've tried to root the nook. Copied the touchnooter on my card, booted the nook. And then : forever stuck on the "root forever" or the "read forever" (when i get the card off)..
The hard reboot (20 sec on power off) doesn't work and i'm stuck at this "read forever" screen.
Is there a way to recover the nook ?
Thanks.. !
When doing the hard power off (long press) the screen doesn't usually change and you might be fooled into believing nothing happened.
Have you tried to let the unit settle for 10 seconds and then press power for a few seconds to see if it tries to boot?
Hey,
thanks for replying. I have tried a 30 sec hard boot + a reboot try but nothing happened. It freezes on the "nook is starting screen".
I afraid i have broke my device... But strangely i followed the rooting steps and nothing seemed to do wrong.. I guess.
Bye
If you can in fact get the unit to start booting, just long press power (10s +) as soon as you see the unit try to boot to interrupt the boot, then power it on again and repeat this procedure for 8 times (sucks, yes I know) and you should drop into factory reset.
Ok so i have to say : WTF !
So this morning i looked at my nook and saw that it still was on the "reading forever"/"starting" thing. As i saw your advice i tried to boot 8 time..
On the first boot attempt : it worked ! So maybe is was the eighth..
The nook started and asked me if i wanted to continue with android guy or "es something"... so i pressed android guy..
SO now i don't really know if the procedure went well ? Is it supposed to be rooted now ?
Thanks anyway for the time you took replying !
I hope my english is not too hard to read.
Bye,
By "android guy" I guess you're referring to the Android Welcome screen?
That would suggest that the Touchnooter went trough successfully.
Did you get Go Launcher and ButtonSavior up and running?
IIRC, whenever you do a fresh boot and try to use ButtonSavior you'll get a notice saying ButtonSavior has been granted superuser access, which would indicate that you're successfully rooted.
I had a similar problem, using touchnooter 1.11.20 and it was too quick. Maybe 45 seconds, removed card and restarted. Stuck in a boot loop, on tne "Nook" screen with the little blocks move across the screen and just keeps restarting. Fortunately I made a backup and was able to restore. Not sure what the problem is but I tried TouchNooter 5 times, downloaded it twice, wrote it to the SD cars 3 times and same result, Stuck on the nook screen, animation gets to the 4th dot and restarts. Tried salsichaNooter .4 with the same result. Any ideas on what the problem could be? It would be really nice if I could get a decent reader on this thing.
I made my life a little easier by having 2 micro SD cards to use, nookie on one and touchnooter on the other. I also made sure I had a good backup of my original ROM by opening the image with 7zip and the nook with partition wizard and verifying they were the same. At least I can gat it back to a working stock rom.
Why dont you try my new method?
http://forum.xda-developers.com/showthread.php?t=1346748
PS:
..... insomnia Sucks......
Thanks, I'll see if this works.
Not really insomnia, trying to get this fixed before I have to put my wife on a plane. It's her nook touch, I have a color, it was so much easier.
I'm having a similar problem: I used SalsichaNooter, I let Rooted Forever to be on the nook screen for an hour, there were no messages on the screen no progress indication of any sort. I did a hard reboot after an hour and it seems at least some part of the rooting script worked - but how do i know the nook was rooted all the way through since it didnt reaboot during the rooting process as it should?
After an OTA update on my 2 day old tablet it gets stuck on the splash screen. Everything was stock. Update looked like it installed correctly and everything. I tried flashing the stock package provided on this website but in the top left corner in red letters it says "recovery verified failed"
I extracted the files. put the update.zip in the root of my sd card.
I don't know what version my tablet had on it as i didnt even have it long enough to play with it.
Any ideas before I have to send it back and wait for weeks on a replacement?
Itncould be a defective tablet.
You could try a reset with the reset hole on side next to USB port.might revert it back. Or d/load a full rom put on formatted SD cardnand try to flash holding volume down and power until flash starts
Lots more info about this in dev area.
Goodluck.
I tried the reset button but its still stuck on the screen when it reboots. I tried that flash method with a full Rom and that's when I got the red error message.
Thanks for the quick reply.
tbturner47 said:
After an OTA update on my 2 day old tablet it gets stuck on the splash screen. Everything was stock. Update looked like it installed correctly and everything. I tried flashing the stock package provided on this website but in the top left corner in red letters it says "recovery verified failed"
I extracted the files. put the update.zip in the root of my sd card.
I don't know what version my tablet had on it as i didnt even have it long enough to play with it.
Any ideas before I have to send it back and wait for weeks on a replacement?
Click to expand...
Click to collapse
I got a same problem ...
My a500 gets stuck
Hi guys, getting kinda desperate here, appreciate any advice.
I've been mucking around with my phone trying to install some of the mod roms from here, but always get stuck in an endless reboot sequence or on the 'huawei' screen. Havent been able to get CM10.1 or 7 installed and working.
I have followed the instructions, including the partition size mod....
This is not my current issue, however, just the background.I was at a loss so after giving up last night I tried to copy b162 to my sd card, but was read only for some reason - showed up as CD rom on my PC.
Out of desperation I formatted the sd (in CWM) and tried again, but couldnt even get CWM, only pink or blue screen.
Pink screen I tried copied recover.img to the one available drive on my PC (windows), no luck. It copies over, but will not enter CWM with vol up + power.
Went out and bought a card reader this AM, have tried to install the stock roms B162 and B136.
I can copy the .app files to the SD card (root/dload), but my phone when going to pink screen does not start updating, just stays in pink screen.
Have formatted the card in windows (fat32) checked for errors etc. Does anyone know if the 'allocation file unit' during formatting makes a difference? I have left it as standard at 32kb....
The current rom boots as far as the animated huawei (splashing stars thing) logo then cycles.
Cant get shell access with ADB on pink or blue screen.
Never really used linux but Im willing to try anything to save my phone.
I have some experience with microcontrollers and think there are some jtag pads on the back of the phone that might be useful but am reluctant to try this as I fear I will make things worse....
Many thanks in advance!
To add ? volume label important?
Just managed to get into the stock recovery screen, selected 'apply update from sdcard and got reply 'failed to mount /sdcard (no such file or directory).
I cant swap out the recovery.img file in the purple screen, I dont have acess to that part of the memory from purple screen, perhaps wrong version of android on previous install?
Was wondering if volume label should be something? I just left it blank, and have tried again as 'sdcard' still no luck.
Thanks again....
OK I did a factory reset from within the stock recovery sftward (couldnt even get this before) and it will now boot heh.
Oh well, thanks for listening! Will have another crack at aurora now =)
AucklandMatt said:
Just managed to get into the stock recovery screen, selected 'apply update from sdcard and got reply 'failed to mount /sdcard (no such file or directory).
I cant swap out the recovery.img file in the purple screen, I dont have acess to that part of the memory from purple screen, perhaps wrong version of android on previous install?
Was wondering if volume label should be something? I just left it blank, and have tried again as 'sdcard' still no luck.
Thanks again....
OK I did a factory reset from within the stock recovery sftward (couldnt even get this before) and it will now boot heh.
Oh well, thanks for listening! Will have another crack at aurora now =)
Click to expand...
Click to collapse
so have you fixed ur phone sir ? tell me how to do that sir bcoz same problem here