Database Develop

Help stuck on grey n screen and can't get out

I'm stuck at the grey N screen and I can't get out. I just got my NC today, updated to 1.0.1, used the latest Autonooter, followed the instructions to a T, everything worked great.
I left the SD Card in (didn't know you were supposed to take it out and reformat it, none of the instructions were specific about that). I was playing with the unit, everything was working great and decided to reboot it because I saw there was a custom animation and I wanted to see it (didn't remember seeing it the first time around). Now the thing won't reboot. It just gets stuck at the grey N screen. I've tried the power + home method and done the factory resets 3 times but when it resets it still hangs on the N-screen and won't boot.
I'm at a loss here. Some one please help.

jbright44 said:
I'm stuck at the grey N screen and I can't get out. I just got my NC today, updated to 1.0.1, used the latest Autonooter, followed the instructions to a T, everything worked great.
I left the SD Card in (didn't know you were supposed to take it out and reformat it, none of the instructions were specific about that). I was playing with the unit, everything was working great and decided to reboot it because I saw there was a custom animation and I wanted to see it (didn't remember seeing it the first time around). Now the thing won't reboot. It just gets stuck at the grey N screen. I've tried the power + home method and done the factory resets 3 times but when it resets it still hangs on the N-screen and won't boot.
I'm at a loss here. Some one please help.
Click to expand...
Click to collapse
Did you try taking the SD out and then booting? It'll keep trying to boot from it as long as nooter is on there.

wvcachi said:
Did you try taking the SD out and then booting? It'll keep trying to boot from it as long as nooter is on there.
Click to expand...
Click to collapse
Yes I did. It's doing all of this with the SD card out.

jbright44 said:
Yes I did. It's doing all of this with the SD card out.
Click to expand...
Click to collapse
I'd say interrupt the boot 8x (powering down will do) to initiate system restore, then re-root.

wvcachi said:
I'd say interrupt the boot 8x (powering down will do) to initiate system restore, then re-root.
Click to expand...
Click to collapse
Edit. That fixed it. Thanks. Man do I feel stupid. I thought the 8x reset and the 3 button method were the same. Apparently not. I'll try this again a little smarter hopefully this time.

Thank you for this thread. I thought I just bricked my 2 hour old nook. I stupidly restarted it after root with the nooter card still plugged in. Then I couldn't figure out why it was taking so long for the screen to turn on, so I kept pressing the button and then holding it. Then I realized the card was still in. Took the card out and tried to boot it, but it hung at the 'n' screen. The 8 interrupted boot method saved me from my stupidity though. Thanks.

Same here - left the card in...
8x reset and then a home and power reset cleared me up. Then update back to 1.1 and autonooter 3 again.
Loving it ever since.

hey
im having the same problem i did the factory reset to and nothing
wats the 3 count and wat else can i do

So what to do when factory restores and stock installs fail?!
OK... reviving this thread since it's my exact problem but I've been unable to find resolution. I've been searching everywhere for what to do next but nothing seems to be working.
I'm helping my buddy get his nook working. He said he was updating to 1.4 and when he rebooted it, it froze on the n screen. He plugged it back into his Win 7 machine to try the update again and it wouldn't mount as a USB device.
After a bunch of reading and fiddling, he built an SD card with ClockworkMod and installed in on an SD card. Or so he thought... he hadn't made it bootable. Over the phone, I walked him through restoring the image to his card and then it booted.
CWM comes back with a pile of errors. Specifically,
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
When trying to format /data and /system, we also get errors.
We've downloaded various factory restore zips and tried installing them but they install (successfully according to CWM) and we reboot only to get stuck at the dreaded n screen again. We've done the 8 boot interrupt restore and get and error to call support (nobody answers this week) and done the regular power/+/n restore and it completes but leaves us again on the n screen.
Can anyone tell me the significance of these errors in CWM? It's the only thing different from all the tutorials and video walkthroughs we've followed and although we've seen these errors in other posts, there's never been a good explanation of them and how to resolve them if necessary.
Also, what is the latest version of CWM for the Nook Color and where do I find it? Is there an official site for CWM? Seems like people are just linking to older versions and sources all over the place with no common "go to the CWM site and get latest build of CWM." The latest I've found is 3.2.0.1 in a post back in August 2011.
Thanks in advance! Hoping this gets us over this hump and helps anyone else in the in the same situation.
moose

Solved it...
I've managed to solve the problem I outlined above. I'm not at home right now, so I'll post the specifics once I can get back and post the links and images I used to get this working.
Note that I had no concern for the data/books/apps that were on the device originally. I just wanted it working again with stock 1.4.1.
Basically, I noticed that after restoring to 1.1, the initial screen said "welcome to the future of reading" and then when I updated to 1.2, it said "read forever" so I knew the updates were at least doing something. I now needed to get rid of the errors in CWM 3.2.0.1 so started looking for something to blow away corrupt (?) partitions.
I found a post that had two zip files and it said they repartitioned the nook entirely. I hoped they would blow away my corrupted partitions by rewriting the partition table. I ran one, and it forced me to reboot. Then I ran the second and rebooted. It loaded up, got to the n screen and paused just long enough for me to lose some hope and then flipped over to the nook color boot animation. Yah! Progress!
Tried to register the device using my own bn.com account but wasn't successful. Turns out that you need to either use the original registered account on bn.com or unregistered the nook from his account, but since the error shared the same wording as previous failed factory restores (but this time in the nook registration interface), I assumed it was something locally. I came across a post in the searching that mentioned the need to unregister the nook from the original account to register it on another.
While trying to figure out what to do, I found a 1.4.1 signed stock image that also reconfigured the restore on the device and worked through CWM "install zip from SD" rather than using bn.com update zip via usb (i was still having trouble accessing the nook via usb at this point).
I downloaded the stock cwm 1.4.1 zip and installed it through cwm 3.2.0.1. It booted and then I saw the intro video on the nook registration page had a different woman. I got my buddy to send me the email and password he registered the nook with and the registration process was successful. I now have a working stock 1.4.1 nook color to return to my buddy.
I'll post the actual links to the posts/images that I used once I get home.
Hope this helps others!

I'm also getting the E: Can't mount / errors.
Will try this when I get home.
Also i'm just realizing now that i am using an older CWR v3.0.0.5, so that might be my issue also.

links
Mooseroo Could you please post links used to fix this issue

Try using this version of CWR. Just remember you can always choose a recovery image smaller than or the same as your SD card but not larger.
http://mrm3.net/blog/2011/03/11/nook-color-updated-clockwork-recovery-bootable-sd/

this is not working. same issue with nook 1.4.1 and CM7...hangs at "N" or goes black with CM7

Have you check the MD5 of all your files to make sure you have good downloads? It is frequently a skipped step but one of the easiest and first things you need to check.

Mooseroo - where are you?
mooseroo said:
I've managed to solve the problem I outlined above. I'm not at home right now, so I'll post the specifics once I can get back and post the links and images I used to get this working.
Note that I had no concern for the data/books/apps that were on the device originally. I just wanted it working again with stock 1.4.1.
Basically, I noticed that after restoring to 1.1, the initial screen said "welcome to the future of reading" and then when I updated to 1.2, it said "read forever" so I knew the updates were at least doing something. I now needed to get rid of the errors in CWM 3.2.0.1 so started looking for something to blow away corrupt (?) partitions.
I found a post that had two zip files and it said they repartitioned the nook entirely. I hoped they would blow away my corrupted partitions by rewriting the partition table. I ran one, and it forced me to reboot. Then I ran the second and rebooted. It loaded up, got to the n screen and paused just long enough for me to lose some hope and then flipped over to the nook color boot animation. Yah! Progress!
Tried to register the device using my own bn.com account but wasn't successful. Turns out that you need to either use the original registered account on bn.com or unregistered the nook from his account, but since the error shared the same wording as previous failed factory restores (but this time in the nook registration interface), I assumed it was something locally. I came across a post in the searching that mentioned the need to unregister the nook from the original account to register it on another.
While trying to figure out what to do, I found a 1.4.1 signed stock image that also reconfigured the restore on the device and worked through CWM "install zip from SD" rather than using bn.com update zip via usb (i was still having trouble accessing the nook via usb at this point).
I downloaded the stock cwm 1.4.1 zip and installed it through cwm 3.2.0.1. It booted and then I saw the intro video on the nook registration page had a different woman. I got my buddy to send me the email and password he registered the nook with and the registration process was successful. I now have a working stock 1.4.1 nook color to return to my buddy.
I'll post the actual links to the posts/images that I used once I get home.
Hope this helps others!
Click to expand...
Click to collapse
Just found this thread and I have the same issue - can you post the links you reference? Please?

tmccully said:
Just found this thread and I have the same issue - can you post the links you reference? Please?
Click to expand...
Click to collapse
I think he's talking about my files in this post.

Urgent Newbie, Nook Ruined?

I need some serious help, I guess. I couldn't even tell you what happened.
**NOTE: I have to post the youtube titles the to tutorials I used since I'm new. I can't post the links.***
Anyway, I am new to nook. I tried to get cute and root it (and thought I was doing so with the MicroSD method) but it wasn't the way I wanted to do so.
I followed this guys tutorial [SEARCH YOUTUBE FOR How to Install CyanogenMod 7 on the Nook Color (PC Version)] to install CyanogenMod 7 on the Nook Color.
Here I am everything's going along fine, and then he gets to the part where he says "take out the SD card and reboot..." and I'm going "WHAAAT?!" I didn't want to root my nook, but create a start up image on my MicroSD card so it wouldn't come to this situation...
Anyway, I did what he said because I'd gone too far as it was. When I tried to reboot, the CyanogenMod 7 screen just stuck loading and loading. I rebooted NUMEROUS times, and nothing... so I repeated all his steps again, and nothing.
I tried to format the cache, data and system. That worked fine... but I think at one point I accidentally chose "wipe data/factory reset" and "wipe cache partition."
I tried using his reversal method here [SEARCH YOUTUBE FOR How to Unroot / Restore / Unbrick the Nook Color (PC Version)] to get my NC back to normal, but upon following these steps, found myself with an error when trying to format the data.
The error reads, "Formatting /data... Error formatting /data!"
Does ANYONE have any idea what I did, and how I can reverse it?
I can pay a couple of bucks to whoever helps me out to show you that I am dead serious about this.
I am a newb, so I'd need some detailed instructions.
I have two MicroSD cards that I can use, one 2GB and one 16GB.
Please help!!!
Email me at [email protected]... please due let me know if you have Skype or Yahoo. I prefer a live chat.
PLEASE... God bless you.

I apologize. I think I posted this in the wrong section.

Firstly, don't panic, no need to. If the first time doesn't work out, try a couple more times.
Secondly, we're here to help so relax and try to tackle your issue slowly.
Now, be sure to tell us what you intend to do NOW (at this stage of your NC)?
a. returning to the original stock ROM or
b. installing and running CM7 from internal memory (aka. eMMC) or
c. booting CM7 off uSD card
If the answer is either a or b, then first step, try getting the ClockworkMod Recovery (CwM R) version 3.2.0.1.

If you want to go back to stock on a NC you can ALWAYS do so(unless you screwed with your partitions which I doubt you did) by doing this simple thing:
-Power it off.
-Now turn on.
-While it's booting up hold down both POWER and N buttons.This will power your nook off no matter what every time, it's built right into the device. Great for getting out of bootloops.
-Do this EIGHT TIMES.
Your Nook was designed to be nearly "UnBrickable". After 8 failed boots it will always restore it's factory settings. So unless you've tried this and it did not work, then no, your Nook is not ruined. Obviously you don't wanna have an SD card in there while doing this, or you will probably get AIDS.

Landara said:
If you want to go back to stock on a NC you can ALWAYS do so(unless you screwed with your partitions which I doubt you did) by doing this simple thing:
-Power it off.
-Now turn on.
-While it's booting up hold down both POWER and N buttons.This will power your nook off no matter what every time, it's built right into the device. Great for getting out of bootloops.
-Do this EIGHT TIMES.
Your Nook was designed to be nearly "UnBrickable". After 8 failed boots it will always restore it's factory settings. So unless you've tried this and it did not work, then no, your Nook is not ruined. Obviously you don't wanna have an SD card in there while doing this, or you will probably get AIDS.
Click to expand...
Click to collapse
you can also do it by holding down "Power" "N button" and "Up volume" at same time and it will do a factory reset

Touchpad Keeps Restarting in Clockworkmod

Hi guys i been searching everywhere, all over forums and google and i cant seem to figure out this issue, the issue is that i have a demo version of a 32gb touchpad, and basically i followed all the steps to install clockworkmod and moboot and all that stuff, once all that was completed i choose to install an android rom from the development section, and no matter what i do in clockworkmod, it just keeps restarting, it begins installing a rom and then just automatically restarts. it does that when i wipe cache aswell, i redid the entire process again and i get the same issue, everytime i try to install a rom or do a gaaps update it just restarts and nothing gets installed, Please let me know how to fix this issue

Sounds like you need to completely restart fresh. It could be because of the Demo setup of the TP, it doens't wanna allow CWM to work properly.
What I would do is read THIS THREAD and follow the instructions - it'll factory reset everything, but it'll then be ready for you to install CWM, Moboot, and CM9 again. I know it works cuz I just did it last night.

thanks alot buddy, it WORKED!!!!! now my touchpad finally has android, and webos, oh man android is amazing, my kid luvs it

[Q] Trouble updating to CM10 3/4

I am coming from OaT LnTJB 12/22 and upgraded to AcmeInstaller3 before flashing that ROM (as I came from CM9, although I didn't use AcmeUninstaller first) and also have moboot 3.8 and the latest TWRP and CWM.
However, when trying to flash the new CM10 build after doing a full wipe through recovery (i.e., System, Data, Cache) I keep coming up with the same errors, such as "damaged SD card" upon boot (even though I can browse the contents through file manager) and broken wallpaper (didn't dive too much into other errors after those, as I already knew something was amiss). Also, in trying to wipe cache/dalvik, upon reboot it gave me this weird screen where it usually would say "Android is upgrading..." and instead had some symbols (one was %) with a prompt that I can paraphrase as "touch to switch apps". Odd to say the least.
Any ideas as to what could be causing these errors? Should I just dirty flash over OaT (not my preference)? Any/all help is appreciated!

rg2 said:
I am coming from OaT LnTJB 12/22 and upgraded to AcmeInstaller3 before flashing that ROM (as I came from CM9, although I didn't use AcmeUninstaller first) and also have moboot 3.8 and the latest TWRP and CWM.
However, when trying to flash the new CM10 build after doing a full wipe through recovery (i.e., System, Data, Cache) I keep coming up with the same errors, such as "damaged SD card" upon boot (even though I can browse the contents through file manager) and broken wallpaper (didn't dive too much into other errors after those, as I already knew something was amiss). Also, in trying to wipe cache/dalvik, upon reboot it gave me this weird screen where it usually would say "Android is upgrading..." and instead had some symbols (one was %) with a prompt that I can paraphrase as "touch to switch apps". Odd to say the least.
Any ideas as to what could be causing these errors? Should I just dirty flash over OaT (not my preference)? Any/all help is appreciated!
Click to expand...
Click to collapse
I would run acmeuninstaller, then go through the cminstall and acmeinstaller3 thing.
Good luck.
Edit: make a backup, just in case. Use cwm, there's been cases where twrp has caused problems.

You say you have two both TWRP and CWM which one did you use? It's also probably one to many as the maximum size for the boot folder is 32mb which you are probably quite close to.

chicle_11 said:
I would run acmeuninstaller, then go through the cminstall and acmeinstaller3 thing.
Good luck.
Edit: make a backup, just in case. Use cwm, there's been cases where twrp has caused problems.
Click to expand...
Click to collapse
Thanks for the advice. Going to have to do this I guess.
sstar said:
You say you have two both TWRP and CWM which one did you use? It's also probably one to many as the maximum size for the boot folder is 32mb which you are probably quite close to.
Click to expand...
Click to collapse
I used them both, although I generally use TWRP. I got rid of CWM and tried again to no avail. Thanks for the reply.

Running ACMEuninstall and reinstalling did nothing to fix the problem. Still have "damaged SD card" prompt upon boot, still have broken wallpaper functionality as well as crippled launcher functionality. Any ideas?

How is webOS running? If you get problems in that also then I would run acmeuninstaller and then run remove android from preware followed by webos doctor 3.00 then 3.0.5 if you want to actually use it.

sstar said:
How is webOS running? If you get problems in that also then I would run acmeuninstaller and then run remove android from preware followed by webos doctor 3.00 then 3.0.5 if you want to actually use it.
Click to expand...
Click to collapse
No issues with WebOS; trying WebOS doctor right now then going to try and reinstall android, hope it works. If not I will try your suggestion. Thanks for the info!
**EDIT** Tried WebOS doctor, but it stuck at 72% and I had to pull the plug; now my TP won't boot at all. Because of course it won't. Device may be bricked
**EDIT2** Okay just rescued my TP using jcsullins de-bricking tool via Linux. Now I am back in WebOS. If I may ask, what should be my next step? My SD storage is intact so I know my device wasn't completely wiped, which to me means that I might run into the same problems installing CM10, and I would obviously like to avoid that. I would like to do a full wipe but seeing as how WebOS doctor ended disastrously I am a little skittish about my next move. Once again, any/all help is appreciated. Thanks!

reset webos
rg2 said:
No issues with WebOS; trying WebOS doctor right now then going to try and reinstall android, hope it works. If not I will try your suggestion. Thanks for the info!
**EDIT** Tried WebOS doctor, but it stuck at 72% and I had to pull the plug; now my TP won't boot at all. Because of course it won't. Device may be bricked
**EDIT2** Okay just rescued my TP using jcsullins de-bricking tool via Linux. Now I am back in WebOS. If I may ask, what should be my next step? My SD storage is intact so I know my device wasn't completely wiped, which to me means that I might run into the same problems installing CM10, and I would obviously like to avoid that. I would like to do a full wipe but seeing as how WebOS doctor ended disastrously I am a little skittish about my next move. Once again, any/all help is appreciated. Thanks!
Click to expand...
Click to collapse
I was having trouble installing cm9 when I bought my touchpad. Got an error that said drive needed to be formatted when connected to my pc. I did a reset in webos and it fixed the problems. Try that.

rg2 said:
No issues with WebOS; trying WebOS doctor right now then going to try and reinstall android, hope it works. If not I will try your suggestion. Thanks for the info!
**EDIT** Tried WebOS doctor, but it stuck at 72% and I had to pull the plug; now my TP won't boot at all. Because of course it won't. Device may be bricked
**EDIT2** Okay just rescued my TP using jcsullins de-bricking tool via Linux. Now I am back in WebOS. If I may ask, what should be my next step? My SD storage is intact so I know my device wasn't completely wiped, which to me means that I might run into the same problems installing CM10, and I would obviously like to avoid that. I would like to do a full wipe but seeing as how WebOS doctor ended disastrously I am a little skittish about my next move. Once again, any/all help is appreciated. Thanks!
Click to expand...
Click to collapse
Did you use webOS doctor 3.00?
Sent from my cm_tenderloin using Tapatalk 2

johna2u said:
I was having trouble installing cm9 when I bought my touchpad. Got an error that said drive needed to be formatted when connected to my pc. I did a reset in webos and it fixed the problems. Try that.
Click to expand...
Click to collapse
Thanks for the tip. Will have to try this.
sstar said:
Did you use webOS doctor 3.00?
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
No did 3.0.5. Gonna try 3.00. Thanks again for all the help!
**EDIT** After downgrading to 3.00 via WebOS Doctor and doing a Secure Full Wipe through WebOS, I was able to install the new JCSullins CM10 build w/o issues! Thanks again to all for the help

rg2 said:
Thanks for the tip. Will have to try this.
No did 3.0.5. Gonna try 3.00. Thanks again for all the help!
**EDIT** After downgrading to 3.00 via WebOS Doctor and doing a Secure Full Wipe through WebOS, I was able to install the new JCSullins CM10 build w/o issues! Thanks again to all for the help
Click to expand...
Click to collapse
Glad you have sorted it I'm using this Rom http://goo.im/devs/SGA/CM10/CM10_UnOfficial_Mar0813.zip with http://goo.im/gapps/gapps-jb-20121011-signed.zip and extremely happy with it.
If you are going to try it do a system,/factory wipe and then flash with your recovery.
I'm assuming you originally used acmeuninstaller 3

sstar said:
Glad you have sorted it I'm using this Rom http://goo.im/devs/SGA/CM10/CM10_UnOfficial_Mar0813.zip with http://goo.im/gapps/gapps-jb-20121011-signed.zip and extremely happy with it.
If you are going to try it do a system,/factory wipe and then flash with your recovery.
I'm assuming you originally used acmeuninstaller 3
Click to expand...
Click to collapse
Thank you for the suggestion! I will try this since I seem to be cursed using the JCSullins build :/

[Q] HELP!!! Removed boot image HELP!!! Can't boot

OK so I'm just going to explain everything I did and ask how we can fix this. I was following the guide to install LuneOS and I got lost somehow and could not put the new boot image and new moboot image on after I removed the old boot image, so I tried to reboot (I know that was dumb) but then I got a error message about no Palm ROM. So I booted into the only thing I could boot into WebOS Recovery. Now I figured I would try out jcsullins Touchpad Toolbox I was able to load it and I figured the only way I could make it work would be to remove and reinstall WebOS to get the boot image back, so I wiped the touchpad (again probably not the best thing to have done). I then went to go and reinstall WebOS and the WebOSdoctor(webosdoctor305) I used failed after 8%(should I try a different doctor?). I then tried to install Android with Toolbox and it failed after checking the files(not sure if that was just bad files or issue with touchpad). I can still access WebOS recovery and use novaterm by finding the batch file on my computer and running it and I can still use Toolbox. Any help would be greatly appreciated and if you have any questions of what steps I took I will be happy to answer if it can help my touchpad.

spenser715 said:
OK so I'm just going to explain everything I did and ask how we can fix this. I was following the guide to install LuneOS and I got lost somehow and could not put the new boot image and new moboot image on after I removed the old boot image, so I tried to reboot (I know that was dumb) but then I got a error message about no Palm ROM. So I booted into the only thing I could boot into WebOS Recovery. Now I figured I would try out jcsullins Touchpad Toolbox I was able to load it and I figured the only way I could make it work would be to remove and reinstall WebOS to get the boot image back, so I wiped the touchpad (again probably not the best thing to have done). I then went to go and reinstall WebOS and the WebOSdoctor(webosdoctor305) I used failed after 8%(should I try a different doctor?). I then tried to install Android with Toolbox and it failed after checking the files(not sure if that was just bad files or issue with touchpad). I can still access WebOS recovery and use novaterm by finding the batch file on my computer and running it and I can still use Toolbox. Any help would be greatly appreciated and if you have any questions of what steps I took I will be happy to answer if it can help my touchpad.
Click to expand...
Click to collapse
Wear exactly do you what with your tp webos or android or both? You could have saved yourself and just put moboot back on lol