Database Develop

Nook will turn on by it self after 5 minutes or so

First I thought that I'm crazy but now I can confirm that my NC will boot on it's own after about 5 minutes after power OFF. I have to shut down 2nd time and than it will stay OFF. Any idea what's wrong ?
Thanks
(Yes I did confirm after first shut down that it's actually OFF since no buttons will respond)

Any weather Apps running? Many of them have an option to wakeup in order to update. Check your mail, twitter and facebook apps. It has to be something you installed, I have run every update, tried all the froyo images and both Honeycomb releases and I have not seen that.

To expand on what gedster wrote, it seems kind of crazy and out there but what about any devices on your network that might send Wake on Lan requests? What if something on your network had located your NOOKcolor. I don't even know why a eReader Tablet would have a function for Wake on Lan but it's just another crazy avenue to jog down.

I do have weather app installed but I find it hard to believe that it can wake up OS that is not in standby but completely off. WIFI is also not enabled before shutdown.

Looks like the problem is there only if I used market, if market is not used it will shut down fine and it will not boot on its own.

lifeisfun said:
Looks like the problem is there only if I used market, if market is not used it will shut down fine and it will not boot on its own.
Click to expand...
Click to collapse
Seems that's unlikely if you're the only one having the issue, I'd keep digging if I were you.

Looks like you're right I can't replicate the problem every time
The timing when it will boot also varies 5, 15 and even 35 minutes.
Don't know what to do, it's hard to imagine how it can boot on it's own from
complete power off state

I can't believe I'm the only one with this problem

lifeisfun said:
I can't believe I'm the only one with this problem
Click to expand...
Click to collapse
I just posted a thread about this issue for me less than an hour ago! Funny, no one replied to mine: http://forum.xda-developers.com/showthread.php?t=940713. It was pretty long...guess I should've added a TL;DR.
It happens to me on any (or no) power source. Timing varies like yours as well. I'm going to pull my weather app based on the above recommendation, and I will try your Market theory out. Knowing someone else has this issue makes me hopeful that we can find something that we have in common as the culprit.
I did download the newest Honeycomb image yesterday and I'm going to put that SD card in and see if I can get it to turn itself back on on a Market-less, user App-less build. If successful I'll Titanium my 1.1 apps and remove everything non-system, then slowly add until I get this figured out. Keep me posted if you figure something out, I'll be sure to do the same!
In case it matters I bought mine about a week ago and the serial number starts with 20046.
EDIT: Testing with Honeycomb SD now so if that's the case here it should just stay off. I booted into Honeycomb at 9CST and turned it off at 9:01. I'll give it a couple of hours.

I used to have this same problem. I would randomly find my 1.0.1 auto-nootered 950mhz rom nook on, when I knew I had turned it off. interesting part is, this problem completely solved itself after I flashed my emmc with the custom nookie 5.9 img. so it must be an eclair issue and not a hardware issue

woot1524 said:
I used to have this same problem. I would randomly find my 1.0.1 auto-nootered 950mhz rom nook on, when I knew I had turned it off. interesting part is, this problem completely solved itself after I flashed my emmc with the custom nookie 5.9 img. so it must be an eclair issue and not a hardware issue
Click to expand...
Click to collapse
Really? I've been putting that off because I don't like the idea of not having Clockwork Recovery. I understand there are ways to do the same things using IOMonster's things but I'd really rather just have Clockwork Recovery working. Unless there's a way to get it going that I missed?

Yup, I've been having this issue as well. I really want to flash NF but I want hardware video acceleration.

oscillot said:
Really? I've been putting that off because I don't like the idea of not having Clockwork Recovery. I understand there are ways to do the same things using IOMonster's things but I'd really rather just have Clockwork Recovery working. Unless there's a way to get it going that I missed?
Click to expand...
Click to collapse
you are correct that clockwork does not work with froyo. however the bootable sd card that you would burn automatically starts up clockwork first. you can run a backup and restore, as far as i know, without having to reflash froyo. on a personal note, froyo still has some issues but overall I'm exteremly pleased so far. i really just wanted to get rid of all of the b&n stuff (mainly the status bar) along with any possible way of them pushing an update to break root. I would recommend it, but CM 7 with gingerbread will probably be out sooner rather than later.

woot1524 said:
you are correct that clockwork does not work with froyo. however the bootable sd card that you would burn automatically starts up clockwork first. you can run a backup and restore, as far as i know, without having to reflash froyo. on a personal note, froyo still has some issues but overall I'm exteremly pleased so far. i really just wanted to get rid of all of the b&n stuff (mainly the status bar) along with any possible way of them pushing an update to break root. I would recommend it, but CM 7 with gingerbread will probably be out sooner rather than later.
Click to expand...
Click to collapse
Which I guess brings us back to, why is Eclair doing this, and why does it seem to be limited to lifeisfun and myself?

I'm glad I'm no longer special
My serial # is 200503 .....
Removing all application that I have installed didn't help.
Only 100% way to shut down is to let it boot and immediately shut down.

unknown.soul said:
Yup, I've been having this issue as well. I really want to flash NF but I want hardware video acceleration.
Click to expand...
Click to collapse
Now that I understand the power of this things SD slot and that CWR can be run off of an SD, I can totally live with that. Hardware Video isn't a must for me yet, so I may take the plunge tonight after work...BTW, what are people's favorite video apps? I have been playing with VLC stream and convert, which works somewhat with my media server's samba shares. I have the share mounted to a directory on the sdcard since many apps look there exclusively.
More on topic, I couldn't get SD Honeycomb to start itself on its own. I tried booting then shutting down. 2 hrs of nothing 15mins light activity then shutting down. 2 more hours of nothing. About an hour of heavy use, seeing what could be installed, sideloading, testing, editing things like build.prop and rebooting often and trying to get swype working (don't think it's supposed to, but that's "heavy use" for me.) Powered down. Went to bed. Still not on this morning. This looks indeed to be an issue with the B&N stock Eclair.

Mine doesn't turn itself on with no interaction at all, but will turn on every time when you plug in the charger or cable hooked to USB port in computer.
I can turn it off once it is already plugged in and it will stay off, but remove and replug the charger and it is on again.
Strange.

Well, strange that only two or three of us noticed this strange problem.

Yeah, started for me after 1.1 update. Turned it off last night, tonight it was on with 40% battery! I think its 1.1 related, this didn't happen with 1.0.1 ...

I'm sure there's a condition that's causing or exasperating this issue, something common to us all. But at this point since I don't use the Nook as a video player (I actually bought it to read books, but I use Aldiko and the open epub format) I will likely flash Nookie to the eMMC and call it a day. Honestly can't wait to get a clean notification bar on this thing anyway.

cm7 broke my nook

I put in CM7 two days ago, and every thing was working fine. I restmy nook and it would not power on at all. I tried for 2 hours, and nothing. I was able take it back to the store and get a new one. What could cause that problem? After I installed cm7 it worked fine, I then took my sd card out reformatted it to put files on it. Then when I reset my nook and no power, no nothing.

Same Issue
I had the exact same thing going on. I installed CM7 and it worked great for a cpl days. Last night I plugged it in to charge it (left it on), and when I woke up it was off and unable to turn on. Black screen.
I put in my CWR sd card and held the nook, volume up, and power buttons to turn it on. I figured I just go back to eclair auto-nooter because I know its stable, so I formatted system and data and flashed the stock barnes and noble 1.0.1 rom. However...
I still have the same issue. The device doesn't power on. I'll return it to the store if I have to, but I'd prefer to fix it so that we can raise awareness.
Edit: I figured it out. The flashable repartition-boot-with-stock.zip was corrupted on my CWR sd card. I made a new one and I'm right as rain. Follow the instrustins HERE to fix the black screen issue with CM7. Although it will restore you NC to stock.

More than likely something happened to your boot partition. Please investigate the threads titled "guide to my nook won't boot"

jd95 said:
After I installed cm7 it worked fine, I then took my sd card out reformatted it to put files on it. Then when I reset my nook and no power, no nothing.
Click to expand...
Click to collapse
Thread should be called, I didn't read the directions and broke my nook. cm7, as well as all the other froyo/ginger roms that I've seen run off of the sd card. If you wiped those files off, it shouldn't be expected to still work.

jeremiah_mn said:
Thread should be called, I didn't read the directions and broke my nook. cm7, as well as all the other froyo/ginger roms that I've seen run off of the sd card. If you wiped those files off, it shouldn't be expected to still work.
Click to expand...
Click to collapse
The CM7 nightlies are not meant to be run from the SD card. There is also a build of HC that is not meant for the SD card. In my experience, nookie froyo ran better from the sd card, but it could also be run off internal storage.
So i respectfully disagree with your opinion. Which was actually a statement of incorrect facts.

jeremiah_mn said:
Thread should be called, I didn't read the directions and broke my nook. cm7, as well as all the other froyo/ginger roms that I've seen run off of the sd card. If you wiped those files off, it shouldn't be expected to still work.
Click to expand...
Click to collapse
You're wrong here, I don't believe CM7 even comes available for SD card, it's an internal install..
And there is a very common theme here... Install CM7, works fine, reboot, it's dead.. Have to do XYZ to get it back up running. Something is hosing something, surprised nobody has figured it out yet.
I remain on rooted Stock 1.0.1.

sparhawk36 said:
More than likely something happened to your boot partition. Please investigate the threads titled "guide to my nook won't boot"
Click to expand...
Click to collapse
Not trying to be a ****, but I did exactly what you said, and stated so in my post.
I followed the instructions listed here
I've actually done this many times in the past. Most of the time its because I'm messing around in adb. I even keep a spare sd card with me, ready to do this at all times.
In this instance, however, it is not fixing it.
Fixed it. My sd card went bad. The post in the link still works, although it restores your NC to stock.

khaytsus said:
You're wrong here, I don't believe CM7 even comes available for SD card, it's an internal install..
And there is a very common theme here... Install CM7, works fine, reboot, it's dead.. Have to do XYZ to get it back up running. Something is hosing something, surprised nobody has figured it out yet.
I remain on rooted Stock 1.0.1.
Click to expand...
Click to collapse
Ive done all kinds of stupid things to my nook including an attempted install of Slackware... but I have never bricked it. Ive been running the CM nightly builds without any kind of problems as well. Well, no problems outside what one would expect from development software that is still in a rapidly changing state. If you want stability and reliability, EMMc installs of CM and HC and even Froyo are probably not where you want to look right now.

admiralnorman said:
Not trying to be a ****, but I did exactly what you said, and stated so in my post.
I followed the instructions listed here
I've actually done this many times in the past. Most of the time its because I'm messing around in adb. I even keep a spare sd card with me, ready to do this at all times.
In this instance, however, it is not fixing it.
Fixed it. My sd card went bad. The post in the link still works, although it restores your NC to stock.
Click to expand...
Click to collapse
So to be clear here, your problem with CM7 not booting was related to your SD card "going bad"? Or was your restore process hampered by this?
You had installed CM7 to emmc and such, right? How would the SD card be affected by that?

If you formatted your card in your NC then that's the problem. Don't format your card with CW because it'll wipe the boot sector giving you a black screen. It's fixable, many people have made the same mistake on the #NookColor channel. Go there for help because it's faster than waiting for someone to respond here.

Edited for derp.

combustiblemonkey said:
Ive done all kinds of stupid things to my nook including an attempted install of Slackware... but I have never bricked it. Ive been running the CM nightly builds without any kind of problems as well. Well, no problems outside what one would expect from development software that is still in a rapidly changing state. If you want stability and reliability, EMMc installs of CM and HC and even Froyo are probably not where you want to look right now.
Click to expand...
Click to collapse
I agree with this statement. I'm happily back to Eclair and advanced task killer.
Sent from my PC36100 using XDA App

succulent said:
If you formatted your card in your NC then that's the problem. Don't format your card with CW because it'll wipe the boot sector giving you a black screen. It's fixable, many people have made the same mistake on the #NookColor channel. Go there for help because it's faster than waiting for someone to respond here.
Click to expand...
Click to collapse
Not helpful information contained in this post.
Sent from my PC36100 using XDA App

khaytsus said:
So to be clear here, your problem with CM7 not booting was related to your SD card "going bad"? Or was your restore process hampered by this?
You had installed CM7 to emmc and such, right? How would the SD card be affected by that?
Click to expand...
Click to collapse
The recovery SD card was not in the nook when it went bad. The Nook and the card weren't even in the same building. I would assume that the SD card simply wore out. It was an old card that saw much use. Everything from sitting in a camera to running the R4 in my Nintendo DS. I will give it the burial of a Patriot, Westboro Baptist protest and all.
I still have no idea why CM7 tore up the boot of my Nook. I was reading a book in aldiko before I fell asleep, but I don't rememeber what else I was doing.
Sent from my PC36100 using XDA App

admiralnorman said:
Not helpful information contained in this post.
Click to expand...
Click to collapse
YOUR post was useless. His post was completely accurate. If it wasn't what caused YOUR issue, fine, but what he said was 100% true.
By the way, you realize you didn't start this thread, right?
admiralnorman said:
The recovery SD card was not in the nook when it went bad. The Nook and the card weren't even in the same building. I would assume that the SD card simply wore out. It was an old card that saw much use. Everything from sitting in a camera to running the R4 in my Nintendo DS.
I still have no idea why CM7 tore up the boot of my Nook. I was reading a book in aldiko before I fell asleep, but I don't rememeber what else I was doing.
Click to expand...
Click to collapse
So what does your SD card going bad and your NC not booting have to do with each other????

khaytsus said:
YOUR post was useless. His post was completely accurate. If it wasn't what caused YOUR issue, fine, but what he said was 100% true.
By the way, you realize you didn't start this thread, right?
So what does your SD card going bad and your NC not booting have to do with each other????
Click to expand...
Click to collapse
Right. You asked for clarification on my earlier post. I provided it. It seems you don't like your quesions being answered. Next time use periods instead of question marks. Or properly label them as rehtorical.
- Sent from my HTC Evo 4g using XDA Developer's app.

It's the boot partition. Same exact thing happened to me. The nook seemingly won't power on due to not having anything to boot from. Luckily the uSD has boot priority so if you get one of the CWR IMGs floating around here and follow the guides, you can be up and running relatively quickly.

paranoid__android said:
It's the boot partition. Same exact thing happened to me. The nook seemingly won't power on due to not having anything to boot from. Luckily the uSD has boot priority so if you get one of the CWR IMGs floating around here and follow the guides, you can be up and running relatively quickly.
Click to expand...
Click to collapse
So any idea what's causing it to get wiped/corrupted? Formatting SD from within the booted ROM or unknown?

These types of threads are funny. People are too quick to blame the rom alone (even when clearly marked as dangerous / test / experimental, etc ones) after making the decision to risk the normal operation of the device in the first place. Take some responsibility people

Exactly.. I don't usually post in forums but this kind of stuff bothers me. I wasn't able to boot my Nook Color for a few hours but I never blamed it on anyone but myself. Almost every one of the custom Roms, Mods, etc says something like "Use at your own risk" Nobody is forcing you to try anything. If you think you "bricked" your Nook Color (which is almost impossible) you shouldn't blame it on the Rom or Mod or even expect to take it back to the store.. YOU took the risk. Even if you installed a Rom that slapped you and gave you the middle finger it's your fault in the end because no one forced you to try it (most likely...). I'm sorry if I haven't offered a useful solution to "cm7 broke my nook", but anyway all this is purely my opinion and I apologize if I have offended anyone but people need to take some responsibility for their actions.

[GUIDE] [BRICKED] Loading Roms/CWR via SD Fails - Black Screen of Death (28/02)

As we know, the Nook Color's SD slot will always take first boot priority. I'm in a situation where even booting via SD through known methods are not working.
The purpose of this thread is to:
1) Share with others who are in this similar situation, on methods which may result in the recovery of their own devices
2) Keep this discussion healthy so one day, I will be able to restore my own bricked device which I'm still striving hard to.
Click to expand...
Click to collapse
IMPORTANT: If you have a bricked device I need to emphasize on searching and reading very carefully what others have shared here in both General and in Development. This is a fundamental requirement, as with the ability to follow instructions and not panic by creating unnecessary threads. This will only make things harder to find, so thank you in advance for not doing that.
There are many useful guides out there, some of which the most helpful are:
Nook Color Restore to stock by samuelhalff
Dummies Guide to Fixing 'My Nook Won't Boot' by RileyGrant
Stock 1.1.0 Clockwork Recovery Image by brianf21
Nook 1.01 stock dd images by shad0wf0x
[RECOVERY] Monster RootPack 0.7 / Clockwork Recovery 3.0.0.5 SD by thecubed
Click to expand...
Click to collapse
Anyway, in severe bricking cases where hardware is not at fault, many of the solutions to restore the NC begins with either:
1) Booting to CWR-SD via uSD
2) Booting to a rom i.e. Nookie Froyo via uSD
3) Having ADB access, if available
Till date I am not sure why the SD-loaded programs do not work for me, and here are the symptoms:
1) Without SD inserted, the standard BN splash appears, 'Welcome to the Future of Reading', then gets stuck there till powered down. Needless to say, the 8-times reset method doesn't work.
2) With SD inserted, the 'LOADING' screen will splash, then screen blacks out with device still powered on . You will know that the device is still running as you need to hold power down for around 20 secs before you're able to power it back up again. I call this the 'Black Screen of Death'.
Click to expand...
Click to collapse
To get your device up and running, try the following:
0) Do not panic. As long there's no hardware failure there will always be a solution. Look at me, thing's still a damn brick and yet here I am, still hopeful
1) Perform a search, read the useful threads created by the above members first. This thread is related only to failed SD-booting.
Once you've done that, prepare your recovery options with these in mind. The elimination process is part and parcel of problem-solving. In no particular order:
2) Sometimes, try powering on your device by connecting the USB cable from your PC or A/C source, instead of using the Power button.
3) Use only the original USB cable that came with your device.
4) Use the back USB ports of your PC, instead of the fronts as they may provide more consistent power and connection to your device. Try to avoid using USB hubs as they may not distribute the required power equally/properly.
5) Try switching to different USB ports, some may be hardware-gimped due to wear-and-tear.
6) Try to attempt the recovery on another Win, Mac or Linux computer. At least eliminate further possibilities of environmental hardware error.
7) Try charging the battery full.
8) Or, try discharging the battery completely, by leaving the device in BSOD state overnight until you get a message saying your device can't boot due to insufficient power when switched on. Once you are in this state, keep booting the device up until the screen does not appear. Then, recharge it back to full to see if the OS returns to stock (I am sceptical of this, but this was what others advised).
9) Try different SD cards. The device could be picky. Variety should be by class-type, brand, SDHC or non-SDHC. It's been discussed that faster cards perform better, as with more reknowned brands. Also, 16GB cards reportedly do not run Froyo (do read more by searching).
10) When loading anything via SD (CWR, roms), try different button combinations i.e. power + n + up, power + n, etc.
11) And/or, hold power for various timed-presses i.e. >30 / 45 / 60 seconds. Some members report CWR booting up after these periods, or even longer.
Note: funnily I tried holding power + n + up for > 60 seconds and the 'LOADING' screen just stays frozen. Still doesn't work, and I didn't get any ADB access.
12) Try formatting the card completely with native Win/Linux tools, EASEUS Partition Master or SDFormatter before each burn.
13) Try using both Win32DiskImager and WinImage, or dd-ing in Linux (search for more instructions). If you have Linux, you can check to see if the SD's /boot partition is indeed bootable or not.
14) For ADB access, try to unregister your hardware (go to Start > Run > devmgmt.msc), then unplug-replug device to have your PC detect it again. If a device with VID of 2080 shows up, that's the NC. You should know what this means, by now. If not, read more here.
15) Try different SD card readers, especially when experiencing failure on multiple computers. As opposed to multi-adapters i.e. 6-in-1s, try dedicated microSD readers like this one. Do not use those microSD-to-normalSD converters (usually packed together in the same shipping plastic as your card) just because you only have a reader that reads regular SD cards, they tend to fail a lot.
16) At your own risk, try cleaning the contact points on your SD cards (if you must, use cleaning alcohol and a cottom swap/q-tip - do not use water), to free them of dirt and invisible grime. If you have multiple SDs, try cleaning the least expensive ones first. Don't forget to leave them to dry completely before insertion into the NC. Credit to bonobomidwest, read his experience here.
Click to expand...
Click to collapse
17) Use Nooter 0.2 (recommendation from thecubed):
Here's my recommendation: use the stock charger cable (the one with the light-up N in it) when you try Nooter 0.2.
If the light goes from orange to green (or something like that) that means Nooter is booted and working.
My new thought: some file in /rom is missing, which controls the backlight and lcd controller. I can't prove this, but it seems logical haha.
All you need to do is get Nooter 0.2 booted and ssh'd in and you'll be able to dd over a complete 1.0.1 backup.
rawfish: I use Ubuntu, so sorry if I'm not able to provide instructions for Windows
Type:
Code:
sudo ifconfig usb0 192.168.2.1
Then:
Code:
ssh [email protected]
And you should be able to follow the directions for restoring on the wiki... either that or check around on IRC, if you tell them that you've got ssh access and you just need to restore your device, they'll help you out if I'm not around..
rawfish: I typed 'dmesg' in shell to see if the NC connected as a usb-ethernet device, and it doesn't show. If it does for you, then you should have progress and should ask around in IRC.
Click to expand...
Click to collapse
All these did not work for me, but hope this is useful to some. I've read testimonies from everyone that this is an unbrickable device, and I certainly hope it's true, and for a kind soul to help suggest more solutions. As I'm overseas, do you think I should call BN up to see if I can arrange to send my device back for fixing/replacement? It's been a month since purchase, and 3 weeks of failed restore attempts.
Disclaimer: I am not responsible if any of these methods get you in deeper trouble. Attempt at your own risk. Credit goes to thecube aka IOMonster, and the #nookcolor channel on irc.freenode.net. Thank you to everyone who created the recovery guides too.

This space reserved.

You sure you just don't have crap or badly burned SD cards? Sounds pretty much what happens if you boot s really slow/junk SD or burn it badly.

khaytsus said:
You sure you just don't have crap or badly burned SD cards? Sounds pretty much what happens if you boot s really slow/junk SD or burn it badly.
Click to expand...
Click to collapse
I tried on 6 different SD cards:
1. Transcend 8GB Class 6
2. Transcend 4GB Class 2
3. Wintec 16GB Class 10
4. Sandisk 4GB Class 4
5. Sandisk 2GB non-SDHC
6. Sandisk 256MB
I've burned stuffs like Autonooter and Honeycomb on these before, and they worked fine.

rawfish said:
I tried on 6 different SD cards:
1. Transcend 8GB Class 6
2. Transcend 4GB Class 2
3. Wintec 16GB Class 10
4. Sandisk 4GB Class 4
5. Sandisk 2GB non-SDHC
6. Sandisk 256MB
I've burned stuffs like Autonooter and Honeycomb on these before, and they worked fine.
Click to expand...
Click to collapse
First of all - great job in pulling all the resources into one place (it's small consolation, but i think you've just helped a whole load of people )
Second, i apologise if I'm telling you stuff that's obvious, but in helping out on these forums often it's the LOGIC of troubleshooting rather than the particulars of the problem that are important... In other words, only vary one thing at a time, and ALWAYS swap out every piece of hardware involved at each stage... if you always rely on one piece of hardware this might be the weak link... so have you tried a different SD drive or adapter? and have you tried burning from a different computer?
Now, I'm not being insulting, because I had a virtually identical problem with my first froyo - it just wouldn't boot (as you describe) despite multiple burns, different cards, all of the standard formatting tricks etc. It wouldn't work in multiple computers - the common element being the SD/microSD adapter. It never occurred to me that such an electrically simple part could be at fault, but you bet it was - in fact i would say in my experience these things consistently fail! (I spent a day kickign myself, because we know ho unreliable they are from using them in other devices). They also all look alike so it's hard to keep track of which one you are dealing with They also fail unexpectedly, so if you used an adapter before there's no guarantee it's working now...
Sooo... Have you tried a dedicated microSD reader (rather than a simple adapter)? I now carry one with me everywhere (it doubles as the world's smallest thumb drive too)
http://www.amazon.com/gp/product/B002HGFKR8
Also bear in mind that froyo appears not to work on 16gb cards (i see you tried one)
Also, from my experience with other devices these cards are very sensitive to dirt and oil on the contacts. Certainly with enough frustrated handling you can get enough finger-grease on them to have them fail. Also they seem to be much less tolerant when writing than reading. I have NO idea how you would go about cleaning out the slot in the NC (and as someone who has ruined at least one DVD drive by blowing canned air where you shouldn't I'm not going to advocate for that). I have resurrected 'dead' SD cards before by cleaning the contacts with rubbing alcohol and a q-tip (on the card's contacts) - but again do so with great care (at your own risk!!!) and with your cheapest card, and make sure it si completely dry before you put it in the NC.
I have been generally a little scared that all this plugging and unplugging of the microSD might hurt the NC, so i have done everything i can to avoid that...

I am sure you can find someone local to you willing to help fix your boot issue but I assure you, its damn near impossible to brick a nook without physical damage.

@bonobomidwest:
No offence taken at all, in fact I am very appreciative of your contribution. I forgot to add the fact that I tried on 2 different card readers, plus indeed tried to clean the slot via an air duster VERY GENTLY as a last effort resort (I would not recommend this, it may cause permanent hardware damage). Once I'm free I'll go get a new SD reader (reads uSD only) and a new uSD which I haven't tried before. I'll try cleaning the contact points too.
*Thanks - I've added more checklists to the OP
@combustiblemonkey:
Thanks for the assurance.

I convinced my friend to buy a nook, rooted it for him, and was bricked within 2 days. Here is how I fixed it
EDIT: I tried to post a link, but was unable. If you go to theunlockr(dot)com and search for how to restore nook color to stock, there is a detailed article.
This took me almost 2 days of reboots, black screens, and freezing. I would get into CWR, and it would freeze. Had to reboot, got the black screen of death. Literally, a couple hundred reboots before it said that the OS has successfully installed, and of course, it froze again. Many more reboots, and it was finally at stock. I figure getting it back to stock was enough to return it.

Dr-Rockso said:
I convinced my friend to buy a nook, rooted it for him, and was bricked within 2 days. Here is how I fixed it
EDIT: I tried to post a link, but was unable. If you go to theunlockr(dot)com and search for how to restore nook color to stock, there is a detailed article.
This took me almost 2 days of reboots, black screens, and freezing. I would get into CWR, and it would freeze. Had to reboot, got the black screen of death. Literally, a couple hundred reboots before it said that the OS has successfully installed, and of course, it froze again. Many more reboots, and it was finally at stock. I figure getting it back to stock was enough to return it.
Click to expand...
Click to collapse
Thanks, this is the direct link:
http://theunlockr.com/2011/02/14/how-to-restore-the-nook-color-to-stock
All instructions were taken from XDA, plus no guarantee it's the most updated
Moving on, great to hear you've gotten it back to stock. Man, you've got GREAT patience, a couple hundred reboots?
1) Was the SD inserted in or not? Curious about the OS successfully installed message, which is the result of 8x unsuccessful reboots without SD inserted.
2) Could you also provide a more detailed account on what you did? Looking forward to hear - thanks.

Hi rawfish
I also have this issue and have been trying many things. My nook did boot nooter 0.2 (the light went green) but I couldn't get Win 7 or Ubuntu to connect to it. My screen never changes at all, no backlight even. Seems this may be a larger issue than most believe it to be, especially for people like us who don't live in the US.

chrysilis said:
Hi rawfish
I also have this issue and have been trying many things. My nook did boot nooter 0.2 (the light went green) but I couldn't get Win 7 or Ubuntu to connect to it. My screen never changes at all, no backlight even. Seems this may be a larger issue than most believe it to be, especially for people like us who don't live in the US.
Click to expand...
Click to collapse
If you can find a friend or person in your area having the same device, you can try to see if an SD you burned work on theirs. If it works on theirs, it's possible that your SD slot is defective - but then comes the question of it being in working condition before the bricking happened, right?
I still think mine's recoverable, as with yours. Could be a bad SD or reader, or bad contacts. I'm going to try out using another reader plus purchase an el-cheapo branded SD. I'm also going to try formatting it via another PC in a linux environment and messing around with the partitions.
I understand the trouble you may have taken to get the device - and this happens. All the best mate, and do cheer up, don't give up.

rawfish said:
Thanks, this is the direct link:
All instructions were taken from XDA, plus no guarantee it's the most updated
Moving on, great to hear you've gotten it back to stock. Man, you've got GREAT patience, a couple hundred reboots?
1) Was the SD inserted in or not? Curious about the OS successfully installed message, which is the result of 8x unsuccessful reboots without SD inserted.
2) Could you also provide a more detailed account on what you did? Looking forward to hear - thanks.
Click to expand...
Click to collapse
When I finally got it to work, the SD card was installed with the 1.0.1 stock OS on it, and CWR. The problem was that that (+) and (-) would only occasionally work. And if they did, it would usually freeze. I would be able to format system, but it would freeze if I tried to format data. Powered off, and I would get the black screen of death (BSoD). Once this happened, I would plug it into my computer so that I could hear the chime indicating a new device was plugged in. I found that ejecting the SD and then rebooting would sometimes help get rid of the BSoD. Then another power down, plug in the SD, and start again. Also, holding the N, +, and Power would sometimes help in launching CWR. I would usually have to hold for 60 seconds, but it would finally launch. It seemed like the nook was trying to run a process that slowing it down and causing it to freeze, but I couldn't figure out what it was. If I would wait an hour, it would boot CWR and allow me to format system and data, but then it would freeze when I would try to install the zip.
The successful install message was in CWR. It said Install From SD Card Complete, or something like that. After that, I still had to do the 8 reboots. It would load up the stock welcome screen and freeze. 8 reboots later, I got the video lady. Good enough to return it to the store.
It really was just persistence. It would usually take an hour of reboots before I was able to try to install the zip, and it probably failed on me 15+ times. The status bar would get half way, and freeze. Then I had to begin again. If it had been my nook instead of my friends, I probably would have given up. I wish I could be more specific, but unfortunately I am new to all of this. My nook rooted just fine, and fixing his is really my only experience with CWR. I just kept going until it worked.
Good luck! It is a pain in the ass, but it can happen.

rawfish said:
If you can find a friend or person in your area having the same device, you can try to see if an SD you burned work on theirs. If it works on theirs, it's possible that your SD slot is defective - but then comes the question of it being in working condition before the bricking happened, right?
I still think mine's recoverable, as with yours. Could be a bad SD or reader, or bad contacts. I'm going to try out using another reader plus purchase an el-cheapo branded SD. I'm also going to try formatting it via another PC in a linux environment and messing around with the partitions.
I understand the trouble you may have taken to get the device - and this happens. All the best mate, and do cheer up, don't give up.
Click to expand...
Click to collapse
My wife has one as well so am able to test using that and the SD works fine in hers. The whole screen not turning on thing is weird though, does your screen turn on?
We bought them when on honeymoon in America so didn't have to pay a shipper or anything

Deleting the partitions manually with Gparted and using dd to burn the SDs and making sure the correct partitions are bootable doesn't seem to work. Last night I retried a lot of the previously attempted options, with no results.
It's weird to think that a working SD slot and a slew of cards will suddenly malfunction, but for now that seems like the most plausible reason why my NC can't boot anything off SD.
To think back how it all started, the device suddenly rebooted from HC preview v0.4 to stock BN 1.01 (rooted + installed CWR on eMMC) while the SD is inserted, then upon another reboot it simply stays dead, this gives me reason to believe that the internal boot partition is corrupted, and SD slot nuked hardware-wise.
Hmmm, really hoping to find someone else who has the same device, in my area.

Right now I am at the Black Screen of Death as well...
I think Barnes should refund me, but I am willing to do some tests for the good of society.

Steelfan555 said:
Right now I am at the Black Screen of Death as well...
I think Barnes should refund me, but I am willing to do some tests for the good of society.
Click to expand...
Click to collapse
Sorry to hear that, and don't give up! Hope you took a look at the other threads, and this little pseudo checklist I made in the OP. Do share the outcome

Thank you Rawfish. The first option, the Dummies Guide to Fixing 'My Nook won't boot'
was what I needed to get started on the right track again. Though I'm not sure anyone wants to know how I ended up here, I'm grateful to those that put in the time and effort to find any of these solutions.
Thank you!

FroztIkon said:
Thank you Rawfish. The first option, the Dummies Guide to Fixing 'My Nook won't boot'
was what I needed to get started on the right track again. Though I'm not sure anyone wants to know how I ended up here, I'm grateful to those that put in the time and effort to find any of these solutions.
Thank you!
Click to expand...
Click to collapse
Update:
Ok, so after running through it, I ended up getting stuck on the boot screen that shows N. If I powered off, it would restart and get stuck at that screen. I tried the 8 shutdowns (it installed new software), but afterwards, it was still stuck. So, I tried another method I found on the forums. I powered off holding the N button and power, which caused it to boot back up and do a factory reset. I now have a factory fresh Nook.

Okay, it's been a while since I kept this thread updated - I contacted BN and had the device sent back, apparently the SD slot failed so they sent me a new one. I'm just wondering if it's sheer concidence that it happened, as I was tinkering with Nookie Honey preview v0.4, when the hardware suddenly failed.
Oh well, I guess the NC still remains as a 99.99% unbrickable device - with the 0.01% being related to the ambiguous root cause to my case.
I now have 2 NCs (one from the RMA process, another one from the $199 eBay deal.

[Q] Another Nook Black Screen

I've read through the Dummies Guide and researched plenty of posts. The Nook will not boot by itself or with an SD card:
1. The SD card boots my other Nook Color just fine.
2. Have tried multiple boot images 128mb, 4gb, 8gb, and the CW 1gb. No go.
3. Tried 8 failed attempts (but without seeing anything on screen I do not know if I did it right)
4. Tried Multiple combination of holding power, n, volume buttons.
5. Disassembled Nook and disconnected the battery overnight.
6. Fully charged battery afterwards and nothing still.
7. Tried all this with and without a bootable SD inserted.
Computer does the whole recognize OMAP 3630 for a split second and loses it. From This Thread, I gather that I might be bricked. However This Guy seemed to have come back from this state. I am a little unsure as to how. I couldn't quite understand his final post about how he fixed it. It sounds like he just found a different boot.img (which I also tried ..... i think) and had finally found a SD card boot image that worked.
I have exhausted my research ability. I have no history on this Nook. I bought my working Nook off Ebay and the seller just threw this in with it along with a error 28 Ipad. I just hate to be defeated by an electronic. The only thing I have not tried is actually replacing the battery, but it seems to work fine. It discharges and recharges. So I am not sure where I stand on this. I believe I have tried everything, but maybe a Nook's nand is like an finicky Xbox and I can short some pins or something to give it electro shock treatment.
Anyway, I have absolutely no problem trying "crazy" ideas that risk frying this thing. Maybe I missed something, maybe I haven't. I apologize if I posted this in the wrong section.

I have a Nook that experienced everything you're saying.
After trying everything multiple times and getting nowhere I assumed it was a hardware problem.
I got a new motherboard off of ebay and replaced it and it's been fine ever since.
I'm not sure which part failed though since everything's integrated on the one board.

I'm going to go through and play with the board a bit. Time to test for shorts.

TWRP, eMMC errors, and a lot of questions...

So I have one great Note 4 that runs fine. A second Note 4, given to me appearing to be a paper weight, has been with some effort rescusitated. But no, the eMMC errors have not gone totally.
This "bad" phone, however, is allowing me to fully exercise some of my curiosity. And in the process, no matter what happens, I hope I can get a few more answers about things. I know about the little app that keeps the phone from going to sleep and stablizes it... that works on the phone unless it gets turned off. And then the whole cycle of trying to start it again (the freezer trick, the holding of buttons, the pulling of the battery... sigh).
My latest gambit has been to go into TWRP and reformat /system /data and /cache (the only directories where I'm allowed to do so) to f2fs. In fact, just to really wipe this baby as clean as I possibly could, I reformatted them back to ext4, then back again to f2fs. I then installed a custom rom (the official CM 14.1). It appears to have installed over the top of the f2fs without trouble.
But of course I am freewheeling it here. I do not know very much about what is going on down inside there.
My questions:
1. What "hidden" directories are there that TWRP isn't showing me? Is there any possibility that if I could reformat them (and not destroy the phone) it might help with the eMMC errors? How would I do that if I in fact can?
2. When I reformat the directories from one format to another, am I actually wiping them or not? (I've read long pages about people suggesting that Android phones are terribly hard to actually wipe all data off.)
3. Is there any other possible cause for the eMMC errors than bad physical memory? I understand that bad memory chip *is* one obvious cause... but are there other causes that could in fact kick up an eMMC error that isn't really about the memory chip?
I'll post any other questions if and when I think of them. Worst happens, I mess this phone up so bad it won't reboot at all. I'm not too worried about that.
All thoughts welcome. I can experiment without caring too much.

I have read elsewhere that the problem could be caused by having a micro sd inserted in the phone.

Intensivefire said:
I have read elsewhere that the problem could be caused by having a micro sd inserted in the phone.
Click to expand...
Click to collapse
Yes, I've read that also. Tried all sorts of experiments with and without micro-sd card inserted. Using a Wake Lock app from playstore (set on mid-range) allows the phone to do and be nicely. But shut it off and I have to freeze it for 5 min before it will restart. So... hopefully the Chinese mb card I bought today will actually work. Providing I can in fact open the phone without busting it. (There's some good clues on youtube which is nice.)

shonkin said:
Yes, I've read that also. Tried all sorts of experiments with and without micro-sd card inserted. Using a Wake Lock app from playstore (set on mid-range) allows the phone to do and be nicely. But shut it off and I have to freeze it for 5 min before it will restart. So... hopefully the Chinese mb card I bought today will actually work. Providing I can in fact open the phone without busting it. (There's some good clues on youtube which is nice.)
Click to expand...
Click to collapse
emmc errors on note 4 is well known hardware failure , its time for you to replace emmc chip or system board

zfk110 said:
emmc errors on note 4 is well known hardware failure , its time for you to replace emmc chip or system board
Click to expand...
Click to collapse
Yes, I said that in my first post. My point was that it is possible other causes for the error message just might exist. But all that is moot now... I did in fact order a new motherboard. But in the meantime, when I went to dissect the phone according to instructions on youtube, I found out too late that the author of said instructions was fairly clueless as far as a successful end result. The phone is dead, dead, dead. Lucky for me, it wasn't my main Note 4, which is just fine.

Here is a 100% hardware fix for this issue that anyone can do with no tools or specia
Here is a 100% hardware fix for this issue that anyone can do with no tools or special equipment.
It really works. Give it a try. ?
https://youtu.be/jLPHWtb0StI